You are not logged in.

#1 2016-01-17 17:11:04

mrunion
Member
From: Jonesborough, TN
Registered: 2007-01-26
Posts: 1,938
Website

[WORKAROUND] SDDM/Breeze Issue With qt5-* Package Upgrade

I updated my system yesterday and got new qt5-* packages that upgraded from 5.5.1-8 to 5.5.1-9.

After a reboot this morning, SDDM would appear, but fail to allow a login. After typing the password, SDDM would just restart. This would just repeat indefinitely.

I didn't find anything useful in the logs after reviewing them for 15-20 minutes. But I do have them saved off.

I use SDDM to start an OpenBox session, if that matters. I tested it to try and start KDE, but it didn't work as well.

I downgraded the qt5-* packages that upgraded yesteday and the problem cleared:

[2016-01-17 11:19] [ALPM] downgraded qt5-base (5.5.1-9 -> 5.5.1-8)
[2016-01-17 11:19] [ALPM] downgraded qt5-xmlpatterns (5.5.1-9 -> 5.5.1-8)
[2016-01-17 11:19] [ALPM] downgraded qt5-declarative (5.5.1-9 -> 5.5.1-8)
[2016-01-17 11:19] [ALPM] downgraded qt5-graphicaleffects (5.5.1-9 -> 5.5.1-8)
[2016-01-17 11:19] [ALPM] downgraded qt5-script (5.5.1-9 -> 5.5.1-8)
[2016-01-17 11:19] [ALPM] downgraded qt5-x11extras (5.5.1-9 -> 5.5.1-8)
[2016-01-17 11:19] [ALPM] downgraded qt5-svg (5.5.1-9 -> 5.5.1-8)
[2016-01-17 11:19] [ALPM] downgraded qt5-location (5.5.1-9 -> 5.5.1-8)
[2016-01-17 11:19] [ALPM] downgraded qt5-sensors (5.5.1-9 -> 5.5.1-8)
[2016-01-17 11:19] [ALPM] downgraded qt5-webchannel (5.5.1-9 -> 5.5.1-8)
[2016-01-17 11:19] [ALPM] downgraded qt5-webkit (5.5.1-9 -> 5.5.1-8)
[2016-01-17 11:19] [ALPM] downgraded qt5-translations (5.5.1-9 -> 5.5.1-8)
[2016-01-17 11:19] [ALPM] downgraded qt5-tools (5.5.1-9 -> 5.5.1-8)
[2016-01-17 11:19] [ALPM] downgraded qt5-quickcontrols (5.5.1-9 -> 5.5.1-8)
[2016-01-17 11:19] [ALPM] downgraded qt5-multimedia (5.5.1-9 -> 5.5.1-8)
[2016-01-17 11:19] [ALPM] downgraded plasma-desktop (5.5.3-2 -> 5.5.3-1)
[2016-01-17 11:19] [ALPM] downgraded qt5-doc (5.5.1-9 -> 5.5.1-8)
[2016-01-17 11:19] [ALPM] downgraded qt5-imageformats (5.5.1-9 -> 5.5.1-8)
[2016-01-17 11:19] [ALPM] downgraded qt5-quick1 (5.5.1-9 -> 5.5.1-8)

Has anyone else experienced this?

Last edited by mrunion (2016-01-20 13:57:44)


Matt

"It is very difficult to educate the educated."

Offline

#2 2016-01-17 17:23:47

arojas
Developer
From: Spain
Registered: 2011-10-09
Posts: 1,639

Re: [WORKAROUND] SDDM/Breeze Issue With qt5-* Package Upgrade

Check journalctl /usr/bin/sddm (as root)

Offline

#3 2016-01-17 17:32:23

mrunion
Member
From: Jonesborough, TN
Registered: 2007-01-26
Posts: 1,938
Website

Re: [WORKAROUND] SDDM/Breeze Issue With qt5-* Package Upgrade

I still see no problems with what I'm looking at. Hopefully you can see something in here. (Occasionally I would switch to a new terminal and test logging in, but obviously, X was already running and the greeter didn't like that!)

