[kde] [Bug 495491] New: Screen goes black after powersave. Cannot be reactivated. Reboot required

bugzilla_noreply at kde.org bugzilla_noreply at kde.org
Mon Oct 28 16:35:45 GMT 2024


https://bugs.kde.org/show_bug.cgi?id=495491

            Bug ID: 495491
           Summary: Screen goes black after powersave.  Cannot be
                    reactivated.  Reboot required
    Classification: I don't know
           Product: kde
           Version: unspecified
          Platform: Ubuntu
                OS: Linux
            Status: REPORTED
          Keywords: usability
          Severity: major
          Priority: NOR
         Component: general
          Assignee: unassigned-bugs at kde.org
          Reporter: r0002 at nxlplyx.com
                CC: r0002 at nxlplyx.com
  Target Milestone: ---

SUMMARY
After locking the screen and comming back a half hour later, the screen is
black.  A hard reboot is required.

STEPS TO REPRODUCE
1.   Lock the screen.
2.   Come back an hour later.
3.   The screen is black.  

OBSERVED RESULT
After locking the screen and comming back after an hour, the screen stays black
regardless of the keys pressed or mouse movement.

EXPECTED RESULT
Screen should awaken to the screenlock screen when a button is pressed or the
mouse is moved.

SOFTWARE/OS VERSIONS
Operating System: Ubuntu 22.04
KDE Plasma Version: 5.24.7
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3
Kernel Version: 6.8.0-47-generic (64-bit)
Graphics Platform: X11
Processors: 32 × Intel® Xeon® w5-3435X
Memory: 125.4 GiB of RAM
Graphics Processor:    2x NVIDIA GeForce RTX 3090 Ti/PCIe/SSE2.   Display port
is in the second card.

ADDITIONAL INFORMATION
It used to work without problems.  After a few updates the problem always
occurs.

The computer boots right into 22.04, shows the lockscreen - it is set for
Plasma(X11).  It shows the splash screen, and then goes into the desktop
without problem.

I have purged the nvidia drivers and reinstalled them to no avail. 
(535-server)

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the Unassigned-bugs mailing list