[Powerdevil] [Bug 480093] Screens don't stay turned off after 60 seconds on lock screen

2024-02-25 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=480093

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #8 from Bug Janitor Service  ---
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 480093] Screens don't stay turned off after 60 seconds on lock screen

2024-02-10 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=480093

--- Comment #7 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 480093] Screens don't stay turned off after 60 seconds on lock screen

2024-01-27 Thread Reboot
https://bugs.kde.org/show_bug.cgi?id=480093

--- Comment #6 from Reboot  ---
I haven't been able to reproduce this bug as consistently as before, even
though my hardware configuration hasn't changed... I did play around with my
display configuration for unrelated reasons though.

Here's a list of package upgrades I've installed since my bug report:

[2024-01-23T23:13:12+0100] [ALPM] upgraded aom (3.8.0-2 -> 3.8.1-1)
[2024-01-23T23:13:12+0100] [ALPM] upgraded zlib (1:1.3-2 -> 1:1.3.1-1)
[2024-01-23T23:13:13+0100] [ALPM] upgraded btrfs-progs (6.6.3-1 -> 6.7-1)
[2024-01-23T23:13:13+0100] [ALPM] upgraded ca-certificates-mozilla (3.96.1-1 ->
3.97-1)
[2024-01-23T23:13:13+0100] [ALPM] upgraded glib2 (2.78.3-1 -> 2.78.4-1)
[2024-01-23T23:13:13+0100] [ALPM] upgraded md4c (0.5.0-1 -> 0.5.1-1)
[2024-01-23T23:13:13+0100] [ALPM] upgraded libnghttp2 (1.58.0-1 -> 1.59.0-1)
[2024-01-23T23:13:13+0100] [ALPM] upgraded minizip (1:1.3-2 -> 1:1.3.1-1)
[2024-01-23T23:13:13+0100] [ALPM] upgraded nss (3.96.1-1 -> 3.97-1)
[2024-01-23T23:13:13+0100] [ALPM] upgraded chatterino2-git
(2.4.5.r206.g36931fa-1 -> 2.4.5.r213.g5628605-1)
[2024-01-23T23:13:14+0100] [ALPM] upgraded chromium (121.0.6167.71-1 ->
121.0.6167.85-1)
[2024-01-23T23:13:15+0100] [ALPM] upgraded clang (16.0.6-1 -> 16.0.6-2)
[2024-01-23T23:13:15+0100] [ALPM] upgraded ddcutil (2.1.0-2 -> 2.1.0-3)
[2024-01-23T23:13:15+0100] [ALPM] upgraded libplacebo (6.338.1-1 -> 6.338.2-1)
[2024-01-23T23:13:15+0100] [ALPM] upgraded discord_arch_electron (0.0.40-1 ->
0.0.41-1)
[2024-01-23T23:13:15+0100] [ALPM] upgraded docker-compose (2.24.1-1 ->
2.24.2-1)
[2024-01-23T23:13:15+0100] [ALPM] upgraded duckstation-git (r6808.bc04854e-1 ->
0.1.r6331.gbcf7f55-1)
[2024-01-23T23:13:16+0100] [ALPM] upgraded electron28 (28.1.4-1 -> 28.1.4-2)
[2024-01-23T23:13:16+0100] [ALPM] upgraded fakeroot (1.32.2-1 -> 1.33-1)
[2024-01-23T23:13:17+0100] [ALPM] upgraded gallery-dl (1.26.6-1 -> 1.26.7-1)
[2024-01-23T23:13:17+0100] [ALPM] upgraded gdb-common (13.2-1 -> 14.1-1)
[2024-01-23T23:13:17+0100] [ALPM] upgraded gdb (13.2-1 -> 14.1-1)
[2024-01-23T23:13:17+0100] [ALPM] upgraded glib2-docs (2.78.3-1 -> 2.78.4-1)
[2024-01-23T23:13:17+0100] [ALPM] upgraded imagemagick (7.1.1.26-2 ->
7.1.1.27-1)
[2024-01-23T23:13:17+0100] [ALPM] upgraded lib32-zlib (1.3-1 -> 1.3.1-1)
[2024-01-23T23:13:17+0100] [ALPM] upgraded lib32-glib2 (2.78.3-1 -> 2.78.4-1)
[2024-01-23T23:13:17+0100] [ALPM] upgraded lib32-nss (3.96.1-1 -> 3.97-1)
[2024-01-23T23:13:17+0100] [ALPM] upgraded libngtcp2 (1.1.0-1 -> 1.2.0-1)
[2024-01-23T23:13:17+0100] [ALPM] upgraded libolm (3.2.15-1 -> 3.2.16-1)
[2024-01-23T23:13:17+0100] [ALPM] upgraded libpaper (2.1.2-1 -> 2.1.3-1)
[2024-01-23T23:13:18+0100] [ALPM] upgraded linux (6.7.arch3-1 -> 6.7.1.arch1-1)
[2024-01-23T23:13:19+0100] [ALPM] upgraded linux-zen (6.7.zen3-1 ->
6.7.1.zen1-1)
[2024-01-23T23:13:22+0100] [ALPM] upgraded linux-zen-headers (6.7.zen3-1 ->
6.7.1.zen1-1)
[2024-01-23T23:13:22+0100] [ALPM] upgraded nodejs (21.6.0-2 -> 21.6.1-1)
[2024-01-23T23:13:22+0100] [ALPM] upgraded openimageio (2.5.6.0-1 -> 2.5.7.0-1)
[2024-01-23T23:13:22+0100] [ALPM] upgraded ostree (2023.8-1 -> 2024.1-1)
[2024-01-23T23:13:22+0100] [ALPM] upgraded python-jaraco.functools (3.9.0-1 ->
4.0.0-1)
[2024-01-23T23:13:22+0100] [ALPM] upgraded python-pyclip (0.7.0-3 -> 0.7.0-4)
[2024-01-23T23:13:22+0100] [ALPM] upgraded qpwgraph (0.6.1-1 -> 0.6.2-1)
[2024-01-23T23:13:22+0100] [ALPM] upgraded qqc2-desktop-style (5.248.0-1 ->
5.248.0-2)
[2024-01-23T23:13:22+0100] [ALPM] upgraded sdl2_mixer (2.6.3-2 -> 2.8.0-1)
[2024-01-23T23:13:22+0100] [ALPM] upgraded sdl2_ttf (2.20.2-2 -> 2.22.0-1)
[2024-01-23T23:13:22+0100] [ALPM] upgraded tenacity-git (1:r14960.g3c9532522-1
-> 1:r14961.gdf6704909-1)
[2024-01-23T23:13:22+0100] [ALPM] upgraded usd (23.11-6 -> 23.11-8)
[2024-01-23T23:13:22+0100] [ALPM] upgraded virtiofsd (1.9.0-2 -> 1.10.0-1)
[2024-01-23T23:13:22+0100] [ALPM] upgraded vlc (3.0.20-4 -> 3.0.20-5)
[2024-01-23T23:13:22+0100] [ALPM] upgraded xorg-xwayland (23.2.4-1 -> 23.2.4-

I'm not sure if any of those fixed it, I'll post an update if I can manage to
reproduce it again.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 480093] Screens don't stay turned off after 60 seconds on lock screen

