void-linux / void-linux/void-packages

lxqt-powermanagement doesn't dim the screen when idle timer is supposed to run out

Open
#53,110 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug needs-testing
Dominant language
Shell
Stars
3.4k
Forks
2.8k
Avg merge
2d 5h
Merged PRs (30d)
299

Description

Is this a new report?

Yes

System Info

Linux gadell 6.11.7-300.fc41.x86_64 #1 SMP PREEMPT_DYNAMIC Fri Nov 8 19:23:10 UTC 2024 x86_64 GNU/Linux

Package(s) Affected

lxqt-powermanagement-2.0.0-1.fc41.x86_64

Does a report exist for this bug with the project's home (upstream) and/or another distro?

No response

Expected behaviour

After idle time, the system is expected to suspend.

Actual behaviour

After idle time (and also lot more), the system doesn't suspend ...

Starting from commandline:

$ lxqt-powermanagement
kf.idletime: Could not find any system poller plugin
qt.core.qobject.connect: QObject::connect(KAbstractIdleTimePoller, KIdleTime): invalid nullptr parameter
qt.core.qobject.connect: QObject::connect(KAbstractIdleTimePoller, KIdleTime): invalid nullptr parameter

Steps to reproduce
  1. stop the usual daemon (started by system) doing
    $ killall lxqt-powermanager

  2. Start the tool
    $ lxqt-powermanagement

  3. wait for idle-time (in my case: 1 minute), and see it doesn't suspend.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the report with lxqt-powermanager stopped, then launch lxqt-powermanagement and observe the reported KIdleTime poller errors after the idle interval. Trace the idle-time and suspend behavior from that entry point; done means the configured idle action occurs reliably without those errors.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux
Domain
desktop, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.