Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[vic0239]

Initially I had issues sending email and had to install libssl-dev to resolve. However, this was evident in the event log as a connection error.

[MikeZ]

Finally sorted. I reinstalled Jessie to undo my previous tinkering, added your desktop script and that runs without errors.
However I wasn't getting a dslstats window even though the task was running and updating MyDSLWebStats.
I suspect that's because the desktop was still initialising when it starts. So instead of calling the dslstats executable directly as above, I call a shell script:

Code: [Select]

#!/bin/bash
sleep 10
/home/pi/dslstats/dslstats
- and that works.

I've followed these instructions and dslstats starts (and starts uploading to MDWS). However, when I connect to the Pi (it's running headless) with RDP it tries to start dslstats again (using dslstats.desktop) and I get the "already running - closing down" error and never see a DSLstats window.

I think what's happening is that DSLstats gets started upon boot when the desktop starts, then it runs again when I log in to the 'pi' account via RDP.

What I don't understand is why it's running in the background to start with and not displaying on the desktop. I've tried setting a longer sleep value in the script (60 seconds) but it makes no difference.

[MikeZ]

Initially I had issues sending email and had to install libssl-dev to resolve. However, this was evident in the event log as a connection error.

Thank you - that was the problem

[vic0239]

I've followed these instructions and dslstats starts (and starts uploading to MDWS). However, when I connect to the Pi (it's running headless) with RDP it tries to start dslstats again (using dslstats.desktop) and I get the "already running - closing down" error and never see a DSLstats window.

I think what's happening is that DSLstats gets started upon boot when the desktop starts, then it runs again when I log in to the 'pi' account via RDP.

What I don't understand is why it's running in the background to start with and not displaying on the desktop. I've tried setting a longer sleep value in the script (60 seconds) but it makes no difference.

I had this issue too which if I recall correctly was due to my VNC server using a different display number to the Pi desktop. Originally I was running tightvnc which couldn’t use display 0, so I changed to x11vnc which could. Apparently the initialisation of the VNC server causes a second iteration of the autostart items.

[roseway]

Sorry, I didn't pick this up before, but I think the above analysis is correct.

[MikeZ]

I had this issue too which if I recall correctly was due to my VNC server using a different display number to the Pi desktop. Originally I was running tightvnc which couldn’t use display 0, so I changed to x11vnc which could. Apparently the initialisation of the VNC server causes a second iteration of the autostart items.

Thanks - this looks promising. I've installed x11vnc but I obviously need to do some more configuration for it to work with xrdp as it's refusing to connect. Could I borrow your config, please?

[vic0239]

Here is my autostart file, there was no other configuration other than creating the session password. I’m connecting from a Mac using screen sharing so can't say if this will work with XRDP.

[Desktop Entry]
Encoding=UTF-8
Type=Application
Name=X11VNC
Comment=
Exec=x11vnc -forever -usepw -display :0 -ultrafilexfer
StartupNotify=false
Terminal=false
Hidden=false

[MikeZ]

Here is my autostart file, there was no other configuration other than creating the session password. I’m connecting from a Mac using screen sharing so can't say if this will work with XRDP.

Thanks - you've been very helpful It works fine with xrdp but, as I'm moving to a Mac myself (new 27" iMac on order), I've decided to use just the vnc protocol.

Everything is working fine, now - very happy with my new Pi

[vic0239]

I'm moving to a Mac myself (new 27" iMac on order)

 

[GigabitEthernet]

Finally sorted. I reinstalled Jessie to undo my previous tinkering, added your desktop script and that runs without errors.
However I wasn't getting a dslstats window even though the task was running and updating MyDSLWebStats.
I suspect that's because the desktop was still initialising when it starts. So instead of calling the dslstats executable directly as above, I call a shell script:

Code: [Select]

#!/bin/bash
sleep 10
/home/pi/dslstats/dslstats
- and that works.

Sorry for the bump but I've been trying this. I've put the code into dslstats.desktop and saved it where requested and when the system is rebooted, dslstats is not shown. I am using tightvnc and accessing the pi remotely. Is this why?

[roseway]

The problem here (I think) is that VNC accesses the RPi at command line level, and launches a separate desktop process from there. So the dslstats.desktop file which you created isn't seen by the new desktop. I'm sure there's a way round this, but for the moment perhaps you can launch DSLstats manually over the VNC interface.

[GigabitEthernet]

I'm using VNC that shows the main desktop though. I'm now connected directly and dslstats still doesn't open on boot

[GigabitEthernet]

Got it working

Edited the startup file by running:

Code: [Select]

sudo nano /home/pi/.config/lxsession/LXDE-pi/autostart
I then added dslstats to this file by adding

@/home/pi/dslstats/dslstats

to the bottom of the file. Saved it, rebooted and voila it's working 

[ejs]

Sorry for the bump but I've been trying this. I've put the code into dslstats.desktop and saved it where requested and when the system is rebooted, dslstats is not shown. I am using tightvnc and accessing the pi remotely. Is this why?

You can't put that shell script code into the dslstats.desktop autostart file, you'd need to put it into a separate file, set exec permissions on that file, and change the Exec line of dslstats.desktop to run that script.

Or, try changing the dslstats.desktop file to contain:

Code: [Select]

[Desktop Entry]
Version=1.0
Type=Application
Name=DSLstats
Exec=/bin/bash -c "sleep 10 ; exec /home/pi/dslstats/dslstats"
@GigabitEthernet
No need to use sudo to edit files in your own home directory.

[GigabitEthernet]

Thanks for the reply @ejs and for your method. I'll stick with mine until something breaks