Bug#931041: Acknowledgement (basez: fails to decode base64url strings with the padding trimmed)
Sorry it failed even with the padding, so I don't know what is failing in basez.
Bug#931041: basez: fails to decode base64url strings with the padding trimmed
Package: basez Version: 1.6-3 Severity: important Tags: upstream Dear Maintainer, * Decoding a JWT signature showed that omitting the padding (as required by one of the JWS RFC) causes a failure in base64url -d. $ echo -n Igzmk82YO1cNEjjEF0WQMEv4tGPLrgm43Yrh_bFvHStV2Qju-eebyN82F-fASOZqQxOGL9sU_g6ewloKNk5yO7Dt__YqJ9GROXiovYD6cM4G2UboYn7BCf4lH84kfRNZAxrVNOOC50aYuVTvTGQrxXUooq9KnCkQzeZLbl26Vw7Yq0fP_D39ztoNu5Oyy0Nar_iHRyyPqAyia3VhrcETIK199IUG4QK0Rj2UIfEg6qPhVrE2rVKZy2zd4s871sLg0XuqOdwwZsYsIBP0tcd2C2-6HTfDNlBEoWo_XtF3DbkvNiBA75xHcxlXkq__ytCdicXDkdfOiS39IfsyzzmGEg== | tr -- '-_' '+/' | base64 -d | xxd -g0 -ps -c20 220ce693cd983b570d1238c4174590304bf8b463 cbae09b8dd8ae1fdb16f1d2b55d908eef9e79bc8 df3617e7c048e66a4313862fdb14fe0e9ec25a0a 364e723bb0edfff62a27d1913978a8bd80fa70ce 06d946e8627ec109fe251fce247d1359031ad534 e382e74698b954ef4c642bc57528a2af4a9c2910 cde64b6e5dba570ed8ab47cffc3dfdceda0dbb93 b2cb435aaff887472c8fa80ca26b7561adc11320 ad7df48506e102b4463d9421f120eaa3e156b136 ad5299cb6cdde2cf3bd6c2e0d17baa39dc3066c6 2c2013f4b5c7760b6fba1d37c3365044a16a3f5e d1770db92f362040ef9c4773195792afffcad09d 89c5c391d7ce892dfd21fb32cf398612 $ echo -n Igzmk82YO1cNEjjEF0WQMEv4tGPLrgm43Yrh_bFvHStV2Qju-eebyN82F-fASOZqQxOGL9sU_g6ewloKNk5yO7Dt__YqJ9GROXiovYD6cM4G2UboYn7BCf4lH84kfRNZAxrVNOOC50aYuVTvTGQrxXUooq9KnCkQzeZLbl26Vw7Yq0fP_D39ztoNu5Oyy0Nar_iHRyyPqAyia3VhrcETIK199IUG4QK0Rj2UIfEg6qPhVrE2rVKZy2zd4s871sLg0XuqOdwwZsYsIBP0tcd2C2-6HTfDNlBEoWo_XtF3DbkvNiBA75xHcxlXkq__ytCdicXDkdfOiS39IfsyzzmGEg== | base64url -d base64url: invalid input -- System Information: Debian Release: 10.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.18.16-x86_64-linode118 (SMP w/1 CPU core; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages basez depends on: ii libc6 2.28-10 basez recommends no packages. basez suggests no packages. -- no debconf information
Bug#712099: appears a feature not a bug
I contacted the author and he pointed to the "-a" option that controls the search behaviour. I found the "-A" option to follow my expectation of a forward and backward search, -a or --search-skip-screen By default, forward searches start at the top of the displayed screen and backwards searches start at the bottom of the displayed screen (except for repeated searches invoked by the n or N commands, which start after or before the "target" line respectively; see the -j op‐ tion for more about the target line). The -a option causes forward searches to instead start at the bottom of the screen and backward searches to start at the top of the screen, thus skipping all lines displayed on the screen. -A or --SEARCH-SKIP-SCREEN Causes all forward searches (not just non-repeated searches) to start just after the target line, and all backward searches to start just before the target line. Thus, forward searches will skip part of the displayed screen (from the first line up to and including the target line). Similarly backwards searches will skip the displayed screen from the last line up to and including the target line. This was the default behavior in less versions prior to 441. I don't understand why the default behaviour needed to change. --
Bug#705251: smbclient -L produces suspicious DNS lookup failures in log.nmbd
Package: smbclient Version: 2:3.6.13-1 Severity: minor Dear Maintainer, * What led up to the situation? Ran smbclient -A /etc/credentials-USER -L HOST.example.net * What exactly did you do (or not do) that was effective (or ineffective)? Ran the above command. * What was the outcome of this action? The list of shares showed up with a harmless NT_STATUS_CONNECTION_RESET message in the bottom. read_fd_with_timeout failed, read error = NT_STATUS_CONNECTION_RESET. Receiving SMB: Server 10.65.25.54 stopped responding session request to HOST.EXAMPLE.NET failed (Read error: Connection reset by peer) The log file /var/log/samba/log.nmbd had this, [2013/04/11 19:15:09, 3] nmbd/nmbd_winsserver.c:2068(wins_process_name_query_request) wins_process_name_query: name query for name HOST.EXAMPLE.NE<20> returning DNS fail. My /etc/request-key.conf has my correction against a dns_resolver from /sbin/key.dns_resover that worked around mounting DFS shares, #create dns_resolver * * /sbin/key.dns_resolver %k create userdebug:* negate /bin/keyctl negate %k 30 %S create userdebug:* rejected/bin/keyctl reject %k 30 %c %S create userdebug:* expired /bin/keyctl reject %k 30 %c %S create userdebug:* revoked /bin/keyctl reject %k 30 %c %S create userdebug:loop:** |/bin/cat create userdebug:* * /usr/share/keyutils /request-key-debug.sh %k %d %c %S # Follow a separate entry in /etc/request-key.d/ #create cifs.spnego * * /usr/sbin/cifs.upcall -t %k # Do not follow man cifs.upcall suggesting to prefer key.dns_resolver to # cifs.upcall as the former receives -126 from a call to # keyctl_instantiate_iov(). create dns_resolver* * /usr/sbin/cifs.upcall -t %k negate * * * /bin/keyctl negate %k 30 %S I kept another option in a separate file /etc/request- key.d/cifs.spnego.conf, create cifs.spnego* * /usr/sbin/cifs.upcall -t %k Running the same command against the short hostname HOST produced same list without the message. I have the recommended version of cifs-utils, $ dpkg -S /usr/sbin/cifs.upcall cifs-utils: /usr/sbin/cifs.upcall $ dpkg -l cifs-utils Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig- pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ NameVersionArchitecture Description +++-===-==-==-=== ii cifs-utils 2:5.5-1i386 Common Internet File System utilities * What outcome did you expect instead? No reset message, no suspicious DNS lookups. -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 3.8-trunk-amd64 (SMP w/2 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages smbclient depends on: ii dpkg 1.16.10 ii libc6 2.13-38 ii libcap2 1:2.22-1.2 ii libcomerr21.42.5-1.1 ii libgssapi-krb5-2 1.10.1+dfsg-5 ii libk5crypto3 1.10.1+dfsg-5 ii libkrb5-3 1.10.1+dfsg-5 ii libldap-2.4-2 2.4.31-1 ii libpopt0 1.16-7 ii libreadline6 6.2+dfsg-0.1 ii libtalloc22.0.8-0.1 ii libtdb1 1.2.10-2 ii libtinfo5 5.9-10 ii libwbclient0 2:3.6.13-1 ii samba-common 2:3.6.13-1 ii zlib1g1:1.2.7.dfsg-13 smbclient recommends no packages. Versions of packages smbclient suggests: ii cifs-utils 2:5.5-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#691093: a work-around
Running "dosfsck -r PARTITION" works around the crash. -- - This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#691093: /sbin/dosfsck: Re: /sbin/dosfsck: fsck.msdos with -a terminates with "buffer overflow detected"
Package: dosfstools Version: 3.0.13-1 Followup-For: Bug #691093 Dear Maintainer, Same here. * What led up to the situation? Checking the filesystem of a micro SD card. * What exactly did you do (or not do) that was effective (or ineffective)? I ran "sudo fsck /dev/sdc1 -a". * What was the outcome of this action? A crash dump referring to a buffer overflow detected by fortify. * What outcome did you expect instead? Fixing the file system. $ sudo fsck /dev/sdc1 -a fsck from util-linux 2.20.1 dosfsck 3.0.13, 30 Jun 2012, FAT32, LFN *** buffer overflow detected ***: fsck.vfat terminated === Backtrace: = /lib/i386-linux-gnu/i686/cmov/libc.so.6(__fortify_fail+0x50)[0xb766a3c0] /lib/i386-linux-gnu/i686/cmov/libc.so.6(+0xe92fa)[0xb76692fa] /lib/i386-linux-gnu/i686/cmov/libc.so.6(+0xe8a38)[0xb7668a38] /lib/i386-linux-gnu/i686/cmov/libc.so.6(_IO_default_xsputn+0x9e)[0xb75ef47e] /lib/i386-linux-gnu/i686/cmov/libc.so.6(_IO_vfprintf+0xef4)[0xb75c0954] /lib/i386-linux-gnu/i686/cmov/libc.so.6(__vsprintf_chk+0xa7)[0xb7668ae7] /lib/i386-linux-gnu/i686/cmov/libc.so.6(__sprintf_chk+0x2d)[0xb7668a2d] fsck.vfat[0x804c8d4] === Memory map: 08048000-08055000 r-xp 08:11 8650815/sbin/dosfsck 08055000-08056000 r--p c000 08:11 8650815/sbin/dosfsck 08056000-08057000 rw-p d000 08:11 8650815/sbin/dosfsck 08057000-08059000 rw-p 00:00 0 09bf5000-09c34000 rw-p 00:00 0 [heap] b74c9000-b74e5000 r-xp 08:11 5785914/lib/i386-linux- gnu/libgcc_s.so.1 b74e5000-b74e6000 rw-p 0001b000 08:11 5785914/lib/i386-linux- gnu/libgcc_s.so.1 b7505000-b758 rw-p 00:00 0 b758-b76dc000 r-xp 08:11 5921995/lib/i386-linux- gnu/i686/cmov/libc-2.13.so b76dc000-b76dd000 ---p 0015c000 08:11 5921995/lib/i386-linux- gnu/i686/cmov/libc-2.13.so b76dd000-b76df000 r--p 0015c000 08:11 5921995/lib/i386-linux- gnu/i686/cmov/libc-2.13.so b76df000-b76e rw-p 0015e000 08:11 5921995/lib/i386-linux- gnu/i686/cmov/libc-2.13.so b76e-b76e3000 rw-p 00:00 0 b7701000-b7704000 rw-p 00:00 0 b7704000-b7705000 r-xp 00:00 0 [vdso] b7705000-b7721000 r-xp 08:11 5788479/lib/i386-linux-gnu/ld-2.13.so b7721000-b7722000 r--p 0001b000 08:11 5788479/lib/i386-linux-gnu/ld-2.13.so b7722000-b7723000 rw-p 0001c000 08:11 5788479/lib/i386-linux-gnu/ld-2.13.so bfd76000-bfd97000 rw-p 00:00 0 [stack] fsck: Warning... fsck.vfat for device /dev/sdc1 exited with signal 6. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.5-trunk-686-pae (SMP w/2 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages dosfstools depends on: ii libc6 2.13-37 dosfstools recommends no packages. dosfstools 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#679319: a work-around
I worked around the crash by choosing Open JDK 1.7 to run davmail compiled by Open JDK 1.6. > sudo update-alternatives --config java I believe it is possible that davmail could compile with Open JDK 1.7 and that its build system prevents higher version numbers by mistake. I believe changing the Java runtime might hide the defect. I did not investigate the root cause of the defect. Perhaps, the libraries shown by the traces only receive a corruption from JDK. -- - This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#679319: a work-around
On 27/06/12 07:57 PM, Ilguiz Latypov wrote: > I worked around the crash by choosing Open JDK 1.7 to run davmail > compiled by Open JDK 1.6. > >> sudo update-alternatives --config java After reporting my work-around I followed advice of the davmail author and disabled the use of system proxy settings in the davmail setup dialog. I then switched the default Java runtime to Open JDK 1.6 and found that davmail could start without a crash. -- - This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#652092: Gnash does not handle --enable-avm2
Package: gnash Version: 0.8.10 The --enable-avm2 option causes a warning in the configure script saying that the script did not recognize the option. I found that configure.ac commented out its handling by putting "dnl" at the beginning of each line. Removing the "dnl" (delete to new line?) words and removing the build directory gnash-0.8.10~git.master21430, then running "make deb" resulted in a build break, CXX DefaultTagLoaders.lo /bin/bash ../libtool --silent --tag=CXX --mode=compile i486-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I/home/ilguiz/gnash/gnash-0.8.10~git.master21430/libcore -I.. -I/home/ilguiz/gnash/gnash-0.8.10~git.master21430/librender -I/home/ilguiz/gnash/gnash-0.8.10~git.master21430/libdevice -I/home/ilguiz/gnash/gnash-0.8.10~git.master21430/libcore/swf -I/home/ilguiz/gnash/gnash-0.8.10~git.master21430/libcore/abc -I/home/ilguiz/gnash/gnash-0.8.10~git.master21430/libcore/asobj -I/home/ilguiz/gnash/gnash-0.8.10~git.master21430/libcore/asobj/flash -I/home/ilguiz/gnash/gnash-0.8.10~git.master21430/libcore/parser -I/home/ilguiz/gnash/gnash-0.8.10~git.master21430/libcore/vm -I/home/ilguiz/gnash/gnash-0.8.10~git.master21430/libltdl -I/home/ilguiz/gnash/gnash-0.8.10~git.master21430/libbase -I/home/ilguiz/gnash/gnash-0.8.10~git.master21430/libmedia -I/home/ilguiz/gnash/gnash-0.8.10~git.master21430/libsound -pthread -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -W -Wall -Wcast-align -Wcast-qual -Wpointer-arith -Wreturn-type -Wnon-virtual-dtor -Wunused -fvisibility-inlines-hidden -c -o DefaultTagLoaders.lo `test -f 'swf/DefaultTagLoaders.cpp' || echo '/home/ilguiz/gnash/gnash-0.8.10~git.master21430/libcore/'`swf/DefaultTagLoaders.cpp In file included from /home/ilguiz/gnash/gnash-0.8.10~git.master21430/libcore/swf/DefaultTagLoaders.cpp:59:0: /home/ilguiz/gnash/gnash-0.8.10~git.master21430/libcore/swf/SymbolClassTag.h: In member function 'virtual void gnash::SWF::SymbolClassTag::executeActions(gnash::MovieClip*, gnash::DisplayList&) const': /home/ilguiz/gnash/gnash-0.8.10~git.master21430/libcore/swf/SymbolClassTag.h:48:33: error: 'class gnash::VM' has no member named 'getMachine' In file included from /home/ilguiz/gnash/gnash-0.8.10~git.master21430/libcore/swf/DefaultTagLoaders.cpp:60:0: /home/ilguiz/gnash/gnash-0.8.10~git.master21430/libcore/swf/DoABCTag.h: In member function 'virtual void gnash::SWF::DoABCTag::executeActions(gnash::MovieClip*, gnash::DisplayList&) const': /home/ilguiz/gnash/gnash-0.8.10~git.master21430/libcore/swf/DoABCTag.h:56:33: error: 'class gnash::VM' has no member named 'getMachine' make[6]: *** [DefaultTagLoaders.lo] Error 1 make[6]: Leaving directory `/home/ilguiz/gnash/gnash-0.8.10~git.master21430/_build/libcore' It seems that the handling of the option was put away because it did not follow later changes in the code and/or did not agree with those changes. So I guess addining the --enable-avm2 option to debian/rules did not enable AVM2, and my tests on a flash web site confirm that. I tried lightspark, but it gave Unsupported ActionScript exception on the "yet unsupported Flash file," http://www.rogersondemand.com/f/hero.swf?ver=2.9.5.13 I wonder if the description of gnash could refer to lightspark as the package extending capabilities of gnash. -- ilguiz - This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#645210: debian-installer: grub2 setup for a new drive misses a Windows boot choice from the original drive
Package: debian-installer Version: i386 netinst as of October 5, 2011 Severity: important Tags: d-i Dear Maintainer, * What led up to the situation? I decided to install Debian on a new disk drive and preserve the Windows installation on the original drive. I downloaded the latest i386 netinst ISO image of Debian Installer, burned it on a DVD and booted off it. * What exactly did you do (or not do) that was effective (or ineffective)? I chose the new drive for simple partitioning. I chose to install Grub2 in MBR of the original drive. * What was the outcome of this action? I did not see Windows as a boot option. (This took a worse turn when the udev in the initial RAM disk image loaded a kernel module "radeon" for my video card ATI Radeon HD 3600, apparently in an attempt to provide a frame buffer for the text mode, and the video card showed garbage. It took a while to add an option "blacklist=radeon" to the kernel command line at boot time and add a line "blacklist radeon" to a file in /etc/modprobe.d). * What outcome did you expect instead? I expected to see a boot option to start from a partition in the original disk drive. Here is how I worked around the issue. I booted off the netinst DVD into a rescue mode. Ran update-grub and it did not show the Windows partition of the original drive. Inspected the output of os-prober. I believe it did not show Windows either. I then ran fdisk -l and I think I saw my original disk drive with its Windows partition. After inspecting os-prober I figured it depended on the list of mounted partitions. I added the Windows partition to /etc/fstab, /dev/sda1 /c ntfsauto0 0 Unfortunately, "mount /c" failed because the target root partition where I chrooted did not have modules of the rescue kernel. I cannot remember how I succeeded in mounting the partition before re-running update-grub. Perhaps, I returned or rebooted to the dialogs of the rescue mode of Debian Installer and chose to re-configure Grub2 in the dialogs. I could see my Windows partition of the original drive in the bootloader's list at boot time. I could successfully start Windows. Here is my opinion on a possible root cause. It seems that Debian Installer does not attempt to mount partitions on drives other than the one selected for partitioning. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.0.0-1-686-pae (SMP w/2 CPU cores) Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (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#622828: recovery
Contrary to my earlier conclusion, the upgrade did not delete older images. It appears a ramdisk generation change may have included a bad module whose loading crashed the system later. I could not boot other images because my Grub 2 configuration file grub.cfg missed the corresponding "initrd" lines. The latter were missing probably because of a ramdisk generation failure. This resulted in a cryptic error message at the boot failure about inability to find a root filesystem in a certain (0,0) disk. As I mentioned earlier, after loading to a shell prompt by editing the "linux" line in grub boot screen and adding init=/bin/bash, I could disable swapping with swapoff -a, remount the root partition in a read-write mode and start networking. This allowed me to update packages in aptitude. I also had to boot off a recent Debian installer CD-R disk, http://cdimage.debian.org/cdimage/daily-builds/unstable/current/i386/iso-cd/ because I did not understand the reason for the (0,0) root disk mount crash. I also suspect that my manual invocation of update-initramfs failed to include all required modules. In the end, I dropped to shell from the rescue disk, mounted my root filesystem with "mount -t ext3 /dev/sda1 /mnt" and changed to it with "chroot /mnt". I then re-generated the initial ramdisk images with update-initramfs -k 2.6.32-5-686 -d update-initramfs -k 2.6.32-5-686 -c and same commands for some other kernel versions. This allowed me to boot my system in full with 2.6.32-5-686 which turned to be the original kernel version that worked long time for me. (The newer 2.6.38..-686 kernel on which 2.6-686 depends crashes in the Wi-Fi module mac80211 calling a function in cfg80211 when I attempt to associate with my Wi-Fi router. I logged that issue under bug #622833). Still, I do not understand how possible differences in update-initramfs could cause a libata kernel crash. -- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#622828: corrected
Thanks for quashing my hasty conclusion about the timing of the kernel crash. I now see that the crash occurred after the ramdisk stage succeeded. Probably, this may have something to do with memory paging to disk. I could boot to the shell, disable swapping, launch udev, resolvconf, dnsmasq, networking, submit the bug, update packages with aptitude. I could not find a work-around. I cannot remember the version of my last successful image as the upgrade deleted it. Perhaps, I can look up my logs to find the version. My online search showed only the current unstable and stable packages, both of which failed to boot for different reasons. The earlier (oldstable?) package 2.6.26 bailed to a ramdisk shell prompt after failing to run a newer udev daemon. Perhaps, the package information for that earlier image could require a ramdisk make tool and/or ramdisk components relevant to that version. I sent screenshots of the stack trace just before receiving your email requesting them. I see the screen shots in the log of this bug report. Cheers. --
Bug#622833: linux-image-2.6.38-2-686: kernel panic in mac80211
Package: linux-2.6
Version: 2.6.38-3
Severity: critical
Justification: breaks the whole system
Booting panics when bringing interfaces up, including a Wi-Fi adm8211
from drivers/net/wireless. The stack trace mentions
ieee80211_rx_handlers in mac80211, net_receive_skb, do_page_fault,
bad_area_nosemaphore, no_context (from the least to the most recently
called).
I will send screenshots of the trace.
-- Package-specific info:
** Kernel log: boot messages should be attached
** Model information
not available
** Network interface configuration:
auto tp
iface tp inet static
address 192.168.3.1
netmask 255.255.255.0
network 192.168.3.0
broadcast 192.168.3.255
auto wl
iface wl inet static
address 192.168.2.172
netmask 255.255.255.0
network 192.168.2.0
broadcast 192.168.2.255
gateway 192.168.2.1
dns-nameservers 192.168.2.1
wpa-ssid D3
wpa-bsssid 00:21:91:F8:36:6E
wpa-psk *
up sleep 5; /sbin/iwconfig "${IFACE}"
up /sbin/ip route add 224.0.0.0/4 dev "${IFACE}"
iface tun6to4 inet6 v4tunnel
address $(printf "2002:%02x%02x:%02x%02x::1" \
$(printf "%s\r\n%s\r\n\r\n" \
"GET / HTTP/1.1" \
"Host: checkip.dyndns.org" \
| /bin/nc checkip.dyndns.org 80 \
| /bin/sed -ne 's/.*Address: \([.0-9]*\).*/\1/p' \
| tr '.' ' ') \
)
netmask 16
endpoint 192.88.99.1
local any
ttl 64
up /sbin/ip -6 route add 2000::/3 dev tun6to4
down /sbin/ip -6 route flush dev tun6to4
auto lo
iface lo inet loopback
** PCI devices:
00:00.0 Host bridge [0600]: ATI Technologies Inc Radeon Xpress 200 Host Bridge
[1002:5a33] (rev 01)
Subsystem: ASUSTeK Computer Inc. Device [1043:819a]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
SERR- TAbort-
SERR- TAbort-
Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [b0] Subsystem: ATI Technologies Inc RS480 PCI Bridge
[1002:5a3f]
00:05.0 PCI bridge [0604]: ATI Technologies Inc RS480 PCI Bridge [1002:5a37]
(prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR+ TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [50] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] Express (v1) Root Port (Slot-), MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <64ns,
L1 <1us
ExtTag+ RBE- FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal-
Unsupported-
RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr-
TransPend-
LnkCap: Port #2, Speed 2.5GT/s, Width x2, ASPM L0s L1, Latency
L0 <64ns, L1 <1us
ClockPM- Surprise- LLActRep- BwNot-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+
DLActive- BWMgmt- ABWMgmt-
RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna-
CRSVisible-
RootCap: CRSVisible-
RootSta: PME ReqID , PMEStatus- PMEPending-
Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit-
Address: Data:
Capabilities: [b0] Subsystem: ATI Technologies Inc Device [1002:5a33]
Capabilities: [b8] HyperTransport: MSI Mapping Enable+ Fixed+
Capabilities: [100 v1] Advanced Error Reporting
UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt-
RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt-
RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UESvrt: DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt-
RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-
CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-
AERCap: First Error Pointer: 00, GenCap- CGenEn- ChkCap- ChkEn-
Capabilities: [140 v1] Virtual Channel
Caps: LPEVC=0 RefClk=100ns PATEntryBits=1
Bug#622828: linux-image-2.6.32-5-686: kernel panic mentions libata in the stack trace
Package: linux-2.6 Version: 2.6.32-30 Severity: critical Justification: breaks the whole system Both normal and safe boot modes panicked when running the ram disk image. Worse, the upgrade DELETED the earlier kernel image and ram disk image. I managed to boot by editing the safe mode command line and adding the option init=/bin/bash. When the kernel panicks, it shows a stack trace mentioning libata. -- Package-specific info: ** Version: Linux version 2.6.32-5-686 (Debian 2.6.32-30) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Wed Jan 12 04:01:41 UTC 2011 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-686 root=UUID=281d76c7-ee09-4f0e-825b-425e95d75878 ro single init=/bin/bash ** Not tainted ** Kernel log: [3.331507] PM: Checking hibernation image. [3.331689] PM: Error -22 checking image file [3.331692] PM: Resume from disk failed. [3.338369] PM: Marking nosave pages: 0009f000 - 0010 [3.338378] PM: Basic memory bitmaps created [3.345712] PM: Basic memory bitmaps freed [3.372024] usb 2-1: new full speed USB device using ohci_hcd and address 2 [3.401886] kjournald starting. Commit interval 5 seconds [3.401897] EXT3-fs: mounted filesystem with ordered data mode. [3.568751] usb 2-1: New USB device found, idVendor=03f0, idProduct=0517 [3.568808] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [3.568857] usb 2-1: Product: hp LaserJet 1000 [3.568903] usb 2-1: Manufacturer: Hewlett-Packard [3.569118] usb 2-1: configuration #1 chosen from 1 choice [7.505287] usb-storage: device scan complete [7.506404] scsi 6:0:0:0: Direct-Access RIM BlackBerry SD0003 PQ: 0 ANSI: 4 CCS [7.507080] sd 6:0:0:0: Attached scsi generic sg2 type 0 [7.508515] sd 6:0:0:0: [sdb] Attached SCSI removable disk [ 184.561988] EXT3 FS on sda1, internal journal [ 1241.810372] <30>udev[382]: starting version 167 [ 1242.505471] <30>udev[405]: renamed network interface eth0 to tp [ 1243.710686] input: PC Speaker as /devices/platform/pcspkr/input/input2 [ 1244.157244] pci_hotplug: PCI Hot Plug PCI Core version: 0.5 [ 1244.250681] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input3 [ 1244.250866] ACPI: Power Button [PWRB] [ 1244.251036] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4 [ 1244.251271] ACPI: Power Button [PWRF] [ 1244.613408] processor LNXCPU:00: registered as cooling_device0 [ 1244.614971] processor LNXCPU:01: registered as cooling_device1 [ 1244.619420] usblp0: USB Bidirectional printer dev 2 if 0 alt 0 proto 2 vid 0x03F0 pid 0x0517 [ 1244.619503] usbcore: registered new interface driver usblp [ 1244.625601] parport_pc 00:06: reported by Plug and Play ACPI [ 1244.627407] parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE] [ 1244.639042] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 [ 1245.015484] ali1535_smbus :00:1e.1: ALI1535_smb region uninitialized - upgrade BIOS? [ 1245.015576] ali1535_smbus :00:1e.1: ALI1535 not detected, module not inserted. [ 1245.025103] ali15x3_smbus :00:1e.1: ALI15X3_smb region uninitialized - upgrade BIOS or use force_addr=0xaddr [ 1245.025165] ali15x3_smbus :00:1e.1: ALI15X3 not detected, module not inserted. [ 1245.089649] alim7101_wdt: Steve Hill . [ 1245.089710] alim7101_wdt: ALi 1543 South-Bridge not present - WDT not set [ 1245.404977] cfg80211: Using static regulatory domain info [ 1245.405031] cfg80211: Regulatory domain: US [ 1245.405076] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 1245.405130] (2402000 KHz - 2472000 KHz @ 4 KHz), (600 mBi, 2700 mBm) [ 1245.405178] (517 KHz - 519 KHz @ 4 KHz), (600 mBi, 2300 mBm) [ 1245.405226] (519 KHz - 521 KHz @ 4 KHz), (600 mBi, 2300 mBm) [ 1245.405274] (521 KHz - 523 KHz @ 4 KHz), (600 mBi, 2300 mBm) [ 1245.405322] (523 KHz - 533 KHz @ 4 KHz), (600 mBi, 2300 mBm) [ 1245.405369] (5735000 KHz - 5835000 KHz @ 4 KHz), (600 mBi, 3000 mBm) [ 1245.405922] cfg80211: Calling CRDA for country: US [ 1245.609148] adm8211 :03:11.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18 [ 1245.619583] :03:11.0 (adm8211): Channel range: 1 - 11 [ 1245.619588] :03:11.0 (adm8211): RFtype=1 BBPtype=1 Specific BBP=0 Transceiver=0 [ 1246.177701] phy0: Selected rate control algorithm 'minstrel' [ 1246.178756] phy0: hwaddr 00:04:e2:7b:70:6b, Rev 0x11 [ 1246.189113] <30>udev[403]: renamed network interface wlan0 to wl [ 1246.938086] HDA Intel :00:1d.0: PCI INT C -> GSI 22 (level, low) -> IRQ 22 [ 1246.938155] hda_intel: position_fix set to 1 for device 1043:81b3 [ 1247.383775] input: HDA Digital PCBeep as /devices/pci:00/:00:1d.0/input/input5 [ 1252.897954] usblp0: removed [ 1323.238716] r8169: tp: link down [ 1323.238987] ADDRCONF(NETDEV_UP): tp: link is not ready [ 1332.520717] ADDRCONF(NETDEV_UP): wl: link is not ready [ 1334.724
Bug#579340: [CRASH] Uncaught exception AttributeError in Frontend/Gtk/ui.py:616
Package: update-manager-gnome
Version: 0.200.3-1
Severity: grave
File: /usr/share/pyshared/UpdateManager/Frontend/Gtk/ui.py
Tags: sid
Justification: renders package unusable
Update Manager crashed on its start.
*** /tmp/update-manager-bugm_Su6p
The information below has been automatically generated.
Please do not remove this from your bug report.
- Exception Type:
- Exception Value: AttributeError("'GtkUI' object has no attribute
'treeview_update'",)
- Exception Origin: <_MainThread(MainThread, started)>
- Exception Traceback:
File "/usr/bin/update-manager", line 38, in
app.main()
File "/usr/lib/pymodules/python2.5/UpdateManager/Application.py", line 421,
in main
self._frontend.init_frontend()
File "/usr/lib/pymodules/python2.5/UpdateManager/Frontend/Gtk/__init__.py",
line 70, in init_frontend
self._ui = GtkUI(self)
File "/usr/lib/pymodules/python2.5/UpdateManager/Frontend/Gtk/ui.py", line
616, in __init__
self.update_list = UpdateListControl(self, self.treeview_update)
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-3-686 (SMP w/2 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages update-manager-gnome depends on:
ii gconf22.28.1-3 GNOME configuration database syste
ii gksu 2.0.2-2+b1 graphical frontend to su
ii python2.5.4-9An interactive high-level object-o
ii python-dbus 0.83.1-1 simple interprocess messaging syst
ii python-gconf 2.28.1-1 Python bindings for the GConf conf
ii python-gobject2.21.1-1 Python bindings for the GObject li
ii python-gtk2 2.17.0-2 Python bindings for the GTK+ widge
ii python-support1.0.8 automated rebuilding support for P
ii python-vte1:0.24.0-2 Python bindings for the VTE widget
ii update-manager-core 0.200.3-1 APT update manager core functional
update-manager-gnome recommends no packages.
Versions of packages update-manager-gnome suggests:
ii software-properties-gtk 0.60.debian-1.1 manage the repositories that you i
ii update-notifier 0.99.3debian3 Daemon which notifies about packag
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#578296: git-core: "ValueError: too many values to unpack"
> Thanks for the proposed patch. Anyhow, the right solution is to simply > ignore that extra value in the module that parses them [..] > conffiles = conffiles + [tuple(line.split()[:2])] Nice. Thanks, Sandro. -- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#578296: git-core: "ValueError: too many values to unpack"
Package: reportbug
Version: 4.12
Severity: normal
This appears to be a result of an extra word "obsolete" in addition to
filename and md5sum fields of a conffiles record. Reproduced when
reporting on python2.5-minimal.
=
il...@ei:~$ dpkg --status python2.5-minimal
Package: python2.5-minimal
Status: install ok installed
Priority: optional
Section: python
Installed-Size: 4316
Maintainer: Matthias Klose
Architecture: i386
Source: python2.5
Version: 2.5.5-5
Replaces: python2.5 (<< 2.5.2-1)
Depends: libc6 (>= 2.3.6-6~), zlib1g (>= 1:1.2.0)
Recommends: python2.5
Suggests: binfmt-support
Conflicts: binfmt-support (<< 1.1.2)
Conffiles:
/etc/python2.5/sitecustomize.py d6b276695157bde06a56ba1b2bc53670
/etc/python2.5/site.py f10d07f5be789964fff663e2dfe560f9 obsolete
Description: A minimal subset of the Python language (version 2.5)
This package contains the interpreter and some essential modules. It can
be used in the boot process for some basic tasks.
See /usr/share/doc/python2.5-minimal/README.Debian for a list of the modules
contained in this package.
Homepage: http://python.org/
Python-Runtime: python2.5
Python-Version: 2.5
=
I wonder if ignoring any extra information in conffiles records addresses the
root cause properly. Here is the change I am suggesting.
=
--- /usr/share/pyshared/reportbug/utils.py.orig 2010-04-21 05:58:15.0
-0400
+++ /usr/share/pyshared/reportbug/utils.py 2010-04-21 05:56:05.0 -0400
@@ -641,7 +641,9 @@
def get_changed_config_files(conffiles, nocompress=False):
confinfo = {}
changed = []
-for (filename, md5sum) in conffiles:
+for cf in conffiles:
+filename = cf[ 0 ]
+md5sum = cf[ 1 ]
try:
fp = file(filename)
except IOError, msg:
=
-- Package-specific info:
** Environment settings:
EDITOR="vi"
INTERFACE="text"
** /home/ilgiz/.reportbugrc:
reportbug_version "3.21.2"
mode standard
ui text
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-2-686 (SMP w/2 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages reportbug depends on:
ii apt 0.7.25.3 Advanced front-end for dpkg
ii python2.5.4-9An interactive high-level object-o
ii python-reportbug 4.12 Python modules for interacting wit
reportbug recommends no packages.
Versions of packages reportbug suggests:
ii debconf-utils1.5.32 debconf utilities
pn debsums(no description available)
pn dlocate(no description available)
ii emacs23-bin-common 23.1+1-6The GNU Emacs editor's shared, arc
ii exim44.71-4 metapackage to ease Exim MTA (v4)
ii exim4-daemon-heavy [ 4.71-4 Exim MTA (v4) daemon with extended
ii file 5.04-2 Determines file type using "magic"
ii gnupg1.4.10-3GNU privacy guard - a free PGP rep
ii python-gtk2 2.17.0-2Python bindings for the GTK+ widge
pn python-gtkspell(no description available)
pn python-urwid (no description available)
ii python-vte 1:0.24.0-2 Python bindings for the VTE widget
ii xdg-utils1.0.2+cvs20100307-1 desktop integration utilities from
-- 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#578596: Fails to install, variable used before assignment
Package: python2.5-minimal Version: 2.5.5-5 Severity: normal I wonder if this can be fixed with the following change, --- /usr/lib/python2.5/py_compile.py.orig 2010-04-21 06:00:38.0 -0400 +++ /usr/lib/python2.5/py_compile.py2010-04-21 05:46:52.0 -0400 @@ -153,6 +153,7 @@ files is taken from standard input. """ +rv = 0 if args is None: args = sys.argv[1:] if args == ['-']: -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.32-2-686 (SMP w/2 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages python2.5-minimal depends on: ii libc6 2.10.2-6 Embedded GNU C Library: Shared lib ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime Versions of packages python2.5-minimal recommends: ii python2.5 2.5.5-5An interactive high-level object-o Versions of packages python2.5-minimal suggests: ii binfmt-support1.2.18 Support for extra binary formats -- 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#549094: wodim: OPC failed; logical block address out of range
Package: wodim
Version: 9:1.1.10-1
Severity: normal
Forgot to add the dmesg output that might be related. Also, I just realized
that the "sense code" error message was "logical block address out of range".
[ 4469.846681] hdb: command error: status=0x51 { DriveReady SeekComplete Error }
[ 4469.846694] hdb: command error: error=0x54 { AbortedCommand
LastFailedSense=0x05 }
[ 4469.846702] hdb: possibly failed opcode: 0xa0
[ 4469.849215] end_request: I/O error, dev hdb, sector 0
[ 4469.849221] Buffer I/O error on device hdb, logical block 0
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-2-686 (SMP w/2 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages wodim depends on:
ii libc6 2.10.2-5 Embedded GNU C Library: Shared lib
ii libcap2 1:2.17-2 support for getting/setting POSIX.
Versions of packages wodim recommends:
ii genisoimage 9:1.1.10-1 Creates ISO-9660 CD-ROM filesystem
Versions of packages wodim suggests:
ii cdrkit-doc9:1.1.10-1 Documentation for the cdrkit packa
-- 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#549094: wodim: intermittent CHECK CONDITION followed by fixating
Package: wodim
Version: 9:1.1.10-1
Severity: normal
Perhaps, my issue is related. I am getting intermittent "no error"
errors displaying "status: 0x02 (CHECK_CONDITION)".
I suspect that an extra "resid: 28" in addition to a regular "resid: 8" is an
early indicator of the trouble.
As a result, the blank DVD-R disk gets its session closed and I cannot
use it for my single-session burning.
I am including a failure log. After making a "coaster" of 2 blank
disks, I then got the burning succeed. I include the log of the
successful cdrecord invocation after the failure log. I think both
wodim and cdrecord suffer from the intermittent failure I am describing.
===
il...@ei:~/download$ sudo wodim -v ${DISK_NAME}.iso
wodim: No write mode specified.
wodim: Assuming -tao mode.
wodim: Future versions of wodim may have different drive dependent defaults.
TOC Type: 1 = CD-ROM
Device was not specified. Trying to find an appropriate drive...
Looking for a DVD-R drive to store 4267.57 MiB...
Detected DVD-R drive: /dev/hdb
scsidev: '/dev/hdb'
devname: '/dev/hdb'
scsibus: -2 target: -2 lun: -2
Linux sg driver version: 3.5.27
Wodim version: 1.1.10
SCSI buffer size: 64512
Device type: Removable CD-ROM
Version: 0
Response Format: 2
Capabilities :
Vendor_info: 'HL-DT-ST'
Identification : 'DVDRAM GSA-H10A '
Revision : 'JL03'
Device seems to be: Generic mmc2 DVD-R/DVD-RW.
Current: 0x0011 (DVD-R sequential recording)
Profile: 0x0012 (DVD-RAM)
Profile: 0x0011 (DVD-R sequential recording) (current)
Profile: 0x0015 (DVD-R/DL sequential recording)
Profile: 0x0016 (DVD-R/DL layer jump recording)
Profile: 0x0014 (DVD-RW sequential recording)
Profile: 0x0013 (DVD-RW restricted overwrite)
Profile: 0x001A (DVD+RW)
Profile: 0x001B (DVD+R)
Profile: 0x002B (DVD+R/DL)
Profile: 0x0010 (DVD-ROM)
Profile: 0x0009 (CD-R)
Profile: 0x000A (CD-RW)
Profile: 0x0008 (CD-ROM)
Profile: 0x0002 (Removable disk)
Using generic SCSI-3/mmc DVD-R(W) driver (mmc_mdvd).
Driver flags : SWABAUDIO BURNFREE
Supported modes: PACKET SAO
Drive buf size : 1114112 = 1088 KB
Beginning DMA speed test. Set CDR_NODMATEST environment variable if device
communication breaks or freezes immediately after that.
Drive DMA Speed: 14562 kB/s 82x CD 10x DVD
FIFO size : 12582912 = 12288 KB
Track 01: data 4267 MB
Total size: 4901 MB (485:33.25) = 2184994 sectors
Lout start: 4901 MB (485:35/19) = 2184994 sectors
Current Secsize: 2048
HINT: use dvd+rw-mediainfo from dvd+rw-tools for information extraction.
Blocks total: 2298496 Blocks current: 2298496 Blocks remaining: 113502
Speed set to 22160 KB/s
Starting to write CD/DVD at speed 17.0 in real unknown mode for single session.
Last chance to quit, starting real write in0 seconds. Operation starts.
Waiting for reader process to fill input buffer ... input buffer ready.
Performing OPC...
resid: 8
resid: 28
Starting new track at sector: 825831473
Track 01:0 of 4267 MB written.Errno: 0 (Success), write_g1 scsi sendcmd: no
error
CDB: 2A 00 31 39 30 31 00 00 1F 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: F0 00 05 31 39 30 31 10 2A 00 00 0C 21 00 00 00
Sense Key: 0x5 Illegal Request, Segment 0
Sense Code: 0x21 Qual 0x00 (logical block address out of range) Fru 0x0
Sense flags: Blk 825831473 (valid)
resid: 63488
cmd finished after 0.008s timeout 40s
write track data: error after 0 bytes
wodim: The current problem looks like a buffer underrun.
wodim: Try to use 'driveropts=burnfree'.
wodim: Make sure that you are root, enable DMA and check your HW/OS set up.
Writing time: 82.650s
Average write speed 111.0x.
Fixating...
Fixating time:5.964s
wodim: fifo had 192 puts and 1 gets.
wodim: fifo was 0 times empty and 0 times full, min fill was 100%.
===
il...@ei:~/download$ sudo cdrecord -vvv -tao ${DISK_NAME}.iso
TOC Type: 1 = CD-ROM
Device was not specified. Trying to find an appropriate drive...
Looking for a DVD-R drive to store 4267.57 MiB...
Detected DVD-R drive: /dev/hdb
scsidev: '/dev/hdb'
devname: '/dev/hdb'
scsibus: -2 target: -2 lun: -2
Linux sg driver version: 3.5.27
Wodim version: 1.1.10
Using libusal version 'Cdrkit-1.1.10'.
SCSI buffer size: 64512
Device type: Removable CD-ROM
Version: 0
Response Format: 2
Capabilities :
Vendor_info: 'HL-DT-ST'
Identification : 'DVDRAM GSA-H10A '
Revision : 'JL03'
Device seems to be: Generic mmc2 DVD-R/DVD-RW.
Current: 0x0011 (DVD-R sequential recording)
Profile: 0x0012 (DVD-RAM)
Profile: 0x0011 (DVD-R sequential recording) (current)
Profile: 0x0015 (DVD-R/DL sequential recording)
Profile: 0x0016 (DVD-R/DL layer jump recording)
Profile: 0x0014 (DVD-RW sequential recording)
Profile: 0x0013 (DVD-RW restricted overwrite)
Profile: 0x001A (DVD+RW)
Profile: 0x001B (DVD+R)
Profile: 0x002B (DVD+R/DL)
Profile: 0x0010 (DVD-ROM)
Profile: 0
Bug#508299: see also
See also bug 511633. -- I. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#396194: my mistake
On Mon, Apr 16, 2007 at 01:51:05AM -0400, Ilguiz Latypov wrote: > My report on wodim failure could be a result of my own liberal > application of hdparm. I am mistaken again, so my former report on the failure in wodim remains in force. I found that wodim still produced blank DVDs even after I removed hdparm.conf and rebooted. -- Ilguiz Latypov. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#396194: my mistake
My report on wodim failure could be a result of my own liberal
application of hdparm. Few days later I removed /etc/hdparm.conf,
rebooted the machine and found wodim working just fine.
The hdparm options that failed my system are included below. My
DVD writer is /dev/hdb. Regards,
--
Ilguiz Latypov.
--- hdparm.conf.dpkg-dist 2006-10-25 11:25:31.0 -0400
+++ hdparm.conf.fails-dvd-wodim-write 2006-07-27 22:00:57.0 -0400
@@ -30,7 +30,7 @@
## outside of a block and all options defined with in the block.
# -q be quiet
-quiet
+# quiet
# -a sector count for filesystem read-ahead
#read_ahead_sect = 12
# -A disable/enable the IDE drive's read-lookahead feature
@@ -40,33 +40,31 @@
# -B apm setting
#apm = 255
# -c enable (E)IDE 32-bit I/O support - can be any of 0,1,3
-#io32_support = 1
+io32_support = 1
# -d disable/enable the "using_dma" flag for this drive
-#dma = off
+dma = on
# -D enable/disable the on-drive defect management
#defect_mana = off
# -E cdrom speed
-#cd_speed = 16
+cd_speed = 66
# -k disable/enable the "keep_settings_over_reset" flag for this drive
#keep_settings_over_reset = off
# -K disable/enable the drive's "keep_features_over_reset" flag
#keep_features_over_reset = on
# -m sector count for multiple sector I/O
-#mult_sect_io = 32
+mult_sect_io = 32
# -P maximum sector count for the drive's internal prefetch mechanism
#prefetch_sect = 12
# -r read-only flag for device
#read_only = off
-# -s Turn on/off power on in standby mode
-#poweron_standby = off
# -S standby (spindown) timeout for the drive
#spindown_time = 24
# -u interrupt-unmask flag for the drive
-#interrupt_unmask = on
+interrupt_unmask = on
# -W Disable/enable the IDE drive's write-caching feature
#write_cache = off
# -X IDE transfer mode for newer (E)IDE/ATA2 drives
-#transfer_mode = 34
+# transfer_mode = 34
# -y force to immediately enter the standby mode
#standby
# -Y force to immediately enter the sleep mode
@@ -135,3 +133,6 @@
#command_line {
# hdparm -q -m16 -q -W0 -q -d1 /dev/hda
#}
+
+/dev/hdb {
+}
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#396194: and the other burning tool worked
The other DVD-burn command produced a working disk with the same ISO image. $ genisoimage -dvd-video -o /dev/dvdrw bv.iso -- Ilguiz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#396194: wodim: another failure with Hyundai DVD+R
Package: wodim Version: 9:1.1.4-1 Followup-For: Bug #396194 I have a similar problem here. I created the ISO image with vobcopy 0.5.14 dvdauthor 0.6.14 genisoimage 1.1.4 $ mkdir vobs $ vobcopy -o vobs $ mkdir dvd $ dvdauthor -o dvd -t vobs/*.vob $ dvdauthor -o dvd -T $ genisoimage -dvd-video -o bv.iso dvd/ I had only 2 VOBs of total size around 3 GB. [EMAIL PROTECTED]:~/download$ wodim -v bv.iso wodim: No write mode specified. wodim: Asuming -tao mode. wodim: Future versions of wodim may have different drive dependent defaults. INFO: no device specified, looking for a DVD-R drive to store 2691.79 MiB... Detected DVD-R drive: /dev/dvdrw TOC Type: 1 = CD-ROM scsidev: '/dev/dvdrw' devname: '/dev/dvdrw' scsibus: -2 target: -2 lun: -2 Linux sg driver version: 3.5.27 Wodim version: 1.1.4 SCSI buffer size: 64512 atapi: 1 Device type: Removable CD-ROM Version: 0 Response Format: 2 Capabilities : Vendor_info: 'HL-DT-ST' Identification : 'DVDRAM GSA-H10A ' Revision : 'JL03' Device seems to be: Generic mmc2 DVD-R/DVD-RW. Current: 0x001B (DVD+R) Profile: 0x0012 (DVD-RAM) Profile: 0x0011 (DVD-R sequential recording) Profile: 0x0015 (DVD-R/DL sequential recording) Profile: 0x0016 (DVD-R/DL layer jump recording) Profile: 0x0014 (DVD-RW sequential recording) Profile: 0x0013 (DVD-RW restricted overwrite) Profile: 0x001A (DVD+RW) Profile: 0x001B (DVD+R) (current) Profile: 0x002B (DVD+R/DL) Profile: 0x0010 (DVD-ROM) Profile: 0x0009 (CD-R) Profile: 0x000A (CD-RW) Profile: 0x0008 (CD-ROM) Profile: 0x0002 (Removable disk) Using generic SCSI-3/mmc DVD-R(W) driver (mmc_mdvd). Driver flags : SWABAUDIO BURNFREE Supported modes: PACKET SAO Drive buf size : 1114112 = 1088 KB Beginning DMA speed test. Set CDR_NODMATEST environment variable if device communication breaks or freezes immediately after that. Drive DMA Speed: 13993 kB/s 79x CD 10x DVD FIFO size : 12582912 = 12288 KB Track 01: data 2691 MB Total size: 3091 MB (306:15.94) = 1378196 sectors Lout start: 3091 MB (306:17/71) = 1378196 sectors Current Secsize: 2048 ATIP start of lead in: -150 (00:00/00) ATIP start of lead out: 157789 (35:05/64) Disk type:unknown dye (reserved id code) Manuf. index: -1 Manufacturer: unknown (not in table) Blocks total: 2295104 Blocks current: 2295104 Blocks remaining: 916908 Speed set to 11080 KB/s Starting to write CD/DVD at speed 8.0 in real unknown mode for single session.Last chance to quit, starting real write0 seconds. Operation starts. Waiting for reader process to fill input buffer ... input buffer ready. Performing OPC... Starting new track at sector: 0 Track 01: 2691 of 2691 MB written (fifo 100%) [buf 94%] 8.3x. Track 01: Total bytes read/written: 2822545408/2822545408 (1378196 sectors). Writing time: 290.205s Average write speed 7.3x. Min drive buffer fill was 94% Fixating... Errno: 0 (Success), close track/session scsi sendcmd: no error CDB: 5B 00 02 00 00 00 00 00 00 00 status: 0x2 (CHECK CONDITION) Sense Bytes: 70 00 02 00 00 00 00 10 00 00 00 0E 04 08 00 80 Sense Key: 0x2 Not Ready, Segment 0 Sense Code: 0x04 Qual 0x08 (logical unit not ready, long write in progress) Fru 0x0 Sense flags: Blk 0 (not valid) operation 0% done cmd finished after 0.002s timeout 1000s Fixating time:0.108s wodim: fifo had 44458 puts and 44458 gets. wodim: fifo was 0 times empty and 8757 times full, min fill was 94%. [EMAIL PROTECTED]:~/download$ mount /media/cdrom0 mount: block device /dev/hdb is write-protected, mounting read-only mount: wrong fs type, bad option, bad superblock on /dev/hdb, missing codepage or other error In some cases useful info is found in syslog - try dmesg | tail or so [EMAIL PROTECTED]:~/download$ dmesg cdrom: This disc doesn't have any tracks I recognize! attempt to access beyond end of device hdb: rw=0, want=68, limit=4 isofs_fill_super: bread failed, dev=hdb, iso_blknum=16, block=16 -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-686 Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Versions of packages wodim depends on: ii libc6 2.3.6.ds1-13 GNU C Library: Shared libraries ii libcap1 1:1.10-14support for getting/setting POSIX. Versions of packages wodim recommends: ii genisoimage 9:1.1.4-1 Creates ISO-9660 CD-ROM filesystem -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#418108: python-central: a guess on fixing the bug
Package: python-central
Version: 0.5.13
Followup-For: Bug #418108
I am guessing that the fix to the problem can be as simple as adding a
line "global config" under "global _defaults" in the failed script:
--- /usr/share/pycentral-data/pyversions.py.orig2007-04-06
23:23:10.0 -0400
+++ /usr/share/pycentral-data/pyversions.py 2007-04-06 23:21:12.0
-0400
@@ -11,6 +11,7 @@
_defaults = None
def read_default(name=None):
global _defaults
+global config
from ConfigParser import SafeConfigParser, NoOptionError
if not _defaults:
if os.path.exists('/usr/share/python/debian_defaults'):
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-3-686
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Versions of packages python-central depends on:
ii python2.4.4-2An interactive high-level object-o
python-central recommends no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#415968: another work-around
Here is another work-around to setting stdout's encoding. > import sys, codecs, locale > > if sys.stdout.encoding is None: > (lang, enc) = locale.getdefaultlocale() > if enc is not None: > (e, d, sr, sw) = codecs.lookup(enc) > # sw will encode Unicode data to the locale-specific character set. > sys.stdout = sw(sys.stdout) Found the missing tid-bit in the Marc-Andre Lemburg's tutorial, > http://mail.python.org/pipermail/i18n-sig/2000-April/66.html -- Ilguiz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#376055: x11-common: dexconf ignores mouse port and protocol selections
Package: x11-common Version: 1:7.0.22 Severity: important Tags: patch Trying to figure why my choice of ImPS/2 isn't stored in xorg.conf, I found that dexconf ignored it. Here is the patch. === --- dexconf.orig2006-06-11 23:40:18.0 -0400 +++ dexconf 2006-06-28 14:22:54.0 -0400 @@ -287,8 +287,8 @@ Identifier "Configured Mouse" Driver "mouse" Option "CorePointer" - Option "Device""/dev/input/mice" - Option "Protocol" "ExplorerPS/2" + Option "Device""$MOUSE_PORT" + Option "Protocol" "$MOUSE_PROTOCOL" SECTION if [ -n "$DO_EMULATE3BUTTONS" ]; then printf "\tOption\t\t\"Emulate3Buttons\"\t\"true\"\n" >&4 === -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-1-686 Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Versions of packages x11-common depends on: ii debconf [debconf-2.0] 1.5.2 Debian configuration management sy ii debianutils 2.16.1 Miscellaneous utilities specific t ii lsb-base 3.1-10 Linux Standard Base 3.1 init scrip x11-common recommends no packages. -- debconf information: x11-common/xwrapper/nice_value: 0 x11-common/xwrapper/allowed_users: Console Users Only x11-common/xwrapper/actual_allowed_users: console x11-common/xwrapper/nice_value/error: x11-common/x11r6_bin_not_empty: * x11-common/upgrade_issues: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#345374: [Yaird-devel] Bug#345374: yaird: via82cxxx
Jonas, On Thu, Jun 29, 2006 at 12:19:45PM +0200, Jonas Smedegaard wrote: > Which kernel package do you use? Is it an official Debian-packaged one? 2.6.17. I am running Debian unstable. The package was retrieved through the regular Debian mechanism (apt-get from debian.yorku.ca). > And what kernel did you use before that? I am asking because I suspect > there can be a corner-case of including from modules if switching from a > kernel with broken sysfs-support to one that is working. I believe it was 2.6.16. The issue with via82cxxx loading after ide_generic must have been lingering for a long time (since 2.6.14 or earlier). > did you read the current text in that file about older official Debian > kernels? >From what I understood, the current note was about ide_generic not being loaded by the most recent kernels. The work-around suggested in the note is quite opposite to my observations, but I didn't go into inner workings of the ram disk to find the exact mechanism of discovering required modules. -- Ilguiz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#345374: yaird: via82cxxx
Package: yaird Version: 0.0.12-14 Followup-For: Bug #345374 Same problem here with via82cxxx not being included into /init. As a work-around, I modified /etc/yaird/Default.cfg to include the chipset-specific IDE driver unconditionally in the prologue: === --- Default.cfg.orig2006-06-29 04:20:02.0 -0400 +++ Default.cfg 2006-06-29 04:00:03.0 -0400 @@ -54,6 +54,7 @@ # If there is a framebuffer module, make it operational # as soon as possible, so that you can see error messages. OPTIONAL MODULE fbcon + MODULE via82cxxx # # INPUT -- Insert all modules needed for keyboard === Perhaps, one can at least provide this or similar work-around in NEWS.Debian.gz before the correct (sysfs-based?) solution is found. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (800, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-1-k7 Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R) Versions of packages yaird depends on: ii cpio 2.6-13 GNU cpio -- a program to manage ar ii dash 0.5.3-3 The Debian Almquist Shell ii libc62.3.6-15GNU C Library: Shared libraries ii libhtml-template-perl2.8-1 HTML::Template : A module for usin ii libparse-recdescent-perl 1.94.free-3 Generates recursive-descent parser ii perl 5.8.8-6 Larry Wall's Practical Extraction yaird recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#226180: x11-common: readline prompts are enabled by a separate package
Package: x11-common Version: 1:7.0.22 Followup-For: Bug #226180 It occured to me that the readline mode of Debian configurator, DEBCONF_FRONTEND=readline dpkg-reconfigure will show default prompts when libterm-readline-gnu-perl is installed. This was suggested by debconf(7) from debconf-doc. The auxiliary readline package is already automatically suggested by the debconf package. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-486 Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Versions of packages x11-common depends on: ii debconf [debconf-2.0] 1.5.2 Debian configuration management sy ii debianutils 2.16.1 Miscellaneous utilities specific t ii lsb-base 3.1-10 Linux Standard Base 3.1 init scrip x11-common recommends no packages. -- debconf information: x11-common/xwrapper/nice_value: 0 x11-common/xwrapper/allowed_users: Console Users Only x11-common/xwrapper/actual_allowed_users: console x11-common/xwrapper/nice_value/error: x11-common/x11r6_bin_not_empty: * x11-common/upgrade_issues: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#342160: initscripts: checkroot.sh ignores fsck result
Package: initscripts Version: 2.86.ds1-6 Severity: normal Tags: patch The /etc/init.d/checkroot.sh script ignored the fsck's "PLEASE REBOOT LINUX NOW" exit code because the code is stored too late. As a result, the fixes fsck made to my filesystem could be corrupted again because the system didn't reboot immediately. Besides, the if/then/else/fi statement's syntax was messed up. Surprisingly, it was still valid according to "sh -n". Here is the suggested patch. --- checkroot.sh.orig 2005-11-19 06:40:50.0 -0500 +++ checkroot.sh2005-12-05 16:35:34.0 -0500 @@ -249,12 +249,13 @@ fi log_action_msg "Will now check root file system" fsck $spinner $force $fix -T -t $roottype $rootdev - if [ "$?" = 0 ] - log_success_msg "Done checking root file system" + FSCKCODE=$? + if [ "$FSCKCODE" = 0 ] then + log_success_msg "Done checking root file system" + else log_failure_msg "Done checking root file system" fi - FSCKCODE=$? fi # -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (800, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.14-2-k7 Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R) Versions of packages initscripts depends on: ii coreutils5.93-5 The GNU core utilities ii dpkg 1.13.11.0.1 package maintenance system for Deb ii e2fsprogs1.38-2 ext2 file system utilities and lib ii libc62.3.5-8.1 GNU C Library: Shared libraries an ii lsb-base 3.0-11 Linux Standard Base 3.0 init scrip ii util-linux 2.12p-8 Miscellaneous system utilities initscripts recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#277298: a fix to hwclock*.sh init scripts
The problem with /dev/rtc on Dell machines will cause an erroneous assumption about the current time in the scripts /etc/init.d/hwclock*. To fix that, add the line HWCLOCKPARS=--directisa to /etc/default/rcS. Make sure that every invokation of hwclock in /etc/init.d/hwclock* contains $HWCLOCKPARS. Without the above fix, the hwclock* scripts will assume that the system time was updated from the hardware clock and that the hardware clock is UTC-based. Then the scripts will apply a timezone shift. This will make the current system time shifted incorrectly. -- Ilguiz Latypov programmer at DiskStream Waterloo, Ontario, Canada -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#264603: postgresql-dev: I concur.
Package: postgresql-dev Version: 7.4.7-3 Followup-For: Bug #264603 It would be nice to get the recent 8.0 stable branch of the PostgresQL client library (currently provided by the postgresql-dev package) because the upstream fixed a bug in the error reporting code: http://developer.postgresql.org/cvsweb.cgi/pgsql/src/port/thread.c.diff?r1=1.20;r2=1.21 The strerror_r() function doesn't necessarily fill the buffer with the error message. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.11-rc3-bk2-p4-sata Locale: LANG=en_CA, LC_CTYPE=en_CA (charmap=ISO-8859-1) Versions of packages postgresql-dev depends on: ii libpq37.4.7-3PostgreSQL C client library ii libssl-dev0.9.7e-3 SSL development libraries, header -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#277640: libnss-ldap links against a non-reentrant version of the OpenLDAP library
Package: libnss-ldap Version: 220-1 Followup-For: Bug #277640 The stall happens because libnss-ldap is linked against the non-reentrant version of the OpenLDAP library. This causes an application's call to gethostbyname() to lock up because another call to gethostbyname() occurs within the non-reentrant version of the OpenLDAP library. The non-reentrant version of the OpenLDAP library intentionally avoids using the reentrant functions such as gethostbyname_r() even though they are available in the C library. I believe libnss_ldap should link against the reentrant version of the OpenLDAP library libldap_r.so.2 rather than against the non-reentrant one libldap.so.2. My simple test setting a symlink to the former and using LD_LIBRARY_PATH showed that the stall disappeared. = [EMAIL PROTECTED]:~$ su - # LD_LIBRARY_PATH will work only for root Password: ibis:~# getent hosts 127.0.0.1 localhost.localdomain localhost 10.1.0.1eivpn 10.1.0.2ibisvpn ibis:~# LD_LIBRARY_PATH=/home/ilatypov/openldap/pkg/ldap/libraries/libldap_r/.libs getent hosts 127.0.0.1 localhost.localdomain localhost 10.1.0.1eivpn 10.1.0.2ibisvpn 127.0.0.1 localhost.localdomain localhost 172.16.10.10bigbird.dsrd bigbird ldap perforce snap-ds 172.16.10.14ibis.dsrd ibis 172.16.10.15kingfisher.dsrd kingfisher 172.16.10.21kakadu.dsrd kakadu ibis:~# = A similar stall occured in /bin/ping even when I added the LDAP server's and the local host's IP addresses to /etc/hosts. This was due to the OpenLDAP's library wanting to figure out the IP address of gethostname(). Again, a recursive call to gethostbyname() in the OpenLDAP's non-reentrant library caused a stall. Thanks, -- Ilguiz -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.11-rc3-bk2-p4-sata Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages libnss-ldap depends on: ii debconf 1.4.45 Debian configuration management sy ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an ii libdb4.24.2.52-18Berkeley v4.2 Database Libraries [ ii libkrb531.3.6-1 MIT Kerberos runtime libraries ii libldap22.1.30-3 OpenLDAP libraries -- debconf information: * libnss-ldap/dblogin: false libnss-ldap/override: true * shared/ldapns/base-dn: dc=diskstream,dc=com * shared/ldapns/ldap-server: 172.16.10.10 * libnss-ldap/confperm: false * shared/ldapns/ldap_version: 3 libnss-ldap/binddn: cn=proxyuser,dc=example,dc=net * libnss-ldap/nsswitch: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
