Bug 379328 - sddm switches on killed X on shutdown, killing shutdown.
Summary: sddm switches on killed X on shutdown, killing shutdown.
Status: RESOLVED UPSTREAM
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_sddm (other bugs)
Version First Reported In: unspecified
Platform: Other Linux
: NOR major
Target Milestone: ---
Assignee: David Edmundson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-04-28 22:06 UTC by unruh
Modified: 2022-04-25 22:42 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
journalctl from shutdown on system which eventually did shut down (21.58 KB, text/plain)
2017-04-28 22:28 UTC, unruh
Details
journalctl from a case where I had to hit the power switch on the laptop (9.15 KB, text/plain)
2017-04-28 22:29 UTC, unruh
Details

Note You need to log in before you can comment on or make changes to this bug.
Description unruh 2017-04-28 22:06:38 UTC
I am running sddm and on shutdown (no splash screen) sddm  restarts sddm-helper and the logon screen reappears. Sometimes it disappears about 5 sec later and the shutdown completes, while in other cases it stays up forever (minutes) and I have have to shutdown while pushing the power switch. 
When it displays the logon screen, I can enter the username and password (but nothing happens, or push the various buttons (shutdown, login,...) but nothing happens. 

Note I have no idea if this is the right place to report this (it is not really a systemsettings problem) , but while there is a kdm product in the list, there is no sddm product.
Comment 1 unruh 2017-04-28 22:28:14 UTC
Created attachment 105247 [details]
journalctl from shutdown on system which eventually did shut down

This is the journalctl output from a time when the system did finally shut down
Note that The X server on :0 is shut down, but then sddm restarts the X server on vt1 and restarts the sddm-greeter Why is it doing this on a shutdown?
Comment 2 unruh 2017-04-28 22:29:42 UTC
Created attachment 105248 [details]
journalctl from a case where I had to hit the power switch on the laptop

This was a case where the greeter came up and never went down for at least a minute. I had to shutdown by hitting the power switch.
Not good.
Comment 3 ralph 2017-06-02 13:36:35 UTC
This disastrous Plasma5 5.10 stable update has totally messed up my computer; 5.10 Release Candidate worked perfectly.
As well as for many other users, at the end of the update this message has appeared:

https://forums.opensuse.org/showthread.php/525168-It-blocks-the-PC

After restarting the computer, sddm (or sddm-greeter) has crashed (SIGINT).
Here I have posted some backtrace:

https://forums.opensuse.org/showthread.php/525135-Black-screen-after-a-huge-update-to-Plasma-5-10-and-libQt-5-9

For example:

/var/log/sddm.log

..
[04:31:52.688] (II) DAEMON: Removing display ":0" ...
[04:31:52.688] (II) DAEMON: Adding new display on vt 7 ...
[04:31:52.688] (II) DAEMON: Display server starting...
[04:31:52.689] (II) DAEMON: Running: /usr/bin/X -nolisten tcp -auth /run/sddm/{36398a0e-9966-44e9-b254-89d1913fda75} -background none -noreset -displayfd 19 vt7
[04:31:53.611] (II) DAEMON: Setting default cursor
[04:31:53.631] (II) DAEMON: Running display setup script  "/etc/X11/xdm/Xsetup"
[04:31:53.748] (II) DAEMON: Display server started.
[04:31:53.749] (II) DAEMON: Socket server starting...
[04:31:53.749] (II) DAEMON: Socket server started.
[04:31:53.749] (II) DAEMON: Greeter starting...
[04:31:53.750] (II) DAEMON: Adding cookie to "/run/sddm/{36398a0e-9966-44e9-b254-89d1913fda75}"
[04:31:53.815] (II) DAEMON: Greeter session started successfully
[04:31:54.036] (II) DAEMON: Message received from greeter: Connect
[04:31:56.363] (WW) DAEMON: Auth: sddm-helper exited with 11
[04:31:56.363] (II) DAEMON: Greeter stopped.
[04:32:02.588] (WW) DAEMON: Signal received: SIGINT
[04:32:02.589] (II) DAEMON: Socket server stopping...
[04:32:02.589] (II) DAEMON: Socket server stopped.
[04:32:02.589] (II) DAEMON: Display server stopping...
[04:32:02.631] (II) DAEMON: Display server stopped.
[04:32:02.631] (II) DAEMON: Running display stop script  "/usr/share/sddm/scripts/Xstop"

sddm-greeter --test-mode

[21:44:36.633] (WW) GREETER: QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-ralph'
[21:44:36.661] (II) GREETER: Reading from "/usr/share/xsessions/default.desktop"
[21:44:36.661] (II) GREETER: Reading from "/usr/share/xsessions/gnome-classic.desktop"
[21:44:36.662] (II) GREETER: Reading from "/usr/share/xsessions/gnome.desktop"
[21:44:36.662] (II) GREETER: Reading from "/usr/share/xsessions/icewm-session.desktop"
[21:44:36.662] (II) GREETER: Reading from "/usr/share/xsessions/icewm.desktop"
[21:44:36.663] (II) GREETER: Reading from "/usr/share/xsessions/kde-plasma.desktop"
[21:44:36.663] (II) GREETER: Reading from "/usr/share/xsessions/plasma5.desktop"
[21:44:36.663] (II) GREETER: Reading from "/usr/share/xsessions/sle-classic.desktop"
[21:44:36.663] (II) GREETER: Reading from "/usr/share/xsessions/xsession.desktop"
[21:44:36.670] (EE) GREETER: Socket error:  "QLocalSocket::connectToServer: Invalid name"
[21:44:36.731] (WW) GREETER: file:///Main.qml: No such file or directory
Segmentation fault (core dumped)

gdb sddm-greeter

Starting program: /usr/bin/sddm-greeter 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[22:59:50.370] (WW) GREETER: QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-ralph'
[New Thread 0x7fffe8f7f700 (LWP 5293)]
[22:59:50.420] (II) GREETER: Reading from "/usr/share/xsessions/default.desktop"
[22:59:50.435] (II) GREETER: Reading from "/usr/share/xsessions/gnome-classic.desktop"
[22:59:50.444] (II) GREETER: Reading from "/usr/share/xsessions/gnome.desktop"
[22:59:50.451] (II) GREETER: Reading from "/usr/share/xsessions/icewm-session.desktop"
[22:59:50.461] (II) GREETER: Reading from "/usr/share/xsessions/icewm.desktop"
[22:59:50.462] (II) GREETER: Reading from "/usr/share/xsessions/kde-plasma.desktop"
[22:59:50.467] (II) GREETER: Reading from "/usr/share/xsessions/plasma5.desktop"
[22:59:50.467] (II) GREETER: Reading from "/usr/share/xsessions/sle-classic.desktop"
[22:59:50.471] (II) GREETER: Reading from "/usr/share/xsessions/xsession.desktop"
[22:59:50.524] (EE) GREETER: Socket error:  "QLocalSocket::connectToServer: Invalid name"
[22:59:50.525] (EE) GREETER: Cannot connect to the daemon - is it running?
[New Thread 0x7fffe318d700 (LWP 5294)]
[22:59:50.608] (WW) GREETER: file:///Main.qml: No such file or directory

Thread 1 "sddm-greeter" received signal SIGSEGV, Segmentation fault.
0x00007ffff7539ab5 in QQuickItem::setCursor(QCursor const&) ()
   from /usr/lib64/libQt5Quick.so.5

backtrace:

#0  0x00007ffff7539ab5 in QQuickItem::setCursor(QCursor const&) ()
   from /usr/lib64/libQt5Quick.so.5
#1  0x00000000004283ca in SDDM::GreeterApp::addViewForScreen(QScreen*) ()
#2  0x00000000004294e3 in SDDM::GreeterApp::GreeterApp(int&, char**) ()
#3  0x000000000041630d in main ()

I can run whatever Plasma5 application from IceWM and Gnome (through kdm or lightdm); sddm and gdm do not work.
Comment 4 ralph 2017-06-02 14:28:05 UTC
OK, there are important news about this bug; the culprit is "subpixel-hinting"!

I have disabled "subpixel-hinting" running systemsettings5 from IceWM and now Plasma 5.10 works properly!
Comment 5 Julia Martin 2021-01-23 13:37:59 UTC
If the bug is still present I suggest reporting it upstream to SDDM (https://github.com/sddm/sddm/issues)