[opensuse-factory] on tumbleed sddm does not start after update
after this weekend update I got into a non starting sddm. seems to be in a loop of crashing. relevant info from log at the end. confusing bit is that startx by hand and kde starts as expected. Anyone else seeing this? -- Logs begin at Mon 2018-03-26 12:26:01 BST, end at Mon 2018-03-26 12:30:53 BST. -- Mar 26 12:26:05 circassia systemd[1]: Starting X Display Manager... Mar 26 12:26:05 circassia display-manager[1625]: /usr/lib/X11/display-manager: line 144: type: console_vars: not found Mar 26 12:26:05 circassia display-manager[1625]: /usr/lib/X11/display-manager: line 144: type: default-displaymanager_vars: not found Mar 26 12:26:05 circassia display-manager[1625]: /etc/vconsole.conf available Mar 26 12:26:05 circassia display-manager[1625]: KEYMAP: gb Mar 26 12:26:05 circassia display-manager[1625]: Command: localectl set-keymap gb Mar 26 12:26:05 circassia display-manager[1625]: I: Using systemd /usr/share/systemd/kbd-model-map mapping Mar 26 12:26:05 circassia sddm[1764]: Initializing... Mar 26 12:26:05 circassia sddm[1764]: Logind interface found Mar 26 12:26:05 circassia sddm[1764]: Starting... Mar 26 12:26:05 circassia sddm[1764]: Adding new display on vt 7 ... Mar 26 12:26:05 circassia sddm[1764]: Loading theme configuration from "" Mar 26 12:26:05 circassia sddm[1764]: Display server starting... Mar 26 12:26:05 circassia sddm[1764]: Running: /usr/bin/X -nolisten-tcp -dpi 192 -auth /run/sddm/{25bb49b8-1e49-4583-8029-ceb297b20e07} -background none -noreset -displayfd 17 -seat seat0 vt7 Mar 26 12:26:05 circassia sddm[1764]: Setting default cursor Mar 26 12:26:05 circassia sddm[1764]: Running display setup script "/etc/X11/xdm/Xsetup" Mar 26 12:26:05 circassia sddm[1764]: Display server started. Mar 26 12:26:05 circassia sddm[1764]: Socket server starting... Mar 26 12:26:05 circassia sddm[1764]: Socket server started. Mar 26 12:26:05 circassia sddm[1764]: Loading theme configuration from "/usr/share/sddm/themes/breeze-openSUSE/theme.conf" Mar 26 12:26:05 circassia sddm[1764]: Greeter starting... Mar 26 12:26:05 circassia sddm[1764]: Adding cookie to "/run/sddm/{25bb49b8-1e49-4583-8029-ceb297b20e07}" Mar 26 12:26:05 circassia display-manager[1625]: Starting service sddm/usr/bin/xauth: (stdin):1: bad "remove" command line Mar 26 12:26:05 circassia display-manager[1625]: /usr/bin/xauth: (stdin):2: bad "add" command line Mar 26 12:26:05 circassia sddm[1764]: Display server stopped. Mar 26 12:26:05 circassia sddm[1764]: Running display stop script "/usr/share/sddm/scripts/Xstop" Mar 26 12:26:05 circassia sddm[1764]: Socket server stopping... Mar 26 12:26:05 circassia sddm[1764]: Socket server stopped. Mar 26 12:26:05 circassia sddm[1764]: Removing display "" ... Mar 26 12:26:05 circassia sddm[1764]: Adding new display on vt 7 ... Mar 26 12:26:05 circassia sddm[1764]: Loading theme configuration from "" Mar 26 12:26:05 circassia sddm[1764]: Display server starting... Mar 26 12:26:05 circassia sddm[1764]: Running: /usr/bin/X -nolisten-tcp -dpi 192 -auth /run/sddm/{ea029520-0a16-4aa8-aa6e-e902045f0c57} -background none -noreset -displayfd 19 -seat seat0 vt7 Mar 26 12:26:05 circassia sddm[1764]: Setting default cursor Mar 26 12:26:05 circassia sddm-helper[1832]: [PAM] Starting... Mar 26 12:26:05 circassia sddm-helper[1832]: [PAM] Authenticating... Mar 26 12:26:05 circassia sddm[1764]: Running display setup script "/etc/X11/xdm/Xsetup" Mar 26 12:26:05 circassia sddm-helper[1832]: [PAM] returning. Mar 26 12:26:05 circassia sddm[1764]: Display server started. Mar 26 12:26:05 circassia sddm[1764]: Socket server starting... Mar 26 12:26:05 circassia sddm[1764]: Socket server started. Mar 26 12:26:05 circassia sddm[1764]: Loading theme configuration from "/usr/share/sddm/themes/breeze-openSUSE/theme.conf" Mar 26 12:26:05 circassia sddm[1764]: Greeter starting... Mar 26 12:26:05 circassia sddm[1764]: Adding cookie to "/run/sddm/{ea029520-0a16-4aa8-aa6e-e902045f0c57}" Mar 26 12:26:05 circassia display-manager[1625]: /usr/bin/xauth: (stdin):1: bad "remove" command line --- Dr Alin Marin Elena http://alin.elena.space -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi,
after this weekend update I got into a non starting sddm. seems to be in a loop of crashing. relevant info from log at the end.
did you check your /etc/sddm.conf and /etc/pam.d/sddm files? At least mine were empty after one of the latest updates. [...]
-+- Dr Alin Marin Elena
Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
did you check your /etc/sddm.conf and /etc/pam.d/sddm files? first one yes... and seems to have some configs inside... second one right now and is not empty
cat /etc/sddm.conf [Autologin] Relogin=false User= [General] HaltCommand= RebootCommand= [Theme] CursorTheme=Breeze_Snow [Users] MaximumUid=65000 MinimumUid=1000 cat /etc/pam.d/sddm #%PAM-1.0 auth include common-auth account include common-account password include common-password session required pam_loginuid.so session include common-session
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
found it... just in case others hit it. hidipi section like this was the culprit [X11] ServerArguments=-nolisten tcp -dpi 192 anyhow seems hidpi is not supported by sddm. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi Alin,
found it... just in case others hit it.
great!
hidipi section like this was the culprit [X11] ServerArguments=-nolisten tcp -dpi 192
Where is ths section? sddm.conf? If so, I don't have it. But according to the man page for sddm.conf, there is an optione named EnableHIDPI=true. Perhaps this can help you? EnableHiDPI= Enables Qt's automatic HiDPI scaling. Can be either "true" or "false". Default value is "false".
anyhow seems hidpi is not supported by sddm.
Thx for the information. Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi, Am Dienstag, 27. März 2018, 00:36:09 CEST schrieb Alin Marin Elena:
found it... just in case others hit it. hidipi section like this was the culprit [X11] ServerArguments=-nolisten tcp -dpi 192
Note that this entry in sddm.conf was a no-op until now, as only [XDisplay] was read, not [X11]. Now both are read.
anyhow seems hidpi is not supported by sddm.
It is. Just add [XDisplay] EnableHiDPI=true and don't set ServerArguments. If your display has a broken EDID, setting -dpi manually is necessary, but that's normally not the case. Cheers, Fabian -- Fabian Vogt - Release Engineer SUSE Linux GmbH GF: Felix Imendörffer, Jane Smithard, Graham Norton; HRB 21284 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Fabian Vogt wrote:
anyhow seems hidpi is not supported by sddm.
It is. Just add
[XDisplay] EnableHiDPI=true
and don't set ServerArguments. If your display has a broken EDID, setting -dpi manually is necessary, but that's normally not the case.
Hmm, my sddm.conf is completely empty, and I do have two computers with +200dpi displays, but on both of them font sizes are fine for the login screen. So does it detect/activate it automatically (on well-behaved displays), or is there some other hidden switch? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (4)
-
Alin Marin Elena -
Fabian Vogt -
mh＠mike.franken.de -
Peter Suetterlin