users-admin crashed with SIGSEGV in magazine_cache_push_magazine()

[Thaddaeus Tintenfisch]

no information available

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: gnome-system-tools 3.0.0-2ubuntu2
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic i686
NonfreeKernelModules: fglrx
ApportVersion: 2.12.5-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Fri Oct 11 02:57:32 2013
ExecutablePath: /usr/bin/users-admin
ExecutableTimestamp: 1365191777
InstallationDate: Installed on 2013-09-21 (19 days ago)
InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130920)
MarkForUpload: True
ProcCmdline: users-admin
ProcCwd: /home/thad
SegvAnalysis:
 Segfault happened at: 0xb6e2b207 <magazine_cache_push_magazine+135>: mov (%ecx),%ebp
 PC (0xb6e2b207) ok
 source "(%ecx)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%ebp" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-system-tools
StacktraceTop:
 magazine_cache_push_magazine (ix=ix@entry=13, magazine_chunks=<optimized out>, count=14) at /build/buildd/glib2.0-2.38.0/./glib/gslice.c:706
 thread_memory_magazine2_unload (ix=ix@entry=13, tmem=<optimized out>) at /build/buildd/glib2.0-2.38.0/./glib/gslice.c:815
 g_slice_free1 (mem_size=108, mem_block=mem_block@entry=0x9929ad0) at /build/buildd/glib2.0-2.38.0/./glib/gslice.c:1106
 g_type_free_instance (instance=instance@entry=0x9929b28) at /build/buildd/glib2.0-2.38.0/./gobject/gtype.c:1938
 g_object_unref (_object=0x9929b28) at /build/buildd/glib2.0-2.38.0/./gobject/gobject.c:3210
Title: users-admin crashed with SIGSEGV in magazine_cache_push_magazine()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1235117, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.