abrt version: 2.0.1 architecture: i686 cmdline: component: wallpapoz executable: /usr/libexec/daemon_wallpapoz kernel: 2.6.38.6-27.fc15.i686 os_release: Fedora release 15 (Lovelock) package: wallpapoz-0.5-6.fc15 reason: wallpapoz_system.py:116:finding_total_workspaces:ValueError: invalid literal for int() with base 10: '' time: Sun Jun 5 15:30:10 2011 uid: 500 username: Berkona backtrace: :wallpapoz_system.py:116:finding_total_workspaces:ValueError: invalid literal for int() with base 10: '' : :Traceback (most recent call last): : File "/usr/libexec/daemon_wallpapoz", line 90, in <module> : wallpapozxml = XMLProcessing() : File "../share/wallpapoz/lib/xml_processing.py", line 49, in __init__ : wallpapoz_system = WallpapozSystem() : File "../share/wallpapoz/lib/wallpapoz_system.py", line 56, in __init__ : self.finding_total_workspaces() : File "../share/wallpapoz/lib/wallpapoz_system.py", line 116, in finding_total_workspaces : self.total_workspaces = int(self.exec_cmd_under_X("xprop -root _NET_NUMBER_OF_DESKTOPS")[36:38]) :ValueError: invalid literal for int() with base 10: '' : :Local variables in innermost frame: :self: <wallpapoz_system.WallpapozSystem instance at 0x8b46a8c>
Well, would you tell me the following? * Please write which desktop environment you are using. * How and when is this bug reproducible? Also if possible please provide the way you can reproduce this bug * Please write the result of the following command: $ xprop -root _NET_NUMBER_OF_DESKTOPS * Please attatch ~/.wallpapoz/wallpapoz.xml * Please attach ~/.xsession-errors when this bug occurs
Package: wallpapoz-0.5-8.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- Did nothing special. Wallpapoz just crashes under Gnome 3.
a) Gnome 3 in Fedora 15 (Lovelock) b) as mentioned above - did nothing special - trying to move active window to a different workspace. Should mention I am also affected by https://bugzilla.redhat.com/show_bug.cgi?id=707652 (similar action : trying to move active window to different workspace - Boom) c) xprop -root _NET_NUMBER_OF_DESKTOPS _NET_NUMBER_OF_DESKTOPS(CARDINAL) = 4 unfortunately this is not at the moment of the crash. Actually the behavior of Gnome 3 is it creates and shuffles workspaces dynamically and if one moves the active window from 1 to 4, there's a fifth workspace briefly created then the whole lot shifts one position up and the fifth workspace is destroyed. d) wallpapoz.xml : <?xml version="1.0" encoding="utf-8"?> <!DOCTYPE Wallpapoz> <wallpapoz interval="5" random="0" style="2" type="workspace"> <workspace name="rename this" no="1"> <file>/usr/share/backgrounds/laughlin/default/laughlin.xml</file> </workspace> <workspace name="rename this" no="2"> <file>/usr/share/backgrounds/laughlin/default/laughlin.xml</file> </workspace> </wallpapoz> e) There's no such file
Well, then - would you tell me if this bug is reproducible? (i.e. how often do you see this issue?)
100% reproducible. Steps to re-create : 1. Make sure you have more than one workspace (put whatever application window in each workspace for example workspaces 1 & 2) 2. Right click on the title bar of the application window of workspace 1, select Move to Another Workspace, then pick Workspace 3. Actualy you can get this, as far as I can tell, whenever you force that dynamic creation, destruction of the last workspace and shifting of the workspaces up for the first time in the session. 3. Boom - get the crash. So I would say you can see the bug once every working session if you reshuffle workspaces. If you don't work with your workspaces like that - nothing happens. Any advice on what I can do to track down what happens at that precise moment? I mean c) above was not done during the crash, but rather after, and the condition to reproduce this is too dynamic to be able to capture the exact status manually. Many thanks in advance!
Do you still see this issue? Unfortunately I don't have any system where gnome-shell works and I always use "classic mode".
(In reply to comment #6) > Do you still see this issue? Unfortunately I don't have any system where > gnome-shell works and I always use "classic mode". I uninstalled wallpapoz and switched to kde. Sorry. Kind Regards, Al
Package: wallpapoz-0.5-8.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- (Re)start the system Login
I forgot: I'm using Gnome3 and the crash happend after restarting the system. I don't have an idea if this is related to automatic login or not.
I've made a bugreport to upstream: https://github.com/vajrasky/wallpapoz/issues/3
Package: wallpapoz-0.5-8.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- Rebooted, logged in, immediately crashed. Using NVIDIA drivers.
Package: wallpapoz-0.5-8.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- I have this set as an autostart on login. Since upgrading to F16 beta, it has started crashing.
Package: wallpapoz-0.5-8.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- This error appeared as soon as I logged in.
Created attachment 527106 [details] patch to verify number of desktops The problem is that daemon_wallpapoz is launching too early in the Gnome Shell startup process and there are no virtual desktops defined yet. If you use twm, you can see what xprop is returning: $ xprop -root _NET_NUMBER_OF_DESKTOPS _NET_NUMBER_OF_DESKTOPS: not found. Python cannot change " not found" into an integer, hence the error message: invalid literal for int() with base 10: '' Attached is a patch that extends the safety checks in /usr/bin/daemon_wallpapoz to make sure that xprop is not returning the above error message. It fixes the problem on my system. Currently the script checks 4 times with a sleep of 3 seconds between checks, so I suppose if a system is slow and it takes longer than 12 seconds to define the virtual desktops, then wallpapoz will never start.
(In reply to comment #14) > Created attachment 527106 [details] > patch to verify number of desktops > Well the problem is that as you see on the comment 5, it seems that this issue occurs not only on startup, but when changing workspace on GNOME shell in some way, and I don't know what xprop is returning at that time.
( And not that currently I am using GNOME 3 with _classic mode_ because GNOME 3 with default mode is still unstable for me )
Created attachment 527267 [details] debug xprop in wallpapoz It's not crashing for me using the method in comment 5. Maybe something has changed in Fedora 16 Beta and Gnome 3.2 that's fixed this? Just in case, though, I added some instrumentation to the wallpapoz daemon to log the output of xprop to /tmp/wallpapoz_debug.out See the attached patch. Example output from the debug log while adding and removing desktops: _NET_NUMBER_OF_DESKTOPS(CARDINAL) = 2 Slice of [36:38] "2 " _NET_NUMBER_OF_DESKTOPS(CARDINAL) = 2 Slice of [36:38] "2 " _NET_NUMBER_OF_DESKTOPS(CARDINAL) = 4 Slice of [36:38] "4 " _NET_NUMBER_OF_DESKTOPS(CARDINAL) = 4 Slice of [36:38] "4 " _NET_NUMBER_OF_DESKTOPS(CARDINAL) = 3 Slice of [36:38] "3 " _NET_NUMBER_OF_DESKTOPS(CARDINAL) = 3 Slice of [36:38] "3 " I had to run the wallpapoz client in order to trigger the daemon to check the number of desktops.
Package: wallpapoz-0.5-8.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- Crashed at boot Also crashed when trying to run manually from activities menu
Package: wallpapoz-0.5-8.fc16 Architecture: i686 OS Release: Fedora release 16 (Verne) Comment ----- I installed a few more packages and tried logging into a Gnome session to see if that would allow me to configure the Language as British English. I got an error message immediately on logging in.
Package: wallpapoz-0.5-8.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- a la mise en route de gnome
Package: wallpapoz-0.5-8.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- à la mise en route
Package: wallpapoz-0.5-8.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- crash occured after boot
Package: wallpapoz-0.5-8.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- I logged into the gnome3 session. I think it has something to do with my background image. I attempted to change it before, and each time I log in it goes back to an older wallpaper that I had.
I no longer receive this after launching wallpapoz manually through applications and deleting all entries and re-adding entries. So something in the upgrade of gnome-shell from 3.0 to 3.2 didn't agree with my saved gnome settings
Package: wallpapoz-0.5-8.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- startup crash
Package: wallpapoz-0.5-8.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- Login to f16
Package: wallpapoz-0.5-8.fc16 Architecture: i686 OS Release: Fedora release 16 (Verne) Comment ----- just login
Package: wallpapoz-0.5-8.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- The crash happened at boot.
Package: wallpapoz-0.5-8.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- Crash happened during boot
Package: wallpapoz-0.5-8.fc16 Architecture: i686 OS Release: Fedora release 16 (Verne) Comment ----- happend on logout + login of same user
Package: wallpapoz-0.5-8.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- startup
Package: wallpapoz-0.5-8.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- Wallpapoz crashes when logging into Gnome.
Package: wallpapoz-0.5-8.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- This occurred on logging in after upgrading to Fedora 16 using the preupgrade
Package: wallpapoz-0.5-8.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- I just installed wallpapoz that is loaded when I log in... I get the error as soon as I log in as a user...
Package: wallpapoz-0.5-8.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- logging in
Package: wallpapoz-0.5-8.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- Au démarrage du system
Package: wallpapoz-0.5-8.fc16 Architecture: i686 OS Release: Fedora release 16 (Verne) Comment ----- just boot up
Package: wallpapoz-0.5-8.fc16 Architecture: i686 OS Release: Fedora release 16 (Verne) Comment ----- just booted
Package: wallpapoz-0.5-8.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- booted up
Package: wallpapoz-0.5-8.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- add the second diplay to gnome desktop. logout. login. then crashed.
Package: wallpapoz-0.5-8.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- No actions were performed.
Package: wallpapoz-0.5-8.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- Just logged in and got error message.
Package: wallpapoz-0.5-8.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- on boot
Package: wallpapoz-0.5-8.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- 1.) fresh install F16 2.) log in 3.) change wallpaper 4.) log out 5.) reboot 6.) log in
Package: wallpapoz-0.5-8.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- Did nothing, just logon on F16/gnome3.
Package: wallpapoz-0.5-8.fc16 Architecture: i686 OS Release: Fedora release 16 (Verne) Comment ----- This error comes immediately after start of Gnome.
Package: wallpapoz-0.5-8.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- -upgrading F15 ->F16 with a working Walpapoz -updating all packages to current version -starting gnome session that normally would use wallpaoz wallpapoz crashes and does not work
Package: wallpapoz-0.5-8.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- Crashed on login to GNOME 3.
Package: wallpapoz-0.5-8.fc16 Architecture: i686 OS Release: Fedora release 16 (Verne) Comment ----- logging in
Package: wallpapoz-0.5-8.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- Crash occured at log in to gnome-shell
Package: wallpapoz-0.5-8.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- I just logged on to this message
on bootup wallpapoz does not work. But starting wallpapoz from "activities" and clicking there "restart daemon" works. After this, the wallpaper changes regularly. I have to do it on every restart.
Package: wallpapoz-0.5-8.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- Crashed on GNOME3 login.
Created attachment 535775 [details] .xsession-errors .xsession-errors Finally reproduced using F-16 x86_64 live DVD
I will now try to fix this...
*** Bug 757204 has been marked as a duplicate of this bug. ***
*** Bug 757069 has been marked as a duplicate of this bug. ***
*** Bug 756919 has been marked as a duplicate of this bug. ***
*** Bug 756553 has been marked as a duplicate of this bug. ***
*** Bug 757329 has been marked as a duplicate of this bug. ***
*** Bug 753978 has been marked as a duplicate of this bug. ***
*** Bug 757215 has been marked as a duplicate of this bug. ***
*** Bug 757380 has been marked as a duplicate of this bug. ***
*** Bug 757381 has been marked as a duplicate of this bug. ***
*** Bug 757409 has been marked as a duplicate of this bug. ***
*** Bug 757432 has been marked as a duplicate of this bug. ***
*** Bug 757433 has been marked as a duplicate of this bug. ***
*** Bug 757434 has been marked as a duplicate of this bug. ***
*** Bug 757379 has been marked as a duplicate of this bug. ***
*** Bug 757494 has been marked as a duplicate of this bug. ***
*** Bug 757521 has been marked as a duplicate of this bug. ***
wallpapoz-0.5-9.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/wallpapoz-0.5-9.fc16
wallpapoz-0.5-9.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/wallpapoz-0.5-9.fc15
Package wallpapoz-0.5-9.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing wallpapoz-0.5-9.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2011-16558/wallpapoz-0.5-9.fc16 then log in and leave karma (feedback).
Tested.. seems to be working fine. Thanks..
*** Bug 758544 has been marked as a duplicate of this bug. ***
*** Bug 758550 has been marked as a duplicate of this bug. ***
(In reply to comment #79) > Tested.. seems to be working fine. Thanks.. I don't get the error message any more, but the daemon doesn't seem to start/work properly.. I'm not sure I took check that in F15..
wallpapoz-0.5-9.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.
wallpapoz-0.5-9.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 766410 has been marked as a duplicate of this bug. ***
*** Bug 766387 has been marked as a duplicate of this bug. ***
*** Bug 759368 has been marked as a duplicate of this bug. ***
*** Bug 766317 has been marked as a duplicate of this bug. ***
*** Bug 766282 has been marked as a duplicate of this bug. ***
*** Bug 766268 has been marked as a duplicate of this bug. ***
*** Bug 766175 has been marked as a duplicate of this bug. ***
*** Bug 766174 has been marked as a duplicate of this bug. ***
*** Bug 765644 has been marked as a duplicate of this bug. ***
*** Bug 765595 has been marked as a duplicate of this bug. ***
*** Bug 761307 has been marked as a duplicate of this bug. ***
*** Bug 761113 has been marked as a duplicate of this bug. ***
*** Bug 761095 has been marked as a duplicate of this bug. ***
*** Bug 760811 has been marked as a duplicate of this bug. ***
*** Bug 760738 has been marked as a duplicate of this bug. ***
*** Bug 760420 has been marked as a duplicate of this bug. ***
*** Bug 760374 has been marked as a duplicate of this bug. ***
*** Bug 759869 has been marked as a duplicate of this bug. ***
*** Bug 759867 has been marked as a duplicate of this bug. ***
*** Bug 759724 has been marked as a duplicate of this bug. ***
After updating new gnome-shell, it does't reproduce any more.
*** Bug 766677 has been marked as a duplicate of this bug. ***