Bug#1070745: Re: Bug#1070745: Bug on Debian 12 Bookworm - Gnome-Shell / After today's upgrade, the dead keys on my keyboard no longer work
Thank you a thousand times Simon for your extremely quick response :) I'm looking forward to the fix... Good day to you. Philippe Message d'origine De : s...@debian.org Date : 08/05/2024 - 12:41 (E) À : pham...@bluewin.ch, 1070...@bugs.debian.org Objet : Re: Bug#1070745: Bug on Debian 12 Bookworm - Gnome-Shell / After today's upgrade, the dead keys on my keyboard no longer work Control: reassign -1 libglib2.0-0 2.74.6-2+deb12u1 Control: affects -1 + gnome-shell On Wed, 08 May 2024 at 11:42:10 +0200, pham...@bluewin.ch wrote: > After today's update, the dead keys on my keyboard no longer work This is a regression in GLib triggered by fixing CVE-2024-34397. I'm testing a possible fix as rapidly as I can, but each GLib build takes about an hour, so please be patient. smcv
Bug#1070745: Bug on Debian 12 Bookworm - Gnome-Shell / After today's upgrade, the dead keys on my keyboard no longer work
Post Scriptum I use Swiss French/German/Italian keyboard. We have a unique keyboard for these 3 languages. I have tested all existing keyboard profiles without success. They all pose this problem. If I enter for exemple : être The result displayed is : tre The keyboard option without dead keys works but is unusable on a daily basis. Regards.
Bug#1070745: Bug on Debian 12 Bookworm - Gnome-Shell / After today's upgrade, the dead keys on my keyboard no longer work
Package: Gnome-Shell Version: 43.9-0+deb12u2 Severity: critical Bug Description: After today's update, the dead keys on my keyboard no longer work, neither on my workstation or on my laptop ?!? I noticed this problem on my station this morning after the proposed update. I checked that it worked well on my laptop everything was ok, I applied the update and after a reboot it no longer worked on my laptop either. - Station update log : Start-Date: 2024-05-08 09:17:44 Commandline: apt dist-upgrade Upgrade: libglib2.0-bin:amd64 (2.74.6-2, 2.74.6-2+deb12u1), libglib2.0-data:amd64 (2.74.6-2, 2.74.6-2+deb12u1), gnome-shell:amd64 (43.9-0+deb12u1, 43.9-0+deb12u2), gnome-shell-common:amd64 (43.9-0+deb12u1, 43.9-0+deb12u2), libglib2.0-0:amd64 (2.74.6-2, 2.74.6-2+deb12u1), libglib2.0-0:i386 (2.74.6-2, 2.74.6-2+deb12u1), gnome-shell-extension-prefs:amd64 (43.9-0+deb12u1, 43.9-0+deb12u2) Remove: linux-image-6.1.0-18-amd64:amd64 (6.1.76-1) End-Date: 2024-05-08 09:17:52 - Laptop update log : Start-Date: 2024-05-08 11:07:48 Commandline: apt dist-upgrade -y Install: linux-headers-6.1.0-21-amd64:amd64 (6.1.90-1, automatic), linux-headers-6.1.0-21-common:amd64 (6.1.90-1, automatic), linux-image-6.1.0-21-amd64:amd64 (6.1.90-1, automatic) Upgrade: libglib2.0-bin:amd64 (2.74.6-2, 2.74.6-2+deb12u1), linux-compiler-gcc-12-x86:amd64 (6.1.85-1, 6.1.90-1), linux-headers-amd64:amd64 (6.1.85-1, 6.1.90-1), libglib2.0-data:amd64 (2.74.6-2, 2.74.6-2+deb12u1), gnome-shell:amd64 (43.9-0+deb12u1, 43.9-0+deb12u2), linux-kbuild-6.1:amd64 (6.1.85-1, 6.1.90-1), linux-image-amd64:amd64 (6.1.85-1, 6.1.90-1), gnome-shell-common:amd64 (43.9-0+deb12u1, 43.9-0+deb12u2), libglib2.0-0:amd64 (2.74.6-2, 2.74.6-2+deb12u1), libglib2.0-0:i386 (2.74.6-2, 2.74.6-2+deb12u1), gnome-shell-extension-prefs:amd64 (43.9-0+deb12u1, 43.9-0+deb12u2), linux-libc-dev:amd64 (6.1.85-1, 6.1.90-1) End-Date: 2024-05-08 11:08:10 Thank you for urgently returning to previous versions, we can no longer work properly since... Regards.
Bug#1067054: Debian 12 - Copy files on USB 3
Extra information : It is stable when you initialize the disk in MBR/MS-DOS format, but only with a USB A to USB C cable, if you use a USB c to USB-C cable the problems persist.
Bug#1067054: Debian 12 - Copy files on USB 3
After further testing, the crash issue when copying multiple files (total volume 150 GB) or a disk image (250 GB) is present when an SSD is formatted in GPT format. This works without problem if the SSD is formatted in MBR/MS-DOS. Regards.
Bug#1067054: Re: Bug#1067054: Debian 12 - Copy files on USB 3
>What you're describing sounds just as likely to be a hardware problem >with the enclosure, to be honest. Does it work 100% reliably elsewhere? Hello Steve, I recently spoke on a forum with a user who also had a USB C box from another brand and who had the same problem as mine... So the problem doesn't seem to only concern me. Under Windows 11 there is no problem, everything works perfectly. The transfer takes place everywhere at 400 MB/sec. So it's not a hardware problem contrary to what you say. I will soon receive a 2.5 inch USB C drive enclosure from another brand. I can do tests again if you want but the result will be the same, that's for sure!! For my part, I more than strongly suspect a teething problem with the USB 3 type C driver under Linux... Regard. Philippe
Bug#1067054: Debian 12 - Copy files on USB 3
For complement of information : The SSD used is a Samsung 850 Pro 256 GB and the case is a Satechi ST-TCDEM. Write rates were high at the start of the copy (450 MB/sec then dropped before the crash to +/- 30 Mb/sec). Restoring the disk image with this same SSD but integrated in a Delock USB 3 Type A case to a USB A socket on my computer works correctly with a transfer rate of 60 to 90 MB/s. The same SSD still plugged into the Delock USB 3 Type A box but connected to my machine on a USB C port completes the restoration of the image with a constant transfer rate of +/- 41MB/sec. Regards.
Bug#1067054: Debian 12 - Copy files on USB 3
Package: kernel Version: 6.1.76-1 (2024-02-01) Severity: critical Bug Description: Good morning, I noticed a problem with Debian 12 and USB 3. When I copy a large volume of data +/- 150 Gb onto a 2.5 inch SSD integrated into an external enclosure (Satechi) which has a USB 3 type C socket and this enclosure is plugged into a USB 3 A socket on my PC, the copy cuts out after a while (+/- 20%), there is a crash. If I use a USB 3 C socket on my PC it seems to make the problem worse. Same thing if I restore a 250 GB disk image, it also crashes. If I do the same restoration job but on a 2 A USB socket, everything works perfectly, except that it takes a lot of time... If I use an M.2 2280 drive also integrated into an external enclosure with a USB 3 type C socket, everything works fine. If I use an SD card connected to an SD card reader connected via USB 3 to my machine it also works perfectly. Debian and its kernel do not seem to appreciate 2.5 inch SSDs integrated into external enclosures with a USB 3 type C socket... Please try to fix this... Best regards.
Bug#1063729: Kernel panic after update from Debian 12.4 to 12.5 in command line and reboot
Package: linux-image-6.1.0-18-amd64 Version: 6.1.76-1: amd64 Severity: critical Bug Description: Kernel panic after update from Debian 12.4 to 12.5 in command line and reboot. Look "Kernel panic after update.txt" in attachment for details. Look message booting display in attachment for more details. Please correct this urgently !!! Regards. Philipperoot@station:~# apt update && apt dist-upgrade Atteint :1 https://security.debian.org/debian-security bookworm-security InRelease Atteint :2 http://ppa.launchpad.net/vincent-vandevyvre/vvv/ubuntu focal InRelease Atteint :3 https://deb.debian.org/debian bookworm InRelease Atteint :4 https://deb.debian.org/debian bookworm-updates InRelease Atteint :5 https://deb.debian.org/debian-security bookworm-security InRelease Lecture des listes de paquets... Fait Construction de l'arbre des dépendances... Fait Lecture des informations d'état... Fait Tous les paquets sont à jour. Lecture des listes de paquets... Fait Construction de l'arbre des dépendances... Fait Lecture des informations d'état... Fait Calcul de la mise à jour... Fait Le paquet suivant a été installé automatiquement et n'est plus nécessaire : linux-headers-6.1.0-16-common Veuillez utiliser « apt autoremove » pour le supprimer. Les paquets suivants seront ENLEVÉS : linux-headers-6.1.0-16-amd64 linux-image-6.1.0-16-amd64 0 mis à jour, 0 nouvellement installés, 2 à enlever et 0 non mis à jour. 4 partiellement installés ou enlevés. Après cette opération, 412 Mo d'espace disque seront libérés. Souhaitez-vous continuer ? [O/n] o (Lecture de la base de données... 416726 fichiers et répertoires déjà installés. ) Suppression de linux-headers-6.1.0-16-amd64 (6.1.67-1) ... Suppression de linux-image-6.1.0-16-amd64 (6.1.67-1) ... /etc/kernel/prerm.d/dkms: dkms: removing: nvidia-current 525.147.05 (6.1.0-16-amd64) (x86_64) Module nvidia-current-525.147.05 for kernel 6.1.0-16-amd64 (x86_64). Before uninstall, this module version was ACTIVE on this kernel. nvidia-current.ko: - Uninstallation - Deleting from: /lib/modules/6.1.0-16-amd64/updates/dkms/ - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. nvidia-current-modeset.ko: - Uninstallation - Deleting from: /lib/modules/6.1.0-16-amd64/updates/dkms/ - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. nvidia-current-drm.ko: - Uninstallation - Deleting from: /lib/modules/6.1.0-16-amd64/updates/dkms/ - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. nvidia-current-uvm.ko: - Uninstallation - Deleting from: /lib/modules/6.1.0-16-amd64/updates/dkms/ - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. nvidia-current-peermem.ko: - Uninstallation - Deleting from: /lib/modules/6.1.0-16-amd64/updates/dkms/ - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. depmod... /etc/kernel/postrm.d/initramfs-tools: update-initramfs: Deleting /boot/initrd.img-6.1.0-16-amd64 /etc/kernel/postrm.d/zz-update-grub: Generating grub configuration file ... Found background image: /usr/share/images/desktop-base/desktop-grub.png Found linux image: /boot/vmlinuz-6.1.0-18-amd64 Found linux image: /boot/vmlinuz-6.1.0-17-amd64 Found initrd image: /boot/initrd.img-6.1.0-17-amd64 Warning: os-prober will be executed to detect other bootable partitions. Its output will be used to detect bootable binaries on them and create new boot entries. Found Windows Boot Manager on /dev/nvme0n1p1@/EFI/Microsoft/Boot/bootmgfw.efi Adding boot menu entry for UEFI Firmware Settings ... done Paramétrage de linux-image-6.1.0-18-amd64 (6.1.76-1) ... I: /initrd.img is now a symlink to boot/initrd.img-6.1.0-18-amd64 /etc/kernel/postinst.d/dkms: dkms: running auto installation service for kernel 6.1.0-18-amd64. Sign command: /usr/lib/linux-kbuild-6.1/scripts/sign-file Signing key: /var/lib/dkms/mok.key Public certificate (MOK): /var/lib/dkms/mok.pub Building module: Cleaning build area... env NV_VERBOSE=1 make -j32 modules KERNEL_UNAME=6.1.0-18-amd64(bad exit status: 2) Error! Bad return status for module build on kernel: 6.1.0-18-amd64 (x86_64) Consult /var/lib/dkms/nvidia-current/525.147.05/build/make.log for more informat ion. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. dkms: autoinstall for kernel: 6.1.0-18-amd64 failed! run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 dpkg: erreur de traitement du paquet
