Hello,

despite reinstalling the console, the problem persists and occurs intermittently, without any specific action on my part.
Have you encountered any other reports of this issue?

Hello,
thanks for the tip.
After making some mistakes, restoring the hosted VM, uninstalling and then reinstalling Python, the upgrade worked, although I'm still getting the same Python error...
Anyway, the migration to version 9450 is OK.

Have a good day.

No, still the same error...
We had no problems during the migration from 1.8 to 2.0.

Thank you for your reply.
However, I absolutely cannot launch Python 3...

root@****wapt:/opt/wapt/bin# python3
Fatal Python error: initfsencoding: Unable to get the locale encoding
ModuleNotFoundError: No module named 'encodings'

Current thread 0x00007f62b4542740 (most recent call first ...

Hello,

Following the publicity regarding the vulnerability and the upgrade to version 2.0.0.9450, I encounter an error message when I launch the upgrade:

The following packages will be upgraded:
aspell krb5-locales krb5-user libaspell15 libgssapi-krb5-2 libgssrpc4 libk5crypto3 libkadm5clnt-mit11 ...

Hello,
Yes, I noticed that the package was in the "conflicts" section and I had modified that setting.
After several modifications and tests, I realized that we had placed a software restriction regarding Microsoft Edge in our GPO.
After removing the...

Hello,

For the past few days I've been encountering an error message while using the WAPT 2.0.0.9428 console.
During navigation, an error suddenly appears:
wapt-Error in application.png

As a result, it's impossible to view the "Tasks" tab

. Tasks-WAPT Console.png

...

I have the same problem whether the repository is the main one or the secondary repositories.
All three secondary repositories we have have an OK status; the package is present on all three repositories, and the package owner is the "wapt" account...

I'm trying to make progress on my issue little by little.
I've tried several times, synchronizing and rebooting the repositories, but the problem persists.

I then tried installing via the self-service interface on the machine, and bingo, it worked without a hitch. So, I'm not...

Any ideas?