guake crashed with SIGSEGV in XInternAtom()

Bug #1040854 reported by Rainer Rohde
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
guake (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Happens just after logging in...

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: guake 0.4.3-3
ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2
Uname: Linux 3.5.0-11-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.5.1-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Thu Aug 23 15:00:02 2012
ExecutablePath: /usr/bin/guake
InterpreterPath: /usr/bin/python2.7
ProcCmdline: python /usr/bin/guake
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f7e79e3cf8a <XInternAtom+26>: mov 0x968(%rdi),%rax
 PC (0x7f7e79e3cf8a) ok
 source "0x968(%rdi)" (0x00000968) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: guake
StacktraceTop:
 XInternAtom () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
 g_object_newv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_new_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: guake crashed with SIGSEGV in XInternAtom()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Rainer Rohde (rainer-rohde) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 XInternAtom (dpy=dpy@entry=0x0, name=name@entry=0x7fff10b6b6a0 "_NET_SYSTEM_TRAY_S0", onlyIfExists=onlyIfExists@entry=0) at ../../src/IntAtom.c:174
 gtk_tray_icon_constructed (object=0x28f7770) at /build/buildd/gtk+2.0-2.24.11/gtk/gtktrayicon-x11.c:148
 g_object_newv (object_type=1, object_type@entry=43028960, n_parameters=n_parameters@entry=1, parameters=parameters@entry=0x291b570) at /build/buildd/glib2.0-2.33.10/./gobject/gobject.c:1746
 g_object_new_valist (object_type=object_type@entry=43028960, first_property_name=first_property_name@entry=0x7f7e7b39740f "title", var_args=var_args@entry=0x7fff10b6b948) at /build/buildd/glib2.0-2.33.10/./gobject/gobject.c:1835
 g_object_new (object_type=43028960, first_property_name=first_property_name@entry=0x7f7e7b39740f "title") at /build/buildd/glib2.0-2.33.10/./gobject/gobject.c:1550

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 guake (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in guake (Ubuntu):
status: New → Confirmed
Revision history for this message
Robert Matusewicz (matekm) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running only once:
apport-collect 1040854 and any other logs that are relevant for this particular issue.

Changed in guake (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for guake (Ubuntu) because there has been no activity for 60 days.]

Changed in guake (Ubuntu):
status: Incomplete → Expired
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.