Replies: 2 comments 14 replies
-
|
Thanks for raising this, @djakubek Having just rebuilt my xrdp development rig, I'm seeing something similar on Ubuntu 24.04, but not in xrdp - I'm seeing it on the VM console using the QEMU QXL driver. Ubuntu 22.04 works fine in the same configuration. There seem to be a few people having similar issues (on the console) on 24.04 using Xorg. There are no obvious common factors between them that I can see, except using At this point I can't offer you a solution, but here are a few potential workarounds:-
Hope this helps a little. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Here are the logs you requested. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks @djakubek For the log in question, I can't see there's much to be changed here. Are any of your users in the |
Beta Was this translation helpful? Give feedback.
13 replies
-
|
Unfortunately, for the 'Black Screen' case, I was only able to generate the information For the case where the screen works correctly, I've included the information below - Case 2. I added a bit more information than you requested, as I noticed there are significant differences, particularly that new lines appeared in the well-functioning Case 1 - Black Screen with Cursor Case 2 - Works Correctly |
Beta Was this translation helpful? Give feedback.
-
|
I'm out of useful ideas too at the moment. I've had a look at some numbers with 22.04 HWE, which works fine for me:-
The Mesa version bump is the only big change. Then of course, GNOME is utterly different too. I tend to use XFCE for testing as it gets in teh way a lot less. I'll bump my Mesa version here using Kisak mesa and see what happens. This is not a recommendation! |
Beta Was this translation helpful? Give feedback.
-
|
Didn't take long - no real improvement here. On 3rd login to the console with Xorg selected I got a black screen with cursor. |
Beta Was this translation helpful? Give feedback.
-
|
I've just installed XFCE on the same VM with |
Beta Was this translation helpful? Give feedback.
-
|
One more thing to try, ONLY if you're logged on as the affected user (and not root) Alternatively, find the required gmoe-shell with I researched ways to restart the compositor manually. You need to restart gnome-shell as mutter is built-in to gnome-shell. There's a command line for this which used to work, but no longer does. |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have an installation of Ubuntu 24.04 LTS with the Gnome graphical interface in a VMware environment:
60 GB RAM
55 GB Disk
8 CPUs
The basic installation consists of standard packages without any tweaks: xrdp, dbus-x11. The server is used by approximately 30 users simultaneously, connected via RDP from Windows 10/11. The users are created using the useradd -m ... command. The issue is difficult to pinpoint. I've searched extensively and haven't found any solid solutions. The problem manifests randomly as a black screen with an active cursor, with no response to keyboard inputs like ENTER or ESC.
This issue occurs for a random user upon their first login after a server restart. Sometimes it's the first user, other times it may be the third or any other user. Out of 30 users, about 24 log in successfully. Occasionally, all users log in without issue. In the second scenario, when sessions are active and a user attempts to reconnect to their RDP session after some time, they again encounter the "Black Screen."
I handle the problem by identifying the session of the user who faces the "Black Screen" and terminate it using loginctl terminate-session . Re-logging into the same account usually resolves the issue, though sometimes I have to repeat the process twice in a row.
I tried removing all snapd packages from the system, which did not yield the expected results, although working with the desktop became more responsive, which is a plus for me. Currently, only the .deb package of the Chrome browser is installed.
xrdp version: 0.9.24
Dbus-daemon version: 1.14.10
In the file nano /etc/gdm3/custom.conf:
#Wayland=false is left by default without any impact on solving the issue.
I also attempted to add the variable to the file /etc/xrdp/startwm.sh --> export XDG_SESSION_TYPE=x11.
I’m out of ideas now. :(
I’m attaching the syslog logs.
Beta Was this translation helpful? Give feedback.
All reactions