Bug 399608

Summary:	Changing state of the xdm/earlyxdm service from graphical YaST brings down the X session
Product:	[openSUSE] openSUSE 11.0	Reporter:	Jiri Dluhos <jdluhos>
Component:	YaST2	Assignee:	Lukas Ocilka <locilka>
Status:	RESOLVED FIXED	QA Contact:	Jiri Srain <jsrain>
Severity:	Normal
Priority:	P5 - None	CC:	locilka, mvidner
Version:	RC 3
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Jiri Dluhos 2008-06-12 10:48:36 UTC

When using YaST runlevel editor, changing the state of xdm/earlyxdm service brings down the whole X server (xdm gets stopped or restarted, and takes X with it).

This is technically correct behavior, but can be a nasty surprise for an unknowing user; maybe we should detect this special case and change only the future setting of the service but not touch the running xdm.

Comment 1 Lukas Ocilka 2008-06-12 10:59:49 UTC

Don't try to remove the floor while you're standing on it :)
However this is more about breaking the door, xdm is not a floor for X.

Special case needs a special treatment -> Enhancement

Anyway, this is pretty generic. Changing the state while running in X (in xterm, or another term...) does the same. So why YaST only?

Comment 2 Martin Vidner 2008-06-12 11:22:43 UTC

No, this is a real bug.
Search for "This may kill your X session." in the runlevel sources.

Comment 3 Lukas Ocilka 2008-06-12 11:31:01 UTC

seven:/etc/init.d # grep -r "This may kill your X session" *
returns nothing :)

It's a special case and really an Enhancement (how to find out an X-session is running?), similar to stopping nfs while running with NFS-based system/home (check mounts?). Stopping iSCSI when running iSCSI-based system (check mounts?)...

Do we really want to have a special handling for all these cases? Samba client, for instance? Starting a firewall usually breaks icecream when not properly configured (fw). What about stopping syslog, show warning again? ...

Comment 4 Martin Vidner 2008-06-12 11:45:40 UTC

Not all of them. Just the one that is supposed to work:
http://svn.opensuse.org/svn/yast/trunk/runlevel/src/ui.ycp line 1260

Comment 5 Lukas Ocilka 2008-06-12 13:29:36 UTC

Well, the one silly check works :) but only for expert dialog, not for the normal one. Anyway, it doesn't check whether any X session is running or not.

Similar to:
"Your hair might be harmed during this procedure, proceed?"
"I have no hair!"
"Never mind, your hair might be harmed during this procedure, proceed?"
"Er, I said ..."
"I know, but your hair might be harmed during this procedure, proceed?"
"Yes, of course."
"'Yes' or 'No'?"
"Yes"
"Thank you for your cooperation, your hair will be harmed soon"
"But, ..."

Comment 6 Lukas Ocilka 2008-06-12 14:29:30 UTC

- Special treatment for special service restart: xdm and earlyxdm
  (bnc #399608)

yast2-runlevel-2.17.0 (11.1)