Apologies and thanks for clarifying!
Package: src:systemd
Version: 257.5-2
Severity: important
Tags: fixed-upstream
Hello,
A regression in networkd, introduced in v256, drops neighbour
discovery configurations if neighbour advertisements are received
without the router flag, but a host can send router advertisements
without acting a
Hi,
I use dracut (106-5) + systemd-ukify (257.3-1) to generate a UKI on trixie.
I had observed an increase in UKI size between the installation of
systemd-ukify (followed by the initial generation of a UKI) and that
generated by a recent kernel update.
I suspected it was a second initrd and, aft
Package: iwd
Version: 3.3-4
Hello,
During startup I see: dbus-daemon[1012]: dbus[1012]: Unknown group
"netdev" in message bus configuration file
I believe this is due to policy group in
/usr/share/dbus-1/system.d/iwd-dbus.conf:
...
Following [1], I understand a postinst step needs to be ad
Thanks Luca, but I think it is a missing dependency - I have just
installed libidn2-0 and it's working as expected.
Best,
Phil
On Mon, 17 Feb 2025 at 18:24, Luca Boccassi wrote:
>
> Control: tags -1 upstream
> Control: close -1
>
> On Mon, 17 Feb 2025 17:47:25 + Phi
Package: systemd-resolved
Version: 257.3-1
Hello,
On trixie, during the startup of systemd-resolved I observe the info
message: "Defaulting to hostname 'linux'."
/etc/hostname is populated and the correct hostname is returned by
hostnamectl and hostname
Attempting to set the hostname (with eith
Package: src:linux
Version: 6.12.12-1
Severity: wishlist
Hello,
With trixie, on an Intel Ultra 7 165H, I observe: *ERROR* GT1: GSC
proxy handler failed to init.
According to [1], this error will be emitted if
CONFIG_INTEL_MEI_GSC_PROXY is not set. As a result, HDCP will be
capped to v1.4 and PXP
Apologies - my original message appears to have become garbled.
Attaching the log messages instead:
journalctl.log - observed error
I have tried resetting the databases and restarting the tracker daemon,
but the problem persists.
tracker_extract.log - snipped identified by tracker daemon as
Package: tracker
Version: 2.3.6-2
Dear Maintainer,
I am encountering an error with tracker failing to store metadata and
consuming resources as it repeatedly tries and fails to continue.
A consequence of this is that one can no longer benefit from indexed
data for rapid searching in nautilus
Hi Michael,
Thanks for the quick reply!
On Thu, 6 May, 2021 at 12:46, Michael Biebl wrote:
This would need convincing of the stable release managers, who
usually prefer targetted, small fixes for stable uploads. I'm a bit
skeptical that this one would qualify.
We do offer newer releases vi
Package: systemd
Version: 247.3-5
Dear Maintainer,
Queries made via the systemd-resolved stub resolver do not have the
RRSIG response returned through the stub, breaking the chain of trust
and preventing applications, such as network diagnostic tools, from
validating DNSSEC signatures themsel
On Fri, 23 Apr, 2021 at 23:51, Roger Shimizu
wrote:
I think backports would be more simple, and fast to upload.
Does that work for you?
Works for me, thanks Roger!
Seems I'm experiencing the same with 3.38.2-1 on bullseye with a fresh
install of epiphany.
After a couple of minutes visiting a single, relatively light website
(newspaper, no embedded media), epiphany locked up my machine,
requiring a hard reset. The only message in journalctl coinciding wit
ase, but do you know if the plan is to merge it into bulleye
post-release?
Cheers,
Phil
On Sun, 18 Apr, 2021 at 21:41, Philip Stewart
wrote:
Thanks Roger, unfortunately both errors remain after updating to
broadcom-sta-dkms/experimental,now 6.30.223.271-16~exp1.
However, on a more positive
:04, Roger Shimizu
wrote:
On Mon, Apr 19, 2021 at 1:33 AM Philip Stewart
wrote:
Package: broadcom-sta-dkms
Version: 6.30.223.271-15
Severity: minor
Dear Maintainer,
Calls to networkctl, e.g. 'networkctl' or 'networkctl status wlan0',
result in the following error mess
Package: broadcom-sta-dkms
Version: 6.30.223.271-15
Severity: minor
Dear Maintainer,
Calls to networkctl, e.g. 'networkctl' or 'networkctl status wlan0',
result in the following error messages in dmesg:
[ 6969.831960] ERROR @wl_dev_intvar_get :
[ 6969.831968] error (-1)
[ 6969.831979] ERROR @
Hi,
Unsure whether there is any appetite to merge this for bullseye, but
the fix for this has been merged upstream:
https://gitlab.freedesktop.org/plymouth/plymouth/-/merge_requests/122
For what it's worth, I've implemented the changes locally and haven't
observed any ill effects in doing so
Thanks to the efforts of the nouveau maintainers, the fix has now made
it into 5.10.13.
Is my understanding correct that this will be make it into bullseye
naturally or does the freeze prevent that?
Cheers, Phil
Hi,
A patch [1] has been proposed by Bastian Beranek [2] to fix the issue.
The issue has been found to affect NV50/Tesla GPUs on kernels 5.9+ and
renders the system unusable.
I've personally tested the patch (and its earlier variant) on the 5.10
kernel for the past couple of weeks without is
I think this is the upstream issue:
https://gitlab.freedesktop.org/drm/nouveau/-/issues/14
As of 5.10.3, the regression appears to remain.
Hello again,
I wanted to share a further finding since the bug report was submitted.
Following repeated lock-ups making the system practically unusable, I
have installed linux-image-5.8.0-2-amd64 (package version 5.8.10-1)
from the Debian snapshot archive.
Having now tested this 5.8 kernel f
Package: src:linux
Version: 5.9.11-1
Hello,
I'm experiencing frequent lock-ups of my machine since installing
bullseye on Saturday, rendering it inoperable for several minutes at a
time, most recently following a launch of GNOME Disk Utility.
Looking in journalctl afterwards, I note:
--
22 matches
Mail list logo
