https://bugzilla.novell.com/show_bug.cgi?id=262317 ------- Comment #2 from tm.mst@gmx-topmail.de 2007-04-07 14:51 MST ------- Created an attachment (id=129760) --> (https://bugzilla.novell.com/attachment.cgi?id=129760&action=view) hwinfo --mouse -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=262317 ------- Comment #4 from tm.mst@gmx-topmail.de 2007-04-07 14:54 MST ------- *** Bug 262318 has been marked as a duplicate of this bug. *** -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=262317 ms@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|ms@novell.com |sndirsch@novell.com ------- Comment #6 from ms@novell.com 2007-04-17 02:12 MST ------- The evdev driver is used for your mouse. I have exactly the same mouse with the same configuration running on my 10.2 machine Section "InputDevice" Driver "evdev" Identifier "Mouse[1]" Option "Buttons" "20" Option "InputFashion" "Mouse" Option "Name" "Logitech USB Receiver" Option "Protocol" "event" Option "SendCoreEvents" "on" Option "Vendor" "Sysp" Option "ZAxisMapping" "4 5" EndSection Stefan the log said: (II) evdev brain: Rescanning devices (1). (EE) PreInit returned NULL for "Mouse[1]" (WW) <default pointer>: No Device specified, looking for one... (II) <default pointer>: Setting Device option to "/dev/input/mice" (--) <default pointer>: Device: "/dev/input/mice" (==) <default pointer>: Protocol: "Auto" (**) Option "AlwaysCore" (**) <default pointer>: always reports core events (**) Option "Device" "/dev/input/mice" (==) <default pointer>: Emulate3Buttons, Emulate3Timeout: 50 (**) <default pointer>: ZAxisMapping: buttons 4 and 5 (**) <default pointer>: Buttons: 9 (WW) No core pointer registered Thanks -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=262317 ------- Comment #11 from tm.mst@gmx-topmail.de 2007-04-23 08:22 MST ------- Do you need information from me or from Stefan? evdev fails gracefully with kernel 2.6.21-rc5. But I can remember that an self-written evdev configuration like the above was working in 10.2. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=262317 sndirsch@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|ms@novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=262317#c16 --- Comment #16 from Thomas Meindl 2007-06-18 02:00:00 MST --- Anything new about this topic? Using the evdev driver still fails in openSUSE 10.3 Alpha5 with 'No core pointer'. Will attach actual /var/log/Xorg.99.log -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317#c19 Dean Hilkewich changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |deanjo@sasktel.net --- Comment #19 from Dean Hilkewich 2007-06-28 06:27:13 MST --- *** Bug 288106 has been marked as a duplicate of this bug. *** https://bugzilla.novell.com/show_bug.cgi?id=288106 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317#c21 --- Comment #21 from Dean Hilkewich 2007-06-28 06:31:14 MST --- Same bug bit me -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317#c23 --- Comment #23 from Thomas Meindl 2007-07-31 13:36:45 MST ---

solution change out evdev for mouse and comment out protocol event. Not really a solution, 'cause it will render special buttons (e.g. Tilt-Wheel) useless - and evdev was already working with G5.

