Forum: >>> Magnum BBS <<<

sddm hangs in Debian/Trixie

From Gary Dale@21:1/5 to All on Sun Dec 29 15:50:01 2024

I'm running Debian/Trixie on an AMD64 system.

After doing a full-upgrade this morning, I rebooted my system. It gets
to the sddm service being started then goes no further. It hangs and is
not responsive to the keyboard. I had to install lightdm and make it my
default desktop manager to get back to my desktop.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

From yaros@21:1/5 to All on Mon Dec 30 08:50:01 2024

Dnia niedziela, 29 grudnia 2024 15:40:16 CET Gary Dale pisze:
I'm running Debian/Trixie on an AMD64 system.

After doing a full-upgrade this morning, I rebooted my system. It gets
to the sddm service being started then goes no further. It hangs and is
not responsive to the keyboard. I had to install lightdm and make it my
default desktop manager to get back to my desktop.

I had similar problem - but was possible to switch to another console. After that i did startx and after restart sddm worked as expected.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

From Gary Dale@21:1/5 to yaros on Tue Dec 31 16:00:01 2024

On 2024-12-30 02:47, yaros wrote:

Dnia niedziela, 29 grudnia 2024 15:40:16 CET Gary Dale pisze:
I'm running Debian/Trixie on an AMD64 system.

After doing a full-upgrade this morning, I rebooted my system. It gets
to the sddm service being started then goes no further. It hangs and is
not responsive to the keyboard. I had to install lightdm and make it my default desktop manager to get back to my desktop.

I had similar problem - but was possible to switch to another console. After that i did startx and after restart sddm worked as expected.

Not quite. You log in at the console then startx. This bypasses sddm.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

From yaros@21:1/5 to All on Tue Dec 31 16:20:01 2024

------K1CSFVXZIBHQIL5XOFXI3Q5J8Q5O4G
Content-Type: text/plain;
charset=utf-8
Content-Transfer-Encoding: quoted-printable

Dnia 31 grudnia 2024 15:54:46 CET, Gary Dale <[email protected]> napisał/a:

On 2024-12-30 02:47, yaros wrote:

Dnia niedziela, 29 grudnia 2024 15:40:16 CET Gary Dale pisze:
I'm running Debian/Trixie on an AMD64 system.

After doing a full-upgrade this morning, I rebooted my system. It gets
to the sddm service being started then goes no further. It hangs and is
not responsive to the keyboard. I had to install lightdm and make it my
default desktop manager to get back to my desktop.

I had similar problem - but was possible to switch to another console. After that i did startx and after restart sddm worked as expected.

Not quite. You log in at the console then startx. This bypasses sddm.

After one time login via console and startx, sddm works again for me.
-- Wysłane za pomocą K-9 Mail.
------K1CSFVXZIBHQIL5XOFXI3Q5J8Q5O4G
Content-Type: text/html;
charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head></head><body><div class="gmail_quote"><div dir="auto">Dnia 31 grudnia 2024 15:54:46 CET, Gary Dale <[email protected]> napisał/a:</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(
204, 204, 204); padding-left: 1ex;">
<pre class="k9mail"><div dir="auto">On 2024-12-30 02:47, yaros wrote: </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"><div dir="auto">Dnia niedziela, 29 grudnia 2024 15:40:16
CET Gary Dale pisze: I'm running Debian/Trixie on an AMD64 system. After doing a full-upgrade this morning, I rebooted my system. It gets to the sddm service being started then goes no further. It hangs and is not responsive to the
keyboard. I had to install lightdm and make it my default desktop manager to get back to my desktop. I had similar problem - but was possible to switch to another console. After that i did startx and after restart sddm worked as expected.<

</div></blockquote><div dir="auto">Not quite. You log in at the console then startx. This bypasses sddm. </div></pre></blockquote></div> <div dir="auto">After one time login via console and startx, sddm works again for me. </div><

div dir="auto">-- Wysłane za pomocą K-9 Mail.</div></body></html> ------K1CSFVXZIBHQIL5XOFXI3Q5J8Q5O4G--

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

From Gary Dale@21:1/5 to yaros on Wed Jan 1 17:20:02 2025

This is a multi-part message in MIME format.
On 2024-12-31 10:18, yaros wrote:

Dnia 31 grudnia 2024 15:54:46 CET, Gary Dale <[email protected]> napisał/a:

On 2024-12-30 02:47, yaros wrote:

