[kde] [Bug 470466] New: Multi-monitor issue when more than one display is attached, the display configuration cycles between new display attached and display removed

bugzilla_noreply at kde.org bugzilla_noreply at kde.org
Tue May 30 21:37:03 BST 2023


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

            Bug ID: 470466
           Summary: Multi-monitor issue when more than one display is
                    attached, the display configuration cycles between new
                    display attached and display removed
    Classification: I don't know
           Product: kde
           Version: unspecified
          Platform: Ubuntu
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: unassigned-bugs at kde.org
          Reporter: gcrume at gmail.com
  Target Milestone: ---

Created attachment 159357
  --> https://bugs.kde.org/attachment.cgi?id=159357&action=edit
screen shot of Display configuration window

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. attach a second monitor to the GPU 
2. 
3. 

OBSERVED RESULT
in Display Configuration a notice continually cycles between:
A new output has been added. Settings have been reloaded.
An output has been removed. Settings have been reloaded.

The cycle time is approximately 10 seconds

EXPECTED RESULT
Display configuration would detect the new display and allow configuration

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION
Kernel Version: 6.2.0-20-generic (64-bit)
Graphics Platform: Wayland

Processor: 16 × AMD Ryzen 7 2700 Eight-Core Processor
Memory: 15.5 GiB of RAM
Graphics Processor: AMD Radeon RX 580 Series

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


More information about the Unassigned-bugs mailing list