Jan 17 08:45:28 rustyhump sddm[484]: Initializing...
Jan 17 08:45:28 rustyhump sddm[484]: Starting...
Jan 17 08:45:28 rustyhump sddm[484]: Adding new display on vt 1 ...
Jan 17 08:45:28 rustyhump sddm[484]: Display server starting...
Jan 17 08:45:28 rustyhump sddm[484]: Running: /usr/bin/X -nolisten tcp -auth /var/run/sddm/{e472e308-8a3f-4b84-a38a-92a7e9410655} -background none -noreset -displayfd 17 vt1
Jan 17 08:45:31 rustyhump sddm[484]: Running display setup script  "/usr/share/sddm/scripts/Xsetup"
Jan 17 08:45:31 rustyhump sddm[484]: Display server started.
Jan 17 08:45:31 rustyhump sddm[484]: Socket server starting...
Jan 17 08:45:31 rustyhump sddm[484]: Socket server started.
Jan 17 08:45:31 rustyhump sddm[484]: Greeter starting...
Jan 17 08:45:31 rustyhump sddm[484]: Adding cookie to "/var/run/sddm/{e472e308-8a3f-4b84-a38a-92a7e9410655}"
Jan 17 08:45:31 rustyhump sddm[484]: Greeter session started successfully
Jan 17 08:45:32 rustyhump sddm[484]: Message received from greeter: Connect
Jan 17 10:44:43 rustyhump sddm[484]: Message received from greeter: Login
Jan 17 10:44:43 rustyhump sddm[484]: Reading from "/usr/share/xsessions/openbox.desktop"
Jan 17 10:44:43 rustyhump sddm[484]: Session "/usr/share/xsessions/openbox.desktop" selected, command: "/usr/bin/openbox-session"
Jan 17 10:44:43 rustyhump sddm[484]: Authenticated successfully
Jan 17 10:44:43 rustyhump sddm[484]: Session started
Jan 17 10:44:44 rustyhump sddm[484]: Display server stopped.
Jan 17 10:44:44 rustyhump sddm[484]: Running display stop script  "/usr/share/sddm/scripts/Xstop"
Jan 17 10:44:44 rustyhump sddm[484]: Greeter stopping...
Jan 17 10:44:44 rustyhump sddm[484]: Socket server stopping...
Jan 17 10:44:44 rustyhump sddm[484]: Socket server stopped.
Jan 17 10:44:44 rustyhump sddm[484]: Removing display ":0" ...
Jan 17 10:44:44 rustyhump sddm[484]: Adding new display on vt 1 ...
Jan 17 10:44:44 rustyhump sddm[484]: Display server starting...
Jan 17 10:44:44 rustyhump sddm[484]: Running: /usr/bin/X -nolisten tcp -auth /var/run/sddm/{42f07a47-bf30-489a-bc16-04e07c2bdf74} -background none -noreset -displayfd 22 vt1
Jan 17 10:44:44 rustyhump sddm[484]: Running display setup script  "/usr/share/sddm/scripts/Xsetup"
Jan 17 10:44:44 rustyhump sddm[484]: Display server started.
Jan 17 10:44:44 rustyhump sddm[484]: Socket server starting...
Jan 17 10:44:44 rustyhump sddm[484]: Socket server started.
Jan 17 10:44:44 rustyhump sddm[484]: Greeter starting...
Jan 17 10:44:44 rustyhump sddm[484]: Adding cookie to "/var/run/sddm/{42f07a47-bf30-489a-bc16-04e07c2bdf74}"
Jan 17 10:44:44 rustyhump sddm[484]: QProcess: Destroyed while process ("/usr/lib/sddm/sddm-helper") is still running.
Jan 17 10:44:44 rustyhump sddm[484]: Greeter stopping...
Jan 17 10:44:44 rustyhump sddm[484]: QProcess: Destroyed while process ("/usr/lib/sddm/sddm-helper") is still running.
Jan 17 10:44:44 rustyhump sddm[484]: Greeter session started successfully
Jan 17 10:44:44 rustyhump sddm[484]: Message received from greeter: Connect
Jan 17 10:44:49 rustyhump sddm[484]: Message received from greeter: Login
Jan 17 10:44:49 rustyhump sddm[484]: Reading from "/usr/share/xsessions/openbox.desktop"
Jan 17 10:44:49 rustyhump sddm[484]: Session "/usr/share/xsessions/openbox.desktop" selected, command: "/usr/bin/openbox-session"
Jan 17 10:44:49 rustyhump sddm[484]: Authenticated successfully
Jan 17 10:44:49 rustyhump sddm[484]: Session started
Jan 17 10:44:50 rustyhump sddm[484]: Display server stopped.
Jan 17 10:44:50 rustyhump sddm[484]: Running display stop script  "/usr/share/sddm/scripts/Xstop"
Jan 17 10:44:50 rustyhump sddm[484]: Greeter stopping...
Jan 17 10:44:50 rustyhump sddm[484]: Socket server stopping...
Jan 17 10:44:50 rustyhump sddm[484]: Socket server stopped.
Jan 17 10:44:50 rustyhump sddm[484]: Removing display ":0" ...
Jan 17 10:44:50 rustyhump sddm[484]: Adding new display on vt 1 ...
Jan 17 10:44:50 rustyhump sddm[484]: Display server starting...
Jan 17 10:44:50 rustyhump sddm[484]: Running: /usr/bin/X -nolisten tcp -auth /var/run/sddm/{e78af3ec-0a2c-4c4d-b031-ca5b801c6790} -background none -noreset -displayfd 21 vt1
Jan 17 10:44:50 rustyhump sddm[484]: Running display setup script  "/usr/share/sddm/scripts/Xsetup"
Jan 17 10:44:50 rustyhump sddm[484]: Display server started.
Jan 17 10:44:50 rustyhump sddm[484]: Socket server starting...
Jan 17 10:44:50 rustyhump sddm[484]: Socket server started.
Jan 17 10:44:50 rustyhump sddm[484]: Greeter starting...
Jan 17 10:44:50 rustyhump sddm[484]: Adding cookie to "/var/run/sddm/{e78af3ec-0a2c-4c4d-b031-ca5b801c6790}"
Jan 17 10:44:50 rustyhump sddm[484]: QProcess: Destroyed while process ("/usr/lib/sddm/sddm-helper") is still running.
Jan 17 10:44:50 rustyhump sddm[484]: Greeter stopping...
Jan 17 10:44:50 rustyhump sddm[484]: QProcess: Destroyed while process ("/usr/lib/sddm/sddm-helper") is still running.
Jan 17 10:44:50 rustyhump sddm[484]: Greeter session started successfully
Jan 17 10:44:50 rustyhump sddm[484]: Message received from greeter: Connect
Jan 17 10:44:54 rustyhump sddm[484]: Message received from greeter: Login
Jan 17 10:44:54 rustyhump sddm[484]: Reading from "/usr/share/xsessions/openbox.desktop"
Jan 17 10:44:54 rustyhump sddm[484]: Session "/usr/share/xsessions/openbox.desktop" selected, command: "/usr/bin/openbox-session"
Jan 17 10:44:54 rustyhump sddm[484]: Authenticated successfully
Jan 17 10:44:54 rustyhump sddm[484]: Auth: sddm-helper exited successfully
Jan 17 10:44:54 rustyhump sddm[484]: Greeter stopped.
Jan 17 10:44:54 rustyhump sddm[484]: Session started
Jan 17 10:44:54 rustyhump sddm[484]: Auth: sddm-helper exited with 1
Jan 17 10:44:54 rustyhump sddm[484]: Display server stopped.
Jan 17 10:44:54 rustyhump sddm[484]: Running display stop script  "/usr/share/sddm/scripts/Xstop"
Jan 17 10:44:54 rustyhump sddm[484]: Socket server stopping...
Jan 17 10:44:54 rustyhump sddm[484]: Socket server stopped.
Jan 17 10:44:54 rustyhump sddm[484]: Removing display ":0" ...
Jan 17 10:44:54 rustyhump sddm[484]: Adding new display on vt 1 ...
Jan 17 10:44:54 rustyhump sddm[484]: Display server starting...
Jan 17 10:44:54 rustyhump sddm[484]: Running: /usr/bin/X -nolisten tcp -auth /var/run/sddm/{5b829b6b-24ff-45dd-86b4-c92255d5333a} -background none -noreset -displayfd 17 vt1
Jan 17 10:44:54 rustyhump sddm[484]: Running display setup script  "/usr/share/sddm/scripts/Xsetup"
Jan 17 10:44:54 rustyhump sddm[484]: Display server started.
Jan 17 10:44:54 rustyhump sddm[484]: Socket server starting...
Jan 17 10:44:54 rustyhump sddm[484]: Socket server started.
Jan 17 10:44:54 rustyhump sddm[484]: Greeter starting...
Jan 17 10:44:54 rustyhump sddm[484]: Adding cookie to "/var/run/sddm/{5b829b6b-24ff-45dd-86b4-c92255d5333a}"
Jan 17 10:44:54 rustyhump sddm[484]: Greeter session started successfully
Jan 17 10:44:54 rustyhump sddm[484]: Message received from greeter: Connect
Jan 17 10:45:00 rustyhump sddm[484]: Message received from greeter: Reboot
Jan 17 10:45:01 rustyhump sddm[484]: Signal received: SIGTERM
Jan 17 10:45:01 rustyhump sddm[484]: Greeter stopping...
Jan 17 10:45:01 rustyhump sddm[484]: Socket server stopping...
Jan 17 10:45:01 rustyhump sddm[484]: Socket server stopped.
Jan 17 10:45:01 rustyhump sddm[484]: Display server stopping...
Jan 17 10:45:01 rustyhump sddm[484]: Display server stopped.
Jan 17 10:45:01 rustyhump sddm[484]: Running display stop script  "/usr/share/sddm/scripts/Xstop"
Jan 17 10:45:01 rustyhump sddm[484]: Greeter stopping...
Jan 17 10:45:01 rustyhump sddm[484]: QProcess: Destroyed while process ("/usr/lib/sddm/sddm-helper") is still running.
Jan 17 10:45:23 rustyhump sddm[480]: Initializing...
Jan 17 10:45:23 rustyhump sddm[480]: Starting...
Jan 17 10:45:23 rustyhump sddm[480]: Adding new display on vt 1 ...
Jan 17 10:45:23 rustyhump sddm[480]: Display server starting...
Jan 17 10:45:23 rustyhump sddm[480]: Running: /usr/bin/X -nolisten tcp -auth /var/run/sddm/{82c8d90e-baa9-42e7-a161-c5c308a20252} -background none -noreset -displayfd 17 vt1
Jan 17 10:45:25 rustyhump sddm[480]: Running display setup script  "/usr/share/sddm/scripts/Xsetup"
Jan 17 10:45:25 rustyhump sddm[480]: Display server started.
Jan 17 10:45:25 rustyhump sddm[480]: Socket server starting...
Jan 17 10:45:25 rustyhump sddm[480]: Socket server started.
Jan 17 10:45:25 rustyhump sddm[480]: Greeter starting...
Jan 17 10:45:25 rustyhump sddm[480]: Adding cookie to "/var/run/sddm/{82c8d90e-baa9-42e7-a161-c5c308a20252}"
Jan 17 10:45:25 rustyhump sddm[480]: Greeter session started successfully
Jan 17 10:45:26 rustyhump sddm[480]: Message received from greeter: Connect
Jan 17 10:46:34 rustyhump sddm[480]: Message received from greeter: Login
Jan 17 10:46:34 rustyhump sddm[480]: Reading from "/usr/share/xsessions/openbox.desktop"
Jan 17 10:46:34 rustyhump sddm[480]: Session "/usr/share/xsessions/openbox.desktop" selected, command: "/usr/bin/openbox-session"
Jan 17 10:46:34 rustyhump sddm[480]: Authenticated successfully
Jan 17 10:46:34 rustyhump sddm[480]: Session started
Jan 17 10:46:34 rustyhump sddm[480]: Display server stopped.
Jan 17 10:46:34 rustyhump sddm[480]: Running display stop script  "/usr/share/sddm/scripts/Xstop"
Jan 17 10:46:35 rustyhump sddm[480]: Greeter stopping...
Jan 17 10:46:35 rustyhump sddm[480]: Socket server stopping...
Jan 17 10:46:35 rustyhump sddm[480]: Socket server stopped.
Jan 17 10:46:35 rustyhump sddm[480]: Removing display ":0" ...
Jan 17 10:46:35 rustyhump sddm[480]: Adding new display on vt 1 ...
Jan 17 10:46:35 rustyhump sddm[480]: Display server starting...
Jan 17 10:46:35 rustyhump sddm[480]: Running: /usr/bin/X -nolisten tcp -auth /var/run/sddm/{4e0d3aa7-197e-48bf-a913-2691e9fed072} -background none -noreset -displayfd 22 vt1
Jan 17 10:46:35 rustyhump sddm[480]: Running display setup script  "/usr/share/sddm/scripts/Xsetup"
Jan 17 10:46:35 rustyhump sddm[480]: Display server started.
Jan 17 10:46:35 rustyhump sddm[480]: Socket server starting...
Jan 17 10:46:35 rustyhump sddm[480]: Socket server started.
Jan 17 10:46:35 rustyhump sddm[480]: Greeter starting...
Jan 17 10:46:35 rustyhump sddm[480]: Adding cookie to "/var/run/sddm/{4e0d3aa7-197e-48bf-a913-2691e9fed072}"
Jan 17 10:46:35 rustyhump sddm[480]: QProcess: Destroyed while process ("/usr/lib/sddm/sddm-helper") is still running.
Jan 17 10:46:35 rustyhump sddm[480]: Greeter stopping...
Jan 17 10:46:35 rustyhump sddm[480]: QProcess: Destroyed while process ("/usr/lib/sddm/sddm-helper") is still running.
Jan 17 10:46:35 rustyhump sddm[480]: Greeter session started successfully
Jan 17 10:46:35 rustyhump sddm[480]: Message received from greeter: Connect
Jan 17 10:48:28 rustyhump sddm[480]: Message received from greeter: Login
Jan 17 10:48:28 rustyhump sddm[480]: Reading from "/usr/share/xsessions/openbox.desktop"
Jan 17 10:48:28 rustyhump sddm[480]: Session "/usr/share/xsessions/openbox.desktop" selected, command: "/usr/bin/openbox-session"
Jan 17 10:48:28 rustyhump sddm[480]: Authenticated successfully
Jan 17 10:48:28 rustyhump sddm[480]: Session started
Jan 17 10:48:28 rustyhump sddm[480]: Auth: sddm-helper exited with 1
Jan 17 10:48:28 rustyhump sddm[480]: Auth: sddm-helper exited successfully
Jan 17 10:48:28 rustyhump sddm[480]: Greeter stopped.
Jan 17 10:48:28 rustyhump sddm[480]: Display server stopped.
Jan 17 10:48:28 rustyhump sddm[480]: Running display stop script  "/usr/share/sddm/scripts/Xstop"
Jan 17 10:48:28 rustyhump sddm[480]: Socket server stopping...
Jan 17 10:48:28 rustyhump sddm[480]: Socket server stopped.
Jan 17 10:48:28 rustyhump sddm[480]: Removing display ":0" ...
Jan 17 10:48:28 rustyhump sddm[480]: Adding new display on vt 1 ...
Jan 17 10:48:28 rustyhump sddm[480]: Display server starting...
Jan 17 10:48:28 rustyhump sddm[480]: Running: /usr/bin/X -nolisten tcp -auth /var/run/sddm/{4273b339-567e-4956-958c-97a64ba6938f} -background none -noreset -displayfd 17 vt1
Jan 17 10:48:28 rustyhump sddm[480]: Running display setup script  "/usr/share/sddm/scripts/Xsetup"
Jan 17 10:48:28 rustyhump sddm[480]: Display server started.
Jan 17 10:48:28 rustyhump sddm[480]: Socket server starting...
Jan 17 10:48:28 rustyhump sddm[480]: Socket server started.
Jan 17 10:48:28 rustyhump sddm[480]: Greeter starting...
Jan 17 10:48:28 rustyhump sddm[480]: Adding cookie to "/var/run/sddm/{4273b339-567e-4956-958c-97a64ba6938f}"
Jan 17 10:48:28 rustyhump sddm[480]: Greeter session started successfully
Jan 17 10:48:28 rustyhump sddm[480]: Message received from greeter: Connect
Jan 17 10:48:35 rustyhump sddm[480]: Message received from greeter: Reboot
Jan 17 10:48:35 rustyhump sddm[480]: Error from greeter session: "Process crashed"
Jan 17 10:48:35 rustyhump sddm[480]: Auth: sddm-helper crashed (exit code 15)
Jan 17 10:48:35 rustyhump sddm[480]: Error from greeter session: "Process crashed"
Jan 17 10:48:35 rustyhump sddm[480]: Auth: sddm-helper exited with 15
Jan 17 10:48:35 rustyhump sddm[480]: Greeter stopped.
Jan 17 10:48:35 rustyhump sddm[480]: Signal received: SIGTERM
Jan 17 10:48:35 rustyhump sddm[480]: Socket server stopping...
Jan 17 10:48:35 rustyhump sddm[480]: Socket server stopped.
Jan 17 10:48:35 rustyhump sddm[480]: Display server stopping...
Jan 17 10:48:35 rustyhump sddm[480]: Display server stopped.
Jan 17 10:48:35 rustyhump sddm[480]: Running display stop script  "/usr/share/sddm/scripts/Xstop"

