gnome-control-center crashed with SIGSEGV in gtk_builder_get_object()

Bug #1201700 reported by BRUN Christian
232
This bug affects 48 people
Affects Status Importance Assigned to Milestone
activity-log-manager (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

The DASH (upper icon, in left corner) does not affich files icons, only system and videos ones
What can I have to do ?
Thanks a lot for your help

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: activity-log-manager 0.9.7-0ubuntu3
ProcVersionSignature: Ubuntu 3.10.0-3.12-generic 3.10.1
Uname: Linux 3.10.0-3-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.10.2-0ubuntu4
Architecture: amd64
CrashCounter: 1
Date: Tue Jul 16 09:43:19 2013
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2013-06-13 (32 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130608)
MarkForUpload: True
ProcCmdline: gnome-control-center --overview
ProcEnviron:
 LANGUAGE=fr_FR
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f933b63c546 <gtk_builder_get_object+22>: mov (%rbx),%rdx
 PC (0x7f933b63c546) ok
 source "(%rbx)" (0x00000004) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: activity-log-manager
StacktraceTop:
 gtk_builder_get_object () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/control-center-1/panels/libactivity-log-manager.so
 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
 g_cclosure_marshal_generic () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-control-center crashed with SIGSEGV in gtk_builder_get_object()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
BRUN Christian (christian-brun83) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 gtk_builder_get_object (builder=0x4, name=name@entry=0x7f931867d1ae "submit_error_reports") at /build/buildd/gtk+3.0-3.8.2/./gtk/gtkbuilder.c:1266
 on_properties_changed (interface=0x7f92f800a550, changed_properties=<optimized out>, invalidated_properties=<optimized out>, user_data=<optimized out>) at diagnostics-widget.c:154
 ffi_call_unix64 () at ../src/x86/unix64.S:76
 ffi_call (cif=cif@entry=0x7fff81bfe630, fn=0x7f9318676850 <on_properties_changed>, rvalue=0x7fff81bfe5a0, avalue=avalue@entry=0x7fff81bfe540) at ../src/x86/ffi64.c:522
 g_cclosure_marshal_generic (closure=0x7f933d97d110, return_gvalue=0x0, n_param_values=<optimized out>, param_values=<optimized out>, invocation_hint=<optimized out>, marshal_data=0x0) at /build/buildd/glib2.0-2.37.3/./gobject/gclosure.c:1454

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in activity-log-manager (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in activity-log-manager (Ubuntu):
status: New → Confirmed
Jeremy Bícha (jbicha)
information type: Private → Public
Revision history for this message
Coya DeBrojara (coyadebrojara) wrote :

The same error. I tried to enter the Google account details. The program has no saved data and was unexpectedly closed.

Fresh installation, Ubu 13.10 beta1, the image of 11 September, lang pl_PL.UTF-8, no proprietary drivers in use.

Revision history for this message
Dac Chartrand (conner-bw) wrote :

This happened to me when I clicked the Firewall icon.

Revision history for this message
Tais P. Hansen (taisph) wrote :

I was going through each of the System Settings areas when this suddenly happened.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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