[Bug 850531] New: Login prompt hangs at shutdown
https://bugzilla.novell.com/show_bug.cgi?id=850531 https://bugzilla.novell.com/show_bug.cgi?id=850531#c0 Summary: Login prompt hangs at shutdown Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Major Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers@suse.de ReportedBy: rb03884@gmail.com QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:25.0) Gecko/20100101 Firefox/25.0 Every time shutdown or restart is selected the Plymouth screen appears briefly followed by the login prompt. It hangs briefly and then shuts down. This happened in the Beta version of 12.3 but was fixed. This MUST be fixed before final release as it appears ever time as a sloppy shutdown. Reproducible: Always Steps to Reproduce: 1. At the KDE4 desktop select shutdown 2. Or select restart 3. Notice how Plymouth appears briefly followed by the login prompt Actual Results: After shutdown or restart Plymouth appears briefly. This is followed by the "login prompt" hang. Expected Results: Plymouth appears and system shutdown and/or restarts. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=850531
https://bugzilla.novell.com/show_bug.cgi?id=850531#c1
--- Comment #1 from Roman Bysh
https://bugzilla.novell.com/show_bug.cgi?id=850531
https://bugzilla.novell.com/show_bug.cgi?id=850531#c2
--- Comment #2 from Roman Bysh
https://bugzilla.novell.com/show_bug.cgi?id=850531
https://bugzilla.novell.com/show_bug.cgi?id=850531#c
Hrvoje Senjan
https://bugzilla.novell.com/show_bug.cgi?id=850531
https://bugzilla.novell.com/show_bug.cgi?id=850531#c
Hrvoje Senjan
https://bugzilla.novell.com/show_bug.cgi?id=850531
https://bugzilla.novell.com/show_bug.cgi?id=850531#c
Roman Bysh
https://bugzilla.novell.com/show_bug.cgi?id=850531
https://bugzilla.novell.com/show_bug.cgi?id=850531#c
zhang jiajun
https://bugzilla.novell.com/show_bug.cgi?id=850531
https://bugzilla.novell.com/show_bug.cgi?id=850531#c3
Roman Bysh
https://bugzilla.novell.com/show_bug.cgi?id=850531
https://bugzilla.novell.com/show_bug.cgi?id=850531#c4
--- Comment #4 from Roman Bysh
https://bugzilla.novell.com/show_bug.cgi?id=850531
https://bugzilla.novell.com/show_bug.cgi?id=850531#c5
Felix Miata
https://bugzilla.novell.com/show_bug.cgi?id=850531
https://bugzilla.novell.com/show_bug.cgi?id=850531#c6
--- Comment #6 from Roman Bysh
https://bugzilla.novell.com/show_bug.cgi?id=850531
https://bugzilla.novell.com/show_bug.cgi?id=850531#c7
Raymond Wooninck
https://bugzilla.novell.com/show_bug.cgi?id=850531
https://bugzilla.novell.com/show_bug.cgi?id=850531#c8
Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=850531
https://bugzilla.novell.com/show_bug.cgi?id=850531#c9
--- Comment #9 from Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=850531
https://bugzilla.novell.com/show_bug.cgi?id=850531#c10
Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=850531
https://bugzilla.novell.com/show_bug.cgi?id=850531#c11
Frederic Crozat
@ Frederic : Please tell us what changes had been done in plymouth and systemd for this smooth transition?
No change have been done in plymouth nor systemd, since both are supporting it out of the box. The way how it is supposed to work is the following: - plymouthd is started in initrd (or later by systemd) and display a graphical splash which will hide the text console - systemd will detect this fact and will send its output to plymouthd (this can be used to track progress of the boot) - for runlevel 5, when gdm is being started, plymouthd is put on hold but not terminated: it is needed to keep the splash on screen (KMS fd needs to stay opened). X server is then called with a flag to not clear the screen but write on top of it. This will allow blending from the splash to the current display manager. - for runlevel 3, plymouthd is stopped before starting getty. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=850531
https://bugzilla.novell.com/show_bug.cgi?id=850531#c12
Dr. Werner Fink
- for runlevel 5, when gdm is being started, plymouthd is put on hold but not terminated: it is needed to keep the splash on screen (KMS fd needs to stay opened). X server is then called with a flag to not clear the screen but write on top of it. This will allow blending from the splash to the current display manager.
@ Stefan: Is this flag honoured by the nouveau driver?
- for runlevel 3, plymouthd is stopped before starting getty.
@ Frederic: I've seen that plymouthd has locked the termios structure of /dev/ttyS0 ... how does this work? Without my hack for agetty in util-linux you can not type in the password due broken termios settings. The other solution was to add the line ``ExecStartPre=-/usr/bin/plymouth quit'' as I've verified. Also plymouthd does forbid change of the virtual console which may break X11 servers trying to switch to the next free virtual console or to switch to the given virtual console. Both are IMHO a nogo. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=850531
https://bugzilla.novell.com/show_bug.cgi?id=850531#c13
Stefan Dirsch
(In reply to comment #11)
- for runlevel 5, when gdm is being started, plymouthd is put on hold but not terminated: it is needed to keep the splash on screen (KMS fd needs to stay opened). X server is then called with a flag to not clear the screen but write on top of it.
@Frederic. Which Xserver flag is this? You mean Xserver option, right? I know gdm is hardcoding the call of the Xserver. Unfortunately ...
This will allow blending from the splash to the current display manager.
@ Stefan: Is this flag honoured by the nouveau driver?
Currently I'm assuming this is not driver related ... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=850531
https://bugzilla.novell.com/show_bug.cgi?id=850531#c14
Frederic Crozat
(In reply to comment #12)
(In reply to comment #11)
- for runlevel 5, when gdm is being started, plymouthd is put on hold but not terminated: it is needed to keep the splash on screen (KMS fd needs to stay opened). X server is then called with a flag to not clear the screen but write on top of it.
@Frederic. Which Xserver flag is this? You mean Xserver option, right? I know gdm is hardcoding the call of the Xserver. Unfortunately ...
"-background none"
This will allow blending from the splash to the current display manager.
@ Stefan: Is this flag honoured by the nouveau driver?
Currently I'm assuming this is not driver related ...
It was, at least for the background "none" part, which wasn't handled by all drivers in the past (I don't know the situation now). But the blending itself was handled by gdm/gnome-settings-daemon -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=850531
https://bugzilla.novell.com/show_bug.cgi?id=850531#c15
--- Comment #15 from Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=850531
https://bugzilla.novell.com/show_bug.cgi?id=850531#c16
--- Comment #16 from Stefan Dirsch
@Frederic. Which Xserver flag is this? You mean Xserver option, right? I know gdm is hardcoding the call of the Xserver. Unfortunately ...
"-background none"
Ok. So that's what I asssumed. I guess only gdm calls the Xserver that way. KDM and other don't ...
This will allow blending from the splash to the current display manager.
@ Stefan: Is this flag honoured by the nouveau driver?
Currently I'm assuming this is not driver related ...
It was, at least for the background "none" part, which wasn't handled by all drivers in the past (I don't know the situation now). But the blending itself was handled by gdm/gnome-settings-daemon
Ah. I remember we had a special patch against intel driver for this, when we worked on Moblin/Meego a few years ago. But we needed to ditch this patch for several reasons (after having it disabled for several openSUSE releases). So I would guess currently there is no driver at all, which honours this flag ... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=850531
https://bugzilla.novell.com/show_bug.cgi?id=850531#c17
--- Comment #17 from Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=850531
https://bugzilla.novell.com/show_bug.cgi?id=850531#c18
--- Comment #18 from Frederic Crozat
(In reply to comment #14)
@Frederic. Which Xserver flag is this? You mean Xserver option, right? I know gdm is hardcoding the call of the Xserver. Unfortunately ...
"-background none"
Ok. So that's what I asssumed. I guess only gdm calls the Xserver that way. KDM and other don't ...
I can't comment on KDM. I think the support for smooth transition in KDM isn't upstream.
This will allow blending from the splash to the current display manager.
@ Stefan: Is this flag honoured by the nouveau driver?
Currently I'm assuming this is not driver related ...
It was, at least for the background "none" part, which wasn't handled by all drivers in the past (I don't know the situation now). But the blending itself was handled by gdm/gnome-settings-daemon
Ah. I remember we had a special patch against intel driver for this, when we worked on Moblin/Meego a few years ago. But we needed to ditch this patch for several reasons (after having it disabled for several openSUSE releases). So I would guess currently there is no driver at all, which honours this flag ...
This was merged upstream, for Intel, ATI and Nouveau : canDoBGNoneRoot is the property checked by Xserver ( 8976e9766edfb33f5cf3f6d54f09e46d29bc4ec5 in xserver 1.10) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=850531
https://bugzilla.novell.com/show_bug.cgi?id=850531#c19
--- Comment #19 from Frederic Crozat
We are talking about KDE4 desktop ... nevertheless it has to work with *all* dekstop, display managers, and X servers/drivers out there.
Either KDE4 has to be fixed or it should stop plymouth before starting (this is why there is a plymouth_quit() function in /etc/init.d/xdm, to handle DM not handling the smooth transition properly). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=850531
https://bugzilla.novell.com/show_bug.cgi?id=850531#c20
--- Comment #20 from Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=850531
https://bugzilla.novell.com/show_bug.cgi?id=850531#c21
--- Comment #21 from Raymond Wooninck
https://bugzilla.novell.com/show_bug.cgi?id=850531
https://bugzilla.novell.com/show_bug.cgi?id=850531#c22
--- Comment #22 from Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=850531
https://bugzilla.novell.com/show_bug.cgi?id=850531#c23
--- Comment #23 from Frederic Crozat
Beside this: Why does the patch stop-graphical.patch add the line
Conflicts=graphical.target
in plymouth-quit.service.in and plymouth-quit-wait.service.in? With this it is impossible to use the units in graphical.target.
That was the way I found to ensure plymouth-quit.service was not run when running in runlevel 5, since this part was handled by either gdm/KDM or xdm initscript. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=850531
https://bugzilla.novell.com/show_bug.cgi?id=850531#c24
Frederic Crozat
Instead of adding the Conflicts= lines IMHO an other solution could be to start plymouthd on vt7 ... or patch plymouthd to start its daemon on vt7 if possible.
or to do like Fedora and have everything running on VT1 but that's a battle I didn't even tried to start on Factory.. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=850531
https://bugzilla.novell.com/show_bug.cgi?id=850531#c25
--- Comment #25 from Stefan Dirsch
(In reply to comment #15)
We are talking about KDE4 desktop ... nevertheless it has to work with *all* dekstop, display managers, and X servers/drivers out there.
Either KDE4 has to be fixed or it should stop plymouth before starting (this is why there is a plymouth_quit() function in /etc/init.d/xdm, to handle DM not handling the smooth transition properly).
Indeed. kdm could make use of it by calling it in /usr/lib/X11/displaymanagers/kdm, but it doesn't. xdm still does ... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=850531
https://bugzilla.novell.com/show_bug.cgi?id=850531#c26
--- Comment #26 from Raymond Wooninck
https://bugzilla.novell.com/show_bug.cgi?id=850531
https://bugzilla.novell.com/show_bug.cgi?id=850531#c27
Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=850531
https://bugzilla.novell.com/show_bug.cgi?id=850531#c28
--- Comment #28 from Raymond Wooninck
I'm aware that kdm does work similar as plymouth_quit() function in /etc/init.d/xdm but more smooth one as seen from the patch you've linked to.
Each DM has its own pros and cons. I know that KDM is not one of the best for the smooth transition as that a full black screen is shown before the KDM login screen is shown. GDM is handling this better, but I guess that we are then starting to talk about KDM internal procedures, etc and not about plymouth specifics. As indicated upstream recognized that KDM is actually not really maintained anymore and the KDE Framework 5 releases will no longer have KDM there. Actually the KDM sources have already been deleted from upstream.
The question is: wouldn't it better to stop plymouthd before any dm is started. And still to see the smooth transion on vt7 to start the daemon spawned by the plymouthd executable on vt7?
How many effort would it be to implement this by using the ply_terminal_activate_vt() before the daemon will be forked ?
Question for me is what are we trying to solve here ? What is the real bug behind this all ? The original bug was that upon shutdown the login screen was shown. Which happens to me also from time to time and that always happens after some updates. This is something that is not plymouth related, as already indicated by me, as that it also happens without plymouth installed. The KDE workspace issues the shutdown command and that is interrupted as that it appears that the user no longer has the authority to shutdown the system and therefore the system returns to the login prompt. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=850531
https://bugzilla.novell.com/show_bug.cgi?id=850531#c29
--- Comment #29 from Dr. Werner Fink
Every time shutdown or restart is selected the Plymouth screen appears briefly followed by the login prompt.
It hangs briefly and then shuts down. This happened in the Beta version of 12.3 but was fixed.
.. ``hangs briefly and then shuts down'' is not this. IMHO plymouthd is started for shutdown the system and shows its nice screen and then it will be terminated and the system shows its default screen that is the last messaages of the agetty which I guess is also not active anymore. I don't know why this MUST be fixed ... it is only an optical issue and does not hurt nor does it influence the usability functionality, or security. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=850531
https://bugzilla.novell.com/show_bug.cgi?id=850531#c30
--- Comment #30 from Roman Bysh
https://bugzilla.novell.com/show_bug.cgi?id=850531
https://bugzilla.novell.com/show_bug.cgi?id=850531#c31
--- Comment #31 from Roman Bysh
https://bugzilla.novell.com/show_bug.cgi?id=850531
https://bugzilla.novell.com/show_bug.cgi?id=850531#c32
Dr. Werner Fink
We are requesting a patch for the shutdown.
.. you may become part of the maitainers of plymouth and help Mark to debug and implement such a patch. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=850531
https://bugzilla.novell.com/show_bug.cgi?id=850531#c33
--- Comment #33 from Mark van Tinteren
https://bugzilla.novell.com/show_bug.cgi?id=850531
https://bugzilla.novell.com/show_bug.cgi?id=850531#c34
--- Comment #34 from Roman Bysh
http://bugzilla.novell.com/show_bug.cgi?id=850531
--- Comment #35 from Roman Bysh
http://bugzilla.novell.com/show_bug.cgi?id=850531
Hrvoje Senjan
participants (1)
-
bugzilla_noreply@novell.com