I used to be able to launch a pixel desktop from the "ports" menu of retropi when I was running Buster.
I tried to pull of the same functionality with the wayfire desktop after switching to Bookworm 64bit.
Perhaps this is due to the incompatibility mentioned by retropie when I manualy installed it over the Bookworm os.
Note I have no problem launching the desktop after a login by typing wayfire. Or startx or even "wf" after I wrote a little script to do that. Right at the system prompt After a bootup.
What I can't seam to do is use the "desktop" item in the ports menu of retropi.
First off, I had to install another port I didn't care for just to get the "ports" menu to even show up. Apparently having a~/RetroPie/roms/ports directory containing a "Desktop.sh" file wasn't enough to make "ports" show up.
What happens when I select "desktop" from the ports menu...
The launching script "desktop.sh" starts and Apparently fails. I am brought back to the ports menu after some screen blanking.
So I tried to play around with the script manually to try to trap the error.
I commented out the launcy bits and just put in a simple echo "completed" command.
I am getting bash: command not found.
From just a simple echo "completed" command. Even if I specify the path /usr/bin/echo "completed"
Unless I launch the script by typing a dot slash before the script name like
"./<script.sh>"
or a "bash <script.sh>"
But not if I just type script.sh alone.
Did scripting rules change?
This seams to be a problem for the retropies launching script.
I like being able to launch into my desktop by selecting a menu option but have had to resign to hitting f4 and typing startx or something.
More to say... I can launch into my desktop by typing ./Desktop.sh after having un-commenting the launcy bits and removing my echo. Command again.
So the script "can work" if it's launched with the "./" or if "bash" is specified first.
I tried to pull of the same functionality with the wayfire desktop after switching to Bookworm 64bit.
Perhaps this is due to the incompatibility mentioned by retropie when I manualy installed it over the Bookworm os.
Note I have no problem launching the desktop after a login by typing wayfire. Or startx or even "wf" after I wrote a little script to do that. Right at the system prompt After a bootup.
What I can't seam to do is use the "desktop" item in the ports menu of retropi.
First off, I had to install another port I didn't care for just to get the "ports" menu to even show up. Apparently having a~/RetroPie/roms/ports directory containing a "Desktop.sh" file wasn't enough to make "ports" show up.
What happens when I select "desktop" from the ports menu...
The launching script "desktop.sh" starts and Apparently fails. I am brought back to the ports menu after some screen blanking.
So I tried to play around with the script manually to try to trap the error.
I commented out the launcy bits and just put in a simple echo "completed" command.
I am getting bash: command not found.
From just a simple echo "completed" command. Even if I specify the path /usr/bin/echo "completed"
Unless I launch the script by typing a dot slash before the script name like
"./<script.sh>"
or a "bash <script.sh>"
But not if I just type script.sh alone.
Did scripting rules change?
This seams to be a problem for the retropies launching script.
I like being able to launch into my desktop by selecting a menu option but have had to resign to hitting f4 and typing startx or something.
More to say... I can launch into my desktop by typing ./Desktop.sh after having un-commenting the launcy bits and removing my echo. Command again.
So the script "can work" if it's launched with the "./" or if "bash" is specified first.
Statistics: Posted by LPSeg13 — Sun Aug 04, 2024 1:11 pm — Replies 0 — Views 20