Ubuntu
unity-control-center package

unity-control-center crashed with SIGSEGV in g_type_check_instance()

Bug #1375073 reported by Cherusker
32
This bug affects 4 people
Affects Status Importance Assigned to Milestone
unity-control-center (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

switch off online search

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: unity-control-center 14.10.0+14.10.20140922-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3
Uname: Linux 3.16.0-18-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.7-0ubuntu2
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Mon Sep 29 02:15:30 2014
ExecutablePath: /usr/bin/unity-control-center
InstallationDate: Installed on 2014-09-28 (0 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140923)
ProcCmdline: unity-control-center --overview
ProcEnviron:
 PATH=(custom, no user)
 LANGUAGE=de_DE
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fbbc6ce2a59 <g_type_check_instance+25>: mov (%rax),%rdi
 PC (0x7fbbc6ce2a59) ok
 source "(%rax)" (0x2c0000005000) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: unity-control-center
StacktraceTop:
 g_type_check_instance () 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
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
Title: unity-control-center crashed with SIGSEGV in g_type_check_instance()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

usr_lib_unity-control-center:
 activity-log-manager 0.9.7-0ubuntu15
 deja-dup 32.0-0ubuntu1

Revision history for this message
Cherusker (grappa-z) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_type_check_instance (type_instance=type_instance@entry=0x1faf350) at /build/buildd/glib2.0-2.41.5/./gobject/gtype.c:4087
 g_signal_emit_valist (instance=0x1faf350, signal_id=364, detail=0, var_args=var_args@entry=0x7fff5d7e1780) at /build/buildd/glib2.0-2.41.5/./gobject/gsignal.c:3094
 g_signal_emit (instance=<optimized out>, signal_id=<optimized out>, detail=detail@entry=0) at /build/buildd/glib2.0-2.41.5/./gobject/gsignal.c:3365
 emit_manager_changed (data=<optimized out>) at /build/buildd/gtk+3.0-3.12.2/./gtk/gtkrecentmanager.c:1381
 gdk_threads_dispatch (data=0x201bd80, data@entry=<error reading variable: value has been optimized out>) at /build/buildd/gtk+3.0-3.12.2/./gdk/gdk.c:635

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 unity-control-center (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Apport retracing service (apport)
tags: added: xenial
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in unity-control-center (Ubuntu):
status: New → Confirmed
Adolfo Jayme Barrientos (fitojb)
information type: Private → Public
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.