shares-admin crashed with signal 5 in g_option_context_parse()

[Curtis Hovey]

This error is more obscure than the simple issue reported on the command line. The two scripts provided by this package are co-mingling gtk2 and 3, which will always fail.
$ users-admin
Gtk-ERROR **: GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported

$ shares-admin
Gtk-ERROR **: GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-system-tools 2.32.0-0ubuntu7
ProcVersionSignature: Ubuntu 3.0.0-5.6-generic-pae 3.0.0-rc7
Uname: Linux 3.0.0-5-generic-pae i686
NonfreeKernelModules: nvidia wl
Architecture: i386
Date: Thu Jul 21 08:43:15 2011
ExecutablePath: /usr/bin/shares-admin
ProcCmdline: shares-admin
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
Signal: 5
SourcePackage: gnome-system-tools
StacktraceTop:
 ?? () from /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0
 g_option_context_parse () from /lib/i386-linux-gnu/libglib-2.0.so.0
 gst_init_tool ()
 main ()
Title: shares-admin crashed with signal 5 in g_option_context_parse()
UpgradeStatus: Upgraded to oneiric on 2011-07-01 (19 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:
 do_pre_parse_initialization (context=0x84eef00, group=0x84f2808, data=0x84f0e00, error=0x0) at /build/buildd/gtk+2.0-2.24.5/gtk/gtkmain.c:676
 pre_parse_hook (context=0x84eef00, group=0x84f2808, data=0x84f0e00, error=0x0) at /build/buildd/gtk+2.0-2.24.5/gtk/gtkmain.c:787
 g_option_context_parse (context=0x84eef00, argc=0xbfed79e4, argv=0xbfed79e8, error=0x0) at /build/buildd/glib2.0-2.29.10/./glib/goption.c:1763
 gst_init_tool ()
 main ()

[Charlie Kravetz (cjkgeek)]

Thanks for reporting this bug and any supporting documentation. Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here.

This can be reproduced simply by installing a daily/daily-live image of Oneiric and trying to use Users and Groups.

Thanks for taking the time to make Ubuntu better!

[Eliah Kagan (degeneracypressure)]

I am able to reproduce this bug on Oneiric with gnome-system-tools 2.32.0-0ubuntu7 (also on an i386 system running 3D Unity, but there is no reason to think this bug does not affect all Oneiric systems).

I mention this even though the bug has already been confirmed and marked triaged because, contrary to https://bugs.launchpad.net/ubuntu/+source/gnome-system-tools/+bug/814060/comments/5, this cannot technically be reproduced by attempting to use Users and Groups. This is shares-admin, whereas Users and Groups actually runs users-admin. Reproducing a crash like this running Users and Groups can be taken to confirm bug 819821 (but I won't mark my own bug Confirmed).

[Eliah Kagan (degeneracypressure)]

To clarify my motivation in https://bugs.launchpad.net/ubuntu/+source/gnome-system-tools/+bug/814060/comments/6:

The original bug report here sought to report both the users-admin and shares-admin crashes, but it characterized the executables as "two scripts", whereas in fact they are separate ELF binaries with nonidentical contents. If this bug is to be taken to apply to both users-admin and shares-admin, then of course the original confirmation was correct and bug 819821 (and perhaps bug 789333, pertaining to the GNOME3 PPA in Natty) can be marked as a duplicate of this bug.

Furthermore, time-admin and network-admin are provided by separate binary packages but the same source package; perhaps the corresponding crashes in those utilities (bug 819879 and bug 819889) should be marked duplicates of this bug as well.

[Charlie Kravetz (cjkgeek)]

Actually, it can be reproduced at any time on a fresh install by attempting to open Menu -> System -> Users and Groups. That is what generated an apport crash of this for me numerous times already in Xubuntu Oneiric Ocelot.

[Eliah Kagan (degeneracypressure)]

I'm going to take that as indicating that it was not a mistake to have considered the related shares-admin and users-admin crashes as the same bug (even though the crashes are not in the same binary, as the wording in this bug report had implied). So I'll mark bug 819821 as a duplicate of this bug. Should bug 819879 (time-admin) and bug 819889 (network-admin) also be considered the same as this?