gnome-shell int trap 3 after update to gnome 3.16

481 views
Skip to first unread message

Dennis Mungai

unread,
Apr 14, 2015, 12:59:16 AM4/14/15
to Nairobi Linux Users Group
Hey guys,

So I upgraded my Arch box today ( Massive update, I guess, more than 1
GB downloaded) and now, on boot, I'm greeted with that error in dmesg.

Google's not much help, so, if you're experiencing a similar problem
and have a solution, please help!

-D

Alan Orth

unread,
Apr 14, 2015, 3:19:12 AM4/14/15
to nairobi-gnu
Sorry, br0heim. My current Arch box doesn't run GNOME, and my Fedora 21 box is on GNOME 3.14. What about checking the Arch BBS?

Alan


-D

--
You received this message because you are subscribed to the Google Groups "Nairobi GNU/Linux User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nairobi-gnu...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
Alan Orth
alan...@gmail.com
https://alaninkenya.org
https://mjanja.ch
"In heaven all the interesting people are missing." -Friedrich Nietzsche
GPG public key ID: 0x8cb0d0acb5cd81ec209c6cdfbd1a0e09c2f836c0

James Oguya

unread,
Apr 14, 2015, 4:40:36 AM4/14/15
to nairo...@googlegroups.com
@mungai More info about the error, please.
James Oguya

Dennis Mungai

unread,
Apr 14, 2015, 5:23:59 AM4/14/15
to Nairobi Linux Users Group
Thanks guys.

So, James, here's the log from dmesg:

traps: gnome-shell[1111] trap int3 ip:7ff0d56f0ac0 sp:7ffd04087290 error:0
[ 64.352668] traps: gnome-shell[1117] trap int3 ip:7fbab311eac0
sp:7ffecc805a00 error:0


My display manager (ATM) is KDM. KDM can launch both Kodi Desktop
(previously XBMC) and KDE successfully, but not Gnome.
GDM is a fail whale for now. Gets straight to the "Gnome has
experienced a problem and cant recover, please contact your system
administrator" with a huge log-off button dab smack at the bottom.
Currently disabled.
LightDM can start up and launch both KDE and Kodi desktop flawlessly.
Currently disabled as well.

Thats' it...

Anthony Oduor

unread,
Apr 14, 2015, 7:06:50 AM4/14/15
to Nairobi Linux Users Group
I got the 3.16 update a few days ago working well with all the bells and whistles! :)

Never encountered such an error but I could guess it to be a gdm / xorg-server related. If you can get to shell, try starting gdm manually or check it's settings.

Dennis Mungai

unread,
Apr 14, 2015, 7:11:18 AM4/14/15
to Nairobi Linux Users Group
I'm guessing you're on Arch Linux, right?

Also, my setup has several Xorg.conf.d entries (related to touchpad &
bbswitch for Optimus GPU switching).

Will keep researching. For now, stuck in KDE. And it suxs.

Dennis Mungai

unread,
Apr 14, 2015, 7:51:26 AM4/14/15
to Nairobi Linux Users Group
So guys,

I've tracked this down to a bug in Mutter > 3.14 on Optimus systems
that use xrandr to offload OGL contexts to the NVIDIA GPU.

See this new bug report here:

https://bugzilla.gnome.org/show_bug.cgi?id=742372

Sourced from:

https://bugs.archlinux.org/task/42452

And linked from:

https://bbs.archlinux.org/viewtopic.php?pid=1467820#p1467820

States the problem definition.

Workaround: Switch permanently to bbswitch, don't use xrandr to
offload sinks with mutter.

Marked as solved.

Anthony Oduor

unread,
Apr 14, 2015, 8:15:43 AM4/14/15
to Nairobi Linux Users Group
Nice, yeah am on Arch too. Good to know. When you mentioned xrandr I remembered a script I run at start to force 1600x1200 resolution on my  secondary monitor. Wonderful tool, before I could only get a lame 1024x768 on the 21".

Cheers!

Dennis Mungai

unread,
Apr 14, 2015, 9:25:46 AM4/14/15
to Nairobi Linux Users Group
Anthony,

Up until lrecently, I had to use xrandr and cvt to calculate and apply
a modeline (1920p) for a weird Benq monitor over eDP because neither
the display vendor nor the driver (i915) bothered implementing reading
the EDIDs properly.

This is in 2014. 2014!!! And we're still calculating modelines...like wtf?

Anthony Oduor

unread,
Apr 14, 2015, 9:58:43 AM4/14/15
to Nairobi Linux Users Group
Dennis -

LOL, thankfully I never had to go deep into the display innards to get it working. True, that's a shame considering where Linux stands now... like everything else just works :). Mine's a dated Viewsonic and all is well besides the difficulty picking up possible resolutions. Now that you've made trips into the display innards :) , it would be a good time we contribute on those neglected displays.
Reply all
Reply to author
Forward
0 new messages