Created attachment 492967 [details] abrt.log Description of problem: /var/log/messages has more ... Had to use report_Logger. "sudo abrt-gui" said it could not connect to keyring. Separate bug? Version-Release number of selected component (if applicable): abrt-2.0.0-5.fc15.x86_64 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
This is the directory with the report: [root@fir abrt]# pwd /var/spool/abrt [root@fir abrt]# ls -alF pyhook-2011-04-18-10:24:27-1530/ total 80 drwxr-x---. 2 abrt root 4096 Apr 18 10:38 ./ drwxr-xr-x. 10 abrt abrt 4096 Apr 18 10:24 ../ -rw-r-----. 1 abrt root 6 Apr 18 10:24 analyzer -rw-r-----. 1 abrt root 6 Apr 18 10:24 architecture -rw-r-----. 1 abrt root 427 Apr 18 10:24 backtrace -rw-r-----. 1 abrt root 0 Apr 18 10:24 cmdline -rw-r-----. 1 abrt root 108 Apr 18 10:35 comment -rw-r-----. 1 abrt root 4 Apr 18 10:24 component -rw-r-----. 1 abrt root 1 Apr 18 10:24 count -rw-r-----. 1 abrt root 446 Apr 18 10:38 event_log -rw-r-----. 1 abrt root 33 Apr 18 10:24 executable -rw-r-----. 1 abrt root 8 Apr 18 10:24 global_uuid -rw-r-----. 1 abrt root 3 Apr 18 10:24 hostname -rw-r-----. 1 abrt root 22 Apr 18 10:24 kernel -rw-r-----. 1 abrt root 28 Apr 18 10:24 os_release -rw-r-----. 1 abrt root 28 Apr 18 10:24 package -rw-r-----. 1 abrt root 91 Apr 18 10:24 reason -rw-r-----. 1 abrt root 10 Apr 18 10:24 time -rw-r-----. 1 abrt root 1 Apr 18 10:24 uid -rw-r-----. 1 abrt root 5 Apr 18 10:24 username -rw-r-----. 1 abrt root 8 Apr 18 10:24 uuid
Created attachment 492970 [details] /var/log/messages Snippet from /var/log/messages: Apr 18 10:24:24 fir dbus: [system] Activating service name='net.reactivated.Fprint' argv0='/lib64/dbus-1/dbus-daemon-launch-helper' Apr 18 10:24:24 fir dbus: [system] Successfully activated service 'net.reactivated.Fprint' Apr 18 10:24:26 fir gnome-session[1269]: Gdk-WARNING: gnome-session: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.#012 Apr 18 10:24:26 fir kernel: [ 597.889883] at-spi-bus-laun[1343]: segfault at 968 ip 00000036b3425321 sp 00007fffdd6a01f0 error 4 in libX11.so.6.3.0[36b3400000+139000] Apr 18 10:24:26 fir abrt[1510]: Can't open '/proc/1343/smaps': No such file or directory Apr 18 10:24:26 fir abrt[1510]: Can't open '/proc/1343/maps': No such file or directory Apr 18 10:24:26 fir abrt[1510]: saved core dump of pid 1343 (/usr/libexec/at-spi-bus-launcher) to /var/spool/abrt/ccpp-2011-04-18-10:24:26-1343.new/coredump (65536 bytes) Apr 18 10:24:26 fir abrtd: Directory 'ccpp-2011-04-18-10:24:26-1343' creation detected Apr 18 10:24:27 fir abrt-action-list-dsos.py: abrt: detected unhandled Python exception in /usr/bin/abrt-action-list-dsos.py Apr 18 10:24:27 fir abrtd: Corrupted or bad dump /var/spool/abrt/ccpp-2011-04-18-10:24:26-1343 (res:2), deleting Apr 18 10:24:27 fir abrtd: New client connected Apr 18 10:24:27 fir abrt-server[1552]: Saved Python crash dump of pid 1530 to /var/spool/abrt/pyhook-2011-04-18-10:24:27-1530 Apr 18 10:24:27 fir abrtd: Directory 'pyhook-2011-04-18-10:24:27-1530' creation detected Apr 18 10:24:27 fir abrtd: New dump directory /var/spool/abrt/pyhook-2011-04-18-10:24:27-1530, processing Apr 18 17:24:28 fir rtkit-daemon[1359]: Successfully made thread 1591 of process 1591 (/usr/bin/pulseaudio) owned by '42' high priority at nice level -11. Apr 18 17:24:28 fir rtkit-daemon[1359]: Failed to make thread 1592 RT: Operation not permitted Apr 18 17:24:28 fir rtkit-daemon[1359]: Failed to make thread 1592 RT: Operation not permitted
The problem is here: Apr 18 10:24:26 fir abrt[1510]: Can't open '/proc/1343/smaps': No such file or directory Apr 18 10:24:26 fir abrt[1510]: Can't open '/proc/1343/maps': No such file or directory ABRT can't save the maps and smaps file, this should be handled in the list-dsos.py "sudo abrt-gui" said it could not connect to keyring. Separate bug? - no, keyring is available only to the user who runs the desktop session, so this behaviour is correct.
Fixed in git.
(In reply to comment #3) ... Thanks, Jiri. > "sudo abrt-gui" said it could not connect to keyring. > Separate bug? > > - no, keyring is available only to the user who runs the desktop session, so > this behaviour is correct. Thanks for the explanation. How does a privileged user submit a report to BZ? (Without logging into a desktop session, which is inconvenient and risky.) This seems to work: $ sudo seahorse
(In reply to comment #5) > > How does a privileged user submit a report to BZ? > (Without logging into a desktop session, which is inconvenient and risky.) > You can still submit a bug, the only problem is that you need to fill username and password everytime, because ABRT wouldn't remember it.. if you don't like running gui apps as root you can use abrt-cli. I'd like to simplify the process of reporting root crashes, please see https://fedorahosted.org/abrt/ticket/210 for details. > This seems to work: > $ sudo seahorse Hm, can look into this, but the solution with polkit seems better...
*** Bug 697984 has been marked as a duplicate of this bug. ***
abrt-2.0.1-1.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/abrt-2.0.1-1.fc15
Package abrt-2.0.1-1.fc15: * should fix your issue, * was pushed to the Fedora 15 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing abrt-2.0.1-1.fc15' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/abrt-2.0.1-1.fc15 then log in and leave karma (feedback).
abrt-2.0.1-2.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/abrt-2.0.1-2.fc15
abrt-2.0.1-2.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.