GNOME Shell

gnome-shell crashed with signal 5 in _cogl_set_error()

Bug #1184823 reported by Tim Lunn on 2013-05-28

This bug affects 2 people

Affects		Status	Importance	Assigned to	Milestone
	GNOME Shell	New	Critical	gnome-bugs #723259
	gnome-shell (Ubuntu)	Invalid	Undecided	Unassigned

Bug Description

ProblemType: CrashDistroRelease: Ubuntu 13.10
Package: gnome-shell 3.8.2-0ubuntu1~raring1.2 [origin: LP-PPA-gnome3-team-gnome3-staging]
ProcVersionSignature: Ubuntu 3.9.0-2.6-generic 3.9.2
Uname: Linux 3.9.0-2-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.10.2-0ubuntu1
Architecture: amd64
CrashDB: ubuntu
Date: Tue May 28 11:27:06 2013
DisplayManager: gdm
ExecutablePath: /usr/bin/gnome-shell
ExecutableTimestamp: 1369606420
InstallationDate: Installed on 2012-09-23 (247 days ago)
InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Alpha amd64(20120922)
MarkForUpload: True
ProcCmdline: gnome-shell --replace
ProcCwd: /home/darkness
Signal: 5SourcePackage: gnome-shell
StacktraceTop:
_cogl_set_error (error=error@entry=0x0, domain=<optimised out>, code=code@entry=0, format=format@entry=0x7f644889f8c8 "Failed to create an OpenGL framebuffer object") at ./cogl-error.c:78
_cogl_offscreen_gl_allocate (offscreen=0x39039c0, error=0x0) at ./driver/gl/cogl-framebuffer-gl.c:844
cogl_framebuffer_allocate (framebuffer=framebuffer@entry=0x39039c0, error=error@entry=0x0) at ./cogl-framebuffer.c:727
_cogl_framebuffer_gl_flush_state (draw_buffer=0x39039c0, read_buffer=0x39039c0, state=(COGL_FRAMEBUFFER_STATE_BIND | COGL_FRAMEBUFFER_STATE_VIEWPORT | COGL_FRAMEBUFFER_STATE_DITHER | COGL_FRAMEBUFFER_STATE_PROJECTION | COGL_FRAMEBUFFER_STATE_COLOR_MASK | COGL_FRAMEBUFFER_STATE_FRONT_FACE_WINDING)) at ./driver/gl/cogl-framebuffer-gl.c:311
_cogl_journal_flush (journal=0x3838da0) at ./cogl-journal.c:1313
Title: gnome-shell crashed with signal 5 in _cogl_set_error()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

See original description

Tags:

Revision history for this message

Tim Lunn (darkxst) wrote on 2013-05-28:

Dependencies.txt Edit (25.4 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (941 bytes, text/plain; charset="utf-8")
GsettingsChanges.txt Edit (373 bytes, text/plain; charset="utf-8")
ProcEnviron.txt Edit (103 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (105.4 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (830 bytes, text/plain; charset="utf-8")
Registers.txt Edit (668 bytes, text/plain; charset="utf-8")
RetraceOutdatedPackages.txt Edit (2.2 KiB, text/plain; charset="utf-8")
Stacktrace.txt Edit (5.6 KiB, text/plain; charset="utf-8")
StacktraceSource.txt Edit (4.2 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (19.8 KiB, text/plain; charset="utf-8")
XsessionErrors.txt Edit (33.0 KiB, text/plain; charset="utf-8")
gdmSessionLog.gz Edit (32.5 KiB, application/x-gzip)

information type:

Private → Public

Apport retracing service (apport) on 2013-05-28

tags:

removed: need-amd64-retrace

Revision history for this message

Launchpad Janitor (janitor) wrote on 2014-01-29:

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-shell (Ubuntu):
status:	New → Confirmed

Revision history for this message

aslam karachiwala (akwala) wrote on 2014-01-29:

apport-retrace_gnome-shell.txt Edit (20.5 MiB, text/plain)

I see similar behavior in Gnome 3.10, Ubuntu 13.10 (apport-retrace output attached):
=====
$ gnome-shell --replace
Window manager warning: IDLETIME counter not found
Window manager warning: IDLETIME counter not found
Window manager warning: IDLETIME counter not found
Window manager warning: IDLETIME counter not found
Window manager warning: IDLETIME counter not found
Window manager warning: IDLETIME counter not found
Window manager warning: IDLETIME counter not found
Window manager warning: IDLETIME counter not found
Gjs-Message: JS LOG: GNOME Shell started at Wed Jan 29 2014 16:22:47 GMT-0500 (EST)
Fontconfig error: "/etc/fonts/conf.d/65-khmer.conf", line 14: out of memory
Fontconfig error: "/etc/fonts/conf.d/65-khmer.conf", line 23: out of memory
Fontconfig error: "/etc/fonts/conf.d/65-khmer.conf", line 32: out of memory

(gnome-shell:10226): Gjs-WARNING **: JS ERROR: could not get remote objects for service org.gnome.SettingsDaemon.Smartcard path /org/gnome/SettingsDaemon/Smartcard: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SettingsDaemon.Smartcard was not provided by any .service files
asyncCallback@/usr/share/gjs-1.0/overrides/Gio.js:84

(gnome-shell:10226): Cogl-ERROR **: Failed to create an OpenGL framebuffer object
Trace/breakpoint trap (core dumped)
=====

Tim Lunn (darkxst) on 2014-01-29

description:

updated

Bug Watch Updater (bug-watch-updater) on 2014-01-29

Changed in gnome-shell:
importance:	Unknown → Critical
status:	Unknown → New

aslam karachiwala (akwala) on 2014-01-30

tags:

added: cogl

Revision history for this message

Jeremy Bícha (jbicha) wrote on 2017-05-13:

Thank you for reporting this bug to Ubuntu. I apologize that we are not always to respond to bug reports promptly. Ubuntu 13.10 reached End of Life in 2014. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases

Please upgrade to Ubuntu 16.04 LTS and re-test. If the bug is still reproducible, increase the verbosity of the steps to recreate it so we can try again.

Do feel free to report any other bugs you may find.

Changed in gnome-shell (Ubuntu):
status:	Confirmed → Invalid

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

gnome-bugs #723259
[UNCONFIRMED] Edit

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

GNOME Shell

gnome-shell crashed with signal 5 in _cogl_set_error()

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches