[KScreen] [Bug 368910] Monitor change not detected on docking

[linuxfluesterer via KDE Bugzilla]

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

--- Comment #13 from linuxfluesterer  ---
@Sebastian As I said, I'm using Sabayon binary distro, based on Gentoo. The
Plasma environment is not upgraded to version 5.8 yet. But I assume due to the
intention to ship 'stable' versions of packages, it will take some time. And,
thank you for your positive) post, I look hopefully forward to upgrading my
system then.

-Linuxfluesterer

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

[KScreen] [Bug 368910] Monitor change not detected on docking

[Sebastian Kügler via KDE Bugzilla]

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

--- Comment #12 from Sebastian Kügler  ---
@Matthias no harm done, thanks for digging into the problem. I'm glad you found
the issue. :)

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

[KScreen] [Bug 368910] Monitor change not detected on docking

[Sebastian Kügler via KDE Bugzilla]

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

--- Comment #11 from Sebastian Kügler  ---
@-Linuxfluesterer Like Matthias said, your bug is an unrelated problem,
fortunately, one which we have fixed already. Your Plasma version is a bit
outdated, so it doesn't contain the fix yet. It would be great if you could try
Plasma 5.8 Beta to verify your problem is fixed.

Thanks for the feedback, though. :)

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

[KScreen] [Bug 368910] Monitor change not detected on docking

[linuxfluesterer via KDE Bugzilla]

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

