Ubuntu
gnome-shell package

gnome-shell crashed with signal 5

Bug #1725906 reported by kosson on 2017-10-22

This bug report is a duplicate of: Bug #1691921: gnome-shell crashed with SIGTRAP in g_wakeup_new() from g_main_context_new() from g_dbus_connection_send_message_with_reply_sync() from g_dbus_connection_call_sync_internal() from g_dbus_connection_call_sync() ["Creating pipes for GWakeup: Too many open files\n"]. Edit Remove

10

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	gnome-shell (Ubuntu)	New	Medium	Unassigned

Bug Description

Computer freeze and than Gnome was restarted.

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: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: GNOME-Classic:GNOME
Date: Sun Oct 22 06:59:11 2017
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
ProcCmdline: /usr/bin/gnome-shell
Signal: 5
SourcePackage: gnome-shell
StacktraceTop:
() at /lib/x86_64-linux-gnu/libglib-2.0.so.0
g_main_context_new () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
g_dbus_connection_send_message_with_reply_sync () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
() at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
() at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: gnome-shell crashed with signal 5
UpgradeStatus: Upgraded to artful on 2017-10-20 (1 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Tags:

Revision history for this message

kosson (kosson) wrote on 2017-10-22:

#1

Dependencies.txt Edit (21.9 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (621 bytes, text/plain; charset="utf-8")
GsettingsChanges.txt Edit (1.6 KiB, text/plain; charset="utf-8")
JournalErrors.txt Edit (137.6 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (1.0 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (290 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (149.3 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (1.3 KiB, text/plain; charset="utf-8")
Registers.txt Edit (663 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (2.0 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (36.8 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2017-10-22: Stacktrace.txt

#2

Stacktrace.txt Edit (16.3 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2017-10-22: StacktraceSource.txt

#3

StacktraceSource.txt Edit (7.1 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2017-10-22: StacktraceTop.txt

#4

StacktraceTop.txt Edit (1.4 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2017-10-22: ThreadStacktrace.txt

#5

ThreadStacktrace.txt Edit (61.5 KiB, text/plain)

Changed in gnome-shell (Ubuntu):
importance:	Undecided → Medium
tags:	removed: need-amd64-retrace

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2017-10-23:

#6

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 1691921, 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

Report a bug

This report contains Public information

Everyone can see this information.

Duplicate of bug #1691921 Remove

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

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