Your message dated Tue, 21 May 2024 19:16:51 +0900
with message-id <7fc80cb444df51d15c0b9d0b7e88a...@duckcorp.org>
and subject line Re: Bug#1061421: Fails to start after an upgrade
has caused the Debian Bug report #1061421,
regarding Fails to start after an upgrade
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1061421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061421
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
Version: 0.5.0-1
On 2024-05-18 03:22, Ryan Kavanagh wrote:
The bug is also fixed for me with 0.5.0-1. Thanks for getting this
fixed!
Thanks for the feedback everyone.
Regards.
\_o<
--
Marc Dequènes
--- End Message ---