Dnia niedziela, 29 grudnia 2024 15:40:16 CET Gary Dale pisze:
I'm running Debian/Trixie on an AMD64 system. After doing a
full-upgrade this morning, I rebooted my system. It gets to
the sddm service being started then goes no further. It hangs
and is not responsive to the keyboard. I had to install
lightdm and make it my default desktop manager to get back to
my desktop. I had similar problem - but was possible to switch
to another console. After that i did startx and after restart
sddm worked as expected.

Not quite. You log in at the console then startx. This bypasses sddm.

After one time login via console and startx, sddm works again for me.
-- Wysłane za pomocą K-9 Mail.

But not for me. After a reboot, it still hangs.

<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">On 2024-12-31 10:18, yaros wrote: 
</div>
<blockquote type="cite"
cite="mid:[email protected]">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div class="gmail_quote">
<div dir="auto">Dnia 31 grudnia 2024 15:54:46 CET, Gary Dale
<a class="moz-txt-link-rfc2396E" href="mailto:[email protected]"><[email protected]></a> napisał/a:</div>
<blockquote class="gmail_quote"
style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail"><div dir="auto">On 2024-12-30 02:47, yaros wrote: </div><blockquote class="gmail_quote"
style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"><div
dir="auto">Dnia niedziela, 29 grudnia 2024 15:40:16 CET Gary Dale pisze:
I'm running Debian/Trixie on an AMD64 system.

After doing a full-upgrade this morning, I rebooted my system. It gets
to the sddm service being started then goes no further. It hangs and is
not responsive to the keyboard. I had to install lightdm and make it my
default desktop manager to get back to my desktop.

I had similar problem - but was possible to switch to another console. After that i did startx and after restart sddm worked as expected.
</div></blockquote><div dir="auto">Not quite. You log in at the console then startx. This bypasses sddm.

</div></pre>
</blockquote>
</div>
 
<div dir="auto">After one time login via console and startx, sddm
works again for me. </div>
<div dir="auto">-- Wysłane za pomocą K-9 Mail.</div>
</blockquote>
 

But not for me. After a reboot, it still hangs. 
</body>
</html>

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

From Salvo Tomaselli@21:1/5 to All on Sat Jan 18 01:54:33 2025

Copy: [email protected] (Gary Dale)

But not for me. After a reboot, it still hangs.

Have you tried removing its configuration? It works for me so it can't be completely broken.

--
Salvo Tomaselli

"Io non mi sento obbligato a credere che lo stesso Dio che ci ha dotato di senso, ragione ed intelletto intendesse che noi ne facessimo a meno."
-- Galileo Galilei

https://ltworf.codeberg.page/
-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEQnSLnnbYmXmeH74Us6fPDIAYhs8FAmeK+8kACgkQs6fPDIAY hs8CXw//dJoUl7j1Pwi77usEg41bE7AKxPzjwPF6RnkRwnJliBKbl/igyyA3nGL/ m+27AHWU4cTK/POGy+3V4c4mowubsXNvJODAQPs/JYSXRtovaNlBkgpbx+EFJEnc 3NUDiPG/3oYsqyKayV7Xrr8t8GaC7ZKiBd157I612NGcYJ7kjhB068uVMNCS/pGZ pjpEQKoaCowOyeAei0p9FD/1KQvm9d8ktkBdoD+1UHu7/Dmv7FqNmPRr07yJTHZA skD7cTg6tdqJbfXirD/GalHMkEyBu00iFP3BX7C14cT12nDJ1sJkPZVsSpiEmPHU TTym/kygrTdsVBCDZj+o3J9hQadlcdvg/+1JlqelTvLa9pGWEOSpZo8YUb/pt92L SMkGuZ/ki5Bl10JV2T67HjX2ZNibVonyLL3q88viOtqxCjWR7jtAUQJrrfUtfJTm ACF9zv/JG5kC9hDiJvvazgOlpzZ4EEXTlo8hK0xgotVn4y2JrR3ClK4eIPJqO5aY HbttXbc2hTPiIZlsDcInnzsJs1pmjM2rjYpgL8lK2Q/j/ITdqpaVIpXFT2aNPoXU krilsxZCBw6DkFuy5eIa/aVW2/SQO59SkQSsa9hY7Wyf2oz8IDHN82z95OoLvuxc qwd4YaqdmvZHqaB8J+BBV5ms/NXDXaPc2lWePV7fFiN9SKFYAus=
=Tc76
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

