Bug#1061421: Fails to start after an upgrade
On Wed, May 08, 2024 at 06:32:03PM +0900, Marc Dequènes wrote: > I packaged and uploaded 0.5.0 and this bug is fixed for me now, but > I'd like to hear from you all before closing this bug. The bug is also fixed for me with 0.5.0-1. Thanks for getting this fixed! Best wishes, Ryan -- |)|/ Ryan Kavanagh | 4E46 9519 ED67 7734 268F |\|\ https://rak.ac | BD95 8F7B F8FC 4A11 C97A signature.asc Description: PGP signature
Bug#1061421: Fails to start after an upgrade
"Marc Dequènes (duck)" writes: > Quack, > > On 2024-05-08 09:40, Marc Dequènes wrote: > >> Not sure this is the same problem but I would say it's worth a try. >> I'll prepare the package and let you know how it goes. > > I packaged and uploaded 0.5.0 and this bug is fixed for me now, but I'd like > to hear from you all before closing this bug. This version works for me. -- Arto Jantunen
Bug#1061421: Fails to start after an upgrade
Quack, On 2024-05-08 09:40, Marc Dequènes wrote: Not sure this is the same problem but I would say it's worth a try. I'll prepare the package and let you know how it goes. I packaged and uploaded 0.5.0 and this bug is fixed for me now, but I'd like to hear from you all before closing this bug. I'm still not sure 0.5.0 fixes this bug and I do not have time to explore all possibilities. As Peter found in #1065506 building with newer wayland and smithay versions can cause problems because there's important changes in newer versions and that may be the real source of this problem. Until upstream works on bumping the deps they are now locked. It's annoying to keep multiple versions around but there's no way around it at the moment. I'm using greetd 0.10.0 as upstream bumped the requirement for the greetd_ipc component. I don't think that's necessary to have such combination according to what changed in 0.10 and I left the link between both packages loose as before. Tell me if you encounter any problem. Regards. \_o< -- Marc Dequènes
Bug#1061421: Fails to start after an upgrade
Quack, On 2024-04-22 00:44, Jeremy Bícha wrote: There have been a huge amount of changes, but most of those changes were in Unstable and haven't reached Testing yet. I can confirm the problem is still there in latest unstable. Marc, there is a fix for sway 1.9 in wlgreet 0.5. Do you want to try if that improves anything here? Not sure this is the same problem but I would say it's worth a try. I'll prepare the package and let you know how it goes. Regards. \_o< -- Marc Dequènes
Bug#1061421: Fails to start after an upgrade
On Sun, Apr 21, 2024 at 2:36 AM Arto Jantunen wrote: > > Jeremy Bícha 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). There have been a huge amount of changes, but most of those changes were in Unstable and haven't reached Testing yet. Marc, there is a fix for sway 1.9 in wlgreet 0.5. Do you want to try if that improves anything here? Thank you, Jeremy Bícha
Bug#1061421: Fails to start after an upgrade
Jeremy Bícha 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
Processed: Re: Bug#1061421: Fails to start after an upgrade
Processing commands for cont...@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 ow...@bugs.debian.org with problems
Bug#1061421: Fails to start after an upgrade
Control: tags +moreinfo Please verify whether wlgreet is working for you now. Thank you, Jeremy Bícha
Bug#1061421: Fails to start after an upgrade
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 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 rak: building it directly in debug mode (cargo build without --release) should give a better error 16:15 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 signature.asc Description: PGP signature
Bug#1061421: Fails to start after an upgrade
"Marc Dequènes (duck)" writes:
> Thanks for the report.
> I stumbled onto the same problem but so far was not able to identify what's
> going on. Rebuilding the package does not help.
> 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.
#1061563 is a similar bug (started at the same time, also talks about
wl_surface) against alacritty. It has more information, and claims to
have a solution as well ("The update of smithay-client-toolkit from
0.16.0 to 0.16.1 is the relevant change and we already have 0.16.1 sctk
packaged."). wlgreet also has a build-dep on
librust-smithay-client-toolkit-dev so this might very well be the same
issue, and fixable in the same way.
--
Arto Jantunen
Processed: Re: Bug#1061421: Fails to start after an upgrade
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 ow...@bugs.debian.org with problems
Bug#1061421: Fails to start after an upgrade
Control: tag -1 +help Quack, On 2024-01-24 19:04, Arto Jantunen wrote: 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: Thanks for the report. I stumbled onto the same problem but so far was not able to identify what's going on. Rebuilding the package does not help. 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. Regards. \_o< -- Marc Dequènes
Processed: Re: Bug#1061421: Fails to start after an upgrade
Processing control commands: > tag -1 +help Bug #1061421 [wlgreet] Fails to start after an upgrade Added tag(s) help. -- 1061421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061421 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1061421: Fails to start after an upgrade
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 - 1: 0x562fb81db7ef - 2: 0x562fb821a5d4 - 3: 0x562fb820d9cf - 4: 0x562fb8217dee - 5: 0x562fb8218960 - 6: 0x562fb820e194 - 7: 0x562fb820e126 - 8: 0x562fb82181f1 - 9: 0x562fb81c1822 - 10: 0x562fb81c187c - 11: 0x562fb829de53 - 12: 0x562fb8269b29 - 13: 0x7fb720bb9a4e - 14: 0x7fb720bb5bb1 - 15: 0x7fb720bb75ac - wl_display_dispatch_queue_pending 16: 0x7fb720bb7b5f - wl_display_roundtrip_queue 17: 0x562fb8298d69 - 18: 0x562fb81cfa3a - 19: 0x562fb82a01a3 - 20: 0x562fb81d225c - 21: 0x7fb7208eb6ca - 22: 0x7fb7208eb785 - __libc_start_main 23: 0x562fb81c7de1 - 24:0x0 - [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
