On 2025-02-01 14:05, Gary Dale wrote:
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 remo
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
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.
H
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
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 include
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]: S
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 displa
> 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 faces
On 2024-12-31 10:18, yaros wrote:
Dnia 31 grudnia 2024 15:54:46 CET, Gary Dale
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 m
Dnia 31 grudnia 2024 15:54:46 CET, Gary Dale 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
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 respons
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 inst
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 ba
13 matches
Mail list logo
