Hi Thomas, On Thu, May 01, 2014 at 01:04:47AM +0200, Thomas Liske wrote: > sorry for the trouble with 0.8 :-(
No problem. It's Debian Unstable after all. :-) > On 04/29/2014 12:35 PM, Axel Beckert wrote: > > # needrestart > > Scanning processes............................................... > > Scanning candidates.Use of uninitialized value in pattern match (m//) at > > /usr/sbin/needrestart line 285, <HPIPE> line 1. > > Use of uninitialized value in pattern match (m//) at /usr/sbin/needrestart > > line 285, <HPIPE> line 1. > > this is very strange... it looks like the return of Proc::ProcessTable > is broken - I could not reproduce it, yet. It looks like the > /proc/<pid>/exe symlink is missing for some processes?! Doesn't seem so: # for i in /proc/[0-9]*; do if [ ! -e $i/exe ]; then ls -l $i/exe; fi; done ls: cannot read symbolic link /proc/10/exe: No such file or directory lrwxrwxrwx 1 root root 0 Apr 28 22:53 /proc/10/exe ls: cannot read symbolic link /proc/11/exe: No such file or directory lrwxrwxrwx 1 root root 0 Apr 28 22:53 /proc/11/exe ls: cannot read symbolic link /proc/12/exe: No such file or directory lrwxrwxrwx 1 root root 0 Apr 28 22:53 /proc/12/exe ls: cannot read symbolic link /proc/13/exe: No such file or directory lrwxrwxrwx 1 root root 0 Apr 28 22:53 /proc/13/exe ls: cannot read symbolic link /proc/14/exe: No such file or directory lrwxrwxrwx 1 root root 0 Apr 28 22:53 /proc/14/exe ls: cannot read symbolic link /proc/15/exe: No such file or directory lrwxrwxrwx 1 root root 0 Apr 28 22:53 /proc/15/exe ls: cannot read symbolic link /proc/16/exe: No such file or directory lrwxrwxrwx 1 root root 0 Apr 28 22:53 /proc/16/exe ls: cannot read symbolic link /proc/17/exe: No such file or directory lrwxrwxrwx 1 root root 0 Apr 28 22:53 /proc/17/exe ls: cannot read symbolic link /proc/18/exe: No such file or directory lrwxrwxrwx 1 root root 0 Apr 28 22:53 /proc/18/exe ls: cannot read symbolic link /proc/19/exe: No such file or directory lrwxrwxrwx 1 root root 0 Apr 28 22:53 /proc/19/exe ls: cannot read symbolic link /proc/2/exe: No such file or directory lrwxrwxrwx 1 root root 0 Apr 28 22:53 /proc/2/exe ls: cannot read symbolic link /proc/21/exe: No such file or directory lrwxrwxrwx 1 root root 0 Apr 28 22:53 /proc/21/exe ls: cannot read symbolic link /proc/22/exe: No such file or directory lrwxrwxrwx 1 root root 0 Apr 28 22:53 /proc/22/exe ls: cannot read symbolic link /proc/2215/exe: No such file or directory lrwxrwxrwx 1 root root 0 Apr 28 22:53 /proc/2215/exe ls: cannot read symbolic link /proc/23/exe: No such file or directory lrwxrwxrwx 1 root root 0 Apr 28 22:53 /proc/23/exe ls: cannot read symbolic link /proc/24/exe: No such file or directory lrwxrwxrwx 1 root root 0 Apr 28 22:53 /proc/24/exe ls: cannot read symbolic link /proc/25/exe: No such file or directory lrwxrwxrwx 1 root root 0 Apr 28 22:53 /proc/25/exe ls: cannot read symbolic link /proc/3/exe: No such file or directory lrwxrwxrwx 1 root root 0 Apr 28 22:53 /proc/3/exe ls: cannot read symbolic link /proc/30/exe: No such file or directory lrwxrwxrwx 1 root root 0 Apr 28 22:53 /proc/30/exe ls: cannot read symbolic link /proc/30347/exe: No such file or directory lrwxrwxrwx 1 root root 0 Apr 28 22:53 /proc/30347/exe ls: cannot read symbolic link /proc/31/exe: No such file or directory lrwxrwxrwx 1 root root 0 Apr 28 22:53 /proc/31/exe ls: cannot read symbolic link /proc/32/exe: No such file or directory lrwxrwxrwx 1 root root 0 Apr 28 22:53 /proc/32/exe ls: cannot read symbolic link /proc/3843/exe: No such file or directory lrwxrwxrwx 1 root root 0 Apr 28 22:53 /proc/3843/exe ls: cannot read symbolic link /proc/4/exe: No such file or directory lrwxrwxrwx 1 root root 0 Apr 28 22:53 /proc/4/exe ls: cannot read symbolic link /proc/4797/exe: No such file or directory lrwxrwxrwx 1 root root 0 Apr 28 22:53 /proc/4797/exe ls: cannot read symbolic link /proc/5/exe: No such file or directory lrwxrwxrwx 1 root root 0 Apr 28 22:53 /proc/5/exe ls: cannot read symbolic link /proc/7/exe: No such file or directory lrwxrwxrwx 1 root root 0 Apr 28 22:53 /proc/7/exe ls: cannot read symbolic link /proc/74/exe: No such file or directory lrwxrwxrwx 1 root root 0 Apr 28 22:53 /proc/74/exe ls: cannot read symbolic link /proc/8/exe: No such file or directory lrwxrwxrwx 1 root root 0 Apr 28 22:53 /proc/8/exe ls: cannot read symbolic link /proc/87/exe: No such file or directory lrwxrwxrwx 1 root root 0 Apr 28 22:53 /proc/87/exe ls: cannot read symbolic link /proc/9/exe: No such file or directory lrwxrwxrwx 1 root root 0 Apr 28 22:53 /proc/9/exe ls: cannot read symbolic link /proc/93/exe: No such file or directory lrwxrwxrwx 1 root root 0 Apr 28 22:53 /proc/93/exe ls: cannot read symbolic link /proc/94/exe: No such file or directory lrwxrwxrwx 1 root root 0 Apr 28 22:53 /proc/94/exe At least all of these pids I checked were kernel threads for which the above behaviour is IIRC normal: # ps auxwww | fgrep --color '[' root 1 0.0 0.0 13228 668 ? Ss 2013 2:21 init [2] root 2 0.0 0.0 0 0 ? S 2013 0:00 [kthreadd] root 3 0.0 0.0 0 0 ? S 2013 36:33 [ksoftirqd/0] root 4 0.0 0.0 0 0 ? S 2013 0:00 [kworker/0:0] root 5 0.0 0.0 0 0 ? S< 2013 0:00 [kworker/0:0H] root 7 0.0 0.0 0 0 ? S 2013 0:00 [migration/0] root 8 0.0 0.0 0 0 ? S 2013 0:00 [rcu_bh] root 9 0.0 0.0 0 0 ? S 2013 45:12 [rcu_sched] root 10 0.0 0.0 0 0 ? S 2013 1:00 [watchdog/0] root 11 0.0 0.0 0 0 ? S< 2013 0:00 [khelper] root 12 0.0 0.0 0 0 ? S 2013 0:00 [kdevtmpfs] root 13 0.0 0.0 0 0 ? S< 2013 0:00 [netns] root 14 0.0 0.0 0 0 ? S 2013 0:00 [xenwatch] root 15 0.0 0.0 0 0 ? S 2013 0:00 [xenbus] root 16 0.0 0.0 0 0 ? S< 2013 0:00 [writeback] root 17 0.0 0.0 0 0 ? S< 2013 0:00 [kintegrityd] root 18 0.0 0.0 0 0 ? S< 2013 0:00 [bioset] root 19 0.0 0.0 0 0 ? S< 2013 0:00 [kblockd] root 21 0.0 0.0 0 0 ? S 2013 0:03 [khungtaskd] root 22 0.0 0.0 0 0 ? S 2013 75:19 [kswapd0] root 23 0.0 0.0 0 0 ? SN 2013 0:00 [ksmd] root 24 0.0 0.0 0 0 ? S 2013 0:00 [fsnotify_mark] root 25 0.0 0.0 0 0 ? S< 2013 0:00 [crypto] root 30 0.0 0.0 0 0 ? S< 2013 0:00 [kthrotld] root 31 0.0 0.0 0 0 ? S 2013 0:00 [khvcd] root 32 0.0 0.0 0 0 ? S< 2013 0:00 [deferwq] root 74 0.0 0.0 0 0 ? S< 2013 20:15 [kworker/0:1H] root 87 0.0 0.0 0 0 ? S< 2013 0:00 [bioset] root 93 0.0 0.0 0 0 ? S 2013 13:14 [jbd2/xvda1-8] root 94 0.0 0.0 0 0 ? S< 2013 0:00 [ext4-rsv-conver] root 2215 0.0 0.0 0 0 ? S 2013 0:00 [kauditd] root 3843 0.0 0.0 0 0 ? S Apr21 0:19 [kworker/u2:2] root 4797 0.0 0.0 0 0 ? S Mar29 0:00 [kworker/u2:0] root 9631 0.0 0.0 82504 2784 ? Ss Apr26 0:00 sshd: abe [priv] root 19088 0.0 0.0 10044 636 pts/5 S+ 01:16 0:00 fgrep --color [ root 30347 0.0 0.0 0 0 ? S Jan23 12:00 [kworker/0:2] root 31214 0.0 0.0 84564 2780 ? Ss Apr23 0:00 sshd: abe [priv] But the /proc/$pid/exe symlink is always there, it just doesn't have a target. Which should be ok for kernel threads. > :-) - could you please run: > > cat /proc/version Linux version 3.12-trunk-amd64 (debian-ker...@lists.debian.org) (gcc version 4.8.2 (Debian 4.8.2-7) ) #1 SMP Debian 3.12.3-1~exp1 (2013-12-05) > strings -n 30 /boot/vmlinuz-3.12-trunk-amd64 > (assuming it's your running kernel image) It's not. The kernel image which runs is the uncompressed version of the kernel image you mentioned: /boot/vmlinux-3.12-trunk-amd64. (Note the "x" instead of "z".) See http://noone.org/blog/English/Computer/Debian/Running%20a%20Sid%20DomU%20on%20a%20Squeeze%20Dom0.futile for the background of running uncompressed kernel images instead of the original ones. I don't want to include all the garbage that command produces for /boot/vmlinux-3.12-trunk-amd64, so here's a summary which may already help: # strings -n 30 /boot/vmlinux-3.12-trunk-amd64 | wc -l 5005 # strings -n 30 /boot/vmlinux-3.12-trunk-amd64 | head D$d3D$`3D$h3D$l3D$D3D$H3D$L3D$P !writable_page_tables|pae_pgdir_above_4gb %s version %s (debian-ker...@lists.debian.org) (gcc version 4.8.2 (Debian 4.8.2-7) ) %s Linux version 3.12-trunk-amd64 (debian-ker...@lists.debian.org) (gcc version 4.8.2 (Debian 4.8.2-7) ) #1 SMP Debian 3.12.3-1~exp1 (2013-12-05) "addr %p entries %u", REC->addr, REC->entries "dt %p entrynum %d type %d desc %016llx", REC->dt, REC->entrynum, REC->type, (unsigned long long)REC->desc "dt %p entrynum %d", REC->dt, REC->entrynum "dt %p entrynum %d entry %016llx", REC->dt, REC->entrynum, (unsigned long long)REC->desc "%s cr3 %lx", REC->kernel ? "kernel" : "user", REC->cr3 "ncpus %d mm %p addr %lx, end %lx", REC->ncpus, REC->mm, REC->addr, REC->end # ;-) For the according compressed image it's far less output: # strings -n 30 /boot/vmlinuz-3.12-trunk-amd64 This kernel requires an %s CPU, This kernel requires the following features not present on the CPU: Probing EDD (edd=off to disable)... WARNING: Ancient bootloader, some functionality may be limited! Unable to boot - please use a kernel appropriate for your CPU. A20 gate not responding, unable to boot... 0123456789ABCDEFPress <ENTER> to see video modes available, <SPACE> to continue, or wait 30 sec Enter a video mode or "scan" to scan for additional modes: Undefined video mode number: %x 3.12-trunk-amd64 (debian-ker...@lists.debian.org) #1 SMP Debian 3.12.3-1~exp1 (2013-12-05) early console in decompress_kernel Destination address inappropriately aligned XZ decompressor ran out of memory Input is not in the XZ format (wrong magic bytes) Input was encoded with settings that are not supported by this XZ decoder Kernel is not a valid ELF file Failed to allocate space for phdrs Failed to alloc mem for initrds Failed to get initrd info size Failed to alloc mem for initrd info Failed to alloc highmem for initrds We've run out of free low memory Failed to get handle for LOADED_IMAGE_PROTOCOL Failed to alloc lowmem for boot params Failed to alloc mem for cmdline Failed to alloc mem for gdt structure Failed to alloc mem for idt structure Failed to alloc mem for kernel # And since the chance seems high that /boot/vmlinux* may confuse needrestart: # ls -l /boot/vmlinu* -rw-r--r-- 1 root root 12307184 Apr 21 02:56 /boot/vmlinux-2.6.32-5-xen-amd64 -rw-r--r-- 1 root root 12093792 Apr 21 02:56 /boot/vmlinux-3.10-2-amd64 -rw-r--r-- 1 root root 12093792 Apr 21 02:56 /boot/vmlinux-3.10-3-amd64 -rw-r--r-- 1 root root 14281056 Apr 21 02:56 /boot/vmlinux-3.11-1-amd64 -rw-r--r-- 1 root root 14281056 Apr 21 02:56 /boot/vmlinux-3.11-2-amd64 -rw-r--r-- 1 root root 12110176 Apr 21 02:56 /boot/vmlinux-3.11-rc4-amd64 -rw-r--r-- 1 root root 12110176 Apr 21 02:56 /boot/vmlinux-3.11-rc7-amd64 -rw-r--r-- 1 root root 12106080 Apr 21 02:56 /boot/vmlinux-3.11-trunk-amd64 -rw-r--r-- 1 root root 14305632 Apr 21 02:56 /boot/vmlinux-3.12-1-amd64 -rw-r--r-- 1 root root 14293344 Apr 21 02:56 /boot/vmlinux-3.12-rc7-amd64 -rw-r--r-- 1 root root 14305632 Apr 21 02:56 /boot/vmlinux-3.12-trunk-amd64 -rw-r--r-- 1 root root 14334304 Apr 21 02:56 /boot/vmlinux-3.13-1-amd64 -rw-r--r-- 1 root root 14338400 Apr 21 02:56 /boot/vmlinux-3.13-rc6-amd64 -rw-r--r-- 1 root root 14338400 Apr 21 02:56 /boot/vmlinux-3.13-trunk-amd64 -rw-r--r-- 1 root root 14354784 Apr 21 02:56 /boot/vmlinux-3.14-rc5-amd64 -rw-r--r-- 1 root root 14358880 Apr 21 02:56 /boot/vmlinux-3.14-rc7-amd64 -rw-r--r-- 1 root root 14354784 Apr 21 02:56 /boot/vmlinux-3.14-trunk-amd64 -rw-r--r-- 1 root root 11704752 Apr 21 02:56 /boot/vmlinux-3.2.0-4-amd64 -rw-r--r-- 1 root root 11622832 Apr 21 02:57 /boot/vmlinux-3.3.0-trunk-amd64 -rw-r--r-- 1 root root 11651504 Apr 21 02:57 /boot/vmlinux-3.4-trunk-amd64 -rw-r--r-- 1 root root 11671904 Apr 21 02:57 /boot/vmlinux-3.5-trunk-amd64 -rw-r--r-- 1 root root 11704672 Apr 21 02:57 /boot/vmlinux-3.6-trunk-amd64 -rw-r--r-- 1 root root 11741536 Apr 21 02:57 /boot/vmlinux-3.7-trunk-amd64 -rw-r--r-- 1 root root 11749728 Apr 21 02:57 /boot/vmlinux-3.8-2-amd64 -rw-r--r-- 1 root root 12036448 Apr 21 02:57 /boot/vmlinux-3.9-1-amd64 -rw-r--r-- 1 root root 2482400 Feb 25 2013 /boot/vmlinuz-2.6.32-5-xen-amd64 -rw-r--r-- 1 root root 2471632 Aug 18 2013 /boot/vmlinuz-3.10-2-amd64 -rw-r--r-- 1 root root 2473056 Sep 11 2013 /boot/vmlinuz-3.10-3-amd64 -rw-r--r-- 1 root root 2800768 Nov 1 19:46 /boot/vmlinuz-3.11-1-amd64 -rw-r--r-- 1 root root 2796128 Dec 5 05:44 /boot/vmlinuz-3.11-2-amd64 -rw-r--r-- 1 root root 2497648 Aug 9 2013 /boot/vmlinuz-3.11-rc4-amd64 -rw-r--r-- 1 root root 2515056 Sep 2 2013 /boot/vmlinuz-3.11-rc7-amd64 -rw-r--r-- 1 root root 2489376 Sep 12 2013 /boot/vmlinuz-3.11-trunk-amd64 -rw-r--r-- 1 root root 2842624 Feb 2 17:56 /boot/vmlinuz-3.12-1-amd64 -rw-r--r-- 1 root root 2834384 Oct 30 2013 /boot/vmlinuz-3.12-rc7-amd64 -rw-r--r-- 1 root root 2837728 Dec 6 09:32 /boot/vmlinuz-3.12-trunk-amd64 -rw-r--r-- 1 root root 2888848 Apr 16 07:00 /boot/vmlinuz-3.13-1-amd64 -rw-r--r-- 1 root root 2885264 Dec 31 12:34 /boot/vmlinuz-3.13-rc6-amd64 -rw-r--r-- 1 root root 2883968 Jan 21 12:34 /boot/vmlinuz-3.13-trunk-amd64 -rw-r--r-- 1 root root 2939840 Apr 29 13:42 /boot/vmlinuz-3.14-1-amd64 -rw-r--r-- 1 root root 2921312 Mar 7 18:03 /boot/vmlinuz-3.14-rc5-amd64 -rw-r--r-- 1 root root 2923280 Mar 18 20:34 /boot/vmlinuz-3.14-rc7-amd64 -rw-r--r-- 1 root root 2923872 Apr 17 20:48 /boot/vmlinuz-3.14-trunk-amd64 -rw-r--r-- 1 root root 2837920 Apr 23 06:01 /boot/vmlinuz-3.2.0-4-amd64 -rw-r--r-- 1 root root 2843600 May 18 2012 /boot/vmlinuz-3.3.0-trunk-amd64 -rw-r--r-- 1 root root 2891312 Jun 26 2012 /boot/vmlinuz-3.4-trunk-amd64 -rw-r--r-- 1 root root 2911936 Oct 4 2012 /boot/vmlinuz-3.5-trunk-amd64 -rw-r--r-- 1 root root 2332720 Dec 5 2012 /boot/vmlinuz-3.6-trunk-amd64 -rw-r--r-- 1 root root 2392544 Feb 15 2013 /boot/vmlinuz-3.7-trunk-amd64 -rw-r--r-- 1 root root 2429168 May 16 2013 /boot/vmlinuz-3.8-2-amd64 -rw-r--r-- 1 root root 2445696 Jun 30 2013 /boot/vmlinuz-3.9-1-amd64 # But then again this is a speciality of only one of three machines where needrestart throws these warnings. Actually I'm not sure if I saw all types of warnings on at least two machines. But at least the /usr/share/perl5/NeedRestart/Kernel.pm warnings were _not_ on all machines where I saw warnings. Here's the bunch of output from another, more "normal" machine (real hardware, not a virtual machine), also Sid amd64: # uname -a Linux c-cactus 3.14-trunk-amd64 #1 SMP Debian 3.14-1~exp1 (2014-04-09) x86_64 GNU/Linux # cat /proc/version Linux version 3.14-trunk-amd64 (debian-ker...@lists.debian.org) (gcc version 4.8.2 (Debian 4.8.2-16) ) #1 SMP Debian 3.14-1~exp1 (2014-04-09) # strings -n 30 /boot/vmlinuz-3.14-trunk-amd64 This kernel requires an %s CPU, This kernel requires the following features not present on the CPU: Probing EDD (edd=off to disable)... WARNING: Ancient bootloader, some functionality may be limited! Unable to boot - please use a kernel appropriate for your CPU. A20 gate not responding, unable to boot... 0123456789ABCDEFPress <ENTER> to see video modes available, <SPACE> to continue, or wait 30 sec Enter a video mode or "scan" to scan for additional modes: Undefined video mode number: %x 3.14-trunk-amd64 (debian-ker...@lists.debian.org) #1 SMP Debian 3.14-1~exp1 (2014-04-09) early console in decompress_kernel Destination address inappropriately aligned XZ decompressor ran out of memory Input is not in the XZ format (wrong magic bytes) Input was encoded with settings that are not supported by this XZ decoder Kernel is not a valid ELF file Failed to allocate space for phdrs Failed to alloc mem for file handle list Failed to alloc mem for file info Failed to alloc highmem for files We've run out of free low memory Failed to get handle for LOADED_IMAGE_PROTOCOL Failed to alloc lowmem for boot params Failed to alloc mem for gdt structure ERROR: Failed to allocate usable memory for kernel. # needrestart Scanning processes........................................................................................................................................ Scanning candidates..........................................Use of uninitialized value in pattern match (m//) at /usr/sbin/needrestart line 285, <HPIPE> line 50. Use of uninitialized value in pattern match (m//) at /usr/sbin/needrestart line 285, <HPIPE> line 50. Use of uninitialized value in pattern match (m//) at /usr/sbin/needrestart line 285, <HPIPE> line 50. Use of uninitialized value in pattern match (m//) at /usr/sbin/needrestart line 285, <HPIPE> line 50. Use of uninitialized value in pattern match (m//) at /usr/sbin/needrestart line 285, <HPIPE> line 50. Use of uninitialized value in pattern match (m//) at /usr/sbin/needrestart line 285, <HPIPE> line 50. Use of uninitialized value in pattern match (m//) at /usr/sbin/needrestart line 285, <HPIPE> line 50. Use of uninitialized value in pattern match (m//) at /usr/sbin/needrestart line 285, <HPIPE> line 50. Use of uninitialized value in pattern match (m//) at /usr/sbin/needrestart line 285, <HPIPE> line 50. Use of uninitialized value in pattern match (m//) at /usr/sbin/needrestart line 285, <HPIPE> line 50. ................ Running kernel seems to be up-to-date. No services required to be restarted. # And after installing linux-image-3.14-1-amd64 and upgrading a bunch of packages (Sid updates for about a day or two), run by the APT hook: [...] Scanning processes..................................................................................................................................... Scanning candidates..........................................Use of uninitialized value in pattern match (m//) at /usr/sbin/needrestart line 285, <HPIPE> line 50. Use of uninitialized value in pattern match (m//) at /usr/sbin/needrestart line 285, <HPIPE> line 50. Use of uninitialized value in pattern match (m//) at /usr/sbin/needrestart line 285, <HPIPE> line 50. Use of uninitialized value in pattern match (m//) at /usr/sbin/needrestart line 285, <HPIPE> line 50. Use of uninitialized value in pattern match (m//) at /usr/sbin/needrestart line 285, <HPIPE> line 50. Use of uninitialized value in pattern match (m//) at /usr/sbin/needrestart line 285, <HPIPE> line 50. Use of uninitialized value in pattern match (m//) at /usr/sbin/needrestart line 285, <HPIPE> line 50. Use of uninitialized value in pattern match (m//) at /usr/sbin/needrestart line 285, <HPIPE> line 50. Use of uninitialized value in pattern match (m//) at /usr/sbin/needrestart line 285, <HPIPE> line 50. Use of uninitialized value in pattern match (m//) at /usr/sbin/needrestart line 285, <HPIPE> line 50. ............... Pending kernel upgrade! Running kernel version: 3.14-trunk-amd64 Diagnostics: Running not the expected kernel version 3.14-1-amd64. You should consider to reboot this machine to activate the pending kernel upgrade. You need to reboot MANUALLY! [Return] No services required to be restarted. [...] Since this doesn't exhibit the warnings from /usr/share/perl5/NeedRestart/Kernel.pm I suspect that they indeed come from those uncompressed kernel images I use on the machine on which I reported the issue. And the HPIPE warnings are probably a different issue which is present on more than one machine. Will have to check the third machine for the types of warnings needrestart emits there. HTH. P.S.: Feel free to clone this report if you want to track the probably at least two different issues in here separately. Kind regards, Axel -- /~\ Plain Text Ribbon Campaign | Axel Beckert \ / Say No to HTML in E-Mail and News | a...@deuxchevaux.org (Mail) X See http://www.nonhtmlmail.org/campaign.html | a...@noone.org (Mail+Jabber) / \ I love long mails: http://email.is-not-s.ms/ | http://noone.org/abe/ (Web) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
