On RHEL 10, TAB completion for the `oscap` {}command does not work as expected. When attempting to auto-complete file paths, bash prints an error and does not complete the path. This can cause the command to run with an incorrect argument and fail.

This issue affects usability of the `oscap` command but does not impact OpenSCAP functionality when full paths are entered manually.

Steps to Reproduce

1. Ensure openscap-scanner is installed.

1. Navigate to a directory containing SCAP content:

 
~~~
cd /usr/share/xml/scap/ssg/content
ls
ssg-rhel10-ds.xml
~~~

1. Attempt to use TAB completion:

~~~

oscap info --fetch-remote-resources /usr/share/xml/scap/ssg/content/<TAB>

~~~

Actual Results

Bash prints the following error:

~~~

-bash: comp_split_longopt: command not found

~~~

Tab completion fails, and pressing Enter executes the command with the uncompleted directory path, resulting in:

~~~

Could not determine document type
OpenSCAP Error: Document is empty
Unable to parse XML at: '/usr/share/xml/scap/ssg/content/'

~~~

Expected Result

• No bash errors during tab completion

• File path autocompletes correctly to `ssg-rhel10-ds.xml`

• `oscap info` successfully processes the file

Additional Information

Installed package versions:

~~~

openscap.x86_64            1:1.4.3-1.el10_1
openscap-scanner.x86_64    1:1.4.3-1.el10_1
bash.x86_64                5.2.26-6.el10
bash-completion.noarch     1:2.11-16.el10

~~~

The bash completion file involved is:

~~~

/etc/bash_completion.d/oscap

~~~

This file references `comp_split_longopt`, which does not exist in the current bash-completion package shipped with RHEL 10.

Impact

• Breaks shell usability for `oscap`

• Causes misleading OpenSCAP errors unrelated to the actual issue

• Affects all users relying on TAB completion