https://bugs.kde.org/show_bug.cgi?id=391778
--- Comment #21 from Robert Cheramy ---
Thank you very much Martin for your help!
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=391778
--- Comment #20 from armin.no...@thincast.com ---
You're correct, setting fullscreen first and the monitors afterward is working
with kwin too.
(In reply to Martin Flöser from comment #19)
> > Hope this helps.
>
> Yes it does, now I understand the prob
https://bugs.kde.org/show_bug.cgi?id=391778
--- Comment #19 from Martin Flöser ---
> Hope this helps.
Yes it does, now I understand the problem.
FreeRDP first sends the _NET_WM_FULLSCREEN_MONITORS and afterwards the change
to fullscreen. Due to BUG #391960 this is not applied when FreeRDP switc
https://bugs.kde.org/show_bug.cgi?id=391778
--- Comment #18 from Robert Cheramy ---
Created attachment 111472
--> https://bugs.kde.org/attachment.cgi?id=111472&action=edit
Output of xev -root when Runing freerdp in Fullscreen mode with multiple
Monitors
Hope this helps.
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=391778
--- Comment #17 from Martin Flöser ---
Could someone please run:
xev -root
then start freerdp and bring it into the broken state and attach the output of
xev? This should show which events are sent from freerdp, maybe that helps to
see what's going on.
https://bugs.kde.org/show_bug.cgi?id=391778
--- Comment #16 from Martin Flöser ---
(In reply to Martin Flöser from comment #15)
> I found a bug explaining why the property is not set, but it would not
> explain why the window is not shown correctly
-> BUG #391960
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=391778
--- Comment #15 from Martin Flöser ---
I found a bug explaining why the property is not set, but it would not explain
why the window is not shown correctly
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=391778
--- Comment #14 from Martin Flöser ---
The combination of the xprop and the debug output would mean that KWin is not
getting the callback from our windowing system library. I checked on
build.kde.org and the code area is not test covered. I'll try to ad
https://bugs.kde.org/show_bug.cgi?id=391778
--- Comment #13 from Martin Flöser ---
Thanks for the debug output.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=391778
--- Comment #12 from Robert Cheramy ---
Created attachment 111453
--> https://bugs.kde.org/attachment.cgi?id=111453&action=edit
Output of kwin debug messages
Here is the Output of KWIN with Debug activated (I activated everything using
kdebugsettings
https://bugs.kde.org/show_bug.cgi?id=391778
--- Comment #11 from Martin Flöser ---
What I noticed is that the xprop output is lacking the fullscreen monitor
property.
This should create a debug message:
"fullscreenMonitors update failed. request higher than number of screens."
Could someone ple
https://bugs.kde.org/show_bug.cgi?id=391778
--- Comment #10 from Martin Flöser ---
(In reply to armin.novak from comment #8)
> I'd be more than happy to fix that in a more modern way, but the depths of
> X11 still have surprises whenever touched. (as I do that not really often)
I would create a
https://bugs.kde.org/show_bug.cgi?id=391778
--- Comment #9 from armin.no...@thincast.com ---
Created attachment 111393
--> https://bugs.kde.org/attachment.cgi?id=111393&action=edit
xprop, xwininfo, qdbus output and screenshot
Attached the desired information.
The screenshot shows that the windo
https://bugs.kde.org/show_bug.cgi?id=391778
--- Comment #8 from armin.no...@thincast.com ---
(In reply to Martin Flöser from comment #7)
> @armin: do you really use _NET_WM_FULLSCREEN_MONITORS? If yes, I would like
> to ask how you think that is supposed to work given that no X server uses
> xiner
https://bugs.kde.org/show_bug.cgi?id=391778
--- Comment #7 from Martin Flöser ---
@armin: do you really use _NET_WM_FULLSCREEN_MONITORS? If yes, I would like to
ask how you think that is supposed to work given that no X server uses xinerama
any more. It's till exposed, but in truth it's xrandr. I
https://bugs.kde.org/show_bug.cgi?id=391778
--- Comment #6 from Martin Flöser ---
I'm not going to test, sorry. I don't have the time to get this setup as I lack
the FreeRDP domain knowledge.
What I would be interested in, is:
* screenshot of the issue
* xprop and xwininfo of the window
* out
https://bugs.kde.org/show_bug.cgi?id=391778
armin.no...@thincast.com changed:
What|Removed |Added
CC||armin.no...@thincast.com
--- Comment
https://bugs.kde.org/show_bug.cgi?id=391778
--- Comment #4 from Robert Cheramy ---
Thank you for taking your time to evaluate the Bug.
I've tried to look into the source code of FreeRDP, but I have no idea of X11
Programming an gave up in the end. I'll have to wait until FreeRDP Developers
fix t
https://bugs.kde.org/show_bug.cgi?id=391778
Martin Flöser changed:
What|Removed |Added
See Also||https://github.com/FreeRDP/
|
https://bugs.kde.org/show_bug.cgi?id=391778
--- Comment #3 from Martin Flöser ---
Furthermore I want to add that relying on the _NET_WM_FULLSCREEN_MONITORS is
quite questionable. To quote the spec: "The indices are from the set returned
by the Xinerama extension."
Now there is just no xinerama e
https://bugs.kde.org/show_bug.cgi?id=391778
Martin Flöser changed:
What|Removed |Added
Resolution|--- |INVALID
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=391778
Martin Flöser changed:
What|Removed |Added
Component|multihead |xrandr
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=391778
jat...@gmail.com changed:
What|Removed |Added
CC||jat...@gmail.com
--- Comment #1 from jat...@g
23 matches
Mail list logo
