Programs Immediately Closing From Desktop When Trying To Open

Hello,

I am currently running Debian and I'm having a problem with opening some programs from my desktop. Here are the technical details of my hardware / software:

- Debian GNU/Linux 9.9 (stretch)
- architecture = armv7l

The problem is that when I go to open a few programs (web browser, TeamViewer, etc), they try to open for a brief second and then close down. This just recently started happening for some reason.

Does anyone have an idea of what is going on?

Thanks in advance!

Can you please start one of the programs from the command line and paste the terminal output here. Thanks.

Originally Posted by hydrurga Can you please start one of the programs from the command line and paste the terminal output here. Thanks.

Sorry, I forgot to include that.... The last line of output is 'Abort' or 'Aborted' - I can't remember exactly, but I will know for sure tomorrow.

There were about 3 or 4 lines of output total.

I've had similar quirks, although not unsuspected for my use case. One user starts X. Other users try to launch X apps and they fail. The user who started X didn't change permissions $(xhost local to allow other users to use X. Basically a permissions issue. Also some things are picky about ONLY running for user 1000.

$ id

Although I suspect your case might be more compiler related. armv71 trying to run something for aarch64 or armv4 or armv6 or whatever applies. Although in theory backwards compatible with the earlier generation opcodes.

You could try deleting the .cache and .browser (.mozilla?) and see if those things start again. Assuming they used to work. Could have been an update too, try to update again and see if it gets fixed. Make sure $DISPLAY is set.

$ echo $DISPLAY

Debian changed something and other users who didn't start X don't assume DISPLAY values or inherit it from other users. I have to $(export DISPLAY=":0") before I launch any gui apps, even when X is shared, for users that didn't start X.

And then there's other quirks like read-only / filesystem. $(mount). Or a soundcard requirement and it's locked / in use by another user. By default pulse does not share, nor do jackd. And various audio application that require /etc/hosts to contain an entry for /etc/hostname or they fail. You could strace the application to see what it's trying to "OPEN" when it fails. See if it exists, make it exist (install not installed package / other trickery) and see if it doesn't fail. Lots of trickery, sometimes distros do not get the dependencies just right, but installs the thing anyway. Or you install it by non-distros means and it doesn't check for dependencies and otherwise makes assumptions.

Here is a picture of the error when trying to open Google Chrome (see attached).

Thx

Permission denied.
GPU failed to adjust.

Seems like your video drivers are not up to par, or your permissions are bad.

$ groups

$ glxinfo | head -n 6

Originally Posted by Shadow_7 Permission denied. GPU failed to adjust. Seems like your video drivers are not up to par, or your permissions are bad. $ groups $ glxinfo | head -n 6

Thank for this... see attached.

In the video group and direct rendering = yes. Is the DISPLAY variable set?

$ echo $DISPLAY

Does it equal the glxinfo output of :0.0 ?

Although many things will say the DISPLAY is not set as the error if you launch it from a terminal. Granted the very first line which might have scrolled away. Beyond that SIG 11 is the application crashed. Perhaps strace it and see what the last thing it tried to do was. Like open a file, and it doesn't exist or the / is full or read-only. Lots of possibilities.

Check permissions on your /home/$USER folders. If you ran something as root it could have changed ownership and you can't write to the required places anymore. Instant software failure. I got my .config folder owned as root when testing a script, caused exactly this problem.

Originally Posted by Shadow_7 In the video group and direct rendering = yes. Is the DISPLAY variable set? $ echo $DISPLAY Does it equal the glxinfo output of :0.0 ? Although many things will say the DISPLAY is not set as the error if you launch it from a terminal. Granted the very first line which might have scrolled away. Beyond that SIG 11 is the application crashed. Perhaps strace it and see what the last thing it tried to do was. Like open a file, and it doesn't exist or the / is full or read-only. Lots of possibilities.

I have attached a pic of the output of 'echo $DISPLAY', 'groups', and 'glxinfo | head -n 6'.

Thx

Originally Posted by jmgibson1981 Check permissions on your /home/$USER folders. If you ran something as root it could have changed ownership and you can't write to the required places anymore. Instant software failure. I got my .config folder owned as root when testing a script, caused exactly this problem.

Hmm, you 'might' be on to something... I did a bunch of updates and TeamViewer seemed to open / work, but then it stopped working a short time thereafter.

I did the following (I think):

sudo apt-get update
sudo apt-get upgrade

Thx