Created attachment 682232 [details] abrt-gui -v when trying to repport two bugs Description of problem: Version-Release number of selected component (if applicable): Nom : abrt Architecture : x86_64 Version : 2.0.20 Révision : 1.fc18 How reproducible: always Steps to Reproduce: 1. Launch abrt-gui by application menu / notification / command line 2. Click on "Rapporter" (probably report in english) or click on "Preferences" Actual results: Nothing append Expected results: repport a bug or show preferences Additional info: - bugs looks like to be correctly detected, only the user interface is crashed : output of nl /var/log/messages|grep abrt|fpaste http://paste.stg.fedoraproject.org/3268/ - output of ll /etc/abrt/abrt.conf*|fpaste http://paste.stg.fedoraproject.org/3269/ - output of ll /var/spool/abrt/ccpp-2013-01-17-19:27:11-1683|fpaste http://paste.stg.fedoraproject.org/3270/
Thank you for taking the time to report this bug. Unfortunately, we can't diagnose the problem without your cooperation. If you have time run the following command and post an output here. $ report-gtk -vvv -e report_uReport -e analyze_CCpp -e "collect_*" -e report_Bugzilla -e post_report -- /var/spool/abrt/ccpp-2013-01-17-19:27:11-1683
Created attachment 682391 [details] Output of report-gtk As requested, the output of the command. Do not hesitate to ask for more if needed.
Just to be sure. You started the command. It printed out the attached output, no window appeared and command successfully finished? Which version of libreport do you have installed?
No window appeared and command did not finished, I had to stop it after a minute Nom : libreport Architecture : x86_64 Version : 2.0.20 Révision : 1.fc18 But it looks like ABRT is back to normal... And I'm actually sending reports with ABRT. Now, when I launch your command I have a window with many informations from bug report. I haven't changed anything, just reboot a few times since this morning. Notable change this time : I had hundreds of calendar meetings showed one after another. I'll send the file again.
I do not know why. But I wanted to launch your command again and ABRT doesn't work anymore. I post right now two files, Yum log file if updates have any impact. Output of the following command : [root@localhost jb]# report-gtk -vvv -e report_uReport -e analyze_CCpp -e "collect_*" -e report_Bugzilla -e post_report -- /var/spool/abrt/ccpp-2013-01-17-19:27:11-1683 2> hop-root.txt
Created attachment 682967 [details] Command output (it showed the window and apparently sended it to bugzilla)
Created attachment 682968 [details] Yum log
(In reply to comment #5) > I do not know why. But I wanted to launch your command again and ABRT > doesn't work anymore. > > I post right now two files, Yum log file if updates have any impact. > Output of the following command : > [root@localhost jb]# report-gtk -vvv -e report_uReport -e analyze_CCpp -e > "collect_*" -e report_Bugzilla -e post_report -- > /var/spool/abrt/ccpp-2013-01-17-19:27:11-1683 2> hop-root.txt Thank you for all your comments! In order to diagnose the problem I need to known the function in which report-gtk is stuck. The following commands should generate a backtrace (http://fedoraproject.org/wiki/StackTraces): $ sudo debuginfo-install libreport $ gdb `which report-gtk` -p `ps aux | grep report-gtk | grep -v grep | tr -s " " | cut -f2 -d" "` --batch --eval-command "t a a bt full" | tee backtrace.txt And it would be useful to provide an output of strace: $ strace report-gtk -vvv -e report_uReport -e analyze_CCpp -e "collect_*" -e report_Bugzilla -e post_report -- /var/spool/abrt/ccpp-2013-01-17-19:27:11-1683 2>&1 | tee needed.log
Created attachment 686164 [details] Backtace gdb - comment 8
Created attachment 686167 [details] Strace report-gtk - comment 8
Created attachment 686171 [details] Strace report-gtk - comment 8 - after manualy killing all abrt processes As requested. The output of the two commands. I did the second one two times to make sure it as full expected effect. Please let me know if I can do anything else. Thanks for your help.
report-gtk got stuck in secret_prompt() function and it means that report-gtk will wait until DBus Secret Service API emits the Completed signal. At this moment you should see some kind of authorization dialog, do you? Which implementation of Secret Service API do you have installed? Is it gnome-keyring or ksecretsservice?
Fixed in git commit f29ac1812afa76303b9e407fab2686162c11e0aa Author: Jakub Filak <jfilak> Date: Tue Feb 19 09:37:29 2013 +0100 ss: add a timeout to the waiting for the Completed signal - closes rhbz#901467 Signed-off-by: Jakub Filak <jfilak> Signed-off-by: Martin Milata <mmilata>
(not sure the problem below is related to this bug report:) abrt-2.1.1-1.fc18.x86_64 from F18 testing repo is not saving user/password but telling me "Secret service is not available, your settings won't be saved" Using gnome-keyring-3.6.2-3.fc18.x86_64. No idea how to enable the convenient auto-login which worked nicely in F17. My F18 laptop was installed from scratch (no upgrade from F17).
(In reply to comment #14) I forgot to copy this problem: [root@localhost neteler]# abrt-gui Failed to open connection to D-Bus session bus: The connection is closed There is no configurable option for: '(null)' [root@localhost neteler]#
(In reply to comment #15) > (In reply to comment #14) > > I forgot to copy this problem: > > [root@localhost neteler]# abrt-gui > Failed to open connection to D-Bus session bus: The connection is closed > There is no configurable option for: '(null)' > > [root@localhost neteler]# Thank you for taking the time to report this misbehaviour. If you have time and can still reproduce the misbehaviour, please file a new bugzilla ticket. Would be useful to know which desktop environment you use and attach the ~/.xsession_errors and ~/.cache/gdm/session.log files and provide a text output of 'sudo grep gnome-keyring-daemon /var/log/messages' and 'abrt-gui -vvv'
abrt-2.1.2-1.fc18,libreport-2.1.2-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/abrt-2.1.2-1.fc18,libreport-2.1.2-1.fc18
Package abrt-2.1.2-1.fc18, libreport-2.1.2-1.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing abrt-2.1.2-1.fc18 libreport-2.1.2-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-4176/abrt-2.1.2-1.fc18,libreport-2.1.2-1.fc18 then log in and leave karma (feedback).
Package abrt-2.1.2-2.fc18, libreport-2.1.2-2.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing abrt-2.1.2-2.fc18 libreport-2.1.2-2.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-4176/abrt-2.1.2-2.fc18,libreport-2.1.2-2.fc18 then log in and leave karma (feedback).
abrt-2.1.2-2.fc18, libreport-2.1.2-2.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.