Desktop from ports fails to load (4.1)

BuZz

I believe I have a workaround - which should be fine on any default RetroPie install where ES is launched from tty1 - if launched from another tty it will probably not work. I will possibly be able to make this less hardcoded when I integrate it into retropie - but I want to test a few more things first.

For the Desktop entry in ports, please edit /opt/retropie/configs/ports/lxde/emulators.cfg and make it look like

lxde = "startx -- vt1 -keeptty"
default = "lxde"

BuZz

Ignore my instructions above - I have now committed my changes to github.

Please update RetroPie-Setup - you should get v4.1.7. You will need to restart the system, and it should be all working again.

sonicsheppard

Excellent, thank you so much @BuZz . Would this fix also be appropriate for the OpenXCom issue I raised and believed to be the same thing?

Unfortunately I won't be able to test this out for a few days, but can test it out asap if it should hopefully resolve that issue too.

Thanks again!

BuZz

@sonicsheppard I don't know - but if it's an X app that used to work, and then didn't, probably.

sonicsheppard

Cool, I believe it was, and the error looked very similar to the one for LXDE. Will check it out next week unless someone else beats me to the punch.

Got some Aquatoids that need killing on TFTD :).

Cheers!

BuZz

I had to commit another fix - v4.1.8 should be working. Overtired and getting over the flu (and going to bed now!). Cheers.

funkyspider

Works perfectly now. I've built a install on a new SD card and will swap over from the multi-boot I built giving a much simpler system.

Thanks to everyone for their input, and to @BUZZ for dragging himself from his sick bed to fix this !

columboscoat

@funkyspider multiboot is shite. Berryboot is the worst. Best thing to do for a triple system is install Raspian or Retropie image and then add what you want on top. Kodi / RetroPie/ Pixel Desktop.... all easily accessible from each other. Rather than rebooting each time

sonicsheppard

Hi @BuZz , unfortunately this is still an issue for openxcom, as descriped above. I've commented on my other thread - https://retropie.org.uk/forum/topic/6491/openxcom-no-longer-working-after-installing-from-experimental-menu/3.

Please let me know if any additional info or output is required.

Side note, this issue has also reared it's head since I updated to 4.1.8 - https://retropie.org.uk/forum/topic/5296/help-keyboard-not-working/10. I have commented that thread also.

Thanks.

BuZz

it won't work with that script automatically. They need to start with xinit or startx or need to do some manual changes to the launch code.

Albertpaella

Hey guys! This is still happenning for me, I installed the last version yesterday and it continue happennig. Do you know if any solution has been found? Thnaks very much for the help!!!

BuZz

@Albertpaella you provided no information. See the link in my signature.

Albertpaella

@BuZz Sorry for the last post. I am using raspberry Pi 3, I have installed retropie 4.1 from a SD card and then I have installed raspbien and the pixel desktop from retopie options. When I try to launch the desktop from the emulationstation using Ports I get several errors and the desktop environment does no launch.

BuZz

@Albertpaella yes. You need to update all packages. It's fixed, but not if you don't update :)

Albertpaella

@BuZz Hello! I have updated all installed packages through the option in retropie configuration menu, I have also updated raspbian and pixel in configuration/tools menu. I have done several reboots but it continues to fail to launch desktop environment from ports. Is there any other to update to fix this problem? Thank you so much for your help!

columboscoat

This post is deleted!

douber

@BuZz Also went with every update possible. Still, no Desktop loading from EmulationStation. Worst, even if I set the RPI to boot directly to LXDE, I see the desktop for milliseconds before it goes directly to command line. Something with login maybe?

BuZz

@douber this topic is solved - your problem may be due to something else entirely

Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first

(Open a new topic providing details).

Rhif

I still got this error in 2021 when I installed chromium in retropie using zerojay/RetroPie-Extra, so i thought i'd chime in with my fix that worked after looking at other's comments and suggestions.
I needed to set the /dev/tty* files/folders to be readable.
so in commandline;
cd /dev/
sudo chmod 666 tty*

hope this helps someone.