Matt

"It is very difficult to educate the educated."

Offline

#4 2016-01-17 17:47:26

arojas
Developer
From: Spain
Registered: 2011-10-09
Posts: 1,639

Re: [WORKAROUND] SDDM/Breeze Issue With qt5-* Package Upgrade

OK so it's not sddm. Check the full journal output from 10:44:43 to 10:44:44 to see what's killing your session

Offline

#5 2016-01-17 19:11:56

cappuccino
Member
Registered: 2012-12-26
Posts: 83

Re: [WORKAROUND] SDDM/Breeze Issue With qt5-* Package Upgrade

mrunion wrote:

Has anyone else experienced this?

Yep, similar problem here:

sddm[535]: Initializing...
sddm[535]: Starting...
sddm[535]: Adding new display on vt 1 ...
sddm[535]: Display server starting...
sddm[535]: Running: /usr/bin/X -nolisten tcp -auth /var/run/sddm/{6e4bb035-caff-4fcf-98b8-d196116b929b} -background none -noreset -displayfd 17 vt1
sddm[535]: Running display setup script  "/usr/share/sddm/scripts/Xsetup"
sddm[535]: Display server started.
sddm[535]: Socket server starting...
sddm[535]: Socket server started.
sddm[535]: Greeter starting...
sddm[535]: Adding cookie to "/var/run/sddm/{6e4bb035-caff-4fcf-98b8-d196116b929b}"
sddm[535]: Greeter session started successfully
sddm[535]: Message received from greeter: Connect
sddm[535]: Message received from greeter: Login
sddm[535]: Reading from "/usr/share/xsessions/plasma.desktop"
sddm[535]: Session "/usr/share/xsessions/plasma.desktop" selected, command: "/usr/bin/startkde"
sddm[535]: Authenticated successfully
sddm[535]: Auth: sddm-helper exited successfully
sddm[535]: Greeter stopped.
sddm[535]: Session started
sddm[535]: Authentication error: "Process crashed"
sddm[535]: Auth: sddm-helper crashed (exit code 15)
sddm[535]: Authentication error: "Process crashed"
sddm[535]: Auth: sddm-helper exited with 15
sddm[535]: Socket server stopping...
sddm[535]: Socket server stopped.
sddm[535]: Display server stopping...
sddm[535]: Display server stopped.
sddm[535]: Running display stop script  "/usr/share/sddm/scripts/Xstop"
sddm[535]: Removing display ":0" ...
sddm[535]: Adding new display on vt 1 ...
sddm[535]: Display server starting...
sddm[535]: Running: /usr/bin/X -nolisten tcp -auth /var/run/sddm/{2b4e237f-b274-4566-8550-81190fe2cd0b} -background none -noreset -displayfd 17 vt1
sddm[535]: Running display setup script  "/usr/share/sddm/scripts/Xsetup"
sddm[535]: Display server started.
sddm[535]: Socket server starting...
sddm[535]: Socket server started.
sddm[535]: Greeter starting...
sddm[535]: Adding cookie to "/var/run/sddm/{2b4e237f-b274-4566-8550-81190fe2cd0b}"
sddm[535]: Signal received: SIGTERM
sddm[535]: Socket server stopping...
sddm[535]: Socket server stopped.
sddm[535]: Display server stopping...

