Bug 220431

Summary:	doubleclicking on sax2 module within yast2 causes X server restart
Product:	[openSUSE] openSUSE 10.2	Reporter:	Ladislav Michnovic <lmichnovic>
Component:	YaST2	Assignee:	Marcus Schaefer <ms>
Status:	RESOLVED WONTFIX	QA Contact:	Jiri Srain <jsrain>
Severity:	Normal
Priority:	P5 - None
Version:	Beta 2
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	logs

Description Ladislav Michnovic 2006-11-13 14:57:37 UTC

Running sax2 within yast2 or alone causes switching to console and back to the X server, which is probably intended.
But when I double click on the sax2 module within yast, what is not so unlike situation it runs sax2 twice. And the result is the restart of X server with loosing my session and all unsaved data and it did not start sax2. 
Quite annoying.
I'm using the NVIDIA binary driver.

Comment 1 Matej Horvath 2006-11-15 10:26:36 UTC

Please provide the YaST logs.
http://en.opensuse.org/Bugs/YaST

Comment 2 Ladislav Michnovic 2006-11-15 11:01:06 UTC

Created attachment 105358 [details]
logs

Comment 3 Ladislav Michnovic 2006-11-15 11:01:28 UTC

attached.

Comment 4 Marcus Schaefer 2006-11-16 11:13:26 UTC

the result is that your current session dies because of some reason.
Of course this is not a bug in sax but in the driver. What I did is
a vt switch and a probeonly call. No matter how often one does that
the currently running X-Server is not allowed to crash

As long as we cannot fix the binary nvidia driver you should prevent
such double clicks in yast

Comment 5 Edith Parzefall 2006-11-16 14:41:57 UTC

Stefan, any idea how to ignore a double click?

Comment 6 Stefan Hundhammer 2006-11-17 18:14:43 UTC

Double clicks are prevented in the Qt control center - if indeed they are double clicks (within the double click interval), not just two separate clicks.

For one thing, there is NO WAY that this can possibly be CRITICAL. It's been like that forever. For another, if it is really crucial that a YaST2 module is only started once, that module should make that sure. The control center has no way of knowing if another instance of the same module is still running successfully (as opposed to hanging or crashed).

Comment 7 Marcus Schaefer 2006-11-20 10:00:05 UTC

well as I said we cannot fix a binary driver the best choice you had
was reassigning to me... nice try

Comment 8 Stefan Hundhammer 2006-11-20 14:03:04 UTC

The binary-only driver is not the only possible location to fix that.