Je suis passé en version “Ubuntu 24.04.2 LTS” (le kernel est 6.8.0-60-generic)
Migration :
Les cartes NVIDIA sont toujours visibles :
+-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 575.51.03 Driver Version: 575.51.03 CUDA Version: 12.9 |
|-----------------------------------------+------------------------+----------------------+
| GPU Name Persistence-M | Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap | Memory-Usage | GPU-Util Compute M. |
| | | MIG M. |
|=========================================+========================+======================|
| 0 Quadro M5000 Off | 00000000:00:10.0 Off | Off |
| 39% 44C P8 14W / 150W | 5MiB / 8192MiB | 0% Default |
| | | N/A |
+-----------------------------------------+------------------------+----------------------+
| 1 Quadro M4000 Off | 00000000:00:11.0 Off | N/A |
| 49% 48C P8 14W / 120W | 5MiB / 8192MiB | 0% Default |
| | | N/A |
+-----------------------------------------+------------------------+----------------------+J’ai refait un benchmark :
Avec Python 3.12.3 :
Python 3.12.3 (main, Feb 4 2025, 14:48:35) [GCC 13.3.0]
Version: v1.10.1
Commit hash: 82a973c04367123ae98bd9abdf80d9eda9b910e2
Installing torch and torchvision
Looking in indexes: https://pypi.org/simple, https://download.pytorch.org/whl/cu121
ERROR: Could not find a version that satisfies the requirement torch==2.1.2
(from versions: 2.2.0, 2.2.0+cu121, 2.2.1, 2.2.1+cu121, 2.2.2, 2.2.2+cu121,
2.3.0, 2.3.0+cu121, 2.3.1, 2.3.1+cu121, 2.4.0, 2.4.0+cu121, 2.4.1,
2.4.1+cu121, 2.5.0, 2.5.0+cu121, 2.5.1, 2.5.1+cu121, 2.6.0, 2.7.0)
ERROR: No matching distribution found for torch==2.1.2Donc j’utilise Python 3.11 :
# apt-get install python3-setuptools
# apt-get install python3-build
# python3.11 -m pip install --upgrade pip setuptools wheel
# virtualenv -p /usr/bin/python3.11 venv
created virtual environment CPython3.11.12.final.0-64 in 1366ms
creator CPython3Posix(dest=/home/XXXX/stable-diffusion-webui/venv, clear=False,
no_vcs_ignore=False, global=False)
seeder FromAppData(download=False, pip=bundle, setuptools=bundle, wheel=bundle,
via=copy, app_data_dir=/home/XXXX/.local/share/virtualenv)
added seed packages: pip==24.0, setuptools==68.1.2, wheel==0.42.0
activators BashActivator,CShellActivator,FishActivator,NushellActivator,PowerShellActivator,PythonActivator
$ source venv/bin/activate
$ python3.11 -m pip install --upgrade pip setuptools wheel
$ bash webui.sh --api --listenJ’ai pas la liste complete des actions que j’ai du faire.
Mais j’ai du supprimer “douane” :
dkms remove douane/0.8.2 --allSinon j’avais une erreur :
make -j8 KERNELRELEASE=6.8.0-53-generic -C /lib/modules/6.8.0-53-generic/build M=/var/lib/dkms/douane/0.8.2/build...(bad exit status: 2)
ERROR (dkms apport): binary package for douane: 0.8.2 not found
Error! Bad return status for module build on kernel: 6.8.0-53-generic (x86_64)
Consult /var/lib/dkms/douane/0.8.2/build/make.log for more information.
dkms autoinstall on 6.8.0-53-generic/x86_64 succeeded for tuxedo-keyboard virtualbox
dkms autoinstall on 6.8.0-53-generic/x86_64 failed for douane(10)
Error! One or more modules failed to install during autoinstall.J’ai du supprimer aussi “tuxedo-cc-wmi”, pareil sinon j’avais une erreur :
J’ai une version Grafana : v6.7.4 (June 3, 2020) sous Ubuntu. J’ai donc fait une mise à jours vers la version v10.3.3 .
En fait le “apt upgrade” ne fonctionnait pas.
Le fichier configuré « main/binary-i386/Packages » ne sera pas pris en compte
car le dépôt « https://apt.grafana.com stable InRelease »
ne prend pas en charge l'architecture « i386 »J’ai donc fait :
# apt-get install -y adduser libfontconfig1 musl
# wget https://dl.grafana.com/enterprise/release/grafana-enterprise_10.3.3_amd64.deb
# cp /var/lib/grafana/grafana.db .
# apt-get remove grafana
# sudo snap remove grafana
# sudo dpkg -i grafana-enterprise_10.3.3_amd64.deb
# sudo /bin/systemctl daemon-reload
# sudo /bin/systemctl enable grafana-server
# updatedb
# cp /var/lib/grafana/grafana.db /var/lib/grafana/grafana.db.backup
# cp /root/grafana.db /var/lib/grafana/grafana.dbJe suis passé du port 3000 au port 3001. Le backup de la configuration ( grafana.db ) n’a pas fonctionné …
Now I have always high CPU load (process tccd) and fan at 100% … very good release ! 
And also impossible to put “Powersave extreme” or “Quiet” … the laptop stop after too hot.
My OS : 22.04.3 LTS (Jammy Jellyfish) .
Logs :
In loops :
$ grep "tccd" /var/log/syslog | tail -f
Dec 20 12:06:47 TUXEDO-Polaris-Intel-Gen3-TGL tccd[1152]: Authorization required, but no authorization protocol specified
Dec 20 12:06:47 TUXEDO-Polaris-Intel-Gen3-TGL tccd[1152]: Can't open display :1
Dec 20 12:06:47 TUXEDO-Polaris-Intel-Gen3-TGL tccd[1152]: Failed executing onWork() => Error: Command failed: export XAUTHORITY=/home/arias/.Xauthority && xrandr -q -display :1 --current
Dec 20 12:06:47 TUXEDO-Polaris-Intel-Gen3-TGL tccd[1152]: Authorization required, but no authorization protocol specified
Dec 20 12:06:47 TUXEDO-Polaris-Intel-Gen3-TGL tccd[1152]: Can't open display :1
Dec 20 12:06:50 TUXEDO-Polaris-Intel-Gen3-TGL tccd[1152]: Authorization required, but no authorization protocol specified
Dec 20 12:06:50 TUXEDO-Polaris-Intel-Gen3-TGL tccd[1152]: Can't open display :1
Dec 20 12:06:50 TUXEDO-Polaris-Intel-Gen3-TGL tccd[1152]: Failed executing onWork() => Error: Command failed: export XAUTHORITY=/home/arias/.Xauthority && xrandr -q -display :1 --current
Dec 20 12:06:50 TUXEDO-Polaris-Intel-Gen3-TGL tccd[1152]: Authorization required, but no authorization protocol specified
Dec 20 12:06:50 TUXEDO-Polaris-Intel-Gen3-TGL tccd[1152]: Can't open display :1And also :
Dans syslog j’ai l’erreur suivante :
make -j16 KERNELRELEASE=6.5.0-10006-tuxedo all INCLUDEDIR=/lib/modules/6.5.0-10006-tuxedo/build/include KVERSION=6.5.0-10006-tuxedo DKMS_BUILD=1...(bad exit status: 2)
ERROR (dkms apport): binary package for evdi: 1.10.1 not found
Error! Bad return status for module build on kernel: 6.5.0-10006-tuxedo (x86_64)
Consult /var/lib/dkms/evdi/1.10.1/build/make.log for more information.Quand je regarde le fichier /var/lib/dkms/evdi/1.10.1/build/make.log :
DKMS make.log for evdi-1.10.1 for kernel 6.5.0-10006-tuxedo (x86_64)
mar. 07 nov. 2023 14:00:31 CET
make KBUILD_VERBOSE=1 M=/var/lib/dkms/evdi/1.10.1/build SUBDIRS=/var/lib/dkms/evdi/1.10.1/build SRCROOT=/var/lib/dkms/evdi/1.10.1/build CONFIG_MODULE_SIG= -C /lib/modules/6.5.0-10006-tuxedo/build modules
make[1]: Entering directory '/usr/src/linux-headers-6.5.0-10006-tuxedo'
make --no-print-directory -C /usr/src/linux-headers-6.5.0-10006-tuxedo \
-f /usr/src/linux-headers-6.5.0-10006-tuxedo/Makefile modules
warning: the compiler differs from the one used to build the kernel
The kernel was built by: x86_64-linux-gnu-gcc-11 (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
You are using: gcc-11 (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
make -f ./scripts/Makefile.build obj=/var/lib/dkms/evdi/1.10.1/build need-builtin=1 need-modorder=1
# cmd_mod /var/lib/dkms/evdi/1.10.1/build/evdi.modPour l’instant j’ai pas réussi à fixer le problème.
Depuis le 17/09/2023, Thunderbird n’arrive plus à se connecter sur Gmail en IMAP.
Ma configuration :
$ sudo snap refresh thunderbird –stable thunderbird 115.2.3-1 from Canonical✓ refreshed
J’ai le même problème avec la version 118 de thunderbird.
J’ai l’erreur :
“400. That’s an error. The server cannot process the request because it is malformed. It should not be retried. That’s all we know.”
J’ai essayé quelques commandes sans succès :
J’ai vu que j’avais en boucle dans syslog :
sh[30354]: modprobe: FATAL: Module evdi not found in directory /lib/modules/6.2.0-10018-tuxedo
sh[30396]: Kernel preparation unnecessary for this kernel. Skipping...
sh[30396]: Building module:
sh[30396]: cleaning build area...
sh[30396]: make -j16 KERNELRELEASE=6.2.0-10018-tuxedo all INCLUDEDIR=/lib/modules/6.2.0-10018-tuxedo/build/include KVERSION=6.2.0-10018-tuxedo DKMS_BUILD=1...(bad exit status: 2)
sh[31025]: ERROR (dkms apport): binary package for evdi: 1.10.1 not found
sh[31099]: Error! Bad return status for module build on kernel: 6.2.0-10018-tuxedo (x86_64)
sh[31099]: Consult /var/lib/dkms/evdi/1.10.1/build/make.log for more information.
systemd[1]: displaylink-driver.service: Control process exited, code=exited, status=10/n/a
systemd[1]: displaylink-driver.service: Failed with result 'exit-code'.
systemd[1]: Failed to start DisplayLink Driver Service.
systemd[1]: displaylink-driver.service: Consumed 7.320s CPU time.
systemd[1]: displaylink-driver.service: Scheduled restart job, restart counter is at 16.
systemd[1]: Stopped DisplayLink Driver Service.
systemd[1]: displaylink-driver.service: Consumed 7.320s CPU time.
systemd[1]: Starting DisplayLink Driver Service...J’ai donc essayé manuellement avec plusieurs versions mais sans succès :
J’ai voulu tester disk-space-saver mais il a planté … trop de fichiers.
disk-space-saver
Gtk-Message: 16:51:43.225: Failed to load module "xapp-gtk3-module"
Gtk-Message: 16:51:43.225: Failed to load module "appmenu-gtk-module"
Gtk-Message: 16:51:45.005: GtkDialog mapped without a transient parent.
This is discouraged.
<--- Last few GCs --->
[11047:0xd780080c000] 77004 ms: Scavenge 1885.0 (1950.3) -> 1879.7
(1951.8) MB, 2.6 / 0.0 ms (average mu = 0.991, current mu = 0.991)
allocation failure;
[11047:0xd780080c000] 77074 ms: Scavenge 1887.0 (1951.9) -> 1881.7
(1953.7) MB, 2.5 / 0.0 ms (average mu = 0.991, current mu = 0.991)
allocation failure;
[11047:0xd780080c000] 77141 ms: Scavenge 1888.5 (1953.9) -> 1883.0
(1955.1) MB, 2.5 / 0.0 ms (average mu = 0.991, current mu = 0.991)
allocation failure;
<--- JS stacktrace --->
[11047:0927/165300.472533:ERROR:v8_initializer.cc(714)] V8 process OOM
(Oilpan: Reserving memory.).Misère.
Je viens de voir une nouvelle erreur au lancement de Thunderbird à cause de GDK :
[GFX1-]: glxtest: VA-API test failed: failed to initialise VAAPI connection.
[Parent 7820, Main Thread] WARNING: gdk_wayland_window_set_dbus_properties_libgtk_only: assertion 'GDK_IS_WAYLAND_WINDOW (window)' failed: 'glib warning', file /builds/worker/checkouts/gecko/toolkit/xre/nsSigHandlers.cpp:167
(thunderbird-beta:7820): Gdk-CRITICAL **: 08:52:03.518: gdk_wayland_window_set_dbus_properties_libgtk_only: assertion 'GDK_IS_WAYLAND_WINDOW (window)' failed
[Parent 7820, Main Thread] WARNING: gdk_wayland_window_set_dbus_properties_libgtk_only: assertion 'GDK_IS_WAYLAND_WINDOW (window)' failed: 'glib warning', file /builds/worker/checkouts/gecko/toolkit/xre/nsSigHandlers.cpp:167
(thunderbird-beta:7820): Gdk-CRITICAL **: 08:52:03.677: gdk_wayland_window_set_dbus_properties_libgtk_only: assertion 'GDK_IS_WAYLAND_WINDOW (window)' failed
[Parent 7820, Main Thread] WARNING: gdk_wayland_window_set_dbus_properties_libgtk_only: assertion 'GDK_IS_WAYLAND_WINDOW (window)' failed: 'glib warning', file /builds/worker/checkouts/gecko/toolkit/xre/nsSigHandlers.cpp:167
(thunderbird-beta:7820): Gdk-CRITICAL **: 08:52:03.794: gdk_wayland_window_set_dbus_properties_libgtk_only: assertion 'GDK_IS_WAYLAND_WINDOW (window)' failed
[Parent 7820, Main Thread] WARNING: gdk_wayland_window_set_dbus_properties_libgtk_only: assertion 'GDK_IS_WAYLAND_WINDOW (window)' failed: 'glib warning', file /builds/worker/checkouts/gecko/toolkit/xre/nsSigHandlers.cpp:167
(thunderbird-beta:7820): Gdk-CRITICAL **: 08:52:04.091: gdk_wayland_window_set_dbus_properties_libgtk_only: assertion 'GDK_IS_WAYLAND_WINDOW (window)' failed
[Parent 7820, Main Thread] WARNING: gdk_wayland_window_set_dbus_properties_libgtk_only: assertion 'GDK_IS_WAYLAND_WINDOW (window)' failed: 'glib warning', file /builds/worker/checkouts/gecko/toolkit/xre/nsSigHandlers.cpp:167
(thunderbird-beta:7820): Gdk-CRITICAL **: 08:52:04.190: gdk_wayland_window_set_dbus_properties_libgtk_only: assertion 'GDK_IS_WAYLAND_WINDOW (window)' failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failedVisiblement l’erreur est liée en GDK et j’ai la même sous Chrome :