For successful login I must enter my password at least seven times. Downgrading sddm did not help.  I will try with downgrading qt5 packages.

My system:
Kernel: 4.3.3-2-ARCH x86_64
KDE Plasma 5.5.3
Graphics: Intel Mobile 4 Series Integrated Graphics Controller

Offline

#6 2016-01-17 19:47:14

lesto
Member
Registered: 2010-07-13
Posts: 115

Re: [WORKAROUND] SDDM/Breeze Issue With qt5-* Package Upgrade

same here, i needed 3 try to login, first one failed without any visible error in log, seems like wgen SDDM closes the greater, systemd start to close the session:

Jan 17 20:21:47 yyy systemd-logind[384]: New session c4 of user xxx.
Jan 17 20:21:47 yyy systemd[1]: Started Session c4 of user xxx.
Jan 17 20:21:47 yyy sddm-helper[590]: pam_kwallet5(sddm:session): pam_kwallet5: pam_sm_open_session
Jan 17 20:21:47 yyy sddm-helper[590]: pam_kwallet5(sddm:session): pam_kwallet5: final socket path: /tmp/kwallet5_xxx.socket
Jan 17 20:21:47 yyy sddm-helper[590]: pam_kwallet(sddm:session): pam_kwallet: pam_sm_open_session
Jan 17 20:21:47 yyy sddm-helper[590]: pam_kwallet(sddm:session): pam_kwallet: final socket path: /tmp/kwallet_xxx.socket
Jan 17 20:21:47 yyy sddm-helper[590]: pam_kwallet(sddm:session): pam_kwallet: Impossible to write walletKey to walletPipe
Jan 17 20:21:47 yyy sddm-helper[590]: Starting: "/usr/share/sddm/scripts/Xsession" "/usr/bin/startkde"
Jan 17 20:21:47 yyy sddm-helper[595]: Adding cookie to "/home/xxx/.Xauthority"
Jan 17 20:21:47 yyy sddm-helper[575]: [PAM] Ended.
Jan 17 20:21:47 yyy sddm[428]: Auth: sddm-helper exited successfully
Jan 17 20:21:47 yyy sddm[428]: Greeter stopped.
Jan 17 20:21:47 yyy sddm[428]: Session started
Jan 17 20:21:47 yyy systemd-logind[384]: Removed session c3.
Jan 17 20:21:47 yyy systemd[1]: Stopping User Manager for UID 998...

