From Bugzilla Helper: User-Agent: Mozilla/5.0 Galeon/1.2.6 (X11; Linux i686; U;) Gecko/20020830 Description of problem: closing a tab-triangle (outline view) in the dialog box, which has been 'left open' from a previous usage, generates a warning/traceback to the console/xterm. Version-Release number of selected component (if applicable): $ rpm -qf `where redhat-config-mouse` redhat-config-mouse-1.0.1-2 How reproducible: Always Steps to Reproduce: 1.run redhat-config-mouse, open the Microsoft tab-triangle, and select the Intellimouse (USB) (for example) 2.close the dialog in the normal way 8:24am {1} pcp02404936pcs:/usr/doc/pam-0.75/ps>$ redhat-config-mouse Shutting down console mouse services: [ OK ] Starting console mouse services: [ OK ] as you can see, things work normally. 3.now, re-run redhat-config-mouse, and click the triangle to CLOSE it, and the error is generated to the console/xterm. Actual Results: Traceback (most recent call last): File "/usr/share/redhat-config-mouse/mouse_gui.py", line 175, in selectMouse type = self.mouseStore.get_value(iter, 2) TypeError: iter must be a GtkTreeIter Expected Results: no error message :) Additional info: problem occurrs with any triangle-tab left open from the previous usage (such as Generic when having just selected a generic 2-button PS/2 mouse) and re-running the configurator and trying to close the Generic tab-triangle.
I believe that this bug has already been fixed in Rawhide. The problem was that the program was allowing you to click the OK button even though no mouse was currently selected in the list because the focus was now on the tree root (the Manufacturer) instead of the branch (the actual mouse name). This caused the program to write out a config file with no mouse. Then, when running the program again, it would crash because the config file was messed up. redhat-config-mouse no longer allows you to click OK if no mouse is selected, so this bug should no longer happen. QA, please verify with the latest tree.
not sure.. The problem occurred before even getting anywhere near the OK button. A mouse was definitely selected in the window, even when re-starting the app .. just when you go and click the down-pointing outline triangle to turn it into a right-pointing one, is when you see the error message to the console (immediately. LONG before clicking the OK button).
Oh, right. The selectMouse() function gets called every time you select a mouse in the list. In the event that you selected the triangle, it would try to get the value of the GtkTreeIter, which of course the triangle doesn't have an iter associated with it. I added a check a number of months ago that avoids this bug by calling a "return" early in the function if the iter does not exist. def selectMouse(self, selection, *args): model, iter = selection.get_selected() if not iter: return type = self.mouseStore.get_value(iter, 2) emu3 = self.mouseStore.get_value(iter, 3) The "if" check above will return from the selectMouse function before it tries to call a get_value for the iter (which does not exist). I'm certain that this bug doesn't occur in versions 1.0.3-4 and later.