Ubuntu
consolekit package

console-kit-daemon crashed with SIGSEGV in g_cclosure_marshal_VOID()

Bug #1035017 reported by Fabio Marconi
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
consolekit (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Hallo
running a live session, clicked nautilus icon and this appear.
Thanks
Fabio

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: consolekit 0.4.5-3
ProcVersionSignature: Ubuntu 3.5.0-8.8-generic 3.5.0
Uname: Linux 3.5.0-8-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.4-0ubuntu6
Architecture: amd64
CasperVersion: 1.320
Date: Thu Aug 9 17:00:10 2012
ExecutablePath: /usr/sbin/console-kit-daemon
LiveMediaBuild: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120809.1)
ProcCmdline: /usr/sbin/console-kit-daemon --no-daemon
ProcEnviron:

SegvAnalysis:
 Segfault happened at: 0x40ee2e: mov 0x28(%rbx),%rdi
 PC (0x0040ee2e) ok
 source "0x28(%rbx)" (0xaaaaaaaaaaaaaad2) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: consolekit
StacktraceTop:
 ?? ()
 g_cclosure_marshal_VOID(int0_t, void) () 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: console-kit-daemon crashed with SIGSEGV in g_cclosure_marshal_VOID()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
Fabio Marconi (fabiomarconi) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 job_completed (job=0x146bd90, status=<optimized out>, data=0x1477490) at ck-session-leader.c:402
 g_cclosure_marshal_VOID__UINT (closure=0x143ade0, return_value=<optimized out>, n_param_values=<optimized out>, param_values=0x33, invocation_hint=0x143adf0, marshal_data=0x20) at /build/buildd/glib2.0-2.33.8/./gobject/gmarshal.c:432
 ?? ()
 ?? ()
 ?? ()

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 consolekit (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) 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:

libglib2.0-0 version 2.33.6-1 required, but 2.33.8-1 is available
outdated debug symbol package for initscripts: package version 2.88dsf-13.10ubuntu13 dbgsym version 2.88dsf-13.10ubuntu11.1
outdated debug symbol package for module-init-tools: package version 3.16-1ubuntu3 dbgsym version 3.16-1ubuntu2

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
Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

dup of bug 810208 ?

Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1035017

tags: added: iso-testing
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.