time-admin crashed with SIGABRT in raise()

[butelie]

NU functioneaza

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: gnome-time-admin 3.0.0-2ubuntu1
Uname: Linux 3.8.1-030801-generic i686
ApportVersion: 2.9.2-0ubuntu5
Architecture: i386
CrashCounter: 1
Date: Wed Mar 27 14:54:51 2013
ExecutablePath: /usr/bin/time-admin
InstallationDate: Installed on 2013-03-05 (21 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
MarkForUpload: True
ProcCmdline: time-admin
Signal: 6
SourcePackage: gnome-system-tools
StacktraceTop:
 raise () from /lib/i386-linux-gnu/libc.so.6
 abort () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /lib/i386-linux-gnu/libc.so.6
Title: time-admin crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
XsessionErrors:
 (process:2114): GLib-CRITICAL **: g_slice_set_config: assertion `sys_page_size == 0' failed
 (eog:2252): EOG-CRITICAL **: eog_list_store_length: assertion `EOG_IS_LIST_STORE (store)' failed
 (polkit-gnome-authentication-agent-1:1736): GLib-WARNING **: GChildWatchSource: Exit status of a child process was requested but ECHILD was received by waitpid(). Most likely the process is ignoring SIGCHLD, or some other thread is invoking waitpid() with a nonpositive first argument; either behavior can break applications that use g_child_watch_add()/g_spawn_sync() either directly or indirectly.
 (process:3917): GLib-CRITICAL **: g_slice_set_config: assertion `sys_page_size == 0' failed

[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 #1159642, 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.