--- Comment #10 from linuxfluesterer  ---
(In reply to Matthias Blaicher from comment #7)
> Hi linuxfluesterer,
> 
> I am sorry, but this is a totally unrelated bug, as you acknowledge: 
> 
> Neither is it docking related, nor does it have problems enabling your
> monitor (looks like a plasmashell crashes to me). Furthermore, you do not
> execute "xrandr", nor do you run Plasma 5.8 beta, which this bug report is
> explicitly about and which carries multiple multi-screen bugfixes.
> 
> If you feel like your bug has not been reported yet, feel free to open a new
> one specific to your issues, or wait for 5.8 Plasma to be released and check
> if the bug remains.
> 
> Very Best,
> Matthias

Ok, Matthias.
To be honest, I was not sure about, but for me it sounded similar a bit.
I will open a new bug report now. Thank you.

Regards.

-Linuxfluesterer

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

[KScreen] [Bug 368910] Monitor change not detected on docking

[Matthias Blaicher via KDE Bugzilla]

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

Matthias Blaicher  changed:

   What|Removed |Added

 Resolution|--- |INVALID
 Status|CONFIRMED   |RESOLVED

--- Comment #9 from Matthias Blaicher  ---
Hi Sebastian,

it turns out, this issue was caused by a broken DVI cable... I guess it somehow
impacted monitor hot-plug detection, but xrandr had an extra look on the I2C
when called, and hence it was detected.

Sorry for the noise!

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

[KScreen] [Bug 368910] Monitor change not detected on docking

[Matthias Blaicher via KDE Bugzilla]

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

--- Comment #8 from Matthias Blaicher  ---
(In reply to Sebastian Kügler from comment #4)
> For kicks, could you check if this works in GNOME or Unity (maybe they've
> found such a workaround)?

I just checked - GNOME also does not work So I guess this bug is in the
wrong tracker... Any option on how to proceed from here?

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

[KScreen] [Bug 368910] Monitor change not detected on docking

[Matthias Blaicher via KDE Bugzilla]

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

--- Comment #7 from Matthias Blaicher  ---
Hi linuxfluesterer,

I am sorry, but this is a totally unrelated bug, as you acknowledge: 

Neither is it docking related, nor does it have problems enabling your monitor
(looks like a plasmashell crashes to me). Furthermore, you do not execute
"xrandr", nor do you run Plasma 5.8 beta, which this bug report is explicitly
about and which carries multiple multi-screen bugfixes.

If you feel like your bug has not been reported yet, feel free to open a new
one specific to your issues, or wait for 5.8 Plasma to be released and check if
the bug remains.

Very Best,
Matthias

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

[KScreen] [Bug 368910] Monitor change not detected on docking

[linuxfluesterer via KDE Bugzilla]

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

--- Comment #6 from linuxfluesterer  ---
I can confirm inability with correct recognising a direct connected monitor to
my laptop, no matter on vga or HDMI. I can connect such a monitor, but after
connecting I still can move the mouse pointer, but I can not execute anything
with the mouse. It is not possible to open any menue, nor I receive a taskbar
or else. 
When I was in menue settings for 'monitor' I could see the monitor is already
recognised and displayed in the menue window. Anyway, I can not activate any
menue, any program. However, when I disconnect the monitor, everthing with the
build in laptop screen works fine and I can activate mouse click again.
I'm using Plasma 5.7.4 with Kernel 4.7 (Sabayon Plasma distro). I don't use
XRANDR or else...

-Linuxfluesterer

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

[KScreen] [Bug 368910] Monitor change not detected on docking

[linuxfluesterer via KDE Bugzilla]

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

linuxfluesterer  changed:

   What|Removed |Added

 CC||linuxflueste...@gmx.net

--- Comment #5 from linuxfluesterer  ---
I can confirm inability with correct recognising a direct connected monitor to
my laptop, no matter on vga or HDMI. I can connect such a monitor, but after
connecting I still can move the mouse pointer, but I can not execute anything
with the mouse. It is not possible to open any menue, nor I receive a taskbar
or else. 
When I was in menue settings for 'monitor' I could see the monitor is already
recognised and displayed in the menue window. Anyway, I can not activate any
menue, any program. However, when I disconnect the monitor, everthing with the
build in laptop screen works fine and I can activate mouse click again.
I'm using Plasma 5.4.7 with Kernel 4.7 (Sabayon Plasma distro). I don't use
XRANDR or else...

-Linuxfluesterer

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

[KScreen] [Bug 368910] Monitor change not detected on docking

[Sebastian Kügler via KDE Bugzilla]

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

--- Comment #4 from Sebastian Kügler  ---
Yeah, it seems to be down to a problem somewhere in the stack. I'm testing
docking station (with a Lenovo X1 Yoga and a OneLine+) almost daily, and that
works flawlessly now -- but there, we do actually get change events which we
can react to. In your setup (hardware / software combo) that doesn't seem to be
the case, so we can't really do anything (even if we know what we'd like to
do).

As I said, I'm mulling over a workaround, but it doesn't look too good right
now.

For kicks, could you check if this works in GNOME or Unity (maybe they've found
such a workaround)?

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

[KScreen] [Bug 368910] Monitor change not detected on docking

[Matthias Blaicher via KDE Bugzilla]

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

--- Comment #3 from Matthias Blaicher  ---
Hi Sebastian,
thank you for your work and looking into it. As this used to work for KDE4, I
suppose it is not an hardware issue, but the whole software stack and kernel
changed since then...

Regarding xrandr, this is an up-to-date Arch Linux with testing enabled, so it
is the libxrandr 1.5.0-1 package atm.

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

[KScreen] [Bug 368910] Monitor change not detected on docking

[Sebastian Kügler via KDE Bugzilla]

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

Sebastian Kügler  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #2 from Sebastian Kügler  ---
Thanks for the report, Matthias. The and information you provide (especially
the annotation) is very useful. Unfortunately, I don't see how we can fix this
issue, as we don't get any useful event which allows us to update the config.
(The QXcbConnection BadWindow error you mention is not that useful,
unfortunately.)

I'll look further into this issue and will get back to you.

Which version of xrandr are you using, by the way?

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

[KScreen] [Bug 368910] Monitor change not detected on docking

[Sebastian Kügler via KDE Bugzilla]

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

Sebastian Kügler  changed:

   What|Removed |Added

   Keywords||multiscreen

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

[KScreen] [Bug 368910] Monitor change not detected on docking

[Matthias Blaicher via KDE Bugzilla]

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

--- Comment #1 from Matthias Blaicher  ---
Created attachment 101128
  --> https://bugs.kde.org/attachment.cgi?id=101128=edit
Annotated kscreen log

Annotated kscreen log with relevant input from journald of the folliowing
sequence:

1. Boot into KDE undocked
2. Dock laptop
3. Execute xrandr
4. Close lid

While there is nothing happening in the kscreen logs, there is one entry after
docking (point 2) I'd like to point out:

Sep 16 20:51:32 meinpc kwin_x11[6183]: QXcbConnection: XCB error: 3
(BadWindow), sequence: 10182, resource id: 94371848, major code: 18
(ChangeProperty), minor code: 0
Sep 16 20:51:32 meinpc kdeinit5[6147]: QObject::connect: invalid null parameter
Sep 16 20:51:32 meinpc kdeinit5[6147]: QObject::connect: invalid null parameter
Sep 16 20:51:32 meinpc kdeinit5[6147]: QObject::connect: invalid null parameter
Sep 16 20:51:32 meinpc kcminit[6975]: Initializing  "kcm_input" : 
"kcminit_mouse"
Sep 16 20:51:32 meinpc kwin_x11[6183]: QXcbConnection: XCB error: 3
(BadWindow), sequence: 10561, resource id: 92274696, major code: 18
(ChangeProperty), minor code: 0 

Could it be, the ChangeProperty is the event we need, but it is dropped
somehow?

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