Bug 391134

Summary: sax2: Can't kill X with ctrl-alt-backspace
Product: [openSUSE] openSUSE 11.0 Reporter: Karl Eichwalder <ke>
Component: SaX2Assignee: Marcus Schaefer <ms>
Status: RESOLVED FIXED QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None CC: agraf, aj, benji, eich, mge, sndirsch, suse-beta
Version: Factory   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Bug Depends on: 388189    
Bug Blocks:    

Description Karl Eichwalder 2008-05-16 04:06:59 UTC 
+++ This bug was initially created as a clone of Bug #388189 +++

------- Comment #19 From Juergen Weigert  2008-05-15 18:53:26 MST
Thanks for the added complexity. I cannot see much support for this new
feature, neither in nor outside of suse. 
Dont we want to educate all debian and redhat users about our new
incompatibility?

Either revert this or advertise it broadly *and*
adjust all packages that instruct the user how to kill the X-Server.

E.g. sax2 has this message box:
|Final Steps
|---------------
|The last step is saving your new
|configuration. It is recommended to test the
|new configuration before saving it. If the test
|server shows a corrupted desktop, press [
|Ctrl+Alt+Backspace ] to kill the server.
|
|[Test] [Save] [Cancel]



Would not be nice, if a user burns his brand new monitor to 
death, although he tried to follow the instructions.

============================================================

Please, check sax2 for consistency with the new c-a-b behavior.
Comment 1 Stefan Dirsch 2008-05-16 06:51:16 UTC 
... press [Ctrl+Alt+Backspace ] and [Ctrl+Alt+Backspace ] shortly after a loud warning to kill the server.
Comment 2 Marcus Schaefer 2008-05-16 09:17:21 UTC 
sorry what is this all about ? you want me to update the information
displayed in the message box according to a new Ctrl-Alt-Backspace feature
which I frankly said don't know anything about ?

If so please provide a suggestion for the new text. Otherwise don't let
me guess what this bug wants to tell me

thanks
Comment 3 Karl Eichwalder 2008-05-16 09:36:14 UTC 
I think Stefan's proposal is fine ( #c1 ):

s/Ctrl+Alt+Backspace ]/Ctrl+Alt+Backspace ] and [Ctrl+Alt+Backspace ] shortly after a loud warning/
Comment 4 Marcus Schaefer 2008-05-16 10:00:50 UTC 
sorry but what should that text tell me

   "Ctrl+Alt+Backspace ] and [Ctrl+Alt+Backspace ] shortly after a loud warning"

what is a load warning ? do I get a beep or something after the first
Ctrl-Alt-Backspace ?
Comment 5 Stefan Dirsch 2008-05-16 10:19:56 UTC 
Right, you get a beep via your PC Speaker after the first Ctrl-Alt-Backspace.
Comment 6 Juergen Weigert 2008-05-16 10:32:14 UTC 
Just add the word 'twice' after the closing ']'.
This should independently of any beeps or warnings.
Comment 7 Stephan Kulow 2008-05-16 11:22:21 UTC 
I think "press Ctrl+Alt+Backspace" is fine - it doesn't say "once" :)

But if you have to change the text anyway, please replace the space with &nbsp;  - the line break before ] or after [ looks weird.
Comment 8 Juergen Weigert 2008-05-16 11:49:58 UTC 
I doubt you think its fine. You are joking.
Comment 9 Stefan Dirsch 2008-05-16 11:56:32 UTC 
(In reply to comment #6 from Juergen Weigert)
> Just add the word 'twice' after the closing ']'.
> This should independently of any beeps or warnings.
I do *not* agree. In case we'll revert this feature (very likley IMHO seing the feedback we got up to now) people will kill not only the Xserver SaX2 started but also the Xserver SaX2 is running on top, which might be the current Xsession.
Comment 10 Juergen Weigert 2008-05-16 12:57:55 UTC 
I see, I did not think of that problem. Your wording attempts to make the user aware of the problem of killing too many servers. I doubt this works.

If SaX would start its Xserver with ZapWarning off, its instructions needed no change.
Otherwise, I suggest to add '(twice if beeping)' after the closing ']'.
Comment 11 Stefan Dirsch 2008-05-16 13:11:30 UTC 
> If SaX would start its Xserver with ZapWarning off, its instructions needed
> no change.

I thought about this as well. But then a different config will be written than has been tested. I don't think Marcus does like this idea.
Comment 12 Marcus Schaefer 2008-05-16 13:24:31 UTC 
*** Bug 388189 has been marked as a duplicate of this bug. ***
Comment 13 Marcus Schaefer 2008-05-16 13:26:51 UTC 
* message text changed
* new pot committed to lcn/50-Pot
* no go for ZapWarning
* package submitted