http://bugzilla.novell.com/show_bug.cgi?id=980292 http://bugzilla.novell.com/show_bug.cgi?id=980292#c2 --- Comment #2 from Stefan Hundhammer <shundhammer@suse.com> --- IIRC I added support for catching double clicks in the control center a long time ago. I can still recall that there was a problem with switching to or from daylight savings time that would use a one-hour timeout in that case. Anyway, forbidding running the same module twice would be WAY too drastic IMHO. What do you do when you have multiple admins on any machine, and one of them left a YaST module open while leaving for the day - and, worse, didn't come back because he got sick or went on vacation? Do you really want to hunt down running processes and identify them which module they run? If double clicking in the control center really is the problem, then the control center has to take care of it - locally, in that one instance. IMHO it should already do that, but it can't hurt to check. But let's not go completely over board with this. Remember how many times Firefox complains about some old Firefox instance alledgedly still being active? And how many times this is just plain wrong? And Firefox does not even need to make a difference for different tasks for different instances - unlike YaST. I strongly vote for not emulating that kind of brain dead^W^Wquestionable behaviour. -- You are receiving this mail because: You are on the CC list for the bug.