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.