Bug 288106 - evdev causes SaX2 to crash X on install
Summary: evdev causes SaX2 to crash X on install
Status: RESOLVED DUPLICATE of bug 262317
Alias: None
Product: openSUSE 10.3
Classification: openSUSE
Component: SaX2 (show other bugs)
Version: Alpha 5
Hardware: x86-64 openSUSE 10.3
: P2 - High : Critical (vote)
Target Milestone: ---
Assignee: Marcus Schaefer
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-06-28 06:20 UTC by Dean Hilkewich
Modified: 2007-06-28 12:28 UTC (History)
0 users

See Also:
Found By: Beta-Customer
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Crashlog when using evdev (58.52 KB, text/x-log)
2007-06-28 06:20 UTC, Dean Hilkewich 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Dean Hilkewich 2007-06-28 06:20:18 UTC 
Created attachment 148673 [details]
Crashlog when using evdev

Logitech G5 mouse

Upon final device configuration during install SaX2 crashes trying to complete install and never finishs.  The error comes from SaX2 determining that the mouse should use evdev under the mouses entry in Section "InputDevice".  Inserting a PS2 mouse will allow for installation to complete.  Once installation is complete, changing the entry in xorg.conf to use a config like in 10.2

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


will result in being able to once again boot into X with the G5 mouse although SaX2 still will not launch with G5 mouse on system.


SaX crashlog attached
Comment 1 Dean Hilkewich 2007-06-28 12:27:13 UTC 

*** This bug has been marked as a duplicate of bug 262317 ***
Comment 2 Dean Hilkewich 2007-06-28 12:28:38 UTC 

*** This bug has been marked as a duplicate of bug 262317 ***