Created attachment 488942 [details] screenshot showing message Description of problem: Unhelpful error message after submitting backtrace: "Reporting finished with exit code 139" Version-Release number of selected component (if applicable): abrt-2.0.0-2.fc15.x86_64 abrt-addon-ccpp-2.0.0-2.fc15.x86_64 abrt-addon-kerneloops-2.0.0-2.fc15.x86_64 abrt-addon-python-2.0.0-2.fc15.x86_64 abrt-desktop-2.0.0-2.fc15.x86_64 abrt-gui-2.0.0-2.fc15.x86_64 abrt-libs-2.0.0-2.fc15.x86_64 abrt-plugin-bugzilla-2.0.0-2.fc15.x86_64 abrt-plugin-logger-2.0.0-2.fc15.x86_64 How reproducible: Tried once. Steps to Reproduce: 1. Submit backtrace to bugzilla. 2. 3. Actual results: "Reporting finished with exit code 139" Expected results: Informative error message. Additional info:
This may be related. Snippet from /var/log/messages: Mar 30 15:37:25 fir kernel: [ 5252.123918] abrt-action-bug[2400]: segfault at 48 ip 0000003227a3e1f3 sp 00007fffd0707f68 error 4 in libglib-2.0.so.0.2800.4[3227a00000+115000] Mar 30 15:37:25 fir abrt[2403]: saved core dump of pid 2400 (/usr/bin/abrt-action-bugzilla) to /var/spool/abrt/abrt-action-bugzilla-coredump (12550144 bytes)
Seems like the abrt-action-bugzilla plugin died on SEGV. Does abrt noticed that crash? Can you send us a backtrace from that crash?
(In reply to comment #2) > Seems like the abrt-action-bugzilla plugin died on SEGV. Does abrt noticed that > crash? Can you send us a backtrace from that crash? abrt didn't notice, but there is a core file. I'll open a new bug, if I can get a backtrace. [joeblow@fir abrt]$ ls -lF total 3636 -rw-r--r--. 1 root root 12550144 Mar 30 15:37 abrt-action-bugzilla-coredump drwxrwxr-x. 2 abrt joeblow 4096 Mar 31 08:20 ccpp-2011-03-29-13:47:38-2362/ drwxrwxr-x. 2 abrt root 4096 Mar 30 16:12 ccpp-2011-03-29-13:57:16-1251/ drwxrwxr-x. 2 abrt joeblow 4096 Mar 31 08:20 ccpp-2011-03-29-14:45:55-23694/ drwxrwxr-x. 2 abrt joeblow 4096 Mar 31 08:20 ccpp-2011-03-29-15:55:36-1595/ drwxrwxr-x. 2 abrt joeblow 4096 Mar 31 08:20 ccpp-2011-03-30-14:15:50-1559/ drwxr-x---. 2 abrt root 4096 Mar 30 16:12 ccpp-2011-03-30-16:12:54-1198/ -rw-------. 1 root root 13 Mar 30 16:12 last-ccpp [joeblow@fir abrt]$ file abrt-action-bugzilla-coredump abrt-action-bugzilla-coredump: ELF 64-bit LSB core file x86-64, version 1 (SYSV), SVR4-style, from 'abrt-action-bugzilla -c /etc/abrt/plugins/Bugzilla.conf'
Same here: Logging into Bugzilla at https://bugzilla.redhat.com Checking for duplicates Bug is already reported: 681057 Bug 681057 is a duplicate, using parent bug 674850 Bug 674850 is a duplicate, using parent bug 669859 No abrt report after this stop.
*** This bug has been marked as a duplicate of bug 692590 ***
Nikola, I am reopening to track the unhelpful error message issue: What does "exit code 139" mean? The underlying problem is tracked here: Bug 692590 - abrt-action-bugzilla segfault
(In reply to comment #6) > Nikola, I am reopening to track the unhelpful error message issue: > What does "exit code 139" mean? when application segfaults it returns exit code 139. You should NEVER see this message ;)
(In reply to comment #7) > (In reply to comment #6) > > Nikola, I am reopening to track the unhelpful error message issue: > > What does "exit code 139" mean? > > when application segfaults it returns exit code 139. You should NEVER see this > message ;) OK, but it would be helpful to report a user-readable string in addition to the exit code. Closing as duplicate again. *** This bug has been marked as a duplicate of bug 692590 ***