Arch Linux

smakked

Member

From: Gold Coast , Australia

Registered: 2008-08-14

Posts: 420

[SOLVED] [Gnome 3.8] Gnome shell segfaults

Having an issue here with gnome-shell

[ 2961.880512] traps: gnome-shell[2764] general protection ip:7fb6a45087d0 sp:7fffccda9438 error:0 in libglib-2.0.so.0.3600.1[7fb6a44d0000+fc000]
[ 2963.270402] systemd-journald[180]: Failed to write entry, ignoring: Argument list too long
[ 3077.748064] gnome-shell[4230]: segfault at 1 ip 00007fb593d087d0 sp 00007fff9c84c4b8 error 4 in libglib-2.0.so.0.3600.1[7fb593cd0000+fc000]
[ 3079.148914] systemd-journald[180]: Failed to write entry, ignoring: Argument list too long
[31220.748188] gnome-shell[4316]: segfault at 1 ip 00007f693fe707d0 sp 00007fffd95b02b8 error 4 in libglib-2.0.so.0.3600.1[7f693fe38000+fc000]
[31222.124573] systemd-journald[180]: Failed to write entry, ignoring: Argument list too long
[39447.062449] systemd-journald[180]: Failed to write entry, ignoring: Argument list too long
[39755.970576] traps: gnome-shell[5083] general protection ip:7fddbe8d87d0 sp:7fffa7ebf1c8 error:0 in libglib-2.0.so.0.3600.1[7fddbe8a0000+fc000]
[39757.250143] systemd-journald[180]: Failed to write entry, ignoring: Argument list too long
[40816.727580] gnome-shell[6675]: segfault at 1 ip 00007f02f0f707d0 sp 00007fffadd54b48 error 4 in libglib-2.0.so.0.3600.1[7f02f0f38000+fc000]
[40818.033701] systemd-journald[180]: Failed to write entry, ignoring: Argument list too long

Not sure what that means exactly , anyone having this?

Last edited by smakked (2013-04-18 11:43:24)

---

Certified Android Junkie
Arch 64

smakked

Member

From: Gold Coast , Australia

Registered: 2008-08-14

Posts: 420

Re: [SOLVED] [Gnome 3.8] Gnome shell segfaults

Seems to be ok now, just done a Syu which pulled down a new build of xorg-server and gdm and seems ok no issue

---

Certified Android Junkie
Arch 64

smakked

Member

From: Gold Coast , Australia

Registered: 2008-08-14

Posts: 420

Re: [SOLVED] [Gnome 3.8] Gnome shell segfaults

This is what pacman pulled down and all is well now , so not sure what it was

[2013-04-18 11:54] [PACMAN] Running 'pacman -Syu'
[2013-04-18 11:54] [PACMAN] synchronizing package lists
[2013-04-18 11:54] [PACMAN] starting full system upgrade
[2013-04-18 11:55] [PACMAN] upgraded apr-util (1.5.1-1 -> 1.5.2-1)
[2013-04-18 11:55] [PACMAN] upgraded clutter (1.14.0-1 -> 1.14.2-1)
[2013-04-18 11:55] [PACMAN] upgraded xorg-server-common (1.14.0-2 -> 1.14.1-1)
[2013-04-18 11:55] [PACMAN] upgraded xorg-server (1.14.0-2 -> 1.14.1-1)
[2013-04-18 11:55] [PACMAN] upgraded libgdm (3.8.1-1 -> 3.8.1.1-1)
[2013-04-18 11:55] [PACMAN] upgraded gdm (3.8.1-1 -> 3.8.1.1-1)
[2013-04-18 11:55] [PACMAN] upgraded gtkmm3 (3.7.12-1 -> 3.8.0-1)
[2013-04-18 11:55] [PACMAN] upgraded libpst (0.6.54-4 -> 0.6.58-1)
[2013-04-18 11:56] [PACMAN] upgraded linux (3.8.7-1 -> 3.8.8-1)
[2013-04-18 11:56] [PACMAN] upgraded lirc-utils (1:0.9.0-41 -> 1:0.9.0-42)
[2013-04-18 11:56] [PACMAN] upgraded modemmanager (0.7.990-1 -> 0.7.990-2)
[2013-04-18 11:56] [PACMAN] upgraded notification-daemon (0.7.6-1 -> 0.7.6-2)
[2013-04-18 11:56] [PACMAN] upgraded poppler (0.22.3-1 -> 0.22.3-2)
[2013-04-18 11:56] [PACMAN] upgraded poppler-glib (0.22.3-1 -> 0.22.3-2)

---

Certified Android Junkie
Arch 64

smakked

Member

From: Gold Coast , Australia

Registered: 2008-08-14

Posts: 420

Re: [SOLVED] [Gnome 3.8] Gnome shell segfaults

Will mark as solved not one issue since the updates

---

Certified Android Junkie
Arch 64

bwat47

Member

Registered: 2009-10-07

Posts: 638

Re: [SOLVED] [Gnome 3.8] Gnome shell segfaults

I still get this same segfault at random even with all latest updates. The segfault message in my log is the exact same glib one in your post It happens pretty rarely at least.

Jul 04 23:14:08 arch-lemu4 kernel: gnome-shell[516]: segfault at 1 ip 00007f16f3afa670 sp 00007fffd066a9b8 error 4 in libglib-2.0.so.0.3600.3[7f16f3ac2000+fc000]

Last edited by bwat47 (2013-07-05 03:37:45)

bmanuel

Member

Registered: 2011-10-06

Posts: 106

Re: [SOLVED] [Gnome 3.8] Gnome shell segfaults

For me it happens at least 2 times per day, on 2 different machines..