time-admin crashed with SIGABRT in __libc_message()

[Paul White]

I tried to change from manual to automatic updating of the system time but was told that ntp suppoort was not installed.

As another package manager was active the install process could not start and while I attempted to stop the other package manager time-admin crashed.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: gnome-time-admin 3.0.0-2ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-14.24-generic 3.8.4
Uname: Linux 3.8.0-14-generic x86_64
ApportVersion: 2.9.2-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Mon Mar 25 06:28:35 2013
ExecutablePath: /usr/bin/time-admin
InstallationDate: Installed on 2013-03-24 (0 days ago)
InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130324)
MarkForUpload: True
ProcCmdline: time-admin
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: gnome-system-tools
StacktraceTop:
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 gst_packages_install ()
Title: time-admin crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7fa48ee43860 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:199
 malloc_printerr (ptr=0x14b5ef0, str=0x7fa48ee43a00 "free(): invalid next size (fast)", action=3) at malloc.c:4902
 _int_free (av=<optimized out>, p=0x14b5ee0, have_lock=0) at malloc.c:3758
 spawn_synaptic (child_pid=0x7fffb76d77ac, path=0x130ec10 "/tmp/packages.Jo9TEj", window=0x12a8000) at gst-package.c:142
 gst_packages_install (window=0x12a8000, packages=<optimized out>) at gst-package.c:194

[Launchpad Janitor (janitor)]

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