Description of problem: When running abrt, it requires root privelidges to gather information, if not given it can't generate the bug report properly. When opening ABRT, there is no prompt for root credentials, which there should be as it's a requirement Version-Release number of selected component (if applicable): ABRT-2.1.0 How reproducible: very reproducable Steps to Reproduce: run Abrt-gui as standard user and attempt to generate a backtrace on a bug, this fails as it cannot gather enough information Actual results: backtrace generation fails Expected results: no failure
Are you trying to generate a backtrace for a crash which happens in a program running with root privs?
Sounds like a dupe of #830389
I will need to investigate further, most of the time they are bugs that come up at boot, and mostly appear to be from services
(In reply to comment #0) > Steps to Reproduce: > run Abrt-gui as standard user and attempt to generate a backtrace on a bug, > this fails as it cannot gather enough information > > Actual results: > > backtrace generation fails How it fails? Please sshow the log messages.
Possibly an effect of fork_execv_on_steroids(uid=0) on "stolen" root crash. Possible solution is to stop changing uid.
Hopefully fixed by this commit: commit 1ca0fd4e0086991b80856e77eed32f1bd812e5d8 Author: Denys Vlasenko <vda.linux> Date: Mon Jun 25 12:20:14 2012 +0200 Don't setuid/setgid when we run eu-unstrip and gdb
abrt-2.0.11-1.fc17,libreport-2.0.11-1.fc17,btparser-0.18-2.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/abrt-2.0.11-1.fc17,libreport-2.0.11-1.fc17,btparser-0.18-2.fc17
Package abrt-2.0.11-1.fc17, btparser-0.18-2.fc17, libreport-2.0.12-1.fc17: * should fix your issue, * was pushed to the Fedora 17 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.11-1.fc17 btparser-0.18-2.fc17 libreport-2.0.12-1.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-11529/abrt-2.0.11-1.fc17,libreport-2.0.12-1.fc17,btparser-0.18-2.fc17 then log in and leave karma (feedback).
Package libreport-2.0.12-2.fc17, abrt-2.0.11-1.fc17, btparser-0.18-2.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing libreport-2.0.12-2.fc17 abrt-2.0.11-1.fc17 btparser-0.18-2.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-11529/abrt-2.0.11-1.fc17,libreport-2.0.12-2.fc17,btparser-0.18-2.fc17 then log in and leave karma (feedback).
Package abrt-2.0.12-1.fc17, libreport-2.0.13-1.fc17, btparser-0.18-2.fc17: * should fix your issue, * was pushed to the Fedora 17 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.12-1.fc17 libreport-2.0.13-1.fc17 btparser-0.18-2.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-11529/abrt-2.0.12-1.fc17,libreport-2.0.13-1.fc17,btparser-0.18-2.fc17 then log in and leave karma (feedback).
abrt-2.0.12-1.fc17, libreport-2.0.13-2.fc17, btparser-0.18-2.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.