https://bugzilla.novell.com/show_bug.cgi?id=227458 ------- Comment #2 from y.poireault@laposte.net 2006-12-11 01:34 MST ------- (In reply to comment #1)

Please attach your yast log files. http://en.opensuse.org/Bugs/YaST

Thank you.

Ok, I've read the doc. But do I have to do something special in Yast that would produce some particular traces ? or the goal is to have the logs resulting from the installation, in this case I hope it was not already overwritten (because I went a lot in Yast since the install) ? Anyway, I'll tar the whole yast logs tonight. Thank you. -- 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=227458 y.poireault@laposte.net changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED ------- Comment #4 from y.poireault@laposte.net 2006-12-12 11:47 MST ------- Created an attachment (id=109387) --> (https://bugzilla.novell.com/attachment.cgi?id=109387&action=view) Yast logfiles The attachment contains only the files for which "grep -i mouse" gives results. (I can provide the full archive, but the file is larger) -- 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=227458 ms@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |y.poireault@laposte.net ------- Comment #5 from ms@novell.com 2006-12-14 06:45 MST ------- Could you attach the xorg.conf currently in use ? 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=227458 ms@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mhopf@novell.com Status|ASSIGNED |NEEDINFO Info Provider| |y.poireault@laposte.net ------- Comment #7 from ms@novell.com 2006-12-18 04:05 MST ------- I'm sorry but I don't want to see the file you have changed already. I would like to see what sax2 added originally. You can recreate that file by calling: cp /etc/X11/xorg.conf /etc/X11/xorg.conf.myconf sax2 -r -a I'm pretty sure the section will add ZAxisMapping 4 5 and Buttons 5 For the current mouse driver this would be correct because the driver doesn't handle the additional buttons correctly. We plan to use evdev in the future to support that better 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=227458 y.poireault@laposte.net changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|y.poireault@laposte.net | ------- Comment #9 from y.poireault@laposte.net 2006-12-18 12:53 MST ------- Created an attachment (id=110188) --> (https://bugzilla.novell.com/attachment.cgi?id=110188&action=view) original xorg.conf Don't care about the name of the file, I renamed it because of my many (15 approx ...) tests. It's the file I created with the provided command "sax2 -r -a". the content is as Herr Schaefer expected. Ok, conclusion of the tests now: my mouse is working again :) I've commented the pointer=... in my /etc/X11/Xmodmap that I've added because of a bad assumption (In fact it was the line I've added on my 10.0 to make my mouse working). Without this line xev shows better result: left button = button 1 middle button = button 2 right button = button 3 mouse wheel up = button 4 mouse wheel down = button 5 extra left = button 8 extra right = button 9 little top button = button 1 I've then added a line to my xorg.conf, like Herr Hopf proposed: Option "ButtonMapping" "1 2 3 6 7" And that's it. No more Xmodmap modification needed. The "Buttons" value in xorg.conf doesn't change anything, either "5" or "8" works. Now, just by curiosity, I started my 10.0 again, on it, without any Xmodmap modification the results were: left button = button 1 middle button = button 2 right button = button 3 mouse wheel up = nothing mouse wheel down = nothing extra left = button 4 extra right = button 5 little top button = button 1 I don't really understand how all that works, but at that time I had to add this line to my /etc/X11/Xmodmap: pointer = 1 2 3 6 7 8 4 5 and in xorg.conf: Option "ZAxisMapping" "7 8" (as you saw in my first comments) and that made the trick. Thank you for your help, and sorry for this waste of time. I shouldn't have copied my old conf file to this 10.2 so fast ... In fact I didn't knew that Xmodmap could modify the result of Xev (thought it was something returned by the kernel, something immutable), so when I saw no event for one button, I thought it was a "bug" ... Regards -- 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=227458 ------- Comment #11 from y.poireault@laposte.net 2006-12-19 06:31 MST ------- With the original xorg.conf and /etc/X11/Xmodmap (without any pointer= line) the mouse buttons sends all events (according to xev). The value are given in comment #9. But, the two extra buttons only act as "left-click". Then I can add the ButtonMapping in xorg.conf to make them work as "back/forward", or add a line in Xmodmap (which I don't remember now). My understanding (which is more "intuition" based on the many tests I've made) is that "back/forward" are by default expected/mapped to "button6" and "button7", that's why I added: Option "ButtonMapping" "1 2 3 6 7" By default ButtonMapping (I mean when it's not present inthe conf file) is: Option "ButtonMapping" "1 2 3 8 9 ...." which (may) explain why my buttons won't worked originally. So, indeed (if I'm not a special case) the ButtonMapping line would be necessary by default for the MX310. -- 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=227458 mhopf@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |INVALID ------- Comment #13 from mhopf@novell.com 2006-12-19 07:11 MST ------- (In reply to comment #9)