-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317 Dean Hilkewich changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P1 - Urgent Version|Alpha 2 |Alpha 6 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317#c26 --- Comment #26 from Stephen Shaw 2007-08-03 01:00:48 MST --- I recommend moving this to critical or even a blocker, as anyone with a logitech mouse that uses this driver will not be able to load xorg unless they use the work around -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317 Dean Hilkewich changed: What |Removed |Added ---------------------------------------------------------------------------- Version|Alpha 6 |Alpha 7 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- CC|sndirsch@novell.com | Component|SaX2 |X.Org QAContact|qa@suse.de |xorg-maintainer-bugs@forge.provo.novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317#c31 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mhopf@novell.com --- Comment #31 from Stefan Dirsch 2007-08-13 09:49:20 MST --- Find also some details in Bug #298398 (duplicate). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317#c34 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|sndirsch@novell.com |mhopf@novell.com Status|ASSIGNED |NEW --- Comment #34 from Stefan Dirsch 2007-08-14 10:20:39 MST --- Reassigning to Matthias again. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317#c37 Matthias Hopf changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Blocker |Critical --- Comment #37 from Matthias Hopf 2007-08-16 11:36:20 MST --- Lowering severity. This is not blocker, but annoying nevertheless. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317#c39 --- Comment #39 from Dean Hilkewich 2007-08-16 12:07:51 MST --- I'm not sure how this could NOT be marked as a blocker. These mice are a common piece of hardware (probably one of the best selling mice) and as such a issue that blocks people from using them IMHO is a show stopper as it effects basic I/O functionality. This issue is not a leftover from a previous configuration as it's easily reproduced on a fresh clean install. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317 Dean Hilkewich changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Critical |Blocker -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317 Matthias Hopf changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #129760|application/octet-stream |text/plain mime type| | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317#c43 --- Comment #43 from Matthias Hopf 2007-08-17 07:54:44 MST --- Created an attachment (id=158213) --> (https://bugzilla.novell.com/attachment.cgi?id=158213) Fix for sax2 evdev profiles This patch should fix the issue. You can apply it in an already installed system (patch -p0 when residing in / as root), and do a "sax2 -r" in order to test. The mouse configuration still states (wrongly) Option "Buttons" "10", but the evdev driver apparently doesn't care about that one either. Even the standard mouse driver is now capable of announcing the correct number of buttons... Can you two please test this patch? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317#c45 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sndirsch@novell.com --- Comment #45 from Stefan Dirsch 2007-08-17 08:21:48 MST ---

- Xserver shouldn't bail out if Corepointer doesn't work, but continue (AllowOpenMouseFail) - Xserver shouldn't crash when attaching additional mice IMHO we should open a seperate bugreport for these issues. Otherwise this bugreport won't be closed soon.

-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317#c47 Thomas Meindl changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|tm.mst@gmx-topmail.de | --- Comment #47 from Thomas Meindl 2007-08-21 04:48:07 MST --- Applied the patch to the OpenSuse103beta1 and it works for me: init 3 sax2 -m 0=nidia // still needed to define the nvidia driver //(don't know whether this is worth a bugreport) SaX2 starts up correctly and shows me the mouse with the name 0x046d (I suppose this is taken from the "Vendor" field of xorg.conf). All Buttons work, number 6 and 7 (i.e Tilt-Wheel) are shown as a wheel movement in the picture of the mouse, which is a mere cosmetically problem. Sax2 works also flawlessly in init 5 with an X-server running. It's up an running again, thank you all a lot! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317#c49 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|mhopf@novell.com |ms@novell.com Status|ASSIGNED |NEW Component|X.Org |SaX2 QAContact|xorg-maintainer-bugs@forge.provo.novell.com |qa@suse.de --- Comment #49 from Stefan Dirsch 2007-08-21 05:52:27 MST --- Reassigning to Marcus. Matthias, please don't forget about comments #44/45. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317#c51 --- Comment #51 from Matthias Hopf 2007-08-21 06:06:18 MST --- (In reply to comment #45 from Stefan Dirsch)

IMHO we should open a seperate bugreport for these issues. Otherwise this bugreport won't be closed soon.

