Bug 584980 - [abrt] crash in wallpapoz-0.4.1-20.svn92_trunk.fc12: wallpapoz_system.py:116:finding_total_workspaces:ValueError: invalid literal for int() with base 10: ''
Summary: [abrt] crash in wallpapoz-0.4.1-20.svn92_trunk.fc12: wallpapoz_system.py:116:...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: wallpapoz
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Mamoru TASAKA
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:0b177013
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-22 20:13 UTC by sjoerd
Modified: 2011-03-17 21:24 UTC (History)
3 users (show)

Fixed In Version: wallpapoz-0.4.1-24.svn92_trunk.fc12
Clone Of:
Environment:
Last Closed: 2010-06-25 18:18:03 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (802 bytes, text/plain)
2010-04-22 20:13 UTC, sjoerd
no flags Details

Description sjoerd 2010-04-22 20:13:11 UTC
abrt 1.0.8 detected a crash.

architecture: x86_64
cmdline: python /usr/bin/daemon_wallpapoz
component: wallpapoz
executable: /usr/bin/daemon_wallpapoz
kernel: 2.6.32.11-99.fc12.x86_64
package: wallpapoz-0.4.1-20.svn92_trunk.fc12
reason: wallpapoz_system.py:116:finding_total_workspaces:ValueError: invalid literal for int() with base 10: ''
release: Fedora release 12 (Constantine)

backtrace
-----
wallpapoz_system.py:116:finding_total_workspaces:ValueError: invalid literal for int() with base 10: ''

Traceback (most recent call last):
  File "/usr/bin/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 0x2484c20>

Comment 1 sjoerd 2010-04-22 20:13:14 UTC
Created attachment 408437 [details]
File: backtrace

Comment 2 Mamoru TASAKA 2010-04-26 15:24:18 UTC
Would you provide how you can reproduce this issue?

Comment 3 sjoerd 2010-04-27 00:28:57 UTC
I can't sorry.

Its an preupgrade from F11 to F12 and testing all the windowmanagers i have installed and this came from the lxde window manager.

I have tried to reproduce it but can't. Not even when i create a test user and start the windowmanager.

Some excerpt from /var/log/message

Apr 25 22:40:23 asus pulseaudio[19478]: sink-input.c: Failed to create sink input: sink is suspended.
Apr 25 22:44:48 asus dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.196" (
uid=507 pid=22713 comm="lxsession-logout) interface="org.freedesktop.Hal.Device.SystemPowerManagement" member="
ThisMethodMustNotExistInHal" error name="(unset)" requested_reply=0 destination="org.freedesktop.Hal" (uid=0 pi
d=13527 comm="hald))
Apr 25 22:44:52 asus xinetd[14089]: START: ldminfod pid=22732 from=10.10.3.11
Apr 25 22:44:52 asus xinetd[14089]: EXIT: ldminfod status=0 pid=22732 duration=0(sec)
Apr 25 22:44:52 asus xinetd[14089]: START: nbdrootd pid=22736 from=10.10.3.11
Apr 25 22:44:52 asus nbd-server: connect from 10.10.3.11, assigned file is /opt/ltsp/images/i386.img
Apr 25 22:44:52 asus nbd-server: Size of exported file/device is 200929280
Apr 25 22:44:53 asus nbd-server: Disconnect request received.
Apr 25 22:44:53 asus xinetd[14089]: EXIT: nbdrootd status=0 pid=22736 duration=1(sec)
Apr 25 22:45:16 asus gnome-keyring-daemon[23933]: couldn't set environment variable in session: The name org.gn
ome.SessionManager was not provided by any .service files
Apr 25 22:45:16 asus setroubleshoot: SELinux not enabled, setroubleshootd exiting...
Apr 25 22:45:16 asus python: abrt: detected unhandled Python exception in /usr/bin/daemon_wallpapoz
Apr 25 22:45:16 asus abrtd: Directory 'pyhook-1272228316-23937' creation detected


Didn't get any more abrt messages. So maybe its and onetime bug and if so please close this bug.

Comment 4 Mamoru TASAKA 2010-04-27 09:55:17 UTC
Do you remember when this happened? (did this happen when
logging in to LXDE session or logging out from LXDE session
or on some other timing?)

Comment 5 Joe Golden 2010-06-10 10:07:29 UTC
Package: wallpapoz-0.4.1-20.svn92_trunk.fc13
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1. Logged in to LXDE 
2.
3.


Comment
-----
Loging into the LXDE desktop

Comment 6 Mamoru TASAKA 2010-06-14 19:12:16 UTC
Well, I added some workaround (I guess) in -24, which is not
a complete solution, however I think it works...

Comment 7 Fedora Update System 2010-06-14 19:21:12 UTC
wallpapoz-0.4.1-24.svn92_trunk.fc13 has been submitted as an update for Fedora 13.
http://admin.fedoraproject.org/updates/wallpapoz-0.4.1-24.svn92_trunk.fc13

Comment 8 Fedora Update System 2010-06-14 19:21:32 UTC
wallpapoz-0.4.1-24.svn92_trunk.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/wallpapoz-0.4.1-24.svn92_trunk.fc12

Comment 9 Fedora Update System 2010-06-15 16:08:30 UTC
wallpapoz-0.4.1-24.svn92_trunk.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 wallpapoz'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/wallpapoz-0.4.1-24.svn92_trunk.fc12

Comment 10 Fedora Update System 2010-06-25 18:09:23 UTC
wallpapoz-0.4.1-24.svn92_trunk.fc13 has been pushed to the Fedora 13 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 11 Fedora Update System 2010-06-25 18:17:21 UTC
wallpapoz-0.4.1-24.svn92_trunk.fc12 has been pushed to the Fedora 12 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 12 atswartz 2011-03-17 21:24:53 UTC
I am now getting this with wallpapoz-0.5-3.fc15.1.noarch on Rawhide.

wallpapoz_system.py:116:finding_total_workspaces:ValueError: invalid literal for int() with base 10: ''

Traceback (most recent call last):
  File "/usr/bin/wallpapoz", line 1355, in <module>
    wallpapozgui = Wallpapoz()
  File "/usr/bin/wallpapoz", line 76, in __init__
    self.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 0x1a23c20>


Package:    	wallpapoz-0.5-3.fc15.1
Latest Crash:	Wed 09 Mar 2011 09:49:39 PM 
Command:    	python /usr/bin/wallpapoz
Reason:     	wallpapoz_system.py:116:finding_total_workspaces:ValueError: invalid literal for int() with base 10: ''


Note You need to log in before you can comment on or make changes to this bug.