Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#74652 - [signal-desktop] Crash when receiving notifications in background
Attached to Project:
Community Packages
Opened by Laurențiu Nicola (lnicola) - Thursday, 05 May 2022, 14:47 GMT
Last edited by Antonio Rojas (arojas) - Friday, 13 May 2022, 10:09 GMT
Opened by Laurențiu Nicola (lnicola) - Thursday, 05 May 2022, 14:47 GMT
Last edited by Antonio Rojas (arojas) - Friday, 13 May 2022, 10:09 GMT
|
DetailsDescription:
From around 5.40, Signal started crashing at times when receiving a notification. Happens to me on GNOME Wayland. Additional info: * 5.41 * stack trace: Stack trace of thread 653064: #0 0x00005619f3499ff3 n/a (signal-desktop + 0x4cc3ff3) #1 0x00007fd5dd9528ae n/a (libnotify.so.4 + 0x48ae) #2 0x00007fd5f24d0f8f g_closure_invoke (libgobject-2.0.so.0 + 0x13f8f) #3 0x00007fd5f24ecba8 n/a (libgobject-2.0.so.0 + 0x2fba8) #4 0x00007fd5f24ee5c7 g_signal_emit_valist (libgobject-2.0.so.0 + 0x315c7) #5 0x00007fd5f24ee824 g_signal_emit (libgobject-2.0.so.0 + 0x31824) #6 0x00007fd5f22bc816 n/a (libgio-2.0.so.0 + 0x10d816) #7 0x00007fd5f22a9348 n/a (libgio-2.0.so.0 + 0xfa348) #8 0x00007fd5f23d4163 g_main_context_dispatch (libglib-2.0.so.0 + 0x55163) #9 0x00007fd5f242a9e9 n/a (libglib-2.0.so.0 + 0xab9e9) #10 0x00007fd5f23d16c5 g_main_context_iteration (libglib-2.0.so.0 + 0x526c5) #11 0x00005619f3402c3b n/a (signal-desktop + 0x4c2cc3b) #12 0x00005619f3453ea4 n/a (signal-desktop + 0x4c7dea4) #13 0x00005619f3420c2c n/a (signal-desktop + 0x4c4ac2c) #14 0x00005619f2757fff n/a (signal-desktop + 0x3f81fff) #15 0x00005619f2759b82 n/a (signal-desktop + 0x3f83b82) #16 0x00005619f27557de n/a (signal-desktop + 0x3f7f7de) #17 0x00005619f0a81e51 n/a (signal-desktop + 0x22abe51) #18 0x00005619f0a832b8 n/a (signal-desktop + 0x22ad2b8) #19 0x00005619f0a82c8b n/a (signal-desktop + 0x22acc8b) #20 0x00005619f0a801ce n/a (signal-desktop + 0x22aa1ce) #21 0x00005619f0a80be3 n/a (signal-desktop + 0x22aabe3) #22 0x00005619f0810108 n/a (signal-desktop + 0x203a108) #23 0x00007fd5f0ea5310 __libc_start_call_main (libc.so.6 + 0x2d310) #24 0x00007fd5f0ea53c1 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2d3c1) #25 0x00005619f04695ea _start (signal-desktop + 0x1c935ea) * upstream doesn't want to support Arch: https://github.com/signalapp/Signal-Desktop/issues/5903 |
This task depends upon
Comment by Leopold Bloom (leopoldbloom) -
Thursday, 05 May 2022, 21:41 GMT
Looks like it was a bug in libnotify. It should have been fixed with this commit and the libnotify package has been updated: https://github.com/archlinux/svntogit-packages/commit/08f504440434fb3a38e51a6affb9a0c4606e8be6