Bug#1069586: Chromium native Wayland support broken
Some more tests confirm the following: --ozone-platform=waylandworks --ozone-platform-hint=wayland does not work Regards Stephan
Bug#1069586: Chromium native Wayland support broken
Workaround: If you are stuck Chromium using native Wayland support, you can reset it with the following steps: 1. Log out GNOME on Wayland session and log in with Gnome on Xorg session. 2. Launch Chromium. 3. Enter chrome://flags into URL bar and reset the setting “Preferred Ozone platform” to “Default”. 4. Log out and log in again with Wayland session. Regards Stephan
Bug#1069586: Chromium native Wayland support broken
Package: chromium Version: 124.0.6367.60-1~deb12u1 Since the last update, Chromium does work with native Wayland. It is starting up, but it is displaying an invisible window. It is listed in the window switchers (Alt+Tab), Gnome Shell etc., but invisible. Note: The default configuration uses X11 via XWayland and is working. The setting can be managed via command line arguments or by typing chrome://flags into the URL bar (filter for ozone). Available settings: default -> X11works auto-> Wayland if available does not work x11 works wayland does not work I have been using Chromium with native Wayland for many months without problems until the last update. I reproduced this with a completely new browser profile. Regards Stephan
Bug#1068024: Or remove xz altogether?
Maybe the people who criticized xz back in the day for being an amateur project implementing a defective file format were right all along? https://www.nongnu.org/lzip/xz_inadequate.html Regards Stephan
Bug#1059618: ITP: ssh3 -- faster and rich secure shell using HTTP/3
On Sat, 30 Dec 2023 12:47:48 + Colin Watson wrote: > I also feel that something security-critical like this that's > labelled by upstream as "still experimental" probably shouldn't > be in a Debian release. It is written in Go. The problem of Go library support in Debian should also be considered for a security-critical tool like this. https://www.debian.org/releases/bookworm/amd64/release-notes/ch-information.en.html#golang-static-linking Regards signature.asc Description: This is a digitally signed message part
Bug#1057967: fixed in linux 6.1.67-1
Hereby I confirm that linux-image-6.1.0-16-amd64 (6.1.67-1) from bookworm-proposed-updates fixed the problems for me. Regards Stephan signature.asc Description: This is a digitally signed message part
Bug#1057967: linux-image-6.1.0-15-amd64 renders my physical bookworm/gnome computer largely unusable
Hello everybody Unfortunately, I can confirm the same problems for 2014 Macbook Pro (Intel CPU and graphics). At first I thought the network problem was due to the proprietary Broadcom WLAN driver because network connectivity was the most obvious problem. However, the problems persisted after removing all proprietary (broadcom-sta) and custom (facetimehd) kernel modules. Regards Stephan signature.asc Description: This is a digitally signed message part
Bug#1057843: Guidelines for affected users
Are there any guidelines for affected users who already updated before they got the warning? Interesting questions for affected users: - Is it safe to assume that other filesystems (like BTRFS) are not affected? - Does this cause filesystem corruption or only file corruption? - Does this affect metadata or only file contents? - Is there a way to detect corrupted files? - If metadata is not affected, is it safe to assume that all files with a modification date older than the update are fine? - Does it help to shut down services (such as Apache) or the whole machine until the fix is available?
Bug#967941: Bug appeared again
This bug appears back some time ago. For some months, video thumbnails failed to generate on multiple of my machines. Since then, I was trying to figure out the cause. It only seemed to affect h264, but not all videos were affected. I even had multiple videos saved from Youtube, some were generating thumbnails, others were not. I could not find any difference in the codec parameters. Adding the -l option in /usr/share/thumbnailers/totem.thumbnailer worked to prevent this bug. Does this option have any downsides? Regards signature.asc Description: This is a digitally signed message part
Bug#1023945: Mozilla and Microsoft acted
Please note that Mozilla and Microsoft have removed the certificates now. It is probably now appropriate to follow Mozilla. Google's and Apple's reaction is still open. Regards signature.asc Description: This is a digitally signed message part
Bug#1024726: nmu: evolution-data-server_3.46.1-1+b1
This seems related: https://bugs.debian.org/1024701 Regards signature.asc Description: This is a digitally signed message part
Bug#1024701: libphonenumber8 update breaks evolution
From changelog: libphonenumber (8.12.57+ds-1+b1) sid; urgency=low, binary-only=yes * Binary-only non-maintainer upload for amd64; no source changes. * Rebuild against libicu72 -- amd64 / i386 Build Daemon (x86-csail-01) Wed, 09 Nov 2022 09:06:01 + signature.asc Description: This is a digitally signed message part
Bug#1024701: libphonenumber8 update breaks evolution
Evolution gives the following confusing error message. $ evolution evolution: symbol lookup error: /lib/x86_64-linux-gnu/libebook- contacts-1.2.so.4: undefined symbol: _ZN4i18n12phonenumbers11PhoneNumberC1EPN6google8protobuf5ArenaE However, libebook-contacts has not changed recently. Regards signature.asc Description: This is a digitally signed message part
Bug#1024701: libphonenumber8 update breaks evolution
Package: libphonenumber8 Version: 8.12.57+ds-1+b2 Severity: serious After updating libphonenumber8 from version 8.12.57+ds-1+b1 to version 8.12.57+ds-1+b2 in Debian Sid, Gnome Evolution fails to launch. Downgrading to the previous version (still in Bookworm) fixes the issue. Regards signature.asc Description: This is a digitally signed message part
Bug#1022900: fixed in linux 6.0.8-1
I am happy to confirm that with Linux kernel 6.0.8-1 in Debian Sid, the issue is fixed. Regards
Bug#1022900: grub-install, efibootmgr etc. not working with new kernel
Yesterday, kernel 6.0.8 was released with a number of EFI fixes. I have compiled the vanilla kernel and I am happy to confirm that it solves the issue. Regards
Bug#1022900: grub-install, efibootmgr etc. not working with new kernel
Update for completeness: The EFI patches have not made it into 6.0.7. As expected, 6.0.7 from Debian still has the problem. New EFI patches have been merged into master on November 4. I hope to find them in 6.0.8 or 6.1. Then I will test again. Regards
Bug#1022900: grub-install, efibootmgr etc. not working with new kernel
Some updates. linux-image-6.0.0-2-amd64 6.0.6-2 does not fix the bug. In the upstream bug, a new set of new patches were mentioned which should address this issue. I expect them to be merged into version 6.0.7. New patches regarding EFI: https://git.kernel.org/pub/scm/linux/kernel/git/efi/efi.git/log/?h=urgent I will not apply any patches manually but just wait for the coming releases instead. Anyone who has this issue right now can boot into kernel 5.19 as a workaround. Regards
Bug#1022900: grub-install, efibootmgr etc. not working with new kernel
Sice the latest vanilla kernel does not work, I have filed an upstream bug. https://bugzilla.kernel.org/show_bug.cgi?id=216640 Regards
Bug#1022900: grub-install, efibootmgr etc. not working with new kernel
For completeness: The problem persists with the new kernel in Sid. > 6.0.0-2-amd64 / Debian 6.0.5-1 (2022-10-28) x86_64 GNU/Linux
Bug#1022900: grub-install, efibootmgr etc. not working with new kernel
Some more information: linux-image-5.19.0-2-amd64/now 5.19.11-1 (not affected) linux-image-6.0.0-1-amd64/now 6.0.2-1+b1 (affected) linux-image-6.0.0-2-amd64/unstable,now 6.0.3-1 (affected) linux-image-6.0.5/now 6.0.5-1 (custom vanilla kernel build, affected) Other relevant package versions (no recent changes): efibootmgr/unstable,now 17-1 efivar/unstable,now 37-6 libefivar1/unstable,now 37-6 grub-common/unstable,now 2.06-4 grub-efi-amd64/unstable,now 2.06-4 grub-efi-amd64-bin/unstable,now 2.06-4 grub-efi-amd64-signed/unstable,now 1+2.06+4 grub2-common/unstable,now 2.06-4 Feel free to ask for more information, logs or additional tests. Regards
Bug#1022900: grub-install, efibootmgr etc. not working with new kernel
I have now compiled and booted vanilla kernel 6.0.5. “efibootmgr -o” is not working. I double-checked that with kernel 5.19.11 (Debian), it is working fine. Regards
Bug#1022900: grub-install, efibootmgr etc. not working with new kernel
I have installed the package “linux-source”, applied the patch, compiled and booted it. The patch alone does not appear to fix the issue. (“efibootmgr -o” still not working.) Maybe I find time to try vanilla kernel 6.0.5 on the weekend. Regards Stephan
Bug#1022900: grub-install, efibootmgr etc. not working with new kernel
Package: src:linux Version: 6.0.3-1 When I boot with kernel 6.0.x, grub-install, efibootmgr etc. keep failing. With kernel 5.19.x it works on the same machine with the same userland. Hardware: MacBookPro11,1, Intel(R) Core(TM) i7-4578U CPU @ 3.00GHz I am not sure if this app is Apple specific. I recommend developers to test grub-install and efibootmgr on other hardware setups. grub-install: info: copying `/usr/lib/shim/shimx64.efi.signed' -> `/boot/efi/EFI/debian/shimx64.efi'. grub-install: info: copying `/usr/lib/grub/x86_64-efi- signed/grubx64.efi.signed' -> `/boot/efi/EFI/debian/grubx64.efi'. grub-install: info: copying `/usr/lib/shim/mmx64.efi.signed' -> `/boot/efi/EFI/debian/mmx64.efi'. grub-install: info: copying `/usr/lib/shim/fbx64.efi.signed' -> `/boot/efi/EFI/debian/fbx64.efi'. grub-install: info: copying `/usr/lib/shim/BOOTX64.CSV' -> `/boot/efi/EFI/debian/BOOTX64.CSV'. grub-install: info: copying `/boot/grub/x86_64-efi/load.cfg' -> `/boot/efi/EFI/debian/grub.cfg'. grub-install: info: Registering with EFI: distributor = `debian', path = `\EFI\debian\shimx64.efi', ESP at hostdisk//dev/sda,gpt1. grub-install: info: executing modprobe efivars 2>/dev/null. grub-install: info: setting EFI variable Boot. grub-install: warning: Cannot set EFI variable Boot. grub-install: warning: efivarfs_set_variable: writing to fd 6 failed: Invalid argument. grub-install: warning: _efi_set_variable_mode: ops->set_variable() failed: Invalid argument. grub-install: error: failed to register the EFI boot entry: Invalid argument. Regards
Bug#1021912: Patch available
There is a patch available in the Arch community: https://github.com/archlinux/svntogit-community/blob/master/broadcom-wl-dkms/repos/community-x86_64/015-linux600.patch Quick and dirty solution until the patch is included in Debian (use at own risk): 1. Download 015-linux600.patch (raw file) 2. # cd /usr/src/broadcom-.../src/wl/sys/ 3. # patch wl_cfg80211_hybrid.c < /path/to/015-linux600.patch 4. # dpkg-reconfigure broadcom-sta-dkms Regards
Bug#1013132: ITP: BabaSSL -- BabaSSL is a base library for modern cryptography and communication security protocols.
As far as I understand it, the main point of BabaSSL is to add support for Chinese developed ciphers and algorithms. Long time ago in my student years, I was working with a German fork of OpenSSL. The point was to add German elliptic curves (BSI and Deutsche Telekom). They were eventually merged into OpenSSL. Regards
Bug#1014029: invisible malicious unicode in source code - detection and prevention
Your text is quite chaotic, it is hard to distinguish the quotes from your ideas what to do in Debian. I think the main problem here are the programs which are presenting source code to humans (text editors, terminals, HTML pages in Gitlab etc.). Quotes should always terminate everything. A control character within a string literal should not have any effect outside of the quotes. The rules should be similar as we know them from syntax highlighting. All directional instructions should be terminated by the closing quote. However, since it is not realistic to free all relevant tools from all related bugs soon, compiler warnings make sense. There I think it does not make sense to ban all Unicode. Unicode clearly distinguishes printable and non-printable characters and so on. So all characters that print something clearly visible can be whitelisted. Regards
Bug#1012655: upstream bug and fix
Kernel 5.18.4 got the patch. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/diff/drivers/input/mouse/bcm5974.c?id=v5.18.4=v5.18.3 Regards
Bug#1012655: upstream bug and fix
They merged it (on June 7) into kernel 5.19, but kernel 5.18.3 (released June 9) does not seem to have it yet. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/diff/?id=v5.18.3=v5.18=2 I will just use 5.17 or external mouse until the fix lands in Sid. Thank you and regards
Bug#1012655: upstream bug and fix
When I filed the bug, I could not find any other reports. Now I found an upstream report which has matching symptoms. https://bugzilla.kernel.org/show_bug.cgi?id=215890 However, there is confusion about the resolution. One reply states that it was resolved in 5.18.0, but other replies talk about accidental fixes. A fix was submitted more recently than 5.18.0 release: https://lore.kernel.org/all/20220606113636.588955-1-mathias.ny...@linux.intel.com/ Regards
Bug#1012655: Macbook Pro touchpad not working with kernel 5.18
Package: src:linux Version: 5.18.2-1 The touchpad on my 2014 Macbook (MacBookPro11,1) is no longer working since kernel 5.18 was installed. This affects both X11 and Wayland. I am using Sid with Gnome. When booting back into kernel 5.17, the touchpad works without problems. That's why I suspect the bug to be in the kernel. Keyboard is working without problems. keyboard and trackpad appear to be one single device. External USB mouse is working without problems. # lsusb Bus 001 Device 003: ID 05ac:0259 Apple, Inc. Internal Keyboard/Trackpad # lshw description: Keyboard product: bcm5974 vendor: Apple Inc. Regards
Bug#1012481: broadcom-sta fails to build with kernel 5.18
Package: broadcom-sta Version: 6.30.223.271-19 broadcom-sta fails to build with kernel 5.18 due to deprecated symbols. There appears to be a patch available in the Arch community: https://github.com/archlinux/svntogit-community/blob/master/broadcom-wl-dkms/trunk/013-linux518.patch Regards
Bug#1010128: Workaround
Quick and dirty workaround for broadcom-sta-dkms on kernel 5.17: 1. Download patch. $ wget https://raw.githubusercontent.com/archlinux/svntogit-community/master/broadcom-wl-dkms/trunk/012-linux517.patch WARNING: Make sure not to download any untrused/malicious code. The changes in the linked patch appear small and safe. 2. With root shell, go to source. # cd /usr/src/broadcom-sta-6.30.223.271/src/wl/sys/ 3. Patch the code. # patch wl_linux.c < /home/stephan/Downloads/012-linux517.patch 4. Reconfigure broadcom-sta-dkms to trigger DKMS # dpkg-reconfigure broadcom-sta-dkms WARNING: Re-installing the package will reverse your changes. Regards
Bug#1010128: Duplicates
Another one: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010424
Bug#1010128: Duplicates
Duplicates: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010283 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010240 Regards
Bug#1010128: Patch
There is a patch circulating in the Arch community. https://github.com/archlinux/svntogit-community/blob/master/broadcom-wl-dkms/trunk/012-linux517.patch Regards
Bug#1010128: confirm
I can confirm this on my machine (2014 Macbook Pro). Note that DKMS for NVIDIA appears to work. I guess the problem is on Broadcom side using deprecated APIs. Regards
Bug#1009367: Confirm fix
The last update fixed the bug for my existing users. I can also confirm that the bug is fixed for newly created users. Regards
Bug#1009367: libnss3 file location changes
This patch is probably also related: https://sources.debian.org/patches/evolution/3.44.1-1/02_nss_paths.patch/ Regards
Bug#1009367: libnss3 file location changes
Another hint: There are hardcoded paths in the following file: ~/.pki/nssdb/pkcs11.txt e.g.: > library=/usr/lib/x86_64-linux-gnu/nss/libnssckbi.so To me it is not clear who creates that file, nss or evolution. Regards
Bug#1009367: libnss3 file location changes
Further analysis shows that it is related to changed file locations between the libnss3 versions. Some files were moved out of the nss directory. Files in stable (libnss3 2:3.61-1+deb11u2): /usr/lib/x86_64-linux-gnu/libnss3.so /usr/lib/x86_64-linux-gnu/libnssutil3.so /usr/lib/x86_64-linux-gnu/libsmime3.so /usr/lib/x86_64-linux-gnu/libssl3.so /usr/lib/x86_64-linux-gnu/nss/libfreebl3.chk /usr/lib/x86_64-linux-gnu/nss/libfreebl3.so /usr/lib/x86_64-linux-gnu/nss/libfreeblpriv3.chk /usr/lib/x86_64-linux-gnu/nss/libfreeblpriv3.so /usr/lib/x86_64-linux-gnu/nss/libnssckbi.so /usr/lib/x86_64-linux-gnu/nss/libnssdbm3.chk /usr/lib/x86_64-linux-gnu/nss/libnssdbm3.so /usr/lib/x86_64-linux-gnu/nss/libsoftokn3.chk /usr/lib/x86_64-linux-gnu/nss/libsoftokn3.so /usr/share/doc/libnss3/changelog.Debian.gz /usr/share/doc/libnss3/copyright /usr/share/lintian/overrides/libnss3 Files in unstable (libnss3 2:3.77-1): /usr/lib/x86_64-linux-gnu/libfreebl3.chk /usr/lib/x86_64-linux-gnu/libfreebl3.so /usr/lib/x86_64-linux-gnu/libfreeblpriv3.chk /usr/lib/x86_64-linux-gnu/libfreeblpriv3.so /usr/lib/x86_64-linux-gnu/libnss3.so /usr/lib/x86_64-linux-gnu/libnssckbi.so /usr/lib/x86_64-linux-gnu/libnssdbm3.chk /usr/lib/x86_64-linux-gnu/libnssdbm3.so /usr/lib/x86_64-linux-gnu/libnssutil3.so /usr/lib/x86_64-linux-gnu/libsmime3.so /usr/lib/x86_64-linux-gnu/libsoftokn3.chk /usr/lib/x86_64-linux-gnu/libsoftokn3.so /usr/lib/x86_64-linux-gnu/libssl3.so /usr/share/doc/libnss3/changelog.Debian.gz /usr/share/doc/libnss3/copyright /usr/share/lintian/overrides/libnss3 QUICK FIX Manually creating a nss directory with symlinks to the shared objects appears to fix the problem. However, that is not a good solution as it could have undesired side effects. I am not sure whether it is the job for libnss3 or evolution maintainers to fix this. Regards
Bug#1009367: Evolution ignoring system certificate store
Package: evolution Version: 3.44.0-2 Evolution is ignoring the system certificate store. As a result, it is impossible to validate signed emails (S/MIME). In addition, Encryption also does not work properly because many certificates are not trusted. It appears to only affect S/MIME. In my tests, TLS protection of server connections was still working. I have reproduced this bug on several machines with Debian Sid, with various Linux users and with various e-mail accounts. The bug is also occuring for newly created users. How to reproduce: 1. Create a new Linux user and log in 2. Launch Evolution 3. Navigate to Edit/Preferences/Certificates 4. Open the “Authorities” tab and note that there are no certificates The bug does not occur in Debian Bullseye with Evolution 3.38. The bug does not occur in Ubuntu 20.04 beta with Evolution 3.44 either. It is possible that this bug is caused by libnss and the ~/.pki configuration rather than Evolution.
Bug#997663: general: bullseye, system freezes completely when firefox freezes
Possibly relevant: - Are you using X11 or Wayland? - Do you have proprietary graphics drivers installed? - Does the freeze occur without those? - Can you SSH into the machine after the screen/input freezes? - Do you have other indications that the machine is still working? Regards
Bug#997055: gnome-builder does not start up (missing library)
Package: gnome-builder Version: 41.1-2 gnome-builder does not start and throws the following error message: $ gnome-builder gnome-builder: error while loading shared libraries: libcmark.so.0.30.1: cannot open shared object file: No such file or directory The corresponding library does not exist with this name. However, there are other versions: $ find /usr/lib -name "libcmark.*" /usr/lib/x86_64-linux-gnu/pkgconfig/libcmark.pc /usr/lib/x86_64-linux-gnu/libcmark.a /usr/lib/x86_64-linux-gnu/libcmark.so /usr/lib/x86_64-linux-gnu/libcmark.so.0.30.2 Creating a symlink libcmark.so.0.30.1 -> libcmark.so.0.30.2 works as a workaround. I am using Debian Sid on AMD64 with all recent package versions.
Bug#995280: gnome-builder cannot open or create projects
Package: gnome-builder Version: 41.1-1 When I try to open or create a project, gnome-builder gets stuck. It prints the following warning, which may be related: $ gnome-builder 05:18:55.3027 ide-subproces-supervisor[ 7160]: WARNING: Failed to execute child process “/usr/libexec/gnome-builder- flatpak” (No such file or directory) The corresponding binary does not exist in this path or anywhere else in /usr. I am using Debian Sid with all recent package versions. I did not experience this problem with gnome-builder 3.40.x.
Bug#971799: mz: Immediate crash when starting interactive mode
This also affects the "mausezahn" command from the netsniff-ng package. When I build myself from Git, it does not crash. This (closed) upstream issue might be related: https://github.com/netsniff-ng/netsniff-ng/issues/195 The Debian packages have not been updated since. Regards Stephan
Bug#971799: mz: Immediate crash when starting interactive mode
Package: mz Version: 0.40-1.1+b1 Severity: important Tags: a11y ipv6 Dear Maintainer, mz (mausezahn) is crashing immediately when launched with interactive mode. As a result, interactive mode cannot be used. How to reproduce? # mz -x The problem exists in Buster and Sid (and also Ubuntu 20.04). Note that according to the manpage, the interactive mode uses a more efficient implementation and is therefore crucial for effective testing networks with the tool. -- System Information: Debian Release: 10.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-11-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages mz depends on: ii libc6 2.28-10 ii libcli1.9 1.9.7-2+b11 ii libnet1 1.1.6+dfsg-3.1 ii libpcap0.8 1.8.1-6 mz recommends no packages. Versions of packages mz suggests: pn python-matplotlib -- no debconf information
Bug#965164: policykit-1
This also makes the system fail to boot. Regards
