abrt 1.0.3 detected a crash. How to reproduce: Gwibber crashes at startup everytime. backtrace ----- Summary: TB2800fe58 traceback.py:13:_print:IOError: [Errno 5] Input/output error Traceback (most recent call last): File "/usr/bin/gwibber", line 55, in <module> from gwibber import client File "/usr/lib/python2.6/site-packages/gwibber/client.py", line 11, in <module> from . import gwui, config, configui, gintegration File "/usr/lib/python2.6/site-packages/gwibber/gwui.py", line 9, in <module> from . import gintegration, resources, config, configui File "/usr/lib/python2.6/site-packages/gwibber/resources.py", line 7, in <module> import os, sys, config, gtk File "/usr/lib/python2.6/site-packages/gwibber/config.py", line 106, in <module> logging.warn("desktopcouch is not available. %s. falling back to gconf", e) File "/usr/lib64/python2.6/logging/__init__.py", line 1441, in warning root.warning(*((msg,)+args), **kwargs) File "/usr/lib64/python2.6/logging/__init__.py", line 1042, in warning self._log(WARNING, msg, args, **kwargs) File "/usr/lib64/python2.6/logging/__init__.py", line 1143, in _log self.handle(record) File "/usr/lib64/python2.6/logging/__init__.py", line 1153, in handle self.callHandlers(record) File "/usr/lib64/python2.6/logging/__init__.py", line 1190, in callHandlers hdlr.handle(record) File "/usr/lib64/python2.6/logging/__init__.py", line 669, in handle self.emit(record) File "/usr/lib64/python2.6/logging/__init__.py", line 778, in emit self.handleError(record) File "/usr/lib64/python2.6/logging/__init__.py", line 720, in handleError traceback.print_exception(ei[0], ei[1], ei[2], None, sys.stderr) File "/usr/lib64/python2.6/traceback.py", line 124, in print_exception _print(file, 'Traceback (most recent call last):') File "/usr/lib64/python2.6/traceback.py", line 13, in _print file.write(str+terminator) IOError: [Errno 5] Input/output error Local variables in innermost frame: file: <open file '<stderr>', mode 'w' at 0x7f5390997140> terminator: str: Traceback (most recent call last): cmdline: /usr/bin/python /usr/bin/gwibber component: gwibber executable: /usr/bin/gwibber kernel: 2.6.31.9-174.fc12.x86_64 package: gwibber-1:2.0.0-2.478bzr.fc12 uuid: 2800fe58
Created attachment 384397 [details] File: backtrace
How to reproduce ----- 1. Run the system for a number of hours 2. Attempt to start gwibber from the Applications menu Comment ----- gwibber runs fine from the command line. I could use some advice on how to gather some better debugging information.
There are a LOT of gwibber 2.0.0 bugs. That codebranch is pretty darned bug-infested. That said, I need to push the latest revision for 2.0.0 into updates-testing to see if it makes anything better, please stay tuned.
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.