I'm seeing a lot of these messages with a kdrive user:
Sep 21 05:55:40 kded5[10869]: kscreen.kded: Failed to find a matching mode - this means that our config is corruptedor a different device with the same serial number has been connected (very unlikely).Falling back to preferred modes. Sep 21 05:55:40 kded5[10869]: colord: Unable to get EDID for output "X2GoKDriv e-0" Sep 21 05:55:40 kded5[10869]: colord: Failed to register device: "device id 'x randr-X2GoKDrive-0' already exists" Sep 21 05:55:40 kded5[10869]: colord: Failed to create ICC profile on cmsCreat eRGBProfile
Repeats every few seconds it seems.
Should kdrive be simulating EDID or some other output/information to help kscreen and colord?
-- Orion Poplawski IT Systems Manager 720-772-5637 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane orion@nwra.com Boulder, CO 80301 https://www.nwra.com/
On 9/25/23 09:17, Orion Poplawski wrote:
I'm seeing a lot of these messages with a kdrive user:
Sep 21 05:55:40 kded5[10869]: kscreen.kded: Failed to find a matching mode - this means that our config is corruptedor a different device with the same serial number has been connected (very unlikely).Falling back to preferred modes. Sep 21 05:55:40 kded5[10869]: colord: Unable to get EDID for output "X2GoKDriv e-0" Sep 21 05:55:40 kded5[10869]: colord: Failed to register device: "device id 'x randr-X2GoKDrive-0' already exists" Sep 21 05:55:40 kded5[10869]: colord: Failed to create ICC profile on cmsCreat eRGBProfile
Repeats every few seconds it seems.
Should kdrive be simulating EDID or some other output/information to help kscreen and colord?
We're seeing this lead to a segfault in kscreen and possibly behavior where the x2go window resizes uncontrollably.
-- Orion Poplawski IT Systems Manager 720-772-5637 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane orion@nwra.com Boulder, CO 80301 https://www.nwra.com/
Hello Orion
There's an entry in the FAQ about kscreen issues.
Regards, Rui Ferreira [user]
Às 18:42 de 25/09/23, Orion Poplawski escreveu:
On 9/25/23 09:17, Orion Poplawski wrote:
I'm seeing a lot of these messages with a kdrive user:
Sep 21 05:55:40 kded5[10869]: kscreen.kded: Failed to find a matching mode - this means that our config is corruptedor a different device with the same serial number has been connected (very unlikely).Falling back to preferred modes. Sep 21 05:55:40 kded5[10869]: colord: Unable to get EDID for output "X2GoKDriv e-0" Sep 21 05:55:40 kded5[10869]: colord: Failed to register device: "device id 'x randr-X2GoKDrive-0' already exists" Sep 21 05:55:40 kded5[10869]: colord: Failed to create ICC profile on cmsCreat eRGBProfile
Repeats every few seconds it seems.
Should kdrive be simulating EDID or some other output/information to help kscreen and colord?
We're seeing this lead to a segfault in kscreen and possibly behavior where the x2go window resizes uncontrollably.
x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
On 9/27/23 05:24, Rui Ferreira wrote:
Hello Orion
There's an entry in the FAQ about kscreen issues.
Regards, Rui Ferreira [user]
Thanks for the note about kscreen, I had forgotten about that. I've removed kscreen from the servers so hopefully that will help.
I'm still getting the colord messages around session resume it seems:
Sep 27 15:31:49 /usr/bin/x2goserver-run-extensions[1213572]: x2goserver-run-extensions called with options: USER-52-1695382629_stKKDE_dp24 post-resume Sep 27 15:31:53 kded5[1084517]: colord: Unable to get EDID for output "X2GoKDrive-0" Sep 27 15:31:53 kded5[1084517]: colord: Failed to register device: "device id 'xrandr-X2GoKDrive-0' already exists" Sep 27 15:31:53 kded5[1084517]: colord: Failed to create ICC profile on cmsCreateRGBProfile Sep 27 15:31:54 kwin_x11[1084520]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 65191, resource id: 20477363, major code: 3 (GetWindowAttributes), minor code: 0 Sep 27 15:31:54 kwin_x11[1084520]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 65192, resource id: 20477363, major code: 14 (GetGeometry), minor code: 0 Sep 27 15:31:54 kwin_x11[1084520]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 65195, resource id: 20477364, major code: 3 (GetWindowAttributes), minor code: 0 Sep 27 15:31:54 kwin_x11[1084520]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 65196, resource id: 20477364, major code: 14 (GetGeometry), minor code: 0 Sep 27 15:31:54 kded5[1084517]: colord: Unable to get EDID for output "X2GoKDrive-0" Sep 27 15:31:54 kded5[1084517]: colord: Failed to register device: "device id 'xrandr-X2GoKDrive-0' already exists" Sep 27 15:31:54 kded5[1084517]: colord: Failed to create ICC profile on cmsCreateRGBProfile Sep 27 15:31:54 kded5[1084517]: colord: Unable to get EDID for output "X2GoKDrive-0" Sep 27 15:31:54 kded5[1084517]: colord: Failed to register device: "device id 'xrandr-X2GoKDrive-0' already exists" Sep 27 15:31:54 kded5[1084517]: colord: Failed to create ICC profile on cmsCreateRGBProfile
Às 18:42 de 25/09/23, Orion Poplawski escreveu:
On 9/25/23 09:17, Orion Poplawski wrote:
I'm seeing a lot of these messages with a kdrive user:
Sep 21 05:55:40 kded5[10869]: kscreen.kded: Failed to find a matching mode - this means that our config is corruptedor a different device with the same serial number has been connected (very unlikely).Falling back to preferred modes. Sep 21 05:55:40 kded5[10869]: colord: Unable to get EDID for output "X2GoKDriv e-0" Sep 21 05:55:40 kded5[10869]: colord: Failed to register device: "device id 'x randr-X2GoKDrive-0' already exists" Sep 21 05:55:40 kded5[10869]: colord: Failed to create ICC profile on cmsCreat eRGBProfile
Repeats every few seconds it seems.
Should kdrive be simulating EDID or some other output/information to help kscreen and colord?
We're seeing this lead to a segfault in kscreen and possibly behavior where the x2go window resizes uncontrollably.
x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
-- Orion Poplawski he/him/his - surely the least important thing about me IT Systems Manager 720-772-5637 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane orion@nwra.com Boulder, CO 80301 https://www.nwra.com/
On 9/27/23 05:24, Rui Ferreira wrote:
Hello Orion
There's an entry in the FAQ about kscreen issues.
Regards, Rui Ferreira [user]
Às 18:42 de 25/09/23, Orion Poplawski escreveu:
On 9/25/23 09:17, Orion Poplawski wrote:
I'm seeing a lot of these messages with a kdrive user:
Sep 21 05:55:40 kded5[10869]: kscreen.kded: Failed to find a matching mode - this means that our config is corruptedor a different device with the same serial number has been connected (very unlikely).Falling back to preferred modes. Sep 21 05:55:40 kded5[10869]: colord: Unable to get EDID for output "X2GoKDriv e-0" Sep 21 05:55:40 kded5[10869]: colord: Failed to register device: "device id 'x randr-X2GoKDrive-0' already exists" Sep 21 05:55:40 kded5[10869]: colord: Failed to create ICC profile on cmsCreat eRGBProfile
Repeats every few seconds it seems.
Should kdrive be simulating EDID or some other output/information to help kscreen and colord?
We're seeing this lead to a segfault in kscreen and possibly behavior where the x2go window resizes uncontrollably.
Even after removing kscreen, one user is still having issues:
The effect seems to be a bit cumulative. First time or two after restarting x2go, no resizing. Then like a 1- or 2-'round' of resizing and it'll stop. Then after another few times it's up to 5 or 6... Then at some point you get to where it just won't stop. But restarting x2go (loosing your session) does get it to stop. Or, start the cycle I describe above over again.
Is there some extra logging that might be useful to log screen resize requests?
-- Orion Poplawski IT Systems Manager 720-772-5637 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane orion@nwra.com Boulder, CO 80301 https://www.nwra.com/
If the client side is Windows: Might have to do with the way Windows adds window decorations. We had an issue like that some years ago where vcxsrv did it wrong. Since kdrive does not use an intermediate X server it needs to handle these problems itself. Maybe try to run the client in Windows 7 compatibility mode. Or change display zoom.
Uli
On Mon, Oct 2, 2023 at 7:43 PM Orion Poplawski <orion@nwra.com> wrote:
On 9/27/23 05:24, Rui Ferreira wrote:
Hello Orion
There's an entry in the FAQ about kscreen issues.
Regards, Rui Ferreira [user]
Às 18:42 de 25/09/23, Orion Poplawski escreveu:
On 9/25/23 09:17, Orion Poplawski wrote:
I'm seeing a lot of these messages with a kdrive user:
Sep 21 05:55:40 kded5[10869]: kscreen.kded: Failed to find a matching mode - this means that our config is corruptedor a different device with the same serial number has been connected (very unlikely).Falling back to preferred modes. Sep 21 05:55:40 kded5[10869]: colord: Unable to get EDID for output "X2GoKDriv e-0" Sep 21 05:55:40 kded5[10869]: colord: Failed to register device: "device id 'x randr-X2GoKDrive-0' already exists" Sep 21 05:55:40 kded5[10869]: colord: Failed to create ICC profile on cmsCreat eRGBProfile
Repeats every few seconds it seems.
Should kdrive be simulating EDID or some other output/information to help kscreen and colord?
We're seeing this lead to a segfault in kscreen and possibly behavior where the x2go window resizes uncontrollably.
Even after removing kscreen, one user is still having issues:
The effect seems to be a bit cumulative. First time or two after restarting x2go, no resizing. Then like a 1- or 2-'round' of resizing and it'll stop. Then after another few times it's up to 5 or 6... Then at some point you get to where it just won't stop. But restarting x2go (loosing your session) does get it to stop. Or, start the cycle I describe above over again.
Is there some extra logging that might be useful to log screen resize requests?
-- Orion Poplawski IT Systems Manager 720-772-5637 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane orion@nwra.com Boulder, CO 80301 https://www.nwra.com/
x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
On 10/2/23 12:57, Ulrich Sibiller wrote:
If the client side is Windows: Might have to do with the way Windows adds window decorations. We had an issue like that some years ago where vcxsrv did it wrong. Since kdrive does not use an intermediate X server it needs to handle these problems itself. Maybe try to run the client in Windows 7 compatibility mode. Or change display zoom.
Uli
Ah, sorry did not specify the client. The client is also AlmaLinux 8.
On Mon, Oct 2, 2023 at 7:43 PM Orion Poplawski <orion@nwra.com> wrote:
On 9/27/23 05:24, Rui Ferreira wrote:
Hello Orion
There's an entry in the FAQ about kscreen issues.
Regards, Rui Ferreira [user]
Às 18:42 de 25/09/23, Orion Poplawski escreveu:
On 9/25/23 09:17, Orion Poplawski wrote:
I'm seeing a lot of these messages with a kdrive user:
Sep 21 05:55:40 kded5[10869]: kscreen.kded: Failed to find a matching mode - this means that our config is corruptedor a different device with the same serial number has been connected (very unlikely).Falling back to preferred modes. Sep 21 05:55:40 kded5[10869]: colord: Unable to get EDID for output "X2GoKDriv e-0" Sep 21 05:55:40 kded5[10869]: colord: Failed to register device: "device id 'x randr-X2GoKDrive-0' already exists" Sep 21 05:55:40 kded5[10869]: colord: Failed to create ICC profile on cmsCreat eRGBProfile
Repeats every few seconds it seems.
Should kdrive be simulating EDID or some other output/information to help kscreen and colord?
We're seeing this lead to a segfault in kscreen and possibly behavior where the x2go window resizes uncontrollably.
Even after removing kscreen, one user is still having issues:
The effect seems to be a bit cumulative. First time or two after restarting x2go, no resizing. Then like a 1- or 2-'round' of resizing and it'll stop. Then after another few times it's up to 5 or 6... Then at some point you get to where it just won't stop. But restarting x2go (loosing your session) does get it to stop. Or, start the cycle I describe above over again.
Is there some extra logging that might be useful to log screen resize requests?
-- Orion Poplawski IT Systems Manager 720-772-5637 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane orion@nwra.com Boulder, CO 80301 https://www.nwra.com/
x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
-- Orion Poplawski IT Systems Manager 720-772-5637 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane orion@nwra.com Boulder, CO 80301 https://www.nwra.com/
Às 18:42 de 02/10/23, Orion Poplawski escreveu:
Even after removing kscreen, one user is still having issues:
The effect seems to be a bit cumulative. First time or two after restarting x2go, no resizing. Then like a 1- or 2-'round' of resizing and it'll stop. Then after another few times it's up to 5 or 6... Then at some point you get to where it just won't stop. But restarting x2go (loosing your session) does get it to stop. Or, start the cycle I describe above over again.
Is there some extra logging that might be useful to log screen resize requests?
Hi Orion.
I don't know. I'm just a user. I'm not even using kdrive. I'm using regular old x2goagent (nxagent) and it works well with KDE/Plasma 5. No issues with kscreen whatsoever.
I just tested it again. Going from fullscreen to windowed mode, tilling around, etc... It always resizes nicely.
Sorry. Can't reproduce, can't help.
Regards, Rui Ferreira
-
Orion Poplawski -
Rui Ferreira -
Ulrich Sibiller