Package: wlgreet
Version: 0.4.1-3
Severity: grave

After a semi-recent upgrade (I'm not sure which one, as I don't reboot
or restart my session after each one) of testing wlgreet no longer
starts. Here is what I get when trying to start it under a manually
launched sway session:

RUST_BACKTRACE=full wlgreet
thread 'main' panicked at 'internal error: entered unreachable code', src/app.rs:473:48
stack backtrace:
0: 0x562fb820dd27 - <unknown>
1: 0x562fb81db7ef - <unknown>
2: 0x562fb821a5d4 - <unknown>
3: 0x562fb820d9cf - <unknown>
4: 0x562fb8217dee - <unknown>
5: 0x562fb8218960 - <unknown>
6: 0x562fb820e194 - <unknown>
7: 0x562fb820e126 - <unknown>
8: 0x562fb82181f1 - <unknown>
9: 0x562fb81c1822 - <unknown>
10: 0x562fb81c187c - <unknown>
11: 0x562fb829de53 - <unknown>
12: 0x562fb8269b29 - <unknown>
13: 0x7fb720bb9a4e - <unknown>
14: 0x7fb720bb5bb1 - <unknown>
15: 0x7fb720bb75ac - wl_display_dispatch_queue_pending
16: 0x7fb720bb7b5f - wl_display_roundtrip_queue
17: 0x562fb8298d69 - <unknown>
18: 0x562fb81cfa3a - <unknown>
19: 0x562fb82a01a3 - <unknown>
20: 0x562fb81d225c - <unknown>
21: 0x7fb7208eb6ca - <unknown>
22: 0x7fb7208eb785 - __libc_start_main
23: 0x562fb81c7de1 - <unknown>
24: 0x0 - <unknown>
[wayland-client error] A handler for wl_surface panicked.

The issue is reproducible under debvm as follows:

debvm-create -o /tmp/debvm -r trixie -- --include=linux-image-amd64,wlgreet,greetd --hook-dir /usr/share/mmdebstrap/hooks/useradd && debvm-run -i /tmp/debvm -g

Modify greetd config to start sway (comment out agreety, uncomment
sway) and restart it, wlgreet fails with what looks like the same
error message.

-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.6.13-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=en_US.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages wlgreet depends on:
ii libc6 2.37-13
ii libgcc-s1 13.2.0-10
ii sway 1.9~debian.2bba8a86-2

wlgreet recommends no packages.

wlgreet suggests no packages.

-- Configuration Files:
/etc/greetd/sway-config changed:
exec "/usr/sbin/wlgreet; swaymsg exit"
bindsym Mod4+shift+e exec swaynag \
-t warning \
-m 'What do you want to do?' \
-b 'Poweroff' 'systemctl poweroff -i' \
-b 'Reboot' 'systemctl reboot -i'
include /etc/sway/config.d/*
include /etc/greetd/sway-config.d/*


-- no debconf information

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

Processing control commands:

tag -1 +help

Bug #1061421 [wlgreet] Fails to start after an upgrade
Ignoring request to alter tags of bug #1061421 to the same tags previously set

--
1061421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061421
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

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

Hi Marc, Arto,

On Mon, Jan 29, 2024 at 03:19:41PM +0900, Marc Dequènes wrote:

I guess it's related to libraries that are loaded dynamically,
possibly mesa, but it does not seem like an ABI breakage. I'll try to
dig deeper but l’m open to suggestion.

I tried asking in #kennylevison on libera a week ago and was given the following suggestion to try to figure what's going on:

11:48 <rak> wlgreet 0.4.1 dies with "thread 'main' panicked at 'internal
error: entered unreachable code', src/app.rs:473:48" on
Debian unstable (see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061421 ).
Any suggestions on a workaround, or any debugging
information that I could provide to help fix the bug?
14:06 <kennylevinsen> rak: building it directly in debug mode (cargo
build without --release) should give a better
error
16:15 <kchibisov> update sctk dunno.

I haven't had time to dig further since, but maybe you can get a better backtrace by rebuilding without --release and ask upstream for help? In
any case, they might appreciate knowing how we reached unreachable code
:)

Best wishes,
Ryan

--
|)|/ Ryan Kavanagh | 4E46 9519 ED67 7734 268F
|\|\ https://rak.ac | BD95 8F7B F8FC 4A11 C97A

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEP7FHOW9as2zJ9q6CWXuniu1D+jAFAmW+gOIACgkQWXuniu1D +jBhCg//aXuQXf8qrMla5CODDZEmYiv+R/q/GONLV4h0MT+2EgwaQ9GNOD8NfRCN qSZDT7WIPLWb6cJidMo4hFaZ9PuFRc4/uNs/snogsKM0BTd7IVImdH1vyi4LFy7l YoTTe1CqaaIY8Wo65C51HHWmeQyiulM9lB0hPZFS2o8/sDTNH2/qT70A1MWVvoAR AdVE8QbKqHDpZ8bsFm/uqePSaM2L7EWpSOhee6lGFeEwt9ttMba/BOLx3JOedsD8 +Gux3loUUxKxtpVisNs+PUAf1F/8rQZA556WYyw7eHYf0/0jXsKcyNV7mu0TLt66 Ng4mD9BZ0PFiqaQa88LB78J7C6pH18WdABRaz7srH6X3qrte/uKGyLrZubI6+paa LkGwIZ20Q3INCV5/F2eHkiIVS0pz1Nfcawlf+QfWYxmUawLeJOysdhq+19tEl0yP y0hA6Hw5+2/g5Pt8KGzAorO9BW6+M73IRlB3siwn4hfN91G65WNuRW3Z/atRzt6v 6v6zntpm9o6vkOUIHPzNWPfTuwQRmUtDvkhgGlpCRQo9EkyOYgV64wPkWQ81IDRt TGTAZkd13rEBQQhCRQStTkc6l0Z5c2jX6WBRfW/IxOMkDPJ1U3HrGVJJPLD/WrnM S5VKNI71Kn6flLr7dK4f1POB2h6qCWpovofyV8jSZyJ+IloP1hA=
=3zUu
-----END PGP SIGNATURE-----

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

Processing commands for control@bugs.debian.org:

tags 1061421 +moreinfo

Bug #1061421 [wlgreet] Fails to start after an upgrade
Added tag(s) moreinfo.

End of message, stopping processing here.

Please contact me if you need assistance.
--
1061421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061421
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

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

Jeremy Bícha <jeremy.bicha@canonical.com> writes:

Please verify whether wlgreet is working for you now.

Was something changed somewhere? What, where?

On trixie the issue reproduces exactly the same (even with sway upgraded
to the binNMU'd version from sid).

--
Arto Jantunen

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