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.
On 2024-12-30 02:47, yaros wrote:
Dnia niedziela, 29 grudnia 2024 15:40:16 CET Gary Dale pisze:Not quite. You log in at the console then startx. This bypasses sddm.
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.<br><br></div></pre></blockquote></div><br clear="all"><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--
Dnia 31 grudnia 2024 15:54:46 CET, Gary Dale <gary@extremeground.com> 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.
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.
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.
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.
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:
Le lundi 27 janvier 2025, 16:22:18 UTC+1 Gary Dale a écrit :
On 2025-01-17 19:54, Salvo Tomaselli wrote:Thanks.
Here's the journalctl output for the latest attempt to start sddm - thisBut 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.
time with the truncated line included:
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
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:Thanks.
Here's the journalctl output for the latest attempt to start sddm -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.
this
time with the truncated line included:
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.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 546 |
Nodes: | 16 (1 / 15) |
Uptime: | 160:34:37 |
Calls: | 10,385 |
Calls today: | 2 |
Files: | 14,056 |
Messages: | 6,416,493 |