[KScreen] [Bug 354437] [regression/4] KScreen does not remember multiple monitor configuration

[Andrew Crouthamel]

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

Andrew Crouthamel  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #16 from Andrew Crouthamel  ---
Dear Bug Submitter,

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.

[KScreen] [Bug 354437] [regression/4] KScreen does not remember multiple monitor configuration

[Andrew Crouthamel]

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

Andrew Crouthamel  changed:

   What|Removed |Added

   Keywords||triaged

--- Comment #15 from Andrew Crouthamel  ---
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 set the bug
status 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.

[KScreen] [Bug 354437] [regression/4] KScreen does not remember multiple monitor configuration

[Sebastian Kügler via KDE Bugzilla]

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

Sebastian Kügler  changed:

   What|Removed |Added

 CC||se...@kde.org
 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |WAITINGFORINFO

--- Comment #14 from Sebastian Kügler  ---
@Thiago: This may well be fixed with Plasma 5.8, could you check that?

You're saying you only get a single configuration file, this may happen if the
EDID information of both monitors is the same (which shouldn't happen, but, you
know ... hardware vendors, especially Samsung...). The output of
kscreen-console would be interesting (for all monitors).

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

[KScreen] [Bug 354437] [regression/4] KScreen does not remember multiple monitor configuration

[Jason Tibbitts via KDE Bugzilla]

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

--- Comment #13 from Jason Tibbitts  ---
I just want to note that as of late I've had no issues at all with kscreen
restoring my monitor configuration.  I get perfect session restores every time.

I think things improved when Fedora moved to the 5.7 series (from 5.6.5 to
5.7.2).

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

[KScreen] [Bug 354437] [regression/4] KScreen does not remember multiple monitor configuration

[Roman Zimmermann via KDE Bugzilla]

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

Roman Zimmermann  changed:

   What|Removed |Added

 CC||toro...@gmail.com

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

[KScreen] [Bug 354437] [regression/4] KScreen does not remember multiple monitor configuration

[David Roberts via KDE Bugzilla]

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

David Roberts  changed:

   What|Removed |Added

 CC||robe...@tellink.net

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

[KScreen] [Bug 354437] [regression/4] KScreen does not remember multiple monitor configuration

[Jason Tibbitts via KDE Bugzilla]

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

Jason Tibbitts  changed:

   What|Removed |Added

 CC||ti...@math.uh.edu

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

[KScreen] [Bug 354437] [regression/4] KScreen does not remember multiple monitor configuration

[Thiago Macieira via KDE Bugzilla]

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

--- Comment #12 from Thiago Macieira  ---
Actually, I just noticed that I misdiagnosed the problem.

The problem is that kscreen5 keeps a single configuration file for both my 45"
Samsung TV and my 23" Samsung monitor. The kded4 module was able to tell the
difference.

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

[KScreen] [Bug 354437] [regression/4] KScreen does not remember multiple monitor configuration

[Thiago Macieira via KDE Bugzilla]

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

--- Comment #11 from Thiago Macieira  ---
Repeating: kscreen remembers the configuration but fails to apply it

[338791.653] kded5(1707 1707): kscreen: starting external backend launcher for
""
[338791.721] kded5(1707 1707): kscreen.kded:resetDisplaySwitch()
[338791.721] kded5(1707 1707): kscreen.kded:outputConnectedChanged():
"HDMI1"
[338791.721] kded5(1707 1707): kscreen.kded:Calculating config ID for
KScreen::Config(0x194cfc0)
[338791.721] kded5(1707 1707): kscreen.kded:Part of the Id: 
"8f1a4a6b5eec2d11cb59060b47b3610a"
[338791.721] kded5(1707 1707): kscreen.kded:Part of the Id: 
"181be8d8ae9f70f1d85e8defd31b0fe6"
[338791.721] kded5(1707 1707): kscreen.kded:Config ID:
"bfb8a9b9e97ddc88f50a9be628232c7e"
[338791.721] kded5(1707 1707): kscreen.kded:Change detected
[338791.732] kded5(1707 1707): kscreen.kded:Applying config
[338791.732] kded5(1707 1707): kscreen.kded:Calculating config ID for
KScreen::Config(0x194cfc0)
[338791.732] kded5(1707 1707): kscreen.kded:Part of the Id: 
"8f1a4a6b5eec2d11cb59060b47b3610a"
[338791.732] kded5(1707 1707): kscreen.kded:Part of the Id: 
"181be8d8ae9f70f1d85e8defd31b0fe6"
[338791.732] kded5(1707 1707): kscreen.kded:Config ID:
"bfb8a9b9e97ddc88f50a9be628232c7e"
[338791.732] kded5(1707 1707): kscreen.kded:Calculating config ID for
KScreen::Config(0x194cfc0)
[338791.732] kded5(1707 1707): kscreen.kded:Part of the Id: 
"8f1a4a6b5eec2d11cb59060b47b3610a"
[338791.732] kded5(1707 1707): kscreen.kded:Part of the Id: 
"181be8d8ae9f70f1d85e8defd31b0fe6"
[338791.732] kded5(1707 1707): kscreen.kded:Config ID:
"bfb8a9b9e97ddc88f50a9be628232c7e"
[338791.732] kded5(1707 1707): kscreen.kded:Applying known config
"bfb8a9b9e97ddc88f50a9be628232c7e"
[338791.732] kded5(1707 1707): kscreen.kded:Finding a mode for QSize(1920,
1080) @ 60.001
[338791.732] kded5(1707 1707): kscreen.kded:Found:  "72"  
QSize(1920, 1080) @ 60.001
[338791.733] kded5(1707 1707): kscreen.kded:Finding a mode for QSize(1920,
1080) @ 60
[338791.733] kded5(1707 1707): kscreen.kded:Found:  "384"  
QSize(1920, 1080) @ 60
[338791.733] kded5(1707 1707): kscreen.kded:doApplyConfig()
[338791.733] kded5(1707 1707): kscreen.kded:Monitor for changes:  false

