abrt 1.0.8 detected a crash. architecture: x86_64 Attached file: backtrace cmdline: /usr/bin/python /usr/bin/gwibber component: gwibber executable: /usr/bin/gwibber kernel: 2.6.32.10-90.fc12.x86_64 package: gwibber-1:2.29.92.1-1.fc12 reason: start_local_couchdb.py:132:run_couchdb:RuntimeError: Can not start couchdb. release: Fedora release 12 (Constantine)
Created attachment 405114 [details] File: backtrace
How to reproduce ----- 1.start gwibber 2. 3.
Package: gwibber-1:2.30.0.1-1.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. go to the about this app 2. view the info 3. try to close the window
Package: gwibber-1:2.29.92.1-1.fc12 Architecture: x86_64 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1.just start it 2. 3.
Try the latest package in updates-testing and let me know if it still fails to start.
Package: gwibber-1:2.30.0.1-6.fc12 Architecture: x86_64 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1. add gwibber.desktop to the autostartup 2. network manager do not connect automatically to wireless network
I'm not sure how these two items are connected.
Package: gwibber-1:2.30.0.1-6.fc12 Architecture: x86_64 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1.Start gwibber at login 2. 3. Comment ----- I have gwibber set to start at login into gnome. I was just logging and apps were starting.
Package: gwibber-1:2.30.0.1-6.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.start gwibber 2. 3.
Package: gwibber-1:2.30.0.1-6.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- N/A Comment ----- Spurious crash happened when starting Gwibber.
Package: gwibber-1:2.30.0.1-6.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. open gwibber 2. 3.
Package: gwibber-1:2.30.0.1-6.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Start Gwibber at login 2. 3.
Package: gwibber-1:2.30.0.1-6.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.open gwipper 2.it crashes instantly 3.
Package: gwibber-1:2.30.0.1-6.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Start Gwibber 2. FAIL 3. Comment ----- Not sure what happened, exactly. I just started Gwibber, like normal, and it failed!
Package: gwibber-1:2.30.0.1-6.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Simply logged into my desktop after machine had booted up
Package: gwibber-1:2.30.0.1-6.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.Start it 2. 3.
Package: gwibber-1:2.30.0.1-6.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Open Gwibber Comment ----- Boot your computer and start gwibber, it always crashes for the first time. But when you start it again, it'll run well. Reboot your computer, and start gwibber, it'll fail again.
Package: gwibber-1:2.30.0.1-6.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Start computer and login 2. Open Gwibber 3. Crash Comment ----- The error message on ABRT said that it couldn't start the db which is why I said that I had just started and logged into my computer.
Package: gwibber-1:2.30.0.1-6.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. start the application 2. 3.
gwibber-2.31.2-7.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/gwibber-2.31.2-7.fc12
gwibber-2.31.2-7.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/gwibber-2.31.2-7.fc13
gwibber-2.31.2-7.fc13 has been pushed to the Fedora 13 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update gwibber'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/gwibber-2.31.2-7.fc13
gwibber-2.31.2-7.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update gwibber'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/gwibber-2.31.2-7.fc12
Package: gwibber-1:2.30.0.1-6.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) Comment ----- Just started Gwibber after login
Package: gwibber-1:2.30.0.1-6.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. start the application 2. 3. Comment ----- Gwibber is launched when i start my gnome session
gwibber-2.31.4-1.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/gwibber-2.31.4-1.fc12
gwibber-2.31.4-1.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/gwibber-2.31.4-1.fc13
gwibber-2.31.4-1.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update gwibber'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/gwibber-2.31.4-1.fc12
gwibber-2.31.4-1.fc13 has been pushed to the Fedora 13 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update gwibber'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/gwibber-2.31.4-1.fc13
gwibber-2.31.4-1.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
gwibber-2.31.4-1.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.