SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Locally mirror the Mate packages (base, deps, extra) from the msb directory on slackware.uk
Upgrade mate with them.
Repeat the last three steps with current of 2024-03-30 over this xz backdoor thing. I needn't have bothered.
On current of 2024-03-24, I could turn off the pc from the system menu in Mate, but on current of 2024-03-30, I can't. I can only log off, which Mate won't let me do if anything is running. Then I get back into sddm, which has kill & reboot buttons.
Also on current of 2024-03-24, there were two screensavers which argued. So I uninstalled one, left and set up xscreensaver. But it never comes on. I have it set for 10 minutes, and of course it doesn't interrupt zoom. But on current of 2024-03-30, after 5 minutes, the screen goes dark and the monitor powers off. It shuts down zoom, and kills the sound. Undoing that takes 15-29 seconds and I typically get 7 or so notices saying this, that & the other have gone, and then been found again
Mate archives are all dated March 31st, so I gather I have the newest ones. Does anyone have similar issues?
Distribution: Slackware 64 -current multilib from AlienBob's LiveSlak MATE
Posts: 1,071
Rep:
If I understand your post correctly, you installed all mate packages 2024-03-30. But as you write, latest mate packages are dated 2024-03-31, so there might be some difference there. You can compare your installed version numbers with the versions here: https://slackware.uk/msb/current/latest/x86_64/
and see if they correspond. Haven't checked (the changelog file at https://slackware.uk/msb/ is outdated) but maybe packages were rebuilt due to the python3 upgrade?
I remember having a conflict between mate-screensaver and xscreensaver years ago which I solved by uninstalling xscreensaver. On my present machine I have both installed without issues.
Distribution: Slackware 64 -current multilib from AlienBob's LiveSlak MATE
Posts: 1,071
Rep:
On second thought, could it be the mate power manager that interferes with zoom?
System > Preferences > Hardware > Power Manager, check the "Put display to sleep when inactive" settings.
To clarify, I installed on April 01/02, but gave the package dates. The Mate updates of 31st March were grabbed on April 2. The list in post #1 should actually have a step
3a. Sort out the resulting mess.
Hence, the lag in the dates. I have uninstalled the mate screensaver, and the xfce4 screensaver. I actually fired up XFCE today to check. It did exactly the same blank screen trick, but it complained about the lack of choice in /usr/share/wallpapers. which is empty. I don't know what was complaining, These messages were grey on grey.I did click on System > Preferences > Hardware > Power management, but it did nothing . No menus or options showed. So I re-installed the mate power manager & rebooted, but still nothing showed. So I ran the (non-running) executables from a terminal and got the following:
Code:
dec@Ebony:~$ mate-power-manager
(mate-power-manager:3116): PowerManager-ERROR **: 12:04:11.224: Error in dbus - GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper exited with unknown return code 127
Trace/breakpoint trap
dec@Ebony:~$ mate-power-preferences
(mate-power-preferences:3149): PowerManager-WARNING **: 12:05:38.930: Failed to get session for pid 3149: The name org.freedesktop.ConsoleKit was not provided by any .service files
(mate-power-preferences:3149): PowerManager-ERROR **: 12:05:38.936: Error in dbus - GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper exited with unknown return code 127
Trace/breakpoint trap
dec@Ebony:~$ mate-power-statistics
dec@Ebony:~$
The power-statistics actually ran, but as neither of the others apparently have, the output was understandably blank. The 'ldd |grep found' trick showed no missing libs.
The power-statistics actually ran, but as neither of the others apparently have, the output was understandably blank. The 'ldd |grep found' trick showed no missing libs.
The bit that gets me is turning off the monitor, which is a bit OTT for a screensaver.
Last edited by business_kid; 04-12-2024 at 06:21 AM.
Distribution: Slackware 64 -current multilib from AlienBob's LiveSlak MATE
Posts: 1,071
Rep:
when running power-management-preferences from terminal, I get
Code:
(mate-power-preferences:19256): PowerManager-WARNING **: 13:55:35.972: Failed to get session for pid 19256: The name org.freedesktop.ConsoleKit was not provided by any .service files
but then the preferences gui starts OK.
And it's odd that it doesn't run when you hit the menu button System > Preferences > Hardware > Power Management
I'm afraid that I haven't a clue to what's missing on your system.
It's odd. I'm in the Mate LiveSlak ATM and that works fine. I'll reinstall the Mate screensaver, tell xscreensaver to go and play in the traffic, and check the ~Current ChangeLog between 2024-03-24 & 2024-03-30 to see if anything pops out.
EDIT: LiveSlak also powers off fine. Neither Mate or XFCE do that.
Last edited by business_kid; 04-12-2024 at 09:25 AM.
Right. I'm calling this solved, as it partially is, and I'm not going to fart about any more with it.
I uninstalled xfce4-screensaver, xscreensaver & reinstalled Mate-screensaver. I'm now getting screen saving without powering the monitor off. I'm not getting a power-off option, but the 'log out' option actually throws me back to sddm, and I get the power-off option there. I suspect something lacks SUID root permissions, but I don't really care.
As for grokking the changelog: Gigabytes of software in ~Current and all of Mate were rebuilt in that week, which effectively ruled out learning anything that way. Errors remain
Code:
dec@Ebony:~$ mate-power-manager
(mate-power-manager:3703): PowerManager-ERROR **: 16:29:20.885: Error in dbus - GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper exited with unknown return code 127
Trace/breakpoint trap
dec@Ebony:~$ mate-power-preferences
(mate-power-preferences:3726): PowerManager-WARNING **: 16:29:34.539: Failed to get session for pid 3726: The name org.freedesktop.ConsoleKit was not provided by any .service files
(mate-power-preferences:3726): PowerManager-ERROR **: 16:29:34.544: Error in dbus - GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper exited with unknown return code 127
Trace/breakpoint trap
So I'm left with the sucky screensavers in Mate, but who watches a screensaver?
Last edited by business_kid; 04-12-2024 at 11:22 AM.
Distribution: Slackware 64 -current multilib from AlienBob's LiveSlak MATE
Posts: 1,071
Rep:
So I've got the t-shirt too...
After fiddling with the elogind issue mentioned here: https://www.linuxquestions.org/quest...-a-4175735969/ I noticed that I got exactly the same issue with power-management and the shutdown menu has disappeared...
Can't understand what has happened.
EDIT: Downgrading elogind from latest version 255.4 to 252.23 is what makes the shutdown menu to disappear and the power management to stop working. With the latest elogind I get the menu and a working power management, but instead I run into network issues after suspend/resume as described in the abovementioned thread.
Oh dear. Well, maybe some elogind fix in the near future will sort that.
Interesting. If I get that right, elogind was the issue. Let me thicken the mess:
Shutdown worked for me on Current of 2024-03-24 (the iso), but not on 2024-03-30. But I happen to still have both isos, and the elogind on both isos is identical, namely elogind-252.23-x86_64-2. I ran a diff on my local archives to be sure.
I checked the version up on current, and it's elogind-255.4 on slackware.uk, whereas 255.4-1 is the bugfix. So I won't bother with source, but simply wait a few days and upgrade to the upcoming package. According to what i read on those links, I didn't think version 252.23 was implicated, so there must be some other issue out there adding to this.
If you have elogind-252.23 installed and downgrade polkit to version 123 (from slackware.uk/cumulative) then the shutdown menu comes back and screen brightness and power manager works, as does suspend/resume.
I hope this will be resolved in future upgrades. In Pat we trust.
dec@Ebony:~$ ls -l /var/log/packages/polkit*; ls -l /var/log/packages/elogind*
-rw-r--r-- 1 root root 5884 Mar 30 19:40 /var/log/packages/polkit-123-x86_64-2
-rw-r--r-- 1 root root 1437 Jan 7 11:10 /var/log/packages/polkit-compat32-123-x86_64-1compat32
-rw-r--r-- 1 root root 6326 Mar 23 12:03 /var/log/packages/polkit-gnome-0.105-x86_64-4
-rw-r--r-- 1 root root 3144 Mar 23 12:03 /var/log/packages/polkit-qt-1-0.114.0-x86_64-1
-rw-r--r-- 1 root root 30856 Mar 23 11:05 /var/log/packages/elogind-252.23-x86_64-2
-rw-r--r-- 1 root root 1248 Jan 7 11:08 /var/log/packages/elogind-compat32-252.9-x86_64-2compat32
dec@Ebony:~$
The polkit also seems identical on both 2024-03-24 & 2024-03-30.
EDIT: If the screen blanks in a 'runlevel 3' console, I'm still getting the "Turn off the monitor" behaviour. When this gets sorted I'm going to try to stay off the bleeding edge. I'm not sure I like the 'bleeding edge' when the blood in question is mine .
Last edited by business_kid; 04-13-2024 at 01:04 PM.
Right. We'll give it a week and see what the updates throw up. If the problem =this+that+the_other, and we make one of them go away, that should solve it. OTOH, if problem=this or that or the_other, it may require a bit of thinking.
I said I'd give it a week, but a new fix of elogind has showed, elogind-255.4-r2.
I didn't find a package, so I tried building it. But it pukes lacking "audit." Whassat? It's acting like I should know, and I don't. As I laid out in post #1, my install was a little unusual, not helped by an early exit from setup2hd.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
. No menus or options showed. So I re-installed the mate power manager & rebooted, but still nothing showed. So I ran the (non-running) executables from a terminal and got the following: 
.
