sddm does not start after update to 0.20.0

  • Open
  • quality assurance status badge
Details
2 participants
  • Jonathan Brielmaier
  • tumashu
Owner
unassigned
Submitted by
Jonathan Brielmaier
Severity
normal
J
J
Jonathan Brielmaier wrote on 5 Feb 23:37 +0100
(address . bug-guix@gnu.org)(address . tumashu@163.com)
4b6ef632-1183-1370-642b-d6ab80355e10@web.de
Today I rebooted my workstation running Guix System and somehow sddm
didn't started anymore.

I quickly found a suspicious commit:
05fad99a431c6708ec18c7d0db67178bd8d36597
gnu: sddm: Update to 0.20.0.

Then I pulled and reconfigured to this commit (Generation 14) and to one
commit before (Generation 13). And indeed the sddm update to 0.20.0
breaks my system.

```
Generation 13 Feb 05 2024 23:00:35
file name: /var/guix/profiles/system-13-link
canonical file name: /gnu/store/hq4bd4vzlyvnwblc5w2jpll4xn7nmzrd-system
label: GNU with Linux 6.6.8
bootloader: grub-efi
root device: /dev/mapper/cryptroot
kernel: /gnu/store/nn8dir9d1d025r123ib11jfsxxc714fl-linux-6.6.8/bzImage
channels:
guix:
commit: f96590fb3662300058022f0aaee594e766f8941f
configuration file:
/gnu/store/4n81nr9bi0jn5vqfpa3s4y4wzci1zxkf-configuration.scm

Generation 14 Feb 05 2024 23:07:31
file name: /var/guix/profiles/system-14-link
canonical file name: /gnu/store/ks1f2wg4gb4sn2gv1ag0f3spp5xjv5gq-system
[ part is identical to Gen 13 ]
channels:
guix:
commit: 05fad99a431c6708ec18c7d0db67178bd8d36597
configuration file:
/gnu/store/4n81nr9bi0jn5vqfpa3s4y4wzci1zxkf-configuration.scm
```

The relevant part of my configuration.scm:
```
(service sddm-service-type
(sddm-configuration
(display-server "wayland")))
```

There is an upstream bug report which is maybe relevant:

@Feng Shu: I CC'ed you for this bug as you updated the sddm package.
Maybe you are not affected by this issue or have a workaround :)

~Jonathan
T
T
tumashu wrote on 5 Feb 23:45 +0100
(name . Jonathan Brielmaier)(address . jonathan.brielmaier@web.de)(address . bug-guix@gnu.org)
1ca1d78a.9f.18d7b72c2ef.Coremail.tumashu@163.com
(display-server "wayland")

remove this line, at the moment, sddm-service-type do not support this feature, for waston is not configure properly






--
?????????????
<br/><br/><br/>


----- Original Message -----
From: "Jonathan Brielmaier" <jonathan.brielmaier@web.de>
To: bug-guix@gnu.org
Cc: tumashu@163.com
Sent: Mon, 5 Feb 2024 23:37:52 +0100
Subject: sddm does not start after update to 0.20.0

Today I rebooted my workstation running Guix System and somehow sddm
didn't started anymore.

I quickly found a suspicious commit:
05fad99a431c6708ec18c7d0db67178bd8d36597
gnu: sddm: Update to 0.20.0.

Then I pulled and reconfigured to this commit (Generation 14) and to one
commit before (Generation 13). And indeed the sddm update to 0.20.0
breaks my system.

```
Generation 13 Feb 05 2024 23:00:35
file name: /var/guix/profiles/system-13-link
canonical file name: /gnu/store/hq4bd4vzlyvnwblc5w2jpll4xn7nmzrd-system
label: GNU with Linux 6.6.8
bootloader: grub-efi
root device: /dev/mapper/cryptroot
kernel: /gnu/store/nn8dir9d1d025r123ib11jfsxxc714fl-linux-6.6.8/bzImage
channels:
guix:
commit: f96590fb3662300058022f0aaee594e766f8941f
configuration file:
/gnu/store/4n81nr9bi0jn5vqfpa3s4y4wzci1zxkf-configuration.scm

Generation 14 Feb 05 2024 23:07:31
file name: /var/guix/profiles/system-14-link
canonical file name: /gnu/store/ks1f2wg4gb4sn2gv1ag0f3spp5xjv5gq-system
[ part is identical to Gen 13 ]
channels:
guix:
commit: 05fad99a431c6708ec18c7d0db67178bd8d36597
configuration file:
/gnu/store/4n81nr9bi0jn5vqfpa3s4y4wzci1zxkf-configuration.scm
```

The relevant part of my configuration.scm:
```
(service sddm-service-type
(sddm-configuration
(display-server "wayland")))
```

There is an upstream bug report which is maybe relevant:

@Feng Shu: I CC'ed you for this bug as you updated the sddm package.
Maybe you are not affected by this issue or have a workaround :)

~Jonathan
Attachment: file
J
J
Jonathan Brielmaier wrote on 6 Feb 00:05 +0100
Re: sddm does not start after update to 0.20.0
(address . 68939@debbugs.gnu.org)(name . tumashu)(address . tumashu@163.com)
d012b5e9-7d91-aa11-7a2d-31470fbec5be@web.de
Hi tumashu,

Am 05.02.24 um 23:45 schrieb tumashu:
Toggle quote (4 lines)
> (display-server "wayland")
>
> remove this line, at the moment, sddm-service-type do not support this feature, for waston is not configure properly

Thanks for that super fast response! Indeed this was the trick, sddm
works now again without setting the display-server to wayland.

I wonder what we could do in the mean time to save other users from this
pitfall?

Would it make sense to deprecate the `display-server` configuration
parameter in order to always default to xorg?

Or maybe just add a note to the manual:

~Jonathan
F
F
Feng Shu wrote on 6 Feb 01:41 +0100
(name . Jonathan Brielmaier)(address . jonathan.brielmaier@web.de)(address . 68939@debbugs.gnu.org)
87il322zlv.fsf@163.com
Jonathan Brielmaier <jonathan.brielmaier@web.de> writes:

Toggle quote (19 lines)
> Hi tumashu,
>
> Am 05.02.24 um 23:45 schrieb tumashu:
>> (display-server "wayland")
>>
>> remove this line, at the moment, sddm-service-type do not support this feature, for waston is not configure properly
>
> Thanks for that super fast response! Indeed this was the trick, sddm
> works now again without setting the display-server to wayland.
>
> I wonder what we could do in the mean time to save other users from this
> pitfall?
>
> Would it make sense to deprecate the `display-server` configuration
> parameter in order to always default to xorg?
>
> Or maybe just add a note to the manual:
> https://guix.gnu.org/manual/devel/en/guix.html#index-sddm_002dconfiguration

I think, we should let sddm-service-type create the below config:

CompositorCommand=
Path of the compositor to execute when starting the greeter. Default value is "weston --shell=fullscreen-shell.so".


Toggle quote (4 lines)
>
> ~Jonathan
>

--
?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 68939@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 68939
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch