Bug#1049332: alg: self-tests for stdrng using drbg_nopr_hmac_sha512 failed (rc=-22)

2023-09-15 Thread in . cognito35
Since reporting this issue I never got that error again in the journal. Feel free to close as "not reproducible".

Bug#1051992: wpasupplicant: unattended-upgrade reports tar errors while upgrading wpasupplicant

2023-09-15 Thread in . cognito35
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

Bug#1043340: curl -D /foo/bar/baz segfaults instead of exiting with error

2023-08-14 Thread in . cognito35
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

Bug#1043339: curl man page generated with HYPHEN chars (\u2010) where regular minus should be used

2023-08-09 Thread in . cognito35
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

Bug#1043340: curl -D /foo/bar/baz segfaults instead of exiting with error

2023-08-09 Thread in . cognito35
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

Bug#1041649: udisks2: udisksd report errors Error getting 'loop0' information: Failed to get status of the device loop0

2023-07-21 Thread in . cognito35
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: -

Bug#1041645: firmware-iwlwifi: Intel AX210 reports "WRT: Invalid buffer destination" after upgrade to version 74 ucode

2023-07-21 Thread in . cognito35
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

Bug#1034717: systemd-run --machine unpriv-user@ results in access denied errors reported in journal

2023-04-22 Thread in . cognito35
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

Bug#912993: printer-driver-cups-pdf: creates wrong filename using short title

2023-03-09 Thread in . cognito35
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

Bug#1001845: Update

2021-12-17 Thread in . cognito35
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

Bug#1001836: Update

2021-12-17 Thread in . cognito35
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 ...