gnome desktop cannot be started due to the following issue (libgtk-3)

kalen · 2017-01-09 11:56:43

Hi there!

Today, I updated the entire system with

pacman -Syu

and I'm still getting there segfaults with Gnome under Wayland (and Xorg).

I've tried downgrading Mutter, updating the microcode, reinstalling Gnome and cleaning the configurations. Does anyone have other suggestions?

Nolchetyre · 2017-01-10 17:18:20

kalen wrote:

Hi there!
Today, I updated the entire system with
pacman -Syu
and I'm still getting there segfaults with Gnome under Wayland (and Xorg).
I've tried downgrading Mutter, updating the microcode, reinstalling Gnome and cleaning the configurations. Does anyone have other suggestions?

Same here, i've tried to downgrade mutter, gdm, gnome packages =\

gururise · 2017-01-10 18:39:13

I'm running an Intel i7-3770k and Nvidia 750ti video card. I have the same problem, and I already have the latest intel microcode installed. I tried downgrading mutter to no avail... Can anyone help?

I've tried gnome on Xorg, Gnome, and Gnome Classic and none will let me start the desktop.

Last edited by gururise (2017-01-10 18:54:28)

nirvana1289 · 2017-01-11 14:10:27

Same here, tried same solutions. I also tried to downgrade gtk3 (that was updated recently).

cml · 2017-01-11 16:10:50

Same problem since today. I'm running on AMD (both cpu and gpu). Switching between Wayland and Xorg doesn't show any effects.

gururise · 2017-01-11 16:41:35

Looks like someone posted a bug report for this issue here: https://bugs.archlinux.org/index.php?do … k_id=51908

If you are having this problem, you may want to vote for the bug.

Last edited by gururise (2017-01-11 17:23:17)

grim_sage · 2017-01-12 07:05:23

