Your message dated Thu, 26 May 2016 20:23:46 +0200 with message-id <20160526182346.GB2503@gnuservers.com.ar> and subject line Re: Bug#798906: sddm crashes on boot has caused the Debian Bug report #798906, regarding sddm crashes on boot to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 798906: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798906 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---Title: Konsole output
- To: submit@bugs.debian.org
- Subject: sddm crashes on boot
- From: Carlos Kosloff <ckosloff@hardwarealien.com>
- Date: Sun, 13 Sep 2015 18:34:57 -0400
- Message-id: <55F5FA11.5040203@hardwarealien.com>
Package: sddm
Version: 0.12.0-1
Severity: grave
-- System Information:
Debian Release: stretch/sid
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.1.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages sddm depends on:
ii adduser 3.113+nmu3
ii debconf [debconf-2.0] 1.5.57
ii libc6 2.19-19
ii libgcc1 1:5.2.1-16
ii libpam0g 1.1.8-3.1
ii libqt5core5a 5.4.2+dfsg-9
ii libqt5dbus5 5.4.2+dfsg-9
ii libqt5gui5 5.4.2+dfsg-9
ii libqt5network5 5.4.2+dfsg-9
ii libqt5qml5 5.4.2-6
ii libqt5quick5 5.4.2-6
ii libstdc++6 5.2.1-16
ii libsystemd0 225-1
ii libxcb-xkb1 1.10-3+b1
ii libxcb1 1.10-3+b1
ii qml-module-qtquick2 5.4.2-6
ii sddm-theme-breeze [sddm-theme] 4:5.3.2-4+b1
sddm recommends no packages.
Versions of packages sddm suggests:
pn pam-kwallet5 <none>
-- debconf information:
* shared/default-x-display-manager: sddm
sddm/daemon_name: /usr/bin/sddm
Dear maintainer,
I only removed leftovers of packages that had already been removed by a dist-upgrade.
After that, sddm would not give me a login prompt so I was unable to log into KDE the normal way.
I had to do 'systemctl stop sddm.service', as root.
Then 'startx startkde' as user to access the desktop, this bypassing sddm.
I checked the above mentioned packages and they are installed and the latest version in stretch.
In order to log into desktop the normal way I installed kdm and set is as default.
To help troubleshooting I will attach some traces I collected from error logs.
Sep 12 16:17:01 crosshair CRON[2632]: pam_unix(cron:session): session opened for user root by (uid=0)
Sep 12 16:17:01 crosshair CRON[2633]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Sep 12 16:17:01 crosshair CRON[2632]: pam_unix(cron:session): session closed for user root
Sep 12 16:19:54 crosshair acpid[852]: client 1105[0:0] has disconnected
Sep 12 16:19:59 crosshair login[1080]: pam_unix(login:auth): check pass; user unknown
Sep 12 16:19:59 crosshair login[1080]: pam_unix(login:auth): authentication failure; logname=LOGIN uid=0 euid=0 tty=/dev/tty1 ruser= rhost=
Sep 12 16:20:02 crosshair login[1080]: FAILED LOGIN (1) on '/dev/tty1' FOR 'UNKNOWN', Authentication failure
Sep 12 16:20:12 crosshair login[1080]: pam_unix(login:session): session opened for user ckosloff by LOGIN(uid=0)
Sep 12 16:20:12 crosshair systemd[1]: Created slice user-1000.slice.
Sep 12 16:20:12 crosshair systemd[1]: Starting User Manager for UID 1000...
Sep 12 16:20:12 crosshair systemd-logind[853]: New session 3 of user ckosloff.
Sep 12 16:20:12 crosshair systemd[1]: Started Session 3 of user ckosloff.
Sep 12 16:20:12 crosshair systemd[2762]: pam_unix(systemd-user:session): session opened for user ckosloff by (uid=0)
Sep 12 16:20:12 crosshair systemd[2762]: Reached target Paths.
Sep 12 16:20:12 crosshair systemd[2762]: Reached target Sockets.
Sep 12 16:20:12 crosshair systemd[2762]: Reached target Timers.
Sep 12 16:20:12 crosshair systemd[2762]: Reached target Basic System.
Sep 12 16:20:12 crosshair systemd[2762]: Reached target Default.
Sep 12 16:20:12 crosshair systemd[2762]: Startup finished in 9ms.
Sep 12 16:20:12 crosshair systemd[1]: Started User Manager for UID 1000.
Sep 12 16:20:24 crosshair su[2807]: pam_unix(su:auth): authentication failure; logname=ckosloff uid=1000 euid=0 tty=/dev/tty1 ruser=ckosloff rhost= user=root
Sep 12 16:20:26 crosshair su[2807]: pam_authenticate: Authentication failure
Sep 12 16:20:26 crosshair su[2807]: FAILED su for root by ckosloff
Sep 12 16:20:26 crosshair su[2807]: - /dev/tty1 ckosloff:root
Sep 12 16:20:35 crosshair su[2810]: Successful su for root by ckosloff
Sep 12 16:20:35 crosshair su[2810]: + /dev/tty1 ckosloff:root
Sep 12 16:20:35 crosshair su[2810]: pam_unix(su:session): session opened for user root by ckosloff(uid=1000)
Sep 12 16:20:35 crosshair su[2810]: pam_systemd(su:session): Cannot create session: Already running in a session
Sep 12 16:20:54 crosshair polkitd(authority=local)[998]: Registered Authentication Agent for unix-process:2817:43654 (system bus name :1.28 [/usr/bin/pkttyagent --notify-fd 5 --fallback], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
Sep 12 16:20:54 crosshair systemd[1]: Stopping Simple Desktop Display Manager...
Sep 12 16:20:54 crosshair sddm[1014]: Signal received: SIGTERM
Sep 12 16:20:54 crosshair sddm-greeter[1646]: The X11 connection broke (error 1). Did the X11 server die?
Sep 12 16:20:54 crosshair sddm[1014]: Greeter stopping...
Sep 12 16:20:54 crosshair sddm[1014]: Socket server stopping...
Sep 12 16:20:54 crosshair sddm[1014]: Socket server stopped.
Sep 12 16:20:54 crosshair sddm[1014]: Display server stopping...
Sep 12 16:20:54 crosshair sddm[1014]: Display server stopped.
Sep 12 16:20:54 crosshair sddm[1014]: Running display stop script "/usr/share/sddm/scripts/Xstop"
Sep 12 16:20:54 crosshair sddm[1014]: Greeter stopping...
Sep 12 16:20:54 crosshair sddm[1014]: QProcess: Destroyed while process ("/usr/lib/x86_64-linux-gnu/sddm/sddm-helper") is still running.
Sep 12 16:20:54 crosshair systemd[1]: Stopped Simple Desktop Display Manager.
Sep 12 16:20:54 crosshair polkitd(authority=local)[998]: Unregistered Authentication Agent for unix-process:2817:43654 (system bus name :1.28, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
Sep 12 16:20:57 crosshair systemd-logind[853]: Removed session 1.
Sep 12 16:20:57 crosshair systemd[1]: Stopping User Manager for UID 122...
Sep 12 16:20:57 crosshair systemd[1638]: Stopped target Default.
Sep 12 16:20:57 crosshair systemd[1638]: Reached target Shutdown.
Sep 12 16:20:57 crosshair systemd[1638]: Stopped target Basic System.
Sep 12 16:20:57 crosshair systemd[1638]: Stopped target Paths.
Sep 12 16:20:57 crosshair systemd[1638]: Stopped target Sockets.
Sep 12 16:20:57 crosshair systemd[1638]: Stopped target Timers.
Sep 12 16:20:57 crosshair systemd[1638]: Starting Exit the Session...
Sep 12 16:20:57 crosshair systemd[1638]: Received SIGRTMIN+24 from PID 2831 (kill).
Sep 12 16:20:57 crosshair systemd[1642]: pam_unix(systemd-user:session): session closed for user sddm
Sep 12 16:20:57 crosshair systemd[1]: Stopped User Manager for UID 122.
Sep 12 16:20:57 crosshair systemd[1]: Removed slice user-122.slice.
---------------------------------------------------------------------------------------------------
● sddm.service - Simple Desktop Display Manager
Loaded: loaded (/lib/systemd/system/sddm.service; enabled; vendor preset: enabled)
Active: failed (Result: start-limit) since Sat 2015-09-12 21:52:34 EDT; 12min ago
Docs: man:sddm(1)
man:sddm.conf(5)
Process: 1639 ExecStartPre=/bin/sh -c [ "$(cat /etc/X11/default-display-manager 2>/dev/null)" = "/usr/bin/sddm" ] (code=exited, status=1/FAILURE)
Thank you,
Carlos Kosloff
--- End Message ---
--- Begin Message ---
- To: Carlos Kosloff <ckosloff@hardwarealien.com>
- Cc: 798906-done@bugs.debian.org
- Subject: Re: Bug#798906: sddm crashes on boot
- From: Maximiliano Curia <maxy@gnuservers.com.ar>
- Date: Thu, 26 May 2016 20:23:46 +0200
- Message-id: <20160526182346.GB2503@gnuservers.com.ar>
- In-reply-to: <55FA36C9.1020006@hardwarealien.com>
- References: <55F5FA11.5040203__10021.7835548849$1442185778$gmane$org@hardwarealien.com> <55F94E5C.4080508@gnuservers.com.ar> <55FA36C9.1020006@hardwarealien.com>
¡Hola!Unfortunately we are not equipped to provide one on one user support. The issue as reported seems to be related to a nvidia card/specific nvidia set-up, and the sddm issue seems to be caused by a non working composite set-up.Once again I recommend using the theme sddm-theme-maui, and creating the /etc/sddm.conf file with the contents:[Theme] Current=maui Or trying using a different display manager, such as lightdm, or gdm.In the report you mentioned kdm, which has it's own set of issues regarding systemd, and was removed from the archive shortly after, so it would be better to test it with a different one.I'm now closing the bug as there isn't anything else we can do here. Happy hacking, -- "Any change looks terrible at first." -- Principle of Design Inertia Saludos /\/\ /\ >< `/Attachment: signature.asc
Description: Digital signature
--- End Message ---