Ubuntu
unity-control-center package

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

Bug #1303814 reported by Alfredo Gemma
26
This bug affects 3 people
Affects Status Importance Assigned to Milestone
unity-control-center (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

This issue uses to happen while switching windows using SUPER + W

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: unity-control-center 14.04.3+14.04.20140404.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
Uname: Linux 3.13.0-20-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Apr 7 15:39:00 2014
ExecutablePath: /usr/bin/unity-control-center
InstallationDate: Installed on 2014-03-31 (6 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140330)
ProcCmdline: unity-control-center datetime
SegvAnalysis:
 Segfault happened at: 0x7f18d9d5c334 <gtk_list_store_reorder+180>: mov %ebx,(%r14,%rax,4)
 PC (0x7f18d9d5c334) ok
 source "%ebx" ok
 destination "(%r14,%rax,4)" (0x1b15f5284) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: unity-control-center
StacktraceTop:
 gtk_list_store_reorder () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/unity-control-center-1/panels/libdatetime.so
 ?? () 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: unity-control-center crashed with SIGSEGV in gtk_list_store_reorder()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
usr_lib_unity-control-center:
 activity-log-manager 0.9.7-0ubuntu13
 deja-dup 30.0-0ubuntu4

Revision history for this message
Alfredo Gemma (alfredo-gemma) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 gtk_list_store_reorder (store=0x39330d0, new_order=0x3603030) at /build/buildd/gtk+3.0-3.10.7/./gtk/gtkliststore.c:1718
 handle_sort (tree_view=<optimized out>, compare=<optimized out>, button=<optimized out>) at datetime-prefs-locations.c:122
 _g_closure_invoke_va (closure=0x362c240, return_value=0x0, instance=0x2af1b00, args=0x7fff7c238d38, n_params=0, param_types=0x0) at /build/buildd/glib2.0-2.40.0/./gobject/gclosure.c:831
 g_signal_emit_valist (instance=0x2af1b00, signal_id=<optimized out>, detail=0, var_args=var_args@entry=0x7fff7c238d38) at /build/buildd/glib2.0-2.40.0/./gobject/gsignal.c:3215
 g_signal_emit (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>) at /build/buildd/glib2.0-2.40.0/./gobject/gsignal.c:3363

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 unity-control-center (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Apport retracing service (apport)
tags: added: utopic
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
Apport retracing service (apport)
tags: added: vivid
Revision history for this message
Dave Chiluk (chiluk) wrote :

I accidentally added a blank location followed by an actual location to the "Time in other locations", choose locations dialog box. I then clicked sort by time.

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.