I've commented the pointer=... in my /etc/X11/Xmodmap that I've added because of a bad assumption (In fact it was the line I've added on my 10.0 to make my mouse working). Without this line xev shows better result:

This was no bad assumption, this was the only possible workaround before 10.1. I think this was mentioned in the release notes, if not, that certainly is a bug :-P

little top button = button 1

We can't do nothing about that, that's PS/2 magic...

Now, just by curiosity, I started my 10.0 again, on it, without any Xmodmap modification the results were: mouse wheel up = nothing mouse wheel down = nothing

You would need a 'Option "ZAxisMapping" "4 5"' for that - this is now the default value. You had "7 8" - which is quite odd.

extra left = button 4 extra right = button 5

No button reordering by the driver in 10.0. The ButtonMapping option is new.

I don't really understand how all that works, but at that time I had to add this line to my /etc/X11/Xmodmap:

10.0: Physical button # 1-5 -> Logical # 1-5 -> user # 1,2,3,6,7 Wheel -> Logical # 7,8 -> user # 4,5 The last change was done by the xmodmap line - necessary, because the driver couldn't change buttons (physical == logical). Usually, wheel was mapped to 6,7 and "pointer = 1 2 3 6 7 4 5" was used. So your config was a bit odd, too.

Thank you for your help, and sorry for this waste of time. I shouldn't have copied my old conf file to this 10.2 so fast ... In fact I didn't knew that Xmodmap could modify the result of Xev (thought it was something returned by the kernel, something immutable), so when I saw no event for one button, I thought it was a "bug" ...

Xev shows events delivered to user programs. You can watch kernel events by using evtest. (In reply to comment #10)

Maybe a stupid question but are there any sax2 changes needed. According to comment #8 sax creates a valid configuration, according to comment #9 ButtonMapping is missing to make you happy ? :)

Stupid in the sense that the answer is trivial: no ;-) (In reply to comment #11)

But, the two extra buttons only act as "left-click". Then I can add the ButtonMapping in xorg.conf to make them work as "back/forward", or add a line in Xmodmap (which I don't remember now).

No, they act as button #8 and #9, and there is no default action in most programs. However, several you can configure to your needs. As we need buttons #6 and #7 free for a horizontal wheel, this is about all we can do for a general configuration. The user is always free to change as he likes, of course.

My understanding (which is more "intuition" based on the many tests I've made) is that "back/forward" are by default expected/mapped to "button6" and "button7", that's why I added:

You only get back/forward because that are the default actions for the horizontal wheel ;-) Try them in a panel with two scrollbars, they probably will scroll left/right. Closing this as INVALID, as it is in fact not a bug :-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, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=227458 ------- Comment #15 from mhopf@novell.com 2006-12-19 09:17 MST ------- (In reply to comment #14)

A little question still remain, does sax recognize precisely each mouse model and then apply a different scheme, or not ? Because in this case, although I'd

Sax2 can apply *exceptions* that might be necessary if something doesn't work at all (e.g. a mouse that doesn't send button # 1,2,3 for the three top buttons).

completely agree with your explanation (and that it's not a bug), the MX310 doesn't have a horizontal wheel, so the mapping could be done by default to back.forward. This would only be to help the "basic" user to have a stock system that behave like ... hummm ... on windows.

On Windows the behavior is dictated by the mouse driver. The one I use doesn't setup anything on these buttons. Also windows has more possible events to choose from. Also right now we don't have configurations for all known mice (we would certainly miss some), and also it would have to be debated what to actually do with the additional 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, or are watching someone who is.