time-admin crashed with signal 5 in do_pre_parse_initialization()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-system-tools (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Like shares-admin (bug 814060) and users-admin (bug 819821), which are provided by binary package gnome-system-tools, and network-admin (bug 819889), which is provided by binary package gnome-network-
Gtk-ERROR **: GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported
Trace/breakpoint trap (core dumped)
If the shares-admin and users-admin crashes are to be considered the same bug, then perhaps this (and bug 819889) should be considered the same bug too, even though time-admin (like network-admin) is provided by a different binary package (same source package).
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-time-admin 2.32.0-0ubuntu7
ProcVersionSign
Uname: Linux 3.0.0-7-generic i686
Architecture: i386
Date: Tue Aug 2 11:02:43 2011
ExecutablePath: /usr/bin/time-admin
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcCmdline: time-admin
ProcEnviron:
SHELL=/bin/bash
LANG=en_US.UTF-8
Signal: 5
SourcePackage: gnome-system-tools
StacktraceTop:
do_pre_
pre_parse_hook (context=0x8895938, group=0x8898390, data=0x8895968, error=0xbf9410ec) at /build/
g_option_
IA__gtk_parse_args (argc=0xbf941174, argv=0xbf941178) at /build/
IA__gtk_init_check (argc=0xbf941174, argv=0xbf941178) at /build/
Title: time-admin crashed with signal 5 in do_pre_
UpgradeStatus: Upgraded to oneiric on 2011-06-18 (44 days ago)
UserGroups: adm admin dialout lpadmin plugdev sambashare
Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #818990, 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.