Bug#920284: debian-installer: Installing Debain 9.6 on amd64 KVM via netinst fails in "select and install software"
Cyril, Thanks for the response! I was able to consistently reproduce the problem I described as of January 23rd. As of today, a clean installation of Debian 9.6 on my VM worked without difficulty. Looking at the error message, it would seem that the hash that apt was using for something in security-cdb.debian.org didn't match what I downloaded. In fact, I just finished the install and got a similar message by running "sudo apt-get install lxde" on the terminal: Err:4 http://security-cdn.debian.org/debian-security stretch/updates/main amd64 libqt5gui5 amd64 5.7.1+fsg-3+deb9u1 Hash Sum mismatch Hashes of expected file: - SHA256:aa740aa9fada96791cd254a26afbebca52267a14b072c33f93ada1e3791c8aec - SHA1:2b50202d9bb2ee257027035498b9f826fc2202fe [weak] - MD5Sum:7be38aee5f595e7ebd95b0f77bf60580 [weak] - Filesize:2449840 [weak] Hashes of received file: - SHA256:0611d7b8e5113bdc7257aa38f8500e2b78ff9fd91a6555114a482a101b7db835 - SHA1:07861e147f8df4e45336d17381731d6d95e5801c [weak] - MD5Sum:f45d307aea95e1ccacb6e7c13a32b33e [weak] - Filesize:43776 [weak] Last modification reported: Thu, 06 Dec 2018 18:05:06 + This occurred immediately upon running "sudo apt-get install lxde"; there was no visible timeout. That said, while the expected file size seems sensible (https://packages.debian.org/stretch/libqt5gui5 seems to indicate that the file should be ~2392.4kb), the received filesize is ridiculously small. It's possible, if no else else can reproduce this problem, that it may be the result of an errant proxy or similar interference on my network: something that's essentially truncating the file. If that's true, though, shouldn't apt-get be producing a corresponding error message (e.g. "download failed due to interrupted connection") rather than assuming that the download is complete? That is, if the HTTP request gets a response with the file size in the header, apt should be able to tell if it successfully downloaded the whole thing, right? The problem itself seems to be less reproducible than it was several days ago: simply re-running the "apt-get" command on the installed system seems to have solved it for now (while, on January 23rd, I was unable to get past the "Select and Install Software" step in the installer). This seems like more of a bug with how apt-get handles failure. Is there a way to reassign this bug to that package? Thanks, Zach Control: tag -1 - d-i Hi Zachary, And thanks for your report. Zachary Palmer (2019-01-23): I am installing Debian 9.6 using a netinst image on an amd64 virtual machine (kvm). Everything runs as expected until the "Select and Install Software" step, which fails with the generic message "Installation step failed". Terminal 4 shows some interesting output: Failed to fetch http://security-cdn.debian.org/debian-security/pool/updates/main/o/openssl/libssl1.1_1.1.0j-1~deb9u1_amd64.deb Writing more data than expected (1235886 > 1231594) Hashes of expected file: - SHA256:dddf4ff686845b82c6c778a70f1f607d0bb9f8aa43f2fb7983db4ff1a55f5fae - SHA1:5d754764288ae1751d7a05d11c801cde71456602 [weak] - MD5Sum:5e3b6c66100964833307d3a943918275 [weak] E : Unable to fetch some archives, maybe run apt-get update or try with --fix-issing? I don't think that this is the only file it failed to fetch, as I see the tail of a similar message further up in the terminal. (I wasn't able to scroll to see it.) Please hit “reply all”, attaching /var/log/installer/syslog (compressed, to make sure it doesn't get rejected due to size on mailing lists), so that we have a look at the whole log. Cheers,
Bug#920284: debian-installer: Installing Debain 9.6 on amd64 KVM via netinst fails in "select and install software"
Package: debian-installer Severity: important Tags: d-i Dear Maintainer, I am installing Debian 9.6 using a netinst image on an amd64 virtual machine (kvm). Everything runs as expected until the "Select and Install Software" step, which fails with the generic message "Installation step failed". Terminal 4 shows some interesting output: Failed to fetch http://security-cdn.debian.org/debian-security/pool/updates/main/o/openssl/libssl1.1_1.1.0j-1~deb9u1_amd64.deb Writing more data than expected (1235886 > 1231594) Hashes of expected file: - SHA256:dddf4ff686845b82c6c778a70f1f607d0bb9f8aa43f2fb7983db4ff1a55f5fae - SHA1:5d754764288ae1751d7a05d11c801cde71456602 [weak] - MD5Sum:5e3b6c66100964833307d3a943918275 [weak] E : Unable to fetch some archives, maybe run apt-get update or try with --fix-issing? I don't think that this is the only file it failed to fetch, as I see the tail of a similar message further up in the terminal. (I wasn't able to scroll to see it.) Repeating the installation step produces the same error. Interestingly, a workaround described in bug 820074 (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820074;msg=14) works here. On terminal 2, I run chroot target bash apt-get install systemd Warnings about /dev/pts are printed, but the package installs correctly. I then log out of the console, return to the installer menu, and re-perform the "Select and Install Software" step. This time, it works just fine and I reach the end of installation without further interruption. The content of Bug 820074 was posted in April 2016 when Stretch was in testing. I am currently using a stable installer for Stretch and the bug seems to still exist. The commands I used to launch KVM were: qemu-img create -f qcow2 hda.img 32g kvm -m 1024 -hda hda.img -cdrom ~/download/debian-9.6.0-amd64-netinst.iso I got similar behavior from a 9.4.0 installer as well. Thank you! *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: 9.6 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-8-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#779457: thunar: Cannot cancel mount authentication
Package: thunar Version: 1.6.3-2 Severity: normal Dear Maintainer, When attempting to cancel the mount of a drive in Thunar (because e.g. it was accidentally clicked in the left-hand navigation panel), a dialog from GNOME policy kit may be presented: Authentication is required to mount... Pressing cancel causes the dialog to be presented again; there appears to be no way to cancel. Thanks! -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages thunar depends on: ii desktop-file-utils 0.22-1 ii exo-utils 0.10.2-4 ii libatk1.0-0 2.14.0-1 ii libc6 2.19-13 ii libcairo2 1.14.0-2.1 ii libdbus-1-3 1.8.12-3 ii libdbus-glib-1-20.102-1 ii libexo-1-0 0.10.2-4 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libglib2.0-02.42.1-1 ii libgtk2.0-0 2.24.25-1 ii libgudev-1.0-0 215-8 ii libice6 2:1.0.9-1+b1 ii libnotify4 0.7.6-2 ii libpango-1.0-0 1.36.8-3 ii libsm6 2:1.2.2-1+b1 ii libthunarx-2-0 1.6.3-2 ii libxfce4ui-1-0 4.10.0-6 ii libxfce4util6 4.10.1-2 ii libxfconf-0-2 4.10.0-3 ii shared-mime-info1.3-1 ii thunar-data 1.6.3-2 Versions of packages thunar recommends: ii dbus-x11 1.8.12-3 ii gvfs 1.22.2-1 ii libfontconfig1 2.11.0-6.3 ii libfreetype6 2.5.2-2 ii libpangocairo-1.0-0 1.36.8-3 ii libpangoft2-1.0-01.36.8-3 ii thunar-volman0.8.0-4 ii tumbler 0.1.30-1+b1 ii xdg-user-dirs0.15-2 ii xfce4-panel 4.10.1-1 Versions of packages thunar suggests: ii thunar-archive-plugin 0.3.1-3 ii thunar-media-tags-plugin 0.2.1-1 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778322: gparted does not issue partprobe before executing resize operations
Package: gparted Version: 0.19.0-2 Severity: minor Dear Maintainer, During the process of recovering from a physical drive failure, I used ddrescue to image the contents of the old drive onto a new one. After doing so, I launched gparted and queued a number of partition moving and resizing operations (to take advantage of the increased size of the larger drive). gparted correctly identified the additional space and resized the GPT, but my first operation -- moving the last partition, an NTFS rescue partition of 12Mb, to the end of the disk -- failed. Upon investigation with strace, this was due to the fact that the device file for /dev/sda5 did not exist. From what I can tell, gparted identifies partitions separately from the device files that exist in /dev (which is good) but then expects them to be present when issuing commands like ntfsresize (which is bad). I would propose the following moficiation: at the start of a series of operations, check to determine if the device files for the partitions exist. If they don't, then issue a partprobe to find them. If they still do not exist, fail with an appropriate error message. (Ideally, the partprobe should be part of the queued command list which appears in the applying pending operations dialog.) For now, the obvious workaround is to run partprobe manually after using ddrescue or a similar tool to image a disk. The only problem is that gparted is clever enough to do some of its work without the device files being present. -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gparted depends on: ii libatkmm-1.6-12.22.7-2.1 ii libc6 2.19-13 ii libgcc1 1:4.9.1-19 ii libglib2.0-0 2.42.1-1 ii libglibmm-2.4-1c2a2.42.0-1 ii libgtk2.0-0 2.24.25-1 ii libgtkmm-2.4-1c2a 1:2.24.4-1.1 ii libpangomm-1.4-1 2.34.0-1.1 ii libparted-fs-resize0 3.2-6 ii libparted23.2-6 ii libsigc++-2.0-0c2a2.4.0-1 ii libstdc++64.9.1-19 ii libuuid1 2.25.2-4 gparted recommends no packages. Versions of packages gparted suggests: pn dmraid none ii dmsetup2:1.02.90-2 ii dosfstools 3.0.27-1 pn gpart none pn jfsutils none pn kpartx none ii mtools 4.0.18-2 ii ntfs-3g1:2014.2.15AR.2-1 pn reiser4progs none pn reiserfsprogs none pn xfsprogs none ii yelp 3.14.1-1 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757369: time: Command-line option --verbose is not observed
Package: time Version: 1.7-24 Severity: normal Dear Maintainer, Running time --verbose echo test on my machine produces the following output: bash: --verbose: command not found real0m0.001s user0m0.000s sys 0m0.000s I would expect --verbose to be consumed by the time program as specified in its man page to adjust the output of the program. Thanks! -- System Information: Debian Release: 7.6 APT prefers stable APT policy: (700, 'stable'), (500, 'stable-updates') Architecture: i386 (i686) Kernel: Linux 3.12-0.bpo.1-686-pae (SMP w/8 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 time depends on: ii dpkg 1.16.15 ii install-info 4.13a.dfsg.1-10 ii libc6 2.13-38+deb7u3 time recommends no packages. time suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#633024: Same Problem
I am also experiencing this bug. My system is configured thus:
/dev/sd{a,b,c,d}{1,2} are partitions for devices
/dev/md1{0,1} are the MD devices for the boot and root, respectively
/dev/md10p1 is the PV for the VG vgboot
/dev/md11p1 is the PV for the VG vg0
/dev/vgboot/boot is an ext4 filesystem mounted at /boot
/dev/vg0/root is an ext4 filesystem mounted at /
In this configuration, the system fails to boot; it drops to an
initramfs prompt. If I run lvm vgchange -a y and hit Ctrl+D, the
system boots. This same system using ext4 directly over /dev/md10p1
booted successfully.
I'm pretty confident that the problem is the use of LVM over MD
partitions. I agree that this is a problem in the mdadm boot script,
which should ensure that the partitions are settled and available before
allowing the system to continue booting. I suppose the only question is
the appropriate policy for the mdadm boot script. Should it wait for
all partitions before booting? Should it always do so or should that be
a configuration option? I'd think that the most sensible default would
be to wait for MD partitions to settle, since any MD with partitions
being assembled at boot time is probably, y'know, important. :)
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#715019: linux-image-3.10-0.bpo.2-686-pae: linux-image-3.11-rc4-686-pae solves my issue
Package: src:linux Version: 3.10.5-1~bpo70+1 Followup-For: Bug #715019 Dear Maintainer, I'm happy to report that installing and booting from linux-image-3.11-rc4-686-pae=3.11~rc4-1~exp1 fixes my issue. I think that this entire bug might be closed by the 3.11 fixes. For my part, I now have a hibernating laptop running on bcache. :) -- Package-specific info: ** Kernel log: boot messages should be attached -- System Information: Debian Release: 7.1 APT prefers stable APT policy: (700, 'stable'), (500, 'stable-updates') Architecture: i386 (i686) Kernel: Linux 3.11-rc4-686-pae (SMP w/8 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 linux-image-3.10-0.bpo.2-686-pae depends on: ii debconf [debconf-2.0] 1.5.49 ii initramfs-tools [linux-initramfs-tool] 0.113~bpo70+1 ii kmod9-3 ii linux-base 3.5 ii module-init-tools 9-3 Versions of packages linux-image-3.10-0.bpo.2-686-pae recommends: ii firmware-linux-free 3.2 ii libc6-i686 2.13-38 Versions of packages linux-image-3.10-0.bpo.2-686-pae suggests: pn debian-kernel-handbook none ii extlinux2:4.05+dfsg-6+deb7u1 ii grub-pc 1.99-27+deb7u1 pn linux-doc-3.10 none Versions of packages linux-image-3.10-0.bpo.2-686-pae is related to: pn firmware-atherosnone pn firmware-bnx2 none pn firmware-bnx2x none pn firmware-brcm80211 none pn firmware-intelwimax none pn firmware-ipw2x00none pn firmware-ivtv none ii firmware-iwlwifi0.39~bpo70+1 pn firmware-libertas none pn firmware-linux none pn firmware-linux-nonfree none pn firmware-myricomnone pn firmware-netxen none pn firmware-qlogic none pn firmware-ralink none ii firmware-realtek0.39~bpo70+1 pn xen-hypervisor none -- debconf information: linux-image-3.10-0.bpo.2-686-pae/postinst/depmod-error-initrd-3.10-0.bpo.2-686-pae: false linux-image-3.10-0.bpo.2-686-pae/postinst/ignoring-ramdisk: linux-image-3.10-0.bpo.2-686-pae/postinst/missing-firmware-3.10-0.bpo.2-686-pae: linux-image-3.10-0.bpo.2-686-pae/prerm/removing-running-kernel-3.10-0.bpo.2-686-pae: true -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#715019: linux-image-3.10-0.bpo.2-686-pae: Similar issues here, but no error feedback
Package: src:linux
Version: 3.10.5-1~bpo70+1
Followup-For: Bug #715019
Dear Maintainer,
I am experiencing similar problems. I have configured a Debian 7.0
installation on a Dell Inspiron 17R SE laptop to use a bcache root device. The
previous known working configuration for the laptop was:
/dev/sda (1TB HDD)
...
/dev/sda7 (used as LUKS encrypted volume)
/dev/mapper/sda7_crypt (used as LVM PV)
/dev/vg0/home
/dev/vg0/root
...
/dev/sda8 (used as ext3 /boot)
The new configuration is
/dev/sda (1TB HDD)
...
/dev/sda7 (used as bcache backing device)
/dev/bcache0 (used as LUKS encrypted volume)
/dev/mapper/bcache_crypt (used as LVM PV)
/dev/vg0/home
/dev/vg0/root
...
/dev/sda8 (used as ext3 /boot)
/dev/sdb (32GB SSD)
...
/dev/sdb3 (used as bcache caching device)
In order to get things booting, I also:
* Installed a Linux 3.10 kernel from wheezy-backports (3.10-0.bpo.2-686-pae)
* Obtained a copy of the bcache-tools source from the git repo and compiled
it
* Constructed a Debian package for bcache-tools using checkinstall
* Because udev recognition wasn't enough at boot time, added a script
/etc/initramfs-tools/scripts/init-premount/z-bcache which looks like this:
#!/bin/sh -e
# ZEP - Added (2013-08-29) because some bcache devices were not
being detected
# at startup by udev. This sloppy hack should do the job.
PREREQS=
prereqs() { echo $PREREQS; }
case $1 in
prereqs)
prereqs
exit 0
;;
esac
. /scripts/functions
if [ -e '/sys/fs/bcache/register_quiet' ]; then
log_begin_msg Scanning for bcache devices...
for d in `ls /dev/sd*`; do
echo $d /sys/fs/bcache/register_quiet 2/dev/null ||
true
done
log_end_msg bcache device scan complete
else
log_warning_msg /sys/fs/bcache/register_quiet not found; not
registering devices
fi
* Executed update-initramfs -u -k all to get everything working
My machine boots from /dev/sda8 and the initramfs has enough machinery to get
the root drive mounted. I was thrilled until I discovered that neither suspend
nor hibernate seems to work; the suspend process seizes up while suspending
devices and never comes back. I booted the laptop from a custom Debian live
disk using the same kernel (3.10-0.bpo.2-686-pae) and performed a series of
tests:
* When the bcache kernel module was not loaded, suspend to RAM worked
correctly.
* When the bcache kernel module was loaded but no devices were registered,
suspend to RAM worked correctly.
* When a single bcache device was registered using echo /dev/sda7
/sys/fs/bcache/register; echo /dev/sdb3 /sys/fs/bcache/register, suspend to
RAM failed to change the power state of the machine.
* With a /dev/bcache0 device in use as an encrypted volume, running echo
freezer /sys/power/pm_test; echo platform /sys/power/disk; echo disk
/sys/power/state allows the machine to awaken from the test correctly.
* With a /dev/bcache0 device in use as an encrypted volume, running echo
devices /sys/power/pm_test; echo platform /sys/power/disk; echo disk
/sys/power/state causes the machine to hang.
Clearly, I can get suspend/hibernate back if I migrate back to using just my
HDD, but caching blocks in a fashion designed for SSDs seems like such a lovely
idea.
Thanks!
-- Package-specific info:
** Version:
Linux version 3.10-0.bpo.2-686-pae (debian-ker...@lists.debian.org) (gcc
version 4.7.2 (Debian 4.7.2-5) ) #1 SMP Debian 3.10.5-1~bpo70+1 (2013-08-11)
** Command line:
BOOT_IMAGE=/vmlinuz-3.10-0.bpo.2-686-pae root=/dev/mapper/vg0-root ro
no_console_suspend
** Tainted: CO (5120)
* Module from drivers/staging has been loaded.
* Out-of-tree module has been loaded.
** Kernel log:
[ 10.924907] iwlwifi :02:00.0: Detected Intel(R) Centrino(R) Wireless-N
2230 BGN, REV=0xC8
[ 10.925034] iwlwifi :02:00.0: L1 Enabled; Disabling L0S
[ 10.927198] Linux video capture interface: v2.00
[ 10.930671] input: HDA Intel PCH HDMI/DP,pcm=3 as
/devices/pci:00/:00:1b.0/sound/card0/input6
[ 10.930949] input: HDA Intel PCH Headphone as
/devices/pci:00/:00:1b.0/sound/card0/input7
[ 10.931226] input: HDA Intel PCH Mic as
/devices/pci:00/:00:1b.0/sound/card0/input8
[ 10.946002] rts5139: module is from the staging directory, the quality is
unknown, you have been warned.
[ 10.946876] ieee80211 phy0: Selected rate control algorithm 'iwl-agn-rs'
[ 10.949342] scsi6 : SCSI emulation for RTS5139 USB card reader
[ 10.949457] usbcore:
Bug#715019: linux-image-3.10-0.bpo.2-686-pae: Additional information about my laptop
Package: src:linux Version: 3.10.5-1~bpo70+1 Followup-For: Bug #715019 Dear Maintainer, I just wanted to post a follow-up on my message. This information may either indicate that I am experiencing a different problem or may shed some light on this one; I'm not sure. To clarify regarding my setup above, both my bcache backing device and my bcache caching device are immediate partitions of the disk; neither the cache nor the backing device are LVM logical volumes. Furthermore, the problem arises *even if the bcache volume is not in use!* That is, I can boot my laptop using this kernel on a Debian Live USB stick, open a console, and run echo '/dev/sda7' /sys/fs/bcache/register echo '/dev/sdb3' /sys/fs/bcache/register ls /dev/bcache0 # Observe that /dev/bcache0 is present pm-suspend ...and the machine will seize up. I do not have to run cryptsetup luksOpen /dev/bcache0 bcache_crypt in order to get this behavior. Since my bcache volumes are immediately over partitions and since /dev/bcache0 isn't even busy, I'd hazard a (novice) guess that the bcache module just doesn't suspend well (though I wouldn't be surprised if someone has contradictory evidence that makes this puzzle more complicated). -- Package-specific info: ** Version: Linux version 3.10-0.bpo.2-686-pae (debian-ker...@lists.debian.org) (gcc version 4.7.2 (Debian 4.7.2-5) ) #1 SMP Debian 3.10.5-1~bpo70+1 (2013-08-11) ** Command line: BOOT_IMAGE=/vmlinuz-3.10-0.bpo.2-686-pae root=/dev/mapper/vg0-root ro no_console_suspend ** Tainted: CO (5120) * Module from drivers/staging has been loaded. * Out-of-tree module has been loaded. ** Kernel log: [ 10.924907] iwlwifi :02:00.0: Detected Intel(R) Centrino(R) Wireless-N 2230 BGN, REV=0xC8 [ 10.925034] iwlwifi :02:00.0: L1 Enabled; Disabling L0S [ 10.927198] Linux video capture interface: v2.00 [ 10.930671] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci:00/:00:1b.0/sound/card0/input6 [ 10.930949] input: HDA Intel PCH Headphone as /devices/pci:00/:00:1b.0/sound/card0/input7 [ 10.931226] input: HDA Intel PCH Mic as /devices/pci:00/:00:1b.0/sound/card0/input8 [ 10.946002] rts5139: module is from the staging directory, the quality is unknown, you have been warned. [ 10.946876] ieee80211 phy0: Selected rate control algorithm 'iwl-agn-rs' [ 10.949342] scsi6 : SCSI emulation for RTS5139 USB card reader [ 10.949457] usbcore: registered new interface driver rts5139 [ 10.949480] scsi 6:0:0:0: Direct-Access Generic- xD/SD/M.S. 1.00 PQ: 0 ANSI: 0 CCS [ 10.949781] sd 6:0:0:0: Attached scsi generic sg3 type 0 [ 10.949954] uvcvideo: Found UVC 1.00 device Laptop_Integrated_Webcam_HD (0c45:644b) [ 10.951966] sd 6:0:0:0: [sdc] Attached SCSI removable disk [ 10.961003] cfg80211: World regulatory domain updated: [ 10.961055] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 10.962342] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 10.962405] cfg80211: (2457000 KHz - 2482000 KHz @ 2 KHz), (300 mBi, 2000 mBm) [ 10.962466] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm) [ 10.962528] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 10.962592] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 10.975823] input: Laptop_Integrated_Webcam_HD as /devices/pci:00/:00:1a.0/usb1/1-1/1-1.5/1-1.5:1.0/input/input9 [ 10.975951] usbcore: registered new interface driver uvcvideo [ 10.976001] USB Video Class driver (1.1.1) [ 11.022428] ACPI: AC Adapter [ADP0] (on-line) [ 11.022537] input: Lid Switch as /devices/LNXSYSTM:00/device:00/PNP0C0D:00/input/input10 [ 11.022980] ACPI: Lid Switch [LID0] [ 11.023074] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input11 [ 11.023179] ACPI: Power Button [PWRF] [ 11.028132] ACPI: Battery Slot [BAT0] (battery present) [ 11.028349] wmi: Mapper loaded [ 11.032916] [drm] Memory usable by graphics device = 2048M [ 11.032970] i915 :00:02.0: setting latency timer to 64 [ 11.033069] i915 :00:02.0: irq 47 for MSI/MSI-X [ 11.033074] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [ 11.033125] [drm] Driver supports precise vblank timestamp query. [ 11.033298] vgaarb: device changed decodes: PCI::00:02.0,olddecodes=io+mem,decodes=none:owns=io+mem [ 11.033362] vgaarb: transferring owner from PCI::00:02.0 to PCI::01:00.0 [ 11.072504] fbcon: inteldrmfb (fb0) is primary device [ 11.129174] input: Dell WMI hotkeys as /devices/virtual/input/input12 [ 11.266513] psmouse serio1: alps: Unknown ALPS touchpad: E7=73 03 50, EC=73 02 02 [ 11.845232] input: PS/2 Generic Mouse as /devices/platform/i8042/serio1/input/input13 [ 11.895882] Console: switching to colour frame buffer device 240x67 [ 11.904399] i915 :00:02.0: fb0: inteldrmfb frame
Bug#711261: okular: Alt-Scroll for horizontal scroll behaves differently at top and bottom of page
Package: okular Version: 4:4.8.4-3 Severity: minor Dear Maintainer, I was happy to discover that okular can horizontally scroll when one is holding the Alt key. There seems to be a minor bug associated with this behavior, though. When *not* in continuous view mode, when viewing single pages, and when the vertical scroll bar is locked to the top position (and the view is at the very top of a page), pressing Alt and scrolling up (which intends to scroll left) causes the document to scroll up to the bottom of the previous page. This is not a feature designed to support document reading, as this scroll-up behavior occurs regardless of the position of the horizontal scroll bar (and the horizontal position of the document is unchanged). Likewise, attempting to scroll right when viewing the very bottom of a page scrolls down instead. This bug is marked minor because it is easy to work around as a user: just scroll a little away from the page boundary and horizontal scrolling works as desired. It's a bit disorienting, though. :) -- System Information: Debian Release: 7.0 APT prefers stable APT policy: (700, 'stable'), (500, 'stable-updates') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/8 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 okular depends on: ii kde-runtime 4:4.8.4-2 ii libc6 2.13-38 ii libfreetype6 2.4.9-1.1 ii libgcc1 1:4.7.2-5 ii libjpeg8 8d-1 ii libkdecore5 4:4.8.4-4 ii libkdeui5 4:4.8.4-4 ii libkio5 4:4.8.4-4 ii libkparts44:4.8.4-4 ii libkprintutils4 4:4.8.4-4 ii libkpty4 4:4.8.4-4 ii libokularcore14:4.8.4-3 ii libphonon44:4.6.0.0-3 ii libpoppler-qt4-3 0.18.4-6 ii libqca2 2.0.3-4 ii libqimageblitz4 1:0.0.6-4 ii libqt4-dbus 4:4.8.2+dfsg-11 ii libqt4-svg4:4.8.2+dfsg-11 ii libqt4-xml4:4.8.2+dfsg-11 ii libqtcore44:4.8.2+dfsg-11 ii libqtgui4 4:4.8.2+dfsg-11 ii libsolid4 4:4.8.4-4 ii libspectre1 0.2.7-2 ii libstdc++64.7.2-5 ii phonon4:4.6.0.0-3 ii zlib1g1:1.2.7.dfsg-13 okular recommends no packages. Versions of packages okular suggests: ii ghostscript9.05~dfsg-6.3 ii jovie 4:4.8.4-2 pn okular-extra-backends none ii poppler-data 0.4.5-10 ii texlive-binaries 2012.20120628-4 ii unrar 1:4.1.4-1 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#707235: debian-installer: Debian Wheezy Stable (7.0.0-i386) installer fails on LVM2 over dm-crypt
Package: debian-installer Severity: normal This appears to be a regression bug. I have a Dell Inspiron 1720 (circa 2008) which I previously used as a work laptop. The drive was configured as follows: sda sda1 ext3 filesystem (for /boot) sda2 physical device for encryption (sda2_crypt) physical volume for LVM2 vg0-root (ext3) vg0-swap (ext3) vg0-home (ext3) This configuration installed quite nicely through the Debian installer menus for Squeeze. Yesterday, I pulled this laptop out of storage and attempted to wipe the installation, replacing it with a fresh Debian Wheezy configuration. The only difference in layout is that my attempt yesterday uses ext4 rather than ext3. Using this configuration with the Wheezy stable installer I downloaded yesterday, GRUB fails to install. I receive the following messages in the diagnostics console: /usr/sbin/grub-probe: error: no such disk. Auto-detection of a filesystem of /dev/mapper/vg0-root failed. I then reconsidered the use case for the laptop and decided to try without the encrypted drive. Eliminating that layer (but keeping LVM2) resulted in a successful installation. Let me know if I can provide any additional info. Thanks! :) -- System Information: Debian Release: 7.0 APT prefers stable APT policy: (700, 'stable'), (500, 'stable-updates') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) 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#623288: dolphin: drag drop does not correctly escape ununsual filename characters
Hello there, I am now running testing as well and observe that I no longer have this problem. Please feel free to close the bug. :) Thanks! Zach tag 623288 unreproducible,moreinfo thanks Hi, With KDE 4.8 from testing, I am able to successfully drag and drop a file named « foo;bar.txt ». Could you please verify it's the same for you ? If so, I will close the bug. Regards, Adrien -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694342: crypttab
Sorry; the crypttab that I'm using doesn't actually us the keyfile. That was from a previous draft. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#633753: kwrite: Haskell indentation mode does not respect Haddock comments
Package: kwrite Version: 4:4.4.5-2 Severity: normal When editing a .hs (Haskell source) file, the Haskell indentation mode is correctly selected. This indentation mode will, among other things, increase indentation when pipes appear in some places, presumably to auto-format ADT definitions. This is all quite desirable. Unfortunately, the indentation mode does not check for comments preceeding the pipe. Haddock autodocumentation format uses the pipe to signal the difference between an autodoc comment and a normal comment; that is, -- |Foo creates a Haddock comment containing the text Foo. The KWrite Haskell indentation mode instead forces this to be -- |Foo The Haddock User Guide (http://www.haskell.org/haddock/doc/html/index.html) seems to indicate that the first form is correct and that the second form is not. -- System Information: Debian Release: 6.0.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686-bigmem (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 kwrite depends on: ii kdebase-runtime 4:4.4.5-1 runtime components from the offici ii libc6 2.11.2-10 Embedded GNU C Library: Shared lib ii libkdecore5 4:4.4.5-2+squeeze2 the KDE Platform Core Library ii libkdeui5 4:4.4.5-2+squeeze2 the KDE Platform User Interface Li ii libkio5 4:4.4.5-2+squeeze2 the Network-enabled File Managemen ii libkparts44:4.4.5-2+squeeze2 the Framework for the KDE Platform ii libktexteditor4 4:4.4.5-2+squeeze2 the KTextEditor interfaces for the ii libqtcore44:4.6.3-4+squeeze1 Qt 4 core module ii libqtgui4 4:4.6.3-4+squeeze1 Qt 4 GUI module ii libstdc++64.4.5-8The GNU Standard C++ Library v3 kwrite recommends no packages. kwrite suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#632857: python-lockfile: Cannot Lock Multiple Files
Package: python-lockfile
Version: 1:0.8-2
Severity: important
The lockfile package does not correctly handle locking multiple files on Linux
systems. Consider the following script:
#!/usr/bin/env python
# -*- coding: iso-8859-1 -*-
import lockfile
import time
a = lockfile.FileLock('/tmp/a')
b = lockfile.FileLock('/tmp/b')
a.acquire()
b.acquire()
b.release()
a.release()
print 'Done!'
This script should clearly execute correctly (as long as /tmp is present) but
instead terminates with the following:
Traceback (most recent call last):
File ./test2.py, line 12, in module
a.release()
File /usr/lib/pymodules/python2.6/lockfile.py, line 273, in release
raise NotMyLock
lockfile.NotMyLock
That is, it fails to release the *second* lock.
-- System Information:
Debian Release: 6.0.2
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-5-686-bigmem (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 python-lockfile depends on:
ii python 2.6.6-3+squeeze6 interactive high-level object-orie
ii python-support 1.0.10 automated rebuilding support for P
python-lockfile recommends no packages.
python-lockfile suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#623336: rdiff-backup: --max-file-size breaks --exclude instructions
Package: rdiff-backup
Version: 1.2.8-6
Severity: normal
Running rdiff-backup with --max-file-size breaks the behavior of --exclude.
Excluded files are still included when --max-file-size is used. For an example
of this behavior, execute the following (bash) commands:
mkdir temp
cd temp
mkdir -p src src/{a,b}
touch src/{a,b}/file
rdiff-backup --include=src/a --exclude=src/* src good-backup
rdiff-backup --max-file-size 104857600 --include=src/a --exclude=src/*
src bad-backup
The first command creates the backup we would expect: it only includes the 'a'
directory and not the 'b' directory. The second backup should therefore
behave the same; the only difference is the maximum file size of 100MB, which
we clearly have not exceeded. Nonetheless, the bad-backup directory contains
a backup of directory 'b' as well.
This is of particular annoyance because backupninja relies on rdiff-backup's
include/exclude behavior in this way. This makes it impossible to use
options=--max-file-size 104857600 to exclude files over 100MB when using
rdiff-backup in a backupninja session. This is not a problem with the
backupninja helper, though, as shown by the session above.
-- System Information:
Debian Release: 6.0.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-5-686-bigmem (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 rdiff-backup depends on:
ii libc6 2.11.2-10Embedded GNU C Library: Shared lib
ii librsync1 0.9.7-7 rsync remote-delta algorithm libra
ii python 2.6.6-3+squeeze6 interactive high-level object-orie
ii python-support 1.0.10 automated rebuilding support for P
Versions of packages rdiff-backup recommends:
ii python-pylibacl 0.5.0-3module for manipulating POSIX.1e A
ii python-pyxattr0.5.0-3module for manipulating filesystem
rdiff-backup suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#623288: dolphin: drag drop does not correctly escape ununsual filename characters
Package: dolphin Version: 4:4.4.5-2 Severity: normal Dolphin does not properly escape filenames when dragging and dropping between applications. In particular, files containing ';' in the name (such as the filename 'foo;bar.txt') are not correctly translated. For instance, dragging the file 'foo;bar.txt' to Iceweasel from Nautilus provides Firefox with the URL 'file:///home/zpalmer/ztemp/foo%3Bbar.txt'. Dragging the same file to Iceweasel from Dolphin results in 'file:///home/zpalmer/ztemp/foo;bar.txt', which prevents the file from being loaded. Dragging the file from Nautilus to an Icedove mail window successfully attaches it to the e-mail, while dragging it from Dolphin results in the file being truncated. (This was the cause of bug #608928, which I reported without realizing that Dolphin was involved.) I am unfamiliar with the DD API that is used between these applications. My expectation, however, is that some rich variation of the dragged resource (such as a URN field) is being set by Nautilus and not by Dolphin. Applications which do not depend on this kind of input seem to work fine with both file managers; for instance, dragging from either file manager onto Konsole or gnome-terminal seems to work fine. -- System Information: Debian Release: 6.0.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686-bigmem (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 dolphin depends on: ii kdebase-runtime 4:4.4.5-1runtime components from the offici ii libc6 2.11.2-10Embedded GNU C Library: Shared lib ii libgcc1 1:4.4.5-8GCC support library ii libkdecore5 4:4.4.5-2+squeeze1 the KDE Platform Core Library ii libkdeui5 4:4.4.5-2+squeeze1 the KDE Platform User Interface Li ii libkfile4 4:4.4.5-2+squeeze1 the File Selection Dialog Library ii libkio5 4:4.4.5-2+squeeze1 the Network-enabled File Managemen ii libknewstuff3-4 4:4.4.5-2+squeeze1 the Get Hot New Stuff v3 Library ii libkonq54:4.4.5-2core libraries for Konqueror ii libkparts4 4:4.4.5-2+squeeze1 the Framework for the KDE Platform ii libkutils4 4:4.4.5-2+squeeze1 various utility classes for the KD ii libnepomuk4 4:4.4.5-2+squeeze1 the Nepomuk Meta Data Library ii libnepomukquery4a 4:4.4.5-2+squeeze1 the Nepomuk Query Library for the ii libphonon4 4:4.6.0really4.4.2-1 the core library of the Phonon mul ii libqt4-dbus 4:4.6.3-4Qt 4 D-Bus module ii libqtcore4 4:4.6.3-4Qt 4 core module ii libqtgui4 4:4.6.3-4Qt 4 GUI module ii libsoprano4 2.5.0+dfsg.1-1 libraries for the Soprano RDF fram ii libstdc++6 4.4.5-8 The GNU Standard C++ Library v3 ii phonon 4:4.6.0really4.4.2-1 metapackage for the Phonon multime Versions of packages dolphin recommends: ii kfind 4:4.4.5-2 file search utility ii ruby 4.5An interpreter of object-oriented dolphin suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#608928: icedove: Cannot Attach Files with Semicolon in Name
Christoph, Thanks for looking into this. I have since upgraded to Squeeze stable and can no longer reproduce the bug. I'm not sure if something changed in 3.0.11 or if (more likely) doing the dist-upgrade resolved the issue. Either way, it seems we can safely close this one. :) Cheers, Zach tags 608928 unreproducible thanks Hi, On Di, Jan 04, 2011 at 12:22:19 -0500, Zachary Palmer wrote: It is not possible to attach a file which contains a semicolon in its name. Icedove erroneously claims that the file does not exist, truncating the name at the semicolon. For instance, foo;bar.txt would result in an error message claiming that the file foo does not exist. sorry, but I can't reproduce your bugreport with icedove 3.0.11 or 3.1.9. Could you check again for this bug? Cheers, Christoph -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#610323: linux-image-2.6.32-5-686: Intermittent Hibernate Failure
Package: linux-2.6 Version: 2.6.32-29 Severity: normal On occasion, hibernating my laptop will result in a kernel bug report. This appears to occur more often when I perform operations such as unplugging the power while the laptop is hibernating; it also appears to occur more often if a large amount of I/O is occurring when hibernation begins. The problem appears to be with the hibernation system attemting to free a page frame that is not allocated. The actual line on which BUG_ON is invoked is in memory_bm_clear_bit of /kernel/power/snapshot.c. It is doing this in response to the -EFAULT value returned by memory_bm_find_bit in the same file. I'm not terribly good at swimming around in kernel land or I would dig further. The following is the full kernel bug message. kernel BUG at /build/buildd-linux-2.6_2.6.32-29-i386-Of6Yt1/linux-2.6-2.6.32/debian/build/source_i386_none/kernel/power/snapshot.c:522! invalid opcode: [#1] SMP last sysfs file: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0/voltage_now Modules linked in: btrfs zlib_deflate crc32c libcrc32c ufs qnx4 hfsplus hfs ninix ntfs vfat msdos fat jfs xfs exportfs reiserfs ext4 jbd2 ext2 ip6table_filter ip6_tables iptable_filter ip_tables x_tables acpi_cpufreq cpufreq_userspace cpufreq_conservative cpufreq_powersave cpufreq_stats parport_pc ppdev lp parport sco bridge stp bnep rfcomm l2cap crc16 bluetooth kvm_intel kvm binfmt_misc uinput fuse loop firewire_sbp2 snd_hda_codec_idt snd_hda_intel snd_hda_codec snd_hwdep arc4 ecb snd_pcm_oss snd_mixer_oss nouveau snd_pcm ttm snd_seq_midi snd_rawmidi snd_seq_midi_event joydev drm_kms_helper snd_seq drm snd_timer videodev psmouse v4l1_compat snd_seq_device i2c_algo_bit cfg80211 i2c_i801 i2c_core snd pcspkr dell_laptop serio_raw rfkill video soundcore dcdbas output wmi snd_page_alloc evdev processor button ac battery ext3 jbd mbcache sha256_generic aes_i586 aes_generic cbc usbhid hid dm_crypt dm_mod sg sd_mod sr_mor crc_t10dif cdrom ata_generic b44 ssb uhci_hcd pcmcia ahci fir ewire_ohci ata_piix sdhci_pci thermal shdci mmc_core led_class pcmcia_core firewire_core mii crc_itu_t ricoh_mmc libata thermal_sys ehci_hcd scsi_mod usbcore nls_base [last unloaded: uvcvideo] Pid: 21360, comm: s2disk Not tainted (2.6.32-5-686 #1) Inspiron 1720 EIP: 0060:[c10593dc] EFLAGS: 00210282 CPU: 0 EIP is at memory_bm_clear_bit+0x15/0x28 EAX fff2 EBX: cd10bea4 ECX: c1462edc EDX: cd10bea4 ESI c14d1fe0 EDI: EBP: 4d93 ESP: cd10bea4 DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 Process s2disk (pid: 21360, ti=cd10a000 task=f3f24cc0 task.ti=cd10a000) Stack: c1059b42 fffe3ccf fffe3cce c105adf3 1c58a5ca 0006c433 000a8a6f 0007bae3 0 4b53 1643 0006605d 0004a9da 00054537 0001873e 0 4d2c55b8 00099e8f 0001 bfe96f9c fff0 c1058d4b 40043303 Call Trace: [c1059b42] ? memory_bm_next_pfn+0x18/0x53 [c105adf3] ? hibernate_preallocate_memory+0x30d/0x3a6 [c1058d4b] ? hibernation_snapshot+0x22/0x1ea [c105bc7e] ? snapshot_ioctl+0x200/0x479 [c105ba7e] ? snapshot_ioctl+0x0/0x479 [c10bd530] ? vfs_ioctl+0x1c/0x5f [c10bdac4] ? do_vfs_ioctl+0x4aa/0x4e5 [c10b295a] ? fsnotify_modify+0x5a/0x61 [c118e969] ? tty_write+0x0/0x1c0 [c10b355a] ? vfs_write+0x9e/0xd6 [c10bdb40] ? sys_ioctl+0x41/0x58 [c10030fb] ? sysenter_do_call+0x12/0x28 Code: 04 16 89 43 04 8d 44 11 04 5b 5e c3 ba 01 00 00 00 e9 2f ff ff ff 53 83 ec 08 89 e3 8d 4c 24 04 53 e8 35 fd ff ff 8a 85 c0 74 04 0f 8b eb fe 8b 54 24 04 8b 04 24 f0 0f b3 02 5b 58 5b c3 8b 0d EIP: [c10593dc] memory_bm_clear_bit+0x15/0x28 SS:ESP 0068:cd10bea4 ---[ end trace 2011b300aeb4af53 ]--- -- Package-specific info: ** Version: Linux version 2.6.32-5-686 (Debian 2.6.32-29) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Fri Dec 10 16:12:40 UTC 2010 ** Command line: BOOT_IMAGE=/vmlinuz-2.6.32-5-686 root=/dev/mapper/vg0-root ro quiet ** Not tainted ** Kernel log: [287223.515419] uhci_hcd :00:1a.0: setting latency timer to 64 [287223.515459] usb usb2: root hub lost power or was reset [287223.515479] uhci_hcd :00:1a.1: setting latency timer to 64 [287223.515518] usb usb4: root hub lost power or was reset [287223.515536] ehci_hcd :00:1a.7: setting latency timer to 64 [287223.515541] usb usb1: root hub lost power or was reset [287223.519415] ehci_hcd :00:1a.7: cache line size of 32 is not supported [287223.519433] HDA Intel :00:1b.0: PCI INT A - GSI 21 (level, low) - IRQ 21 [287223.519439] HDA Intel :00:1b.0: setting latency timer to 64 [287223.519464] uhci_hcd :00:1d.0: setting latency timer to 64 [287223.519503] usb usb5: root hub lost power or was reset [287223.519522] uhci_hcd :00:1d.1: setting latency timer to 64 [287223.519561] usb usb6: root hub lost power or was reset [287223.519579] uhci_hcd :00:1d.2: setting latency timer to 64 [287223.519618] usb usb7: root hub lost power or was reset [287223.519636] ehci_hcd :00:1d.7: setting latency
Bug#608928: icedove: Cannot Attach Files with Semicolon in Name
Package: icedove Version: 3.0.10-1 Severity: normal Tags: upstream It is not possible to attach a file which contains a semicolon in its name. Icedove erroneously claims that the file does not exist, truncating the name at the semicolon. For instance, foo;bar.txt would result in an error message claiming that the file foo does not exist. Steps to reproduce: 1. Create a new e-mail 2. Attach any file with a semicolon in its name 3. Attempt to send the e-mail Expected behavior: E-mail is sent appropriately. Observed behavior: Erroneous message claiming the absence of the file. Workaround: Create a copy or hard link of the file whose name does not contain a semicolon and attach that. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, '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 icedove depends on: ii debianutils 3.4 Miscellaneous utilities specific t ii fontconfig 2.8.0-2.1generic font configuration library ii libasound2 1.0.23-2.1 shared library for ALSA applicatio ii libatk1.0-0 1.30.0-1 The ATK accessibility toolkit ii libc6 2.11.2-7 Embedded GNU C Library: Shared lib ii libcairo2 1.8.10-6 The Cairo 2D vector graphics libra ii libdbus-1-3 1.2.24-3 simple interprocess messaging syst ii libfontconfig1 2.8.0-2.1generic font configuration library ii libfreetype62.4.2-2.1FreeType 2 font engine, shared lib ii libgcc1 1:4.4.5-8GCC support library ii libglib2.0-02.24.2-1 The GLib library of C routines ii libgtk2.0-0 2.20.1-2 The GTK+ graphical user interface ii libjpeg62 6b1-1The Independent JPEG Group's JPEG ii libnspr4-0d 4.8.6-1 NetScape Portable Runtime Library ii libnss3-1d 3.12.8-1 Network Security Service libraries ii libpango1.0-0 1.28.3-1 Layout and rendering of internatio ii libpng12-0 1.2.44-1 PNG library - runtime ii libsqlite3-03.7.3-1 SQLite 3 shared library ii libstartup-notification 0.10-1 library for program launch feedbac ii libstdc++6 4.4.5-8 The GNU Standard C++ Library v3 ii libx11-62:1.3.3-4X11 client-side library ii libxrender1 1:0.9.6-1X Rendering Extension client libra ii libxt6 1:1.0.7-1X11 toolkit intrinsics library ii psmisc 22.11-1 utilities that use the proc file s ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime Versions of packages icedove recommends: ii hunspell-en-us [hunspell-dict 20070829-4 English_american dictionary for hu Versions of packages icedove suggests: ii libdbus-glib-1-20.88-2 simple interprocess messaging syst ii libgconf2-4 2.28.1-6 GNOME configuration database syste ii libgnome2-0 2.30.0-1 The GNOME library - runtime files ii libgnomevfs2-0 1:2.24.3-1 GNOME Virtual File System (runtime ii libgssapi-krb5-21.8.3+dfsg-3 MIT Kerberos runtime libraries - k ii ttf-lyx 1.6.7-1 TrueType versions of some TeX font -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#588569: regression: cannot cache Debian installer files
Package: apt-cacher Version: 1.6.4 Severity: normal Content-Type: text/plain; charset=us-ascii MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Zachary Palmer zep_deb...@bahj.com To: Debian Bug Tracking System sub...@bugs.debian.org Subject: Regression: apt-cacher no longer properly supports Debian installer files Message-ID: 20100709181656.28329.91443.report...@nestor.bahj.com X-Mailer: reportbug 3.48 Date: Fri, 09 Jul 2010 14:16:56 -0400 Package: apt-cacher Version: 1.6.4 Severity: normal A patch was applied to apt-cacher 1.5.5 to allow the Debian Live project's scripts to properly pull Debian Installer files through apt-cacher. The patch appears to have involved adding a clause to the /usr/share/apt-cacher/apt-cacher script (at line 540 in my copy of version 1.6.4) which checks based on the following condition: ($filename =~ /^(?:vmlinuz|initrd\.gz)$/) However, attempting to create a clean Debian Live Lenny image including the Lenny installer results in the error: http://nestor:3142/debian//dists/lenny/main/installer-i386/current/images//netboot/debian-installer/i386/linux: 2010-07-09 14:10:37 ERROR 403: Sorry, not allowed to fetch that type of file: linux. E: Could not download file: http://nestor:3142/debian//dists/lenny/main/installer-i386/current/images//netboot/debian-installer/i386/linux It appears that the Debian Installer is now using the name linux rather than the name vmlinuz. Adding this name to the above condition to get ($filename =~ /^(?:linux|vmlinuz|initrd\.gz)$/) and restarting apt-cacher seems to have worked for me. This problem also seems to exist in 1.6.11 in Sid at the moment. Can this fix be applied to mainstream? On a slightly more wishlist-y note, it would be nice for apt-cacher to use a configuration file for these filenames rather than a hardcoded regexp. That way, I could edit something in /etc to fix this if it comes up again as opposed to editing something in /usr/share. Thanks! -- System Information: Debian Release: 5.0.5 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-2-amd64 (SMP w/8 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 apt-cacher depends on: ii bzip21.0.5-1 high-quality block-sorting file co ii ed 0.7-3 The classic unix line editor ii libdigest-sha1-perl 2.11-2+b1 NIST SHA-1 message digest algorith ii libwww-curl-perl 4.05-1 Perl bindings to libcurl ii libwww-perl 5.813-1 WWW client/server library for Perl ii perl 5.10.0-19lenny2 Larry Wall's Practical Extraction Versions of packages apt-cacher recommends: ii libberkeleydb-perl0.34-1+b1 use Berkeley DB 4 databases from P Versions of packages apt-cacher suggests: pn libio-socket-inet6-perl none (no description available) -- no debconf information -- System Information: Debian Release: 5.0.5 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-2-amd64 (SMP w/8 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 apt-cacher depends on: ii bzip21.0.5-1 high-quality block-sorting file co ii ed 0.7-3 The classic unix line editor ii libdigest-sha1-perl 2.11-2+b1 NIST SHA-1 message digest algorith ii libwww-curl-perl 4.05-1 Perl bindings to libcurl ii libwww-perl 5.813-1 WWW client/server library for Perl ii perl 5.10.0-19lenny2 Larry Wall's Practical Extraction Versions of packages apt-cacher recommends: ii libberkeleydb-perl0.34-1+b1 use Berkeley DB 4 databases from P Versions of packages apt-cacher suggests: pn libio-socket-inet6-perl none (no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#565229: More Info: The Source of the Problem
A friend of mine and I just did some digging today and came up with more knowledge on this problem. The issue at hand appears to be that sshfs isn't recognizing when the TCP/IP connection goes down. I can, for instance, execute the following steps without problem: 1. Boot my machine fresh (no GUI login) 2. Mount something via sshfs 3. Suspend and resume an arbitrary number of times However, the following reliably causes my machine to fail: 1. Boot my machine fresh (no GUI login) 2. Mount something via sshfs 3. Disconnect my network card or otherwise interfere with the sshfs TCP/IP connection 4. Run a program which attempts to access the sshfs mount (which will block indefinitely) 5. Attempt to suspend (which will fail) Unmounting the filesystem will fail in this case because the program started in step 4 is keeping the resource busy. The FUSE kernel module code which calls into the userspace daemon is performing a non-interruptable I/O wait, so you can't signal it to die (even with SIGKILL). The only solution I've found is to kill -9 the sshfs userspace daemon and then to fusermount -uz the mountpoint. This problem is still the case even when -o ServerAliveInterval=15 is added to the sshfs options; it appears at a glance that sshfs is not realizing that its ssh client's connection has died even when it terminates due to lack of keepalive packets. This is a particularly frustrating problem when processes like dolphin latch onto a directory in the sshfs mount and won't let go. Specifically, I often suspend my laptop with sshfs processes running (as in Lenny, this wasn't a problem for me). When I start the laptop back up and connect to a different network, everything is fine. However, it is at this point that the processes using the sshfs mount fail to escape their blocking I/O calls, so it's when I decide to suspend at this remote location that I am faced with the problem. The following link appears to indicate that the sshfs people are aware of the issue but have not yet prioritized it: http://sourceforge.net/mailarchive/forum.php?thread_name=E1Nz5rE-0006Yj-EW%40pomaz-ex.szeredi.huforum_name=fuse-sshfs For users who want this to be part of the behavior of things like the GNOME power manager, I'd suggest editing /etc/hibernate/common.conf to include something like OnSuspend 20 killall -9 sshfs Cheers, Zach -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#567590: Reproducable
Frans,
I witnessed the same confusion myself; in retrospect, I should've
mentioned it. I simply assumed that it was a graphical glitch of some
kind. I was unable to set the bootable flag as well and had been
setting the BIOS boot area flag (bios_grub) as well. I'm not clear as
to the semantic of that flag, but that's what I have set at the moment
and it seems to be booting my machine correctly. I'd be glad to provide
more information at request, but I'm not terribly familiar with GPT, so
I'm not sure what's relevant. :)
Thanks,
Zach
On Saturday 30 January 2010, Frans Pop wrote:
│ Bootable flag:off│
│ off │
Note the extra line with 'off' below the 'Bootable flag' line. That
could be caused by bootable flag, but possibly also a different flag.
OK, that was possibly an unrelated issue. The second line was for the 'BIOS
boot area flag' for which the description is not correctly displayed.
I've committed a fix for that.
Toggling Bootable flag does not work (it remains 'off'), but toggling
the line below changes it from 'off' to 'on'.
Toggling the bootable flag still does not have any effect. It should be
supported: VALID_FLAGS in the partman log has: boot, hidden, raid, lvm,
hp-service, msftres, bios_grub.
I can see the flag is getting set correctly, but when libparted reads the
current flags again, it's not there.
Zacharay: is the problem really with the bootable flag, or rather with
that 'BIOS boot area' (bios_grub) flag?
It looks as if setting bios_grub may remove the raid flag. Could it be that
a 'BIOS boot area' partition simply cannot be a RAID partition? That seems
quite logical...
To test with that display issue corrected, you need to make the following
change in /lib/partman/active-partition/67toggle_biosgrub/choices before
you run partman:
-description=$(stralign -25 $RET)
+description=$RET
if [ $biosgrub = yes ]; then
db_metaget partman-partitioning/text/on description
- printf nobiosgrub\t%s%s\n $description ${RET}
+ printf nobiosgrub\t%s\${!TAB}%s\n $description ${RET}
else
db_metaget partman-partitioning/text/off description
- printf biosgrub\t%s%s\n $description ${RET}
+ printf biosgrub\t%s\${!TAB}%s\n $description ${RET}
fi
I'll test a bit more myself too.
Cheers,
FJP
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#567590: debian-installer: GPT with RAID fails to install
Package: debian-installer Severity: normal I have a system containing two 2TB SATA drives which I have configured into a RAID1 and am using through LVM. When using the Debian 5.03 amd64 installer, I was unable to use the partitioner provided in the menus to install. When the partitioner started, I created new partition tables on the otherwise empty drives. Because the drives are so large (2TB each), the installer wisely suggested that I use GPT rather than the traditional MBR partition table. I created a new GPT on each drive with a single partition (named RAID1-0 and RAID1-1 respectively). I then chose to configure software RAID; this is the point at which things broke down. I received an error message indicating that there were no Linux RAID/Autodetect partitions available and that I should format one of my drives to create one. It is my suspicion that the check to ensure that RAID partitions exist is assuming an MBR-style partition table. I ran an mdadm --create command from the secondary terminal and restarted the partitioner. When it rescanned the disks and discovered my RAID1 already in place, I was able to set up LVM without difficulty. -- System Information: Debian Release: 5.0.2 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-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 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#567606: virt-manager: confusion about network devices when administering a remote host
Package: virt-manager Version: 0.7.0-2~bpo50+1 Severity: important I am finding virt-manager impossible to use with a remote host. Using SSH access, I log into the remote machine and attempt to add a virtual network. Upon reaching the page where I am asked to select a physical network to which to NAT traffic, I see not the physical networks on the remote machine (eth0, eth1, eth2, etc.) but the physical networks on my laptop (wlan0, etc.). Additionally, when asked to choose a file (whether it be installation media, a block device for a new virtual hard disk, etc.), I am given a Choose Volume dialog rather than a remote file chooser. This makes it impossible to install the VM. These problems do not arise when administering local VMs. At the moment, my workaround is to install virt-manager on the remote machine and use an SSH tunnel to forward my X session. This is, obviously, quite inefficient. Thanks for reading. :) -- System Information: Debian Release: 5.0.2 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-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 virt-manager depends on: ii libatk1.0-01.22.0-1 The ATK accessibility toolkit ii libc6 2.7-18GNU C Library: Shared libraries ii libcairo2 1.6.4-7 The Cairo 2D vector graphics libra ii libglib2.0-0 2.16.6-2 The GLib library of C routines ii libgtk2.0-02.12.12-1~lenny1 The GTK+ graphical user interface ii libpango1.0-0 1.20.5-5 Layout and rendering of internatio ii librsvg2-common2.22.2-2lenny1SAX-based renderer library for SVG ii python-dbus0.82.4-2 simple interprocess messaging syst ii python-glade2 2.12.1-6 GTK+ bindings: Glade support ii python-gnome2 2.22.0-1 Python bindings for the GNOME desk ii python-gtk-vnc 0.3.8-2 A VNC viewer widget for GTK+ (Pyth ii python-gtk22.12.1-6 Python bindings for the GTK+ widge ii python-libvirt 0.4.6-10 libvirt Python bindings ii python-urlgrabber 3.1.0-4 A high-level cross-protocol url-gr ii python-vte 1:0.16.14-4 Python bindings for the VTE widget ii python2.5 2.5.2-15 An interactive high-level object-o ii virtinst 0.400.3-2~bpo50+1 Programs to create and clone virtu Versions of packages virt-manager recommends: ii hal 0.5.11-8 Hardware Abstraction Layer ii libvirt-bin 0.4.6-10 the programs for the libvirt libra Versions of packages virt-manager suggests: ii virt-viewer 0.0.3-2Displaying the graphical console o -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#567590: Reproducable
I managed to reproduce the problem on my laptop with a KVM instance and two 8G QEMU drive images. I used the i386 Debian 5.03 net installer CD and started an expert install. I put a GPT on each of the two drives and created a single partition on each. I instructed the installer to use each as a physical device for software RAID. Here's the interesting bit. I sped through the menus and discovered that the RAID system was quite happy to create a RAID1 for me. I went back, deleted the RAID, and started over. The second time, I was able to reproduce the bug. The only difference between these two runs was that I remembered to flag both drives as bootable the second time. It seems that a bootable GPT partition is the problem; the RAID menu system doesn't seem to see it. (Again, mdadm works just fine.) Cheers, Zach -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#563735: live-initramfs: nfs cow leads to segfault
Package: live-initramfs Version: 1.156.1+1.157.2-1 Severity: normal I have created a relatively simple Debian Live configuration to allow PXE booting a thin client. Everything was working fine until I tried to add persistent copy-on-write via NFS. The NFS server is configured like so: /srv/debian-live *(ro,async,subtree_check,no_root_squash) #/srv/debian-live-cow *(rw,async,subtree_check,all_squash,anonuid=1007,anongid=1007) /srv/debian-live-cow *(rw,async,subtree_check,no_root_squash) (The commented second line is the configuration I was originally using; things broke there too. The UID and GID are for a user I created to avoid giving root write permissions on the server to the thin client.) The configuration in the Debian Live config directory was changed only in the binary file: # $LH_NET_COW_PATH: set cow directory # (Default: ) LH_NET_COW_PATH=/srv/debian-live-cow # $LH_NET_COW_SERVER: set cow server # (Default: ) LH_NET_COW_SERVER=10.0.0.1 This is *without* use of the persistent boot parameter, since that disables the functionality that makes use of these variables (and since the persistent boot-time parameter doesn't support NFS - it looks at local block devices). Upon booting, I get the following: Begin: Running /scripts/live-premount ... done. IP-Config: eth0 hardware address 00:19:21:0d:24:84 mtu 1500 DHCP RARP [ 10.260015] RPC: Registered udp transport module. [ 10.260059] RPC: Registered tcp transport module. [ 10.299282] aufs 20080714 [ 10.320096] loop: module loaded [ 10.389098] squashfs: version 3.3-CVS (2008/04/04) Phillip Lougher [ 10.409185] BUG: unable to handle kernel NULL pointer dereference at 0015 [ 10.409278] IP: [f89dbf90] :nfs:nfs_create+0x47/0xa4 [ 10.409361] *pde = [ 10.409423] Oops: [#1] [ 10.409482] Modules linked in: squashfs zlib_inflate loop aufs exportfs nfs lockd nfs_acl sunrpc ide_generic ide_cd_mod cdrom ata_generic sata_nv libata scsi_mod dock usbhid hid ff_memless floppy forcedeth ide_pci_generic amd74xx ide_core ehci_hcd ohci_hcd usbcore thermal processor fan thermal_sys [last unloaded: scsi_wait_scan] [ 10.410365] [ 10.410401] Pid: 1433, comm: exe Not tainted (2.6.26-2-486 #1) [ 10.410443] EIP: 0060:[f89dbf90] EFLAGS: 00010246 CPU: 0 [ 10.410499] EIP is at nfs_create+0x47/0xa4 [nfs] [ 10.410539] EAX: f7136ae4 EBX: 8124 ECX: 8124 EDX: [ 10.410581] ESI: f70f2294 EDI: f7136ae4 EBP: ESP: f79e9c6c [ 10.410623] DS: 007b ES: 007b FS: GS: 0033 SS: 0068 [ 10.410665] Process exe (pid: 1433, ti=f79e8000 task=f79414d0 task.ti=f79e8000) [ 10.410708] Stack: 0001 39368124 3961 fffee532 f8a0acb0 f79e9c94 f897c580 f7455cc0 [ 10.410967]f7136ae4 f7136ae4 f89dbafe 0003 c016b971 f89f9d20 f7136ae4 8124 [ 10.411224]f70f2294 c016bf2b 0124 f7138594 f70f2294 f89a4cee [ 10.411482] Call Trace: [ 10.411554] [f89dbafe] nfs_permission+0x0/0x10d [nfs] [ 10.411633] [c016b971] permission+0xd6/0xfc [ 10.411698] [c016bf2b] vfs_create+0xb4/0x116 [ 10.411763] [f89a4cee] au_h_create+0x25/0x93 [aufs] The trace proceeds thusly. I am then left in a BusyBox shell. The read-only NFS mount (10.0.0.1:/srv/debian-live mounted on /live/image) behaves correctly. Attempting to list the contents of the COW NFS mount (10.0.0.1:/srv/debian-live-cow mounted on /cow) locks up and will not respond to SIGINT. I am able to mount both NFS shares successfully on other machines. I am also able to mount the COW NFS share on the initramfs after the segfault using the same command that the /live.log claimed failed in the first place (nfsmount -o nolock 10.0.0.1:/srv/debian-live-cow /cow) as long as I change the mount point. Attempting to run the AUFS mount over that using mount -o noatime,dirs=/foo=rw://filesystem.squashfs=rr -t aufs aufs /bar (where /foo is the place I mounted the newer COW NFS share) leads to the same segfault. Please also note that passing the boot-time parameter nopersistent avoids all of this. As a result of the above, I can only conclude that this is the result of some peculiar combination between AUFS and using an NFS share for COW. I have no workaround. Please let me know if I can provide any additional information. -- Package-specific info: -- System Information: Debian Release: 5.0.2 APT prefers stable APT policy: (600, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.18-5-686 (SMP w/1 CPU core) Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages live-initramfs depends on: ii busybox 1:1.10.2-2 Tiny utilities for small and embed ii file 4.26-1 Determines file type using magic ii initramfs-tools 0.92o
Bug#446357: kcalc: Problem Related to Use of Constants
Package: kcalc Version: 4:3.5.9-2 Followup-For: Bug #446357 I have encountered this problem as well. As a simple workaround, you can copy the constant into a text editor, clear the calculator, and paste the constant in (rather than using the Constants menu or some other built-in means to get your Euler number). It seems that it only crashes when you raise a constant (such as the Euler number) to a sufficiently complicated number (e^pi worked for me, but I encountered it while trying to calculate e^-7.3635959605). -- System Information: Debian Release: 5.0.2 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-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 kcalc depends on: ii kdelibs4c2a 4:3.5.10.dfsg.1-0lenny1 core libraries and binaries for al ii libc62.7-18 GNU C Library: Shared libraries ii libgcc1 1:4.3.2-1.1 GCC support library ii libgmp3c22:4.2.2+dfsg-3 Multiprecision arithmetic library ii libqt3-mt3:3.3.8b-5+b1 Qt GUI Library (Threaded runtime v ii libstdc++6 4.3.2-1.1 The GNU Standard C++ Library v3 kcalc recommends no packages. Versions of packages kcalc suggests: ii khelpcente 4:4.0.0.really.3.5.9.dfsg.1-6 help center for KDE -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#538256: icedove: Silent failure to automatically check inbox when password is incorrect
Package: icedove Version: 2.0.0.22-0lenny1 Severity: normal Icedove does not display any alert or error message if it automatically checks an inbox and the password stored in the password manager is incorrect. The most common example of this occurring is when the e-mail server requires a password change (i.e., password expires every six months). In this case, it happily tries the old, dead password again and again. This leads to two problems. Firstly, the user may be unaware of the change (particularly in my case, in which the password is part of an SSO system that controls a number of services of which e-mail is only one) and thus unaware of the fact that mail may be available. Second, Icedove continually retries with the old password, causing it to trigger account lock-outs. -- System Information: Debian Release: 5.0.2 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-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 icedove depends on: ii debianutils2.30 Miscellaneous utilities specific t ii fontconfig 2.6.0-3 generic font configuration library ii libatk1.0-01.22.0-1 The ATK accessibility toolkit ii libc6 2.7-18GNU C Library: Shared libraries ii libcairo2 1.6.4-7 The Cairo 2D vector graphics libra ii libfontconfig1 2.6.0-3 generic font configuration library ii libfreetype6 2.3.7-2+lenny1FreeType 2 font engine, shared lib ii libgcc11:4.3.2-1.1 GCC support library ii libglib2.0-0 2.16.6-2 The GLib library of C routines ii libgtk2.0-02.12.12-1~lenny1 The GTK+ graphical user interface ii libhunspell-1.2-0 1.2.6-1 spell checker and morphological an ii libjpeg62 6b-14 The Independent JPEG Group's JPEG ii libnspr4-0d4.7.1-4 NetScape Portable Runtime Library ii libnss3-1d 3.12.0-6 Network Security Service libraries ii libpango1.0-0 1.20.5-5 Layout and rendering of internatio ii libpng12-0 1.2.27-2+lenny2 PNG library - runtime ii libstdc++6 4.3.2-1.1 The GNU Standard C++ Library v3 ii libx11-6 2:1.1.5-2 X11 client-side library ii libxft22.1.12-3 FreeType-based font drawing librar ii libxinerama1 2:1.0.3-2 X11 Xinerama extension library ii libxrender11:0.9.4-2 X Rendering Extension client libra ii libxt6 1:1.0.5-3 X11 toolkit intrinsics library ii psmisc 22.6-1Utilities that use the proc filesy ii zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime icedove recommends no packages. Versions of packages icedove suggests: pn icedove-gnome-support none (no description available) ii latex-xft-fonts 0.1-8 Xft-compatible versions of some La ii libthai0 0.1.9-4Thai language support library -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#515015: azureus incorrectly depends on openjdk-6-jre
Shaun, The Sun-based alternative is sun-java6-jre. It's part of the mainline Debian non-free archives because it requires acceptance of the Sun DLJ (distributor's license for Java). Thanks much! - Zach Hi Zachary, Azureus depends on openjdk-6-jre primarily to exclude the GNU java interpreter, which for some unknown reason does not work with Azureus. Since, as far as I know, Sun's java interpreter is not in the Debian archive, I didn't add an explicit alternative for it. I don't however see any harm in adding an alternative. What's the name of the Sun java interpreter package? Cheers, Shaun 2009/7/10 Zachary Palmer zep_deb...@bahj.com: Package: azureus Version: 3.1.1.0-4 Followup-For: Bug #515015 In order to correct this, azureus should be made to depend upon java6-runtime, right? Then, one could use either OpenJDK's JRE or the Sun JRE to run Azureus. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#515015: azureus incorrectly depends on openjdk-6-jre
Package: azureus Version: 3.1.1.0-4 Followup-For: Bug #515015 In order to correct this, azureus should be made to depend upon java6-runtime, right? Then, one could use either OpenJDK's JRE or the Sun JRE to run Azureus. -- System Information: Debian Release: 5.0.1 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-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 azureus depends on: ii libcommons-cli-java 1.1-3 API for working with the command l ii liblog4j1.2-java 1.2.15-4Logging library for java ii libswt-gtk-3.4-java 3.4-1 Standard Widget Toolkit for GTK+ J ii openjdk-6-jre6b11-9.1+lenny2 OpenJDK Java runtime, using Hotspo Versions of packages azureus recommends: ii vuze 3.1.1.0-4 Multimedia BitTorrent client azureus suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#536297: kile: Missing Working Directory Causes Spurious Errors
Package: kile Version: 1:2.0.1-1 Severity: normal If kile's working directory does not exist, it is incapable of opening new files. It also produces an error message whenever a file is compiled, although a successful compile will display the file appropriately. To reproduce this bug is simple: mkdir /tmp/kilebug cd /tmp/kilebug kile # Open a .tex file in Kile and verify that everything is working. cd / rmdir /tmp/kilebug # Try to open a .tex file in Kile and observe that it will fail. -- System Information: Debian Release: 5.0.1 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-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 kile depends on: ii kdelibs4c2a 4:3.5.10.dfsg.1-0lenny1 core libraries and binaries for al ii konsole 4:3.5.9.dfsg.1-6X terminal emulator for KDE ii libc62.7-18 GNU C Library: Shared libraries ii libqt3-mt3:3.3.8b-5+b1 Qt GUI Library (Threaded runtime v ii libstdc++6 4.3.2-1.1 The GNU Standard C++ Library v3 ii texlive-latex-ba 2007.dfsg.1-5 TeX Live: Basic LaTeX packages Versions of packages kile recommends: ii dvipng 1.11-1 convert DVI files to PNG graphics ii kdvi4:3.5.9-3+lenny1 dvi viewer for KDE ii kghostview 4:3.5.9-3+lenny1 PostScript viewer for KDE ii kpdf4:3.5.9-3+lenny1 PDF viewer for KDE Versions of packages kile suggests: pn gbib none (no description available) pn gv none (no description available) pn kile-i18nnone (no description available) ii latex2html 2002-2-1-20050114-6 LaTeX to HTML translator pn pybliographernone (no description available) pn xfig none (no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#481028: initscripts: if-up.d too aggressive with multiple interfaces
Package: initscripts Version: 2.86.ds1-61 Followup-For: Bug #481028 I recently upgraded to Lenny and noticed the same problem on my machine (albeit to a lesser extent, as I only have about ten virtual interfaces). I've observed that the delay problem is not actually the mountnfs script itself (although it does like to babble); it's that *every* script in if-up.d gets executed for *every* interface. This means that anyone who has fifty virtual interfaces gets to run things like openssh-server fifty times. For me, removing avahi-daemon sped things up quite a lot; it took a couple seconds each time to restart. Which leads me to wonder: should these scripts be rewritten to recognize (as mountnfs does) that there are still interfaces pending and hold off their operations until the last interface comes up? The script used in mountnfs could be generalized so that each script simply does something like is_last_interface || exit 0 at the top (probably with an additional check to ensure that we're actually bringing everything up and not just in the middle of reconfiguring one interface) in order to prevent them from being run a bunch of times. What we really need is to have ifup -a set another environment variable (in addition to the ones listed in the interfaces man page) which indicates whether or not the current interface being brought up is the last one (such as NOT_LAST). NOT_LAST would be unset for the last interface of an ifup -a as well as for any execution of ifup on a single interface (e.g., ifup eth0). But I don't know how feasible that would be; can anyone make any comments about that? Nonetheless, mountnfs is still quite chatty. It could probably mention all of the interfaces on a single line; that would help a lot. (e.g.: if-up.d/mountnfs[eth1:5]: waiting for interfaces before doing NFS mounts: eth1:6, eth1:7, eth1:8, ...) Cheers! -- System Information: Debian Release: 5.0 APT prefers stable APT policy: (600, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core) Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages initscripts depends on: ii debianutils 2.30Miscellaneous utilities specific t ii e2fsprogs1.41.3-1ext2/ext3/ext4 file system utiliti ii libc62.7-18 GNU C Library: Shared libraries ii lsb-base 3.2-20 Linux Standard Base 3.2 init scrip ii mount2.13.1.1-1 Tools for mounting and manipulatin ii sysvinit-utils 2.86.ds1-61 System-V-like utilities Versions of packages initscripts recommends: ii psmisc22.6-1 Utilities that use the proc filesy initscripts suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#398435: backupninja: Spaces now becoming wildcards
Package: backupninja Version: 0.9.6-4 Followup-For: Bug #398435 Instead of splitting a path (such as /foo bar) into different pieces, backupninja is now using a wildcard (such as --include '/foo*'). This is better, but still not correct behavior; I'm not sure what the upstream authors' rationale was, but this could easily include directories which are not intended for backup. -- System Information: Debian Release: 5.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.26-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 backupninja depends on: ii bash 3.2-4 The GNU Bourne Again SHell ii bsd-mailx [mailx] 8.1.2-0.20071201cvs-3 A simple mail user agent ii dialog 1.1-20080819-1Displays user-friendly dialog boxe ii mailx 1:20071201-3 Transitional package for mailx ren ii mawk 1.3.3-11.1a pattern scanning and text proces backupninja recommends no packages. Versions of packages backupninja suggests: ii cdrdao1:1.2.2-16 records CDs in Disk-At-Once (DAO) pn debconf-utils none (no description available) ii dvd+rw-tools 7.1-3 DVD+-RW/R tools ii genisoimage 9:1.1.9-1 Creates ISO-9660 CD-ROM filesystem pn hwinfonone (no description available) pn mdadm none (no description available) ii rdiff-backup 1.2.2-1remote incremental backup ii wodim 9:1.1.9-1 command line CD/DVD writing tool -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#514299: jacksum: Incorrect output for data provided by stdin
Package: jacksum Version: 1.7.0-2 Severity: normal *** /tmp/reportbug-jacksum-20090205-14781-RuopgH Subject: jacksum: incorrect checksum generated from stdin Package: jacksum Version: 1.7.0-2 Severity: normal When reading from standard input, Jacksum assumes the existence of a newline at the end of the input even if one is not present. Consider the following: zpal...@thirtyseven:~$ echo test | md5sum d8e8fca2dc0f896fd7cb4cb0031ba249 - zpal...@thirtyseven:~$ echo test | jacksum -a md5 d8e8fca2dc0f896fd7cb4cb0031ba249 zpal...@thirtyseven:~$ echo -n test | md5sum 098f6bcd4621d373cade4e832627b4f6 - zpal...@thirtyseven:~$ echo -n test | jacksum -a md5 d8e8fca2dc0f896fd7cb4cb0031ba249 This appears to be independent of the algorithm in question; the same problem arose when using CRC8 and SHA1. This problem is not present when reading from a file: zpal...@thirtyseven:~$ echo -n test ztemp zpal...@thirtyseven:~$ jacksum -a md5 ztemp 098f6bcd4621d373cade4e832627b4f6 ztemp -- System Information: Debian Release: 5.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.26-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 jacksum depends on: ii gij-4.1 [java2-runtime] 4.1.1-20 The GNU Java bytecode interpreter ii java-gcj-compat [java2-runtim 1.0.78-2 Java runtime environment using GIJ ii openjdk-6-jre [java2-runtime] 6b11-9 OpenJDK Java runtime, using Hotspo ii sun-java5-jre [java2-runtime] 1.5.0-16-3 Sun Java(TM) Runtime Environment ( ii sun-java6-jre [java2-runtime] 6-07-4 Sun Java(TM) Runtime Environment ( jacksum recommends no packages. Versions of packages jacksum suggests: ii gij [java-virtual-machine]4:4.3.2-2 The GNU Java bytecode interpreter ii gij-4.1 [java-virtual-machine 4.1.1-20 The GNU Java bytecode interpreter ii gij-4.3 [java-virtual-machine 4.3.2-2The GNU Java bytecode interpreter ii java-gcj-compat [java-virtual 1.0.78-2 Java runtime environment using GIJ ii java-gcj-compat-headless [jav 1.0.78-2 Java runtime environment using GIJ ii openjdk-6-jre-headless [java- 6b11-9 OpenJDK Java runtime, using Hotspo ii sun-java5-jre [java-virtual-m 1.5.0-16-3 Sun Java(TM) Runtime Environment ( ii sun-java6-jre [java-virtual-m 6-07-4 Sun Java(TM) Runtime Environment ( -- no debconf information -- System Information: Debian Release: 5.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.26-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 jacksum depends on: ii gij-4.1 [java2-runtime] 4.1.1-20 The GNU Java bytecode interpreter ii java-gcj-compat [java2-runtim 1.0.78-2 Java runtime environment using GIJ ii openjdk-6-jre [java2-runtime] 6b11-9 OpenJDK Java runtime, using Hotspo ii sun-java5-jre [java2-runtime] 1.5.0-16-3 Sun Java(TM) Runtime Environment ( ii sun-java6-jre [java2-runtime] 6-07-4 Sun Java(TM) Runtime Environment ( jacksum recommends no packages. Versions of packages jacksum suggests: ii gij [java-virtual-machine]4:4.3.2-2 The GNU Java bytecode interpreter ii gij-4.1 [java-virtual-machine 4.1.1-20 The GNU Java bytecode interpreter ii gij-4.3 [java-virtual-machine 4.3.2-2The GNU Java bytecode interpreter ii java-gcj-compat [java-virtual 1.0.78-2 Java runtime environment using GIJ ii java-gcj-compat-headless [jav 1.0.78-2 Java runtime environment using GIJ ii openjdk-6-jre-headless [java- 6b11-9 OpenJDK Java runtime, using Hotspo ii sun-java5-jre [java-virtual-m 1.5.0-16-3 Sun Java(TM) Runtime Environment ( ii sun-java6-jre [java-virtual-m 6-07-4 Sun Java(TM) Runtime Environment ( -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#493065: debootstrap fakechroot variant fails for i386 chroot on AMD64 system
Package: debootstrap Version: 1.0.10 Severity: normal On an AMD64 system, it appears to be impossible to use the fakechroot variant to create an i386 chroot. * It is entirely possible for a user to create an i386 root using fakechroot and debootstrap on an i386 Debian system. * It is also possible for a user to create an AMD64 root using fakechroot and debootstrap on an AMD64 system. * Using Etch on an AMD64 system, it is possible to debootstrap an Etch i386 chroot using fakechroot. * Using Lenny on an AMD64 system, it is NOT possible to debootstrap a Lenny i386 chroot using fakechroot. When attempting to execute the command fakechroot fakeroot debootstrap --arch i386 --variant=fakechroot etch target I receive the message W: Failure trying to run: chroot /path/to/target dpkg --force-depends --install var/cache/apt/archives/base-files_4_i386.deb var/cache/apt/archives/base-passwd_3.5.11_i386.deb The contents of the target's /debootstrap/debootstrap.log are: dpkg: /home/zpalmer/sandbox/ztemp2/test7/lib/tls/libc.so.6: version `GLIBC_2.4' not found (required by /usr/lib32/libfakeroot/libfakeroot-sysv.so) This leads me to believe that it either has something to do with the way debootstrap executes the fakechroot variant or something to do with how the fakeroot package is built. Either way, this prevents cross-platform fakechroot debootstraps. I have no workaround at this time other than to create a normal 32-bit chroot on my system using privileges and do the fakechroot from within that. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.25-2-amd64 (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 debootstrap depends on: ii binutils2.18.1~cvs20080103-7 The GNU assembler, linker and bina ii wget1.11.4-1 retrieves files from the web debootstrap recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#432107: fakechroot fails on AMD64 Lenny systems
Package: fakechroot Version: 2.6-1.3 Severity: important Using an AMD64 VM, I installed Debian Etch from the netinst disc and using http://ftp.debian.org/debian as the network mirror. I then added the line deb http://ftp.debian.org/debian testing main to /etc/apt/sources.list and ran the following sequence of commands: apt-get update apt-get dist-upgrade apt-get install fakeroot fakechroot debootstrap Then, as a normal user, I ran fakeroot fakechroot debootstrap --variant=fakechroot etch /some/testdir 'http://http.us.debian.org/debian' debootstrap successfully downloaded, verified, and extracted all of the packages but then failed with the error message in debootstrap.log: dpkg: /some/testdir/lib/tls/libc.so.6: version `GLIBC_2.4' not found (required by /usr/lib/libfakeroot/libfakeroot-sysv.so) fakeroot, fakechroot, and debootstrap perform perfectly well under a clean Debian Etch installation from what I can tell. Cheers! Zach -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.18-4-amd64 (SMP w/1 CPU core) 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 fakechroot depends on: ii libc6 2.5-9 GNU C Library: Shared libraries ii libc6-i3862.5-9 GNU C Library: 32bit shared librar fakechroot recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#413044: apt-get source does not respect pinning
Package: apt Version: 0.6.46.4 Severity: normal apt-get source does not seem to respect pinning. I have experimental in my sources.list and pinned to -1 (so experimental packages won't be installed unless explicitly requested). If I run apt-get source, however, the experimental source package is downloaded. I would expect that the source package which corresponds to the binary which is installed by apt-get install would instead be obtained. -- Package-specific info: -- apt-config dump -- APT ; APT::Architecture amd64; APT::Build-Essential ; APT::Build-Essential:: build-essential; APT::Cache-Limit 33554432; Dir /; Dir::State var/lib/apt/; Dir::State::lists lists/; Dir::State::cdroms cdroms.list; Dir::State::userstatus status.user; Dir::State::status /var/lib/dpkg/status; Dir::Cache var/cache/apt/; Dir::Cache::archives archives/; Dir::Cache::srcpkgcache srcpkgcache.bin; Dir::Cache::pkgcache pkgcache.bin; Dir::Etc etc/apt/; Dir::Etc::sourcelist sources.list; Dir::Etc::sourceparts sources.list.d; Dir::Etc::vendorlist vendors.list; Dir::Etc::vendorparts vendors.list.d; Dir::Etc::main apt.conf; Dir::Etc::parts apt.conf.d; Dir::Etc::preferences preferences; Dir::Bin ; Dir::Bin::methods /usr/lib/apt/methods; Dir::Bin::dpkg /usr/bin/dpkg; DPkg ; DPkg::Pre-Install-Pkgs ; DPkg::Pre-Install-Pkgs:: /usr/sbin/dpkg-preconfigure --apt || true; -- /etc/apt/preferences -- Package: * Pin: release a=sarge Pin-Priority: 500 Package: * Pin: release a=testing Pin-Priority: 600 Package: * Pin: release a=unstable Pin-Priority: 400 Package: * Pin: release a=experimental Pin-Priority: -1 -- /etc/apt/sources.list -- # Sarge fallback deb http://amd64.debian.net/debian sarge main contrib non-free deb-src http://amd64.debian.net/debian sarge main contrib non-free deb http://security.debian.org sarge/updates main contrib non-free # Mainline testing deb http://http.us.debian.org/debian testing main contrib non-free deb-src http://http.us.debian.org/debian testing main contrib non-free deb http://security.debian.org testing/updates main contrib non-free # Mainline unstable deb http://http.us.debian.org/debian unstable main contrib non-free deb-src http://http.us.debian.org/debian unstable main contrib non-free # Mainline experimental (pinned to -1) deb http://http.us.debian.org/debian experimental main contrib non-free deb-src http://http.us.debian.org/debian experimental main contrib non-free # Debian multimedia deb http://www.debian-multimedia.org/ testing main deb http://www.debian-multimedia.org/ unstable main -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (600, 'testing'), (500, 'stable'), (400, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-2-amd64 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages apt depends on: ii debian-archive-keyring 2006.11.22 GnuPG archive keys of the Debian a ii libc62.3.6.ds1-7 GNU C Library: Shared libraries ii libgcc1 1:4.1.1-13 GCC support library ii libstdc++6 4.1.1-13The GNU Standard C++ Library v3 apt recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#411178: genisoimage: -stream-media-size causes problems with a very large (=4Gb) file
Package: genisoimage Version: 9:1.1.1-1 Severity: normal Using the -stream-media-size option with genisoimage will silently break when used with files of 4Gb or larger. The following command illustrates this: dd if=/dev/zero bs=1024M count=4 2/dev/null | genisoimage\ -stream-media-size $((512*1024*4+201)) broken.iso The media size is specified as 2097152 sectors (4Gb) plus the 200 sectors genisoimage needs to store metadata plus one sector (because genisoimage seems to need more than it claims). If the ISO-9660 filesystem is then mounted, it shows one file (stream.img) which appears to contain zero bytes. genisoimage does not fail, nor does it complain or warn of this problem. Cheers! -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (600, 'testing'), (500, 'stable'), (400, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-2-amd64 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages genisoimage depends on: ii libc62.3.6.ds1-7 GNU C Library: Shared libraries ii libmagic14.17-3 File type determination library us ii zlib1g 1:1.2.3-13 compression library - runtime genisoimage recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#387673: debootstrap to target with spaces fails
Package: debootstrap Version: 0.3.3 Severity: normal Running debootstrap when the target directory contains spaces causes odd behavior and does not result in bootstrap. For example, running debootstrap sarge /some/path/some directory http://mirror.site/debian will create the directories /some/path/some, /some/path/some/directory, and /some/path/some directory/debootstrap. The output of the program is a single line, I: Validating Release. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (600, 'testing'), (500, 'stable'), (400, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-2-amd64 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages debootstrap depends on: ii binutils 2.17-2 The GNU assembler, linker and bina ii wget 1.10.2-2 retrieves files from the web debootstrap recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#386056: linux-image-2.6.17-2-amd64: Out of Memory syslog kernel message with more than 2Gb of RAM
Package: linux-image-2.6.17-2-amd64 Version: 2.6.17-8 Severity: critical Justification: breaks unrelated software The specifications of the machine in question before the bug was found: AMD64 3700+ processor (single core) ASUS A8N-SLI deluxe motherboard 2Gb of 333MHz DDR in two 1Gb sticks Debian Etch (dist-upgrade as of August 31) Debian stock kernel 2.6.17-2-amd64 VMWare 5.5 using Any-to-Any patch, installed and running properly Everything was happy until I added another 1Gb of RAM to the machine (in the form of two 512Mb 400MHz DDR sticks). Upon doing so, the VMWare GUI launches properly but starting a VM crashes the entire X session and a number of other programs with the following output to syslog: --- Sep 4 00:40:31 localhost kernel: Active:73720 inactive:32596 dirty:683 writeback:0 unstable:0 free:648340 slab:9099 mapped:57706 pagetables:1790 Sep 4 00:40:31 localhost kernel: Node 0 DMA free:24kB min:24kB low:28kB high:36kB active:0kB inactive:0kB present:11292kB pages_scanned:0 all_unreclaimable? yes Sep 4 00:40:31 localhost kernel: lowmem_reserve[]: 0 3014 3014 3014 Sep 4 00:40:31 localhost kernel: Node 0 DMA32 free:2593336kB min:7012kB low:8764kB high:10516kB active:294880kB inactive:130384kB present:3086500kB pages_scanned:0 all_unreclaimable? no Sep 4 00:40:31 localhost kernel: lowmem_reserve[]: 0 0 0 0 Sep 4 00:40:31 localhost kernel: Node 0 Normal free:0kB min:0kB low:0kB high:0kB active:0kB inactive:0kB present:0kB pages_scanned:0 all_unreclaimable? no Sep 4 00:40:31 localhost kernel: lowmem_reserve[]: 0 0 0 0 Sep 4 00:40:31 localhost kernel: Node 0 HighMem free:0kB min:128kB low:128kB high:128kB active:0kB inactive:0kB present:0kB pages_scanned:0 all_unreclaimable? no Sep 4 00:40:31 localhost kernel: lowmem_reserve[]: 0 0 0 0 Sep 4 00:40:31 localhost kernel: Node 0 DMA: 0*4kB 1*8kB 1*16kB 0*32kB 0*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 24kB Sep 4 00:40:31 localhost kernel: Node 0 DMA32: 2506*4kB 19942*8kB 21602*16kB 16772*32kB 10139*64kB 4347*128kB 843*256kB 109*512kB 29*1024kB 11*2048kB 3*4096kB = 2593336kB Sep 4 00:40:31 localhost kernel: Node 0 Normal: empty Sep 4 00:40:31 localhost kernel: Node 0 HighMem: empty Sep 4 00:40:31 localhost kernel: Swap cache: add 44, delete 44, find 0/0, race 0+0 Sep 4 00:40:31 localhost kernel: Free swap = 3855420kB Sep 4 00:40:31 localhost kernel: Total swap = 3855592kB Sep 4 00:40:31 localhost kernel: Free swap: 3855420kB Sep 4 00:40:31 localhost kernel: 786416 pages of RAM Sep 4 00:40:31 localhost kernel: 13657 reserved pages Sep 4 00:40:31 localhost kernel: 120890 pages shared Sep 4 00:40:31 localhost kernel: 0 pages swap cached Sep 4 00:40:31 localhost kernel: Out of Memory: Kill process 21606 (kdeinit) score 200185 and children. Sep 4 00:40:31 localhost kernel: Out of memory: Killed process 21634 (artsd). Sep 4 00:40:31 localhost kernel: Out of Memory: Kill process 21606 (kdeinit) score 191734 and children. Sep 4 00:40:31 localhost kernel: Out of memory: Killed process 21638 (konqueror). Sep 4 00:40:31 localhost kernel: Out of Memory: Kill process 21606 (kdeinit) score 165438 and children. Sep 4 00:40:31 localhost kernel: Out of memory: Killed process 21639 (konqueror). Sep 4 00:40:31 localhost kernel: Out of Memory: Kill process 21606 (kdeinit) score 139152 and children. Sep 4 00:40:31 localhost kernel: Out of memory: Killed process 21640 (kwrite). Sep 4 00:40:31 localhost kernel: Out of Memory: Kill process 21606 (kdeinit) score 124096 and children. Sep 4 00:40:31 localhost kernel: Out of memory: Killed process 21641 (konqueror). Sep 4 00:40:31 localhost kernel: Out of Memory: Kill process 21606 (kdeinit) score 97760 and children. Sep 4 00:40:31 localhost kernel: Out of memory: Killed process 21642 (konqueror). Sep 4 00:40:31 localhost kernel: Out of Memory: Kill process 21606 (kdeinit) score 71478 and children. Sep 4 00:40:31 localhost kernel: Out of memory: Killed process 21643 (konqueror). Sep 4 00:40:31 localhost kernel: Out of Memory: Kill process 21644 (gaim) score 58404 and children. Sep 4 00:40:31 localhost kernel: Out of memory: Killed process 21651 (gaim). Sep 4 00:40:31 localhost kernel: Out of Memory: Kill process 21606 (kdeinit) score 45197 and children. Sep 4 00:40:31 localhost kernel: Out of memory: Killed process 21644 (gaim). Sep 4 00:40:31 localhost kernel: Out of Memory: Kill process 21623 (kdesktop) score 30577 and children. Sep 4 00:40:31 localhost kernel: Out of memory: Killed process 21623 (kdesktop). Sep 4 00:40:31 localhost kernel: Out of Memory: Kill process 21606 (kdeinit) score 30482 and children. Sep 4 00:40:31 localhost kernel: Out of memory: Killed process 21823 (wrapper-gtk24.s). Sep 4 00:40:31 localhost kernel: Out of Memory: Kill process 21613 (kded) score 30037 and children. Sep 4 00:40:31 localhost kernel: Out of memory: Killed process 21613
