You are not logged in.
Hi
Recently I installed 3 computers from scratch. they should have the same desktop appearance. mate desktop, no big deal.
However they came out different. In one install the mate desktop/ panel / system menus / shutdown button is missing
Did not find out how to get it back. the other 2 have it.
All three have different HW and age. (2010 2 cores, 2017 2 cores, 2019 12 cores)
I now wonder why 2 have the shutdown button but the one of 2010 not. Although it had it before the HDD crash.
Last edited by bai4Iej2need (2023-05-09 13:54:07)
The devil, you know, is better than the angel, you don't know. by a British Citizen, I don't know too good.
One generation abandons the enterprises of another like stranded vessels. By Henry David Thoreau, WALDEN, Economy. Line 236 (Gutenberg text Version)
broken by design :
https://bugs.debian.org/cgi-bin/bugrepo … bug=958390
Offline
Investigate what caused the HDD crash, and attribute the change to the crash.
Online
Investigate what caused the HDD crash, and attribute the change to the crash.
The HDD crash was caused by the old age and 11 years of operation .
Certain ranges in my home directory were affected, but that has been fixed with backups. nothing in /etc /usr/ was affected
As I have written, the install was from scratch.
The devil, you know, is better than the angel, you don't know. by a British Citizen, I don't know too good.
One generation abandons the enterprises of another like stranded vessels. By Henry David Thoreau, WALDEN, Economy. Line 236 (Gutenberg text Version)
broken by design :
https://bugs.debian.org/cgi-bin/bugrepo … bug=958390
Offline
Make sure policykit-1-gnome is installed. If that doesn't do it, check some other discussions here about the same thing. If all the installs are supposed to be the same, compare the package lists. This will create a package list:
dpkg -l | awk '/^ii/ { print $2 }' > package-list
Offline
Assuming the system where the mate components are missing is the one that had the HDD crash:
Check the config files in your home dir. And compare them with the systems that are OK. That sounds the most likely cause if the OS is identical.
Offline
Make sure policykit-1-gnome is installed.
Yes it is installed.
Check the config files in your home dir.
I checked , the problem is not in the $HOME.
Thanks for the help, this hint is leading to the right direction.
When starting both as user 1000 or 1001 , the item is not there.
But doing startx as root, the shutdown menu item it present.
therefore everything is installed as should be,
giving the users >=1000 the rights to access the shutdown menu will solve the puzzle.
The devil, you know, is better than the angel, you don't know. by a British Citizen, I don't know too good.
One generation abandons the enterprises of another like stranded vessels. By Henry David Thoreau, WALDEN, Economy. Line 236 (Gutenberg text Version)
broken by design :
https://bugs.debian.org/cgi-bin/bugrepo … bug=958390
Offline
Compare what groups the users are in on the faulty system and both the working systems. And how sudo (or doas) is configured on them.
Offline
Now I found the difference
bad computer :
May 9 16:10:25 lenovo-r500 x-session-manager[6629]: WARNING: Could not make DBUS call: Failed to execute program org.freedesktop.PolicyKit1: Permission denied
Now I fight these strange program names, which are not reflected in the ps -tree
May 9 16:14:31 lenovo-r500 dbus-daemon[1789]: [system] Activating service name='org.freedesktop.PolicyKit1' requested by ':1.1497' (uid=1000 pid=8547 comm="/usr/lib/x86_64-linux-gnu/polkit-mate/polkit-mate-") (using servicehelper)
May 9 16:14:31 lenovo-r500 dbus-daemon[1789]: [system] Activated service 'org.freedesktop.PolicyKit1' failed: Failed to execute program org.freedesktop.PolicyKit1: Permission denied
May 9 16:14:31 lenovo-r500 dbus-daemon[1789]: [system] Activating service name='org.freedesktop.PolicyKit1' requested by ':1.0' (uid=0 pid=2142 comm="elogind-daemon ") (using servicehelper)
May 9 16:14:31 lenovo-r500 dbus-daemon[1789]: [system] Activated service 'org.freedesktop.PolicyKit1' failed: Failed to execute program org.freedesktop.PolicyKit1: Permission denied
The command
comm="/usr/lib/x86_64-linux-gnu/polkit-mate/polkit-mate-"
line is not complete
the only file in the directory is named /usr/lib/x86_64-linux-gnu/polkit-mate/polkit-mate-authentication-agent-1
The command is given to the dbus daemon dynamically, not in the commandline
apt-file search /usr/lib/x86_64-linux-gnu/polkit-mate/polkit-mate-authentication-agent-1
mate-polkit: /usr/lib/x86_64-linux-gnu/polkit-mate/polkit-mate-authentication-agent-1
I reinstalled mate-polkit, but the wrong command is created somewhere upstream dbus-daemon
netstat -pe | grep 1789
unix 3 [ ] STREAM VERBUNDEN 1843695 1789/dbus-daemon /run/dbus/system_bus_socket
unix 3 [ ] STREAM VERBUNDEN 15114 1789/dbus-daemon
unix 3 [ ] STREAM VERBUNDEN 1844316 1789/dbus-daemon /run/dbus/system_bus_socket
unix 3 [ ] STREAM VERBUNDEN 15115 1789/dbus-daemon
unix 3 [ ] STREAM VERBUNDEN 1843633 1789/dbus-daemon /run/dbus/system_bus_socket
unix 3 [ ] STREAM VERBUNDEN 17893 2518/ntpd
unix 2 [ ] DGRAM 2220616 1789/dbus-daemon
unix 3 [ ] STREAM VERBUNDEN 17894 2518/ntpd
unix 3 [ ] STREAM VERBUNDEN 1843969 1789/dbus-daemon /run/dbus/system_bus_socket
unix 3 [ ] STREAM VERBUNDEN 1843355 1789/dbus-daemon /run/dbus/system_bus_socket
unix 3 [ ] STREAM VERBUNDEN 2188007 1789/dbus-daemon /run/dbus/system_bus_socket
unix 3 [ ] STREAM VERBUNDEN 1843535 1789/dbus-daemon /run/dbus/system_bus_socket
unix 3 [ ] STREAM VERBUNDEN 1843493 1789/dbus-daemon /run/dbus/system_bus_socket
unix 3 [ ] STREAM VERBUNDEN 1844931 1789/dbus-daemon /run/dbus/system_bus_socket
unix 3 [ ] STREAM VERBUNDEN 17598 1789/dbus-daemon /run/dbus/system_bus_socket
Last edited by bai4Iej2need (2023-05-10 10:26:45)
The devil, you know, is better than the angel, you don't know. by a British Citizen, I don't know too good.
One generation abandons the enterprises of another like stranded vessels. By Henry David Thoreau, WALDEN, Economy. Line 236 (Gutenberg text Version)
broken by design :
https://bugs.debian.org/cgi-bin/bugrepo … bug=958390
Offline