The script hereafter is outdated and has been replaced by a newer version. Please Check the Download page for latest version.
|
Hello World,
In our previous post, we have mentioned a bunch of issues that have been encountered when using the xrdp-installer script (ver. 1.4.5). Since the issues detected are quite significative, we have decided to release (quick and dirty) a new version of the script which should tackle the most important issues detected. This script replaces all the previous versions
The new version of the famous xrdp installation script will be set to 1.4.6 (i.e. xrdp-installer-1.4.6.sh). Version 1.4.6 should be seen as an emergency release in order to quickly fix the detected issues. We will need to perform some additional tests to validate the script and then mark it as stable
So, let’s go !
Overview
By now, you should know that the xrdp-installer script aim to ease installation and post-configuration actions of xRDP on top of Ubuntu Operating system. xRDP is a piece of software that enable remote desktop services on Linux. This means that windows users can use their Remote desktop client (mstsc) and perform a remote connection to Ubuntu Computer.
Initially, the script was supporting only Ubuntu with Gnome Desktop interface. However, recent version of script tries to detect the Desktop interface in use and try to perform the post-configuration actions as required. Recent version of the script also can run against Debian Operating system as well. Please note that supporting other Flavors is based on a Best effort approach
What’s new in this release (Version 1.4.6) ?
Fixing package conflict between fuse and fuse 3 on Ubuntu 22.10″
As explained in our previous post, Ubuntu 22.10 ships with fuse3 package by default. When performing a custom installation, the script will try to install fuse package. The fuse package conflicts with the newer fuse3 package and some important packages are removed from your Ubuntu machine (such as ubuntu desktop !!). The xrdp-installer-1.4.6 will not try to install fuse package anymore. Instead the libfuse-dev package will be installed when performing a custom installation
Downloading the latest stable xrdp & xorgxrdp package from Github
The xrdp-installer script can perform a standard installation (i.e. using Ubuntu packages from repositories) or a user can decide to run a custom installation from sources files. In the previous versions of the script, when custom mode was selected, the script would download files from the Github dev branch repository. Some users pointed out that they would prefer to use the latest releases versions rather than dev versions on their systems. I think that these users have a point. This is why in version 1.4.6, the script will always try to download the latest release version sources files.
Adding MP3 codecs support in audio redirection
Our famous reader Hiero has also made a small suggestions in order to improve sound redirection. xRDP supports mp3 codecs in audio redirection via LAME encoder. This feature can help reduce network traffic and improve sound quality. So, now when we use custom install mode and we compile the xrdp package, we pass the –enable-mp3lame which will include the mp3 support to xRDP software
Click on Picture for better Resolution
We have not fully tested this featue and we still need to see if this improve xRDP sound redirection feature….
Compilation Fails on Debian 11.x (Still under investigation)
Some users have reported that the custom installation was not working on Debian OS. The error was caused by the checkinstall package that is used to compile xrdp and xorgxrdp software solution. We have installed Debian 11.6 and run the script 1.4.6. We have not encountered the issue (so far ?). If you are using Debian OS, if you have time, please give it a try and provide feedback
How to Use the Script
The xrdp-installer-1.4.6 script will work in a similar way as the previous versions. The following section will explain how to download, extract, set executable mode and perform the installation using the script. The script provides some switches that can be used to customize the installation process.
So, let’s see how this would be working….
Disclaimer
Prerequisites and assumptions
The following conditions should be met in order to have the best results while using the script
- We assume that your machine is connected to internet while performing the installation. This is needed as additional packages and software needs to be downloaded and installed on your Ubuntu machine
Script version & Supported Ubuntu Version
The xrdp-installer-1.4.6.sh script will support the following Ubuntu operating system version assuming that Gnome Desktop is the default Desktop interface
- Ubuntu 18.04.x
- Ubuntu 20.04.x
- Ubuntu 22.04.x
- Ubuntu 22.10.x
- Debian 10
- Debian 11 (only if you select custom mode installation !!!)
The xrdp-installer-1.4.6.sh script can be run against the following Ubuntu flavors but we cannot guarantee that everything will work as expected (best effort)
- Kubuntu (20.04 and later)
- Ubuntu Budgie (20.04 and later)
- Ubuntu Mate (20.04 and later)
- Xubuntu (20.04 and later)
- Lubuntu (20.04 and later)
- Linux Mint (Experimental at this stage)
- Pop!_OS 22.04
Note : If you are running any of these distributions and you want to help us improving the support on those, please download and test the script. Do no hesitate to share your findings so we can try to incorporate them in the next release
Step 1 – Download the script
To download the script, you have multiple options. You can from a Terminal issue the following command
wget https://www.c-nergy.be/downloads/xRDP/xrdp-installer-1.4.6.zip
You can also simply use your browser and click on the link to download the script :
Step 2 – unzip the file
After downloading the zip package containing the file, you will need to unzip it first. To unzip the package, you can use the Terminal console and issue the following command
unzip xrdp-installer-1.4.6.zip
You can also use the GUI and the Nautilus file manager to select the downloaded package, right-click on it and select the option Extract Here
Step 2 – Set Execute Right on the script
Download the xrdp-installer-1.4.6.sh script to your system, extract content and mark it as executable . To do this, perform the following action in a terminal console
chmod +x ~/Downloads/xrdp-installer-1.4.6.sh
Note : Adjust the path where the xrdp-Installer-1.4.6.sh script to reflect your environment
Step 2 – Run as normal user
The script needs to be run as a normal user. The script will start running and will prompt you for password when sudo actions are initiated. If you run the script as root or using sudo command, the Download folder does not exist for the root user and the script fails to run as expected. To overcome this situation, the script also check which user is executing the script. If the script is run under sudo or root accounts, a warning message will be displayed and the script will not execute
Step 3 – Switches and parameters
The xrdp-installer-1.4.6.sh script can be executed as is (with no parameters or switches). This will perform a standard (and basic) installation of xRDP. No sound or custom xrdp login script will be made available. However, remote desktop, drive redirection and clipboard redirection would be available with this installation mode.
The xrdp-installer-1.4.6.sh script accept also some additional parameters that will help customize the xrdp installation and enable additional features. The script provides the following parameters
--help or -h => will display a basic help menu --sound or -s => will enable sound redirection --loginscreen or -l => will customize the xRDP login screen --remove or -r => will remove the xrdp package --custom or -c => will perform a custom installation (i.e. compiled from sources)
Step 4 – Perform xRDP installation using the script
The following sections will provide some examples and scenario on how you can use the script…..
Standard Installation – No Parameter
As mentioned above, you can decide to use the default xrdp package available in the Ubuntu repository and perform a basic installation which will provide you remote desktop capability and will also customize the remote sesssion. The script will ensure that the same look n’ feel will be maintained when the user logs on locally or remotely.
To perform a standard installation, you execute the script with no parameters. Open a Terminal console, browse to the location where the script has been downloaded and issue the following command
./xrdp-installer-1.4.6.sh
When the xrdp installation package will start, you be requested to enter your password. Provide the password and proceed with the installation. Wait for completion of the script. The machine will not reboot automatically when done so you can review the actions performed by the script….
Standard Installation with Parameters
The script can be used to perform a standard installation and still passes some parameters to get the most of the xRDP packages and their features. For all the Ubuntu versions, we could use the following combination of parameters
./xrdp-installer-1.4.6.sh -s (this would enable the sound redirection) ./xrdp-installer-1.4.6.sh -l (this would customize the xrdp login screen -see here)
Obviously, you can combine the switches (any order) to have more features enabled
./xrdp-installer-1.4.6.sh -s -l (this would enable the sound redirection and customize the xrdp login screen)
Important Notes
The script can be run multiple times on the same machine. If you have run initially the script with no parameters but you decide afterward to enable additional features, the script can be re-executed and the additional features will be enabled.
Custom Installation – Default Installation
Custom installation script is really flexible. Custom installation means that the script will compile the xrdp package from the source binaries. The custom installation script always uses the latest xrdp package version available
To perform a custom installation, you will need at minimum to pass one parameter. The following command line shows you how to perform a custom installation
./xrdp-installer-1.4.6.sh -c (this would perform a custom installation but will not enabled adv features like sound redirection or custom login screen)
Custom Installation – Additional Options
If a user wants to enable additional features, you will pass some additional parameters as shown in the following examples
./xrdp-installer-1.4.6.sh -c -s (this would perform a custom install and enable sound redirection) ./xrdp-installer-1.4.6.sh -c -l (this would perform a custom install and customize xrdp login screen) ./xrdp-installer-1.4.6.sh -c -l -s (this would perform a custom install, enable sound and customize login screen)
Important Notes
The script can be run multiple times on the same machine. If you have run initially the script with no parameters but you decide afterward to enable additional features, the script can be re-executed and the additional features will be enabled.
Remove Installation option
This version of the script also ship with the option to remove xRDP package. The removal option should be only used if you have uses this version of this script to perform the installation. To remove the xrdp package, you would simply execute the following command
./xrdp-installer-1.4.6.sh -r (to remove the xrdp packages)
Step 5 – Test your configuration
After the script has run and after the reboot/shutdown and start process, it’s time to test and see if you can indeed perform a smooth remote connection to your Ubuntu machine. Start your favorite rdp client and simply enter your credentials and start testing your installation. If everything is ok, you will see a similar Desktop interface where Gnome Desktop is used and the Dock is visible.
Limitations
Switch between standard and Custom install
This version of the script can be run multiple times on the same machine. However, because of this new behavior, you cannot perform a standard installation and then decide to perform the custom installation. Once you have selected your installation mode, you will have to stick to it. This is kind of checked by the script.
So, if you have performed a standard installation but afterwards you might want to use the custom installation option, the script will ignore the request. If you want to move from standard install mode to custom mode (or vice versa), the correct process is
- remove xrdp (using the xrdp-installer-1.4.6.sh -r option)
- perform a new installation using your selected installation mode (standard or custom install mode)
Known issues, Fixed Issues and limitations
Known Issues
Black Screen or disconnected immediately after connecting
As mentioned and explained multiple times, this situation will happen (or can happen) when the same user account is used concurrently locally and remotely. In other words, the problem is related to the fact that the same user account is already logged in locally and a remote connection is attempted at the same time. With xRDP software solution, a specific user account can be logged on either locally or remotely but not both….
In the past, we have provided some workarounds that could be used to allow multiple connections for the same user. However, in Ubuntu 22.04, we have encountered some additional issues and again we strongly recommend not using these workarounds…..
Some workarounds (provided as is) to try to fix the issues are available. We do not recommend to use them ! Use at your own risk !!!
Final Notes
This is it for this post !
The script version has not been tested extensively because we needed to fix quite quickly the discovered issues. The script should be seen as an emergency release in order to maintain usability. Please if you have time or want to help us in creating the best xRDP installer script, download the script, test it and provide constructive feedback. If you find a bug or an issue with the script, let us know as well so we can try to fix it.
Last but not least ! Special Thanks to Hiero who discovered and shared the information with you… Really appreciated 🙂
Till next time
See ya
su
Hi
Thank you for your efforts, just installed it on Ubuntu 22.04.1 LTS and works like a charm.
One small issue for me, I cannot open nautilus or nemo open as admin in the rdp session.
Any solution of workaround for this please if you can suggest.
Regards
@Patel,
Thank you for visiting our blog and providing feedback. In the past, some workarounds exists to still open the gui interface within xRDP. Nowadays, it seems that newer version of gnome is not allowing this anymore… A possibility might be to disable the Polkit feature… We will need to look into this but we are a little bit short in time for blogging at the moment… So please be patient if you want us to come up with a possible workaround
Hope this help
Till next time
See ya
Hi,
In my case after the successful installation on Ubuntu 22.04.1 LTS having the parameter -s , and following the procedure
I shut down the VM, Started it again, but then-No login screen, and no booting. I kept a snapshot for having this case available for any future reference.
Any solution or workaround for this please if you can suggest.
Regards
Hello, is it possible to install enable sound redirection before installing the script? installation and before the setup has already been done and the system is in use, I don’t want to break it, but the sound was needed
@Antonio,
Thank you for visiting our blog and providing feedback… We are checking this specific issue on our lab. Give us some time to check…if possible, can you retry but then save all the output information that will be shown in the Terminal console. This can help us and finding the issue… So, maybe there is again a conflicting package…During the installation, the output might show removal of some packageS…
Please be patient while we are investigating…we will come back to you asap
Update : we have performed some tests in our lab. Fresh install of Ubuntu 22.04.1 and xrdp was working even after a reboot…Cannot reproduce your error…
Hope this help
Till next time
See ya
@Igor,
Thank you for visiting our blog and providing feedback.. Not sure we understand fully your question but we will try
So, if you have already installed xrdp package on your system and you want to enable sound, you have the following options
you can try to use the script provided by xrdp maintainer team (detailed info can be found here) => This would be our recommendation
You can try to use our little script with the -s parameter but you will need to create the file /etc/xrdp/xrdp-installer-check.log. In the file, you have to write either Standard or Custom value. Doing this should prevent the script to run the xrdp installation steps and will jump directly to the sound redirection section and perform the installation (use this at your own risk !!!)
We will try to make the script even more flexible to take this request into account
Hope this help
Till next time
See ya
@Patel,
HEllo Patel, so we have checked the issue about nautilus and sudo right in xrdp session… To have it running under Ubuntu 22.04, you can use the following command
To allow to run Nautilus as root, you issue the following command in a terminal session
xhost si:localuser:root
sudo nautilus
To Restore the default permissions, issue the following command
xhost -si:localuser:root
However, using this tip fails on Ubuntu 22.10…seems to be a problem with the gnome version….we will keep investigating
Hope this help
We might write a post about that
Till next time
See ya
Hi – I use KDE on Kubuntu 22.04.1. You mention that Kubuntu is supported.
In that case will the script install KDE Plasma desktop instead of Gnome?
Tks
@Richard,
Thank you for visiting our blog and providing feedback… The script does not install any Desktop interface. The script will try to detect the one you are using… if the Desktop interface is detected correctly, the script will simply check if there is a need to create an additional file to let know xRDP software that Kubuntu and thus KDE Interface is in use
Hope this answer your question
Till next time
See ya
I installed ubuntu 22.10 on my proxmox, then setup ssh server and that was tested and working. then ran this script, got rdp working with my mac client, but now I can’t ssh from my mac anymore. I also can’t copy paste from mac to ubuntu, so it is pretty unusable. copy paste works for login and other password popups in the the desktop but not in shell. very strange. and no sound, but I saw your post about that, but won’t bother trying to get sound until I get copy paste and ssh access sorted out
ssh to ubuntu 22.10 stopped working after installing this.
I figured it out. have ssh remote access setup and working before (turned on in prefs) if you want that, and turn off remote desktop in prefs. It was turned on there, which is why I couldn’t get the script to work.
Hi!
Anybody have a experience with old lubuntu 18.04.6 LTE?
Script 1.2.1 not working properly with sound redirection.
Thank You.
@Kurt,
Thank you for visiting our blog and providing feedback… Quick question, have you tried to run the xrdp-installer-1.4.6 version against the Ubuntu 18.04.6…? The version 1.4.6 still provide support to Ubuntu 18.04.x. When you say, problem with sound redirection, can you provide a little bit more information ? Do you see the xrdp sink objects ? do you have sound ? have you rebooted the server before tryin the sound redirection,? have you tried the old trick pulseaudio -k ?
We have tested a few weeks ago the script against Ubuntu 18.0.4.6 with sound and we didn’t encountered specific issues
Waiting for your feedback
Till next time
Awesome work, thanks a lot!
Your installer script works flawlessly as ever, I just noticed an issue with this release.
In my environment I’m using Ubuntu 20.04.5 LTS on Hyper-V in Enhanced Session (HvSocket) mode. When xrdp sound redirection is enabled the touchpad and mouse starts to be freezing/lagging (movement only gets picked up after several seconds but it would freeze again after a short idle period). This impacts the complete entire host, not just the VM. Audio playback does not have to be active to trigger the issue, but I think it had to be active previously in order to have certain conditions set on the host.
As mentioned, I first observed the issue when I upgraded to 1.46 (skipped 1.45), it never occurred to me in releases 1.44 or lower. Not sure if this is related to MP3 audio support introduced in this release, as compiling from sources fails for me (libtoolize places ltmain.sh in the wrong location … still need to figure out why).
Thank you
@griffon
Thanks for the update.
I will be eagerly awaiting update for 22.10 before updating to 22.10 branch :-))
unfortunately the workaround is not working and produces error on terminal as below while opening nautilus with only the user desktop folder visible
(org.gnome.Nautilus:16230): libunity-CRITICAL **: 13:58:14.435: file unity-launcher.c: line 1638: unexpected error: Failed to execute child process “dbus-launch” (No such file or directory) (g-exec-error-quark, 8)
(org.gnome.Nautilus:16230): libunity-CRITICAL **: 13:58:14.435: unity_launcher_entry_dbus_impl_construct: assertion ‘conn != NULL’ failed
(org.gnome.Nautilus:16230): libunity-CRITICAL **: 13:58:14.438: unity-inspector.vala:96: Unable to connect to session bus: Failed to execute child process “dbus-launch” (No such file or directory)
(org.gnome.Nautilus:16230): dconf-WARNING **: 13:58:14.552: failed to commit changes to dconf: Failed to execute child process “dbus-launch” (No such file or directory)
(org.gnome.Nautilus:16230): dconf-WARNING **: 13:58:14.552: failed to commit changes to dconf: Failed to execute child process “dbus-launch” (No such file or directory)
** (org.gnome.Nautilus:16230): WARNING **: 13:58:14.603: Unable to get contents of the bookmarks file: Error opening file /root/.gtk-bookmarks: No such file or directory
** (org.gnome.Nautilus:16230): WARNING **: 13:58:14.616: Unable to get contents of the bookmarks file: Error opening file /root/.gtk-bookmarks: No such file or directory
** (org.gnome.Nautilus:16230): CRITICAL **: 13:58:14.673: update_dbus_opened_locations: assertion ‘dbus_object_path’ failed
(org.gnome.Nautilus:16230): dconf-WARNING **: 13:58:14.673: failed to commit changes to dconf: Failed to execute child process “dbus-launch” (No such file or directory)
Nautilus-Share-Message: 13:58:14.707: Called “net usershare info” but it failed: Failed to execute child process “net” (No such file or directory)
(org.gnome.Nautilus:16230): dconf-WARNING **: 13:58:17.367: failed to commit changes to dconf: Failed to execute child process “dbus-launch” (No such file or directory)
(org.gnome.Nautilus:16230): dconf-WARNING **: 13:58:17.367: failed to commit changes to dconf: Failed to execute child process “dbus-launch” (No such file or directory)
** (org.gnome.Nautilus:16230): CRITICAL **: 13:58:17.381: update_dbus_opened_locations: assertion ‘dbus_object_path’ failed
(org.gnome.Nautilus:16230): GLib-GIO-CRITICAL **: 13:58:17.415: g_dbus_proxy_new_sync: assertion ‘G_IS_DBUS_CONNECTION (connection)’ failed
(org.gnome.Nautilus:16230): GLib-GIO-CRITICAL **: 13:58:17.415: g_dbus_proxy_call_internal: assertion ‘G_IS_DBUS_PROXY (proxy)’ failed
@Buzz,
Thank you for visiting our blog and providing feedback. Ok; this is the first time we hear such issue. We have run the script on VMS hosted on Hyper-v server and we didn’t really got an issue. We are using standard Keyboard and Mouse. no touchpad. The fact that it affect the host as well seems strange and the audio redirection feature should not really matter. But as you said, might be caused by the MP3 audio support when compiling. To validate this assumption, I would try to perform installation again but I would remove the Mp3 audio support within the script…. If you go to line 606, you can see the option –enable-mp3lame…. remove it and try again to see if you get better results or if this is something else
Hope this help
Till next time
See ya
Hello Patel,
Thank you for visiting our blog and providing some feedback…. We have looked into this issue…we are also finishing a short post about this scenario…. What we have found is that the issue only exists on Ubuntu 22.10. Previous versions will support the workaround.. Looking at the logs and output from the console, it seems that this is a problem with latest GNome Desktop software…. We have installed another File Manager and it works…. So Gnome is definitely the problem
Hope this help
Till next time
See ya
Hi,
Accessing the Ubuntu host from a Thin-client (Dell Wyse – ThinOS 8) through RDP , the sound format is not supported.
How can I try other formats ?
@Lolix,
Thank you for visiting our blog and providing feedback. I have no clue about supported formats and how to test others… will need to dig a little bit on this topic
We will try to have a look but no guarantee as we are really overloaded at the moment
till next time
See ya
Hi ,Thanks for your reply.
I asked also in the xrdp Git Discussions area. Not sure if it’s duplicate from here…
BTW, the script fetched xrdp 0.9.17 not the latest (currently 0.9.21).
Ran the script first to clean up any mess I had made, after re running the script it still has the same error as before, cannot open /run/xrpd/xrpd.pid ubuntu 22.04
Hello Fahza,
Sorry for the late reaction..but we are a little bit overloaded. Can you provide more information about your problem.. This can be a generic error or a simple warning… Can you perform a remote desktop session yes or no. . can you share the logs /var/log/xrdp-sesman.log and /var/log/xrdp.log … have you rebooted the machine ?
are you using the Sharing desktop as well or not … if yes; this conflict with xrdp
waiting for your feedback
Till next time
See ya
All the following refers to an Ubuntu 20.04 LTS (no exotic stuff, all updates installed, kernel 6.2.12) VM with xrdp script v1.2.3 installed on Win10P / Hyper-V (local), in daily use with RDP (works as a charm). I tried to upgrade this VM to 22.04 LTS. This is not possible via xRDP (don’t know why), so I processed the upgrade using “native” (“simple session”) access. Upgrade to 22.04 went thru. Cleaned up some PPA entries directing to focal / bionic. Still in “simple session” mode, I installed script 1.4.6 with parameters -c -s -l (I want it all…). No problems were reported, but when I connect to the VM, no “extended session” is offered anymore by the RDP client: The menu option is greyed out; only “simple session” mode is possible. (“Extended session” mode is generally allowed in the Hyper-V overall setup of course.) — What did I miss? Seems like no one listens to the RDP port or something like this. Do you have any idea how to do it better or fix it? (Both a fix to the resulting 22.04 or start over again from 20.04 would be possible.) — Thanks for any clue!
@ZipWiZ,
Thank you for visiting our blog and providing some feedback. So the xrdp script does not take into account Hyper-V Enhanced session by default. You can use the script to perform your xRDP installation but then you would need to perform some additional configuration steps (if using Hyper-v and you want to use Enhanced mode). You can find all the detailed information in this post (https://c-nergy.be/blog/?p=17109)
Give it a try and let us know if this was helpful
Till next time
See ya
@Griffon
That does not work: I checked the recommended Hyper-V “extended mode” page and made all recommended changes (Ubuntu: “port” (was vsock already, but not yet tcp also) and “security_layer” (was rdp already) — however “crypt_level” was set to “none” (and “high” in a 2nd try) -> Hyper-V: HvSocket (not checked before, but should have been already set so). Start of the VM did not offer any change: Still no “extended mode” available. What can I do else?
@ZipwiZ,
we have just tried the instructions on Hyper-V on Win Server 2022 and followed the instructions against UBuntu 22.10… This is working for us…. Can you provide the content of your xrdp.ini file ? (at least the section to be configured) | fl *Enhanc*
Can you provide also the output of the get-vm
Have you checked enhanced mode (in hyper-v settings) in both location…. enable the feature and allow if possible
When you restart your machine, is the Hyper-V popup asking you to connect via rdp showing up or you go straight to the VM ?
waiting for some feedback
Till next time
See ya
I have updated to 23.04 and was pleased to see that both enhanced session and sound redirection still work.
Surely we can edit the script now to include 23.04 and this should also work…
@James,
Thank you for visiting our blog and providing some feedback. We will release the version 1.4.7 of the xrdp-installer script in order to support Ubuntu 23.04. I do not know you get the sound redirection working since UBuntu 23.04 is using PipeWire while the script is looking specifically with pulseaudio. Finally, about the enhanced mode, we would assume that you have performed a standard installation otherwise it would not have worked (as far as we know). So, for standard installation, indeed editing the script to add support for Ubuntu 23.04 could be enough but for a custom installation there is more to check
Till next time
See ya
hello does this script support arm64 architecture equipment?
@Antonio,
Thank you for visiting our blog and providing feedback. The script is checking Operating system version rather that CPU architecture. xRDP software supports arm technology since the software can be installed on Raspberry pi. Raspberry is not supported by the script (yet). So, we would say, run the script in a lab (and/or VM) and see if this could work
Hope this help
Till next time
See ya
Any timeframe when you will release 1.4.7? I am running Ubuntu 23.04. Want someone to test it?
@Charlie,
Thank you for visiting our blog and providing some feedback. Version 1.4.7 is out since May 2, 2023… You can find the script by checking this post (see https://c-nergy.be/blog/?p=18918). We didn’t change yet the product page because we had a lot of issues with Ubuntu 23.04 from installation to usability. It starts to get better but we are not sure we will invest a lot of time with this release. There are still some problems when trying to use Ubuntu 23.04 as an Hyper-V virtual machine
Till next time
See ya