gnome-shell assert failure: *** longjmp causes uninitialized stack frame ***: /usr/bin/gnome-shell terminated

Bug #1253723 reported by Matthew Dobson
104
This bug affects 14 people
Affects Status Importance Assigned to Milestone
Ubuntu GNOME
New
Undecided
Unassigned

Bug Description

This seems to happen if I use Super and type a command before my wifi connects. The shell hangs for several seconds, followed by the crash.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: gnome-shell 3.10.1-0ubuntu1~saucy1 [origin: LP-PPA-gnome3-team-gnome3-staging]
ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
Uname: Linux 3.11.0-13-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
AssertionMessage: *** longjmp causes uninitialized stack frame ***: /usr/bin/gnome-shell terminated
CrashCounter: 1
Date: Thu Nov 21 18:16:14 2013
DisplayManager: gdm
ExecutablePath: /usr/bin/gnome-shell
InstallationDate: Installed on 2013-10-30 (22 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64+mac (20131016.1)
MarkForUpload: True
ProcCmdline: /usr/bin/gnome-shell
Signal: 6
SourcePackage: gnome-shell
StacktraceTop:
 __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7f81dbcaff10 "*** %s ***: %s terminated\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:199
 __GI___fortify_fail (msg=<optimized out>) at fortify_fail.c:37
 ____longjmp_chk () at ../sysdeps/unix/sysv/linux/x86_64/____longjmp_chk.S:100
 __longjmp_chk (env=0x380e9d0, val=<optimized out>) at ../setjmp/longjmp.c:39
 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
Title: gnome-shell assert failure: *** longjmp causes uninitialized stack frame ***: /usr/bin/gnome-shell terminated
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
gdmSessionLog:
 /etc/gdm/Xsession: Beginning session setup...
 localuser:mcd being added to access control list
 localuser:mcd being added to access control list
 Script for cjkv started at run_im.
 Script for default started at run_im.

Revision history for this message
Matthew Dobson (matthew-dobson) wrote :
Revision history for this message
Ubuntu GNOME (ug-bot) wrote :

StacktraceTop:
 sigorset (dest=0x6d2, left=0x6d2, right=0x6) at sigorset.c:30
 __GI_qsort_r (b=0x6d2, n=1746, s=6, cmp=0xffffffffffffffff, arg=0x0) at msort.c:175
 __GI___vfwprintf_chk (fp=<optimized out>, flag=<optimized out>, format=<optimized out>, ap=<optimized out>) at vfwprintf_chk.c:41
 _L_unlock_161 () from /home/darkxst/gnome3-amd64/lib/x86_64-linux-gnu/libc.so.6
 _IO_acquire_lock_clear_flags2_fct (p=<optimized out>) at ../libio/libioP.h:915

Revision history for this message
Ubuntu GNOME (ug-bot) wrote : Stacktrace.txt
Revision history for this message
Ubuntu GNOME (ug-bot) wrote : StacktraceSource.txt
Revision history for this message
Ubuntu GNOME (ug-bot) wrote : ThreadStacktrace.txt
tags: removed: need-amd64-retrace
Tim Lunn (darkxst)
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.