[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [KScreen] [Bug 353637] Cannot enable second monitor in Display Configuration
From:       Maciej Mrozowski <reavertm () gmail ! com>
Date:       2015-10-09 12:32:12
Message-ID: bug-353637-17878-FQE20sLbsc () http ! bugs ! kde ! org/
[Download RAW message or body]

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

Maciej Mrozowski <reavertm@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |reavertm@gmail.com

--- Comment #1 from Maciej Mrozowski <reavertm@gmail.com> ---
I can confirm this and other weird behaviour of kscreen, with VGA output in my
case.
It seeems kscreen keeps some cached information of connected monitors, ignoring
(at least partially) what xrandr returns.

Procedure to reproduce in my case:
1. Login (new plasma/kscreen session started) with just single output connected
(for instance built-in laptop screen)
2. Plug-in some monitor A to VGA connector (in my case it was Sony TV in some
conference room).
3. This will usually work - new empty screen is assigned, plasmashell is aware
of screen, output is enabled.
In my case I had screens already defined (.local/share/kscreen) so this new VGA
output will display next screen. All fine so far.
4. Now, unplug monitor A and plug different monitor B, monitor with different
parameters, EDID, resolutions , etc.
Kscreen KCM will still show monitor A and its resolutions, completely ignoring
xrandr information. Like it cached some information and didn't think hot-plug
event should invalidate it.
In my case, in step 4, I'm plugging laptop to docking station with two monitors
- one via DVI (let's call it monitor C - HP in my case), one via VGA (monitor B
- in my case some Dell).

Then, when I want to manually enable monitor B via kscreen KCM, checkbox goes
'disabled' automatically, probably because selected moitor parameters
(resolution likely) is not supported by actually connected monitor B (since KCM
did not update that info).

I consider this a regression, I remember, a month or two ago, it was still
working well.

-- 
You are receiving this mail because:
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]