It says it applied the config, but the screen configuration did not change.

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

[KScreen] [Bug 354437] [regression/4] KScreen does not remember multiple monitor configuration

[Maciej Mrozowski via KDE Bugzilla]

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

--- Comment #7 from Maciej Mrozowski  ---
Then KDE4 kscreen must have had some own randr polling mechanism, because
there, it detects my dock-station/monitor hot-plug events immediately. It's
just with KDE5 kscreen I have those output detection problems:
https://bugs.kde.org/show_bug.cgi?id=340120
https://bugs.kde.org/show_bug.cgi?id=356505
https://bugs.kde.org/show_bug.cgi?id=351025
https://bugs.kde.org/show_bug.cgi?id=346535

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

[KScreen] [Bug 354437] [regression/4] KScreen does not remember multiple monitor configuration

[Maciej Mrozowski via KDE Bugzilla]

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

--- Comment #8 from Maciej Mrozowski  ---
But that's of course not relevant in this bug. I can also confirm behaviour
reported here - not restoring latest monitor configuration.
(in previous comments just wanted say that imho root cause is with not working
autodetection, like in the case of bugs where user cannot change monitor
resolution occasionally because kscreen has outdated/mismatching EDID
information on monitor (like list of supported resolutions), I suspect this
might be the case with automatically trying to apply previous config as well)

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

[KScreen] [Bug 354437] [regression/4] KScreen does not remember multiple monitor configuration

[Maciej Mrozowski via KDE Bugzilla]

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

--- Comment #5 from Maciej Mrozowski  ---
Duplicate of  346961 likely.

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

[KScreen] [Bug 354437] [regression/4] KScreen does not remember multiple monitor configuration

[Maciej Mrozowski via KDE Bugzilla]

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

Maciej Mrozowski  changed:

   What|Removed |Added

 CC||reave...@gmail.com

--- Comment #4 from Maciej Mrozowski  ---
Remember multi-monitor config is minor problem here, detecting screens whenever
they change is more pressing. kscreen somewhat cannot catch up with output
device hot-plug events. I noticed runnig 'xrandr' tool (without arguments, just
in console) actally triggers kscreen to get notified about monitors being
reconnected (otherwise hot-plug events seem to be ignored in my case). I heard
someone blaming Qt for that..

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

[KScreen] [Bug 354437] [regression/4] KScreen does not remember multiple monitor configuration

[Thiago Macieira via KDE Bugzilla]

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

--- Comment #6 from Thiago Macieira  ---
(In reply to Maciej Mrozowski from comment #4)
> Remember multi-monitor config is minor problem here, detecting screens
> whenever they change is more pressing. kscreen somewhat cannot catch up with
> output device hot-plug events. I noticed runnig 'xrandr' tool (without
> arguments, just in console) actally triggers kscreen to get notified about
> monitors being reconnected (otherwise hot-plug events seem to be ignored in
> my case). I heard someone blaming Qt for that..

That used to happen with KDE 4 kscreen too and is not its fault. Running xrandr
without arguments causes the video driver (i915, usually) to re-scan the
outputs and thus find that you've connected something. It shouldn't be and
isn't needed. It's not kscreen's fault and it should not cause frequent
polling.

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

[KScreen] [Bug 354437] [regression/4] KScreen does not remember multiple monitor configuration

[Martin Kostolný via KDE Bugzilla]

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

--- Comment #2 from Martin Kostolný  ---
I think this is fixed for Plasma 5.5.1, KF 5.17.
@Thiago Macieira: can you confirm that?

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

[KScreen] [Bug 354437] [regression/4] KScreen does not remember multiple monitor configuration

[Thiago Macieira via KDE Bugzilla]

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

--- Comment #3 from Thiago Macieira  ---
(In reply to Martin Kostolný from comment #2)
> I think this is fixed for Plasma 5.5.1, KF 5.17.
> @Thiago Macieira: can you confirm that?

Will answer when 5.5.1 drops in OpenSUSE Tumbleweed (currently 5.4.3).

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