Bug 148155

Maybe I should add that the mouse is a Logitech USB-mouse.

Please attach `hwinfo --mouse' and your yast logfiles, as well as /etc/sysconfig/mouse and /etc/X11/Xorg.conf.

Created attachment 66519 [details]
as requested /etc/sysconfig/mouse

Created attachment 66520 [details]
As requested /etc/X11/xorg.conf

Created attachment 66521 [details]
hwinfo --mouse copied to text file

Created attachment 66522 [details]
/var/log/YAST2 - gzipped.

Stefan ?

Martin, you seem to have clicked on "Cancel" (or hit "Esc") in that dialog asking you whether or not to switch mouse buttons. Otherwise this log line would be in one of the y2logs - and I can't find it:

    Switching mouse buttons: xmodmap -e "pointer = 3 2 1"


See also yast2/qt/src/YQUI_x11.cc:

void YQUI::maybeLeftHandedUser()
{
    if ( _askedForLeftHandedMouse )
	return;

    QString message =
	_( "You clicked the right mouse button "
	   "where a left-click was expected."
	   "\n"
	   "Switch left and right mouse buttons?"
	   );
    int button = QMessageBox::question( 0,
					// Popup dialog caption
					_( "Unexpected Click" ),
					message,
					QMessageBox::Yes | QMessageBox::Default,
					QMessageBox::No,
					QMessageBox::Cancel | QMessageBox::Escape );

    if ( button == 0 )	// Yes
    {

	const char * command = 
	    _leftHandedMouse ?
	    "xmodmap -e \"pointer = 1 2 3\"":	// switch back to right-handed mouse
	    "xmodmap -e \"pointer = 3 2 1\"";	// switch to left-handed mouse

	_leftHandedMouse	 = ! _leftHandedMouse; 	// might be set repeatedly!
	_askedForLeftHandedMouse = false;	// give the user a chance to switch back
	y2milestone( "Switching mouse buttons: %s", command );
	
	system( command );
    }
    else if ( button == 1 )	// No
    {
	_askedForLeftHandedMouse = true;
    }
}


(sorry for the formatting, Bugzilla forces line wrapping)

*** Bug 166973 has been marked as a duplicate of this bug. ***

Seems to be an issue anyway at least for RC1, Stefan please have a look

What new information is there that warrants reopening this issue?

It's the same issue for a way later release and the reporter is sure not to have hit Esc. If you have more questions, please ask him.

This one is a different case. There is no log entry, so this "xmodmap" call never happened.