You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Connection as X2GO to a KDE Desktop will create a Window that can be resized. Plus the KDE menu is visible at bottom.
Current Behavior
Connection as X2GO to KDE Desktop will create a Window that cannot be resized. Plus the desktop is too big for the window, so even the KDE menu at bottom cannot be seen.
Environment
Client:
Reproducible with
CentOS 7.9 with X2GO client 4.1.1.1
Windows 10 with X2GO client 4.1.2.2
NOT reproducible with
Windows 10 with X2GO client 4.0.5.0
Workaround
(A)
If one does xrandr -s 1600x900, then this fix the window size, and we can see the KDE menu. But the window cannot be resized again. If after that, one logout (either KDE menu -> logout or directly at x2go client logout button, or let the KDE timeout autologout), then after relogging with the same user, the window size is now resizable and we can see directly the KDE menu.
(B)
Instead of doing xrandr [workaround (A)], it is also possible to create for any new user a kscreen file:
Then X2GO client connects as if we already configured window size of 1440x900 (see code kscreen beyond), and this also ignore X2GO client size field in profile. But that is OK because we can fix the size.
The text was updated successfully, but these errors were encountered:
On Fri, Sep 15, 2023 at 5:24 PM antoinetran ***@***.***> wrote:
Expected Behavior
Connection as X2GO to a KDE Desktop will create a Window that can be resized. Plus the KDE menu is visible at bottom.
Current Behavior
Connection as X2GO to KDE Desktop will create a Window that cannot be resized. Plus the desktop is too big for the window, so even the KDE menu at bottom cannot be seen.
Environment
Client:
Reproducible with
CentOS 7.9 with X2GO client 4.1.1.1
Windows 10 with X2GO client 4.1.2.2
NOT reproducible with
Windows 10 with X2GO client 4.0.5.0
Workaround
(A)
If one does xrandr -s 1600x900, then this fix the window size, and we can see the KDE menu. But the window cannot be resized again. If after that, one logout (either KDE menu -> logout or directly at x2go client logout button, or let the KDE timeout autologout), then after relogging with the same user, the window size is now resizable and we can see directly the KDE menu.
(B)
Instead of doing xrandr [workaround (A)], it is also possible to create for any new user a kscreen file:
mkdir /etc/skel/.kde/share/apps/kscreen -p
cat <<EOF >/etc/skel/.kde/share/apps/kscreen/c21f969b5f03d33d43e04f8f136e7682
[ { "enabled" : true, "id" : "default", "metadata" : { "name" : "default" }, "mode" : { "refresh" : 60.0, "size" : { "height" : 900, "width" : 1440 } }, "pos" : { "x" : 0, "y" : 0 }, "primary" : true, "rotation" : 1 } ]
EOF
Then X2GO client connects as if we already configured window size of 1440x900 (see code kscreen beyond), and this also ignore X2GO client size field in profile. But that is OK because we can fix the size.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
Expected Behavior
Connection as X2GO to a KDE Desktop will create a Window that can be resized. Plus the KDE menu is visible at bottom.
Current Behavior
Connection as X2GO to KDE Desktop will create a Window that cannot be resized. Plus the desktop is too big for the window, so even the KDE menu at bottom cannot be seen.
Environment
Client:
Reproducible with
NOT reproducible with
Workaround
(A)
If one does xrandr -s 1600x900, then this fix the window size, and we can see the KDE menu. But the window cannot be resized again. If after that, one logout (either KDE menu -> logout or directly at x2go client logout button, or let the KDE timeout autologout), then after relogging with the same user, the window size is now resizable and we can see directly the KDE menu.
(B)
Instead of doing xrandr [workaround (A)], it is also possible to create for any new user a kscreen file:
Then X2GO client connects as if we already configured window size of 1440x900 (see code kscreen beyond), and this also ignore X2GO client size field in profile. But that is OK because we can fix the size.
The text was updated successfully, but these errors were encountered: