Version-Release number of selected component: gnome-boxes-3.14.2-2.fc21 Additional info: reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: /usr/bin/gnome-boxes --gapplication-service crash_function: g_type_check_instance_is_a executable: /usr/bin/gnome-boxes kernel: 3.18.3-201.fc21.x86_64 runlevel: N 5 type: CCpp uid: 1001 Truncated backtrace: Thread no. 1 (10 frames) #0 g_type_check_instance_is_a at gtype.c:3969 #1 spice_session_get_channels at spice-session.c:1802 #2 spice_gtk_session_sync_keyboard_modifiers at spice-gtk-session.c:1187 #6 g_signal_emit_by_name at gsignal.c:3405 #7 _gdk_x11_keymap_state_changed at gdkkeys-x11.c:639 #8 gdk_x11_display_translate_event at gdkdisplay-x11.c:1049 #9 _gdk_x11_event_translator_translate at gdkeventtranslator.c:51 #10 gdk_event_source_translate_event at gdkeventsource.c:240 #11 _gdk_x11_display_queue_events at gdkeventsource.c:338 #12 gdk_display_get_event at gdkdisplay.c:321
Created attachment 984645 [details] File: backtrace
Created attachment 984646 [details] File: cgroup
Created attachment 984647 [details] File: core_backtrace
Created attachment 984648 [details] File: dso_list
Created attachment 984649 [details] File: environ
Created attachment 984650 [details] File: exploitable
Created attachment 984651 [details] File: limits
Created attachment 984652 [details] File: maps
Created attachment 984653 [details] File: open_fds
Created attachment 984654 [details] File: proc_pid_status
Created attachment 984655 [details] File: var_log_messages
*** Bug 1201316 has been marked as a duplicate of this bug. ***
Happens on f22 as well.
Reproducer at https://bugzilla.gnome.org/show_bug.cgi?id=746800#c1
most likely spice-session was disposed before spice-gtk-session, and it has a weak reference, I guess it could use a weak pointer for extra safe, but I think spice-gtk-session is supposed to be always weakly handled. Unfortunately, it's hard to enforce this, so we should make it a bit more robust for this kind of situation.
Created attachment 1006805 [details] Workaround for the crash Yeah this is what happens (the GObject part of SpiceSession is all garbage when this occurs), and the attached patch works around the issue. However, as noted in https://bugzilla.gnome.org/show_bug.cgi?id=746800 , Boxes is doing unexpected things with disconnected SpiceDisplays. I don't know if this crash will still occur once that is fixed.
Comment on attachment 1006805 [details] Workaround for the crash that looks okayish to me (I think I would have prefered weak pointers), feel free to submit to spice-devel
I do not really mean it to be a fix, this was just some quick debugging test, I'll try a weak pointer approach, though it would be nice to also know how to get in this situation;)
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.