From Gary Dale@21:1/5 to Salvo Tomaselli on Fri Jan 24 21:20:01 2025

On 2025-01-17 19:54, Salvo Tomaselli wrote:

But not for me. After a reboot, it still hangs.

Have you tried removing its configuration? It works for me so it can't be completely broken.

I did an apt purge sddm, followed by a reboot. This ended up at the
command line because there was no display manager (the purge didn't
switch the default DM to lightdm, which was also installed). I
reinstalled sddm and rebooted. sddm still hangs.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

From Gary Dale@21:1/5 to Salvo Tomaselli on Mon Jan 27 16:10:01 2025

This is a multi-part message in MIME format.
On 2025-01-17 19:54, Salvo Tomaselli wrote:

But not for me. After a reboot, it still hangs.

Have you tried removing its configuration? It works for me so it can't be completely broken.

Here's the journalctl output for the latest attempt to start sddm:

Jan 27 09:49:49 transponder systemd[1]: Started sddm.service - Simple
Desktop Display Manager.
Jan 27 09:49:49 transponder sddm[1590]: Initializing...
Jan 27 09:49:49 transponder sddm[1590]: Starting...
Jan 27 09:49:49 transponder sddm[1590]: Logind interface found
Jan 27 09:49:49 transponder sddm[1590]: Adding new display...
Jan 27 09:49:49 transponder sddm[1590]: Loaded empty theme configuration
Jan 27 09:49:49 transponder sddm[1590]: Xauthority path: "/run/sddm/xauth_QcqrjQ"
Jan 27 09:49:49 transponder sddm[1590]: Using VT 2
Jan 27 09:49:49 transponder sddm[1590]: Display server starting...
Jan 27 09:49:49 transponder sddm[1590]: Writing cookie to "/run/sddm/xauth_QcqrjQ"
Jan 27 09:49:49 transponder sddm[1590]: Running: /usr/bin/X -nolisten
tcp -background none -seat seat0 vt2 -a>
Jan 27 09:49:49 transponder sddm[1590]: Failed to read display number
from pipe
Jan 27 09:49:49 transponder sddm[1590]: Display server stopping...
Jan 27 09:49:49 transponder sddm[1590]: Attempt 1 starting the Display
server on vt 2 failed

<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">On 2025-01-17 19:54, Salvo Tomaselli
wrote: 
</div>
<blockquote type="cite" cite="mid:6273893.lOV4Wx5bFT@galatea">
<blockquote type="cite">
<pre wrap="" class="moz-quote-pre">But not for me. After a reboot, it still hangs.
</pre>
</blockquote>
<pre wrap="" class="moz-quote-pre">
Have you tried removing its configuration? It works for me so it can't be completely broken.

</pre>
</blockquote>
Here's the journalctl output for the latest attempt to start
sddm:
Jan 27
09:49:49 transponder systemd[1]: Started sddm.service - Simple
Desktop Display Manager.
 
Jan 27
09:49:49 transponder sddm[1590]: Initializing...
 
Jan 27
09:49:49 transponder sddm[1590]: Starting...
 
Jan 27
09:49:49 transponder sddm[1590]: Logind
interface found
 
Jan 27
09:49:49 transponder sddm[1590]: Adding new
display...
 
Jan 27
09:49:49 transponder sddm[1590]: Loaded empty
theme configuration
 
Jan 27
09:49:49 transponder sddm[1590]: Xauthority
path: "/run/sddm/xauth_QcqrjQ"
 
Jan 27
09:49:49 transponder sddm[1590]: Using VT 2
 
Jan 27
09:49:49 transponder sddm[1590]: Display server
starting...
 
Jan 27
09:49:49 transponder sddm[1590]: Writing cookie
to "/run/sddm/xauth_QcqrjQ"
 
Jan 27
09:49:49 transponder sddm[1590]: Running:
/usr/bin/X -nolisten tcp -background none -seat seat0 vt2 -a>
 
Jan 27
09:49:49 transponder sddm[1590]: Failed
to read display number from pipe
 
Jan 27
09:49:49 transponder sddm[1590]: Display server
stopping...
 
Jan 27
09:49:49 transponder sddm[1590]: Attempt
1 starting the Display server on vt 2 failed 

 
 

</body>
</html>

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

From Gary Dale@21:1/5 to Salvo Tomaselli on Mon Jan 27 16:30:01 2025

This is a multi-part message in MIME format.
On 2025-01-17 19:54, Salvo Tomaselli wrote:

