Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionMiroslav Svoboda
2011-09-19 14:37:32 UTC
Created attachment 523847[details]
Screenshot of console output.
Description of problem:
The abrt-cli application does not behave as expected. I encountered two issues while testing abrt-cli for documentation purposes.
Firstly, when running the "abrt-cli report /problem_data_directory" command in a terminal window in GNOME desktop GUI, the problem report opens up the ABRT GUI instead of proceeding with the reporting process in the terminal.
Secondly, when running the "abrt-cli report /problem_data_directory" command in the virtual console or in the terminal connected remotely via ssh, ABRT does not proceed with reporting as expected but fails with the "Invalid input, program exiting..." message.
Version-Release number of selected component (if applicable):
[arcanus@rhel6 ~]$ rpm -qa|grep abrt
abrt-gui-2.0.4-10.el6.x86_64
abrt-addon-python-2.0.4-10.el6.x86_64
abrt-addon-ccpp-2.0.4-10.el6.x86_64
abrt-cli-2.0.4-10.el6.x86_64
abrt-libs-2.0.4-10.el6.x86_64
abrt-addon-kerneloops-2.0.4-10.el6.x86_64
abrt-2.0.4-10.el6.x86_64
abrt-desktop-2.0.4-10.el6.x86_64
How reproducible:
always
Steps to Reproduce:
1-a. Open up terminal window in desktop GUI and make sure that there exist problem data on the system, for example:
~]$ abrt-cli list --full
Directory: /home/<user>/.abrt/spool/<problem_data_directory>
count: 1
executable: /usr/bin/gedit
package: gedit-2.28.4-3.el6
time: Sun 18 Sep 2011 03:59:57 PM CEST
uid: 500
2-a. Run the "abrt-cli report" command on existing problem data, for example:
~]$ abrt-cli report /home/<user>/.abrt/spool/<problem_data_directory>
1-b. Log in the virtual console or log in the system remotely using the ssh protocol
2-b. Run the "abrt-cli report" command on existing problem data
~]$ abrt-cli report /home/<user>/.abrt/spool/<problem_data_directory>
Actual results:
a) ABRT opens up the problem description window in ABRT GUI.
b) Usage: abrt-cli report [options] [<dump-dir>]...
-v, --verbose Be verbose
~]$ How you would like to analyze the problem?
1) Collect .xsession-errors
2) Local GNU Debugger
Select analyzer: Select analyzer: Select analyzer: Invalid input, program exiting...
Expected results:
ab) ABRT proceeds with the problem reporting process in the command line:
How you would like to analyze the problem?
1) Local GNU Debugger
2) Retrace Server
Select analyzer:_
Additional info:
Created attachment 523847 [details] Screenshot of console output. Description of problem: The abrt-cli application does not behave as expected. I encountered two issues while testing abrt-cli for documentation purposes. Firstly, when running the "abrt-cli report /problem_data_directory" command in a terminal window in GNOME desktop GUI, the problem report opens up the ABRT GUI instead of proceeding with the reporting process in the terminal. Secondly, when running the "abrt-cli report /problem_data_directory" command in the virtual console or in the terminal connected remotely via ssh, ABRT does not proceed with reporting as expected but fails with the "Invalid input, program exiting..." message. Version-Release number of selected component (if applicable): [arcanus@rhel6 ~]$ rpm -qa|grep abrt abrt-gui-2.0.4-10.el6.x86_64 abrt-addon-python-2.0.4-10.el6.x86_64 abrt-addon-ccpp-2.0.4-10.el6.x86_64 abrt-cli-2.0.4-10.el6.x86_64 abrt-libs-2.0.4-10.el6.x86_64 abrt-addon-kerneloops-2.0.4-10.el6.x86_64 abrt-2.0.4-10.el6.x86_64 abrt-desktop-2.0.4-10.el6.x86_64 How reproducible: always Steps to Reproduce: 1-a. Open up terminal window in desktop GUI and make sure that there exist problem data on the system, for example: ~]$ abrt-cli list --full Directory: /home/<user>/.abrt/spool/<problem_data_directory> count: 1 executable: /usr/bin/gedit package: gedit-2.28.4-3.el6 time: Sun 18 Sep 2011 03:59:57 PM CEST uid: 500 2-a. Run the "abrt-cli report" command on existing problem data, for example: ~]$ abrt-cli report /home/<user>/.abrt/spool/<problem_data_directory> 1-b. Log in the virtual console or log in the system remotely using the ssh protocol 2-b. Run the "abrt-cli report" command on existing problem data ~]$ abrt-cli report /home/<user>/.abrt/spool/<problem_data_directory> Actual results: a) ABRT opens up the problem description window in ABRT GUI. b) Usage: abrt-cli report [options] [<dump-dir>]... -v, --verbose Be verbose ~]$ How you would like to analyze the problem? 1) Collect .xsession-errors 2) Local GNU Debugger Select analyzer: Select analyzer: Select analyzer: Invalid input, program exiting... Expected results: ab) ABRT proceeds with the problem reporting process in the command line: How you would like to analyze the problem? 1) Local GNU Debugger 2) Retrace Server Select analyzer:_ Additional info: