Bug#1076372: linux-image-6.11.5+debian+tj: Diagnostic steps

2024-10-30 Thread Tj
Package: linux-image-6.11.5+debian+tj Followup-For: Bug #1076372 X-Debbugs-Cc: tj.iam...@proton.me Following up from the kernel team discussion this evening that I only caught the tail-end of I've reviewed this report and have the following suggestions and observations. It would be good t

Bug#1085184: apt: Alternative approach?

2024-10-30 Thread Tj
Package: apt Followup-For: Bug #1085184 X-Debbugs-Cc: tj.iam...@proton.me I helped diagnose this same issue last evening in the Debian Matrix room and independently found the same causes as JAK reports. To my mind the entire approach of trying to guess ahead of time how much space will be require

Bug#1085262: Broken: ACPI DSDT loading does not work

2024-10-17 Thread Tj
Package: initramfs-tools Version: 0.143~tj01 Severity: normal X-Debbugs-Cc: tj.iam...@proton.me The current ACPI DSDT code cannot possibly work. 1. The path DSDT.aml is stored in is not searched by the kernel 2. Kernel will not over-ride an ACPI table after PID 1 starts 3. File needs to be in an

Bug#1077452: picolibc: FTBFS: make[1]: *** [debian/rules:134: override_dh_auto_test] Error 104

2024-09-10 Thread Tj
> Since Keith seems to still be busy, I'm wondering how to best fix this FTBFS > via an NMU without doing a huge change like importing a new upstream release. > > What do you think of doing a minimal NMU which just temporarily (until a new > upstream version is packaged) disables the tests? In

Bug#1077452: picolibc: FTBFS: make[1]: *** [debian/rules:134: override_dh_auto_test] Error 104

2024-09-05 Thread Tj
Source: picolibc Followup-For: Bug #1077452 X-Debbugs-Cc: tj.iam...@proton.me The package needs updating to the current (2024-09-05) upstream HEAD /and/ build-testing via sbuild to ensure it builds and tests correctly. There are an entire series of TIMEOUT issues in the arm and aarch64 tests that

Bug#1080524: QUILT_PATCHES, QUILT_SERIES ignored if .pc/.quilt_{series,patches} exist

2024-09-05 Thread Tj
Package: quilt Version: 0.67+really0.66-1 Severity: normal X-Debbugs-Cc: tj.iam...@proton.me It is confusing that despite the man-page describing the environment over-rides that can be set either on command-line or via ~/.quiltrc, etc., these are ignored if there are already files in ./pc/ contain

Bug#1079835: Regression: QEMU 9 makes picolibc FTBFS (failing tests)

2024-08-29 Thread Tj
Source: qemu-system-arm Followup-For: Bug #1079835 X-Debbugs-Cc: tj.iam...@proton.me With the failed sbuild environment still available one can debug the FAIL or TIMEOUT test binaries from outside: $ base=/srv/NAS/Sunny/SourceCode/builds/tmp.sbuild.voDevnvR A FAIL test: $ sudo qemu-system-arm

Bug#1079443: fts_build() calling __getdents breaks 32bit on 64bit

2024-08-24 Thread Tj
Source: glibc Followup-For: Bug #1079443 X-Debbugs-Cc: tj.iam...@proton.me This seems to confirm the cause: debvm$ sudo chroot debvm.fs apt-get install libc6-dev debvm$ grep -rn 'define .*TIMESIZE' debvm.fs/usr/include debvm.fs/usr/include/arm-linux-gnueabihf/bits/timesize.h:20:#define __TIMESIZE

Bug#1079443: fts_build() calling __getdents breaks 32bit on 64bit

2024-08-24 Thread Tj
Source: glibc Followup-For: Bug #1079443 X-Debbugs-Cc: tj.iam...@proton.me fts_* functions, and fts_read() -> fts_build() end up calling > sysdeps/unix/sysv/linux/readdir.c: #if !_DIRENT_MATCHES_DIRENT64 __readdir_unlocked() So follow this back to see why it is (not) set (on armhf) > sysdeps/

Bug#1079443: fts_build() calling __getdents breaks 32bit on 64bit

2024-08-24 Thread Tj
Source: glibc Followup-For: Bug #1079443 X-Debbugs-Cc: tj.iam...@proton.me To ensure we capture all relavent info I'm copying here some test results Chris produced using a custom-written executable. Using emulation: $ sudo chroot /mnt/e4/armhf /pdents-armhf fd = 3 dp = 0x403190 entry 0 ino 103

Bug#1079443: glibc: Change bug title

2024-08-24 Thread Tj
Source: glibc Followup-For: Bug #1079443 X-Debbugs-Cc: tj.iam...@proton.me Control: retitle -1 fts_build() calling __getdents breaks 32bit on 64bit mjt identified that as well as this report's armhf emulation on 64 bit host he can reproduce the apparent problem with i386: Quotes: see comment #12

Bug#1079443: dracut-install ... -m =drivers/XXX is ignored

2024-08-24 Thread Tj
Package: dracut-install Followup-For: Bug #1079443 X-Debbugs-Cc: tj.iam...@proton.me Control: reassign -1 glibc After considerable discussion and investigation on IRC #debian-devel on 20240824 after 1000 UTC the consensus is this is a glibc issue with the (rarely used) fts_* functions calling __ge

Bug#1079443: dracut-install ... -m =drivers/XXX is ignored

2024-08-24 Thread Tj
Package: dracut-install Followup-For: Bug #1079443 X-Debbugs-Cc: tj.iam...@proton.me Control: affects -1 + qemu glibc I think this will need re-assigning to another package but not clear which as yet. Thanks to Chris's investigations in the last few hours he's identified a couple of bug reports t

Bug#1079443: dracut-install ... -m =drivers/XXX is ignored

2024-08-23 Thread Tj
Package: dracut-install Followup-For: Bug #1079443 X-Debbugs-Cc: tj.iam...@proton.me Further debugging leads to the getdents64 syscall returning -1 at https://sources.debian.org/src/glibc/2.39-7/sysdeps/unix/sysv/linux/getdents.c/?hl=56#L58 I'm including a dump of the gdb session including my at

Bug#1079443: dracut-install ... -m =drivers/XXX is ignored

2024-08-23 Thread Tj
Package: dracut-install Followup-For: Bug #1079443 X-Debbugs-Cc: tj.iam...@proton.me I've managed to set up a gdb-multilib debug session and have been single-stepping through the glibc fts_* code that seems to be affected. As Chris has found that xfs file-system doesn't seem to be affected but ex

Bug#1079443: dracut-install ... -m =drivers/XXX is ignored

2024-08-23 Thread Tj
Package: dracut-install Followup-For: Bug #1079443 X-Debbugs-Cc: tj.iam...@proton.me Control: affects -1 + debvm Results of further diagnosis. First, discovered that -v overrides --debug: removing -v from the command line allowed debug messages and removing -o means any missing modules causes an

Bug#1079443: dracut-install ... -m =drivers/XXX is ignored

2024-08-23 Thread Tj
Package: dracut-install Version: 103-1.1 Severity: important X-Debbugs-Cc: tj.iam...@proton.me debvm in the last week is failing armhf/armel build tests because virtio_blk kernel module is not installed in the initrd.img. This was reported and help requested by Helmut Grohne on IRC #debian-devel.

Bug#1077190: curl: pkgconf --cflags libcurl failing due to missing deps

2024-07-26 Thread Tj
Source: curl Followup-For: Bug #1077190 X-Debbugs-Cc: tj.iam...@proton.me This is a result of upstream commit f057de5a1a which results in libcurl.pc having: Name: libcurl URL: https://curl.se/ Description: Library to transfer files with ftp, http, etc. Version: 8.9.0 Requires: Requires.private:

Bug#989229: Fw: Re: Bug#989229: grub-install: warning: Cannot read EFI Boot* variables.

2024-07-17 Thread Tj
The reporter "retired" the PC but directly replied to me; copying in for completeness. --- Forwarded Message --- From: Joseph Maher Date: On Wednesday, 17 July 2024 at 07:22 Subject: Re: Bug#989229: grub-install: warning: Cannot read EFI Boot* variables. To: Tj > Th

Bug#1076438: taskwarrior: If moving to v3.x please retain v2.x

2024-07-16 Thread Tj
Package: taskwarrior Version: 2.6.2+dfsg-1 Severity: wishlist X-Debbugs-Cc: tj.iam...@proton.me Since v3.0 was recently released I expect there will be a move to it at some point. I'd like to request keeping v2.x and v3.x in parallel for the following reasons (or at least until they are no longer

Bug#989229: grub-install: warning: Cannot read EFI Boot* variables.

2024-07-16 Thread Tj
Source: linux Followup-For: Bug #989229 X-Debbugs-Cc: tj.iam...@proton.me Control: tag -1 moreinfo This is in all probability a system (manufacturer's) firmware bug. The kernel is doing what it is designed to do; that is, try to recover from the system's UEFI Runtime Services causing a Page Fault.

Bug#1075713: linux: Change to firmware fb device parent broke X fbdev

2024-07-15 Thread Tj
Package: linux-image-6.9.7+debian+tj Followup-For: Bug #1075713 X-Debbugs-Cc: tj.iam...@proton.me It does help to include the references! [0] https://gitlab.freedesktop.org/xorg/xserver/-/issues/1714

Bug#1075713: linux: Change to firmware fb device parent broke X fbdev

2024-07-15 Thread Tj
Package: linux-image-6.9.7+debian+tj Followup-For: Bug #1075713 X-Debbugs-Cc: tj.iam...@proton.me This is best fixed in xorg-server. I've opened an upstream issue [0] and sent the patch to xorg-devel@. In the meantime here's a patch tested with kernel v6.8.12 and v6.9.7 using

Bug#1075713: Regression: firmware/sysfb.c device path

2024-07-15 Thread Tj
On Monday, 15 July 2024 at 10:22, Thomas Zimmermann wrote: > We should definitely get your patch into the Xorg upstream. Working on that now.

Bug#1075713: Regression: firmware/sysfb.c device path

2024-07-15 Thread Tj
On Monday, 15 July 2024 at 07:44, Thomas Zimmermann wrote: > > See hw/xfree86/fbdevhw/fbdevhw.c::fbdev_open() > > > > https://gitlab.freedesktop.org/xorg/xserver/-/blob/master/hw/xfree86/fbdevhw/fbdevhw.c?ref_type=heads#L381 > > > Amazing debugging skills! > > The patch that causes the regression

Bug#1072004: linux: regression in the 9p protocol in 6.8 breaks autopkgtest qemu jobs (affecting debci)

2024-07-14 Thread Tj
Package: linux-image-6.9.7+debian+tj Followup-For: Bug #1072004 X-Debbugs-Cc: tj.iam...@proton.me I've completed 10 successful passes of the autopkgtest reproducer with the proposed patch in the kernel bugzilla from Dominique Martinet on current mainline, so with luck that might squeeze

Bug#1075713: Regression: firmware/sysfb.c device path

2024-07-13 Thread Tj
The recent commits to add the parent device path broke Debian's kvm based QA workers for testing installer ISOs after a kernel upgrade from v6.8.12 to v6.9.7. For the details: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075713 It took some time to track it down since the superficial sym

Bug#1075713: linux: D-I's X fails to start under kvm -vga qxl

2024-07-13 Thread Tj
Package: linux-image-6.9.7+debian+tj Followup-For: Bug #1075713 X-Debbugs-Cc: tj.iam...@proton.me After reverting the recent sysfb commits: linux$ git l -n 15 e932a4281dfd4 2024-07-13 17:27:49 +0100 N Tj Revert "firmware/sysfb: Set firmware-framebuffer parent device" c16bbb2e6863d 202

Bug#1075713: linux: D-I's X fails to start under kvm -vga qxl

2024-07-13 Thread Tj
Source: debian-installer Followup-For: Bug #1075713 X-Debbugs-Cc: tj.iam...@proton.me Finally managed to build the v6.8.12 initrd; process is quite convoluted due to having to manually identify, install, and depmod modules. However... ... it works (both with and without a hard-coded xorg.conf fra

Bug#1075713: linux: D-I's X fails to start under kvm -vga qxl

2024-07-09 Thread Tj
Source: debian-installer Followup-For: Bug #1075713 X-Debbugs-Cc: tj.iam...@proton.me Creating a modified non-ISO bootable image that can be interactively debugged proved a trial and a half, but after creating a custom initrd and modifying several of the d-i scripts that mess with console I've fin

Bug#1075844: xserver-xorg-video-fbdev: ./revert-ae0aeffae665746.diff in source package

2024-07-06 Thread Tj
Package: xserver-xorg-video-fbdev Version: 1:0.5.0-2 Severity: minor X-Debbugs-Cc: tj.iam...@proton.me Whilst researching a bug in other packages and inspecting how fbdev interacts with them I found the source package (.diff.gz) fetched with dget contains the file ./revert-ae0aeffae665746.diff I

Bug#1075713: linux: D-I's X fails to start under kvm -vga qxl

2024-07-05 Thread Tj
Source: debian-installer Followup-For: Bug #1075713 X-Debbugs-Cc: tj.iam...@proton.me To be explicit this issue is not related to the QXL driver; that is a red herring. The problem is the fbdev driver is failing to handle the kernel's /dev/fb0. Digging further I compared the kernel configs and se

Bug#1075713: debian-installer: Not caused by kvm version

2024-07-05 Thread Tj
Source: debian-installer Version: 20230607+deb12u6 Followup-For: Bug #1075713 X-Debbugs-Cc: tj.iam...@proton.me Thank-you to Philip for pointing me to the OpenQA assets and details. I had explored those pages but totally missed that those words were actually hyperlinks to additional page content!

Bug#1075713: linux: D-I's X fails to start under kvm -vga qxl

2024-07-04 Thread Tj
Source: debian-installer Followup-For: Bug #1075713 X-Debbugs-Cc: tj.iam...@proton.me I've done some further research via debian-installer repo, build logs, and inspecting fb-modules-*-amd64-di packages. Focusing on just 6.8.12-1 and 6.9.7-1 I cannot see any difference in the ISO builds. That is,

Bug#1075713: linux: ISO missing qxl.ko.xz kernel module

2024-07-03 Thread Tj
Source: linux Followup-For: Bug #1075713 X-Debbugs-Cc: tj.iam...@proton.me debian-b...@lists.debian.org I've inspected the arch-latest amd64 ISO from: https://get.debian.org/images/daily-builds/daily/arch-latest/amd64/iso-cd/debian-testing-amd64-netinst.iso It is missing drivers/gpu/drm/qxl/qxl.

Bug#1074404: apt-cacher-ng: 302 Location redirect fails for snapshot.debian.org

2024-06-27 Thread Tj
path-only is pre-empted by the // protocol detection. This revised patch moves the existing path detection before // protocol but ensures the second character is not also '/'. >From dcedac77092b08c358cb9017767c70025f92aee4 Mon Sep 17 00:00:00 2001 From: Tj Date: Wed, 26 Jun 2024 0

Bug#1074404: apt-cacher-ng: 302 Location redirect fails for snapshot.debian.org

2024-06-27 Thread Tj
SIGNED MESSAGE- Hash: SHA256 Origin: Debian Label: Debian Suite: unstable Codename: sid Changelogs: https://metadata.ftp-master.debian.org/changelogs/@CHANGEPATH@_changelog Date: Mon, 17 Jun 2024 02:15:25 UTC Valid-Until: Mon, 24 Jun 2024 02:15:25 UTC >From 51961164a89c562b333efcbc3dcd8537

Bug#1067462: ERROR: Failed to create organization

2024-03-21 Thread Tj
. -- System Information: Debian Release: 12.5 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.6.7+debian+tj (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=

Bug#1067444: FileNotFoundError: [Errno 2] ... /usr/lib/python3/dist-packages/bugwarrior/docs/configuration.rst

2024-03-21 Thread Tj
such file or directory: '/home/tj/.config/bugwarrior/bugwarriorrc' $ mv ~/.config/bugwarrior{.bak,} $ bugwarrior-pull CRITICAL:bugwarrior.command:Could not load configuration. Maybe you have not created a configuration file. FileNotFoundError: [Errno 2] No such file or directory: &#

Bug#1066883: alg: ecdh-nist-p256: test failed on vector 2, err=-14

2024-03-14 Thread Tj
sort -u version 6.7.0-rc5+debian+tj version 6.7.1+debian+tj version 6.7.4+debian+tj version 6.8.0+debian+tj crypto algo self-tests 'alg: ecdh-nist-p256: test failed on vector 2, err=-14 -14 is "EFAULT 14 / Bad address */ and the log shows Modules linked in: ecdh_generic(+) ... whe

Bug#1064283: nftlb: Upstream has moved

2024-02-19 Thread Tj
Source: nftlb Version: 1.0.7-1 Severity: important Tags: upstream The upstream repo was archived read-only in January 2024. From a netfilter-devel mailing-list post in September 2023 it appears the upstream moved: https://lore.kernel.org/netfilter-devel/CAF90-Wg4NTjfUE7pomw8VnQAjSQC2OXa5FQFH_XwK=

Bug#1064008: vncsnapshot: Recommends vnc4server but unable to find a Provides: vnc4server

2024-02-15 Thread Tj
Source: vncsnapshot Version: 1.2a-5.2 Severity: normal Whilst investigating guacamole-server I noticed that libguac-client-vnc0 and vncsnapshot recommends "vnc4server" but I've been unable to find any packages that provide that. ~/tmp/debian-sid$ awk '/^Package:/{p=$0} /^Recommends: .*vnc4serve

Bug#1064007: Recommends vnc4server but cannot find any package doing Provides: vnc4server

2024-02-15 Thread Tj
Package: libguac-client-vnc0 Version: 1.3.0-1.1+b3 Severity: normal Whilst investigating guacamole-server I noticed that libguac-client-vnc0 recommends "vnc4server" but I've been unable to find any packages that provide that. ~/tmp/debian-sid$ awk '/^Package:/{p=$0} /^Recommends: .*vnc4server/{pr

Bug#1058638: grub-installer: boot fails: $bootdev empty [BIOS/MBR, Vista, 2 disks]: Installing grub on ''

2023-12-13 Thread Tj
Source: grub-installer Version: 1.194 Followup-For: Bug #1058638 I fetched the proposed patch and applied it to grub-installer inside the installer and can confirm it solved this issue. syslog now shows "grub-installer: info: Installing grub on '/dev/vdb' and examining sector 0 of the disk image

Bug#1058638: grub-installer: boot fails: $bootdev empty [BIOS/MBR, Vista, 2 disks]: Installing grub on ''

2023-12-13 Thread Tj
Source: grub-installer Version: 1.194 Followup-For: Bug #1058638 I think this may be due to the same cause as #1035096 and possibly also #1035085

Bug#1058638: grub-installer: boot fails: $bootdev empty [BIOS/MBR, Vista, 2 disks]: Installing grub on ''

2023-12-13 Thread Tj
Source: grub-installer Version: 1.194 Severity: important Tags: d-i Whilst helping user "mavaviij" in matrix Debian room I was able to reproduce in a virtual machine a bug that causes the Debian install to fail to boot with a blinking cursor after install. After a lot of code-chasing it appears t

Bug#1053101: qemu-user-static: Remove --disable-pie

2023-11-26 Thread Tj
mu (1:7.2+dfsg-7+deb12u2.1) UNRELEASED; urgency=medium + + * user-static: build position independent executable. Closes: #1053101. + + -- Tj Sun, 26 Nov 2023 09:26:24 + + qemu (1:7.2+dfsg-7+deb12u2) bookworm; urgency=medium * d/rules: add the forgotten --enable-virtfs for the xen build.

Bug#1053101: qemu-user-static: Without PIE emulator and targets map to same address

2023-11-25 Thread Tj
Package: qemu-user-static Version: 1:7.2+dfsg-7+deb12u2 Followup-For: Bug #1053101 After building without `--disable-pie` and observing differences and results I suspect the cause is something that is so obvious I missed it! The emulator - when totally static - maps to 0x0004 itself. Then in

Bug#1056727: qemu-user-static: FTBFS when linux-libc-dev /usr/include/linux/btrfs.h installed

2023-11-25 Thread Tj
Package: qemu-user-static Version: 1:7.2+dfsg-7+deb12u2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Whilst investigating #1053101 and needing to build the qemu-aarch64-static without `--disable-pie` I hit an FTBFS with: qemu-7.2+dfs

Bug#1053101: qemu-user-static: Trace results

2023-11-25 Thread Tj
Package: qemu-user-static Version: 1:7.2+dfsg-7+deb12u2 Followup-For: Bug #1053101 Sharing some further in-depth debugging results. Everything seems to point to the executables with ELF type 3 (Linux) not marked as PIE suffering the same fate. The address that faults is always 0x40 so I'm hunt

Bug#1053101: qemu-user-static: PIE and mmap()

2023-11-24 Thread Tj
Package: qemu-user-static Version: 1:7.2+dfsg-7+deb12u2 Followup-For: Bug #1053101 Debugging across an architecture boundary when the architecture is emulated is... painful! However, as I dig in from both sides this is pointing to an issue with PIE handling. E.g.: $ qemu-aarch64-static -strace s

Bug#1053101: qemu-user-static: PIE conflicts?

2023-11-24 Thread Tj
Package: qemu-user-static Version: 1:7.2+dfsg-7+deb12u2 Followup-For: Bug #1053101 I forgot to note that Michael's observation that building qemu-user-static without --disable-pie might reveal a conflict between the emulator and target linking: # file /usr/bin/ls /usr/bin/ls: ELF 64-bit LSB pie e

Bug#1053101: qemu-user-static: Host debug trace

2023-11-24 Thread Tj
Package: qemu-user-static Version: 1:7.2+dfsg-7+deb12u2 Followup-For: Bug #1053101 Initially I noticed the ELF types shown for ls (0 a.k.a. SYSV) and aarch64-linux-gnu-g++-13 (3 a.k.a. GNU/Linux) are different. This is octet offset 7 of the ELF header, e_ident[EI_OSABI]. When it is 3 the followi

Bug#1040373: lsof does not work correctly with btrfs subvolumes

2023-11-02 Thread Tj
Package: lsof Version: 4.95.0-1 Followup-For: Bug #1040373 This seems to be related to upstream issue: https://github.com/lsof-org/lsof/issues/152 "LTlock fails on btrfs" Small test-case: SUBVOL_FILE="/mnt/machines_old/test"; sudo findmnt -oTARGET,SOURCE,FSTYPE,MAJ:MIN "${SUBVOL_FILE%/*}" su

Bug#1054040: cups: 'make clean' fails in man/Makefile - master file 'backend.7' does not exist

2023-10-16 Thread Tj
Package: cups Version: 2.4.2-3+deb12u4 Severity: minor Tags: l10n Whilst cherry-picking an upstream commit to Bookworm (2.4.2-3+deb12u4) to fix #1039983 I discovered an 'un'build failure doing either: debian/rules clean make clean ... Cleaning in man... make[3]: Entering directory '/srv/NAS/Sunny

Bug#1008092: antiword: Possible related RedHat-reported buffer overflow

2023-10-09 Thread Tj
Package: antiword Followup-For: Bug #1008092 A package search on the RedHat bugzilla shows other reports including tracking bugs for the referenced (security) bug #2064638. https://bugzilla.redhat.com/buglist.cgi?component=antiword&product=Fedora It might be worth contacting Adrian Reber for inf

Bug#1008092: antiword: Possible unsanitised input data

2023-10-09 Thread Tj
Package: antiword Followup-For: Bug #1008092 As requested here's a summary of one potential unsanitised input data issue that may be leading to this (or other) error(s). `vSetSummaryInfoOLE()` calls `pucAnalyseSummaryInfoHeader()` that does: `if (!bReadBuffer(pFile, ... aucBuffer, ...) ... retur

Bug#1052290: cryptsetup-initramfs: askpass is not executed; cryptroot-unlock fails

2023-09-20 Thread Tj
On 20/09/2023 08:35, Guilhem Moulin wrote: Control: tag -1 moreinfo On Tue, 19 Sep 2023 at 22:39:40 +0100, Tj wrote: Error: Timeout reached while waiting for askpass. After using `break=mount` and investigating with `sh -x /bin/cryptsetup-unlock` it seems it fails because it is not finding

Bug#1052290: cryptsetup-initramfs: askpass is not executed; cryptroot-unlock fails

2023-09-19 Thread Tj
Package: cryptsetup-initramfs Version: 2:2.6.1-4~deb12u1 Severity: important Discovered this whilst working on a relatively simple test of multiple LUKS block devices for LUKS.0 + LUKS.1 > btrfs RAID1 @/ - that is a BTRFS RAID1 using 2 LUKS block devices. Two files represent SSD1 and SSD2, which

Bug#1051535: linux: HW_RANDOM_TPM disabled due to IMA=y

2023-09-09 Thread Tj
Source: linux Severity: normal Working with a Debian user in Matrix channel #Debian where they report that the TPM hardware random number generator that was available in v5.10* series is missing from v6.1* series for the amd64 kernel. After examining the Kconfig options and the Debian configs I f

Bug#1051481: apt-cacher-ng: Illegal SRV name (underscore not valid except first character of label)

2023-09-08 Thread Tj
x27;) Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0+debian+tj (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked

Bug#1051479: squid-deb-proxy: Illegal SRV name (underscore not valid except first character of label)

2023-09-08 Thread Tj
;stable-debug'), (500, 'proposed-updates-debug'), (500, 'stable'), (100, 'proposed-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.1+debian+tj (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN, TAINT_OOT_M

Bug#1051477: dnssd: IPv6: fails to resolve services

2023-09-08 Thread Tj
chitecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.1+debian+tj (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /

Bug#1050786: cgget: buffer overflow detected; Aborted (core dumped)

2023-08-29 Thread Tj
2, si_uid=1000} --- +++ killed by SIGABRT (core dumped) +++ Aborted (core dumped) -- Package-specific info: -- System Information: Debian Release: 12.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable-debug'), (500, &#

Bug#1050719: debootstrap: Leaving wget-log* files in $PWD

2023-08-28 Thread Tj
table-security'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0+debian+tj (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED

Bug#1041647: Stepping back and checking basics

2023-07-21 Thread Tj
vainfo: VA-API version: 1.17 (libva 2.12.0) vainfo: Driver version: Mesa Gallium driver 22.3.6 for VERDE (, LLVM 15.0.6, DRM 2.50, 6.5.0-rc2+debian+tj+) vainfo: Supported profile and entrypoints VAProfileMPEG2Simple: VAEntrypointVLD VAProfileMPEG2Main

Bug#1041647: Stepping back and checking basics

2023-07-21 Thread Tj
:00.0: disabling GPU acceleration $ uname -r 6.4.3+debian+tj+

Bug#1041647: Further gdb debugging (more #2)

2023-07-21 Thread Tj
After solving the relative path issue I now have better info: (gdb) s __vaDriverInit_1_17 (ctx=0x555702b0) at ../src/gallium/frontends/va/context.c:123 123if (!ctx) (gdb) n 126drv = CALLOC(1, sizeof(vlVaDriver)); (gdb) n 127if (!drv) (gdb) n 130switch (ctx->d

Bug#1041647: Further gdb debugging (more)

2023-07-21 Thread Tj
The mesa-va-drivers-dbgsym package seems to have incorrect (relative to build) paths stored which prevents gdb showing the source lines when it has the path to the mesa-22.6.3 source, however by blindly stepping and then looking at the source it narrows down the cause: (gdb) s 126 in ../sr

Bug#1041647: Further gdb debugging

2023-07-21 Thread Tj
Using export LIBVA_MESSAGING_LEVEL=2; export LIBVA_DRIVER_NAME=radeonsi; gdb --directory . --directory ../libva-2.17.0 --directory ../mesa-22.3.6 --args /usr/bin/vainfo I've stepped through vainfo and focused on va_openDriver() which eventually leads to: (gdb) n libva info: Found init functi

Bug#1035842: Namespaces: Operation not permitted. Fails to setgroups due to EPERM

2023-05-09 Thread Tj
tem Information: Debian Release: 11.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Ar

Bug#1035558: Acknowledgement (libxml2-utils: xmllint ignores --output option and writes to stdout)

2023-05-05 Thread Tj
Apologies - email client didn't fill the correct address. This was a reply to bug #1035554 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035554 This can be closed!

Bug#1035554: libxml2-utils: xmllint ignores --output option and writes to stdout

2023-05-05 Thread Tj
I've done some follow-up debugging (on upstream git) to be sure the problem seems to exist upstream - unless I'm severely misunderstanding what --output is supposed to do. Anyhow; the trace shows it reaches doXPathDump(). Note that 'buf' is hard-coded to use stdout. The call to xmlOutputBufferC

Bug#1035558: libxml2-utils: xmllint ignores --output option and writes to stdout

2023-05-05 Thread Tj
Package: libxml2-utils I've done some follow-up debugging (on upstream git) to be sure the problem seems to exist upstream - unless I'm severely misunderstanding what --output is supposed to do. Anyhow; the trace shows it reaches doXPathDump(). Note that 'buf' is hard-coded to use stdout. The

Bug#1035554: libxml2-utils: xmllint ignores --output option and writes to stdout

2023-05-05 Thread Tj
Package: libxml2-utils Version: 2.9.10+dfsg-6.7+deb11u4 Severity: normal Tags: upstream xmllint is ignoring --output FILE option. I've done a debug run with gdb and it correctly reads the option and assigns its value to the 'output' variable but doesn't read that variable before writing the outp

Bug#1034628: netfilter-persistent: Does not support Netfilter rules!

2023-04-19 Thread Tj
Package: netfilter-persistent Version: 1.0.15 Severity: normal X-Debbugs-Cc: deb...@iam.tj Despite the package name, control file Description text, and man page there is no support for applying kernel Netfilter rules via nftables etc. This is misleading and causes confusion especially as there is

Bug#943343: fwupd: Workaround using dbus-broker

2023-02-02 Thread Tj
able-security'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.7-tj-7-g94868ba9f924 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF

Bug#971170: Possible cause?

2022-11-27 Thread Tj
I also see the same list of errors from sddm-greeter using the default KDE/Plasma Breeze theme on Bullseye. I'm not familiar with the KDE/Plasma QML theme system but I believe I've found a clue/cause. Almost all the errors are related to units.XXX but units isn't available and evaluates to N

Bug#1004154: Fwd: Bug#1004154: xserver-xorg-video-qxl: XOrg frequently crashes when using qxl driver: qxl(0): error doing QXL_ALLOC

2022-10-21 Thread TJ
On Sat, 12 Feb 2022 08:21:55 + Felix Leimbach wrote: I noticed that vgamem_mb was still low (32 MB). So I changed to this (slightly wasteful) command-line and am now running the latest kernel (5.15.0-3-amd64): -vga none -device qxl-vga,ram_size_mb=256,vgamem_mb=256,vram_size_mb=256,vram64

Bug#1005899: mplayer: should not release with bookworm

2022-10-21 Thread Tj
On Wed, 16 Mar 2022 20:09:59 +0100 Diederik de Haas wrote: On 16 Feb 2022 23:25:00 +0100 Sebastian Ramacher wrote: > Source: mplayer > Version: 2:1.4+ds1-3 > Severity: serious > Tags: sid bookworm > > I think we should not include mplayer in bookworm. > mpv is a worthy replacement for mplayer

Bug#1016885: obs-studio: IPv6 bind address handling totally broken

2022-08-08 Thread Tj
Package: obs-studio Version: 26.1.2+dfsg1-2 Severity: wishlist Due to a bug in upstream all IPv6 address handling is broken. The specific problem is incorrect setting of sin_addr for calls to inet_ntop()/inet_pton() resulting in broken string representation of IPv6 addresses, which percolates

Bug#991625: debootstrap: extra-suites= broken; attempts Package.* fetches from primary suite

2021-07-28 Thread TJ
ubuntu-archive-keyring -- no debconf information -- commit 23bb0a9f3c39b1f23f6c27bd7e8e85f43d7a0316 (HEAD -> master) Author: Tj Date: Wed Jul 28 21:27:01 2021 +0100 fix: download correct extra-suites Packages files diff --git a/functions b/functions index 09d93f4..ec34d84 100644

Bug#637076: ProFTPD file uploads and UserOwner

2021-06-21 Thread TJ Saunders
I believe that the scenario described here: http://bugs.proftpd.org/show_bug.cgi?id=4418#c5 might capture/describe this bug, in which case, it would fall under "working as expected". TJ

Bug#965262: rc.local/FAISERVER fails due to changes in FAI installer

2020-07-18 Thread Tj (Elloe)
Package: fai-doc Version: 5.8.4 Severity: normal When using the FAI installer ISO to create the master server (static and DHCP server) booting the installed instance results in errors from the /etc/rc.local script. This script appears to be copied from fai-doc /usr/share/doc/fai-doc/examples/simp

Bug#926078: ITP: node-zen-observable -- implementation of observables for javascript

2019-03-31 Thread amrithaa tj
Package: wnpp Severity: wishlist Owner: Amrithaa.T.J X-Debbugs-CC: debian-de...@lists.debian.org * Package name: node-zen-observable Version : 0.8.13 Upstream Author : Microsoft corp. * URL : https://github.com/zenparsing/zen-observable * License : Expat Prog

Bug#916967: dwardump: passing any options prevents output

2018-12-20 Thread Tj
Package: dwarfdump Version: 20180809-1 Severity: important Whilst using dwarfdump (amd64 build) on MIPS ELF files I discovered that adding any command-line options (such as '-v' or '-x abi=mips') somehow prevents the program from writing any output. I then tried it on x86_64 ELF files, and on an

Bug#880993: enable http2 protocol when http2 module is enabled

2018-09-11 Thread TJ
I second this. I was expecting something of this sort when I ran "a2enmod http2" and was surprised not to find an accompanying .conf.

Bug#891340: pssh: Update upstream to forked maintained repo

2018-02-24 Thread Tj
Package: pssh Version: 2.3.1-1 Severity: important Tags: upstream Dear Maintainer, * What led up to the situation? Upstream source was originally moved to code.google.com which was discontinued. Original authors seem to have stopped caring around 2013. A forked new upstream is at https://gith

Bug#626524: DefaultAddress not obeyed when SocketBindTight is off

2017-02-21 Thread TJ Saunders
ltServer directive is for. Thus if your "SocketBindTight on" configuration is not causing clients to receive the "no server available to handle request" when they try to connect to an unconfigured IP address/port, then it says that your proftpd.conf is using DefaultServer somewhere. Cheers, TJ

Bug#336001: proftpd: improving documentation

2017-02-21 Thread TJ Saunders
Done; see: http://www.proftpd.org/docs/modules/mod_core.html#MaxInstances Cheers, TJ

Bug#691617: mod_ban fails to handle unknown ctrl commands correctly (Bug 691617)

2017-01-21 Thread TJ Saunders
This issue with mod_ban was reported separately upstream, and fixed there; see: http://bugs.proftpd.org/show_bug.cgi?id=3866 Cheers, TJ

Bug#794737: Incorrect (ppc64le) binfmt prevents execution of statically linked executables

2015-08-05 Thread TJ
Package: qemu-user-binfmt Version: 1:2.1+dfsg-12+deb8u1 This likely affects all releases and other architectures. I was helping a user on IRC #debian who was having problems completing the build of a PPC64LE chroot on amd64. The specific problem was early failure of "/debootstrap/debootstrap

Bug#734390: isomaster: El Torito boot image corrupted by truncation

2014-01-06 Thread TJ
ze in El Torito boot catalog Author: TJ Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+bug/1266461 Forwarded: yes Last-Update: 2014-01-06 Index: isomaster/bk/bkWrite.c === --- isomaster.orig/bk/bkWrite.c 2014-01-06 15:17:49.

Bug#716974: Can't locate File/Path.pm in @INC

2013-07-15 Thread TJ
Package: sysv-rc Version: 2.88dsf-42 Using pbuilder and deboostrap to create a 'sid' pbuilder from Ubuntu 13.04 I hit what looks to be a dependency issue as util-linux is being unpacked. I have a customised ~/.pbuilderrc to allow me to build Debian releases on Ubuntu which is run thus: $ sudo B

Bug#573070: ITP: hivex -- Windows Registry "hive" extraction library

2010-04-01 Thread TJ
* Package name: hivex Version : 1.2.1 Upstream Author : R. Jones * URL : http://git.annexia.org/?p=hivex.git;a=summary http://libguestfs.org/download/ * License : LGPL 2.1 Programming Lang: C Description : Windows Registry "hive" extra

Bug#541100: Updates to patches

2009-09-17 Thread TJ
I attached an incorrect set of patches to my earlier email. This is the correct set for: debian/patches/icedtea-plugin-use-runtime-nsIProcess-IID.diff debian/rules Apply from the source package's base directory. As before, the changelog entry is: openjdk-6 (6b14-1.4.1-0ubuntu12~tj~

Bug#541100: Cause found, working patch created.

2009-09-17 Thread TJ
g the same patch to this report. The patch needs adding to debian/rules but as the Debian and Ubuntu packages diverge slightly due to security CVE patches I won't attach a debdiff; instead I've attached a second patch. The Ubuntu changelog entry reads: openjdk-6 (6b14-1.4.1-0ubunt

Bug#525969: udev reports the usage of an invalid parameter '-s'

2009-04-28 Thread tj
Package: udev Version: 0.141-1 Severity: critical Justification: breaks the whole system udev reports an invalid parameter '-s'. this doesn't happen with version 0.125-6 of udev. on the log i seen multipathd reporting error when calling scsi_id, for example: "Apr 28 09:27:25 info multipathd: err

Bug#514358: pdebuild host --debbuildopts inherited by target pbuild

2009-02-08 Thread TJ
On Mon, 2009-02-09 at 00:02 +0900, Junichi Uekawa wrote: > Hmm > > IMO, That's a feature, not a bug. If this is really biting people, I > might consider adding that... A feature to break the expected functionality? I would agree with you *if* dpkg-source hadn't changed the semantics of -I in

Bug#514358: pdebuild host --debbuildopts inherited by target pbuild

2009-02-06 Thread TJ
2009-02-06 16:20:57.0 + @@ -1,3 +1,9 @@ +pbuilder (0.183ubuntu2) jaunty; urgency=low + + * Don't pass host --debbuildopts to target (LP: #326216) + + -- TJ Fri, 06 Feb 2009 16:30:00 + + pbuilder (0.183ubuntu1) jaunty; urgency=low * Merge with Debian unstable. Rem

  1   2   >