do you also use PAM with kwallet?

Last edited by lesto (2016-01-17 19:49:27)

Offline

#7 2016-01-17 21:12:47

mrunion
Member
From: Jonesborough, TN
Registered: 2007-01-26
Posts: 1,938
Website

Re: [WORKAROUND] SDDM/Breeze Issue With qt5-* Package Upgrade

@lesto: If you are asking me, then no. I use OpenBox. But I did try to boot KDE with no success either.

I can still find no errors in the log. But downgrading the packages that updated from 5.5.1-8 to 5.5.1-9 fixed the issue for me. SDDM was not one of th packages that changed. (I reinstalled it to be sure, but it had no affect.)

I think the issue is with the new qt5-* packages somewhere, but I haven't found the problem yet.


Matt

"It is very difficult to educate the educated."

Offline

#8 2016-01-17 21:29:27

zersaa
Member
From: Pskov, Russia
Registered: 2009-02-09
Posts: 28

Re: [WORKAROUND] SDDM/Breeze Issue With qt5-* Package Upgrade

I encountered this problem on desktop and notebook, both with intel graphics.

vdemin@t510 ~ % coredumpctl list sddm-greeter
TIME                            PID   UID   GID SIG PRESENT EXE
Вс 2016-01-17 10:13:50 MSK    858   990   990  11   /usr/bin/sddm-greeter
Вс 2016-01-17 10:29:46 MSK   2916   990   990   6   /usr/bin/sddm-greeter
Вс 2016-01-17 18:38:33 MSK    673   990   990  11   /usr/bin/sddm-greeter
vdemin@t510 ~ % coredumpctl info 673         
           PID: 673 (sddm-greeter)
           UID: 990 (sddm)
           GID: 990 (sddm)
        Signal: 11 (SEGV)
     Timestamp: Вс 2016-01-17 18:38:31 MSK (5h 53min ago)
  Command Line: /usr/bin/sddm-greeter --socket /tmp/sddm-:0-rxHzeE --theme /usr/share/sddm/themes/breeze
    Executable: /usr/bin/sddm-greeter
 Control Group: /user.slice/user-990.slice/session-c1.scope
          Unit: session-c1.scope
         Slice: user-990.slice
       Session: c1
     Owner UID: 990 (sddm)
       Boot ID: 7f36ad9b703d4d238ee0732bd5d85a21
    Machine ID: c91b643cce65e8444ef30b4600000b59
      Hostname: t510
       Message: Process 673 (sddm-greeter) of user 990 dumped core.
                
                Stack trace of thread 673:
                #0  0x00007f81a01c49bf n/a (libKF5CoreAddons.so.5)
                #1  0x00007f81a01c4e8f _ZN9KDirWatchD1Ev (libKF5CoreAddons.so.5)
                #2  0x00007f81a01c4ea9 n/a (libKF5CoreAddons.so.5)
                #3  0x00007f81b41e7f88 __run_exit_handlers (libc.so.6)
                #4  0x00007f81b41e7fd5 exit (libc.so.6)
                #5  0x00007f81ae2e06f5 _XDefaultIOError (libX11.so.6)
                #6  0x00007f81ab602c5e n/a (libQt5XcbQpa.so.5)
                #7  0x00007f81ae2e091e _XIOError (libX11.so.6)
                #8  0x00007f81ae2de9fb _XReply (libX11.so.6)
                #9  0x00007f81ae2da11d XSync (libX11.so.6)
                #10 0x00007f81b2037038 n/a (libGL.so.1)
                #11 0x00007f81b2037ed3 n/a (libGL.so.1)
                #12 0x00007f81b2011e19 n/a (libGL.so.1)
                #13 0x00007f81b64b1134 n/a (/usr/lib/qt/plugins/xcbglintegrations/libqxcb-glx-integration.so)
                #14 0x00007f81b64b1159 n/a (/usr/lib/qt/plugins/xcbglintegrations/libqxcb-glx-integration.so)
                #15 0x00007f81b564209d _ZN17QOffscreenSurface7destroyEv (libQt5Gui.so.5)
                #16 0x00007f81b5642121 _ZN17QOffscreenSurfaceD1Ev (libQt5Gui.so.5)
                #17 0x00007f81b5642159 _ZN17QOffscreenSurfaceD0Ev (libQt5Gui.so.5)
                #18 0x00007f81b5bf648c n/a (libQt5Quick.so.5)
                #19 0x00007f81b5bf6da1 _ZN13QSGRenderLoop7cleanupEv (libQt5Quick.so.5)
                #20 0x00007f81b4d73ad1 _Z21qt_call_post_routinesv (libQt5Core.so.5)
                #21 0x00007f81b4d743d2 _ZN16QCoreApplicationD1Ev (libQt5Core.so.5)
                #22 0x00000000004142d5 main (sddm-greeter)
                #23 0x00007f81b41d2610 __libc_start_main (libc.so.6)
                #24 0x00000000004143a9 _start (sddm-greeter)
                
                Stack trace of thread 676:
                #0  0x00007f81b429218d poll (libc.so.6)
                #1  0x00007f81b09befbc n/a (libglib-2.0.so.0)
                #2  0x00007f81b09bf0cc g_main_context_iteration (libglib-2.0.so.0)
                #3  0x00007f81b4dcb54f _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5)
                #4  0x00007f81b4d7257a _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5)
                #5  0x00007f81b4b8ebe4 _ZN7QThread4execEv (libQt5Core.so.5)
                #6  0x00007f81b53f3055 n/a (libQt5Qml.so.5)
                #7  0x00007f81b4b93b8e n/a (libQt5Core.so.5)
                #8  0x00007f81b29434a4 start_thread (libpthread.so.0)
                #9  0x00007f81b429b13d __clone (libc.so.6)