But not for me. After a reboot, it still hangs.

Have you tried removing its configuration? It works for me so it can't be completely broken.

Here's the journalctl output for the latest attempt to start sddm - this
time with the truncated line included:

Jan 27 09:49:49 transponder systemd[1]: Started sddm.service - Simple
Desktop Display Manager.
Jan 27 09:49:49 transponder sddm[1590]: Initializing...
Jan 27 09:49:49 transponder sddm[1590]: Starting...
Jan 27 09:49:49 transponder sddm[1590]: Logind interface found
Jan 27 09:49:49 transponder sddm[1590]: Adding new display...
Jan 27 09:49:49 transponder sddm[1590]: Loaded empty theme configuration
Jan 27 09:49:49 transponder sddm[1590]: Xauthority path: "/run/sddm/xauth_QcqrjQ"
Jan 27 09:49:49 transponder sddm[1590]: Using VT 2
Jan 27 09:49:49 transponder sddm[1590]: Display server starting...
Jan 27 09:49:49 transponder sddm[1590]: Writing cookie to "/run/sddm/xauth_QcqrjQ"
Jan 27 09:49:49 transponder sddm[1590]: Running: /usr/bin/X -nolisten
tcp -background none -seat seat0 vt2 -au
th /run/sddm/xauth_QcqrjQ -noreset -displayfd 16
Jan 27 09:49:49 transponder sddm[1590]: Failed to read display number
from pipe
Jan 27 09:49:49 transponder sddm[1590]: Display server stopping...
Jan 27 09:49:49 transponder sddm[1590]: Attempt 1 starting the Display
server on vt 2 failed

<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">On 2025-01-17 19:54, Salvo Tomaselli
wrote: 
</div>
<blockquote type="cite" cite="mid:6273893.lOV4Wx5bFT@galatea">
<blockquote type="cite">
<pre wrap="" class="moz-quote-pre">But not for me. After a reboot, it still hangs.
</pre>
</blockquote>
<pre wrap="" class="moz-quote-pre">Have you tried removing its configuration? It works for me so it can't be
completely broken.

</pre>
</blockquote>
Here's the journalctl output for the latest attempt to start sddm
- this time with the truncated line included: 

Jan 27
09:49:49 transponder systemd[1]: Started sddm.service - Simple
Desktop Display Manager. 
Jan 27
09:49:49 transponder sddm[1590]: Initializing... 
Jan 27
09:49:49 transponder sddm[1590]: Starting... 
Jan 27
09:49:49 transponder sddm[1590]: Logind
interface found 
Jan 27
09:49:49 transponder sddm[1590]: Adding new
display... 
Jan 27
09:49:49 transponder sddm[1590]: Loaded empty
theme configuration 
Jan 27
09:49:49 transponder sddm[1590]: Xauthority
path: "/run/sddm/xauth_QcqrjQ" 
Jan 27
09:49:49 transponder sddm[1590]: Using VT 2 
Jan 27
09:49:49 transponder sddm[1590]: Display server
starting... 
Jan 27
09:49:49 transponder sddm[1590]: Writing cookie
to "/run/sddm/xauth_QcqrjQ" 
Jan 27
09:49:49 transponder sddm[1590]: Running:
/usr/bin/X -nolisten tcp -background none -seat seat0 vt2 -au 
th /run/sddm/xauth_QcqrjQ -noreset -displayfd 16 

Jan 27
09:49:49 transponder sddm[1590]: Failed
to read display number from pipe 
Jan 27
09:49:49 transponder sddm[1590]: Display server
stopping... 
Jan 27
09:49:49 transponder sddm[1590]: Attempt
1 starting the Display server on vt 2 failed 
 
 

</body>
</html>

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

From =?UTF-8?B?QXVyw6lsaWVu?= COUDERC@21:1/5 to All on Wed Jan 29 21:30:01 2025

Le lundi 27 janvier 2025, 16:22:18 UTC+1 Gary Dale a écrit :

On 2025-01-17 19:54, Salvo Tomaselli wrote:

But not for me. After a reboot, it still hangs.

Have you tried removing its configuration? It works for me so it can't be completely broken.

Here's the journalctl output for the latest attempt to start sddm - this time with the truncated line included:

Thanks.

By any chance does switching to another VT (like ctrl+alt+F3 or any other number) and restarting SDDM (systemctl restart sddm.service) work ?

There’s an upstream bug here [1] that describes the same symptoms.

