Since reporting this issue I never got that error again in the journal.
Feel free to close as "not reproducible".
Package: wpasupplicant
Version: 2:2.10-15
Severity: minor
X-Debbugs-Cc: in.cognit...@arcor.de
Dear Maintainer,
* What led up to the situation?
unattended-upgrade upgrading wpasupplicant (2:2.10-15) over (2:2.10-12).
* What exactly did you do (or not do) that was effective (or
ineffec
Hi Samuel,
I can confirm that with version 8.2.1-1, installed today from Debian testing,
the segfault is *not* seen any longer.
As expected, I get now a regular file error when I specify an invalid path to
option "-D".
Feel free to close this bug.
Thanks
Package: curl
Version: 7.88.1-11
Severity: normal
X-Debbugs-Cc: in.cognit...@arcor.de
Dear Maintainer,
* What led up to the situation?
Me looking at the man page of curl and searching in it.
* What exactly did you do (or not do) that was effective (or
ineffective)?
Using my standard
Package: curl
Version: 7.88.1-11
Severity: normal
X-Debbugs-Cc: in.cognit...@arcor.de
Dear Maintainer,
* What led up to the situation?
Nothing in particular.
* What exactly did you do (or not do) that was effective (or
ineffective)?
curl -D /foo/bar/baz https://www.gnus.org
* Wh
Package: udisks2
Version: 2.10.0-3
Severity: normal
X-Debbugs-Cc: in.cognit...@arcor.de
Dear Maintainer,
* What led up to the situation?
Upgrade of package udisks2 from 2.9.4-4 to 2.10.0-3.
More precisely, unattended-upgrade did the following batch:
-
Package: firmware-iwlwifi
Version: 20230515-3
Severity: normal
X-Debbugs-Cc: in.cognit...@arcor.de
Dear Maintainer,
* What led up to the situation?
Upgrade of package firmware-iwlwifi to version 20230515-3, which provided
iwlwifi-ty-a0-gf-a0-74.ucode.
* What was the outcome of this action
Package: systemd
Version: 252.6-1
Severity: minor
X-Debbugs-Cc: in.cognit...@arcor.de
Dear Maintainer,
this happens on an up-to-date Debian testing system.
* What led up to the situation?
Executing command:
sudo systemd-run --quiet --user --machine jschmidt@ --wait --pipe --collect id
* Wha
I'm on Debian testing with package printer-driver-cups-pdf version 3.0.1-14.
I get broken output file names as well, and I think it is an upstream bug.
Here is my configuration as dumped by cups-pdf:
-- snip --
Thu Mar 9 14:50:11 2023 [DE
There is actually a much simpler repro case:
Format volume, create large file, fsck volume, boink:
farblos@sappc2:~$ sudo mkfs.vfat -n MCBACKUP /dev/sdc1
mkfs.fat 4.2 (2021-01-31)
farblos@sappc2:~$ sudo mount /dev/sdc1 /mnt
farblos@sappc2:~$ sudo truncate -s 4294967295 /mnt/bigfile
farblos@sap
Not sure whether and under which conditions you backport bugs known to be fixed in newer releases to stable releases. Anyway, probably it helps somebody searching BTS for this particular bug ...
11 matches
Mail list logo