When I know what packages I want, {and/or for upgrades} I prefer apt-get... But when I'm looking for something I'm not already familiar with, then synaptic is just easier.

But anyway I just installed antiX on my gateway laptop this past week.
The first thing I did was to install E17 (Enlightenment) Then I ran synaptic several times as I slowly got my user environment configured.

I did an: and it was still possible to launch synaptic from the application menu. But that left over 200 packages NOTupgraded so the next day I did an After that, I was no longer able to start synaptic by any method that depends on Though I can still start it from the command line with su -c, sudo, or a root shell. It almost acts like it needs a specific gui sudo type authenticater that isn't on my system??? I would install a collection of those if I could find them in the repos But I'm not fnding much of that at all...

Any suggestions

Install all the policykit consolekit crap and then synaptic will work OOTB. They have changed it so the .desktop file no longer points to gksu synaptic but synaptic-pkexec.

The synaptic entry in menu/others should still work.

anticapitalista wrote:Install all the policykit consolekit crap and then synaptic will work OOTB. They have changed it so the .desktop file no longer points to gksu synaptic but synaptic-pkexec.

If policykit means what I think it does then crap is the appropriate word alright. I never liked thr idea of somebody else setting"policy" on my machine. But as time goes on, I suspect I'm either going to have to do it their way, or see a lot of things stop working...

So like if I fire up synaptic the hard way, and use"policykit" and"consolekit" as search terms, I should install every thing it finds including the kitchen sink? or are those the actual package names?

anticapitalista wrote:The synaptic entry in menu/others should still work.

Perhaps it should, but it doesn't. Nor does typing synaptic in E17's"Everything" application launcher...

But I'll look and see if"policykit" and"consolekit" are actual package names... Otherwise I could use a list of which packages you were referring to... In any case thanks for the explanation.

Actually according to synaptic, I've already got consolekit and policykit-1 installed...

But you gave me an idea... I edited the synaptic.desktop file. Manually commenting out the exec line for synaptic-pkexec {which is the name enlightenment's error pop-up said failed to start} and adding one for"gksu synaptic"... That worked. But will probably get overwritten the next time synaptic gets upgraded... {sigh}