Desktop from ports fails to load (4.1)

wally.yeh

@BuZz : thank you for your attention. :D
BTW I tried fresh install RetroPie 4.1 yesterday, it also have this issue.

sonicsheppard

Ah glad I spotted this, I believe this is the exact same issue I'm experiencing with the port openxcom from the experimental menu when compiling from sources.

https://retropie.org.uk/forum/topic/6491/openxcom-no-longer-working-after-installing-from-experimental-menu

Thanks very much.

funkyspider

@gameaddict20 Thank you so much for investigating this and finding the problem and a workaround. I hope an official fix is formulated for 4.1.x

I suspect this is going to affect a few people, I'm surprised more haven't found it. Maybe most people don't try to run desktop, but it also affected other applications launched from 'Ports' menu (chromium browser, Iceweasel etc).

In the end I ran out of time and had to go with a multi-boot solution, which wasn't the simple solution I wanted. However I enjoyed setting up the pi system so much I'm ordering one for myself to play with so I'll give this a try when it arrives and swap the SD cards over if it works.

I was surprised kodi launched correctly from within emulationstation.

BuZz

I will be looking into this. Unfortunately I've spent most of the Xmas break in bed with a high fever, so no time for coding.

herb_fargus

some more discussion - not really raspberry pi but similar issue:

https://bugs.launchpad.net/ubuntu/+source/xinit/+bug/1562219

looking into it as well, though I'm sure @BuZz will come up with a more elegant solution than whatever hack I generate once he is on the mend.

funkyspider

@BuZz Sounds like the flu has got you. I'm sure everyone wishes you a speedy recovery and I'm sure noone would expect you to be delving into code during Christmas anyway !
Keep hydrated and get better soon. It'll all be sorted in good time.

Rascas

Did anybody solved it already ? Here is what fixes it for me:

sudo su
printf 'SUBSYSTEM=="input", GROUP="input", MODE="0660"\nKERNEL=="tty[0-9]*", GROUP="tty", MODE="0660"' > /etc/udev/rules.d/99-input.rules
exit

What really "solves" it, is chmoding 0660 /dev/tty*. It was the only way I found to fix it.

funkyspider

@Rascas said in Desktop from ports fails to load (4.1):

Did anybody solved it already ? Here is what fixes it for me:
sudo su
printf 'SUBSYSTEM=="input", GROUP="input", MODE="0660"\nKERNEL=="tty[0-9]*", GROUP="tty", MODE="0660"' > /etc/udev/rules.d/99-input.rules
exit
What really "solves" it, is chmoding 0660 /dev/tty*. It was the only way I found to fix it.

Hi.
Can you give a step-by-step for this "fix" for people who may not be familiar with running terminal from emulationstation and chmod.

Many thanks

BuZz

@Rascas I may well have to do something like that, but it's not nice security wise etc. Am looking into it.

Rascas

@BuZz Yeah, I know. Or downgrading the X server packages can also be a solution.

BuZz

@Rascas I have a ticket here - https://github.com/RetroPie/RetroPie-Setup/issues/1805 - I'm trying a few ideas.

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.