I've created an LXD container with Fedora 34 and KDE. When I connect using x2go, I initially see a login screen (SDDM, I believe). After I log in, all I see is a black screen. No menu bars, no cursor.
There's nothing interesting in the system log, but a .xsession-errors file was generated. There's an XIO error:
$ cat .xsession-x2go-fedora34-errors XSession-x2go: X session started for eager at Sat Sep 4 18:59:28 UTC 2021 xsettingsd: Loaded 0 settings from /home/eager/.config/xsettingsd/xsettingsd.conf xsettingsd: Created window 0xe00001 on screen 0 with timestamp 2989364519 xsettingsd: Selection _XSETTINGS_S0 is owned by 0x0 xsettingsd: Took ownership of selection _XSETTINGS_S0 xsettingsd: Reloading configuration xsettingsd: Loaded 10 settings from /home/eager/.config/xsettingsd/xsettingsd.conf xsettingsd: Reloading configuration xsettingsd: Loaded 10 settings from /home/eager/.config/xsettingsd/xsettingsd.conf xsettingsd: Reloading configuration xsettingsd: Loaded 10 settings from /home/eager/.config/xsettingsd/xsettingsd.conf xsettingsd: Reloading configuration xsettingsd: Loaded 10 settings from /home/eager/.config/xsettingsd/xsettingsd.conf xsettingsd: Reloading configuration xsettingsd: Loaded 10 settings from /home/eager/.config/xsettingsd/xsettingsd.conf xsettingsd: Reloading configuration xsettingsd: Loaded 10 settings from /home/eager/.config/xsettingsd/xsettingsd.conf xsettingsd: Reloading configuration xsettingsd: Loaded 10 settings from /home/eager/.config/xsettingsd/xsettingsd.conf xsettingsd: Reloading configuration xsettingsd: Loaded 10 settings from /home/eager/.config/xsettingsd/xsettingsd.conf xsettingsd: Reloading configuration xsettingsd: Loaded 10 settings from /home/eager/.config/xsettingsd/xsettingsd.conf vmware-user: could not open /proc/fs/vmblock/dev Error: /usr/bin/vmtoolsd must be run inside a virtual machine on a VMware hypervisor product. Failed to rename ‘/home/eager/.abrt/spool’ to ‘/home/eager/.cache/abrt/spool’: No such file or directory Failed to rename ‘/home/eager/.abrt/settings’ to ‘/home/eager/.config/abrt/settings’: No such file or directory SELinux Troubleshooter: Applet requires SELinux be enabled to run akonadi.collectionattributetable OK akonadi.collectionmimetyperelation OK akonadi.collectionpimitemrelation OK akonadi.collectiontable OK akonadi.flagtable OK akonadi.mimetypetable OK akonadi.parttable OK akonadi.parttypetable OK akonadi.pimitemflagrelation OK akonadi.pimitemtable OK akonadi.pimitemtagrelation OK akonadi.relationtable OK akonadi.relationtypetable OK akonadi.resourcetable OK akonadi.schemaversiontable OK akonadi.tagattributetable OK akonadi.tagremoteidresourcerelationtable OK akonadi.tagtable OK akonadi.tagtypetable OK XIO: fatal IO error 2 (No such file or directory) on X server ":50" after 479 requests (478 known processed) with 0 events remaining.
Any suggestions?
-- Michael Eager
Hmm, does it work without using a container? Does it work inside the container with xfce, lxde or or just an xterm?
Uli
On Sat, Sep 4, 2021 at 9:15 PM Michael Eager <eager@eagerm.com> wrote:
I've created an LXD container with Fedora 34 and KDE. When I connect using x2go, I initially see a login screen (SDDM, I believe). After I log in, all I see is a black screen. No menu bars, no cursor.
There's nothing interesting in the system log, but a .xsession-errors file was generated. There's an XIO error:
$ cat .xsession-x2go-fedora34-errors XSession-x2go: X session started for eager at Sat Sep 4 18:59:28 UTC 2021 xsettingsd: Loaded 0 settings from /home/eager/.config/xsettingsd/xsettingsd.conf xsettingsd: Created window 0xe00001 on screen 0 with timestamp 2989364519 xsettingsd: Selection _XSETTINGS_S0 is owned by 0x0 xsettingsd: Took ownership of selection _XSETTINGS_S0 xsettingsd: Reloading configuration xsettingsd: Loaded 10 settings from /home/eager/.config/xsettingsd/xsettingsd.conf xsettingsd: Reloading configuration xsettingsd: Loaded 10 settings from /home/eager/.config/xsettingsd/xsettingsd.conf xsettingsd: Reloading configuration xsettingsd: Loaded 10 settings from /home/eager/.config/xsettingsd/xsettingsd.conf xsettingsd: Reloading configuration xsettingsd: Loaded 10 settings from /home/eager/.config/xsettingsd/xsettingsd.conf xsettingsd: Reloading configuration xsettingsd: Loaded 10 settings from /home/eager/.config/xsettingsd/xsettingsd.conf xsettingsd: Reloading configuration xsettingsd: Loaded 10 settings from /home/eager/.config/xsettingsd/xsettingsd.conf xsettingsd: Reloading configuration xsettingsd: Loaded 10 settings from /home/eager/.config/xsettingsd/xsettingsd.conf xsettingsd: Reloading configuration xsettingsd: Loaded 10 settings from /home/eager/.config/xsettingsd/xsettingsd.conf xsettingsd: Reloading configuration xsettingsd: Loaded 10 settings from /home/eager/.config/xsettingsd/xsettingsd.conf vmware-user: could not open /proc/fs/vmblock/dev Error: /usr/bin/vmtoolsd must be run inside a virtual machine on a VMware hypervisor product. Failed to rename ‘/home/eager/.abrt/spool’ to ‘/home/eager/.cache/abrt/spool’: No such file or directory Failed to rename ‘/home/eager/.abrt/settings’ to ‘/home/eager/.config/abrt/settings’: No such file or directory SELinux Troubleshooter: Applet requires SELinux be enabled to run akonadi.collectionattributetable OK akonadi.collectionmimetyperelation OK akonadi.collectionpimitemrelation OK akonadi.collectiontable OK akonadi.flagtable OK akonadi.mimetypetable OK akonadi.parttable OK akonadi.parttypetable OK akonadi.pimitemflagrelation OK akonadi.pimitemtable OK akonadi.pimitemtagrelation OK akonadi.relationtable OK akonadi.relationtypetable OK akonadi.resourcetable OK akonadi.schemaversiontable OK akonadi.tagattributetable OK akonadi.tagremoteidresourcerelationtable OK akonadi.tagtable OK akonadi.tagtypetable OK XIO: fatal IO error 2 (No such file or directory) on X server ":50" after 479 requests (478 known processed) with 0 events remaining.
Any suggestions?
-- Michael Eager
x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
I can run konsole from a ssh -X session.
On 9/4/21 3:21 PM, Ulrich Sibiller wrote:
Hmm, does it work without using a container? Does it work inside the container with xfce, lxde or or just an xterm?
Uli
On Sat, Sep 4, 2021 at 9:15 PM Michael Eager <eager@eagerm.com> wrote:
I've created an LXD container with Fedora 34 and KDE. When I connect using x2go, I initially see a login screen (SDDM, I believe). After I log in, all I see is a black screen. No menu bars, no cursor.
There's nothing interesting in the system log, but a .xsession-errors file was generated. There's an XIO error:
$ cat .xsession-x2go-fedora34-errors XSession-x2go: X session started for eager at Sat Sep 4 18:59:28 UTC 2021 xsettingsd: Loaded 0 settings from /home/eager/.config/xsettingsd/xsettingsd.conf xsettingsd: Created window 0xe00001 on screen 0 with timestamp 2989364519 xsettingsd: Selection _XSETTINGS_S0 is owned by 0x0 xsettingsd: Took ownership of selection _XSETTINGS_S0 xsettingsd: Reloading configuration xsettingsd: Loaded 10 settings from /home/eager/.config/xsettingsd/xsettingsd.conf xsettingsd: Reloading configuration xsettingsd: Loaded 10 settings from /home/eager/.config/xsettingsd/xsettingsd.conf xsettingsd: Reloading configuration xsettingsd: Loaded 10 settings from /home/eager/.config/xsettingsd/xsettingsd.conf xsettingsd: Reloading configuration xsettingsd: Loaded 10 settings from /home/eager/.config/xsettingsd/xsettingsd.conf xsettingsd: Reloading configuration xsettingsd: Loaded 10 settings from /home/eager/.config/xsettingsd/xsettingsd.conf xsettingsd: Reloading configuration xsettingsd: Loaded 10 settings from /home/eager/.config/xsettingsd/xsettingsd.conf xsettingsd: Reloading configuration xsettingsd: Loaded 10 settings from /home/eager/.config/xsettingsd/xsettingsd.conf xsettingsd: Reloading configuration xsettingsd: Loaded 10 settings from /home/eager/.config/xsettingsd/xsettingsd.conf xsettingsd: Reloading configuration xsettingsd: Loaded 10 settings from /home/eager/.config/xsettingsd/xsettingsd.conf vmware-user: could not open /proc/fs/vmblock/dev Error: /usr/bin/vmtoolsd must be run inside a virtual machine on a VMware hypervisor product. Failed to rename ‘/home/eager/.abrt/spool’ to ‘/home/eager/.cache/abrt/spool’: No such file or directory Failed to rename ‘/home/eager/.abrt/settings’ to ‘/home/eager/.config/abrt/settings’: No such file or directory SELinux Troubleshooter: Applet requires SELinux be enabled to run akonadi.collectionattributetable OK akonadi.collectionmimetyperelation OK akonadi.collectionpimitemrelation OK akonadi.collectiontable OK akonadi.flagtable OK akonadi.mimetypetable OK akonadi.parttable OK akonadi.parttypetable OK akonadi.pimitemflagrelation OK akonadi.pimitemtable OK akonadi.pimitemtagrelation OK akonadi.relationtable OK akonadi.relationtypetable OK akonadi.resourcetable OK akonadi.schemaversiontable OK akonadi.tagattributetable OK akonadi.tagremoteidresourcerelationtable OK akonadi.tagtable OK akonadi.tagtypetable OK XIO: fatal IO error 2 (No such file or directory) on X server ":50" after 479 requests (478 known processed) with 0 events remaining.
Any suggestions?
-- Michael Eager
x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
Well, that's not the same. Nxagent is derived from xnest and can be used in the same manner. So for testing please try this:
- Ssh -X fedoraserver in two shells
- In the first session run nxagent -ac :5
- In the second run xterm -display :5
- In the xterm run startkde (or however kde is started on fedora)
What happens?
Uli
Michael Eager <eager@eagerm.com> schrieb am So., 5. Sep. 2021, 03:59:
I can run konsole from a ssh -X session.
On 9/4/21 3:21 PM, Ulrich Sibiller wrote:
Hmm, does it work without using a container? Does it work inside the container with xfce, lxde or or just an xterm?
Uli
On Sat, Sep 4, 2021 at 9:15 PM Michael Eager <eager@eagerm.com> wrote:
I've created an LXD container with Fedora 34 and KDE. When I connect using x2go, I initially see a login screen (SDDM, I believe). After I log in, all I see is a black screen. No menu bars, no cursor.
There's nothing interesting in the system log, but a .xsession-errors file was generated. There's an XIO error:
$ cat .xsession-x2go-fedora34-errors XSession-x2go: X session started for eager at Sat Sep 4 18:59:28 UTC
2021
xsettingsd: Loaded 0 settings from /home/eager/.config/xsettingsd/xsettingsd.conf xsettingsd: Created window 0xe00001 on screen 0 with timestamp 2989364519 xsettingsd: Selection _XSETTINGS_S0 is owned by 0x0 xsettingsd: Took ownership of selection _XSETTINGS_S0 xsettingsd: Reloading configuration xsettingsd: Loaded 10 settings from /home/eager/.config/xsettingsd/xsettingsd.conf xsettingsd: Reloading configuration xsettingsd: Loaded 10 settings from /home/eager/.config/xsettingsd/xsettingsd.conf xsettingsd: Reloading configuration xsettingsd: Loaded 10 settings from /home/eager/.config/xsettingsd/xsettingsd.conf xsettingsd: Reloading configuration xsettingsd: Loaded 10 settings from /home/eager/.config/xsettingsd/xsettingsd.conf xsettingsd: Reloading configuration xsettingsd: Loaded 10 settings from /home/eager/.config/xsettingsd/xsettingsd.conf xsettingsd: Reloading configuration xsettingsd: Loaded 10 settings from /home/eager/.config/xsettingsd/xsettingsd.conf xsettingsd: Reloading configuration xsettingsd: Loaded 10 settings from /home/eager/.config/xsettingsd/xsettingsd.conf xsettingsd: Reloading configuration xsettingsd: Loaded 10 settings from /home/eager/.config/xsettingsd/xsettingsd.conf xsettingsd: Reloading configuration xsettingsd: Loaded 10 settings from /home/eager/.config/xsettingsd/xsettingsd.conf vmware-user: could not open /proc/fs/vmblock/dev Error: /usr/bin/vmtoolsd must be run inside a virtual machine on a VMware hypervisor product. Failed to rename ‘/home/eager/.abrt/spool’ to ‘/home/eager/.cache/abrt/spool’: No such file or directory Failed to rename ‘/home/eager/.abrt/settings’ to ‘/home/eager/.config/abrt/settings’: No such file or directory SELinux Troubleshooter: Applet requires SELinux be enabled to run akonadi.collectionattributetable OK akonadi.collectionmimetyperelation OK akonadi.collectionpimitemrelation OK akonadi.collectiontable OK akonadi.flagtable OK akonadi.mimetypetable OK akonadi.parttable OK akonadi.parttypetable OK akonadi.pimitemflagrelation OK akonadi.pimitemtable OK akonadi.pimitemtagrelation OK akonadi.relationtable OK akonadi.relationtypetable OK akonadi.resourcetable OK akonadi.schemaversiontable OK akonadi.tagattributetable OK akonadi.tagremoteidresourcerelationtable OK akonadi.tagtable OK akonadi.tagtypetable OK XIO: fatal IO error 2 (No such file or directory) on X server ":50" after 479 requests (478 known processed) with 0 events remaining.
Any suggestions?
-- Michael Eager
x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
On 9/5/21 3:18 AM, Ulrich Sibiller wrote:
Well, that's not the same. Nxagent is derived from xnest and can be used in the same manner. So for testing please try this:
- Ssh -X fedoraserver in two shell > 2. In the first session run nxagent -ac :5
I get an NX Agent window, completely black. Session started message in the shell.
- In the second run xterm -display :5
I ran "konsole -display :5" and konsole opened in the NS Agent window.
In the shell, I get qt.qpa.xcb: X server does not support XInput 2 qt.qpa.gl: QXcbConnection: Failed to initialize GLX qt.qpa.xcb: QXcbConnection: XCB error: 1 (BadRequest), sequence: 169, resource id: 225, major code: 130 (Unknown), minor code: 47
I think that these are all informational, not errors.
- In the xterm run startkde (or however kde is started on fedora)
I get a popup (not on the NX Agent window) saying "Plasma seems to already running on this display".
What happens?
Uli
Michael Eager <eager@eagerm.com <mailto:eager@eagerm.com>> schrieb am So., 5. Sep. 2021, 03:59:
I can run konsole from a ssh -X session. On 9/4/21 3:21 PM, Ulrich Sibiller wrote: > Hmm, does it work without using a container? Does it work inside the > container with xfce, lxde or or just an xterm? > > Uli > > On Sat, Sep 4, 2021 at 9:15 PM Michael Eager <eager@eagerm.com <mailto:eager@eagerm.com>> wrote: >> >> I've created an LXD container with Fedora 34 and KDE. When I connect >> using x2go, I initially see a login screen (SDDM, I believe). After I >> log in, all I see is a black screen. No menu bars, no cursor. >> >> There's nothing interesting in the system log, but a .xsession-errors >> file was generated. There's an XIO error: >> >> $ cat .xsession-x2go-fedora34-errors >> XSession-x2go: X session started for eager at Sat Sep 4 18:59:28 UTC 2021 >> xsettingsd: Loaded 0 settings from >> /home/eager/.config/xsettingsd/xsettingsd.conf >> xsettingsd: Created window 0xe00001 on screen 0 with timestamp 2989364519 >> xsettingsd: Selection _XSETTINGS_S0 is owned by 0x0 >> xsettingsd: Took ownership of selection _XSETTINGS_S0 >> xsettingsd: Reloading configuration >> xsettingsd: Loaded 10 settings from >> /home/eager/.config/xsettingsd/xsettingsd.conf >> xsettingsd: Reloading configuration >> xsettingsd: Loaded 10 settings from >> /home/eager/.config/xsettingsd/xsettingsd.conf >> xsettingsd: Reloading configuration >> xsettingsd: Loaded 10 settings from >> /home/eager/.config/xsettingsd/xsettingsd.conf >> xsettingsd: Reloading configuration >> xsettingsd: Loaded 10 settings from >> /home/eager/.config/xsettingsd/xsettingsd.conf >> xsettingsd: Reloading configuration >> xsettingsd: Loaded 10 settings from >> /home/eager/.config/xsettingsd/xsettingsd.conf >> xsettingsd: Reloading configuration >> xsettingsd: Loaded 10 settings from >> /home/eager/.config/xsettingsd/xsettingsd.conf >> xsettingsd: Reloading configuration >> xsettingsd: Loaded 10 settings from >> /home/eager/.config/xsettingsd/xsettingsd.conf >> xsettingsd: Reloading configuration >> xsettingsd: Loaded 10 settings from >> /home/eager/.config/xsettingsd/xsettingsd.conf >> xsettingsd: Reloading configuration >> xsettingsd: Loaded 10 settings from >> /home/eager/.config/xsettingsd/xsettingsd.conf >> vmware-user: could not open /proc/fs/vmblock/dev >> Error: /usr/bin/vmtoolsd must be run inside a virtual machine on a >> VMware hypervisor product. >> Failed to rename ‘/home/eager/.abrt/spool’ to >> ‘/home/eager/.cache/abrt/spool’: No such file or directory >> Failed to rename ‘/home/eager/.abrt/settings’ to >> ‘/home/eager/.config/abrt/settings’: No such file or directory >> SELinux Troubleshooter: Applet requires SELinux be enabled to run >> akonadi.collectionattributetable OK >> akonadi.collectionmimetyperelation OK >> akonadi.collectionpimitemrelation OK >> akonadi.collectiontable OK >> akonadi.flagtable OK >> akonadi.mimetypetable OK >> akonadi.parttable OK >> akonadi.parttypetable OK >> akonadi.pimitemflagrelation OK >> akonadi.pimitemtable OK >> akonadi.pimitemtagrelation OK >> akonadi.relationtable OK >> akonadi.relationtypetable OK >> akonadi.resourcetable OK >> akonadi.schemaversiontable OK >> akonadi.tagattributetable OK >> akonadi.tagremoteidresourcerelationtable OK >> akonadi.tagtable OK >> akonadi.tagtypetable OK >> XIO: fatal IO error 2 (No such file or directory) on X server ":50" >> after 479 requests (478 known processed) with 0 events remaining. >> >> >> Any suggestions? >> >> -- >> Michael Eager >> >> _______________________________________________ >> x2go-user mailing list >> x2go-user@lists.x2go.org <mailto:x2go-user@lists.x2go.org> >> https://lists.x2go.org/listinfo/x2go-user <https://lists.x2go.org/listinfo/x2go-user> >
As another data point, I installed TigerVNC and it works.
On 9/5/21 9:01 AM, Michael Eager wrote:
On 9/5/21 3:18 AM, Ulrich Sibiller wrote:
Well, that's not the same. Nxagent is derived from xnest and can be used in the same manner. So for testing please try this:
- Ssh -X fedoraserver in two shell > 2. In the first session run
nxagent -ac :5I get an NX Agent window, completely black. Session started message in the shell.
- In the second run xterm -display :5
I ran "konsole -display :5" and konsole opened in the NS Agent window.
In the shell, I get qt.qpa.xcb: X server does not support XInput 2 qt.qpa.gl: QXcbConnection: Failed to initialize GLX qt.qpa.xcb: QXcbConnection: XCB error: 1 (BadRequest), sequence: 169, resource id: 225, major code: 130 (Unknown), minor code: 47
I think that these are all informational, not errors.
- In the xterm run startkde (or however kde is started on fedora)
I get a popup (not on the NX Agent window) saying "Plasma seems to already running on this display".
What happens?
Uli
Michael Eager <eager@eagerm.com <mailto:eager@eagerm.com>> schrieb am So., 5. Sep. 2021, 03:59:
I can run konsole from a ssh -X session.
On 9/4/21 3:21 PM, Ulrich Sibiller wrote: > Hmm, does it work without using a container? Does it work inside the > container with xfce, lxde or or just an xterm? > > Uli > > On Sat, Sep 4, 2021 at 9:15 PM Michael Eager <eager@eagerm.com <mailto:eager@eagerm.com>> wrote: >> >> I've created an LXD container with Fedora 34 and KDE. When I connect >> using x2go, I initially see a login screen (SDDM, I believe). After I >> log in, all I see is a black screen. No menu bars, no cursor. >> >> There's nothing interesting in the system log, but a .xsession-errors >> file was generated. There's an XIO error: >> >> $ cat .xsession-x2go-fedora34-errors >> XSession-x2go: X session started for eager at Sat Sep 4 18:59:28 UTC 2021 >> xsettingsd: Loaded 0 settings from >> /home/eager/.config/xsettingsd/xsettingsd.conf >> xsettingsd: Created window 0xe00001 on screen 0 with timestamp 2989364519 >> xsettingsd: Selection _XSETTINGS_S0 is owned by 0x0 >> xsettingsd: Took ownership of selection _XSETTINGS_S0 >> xsettingsd: Reloading configuration >> xsettingsd: Loaded 10 settings from >> /home/eager/.config/xsettingsd/xsettingsd.conf >> xsettingsd: Reloading configuration >> xsettingsd: Loaded 10 settings from >> /home/eager/.config/xsettingsd/xsettingsd.conf >> xsettingsd: Reloading configuration >> xsettingsd: Loaded 10 settings from >> /home/eager/.config/xsettingsd/xsettingsd.conf >> xsettingsd: Reloading configuration >> xsettingsd: Loaded 10 settings from >> /home/eager/.config/xsettingsd/xsettingsd.conf >> xsettingsd: Reloading configuration >> xsettingsd: Loaded 10 settings from >> /home/eager/.config/xsettingsd/xsettingsd.conf >> xsettingsd: Reloading configuration >> xsettingsd: Loaded 10 settings from >> /home/eager/.config/xsettingsd/xsettingsd.conf >> xsettingsd: Reloading configuration >> xsettingsd: Loaded 10 settings from >> /home/eager/.config/xsettingsd/xsettingsd.conf >> xsettingsd: Reloading configuration >> xsettingsd: Loaded 10 settings from >> /home/eager/.config/xsettingsd/xsettingsd.conf >> xsettingsd: Reloading configuration >> xsettingsd: Loaded 10 settings from >> /home/eager/.config/xsettingsd/xsettingsd.conf >> vmware-user: could not open /proc/fs/vmblock/dev >> Error: /usr/bin/vmtoolsd must be run inside a virtual machine on a >> VMware hypervisor product. >> Failed to rename ‘/home/eager/.abrt/spool’ to >> ‘/home/eager/.cache/abrt/spool’: No such file or directory >> Failed to rename ‘/home/eager/.abrt/settings’ to >> ‘/home/eager/.config/abrt/settings’: No such file or directory >> SELinux Troubleshooter: Applet requires SELinux be enabled to run >> akonadi.collectionattributetable OK >> akonadi.collectionmimetyperelation OK >> akonadi.collectionpimitemrelation OK >> akonadi.collectiontable OK >> akonadi.flagtable OK >> akonadi.mimetypetable OK >> akonadi.parttable OK >> akonadi.parttypetable OK >> akonadi.pimitemflagrelation OK >> akonadi.pimitemtable OK >> akonadi.pimitemtagrelation OK >> akonadi.relationtable OK >> akonadi.relationtypetable OK >> akonadi.resourcetable OK >> akonadi.schemaversiontable OK >> akonadi.tagattributetable OK >> akonadi.tagremoteidresourcerelationtable OK >> akonadi.tagtable OK >> akonadi.tagtypetable OK >> XIO: fatal IO error 2 (No such file or directory) on X server ":50" >> after 479 requests (478 known processed) with 0 events remaining. >> >> >> Any suggestions? >> >> -- >> Michael Eager >> >> _______________________________________________ >> x2go-user mailing list >> x2go-user@lists.x2go.org <mailto:x2go-user@lists.x2go.org> >> https://lists.x2go.org/listinfo/x2go-user <https://lists.x2go.org/listinfo/x2go-user> >
On Sun, Sep 5, 2021 at 6:02 PM Michael Eager <eager@eagerm.com> wrote:
On 9/5/21 3:18 AM, Ulrich Sibiller wrote:
Well, that's not the same. Nxagent is derived from xnest and can be used in the same manner. So for testing please try this:
- Ssh -X fedoraserver in two shell > 2. In the first session run nxagent -ac :5
I get an NX Agent window, completely black. Session started message in the shell.
- In the second run xterm -display :5
I ran "konsole -display :5" and konsole opened in the NS Agent window.
no, please run xterm -display :5 and run konsole from there. This is to ensure all started program will get the right display.
In the shell, I get qt.qpa.xcb: X server does not support XInput 2 qt.qpa.gl: QXcbConnection: Failed to initialize GLX qt.qpa.xcb: QXcbConnection: XCB error: 1 (BadRequest), sequence: 169, resource id: 225, major code: 130 (Unknown), minor code: 47
I think that these are all informational, not errors.
Hmm, not sure. At least the xkb thing looks suspicious.
- In the xterm run startkde (or however kde is started on fedora)
I get a popup (not on the NX Agent window) saying "Plasma seems to already running on this display".
That's because you skipped the xterm step. The KDE framework is referring to the local display...
uli
On 9/5/21 12:16 PM, Ulrich Sibiller wrote:
On Sun, Sep 5, 2021 at 6:02 PM Michael Eager <eager@eagerm.com> wrote:
On 9/5/21 3:18 AM, Ulrich Sibiller wrote:
Well, that's not the same. Nxagent is derived from xnest and can be used in the same manner. So for testing please try this:
- Ssh -X fedoraserver in two shell > 2. In the first session run nxagent -ac :5
I get an NX Agent window, completely black. Session started message in the shell.
- In the second run xterm -display :5
I ran "konsole -display :5" and konsole opened in the NS Agent window.
no, please run xterm -display :5 and run konsole from there. This is to ensure all started program will get the right display.
Xterm was not previously installed. Installed xterm. It displays an xterm window on NX Agent window.
In the shell, I get qt.qpa.xcb: X server does not support XInput 2 qt.qpa.gl: QXcbConnection: Failed to initialize GLX qt.qpa.xcb: QXcbConnection: XCB error: 1 (BadRequest), sequence: 169, resource id: 225, major code: 130 (Unknown), minor code: 47
I think that these are all informational, not errors.
Hmm, not sure. At least the xkb thing looks suspicious.
- In the xterm run startkde (or however kde is started on fedora)
I get a popup (not on the NX Agent window) saying "Plasma seems to already running on this display".
That's because you skipped the xterm step. The KDE framework is referring to the local display...
(Actually, I previously replaced the xterm step with running konsole with the same command line options. The popup was referring to the target, not the local display. Running konsole probably started KDE. But it did confuse the test.)
Ran 'startkde' in the xterm window, I get message about XInput 2 and two messages about skipping syncing environment variable BASH_FUNC_which%%. The NX Agent window is otherwise mostly non-responsive. Right or left click does nothing. The cursor does change from | within the xterm to arrow outside of the xterm. There is no window menu or title bar on the xterm window. None of the KDE/Plasma widgets are displayed.
If I run 'konsole' in the xterm window, it displays in the NX Agent window. There is no window title or decorations.
When I run VNCserver, the KDE/Plasma widgets are displayed. Running konsole does show a window title bar with decorations.
Hi Ulrich --
Anything I can do to help diagnose this problem?
On 9/5/21 1:22 PM, Michael Eager wrote:
On 9/5/21 12:16 PM, Ulrich Sibiller wrote:
On Sun, Sep 5, 2021 at 6:02 PM Michael Eager <eager@eagerm.com> wrote:
On 9/5/21 3:18 AM, Ulrich Sibiller wrote:
Well, that's not the same. Nxagent is derived from xnest and can be used in the same manner. So for testing please try this:
- Ssh -X fedoraserver in two shell > 2. In the first session run
nxagent -ac :5I get an NX Agent window, completely black. Session started message in the shell.
- In the second run xterm -display :5
I ran "konsole -display :5" and konsole opened in the NS Agent window.
no, please run xterm -display :5 and run konsole from there. This is to ensure all started program will get the right display.
Xterm was not previously installed. Installed xterm. It displays an xterm window on NX Agent window.
In the shell, I get qt.qpa.xcb: X server does not support XInput 2 qt.qpa.gl: QXcbConnection: Failed to initialize GLX qt.qpa.xcb: QXcbConnection: XCB error: 1 (BadRequest), sequence: 169, resource id: 225, major code: 130 (Unknown), minor code: 47
I think that these are all informational, not errors.
Hmm, not sure. At least the xkb thing looks suspicious.
- In the xterm run startkde (or however kde is started on fedora)
I get a popup (not on the NX Agent window) saying "Plasma seems to already running on this display".
That's because you skipped the xterm step. The KDE framework is referring to the local display...
(Actually, I previously replaced the xterm step with running konsole with the same command line options. The popup was referring to the target, not the local display. Running konsole probably started KDE. But it did confuse the test.)
Ran 'startkde' in the xterm window, I get message about XInput 2 and two messages about skipping syncing environment variable BASH_FUNC_which%%. The NX Agent window is otherwise mostly non-responsive. Right or left click does nothing. The cursor does change from | within the xterm to arrow outside of the xterm. There is no window menu or title bar on the xterm window. None of the KDE/Plasma widgets are displayed.
If I run 'konsole' in the xterm window, it displays in the NX Agent window. There is no window title or decorations.
When I run VNCserver, the KDE/Plasma widgets are displayed. Running konsole does show a window title bar with decorations.
-
Michael Eager -
Ulrich Sibiller