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

Bug #1553696 reported by cliff tinker
46
This bug affects 8 people
Affects Status Importance Assigned to Milestone
indicator-datetime (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

occurs on login

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: indicator-datetime 15.10+16.04.20160129-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4
Uname: Linux 4.4.0-10-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
Date: Sun Mar 6 06:35:22 2016
ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service
InstallationDate: Installed on 2016-02-23 (11 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205)
ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service
ProcEnviron:
 PATH=(custom, no user)
 LANGUAGE=en_GB:en
 XDG_RUNTIME_DIR=<set>
 LANG=en_GB.UTF-8
 SHELL=/bin/false
SegvAnalysis:
 Segfault happened at: 0x7eff737ead8d <g_type_check_instance+13>: mov (%rdi),%rax
 PC (0x7eff737ead8d) 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 () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_handler_disconnect () 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()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
cliff tinker (cliff5555) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_type_check_instance () from /tmp/apport_sandbox_d2yEZ0/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_handler_disconnect () from /tmp/apport_sandbox_d2yEZ0/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 on_connection_disconnected () from /tmp/apport_sandbox_d2yEZ0/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ffi_call_unix64 () from /tmp/apport_sandbox_d2yEZ0/usr/lib/x86_64-linux-gnu/libffi.so.6
 ffi_call () from /tmp/apport_sandbox_d2yEZ0/usr/lib/x86_64-linux-gnu/libffi.so.6

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
Charles Kerr (charlesk)
information type: Private → Public
tags: added: yakkety
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

Other bug subscribers

Remote bug watches

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