Last edited by zersaa (2016-01-17 21:33:52)

Offline

#9 2016-01-17 21:36:09

arojas
Developer
From: Spain
Registered: 2011-10-09
Posts: 1,639

Re: [WORKAROUND] SDDM/Breeze Issue With qt5-* Package Upgrade

mrunion wrote:

@lesto: If you are asking me, then no. I use OpenBox. But I did try to boot KDE with no success either.

I can still find no errors in the log. But downgrading the packages that updated from 5.5.1-8 to 5.5.1-9 fixed the issue for me. SDDM was not one of th packages that changed. (I reinstalled it to be sure, but it had no affect.)

I think the issue is with the new qt5-* packages somewhere, but I haven't found the problem yet.

Could you please test with 5.5.1-7?

Offline

#10 2016-01-17 21:46:15

zersaa
Member
From: Pskov, Russia
Registered: 2009-02-09
Posts: 28

Re: [WORKAROUND] SDDM/Breeze Issue With qt5-* Package Upgrade

The strange thing, but 5.5.1-7 is OK. Although I don't see any difference in PKGBUILD between 5.5.1-7 and 5.5.1-9.

Last edited by zersaa (2016-01-17 21:46:43)

Offline

#11 2016-01-17 22:30:23

lesto
Member
Registered: 2010-07-13
Posts: 115

Re: [WORKAROUND] SDDM/Breeze Issue With qt5-* Package Upgrade

arojas wrote:

Could you please test with 5.5.1-7?

Before update everything was fine*, and i run the update multiple times for day.

also tried to login with mainline kernel, same problem

* well, the left part of the monitor sometime was black vertical band, again a problem i was having from a couple of day, but I think it was coming from an update from plasma, but now is not there anymore.

Last edited by lesto (2016-01-17 22:32:37)

Offline

#12 2016-01-17 23:02:39

Cuke
Member
Registered: 2012-03-23
Posts: 2

Re: [WORKAROUND] SDDM/Breeze Issue With qt5-* Package Upgrade

i'm experiecing the same behaviour. this doesn't happen with different DE. I also noticed that if i remove the /etc/sddm.conf and reboot sddm load the default theme and with this one i can successfully login the first time. If i change it to the plasma theme with sddm-kcm and reboot i cannot login again.
Can someone confirm the same thing?

Offline

#13 2016-01-18 06:58:38

prash
Member
Registered: 2011-08-18
Posts: 57

Re: [WORKAROUND] SDDM/Breeze Issue With qt5-* Package Upgrade

I have this problem since yesterday too. I have LXQT (my default), KDE, i3, Enlightenment, and Gnome (since yesterday). The only WM that SDDM would let me login to was Gnome Wayland, but the mouse sprite would be invisible on any X client. For the time being, I use lightdm to login on LXQT.

Last edited by prash (2016-01-18 06:59:51)

Offline

#14 2016-01-18 08:14:29

Gosi
Member
From: Vienna, Austria
Registered: 2010-02-25
Posts: 51

Re: [WORKAROUND] SDDM/Breeze Issue With qt5-* Package Upgrade

I managed to login after switching the session from "plasma" to "plasma media center" and then back to "plasma" on the next login.

It seems to be solved only temporarily though, as the login problem reapears after reboot.

Last edited by Gosi (2016-01-18 08:16:32)

Offline

#15 2016-01-18 08:24:05

aatoma
Member
Registered: 2013-01-22
Posts: 29

Re: [WORKAROUND] SDDM/Breeze Issue With qt5-* Package Upgrade

Same situation here,

I'm on SDDM+Plasma and the symptom is

login attempt --> a few seconds of black screen --> sddm restarts

tried several times after the update with no result but didn't have time to rollback and see if this fixes the issue.

Offline

#16 2016-01-18 08:34:06

gotunandan
Member
Registered: 2012-01-30
Posts: 8

Re: [WORKAROUND] SDDM/Breeze Issue With qt5-* Package Upgrade

Apart from downgrading the qt5-* packages to 5.5.1-7, I had to downgrade xorg-server-common (1.18.0-4 -> 1.18.0-3) and xorg-server (1.18.0-4 -> 1.18.0-3)
Without the xorg-server downgrade, the issue still occurred.
Since I have auto login at bootup, I noticed the problem when unlocking the plasma session via sddm

I am not sure whether the problem is related to SDDM though. Seems that xorg dies, resulting in kactivities segfault.

P.S. I am using the i915 Intel driver (in case that helps)


~ Less is more ~

gotunandan

Offline

#17 2016-01-18 09:30:53

halogene
Member
Registered: 2013-05-29
Posts: 22

Re: [WORKAROUND] SDDM/Breeze Issue With qt5-* Package Upgrade

I can confirm this. My setup: i5-5200, auto-mount encrypted partition upon login via PAM, Breeze theme for sddm selected via sddm-kcm.

