User Accounts window crashes when trying to edit - running from USB

Bug #883978 reported by Bryan
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
gnome-control-center (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

1. Release 11.10
2. ?
3. Wanted to edit user information
4. No user information was available (just started using Ubuntu booted from USB). When clicking to add user or clicking anywhere on the screen, the user accounts screen freezes and closes.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-control-center 1:3.2.0-0ubuntu6
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic i686
ApportVersion: 1.23-0ubuntu3
Architecture: i386
CasperVersion: 1.287
Date: Sun Oct 30 20:49:57 2011
ExecutablePath: /usr/bin/gnome-control-center
LiveMediaBuild: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
ProcCmdline: gnome-control-center --overview
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x1ce6f43d: mov 0x10(%eax),%eax
 PC (0x1ce6f43d) ok
 source "0x10(%eax)" (0x00000010) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 ?? () from /usr/lib/control-center-1/panels/libuser-accounts.so
 ?? () from /usr/lib/control-center-1/panels/libuser-accounts.so
 g_cclosure_marshal_VOID__PARAM () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: gnome-control-center crashed with SIGSEGV in g_cclosure_marshal_VOID__PARAM()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
usr_lib_gnome-control-center:
 deja-dup 20.0-0ubuntu3
 gnome-bluetooth 3.2.0-0ubuntu1
 indicator-datetime 0.3.0-0ubuntu3

Revision history for this message
Bryan (bkapicka) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 um_user_set_automatic_login (user=0x0, enabled=1) at um-user.c:1075
 autologin_changed (object=0x22058118, pspec=0x2213c8c0, d=0x21f1d150) at um-user-panel.c:532
 g_cclosure_marshal_VOID__PARAM (closure=0x21ebfd80, return_value=0x0, n_param_values=2, param_values=0x2222a400, invocation_hint=0xbfcc3d60, marshal_data=0x0) at /build/buildd/glib2.0-2.30.0/./gobject/gmarshal.c:539
 g_closure_invoke (closure=0x21ebfd80, return_value=0x0, n_param_values=2, param_values=0x2222a400, invocation_hint=0xbfcc3d60) at /build/buildd/glib2.0-2.30.0/./gobject/gclosure.c:774
 signal_emit_unlocked_R (node=0x21e5d0c0, detail=916, instance=0x22058118, emission_return=0x0, instance_and_params=0x2222a400) at /build/buildd/glib2.0-2.30.0/./gobject/gsignal.c:3272

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 gnome-control-center (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in gnome-control-center (Ubuntu):
status: New → Confirmed
visibility: private → public
Revision history for this message
Ralph Gardner (rgrdnrjr) wrote :

 After my harddisk failed I was looking for a way to turn off the keyring request when I use Ubuntu from the USB.

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.