Done. Bug #302116 Marcus, close this one when the patch is applied. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317#c53 darren winter changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Critical |Blocker --- Comment #53 from darren winter 2007-08-24 07:10:04 MST --- what the hell??? this bug still exists in beta 2! is this bug going to persist through the 10.3 final release? i am officially requesting that this is changed back to BLOCKER until it is FIXED. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317#c55 --- Comment #55 from Dean Hilkewich 2007-08-29 09:51:10 MST --- sax2 fails due logitech usb gaming mouse <---that's the issue, how can something be marked as resolved when it still doesn't work? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317#c57 --- Comment #57 from Matthias Hopf 2007-09-04 07:19:50 MST --- I think the fix got in by Marcus just after code freeze for beta 2. But you can try to install all sax2*.rpm from factory to test that. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317#c59 --- Comment #59 from Thomas Meindl 2007-09-06 12:33:40 MST --- You won't like this to hear, but either the fix didn't get in or it was changed in some sort of way, because it doesn't work in beta3 - unless I apply the patch. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317#c61 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | --- Comment #61 from Stefan Dirsch 2007-09-06 13:26:16 MST --- .. but the patch (see comment #43) has not been applied. :-( Need to reopen this one. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317#c63 --- Comment #63 from Dean Hilkewich 2007-09-06 15:41:47 MST --- Can we please get a new sax2-ident package up on the updates until this issue is resolved? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317#c65 --- Comment #65 from Dean Hilkewich 2007-09-06 16:53:13 MST --- Well, if I hook up another mouse then Sax correctly gives me the 1600x1200 option and does not limit me to 1280x1024. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317#c67 --- Comment #67 from Dean Hilkewich 2007-09-06 16:56:56 MST --- One last thing, this issue replicable with both the nv and nvidia driver. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317#c69 --- Comment #69 from Dean Hilkewich 2007-09-06 17:43:11 MST --- Very well I will get you xorg.confs of an install with the MX510 and the G5 mouse. Just give me a few hours -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317#c71 Marcus Schaefer changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |DUPLICATE --- Comment #71 from Marcus Schaefer 2007-09-07 02:01:17 MST --- - the manual selection of the mouse data in the CDB has been fixed It was an issue related to this bug but not the main problem - but the X driver problem seems to be still present. Comment #51 points to the real problem *** This bug has been marked as a duplicate of bug 302116 *** https://bugzilla.novell.com/show_bug.cgi?id=302116 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317#c73 Stephan Kulow changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |coolo@novell.com --- Comment #73 from Stephan Kulow 2007-09-07 02:51:40 MST --- How likely is that #302116 is fixed the days after Matthias returns? Because then I would prefer an online update for the real issue instead of a work around now. After all the GM is 27th - so if we have a fix on let's say 29th it would be ok, no? I admit I miss a good picture of the remaining impact. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317#c75 --- Comment #75 from Stephan Kulow 2007-09-07 03:11:56 MST --- I agree. We should track the real issue only - meaning DUPLICATE again and severity up 302116 if it's really that much of a problem. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317#c77 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |deanjo@sasktel.net --- Comment #77 from Stefan Dirsch 2007-09-07 04:39:14 MST --- (In reply to comment #69 from Dean Hilkewich)

Very well I will get you xorg.confs of an install with the MX510 and the G5 mouse. Just give me a few hours.

