Bug 114919

Summary: /etc/sysconfig/mouse isn't set up
Product: [openSUSE] SUSE LINUX 10.0 Reporter: Volker Kuhlmann <bugz57>
Component: YaST2Assignee: Marcus Schaefer <ms>
Status: RESOLVED WONTFIX QA Contact: Klaus Kämpf <kkaempf>
Severity: Normal    
Priority: P5 - None CC: kontakt, pmladek
Version: Beta 4   
Target Milestone: ---   
Hardware: PC   
OS: All   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Volker Kuhlmann 2005-09-02 08:59:44 UTC 
Installation of default system doesn't configure the console mouse 
in /etc/sysconfig/mouse. In previous SuSE versions I never needed to change 
anything in that file, so some sensible values should work. 
 
# rcgpm start 
Neither the variables MOUSEDEVICE and MOUSETYPE nor the variable GPM_PARAM 
is set in /etc/sysconfig/mouse
Comment 1 Petr Mladek 2005-09-05 12:44:27 UTC 
The configuration should be defined by YaST within installation.

Maybe, it is realted to the bug #100665. It should be fixed but...
Comment 2 Petr Mladek 2005-09-05 12:46:49 UTC 
I can reproduce the bug on beta4.
Comment 3 Petr Mladek 2005-09-05 12:50:33 UTC 
Ah, I see that it is assigned back to the screening team => I'll reassign it to
the maintainer of the related YaST module.
Comment 4 Marcus Schaefer 2005-09-05 13:01:06 UTC 
That's a consequence of the decision of bug #106631 
in a graphical installation process the mouse module for the console 
is no longer called. Therefore the user has to call yast2 mouse one 
time manually to configure the console mouse (GPM) 
 
In a textbased installation the console mouse is configured 
automatically as before 
 
You can't please everybody and the code will not be changed now 
any more
Comment 5 Michael Gross 2005-10-14 18:57:21 UTC 
*** Bug 118181 has been marked as a duplicate of this bug. ***
Comment 6 Michal Marek 2005-11-03 08:24:52 UTC 
*** Bug 131525 has been marked as a duplicate of this bug. ***
Comment 7 Michal Marek 2006-01-09 12:03:30 UTC 
*** Bug 141345 has been marked as a duplicate of this bug. ***