Ubuntu
indicator-datetime package

indicator-datetime-service crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()

Bug #1440829 reported by Alexander Langanke
26
This bug affects 4 people
Affects Status Importance Assigned to Milestone
indicator-datetime (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Happened after Login

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: indicator-datetime 13.10.0+15.04.20150331-0ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
Uname: Linux 3.19.0-12-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.17-0ubuntu1
Architecture: amd64
Date: Mon Apr 6 19:52:48 2015
ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service
InstallationDate: Installed on 2015-03-21 (16 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150321)
ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service
SegvAnalysis:
 Segfault happened at: 0x7f349fc1f435 <g_type_check_instance_is_fundamentally_a+5>: mov (%rdi),%rax
 PC (0x7f349fc1f435) ok
 source "(%rdi)" (0x72747365645f6c6c) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: indicator-datetime
StacktraceTop:
 g_type_check_instance_is_fundamentally_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
Title: indicator-datetime-service crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
Alexander Langanke (alexlanganke) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_type_check_instance_is_fundamentally_a (type_instance=type_instance@entry=0x72747365645f6c6c, fundamental_type=fundamental_type@entry=80) at /build/buildd/glib2.0-2.44.0/./gobject/gtype.c:4026
 g_object_unref (_object=0x72747365645f6c6c) at /build/buildd/glib2.0-2.44.0/./gobject/gobject.c:3071
 on_connection_disconnected (connection=<optimized out>, remote_peer_vanished=<optimized out>, error=<optimized out>, user_data=0x1f67410) at /build/buildd/glib2.0-2.44.0/./gio/gdbusnamewatching.c:261
 ffi_call_unix64 () at ../src/x86/unix64.S:76
 ffi_call (cif=cif@entry=0x7f3496481810, fn=<optimized out>, rvalue=0x7f3496481770, avalue=avalue@entry=0x7f3496481710) at ../src/x86/ffi64.c:525

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 indicator-datetime (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Sebastien Bacher (seb128)
information type: Private → Public
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in indicator-datetime (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

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