xrdp does not show the (Gnome) GUI :(

L

Louis

I am trying to get FreeBSD14 running in a TrueNas Scale VM. That partly .... works now
One of the issues I am facing is xrdp

I use the xrdp-server to provide the GNOME-desktop to windows11 Remote Desktop Viewer. On communication level that works, however two problems:
1) the display on windows shows a terminal and not the GNOME desktop
2) If I start the xrdp connection the local vnc session as displayed using the Spice viewer disappears. That is not dramatic and it is perhaps not possible to show both versions of the Gnome GUI simultaneous, but it would have been nice

What ever the main problem is of course, that the Gnome desktop is not shown on the windows system. I noticed that others had the problem as well. I some some weird solutions mostly related to linux versions.

What ever, I need to know how to solve the issue for FreeBSD.

PS.
note that I installed and enabled xrdp and sesman
xrdp_enable="YES"
xrdp_sesman_enable="YES"
te that I installed
 
Can you explain which verdict you have? There is communication between the xrdp-server (on FreeBSD14) and rdp on windows. In the left top corner of the rdp screen is a terminal window, I can even enter commands there.
 
Louis said:
Can you explain which verdict you have? There is communication between the xrdp-server (on FreeBSD14) and rdp on windows. In the left top corner of the rdp screen is a terminal window, I can even enter commands there.
Click to expand...
I was just trying to think of helpful thing that it could possibly be. There are ports associated with an rdp server that may be blocked by your firewall was my thought. I'm sure there are other far more skilled in the area of rdp on freebsd that could offer more experience oriented assistance.
 
The default exec path for xrdp on FreeBSD is to use /usr/local/etc/xrdp/startwm.sh

This just runs xterm and sounds like what is going on. If you look at the default sesman.ini you'll see UserWindowManager=startwm.sh. This is a script if found in ~/ will exec instead of the script listed above.

So in your home dir create an executable script named startwm.sh and add whatever you want to run to that. Maybe something like:

#!/bin/sh
{ eval $(dbus-launch --sh-syntax); exec /usr/local/bin/gnome-session; }


I believer you're correct that most current desktops will not allow multiple GUI sessions from the same user.
 
derekschrock said:
The default exec path for xrdp on FreeBSD is to use /usr/local/etc/xrdp/startwm.sh

This just runs xterm and sounds like what is going on. If you look at the default sesman.ini you'll see UserWindowManager=startwm.sh. This is a script if found in ~/ will exec instead of the script listed above.

So in your home dir create an executable script named startwm.sh and add whatever you want to run to that. Maybe something like:

#!/bin/sh
{ eval $(dbus-launch --sh-syntax); exec /usr/local/bin/gnome-session; }


