Some more tests confirm the following:
--ozone-platform=waylandworks
--ozone-platform-hint=wayland does not work
Regards
Stephan
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
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
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
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
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
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
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
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
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
This seems related:
https://bugs.debian.org/1024701
Regards
signature.asc
Description: This is a digitally signed message part
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
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
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
I am happy to confirm that with Linux kernel 6.0.8-1 in Debian Sid, the
issue is fixed.
Regards
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
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
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:
Sice the latest vanilla kernel does not work, I have filed an upstream
bug.
https://bugzilla.kernel.org/show_bug.cgi?id=216640
Regards
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
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
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
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
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
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.
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
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
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
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
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
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
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
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
Another one:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010424
Duplicates:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010283
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010240
Regards
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
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
The last update fixed the bug for my existing users. I can also confirm
that the bug is fixed for newly created users.
Regards
This patch is probably also related:
https://sources.debian.org/patches/evolution/3.44.1-1/02_nss_paths.patch/
Regards
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
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
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,
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
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
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
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
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
This also makes the system fail to boot.
Regards
48 matches
Mail list logo
