abrt 1.0.0 detected a crash. How to reproduce ----- 1. Use gwibber 2. Not sure what I did next to cause this 3. cmdline: /usr/bin/python /usr/bin/gwibber component: gwibber executable: /usr/bin/gwibber kernel: 2.6.31.6-134.fc12.i686.PAE package: gwibber-1:2.0.0-2.478bzr.fc12 uuid: 3f4864c3
Backtrace : Summary: TB3f4864c3 connection.py:620:call_blocking:TypeError: Don't know how which D-Bus type to use to encode type "NoneType" Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/gwibber/client.py", line 705, in on_close_stream self.microblog.unschedule_operation("gwibber", self.selected[SELECTED_OPID]) File "/usr/lib/python2.6/site-packages/dbus/proxies.py", line 140, in __call__ **keywords) File "/usr/lib/python2.6/site-packages/dbus/connection.py", line 620, in call_blocking message.append(signature=signature, *args) TypeError: Don't know how which D-Bus type to use to encode type "NoneType" Local variables in innermost frame: byte_arrays: False dbus_interface: com.Gwibber self: <dbus._dbus.SessionBus (session) at 0x9ca011c> args: ('gwibber', None) utf8_strings: False bus_name: com.Gwibber get_args_opts: {'byte_arrays': False, 'utf8_strings': False} object_path: /com/gwibber/Microblog timeout: -1.0 signature: vv e: Don't know how which D-Bus type to use to encode type "NoneType" message: <dbus.lowlevel.MethodCallMessage object at 0xa9f5100> method: unschedule_operation
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.