Gala

gala crashed with SIGSEGV in g_closure_invoke()

Bug #1068018 reported by jordi
70
This bug affects 16 people
Affects Status Importance Assigned to Milestone
Gala
Expired
High
Unassigned

Bug Description

When starts

ProblemType: Crash
DistroRelease: elementary 0.2
Package: gala 0.1-0~r247+pkg14~precise1 [origin: LP-PPA-elementary-os-daily]
ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30
Uname: Linux 3.2.0-32-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.0.1-0ubuntu13+elementary3~precise1
Architecture: amd64
CrashDB: gala
Date: Thu Oct 18 10:00:59 2012
ExecutablePath: /usr/bin/gala
InstallationMedia: elementary OS 0.2 "Luna" - Build amd64 LIVE Binary 20120817-21:58
ProcCmdline: gala
SegvAnalysis:
 Segfault happened at: 0x7fd19220336e: mov 0x18(%r12),%r14
 PC (0x7fd19220336e) ok
 source "0x18(%r12)" (0x00000018) not located in a known VMA region (needed readable region)!
 destination "%r14" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gala
StacktraceTop:
 ?? () from /usr/lib/libgranite.so.0
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gala crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
jordi (jjuvilla) wrote :
Revision history for this message
RabbitBot (rabbitbot-a) wrote :

StacktraceTop:
 ?? ()
 ?? ()
 ?? ()

Revision history for this message
RabbitBot (rabbitbot-a) wrote : Stacktrace.txt
Revision history for this message
RabbitBot (rabbitbot-a) wrote : ThreadStacktrace.txt
Changed in gala:
status: New → Invalid
Revision history for this message
RabbitBot (rabbitbot-a) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

outdated debug symbol package for fontconfig: package version 2.8.0-3ubuntu9.1 dbgsym version 2.8.0-3ubuntu9
libgranite0 version 0.2-0~r415+pkg31~precise1 required, but 0.2-0~r416+pkg31~precise1 is available
outdated debug symbol package for libmutter0: package version 3.4.1-0ubuntu99~elementary2 dbgsym version 3.4.1-0ubuntu1
outdated debug symbol package for dbus: package version 1.4.18-1ubuntu1.3 dbgsym version 1.4.18-1ubuntu1
outdated debug symbol package for passwd: package version 1:4.1.4.2+svn3283-3ubuntu5.1 dbgsym version 1:4.1.4.2+svn3283-3ubuntu5
outdated debug symbol package for libdbus-1-3: package version 1.4.18-1ubuntu1.3 dbgsym version 1.4.18-1ubuntu1
outdated debug symbol package for libcups2: package version 1.5.3-0ubuntu4 dbgsym version 1.5.2-9ubuntu1
libc-bin version 2.15-0ubuntu10.2 required, but 2.15-0ubuntu10.3 is available
outdated debug symbol package for libc-bin: package version 2.15-0ubuntu10.3 dbgsym version 2.15-0ubuntu10
outdated debug symbol package for coreutils: package version 8.13-3ubuntu3.1 dbgsym version 8.13-3ubuntu3
outdated debug symbol package for dbus-x11: package version 1.4.18-1ubuntu1.3 dbgsym version 1.4.18-1ubuntu1
multiarch-support version 2.15-0ubuntu10.2 required, but 2.15-0ubuntu10.3 is available
libc6 version 2.15-0ubuntu10.2 required, but 2.15-0ubuntu10.3 is available
outdated debug symbol package for gvfs-libs: package version 1.12.1-0ubuntu1.1 dbgsym version 1.12.1-0ubuntu1

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags: removed: need-amd64-retrace
Sergey "Shnatsel" Davidoff (shnatsel)
information type: Private → Public
Revision history for this message
Eric Karnes (karneseric) wrote :

Wondering why this is invalid. just loaded up luna beta 1 on my laptop and got this. All packages are up to date

Changed in gala:
status: Invalid → Confirmed
Cody Garver (codygarver)
Changed in gala:
milestone: none → 0.3-beta1
importance: Undecided → High
status: Confirmed → Incomplete
Revision history for this message
Zygmunt Krynicki (zyga) wrote :

I just got this while dragging windows between workspaces. Fully up-to-date as of this moment.

Cody Garver (codygarver)
Changed in gala:
status: Incomplete → Confirmed
Cody Garver (codygarver)
Changed in gala:
milestone: 0.3-beta1 → luna-rc1
Revision history for this message
Tom Beckmann (tombeckmann) wrote :

The information here is unfortunately very insufficient to effectively debug this.

When exactly is this crash happening?
@jordi, you said on startup? Right when you logged in or a little afterwards?
@Eric, same question for you.
@Zygmunt, we recently had an update in that area, can you still reproduce this issue?

Also it'd be great if anyone of you could catch the crash in gdb and get us a backtrace that is actually usable.

I'll detach the bug from the milestone until we're able to really work on it.

Changed in gala:
milestone: luna-rc1 → none
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Gala because there has been no activity for 60 days.]

Changed in gala:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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