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

Bug #1296113 reported by NeLaS
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu GNOME
New
Undecided
Unassigned

Bug Description

Happened after restart, I was trying to activate a VPN. Not sure if is related...

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: gnome-shell 3.10.4-0ubuntu1~saucy1 [origin: LP-PPA-gnome3-team-gnome3]
ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5
Uname: Linux 3.11.0-19-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
AssertionMessage: *** longjmp causes uninitialized stack frame ***: /usr/bin/gnome-shell terminated
Date: Sat Mar 22 19:20:24 2014
DisplayManager: gdm
ExecutablePath: /usr/bin/gnome-shell
InstallationDate: Installed on 2012-09-29 (538 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
MarkForUpload: True
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 PATH=(custom, user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: gnome-shell
StacktraceTop:
 __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7fbd56fb1f10 "*** %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=0x400f480, 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: Upgraded to saucy on 2013-10-18 (154 days ago)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo vboxusers
gdmSessionLog:
 /etc/gdm/Xsession: Beginning session setup...
 localuser:nelas being added to access control list
 localuser:nelas 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
NeLaS (organelas) wrote :
Revision history for this message
Ubuntu GNOME (ug-bot) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1253723, so 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. Please continue to report any other bugs you may find.

information type: Private → Public
tags: removed: need-amd64-retrace
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.