http://bugzilla.novell.com/show_bug.cgi?id=524780 Summary: Graphical YaST -> Mouse Model should set MOUSEDEVICE in /etc/sysconfig/mouse Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: PC OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: ashaduri@gmail.com QAContact: jsrain@novell.com Found By: --- User-Agent: Opera/9.64 (X11; Linux x86_64; U; en) Presto/2.1.1 The problem is that graphical and text-mode YaSTs behave differently in regards of mouse setup. When setting mouse model from graphical YaST, it doesn't set MOUSEDEVICE in /etc/sysconfig/mouse, forcing users to use the text mode version of YaST to have gpm (which won't work if MOUSEDEVICE is not set). This is not intuitive (I discovered it only by accident) and users should not have to run two versions of the same tool, which in most cases provide the same functionality. Also, the mouse models in text-mode version are completely different, which adds to the confusion. For example, the only ps/2 mouse in text mode is "IntelliMouse Explorer". I understand that one is a X mouse driver list and another is probably a "gpm" list, but I don't see a problem in unifying them and setting a model for both from a single location. P.S. I'm not sure but this may also be affecting MOUSETYPE. Reproducible: Always Steps to Reproduce: 1. Run graphical YaST -> Hardware -> Mouse Model, select the mouse model you have. 2. Check /etc/sysconfig/mouse, see that MOUSEDEVICE is not set. 3. Run text-mode YaST -> Hardware -> Mouse Model, select the mouse model you have (if you can find it, since it's a different list). 4. Verify that MOUSEDEVICE is now set. openSUSE 11.1 x86_64 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.