So, it really makes no difference where I put it, as long as I can find it?
I would have to edit the thingies that want to look at the file.sh, I guess, so it can find it too?
-
Posts: 765
- Joined: 27 Dec 2011
-
Posts: 4,164
- Joined: 20 Feb 2009
#47
Yep.
So, it really makes no difference where I put it, as long as I can find it?
I would have to edit the thingies that want to look at the file.sh, I guess, so it can find it too?
Code: Select all
Pecos: ${execi 300 /home/harry/scripts/weather.sh 79772}
-
Posts: 1,062
- Joined: 20 Jan 2010
#48
RC,
sometimes it does make a differance for example if you would like to type something.sh to run your script instead of /home/user/something.sh, this would go along with running one script from another. also if you would like to use the script in a cron job or udev rule or your drive is mounted under the noexec rule.
sometimes it does make a differance for example if you would like to type something.sh to run your script instead of /home/user/something.sh, this would go along with running one script from another. also if you would like to use the script in a cron job or udev rule or your drive is mounted under the noexec rule.
-
Posts: 765
- Joined: 27 Dec 2011
#49
Ok, you are way over my head, but I think I get what you are saying __{{emoticon}}__
-
Posts: 765
- Joined: 27 Dec 2011
#50
And now... a new issue...
On my stick-install of antix core, and icewm, I get this error when I try to start a roxterm
So, am I right thinking that dbus is just not running?
I did remove nodbus and antix lmde(or what it was) from thee boot cheats.
What exactly is the session manager?
On my stick-install of antix core, and icewm, I get this error when I try to start a roxterm
Code: Select all
** (x-terminal-emulator:8830): CRITICAL **: Error connecting to dbus: /usr/bin/dbus-launch terminated abnormally without any error message
** (x-terminal-emulator:8830): CRITICAL **: optsdbus_listen_for_opt_signals: assertion `rtdbus_ok' failed
** (x-terminal-emulator:8830): CRITICAL **: optsdbus_listen_for_stuff_changed_signals: assertion `rtdbus_ok' failed
** (x-terminal-emulator:8830): CRITICAL **: optsdbus_listen_for_set_profile_signals: assertion `rtdbus_ok' failed
** (x-terminal-emulator:8830): CRITICAL **: optsdbus_listen_for_set_colour_scheme_signals: assertion `rtdbus_ok' failed
** (x-terminal-emulator:8830): CRITICAL **: optsdbus_listen_for_set_shortcut_scheme_signals: assertion `rtdbus_ok' failed
** (x-terminal-emulator:8830): WARNING **: Failed to connect to session manager: SESSION_MANAGER environment variable not defined
I did remove nodbus and antix lmde(or what it was) from thee boot cheats.
What exactly is the session manager?
-
anticapitalista
Posts: 5,955
- Site Admin
- Joined: 11 Sep 2007
#51
rc - what desktop manager are you using, slim?
-
Posts: 765
- Joined: 27 Dec 2011
#52
Right now... nothing... I guess I was wrong?
Is desktop manager and session manager the same thing?
Is desktop manager and session manager the same thing?
-
anticapitalista
Posts: 5,955
- Site Admin
- Joined: 11 Sep 2007
#53
Ok, install dbus-x11
-
Posts: 765
- Joined: 27 Dec 2011
#54
Wow! that was easy! Works great!
-
Posts: 765
- Joined: 27 Dec 2011
#55
Aw! it does work well, BUT not if I su to root?
I decided to try using gdm3, and it does work...if it works well...Who knows? but it does log me in, and do what it should, I think.
I decided to try using gdm3, and it does work...if it works well...Who knows? but it does log me in, and do what it should, I think.
-
Posts: 765
- Joined: 27 Dec 2011
#56
so, now my latest screwup!
I somehow managed to break the wallpaper chooser thingie?
I made a picture, and svaed it to home/wallpaper, then tried to copy it to /usr/share/wallpaper
It just made a link, but oh well.
So, when I tried to set the background, it complained it had too many symbolic links, and wallpaper was disabled, or removed, or something along those lines.
Ok, so I try to set a different pic, but the chooser thinge don't work?
So now I use rox to set the background, which is ok... but the thing shouldn't just disappear, right?
I somehow managed to break the wallpaper chooser thingie?
I made a picture, and svaed it to home/wallpaper, then tried to copy it to /usr/share/wallpaper
It just made a link, but oh well.
So, when I tried to set the background, it complained it had too many symbolic links, and wallpaper was disabled, or removed, or something along those lines.
Ok, so I try to set a different pic, but the chooser thinge don't work?
So now I use rox to set the background, which is ok... but the thing shouldn't just disappear, right?
-
Posts: 1,062
- Joined: 20 Jan 2010
#57
in ~/.wallpaper there are several files, change the contents of the saved file to a different picture (not a link) by full path and it should come back up.
If it does not you *should* be able to copy the original .wallpaper from / etc/ skel/
If it does not you *should* be able to copy the original .wallpaper from / etc/ skel/
-
Posts: 765
- Joined: 27 Dec 2011
#58
Oh, the picture itself is ok, but the tool to choose wallpapers is not working anymore.
I have fixed the pic.
but thanks!
I have fixed the pic.
but thanks!
-
Posts: 1,062
- Joined: 20 Jan 2010
#59
if"the tool" is wallpaper.py (antixCC --> choose wallpaper), changing the contents of the saved file will allow for"the tool" to open. Reason being it is looking for a valid picture file to load in the preview inside of the main window.
EDIT:
I do have a newer version that should fix several issues similar to this one, when it is ready/tested it will be downloaded and installed on a apt-get dist-upgrade
EDIT:
I do have a newer version that should fix several issues similar to this one, when it is ready/tested it will be downloaded and installed on a apt-get dist-upgrade
-
Posts: 765
- Joined: 27 Dec 2011
#60
aha! ok!
As usual, I end up learning something!
I will try the new one when it gets done
And an edit...
Sure enough, it works fine now...
As usual, I end up learning something!
I will try the new one when it gets done
And an edit...
Sure enough, it works fine now...