elogind and incessant entry into standby of FeedMe F9 pro

[bracecomputerlab]

I am not sure this is the right forum to discuss this matter.
I am having an issue with a rather unusual computer having a weird standby related issue.
The computer enters standby every 60 seconds, and I do not know how to prevent this other than installing Xfce4 Power Manager.
After trying to understand what is going on, it appears that this issue involved D-Bus and elogind.
First of all, is there a way to at least manually stop this other than installing Xfce4 Power Manager?
The computer I am having issue with is called FeedMe F9 pro laptop.
It is a Chinese domestic market computer with Zhaoxin KX-6640MA processor (a quad-core Centaur Technology derived design).
Note that I have another mini PC with a Zhaoxin KX-6540 processor, but this one does not exhibit the problem (ATOPNUC AZ60 mini desktop PC).
Only FeedMe F9 pro has this issue, so I do not think this issue to specific to a Zhaoxin processor.
This issue really started when I installed Network Manager.
Prior to installing Network Manager, I was not having this issue.
It appears that the installation of Network Manager automatically starts up dbus OpenRC service, and the activation of D-Bus causes the issue.
I will like to use Network Manager, so I need a fix or at least a workaround for this issue.
Both FeedMe F9 pro laptop and ATOPNUC AZ60 mini desktop PC have Intel 7265 WLAN for WiFi connectivity.
Both systems have Byosoft UEFI firmware.
The odd thing about this issue is that this issue starts to happen as soon as I log in.
If display-manager OpenRC service is not added to default group, I need to perform a text based log in.
The incessant entry into standby fires up as soon as I get a successful log in.
In other words, if I leave the computer waiting for a log in, the computer sits there happy, but as soon as I have a successful log in, I get the incessant standby entry.
At one point, it appeared that ModemManager is causing the issue, but since this occurs as soon as I have a successful log in, I started to suspect something with elogind.
What I want to know is, is this type of an issue fairly common with some laptops?
Has anybody heard of this issue?
How do I debug elogind issues?
_________________
Kevin Brace
Brace Computer Laboratory blog
https://bracecomputerlab.com

[guyuming]

If you think elogind does something wrong, you can change to seatd.

I am using openrc with seatd (https://wiki.gentoo.org/wiki/Seatd) because i prefer a minimalism config.

I use DWL as wayland compositor.

I need to set XDG_RUNTIME_DIR env variable since seatd won't set it and elogind will set it for you.

https://forums.gentoo.org/viewtopic-p-8790881-highlight-.html

I call the XDG_RUNTIME_DIR setting script in my dwl launching script:

https://gitee.com/guyuming76/dwl/blob/V0.5cn/xdg_run_user

https://gitee.com/guyuming76/dwl/blob/V0.5cn/dwl.sh


Usually, i don't start dbus. When i need to run some software which depends on dbus, i modify the dwl.sh temporarily.