[XOA] Problem with AltGr and space bar while installing a VM
-
olivierlambert said in [XOA] Problem with AltGr and space bar while installing a VM:
Yes we will (and we did!) See https://xen-orchestra.com/blog/devblog-3-working-on-xo-6/
It's a BIG rework because we'll change the ENTIRE system, from the API to the UI, and various mechanisms.
I remember reading it. It would be nice with a progress update
-
Hello Everyone,
Is XO6 available ?
We are still running a XOA vm (licenced) but we don't use it because of AltGr problem.Regards,
Vincent
-
I suggest you can use XO Lite in the meantime. XO 6 isn't available right now.
-
olivierlambert said in [XOA] Problem with AltGr and space bar while installing a VM:
Okay so it means it's fixed in more recent noVNC versions
XO 6 will get the latest version, and XO Lite is about to be released with minimal "theme" for the end of the month.
We hope to get first XO6 for the end of the year.
First of all, I know I'm posting on an old topic and that's the point.
I built a test environment with XCP-ng last month to get familiar with this solution as a possible replacement for VMWare and stambled on the AltGr issue (french keyboard).
Asking google about it, I found this topic, and this post saying "XO Lite is about to be released" and "first XO6 for the end of the year" from... 2021.
Here we are in 2024 and the deployment I made last month is under XOA 5.92.1, and the home page of XO Lite says "XO Lite is still a beta project. The first release will come very soon."
And the bug about AltGr, acknowledged and solved in the xo lite test in 2021, is still there on the mainstream deployments.Any update on an usable console in the mainstream deployments ?
Using a "hack" with the online version of xo lite, or deploying it manually on each host, and then having to play with different interfaces when you have to manage many hosts simply is a no-go. This bug really is a PITA when you have to use AltGr each time you need a #, a @, a pipe | in a VM console, brackets {[]} in config files, anti-slash \ for networking, etc... -
Sadly, I'm totally agree.
Fews months ago, we planned to move on vmware, and finally, we will not do it.
So, we are still stuck with this altGr thing, so we are using XenCenter's console on each machine with Citrix Hypervisor, and we still pay a XOA licence for only one xcp-ng server (and some backup stuff from XOA)Regards,
-
Squall124 said in [XOA] Problem with AltGr and space bar while installing a VM:
olivierlambert said in [XOA] Problem with AltGr and space bar while installing a VM:
Okay so it means it's fixed in more recent noVNC versions
XO 6 will get the latest version, and XO Lite is about to be released with minimal "theme" for the end of the month.
We hope to get first XO6 for the end of the year.
First of all, I know I'm posting on an old topic and that's the point.
I built a test environment with XCP-ng last month to get familiar with this solution as a possible replacement for VMWare and stambled on the AltGr issue (french keyboard).
Asking google about it, I found this topic, and this post saying "XO Lite is about to be released" and "first XO6 for the end of the year" from... 2021.
Here we are in 2024 and the deployment I made last month is under XOA 5.92.1, and the home page of XO Lite says "XO Lite is still a beta project. The first release will come very soon."
And the bug about AltGr, acknowledged and solved in the xo lite test in 2021, is still there on the mainstream deployments.Any update on an usable console in the mainstream deployments ?
Using a "hack" with the online version of xo lite, or deploying it manually on each host, and then having to play with different interfaces when you have to manage many hosts simply is a no-go. This bug really is a PITA when you have to use AltGr each time you need a #, a @, a pipe | in a VM console, brackets {[]} in config files, anti-slash \ for networking, etc...Poke
-
Hi,
It's not possible to easily upgrade XO 5 with a more recent version of the console, you'll have to wait for XO 6. If you read our blog posts lately, you can see we are doing progress. I'll see if I can get the new consoles sooner than later.
-
Hi,
My colleague was pissed with this bug and while he hitted nervously his keyboard, the bug is gone.
So I searched how he did it, and I found that if you hit simultaneously ctrl and AltGr, the normal keyboard is back.
Just a workaround, but that works.Regards,
Tiki_
-
-
Tiki_ tested and it works, thank you very much for this workaround.
Still, 3 years (and still counting) for fixing this bug is really scary when we think about using this solution in production.
-
Squall124 that's because our priority is about security and many other things that are far more pressing than this. But it's open source you know
Also, we made a choice to stop updating some components in XO 5 because it's too much work while we are designing XO Lite & XO 6 and the new UI.
-
Squall124 While being a bug and I understand it can be a pita but then there's a workaround, I still think you're making a storm in a waterglass by saying "really scary when we think about using this solution in production". Nobody is forcing you to this. We ourselves are more than happy, to say the least, to have made the switch from Vmware (with 2yrs of paid contract in place) to xcp-ng last year!
The level of support and interaction you get, you can only dream about it getting it on the black side (even before the Broadcom debacle), puts up with this smaller nuisances by the ton.Just my 2 cents.
