You are not logged in.
- Topics: Active | Unanswered
#1 2021-12-04 14:43:13
- taiongh
- Member
- Registered: 2018-10-04
- Posts: 75
[SOLVED]mate-power-manager，Can't work.
A very fancy solution:
Install the mate-Screensaver, then set it to cancel the screensaver, and your computer won't go black and restart automatically.
If not, install mate-tweak.
The computer will automatically go black after a period of idleness, and then automatically restart after a few minutes.
Today, I suspected that the power manager was not working, and I found an error after the terminal input command:
[taizongh@ZhuFengGeShi ~]$ sudo mate-power-manager
(mate-power-manager:41097): PowerManager-WARNING **: 22:39:44.732: Using X11 for dbus-daemon autolaunch was disabled at compile time, set your DBUS_SESSION_BUS_ADDRESS instead
(mate-power-manager:41097): PowerManager-ERROR **: 22:39:44.732: This program cannot start until you start the dbus session service.
This is usually started automatically in X or mate startup when you start a new session.What should I do specifically?Thinks.
Last edited by taiongh (2021-12-14 13:19:26)
Offline
#2 2021-12-05 13:36:37
- Lone_Wolf
- Administrator
- From: Netherlands, Europe
- Registered: 2005-10-04
- Posts: 15,312
Re: [SOLVED]mate-power-manager，Can't work.
How are you starting X (display manager, startx/xinit , none of the previous ) ?
Please post the output of systemctl status
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
#3 2021-12-05 16:11:24
- Alad
- Wiki Admin/IRC Op
- From: Bagelstan
- Registered: 2014-05-04
- Posts: 2,420
- Website
Re: [SOLVED]mate-power-manager，Can't work.
Don't run mate-power-manager as root.
Mods are just community members who have the occasionally necessary option to move threads around and edit posts. -- Trilby
Offline
#4 2021-12-07 12:43:13
- taiongh
- Member
- Registered: 2018-10-04
- Posts: 75
Re: [SOLVED]mate-power-manager，Can't work.
Lone_Wolf wrote:
How are you starting X (display manager, startx/xinit , none of the previous ) ?
Please post the output of systemctl status
The output is as follows:
[taizongh@ZhuFengGeShi ~]$ systemctl list-units
UNIT >
proc-sys-fs-binfmt_misc.automount >
sys-devices-pci0000:00-0000:00:02.0-drm-card0-card0\x2deDP\x2d1-intel_backlig>
sys-devices-pci0000:00-0000:00:14.0-usb1-1\x2d3-1\x2d3:1.0-bluetooth-hci0.dev>
sys-devices-pci0000:00-0000:00:17.0-ata2-host1-target1:0:0-1:0:0:0-block-sda->
sys-devices-pci0000:00-0000:00:17.0-ata2-host1-target1:0:0-1:0:0:0-block-sda.>
sys-devices-pci0000:00-0000:00:17.0-ata3-host2-target2:0:0-2:0:0:0-block-sdb->
sys-devices-pci0000:00-0000:00:17.0-ata3-host2-target2:0:0-2:0:0:0-block-sdb->
sys-devices-pci0000:00-0000:00:17.0-ata3-host2-target2:0:0-2:0:0:0-block-sdb->
sys-devices-pci0000:00-0000:00:17.0-ata3-host2-target2:0:0-2:0:0:0-block-sdb->
sys-devices-pci0000:00-0000:00:17.0-ata3-host2-target2:0:0-2:0:0:0-block-sdb->
sys-devices-pci0000:00-0000:00:17.0-ata3-host2-target2:0:0-2:0:0:0-block-sdb.>
sys-devices-pci0000:00-0000:00:1c.4-0000:02:00.0-net-wlp2s0.device >
sys-devices-pci0000:00-0000:00:1c.5-0000:03:00.0-net-enp3s0.device >
sys-devices-pci0000:00-0000:00:1f.3-sound-card0-controlC0.device >
sys-devices-platform-serial8250-tty-ttyS0.device >
sys-devices-platform-serial8250-tty-ttyS1.device >
sys-devices-platform-serial8250-tty-ttyS10.device >
sys-devices-platform-serial8250-tty-ttyS11.device >
sys-devices-platform-serial8250-tty-ttyS12.device >
sys-devices-platform-serial8250-tty-ttyS13.device >
sys-devices-platform-serial8250-tty-ttyS14.device >
sys-devices-platform-serial8250-tty-ttyS15.device >
sys-devices-platform-serial8250-tty-ttyS16.device >
sys-devices-platform-serial8250-tty-ttyS17.device >
sys-devices-platform-serial8250-tty-ttyS18.device >
sys-devices-platform-serial8250-tty-ttyS19.device >
sys-devices-platform-serial8250-tty-ttyS2.device >
sys-devices-platform-serial8250-tty-ttyS20.device >
sys-devices-platform-serial8250-tty-ttyS21.device >
sys-devices-platform-serial8250-tty-ttyS22.device >
sys-devices-platform-serial8250-tty-ttyS23.device >
sys-devices-platform-serial8250-tty-ttyS24.device >
sys-devices-platform-serial8250-tty-ttyS25.device >
sys-devices-platform-serial8250-tty-ttyS26.device >
sys-devices-platform-serial8250-tty-ttyS27.device >
sys-devices-platform-serial8250-tty-ttyS28.device >
sys-devices-platform-serial8250-tty-ttyS29.device >
sys-devices-platform-serial8250-tty-ttyS3.device >
sys-devices-platform-serial8250-tty-ttyS30.device >
sys-devices-platform-serial8250-tty-ttyS31.device >
sys-devices-platform-serial8250-tty-ttyS4.device >
sys-devices-platform-serial8250-tty-ttyS5.device >
sys-devices-platform-serial8250-tty-ttyS6.device >
sys-devices-platform-serial8250-tty-ttyS7.device >
sys-devices-platform-serial8250-tty-ttyS8.device >
sys-devices-platform-serial8250-tty-ttyS9.device >
sys-devices-virtual-misc-rfkill.device >
sys-module-configfs.device >
sys-module-fuse.device >
sys-subsystem-bluetooth-devices-hci0.device >
sys-subsystem-net-devices-enp3s0.device >
sys-subsystem-net-devices-wlp2s0.device >
-.mount >
boot.mount >
dev-hugepages.mount >
dev-mqueue.mount >
run-user-1000-gvfs.mount >
run-user-1000.mount >
sys-fs-fuse-connections.mount >
sys-kernel-config.mount >
sys-kernel-debug.mount >
sys-kernel-tracing.mount >
tmp.mount >
systemd-ask-password-console.path >
systemd-ask-password-wall.path >
init.scope >
session-2.scope >
accounts-daemon.service >
bluetooth.service >
dbus.service >
kmod-static-nodes.service >
lightdm.service >
lvm2-monitor.service >
NetworkManager.service >
polkit.service >
systemd-backlight@backlight:intel_backlight.service >
systemd-fsck@dev-sdb5.service >
systemd-journal-flush.service >
systemd-journald.service >
systemd-logind.service >
systemd-modules-load.service >
systemd-random-seed.service >
systemd-remount-fs.service >
systemd-sysctl.service >
systemd-tmpfiles-setup-dev.service >
systemd-tmpfiles-setup.service >
systemd-udev-trigger.service >
systemd-udevd.service >
systemd-update-utmp.service >
systemd-user-sessions.service >
udisks2.service >
upower.service >
user-runtime-dir@1000.service >
user@1000.service >
wpa_supplicant.service >
-.slice >
system-getty.slice >
system-modprobe.slice >
system-systemd\x2dbacklight.slice >
system-systemd\x2dfsck.slice >
system.slice >
user-1000.slice >
user.slice >
dbus.socket >
dm-event.socket >
lvm2-lvmpolld.socket >
systemd-coredump.socket >
systemd-journald-audit.socket >
systemd-journald-dev-log.socket >
systemd-journald.socket >
systemd-rfkill.socket >
systemd-udevd-control.socket >
systemd-udevd-kernel.socket >
basic.target >
bluetooth.target >
cryptsetup.target >
getty.target >
graphical.target >
local-fs-pre.target >
local-fs.target >
multi-user.target >
network.target >
nss-user-lookup.target >
paths.target >
remote-fs.target >
slices.target >
sockets.target >
sound.target >
swap.target >
sysinit.target >
timers.target >
veritysetup.target >
man-db.timer >
shadow.timer >
systemd-tmpfiles-clean.timer >
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
135 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
lines 120-142/142 (END)
local-fs-pre.target loaded active active Preparation for Local File Systems
local-fs.target loaded active active Local File Systems
multi-user.target loaded active active Multi-User System
network.target loaded active active Network
nss-user-lookup.target loaded active active User and Group Name Lookups
paths.target loaded active active Path Units
remote-fs.target loaded active active Remote File Systems
slices.target loaded active active Slice Units
sockets.target loaded active active Socket Units
sound.target loaded active active Sound Card
swap.target loaded active active Swaps
sysinit.target loaded active active System Initialization
timers.target loaded active active Timer Units
veritysetup.target loaded active active Local Verity Protected Volumes
man-db.timer loaded active waiting Daily man-db regeneration
shadow.timer loaded active waiting Daily verification of password and group files
systemd-tmpfiles-clean.timer loaded active waiting Daily Cleanup of Temporary Directories
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
135 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
lines 120-142/142 (END)Offline
#5 2021-12-07 12:45:17
- taiongh
- Member
- Registered: 2018-10-04
- Posts: 75
Re: [SOLVED]mate-power-manager，Can't work.
Alad wrote:
Don't run mate-power-manager as root.
Also complains：
[taizongh@ZhuFengGeShi ~]$ mate-power-manager
(mate-power-manager:1730): PowerManager-WARNING **: 20:43:26.447: Failed to get session for pid 1730: The name org.freedesktop.ConsoleKit was not provided by any .service files
(mate-power-manager:1730): PowerManager-WARNING **: 20:43:26.451: could not map keysym 1008ffa8 to keycode
(mate-power-manager:1730): PowerManager-ERROR **: 20:43:26.476: Power manager is already running in this session.
Trace and breakpoint traps (core dumped)Offline
#6 2021-12-07 13:21:24
- Scimmia
- Fellow
- Registered: 2012-09-01
- Posts: 13,729
Re: [SOLVED]mate-power-manager，Can't work.
Did you read the error?
Offline