Bug#848029: chromium: v55 security upgrade broke Pulseaudio support on jessie
Package: chromium Version: 55.0.2883.75-1~deb8u1 Severity: important Dear Maintainer, After upgrading from 53.0.2785.89-1~deb8u1 to 55.0.2883.75-1~deb8u1, Chromium is unable to properly use Pulseaudio. When I open a website with audio (a YouTube video for example), Chromium starts opening and closing 'ALSA Playback'-sinks at very rapid rate (thousands of times per minute). This makes audio extremely degraded and causes some noticeable CPU load. Downgrading back to to v53 immediately fixes the problem. I'm using jessies Pulseaudio 5.0-13 with default settings in a plasma-desktop 4 desktop environment. % cat .asoundrc pcm.pulse { type pulse hint.description "Default Audio Device" } ctl.pulse { type pulse } pcm.default pulse ctl.default pulse -- System Information: Debian Release: 8.6 APT prefers stable APT policy: (990, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.7.0-1-grsec-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/dash Init: systemd (via /run/systemd/system) Versions of packages chromium depends on: ii libasound2 1.0.28-1 ii libatk1.0-0 2.14.0-1 ii libc62.19-18+deb8u6 ii libcairo21.14.0-2.1+deb8u1 ii libcups2 1.7.5-11+deb8u1 ii libdbus-1-3 1.8.20-0+deb8u1 ii libexpat12.1.0-6+deb8u3 ii libfontconfig1 2.11.0-6.3+deb8u1 ii libfreetype6 2.5.2-3+deb8u1 ii libgcc1 1:4.9.2-10 ii libgdk-pixbuf2.0-0 2.31.1-2+deb8u5 ii libglib2.0-0 2.42.1-1+b1 ii libgtk2.0-0 2.24.25-3+deb8u1 ii libjpeg62-turbo 1:1.3.1-12 ii libnspr4 2:4.12-1+debu8u1 ii libnss3 2:3.26-1+debu8u1 ii libpango-1.0-0 1.36.8-3 ii libpangocairo-1.0-0 1.36.8-3 ii libpng12-0 1.2.50-2+deb8u2 ii libstdc++6 4.9.2-10 ii libwebp5 0.4.1-1.2+b2 ii libwebpdemux10.4.1-1.2+b2 ii libx11-6 2:1.6.2-3 ii libx11-xcb1 2:1.6.2-3 ii libxcb1 1.10-3+b1 ii libxcomposite1 1:0.4.4-1 ii libxcursor1 1:1.1.14-1+b1 ii libxdamage1 1:1.1.4-2+b1 ii libxext6 2:1.3.3-1 ii libxfixes3 1:5.0.1-2+b2 ii libxi6 2:1.7.4-1+b2 ii libxml2 2.9.1+dfsg1-5+deb8u3 ii libxrandr2 2:1.4.2-1+b1 ii libxrender1 1:0.9.8-1+b1 ii libxslt1.1 1.1.28-2+deb8u2 ii libxss1 1:1.2.2-1 ii libxtst6 2:1.2.2-1+b1 ii x11-utils7.7+2 ii xdg-utils1.1.0~rc1+git20111210-7.4 chromium recommends no packages. Versions of packages chromium suggests: pn chromium-inspector pn chromium-l10n -- no debconf information
Bug#843794: [libvirt] tweak build dependencies to allow building for jessie
Package: libvirt Version: 2.4.0-1 Severity: wishlist --- Please enter the report below this line. --- Currently, on Debian jessie the build process depends on resolving: Backporting package libvirt in sid→jessie/amd64: unsatisfiable build dependencies: Build-Depends libxml2-dev (>2.9.2+really2.9.1+dfsg1-0.2). But, using "dpkg-buildpackage -d -b -uc", the build does succeed on jessie even with libxml2-dev (2.9.1+dfsg1-5+deb8u3) installed. Could the B-D be relaxed to allow building on jessie without having to use -d? --- System information. --- Architecture: amd64 Kernel: Linux 4.7.0-0.bpo.1-amd64 Debian Release: 8.6 990 stable security.debian.org 990 stable ftp.debian.org 500 stable repos.wine-staging.com 500 stable deb.i2p2.no 500 jessie-backports mozilla.debian.net 100 jessie-backports ftp.debian.org --- Package information. --- Package's Depends field is empty. Package's Recommends field is empty. Package's Suggests field is empty.
Bug#843651: [yarssr] error-generic for tracker.debian.org rss feeds
Package: yarssr Version: 0.2.2-9 Severity: normal --- Please enter the report below this line. --- yarssr is unable to fetch rss feed such as: https://tracker.debian.org/pkg/firefox/rss Running yarssr with --debug only reveals: [17:02:43] Downloading firefox [17:02:54] failed (error-generic) --- System information. --- Architecture: amd64 Kernel: Linux 4.7.0-0.bpo.1-amd64 Debian Release: 8.6 990 stable security.debian.org 990 stable ftp.debian.org 500 stable repos.wine-staging.com 500 stable deb.i2p2.no 500 jessie-backports mozilla.debian.net 100 jessie-backports ftp.debian.org --- Package information. --- Package's Depends field is empty. Package's Recommends field is empty. Package's Suggests field is empty.
Bug#843520: [akonadi-server] Fails to start after mysql upgrade
Package: akonadi-server Version: 1.13.0-2+deb8u1 Severity: important Tags: patch --- Please enter the report below this line. --- After this apt upgrade: Upgrade: mysql-server-core-5.5:amd64 (5.5.52-0+deb8u1, 5.5.53-0+deb8u1), mysql-common:amd64 (5.5.52-0+deb8u1, 5.5.53-0+deb8u1), libmysqlclient18:amd64 (5.5.52-0+deb8u1, 5.5.53-0+deb8u1) I rebooted and noticed that Akonadi was unable to start. akonadiserver.error: Database process exited unexpectedly during initial connection! executable: "/usr/sbin/mysqld" arguments: ("--defaults-file=/home/fld/.local/share/akonadi/mysql.conf", "--datadir=/home/fld/.local/share/akonadi/db_data/", "--socket=/tmp/akonadi-fld.T7GgAn/mysql.socket") stdout: "" stderr: "/usr/sbin/mysqld: Error on realpath() on '/var/lib/mysql-files' (Error 2) 161107 13:16:09 [ERROR] Failed to access directory for --secure-file-priv. Please make sure that directory exists and is accessible by MySQL Server. Supplied value : /var/lib/mysql-files 161107 13:16:09 [ERROR] Aborting I was able to fix it by adding "secure_file_priv=" to ~/.local/share/akonadi/mysql.conf --- System information. --- Architecture: amd64 Kernel: Linux 4.7.0-0.bpo.1-amd64 Debian Release: 8.6 990 stable security.debian.org 990 stable ftp.debian.org 500 stable repos.wine-staging.com 500 stable deb.i2p2.no 500 jessie-backports mozilla.debian.net 100 jessie-backports ftp.debian.org --- Package information. --- Package's Depends field is empty. Package's Recommends field is empty. Package's Suggests field is empty.
Bug#838640: [deluge]
Package: deluge Version: 1.3.10-3 --- Please enter the report below this line. --- Hopefully this makes it in time before the Stretch freeze, because I've already wasted tens of gigabytes of bandwidth when Deluge automatically re-downloads torrents whose data has been moved (http://dev.deluge-torrent.org/ticket/1032) --- System information. --- Architecture: amd64 Kernel: Linux 4.7.0-0.bpo.1-amd64 Debian Release: 8.6 990 stable security.debian.org 990 stable ftp.debian.org 500 stable repos.wine-staging.com 500 stable deb.i2p2.no 500 jessie-backports mozilla.debian.net 100 jessie-backports ftp.debian.org --- Package information. --- Package's Depends field is empty. Package's Recommends field is empty. Package's Suggests field is empty.
Bug#840299: [shatag] Package new upstream version
Package: shatag Version: 0.4.1-2 Severity: wishlist --- Please enter the report below this line. --- The new upstream version of shatag (https://bitbucket.org/maugier/shatag/commits/) adds better support for handling Unicode filenames (no more errors) and introduces a handy new mode for easily checking files for silent data corruption (scrubbing). These little changes made shatag much more usable for me. --- System information. --- Architecture: amd64 Kernel: Linux 4.7.0-0.bpo.1-amd64 Debian Release: 8.6 990 stable security.debian.org 990 stable ftp.debian.org 500 stable repos.wine-staging.com 500 stable deb.i2p2.no 500 jessie-backports mozilla.debian.net 100 jessie-backports ftp.debian.org --- Package information. --- Package's Depends field is empty. Package's Recommends field is empty. Package's Suggests field is empty.
Bug#838383: udisks2: Error updating SMART data causes external USB storage device to drop-out
Package: udisks2 Version: 2.1.3-5 Severity: normal Tags: newcomer Dear Maintainer, With this external Seagate Expansion Portable 1 TB USB 3 disk: === START OF INFORMATION SECTION === Device Model: ST1000LM035-1RK172 Firmware Version: SBM3 User Capacity:1,000,204,886,016 bytes [1.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate:5400 rpm Form Factor: 2.5 inches Device is:Not in smartctl database [for details use: -P showall] ATA Version is: ACS-3 T13/2161-D revision 3b SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is:Tue Sep 20 20:59:05 2016 EEST SMART support is: Available - device has SMART capability. SMART support is: Enabled Every 10 minutes this happens: udisksd[2159]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/ST1000LM035_1RK172_W9320RGD: Error updating SMART data: sk_disk_check_sleep_mode: Operation not supported (udisks-error- quark, 0) main kernel: [94887.803919] sd 10:0:0:0: [sdd] tag#28 uas_eh_abort_handler 0 uas-tag 29 inflight: CMD main kernel: [94887.803923] sd 10:0:0:0: [sdd] tag#28 CDB: ATA command pass through(12)/Blank a1 08 2e 00 01 00 00 00 00 ec 00 00 main kernel: [94910.787219] sd 10:0:0:0: [sdd] tag#6 uas_eh_abort_handler 0 uas-tag 7 inflight: CMD main kernel: [94910.787224] sd 10:0:0:0: [sdd] tag#6 CDB: Read(10) 28 00 00 5f e1 00 00 02 00 00 main kernel: [94910.787243] scsi host10: uas_eh_bus_reset_handler start main kernel: [94910.875335] usb 3-3.4: reset high-speed USB device number 17 using xhci_hcd main kernel: [94911.060414] scsi host10: uas_eh_bus_reset_handler success Going trough this causes noticeable delays to any ongoing I/O operations! -- System Information: Debian Release: 8.6 APT prefers stable APT policy: (990, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.7.2 (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 Init: systemd (via /run/systemd/system) Versions of packages udisks2 depends on: ii dbus 1.8.20-0+deb8u1 ii libacl12.2.52-2 ii libatasmart4 0.19-3 ii libc6 2.19-18+deb8u6 ii libglib2.0-0 2.42.1-1+b1 ii libgudev-1.0-0 215-17+deb8u5 ii libpam-systemd 215-17+deb8u5 ii libpolkit-agent-1-00.105-15~deb8u2 ii libpolkit-gobject-1-0 0.105-15~deb8u2 ii libsystemd0215-17+deb8u5 ii libudisks2-0 2.1.3-5 ii parted 3.2-7 ii udev 215-17+deb8u5 Versions of packages udisks2 recommends: ii dosfstools 3.0.27-1 ii eject2.1.5+deb1+cvs20081104-13.1 ii gdisk0.8.10-2 ii ntfs-3g 1:2014.2.15AR.2-1+deb8u2 ii policykit-1 0.105-15~deb8u2 Versions of packages udisks2 suggests: ii btrfs-tools 3.17-1.1 ii cryptsetup-bin 2:1.6.6-5 pn exfat-utils ii mdadm 3.3.2-5+deb8u1 ii reiserfsprogs 1:3.6.24-1 ii xfsprogs3.2.1 -- no debconf information
Bug#780062: lircrcd segfaults
On Sun, 8 Mar 2015 22:09:00 + John Williamswrote: > Package: lirc > Version: 0.9.0~pre1-1.2 > > I have just updated from wheezy to jessie (i386) > > At random intervals my lirc configuration stops working; I can see that > the lircrcd program has disappeared, and /var/log/syslog contains this: > > lircrcd[843]: segfault at e975f324 ip 0804942b sp bfac5c90 error 7 in > lircrcd[8048000+4000] > > I have the current latest jessie version of every package. My lirc > configuration files have not changed and were working fine in wheezy. > > Hi, Just upgraded from Wheezy->Jessie and I also started getting these random segfaults: $ dmesg | grep segm [ 4235.019558] traps: lircrcd[969] trap stack segment ip:401a87 sp:7ffd5ab61bc0 error:0 in lircrcd[40+4000] [16587.897038] traps: lircrcd[17175] trap stack segment ip:401a87 sp:7ffc39fb23e0 error:0 in lircrcd[40+4000] [16604.362987] traps: lircrcd[17364] trap stack segment ip:401a87 sp:7ffeefdd7fa0 error:0 in lircrcd[40+4000] [16645.638990] traps: lircrcd[17611] trap stack segment ip:401a87 sp:7fff7cc04b20 error:0 in lircrcd[40+4000] [16652.761130] traps: lircrcd[17947] trap stack segment ip:401a87 sp:7ffc13236300 error:0 in lircrcd[40+4000] [97933.168463] traps: lircrcd[3988] trap stack segment ip:401a87 sp:7ffd60e72a90 error:0 in lircrcd[40+4000] [97940.655398] traps: lircrcd[26463] trap stack segment ip:401a87 sp:7ffe29c07fb0 error:0 in lircrcd[40+4000] [191015.136621] traps: lircrcd[29975] trap stack segment ip:401a87 sp:7ffd56ac76f0 error:0 in lircrcd[40+4000] $ sudo ir-keytable Found /sys/class/rc/rc0/ (/dev/input/event3) with: Driver mceusb, table rc-rc6-mce Supported protocols: NEC RC-5 RC-6 JVC SONY SANYO LIRC SHARP other Enabled protocols: NEC RC-5 RC-6 JVC SONY SANYO LIRC SHARP other Name: Media Center Ed. eHome Infrared bus: 3, vendor/product: 045e:006d, version: 0x0200 Repeat delay = 500 ms, repeat period = 125 ms $ ps aux | grep lirc root 28584 0.0 0.0 21044 1480 ?Ss 16:32 0:00 /usr/sbin/lircd --driver=default --device=/dev/lirc0 root 28589 0.0 0.0 6288 1224 ?Ss 16:32 0:00 lircrcd /etc/lirc/lircrc root 28590 0.0 0.0 627696 ?Ss 16:32 0:00 /usr/bin/irexec -d /etc/lirc/lircrc The current workaround that I'm using: /bin/sh -c 'while true; do while pgrep lircrcd; do sleep 1s; done; /etc/init.d/lirc restart; done' &> /dev/null & This bug should be escalated to 'Serious / Release Critical' classification?
Bug#750959: linux-image-3.15-rc8-amd64: Add support for VGA VFIO (CONFIG_VFIO_PCI_VGA)
The requested feature is now present in the latest Debian SID kernel (3.16.7-ckt4-3): % grep VFIO /boot/config-3.16.0-4-amd64 CONFIG_VFIO_IOMMU_TYPE1=m CONFIG_VFIO=m CONFIG_VFIO_PCI=m CONFIG_VFIO_PCI_VGA=y CONFIG_KVM_VFIO=y This bug report can thus be closed. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773172: linux: Easier PCI Stub support with CONFIG_PCI_STUB=y
Source: linux Severity: wishlist Dear Maintainer, Using the kernel commandline option pci-stub.ids= is a very popular and easy way of preventing device drivers from attaching to devices that are meant to be assigned (PCI passthrough via Vt-d/IOMMU) to virtual machines. Currently Debian's default kernel images do not support this parameter because pci-stub has been configured as a module. Loading the module via /etc/modules or /etc/initramfs-tools/modules does not seem to guarantee that the pci-stub module gets loaded before other device drivers have a chance to snatch up the devices that need to be stubbed. I propose we change the default from CONFIG_PCI_STUB=m to CONFIG_PCI_STUB=y so that Debian can support the widely popular practice of specifying pci-stub.ids on the kernel commandline. -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.17.0-trunk-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/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750959: linux-image-3.15-rc8-amd64: Add support for VGA VFIO (CONFIG_VFIO_PCI_VGA)
Source: linux-image-3.15-rc8-amd64 Severity: wishlist Dear Maintainer, In the past few years with the increased availability of IOMMU/Vt-d supporting hardware, there has been an increase in the popularity of experimenting with VGA passtrough to virtual machines via IOMMU. Currently the most bleeding edge way of doing this is with the combination of kvm, qemu and vfio. However, most graphics cards don't play nice with just the plain vfio and need special considerations that need to be enabled in the kernel. I propose that we enable these special features called CONFIG_VFIO_PCI_VGA in the kernel so that people can more easily experiment with these new cool features. I asked the leading developer of VFIO VGA support (Alex Williamson) if he could think of any reason why not to enable this feature by default, and he could not think of any. The option should simply add the capability to use the x-vga feature in Qemu. Here some basic information about VFIO: https://www.kernel.org/doc/Documentation/vfio.txt Interesting presentations about VGA Passtroughs with VFIO: http://www.linux-kvm.org/wiki/images/b/b4/2012-forum-VFIO.pdf http://www.linux-kvm.org/wiki/images/e/ed/Kvm-forum-2013-VFIO-VGA.pdf There is also quite a bit of mainstream interest about this stuff: https://bbs.archlinux.org/viewtopic.php?id=162768 Thank you. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.15.0-rc7 (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#750958: 20_linux_xen: wrong Xen parameters generated for pc's using efi
Package: grub-efi Version: 2.02~beta2-10 Severity: normal Tags: upstream Dear Maintainer, Consider this code in the 20_linux_xen script: if [ \$grub_platform = pc -o \$grub_platform = ]; then xen_rm_opts= else xen_rm_opts=no-real-mode edd=off fi The purpose is to set options: no-real-mode edd=off for non-pc machines, yet when booting up with U(EFI), the $grub_platform equals efi, and those boot parameters get added. They are probably not something many PC users would want, especially since no-real-mode seems to disable the VGA completely. Without really knowing much about anything, this is how I fixed it: if [ $grub_platform = pc -o $grub_platform = efi -o $grub_platform = ]; then xen_rm_opts= else xen_rm_opts=no-real-mode edd=off fi -- Package-specific info: *** BEGIN /proc/mounts /dev/mapper/debian-lvroot / ext4 rw,noatime,errors=remount-ro,data=ordered 0 0 /dev/sda3 /boot ext3 rw,noatime,data=ordered 0 0 /dev/sda1 /boot/efi vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=utf8,shortname=mixed,errors=remount-ro 0 0 *** END /proc/mounts *** BEGIN /boot/grub/grub.cfg # # DO NOT EDIT THIS FILE # # It is automatically generated by grub-mkconfig using templates # from /etc/grub.d and settings from /etc/default/grub # ### BEGIN /etc/grub.d/00_header ### if [ -s $prefix/grubenv ]; then set have_grubenv=true load_env fi if [ ${next_entry} ] ; then set default=${next_entry} set next_entry= save_env next_entry set boot_once=true else set default=${saved_entry} fi if [ x${feature_menuentry_id} = xy ]; then menuentry_id_option=--id else menuentry_id_option= fi export menuentry_id_option if [ ${prev_saved_entry} ]; then set saved_entry=${prev_saved_entry} save_env saved_entry set prev_saved_entry= save_env prev_saved_entry set boot_once=true fi function savedefault { if [ -z ${boot_once} ]; then saved_entry=${chosen} save_env saved_entry fi } function load_video { if [ x$feature_all_video_module = xy ]; then insmod all_video else insmod efi_gop insmod efi_uga insmod ieee1275_fb insmod vbe insmod vga insmod video_bochs insmod video_cirrus fi } if [ x$feature_default_font_path = xy ] ; then font=unicode else insmod part_gpt insmod ext2 set root='hd0,gpt3' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt3 --hint-efi=hd0,gpt3 --hint-baremetal=ahci0,gpt3 d6906260-070a-41f6-bb66-89b4ce4dde0a else search --no-floppy --fs-uuid --set=root d6906260-070a-41f6-bb66-89b4ce4dde0a fi font=/grub/unicode.pf2 fi if loadfont $font ; then set gfxmode=auto load_video insmod gfxterm set locale_dir=$prefix/locale set lang=en_US insmod gettext fi terminal_output gfxterm if [ ${recordfail} = 1 ] ; then set timeout=-1 else if [ x$feature_timeout_style = xy ] ; then set timeout_style=menu set timeout=10 # Fallback normal timeout code in case the timeout_style feature is # unavailable. else set timeout=10 fi fi ### END /etc/grub.d/00_header ### ### BEGIN /etc/grub.d/05_debian_theme ### insmod part_gpt insmod ext2 set root='hd0,gpt3' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt3 --hint-efi=hd0,gpt3 --hint-baremetal=ahci0,gpt3 d6906260-070a-41f6-bb66-89b4ce4dde0a else search --no-floppy --fs-uuid --set=root d6906260-070a-41f6-bb66-89b4ce4dde0a fi insmod png if background_image /grub/.background_cache.png; then set color_normal=white/black set color_highlight=black/white else set menu_color_normal=cyan/blue set menu_color_highlight=white/blue fi ### END /etc/grub.d/05_debian_theme ### ### BEGIN /etc/grub.d/10_linux ### function gfxmode { set gfxpayload=${1} } set linux_gfx_mode= export linux_gfx_mode menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-e6dbee93-5688-4d7d-9cb3-9aec74150cc2' { savedefault load_video insmod gzio insmod part_gpt insmod ext2 set root='hd0,gpt3' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt3 --hint-efi=hd0,gpt3 --hint-baremetal=ahci0,gpt3 d6906260-070a-41f6-bb66-89b4ce4dde0a else search --no-floppy --fs-uuid --set=root d6906260-070a-41f6-bb66-89b4ce4dde0a fi echo'Loading Linux 3.15.0-rc8-next-20140603+ ...' linux /vmlinuz-3.15.0-rc8-next-20140603+ root=/dev/mapper/debian-lvroot ro consoleblank=0 intel_iommu=on,igfx_off echo'Loading initial ramdisk ...' initrd /initrd.img-3.15.0-rc8-next-20140603+ } submenu 'Advanced options for Debian GNU/Linux' $menuentry_id_option 'gnulinux-advanced-e6dbee93-5688-4d7d-9cb3-9aec74150cc2' { menuentry 'Debian
Bug#666517: dnsmasq: TXT record problems found by berkeley's netalyzr
Package: dnsmasq Version: 2.55-2 Severity: normal Did the berkeley's ICSI Netalyzr test on a Win XP (Java 7) machine behind my Debian gateway running Squeeze, got following results: Direct probing of DNS resolvers (?) – Your system is configured to use 1 DNS resolver(s). The resolver at 192.168.0.1 (phys-dns51) could not process the following tested types: * Medium (~1300B) TXT records * Large (~3000B) TXT records It validates DNSSEC. It does not wildcard NXDOMAIN errors. The resolver reports a number of additional properties. Hide them. * Hostname: phys-dns51 * Version: dnsmasq-2.55 * Authors: Simon Kelley * Copyright: Copyright (c) 2000-2010 Simon Kelley -- System Information: Debian Release: 6.0.3 APT prefers stable APT policy: (700, 'stable'), (500, 'stable-updates') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (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 dnsmasq depends on: ii adduser 3.112+nmu2 add and remove users and groups ii dnsmasq-base 2.55-2+b1 A small caching DNS proxy and DHCP ii netbase 4.45 Basic TCP/IP networking system dnsmasq recommends no packages. Versions of packages dnsmasq suggests: pn resolvconfnone (no description available) -- Configuration Files: /etc/dnsmasq.conf changed [not included] -- 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