Bug#1063910: nvidia-detect fails to detect 470-series devices
Package: nvidia-detect Version: 525.147.05-6~deb12u1 Severity: normal Dear Maintainer, $ grep 10DE128B /usr/share/nvidia/*.ids /usr/share/nvidia/nvidia-legacy-390xx.ids:10DE128B /usr/share/nvidia/nvidia-tesla-418.ids:10DE128B /usr/share/nvidia/nvidia-tesla-440.ids:10DE128B /usr/share/nvidia/nvidia-tesla-450.ids:10DE128B /usr/share/nvidia/nvidia-tesla-460.ids:10DE128B /usr/share/nvidia/nvidia-tesla-470.ids:10DE128B $ nvidia-detect 10DE128B Checking driver support for PCI ID [10de:128B] Your card is only supported by the Tesla 418 drivers series, which is only available up to bullseye. In the script, it looks like VERSIONS[471] is set, but never checked. Incomplete merge of tesla ids? -- Package-specific info: uname -a: Linux asdf 6.1.0-18-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.76-1 (2024-02-01) x86_64 GNU/Linux /proc/version: Linux version 6.1.0-18-amd64 (debian-ker...@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC Debian 6.1.76-1 (2024-02-01) /proc/driver/nvidia/version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.147.05 Wed Oct 25 20:27:35 UTC 2023 GCC version: gcc version 12.2.0 (Debian 12.2.0-14) lspci 'display controller [030?]': 26:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP108 [GeForce GT 1030] [10de:1d01] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP108 [GeForce GT 1030] [3842:6339] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: nvidia Kernel modules: nvidia dmesg: Device node permissions: crw-rw+ 1 root video 226, 0 Feb 12 18:07 /dev/dri/card0 crw-rw+ 1 root render 226, 128 Feb 12 18:07 /dev/dri/renderD128 crw-rw-rw- 1 root root 195, 254 Feb 12 18:07 /dev/nvidia-modeset crw-rw-rw- 1 root root 195, 0 Feb 12 18:07 /dev/nvidia0 crw-rw-rw- 1 root root 195, 255 Feb 12 18:07 /dev/nvidiactl /dev/dri/by-path: total 0 lrwxrwxrwx 1 root root 8 Feb 12 18:07 pci-:26:00.0-card -> ../card0 lrwxrwxrwx 1 root root 13 Feb 12 18:07 pci-:26:00.0-render -> ../renderD128 video:x:44: Alternative 'nvidia': nvidia - auto mode link best version is /usr/lib/nvidia/current link currently points to /usr/lib/nvidia/current link nvidia is /usr/lib/nvidia/nvidia slave nvidia--libEGL_nvidia.so.0-x86_64-linux-gnu is /usr/lib/x86_64-linux-gnu/libEGL_nvidia.so.0 slave nvidia--libGLX_nvidia.so.0-x86_64-linux-gnu is /usr/lib/x86_64-linux-gnu/libGLX_nvidia.so.0 slave nvidia--libcuda.so-x86_64-linux-gnu is /usr/lib/x86_64-linux-gnu/libcuda.so slave nvidia--libcuda.so.1-x86_64-linux-gnu is /usr/lib/x86_64-linux-gnu/libcuda.so.1 slave nvidia--libglxserver_nvidia.so is /usr/lib/nvidia/libglxserver_nvidia.so slave nvidia--libnvidia-cfg.so.1-x86_64-linux-gnu is /usr/lib/x86_64-linux-gnu/nvidia/libnvidia-cfg.so.1 slave nvidia--libnvidia-ml.so-x86_64-linux-gnu is /usr/lib/x86_64-linux-gnu/libnvidia-ml.so slave nvidia--libnvidia-ml.so.1-x86_64-linux-gnu is /usr/lib/x86_64-linux-gnu/libnvidia-ml.so.1 slave nvidia--libnvidia-ptxjitcompiler.so.1-x86_64-linux-gnu is /usr/lib/x86_64-linux-gnu/libnvidia-ptxjitcompiler.so.1 slave nvidia--libvdpau_nvidia.so.1-x86_64-linux-gnu is /usr/lib/x86_64-linux-gnu/vdpau/libvdpau_nvidia.so.1 slave nvidia--nv-control-dpy is /usr/bin/nv-control-dpy slave nvidia--nvidia-application-profiles-key-documentation is /usr/share/nvidia/nvidia-application-profiles-key-documentation slave nvidia--nvidia-blacklists-nouveau.conf is /etc/nvidia/nvidia-blacklists-nouveau.conf slave nvidia--nvidia-bug-report.sh is /usr/lib/nvidia/nvidia-bug-report.sh slave nvidia--nvidia-debugdump is /usr/bin/nvidia-debugdump slave nvidia--nvidia-drm-outputclass.conf is /etc/nvidia/nvidia-drm-outputclass.conf slave nvidia--nvidia-load.conf is /etc/nvidia/nvidia-load.conf slave nvidia--nvidia-modprobe.conf is /etc/nvidia/nvidia-modprobe.conf slave nvidia--nvidia-options.conf is /etc/modprobe.d/nvidia-options.conf slave nvidia--nvidia-settings is /usr/bin/nvidia-settings slave nvidia--nvidia-settings.1.gz is /usr/share/man/man1/nvidia-settings.1.gz slave nvidia--nvidia-settings.desktop is /usr/share/applications/nvidia-settings.desktop slave nvidia--nvidia-smi is /usr/bin/nvidia-smi slave nvidia--nvidia-smi.1.gz is /usr/share/man/man1/nvidia-smi.1.gz slave nvidia--nvidia_drv.so is /usr/lib/nvidia/nvidia_drv.so /usr/lib/nvidia/current - priority 525 slave nvidia--libEGL_nvidia.so.0-x86_64-linux-gnu: /usr/lib/x86_64-linux-gnu/nvidia/current/libEGL_nvidia.so.0 slave nvidia--libGLX_nvidia.so.0-x86_64-linux-gnu: /usr/lib/x86_64-linux-gnu/nvidia/current/libGLX_nvidia.so.0 slave nvidia--libcuda.so-x86_64-linux-gnu: /usr/lib/x86_64-linux-gnu/nvidia/current/libcuda.so slave nvidia--libcuda.so.1-x86_64-linux-gnu:
Bug#999502: Acknowledgement (linux-image-5.10.0-9-amd64: read from pty does not return newline on 64-byte boundaries)
Here's the output of the test program that we see under bullseye, kernel 5.10.0.-9: $ ./rbpty TEST len 130 text [123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789 ] 130 bytes read buf read: [123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789 ] TEST len 129 text [12345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678 ] 128 bytes read 1 bytes read buf read: [12345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678 ] TEST len 128 text [1234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567 ] 128 bytes read buf read: [1234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567 ] TEST len 66 text [12345678901234567890123456789012345678901234567890123456789012345 ] 66 bytes read buf read: [12345678901234567890123456789012345678901234567890123456789012345 ] TEST len 65 text [1234567890123456789012345678901234567890123456789012345678901234 ] 64 bytes read 1 bytes read buf read: [1234567890123456789012345678901234567890123456789012345678901234 ] TEST len 64 text [123456789012345678901234567890123456789012345678901234567890123 ] 64 bytes read buf read: [123456789012345678901234567890123456789012345678901234567890123 ] And here is the output of the same program under buster, kernel 4.19.0-18: $ src/rbpty TEST len 130 text [123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789 ] 130 bytes read buf read: [123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789 ] TEST len 129 text [12345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678 ] 129 bytes read buf read: [12345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678 ] TEST len 128 text [1234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567 ] 128 bytes read buf read: [1234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567 ] TEST len 66 text [12345678901234567890123456789012345678901234567890123456789012345 ] 66 bytes read buf read: [12345678901234567890123456789012345678901234567890123456789012345 ] TEST len 65 text [1234567890123456789012345678901234567890123456789012345678901234 ] 65 bytes read buf read: [1234567890123456789012345678901234567890123456789012345678901234 ] TEST len 64 text [123456789012345678901234567890123456789012345678901234567890123 ] 64 bytes read buf read: [123456789012345678901234567890123456789012345678901234567890123 ] John
Bug#999502: linux-image-5.10.0-9-amd64: read from pty does not return newline on 64-byte boundaries
Package: src:linux Version: 5.10.70-1 Severity: normal Tags: upstream Dear Maintainer, When reading from a pty, a call to read(2) always returns a string ending in a newline, except when the text written to the pty contains a multiple of 64 characters, plus the newline. In the exceptional case, a second call to read returns just the newline. In the previous debian release, buster, with kernel 4.19.0-18-amd64, a newline was always returned irrespective of the size of the input. This was discovered by students on our operating systems class. We include a test program that exhibits the problem. The hardware referenced in this ticket is a VM, but we saw similar results on hardware. -- Package-specific info: ** Version: Linux version 5.10.0-9-amd64 (debian-ker...@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.70-1 (2021-09-30) ** Command line: BOOT_IMAGE=/vmlinuz-5.10.0-9-amd64 root=/dev/mapper/debian--bullseye--vg-root ro quiet ** Not tainted ** Kernel log: Unable to read kernel log; any relevant messages should be attached ** Model information sys_vendor: VMware, Inc. product_name: VMware Virtual Platform product_version: None chassis_vendor: No Enclosure chassis_version: N/A bios_vendor: Phoenix Technologies LTD bios_version: 6.00 board_vendor: Intel Corporation board_name: 440BX Desktop Reference Platform board_version: None ** Loaded modules: cbc cts nfsv3 nfs_acl rpcsec_gss_krb5 nfsv4 dns_resolver nfs lockd 8021q grace nfs_ssc garp vsock_loopback stp mrp vmw_vsock_virtio_transport_common fscache llc vmw_vsock_vmci_transport vsock binfmt_misc intel_rapl_msr intel_rapl_common ghash_clmulni_intel aesni_intel vmwgfx libaes crypto_simd cryptd glue_helper rapl ttm evdev joydev vmw_balloon serio_raw sg pcspkr drm_kms_helper vmw_vmci cec ac button auth_rpcgss sunrpc drm fuse configfs ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c crc32c_generic raid1 raid0 multipath linear md_mod dm_mod sr_mod cdrom sd_mod t10_pi crc_t10dif crct10dif_generic ata_generic psmouse crct10dif_pclmul crct10dif_common crc32_pclmul crc32c_intel vmw_pvscsi ata_piix libata vmxnet3 scsi_mod i2c_piix4 ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge [8086:7190] (rev 01) Subsystem: VMware Virtual Machine Chipset [15ad:1976] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B+ PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- 00:07.0 ISA bridge [0601]: Intel Corporation 82371AB/EB/MB PIIX4 ISA [8086:7110] (rev 08) Subsystem: VMware Virtual Machine Chipset [15ad:1976] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- Kernel driver in use: vmw_vmci Kernel modules: vmw_vmci 00:0f.0 VGA compatible controller [0300]: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: vmwgfx Kernel modules: vmwgfx 00:11.0 PCI bridge [0604]: VMware PCI bridge [15ad:0790] (rev 02) (prog-if 01 [Subtractive decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: 00:15.0 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:15.1 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:15.2 PCI
Bug#944139: debmirror archive.debian.org fails due to missing binary-all
Package: debmirror Version: 1:2.32 Severity: important Dear Maintainer, The resolution of bug #904927 (Please sync/mirror Packages-all and Contents-all by default) appears to have broken debmirror's ability to mirror archive.debian.org. Wheezy-backports, for instance, lists main/binary-all/Packages in its Release file, but it does not actually exist in the archive. Debmirror reports a 404 and fails. There's no option to ignore this error. When I revert that change, debmirror works as before. Perhaps this is a problem with archive.debian.org, but I'm not sure how to report that, and, well, it used to work. -- System Information: Debian Release: 10.1 APT prefers stable APT policy: (750, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages debmirror depends on: ii bzip21.0.6-9.2~deb10u1 pn libdigest-md5-perl pn libdigest-sha-perl pn liblockfile-simple-perl ii libwww-perl 6.36-2 ii perl [libnet-perl] 5.28.1-6 ii rsync3.1.3-6 ii xz-utils 5.2.4-1 Versions of packages debmirror recommends: pn ed ii gpgv 2.2.12-1+deb10u1 ii patch 2.7.6-3+deb10u1 Versions of packages debmirror suggests: ii gnupg 2.2.12-1+deb10u1
Bug#943970: debmirror: Debmirror fails to verify valid, signed InRelease files
Package: debmirror
Version: 1:2.32
Severity: important
Dear Maintainer,
When debmirror splits InRelease files using split_clearsigned_file, it can
produce text and signature files that gpgv reports as having a "BAD signature."
Yet gpgv reports "Good signature" for the original InRelease file, by itself.
What I found is that most files work but some do not. Attached is a standalone
split command, using the code from debmirror. This is what I see when I test
the debian-archive wheezy-backports InRelease file:
# md5sum wheezy-inrelease
a3f7caeef19f3e3797ec08748409d413 wheezy-inrelease
# head -n 20 wheezy-inrelease
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Origin: Debian Backports
Label: Debian Backports
Suite: wheezy-backports
Version:
Codename: wheezy-backports
Date: Wed, 24 Jan 2018 08:51:34 UTC
NotAutomatic: yes
ButAutomaticUpgrades: yes
Architectures: amd64 armel armhf i386 ia64 kfreebsd-amd64 kfreebsd-i386 mips
mipsel powerpc s390 s390x sparc
Components: main contrib non-free
Description: Backports for the Wheezy Distribution
MD5Sum:
21206181d8c101b785f51c82820acef7 118763 contrib/Contents-amd64
85c8255dffc0437f45d71e2e0d27401b 2704 contrib/Contents-amd64.diff/Index
01c60695e6465dc1a3f2035d7060de5710211 contrib/Contents-amd64.gz
01d265b9bcabbad6969c560a6955089072100 contrib/Contents-armel
e03cee735398401fedf5b505fdc0cdbc 1720 contrib/Contents-armel.diff/Index
# gpgv --keyring /usr/share/keyrings/debian-archive-keyring.gpg --keyring
/usr/share/keyrings/debian-archive-removed-keys.gpg -v wheezy-inrelease
gpgv: armor header: Hash: SHA256
gpgv: original file name=''
gpgv: Signature made Wed 24 Jan 2018 03:51:53 AM EST
gpgv:using RSA key A1BD8E9D78F7FE5C3E65D8AF8B48AD6246925553
gpgv: Good signature from "Debian Archive Automatic Signing Key (7.0/wheezy)
"
gpgv: textmode signature, digest algorithm SHA256, key algorithm rsa4096
gpgv: Signature made Wed 24 Jan 2018 03:51:53 AM EST
gpgv:using RSA key 126C0D24BD8A2942CC7DF8AC7638D0442B90D010
gpgv: Good signature from "Debian Archive Automatic Signing Key (8/jessie)
"
gpgv: textmode signature, digest algorithm SHA256, key algorithm rsa4096
# ./split_clearsigned_file wheezy-inrelease
# gpgv --keyring /usr/share/keyrings/debian-archive-keyring.gpg --keyring
/usr/share/keyrings/debian-archive-removed-keys.gpg -v wheezy-inrelease-sig
wheezy-inrelease-txt
gpgv: Signature made Wed 24 Jan 2018 03:51:53 AM EST
gpgv:using RSA key A1BD8E9D78F7FE5C3E65D8AF8B48AD6246925553
gpgv: BAD signature from "Debian Archive Automatic Signing Key (7.0/wheezy)
"
gpgv: textmode signature, digest algorithm SHA256, key algorithm rsa4096
It does not always fail in this way. The jessie-backports InRelease file works
fine.
Here's the source I used for split_clearsigned_file:
#!/usr/bin/perl -w
# isolate split_clearsigned_file from debmirror
my $infile = $ARGV[0];
open my $sfd, '>', "$infile-sig" or die "$infile-sig\n";
open my $tfd, '>', "$infile-txt" or die "$infile-txt\n";
split_clearsigned_file($infile, $tfd, $sfd) or die "split failed\n";
# Split a clearsigned message into data and signature.
# Based on the similar SplitClearSignedFile in APT.
sub split_clearsigned_file {
my ($filename, $content_fh, $signature_fh) = @_;
my $found_message_start = '';
my $found_message_end = '';
my $skip_until_empty_line = '';
my $found_signature = '';
my $first_line = 1;
my $signed_message_not_on_first_line = '';
my $found_garbage = '';
open my $handle, "<", $filename or die "can't open $filename: $1";
while (my $line = <$handle>) {
$line =~ s/[\n\r]+$//;
if (not $found_message_start) {
if ($line eq '-BEGIN PGP SIGNED MESSAGE-') {
$found_message_start = 1;
$skip_until_empty_line = 1;
} else {
$signed_message_not_on_first_line = 1;
$found_garbage = 1;
}
} elsif ($skip_until_empty_line) {
if ($line eq '') {
$skip_until_empty_line = '';
}
} elsif (not $found_signature) {
if ($line eq '-BEGIN PGP SIGNATURE-') {
$found_signature = 1;
$found_message_end = 1;
print $signature_fh "$line\n";
} elsif (not $found_message_end) { # we are in the message block
# We don't have any fields that need to be dash-escaped, but
# implementations are free to encode all lines.
$line =~ s/^- //;
if ($first_line) { # first line does not need a newline
$first_line = '';
} else {
print $content_fh "\n";
}
print $content_fh $line;
} else {
$found_garbage = 1;
}
} else {
print $signature_fh "$line\n";
if ($line eq '-END PGP SIGNATURE-') {
$found_signature = '';
}
}
}
$content_fh->flush;
$signature_fh->flush;
if ($found_message_start) {
if ($signed_message_not_on_first_line) {
die "Clearsigned file '$filename' does not
Bug#728250: live-boot: bug in 9990-overlay.sh breaks plain dir boot
Source: live-boot
Severity: important
Tags: patch
Dear Maintainer,
A bug in the 990-overlay.sh component causes an error when booting
from a plain directory.
I discovered this in the 3.0.1-1 (wheezy), but it is present in
4.0~alpha16-1. The supplied patch is against the latter.
-- System Information:
Debian Release: 7.2
APT prefers stable
APT policy: (750, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
diff --git a/components/9990-overlay.sh b/components/9990-overlay.sh
index 6b62093..4ae5c07 100755
--- a/components/9990-overlay.sh
+++ b/components/9990-overlay.sh
@@ -353,7 +353,7 @@ setup_unionfs ()
live_rootfs=/live/rootfs/${d##*/}
live_rootfs_list=${live_rootfs_list} ${live_rootfs}
mkdir -p ${live_rootfs}
- case d in
+ case ${d} in
*.dir)
# do nothing # mount -o bind ${d} ${live_rootfs}
;;
Bug#697644: closed by Sergey B Kirpichev skirpic...@gmail.com (Re: apache2-mod-rpaf: failure to work with authz allow/deny should be documented)
Sorry, I didn't see your response. I have an nginx proxy on a separate server passing requests to apache. I am not using ipv6. Rpaf works, in as much as the logs show the original client ip addresses. But when I try to use allow/deny directives from an .htaccess file, referencing either domain names or ip addresses, they are not honored. All proxied requests are treated as though they come from the proxy host. I tested this by allowing access, in the apache config, only to the proxy host, verified that requests were denied when connecting directly to the apache server, and observed that proxied requests were always allowed (they should never be if rpaf works). Rpaf runs before access, so it seems like rpaf doesn't do whatever is necessary for access to see the client ip. I was able to make my configuration work by replacing rpaf with a backported version of remoteip. I've moved on, so I don't have a test config still lying around. Googling around, there are lots of confusing discussions about this issue, and I wasted a lot of time trying to make rpaf work. I saw, for instance, the discussion of the ipv6 bug report, which makes it seem like this problem was fixed. John -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#697644: closed by Sergey B Kirpichev skirpic...@gmail.com (Re: apache2-mod-rpaf: failure to work with authz allow/deny should be documented)
/etc/nginx/sites-enabled/default:
server {
listen 80;
root /usr/share/nginx/www;
location / {
proxy_pass http://[apache-host]/;
proxy_redirect off;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header Host $host;
}
}
/etc/apache2/mods-enabled/rpaf.conf:
IfModule rpaf_module
RPAFenable On
RPAFsethostname On
RPAFproxy_ips [nginx-ip]
RPAFheader X-Real-IP
/IfModule
/etc/apache2/sites-enabled/000-default:
VirtualHost *:80
DocumentRoot /var/www
Directory /
Options FollowSymLinks
AllowOverride None
/Directory
Directory /var/www/
Options Indexes FollowSymLinks MultiViews
AllowOverride None
Order allow,deny
allow from [nginx-ip]
/Directory
/VirtualHost
In the above case, I should get a deny from any host except [nginx-host].
Instead, proxied requests are allowed. In the apache log, it shows the
original client ip and 200 success.
If I change the apache config
allow from [nginx-ip]
to
allow from [client-ip]
then direct requests are allowed, and proxied requests are denied.
Note that I have separate servers. I never tried this with both servers
on the same host. Perhaps that has something to do with it.
John
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#697644: apache2-mod-rpaf: failure to work with authz allow/deny should be documented
Package: apache2-mod-rpaf Severity: important mod-rpaf does not work with apache's allow/deny directives. Although the logs show the forwarded IPs and cgi's and other applications see them, too, the allow/deny directives use the proxy IP address. This should be clearly documented. I marked this important because it is a subtle problem and can expose protected content. And I made this a doc bug because rpaf is deprecated in favor of remoteip. I tested 0.5-3+squeeze1 and 0.6-7~bpo60+1 under squeeze. The (apache 2.4.1) backported version of remoteip at https://github.com/ttkzw/mod_remoteip-httpd22 does work. -- System Information: Debian Release: 6.0.6 APT prefers stable APT policy: (750, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686-bigmem (SMP w/4 CPU cores) Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679318: flumotion: twisted override bug - one more
Package: flumotion Version: 0.10.0-2 Severity: grave Tags: upstream patch Justification: renders package unusable This is the same problem I reported in #672404, but affecting a different part of the code (there are two places that need to be fixed). To recap, flumotion overrides an internal method in twisted, which has changed. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (750, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/6 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash diff -ur a/flumotion/twisted/fdserver.py b/flumotion/twisted/fdserver.py --- a/flumotion/twisted/fdserver.py 2011-10-07 06:10:58.0 -0400 +++ b/flumotion/twisted/fdserver.py 2012-06-15 10:55:46.344267000 -0400 @@ -173,7 +173,7 @@ class _SocketMaybeCloser(tcp._SocketCloser): keepSocketAlive = False -def _closeSocket(self): +def _closeSocket(self, orderly): # We override this (from tcp._SocketCloser) so that we can close # sockets properly in the normal case, but once we've passed our # socket on via the FD-channel, we just close() it (not calling
Bug#657138: save/load
I see exactly those messages when I try to load a glade (GtkBuilder) file that I saved moments before. Then glade segfaults. John -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#672404: flumotion: breaks with twisted 11.1.0
Package: flumotion Version: 0.10.0-1 Severity: grave Tags: upstream patch Justification: renders package unusable Flumotion overrides an internal interface from twisted which changed between 10.1.0 and 11.1.0. Using a fresh wheezy install, flumotion fails to create a working pipeline after following all the defaults in the wizard (as suggested in the doc). I filed a bug with upstream: https://code.flumotion.com/trac/ticket/1544 In the meantime, the fix is simple. I've included a patch. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (750, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages flumotion depends on: ii adduser 3.113+nmu1 ii gstreamer0.10-ffmpeg0.10.13-5 ii gstreamer0.10-plugins-bad [gstreamer0.10-schroedinger] 0.10.23-1+b1 ii gstreamer0.10-plugins-base 0.10.36-1 ii gstreamer0.10-plugins-good 0.10.31-2 ii libc6 2.13-32 ii python 2.7.2-10 ii python-cairo1.8.8-1+b2 ii python-dateutil 1.5-1 ii python-glade2 2.24.0-3 ii python-gobject 3.2.0-3 ii python-gst0.10 0.10.22-3 ii python-gtk2 2.24.0-3 ii python-kiwi 1.9.22-2 ii python-openssl 0.13-1 ii python-rrdtool 1.4.7-1 ii python-twisted-core 11.1.0-1 ii python-twisted-web 11.1.0-1 ii python2.7 2.7.3~rc2-2.1 ii ssl-cert1.0.28 ii xsltproc1.1.26-8 Versions of packages flumotion recommends: ii python-gnome2 2.28.1+dfsg-1 flumotion suggests no packages. diff -urN a/flumotion/component/feed.py b/flumotion/component/feed.py --- a/flumotion/component/feed.py 2011-10-07 06:10:58.0 -0400 +++ b/flumotion/component/feed.py 2012-05-10 15:37:46.608846000 -0400 @@ -38,7 +38,7 @@ class _SocketMaybeCloser(tcp._SocketCloser): keepSocketAlive = False -def _closeSocket(self): +def _closeSocket(self, orderly): # We override this (from tcp._SocketCloser) so that we can close # sockets properly in the normal case, but once we've passed our # socket on via the FD-channel, we just close() it (not calling
Bug#476946: unattended installs
This bug makes unattended installs extremely difficult. I have a remote postgresql server, and I cannot find a workable combination of debconf settings that allows the sympa package (which uses dbconfig-common) to install without error. Without the ability to preseed the dbc answers, sympa fails to install. Even preseeding dbconfig-common this way: * dbconfig-common/dbconfig-install: false * dbconfig-common/dbconfig-remove: false * dbconfig-common/dbconfig-upgrade: false * dbconfig-common/missing-db-package-error: ignore Does not stop this package from attempting to contact the database server, and create a database admin user: Setting up sympa (6.1.4~dfsg-1~bpo60+1) ... dbconfig-common: writing config to /etc/dbconfig-common/sympa.conf warning: database package not installed? chown: invalid user: `postgres' unable to connect to postgresql server. error encountered creating user: Unknown id: postgres dbconfig-common: sympa configure: aborted. dbconfig-common: flushing administrative password dpkg: error processing sympa (--configure): subprocess installed post-installation script returned error exit status 1 John -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#660792: pure-ftpd: multiple daemon support removed from debian packaging
Package: pure-ftpd Version: 1.0.28-3+squeeze1 Severity: important Support for configuring and running multiple daemons was removed between 1.0.28-2 (lenny) and this release. In the older version, it was possible to create an alternate ftpd config for $host under /etc/pure-ftpd/$host.cfg. The boot script would then run a separate ftpd daemon for each of these (in addition to one for the top-level daemon). The code to support this was removed from the boot script and from pure-ftpd-wrapper. Was this a deliberate change or a regression? If deliberate, is there an alternate way to configure two or more daemons (within the framework of the debian packaging)? -- System Information: Debian Release: 6.0.4 APT prefers stable APT policy: (750, 'stable'), (70, 'oldstable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686-bigmem (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages pure-ftpd depends on: ii libc6 2.11.3-2 Embedded GNU C Library: Shared lib ii libcap2 1:2.19-3 support for getting/setting POSIX. ii libpam0g 1.1.1-6.1+squeeze1 Pluggable Authentication Modules l ii libssl0.9.8 0.9.8o-4squeeze7 SSL shared libraries ii lsb-base 3.2-23.2squeeze1 Linux Standard Base 3.2 init scrip ii openbsd-inetd [inet-s 0.20080125-6 The OpenBSD Internet Superserver pn pure-ftpd-common none (no description available) pure-ftpd recommends no packages. pure-ftpd suggests no packages. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#660792: pure-ftpd: multiple daemon support removed from debian packaging
The multi-daemon support is also missing from the most recent (1.0.35) release. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#568838: lvm2_wait-lvm.patch works
I can confirm that the lvm2_wait-lvm.patch works, also. I have an entire class of blade systems that will not boot without it. Please don't let this go unresolved. John -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#568838: oops
Oops - forgot to mention: squeeze lvm2 2.02.66-5 kernel 2.6.32-5-amd64 John -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#620249: apt: specific+general pin chooses wrong package version
Package: apt Version: 0.7.20.2+lenny2 Severity: normal I thought I had a pretty good grasp of pinning, but I can't understand the following behavior. What I'm trying to do is, for a particular package, always install the newest package version from either my local archive OR lenny-backports. My local archive is oldstable (same as lenny), and I have no target release defined. sources.list: deb http://mymirror/debian lenny main contrib non-free deb http://mymirror/debian-security lenny/updates main contrib non-free deb http://mymirror/debian-backports lenny-backports main contrib non deb http://mymirror/debian-browncs lenny local preferences: Package: * Pin: release a=oldstable Pin-Priority: 750 Package: * Pin: release a=lenny-backports Pin-Priority: 80 Package: dovecot-imapd Pin: release a=lenny-backports Pin-Priority: 750 % apt-cache policy dovecot-imapd dovecot-imapd: Installed: (none) Candidate: 1:1.2.15-1~bpo50+1 Package pin: 1:1.2.15-1~bpo50+1 Version table: 1:1.2.15-1~bpo50+1+browncs 750 750 http://mymirror lenny/local Packages 1:1.2.15-1~bpo50+1 750 80 http://mymirror lenny-backports/main Packages 1:1.0.15-2.3+lenny1 750 750 http://mymirror lenny/main Packages 750 http://mymirror lenny/updates/main Packages The priorities are equal, but the older version from lenny-backports is the candidate. I would expect the newer version to be installed. I tried adding a second specific pin at 750 to oldstable, but then the package chosen depends on the ordering in the preferences file. It seems like the specific pin supercedes the package version comparison, but only in the case that the priorities are equal. -- Package-specific info: -- (/etc/apt/preferences present, but not submitted) -- -- (/etc/apt/sources.list present, but not submitted) -- -- System Information: Debian Release: 5.0.8 APT prefers oldstable APT policy: (750, 'oldstable') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-686 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages apt depends on: ii debian-archive-keyring 2010.08.28~lenny1 GnuPG archive keys of the Debian a ii libc6 2.7-18lenny7 GNU C Library: Shared libraries ii libgcc11:4.3.2-1.1 GCC support library ii libstdc++6 4.3.2-1.1 The GNU Standard C++ Library v3 apt recommends no packages. Versions of packages apt suggests: pn apt-doc none (no description available) ii aptitude 0.4.11.11-1~lenny1 terminal-based package manager ii bzip2 1.0.5-1+lenny1 high-quality block-sorting file co ii dpkg-dev 1.14.31Debian package development tools ii gnome-apt 0.4.9-5graphical package manager ii lzma 4.43-14Compression method of 7z format in ii python-apt0.7.7.1+nmu1 Python interface to libapt-pkg ii synaptic 0.62.1+nmu1Graphical package manager -- debconf-show failed -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#604562: gridengine-master: config support for shadowd
Package: gridengine-master Version: 6.2-4 Severity: wishlist It'd be really nice if the debian packaging made it easy to configure a shadow master. Perhaps /etc/default/gridengine could include SGE_START_SHADOWD (default to no), and a boot script could fire it up if it's yes. -- System Information: Debian Release: 5.0.6 APT prefers stable APT policy: (750, 'stable'), (70, 'oldstable') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-686 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#597895: gridengine-master: does not support classic spooling
Package: gridengine-master Severity: important I tried configuring gridengine to use classic spooling, but when the qmaster daemon starts up, I see these errors in the logs: E|Binaries were compiled with spooling method berkeleydb, requested spooling method is classic E|error creating a classic spooling context C|setup failed It looks to me like they are not mutually exclusive. Classic spooling is important if, like me, you want to set up shadow masters. Can we have both methods compiled in? I'm running 6.2-4 (lenny), but it doesn't look different in 6.2u5-1. -- System Information: Debian Release: 5.0.6 APT prefers stable APT policy: (750, 'stable'), (70, 'oldstable') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-686 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#597898: gridengine-exec: manual config debconf setting does not prevent daemon from starting
Package: gridengine-exec Severity: normal If the 'gridengineconfig' debconf setting is set to false, no configuration is generated, but the execd daemon is still started. Not finding its config, it complains and eventually dies. If manual configuration is an package option, it shouldn't start the daemon. This is probably also true for gridengine-master. I'm running 6.2-4 (lenny), but I checked 6.2u5-1 and it looks the same. -- System Information: Debian Release: 5.0.6 APT prefers stable APT policy: (750, 'stable'), (70, 'oldstable') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-686 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#587685: apache2: lenny8 rev broke DirectoryIndex processing
On Fri, Jul 02, 2010 at 09:34:49PM +0200, Stefan Fritsch wrote: If you have several DirectoryIndex statements in the same section, they are merged. Only if you have DirectoryIndex statements in different sections, the last section to be merged wins. I strongly doubt that there was any behaviour change caused by the update. Really? I wondered that, but couldn't find it documented anywhere. My user must be mistaken about when things broke here. Sorry to bother you guys, and thanks. John -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#587685: apache2: lenny8 rev broke DirectoryIndex processing
Package: apache2 Version: 2.2.9-10+lenny8 Severity: normal With the update from lenny7 to lenny8 a few days ago, my apache server began choosing the wrong DirectoryIndex files to serve. I have a config snippet in /etc/apache2/conf.d/mod_dir that orders them like this: DirectoryIndex home.html home.htm home.shtml\ index.html index.htm index.shtml index.xml Directories with only home.html files work fine, but index.html is now preferred. More weirdly, in debugging this, I removed the DirectoryIndex directive from /etc/apache2/mods-available/dir.conf, and that fixed it. Since that file is processed before my snippet, I would expect my snippet to override it. Since home.html files *are* being processed, it seems like the two directives are being combined instead. I realize this makes no sense. I looked at the changelog. But I've got two web servers with different but similar configs that are both affected. And in both cases, the only thing that changed was the new apache rev. -- System Information: Debian Release: 5.0.5 APT prefers stable APT policy: (750, 'stable'), (70, 'oldstable') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-686 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages apache2 depends on: pn apache2-mpm-worker | apache2- none (no description available) apache2 recommends no packages. apache2 suggests no packages. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#550404: sympa.config ignores some debconf defaults
On Sat, Apr 10, 2010 at 05:28:58PM +0200, Stefan Hornburg (Racke) wrote: How do I seed debconf in order to test whether this problem exists with my Sympa 6.0 packaging (see http://git.debian.org/?p=collab-maint/sympa.git)? Here's one way: cat EOF | debconf-set-selections sympa sympa/hostname string sympa.example.com sympa sympa/listmaster string ad...@sympa.example.com sympa wwsympa/wwsympa_url string http://sympa.example.com/sympa EOF Note that debconf-set-selections expects a single space between fields. John -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#569616: monit: State file path is hardcoded in init script
Package: monit Version: 1:4.10.1-4 Severity: normal Monit's state file path is hardcoded in /etc/init.d/monit: ARGS=-d $CHECK_INTERVALS -c $CONFIG -s /var/lib/monit/monit.state Check the docs - in the section Monitoring Mode they suggest: If you use Monit in a HA-cluster you should place the state file in a temporary filesystem so if the machine should crash and the stand-by machine take over services, any manual monitoring mode services that were started on the crashed machine won't be started on reboot. Use for example: set statefile /tmp/monit.state So a little flexibility would be appreciated here. How about setting it in /etc/defaults/monit instead? -- System Information: Debian Release: 5.0.4 APT prefers stable APT policy: (750, 'stable'), (70, 'oldstable') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-686 (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages monit depends on: ii libc6 2.7-18lenny2 GNU C Library: Shared libraries ii libssl0.9.8 0.9.8g-15+lenny6 SSL shared libraries monit recommends no packages. monit suggests no packages. -- debconf-show failed -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#568543: sympa: bootscript reload always restarts daemons
Package: sympa Version: 5.3.4-6.1 Severity: normal /etc/init.d/sympa reload always restarts the daemons, even if they are not running. This is a problem in a typical failover configuration using heartbeat, in which one machine (a warm standby) always has sympa disabled. Logrotate calls the bootscript with reload and restarts the service. This problem exists in the most recent version in unstable (5.4.7-1) too. Reload should check to see if the pidfile exists before restarting. I suggest replacing this: restart|force-reload|reload) $0 stop sleep 3 $0 start ;; with something like this: restart|force-reload) $0 stop sleep 3 $0 start ;; reload) if test -s $PIDFILE; then $0 stop sleep 3 $0 start fi ;; -- System Information: Debian Release: 5.0.4 APT prefers stable APT policy: (750, 'stable'), (70, 'oldstable') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-686 (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages sympa depends on: ii adduser 3.110add and remove users and groups ii debconf [debconf-2.0] 1.5.24 Debian configuration management sy pn libarchive-zip-perl none (no description available) ii libc6 2.7-18lenny2 GNU C Library: Shared libraries pn libcgi-fast-perlnone (no description available) pn libcrypt-ciphersaber-pe none (no description available) ii libdbd-mysql-perl 4.007-1+lenny1 A Perl5 database interface to the ii libdbd-pg-perl 2.8.7-1+lenny1 Perl DBI driver for the PostgreSQL ii libdbi-perl 1.605-1 Perl5 database interface by Tim Bu ii libfcgi-perl0.67-2.1+b1 FastCGI Perl module pn libintl-perlnone (no description available) ii libio-stringy-perl 2.110-4 Perl modules for IO from scalars a ii libmailtools-perl 2.03-1 Manipulate email in perl programs ii libmd5-perl 2.03-1 backwards-compatible wrapper for D ii libmime-perl5.427-1 transitional dummy package ii libmime-tools-perl [lib 5.427-1 Perl5 modules for MIME-compliant m pn libmsgcat-perl none (no description available) ii libnet-ldap-perl1:0.36-1 A Client interface to LDAP servers ii libtemplate-perl2.19-1.1lenny1.1 template processing system written ii libxml-libxml-perl 1.66-1+b1Perl module for using the GNOME li ii mhonarc 2.6.16-1 Mail to HTML converter ii perl [libmime-base64-pe 5.10.0-19lenny2 Larry Wall's Practical Extraction ii perl-suid 5.10.0-19lenny2 Runs setuid Perl scripts ii postfix [mail-transport 2.5.5-1.1High-performance mail transport ag ii sysklogd [system-log-da 1.5-5System Logging Daemon Versions of packages sympa recommends: ii doc-base 0.8.20 utilities to manage online documen ii logrotate 3.7.1-5Log rotation utility Versions of packages sympa suggests: pn apache | apache-ssl | h none (no description available) pn libapache-mod-fastcgi none (no description available) pn mysql-server | postgres none (no description available) ii openssl 0.9.8g-15+lenny6 Secure Socket Layer (SSL) binary a -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#560343: qpsmtpd: config script bug setting INTERFACES
Package: qpsmtpd
Version: 0.40-3
Severity: normal
There's a minor error in the config script. If you don't set INTERFACES,
it is set as follows:
INTERFACES=`/sbin/ifconfig -a | \
grep 'inet addr' | \
tr : ' ' | \
awk '{print $3}' | \
tr '\n' ' ' | \
sort | uniq`
The second tr makes the sort superfluous. You probably want that
tr to be last.
-- System Information:
Debian Release: 5.0.3
APT prefers stable
APT policy: (750, 'stable'), (70, 'oldstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-2-686 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash
Versions of packages qpsmtpd depends on:
ii adduser 3.110 add and remove users and groups
ii debconf 1.5.24 Debian configuration management sy
ii libdigest-hmac-perl 1.01-7 create standard message integrity
pn libmail-spf-query-perl none (no description available)
ii libmailtools-perl2.03-1 Manipulate email in perl programs
ii libnet-dns-perl 0.63-2 Perform DNS queries from a Perl sc
ii perl 5.10.0-19lenny2 Larry Wall's Practical Extraction
ii perl-modules [libnet-per 5.10.0-19lenny2 Core Perl modules
qpsmtpd recommends no packages.
Versions of packages qpsmtpd suggests:
pn clamav-daemon none (no description available)
ii spamassassin 3.2.5-2+lenny1 Perl-based spam filter using text
pn tinycdb none (no description available)
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#523515: fixed upstream
Hi, this is fixed in version 1.14, uploaded to CPAN today. Thanks for your work diagnosing the problem. John -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#550404: sympa.config ignores some debconf defaults
Package: sympa Version: 5.3.4-6.1 Severity: normal Seeding debconf to perform an unattended installation of sympa doesn't work because sympa.config ignores the debconf values for: sympa/hostname sympa/listmaster wwsympa/wwsympa_url Some other values are honored, however (sympa/db_* for instance). I understand you are redoing the packaging in sid, but I figured I'd report this anyway, to help others who bump into the issue. Also, I'd like to urge you to keep in mind folks like me who do unattended installs. The current package forces me to seed debconf to benefit from file permissions set in the postinst and to avoid failure due to a missing database connection. But due to this bug, I still have to modify sympa.conf after installation, and restart the daemons. It's a bit messy. It'd be nice if a fresh, default, unattended install would succeed, but not start the daemons (so I can finish the configuration separately). -- System Information: Debian Release: 5.0.3 APT prefers stable APT policy: (750, 'stable'), (70, 'oldstable') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-686 (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages sympa depends on: ii adduser 3.110add and remove users and groups ii debconf [debconf-2.0] 1.5.24 Debian configuration management sy pn libarchive-zip-perl none (no description available) ii libc6 2.7-18 GNU C Library: Shared libraries pn libcgi-fast-perlnone (no description available) pn libcrypt-ciphersaber-pe none (no description available) ii libdbd-mysql-perl 4.007-1 A Perl5 database interface to the ii libdbd-pg-perl 2.8.7-1 Perl DBI driver for the PostgreSQL ii libdbi-perl 1.605-1 Perl5 database interface by Tim Bu ii libfcgi-perl0.67-2.1+b1 FastCGI Perl module pn libintl-perlnone (no description available) ii libio-stringy-perl 2.110-4 Perl modules for IO from scalars a ii libmailtools-perl 2.03-1 Manipulate email in perl programs ii libmd5-perl 2.03-1 backwards-compatible wrapper for D ii libmime-perl5.427-1 transitional dummy package ii libmime-tools-perl [lib 5.427-1 Perl5 modules for MIME-compliant m pn libmsgcat-perl none (no description available) ii libnet-ldap-perl1:0.36-1 A Client interface to LDAP servers ii libtemplate-perl2.19-1.1lenny1.1 template processing system written ii libxml-libxml-perl 1.66-1+b1Perl module for using the GNOME li ii mhonarc 2.6.16-1 Mail to HTML converter ii perl [libmime-base64-pe 5.10.0-19lenny2 Larry Wall's Practical Extraction ii perl-suid 5.10.0-19lenny2 Runs setuid Perl scripts ii postfix [mail-transport 2.5.5-1.1High-performance mail transport ag ii sysklogd [system-log-da 1.5-5System Logging Daemon Versions of packages sympa recommends: ii doc-base 0.8.20 utilities to manage online documen ii logrotate 3.7.1-5Log rotation utility Versions of packages sympa suggests: pn apache | apache-ssl | h none (no description available) pn libapache-mod-fastcgi none (no description available) pn mysql-server | postgres none (no description available) ii openssl 0.9.8g-15+lenny5 Secure Socket Layer (SSL) binary a -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#510949: (no subject)
-- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#510949: I see this w/o root
I'm seeing this, but as a normal user. Same version of mailutils
(1:1.2+dfsg1-4). I'm running a current lenny with a stock 2.6.26-1-686
kernel.
Certain .mailrc files cause it. I tried to pare down an example file,
but found it wasn't any particular line. That is, I can remove bits
from the beginning or from the end or from the middle and the segfault
disappears. Unfortunately, to protect my user's privacy, I cannot
forward the file. The file contains only aliases at this point, and no
unprintable characters or obvious syntactic errors. I prepended one line
(alias foobarf...@bar.org) so I can upload the end of an strace:
gettimeofday({1232988253, 523429}, NULL) = 0
getrusage(RUSAGE_SELF, {ru_utime={0, 0}, ru_stime={0, 4000}, ...}) = 0
time(NULL) = 1232988253
times({tms_utime=0, tms_stime=0, tms_cutime=0, tms_cstime=0}) = 1865617403
open(/etc/mail.rc, O_RDONLY|O_LARGEFILE) = 4
fstat64(4, {st_mode=S_IFREG|0644, st_size=607, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb7f93000
read(4, # Default .mailrc\n# Set prompt st..., 4096) = 607
read(4, ..., 4096)= 0
close(4)= 0
munmap(0xb7f93000, 4096)= 0
open(/home/jsb/.mailrc, O_RDONLY|O_LARGEFILE) = 4
fstat64(4, {st_mode=S_IFREG|0644, st_size=1511, ...}) = 0
mmap2(NULL, 32768, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb7f8c000
read(4, alias foobar\t...@bar.org\nalias cl..., 32768) = 1511
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++
John
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#496962: yabasic: The open window statement fails.
Package: yabasic Version: 2.763-4 Severity: normal Tags: patch In yabasic, executing the statement open window 200,200 results in the following error output: open window 200,200 *** glibc detected *** yabasic: munmap_chunk(): invalid pointer: 0x080683a1 *** === Backtrace: = /lib/i686/cmov/libc.so.6[0xb7ca74f4] yabasic[0x80575f1] yabasic[0x8059552] yabasic[0x804db6b] yabasic[0x804e336] /lib/i686/cmov/libc.so.6(__libc_start_main+0xe5)[0xb7c4f455] yabasic[0x804a711] === Memory map: 08048000-08078000 r-xp 08:06 296531 /usr/bin/yabasic 08078000-08079000 rw-p 0002f000 08:06 296531 /usr/bin/yabasic 08079000-080b2000 rw-p 08079000 00:00 0 [heap] b7bdd000-b7be7000 r-xp 08:01 39952 /lib/i686/cmov/libnss_files-2.7 .so b7be7000-b7be9000 rw-p 9000 08:01 39952 /lib/i686/cmov/libnss_files-2.7 .so b7c11000-b7c12000 rw-p b7c11000 00:00 0 b7c12000-b7c16000 r-xp 08:06 1235847/usr/lib/libXdmcp.so.6.0.0 b7c16000-b7c17000 rw-p 3000 08:06 1235847/usr/lib/libXdmcp.so.6.0.0 b7c17000-b7c19000 r-xp 08:06 1235845/usr/lib/libXau.so.6.0.0 b7c19000-b7c1a000 rw-p 1000 08:06 1235845/usr/lib/libXau.so.6.0.0 b7c1a000-b7c31000 r-xp 08:06 1235849/usr/lib/libxcb.so.1.0.0 b7c31000-b7c32000 rw-p 00016000 08:06 1235849/usr/lib/libxcb.so.1.0.0 b7c32000-b7c33000 rw-p b7c32000 00:00 0 b7c33000-b7c34000 r-xp 08:06 1236455/usr/lib/libxcb-xlib.so.0.0.0 b7c34000-b7c35000 rw-p 08:06 1236455/usr/lib/libxcb-xlib.so.0.0.0 b7c35000-b7c37000 r-xp 08:01 39946 /lib/i686/cmov/libdl-2.7.so b7c37000-b7c39000 rw-p 1000 08:01 39946 /lib/i686/cmov/libdl-2.7.so b7c39000-b7d8e000 r-xp 08:01 39943 /lib/i686/cmov/libc-2.7.so b7d8e000-b7d8f000 r--p 00155000 08:01 39943 /lib/i686/cmov/libc-2.7.so b7d8f000-b7d91000 rw-p 00156000 08:01 39943 /lib/i686/cmov/libc-2.7.so b7d91000-b7d94000 rw-p b7d91000 00:00 0 b7d94000-b7e7f000 r-xp 08:06 1236457/usr/lib/libX11.so.6.2.0 b7e7f000-b7e82000 rw-p 000eb000 08:06 1236457/usr/lib/libX11.so.6.2.0 b7e82000-b7e83000 rw-p b7e82000 00:00 0 b7e83000-b7eb2000 r-xp 08:01 26585 /lib/libncurses.so.5.6 b7eb2000-b7eb5000 rw-p 0002f000 08:01 26585 /lib/libncurses.so.5.6 b7eb5000-b7ed9000 r-xp 08:01 39947 /lib/i686/cmov/libm-2.7.so b7ed9000-b7edb000 rw-p 00023000 08:01 39947 /lib/i686/cmov/libm-2.7.so b7edb000-b7edc000 rw-p b7edb000 00:00 0 b7edc000-b7ef r-xp 08:06 1236461/usr/lib/libICE.so.6.3.0 b7ef-b7ef1000 rw-p 00014000 08:06 1236461/usr/lib/libICE.so.6.3.0 b7ef1000-b7ef3000 rw-p b7ef1000 00:00 0 b7ef3000-b7efa000 r-xp 08:06 1236463/usr/lib/libSM.so.6.0.0 b7efa000-b7efb000 rw-p 6000 08:06 1236463/usr/lib/libSM.so.6.0.0 b7f14000-b7f2 r-xp 08:01 26627 /lib/libgcc_s.so.1 b7f2-b7f21000 rw-p b000 08:01 26627 /lib/libgcc_s.so.1 b7f21000-b7f25000 rw-p b7f21000 00:00 0 b7f25000-b7f3f000 r-xp 08:01 29362 /lib/ld-2.7.so b7f3f000-b7f41000 rw-p 0001a000 08:01 29362 /lib/ld-2.7.so bf9de000-bf9f3000 rw-p bffeb000 00:00 0 [stack] e000-f000 r-xp 00:00 0 [vdso] ---Fatal in standard input, line 1: received signal ABORT, cannot proceed. ---Immediate exit to system, due to a fatal error. I found a discussion at http://forum.basicprogramming.org/index.php?topic=21.0 and a patch at http://www.basicprogramming.org/files/graphic.patch, which I'm including with this report. I've applied the patch on my system and it does fix the problem. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (750, 'testing'), (80, 'cool'), (80, 'cold'), (40, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.24-1-686 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages yabasic depends on: ii libc6 2.7-13 GNU C Library: Shared libraries ii libice6 2:1.0.4-1 X11 Inter-Client Exchange library ii libncurses5 5.6+20080804-1 shared libraries for terminal hand ii libsm62:1.0.3-2 X11 Session Management library ii libx11-6 2:1.1.4-2 X11 client-side library yabasic recommends no packages. yabasic suggests no packages. -- debconf-show failed diff -r -u yabasic-2.763.orig/graphic.c yabasic-2.763/graphic.c --- yabasic-2.763.orig/graphic.c 2008-08-28 15:35:44.0 -0400 +++ yabasic-2.763/graphic.c 2008-08-28 15:36:50.0 -0400 @@ -212,12 +212,12 @@ return; #ifdef UNIX - /* create the window */ attrib.backing_store = Always; attrib.save_under = TRUE; attrib.background_pixel = backpixel; attrib.colormap = colormap; + window = XCreateWindow (display, root, winx, winy, winwidth, winheight, 0, CopyFromParent, CopyFromParent,
Bug#471345: wml_p1_ipp fails to remove tmp directories
Package: wml Version: 2.0.11-1etch1 Severity: normal wml_p1_ipp creates temporary directories like /tmp/ipp.X, but doesn't remove them. On a busy site like ours, this can cause problems when /tmp fills up with these and wml stops working (with a not very helpful error message). This was reported earlier, with a patch, here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=463907#76 Please apply Jochen's patch. -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (750, 'stable'), (60, 'cool') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-6-k7 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages wml depends on: ii eperl 2.2.14-14 Embedded Perl 5 Language ii iselect1.3.1-2 An interactive line selection tool ii libbit-vector-perl 6.4-5 Perl and C library for bit vectors ii libc6 2.3.6.ds1-13etch4 GNU C Library: Shared libraries ii libimage-size-perl 3.01-1determine the size of images in se ii libpng12-0 1.2.15~beta5-1PNG library - runtime ii libterm-readkey-perl 2.30-3A perl module for simple terminal ii m4 1.4.8-2 a macro processing language ii mp4h 1.3.1-3 Macro processor for HTML documents ii perl 5.8.8-7etch1 Larry Wall's Practical Extraction ii perl-base [perlapi-5.8 5.8.8-7etch1 The Pathologically Eclectic Rubbis ii slice 1.3.8-8 Extract out pre-defined slices of Versions of packages wml recommends: pn libhtml-clean-perlnone (no description available) pn linklint none (no description available) ii tidy 20051018-1 HTML syntax checker and reformatte pn txt2html none (no description available) -- debconf-show failed -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#335782: quintuple-agent: does not die after Xsession terminates
Package: quintuple-agent Version: 1.0.4-7 Severity: normal quintuple-agent installs the file 91quintuple-agent_q-agent in /etc/X11/Xsesssion.d, which fires up q-agent when a user logs in. Unlike all (most?) other packages that avail themselves of this feature, q-agent does not die when the Xsession terminates, so the q-agent process is left lying about. These processes prevent automount from unmounting user directories at our site, so this is actually a problem for us. Xsession does not seem to have any mechanism for executing commands on logout, so perhaps this is simply the wrong way for q-agent to start itself. Or perhaps it's a bug for x11-common. Not sure. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (750, 'testing'), (80, 'cool'), (80, 'cold'), (50, 'unstable'), (40, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.10cs.a64.hm.1 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages quintuple-agent depends on: ii libc6 2.3.5-6GNU C Library: Shared libraries an ii libcap1 1:1.10-14 support for getting/setting POSIX. ii libglib1.21.2.10-10 The GLib library of C routines ii libgtk1.2 1.2.10-18 The GIMP Toolkit set of widgets fo ii libx11-6 6.8.2.dfsg.1-7 X Window System protocol client li ii libxext6 6.8.2.dfsg.1-7 X Window System miscellaneous exte ii libxi66.8.2.dfsg.1-7 X Window System Input extension li ii xlibs 6.8.2.dfsg.1-7 X Window System client libraries m quintuple-agent recommends no packages. -- debconf-show failed -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
