Bug 3489

Summary: Mouse dont work in KDM screen
Product: Mageia Reporter: Jan Eriksson <jan-olof.eriksson>
Component: RPM PackagesAssignee: John Balcaen <balcaen.john>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Normal CC: balcaen.john
Version: 1Keywords: Triaged
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: kdm-4.6.5 CVE:
Status comment:
Attachments: kdm.log.1
kdm.log.1

Description Jan Eriksson 2011-11-27 07:49:32 CET 
Description of problem: I changed my mouse cursor to away from default. Now when pc starts and kdm screen shows, mouse wont work. I use tabulator to log in, and after that, its starts to work. Seems kdm screen uses that default cursor theme.


Version-Release number of selected component (if applicable):4.6.5
Comment 1 Jan Eriksson 2011-11-27 07:58:11 CET 
And it does this after reboot, it works if i just logout.
Comment 2 Manuel Hiebel 2011-11-27 11:36:09 CET 
Hi, thanks for reporting this bug.

Can you attach the files /var/log/kdm.log and  /var/log/kdm.log.1 ?

Assigned to the package maintainer.

Keywords: (none) => Triaged
Assignee: bugsquad => balcaen.john
Source RPM: (none) => kdm-4.6.5

Comment 3 Jan Eriksson 2011-11-27 11:53:44 CET 
Created attachment 1134 [details]
kdm.log.1

kdm.log is empty
Comment 4 Jan Eriksson 2011-11-27 11:54:53 CET 
Created attachment 1135 [details]
kdm.log.1

Attachment 1134 is obsolete: 0 => 1

Comment 5 John Balcaen 2011-11-28 02:01:28 CET 
What do you mean by « i change my mouse cursor to away from default » ?

CC: (none) => balcaen.john

Comment 6 Jan Eriksson 2011-11-28 04:47:02 CET 
Changed another cursor theme.
Comment 7 John Balcaen 2011-11-28 06:03:06 CET 
Hum, i failed to understand how the change of the mouse theme prevent the mouse to work in kdm.
The problem is probably something else where mouse is not recognized.
Just in case which theme are you using ?
Switching back to the default theme fix your problem or not ?
Comment 8 Jan Eriksson 2011-12-08 19:33:25 CET 
Mouse works now. So i guess this is fixed. :)

Status: NEW => RESOLVED
Resolution: (none) => FIXED

Comment 9 John Balcaen 2011-12-08 21:28:09 CET 
Well i did not push *any* fix for this specific issue so i don't know if it's really fixed...