http://bugzilla.suse.com/show_bug.cgi?id=980292 http://bugzilla.suse.com/show_bug.cgi?id=980292#c6 Stefan Hundhammer <shundhammer@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(shundhammer@suse. | |com) | --- Comment #6 from Stefan Hundhammer <shundhammer@suse.com> --- (In reply to Lukas Ocilka from comment #4)
And what if we just warn the user that the same Yast module already runs?
That doesn't really change anything for the scenarios from comment #2. If anything, we'd need to offer the user to terminate that other YaST instance (e.g. send a SIGTERM, after a timeout a SIGKILL). Otherwise we'd end up in the same unfortunate scenario as Firefox does so often: The application flatly refuses to start, and the user has to hunt down processes to terminate manually. -- You are receiving this mail because: You are on the CC list for the bug.