Hi,
When I click the button mentioned in the subject, a ROX terminal window opens, asking for my sudo password. After typing this password, ROX close immediately. I'm sure I have done this before and got an overview of the services running on my system. But not anymore apparently.
It may be that a flawed installation of VMware Player (32 bit, version 6.0.6) is involved, but I'm not sure. Starting a VM results in an error message about /dev/vmmon not being found.
Now, what script is started by this button in AntixCC? Maybe I can start it from a terminal window.
Thanks.
topic title: Antix Control Center/Choose Startup Services broken.
6 posts
• Page 1 of 1
-
dirkdPosts: 91
- Joined: 30 May 2014
-
dolphin_oraclePosts: 2,238
- Joined: 16 Dec 2007
#2
it runs an app called sysv-rc-conf. Run this in a root terminal.
-
dolphin_oraclePosts: 2,238
- Joined: 16 Dec 2007
#3
also, that particular control center button is using the root password instead of the sudo (regular user) password.
-
dirkdPosts: 91
- Joined: 30 May 2014
#4
Aha! Should have tried that I guess. Quite a relief that nothing is wrong with my AntixCC! It works!
-
skidooPosts: 1,445
- Joined: 09 Feb 2012
#5
TLDR: For my"short answer", scroll down to the blue text.
Ah, dolphin jumped in while I was typing this.
He's usually right; me, I'm usually just long-winded so, yeah, go with what dolphin said.
You asked: What program is launched?
In answering, I'm gonna take a step back to the borader scope. The menu item labeled"controlCentre" launches
/usr/local/bin/antixcc.sh
For future reference (you peeps, anyone reading this), you can view the code of antixcc.sh in a text editor
to determine what command or program is launched via each of the controlCentre items.
content of the desktop menu(s) is also easily readible, BTW... but that's a post for another day
In this case, searching"startup" within the controlCentre script reveals the associated commandline:
desktop-defaults-run -t su -c sysv-rc-conf &
Here, I'm not advocating blindly pasting that into a terminal prompt.
(Doing so would be pointless; the expected result would be identical to having clicked the launcher icon.)
To"follow the bouncing ball" so to speak...
in terminal, try
locate desktop-defaults-run
and / or
man desktop-defaults-run
Personally, I'd be tempted to just immediately try
sudo geany /usr/local/bin/desktop-defaults-run
(geany won't be able to load the file if binary, but no harm... and most of the usr_local_bin commands are indeed scripts, not binaries.)
Ah, in this case, maybe you're quicker than me to notice that this commandline
really just passes through to sysv-rc-conf
which you can't directly access (without sudo/root permissions)
$ /usr/sbin/sysv-rc-confsysv-rc-conf
bash: sysv-rc-conf: command not found
FWIW (in case you care to peek under the hood) sysv-rc-conf is a perl script sudo geany /usr/sbin/sysv-rc-conf
but
I seriously doubt that it, nor any of the chained commands leading to it, are"broken".
While jumping (booting) back-n-fro between live-persist and non-persistent sessions, I've occasionally encountered what you've described.
Regardless what you might expect the password should be...
try using the default passwords ~~ First, by typing"demo" as the password. If that doesn't work, try again and type"root".
By the way, I recommend installing debian package"bum" (BootUpManager).
It provides a GUI interface (and some item descriptions) for startups management.
bum provide less granular control though, in case you (for some reason) want an item running (or not) during a particular runlevel.
Ah, dolphin jumped in while I was typing this.
He's usually right; me, I'm usually just long-winded so, yeah, go with what dolphin said.
You asked: What program is launched?
In answering, I'm gonna take a step back to the borader scope. The menu item labeled"controlCentre" launches
/usr/local/bin/antixcc.sh
For future reference (you peeps, anyone reading this), you can view the code of antixcc.sh in a text editor
to determine what command or program is launched via each of the controlCentre items.
content of the desktop menu(s) is also easily readible, BTW... but that's a post for another day
In this case, searching"startup" within the controlCentre script reveals the associated commandline:
desktop-defaults-run -t su -c sysv-rc-conf &
Here, I'm not advocating blindly pasting that into a terminal prompt.
(Doing so would be pointless; the expected result would be identical to having clicked the launcher icon.)
To"follow the bouncing ball" so to speak...
in terminal, try
locate desktop-defaults-run
and / or
man desktop-defaults-run
Personally, I'd be tempted to just immediately try
sudo geany /usr/local/bin/desktop-defaults-run
(geany won't be able to load the file if binary, but no harm... and most of the usr_local_bin commands are indeed scripts, not binaries.)
Ah, in this case, maybe you're quicker than me to notice that this commandline
really just passes through to sysv-rc-conf
which you can't directly access (without sudo/root permissions)
$ /usr/sbin/sysv-rc-confsysv-rc-conf
bash: sysv-rc-conf: command not found
FWIW (in case you care to peek under the hood) sysv-rc-conf is a perl script sudo geany /usr/sbin/sysv-rc-conf
but
I seriously doubt that it, nor any of the chained commands leading to it, are"broken".
While jumping (booting) back-n-fro between live-persist and non-persistent sessions, I've occasionally encountered what you've described.
Regardless what you might expect the password should be...
try using the default passwords ~~ First, by typing"demo" as the password. If that doesn't work, try again and type"root".
By the way, I recommend installing debian package"bum" (BootUpManager).
It provides a GUI interface (and some item descriptions) for startups management.
bum provide less granular control though, in case you (for some reason) want an item running (or not) during a particular runlevel.
-
dirkdPosts: 91
- Joined: 30 May 2014
#6
Thank you, Skidoo! I learned more in a few weeks serious Antix then I did in four years of Ubuntu. Well, that may not be really true, but it sure feels like that.