Bug 560883
| Summary: | [abrt] crash in gwibber-1:2.0.0-2.478bzr.fc12 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Dwayne Bailey <dwayne> | ||||
| Component: | gwibber | Assignee: | Tom "spot" Callaway <tcallawa> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 12 | CC: | tcallawa | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | i686 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | abrt_hash:a0948291 | ||||||
| Fixed In Version: | gwibber-2.31.4-1.fc12 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2010-08-20 01:54:40 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
Created attachment 388197 [details]
File: backtrace
gwibber-2.29.92.1-1.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/gwibber-2.29.92.1-1.fc12 I have just pushed a test update for gwibber-2.29.92.1. While I would not normally perform a major update to gwibber for released distributions, this update is important for the following reasons: * Gwibber 1.2.0 and 2.0.0 crash. A lot. Most of the reasons for these crashes are exposed feature functionality which was never implemented completely. These features are generally implemented properly in the 2.29.92.1 code, and so far, it has yet to crash on me in extensive testing. * Upstream is not maintaining the 1.2 or 2.0 branches at all, so any work done in those spaces is wasteful. I need your help to test this package, but first, you need to upgrade to it! There are two ways you can do this: 1. You can wait for it to go into updates-testing (this will happen in the next day or so), and then run: yum update --enablerepo=updates-testing gwibber 2. You can run these two commands: koji download-build --arch=noarch gwibber-2.29.92.1-1.fc12 yum update gwibber-2.29.92.1-1.fc12.noarch.rpm --nogpgcheck ***** Once you have the new gwibber installed, you should be able to immediately start using it, as it will migrate your old settings. Test it out, make sure it works, and if it looks like it resolves your issues, please, go to: https://admin.fedoraproject.org/updates/gwibber-2.29.92.1-1.fc12 Once there, leave a comment and give a +1. If it doesn't work well for you, please leave a comment and give a -1. Thanks! gwibber-2.29.92.1-2.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.29.92.1-2.fc12 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 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. |
abrt 1.0.4 detected a crash. architecture: i686 cmdline: /usr/bin/python /usr/bin/gwibber-daemon comment: I get one of these every few days component: gwibber executable: /usr/bin/gwibber-daemon kernel: 2.6.31.12-174.2.3.fc12.i686.PAE package: gwibber-1:2.0.0-2.478bzr.fc12 release: Fedora release 12 (Constantine) backtrace ----- Summary: TBa0948291 gintegration.py:46:notify:GError: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/gwibber/microblog/__init__.py", line 201, in process_opdata if not k in self.messages: self.new_message(v) File "/usr/lib/python2.6/site-packages/gwibber/server.py", line 215, in new_message self.show_notification_bubble(message) File "/usr/lib/python2.6/site-packages/gwibber/server.py", line 251, in show_notification_bubble n = gintegration.notify(message["sender"], body, image, expire_timeout) File "/usr/lib/python2.6/site-packages/gwibber/gintegration.py", line 46, in notify return notification.show() GError: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Local variables in innermost frame: title: 'Dimitris Glezos' notification: <pynotify.Notification object at 0xb5153fa4 (NotifyNotification at 0xb5101d80)> caps: ['actions', 'body', 'body-hyperlinks', 'body-markup', 'icon-static'] timeout: 5000 text: 'Lotte now shows context, developer comments & occurrences of translations: http://ow.ly/12IdT #transifex #contextrocks' icon: '/usr/share/pixmaps/gwibber.svg'