Synaptic and gksu

[Jib]

Tested on iBook G4 with up-to-date Dapper.

When I graphically appeal synaptic a pop-up error window explains :

Échec lors du lancement de /usr/sbin/synaptic en tant qu'utilisateur root :
(translation by me : /usr/sbin/synaptic launch failure as root user )
Failed to communicate with gksu-run-helper.

Received:
 su : Authentication failure

While expecting:
 gksu: waiting

Yet, a "sudo synaptic" works after that message :
(synaptic:4185): Gtk-CRITICAL **: gtk_accel_label_set_accel_closure: assertion
`gtk_accel_group_from_accel_closure (accel_closure) != NULL' failed

(synaptic:4185): Gtk-CRITICAL **: gtk_accel_label_set_accel_closure: assertion
`gtk_accel_group_from_accel_closure (accel_closure) != NULL' failed
jib@naugnim:~$ sudo update-manager
Password:
/usr/lib/python2.4/site-packages/apt/__init__.py:17: FutureWarning: apt API not
stable yet
  warnings.warn("apt API not stable yet", FutureWarning)
/usr/lib/python2.4/site-packages/UpdateManager/MetaRelease.py:164:
DeprecationWarning: Class MetaRelease is already GObject-registered; Please note
that classes containing any of the attributes __gtype_name__, __gproperties__,
or __gsignals__ are now automatically registered.
  gobject.type_register(MetaRelease)

(update-manager:4516): libglade-WARNING **: Error loading image: L'ouverture du
fichier « /usr/share/update-manager/glade/synaptic.xpm » a échoué : No such file
or directory

(update-manager:4516): libglade-WARNING **: could not convert string to type
`GdkPixbuf' for property `icon'
current dist not found in meta-release file
jib@naugnim:~$ sudo synaptic

(synaptic:4555): Gtk-CRITICAL **: gtk_accel_label_set_accel_closure: assertion
`gtk_accel_group_from_accel_closure (accel_closure) != NULL' failed

(synaptic:4555): Gtk-CRITICAL **: gtk_accel_label_set_accel_closure: assertion
`gtk_accel_group_from_accel_closure (accel_closure) != NULL' failed

I think this bug is likely linked to that one :
http://bugzilla.ubuntu.com/post_bug.cgi

[Jib (moramarth-deactivatedaccount)]

I apologize : my link is broken.

I was thinking about the 21542 bug...

[Michael Vogt (mvo)]

Thanks for your bugreport.

it seems that #21542 is exactly the same problem.

This bug has been marked as a duplicate of bug 27636.