abrt detected a crash. Attached file: backtrace cmdline: /usr/bin/python /usr/bin/gwibber component: gwibber executable: /usr/bin/gwibber kernel: 2.6.31.5-127.fc12.i686.PAE package: gwibber-1:1.2.0-3.349bzr.fc12 uuid: 08997608
Created attachment 374882 [details] File: backtrace
Are you able to reproduce this with version 2.0 in updates-testing?
no, i can reproduce it with version 2.0
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
How to reproduce ----- 1. Start gwibber after running the system for awhile 2. gwibber only starts if it is the first application run after log in. 3.
Package: gwibber-1:2.30.0.1-3.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Attempt to run gwibber 2. gwibber crashes with attached error 3. Comment ----- I have a clean install of fedora 13, with old home folder. Before running gwibber, I removed desktop-couch and gwibber files/directories from ~/.cache, ~/.config, ~/.local and ~/.gconf, where they existed. Attempting to run gwibber results in attached backtrace
(In reply to comment #8) > Attempting to run gwibber results in attached backtrace Could you please attach the backtrace?
Created attachment 409587 [details] Backtrace
Weird. I'm wondering if this has something to do with older dbus configs. Can you create a brand new user (with brand new home folder) and try to reproduce this failure?
Here's what happens when I try to run gwibber in a brand new account: [test@Strider ~]$ gwibber ** (gwibber:3230): WARNING **: Trying to register gtype 'WnckWindowState' as enum when in fact it is of type 'GFlags' ** (gwibber:3230): WARNING **: Trying to register gtype 'WnckWindowActions' as enum when in fact it is of type 'GFlags' ** (gwibber:3230): WARNING **: Trying to register gtype 'WnckWindowMoveResizeMask' as enum when in fact it is of type 'GFlags' Traceback (most recent call last): File "/usr/bin/gwibber", line 47, in <module> from gwibber.microblog.util import log File "/usr/lib/python2.6/site-packages/gwibber/microblog/util/__init__.py", line 3, in <module> import log File "/usr/lib/python2.6/site-packages/gwibber/microblog/util/log.py", line 9, in <module> mkdir(cache_dir) OSError: [Errno 2] No such file or directory: '/home/test/.cache/gwibber'
After a good night's sleep, I logged back into my test user, and manually created the ~/.cache directory (should I file a bug for that issue? - not sure what uses it other than desktop-couch and gwibber). Gwibber ran successfully, prompting me to create an account, and it fetched my twitter stream. So there must be something lurking in my old home directory.
Well, any application that depends on ~/.cache being there, should create it if it doesn't exist, but I'm not sure if gwibber is to blame, or if it is really desktopcloud. I'll have to look into that.
Nm, i see it. Gwibber is to blame here. cache_dir = realpath(join(xdg.BaseDirectory.xdg_cache_home, "gwibber")) if not isdir(cache_dir): mkdir(cache_dir) The problem here is that it is trying to do the equivalent of: # mkdir ~/.cache/gwibber When ~/.cache/ doesn't exist. You'd want to run mkdir -p in that instance, which is os.makedirs() in python. New builds coming soon.
That's one issue down. Meanwhile, trying to see if I can fix gwibber in my old home directory, I moved my whole ~/.config directory to ~/.config-bak, and logged out and back in. That's in addition to previously removing ~/.cache/gwibber, ~/.cache/desktop-couch, ~/.dbus, ~/.local/share/desktop-couch, ~/.gconf/apps/gwibber. After logging back in, I ran gwibber, it gwibber-accounts, and after I added twitter and identi.ca accounts, it started successfully.
Package: gwibber-1:2.30.0.1-3.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Trying to start Gwibber. Comment ----- Gwibber crashed while trying to start it up.
Package: gwibber-1:2.29.92.1-1.fc12 Architecture: x86_64 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1. Start gwibber 2. I'm not sure, but it seems to crash after a hibernate/resume cycle 3. Close gwibber 4. Try to start gwibber again 5. Gwibber crashes
Package: gwibber-1:2.30.0.1-6.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. selected refresh in File 2. 3.
Package: gwibber-1:2.30.0.1-6.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.just start it 2. 3.
Package: gwibber-1:2.30.0.1-6.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. crashes at start up 2. 3.
Package: gwibber-1:2.30.0.1-6.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Added Twitter account and Facebook account 2. Clicked close
Package: gwibber-1:2.30.0.1-6.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Started Gwibber, window did not appear, program crashed
Package: gwibber-1:2.30.0.1-6.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) Comment ----- Unknown what caused it
Package: gwibber-1:2.30.0.1-6.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Attempt to start Gwibber. Comment ----- Gwibber had been running correctly. I suspended my laptop. On resume from suspend, Gwibber would no longer refresh. I shut it down and attempted to restart it. It now crashes on startup.
Package: gwibber-1:2.30.0.1-6.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Applications -> Internet -> Gwibber, or run 'gwibber' from the command line (in other words, start gwibber) 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
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
Package: gwibber-1:2.30.0.1-6.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) Comment ----- pls look fw to my first report to "gwibber-service" it the same, after update and first run......
Package: gwibber-1:2.31.4-1.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. updated to 2.31.4-1 via updates-testing 2. tried to refresh stream 3. ABRT popup.
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.
I realise this bug has been closed for a while, but I have an error of this DBus message with an update to Gwibber 2.31.93 for OAuth on Twitter. Is it worth posting the details, or log a new bug?