Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

XDG_RUNTIME_DIR not set in the environment #453

Closed
matenkoH opened this issue Mar 20, 2019 · 4 comments
Closed

XDG_RUNTIME_DIR not set in the environment #453

matenkoH opened this issue Mar 20, 2019 · 4 comments
Assignees
Labels

Comments

@matenkoH
Copy link

Hello,
I would like to run Amiberry 2.25 on Odroid-XU4 platform with DietPi 6.21.1 installed on it. I followed the installation guide on this wiki and compiled SDL2 for xu4 platform, after that installed Amiberry also as per guide. After all is set when I trigger run.sh I got following error:

error: XDG_RUNTIME_DIR not set in the environment.

Any ideas where could be the problem?
Thank you.

@midwan
Copy link
Collaborator

midwan commented Mar 20, 2019

@matenkoH
Hm, I think that sounds like a DietPi-specific issue rather than an Amiberry one.

@Fourdee - do you have any suggestions? Should this be opened on DietPi's repo instead?

@midwan
Copy link
Collaborator

midwan commented Mar 28, 2019

Some related answers here: https://askubuntu.com/questions/872792/what-is-xdg-runtime-dir
and here: https://serverfault.com/questions/388840/good-default-for-xdg-runtime-dir

Either way, this is related to the distro and not the emulator itself...

@midwan midwan self-assigned this Mar 28, 2019
@midwan
Copy link
Collaborator

midwan commented Apr 4, 2019

Closing this, as we can't fix it from the emulator side.

@midwan midwan closed this as completed Apr 4, 2019
@MichaIng
Copy link
Contributor

MichaIng commented Nov 3, 2019

@matenkoH @midwan
Just fall over this, while searching for DietPi-specific issues with Amiberry. The issue should have been resolved with DietPi v6.23, where we added dbus + libpam-systemd install and unmask of systemd-logind service. This was to solve another issue: #514

Background: For login sessions, systemd-logind is responsible to register those sessions with pam_systemd, which creates the XDG_* session variables. In server setups this is not required, hence we mask this service (if not chosen differently via dietpi.txt), which saves around 10 MiB RAM and reduces tasks and logs on every login/shell session/sudo call etc. Instead it is installed/unmasked automatically when installing any desktop, and since v6.23 as well when installing Amiberry.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants