Bug#1041836: Version Correction
Please note that the bug is in version 2.36-9+deb12u1 i.e. the new version just released to Stable. reportbug saw 2.36-9 because I had to revert to the previous version before anything but static executables would work. --Mike
Bug#1041836: libc6 2.36-9+deb12u1 stack smashing on some but not all amd64
Package: libc6 Version: 2.36-9 Severity: critical Justification: breaks the whole system Dear Maintainer, Installing libc6_2.36-9+deb12u1_amd64.deb on some but not all systems results in every dynamically linked program dying with a spurious report of stack smashing. Getting back to a working system required use of busybox to get bash-static and also creating a fake perl as a shell script containing exit 0 (because /bin/true is dynamic) and then busybox again to wget and dpkg install the 2.36-9. I repeated this three times to be sure. Works OK on e.g. Intel(R) Xeon(R) CPU L5520 @ 2.27GHz Stack smashing on e.g. Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz Preparing to unpack .../libc6_2.36-9+deb12u1_amd64.deb ... Unpacking libc6:amd64 (2.36-9+deb12u1) over (2.36-9) ... *** stack smashing detected ***: terminated dpkg: error while cleaning up: rm command for cleanup subprocess was killed by signal (Aborted) *** stack smashing detected ***: terminated E: Sub-process /usr/bin/dpkg exited unexpectedly # ls -l *** stack smashing detected ***: terminated Aborted # Both successes and failures were on multiarch systems with i386 although that does not seem to be relevant. -- System Information: Debian Release: 12.1 APT prefers stable-updates APT policy: (2000, 'stable-updates'), (2000, 'stable-security'), (2000, 'stable') merged-usr: no Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-10-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/bash-static Init: sysvinit (via /sbin/init) Versions of packages libc6 depends on: ii libgcc-s1 12.2.0-14 Versions of packages libc6 recommends: ii libidn2-0 2.3.3-1+b1 Versions of packages libc6 suggests: ii debconf [debconf-2.0] 1.5.82 ii glibc-doc 2.36-9+deb12u1 ii libc-l10n 2.36-9+deb12u1 pn libnss-nis pn libnss-nisplus ii locales2.36-9 -- no debconf information
Bug#610185: sysv-rc.postinst needs to provide more balanced description of insserv pros and cons
Package: sysv-rc Version: 2.88dsf-13.1 Severity: critical Justification: causes serious data loss Blindly enabling insserv can result in unbootable systems or systems which boot but don't start all services. sysv-rc.postinst currently states that enabling insserv is recommended, with no mention of the possible severe consequences. This bug is critical rather than grave because the lost data - the Snn and Knn values - cannot be recovered without restoring a backup. (In fact it's slightly worse than that - if you merely restore /etc insserv will eat it again. You have to use undocumented magic to prevent this.) Patch attached. -- System Information: Debian Release: 6.0 APT prefers testing APT policy: (990, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages sysv-rc depends on: ii debconf [debconf-2.0] 1.5.36 Debian configuration management sy ii insserv 1.14.0-2 Tool to organize boot sequence usi ii sysvinit-utils 2.88dsf-13.1 System-V-like utilities Versions of packages sysv-rc recommends: ii lsb-base 3.2-23.1 Linux Standard Base 3.2 init scrip Versions of packages sysv-rc suggests: pn bum none (no description available) pn sysv-rc-conf none (no description available) -- debconf information: sysv-rc/unable-to-convert: * sysv-rc/convert-legacy: true diff -ruN sysvinit-2.88dsf/debian/sysv-rc.templates sysvinit-2.88dsf.NEW/debian/sysv-rc.templates --- sysvinit-2.88dsf/debian/sysv-rc.templates 2011-01-15 14:30:43.0 -0800 +++ sysvinit-2.88dsf.NEW/debian/sysv-rc.templates 2011-01-15 14:38:16.0 -0800 @@ -12,13 +12,18 @@ Default: true _Description: Migrate legacy boot sequencing to dependency-based sequencing? The boot system is prepared to migrate to dependency-based sequencing. - This is an irreversible step, but one that is recommended: it allows - the boot process to be optimized for speed and efficiency, and provides - a more resilient framework for development. + This is an irreversible step - restoring your /etc will not undo it. It + affords slightly faster booting and a different framework for sequencing + system start up which some people prefer. However it may not correctly + boot a complex system without further effort on your part. . A full rationale is detailed in /usr/share/doc/sysv-rc/README.Debian. If you choose not to migrate now, you can do so later by running dpkg-reconfigure sysv-rc. + . + If you do need to manually reverse this irreversible step first + touch /etc/init.d/.legacy-bootordering and then the files in + /var/lib/update-rc.d will help you to recover most of the way. Template: sysv-rc/unable-to-convert Type: note
Bug#487606: cups.prerm deletes /usr/lib/cups/backend/smb which belongs to smbclient
Package: cups Version: 1.3.7-7 Severity: serious Justification: see debian-devel thread cups.prerm deletes the /usr/lib/cups/backend/smb symlink which belongs to smbclient package. Several systems here were bitten by this during the cupsys-cups transition, as cupsys.prerm had the same problem. I couldn't find a specific policy section which prohibited this so I asked on debian-devel where DD's said it was so obviously wring that it didn't need a policy section: http://lists.debian.org/debian-devel/2008/06/msg00613.html Workaround is to reinstall smbclient on top of itself in order for SMB printers to work. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.24-1-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages cups depends on: ii adduser 3.108 add and remove users and groups ii cups-common 1.3.7-7 Common UNIX Printing System(tm) - ii debconf [debconf-2.0]1.5.22 Debian configuration management sy ii ghostscript 8.62.dfsg.1-2.1 The GPL Ghostscript PostScript/PDF ii libavahi-compat-libdnssd 0.6.22-3Avahi Apple Bonjour compatibility ii libc62.7-10 GNU C Library: Shared libraries ii libcups2 1.3.7-7 Common UNIX Printing System(tm) - ii libcupsimage21.3.7-7 Common UNIX Printing System(tm) - ii libdbus-1-3 1.2.1-2 simple interprocess messaging syst ii libgnutls26 2.2.5-1 the GNU TLS library - runtime libr ii libkrb53 1.6.dfsg.3-2MIT Kerberos runtime libraries ii libldap-2.4-22.4.9-1 OpenLDAP libraries ii libpam0g 0.99.7.1-6 Pluggable Authentication Modules l ii libpaper11.1.23 library for handling paper charact ii libslp1 1.2.1-7.3 OpenSLP libraries ii lsb-base 3.2-12 Linux Standard Base 3.2 init scrip ii perl-modules 5.10.0-10 Core Perl modules ii procps 1:3.2.7-8 /proc file system utilities ii ssl-cert 1.0.20 simple debconf wrapper for OpenSSL ii xpdf-utils [poppler-util 3.02-1.3Portable Document Format (PDF) sui Versions of packages cups recommends: pn avahi-utils none (no description available) ii cups-client 1.3.7-7Common UNIX Printing System(tm) - ii foomatic-filters 3.0.2-20080211-3.1 OpenPrinting printer support - fil ii smbclient 2:3.0.30-2 a LanManager-like simple client fo -- debconf information: cupsys/raw-print: true cupsys/backend: ipp, lpd, parallel, scsi, serial, socket, usb, snmp, dnssd -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#478547: grub-install raid1 ext3 failure - regression from Etch
On Wed April 30 2008 03:38:29 Robert Millan wrote: Please could you test the attached patch? The patched version of grub-install ran without errors on the raid1 ext3 system and the system was was subsequently rebooted successfully. Thanks, --Mike Bird -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#478547: grub-install raid1 ext3 failure - regression from Etch
On Wed April 30 2008 11:21:49 Mike Bird wrote: On Wed April 30 2008 03:38:29 Robert Millan wrote: Please could you test the attached patch? The patched version of grub-install ran without errors on the raid1 ext3 system and the system was was subsequently rebooted successfully. Also confirmed on second raid1 ext3 system and on a non-RAID ext3 system. --Mike Bird -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#478547: grub-install raid1 ext3 failure - regression from Etch
Package: grub Version: 0.97-37 Severity: critical Justification: breaks the whole system grub-install '(hd0)' reports The file /boot/grub/stage1 not read correctly. The problem occurs when grub-install is using dump for some kind of verification. The log is written to /tmp file with a random name: # cat grubJM5Q31 GNU GRUB version 0.97 (640K lower / 3072K upper memory) [ Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists the possible completions of a device/filename. ] grub dump (md0)/grub/stage1 /tmp/grubrakRL1 Error 23: Error while parsing number grub quit This is a regression from Etch. In fact, simply copying /usr/sbin/grub-install from Etch into another directory and running it without replacing any other grub component works. This happens on a lot of systems but most people don't run grub-install on a working system. We have a policy of always running grub-install after updating the grub package so we see this problem sooner than most. -- Package-specific info: *** BEGIN /boot/grub/device.map (fd0) /dev/fd0 (hd0) /dev/hde (hd1) /dev/hdg *** END /boot/grub/device.map *** BEGIN /proc/mounts /dev/md1 / ext3 rw,errors=remount-ro,data=ordered 0 0 /dev/md1 /dev/.static/dev ext3 rw,errors=remount-ro,data=ordered 0 0 /dev/mapper/VG0-ACCT /store/ACCT ext3 rw,data=ordered 0 0 /dev/mapper/VG0-IMS++ /cache/IMS++ ext3 rw,data=ordered 0 0 /dev/mapper/VG0-JPG /cache/JPG ext3 rw,data=ordered 0 0 /dev/mapper/VG0-MP3 /store/MP3 ext3 rw,data=ordered 0 0 /dev/mapper/VG0-OLD /store/OLD ext3 rw,noatime,data=ordered 0 0 /dev/mapper/VG0-mpa--sf.yosemite.net.1 /BACKUP/mpa-sf.yosemite.net.1 ext3 rw,noatime,data=ordered 0 0 /dev/mapper/VG0-mpa--sf.yosemite.net.2 /BACKUP/mpa-sf.yosemite.net.2 ext3 rw,noatime,data=ordered 0 0 /dev/mapper/VG0-mpa--sf.yosemite.net.3 /BACKUP/mpa-sf.yosemite.net.3 ext3 rw,noatime,data=ordered 0 0 /dev/md0 /boot ext3 rw,data=ordered 0 0 *** END /proc/mounts *** BEGIN /boot/grub/menu.lst # menu.lst - See: grub(8), info grub, update-grub(8) #grub-install(8), grub-floppy(8), #grub-md5-crypt, /usr/share/doc/grub #and /usr/share/doc/grub-doc/. ## default num # Set the default entry to the entry number NUM. Numbering starts from 0, and # the entry number 0 is the default if the command is not used. # # You can specify 'saved' instead of a number. In this case, the default entry # is the entry saved with the command 'savedefault'. # WARNING: If you are using dmraid do not change this entry to 'saved' or your # array will desync and will not let you boot your system. default 0 ## timeout sec # Set a timeout, in SEC seconds, before automatically booting the default entry # (normally the first entry defined). timeout 5 # Pretty colours color cyan/blue white/blue ### PASSWORD LINE REMOVED ### # If used in the first section of a menu file, disable all interactive editing # control (menu entry editor and command-line) and entries protected by the # command 'lock' ### PASSWORD LINE REMOVED ### ### PASSWORD LINE REMOVED ### ### PASSWORD LINE REMOVED ### # # examples # # title Windows 95/98/NT/2000 # root (hd0,0) # makeactive # chainloader +1 # # title Linux # root (hd0,1) # kernel/vmlinuz root=/dev/hda2 ro # # # Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST ### BEGIN AUTOMAGIC KERNELS LIST ## lines between the AUTOMAGIC KERNELS LIST markers will be modified ## by the debian update-grub script except for the default options below ## DO NOT UNCOMMENT THEM, Just edit them to your needs ## ## Start Default Options ## ## default kernel options ## default kernel options for automagic boot options ## If you want special options for specific kernels use kopt_x_y_z ## where x.y.z is kernel version. Minor versions can be omitted. ## e.g. kopt=root=/dev/hda1 ro ## kopt_2_6_8=root=/dev/hdc1 ro ## kopt_2_6_8_2_686=root=/dev/hdc2 ro # kopt=root=/dev/md1 ro panic=60 ## default grub root device ## e.g. groot=(hd0,0) # groot=(hd0,0) ## should update-grub create alternative automagic boot options ## e.g. alternative=true ## alternative=false # alternative=true ## should update-grub lock alternative automagic boot options ## e.g. lockalternative=true ## lockalternative=false # lockalternative=false ## additional options to use with the default boot option, but not with the ## alternatives ## e.g. defoptions=vga=791 resume=/dev/hda5 # defoptions= ## should update-grub lock old automagic boot options ## e.g. lockold=false ## lockold=true # lockold=false ## Xen hypervisor options to use with the default Xen boot option # xenhopt= ## Xen Linux kernel options to use with the default Xen boot option # xenkopt=console=tty0 ##