2024-01-23 Thread Jakob Petsovits
https://bugs.kde.org/show_bug.cgi?id=480093

--- Comment #5 from Jakob Petsovits  ---
Seems similar to bug 480026, which btw (just an observation, not necessarily
meaningful) is also using a discrete AMD GPU.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 480093] Screens don't stay turned off after 60 seconds on lock screen

2024-01-23 Thread Jakob Petsovits
https://bugs.kde.org/show_bug.cgi?id=480093

--- Comment #4 from Jakob Petsovits  ---
The screens are supposed to come back on when "user activity" is detected.
Normally, this means the desktop receiving input events from devices like
touchpad, mouse or keyboard. Activity can also be simulated by an application.

Does this still happen if you unplug your mouse and keyboard?

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 480093] Screens don't stay turned off after 60 seconds on lock screen

2024-01-23 Thread Reboot
https://bugs.kde.org/show_bug.cgi?id=480093

--- Comment #3 from Reboot  ---
- I'm using Wayland.
- I've just done a bit of testing, and it seems to only happen when all of the
three screens are plugged in.
- Yes it does, with the same behavior as above: it happens only when the three
screens are plugged in.
- AMD Radeon RX 5700 XT
- The three screens I'm using, from left to right :
   - HP E190i, 1280x1024, using DisplayPort
   - LG Ultrafine, 3840x2160@150%, using HDMI
   - Philips 247E6, 1920x1080, using HDMI
The CPU doesn't have a graphics chipset, so all of these are plugged into the
GPU's ports.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 480093] Screens don't stay turned off after 60 seconds on lock screen

2024-01-23 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=480093

Nate Graham  changed:

   What|Removed |Added

  Component|common  |general
Product|KScreen |Powerdevil
 CC||jpe...@petsovits.com,
   ||m...@ratijas.tk,
   ||natalie_clar...@yahoo.de,
   ||n...@kde.org
   Assignee|kscreen-bugs-n...@kde.org   |plasma-b...@kde.org
 Resolution|--- |WAITINGFORINFO
 Status|REPORTED|NEEDSINFO

--- Comment #2 from Nate Graham  ---
Thanks for the bug report. A few questions?

- Are you using Wayland or X11?
- Does the issue reproduce with only a single screen?
- Does the issue happen if you turn the screens off manually using a global
keyboard shortcut assigned to the relevant action in System Settings > Keyboard
> Shortcuts?
- What kind of GPU hardware is the system using?
- Can you provide details about the screens that exhibit the issues and mention
how they're physically plugged in?

Thanks again!

-- 
You are receiving this mail because:
You are watching all bug changes.