Bug 1955973 - X2goserver Gnome Desktop, XFCE Desktop issues.
Summary: X2goserver Gnome Desktop, XFCE Desktop issues.
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: x2goserver
Version: 34
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Orion Poplawski
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-05-01 20:35 UTC by Jeff Sadowski
Modified: 2022-06-08 00:25 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-06-08 00:25:03 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jeff Sadowski 2021-05-01 20:35:06 UTC
Description of problem:
X2go seems to try and start the Wayland version of the desktop even if the Xorg version exists. Many desktops seem broken because of this. Not sure if this is an x2go server issue or each desktop that is broken because of this issue. There should be a way for you to communicate and work this out.


Version-Release number of selected component (if applicable):
Package x2goserver-4.1.0.3-10.fc34.x86_64 is already installed.

How reproducible:
gnome will not even start XFCE now seems broken(worked in Fedora 33) KDE sort of works seems not to resize. 

Steps to Reproduce:
1.install x2goserver
2. Try connecting using one of the broken desktops mentioned above

Actual results:
Gnome will not even start. XFCE stops working after a while. Can't seem to resize or move windows.

Expected results:
Normal remote desktop behavior.

Additional info:

Comment 1 Orion Poplawski 2021-05-01 20:43:30 UTC
Please report upstream.  For the most part I just package up what they ship.

Comment 2 Jeff Sadowski 2021-05-02 15:22:03 UTC
Is there maybe a way to point gnome and xfce to Xorg versions for x2goserver? Is it maybe a fault of the desktops that are putting wayland startup scripts where xorg startup scripts should be? Maybe its a missing standard that should exist?

Comment 3 Ben Cotton 2022-05-12 16:21:29 UTC
This message is a reminder that Fedora Linux 34 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '34'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 34 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 4 Ben Cotton 2022-06-08 00:25:03 UTC
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07.

Fedora Linux 34 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.