Posts: 39
frogprince
Joined: 08 Nov 2012
#1
When I click on Applications/Other/Synaptic Package Manager, I get a dialog box that states:

Synaptic
Command passed is invalid.

If as root, I type"synaptic" into a terminal, I get

sh: 1: lsb_release: not found
sh: 1: lsb_release: not found

And then Synaptic opens and runs fine. ???? __{{emoticon}}__

Where does one edit the command for a menu icon? Or???

Thanks!
Posts: 325
male
Joined: 04 Nov 2011
#2
viewtopic.php?f=47&t=4053
Posts: 137
duncan_mk
Joined: 19 Sep 2012
#3
Had the same problem

post27027.html#p27027

dmk
Posts: 39
frogprince
Joined: 08 Nov 2012
#4
Thanks for your kind suggestion. What I've found is that if I edit /usr/share/applications/synaptic.desktop as root:

Exec=gksu synaptic

And I click on

applications/preferences/synaptic package manager

it immediately prompts me for a root password and then opens and runs. But if I click on

applications/other/synaptic package manager

I get the ktsuss error message. Is there a different file to edit for the second menu entry? Or ????

I also tried

Exec=ktsuss /usr/sbin/synaptic

But that won't work with the second menu entry either. ????

Thanks again!
anticapitalista
Posts: 5,955
Site Admin
Joined: 11 Sep 2007
#5
applications/other/synaptic package manager do as you did for /usr/share/applications/synaptic.desktop
but in /usr/share/applications/antiX/synaptic.desktop
Posts: 39
frogprince
Joined: 08 Nov 2012
#6
anticapitalista: thanks for your kind response. It didn't work, but I'm really interested in figuring this one out.

I tried, as root:

leafpad /usr/share/applications/antiX/synaptic.desktop

which opened; the synaptic.desktop file was there, but was completely empty.
So I added:

Exec=gksu synaptic

and tried to save it. I got an error message:

(leafpad:3912): GVFS-RemoteVolumeMonitor-WARNING **: cannot connect to the session bus: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

And then the file manager opened to /usr/share/applications. I selected the antiX directory, then synaptic.desktop, and save.
It asked if I wanted to overwrite the file. I selected yes, closed leafpad, and then went back to applications/other to test the link.

But synaptic package manager wasn't there anymore. It is still present in applications/preferences, but only once now. It was
originally there twice.

So I opened leafpad /usr/share/applications/antiX/synaptic.desktop again to check, and found that the change had not saved,
even though I was root. The synaptic.desktop file was still empty.

You support a lot of users, and I appreciate your time. I really like antiX, in part because it's taught me some details about
Linux that I hadn't had to deal with before. I like being this close to the machine! So if you have a suggestion on a direction to
proceed, I'd love to hear it. And thanks!
anticapitalista
Posts: 5,955
Site Admin
Joined: 11 Sep 2007
#7
Here is the correct file for /usr/share/applications/antix/synaptic.desktop (My mistake with small x for antix)


========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://www.mepisimo.com/antix/Others/"
linktext was:"http://www.mepisimo.com/antix/Others/"
====================================
Posts: 39
frogprince
Joined: 08 Nov 2012
#8
Thank you! But how do I save it? I was unable to get leafpad to save that file after editing it.
Do I need to do this outside of xorg like smxi?
anticapitalista
Posts: 5,955
Site Admin
Joined: 11 Sep 2007
#9
Best way IMO is to click on Run from the menu, type gksu rox and give root password then navigate to the file and right click on it - open as Text
anticapitalista
Posts: 5,955
Site Admin
Joined: 11 Sep 2007
#10
frogprince - to download the link, right click and choose save link as to anywhere in home (You cannot save in any root directory due to permissions).
Once saved in home you can just drag and drop the file to /usr/share/applications/antix (via rox opened as root).

BTW, there should be an option when editing any files that requires root permission to right click on the file and at the top Edit as root.
Posts: 39
frogprince
Joined: 08 Nov 2012
#11
anticapitalista: OK, that fixed everything, thankyouthankyou. I'm curious why leafpad wouldn't save the edit as root, but hey, this worked.

I still also have the ghost window at boot despite"uncommenting the line which starts icewmtray in the startup script
of the ~/.icewm directory" as per

several-little-bugs-t3834.html

The ghost window sometimes disappears when I boot the system, but most of the time does not. If it's there, I can make
it go away by logging out and back in. ????? Is there a different icewm file that I need to edit?

Thanks again for all your help! __{{emoticon}}__
anticapitalista
Posts: 5,955
Site Admin
Joined: 11 Sep 2007
#12
Have you tried this?

post25928.html?hilit=ghost%20window#p25928
Posts: 39
frogprince
Joined: 08 Nov 2012
#13
anticapitalista: this finally worked. SamK suggested taking these three lines in ~/.icewm/startup out of background mode:

login_background.sh
rox --pinboard=antiX-ice
conky

I found a link that showed me that adding the"&" sign after the command puts it in background mode. Deleting"&" takes it out:


========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://www.unix.com/shell-programming-scripting/167953-how-run-background-mode.html"
linktext was:"http://www.unix.com/shell-programming-s ... -mode.html"
====================================


So I deleted the"&" from the above three lines, resaved the startup file, and have now rebooted the system without the"ghost
window" multiple times. As yet, I have found no new problems created by this change. Might this qualify as a bug fix?

As another bug fix, the file at /usr/share/applications/antiX/synaptic.desktop was empty. Copying your link contents to this
file and saving fixed that bug.

So to summarize, right now I have a very quick system running on a ten year old machine with access to the full Debian repositories.
And I've learned some things in the process. This is cool! Thanks again for your patient time and help.