Dean, please provide them ASAP. (In reply to comment #62 from Dean Hilkewich)

Ya the bug is still there but even after applying the patch sax still refuses to launch unless a sax -r is done. Unfortunately this results in a xorg.conf that limits my setting of resolution to 1280x1024 in sax even though I was previously able to set it to my preferred 1600x1200 before.

This one I need as well. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317#c79 --- Comment #79 from Stefan Dirsch 2007-09-08 07:41:16 MST --- Can't find the other requested xorg.conf files. :-( -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317#c81 --- Comment #81 from Stefan Dirsch 2007-09-08 08:13:54 MST --- It would already help to see the xorg.conf files I've been offered before. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317#c83 --- Comment #83 from darren winter 2007-09-10 07:34:52 MST --- so, how's this one looking for rc1? :p -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317#c85 --- Comment #85 from Julian Medina 2007-09-10 10:14:49 MST --- They should defiantly fix this by RC1. It is a pretty important bug. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317#c87 --- Comment #87 from darren winter 2007-09-10 20:10:15 MST --- how about fixing it instead of claiming that it's fixed - only to find out that it's not - and then asking for more logs? i know i've provided my share of bugs. this has been on the books for months now, and we've all said this would end up as a huge problem for everyone. now here we are on the verge of final release and we are being asked for more logs. i've been reporting (and supplying logs) since alpha 1, both here and on irc. none of this should be a shock. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317#c89 --- Comment #89 from Julian Medina 2007-09-10 22:31:10 MST --- I would defiantly recommend you fix this by RC1. The whole world has Logitech Mice. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317#c91 Stephan Kulow changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Blocker |Critical --- Comment #91 from Stephan Kulow 2007-09-11 03:32:56 MST --- ok, this is not blocking the release. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317#c92 --- Comment #92 from Stefan Dirsch 2007-09-11 05:51:04 MST --- I'm currently trying hard to reproduce this issue. The mouse I'm using: ################# # # Logitech # MediaPlay # Cordless Mouse # ################## # hwinfo --mouse 47: USB 00.0: 10503 USB Mouse [Created at usb.122] UDI: /org/freedesktop/Hal/devices/usb_device_46d_c50e_noserial_if0 Unique ID: UfPf.r+G0OqTk0u7 Parent ID: 2XnU.+3dax8OvtgB SysFS ID: /devices/pci0000:00/0000:00:1d.0/usb5/5-1/5-1:1.0 SysFS BusID: 5-1:1.0 Hardware Class: mouse Model: "Logitech USB Receiver" Hotplug: USB Vendor: usb 0x046d "Logitech Inc." Device: usb 0xc50e "USB Receiver" Revision: "25.00" Compatible to: int 0x0210 0x0028 Driver: "usbhid" Driver Modules: "usbhid" Device File: /dev/input/mice (/dev/input/mouse0) Device Files: /dev/input/mice, /dev/input/mouse0, /dev/input/event2, /dev/input/by-id/usb-Logitech_USB_Receiver-event-mouse, /dev/input/by-path/pci-0000:00:1d.0-usb-0:1:1.0-event-mouse, /dev/input/by-id/usb-Logitech_USB_Receiver-mouse, /dev/input/by-path/pci-0000:00:1d.0-usb-0:1:1.0-mouse Device Number: char 13:63 (char 13:32) Speed: 1.5 Mbps Module Alias: "usb:v046DpC50Ed2500dc00dsc00dp00ic03isc01ip02" Driver Info #0: Buttons: 8 Wheels: 2 XFree86 Protocol: explorerps/2 GPM Protocol: exps2 Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #43 (Hub) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317#c94 --- Comment #94 from Stefan Dirsch 2007-09-11 05:53:51 MST --- Created an attachment (id=163192) --> (https://bugzilla.novell.com/attachment.cgi?id=163192) xorg.conf created with "sax2 -r" (works) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317#c96 --- Comment #96 from Thomas Meindl 2007-09-11 06:27:59 MST --- I just tried the input-section from your Xorg.conf form comment 93 and it kills my XServer so hard, that if I switch to console 7 via Alt-Ctrl-F7 it shows a black screen with a blinking cursor - then switching back to any other console doesn't work any more (NVIDIA and nv driver). I believe that you've got a newer revision of the Logitech G5 mouse (according c. 92). Newer G5s have an extra button on the side (so there are two side-buttons now). With the patch I can use sax2 and the Xserver without any problem (whereas I cannot say something about resolutions above 1280x1024 because this is the max. resolution of a single screen of my Twinview setup). My 2 years old one-side-button-G5: 42: USB 00.0: 10503 USB Mouse [Created at usb.122] UDI: /org/freedesktop/Hal/devices/usb_device_46d_c041_noserial_if0 Unique ID: 7bWa.xCkw_U0ZPy7 Parent ID: pBe4.eStfeOR6kQD SysFS ID: /devices/pci0000:00/0000:00:0b.0/usb2/2-3/2-3:1.0 SysFS BusID: 2-3:1.0 Hardware Class: mouse Model: "Logitech USB Gaming Mouse" Hotplug: USB Vendor: usb 0x046d "Logitech Inc." Device: usb 0xc041 "USB Gaming Mouse" Revision: "46.02" Compatible to: int 0x0210 0x0028 Driver: "usbhid" Driver Modules: "usbhid" Device File: /dev/input/mice (/dev/input/mouse0) Device Files: /dev/input/mice, /dev/input/mouse0, /dev/input/event1, /dev/inpu t/by-id/usb-Logitech_USB_Gaming_Mouse-event-mouse, /dev/input/by-path/pci-0000:0 0:0b.0-usb-0:3:1.0-event-mouse, /dev/input/by-id/usb-Logitech_USB_Gaming_Mouse-m ouse, /dev/input/by-path/pci-0000:00:0b.0-usb-0:3:1.0-mouse Device Number: char 13:63 (char 13:32) Speed: 12 Mbps Module Alias: "usb:v046DpC041d4602dc00dsc00dp00ic03isc01ip02" Driver Info #0: Buttons: 8 Wheels: 2 XFree86 Protocol: explorerps/2 GPM Protocol: exps2 Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #41 (Hub) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317#c98 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #158213|0 |1 is obsolete| | --- Comment #98 from Stefan Dirsch 2007-09-11 06:40:05 MST --- Created an attachment (id=163200) --> (https://bugzilla.novell.com/attachment.cgi?id=163200) sax2-logitech-profile.diff update for sax2 evdev profile patch -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317#c100 --- Comment #100 from Stefan Dirsch 2007-09-11 07:23:04 MST --- Thomas, Julian, Darren, Stephen, Dean. Could we agree, that anybody who is still interested into getting this fixed, to give the updated patch of comment #98 a try and provide feedback ASAP? The patch can be applied as root by running cd /; patch -p0 < Afterwards run "sax2 -r". Attach /var/log/SaX.log. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317#c103 --- Comment #103 from Thomas Meindl 2007-09-11 08:07:48 MST --- Created an attachment (id=163231) --> (https://bugzilla.novell.com/attachment.cgi?id=163231) SaX.log file I applied the patch to the original profile files. Again sax2 (or xorg) couldn't start up. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317#c105 --- Comment #105 from Stefan Dirsch 2007-09-11 08:41:31 MST --- (In reply to comment #103 from Thomas Meindl)

Created an attachment (id=163231) --> (https://bugzilla.novell.com/attachment.cgi?id=163231) [details] SaX.log file

I applied the patch to the original profile files. Again sax2 (or xorg) couldn't start up.

Obviously the evdev driver does not work together with this mouse (Gaming: 0x046d:0xc041). :-( (II) evdev brain: Rescanning devices (1). (EE) PreInit returned NULL for "Mouse[1]" ==> it doesn't make sense to enable evdev for this mouse. It looks different for me (MediaPlay: 0x046d:0xc50e): (II) evdev brain: Rescanning devices (1). (**) Option "SendCoreEvents" "on" (**) Mouse[1]-usb-0000:00:1d.0-1/input0: always reports core events (**) Option "CorePointer" (**) Mouse[1]-usb-0000:00:1d.0-1/input0: Core Pointer (II) Mouse[1]-usb-0000:00:1d.0-1/input0: Found 4 relative axes. (II) Mouse[1]-usb-0000:00:1d.0-1/input0: Configuring as pointer. (**) Mouse[1]-usb-0000:00:1d.0-1/input0: HWHEELRelativeAxisButtons: 6 7. (**) Mouse[1]-usb-0000:00:1d.0-1/input0: WHEELRelativeAxisButtons: 4 5. (II) Mouse[1]-usb-0000:00:1d.0-1/input0: Found 16 mouse buttons (**) Mouse[1]-usb-0000:00:1d.0-1/input0: Configuring 4 relative axes. (II) Mouse[1]-usb-0000:00:1d.0-1/input0: Configured 20 mouse buttons -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317#c107 --- Comment #107 from Thomas Meindl 2007-09-11 09:20:14 MST --- In reply of comment 105: But with patch number 1 I get evdev working (and working stable): (II) evdev brain: Rescanning devices (1). (**) Option "SendCoreEvents" "on" (**) Mouse[1]-usb-0000:00:0b.0-3/input0: always reports core events (**) Option "CorePointer" (**) Mouse[1]-usb-0000:00:0b.0-3/input0: Core Pointer (II) Mouse[1]-usb-0000:00:0b.0-3/input0: Found 4 relative axes. (II) Mouse[1]-usb-0000:00:0b.0-3/input0: Configuring as pointer. (**) Mouse[1]-usb-0000:00:0b.0-3/input0: HWHEELRelativeAxisButtons: 6 7. (**) Mouse[1]-usb-0000:00:0b.0-3/input0: WHEELRelativeAxisButtons: 4 5. (II) Mouse[1]-usb-0000:00:0b.0-3/input0: Found 16 mouse buttons (**) Mouse[1]-usb-0000:00:0b.0-3/input0: Configuring 4 relative axes. (II) Mouse[1]-usb-0000:00:0b.0-3/input0: Configured 20 mouse buttons (WW) <default pointer>: No Device specified, looking for one... (II) <default pointer>: Setting Device option to "/dev/input/mice" (--) <default pointer>: Device: "/dev/input/mice" (==) <default pointer>: Protocol: "Auto" (**) Option "AlwaysCore" (**) <default pointer>: always reports core events (**) Option "Device" "/dev/input/mice" (==) <default pointer>: Emulate3Buttons, Emulate3Timeout: 50 (**) <default pointer>: ZAxisMapping: buttons 4 and 5 (**) <default pointer>: Buttons: 9 (**) <default pointer>: Sensitivity: 1 (II) XINPUT: Adding extended input device "<default pointer>" (type: MOUSE) (II) XINPUT: Adding extended input device "Mouse[1]-usb-0000:00:0b.0-3/input0" (type: MOUSE) (II) XINPUT: Adding extended input device "evdev brain" (type: evdev brain) (II) XINPUT: Adding extended input device "Keyboard[0]" (type: KEYBOARD) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #158213|1 |0 is obsolete| | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317#c109 --- Comment #109 from Stefan Dirsch 2007-09-11 09:53:18 MST --- But without any patch evdev does not work. Is this correct, Thomas? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317#c111 --- Comment #111 from Stefan Dirsch 2007-09-11 10:51:59 MST --- Thanks. So Julian, Darren, Stephen, Dean, please use the patch of comment #43 and not my broken one of comment #98. Besides from that the instructions remain the same as in comment #100. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317#c113 --- Comment #113 from darren winter 2007-09-11 20:00:12 MST --- Created an attachment (id=163398) --> (https://bugzilla.novell.com/attachment.cgi?id=163398) sax logs & xorg confs

#48 - patch -p0 when residing in / as root attachment: bug-262317_sax2-logitech-profile.diff

meh-rd42:/ # patch -p0 < bug-262317_sax2-logitech-profile.diff patching file /usr/share/sax/profile/logitech-Gaming patching file /usr/share/sax/profile/logitech-MediaPlay patching file /usr/share/sax/profile/logitech-mxlaser

#100 Afterwards run "sax2 -r". Attach /var/log/SaX.log.

meh-rd42:/ # sax2 -r SaX: initializing please wait... SaX: your current configuration will not be read in SaX: access to your display has been granted SPP: prepare device [0] profile: NoModelines SPP: prepare device [1] profile: logitech-Gaming SPP: prepare device [0] profile: microsoft-natural SPP: including prepared profile(s)... SaX: startup SaX: X-Server: :0.0 -> grant SaX: using cache data... popups... title: message invalid color/resolution combination. the selected resolution and/or color settings are not supported by the graphics cards framebuffer. title: message 3d accelleration not supported sax2 cannot offer activation of the 3d subsystem because your graphics card/driver doesn't support 3d. results... when sax2 came up, i clicked test - no test occurred, sax2 window disappeared -> sax1.log i ran it again and clicked save this time, the window went away -> sax2.log in any case, when i restarted x, my monitor started flipping diagonally at about 10,000 mph. i had to kill it and login again to get it to stop. i rebooted, same thing. i had to restart x and login to get it to stop. additionally, for some stupid reason. /boot/grub/menu.lst on my main title vga-0x31a was changed by sax2 to vga=0x0. so when i was booting up my text was like 10 inches tall. does the mouse work? it always has AFTER i have gotten back in to X and/OR been able to run sax2 -r. so, this time, with the patch the mouse worked... but it also worked when i ran sax2 -r back in beta 1 and beta 2 with the same exact results as i had tonight - but in both of those cases i never patched anything. and if you look at these new logs, i'm not sure the end of the logs look like any kind of real success, maybe i'm wrong though. xorg.sax was the config AFTER i ran sax2 -r - like i said, it doesn't appear to be working, so maybe this file is unchanged by it... and when compared to my real xorg.conf = identical. anyway, these are my results with the patch on suse 10.3 beta 3 64-bit and the logitech g5 version 1 (one side button). hope this helps! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317#c115 --- Comment #115 from darren winter 2007-09-11 20:32:10 MST --- confirming... i'm seeing the same thing. sax2 does not test or close properly, it makes no changes to the xorg.conf file whatsoever - but it also modified by /boot/grub/menu.lst file from vga=0x31a to vga=0x0 - so when i rebooted my text was HUGE. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317#c117 --- Comment #117 from Stefan Dirsch 2007-09-12 00:22:16 MST --- Dean, you own the same mouse as Thomas and said that adding the patch fixes the configuration. The configuration files you sent confirm this. The limitation in the resolution looks completely unrelated to me. So I don't want to handle it in this bugreport. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317#c119 --- Comment #119 from Stefan Dirsch 2007-09-12 00:38:16 MST --- Now let's wait for feedback by Stephen and Julian, since I don't know which mice they own. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317#c121 --- Comment #121 from Dean Hilkewich 2007-09-12 06:55:06 MST --- Stefan Dirsch, Thomas says that he cannot confirm the issue. "With the patch I can use sax2 and the Xserver without any problem (whereas I cannot say something about resolutions above 1280x1024 because this is the max. resolution of a single screen of my Twinview setup)." Like I say, until the patch is applied and then reconfigured using sax -r, the xorg is correct with the metamodes. With the MX510 you can change the xorg easily with sax and you do not have metamode issues. It's only after the patch is applied and a sax -r is done that the xorg then becomes unwritable/unupdateable with the wrong metamodes. If instead of running the patch I just use the old mouse config pre evdev: Section "InputDevice" Driver "mouse" Identifier "Mouse[1]" Option "Buttons" "12" Option "Device" "/dev/input/mice" Option "Name" "Logitech USB Gaming Mouse" Option "Protocol" "explorerps/2" Option "Vendor" "Sysp" Option "ZAxisMapping" "4 5" EndSection Then sax remains fully configurable and metamodes are correct. sax becomes totally useless after the patch is applied where as without it it functions properly if the old style mouse confiq is used. So once again.... patch=sax incorrect metamodes and the resulting xorg.conf never gets written after sax -r is done. no patch but old mouse config is edited in xorg, sax remains fully and properly functional The bug only appears after the patch is applied and a sax -r is done. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317#c123 Marcus Schaefer changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #123 from Marcus Schaefer 2007-09-12 08:03:19 MST --- done -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317#c125 --- Comment #125 from Stefan Dirsch 2007-09-12 08:58:14 MST --- I'm sorry, but we don't have any other choice at the moment. I suggest to send us such a mouse so we can improve the situation for the next openSUSE release. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317#c127 --- Comment #127 from Stefan Dirsch 2007-09-12 09:10:53 MST --- I've tested on a x64 system. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317#c129 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |thomas@regner.be --- Comment #129 from Stefan Dirsch 2007-09-12 11:01:55 MST --- *** Bug 309925 has been marked as a duplicate of this bug. *** https://bugzilla.novell.com/show_bug.cgi?id=309925 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317#c131 --- Comment #131 from Stephen Shaw 2007-09-12 13:28:32 MST --- Maybe instead of closing this bug, we reassign it to opensuse 11.0? This way no one thinks that this is fixed? I just seems weird to make something resolve this way. It would be cool to have an option such as delayed I'll still plan on testing the patch tonight. I'm also running x86_64, because of XEN testing as well -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317#c133 --- Comment #133 from Dean Hilkewich 2007-09-12 14:03:04 MST --- "If I did understand Dean correctly, sax2 refuses to rewrite the xorg.conf with the patch in place in general - unrelated to the resolution. Yes, this should be handled in a different bugreport." Ok I'm not sure how you can determine that this is not directly a result of the patch as pre-patch sax2 saves and configures xorg.conf properly. After applying the patch sax2 no longer saves the xorg file but seems to use a "default or generic" metamodes (where it gets these modes I don't have any idea). After the patch is applied and a sax2 -r is done you cannot see nor adjust any xorg.conf settings using sax2. Using sax2 create a new xorg.conf then results in no updated xorg.conf being written (file date and time stays the same). Even then swapping the G5 for the MX510 does not cure the issue afterwards. Even installing the nvidia drivers and then using the sax2 -m 0=nvidia results in no changes being applied to the xorg.conf. With patch = cannot update xorg.conf without patch = can update xorg.conf Only 1 thing has changed between the setups and that's the patch. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317#c135 --- Comment #135 from Dean Hilkewich 2007-09-12 14:10:59 MST --- After the patch sax2 does not seem to save the xog.conf. How would I create a new bug that is a direct result of the patch? Title it..."Patch to fix evdev breaks sax2?" -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317#c137 --- Comment #137 from darren winter 2007-09-12 21:23:34 MST --- Created an attachment (id=163745) --> (https://bugzilla.novell.com/attachment.cgi?id=163745) default suse xorg - after running sax2 so... i ran sax2 again, after the patch. before running it i move the original xorg.conf file from my suse installation (before any nvidia stuff was added). when sax2 was done, the test never ran, so i launched sax2 again, this time skipping the test and just telling it to save my settings. it did not make a single change to my xorg.conf. so, i started over without an xorg.conf file in place. test button did nothing but close sax2. clicking save button closes sax2 but an xorg.conf file is never written. so, i'm back on my nvidia xorg.conf for now. finally, even though sax2 hates my xorg.conf (does nothing for it), it sure seems to love playing with my /boot/grub/menu.lst file: Bug 310115 - sax2 modifies grub's menu.lst - why is sax2 modifying a boot loader?! https://bugzilla.novell.com/show_bug.cgi?id=310115 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317#c139 --- Comment #139 from Stefan Dirsch 2007-09-12 21:50:58 MST ---

Bug 310115 - sax2 modifies grub's menu.lst - why is sax2 modifying a boot loader?! Thanks. I commented on this bug now.

-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317#c141 --- Comment #141 from Stephen Shaw 2007-09-12 22:25:01 MST --- that's strange, when I was running one of my PV domUs today I ran into the same thing with sax2. When I hit test it exited out. Point being that might be a sax2 problem that has nothing to do with this. Burning beta 3 right now -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317#c143 --- Comment #143 from Stefan Dirsch 2007-09-13 01:20:21 MST --- (In reply to comment #142 from Stephan Kulow)

then don't hijack random bugs? Please ignore this comment. Probably he missed the context of the discussion here.

-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317#c145 --- Comment #145 from Dean Hilkewich 2007-09-14 23:17:25 MST --- *** Bug 310305 has been marked as a duplicate of this bug. *** https://bugzilla.novell.com/show_bug.cgi?id=310305 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317 Stephan Kulow changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |coolo@novell.com Flag| |SHIP_STOPPER- -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317#c148 --- Comment #148 from darren winter 2007-09-21 08:07:18 MST --- i just wanted to follow up on this bug... i installed rc1 last night and after the installation, runlevel 5 worked. granted, it's not with evdev, so this was the "workaround" in action. at least end users won't be stuck at a text based login this way. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317#c150 --- Comment #150 from Thomas Meindl 2007-09-21 12:10:06 MST --- As far as I can see there's no workaround in my xorg.conf . Instead there is a nice evdev configuration for the mouse, which works. :-) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317#c152 darren winter changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sgt-d@sodpit.com --- Comment #152 from darren winter 2007-09-23 15:53:48 MST --- @stephen comment #122 mentions disabling evdev for the logitech g5 gaming mouse (v1) which was causing the problem. i'm not sure what changed, but x is working after installation. @julian... what happens? no x? @thomas... my xorg.conf also shows evdev, what in the world?!? Section "InputDevice" Driver "evdev" Identifier "Mouse[1]" Option "Buttons" "20" Option "InputFashion" "Mouse" Option "Name" "Logitech USB Gaming Mouse" Option "Protocol" "event" Option "SendCoreEvents" "on" Option "Vendor" "Sysp" Option "ZAxisMapping" "4 5" EndSection hmm, maybe evdev is causing my major mouse slow down problems during heavy system load - bug 327517. my old installs ever used evdev: Section "InputDevice" # generated from default Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/psaux" Option "Emulate3Buttons" "no" Option "ZAxisMapping" "4 5" EndSection -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317#c154 --- Comment #154 from Stephen Shaw 2007-09-29 09:04:07 MST --- I finally have some info on my mouse. Bus 002 Device 006: ID 046d:c50e Logitech, Inc. MX-1000 Cordless Mouse Receiver still the same issue. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=262317 User sndirsch@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=262317#c156 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Component|SaX2 |SaX2 OS/Version|openSUSE 11.0 |openSUSE 10.3 Product|openSUSE 11.0 |openSUSE 10.3 Platform|x86-64 |Other Resolution| |FIXED Version|Factory |Alpha 7 --- Comment #156 from Stefan Dirsch 2008-04-17 04:47:24 MST ---

I'd like to reopen this bug for openSUSE 11.0. I bought a new Logitech VX Nano notebook mouse yesterday and found out, that I have to use the evdev driver to be able to use all the buttons this mouse provides.

Please open a seperate bugreport for this as enhancement? Thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.