Puppy Linux Discussion Forum

[ocpaul20]

[ocpaul20]

It is strange, because I have added a link to /root/Startup and am sure it is executable. When I click on it as you suggested, it runs and shows the drive icons correctly.

However, after all that, when I reboot, expecting this to run as part of the startup routine, I get no drive icons but I get a message which tells me that I am using the default pinboard.

To test it all, I placed a line at the end of another shell script which runs at my startup.
nohup /root/Startup/desktop_drive_icons &

and nohup.out gives me a message
(desktop_drive_icons:3539): Gtk-WARNING **: cannot open display:

Maybe this is a total Red Herring and the real problem is to do with the lost pinboard and the nohup.out message above?

With linux, nothing is as simple as you think it is going to be, huh?

[dancytron]

Sorry, don't know. If Fred (posted the first message in this thread) doesn't see this in a day or two you might send him a pm.

[fredx181]

Hi ocpaul20,

[ocpaul20]

Hi Fred,
Thanks for your comment.

I have managed to get back my drive icons and the message about the default pinboard no longer shows on bootup. I am not sure what I did, but I did restore some stuff as you suggested so it was most probably that which sorted it out.

The only problem now I have is that I have lost some menu items which I thought would have been restored in the same series of operations when I restored the ROX-filer directory.

In particular, the JWM menu, Network item at bottom right has lost a few entries such as Deluge and Icedove etc. I can reinstall them and the menu items will probably be re-installed too.

Anyway, thanks for all the help on this everyone.

=====================
I found the missing menu items in a couple of files /root/.jwmrc & /root/.jwmrc-mjwm so I restored them too and everything is fine now.
======================

[ocpaul20]

I have another small problem but it may not be anything to do with DD at all. I have found other posts about it online but none of them really seem to make it any better. I will describe it and see if anyone has any ideas.

I am developing an application using python and gtk 2.

The program runs OK if I am root but not if I am puppy. When I am puppy, the error message is as follows:

[fredx181]

Hi Paul, just guessing, but maybe try before running your script:

[ocpaul20]

Hi Fred,
Thanks for your quick reply.

[fredx181]

Is it DebianDog64 Jessie you are on ? Or... ?
Anyway, it's different for me when I do the xhost command logged in as puppy:

[ocpaul20]

It is a bog-standard one as far as I know.

What does your environment DISPLAY variable show?

When I logout from root and login as puppy (as opposed to doing su as I was before) I get:
$ xhost +local:puppy
xhost: unable to open display ""

and env DISPLAY is not present at all in env variables.

What do I need to do to get in in there? Where does it come from?

================
I tried this

[fredx181]

[ocpaul20]

Yes, I changed my host name as I am running it from a memory stick on another computer. This changing my PCs hostname helps me be certain of which one I am on. I need to ssh to other copies of DD.

Maybe if I go back to the iso and load that I will find the DISPLAY env variable I need.

OK, well thanks for the help. I will have to try a few things and see if I can get DISPLAY set up on user puppy like you have.

Paul

edit
------
I have created another user as you suggested, but the env still does not create the DISPLAY variable for the new user.

I am going to have to create another memory stick from the iso I think thats the answer maybe.

[ocpaul20]

Couple of quick questions -
1) on boot, where do I change the boot process to login as puppy rather than as root?

2) I just want to copy a simple file from one machine to another but the scp command is executing my ~/.bashrc & ~/.profile as well which appears to make the scp fail. Am I doing something wrong?

# scp -v testfile root@192.168.1.27:/home/puppy/llabdir

the '/root' in the code below is a pwd command I have in my .bashrc file

[fredx181]

Hi Paul,

[rufwoof]

Try adding a dot to the end of that command i.e. copy to the same filename.

Or have you tried transferring files from the command line?