Applications not launching from menu [SOLVED]

[CwF]

@CwF: I think we should try to narrow down the source of the problem before applying a hacky workaround. The menu entries should work without having to bypass polkit.

Well, not quite hacky, more like official DE-agnostic method.. It does not 'bypass' polkit, it USES it! It completes the chain - the chain that is broken in more than one DE! That's why I ask the way I did and pointed towards the agent, which is not required...unless you want one.

The qualifier is simple, only user desktop. The mechanism is not required, so I propose the logical to not fix what we don't need!

[shloz]

Let's check the error messages for a fresh session.

Log out and back in again and run

Code: Select all

rm ~/.xsession-errors

Then attempt to launch synaptic from the menu and post the content of ~/.xsession-errors here but please use code tags instead of just pasting the output directly into your post.

And I really do think we need to see the output of

Code: Select all

apt policy

Please read the "Don't Break Debian" link I provided earlier — most problems of this nature are due to user misconfiguration.

@CwF: I think we should try to narrow down the source of the problem before applying a hacky workaround. The menu entries should work without having to bypass polkit.

I logged out and back in, ran rm ~/.xsession-errors, tried to launch synaptic, but there's no ~/.xsession-errors file (assuming it's supposed to be in my home/sz/ as per the ~)
The following is the output of apt policy:

Code: Select all

sz@x240:~$ apt policy
Package files:
 100 /var/lib/dpkg/status
     release a=now
 500 http://deb.debian.org/debian buster-updates/non-free amd64 Packages
     release o=Debian,a=stable-updates,n=buster-updates,l=Debian,c=non-free,b=amd64
     origin deb.debian.org
 500 http://deb.debian.org/debian buster-updates/main amd64 Packages
     release o=Debian,a=stable-updates,n=buster-updates,l=Debian,c=main,b=amd64
     origin deb.debian.org
 500 http://security.debian.org/debian-security buster/updates/non-free amd64 Packages
     release v=10,o=Debian,a=stable,n=buster,l=Debian-Security,c=non-free,b=amd64
     origin security.debian.org
 500 http://security.debian.org/debian-security buster/updates/main amd64 Packages
     release v=10,o=Debian,a=stable,n=buster,l=Debian-Security,c=main,b=amd64
     origin security.debian.org
 500 http://deb.debian.org/debian buster/non-free amd64 Packages
     release v=10.7,o=Debian,a=stable,n=buster,l=Debian,c=non-free,b=amd64
     origin deb.debian.org
 500 http://deb.debian.org/debian buster/contrib amd64 Packages
     release v=10.7,o=Debian,a=stable,n=buster,l=Debian,c=contrib,b=amd64
     origin deb.debian.org
 500 http://deb.debian.org/debian buster/main amd64 Packages
     release v=10.7,o=Debian,a=stable,n=buster,l=Debian,c=main,b=amd64
     origin deb.debian.org
Pinned packages:

[Head_on_a_Stick]

It does not 'bypass' polkit, it USES it!

Touché.

The menu entries should work without having to bypass the polkit authentication mechanism.

there's no ~/.xsession-errors file

No, of course, silly me — the errors wouldn't be written there.

Open a terminal and follow the journal to see the errors as they're written:

Code: Select all

journalctl --follow

If your user isn't in the systemd-journal group then the command will have to be run as root.

EDIT: your sources are fine btw.

[shloz]

OK here's the error when I try to launch synaptic from the menu:

Code: Select all

Feb 05 13:45:25 x240 pkexec[2103]: sz: The value for environment variable TERM contains suscipious content [USER=root] [TTY=unknown] [CWD=/home/sz] [COMMAND=/usr/sbin/synaptic]

[Head_on_a_Stick]

Code: Select all

The value for environment variable TERM contains suscipious content

^ I put this into a search engine:

https://www.digitalfoundations.com.au/b ... t-in-lxqt/

Does that help?

[shloz]

I had set the default terminal in LXQT session settings to Alacritty, now I changed it back to qterminal and everything works! Thanks for all the help. The TERM in the error message made me think of that...

[shloz]

How do I mark this as "solved"?

[Head_on_a_Stick]

Edit the title of the thread (in your first post) and prepend [SOLVED].