On Thu, 24 Aug 2017 13:11:49 +0200 "Cliff McDiarmid" <cliffhan...@gardener.com> wrote:
> gnome-session-f[3065]: segfault at 0 ip 00007f17482e79a9 sp 00007ffcfe694900 error 4 in libgtk-3.so.0.2200.4[7f1748013000+6e5000] I did a search and here are some more things to try. It would be very helpful if you could produce a log like the "bug.log" posted by Pierre Durand (Pierrre): https://bugs.archlinux.org/task/51791?project=1&cat[0]=2&string=mutter However that log is from journalctl, which does requires systemd. The mutter issue was "fixed" by reverting this change: http://git.net/ml/commits.gnome/2016-11/msg00443.html?PageSpeed=noscript It also may be related to a bug related to libinput: https://bugs.freedesktop.org/show_bug.cgi?id=99245 "I can not get gnome or even gdm started since I get a segfault for gnome-session. I traced the issue down to libinput switch from synaptics. Switching back to synaptics+evdev resolves the issue. This is what I see in journal ..." and so switching back to Xorg evdev might be something to try. There is also: https://bugs.archlinux.org/index.php?do=details&task_id=51908 "Command `gdk-pixbuf-query-loaders --update-cache` allowed me to login into gnome-session." Note the gotcha mention in the posts: "The fail whale screen (gnome-session-failed) crashing is most likely a red herring. Something must have caused the screen to be launched in the first place; perhaps the components that gnome-session attempted to launch crashed similarly. That said, the fail whale screen shouldn't be crashing, either, so that's another issue." "Don't focus on the backtraces. You're debugging the 'Oh no something is wrong' screen that should show up when gnome can't start. Look at journalctl logs why gnome-session is not working." So, there also could be two different crashes going on - the initial one and then a later crash of the "fail whale" screen: https://bugzilla.gnome.org/show_bug.cgi?id=775463 where Ray Strode has a patch that fixes the "fail whale" crash: https://bugzilla.gnome.org/attachment.cgi?id=352892&action=diff Another bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1384508 suggests trying gsettings set org.gnome.SessionManager auto-save-session false Cheers, Mike Shell -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
