LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Software (https://www.linuxquestions.org/questions/linux-software-2/)
-   -   Installed program fails to run at other profile (https://www.linuxquestions.org/questions/linux-software-2/installed-program-fails-to-run-at-other-profile-4175671999/)

UNeverNo 03-26-2020 04:35 AM

Installed program fails to run at other profile
 
I installed a program called lucaschess with my sudo-profile from https://github.com/lukasmonk/lucasch...e/master/Linux (see xlinux_install.sh) and can run it using xlucas.sh afterwards.
But when another user tries to run it, it fails without an error message.

The normal behaviour is to run the sh-file. It then logs 'x86_64' to console and starts the GUI where one can select a language.
On the other user's profile it just logs 'x86_64' and that's it.

Is there a way to find out, why it fails?

I'm running Ubuntu 18.04 if that matters.

sevendogsbsd 03-26-2020 07:25 AM

Where is the software installed? What path?

Shadow_7 03-26-2020 07:57 AM

If the installer put stuff in $HOME of the user that installed it, that wont exist on the $HOME of the "other" user.

But it depends on what you mean by "other" user. Cold boot and log in as someone else? Or su / sudo to someone else in an already running GUI? I tend to su / sudo to someone else. Which requires $( xhost local: ) for the user who launched the GUI / X session to "share" the gui environment. With various other trickery to "share" the audio environment if using pulseaudio.

And then there's some software that's just poorly designed and will only work for the one who installed it. They might call that a feature or "licensing".

UNeverNo 03-28-2020 12:15 PM

Quote:

Originally Posted by sevendogsbsd (Post 6104524)
Where is the software installed? What path?

I copied the git repo to /opt.

Quote:

Originally Posted by Shadow_7 (Post 6104541)
If the installer put stuff in $HOME of the user that installed it, that wont exist on the $HOME of the "other" user.

But it depends on what you mean by "other" user. Cold boot and log in as someone else? Or su / sudo to someone else in an already running GUI? I tend to su / sudo to someone else. Which requires $( xhost local: ) for the user who launched the GUI / X session to "share" the gui environment. With various other trickery to "share" the audio environment if using pulseaudio.

And then there's some software that's just poorly designed and will only work for the one who installed it. They might call that a feature or "licensing".

I was talking about log out and log in with another user. Normally I install something with sudo and everyone can use it.

Is there a way to find out if this software is installing something to $HOME? Are there any system logs?

Shadow_7 03-28-2020 02:29 PM

They'll be files in $HOME. You could also strace it and filter out the "Open" commends. See what it's looking at when it runs. Do it on the failed user account and see what it's NOT finding at the point that it fails. Could also be a group or something the user needs to be in. AKA permissions.

sevendogsbsd 03-28-2020 05:15 PM

Check to see if /opt is in your path. Also, does it need to be built? If the app is a binary and the git repo is just source code, that’s not going to do anything.

FlinchX 04-01-2020 02:18 AM

Might be worth pinging the author by bumping the years old issue that requested an official AppImage.

UNeverNo 04-08-2020 07:33 AM

Sorry for the late reply. It's the kids computer and they had some heavy corona-homework.

I updated the system to 20.04 Beta because there was another issue and now it doesn't even run at my profile.

So I tried wine with the portable version and it seems to do fine.


All times are GMT -5. The time now is 09:20 PM.