[1] https://github.com/sddm/sddm/issues/1316

--
Aurélien

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

From Gary Dale@21:1/5 to All on Sat Feb 1 19:00:02 2025

On 2025-01-29 15:11, Aurélien COUDERC wrote:

Le lundi 27 janvier 2025, 16:22:18 UTC+1 Gary Dale a écrit :

On 2025-01-17 19:54, Salvo Tomaselli wrote:

But not for me. After a reboot, it still hangs.

Have you tried removing its configuration? It works for me so it can't be >>> completely broken.

Here's the journalctl output for the latest attempt to start sddm - this
time with the truncated line included:

Thanks.

By any chance does switching to another VT (like ctrl+alt+F3 or any other number) and restarting SDDM (systemctl restart sddm.service) work ?

There’s an upstream bug here [1] that describes the same symptoms.

[1] https://github.com/sddm/sddm/issues/1316

--
Aurélien

That worked. I'm not sure what part of it did the trick.

I hate rebooting because it always takes me time to reorganize may
desktops. The first time I tried it, I went to F3 and mistakenly entered
the systemctl start command, which didn't work. It asked for the root
password then died. The second time I rebooted, I logged in on F2 by
mistake then relogged in on F3 and entered the correct restart command
and it succeeded.

However my desktop was even more messed up than usual. Everything opened
on virtual desktop 1, usually in the centre of the screen and with
window sizes forgotten.

Also, I'm not sure why sddm wants to bring up a virtual keyboard each
time. I'd think it should only do this if there is not actual keyboard
present.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

From Gary Dale@21:1/5 to Gary Dale on Sat Feb 1 20:10:01 2025

On 2025-02-01 12:52, Gary Dale wrote:

On 2025-01-29 15:11, Aurélien COUDERC wrote:

Le lundi 27 janvier 2025, 16:22:18 UTC+1 Gary Dale a écrit :

On 2025-01-17 19:54, Salvo Tomaselli wrote:

But not for me. After a reboot, it still hangs.

Have you tried removing its configuration? It works for me so it
can't be
completely broken.

Here's the journalctl output for the latest attempt to start sddm -
this
time with the truncated line included:

Thanks.

By any chance does switching to another VT (like ctrl+alt+F3 or any
other number) and restarting SDDM (systemctl restart sddm.service)
work ?

There’s an upstream bug here [1] that describes the same symptoms.

[1] https://github.com/sddm/sddm/issues/1316

--
Aurélien

That worked. I'm not sure what part of it did the trick.

I hate rebooting because it always takes me time to reorganize may
desktops. The first time I tried it, I went to F3 and mistakenly
entered the systemctl start command, which didn't work. It asked for
the root password then died. The second time I rebooted, I logged in
on F2 by mistake then relogged in on F3 and entered the correct
restart command and it succeeded.

However my desktop was even more messed up than usual. Everything
opened on virtual desktop 1, usually in the centre of the screen and
with window sizes forgotten.

Also, I'm not sure why sddm wants to bring up a virtual keyboard each
time. I'd think it should only do this if there is not actual keyboard present.

OK, found part of the problem. It brought me up in Wayland instead of
X11. That's why my desktops were so messed up.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Who's Online
Recent Visitors
- Bob Worm
  Tue Jun 9 10:31:07 2026
  from Wales, Uk via Telnet
- Centurion
  Mon Jun 8 23:30:43 2026
  from Berea, Ohio via Telnet
- Centurion
  Mon Jun 8 21:33:11 2026
  from Berea, Ohio via Telnet
- Bob Worm
  Mon Jun 8 20:15:00 2026
  from Wales, Uk via Telnet
- Bob Worm
  Mon Jun 8 16:33:22 2026
  from Wales, Uk via Telnet
- Bob Worm
  Mon Jun 8 14:11:46 2026
  from Wales, Uk via Telnet
- Krenn
  Mon Jun 8 11:22:02 2026
  from Sydney, Nsw via Telnet
- Bob Worm
  Mon Jun 8 08:26:26 2026
  from Wales, Uk via Telnet

System Info

Sysop:	Keyop
Location:	Huddersfield, West Yorkshire, UK
Users:	715
Nodes:	16 (3 / 13)
Uptime:	42:18:06
Calls:	12,110
Calls today:	1
Files:	15,007
Messages:	6,518,421

sddm hangs in Debian/Trixie

Who's Online

Recent Visitors

System Info