Bug#386213: gksu: Could not connect to database

Gustavo Noronha Silva kov at debian.org
Sun Sep 10 17:28:22 UTC 2006


Em Wed, 06 Sep 2006 02:41:36 +0200
kike <kike+bts at eldemonionegro.com> escreveu:

> After trying to install gforge gksu authentication begins to fail.
> I've seen that the problem comes specificly from
> gforge-shell-postgresql, which depends on libnss-pgsql1 which on it's
> side depends on libpam-pgsql. This causes somekind of interference
> because the message
> 
> 	"Failed to communicate with gksu-run-helper.
> 	Received: Could not connect to database
> 	While expecting:  gksu: waiting"
> 
> appears when trying to execute synaptic as non root, as an example.
> When you run from command line 'gksu' you get "Could not connect to
> database" and then the dialog opens.

This is probably because gforce configured some pam module that su is
using to get authentication information from a database. Up to now gksu
would not handle warning/debug messages from su very well. I hope this
will be fixed in the next version of libgksu (I've commited a fix this
weekend).

Thanks,

-- 
Gustavo Noronha Silva <kov at debian.org>
http://people.debian.org/~kov/





More information about the Pkg-gnome-maintainers mailing list