I can't log on to LXQT, Plasma, Gnome, Gnome classic and Openbox. I can log in to Gnome Wayland and Kodi. Plasma Mediacenter manages to show the loading sequence but will only generate a lot of system load and then fade to black and that's it.

To me this seems that something is wrong with loading X from sddm - though a standalone X session via startx worked and Xorg.0.log didn't show anything suspicious.

Offline

#18 2016-01-18 09:58:31

halogene
Member
Registered: 2013-05-29
Posts: 22

Re: [WORKAROUND] SDDM/Breeze Issue With qt5-* Package Upgrade

Interesting detail: I even can start plasma from console by doing "startx" (with the line  "exec startkde" in .xinitrc).

Another update: everything works normal on another machine that runs a dedicated nvidia GPU (also upgraded). The one that is refusing to let sddm start X runs on i915 integrated GPU.

Last edited by halogene (2016-01-18 10:08:42)

Offline

#19 2016-01-18 10:43:19

arojas
Developer
From: Spain
Registered: 2011-10-09
Posts: 1,639

Re: [WORKAROUND] SDDM/Breeze Issue With qt5-* Package Upgrade

Everybody: please remove *both* /var/lib/sddm/.cache and ~/.cache and see if it improves things.

Offline

#20 2016-01-18 11:09:39

bleach
Member
Registered: 2013-07-26
Posts: 264

Re: [WORKAROUND] SDDM/Breeze Issue With qt5-* Package Upgrade

it also works fine with AMD's R7 240 with open ati driver

Offline

#21 2016-01-18 11:11:54

halogene
Member
Registered: 2013-05-29
Posts: 22

Re: [WORKAROUND] SDDM/Breeze Issue With qt5-* Package Upgrade

I can confirn that cleaning the cache directories helped. Thank you!

Oh, and suddenly I can drag control panels again across multiple monitors o.O amazing.

Last edited by halogene (2016-01-18 11:14:53)

Offline

#22 2016-01-18 11:20:43

cappuccino
Member
Registered: 2012-12-26
Posts: 83

Re: [WORKAROUND] SDDM/Breeze Issue With qt5-* Package Upgrade

arojas wrote:

Everybody: please remove *both* /var/lib/sddm/.cache and ~/.cache and see if it improves things.

Unfortunately, not.

Offline

#23 2016-01-18 11:40:47

arbacle
Member
Registered: 2015-11-16
Posts: 19

Re: [WORKAROUND] SDDM/Breeze Issue With qt5-* Package Upgrade

Maybe my issue is related to this one.

After updating and restarting (for unrelated reasons), the login screen popped as normal, so I entered my password and then I was greeted with the boot console (tty1). I wasn't able to do anything - Ctrl+C, etc. Logging in at tty2 was also not possible - the computer was totally non-responsive.

After cold resetting I logged in tty2 before entering my password in SDDM - again tty1 showed up, but tty2 was accessible. I tried stopping sddm.service with no luck. The command ("systemctl stop sddm.service") was just hanging there, without any visible output or action (for about 2 min). Ctrl+C stopped this, but I got a message about Xorg being blocked for longer than 120 seconds.

I mucked around a bit, but at the end just disabled sddm.service. After rebooting, tty1 showed up with login prompt. I did the login, ran "startx" and my KDE started normally.

After downgrading my sddm-kcm package to 5.5.2-1, and enabling the service, everything was working again.

This is the log from the update that borked my system:

[2016-01-07 19:49] [ALPM] upgraded bluedevil (1:5.5.2-1 -> 1:5.5.3-1)
[2016-01-07 19:49] [ALPM] upgraded kdecoration (5.5.2-1 -> 5.5.3-1)
[2016-01-07 19:49] [ALPM] upgraded breeze (5.5.2-1 -> 5.5.3-1)
[2016-01-07 19:49] [ALPM] upgraded breeze-gtk (5.5.2-1 -> 5.5.3-1)
[2016-01-07 19:49] [ALPM] upgraded drkonqi (5.5.2-2 -> 5.5.3-1)
[2016-01-07 19:49] [ALPM] upgraded firefox (43.0.1-2 -> 43.0.4-1)
[2016-01-07 19:49] [ALPM] upgraded git (2.6.4-1 -> 2.7.0-1)
[2016-01-07 19:49] [ALPM] upgraded kde-cli-tools (5.5.2-1 -> 5.5.3-1)
[2016-01-07 19:49] [ALPM] upgraded kde-gtk-config (5.5.2-1 -> 5.5.3-1)
[2016-01-07 19:49] [ALPM] upgraded libksysguard (5.5.2-1 -> 5.5.3-1)
[2016-01-07 19:49] [ALPM] upgraded libkscreen (5.5.2-1 -> 5.5.3-1)
[2016-01-07 19:49] [ALPM] upgraded milou (5.5.2-1 -> 5.5.3-1)
[2016-01-07 19:49] [ALPM] upgraded kwayland (5.5.2-1 -> 5.5.3-1)
[2016-01-07 19:49] [ALPM] upgraded kscreenlocker (5.5.2-1 -> 5.5.3-1)
[2016-01-07 19:49] [ALPM] upgraded kwin (5.5.2-1 -> 5.5.3-1)
[2016-01-07 19:49] [ALPM] upgraded kuiserver (5.5.2-2 -> 5.5.3-1)
[2016-01-07 19:49] [ALPM] upgraded plasma-workspace (5.5.2-2 -> 5.5.3-1)
[2016-01-07 19:49] [ALPM] upgraded kdeplasma-addons (5.5.2-1 -> 5.5.3-1)
[2016-01-07 19:49] [ALPM] upgraded kgamma5 (5.5.2-1 -> 5.5.3-1)
[2016-01-07 19:49] [ALPM] upgraded khelpcenter (5.5.2-1 -> 5.5.3-1)
[2016-01-07 19:49] [ALPM] upgraded khotkeys (5.5.2-1 -> 5.5.3-1)
[2016-01-07 19:49] [ALPM] upgraded kinfocenter (5.5.2-1 -> 5.5.3-1)
[2016-01-07 19:49] [ALPM] upgraded kmenuedit (5.5.2-1 -> 5.5.3-1)
[2016-01-07 19:49] [ALPM] upgraded kscreen (5.5.2-1 -> 5.5.3-1)
[2016-01-07 19:49] [ALPM] upgraded ksshaskpass (5.5.2-2 -> 5.5.3-1)
[2016-01-07 19:49] [ALPM] upgraded ksysguard (5.5.2-1 -> 5.5.3-1)
[2016-01-07 19:49] [ALPM] upgraded kwallet-pam (5.5.2-1 -> 5.5.3-1)
[2016-01-07 19:49] [ALPM] upgraded kwayland-integration (5.5.2-1 -> 5.5.3-1)
[2016-01-07 19:49] [ALPM] upgraded kwrited (5.5.2-1 -> 5.5.3-1)
[2016-01-07 19:49] [ALPM] upgraded libbsd (0.8.0-1 -> 0.8.1-1)
[2016-01-07 19:49] [ALPM] upgraded oxygen (5.5.2-1 -> 5.5.3-1)
[2016-01-07 19:49] [ALPM] upgraded oxygen-cursors (5.5.2-1 -> 5.5.3-1)
[2016-01-07 19:49] [ALPM] upgraded powerdevil (5.5.2-1 -> 5.5.3-1)
[2016-01-07 19:49] [ALPM] upgraded polkit-kde-agent (5.5.2-1 -> 5.5.3-1)
[2016-01-07 19:49] [ALPM] upgraded systemsettings (5.5.2-1 -> 5.5.3-1)
[2016-01-07 19:49] [ALPM] upgraded plasma-desktop (5.5.2-1 -> 5.5.3-1)
[2016-01-07 19:49] [ALPM] upgraded plasma-mediacenter (5.5.2-1 -> 5.5.3-1)
[2016-01-07 19:49] [ALPM] upgraded plasma-nm (5.5.2-1 -> 5.5.3-1)
[2016-01-07 19:49] [ALPM] upgraded plasma-pa (5.5.2-1 -> 5.5.3-1)
[2016-01-07 19:49] [ALPM] upgraded plasma-sdk (5.5.2-1 -> 5.5.3-1)
[2016-01-07 19:49] [ALPM] upgraded plasma-workspace-wallpapers (5.5.2-1 -> 5.5.3-1)
[2016-01-07 19:49] [ALPM] upgraded sddm-kcm (5.5.2-1 -> 5.5.3-1)
[2016-01-07 19:49] [ALPM] upgraded user-manager (5.5.2-1 -> 5.5.3-1)

