Description of problem: Happened when logging in for the first time after upgrading to f38 (from f36). Shutter is started automatically, so it's available in system tray. Version-Release number of selected component: shutter-0.99.4-1.fc38 Additional info: reporter: libreport-2.17.9 type: CCpp reason: perl killed by SIGSEGV journald_cursor: s=148227e5fdb144809ac546e23c3adfdc;i=1c135;b=de1e9ba0379b4f948241460cbafe16d0;m=8b90c0a70;t=5fac7522d73ac;x=6859d110e09cc958 executable: /usr/bin/perl cmdline: /usr/bin/perl /usr/bin/shutter --min_at_startup cgroup: 0::/user.slice/user-1000.slice/session-2.scope rootdir: / uid: 1000 kernel: 6.2.14-300.fc38.x86_64 package: shutter-0.99.4-1.fc38 runlevel: N 5 comment: Happened when logging in for the first time after upgrading to f38 (from f36). Shutter is started automatically, so it's available in system tray. backtrace_rating: 4 crash_function: emission_find Truncated backtrace: Thread no. 1 (18 frames) #0 emission_find at ../gobject/gsignal.c:895 #1 signal_emit_unlocked_R.isra.0 at ../gobject/gsignal.c:3696 #4 gtk_widget_dispose at ../gtk/gtkwidget.c:12166 #7 gtk_container_remove at ../gtk/gtkcontainer.c:1911 #8 gtk_image_menu_item_destroy at ../gtk/deprecated/gtkimagemenuitem.c:407 #10 signal_emit_unlocked_R.isra.0 at ../gobject/gsignal.c:3930 #13 gtk_widget_dispose at ../gtk/gtkwidget.c:12166 #16 XS_Glib__Object_DESTROY at /usr/src/debug/perl-Glib-1.3293-10.fc38.x86_64/GObject.xs:1301 #17 Perl_pp_entersub at /usr/src/debug/perl-5.36.1-496.fc38.x86_64/pp_hot.c:5353 #18 Perl_call_sv at /usr/src/debug/perl-5.36.1-496.fc38.x86_64/perl.c:3057 #19 S_curse at /usr/src/debug/perl-5.36.1-496.fc38.x86_64/sv.c:6973 #20 Perl_sv_clear at /usr/src/debug/perl-5.36.1-496.fc38.x86_64/sv.c:6536 #21 Perl_sv_free2 at /usr/src/debug/perl-5.36.1-496.fc38.x86_64/sv.c:7073 #22 Perl_SvREFCNT_dec_NN at /usr/src/debug/perl-5.36.1-496.fc38.x86_64/inline.h:419 #23 do_clean_objs at /usr/src/debug/perl-5.36.1-496.fc38.x86_64/sv.c:448 #24 S_visit at /usr/src/debug/perl-5.36.1-496.fc38.x86_64/sv.c:391 #25 Perl_sv_clean_objs at /usr/src/debug/perl-5.36.1-496.fc38.x86_64/sv.c:542 #26 perl_destruct at /usr/src/debug/perl-5.36.1-496.fc38.x86_64/perl.c:880 Potential duplicate: bug 2183017
Created attachment 1961926 [details] File: proc_pid_status
Created attachment 1961927 [details] File: maps
Created attachment 1961928 [details] File: limits
Created attachment 1961929 [details] File: environ
Created attachment 1961930 [details] File: open_fds
Created attachment 1961931 [details] File: mountinfo
Created attachment 1961932 [details] File: os_info
Created attachment 1961934 [details] File: cpuinfo
Created attachment 1961936 [details] File: core_backtrace
Created attachment 1961937 [details] File: exploitable
Created attachment 1961938 [details] File: dso_list
Created attachment 1961939 [details] File: backtrace
upstream ticket: https://github.com/shutter-project/shutter/issues/573 answer from the developer: I looked into the backtrace, there is nothing Shutter specific there, as far as I can see. Looks like some problem with underlying libraries. Are there any details regarding how to reproduce this issue? What is Shutter's own output before the crash?
Created attachment 1982927 [details] output in terminal from shutter -min_at_startup The underlying command that is being run at startup is mentioned in cmdline. It's `shutter --min_at_startup`. Currently, however, that appears to do nothing at all after log in when triggered from Startup Applications. When running it from the terminal, it works (tray icon shows), but the process doesn't detach and I get the output shown in shutter.log (attached). I added a 7s delay timer now. In the past that helped with fixing some timing issues. I don't know where I would find "Shutter's own output".
please read the developer's suggestions and give feedback. So, did this crash happen just once after the system update or is it reproducible if Shutter is started via autostart? Looks like this is some race condition as the user already pointed out, probably the panel, which should show the tray icon isn't loaded fast enough. I will try to set up a Fedora Cinnamon VM to reproduce it, otherwise it will be hard to fix. Another idea: I could reproduce Shutter failing to launch on a Cinnamon install. The reason is that Cinnamon is too slow to load the panel, so Shutter exits after failing to create a tray icon. Butt Cinnamon has a timeout setting in its autostart configuration. I set it to 20s and it solved the problem for me.
(In reply to MartinKG from comment #15) > So, did this crash happen just once after the system update or is it > reproducible if Shutter is started via autostart? Looks like this is some > race condition as the user already pointed out, probably the panel, which > should show the tray icon isn't loaded fast enough. I will try to set up a > Fedora Cinnamon VM to reproduce it, otherwise it will be hard to fix. Yes, the SIGSEGV only happened once after the system upgrade, afaicr. > Another idea: I could reproduce Shutter failing to launch on a Cinnamon > install. The reason is that Cinnamon is too slow to load the panel, so > Shutter exits after failing to create a tray icon. Butt Cinnamon has a > timeout setting in its autostart configuration. I set it to 20s and it > solved the problem for me. I can confirm, that setting a timeout fixes the issue. I set mine to 7s and it works. However, I feel it would be better if Shutter handles this gracefully by either checking the panel is loaded or by retrying using an internal timer. But I'm no expert on these matters and can live with setting a timeout. I did so in the past as well.
Answer from the developer: (will close the ticket) https://github.com/shutter-project/shutter/issues/573#issuecomment-1680256047 Many apps that have tray icons suffer from this issue, it looks to me like there is no good solution for it... I tried to find some workaround to check programmatically whether the tray has started, but couldn't find anything so far.