Bug 597687

Summary: [abrt] crash in wallpapoz-0.4.1-20.svn92_trunk.fc12: wallpapoz_system.py:130:check_beryl:ValueError: invalid literal for int() with base 10: ''
Product: [Fedora] Fedora Reporter: sjoerd <bugzilla001>
Component: wallpapozAssignee: Mamoru TASAKA <mtasaka>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: mtasaka, vision1983
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:93ef708b
Fixed In Version: wallpapoz-0.4.1-24.svn92_trunk.fc12 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-06-25 18:18:11 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description sjoerd 2010-05-30 04:28:43 UTC
abrt 1.0.9 detected a crash.

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

backtrace
-----
wallpapoz_system.py:130:check_beryl: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 49, in __init__
    self.check_beryl()
  File "../share/wallpapoz/lib/wallpapoz_system.py", line 130, in check_beryl
    self.geometry_width = int(geometry[0])
ValueError: invalid literal for int() with base 10: ''

Local variables in innermost frame:
geometry: ['']
self: <wallpapoz_system.WallpapozSystem instance at 0x242bcb0>
raw_geometry: ''

Comment 1 sjoerd 2010-05-30 04:28:45 UTC
Created attachment 417983 [details]
File: backtrace

Comment 2 Mamoru TASAKA 2010-05-30 05:08:57 UTC
When did this crash happen?
Also would you provide how you can reproduce this issue?

Comment 3 sjoerd 2010-05-30 05:34:56 UTC
I can't. Sorry.

It's something I'm starting up whatever program and normally never happens but sometimes it crashed unexpectedly.

I'll keep an eye on this to solve this bug.

Until now I don't know.

Comment 4 sjoerd 2010-05-30 05:43:52 UTC
Also reported an older bug at:

https://bugzilla.redhat.com/show_bug.cgi?id=573642

Comment 5 Mamoru TASAKA 2010-06-14 19:13:19 UTC
Well, -24 may shut down this issue, or may not...

Comment 6 Fedora Update System 2010-06-14 19:21:16 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 7 Fedora Update System 2010-06-14 19:21:36 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 8 Fedora Update System 2010-06-15 16:08:35 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 9 Fedora Update System 2010-06-25 18:09:29 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 10 Fedora Update System 2010-06-25 18:17:26 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.