|
|
Post by beardyboy40 on Apr 1, 2021 18:37:38 GMT
Hi folks Its not a big deal but I am getting an annoying start up error message when I boot into the desktop.
Message is /home/ryan/.e/e/applications/startup/startupcommands stopped running unexpectedly I have had a look in the file and this is what I am seeing:
xrandr --output HDMI-2 --off --output HDMI-1 --primary --mode 1600x900 --pos 1366x0 --rotate normal --output DP-1 --off --output eDP-1 --mode 1366x768 --pos 0x0 --rotate normal --output DP-2 --off I am guessing this is to do with the fact that I set it up by default to operate across 2 screens so when i log in on just the laptop it is throwing up this error? I did save the two screen configuration in the settings as otherwise I kept having to move the panel to the bigger screen every time I logged in,
|
|
enigma9o7
Crew Member
Posts: 1,427 
Likes: 1,336
|
Post by enigma9o7 on Apr 1, 2021 19:20:34 GMT
Hi folks Its not a big deal but I am getting an annoying start up error message when I boot into the desktop.
Message is /home/ryan/.e/e/applications/startup/startupcommands stopped running unexpectedly I have had a look in the file and this is what I am seeing:
xrandr --output HDMI-2 --off --output HDMI-1 --primary --mode 1600x900 --pos 1366x0 --rotate normal --output DP-1 --off --output eDP-1 --mode 1366x768 --pos 0x0 --rotate normal --output DP-2 --off
I am guessing this is to do with the fact that I set it up by default to operate across 2 screens so when i log in on just the laptop it is throwing up this error? I did save the two screen configuration in the settings as otherwise I kept having to move the panel to the bigger screen every time I logged in,
Yeah I have a similar issue too. This is how I solved it:
if ! xrandr --output VGA-0 --off --output LVDS-0 --primary --mode 1920x1080 --pos 0x0 --rotate normal --output HDMI-0 --mode 1920x1080 --pos 0x0 --rotate normal ; then
echo "Cannot enable HDMI when nothings turned on, dumb thing, but cant let moksha see the error when it fails"
fi
I grabbed that straight out of my ~/.e/e/applications/startup/startupcommands that I had modified to deal with my situation, which is, if the xrandr command to configure the 2nd screen is sent when my tv is turned off, then it fails. By adding "if !" before it and "; then" after it, that makes it deal with the failure there, so moksha doesnt see the failure as the last exit code from startup script. the way I deal with it is just send a message, but could be any command there, the word echo by itself or true by itself would be fine too, there is no terminal open so nowhere to see the echo output I put anyway. You could use this directly: startupcommands (248 B) |
|
|
|
Post by beardyboy40 on Apr 1, 2021 19:42:36 GMT
Worked like a charm. Thanks very much! Appreciated.  |
|
