@Jonas. my problem was broken gconf environment after automatic
distribution upgrade.
That is the kind of thing that does not happen to the new user, because
he isn't likely to distro-upgrade from 8.4 to 8.10 now
--
Synaptic menu file uses gksu = prevents from using synaptic
Does this mean that the issue will not be addressed? This issue is also
a problem with gparted, wich is set up in the same way as synaptic. I
think this can be very frustrating for a new user
--
Synaptic menu file uses gksu = prevents from using synaptic
changing to an answer tracker ticket
** Changed in: gksu (Ubuntu)
Status: New = Invalid
** Converted to question:
https://answers.edge.launchpad.net/ubuntu/+source/gksu/+question/77860
--
Synaptic menu file uses gksu = prevents from using synaptic
the issue is an environment one and not a gksu bug
** Changed in: gksu (Ubuntu)
Importance: Undecided = Low
** Changed in: gksu (Ubuntu)
Status: New = Invalid
** Converted to question:
https://answers.edge.launchpad.net/ubuntu/+source/gksu/+question/77859
** Changed in: gksu
This really isn't a bug in synaptic, reassigning to gksu instead.
** Package changed: synaptic (Ubuntu) = gksu (Ubuntu)
--
Synaptic menu file uses gksu = prevents from using synaptic
https://bugs.launchpad.net/bugs/295568
You received this bug notification because you are a member of Ubuntu
Sorry, this is not synaptic bug.
Shell output of gksu synaptic: (6x the same)
GConf Error: Failed to contact configuration server; some possible causes are
that you need to enable TCP/IP networking for ORBit, or you have stale NFS
locks due to a system crash. See
