Bug 479384 - External screen turning off when closing the laptop lid despite configured to stay enabled
Summary: External screen turning off when closing the laptop lid despite configured to...
Status: RESOLVED DUPLICATE of bug 488005
Alias: None
Product: Powerdevil
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: 6.0.2
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords: qt6
Depends on:
Blocks:
 
Reported: 2024-01-04 09:06 UTC by Dennis
Modified: 2024-09-30 21:28 UTC (History)
7 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Relevant energy saving settings (25.62 KB, image/png)
2024-03-19 18:35 UTC, Louis Moureaux
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Dennis 2024-01-04 09:06:32 UTC
SUMMARY
***
I have a TB16 dock with an external monitor. I have my energy settings set to do nothing when closing the lid while on AC power. I could close the lid and keep on working. It looks like this behaviour does not work correctly anymore
***


STEPS TO REPRODUCE
1. have neon unstable updated, clean start OS with dock attached and lid open.
2.  connect TB16 dock to my XPS13 with external monitor
3. login to session
4. both displays are enabled (or just external monitor), close lid.
5. system goes to sleep mode (this used to be the previous setting.

OBSERVED RESULT
closing lid lets system sleep while energy settings are set to do nothing. 

EXPECTED RESULT
Closing the lid should not do anything as I have configured the energy settings to do nothing. 

Software versions:
Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.91.90
KDE Frameworks Version: 5.248.0
Qt Version: 6.6.1
Kernel Version: 6.2.0-39-generic (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz
Memory: 15,3 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Manufacturer: Dell Inc.
Product Name: XPS 13 9380

ADDITIONAL INFORMATION
Interesting, this used to work. I don't know with what previous version, I presume about a month ago or so. It also results in a crash of plasmashell. I can't attach drkonqi reports due to bugs:
https://bugs.kde.org/show_bug.cgi?id=478885
https://bugs.kde.org/show_bug.cgi?id=478883
Comment 1 Louis Moureaux 2024-03-19 18:29:55 UTC
I can confirm on a DELL Latitude 7410 with a monitor connected via DisplayPort over USB-C, resembling the configuration of the original poster.
I think this is more likely a Powerdevil bug than a Neon bug so I'm switching the Product category accordingly.

Operating System: KDE neon 6.0
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.5.0-25-generic (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i5-10310U CPU @ 1.70GHz
Memory: 15.3 Gio of RAM
Graphics Processor: Mesa Intel® UHD Graphics
Manufacturer: Dell Inc.
Product Name: Latitude 7410

$ kscreen-doctor -i
Environment: 
  * KSCREEN_BACKEND           : [not set]
  * KSCREEN_BACKEND_INPROCESS : [not set]
  * KSCREEN_LOGGING           : [not set]
Logging to                : [logging disabled]
Preferred KScreen backend : KSC_KWayland.so
Available KScreen backends:
  * KSC_Fake.so: /usr/lib/x86_64-linux-gnu/qt6/plugins/kf6/kscreen/KSC_Fake.so
  * KSC_KWayland.so: /usr/lib/x86_64-linux-gnu/qt6/plugins/kf6/kscreen/KSC_KWayland.so
  * KSC_QScreen.so: /usr/lib/x86_64-linux-gnu/qt6/plugins/kf6/kscreen/KSC_QScreen.so
  * KSC_XRandR.so: /usr/lib/x86_64-linux-gnu/qt6/plugins/kf6/kscreen/KSC_XRandR.so

$ kscreen-doctor -o
Output: 1 eDP-1
        enabled
        connected
        priority 2
        Panel
        Modes:  0:1920x1080@60*!  1:1920x1080@48  2:1280x1024@60  3:1024x768@60  4:1280x800@60  5:1920x1080@60  6:1600x900@60  7:1368x768@60  8:1280x720@60 
        Geometry: 0,1440 1920x1080
        Scale: 1
        Rotation: 1
        Overscan: 0
        Vrr: incapable
        RgbRange: Automatic
        HDR: incapable
        Wide Color Gamut: incapable
        ICC profile: none
Output: 2 DP-3
        enabled
        connected
        priority 1
        DisplayPort
        Modes:  0:2560x1440@75!  1:2560x1440@60*  2:1920x1080@60  3:1920x1080@60  4:1920x1080@60  5:1920x1080@50  6:1680x1050@60  7:1600x900@60  8:1280x1024@75  9:1280x1024@60  10:1440x900@60  11:1280x800@60  12:1152x864@75  13:1280x720@60  14:1280x720@60  15:1280x720@60  16:1280x720@50  17:1024x768@75  18:1024x768@70  19:1024x768@60  20:832x624@75  21:800x600@75  22:800x600@72  23:800x600@60  24:800x600@56  25:720x576@50  26:720x480@60  27:720x480@60  28:640x480@75  29:640x480@73  30:640x480@67  31:640x480@60  32:640x480@60  33:720x400@70 
        Geometry: 0,0 2560x1440
        Scale: 1
        Rotation: 1
        Overscan: 0
        Vrr: incapable
        RgbRange: Automatic
        HDR: incapable
        Wide Color Gamut: incapable
        ICC profile: none
Comment 2 Louis Moureaux 2024-03-19 18:35:09 UTC
Created attachment 167480 [details]
Relevant energy saving settings

Adding a screenshot of the relevant energy saving settings
Comment 3 Dennis 2024-09-11 07:07:13 UTC
Not happening anymore on a new install, same TB16 dock:

Operating System: KDE neon 6.0
KDE Plasma Version: 6.1.4
KDE Frameworks Version: 6.5.0
Qt Version: 6.7.2
Kernel Version: 6.8.0-40-generic (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-6700HQ CPU @ 2.60GHz
Memory: 15,4 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 530
Manufacturer: Dell Inc.
Product Name: XPS 15 9550

@louis, can you confirm?
Comment 4 Louis Moureaux 2024-09-12 16:18:22 UTC
No longer happening for me either, with:
Operating System: KDE neon 6.0
KDE Plasma Version: 6.1.5
KDE Frameworks Version: 6.5.0
Qt Version: 6.7.2

--> closing
Comment 5 Alberto Salvia Novella 2024-09-30 20:17:39 UTC
Still happening for me with more modern versions of everything:
https://bugs.kde.org/show_bug.cgi?id=493888
Comment 6 Natalie Clarius 2024-09-30 21:25:48 UTC
*** Bug 493888 has been marked as a duplicate of this bug. ***
Comment 7 Natalie Clarius 2024-09-30 21:26:52 UTC

*** This bug has been marked as a duplicate of bug 488005 ***