I was planning to write a post, but life got in the way. Anyway - from my experience, the problem seems rooted in sddm-kcm version 5.5.3-1. If I can give more information, please tell me what do you need.

P.S. There's a major update in the pipeline, but i'm hesitant to update right now, because the version of sddm-kcm in it is still 5.5.3-1.

Edit:
Here's the log from one of the attempts to login:

-- Reboot --
Jan 07 22:10:19 computer sddm[356]: Initializing...
Jan 07 22:10:19 computer sddm[356]: Starting...
Jan 07 22:10:19 computer sddm[356]: Adding new display on vt 1 ...
Jan 07 22:10:19 computer sddm[356]: Display server starting...
Jan 07 22:10:19 computer sddm[356]: Running: /usr/bin/X -nolisten tcp -auth /var/run/sddm/{cd2e08be-9580-41ab-8704-a9d3828cc8f4} -background none -noreset -displayfd 17 vt1
Jan 07 22:10:22 computer sddm[356]: Running display setup script  "/usr/share/sddm/scripts/Xsetup"
Jan 07 22:10:22 computer sddm[356]: Display server started.
Jan 07 22:10:22 computer sddm[356]: Socket server starting...
Jan 07 22:10:22 computer sddm[356]: Socket server started.
Jan 07 22:10:22 computer sddm[356]: Greeter starting...
Jan 07 22:10:22 computer sddm[356]: Adding cookie to "/var/run/sddm/{cd2e08be-9580-41ab-8704-a9d3828cc8f4}"
Jan 07 22:10:23 computer sddm[356]: Greeter session started successfully
Jan 07 22:10:24 computer sddm[356]: Message received from greeter: Connect
Jan 07 22:10:44 computer sddm[356]: Message received from greeter: Login
Jan 07 22:10:44 computer sddm[356]: Reading from "/usr/share/xsessions/plasma.desktop"
Jan 07 22:10:44 computer sddm[356]: Session "/usr/share/xsessions/plasma.desktop" selected, command: "/usr/bin/startkde"
Jan 07 22:10:45 computer sddm[356]: Authenticated successfully
Jan 07 22:10:45 computer sddm[356]: Auth: sddm-helper exited successfully
Jan 07 22:10:45 computer sddm[356]: Greeter stopped.
Jan 07 22:10:45 computer sddm[356]: Session started
Jan 07 22:10:45 computer sddm[356]: Auth: sddm-helper exited with 1
Jan 07 22:12:52 computer sddm[356]: Signal received: SIGTERM
Jan 07 22:12:52 computer sddm[356]: Socket server stopping...
Jan 07 22:12:52 computer sddm[356]: Socket server stopped.
Jan 07 22:12:52 computer sddm[356]: Display server stopping...
Jan 07 22:12:57 computer sddm[356]: Display server stopping...
Jan 07 22:13:02 computer sddm[356]: QProcess: Destroyed while process ("/usr/bin/X") is still running.
-- Reboot --

Last edited by arbacle (2016-01-18 11:48:01)

Offline

#24 2016-01-18 12:03:25

wroobel
Member
From: Poland
Registered: 2010-03-27
Posts: 8

Re: [WORKAROUND] SDDM/Breeze Issue With qt5-* Package Upgrade

cappuccino wrote:
arojas wrote:

Everybody: please remove *both* /var/lib/sddm/.cache and ~/.cache and see if it improves things.

Unfortunately, not.

Confirmed.


I had to downgrade qt5-base (from 5.5.1-9 to 5.5.1-8). Screen flickering again, but I can login at least.

Last edited by wroobel (2016-01-18 12:08:24)

Offline

#25 2016-01-18 12:08:23

lesto
Member
Registered: 2010-07-13
Posts: 115

Re: [WORKAROUND] SDDM/Breeze Issue With qt5-* Package Upgrade

please everybody notice this is a bit of random error, so getting it to work at first try ONE TIME has no meaning, you have to try at least a couple of times.

Also running i915

Offline

Board footer

Powered by FluxBB