Red Hat Bugzilla – Bug 68557
redhat-mouse-config crashes with internal touchpoint on x20 thinkpad
Last modified: 2008-05-01 11:38:02 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020625
Description of problem:
first noticed when firstboot runs. clicking on the config button for mouse just
died. the i tried runnning it from the command line and python died as detailed
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.execute redhat-config-mouse from either firstboot, or afterwards directly from
the command line.
Actual Results: [root@random root]# redhat-config-mouse
Traceback (most recent call last):
File "/usr/share/redhat-config-mouse/redhat-config-mouse.py", line 13, in ?
File "/usr/share/redhat-config-mouse/mouse_gui.py", line 214, in stand_alone
File "/usr/share/redhat-config-mouse/mouse_gui.py", line 51, in setupScreen
self.probedMouse = self.probeMouse()
File "/usr/share/redhat-config-mouse/mouse_gui.py", line 142, in probeMouse
lines = string.split(str(mouse), '\n')
IndexError: list index out of range
i'm running on an X20 thinkpad, and using the internal touchpoint. the mouse,
btw, works fine. it's just this config app that doesn't work.
*** Bug 68596 has been marked as a duplicate of this bug. ***
*** Bug 69681 has been marked as a duplicate of this bug. ***
Should be fixed with 0.9.9-2.
QA, please verify.
I don't have an x20 at my disposal, so could the reporter grab the latest
redhat-config-mouse out of Rawhide and give this a try and let me know if things
are working now?
unfortunately i've since gone back to redhat 7.3. i did try and install the
requisite rpms (rhpl-0.51-1.i386.rpm redhat-config-mouse-1.0.1-2.noarch.rpm
pyxf86config-0.3.1-2.i386.rpm), and got the following response:
> sudo redhat-config-mouse
Traceback (innermost last):
File "/usr/share/redhat-config-mouse/redhat-config-mouse.py", line 5, in ?
File "/usr/share/redhat-config-mouse/mouse_gui.py", line 30
import rhpl.mouse as mouse
SyntaxError: invalid syntax
i got the same response running as a user, and with sudo.
OK, since I don't have access to this type of machine, just going to have to
resolve it and have you reopen if you find problems.