I believer you're correct that most current desktops will not allow multiple GUI sessions from the same user.
Click to expand...
Thanks,
I was thinking in the same direction and did:
- generate a startwm.sh file in the user home dir (root home dir and me as user). I also made those executable (chmod +x startwm.sh)
- In startwm.sh just exec gnome-session (I tried multiple options among those also
{ eval $(dbus-launch --sh-syntax); exec /usr/local/bin/gnome-session; } and
eval $(dbus-launch --sh-syntax)
exec /usr/local/bin/gnome-session

But it has some results but not work. I have multiple probably related items:
- with "exec gnome-session" xrdp shows gnome inlog ..... for the root user and not for the other user
- but I can not login keyboard and mouse do not work at the moment the gnome login screen arrives
- related, if I use the spice vnc application beeing part of TrueNas Scale, I do get the gnome gui even without the startwm.sh file
- however after gnome login, mouse and keyboard do not work :'‑( (problem-1: mouse and keyboard)
- problem-2 gnome does not show up via xrdp for the other user
- problem-3 gnome, via rdp root user screen is not the intendend 1920x1080 window but probably the size of my 4K-monitor (showing partly in smaller window)

So we have some progress, but its not working yet :'‑(
 
Hum, the situation is vague. After a couple of tries and vm restarts, and changing the windows size in the windows rdp gui to 1920x1080, I can login via xrdp on windows as root.
Not as normal user :eek:
After some time the root session is locked and I can not login to the gnome window

If I try as normal user after simetime there is "a popup window on the rdp screen" saying
sesman connect OK
sending login info to session manager please wait
login successful for etc
connection problem giving up
some problem
error connecting user session

Now and than I have to restart the vm, to solve rdp issues / locks

The window size can I correct using a setting in the window rdp client


So still issues left :rude:
 
GNOME uses Wayland, so might be something to do with xrdp probably being developed for Xorg.

An extremely brief Google brought up the word Waypipe, might be an avenue for exploration. Or change your GUI environment
 
I looked at the errorlogs and one of the things I noticed is "There is no X server active on display", and yep I have some verdict in direction wayland related things as well.

It is also strange that it works better with user "root" than if I try with "some other user (even being member of wheels)". That points in an autorisation direction !?

Never the less here part of the logs I captured

192.168.100.20 2024-02-03 20:15:00.000 /usr/sbin/cron[950]:
/usr/sbin/cron[950]: (root) CMD (/usr/libexec/atrun)
192.168.100.20 2024-02-03 20:14:39.000 xrdp[935]:
xrdp[935]: [INFO ] Error connecting to user session
192.168.100.20 2024-02-03 20:14:39.000 kernel:
kernel: Feb 3 20:14:39 <daemon.err> freebsd xrdp[935]: [ERROR] xrdp_wm_log_msg: Error connecting to user session
192.168.100.20 2024-02-03 20:14:39.000 xrdp[935]:
xrdp[935]: [ERROR] xrdp_wm_log_msg: Error connecting to user session
192.168.100.20 2024-02-03 20:14:39.000 xrdp[935]:
xrdp[935]: [INFO ] some problem
192.168.100.20 2024-02-03 20:14:39.000 xrdp[935]:
xrdp[935]: [INFO ] connection problem, giving up
192.168.100.20 2024-02-03 20:11:14.000 xrdp-sesman[805]:
xrdp-sesman[805]: [INFO ] ++ terminated session: username louisb, display :13.0, session_pid 943, ip 192.168.17.34:39928 - socket: 12
192.168.100.20 2024-02-03 20:11:14.000 xrdp-sesman[805]:
xrdp-sesman[805]: [INFO ] Process 943 has exited
192.168.100.20 2024-02-03 20:11:14.000 xrdp-sesman[944]:
xrdp-sesman[944]: [INFO ] cleanup_sockets:
192.168.100.20 2024-02-03 20:11:14.000 xrdp-sesman[944]:
xrdp-sesman[944]: [INFO ] xrdp channel server for display 13 (pid 948) exit code 0 and signal number 0
192.168.100.20 2024-02-03 20:11:14.000 xrdp-sesman[944]:
xrdp-sesman[944]: [INFO ] X server on display 13 (pid 946) returned exit code 1 and signal number 0
192.168.100.20 2024-02-03 20:11:14.000 xrdp-sesman[944]:
xrdp-sesman[944]: [INFO ] Terminating the xrdp channel server (pid 948) on display 13
192.168.100.20 2024-02-03 20:11:14.000 xrdp-sesman[944]:
xrdp-sesman[944]: [INFO ] Terminating X server (pid 946) on display 13
192.168.100.20 2024-02-03 20:11:14.000 xrdp-sesman[944]:
xrdp-sesman[944]: [INFO ] Calling auth_stop_session and auth_end from pid 944
192.168.100.20 2024-02-03 20:11:14.000 xrdp-sesman[944]:
xrdp-sesman[944]: [WARN ] Window manager (pid 945, display 13) exited quickly (0 secs). This could indicate a window manager config problem
192.168.100.20 2024-02-03 20:11:14.000 kernel:
kernel: Feb 3 20:11:14 <daemon.err> freebsd xrdp-sesman[945]: [ERROR] A fatal error has occurred attempting to start the window manager on display 13, aborting connection
192.168.100.20 2024-02-03 20:11:14.000 xrdp-sesman[945]:
xrdp-sesman[945]: [ERROR] A fatal error has occurred attempting to start the window manager on display 13, aborting connection
192.168.100.20 2024-02-03 20:11:14.000 kernel:
kernel: Feb 3 20:11:14 <daemon.err> freebsd xrdp-sesman[945]: [ERROR] There is no X server active on display 13
192.168.100.20 2024-02-03 20:11:14.000 xrdp-sesman[945]:
xrdp-sesman[945]: [ERROR] There is no X server active on display 13
192.168.100.20 2024-02-03 20:11:14.000 xrdp-sesman[945]:
xrdp-sesman[945]: [WARN ] Timed out waiting for X server on display 13 to startup
192.168.100.20 2024-02-03 20:11:14.000 xrdp-sesman[944]:
xrdp-sesman[944]: [INFO ] Session in progress on display 13, waiting until the window manager (pid 945) exits to end the session
192.168.100.20 2024-02-03 20:11:14.000 xrdp-sesman[948]:
xrdp-sesman[948]: [INFO ] Starting the xrdp channel server for display 13
192.168.100.20 2024-02-03 20:11:14.000 xrdp-sesman[944]:
xrdp-sesman[944]: [INFO ] Session started successfully for user louis on display 13
192.168.100.20 2024-02-03 20:11:14.000 xrdp-sesman[944]:
xrdp-sesman[944]: [WARN ] Timed out waiting for X server on display 13 to startup
192.168.100.20 2024-02-03 20:11:03.000 xrdp-sesman[946]:
xrdp-sesman[946]: [INFO ] Starting X server on display 13: /usr/local/libexec/Xorg :13 -auth .Xauthority -config xrdp/xorg.conf -noreset -nolisten tcp
192.168.100.20 2024-02-03 20:11:03.000 xrdp[935]:
xrdp[935]: [INFO ] lib_mod_connect: connecting via UNIX socket
192.168.100.20 2024-02-03 20:11:03.000 xrdp[935]:
xrdp[935]: [INFO ] started connecting
 
If root works and non-root doesn't it sounds like you need to maybe put the user in the video group. Modern gnome needs acceleration. gnome works in xrdp I have it running. There's just any depends for it that might be missing. Other gnome things, dbus, the user running dbus per window manager, etc...
 
However, I have to admit my setup is unique since the only place I have to test is in two jail with xrdp devel branch and xrdp gfx branch with custom options (mainly the different with default ports is DRI support).
 
I think there is more than one issue under the hood.
= Root works via xrdp,
= but via truenas vnc even for root keyboard and mouse do not work as soon as gnome becomes active"
= same for the normal user (being member of both wheel and video (both not required I think)
= for the normal user after connecting via xrdp and login the screen stays blue, after some time the connection log appears telling something went wrong

As you see I did allready add the video group to the users, dispite that I think it is not required (and does not help)
The video is not accelerated for the simple fact, that you can not share video cards (I am afraid for commercial reasons :rude: ).
However, just need a system for simplethings not requireing high performance video. The xrdp root session show, that even a you tube video is possible without acceleration.

Tja ...... how to fix this ???
 
I still did not manage to get things working. However I have some verdict in the direction of session managment.
The sesman config is in /usr/local/etc/xrdp/sesman.ini and in that file I raised the loging level to TRACE

Below the resulting logging. I did mark verdict things bold


17:05:00.000 /usr/sbin/cron[959]: 6 /usr/sbin/cron[959]: (root) CMD (/usr/libexec/atrun)
17:03:54.000 xrdp-sesman[807]: 6 xrdp-sesman[807]: [INFO ] ++ terminated session: username louis, display :13.0, session_pid 952, ip 192.168.17.34:3211 - socket: 12
17:03:54.000 xrdp-sesman[807]: 6 xrdp-sesman[807]: [INFO ] Process 952 has exited
17:03:54.000 xrdp-sesman[953]: 6 xrdp-sesman[953]: [INFO ] cleanup_sockets:
17:03:54.000 xrdp-sesman[953]: 6 xrdp-sesman[953]: [INFO ] xrdp channel server for display 13 (pid 957) exit code 0 and signal number 0
17:03:54.000 xrdp-sesman[953]: 6 xrdp-sesman[953]: [INFO ] X server on display 13 (pid 955) returned exit code 1 and signal number 0
17:03:54.000 xrdp-sesman[953]: 6 xrdp-sesman[953]: [INFO ] Terminating the xrdp channel server (pid 957) on display 13
17:03:54.000 xrdp-sesman[953]: 6 xrdp-sesman[953]: [INFO ] Terminating X server (pid 955) on display 13
17:03:54.000 xrdp-sesman[953]: 6 xrdp-sesman[953]: [INFO ] Calling auth_stop_session and auth_end from pid 953
17:03:54.000 xrdp-sesman[953]: 4 xrdp-sesman[953]: [WARN ] Window manager (pid 954, display 13) exited quickly (0 secs). This could indicate a window manager config problem
17:03:54.000 kernel: 6 kernel: Feb 4 17:03:54 <daemon.err> freebsd xrdp-sesman[954]: [ERROR] A fatal error has occurred attempting to start the window manager on display 13, aborting connection
17:03:54.000 xrdp-sesman[954]: 3 xrdp-sesman[954]: [ERROR] A fatal error has occurred attempting to start the window manager on display 13, aborting connection
17:03:54.000 kernel: 6 kernel: Feb 4 17:03:54 <daemon.err> freebsd xrdp-sesman[954]: [ERROR] There is no X server active on display 13
17:03:54.000 xrdp-sesman[954]: 3 xrdp-sesman[954]: [ERROR] There is no X server active on display 13
17:03:54.000 xrdp-sesman[954]: 4 xrdp-sesman[954]: [WARN ] Timed out waiting for X server on display 13 to startup
17:03:54.000 xrdp-sesman[953]: 6 xrdp-sesman[953]: [INFO ] Session in progress on display 13, waiting until the window manager (pid 954) exits to end the session
17:03:54.000 xrdp-sesman[957]: 6 xrdp-sesman[957]: [INFO ] Starting the xrdp channel server for display 13
17:03:54.000 xrdp-sesman[953]: 6 xrdp-sesman[953]: [INFO ] Session started successfully for user louis on display 13
17:03:54.000 xrdp-sesman[953]: 4 xrdp-sesman[953]: [WARN ] Timed out waiting for X server on display 13 to startup

>> see the difference above compaired to the trace in the next post <<

17:03:43.000 xrdp-sesman[955]: 6 xrdp-sesman[955]: [INFO ] Starting X server on display 13: /usr/local/libexec/Xorg :13 -auth .Xauthority -config xrdp/xorg.conf -noreset -nolisten tcp
17:03:43.000 xrdp[933]: 6 xrdp[933]: [INFO ] lib_mod_connect: connecting via UNIX socket
17:03:43.000 xrdp[933]: 6 xrdp[933]: [INFO ] started connecting
17:03:43.000 xrdp[933]: 6 xrdp[933]: [INFO ] loaded module 'libxup.so' ok, interface size 10296, version 4
17:03:43.000 kernel: 6 kernel: Feb 4 17:03:43 <daemon.err> freebsd xrdp-sesman[807]: [ERROR] sesman_main_loop: trans_check_wait_objs failed, removing trans
17:03:43.000 xrdp-sesman[807]: 3 xrdp-sesman[807]: [ERROR] sesman_main_loop: trans_check_wait_objs failed, removing trans
17:03:43.000 xrdp-sesman[952]: 6 xrdp-sesman[952]: [INFO ] PAM: Last login: Sun Feb 4 16:57:17 on :13
17:03:43.000 xrdp[933]: 6 xrdp[933]: [INFO ] login successful for user louis on display 13
17:03:43.000 xrdp[933]: 6 xrdp[933]: [INFO ] xrdp_wm_log_msg: login successful for user louis on display 13
17:03:43.000 kernel: 6 kernel: Feb 4 17:03:43 <daemon.err> freebsd xrdp-sesman[807]: [ERROR] sesman_data_in: scp_process_msg failed
17:03:43.000 xrdp-sesman[807]: 3 xrdp-sesman[807]: [ERROR] sesman_data_in: scp_process_msg failed
17:03:43.000 xrdp-sesman[952]: 6 xrdp-sesman[952]: [INFO ] [session start] (display 13): calling auth_start_session from pid 952
17:03:43.000 xrdp-sesman[807]: 6 xrdp-sesman[807]: [INFO ] Starting session: session_pid 952, display :13.0, width 1920, height 1080, bpp 24, client ip 192.168.17.34:3211 - socket: 12, user name louis
17:03:43.000 xrdp-sesman[807]: 6 xrdp-sesman[807]: [INFO ] Found X server running at /tmp/.X12-lock
17:03:43.000 xrdp-sesman[807]: 6 xrdp-sesman[807]: [INFO ] Found X server running at /tmp/.X11-lock
17:03:43.000 xrdp-sesman[807]: 6 xrdp-sesman[807]: [INFO ] Found X server running at /tmp/.X10-lock
17:03:43.000 xrdp-sesman[807]: 6 xrdp-sesman[807]: [INFO ] starting Xorg session...
17:03:43.000 xrdp-sesman[807]: 6 xrdp-sesman[807]: [INFO ] ++ created session (access granted): username louis, ip 192.168.17.34:3211 - socket: 12
17:03:43.000 xrdp-sesman[807]: 6 xrdp-sesman[807]: [INFO ] Terminal Server Users group is disabled, allowing authentication
17:03:43.000 xrdp[933]: 6 xrdp[933]: [INFO ] sending login info to session manager. Please wait...
17:03:43.000 xrdp[933]: 6 xrdp[933]: [INFO ] sesman connect ok
17:03:43.000 xrdp[933]: 6 xrdp[933]: [INFO ] xrdp_wm_log_msg: sesman connect ok
17:03:43.000 xrdp-sesman[807]: 6 xrdp-sesman[807]: [INFO ] Socket 12: AF_INET6 connection received from ::1 port 34449
17:03:43.000 xrdp[933]: 6 xrdp[933]: [INFO ] connecting to sesman on 127.0.0.1:3350
 
Here the first part of the logging related to a root rdp session

18:38:45.000 xrdp-chansrv[1103]: 6 xrdp-chansrv[1103]: [INFO ] Socket 12: AF_UNIX connection received
18:38:45.000 xrdp-sesman[1098]: 6 xrdp-sesman[1098]: [INFO ] Starting window manager on display 13 from user home directory: /root/startwm.sh
18:38:45.000 xrdp-sesman[1097]: 6 xrdp-sesman[1097]: [INFO ] Session in progress on display 13, waiting until the window manager (pid 1098) exits to end the session
18:38:45.000 xrdp-sesman[1098]: 6 xrdp-sesman[1098]: [INFO ] Found X server running at /tmp/.X11-unix/X13
18:38:45.000 xrdp-sesman[1103]: 6 xrdp-sesman[1103]: [INFO ] Starting the xrdp channel server for display 13
18:38:45.000 xrdp-sesman[1097]: 6 xrdp-sesman[1097]: [INFO ] Session started successfully for user root on display 13
18:38:45.000 xrdp-sesman[1098]: 6 xrdp-sesman[1098]: [INFO ] Found X server running at /tmp/.X11-unix/X13
18:38:45.000 xrdp-sesman[1097]: 6 xrdp-sesman[1097]: [INFO ] Found X server running at /tmp/.X11-unix/X13
18:38:45.000 xrdp[1018]: 6 xrdp[1018]: [INFO ] connected ok
18:38:45.000 xrdp[1018]: 6 xrdp[1018]: [INFO ] lib_mod_log_peer: xrdp_pid=1018 connected to X11rdp_pid=0 X11rdp_uid=7125 X11rdp_gid=0 client_ip=192.168.17.34 client_port=3667

>>> first part / part below more or less the same for root as the normal user(still a lot of verdict errors); but now above (for root) the session continues <<<
(with less important(?) errors to be solved later)

18:38:45.000 xrdp-sesman[1099]: 6 xrdp-sesman[1099]: [INFO ] Starting X server on display 13: /usr/local/libexec/Xorg :13 -auth .Xauthority -config xrdp/xorg.conf -noreset -nolisten tcp
18:38:45.000 xrdp[1018]: 6 xrdp[1018]: [INFO ] lib_mod_connect: connecting via UNIX socket
18:38:45.000 xrdp[1018]: 6 xrdp[1018]: [INFO ] started connecting
18:38:45.000 xrdp[1018]: 6 xrdp[1018]: [INFO ] loaded module 'libxup.so' ok, interface size 10296, version 4
18:38:45.000 kernel: 6 kernel: Feb 4 18:38:45 <daemon.err> freebsd xrdp-sesman[807]: [ERROR] sesman_main_loop: trans_check_wait_objs failed, removing trans
18:38:45.000 xrdp-sesman[807]: 3 xrdp-sesman[807]: [ERROR] sesman_main_loop: trans_check_wait_objs failed, removing trans
18:38:45.000 xrdp-sesman[1096]: 6 xrdp-sesman[1096]: [INFO ] PAM: Last login: Sun Feb 4 17:30:32 from 192.168.17.34
18:38:45.000 xrdp[1018]: 6 xrdp[1018]: [INFO ] login successful for user root on display 13
18:38:45.000 xrdp[1018]: 6 xrdp[1018]: [INFO ] xrdp_wm_log_msg: login successful for user root on display 13
18:38:45.000 kernel: 6 kernel: Feb 4 18:38:45 <daemon.err> freebsd xrdp-sesman[807]: [ERROR] sesman_data_in: scp_process_msg failed
18:38:45.000 xrdp-sesman[807]: 3 xrdp-sesman[807]: [ERROR] sesman_data_in: scp_process_msg failed
18:38:45.000 xrdp-sesman[1096]: 6 xrdp-sesman[1096]: [INFO ] [session start] (display 13): calling auth_start_session from pid 1096
18:38:45.000 xrdp-sesman[807]: 6 xrdp-sesman[807]: [INFO ] Starting session: session_pid 1096, display :13.0, width 1920, height 1080, bpp 24, client ip 192.168.17.34:3667 - socket: 12, user name root
18:38:45.000 xrdp-sesman[807]: 6 xrdp-sesman[807]: [INFO ] Found X server running at /tmp/.X12-lock
18:38:45.000 xrdp-sesman[807]: 6 xrdp-sesman[807]: [INFO ] Found X server running at /tmp/.X11-lock
18:38:45.000 xrdp-sesman[807]: 6 xrdp-sesman[807]: [INFO ] Found X server running at /tmp/.X10-lock
18:38:45.000 xrdp-sesman[807]: 6 xrdp-sesman[807]: [INFO ] starting Xorg session...
18:38:45.000 xrdp-sesman[807]: 6 xrdp-sesman[807]: [INFO ] ++ created session (access granted): username root, ip 192.168.17.34:3667 - socket: 12
18:38:45.000 xrdp-sesman[807]: 6 xrdp-sesman[807]: [INFO ] Terminal Server Users group is disabled, allowing authentication
18:38:45.000 xrdp[1018]: 6 xrdp[1018]: [INFO ] sending login info to session manager. Please wait...
18:38:45.000 xrdp[1018]: 6 xrdp[1018]: [INFO ] sesman connect ok
18:38:45.000 xrdp[1018]: 6 xrdp[1018]: [INFO ] xrdp_wm_log_msg: sesman connect ok
18:38:45.000 xrdp-sesman[807]: 6 xrdp-sesman[807]: [INFO ] Socket 12: AF_INET6 connection received from ::1 port 30193
18:38:45.000 xrdp[1018]: 6 xrdp[1018]: [INFO ] connecting to sesman on 127.0.0.1:3350
 
derekschrock said:
Do you have xorgxrdp installed?
Click to expand...
Yep, has been automaticly installed I assume

xorg-7.7_3 X.Org complete distribution metaport
xorg-apps-7.7_4 X.org apps meta-port
xorg-docs-1.7.2,1 X.org documentation files
xorg-drivers-7.7_7 X.org drivers meta-port
xorg-fonts-7.7_1 X.org fonts meta-port
xorg-fonts-100dpi-7.7 X.Org 100dpi bitmap fonts
xorg-fonts-75dpi-7.7 X.Org 75dpi bitmap fonts
xorg-fonts-cyrillic-7.7 X.Org Cyrillic bitmap fonts
xorg-fonts-miscbitmaps-7.7 X.Org miscellaneous bitmap fonts
xorg-fonts-truetype-7.7_1 X.Org TrueType fonts
xorg-fonts-type1-7.7 X.Org Type1 fonts
xorg-libraries-7.7_5 X.org libraries meta-port
xorg-server-21.1.11_1,1 X.Org X server and related programs
xorgproto-2023.2 X Window System unified protocol definitions
xorgxrdp-0.9.19_3 X.Org driver enabling use through an RDP session with xrdp

Also note that root rdp stopped a few minutes after session start (the session was not used), with the following message
18:43:49.000 kernel: 6 kernel: Feb 4 18:43:49 <daemon.crit> freebsd gnome-session-binary[1098]: GLib-GIO-CRITICAL: g_dbus_proxy_call_sync_internal: assertion 'G_IS_DBUS_PROXY (proxy)' failed

I had to restart the VM, to make things working again
 
I did open a separate tread explicitly related to my verdict that ^xrdp-sesman^ has insufficient rights to start an x-server if user <> "root"
 
I log on FreeBSD (with xrdp and xrdp_sesman installed and running) and login with remote desktop on Windows (11Pro) but...
  • the FreeBSD server doesn't start an Xorg session
  • I use XFCE
In ${HOME}/startwm.sh it's recommended to start XFCE as:
Code: 
exec startxfce4
this doesn't work, I get an XFCE error (cannot start config or something like this). To get XFCE start I have to change the exec in:
Code: 
exec xterm -e startxfce4
The xterm will launch XFCE and it will be stay in DE (I push it on workspace 4 and forget it). I guess GNOME too will starts with
Code: 
exec xterm -e gnome-session
the only one that runs is
Code: 
exec twm
 
The normal startup method should work and if ^user = root^ it does, however it does not.
So I gave your idea "exec xterm -e gnome-session" a try.

It did not work
 
Did you try another desktop environment (DE) to narrow down if is the DE or something on the XRDP/xorg side? I am using XRDP with Mate and xfce4 all the time without issues.
 
No I did not. In fact I am loosing much to much time which things "which should work instantly" but do not (in general not only related to freebsd).
What ever, I will update the VM shortly and hope .... that that solves the problem
 
Louis said:
No I did not. In fact I am loosing much to much time which things "which should work instantly" but do not (in general not only related to freebsd).
What ever, I will update the VM shortly and hope .... that that solves the problem
Click to expand...
I do not like to waste my time trying to help people that don't really look for answers and show no intent to learn
/thread
 
I think that remartk is far for correct!

As you can see here and also with other issues, I am spendings seas of time trying to understand and solve problems.

But since it is costing me many(!), many(!) days, you should not be surprised that I become frustrated and sometimes stop investing a problem like this one in which I have spend day's for something which should have worked instandly!
 
You must log in or register to reply here.
Back
Top