Hello. I'm not sure if this is related to the topic but I've found similar problem on BudgieWM after setting kernel paramater kernel.kptr_restrict = 1 and installing hidepid (I've been following security guidelines https://wiki.archlinux.org/index.php/Se … filesystem not sure which one caused segfault) .
My error message looks like this:
kernel: gnome-session-f[1245]: segfault at 0 ip 00007fac13767cc9 sp 00007ffc94002fe0 error 4 in libgtk-3.so.0.2200.6[7fac13485000+6fa000]

Last edited by grim_sage (2017-01-12 07:06:14)

nirvana1289 · 2017-01-12 07:46:57

At least I found a way to login on my system: I have restored all packages to a specific date and now I can login with Classic and on Xorg, but not on Wayland. In particular I have restored to 2017/01/06.

Packages that may be responsible for the bug (that changed and are connected to GNOME in some way AFAIK) are:

gdk-pixbuf2
gnome-online-accounts
systemd and libsystemd
xorg-mkfontdir
fontconfig
harfbuzz
libpng
libuv
zeitgeist

I don't see other packages that can be considered responsible for the bug...

Unfortunately I cannot test more in this days...

Last edited by nirvana1289 (2017-01-12 08:00:07)

Nolchetyre · 2017-01-12 09:01:13

Can't login into gnome (pushes back to login screen). I'm able to login another WM, like i3.

journalctl -xk
kernel: gnome-session-f[3375]: segfault at 0 ip 00007f2deb90ecc9 sp 00007fff724f72b0 error 4 in libgtk-3.so.0.2200.6[7f2deb62c000+6fa000]

coredump process
Stack trace of thread 3375:
#0 0x00007f2deb90ecc9 n/a (libgtk-3.so.0)
#1 0x00007f2deb7aa9a8 n/a (libgtk-3.so.0)
#2 0x00007f2deb7bfa94 n/a (libgtk-3.so.0)
#3 0x00007f2deb7abcdc n/a (libgtk-3.so.0)
#4 0x00007f2deb7bf9bc n/a (libgtk-3.so.0)
#5 0x00007f2deb7bfa15 n/a (libgtk-3.so.0)
#6 0x00007f2deb7ac642 n/a (libgtk-3.so.0)
#7 0x00007f2deb11730f g_type_create_instance (libgobject-2.0.so.0)
#8 0x00007f2deb0f91fb n/a (libgobject-2.0.so.0)
#9 0x00007f2deb0fac0d g_object_newv (libgobject-2.0.so.0)
#10 0x00007f2deb0fb3c4 g_object_new (libgobject-2.0.so.0)
#11 0x00007f2deb7c7efa n/a (libgtk-3.so.0)
#12 0x00007f2deb9a5cb7 n/a (libgtk-3.so.0)
#13 0x00007f2deb11730f g_type_create_instance (libgobject-2.0.so.0)
#14 0x00007f2deb0f91fb n/a (libgobject-2.0.so.0)
#15 0x00007f2deb0fac0d g_object_newv (libgobject-2.0.so.0)
#16 0x00007f2deb0fb3c4 g_object_new (libgobject-2.0.so.0)
#17 0x0000000000401db3 n/a (gnome-session-failed)
#18 0x00007f2deaa53291 __libc_start_main (libc.so.6)
#19 0x00000000004021ba n/a (gnome-session-failed)

eKoeS · 2017-01-12 16:57:06

nirvana1289 wrote:

harfbuzz

Downgrading this package to version 1.3.4-1 worked for me.

Last edited by eKoeS (2017-01-12 16:57:25)

WorMzy · 2017-01-12 17:08:28

In that case I wonder how many of you are using the infinality packages that don't work with an up-to-date harfbuzz. Those of you who are, should check out the many topics about removing them and switching to the official repository packages.

Nolchetyre · 2017-01-12 17:50:22

I did, but completly switched to official. Same results.

amatriain · 2017-01-12 17:59:52

I'm having the same issue.

I did use infinality packages. I've removed their fontconfig and freetype2 packages and installed the ones from the official repos, but still gnome crashes on startup. Which other infinality packages should be removed?

For the moment it's fixed by rolling back all pacman updates to 2017-07-january.

nirvana1289 · 2017-01-12 18:28:23

WorMzy wrote:

In that case I wonder how many of you are using the infinality packages that don't work with an up-to-date harfbuzz. Those of you who are, should check out the many topics about removing them and switching to the official repository packages.

Never heard before about infinality, but I actually do have freetype2 in IgnorePkg for something, and I don't remember why :S

With harfbuzz and harfbuzz-icu in IgnorePkg, I successfully upgraded the system to current roll, but still Wayland does not work, only Xorg does.

WorMzy · 2017-01-12 18:37:55

nirvana1289 wrote:

WorMzy wrote:
In that case I wonder how many of you are using the infinality packages that don't work with an up-to-date harfbuzz. Those of you who are, should check out the many topics about removing them and switching to the official repository packages.
Never heard before about infinality, but I actually do have freetype2 in IgnorePkg for something, and I don't remember why :S
With harfbuzz and harfbuzz-icu in IgnorePkg, I successfully upgraded the system to current roll, but still Wayland does not work, only Xorg does.

Do you have the same problems if you update your whole system, freetype2 included?

eschwartz · 2017-01-12 20:06:38

If you have a broken freetype2 <-->gdk-pixbuf2 linkage when you upgrade gdk-pixbuf2 then the pacman hook which regenerates the cache will generate a broken cache, which breaks stuff -- this is already posted about, and rather than reinstalling gdk-pixbuf2 in a bubble you can simply re-run the hook command: `gdk-pixbuf-query-loaders --update-cache`

If anyone is is or was using infinality, this is the likely cause.

cris9288 · 2017-01-12 20:43:52

I can confirm that following this guide, as well as running the command mentioned by Eschwartz above allowed me to log back in to Gnome.

https://gist.github.com/cryzed/e002e705 … 9e748c5671

Nolchetyre · 2017-01-12 21:28:35

Confirm.
Command `gdk-pixbuf-query-loaders --update-cache` allowed me to login into gnome-session. For sure, I switched from infinality to official before.

Last edited by Nolchetyre (2017-01-12 21:33:23)

nirvana1289 · 2017-01-13 10:47:21

Confirm. It worked, releasing both freetype2 and harfbuzz

Scimmia · 2017-01-13 15:00:09

Then your issue is different than the OP.

Nolchetyre · 2017-01-13 20:04:16

But same error and behavior. Mates will search for a solution.

fisco · 2017-02-18 21:26:12

I can confirm that I encounter this segfault in libgtk-3 when I have aur/chrome-remote-desktop installed.
Remove chrome-remote-desktop and no segfault.

Last edited by fisco (2017-02-18 21:39:00)

kmiernik · 2017-04-06 17:00:45

I hope this will not be considered necrobumping but I have been hit yesterday by this issue. None of the solution in this thread worked. Only after looking around my system I have realized that my root partition is 100% full (I have root + home partition scheme). Removing some pacman cache actually cured the problem. So if you encounter this segfault/error message it may be as simple as that.

Arch Linux

#26 2017-01-09 11:56:43

Re: gnome desktop cannot be started due to the following issue (libgtk-3)

#27 2017-01-10 17:18:20

Re: gnome desktop cannot be started due to the following issue (libgtk-3)

#28 2017-01-10 18:39:13

Re: gnome desktop cannot be started due to the following issue (libgtk-3)

#29 2017-01-11 14:10:27

Re: gnome desktop cannot be started due to the following issue (libgtk-3)

#30 2017-01-11 16:10:50

Re: gnome desktop cannot be started due to the following issue (libgtk-3)

#31 2017-01-11 16:41:35

Re: gnome desktop cannot be started due to the following issue (libgtk-3)

#32 2017-01-12 07:05:23

Re: gnome desktop cannot be started due to the following issue (libgtk-3)

#33 2017-01-12 07:46:57

Re: gnome desktop cannot be started due to the following issue (libgtk-3)

#34 2017-01-12 09:01:13

Re: gnome desktop cannot be started due to the following issue (libgtk-3)

#35 2017-01-12 16:57:06

Re: gnome desktop cannot be started due to the following issue (libgtk-3)

#36 2017-01-12 17:08:28

Re: gnome desktop cannot be started due to the following issue (libgtk-3)

#37 2017-01-12 17:50:22

Re: gnome desktop cannot be started due to the following issue (libgtk-3)

#38 2017-01-12 17:59:52

Re: gnome desktop cannot be started due to the following issue (libgtk-3)

#39 2017-01-12 18:28:23

Re: gnome desktop cannot be started due to the following issue (libgtk-3)

#40 2017-01-12 18:37:55

Re: gnome desktop cannot be started due to the following issue (libgtk-3)

#41 2017-01-12 20:06:38

Re: gnome desktop cannot be started due to the following issue (libgtk-3)

#42 2017-01-12 20:43:52

Re: gnome desktop cannot be started due to the following issue (libgtk-3)

#43 2017-01-12 21:28:35

Re: gnome desktop cannot be started due to the following issue (libgtk-3)

#44 2017-01-13 10:47:21

Re: gnome desktop cannot be started due to the following issue (libgtk-3)

#45 2017-01-13 15:00:09

Re: gnome desktop cannot be started due to the following issue (libgtk-3)

#46 2017-01-13 20:04:16

Re: gnome desktop cannot be started due to the following issue (libgtk-3)

#47 2017-02-18 21:26:12

Re: gnome desktop cannot be started due to the following issue (libgtk-3)

#48 2017-04-06 17:00:45

Re: gnome desktop cannot be started due to the following issue (libgtk-3)

Board footer