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 wrote:
On 9/5/21 3:18 AM, Ulrich Sibiller wrote:
Well, that's not the same. Nxagent is derived from
On 9/5/21 12:16 PM, Ulrich Sibiller wrote:
On Sun, Sep 5, 2021 at 6:02 PM 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:
1. Ssh -X fedoraserver in two
On Sun, Sep 5, 2021 at 6:02 PM 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:
> >
> > 1. Ssh -X fedoraserver in two shell > 2. In the first
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:
1. Ssh -X fedoraserver in
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:
1. Ssh -X fedoraserver in two shell > 2. In the first session run nxagent -ac
:5
I get an NX Agent window, completely
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:
1. Ssh -X fedoraserver in two shells
2. In the first session run nxagent -ac :5
3. In the second run xterm -display :5
4. In the xterm run startkde (or however kde is
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 wrote:
I've created an LXD container with
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 wrote:
>
> I've created an LXD container with Fedora 34 and KDE. When I connect
> using x2go, I initially see a login screen
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.
On 1/30/19 4:40 PM, Orion Poplawski wrote:
Anyone know what would cause a completely black screen on resuming a session?
windows 10 client, EL7 server. Haven't heard reports of this for a while.
Looks like a hung NFS mount is to blame here. A number of processes
including plasma-desktop
Anyone know what would cause a completely black screen on resuming a session?
windows 10 client, EL7 server. Haven't heard reports of this for a while.
--
Orion Poplawski
Manager of NWRA Technical Systems 720-772-5637
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380
bil...@gmail.com>
To: Brian Walsh <brian.wa...@owmobility.com>,
"x2go-user@lists.x2go.org" <x2go-user@lists.x2go.org>
Subject: Re: [X2Go-User] Black screen of death - please help
I suggest trying it with a clean user profile on the server, maybe create a
test user.
Hi,
I've recently upgraded from redhat 7.0 to 7.3 and as such lost some of my
useful tools - one of which was x2go.
So I reinstalled the relevant rpms and using the same client and config I now
can login but just get a blank black screen with no way to open a terminal etc.
I'm using XFCE (as I
I'm trying to use x2goclient on a Ubuntu 15.10 GNOME laptop
to connect to an system running Fedora 23 KDE.
When I connect, I see the K-gear logo as KDE starts, followed by
a popup saying that Firefox is already running, which I cancel.
Other than that, the screen is black. Left-click or
o-user@lists.x2go.org
Subject: [X2Go-User] Black screen
I'm trying to use x2goclient on a Ubuntu 15.10 GNOME laptop
to connect to an system running Fedora 23 KDE.
When I connect, I see the K-gear logo as KDE starts, followed by
a popup saying that Firefox is already running, which I cancel.
Othe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Am 28.11.2015 um 18:20 schrieb Robert Dinse:
>
> Ubuntu ships with kde5 which is incompatible due to plasmashell
> requiring GLX 1.3 per the X2Go Wiki.
>
> Mate works well on 15.10 with X2Go.
>
Uh,
Michael is running FC23, not Ubuntu, on his
, 28 Nov 2015 18:25:50 +0100
From: Stefan Baur <x2go-m...@baur-itcs.de>
To: x2go-user@lists.x2go.org
Subject: Re: [X2Go-User] Black screen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Am 28.11.2015 um 18:20 schrieb Robert Dinse:
Ubuntu ships with kde5 which is incompatible due to plasm
+0100
From: Stefan Baur <x2go-m...@baur-itcs.de>
To: x2go-user@lists.x2go.org
Subject: Re: [X2Go-User] Black screen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Am 28.11.2015 um 18:20 schrieb Robert Dinse:
Ubuntu ships with kde5 which is incompatible due to plasmashell
requiring GLX 1
ct: Re: [X2Go-User] Black screen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Am 28.11.2015 um 18:20 schrieb Robert Dinse:
Ubuntu ships with kde5 which is incompatible due to plasmashell
requiring GLX 1.3 per the X2Go Wiki.
Mate works well on 15.10 with X2Go.
Uh,
Michael is running FC23, not
19 matches
Mail list logo
