Description of problem: Gnome-shell is crashing after update. There was gnome-desktop3, glibc, gvfs, dbus in update (not g-s). I don't get to gdm. Version-Release number of selected component: gnome-shell-3.23.1-1.fc26 Additional info: reporter: libreport-2.8.0 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: _meta_plugin_set_compositor executable: /usr/bin/gnome-shell global_pid: 1743 kernel: 4.9.0-0.rc7.git3.1.fc26.x86_64 pkg_fingerprint: 812A 6B4B 64DA B85D pkg_vendor: Fedora Project runlevel: unknown type: CCpp uid: 42 Truncated backtrace: Thread no. 1 (6 frames) #0 _meta_plugin_set_compositor at compositor/meta-plugin.c:214 #1 meta_plugin_manager_new at compositor/meta-plugin-manager.c:105 #2 meta_compositor_manage at compositor/compositor.c:556 #3 enable_compositor at core/display.c:458 #4 meta_display_open at core/display.c:950 #5 meta_run at core/main.c:569
Created attachment 1228397 [details] File: backtrace
Created attachment 1228398 [details] File: cgroup
Created attachment 1228399 [details] File: core_backtrace
Created attachment 1228400 [details] File: dso_list
Created attachment 1228401 [details] File: environ
Created attachment 1228402 [details] File: exploitable
Created attachment 1228403 [details] File: limits
Created attachment 1228404 [details] File: maps
Created attachment 1228405 [details] File: mountinfo
Created attachment 1228406 [details] File: namespaces
Created attachment 1228407 [details] File: open_fds
Created attachment 1228408 [details] File: proc_pid_status
Created attachment 1228409 [details] File: var_log_messages
*** Bug 1401805 has been marked as a duplicate of this bug. ***
*** Bug 1401317 has been marked as a duplicate of this bug. ***
The workaround here is to downgrade to mutter-3.23.1-2.fc26.x86_64.
Thx. All my ABRT reports were corrupted. Anyway, this kind of bugs is pretty annoying, because it even prevented me to use the text console, since the display server was restarting all the time and it somehow gradually influenced all the text consoles. Is there a chance to handle such issues more gracefully? E.g. Degrade to multi-user.target or something just a bit better than constantly restarting display server?
is there a way to obtain the mutter-3.23.1-2.fc26.x86_64 package? would it be possible to keep at least 2 packages in the repo for downgrading purposes?
Manually with Koji. http://koji.fedoraproject.org/koji/buildinfo?buildID=816346
The root cause of this is that gnome-shell needs to be updated in sync with mutter, and mutter build passed, but gnome-shell build failed [1]. The reason why it failed is probably because of bug 1401231. [1] http://koji.fedoraproject.org/koji/buildinfo?buildID=822182 (In reply to Jakub from comment #18) > is there a way to obtain the mutter-3.23.1-2.fc26.x86_64 package? would it > be possible to keep at least 2 packages in the repo for downgrading purposes? That's out of the scope of this bug, and it has been proposed many times on the list. Your best solution atm is to enable dnf cache when running on Rawhide. Then all the RPMs you installed in the past should be available to you locally. (In reply to Vít Ondruch from comment #17) > Anyway, this kind of bugs is pretty annoying, because it even prevented me > to use the text console, since the display server was restarting all the > time and it somehow gradually influenced all the text consoles. Is there a > chance to handle such issues more gracefully? E.g. Degrade to > multi-user.target or something just a bit better than constantly restarting > display server? From what I've seen, Petr Schindler wasn't affected by this. Please file a bug/RFE in https://bugzilla.gnome.org/ . Display restart loops should be detected, but it seems it doesn't always work.
(In reply to Jakub from comment #18) > is there a way to obtain the mutter-3.23.1-2.fc26.x86_64 package? would it > be possible to keep at least 2 packages in the repo for downgrading purposes? https://bugzilla.redhat.com/show_bug.cgi?id=1397174
I've cleared the #1401231 logjam and a rebuild of gnome-shell is running: http://koji.fedoraproject.org/koji/buildinfo?buildID=823202 . Hopefully that should resolve this.
System is bootable with gnome-shell from comment 22 and matching mutter.
Closing then.