gnome-shell crashed with signal 5 in _XReply()

Bug #1727079 reported by andre
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
New
Medium
Unassigned

Bug Description

Sorry, that's all i got.

To help, what i was doing was trying to enable my nvidia graphics driver. for some reason, it seems that the new gnome desktop keeps the gpu active all the time, meaning the fan is firing up more than it should to cool it down. I was going to switch to power-saving mode into the Nvidia x server settings applet which works, but you cannot open the applet again after a reboot to turn the gpu back on.

I had to remove the nvidia driver > remove local cached/downloaded using the GRUB manager at start up as system wouldn't boot > re-enable driver > rebooted > back in business.

I will leave it on and see how it settles in, but now i have my applet back :)

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu4
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: GNOME-Greeter:GNOME
Date: Tue Oct 24 01:33:28 2017
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:

InstallationDate: Installed on 2017-10-23 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_GB.UTF-8
 SHELL=/bin/false
Signal: 5
SourcePackage: gnome-shell
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 XSync () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
Title: gnome-shell crashed with signal 5 in _XReply()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
andre (dre109offishall) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? () at wayland/meta-xwayland.c:56 from /tmp/apport_sandbox_eNgDg5/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
 ?? ()
 _XIOError (dpy=dpy@entry=0x560a941df070) at ../../src/XlibInt.c:1469
 _XReply (dpy=dpy@entry=0x560a941df070, rep=rep@entry=0x7ffd9fed6ac0, extra=extra@entry=0, discard=discard@entry=1) at ../../src/xcb_io.c:704
 XSync (dpy=0x560a941df070, discard=discard@entry=0) at ../../src/Sync.c:44

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-shell (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1556601, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

information type: Private → Public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.