The truncated backtrace is unfortunately:
Quiterss hang full#
I lost the full backtrace, but it wasn't useful, so no matter. I built gnome-session to crash on the first critical. It's when I do try to log out that I see the errors. In my case, though, canceling logout works fine. I duped a bunch of other logout bugs against this one simply because your bug shows the same g_object_unref journal errors I'm seeing when I try to log out. And they are also visible when doing a regular shutdown or logout (not aborting it). Sometimes the dialog does not show up at all, sometimes it shows up for the second (but not the third) time. This bug is not always behaving the same. Jun 07 03:58:04 hostname gnome-session: Entering running state Jun 07 03:58:01 hostname gnome-session: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x1c00006 specified for 0x1c00205 (quiterss). Jun 07 03:58:01 hostname gnome-session: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed Jun 07 03:58:01 hostname gnome-session: gnome-session: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed timer is not stopped so although I did not confirm the dialog gnome session logs out or even shuts down. ** (gnome-session-quit:29795): WARNING **: Failed to call logout: GDBus.Error:: Logout interface is only available during the Running phaseĢ. Instead if I force it to run again (`gnome-session-quit -no-prompt` I often get an error message: I am using gnome-session 3.16 on Fedora 22 with gnome-shell 3.18.ġ.
0 kommentar(er)
