Bug#716767: libvirt-bin: Segfaults in virUUIDParse

[Luca Tettamanti]

Package: libvirt-bin
Version: 0.9.12-11+deb7u1
Severity: normal
Tags: patch

Hello,
>From time to time I get a segfault in virUUIDParse, with the following
stack trace:

(gdb) bt
#0  virUUIDParse (uuidstr=0x4 , 
uuid=uuid@entry=0x7fffc1ebe700 
"g5\036\311\003\006\347\\\335\300\376M\327\373\311\343`") at 
/build/libvirt-FsA54o/libvirt-0.9.12/./src/util/uuid.c:139
#1  0x7f0eaa281485 in xenStoreDomainGetUUID conn=conn@entry=0x12546f0, 
id=, uuid=uuid@entry=0x7fffc1ebe700 
"g5\036\311\003\006\347\\\335\300\376M\327\373\311\343`") at 
/build/libvirt-FsA54o/libvirt-0.9.12/./src/xen/xs_internal.c:1114
#2  0x7f0eaa2815cf in xenStoreDomainIntroduced (conn=0x12546f0, 
path=, token=, opaque=0x1254810) at 
/build/libvirt-FsA54o/libvirt-0.9.12/./src/xen/xs_internal.c:1360
#3  0x7f0eaa27ffdb in xenStoreWatchEvent (watch=, 
fd=, events=, data=0x12546f0) at 
/build/libvirt-FsA54o/libvirt-0.9.12/./src/xen/xs_internal.c:1300
#4  0x7f0eaa189e7e in virEventPollDispatchHandles (fds=, 
nfds=) at 
/build/libvirt-FsA54o/libvirt-0.9.12/./src/util/event_poll.c:490
#5  virEventPollRunOnce () at 
/build/libvirt-FsA54o/libvirt-0.9.12/./src/util/event_poll.c:637
#6  0x7f0eaa1888b7 in virEventRunDefaultImpl () at 
/build/libvirt-FsA54o/libvirt-0.9.12/./src/util/event.c:247
#7  0x7f0eaa25cd7d in virNetServerRun (srv=0xd9fa00) at 
/build/libvirt-FsA54o/libvirt-0.9.12/./src/rpc/virnetserver.c:712
#8  0x00423ab1 in main (argc=, argv=) at 
/build/libvirt-FsA54o/libvirt-0.9.12/./daemon/libvirtd.c:1138
(gdb) f 1
#1  0x7f0eaa281485 in xenStoreDomainGetUUID (conn=conn@entry=0x12546f0, 
id=, uuid=uuid@entry=0x7fffc1ebe700 
"g5\036\311\003\006\347\\\335\300\376M\327\373\311\343`") at 
/build/libvirt-FsA54o/libvirt-0.9.12/./src/xen/xs_internal.c:1114
1114ret = virUUIDParse(uuidstr + 4, uuid);
(gdb) list
1109/* This will return something like
1110 * /vm/---- */
uuidstr = xs_read(priv->xshandle, 0, prop, &len);
1112
1113/* remove "/vm/" */
1114ret = virUUIDParse(uuidstr + 4, uuid);
1115
1116VIR_FREE(uuidstr);
1117
1118return ret;

xs_read() returns NULL and the surrounding code fails to check for this.

The bug happens maybe once a week on various hosts, and I'm not sure how
to reproduce it. It might be triggered by our management tools using
libvirt while another instace is being created/destroyed (i.e. some kind
of race condition).

For a quick glance to the latest code I think this might happend there
too. Regardless of the cause, xs_read can return NULL so the code should
check before using the resulting pointer:

--- libvirt-0.9.12.orig/src/xen/xs_internal.c
+++ libvirt-0.9.12/src/xen/xs_internal.c
@@ -1109,6 +1109,8 @@ int xenStoreDomainGetUUID(virConnectPtr
 /* This will return something like
  * /vm/---- */
 uuidstr = xs_read(priv->xshandle, 0, prop, &len);
+if (uuidstr == NULL)
+return -errno;
 
 /* remove "/vm/" */
 ret = virUUIDParse(uuidstr + 4, uuid);

What do you think?

Thanks,
Luca

-- System Information:
Debian Release: 7.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libvirt-bin depends on:
ii  adduser 3.113+nmu3
ii  gettext-base0.18.1.1-9
ii  libavahi-client30.6.31-2
ii  libavahi-common30.6.31-2
ii  libblkid1   2.20.1-5.3
ii  libc6   2.13-38
ii  libcap-ng0  0.6.6-2
ii  libdbus-1-3 1.6.8-1+deb7u1
ii  libdevmapper1.02.1  2:1.02.74-7
ii  libgcrypt11 1.5.0-5
ii  libgnutls26 2.12.20-7
ii  libnetcf1   0.1.9-2
ii  libnl1  1.1-7
ii  libnuma12.0.8~rc4-1
ii  libparted0debian1   2.3-12
ii  libpcap0.8  1.3.0-1
ii  libpciaccess0   0.13.1-2
ii  libreadline66.2+dfsg-0.1
ii  libsasl2-2  2.1.25.dfsg1-6+deb7u1
ii  libudev0175-7.2
ii  libvirt00.9.12-11+deb7u1
ii  libxenstore3.0  4.1.4-3+deb7u1
ii  libxml2 2.8.0+dfsg1-7+nmu1
ii  libyajl22.0.4-2
ii  logrotate   3.8.1-4

Versions of packages libvirt-bin recommends:
ii  bridge-utils1.5-6
ii  dmidecode   2.11-9
ii  dnsmasq-base2.62-3+deb7u1
ii  ebtables2.0.10.4-1
ii  gawk1:4.0.1+dfsg-2.1
ii  iproute 20120521-3+b3
ii  iptables1.4.14-3.1
ii  libxml2-utils   2.8.0+dfsg1-7+nmu1
ii  netcat-openbsd  1.105-7
ii  parted  2.3-12
ii  qemu1.1.2+dfsg-6a
ii  qemu-kvm1.1.2+dfsg-6

Versions of packages libvirt-bin suggests:
ii  policykit-1  0.105-3
pn  radvd

-- Configuration Files:
/etc/default/libvirt-bin changed:
ulimit -c unlimited
start_libvirtd="yes"
libvirtd_opts="-d"


-- no debconf information


-- 
T

Bug#706221: udev: 91-permissions.rules:94 missing continuation

[Luca Tettamanti]

Package: udev
Version: 175-7.1
Severity: important

Hello,
after upgrading a machine to Wheezy I noticed that MD device nodes where
not removed anymore once the array was stopped.
I noticed that the device node had the sticky bit set, and udev was
refusing to remove it:

  device node '/dev/md1' has sticky bit set, skip removal

The sticky bit is only set by the "static_node" option, and there are
not rules setting it for block devices.

Unfortunately, in 91-permissions.rules at line 94 you can see this:

# sound devices
SUBSYSTEM=="sound", GROUP="audio", 
OPTIONS+="static_node=snd/seq", OPTIONS+="static_node=snd/timer"

Note that there's not continuation backslash at the end of the line: the
options are applied unconditionally (hence the "important" severity).

I've verified that adding the backslash fixes the bug.

-- System Information:
Debian Release: 7.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages udev depends on:
ii  debconf [debconf-2.0]  1.5.49
ii  libc6  2.13-38
ii  libselinux12.1.9-5
ii  libudev0   175-7.1
ii  lsb-base   4.1+Debian8
ii  procps 1:3.3.3-3
ii  util-linux 2.20.1-5.3

Versions of packages udev recommends:
ii  pciutils  1:3.1.9-6
ii  usbutils  1:005-3

udev suggests no packages.

-- Configuration Files:
/etc/udev/udev.conf changed [not included]

-- debconf information:
  udev/new_kernel_needed: false
  udev/title/upgrade:
  udev/reboot_needed:
  udev/sysfs_deprecated_incompatibility:

-- debsums errors found:
debsums: changed file /lib/udev/rules.d/91-permissions.rules (from udev package)


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#705205: libvirt-bin: Memory leak in virStorageBackendLogicalMakeVol

[Luca Tettamanti]

Package: libvirt-bin
Version: 0.9.12-11
Severity: important
Tags: patch

Hello,
In our workload we use LVM for VM storage and continuously create and destroy 
instances.
We noticed that over time libvirtd memory usage grows until libvirt
cannot fork anymore (to spawn LVM tools):

virFork:279 : cannot fork child process: Cannot allocate memory

libvirtd won't crash (yet), but it will eventually mark all the storage
pools as offline.

I've tracked down the issue to a memory leak in
virStorageBackendLogicalMakeVol (creating a volume triggers a refresh of
the pool):

50,229,128 (820,736 direct, 49,408,392 indirect) bytes in 3,664 blocks are 
definitely lost in loss record 883 of 883
   at 0x4C28BED: malloc (vg_replace_malloc.c:263)
   by 0x4C28D6F: realloc (vg_replace_malloc.c:632)
   by 0x805ADF3: re_compile_internal (regcomp.c:760)
   by 0x805B1AB: regcomp (regcomp.c:506)
   by 0x4D13CD: virStorageBackendLogicalMakeVol (storage_backend_logical.c:203)
   by 0x4CE09B: virStorageBackendRunProgRegex (storage_backend.c:1512)
   by 0x4D0A8E: virStorageBackendLogicalFindLVs (storage_backend_logical.c:306)
   by 0x4D1971: virStorageBackendLogicalRefreshPool 
(storage_backend_logical.c:591)
   by 0x4C9596: storagePoolRefresh (storage_driver.c:904)
   by 0x511CE44: virStoragePoolRefresh (libvirt.c:12116)
   by 0x436687: remoteDispatchStoragePoolRefreshHelper (remote_dispatch.h:11759)
   by 0x515B7FF: virNetServerProgramDispatch (virnetserverprogram.c:423)

This bug has already been fixed upstream with commit 71da3b66 (which
also reverts afc4631b). This fix is already included in the experimental
package, but since it's self-contained and minimally intrusive I suggest
to backport it for Wheezy (and squeeze-backports?).
Patch is attached.

Luca

-- System Information:
Debian Release: 7.0
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libvirt-bin depends on:
ii  adduser 3.113+nmu3
ii  gettext-base0.18.1.1-9
ii  libavahi-client30.6.31-2
ii  libavahi-common30.6.31-2
ii  libblkid1   2.20.1-5.3
ii  libc6   2.13-38
ii  libcap-ng0  0.6.6-2
ii  libdbus-1-3 1.6.8-1
ii  libdevmapper1.02.1  2:1.02.74-7
ii  libgcrypt11 1.5.0-5
ii  libgnutls26 2.12.20-4
ii  libnetcf1   0.1.9-2
ii  libnl1  1.1-7
ii  libnuma12.0.8~rc4-1
ii  libparted0debian1   2.3-12
ii  libpcap0.8  1.3.0-1
ii  libpciaccess0   0.13.1-2
ii  libreadline66.2+dfsg-0.1
ii  libsasl2-2  2.1.25.dfsg1-6
ii  libudev0175-7.1
ii  libvirt00.9.12-11
ii  libxenstore3.0  4.1.4-2
ii  libxml2 2.8.0+dfsg1-7+nmu1
ii  libyajl22.0.4-2
ii  logrotate   3.8.1-4

Versions of packages libvirt-bin recommends:
ii  bridge-utils1.5-6
ii  dmidecode   2.11-9
ii  dnsmasq-base2.62-3+deb7u1
ii  ebtables2.0.10.4-1
ii  gawk1:4.0.1+dfsg-2.1
ii  iproute 20120521-3+b3
ii  iptables1.4.14-3.1
ii  libxml2-utils   2.8.0+dfsg1-7+nmu1
ii  netcat-openbsd  1.105-7
ii  parted  2.3-12
ii  qemu1.1.2+dfsg-6a
ii  qemu-kvm1.1.2+dfsg-6

Versions of packages libvirt-bin suggests:
ii  policykit-1  0.105-3
ii  radvd1:1.8.5-1

-- Configuration Files:
/etc/default/libvirt-bin changed [not included]
/etc/init.d/libvirt-bin changed [not included]

-- no debconf information

*** /tmp/fix-leak.diff
diff -Nru libvirt-0.9.12/debian/changelog libvirt-0.9.12/debian/changelog
--- libvirt-0.9.12/debian/changelog 2013-03-06 11:27:13.0 +
+++ libvirt-0.9.12/debian/changelog 2013-04-11 09:53:13.0 +0100
@@ -1,3 +1,10 @@
+libvirt (0.9.12-11.1) UNRELEASED; urgency=low
+
+  * Non-maintainer upload.
+  * Backport upstream 71da3b66 (fix leak in virStorageBackendLogicalMakeVol)
+
+ -- Luca Tettamanti   Thu, 11 Apr 2013 09:53:03 +0100
+
 libvirt (0.9.12-11) unstable; urgency=low
 
   * [422c506] Use "getent passwd" instead of the non existing "getent user"
diff -Nru 
libvirt-0.9.12/debian/patches/fix-leak-virStorageBackendLogicalMakeVol.patch 
libvirt-0.9.12/debian/patches/fix-leak-virStorageBackendLogicalMakeVol.patch
--- 
libvirt-0.9.12/debian/patches/fix-leak-virStorageBackendLogicalMakeVol.patch
1970-01-01 01:00:00.0 +0100
+++ 
libvirt-0.9.12/debian/patches/fix-leak-virStorageBackendLogicalMakeVol.patch
2013-04-11 09:55:16.0 +0100
@@ -0,0 +1,22 @@
+Index: libvirt-0.9.12/src/storage/storage_backend_logical.c
+===
+--- libvirt-0.9.12.orig/src/storage/storage_backend_logical.c  2012-04-18 
06:07:44.0 +0100
 libvirt-0.9.12/src/storage/storage_backe

Bug#676617: uswsusp: postinst generates an invalid config file

[Luca Tettamanti]

Package: uswsusp
Version: 1.0+20110509-2
Severity: normal

The configuration file generated after the first install contains this line:

image size = 2.86942e+09

which is bogus (the program expects an unsigned int, so the value is truncated).
This is generated in uswsusp.config:55 by:

IMAGESIZE=`awk '$1 == "MemTotal:" {print int($2*1024*0.46)}' /proc/meminfo 2> 
/dev/null`

My system has 6GB of RAM:

$ grep MemTotal /proc/meminfo
MemTotal:6091988 kB

So the expression overflows the 'int' and is printed as floating point.
The following statement outputs an integer, but the result is somewhat off
(maybe it gets truncated internally):

awk '$1 == "MemTotal:" {printf("%lu\n", $2*1024*0.46)}' /proc/meminfo

The shell (I've tried both dash and bash) is able to compute the correct value,
like this:

IMAGESIZE=$((`awk '$1 == "MemTotal:" {print $2}' /proc/meminfo` * 1024 / 100 * 
46))

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (600, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.4.0 (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 uswsusp depends on:
ii  debconf [debconf-2.0]  1.5.43
ii  libc6  2.13-33
ii  libgcrypt111.5.0-3
ii  liblzo2-2  2.06-1
ii  libpci31:3.1.9-3
ii  libx86-1   1.1+ds1-9

Versions of packages uswsusp recommends:
ii  initramfs-tools  0.106
ii  mount2.20.1-5

uswsusp suggests no packages.

-- debconf information:
  uswsusp/compute_checksum: false
  uswsusp/no_snapshot:
  uswsusp/suspend_loglevel:
  uswsusp/no_swap:
  uswsusp/resume_offset:
  uswsusp/early_writeout: true
  uswsusp/image_size: 2.86942e+09
  uswsusp/compress: true
  uswsusp/create_RSA_key: false
  uswsusp/snapshot_device:
  uswsusp/RSA_key_file: /etc/uswsusp.key
  uswsusp/max_loglevel:
  uswsusp/resume_device: /dev/dm-1
  uswsusp/shutdown_method: platform
  uswsusp/encrypt: false
  uswsusp/splash: true
  uswsusp/RSA_key_bits: 1024
  uswsusp/continue_without_swap: true



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#603620: Verify #603620 with 3.1.9

[Luca Tettamanti]

On Sat, Apr 7, 2012 at 1:24 PM, Lior Kaplan  wrote:
> Hi,
>
> Could you help with verifying / reproducing Debian #603620 with apc
> 3.1.9-0.1~bpo60+1 from squeeze-backports repository
> (http://packages.debian.org/squeeze-backports/php-apc) ?

I've tested for a while and I've seen only 1 crash in the past week,
it seems stable.
The machine is running Debian Squeeze, PHP is configured as FCGI.

thanks,
Luca



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#666565: libcairo2:amd64: iceweasel also affected

[Luca Tettamanti]

Package: libcairo2:amd64
Version: 1.12.0-2
Followup-For: Bug #666565

Hello,
iceweasel is also affected; in this case however it's the content of the
brower windows that's corrupted. It's very noticeable on text "intesive"
sites, like gmail. I'm attaching a sample of the corruption.
Downgrading to 1.10.2-7 fixes the issue.


-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-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/dash

Versions of packages libcairo2:amd64 depends on:
ii  libc6  2.13-27
ii  libfontconfig1 2.8.0-3.1
ii  libfreetype6   2.4.9-1
ii  libpixman-1-0  0.24.4-1
ii  libpng12-0 1.2.47-2
ii  libx11-6   2:1.4.4-4
ii  libxcb-render0 1.8.1-1
ii  libxcb-shm01.8.1-1
ii  libxcb11.8.1-1
ii  libxrender11:0.9.6-2
ii  multiarch-support  2.13-27
ii  zlib1g 1:1.2.6.dfsg-2

libcairo2:amd64 recommends no packages.

libcairo2:amd64 suggests no packages.

-- no debconf information
<>

Bug#627630: grub-pc: core.img too large after recent update, raid1+lvm+xfs

[Luca Tettamanti]

Package: grub-pc
Version: 1.99-15
Followup-For: Bug #627630

I just ran into the same issue upgrading from 1.99-14 to 1.99-15.
The list of the modules loaded is minimal:

/usr/bin/grub-mkimage -d /usr/lib/grub/i386-pc -O i386-pc 
--output=/boot/grub/core.img --prefix=(,msdos5)/grub biosdisk ext2 part_msdos

grub modules resides in a separate partition:

/dev/sda5 /boot ext3 rw,noatime,errors=continue,barrier=1,data=ordered 0 0

AFAICS there's no way to resolve the problem without repartitioning the
disk to move the first partition.


-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-1-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/dash

Versions of packages grub-pc depends on:
ii  debconf [debconf-2.0]  1.5.41
ii  grub-common1.99-15
ii  grub-pc-bin1.99-15
ii  grub2-common   1.99-15
ii  ucf3.0025+nmu2

grub-pc recommends no packages.

grub-pc suggests no packages.

-- Configuration Files:
/etc/default/grub changed [not included]

-- debconf information excluded



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#661424: icedtea-netx: warning on upgrade - binary operator expected

[Luca Tettamanti]

Package: icedtea-netx
Version: 1.2~pre2-1
Followup-For: Bug #661424

Same here, looking at the postinst file the error is causes by the
strange output of update-alternatives for javaws:

$ update-alternatives --list javaws
/usr/lib/jvm/java-6-openjdk-amd64//jre/bin/javaws
/usr/lib/jvm/java-6-openjdk-amd64/jre/bin/javaws
/usr/lib/jvm/java-6-sun/jre/bin/javaws

It seems that someone installed an alternative with an extra slash...

update-alternatives --list javaws | grep "^$basedir/"

returns two lines and the shell gets confused.

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-1-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/dash

Versions of packages icedtea-netx depends on:
ii  icedtea-netx-common  1.2~pre2-1
ii  openjdk-6-jre6b24-1.11.1-2

icedtea-netx recommends no packages.

icedtea-netx 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#639889: closed by Javier Fernández-Sanguino Peña (Bug#639889: fixed in ifupdown-extra 0.20)

[Luca Tettamanti]

Version 0.20 fixes the problem with dash, however in
check_status_iplink now "/sbin/ip" is executed *before* checking its
existence.

Luca



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#639889: ifupdown-extra: 00check-network-cable does not work properly with dash

[Luca Tettamanti]

Package: ifupdown-extra
Version: 0.19
Severity: normal

Dear Maintainer,
00check-network-cable does not work with dash, which starting from
Squeeze is installed as the default /bin/sh. The error reported when
bringing up the interface is:

/etc/network/if-up.d/00check-network-cable: 64: local: detected:: bad variable 
name
run-parts: /etc/network/if-up.d/00check-network-cable exited with return code 2

The problem seems to be related to the "local" command; the man page
says:

  This should appear as the first statement of a function[...]

Changing the function to (moving local declarations at the top):

check_status_ethtool () {
local status=0
local LINK
LINK=`$ETHTOOL $IFACE 2>&1 | grep "Link detected"`

fixes the error, but I'm not 100% sure that it's the correct approach.
Other functions are also affected.

The script works fine when run using bash.


-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.0.0-1-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/dash

Versions of packages ifupdown-extra depends on:
ii  bind9-host [host]1:9.7.3.dfsg-1+b1
ii  iproute  20110629-1   
ii  iputils-arping   3:20101006-1+b1  
ii  iputils-ping [ping]  3:20101006-1+b1  
ii  net-tools1.60-24.1
ii  netcat   1.10-39  
ii  netcat-openbsd [netcat]  1.89-4   
ii  netcat-traditional [netcat]  1.10-39  

Versions of packages ifupdown-extra recommends:
ii  ethtool  1:3.0-1

ifupdown-extra 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#635721: libvirt0: ssh changes break virt-manager and qemu+ssh:// protocol

[Luca Tettamanti]

Package: libvirt0
Version: 0.9.3-4
Severity: normal
Tags: patch


virt-manager is unable to connect to remote hosts using qemu+ssh://
protocol; the error (see below) is rather uninformative, but this isse
has already been debugged upstream, see here:

[libvirt] remote driver RPC API usage breaks launching ssh askpass
https://www.redhat.com/archives/libvir-list/2011-July/msg01259.html

In short, DISPLAY is not passed to ssh which is then unable to spawn
askpass to decrypt the private key for the connection.

A fix is already available upstream (tested recompiling debian package):

http://libvirt.org/git/?p=libvirt.git;a=commitdiff;h=e0a21dfef4a6ba9d09386cbedd2322aede0114dc

Error log:
Cannot recv data: Permission denied, please try again.
Permission denied, please try again.
Permission denied (publickey,password).
: Connection reset by peer

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/connection.py", line 1055,
in _try_open
   None], flags)
  File "/usr/lib/python2.6/dist-packages/libvirt.py", line 102, in openAuth
   if ret is None:raise libvirtError('virConnectOpenAuth() failed')
libvirtError: Cannot recv data: Permission denied, please try again.
Permission denied, please try again.
Permission denied (publickey,password).
: Connection reset by peer


-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.0.0 (SMP w/2 CPU cores; PREEMPT)
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 libvirt0 depends on:
ii  libc6   2.13-11  Embedded GNU C Library: Shared lib
ii  libcap- 0.6.6-1  An alternate POSIX capabilities li
ii  libdevm 2:1.02.63-3.1The Linux Kernel Device Mapper use
ii  libgcry 1.4.6-8  LGPL Crypto library - runtime libr
ii  libgnut 2.10.5-3 the GNU TLS library - runtime libr
ii  libnl1  1.1-7library for dealing with netlink s
ii  libsasl 2.1.24~rc1.dfsg1+cvs2011-05-23-4 Cyrus SASL - authentication abstra
ii  libxens 4.1.1-1  Xenstore communications library fo
ii  libxml2 2.7.8.dfsg-3 GNOME XML library

Versions of packages libvirt0 recommends:
ii  lvm2  2.02.84-3  The Linux Logical Volume Manager

libvirt0 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#621358: on logging out and in again kded4 (often?) loops on the CPU

[Luca Tettamanti]

Package: kdelibs-bin
Version: 4:4.6.1-0r3
Followup-For: Bug #621358


Reproduced here.
George Kiagiadakis asked to take a backtrace of all the threads, so here
it is:

(gdb) thread apply all bt

Thread 4 (Thread 0x7fb49246e700 (LWP 8758)):
#0  0x7fb4a9aabc73 in select () at ../sysdeps/unix/syscall-template.S:82
#1  0x7fb4aae9427d in QProcessManager::run (this=0x7fb4ab1ea7e0) at 
io/qprocess_unix.cpp:245
#2  0x7fb4aadcb035 in QThreadPrivate::start (arg=0x7fb4ab1ea7e0) at 
thread/qthread_unix.cpp:320
#3  0x7fb4a75af8ba in start_thread (arg=) at 
pthread_create.c:300
#4  0x7fb4a9ab23cd in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#5  0x in ?? ()

Thread 3 (Thread 0x7fb490890700 (LWP 8766)):
#0  0x7fb4a9aa74b3 in __poll (fds=, nfds=, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x7fb4a6ce99e4 in g_main_context_poll (context=0x23ea790, block=1, 
dispatch=1, self=)
at /tmp/buildd/glib2.0-2.28.4/./glib/gmain.c:3404
#2  g_main_context_iterate (context=0x23ea790, block=1, dispatch=1, self=)
at /tmp/buildd/glib2.0-2.28.4/./glib/gmain.c:3086
#3  0x7fb4a6cea2f2 in g_main_loop_run (loop=0x23ea770) at 
/tmp/buildd/glib2.0-2.28.4/./glib/gmain.c:3299
#4  0x7fb490d6aad4 in gdbus_shared_thread_func (data=)
at /tmp/buildd/glib2.0-2.28.4/./gio/gdbusprivate.c:276
#5  0x7fb4a6d10cf6 in g_thread_create_proxy (data=0x23ea870) at 
/tmp/buildd/glib2.0-2.28.4/./glib/gthread.c:1897
#6  0x7fb4a75af8ba in start_thread (arg=) at 
pthread_create.c:300
#7  0x7fb4a9ab23cd in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#8  0x in ?? ()

Thread 2 (Thread 0x7fb48fe83700 (LWP 8767)):
#0  0xff60013b in ?? ()
#1  0x7fb48fe82ae0 in ?? ()
#2  0x7fffdf9ff782 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 1 (Thread 0x7fb4ac264760 (LWP 8755)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at 
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x7fb4aadcb71b in wait (this=, mutex=0x23f8940, 
time=18446744073709551615)
at thread/qwaitcondition_unix.cpp:88
#2  QWaitCondition::wait (this=, mutex=0x23f8940, 
time=18446744073709551615)
at thread/qwaitcondition_unix.cpp:160
#3  0x7fb4aadca7f0 in QThread::wait (this=, 
time=18446744073709551615)
at thread/qthread_unix.cpp:722
#4  0x7fb4aae882e0 in QFileSystemWatcher::~QFileSystemWatcher (this=, 
__in_chrg=) at io/qfilesystemwatcher.cpp:446
#5  0x7fb4aae883b9 in QFileSystemWatcher::~QFileSystemWatcher 
(this=0x23f8550, __in_chrg=)
at io/qfilesystemwatcher.cpp:462
#6  0x7fb4aaec66d4 in QObjectPrivate::deleteChildren (this=0x23f84b0) at 
kernel/qobject.cpp:1955
#7  0x7fb4aaecb212 in QObject::~QObject (this=0x23f86f0, __in_chrg=)
at kernel/qobject.cpp:946
#8  0x7fb4a3d7fed9 in Solid::Backends::Fstab::FstabWatcher::~FstabWatcher 
(this=0x23f86f0, 
__in_chrg=) at 
../../../solid/solid/backends/fstab/fstabwatcher.cpp:51
#9  0x7fb4a9a195c2 in __run_exit_handlers (status=1, listp=0x7fb4a9d3f4a8, 
run_list_atexit=true) at exit.c:78
#10 0x7fb4a9a19615 in exit (status=37537660) at exit.c:100
#11 0x7fb4aa2c19e8 in qt_xio_errhandler () at 
kernel/qapplication_x11.cpp:772
#12 0x7fb4ab712a2e in _XIOError (dpy=0x22bece0) at ../../src/XlibInt.c:1618
#13 0x7fb4ab710e6e in _XReply (dpy=0x22bece0, rep=0x7fffdf9edf90, 
extra=, 
discard=) at ../../src/xcb_io.c:643
#14 0x7fb4ab6f5bc3 in XGetSelectionOwner (dpy=0x22bece0, selection=)
at ../../src/GetSOwner.c:41
#15 0x7fb4aa2d9788 in QClipboard::event (this=0x22a8a90, e=) at kernel/qclipboard_x11.cpp:922
#16 0x7fb4aa254d14 in QApplicationPrivate::notify_helper (this=0x22a8ae0, 
receiver=0x22a8a90, e=0x7fffdf9ee780)
at kernel/qapplication.cpp:4462
#17 0x7fb4aa2598da in QApplication::notify (this=, 
receiver=0x22a8a90, e=0x7fffdf9ee780)
at kernel/qapplication.cpp:4341
#18 0x7fb4aaeb3c8c in QCoreApplication::notifyInternal 
(this=0x7fffdf9ee860, receiver=0x22a8a90, 
event=0x7fffdf9ee780) at kernel/qcoreapplication.cpp:731
#19 0x7fb4aa25e0bb in sendEvent (this=0x7fffdf9ee860, __in_chrg=)
at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#20 QApplication::~QApplication (this=0x7fffdf9ee860, __in_chrg=) at kernel/qapplication.cpp:1088
#21 0x7fb49a47b77d in ~KDEDApplication (argc=0, argv=0x22314e0) at 
../../kded/kded.cpp:797
#22 kdemain (argc=0, argv=0x22314e0) at ../../kded/kded.cpp:915
#23 0x004074b3 in launch (argc=1, _name=0x40b7ee "kded4", args=, cwd=0x0, 
envc=, envs=, reset_env=false, 
tty=0x0, avoid_loops=false, 
startup_id_str=0x40b676 "0") at ../../kinit/kinit.cpp:746
#24 0x00409e4e in main (argc=4, argv=0x7fffdf9ef978, 
envp=0x7fffdf9ef9a0) at ../../kinit/kinit.cpp:1861

-- System Information:
Debian Release: wheezy/sid
  APT prefers oldstable
  APT policy: (500, 'oldstable'), (500, 'unstable'), (500, 'te

Bug#603620: php-apc: More crashes (squeeze)

[Luca Tettamanti]

Package: php-apc
Version: 3.1.3p1-2
Followup-For: Bug #603620


I'm also seeing many segfaults with squeeze; the backtraces look like this:

(gdb) bt
#0  _zval_ptr_dtor (zval_ptr=0xc9a370) at /tmp/buildd/php5-5.3.3/Zend/zend.h:385
#1  0x7f8e890c3a28 in zend_hash_clean (ht=0x25276b8) at 
/tmp/buildd/php5-5.3.3/Zend/zend_hash.c:753
#2  0x7f8e86f2616b in apc_free_class_entry_after_execution () from 
/usr/lib/php5/20090626/apc.so
#3  0x7f8e86f28bd4 in apc_request_shutdown () from 
/usr/lib/php5/20090626/apc.so
#4  0x7f8e86f1f935 in ?? () from /usr/lib/php5/20090626/apc.so
#5  0x7f8e890b861c in module_registry_cleanup (module=0xc9a370) at 
/tmp/buildd/php5-5.3.3/Zend/zend_API.c:2150
#6  0x7f8e890c35c4 in zend_hash_reverse_apply (ht=0x7f8e897b49c0, 
apply_func=0x7f8e890b8600 )
at /tmp/buildd/php5-5.3.3/Zend/zend_hash.c:957
#7  0x7f8e890b708d in zend_deactivate_modules () at 
/tmp/buildd/php5-5.3.3/Zend/zend.c:938
#8  0x7f8e89062bd5 in php_request_shutdown (dummy=0xc9a370) at 
/tmp/buildd/php5-5.3.3/main/main.c:1623
#9  0x7f8e89143ed7 in php_handler (r=0x7f8e89143ed7) at 
/tmp/buildd/php5-5.3.3/sapi/apache2handler/sapi_apache2.c:526
#10 0x00438f73 in ap_run_handler ()
#11 0x0043c53f in ap_invoke_handler ()
#12 0x0044970e in ap_process_request ()
#13 0x00446838 in ?? ()
#14 0x00440493 in ap_run_process_connection ()
#15 0x0044dd10 in ?? ()
#16 0x0044e064 in ?? ()
#17 0x0044e60c in ap_mpm_run ()
#18 0x00425be5 in main ()


-- System Information:
Debian Release: 5.0.7
  APT prefers stable
  APT policy: (700, 'stable'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26-2-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 php-apc depends on:
ii  libapache2-mod-php5 [phpapi-2 5.3.3-6server-side, HTML-embedded scripti
ii  libc6 2.11.2-7   Embedded GNU C Library: Shared lib
ii  php5-cgi [phpapi-20090626]5.3.3-6server-side, HTML-embedded scripti
ii  php5-cli [phpapi-20090626]5.3.3-6command-line interpreter for the p

php-apc recommends no packages.

Versions of packages php-apc suggests:
ii  php5-gd   5.3.3-6GD module for php5

-- 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#600288: Still seen in 6b18-1.8.2-2

[Luca Tettamanti]

2010/10/20 LEDUQUE Mickaël :
> Hello,
>
> I can still see this bug even after upgrading to 6b18-1.8.2-2.

Hum, yes.
If you upgrade from 6b18-1.8.2-1 javazi data has already been removed,
so it doesn't come back.
Even if you downgrade /usr/lib/jvm/java-6-openjdk/jre/lib/zi remains a
symlink (and the older version shipped with a copy of javazi stuff),
and this confuses the upgrade.
When installing after a purge from either versions everything is fine.

I also found out that "aptitude reinstall tzdata-java" fixes the issue.

Luca



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#600288: Debug session

[Luca Tettamanti]

Debugging the test program it seems that the problem is a missing
ZoneInfoMappings file.
The stack trace is:

Thread [main] (Suspended)   
ZoneInfoFile$2.run() line: 1075 
ZoneInfoFile$2.run() line: 1073 
AccessController.doPrivileged(PrivilegedExceptionAction) line: not
available [native method]
ZoneInfoFile.readZoneInfoFile(String) line: 1073
ZoneInfoFile.getZoneInfoMappings() line: 1042   
ZoneInfoFile.getZoneIDs() line: 783 
ZoneInfo.getAvailableIDs() line: 535
TimeZone.getAvailableIDs() line: 514
tztest.main(String[]) line: 3   


readZoneInfoFile opens this file:
/usr/share/javazi/ZoneInfoMappings
which does not exists; the null return value is propagated up to
getZoneIDs, leading to the NullPointerException.
That file is indeed present in the older package:

# ls /usr/share/javazi/
Africa   Antarctica  Atlantic   CET  EET  EST5EDT  Europe  HST
MET  MST7MDT  PST8PDT  WET
America  AsiaAustralia  CST6CDT  EST  Etc  GMT Indian
MST  Pacific  SystemV  ZoneInfoMappings

# dpkg -S /usr/share/javazi/ZoneInfoMappings
tzdata-java: /usr/share/javazi/ZoneInfoMappings

Hum. So upgrading the openjdk packages somehow deletes files from
another package...

[upgrade]
Unpacking replacement openjdk-6-jre-lib ...
dpkg: warning: unable to delete old directory
'/usr/lib/jvm/java-6-openjdk/jre/lib/zi/Antarctica': Directory not
empty
dpkg: warning: unable to delete old directory
'/usr/lib/jvm/java-6-openjdk/jre/lib/zi/Pacific': Directory not empty
dpkg: warning: unable to delete old directory
'/usr/lib/jvm/java-6-openjdk/jre/lib/zi/America': Directory not empty

# ls /usr/share/javazi
America  Antarctica  Pacific

The preinst file of openjdk-6-jre-lib shows:

with_tzdata=yes

if [ "$with_tzdata" = yes ]; then
if [ ! -h /usr/lib/jvm/java-6-openjdk/jre/lib/zi ] && [ -d
/usr/lib/jvm/java-6-openjdk/jre/lib/zi ]; then
rm -rf /usr/lib/jvm/java-6-openjdk/jre/lib/zi
fi
fi

But, even with 6b18-1.8.1-2 installed that directory is a symlink;

# ll /usr/lib/jvm/java-6-openjdk/jre/lib/zi
lrwxrwxrwx 1 root root 27 Oct 15 17:19
/usr/lib/jvm/java-6-openjdk/jre/lib/zi -> ../../../../../share/javazi

The rm -rf should not be triggered. Double hum :)

Luca



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#600288: workaround

[Luca Tettamanti]

I'm aware of the workaround (see the first post). However there's no
need to repack the JAR: just add

-Dcom.ibm.icu.util.TimeZone.DefaultTimeZoneType=ICU

to eclipse.ini

Luca



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#600288: eclipse: Could not initialize class com.ibm.icu.impl.JavaTimeZone

[Luca Tettamanti]

Package: openjdk-6-jre
Version: 6b18-1.8.2-1
Severity: normal

Hello,
after upgrading from 6b18-1.8.1-2 eclipse (3.6) misbehaves in various
areas (run configuration, debugging, project properties); the common
underlying cause seems to be:

!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.jface".
!STACK 0
java.lang.NoClassDefFoundError: Could not initialize class 
com.ibm.icu.impl.JavaTimeZone
at com.ibm.icu.util.TimeZone.getDefault(TimeZone.java:679)
at com.ibm.icu.util.Calendar.getInstanceInternal(Calendar.java:1633)
at com.ibm.icu.util.Calendar.getInstance(Calendar.java:1597)
at com.ibm.icu.text.DateFormat.get(DateFormat.java:1255)
at com.ibm.icu.text.DateFormat.getDateTimeInstance(DateFormat.java:1045)
at 
org.eclipse.ui.internal.ide.dialogs.IDEResourceInfoUtils.getDateStringValue(IDEResourceInfoUtils.java:137)
at 
org.eclipse.ui.internal.ide.dialogs.ResourceInfoPage.createBasicInfoGroup(ResourceInfoPage.java:308)
at 
org.eclipse.ui.internal.ide.dialogs.ResourceInfoPage.createContents(ResourceInfoPage.java:405)
at 
org.eclipse.jface.preference.PreferencePage.createControl(PreferencePage.java:232)
at 
org.eclipse.jface.preference.PreferenceDialog.createPageControl(PreferenceDialog.java:1501)
at 
org.eclipse.jface.preference.PreferenceDialog$14.run(PreferenceDialog.java:1258)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
at 
org.eclipse.jface.preference.PreferenceDialog.showPage(PreferenceDialog.java:1252)
at 
org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.showPage(FilteredPreferenceDialog.java:673)
at 
org.eclipse.jface.preference.PreferenceDialog$10.run(PreferenceDialog.java:708)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at 
org.eclipse.jface.preference.PreferenceDialog$9.selectionChanged(PreferenceDialog.java:704)
at 
org.eclipse.jface.viewers.StructuredViewer$3.run(StructuredViewer.java:867)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
at 
org.eclipse.jface.viewers.StructuredViewer.firePostSelectionChanged(StructuredViewer.java:865)
at 
org.eclipse.jface.viewers.StructuredViewer.setSelection(StructuredViewer.java:1700)
at 
org.eclipse.jface.viewers.TreeViewer.setSelection(TreeViewer.java:1139)
at 
org.eclipse.jface.preference.PreferenceDialog.selectSavedItem(PreferenceDialog.java:1054)
at 
org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.selectSavedItem(FilteredPreferenceDialog.java:728)
at 
org.eclipse.jface.preference.PreferenceDialog$4.run(PreferenceDialog.java:375)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at 
org.eclipse.jface.preference.PreferenceDialog.createContents(PreferenceDialog.java:371)
at org.eclipse.jface.window.Window.create(Window.java:431)
at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1089)
at 
org.eclipse.ui.internal.dialogs.PropertyDialog.createDialogOn(PropertyDialog.java:82)
at 
org.eclipse.ui.dialogs.PropertyDialogAction.createDialog(PropertyDialogAction.java:176)
at 
org.eclipse.ui.dialogs.PropertyDialogAction.run(PropertyDialogAction.java:155)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
at 
org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
at 
org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
at 
org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3540)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3161)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671)
at 
org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at 
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at 
org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115)
at 
org.eclipse.equ

Bug#595023: doesn't seem to support multiple bind addresses

[Luca Tettamanti]

Package: apt-cacher-ng
Version: 0.2.2-2
Severity: normal


Just hit this bug :s
The problem is in the perl script
(/usr/lib/apt-cacher-ng/expire-caller.pl), in the part where it parses
the configuration files.

It parses each line into key+value pairs:

  ($key, $value) = split(/\s*:\s*/);

And then builds the map:

  $cfg{$key}=$value;
 
BindAddress might list more than one value in the "value" part, but the
script treats it like a single string - which is likely an invalid
hostname.
The address is used to contact the daemon (conTcp), so in this case it
should be acceptable to add a special case to use only the first address
listed.

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.36-rc4 (SMP w/2 CPU cores; PREEMPT)
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#587583: 4.4.0-2 does not work here: charon seems not to ignore all incoming requests/answers

[Luca Tettamanti]

Package: strongswan
Severity: normal


Confirmed here: after upgrade from 4.3.2-1.3 charon is not working;
pluto (IKEv1 seems fine though).
It's not a networking problem, the packets are coming through, but the
daemon does not "see" them:

IP 111.111.111.111.isakmp > 222.222.222.222.isakmp: isakmp: parent_sa 
ikev2_init[I]
IP 222.222.222.222.isakmp > 111.111.111.111.isakmp: isakmp: parent_sa 
ikev2_init[R]
(nothing happens, the local machine retries)
IP 111.111.111.111.isakmp > 222.222.222.222.isakmp: isakmp: parent_sa 
ikev2_init[I]
IP 222.222.222.222.isakmp > 111.111.111.111.isakmp: isakmp: parent_sa 
ikev2_init[R]
(again...)
IP 111.111.111.111.isakmp > 222.222.222.222.isakmp: isakmp: parent_sa 
ikev2_init[I]
IP 222.222.222.222.isakmp > 111.111.111.111.isakmp: isakmp: parent_sa 
ikev2_init[R]
(etc)

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.35 (SMP w/2 CPU cores; PREEMPT)
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 strongswan depends on:
ii  strongswan-ikev1  4.4.0-2strongSwan Internet Key Exchange (
ii  strongswan-ikev2  4.4.0-2strongSwan Internet Key Exchange (

strongswan recommends no packages.

Versions of packages strongswan suggests:
pn  network-manager-strongswan (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#588964: [Pkg-libvirt-maintainers] Bug#588964: virt-manager: Screenshot

[Luca Tettamanti]

On Fri, Jul 16, 2010 at 9:15 AM, Guido Günther  wrote:
> Hi Luca,
> On Thu, Jul 15, 2010 at 10:33:10PM +0200, Luca Tettamanti wrote:
>> Package: virt-manager
>> Version: 0.8.4-6
>> Severity: normal
>>
>> Attaching a screenshot.
> Could you check if installing (and using) gnome-icon-theme fixes your problem?

Hi,
I've upgraded gnome-icon-theme to the latest version (from 2.22) and
now I see the icons (the same one for all the 4 buttons, is this
correct?).
I'm running KDE4 BTW, the icons are there even with default oxygen icon theme.

Luca



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#588964: virt-manager: Screenshot

[Luca Tettamanti]

Package: virt-manager
Version: 0.8.4-6
Severity: normal

Attaching a screenshot.

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.35-rc5-dirty (SMP w/2 CPU cores; PREEMPT)
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 virt-manager depends on:
ii  gconf2   2.28.1-3GNOME configuration database syste
ii  librsvg2-common  2.26.3-1SAX-based renderer library for SVG
ii  python   2.6.5-7 interactive high-level object-orie
ii  python-dbus  0.83.1-1simple interprocess messaging syst
ii  python-glade22.17.0-2GTK+ bindings: Glade support
ii  python-gnome22.28.1-1Python bindings for the GNOME desk
ii  python-gtk-vnc   0.3.10-6+b1 A VNC viewer widget for GTK+ (Pyth
ii  python-gtk2  2.17.0-2Python bindings for the GTK+ widge
ii  python-libvirt   0.8.2-1 libvirt Python bindings
ii  python-support   1.0.9   automated rebuilding support for P
ii  python-urlgrabber3.1.0-5 A high-level cross-protocol url-gr
ii  python-vte   1:0.24.1-1  Python bindings for the VTE widget
ii  virtinst 0.500.3-2   Programs to create and clone virtu

Versions of packages virt-manager recommends:
ii  libvirt-bin   0.8.2-1the programs for the libvirt libra

Versions of packages virt-manager suggests:
pn  virt-viewer(no description available)

-- no debconf information
<>

Bug#588434: libpam-ldap: unable to change password

[Luca Tettamanti]

Package: libpam-ldap
Version: 184-8.4
Severity: normal


Hello,
after installing the package it's not possible to change the password
stored on the LDAP server:

$ passwd
Enter login(LDAP) password: 
passwd: Authentication information cannot be recovered
passwd: password unchanged

syslog reports:

passwd[23595]: pam_unix(passwd:chauthtok): user "tettamanti" does not exist in 
/etc/passwd

This is the content of common-password, as generated by pam-auth-update:

# here are the per-package modules (the "Primary" block)
password[success=2 default=ignore]  pam_unix.so obscure sha512
password[success=1 user_unknown=ignore default=die] pam_ldap.so 
use_authtok try_first_pass
# here's the fallback if no module succeeds

The problem seems (my knowledge of PAM is rather limited) to be the
use_authtok option: the users of the system are *not* present in
/etc/password, they exist only on LDAP.
I guess that use_authtok was put there to keep local data in sync with
LDAP, right?
In this case what's needed is the equivalent of try_first_pass for for
password changing (but I don't see such an option).

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-3-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/dash

Versions of packages libpam-ldap depends on:
ii  debconf [debconf-2.0] 1.5.32 Debian configuration management sy
ii  libc6 2.10.2-9   Embedded GNU C Library: Shared lib
ii  libldap-2.4-2 2.4.17-2.1 OpenLDAP libraries
ii  libpam-runtime1.1.1-3Runtime support for the PAM librar
ii  libpam0g  1.1.1-3Pluggable Authentication Modules l

libpam-ldap recommends no packages.

Versions of packages libpam-ldap suggests:
ii  libnss-ldap   264-2.1NSS module for using LDAP as a nam

-- debconf information excluded



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#578398: megasas: Failed to copy out to user sense data

[Luca Tettamanti]

Package: linux-2.6
Version: 2.6.32-9
Severity: normal


The kernel 2.6.32 is affected by the following bug:

http://bugzilla.kernel.org/show_bug.cgi?id=15001

The issue is caused by a 32 bit application (omreport - from Dell Open
Manage suite) with a 64 bit OS.
The fix is already available upstream, with this commit:

commit b3dc1a212e5167984616445990c76056034f8eeb
Author: Tomas Henzl 
Date:   Thu Feb 11 18:01:50 2010 +0100

[SCSI] megaraid_sas: fix for 32bit apps

Is it possible to backport the patch to Debian kernel?


-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: Dell Inc.
product_name: PowerEdge 2900
product_version: 
chassis_vendor: Dell Inc.
chassis_version: 
bios_vendor: Dell Inc.
bios_version: 2.5.0
board_vendor: Dell Inc.
board_name: 0YM158
board_version: A02

** PCI devices:
[cut - not really relevant]

02:0e.0 RAID bus controller [0104]: Dell PowerEdge Expandable RAID controller 5 
[1028:0015]
Subsystem: Dell PERC 5/i Integrated RAID Controller [1028:1f03]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr+ 
Stepping+ SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: megaraid_sas
Kernel modules: megaraid_sas

** USB devices:
Bus 003 Device 002: ID 0624:0294 Avocent Corp. 
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 003: ID 04b4:6560 Cypress Semiconductor Corp. CY7C65640 USB-2.0 
"TetraHub"
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


-- System Information:
Debian Release: 5.0.4
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'oldstable'), (500, 'unstable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-3-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 linux-image-2.6.32-3-amd64 depends on:
ii  debconf [debconf-2.0] 1.5.24 Debian configuration management sy
ii  initramfs-tools [linux-initra 0.92o  tools for generating an initramfs
ii  module-init-tools 3.4-1  tools for managing Linux kernel mo

Versions of packages linux-image-2.6.32-3-amd64 recommends:
ii  firmware-linux-free   2.6.32-10  Binary firmware for various driver

Versions of packages linux-image-2.6.32-3-amd64 suggests:
ii  grub   0.97-47lenny2 GRand Unified Bootloader (Legacy v
pn  linux-doc-2.6.32   (no description available)

Versions of packages linux-image-2.6.32-3-amd64 is related to:
ii  firmware-bnx2 0.23   Binary firmware for Broadcom NetXt
pn  firmware-bnx2x (no description available)
pn  firmware-ipw2x00   (no description available)
pn  firmware-ivtv  (no description available)
pn  firmware-iwlwifi   (no description available)
pn  firmware-linux (no description available)
ii  firmware-linux-nonfree0.23   Binary firmware for various driver
pn  firmware-qlogic(no description available)
pn  firmware-ralink(no description available)

-- debconf information excluded



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#574355: openjdk-6-jdk: eclipse networking failure

[Luca Tettamanti]

Package: openjdk-6-jdk
Version: 6b18~pre2-1
Severity: normal

This might be related to #560056, but it's not directly caused by
bindv6only (it happens with either setting).
Instead I suspect that it's caused by the workaround for that bug
(ipv4-mapped-ipv6-addresses.diff)

I'm using eclipse 3.5 SR1 (from upstream) and when trying to connect to
the software repositories I get:

!ENTRY org.eclipse.equinox.p2.ui 4 0 2010-03-17 15:51:45.812
!MESSAGE Unable to load the repository 
http://download.eclipse.org/releases/galileo
!STACK 1
[cut]
Caused by: java.net.ConnectException: Invalid argument
at java.net.PlainSocketImpl.socketConnect(Native Method)
at 
java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:310)
at 
java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:176)
at 
java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:163)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:384)
at java.net.Socket.connect(Socket.java:542)
[cut]

With strace I see lots of:

4976  socket(PF_INET6, SOCK_STREAM, IPPROTO_IP) = 90
4976  setsockopt(90, SOL_IPV6, IPV6_V6ONLY, [0], 4) = -1 EINVAL (Invalid 
argument)
4976  close(90) = 0

Sun JVM works (at least with bindv6only=0)

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.33 (SMP w/2 CPU cores; PREEMPT)
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 openjdk-6-jdk depends on:
ii  dpkg1.15.5.6 Debian package management system
ii  libc6   2.10.2-6 Embedded GNU C Library: Shared lib
ii  libx11-62:1.3.3-2X11 client-side library
ii  openjdk-6-jre   6b18~pre2-1  OpenJDK Java runtime, using Hotspo
ii  zlib1g  1:1.2.3.4.dfsg-3 compression library - runtime

Versions of packages openjdk-6-jdk recommends:
ii  libxt-dev 1:1.0.7-1  X11 toolkit intrinsics library (de

Versions of packages openjdk-6-jdk suggests:
pn  openjdk-6-demo (no description available)
pn  openjdk-6-source   (no description available)
pn  visualvm   (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#569332: xserver-xorg-video-radeon: KMS/UMS confusion and hangup if radeon.ko was not loaded before starting X

[Luca Tettamanti]

On Thu, Feb 11, 2010 at 3:13 PM, Piotr Engelking  wrote:
> Package: xserver-xorg-video-radeon
> Version: 1:6.12.99+git20100201.a887818f-1
> Severity: important
>
> With upstream kernel 2.6.33-rc7, starting X while the KMS-enabled
> 'radeon' kernel module is not loaded yet results in the kernel using
> KMS and the X server using UMS. Pressing Ctrl+Alt+F1 while in X results
> in hangup: the monitor stops receiving video signal and the X server
> stops reacting to keypresses. Killing the X server restores the console
> to an usable state.

The problem is known, there's also a proposed patch floating around
[1]; as a workaround you can add radeon to /etc/modules so that it's
loaded at boot.
Might be tagged as duplicate of #569098...

Luca
[1] http://permalink.gmane.org/gmane.comp.freedesktop.xorg.drivers.ati/12853



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#565983: [Pkg-libvirt-maintainers] Bug#565983: libvirt-bin: libvirtd crashes when accessed through virt-manager

[Luca Tettamanti]

On Mon, Jan 25, 2010 at 06:13:08PM +0100, Luca Tettamanti wrote:
> More in details:
> 
> (gdb)
> make_nonnull_node_device (server=, client= optimized out>, conn=0x714d60,
> hdr=, rerr=0x7fffef610e20, args= out>, ret=0x7fffef610e70) at remote.c:5401
> 5401dev_dst->name = strdup(dev_src->name);
> (gdb) p dev_dst
> $4 = 
> (gdb) s
> *__GI___strdup (s=0x5f74736f685f6973  bounds>) at strdup.c:41
> (gdb) l
> 36  #endif
> 37
> 38  /* Duplicate S, returning an identical malloc'd string.  */
> 39  char *
> 40  __strdup (const char *s)
> 41  {
> 42size_t len = strlen (s) + 1;
> 43void *new = malloc (len);
> 44
> 45if (new == NULL)
> (gdb) p s
> $5 = 0x5f74736f685f6973 
> 
> So... virNodeDeviceLookupByName returns corrupted data?

Yep.

virGetNodeDevice (conn=0x6dcae0, name=0x6d3120 "storage_model_DVD_RAM_UJ_850S") 
at datatypes.c:1056
1056{
[cut]
1065ret = (virNodeDevicePtr) virHashLookup(conn->nodeDevices, name);
(gdb)
1066if (ret == NULL) {
(gdb) p ret
$26 = (virNodeDevicePtr) 0x0
(gdb) p ret
$28 = (virNodeDevicePtr) 0x6d2570
(gdb) p *ret
$29 = {magic = 1601463662, refs = 1886220131, conn = 0x6f6f6c5f72657475,
  name = 0x6b63616270 , parent = 0x0}

So, somehow the hashmap contains a node with corrupted ->name; I tried setting
a watchpoint on ->name, but the node is deallocated almost immediatly in
remoteDispatchNodeDeviceLookupByName.

L



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#565983: [Pkg-libvirt-maintainers] Bug#565983: libvirt-bin: libvirtd crashes when accessed through virt-manager

[Luca Tettamanti]

On Mon, Jan 25, 2010 at 04:13:38PM +0100, Guido Günther wrote:
> On Fri, Jan 22, 2010 at 03:03:47PM +0100, Luca Tettamanti wrote:
> > #2  0x0041d1ff in remoteDispatchNodeDeviceLookupByName
> > (server=, client=,
> > conn=0x14ea030, hdr=, rerr=0x7f8115bb7e30,
> > args=, ret=0x7f8115bb7e80)
> > at remote.c:5401
> This seems to be in the device enumeration code.

Hum, it crashes the second time (same connection) it asks about my DVD unit
(I'm testing locally).

Breakpoint 1, remoteDispatchNodeDeviceLookupByName (server=0x6c6250, 
client=0x6def00, conn=0x6e3a40, hdr=0x75d210,
rerr=0x7fffede0de20, args=0x7fffede0ddd0, ret=0x7fffede0de70) at 
remote.c:4461
4461{
(gdb) p *args
$81 = {name = 0x6e4250 "storage_model_DVD_RAM_UJ_850S"}
(gdb) c
Continuing.

Program received signal SIGSEGV, Segmentation fault.
strlen () at ../sysdeps/x86_64/strlen.S:31
31  ../sysdeps/x86_64/strlen.S: No such file or directory.
in ../sysdeps/x86_64/strlen.S
Current language:  auto
The current source language is "auto; currently asm".

More in details:

(gdb)
make_nonnull_node_device (server=, client=, conn=0x714d60,
hdr=, rerr=0x7fffef610e20, args=, 
ret=0x7fffef610e70) at remote.c:5401
5401dev_dst->name = strdup(dev_src->name);
(gdb) p dev_dst
$4 = 
(gdb) s
*__GI___strdup (s=0x5f74736f685f6973 ) at strdup.c:41
(gdb) l
36  #endif
37
38  /* Duplicate S, returning an identical malloc'd string.  */
39  char *
40  __strdup (const char *s)
41  {
42size_t len = strlen (s) + 1;
43void *new = malloc (len);
44
45if (new == NULL)
(gdb) p s
$5 = 0x5f74736f685f6973 

So... virNodeDeviceLookupByName returns corrupted data?
Might be related to "invalid node device pointer in virNodeDeviceFree"?

L



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#565983: [Pkg-libvirt-maintainers] Bug#565983: libvirt-bin: libvirtd crashes when accessed through virt-manager

[Luca Tettamanti]

On Fri, Jan 22, 2010 at 1:21 PM, Guido Günther  wrote:
>
> - Ursprüngliche Mitteilung -
>> On Thu, Jan 21, 2010 at 11:49:47PM +0100, Laurent Léonard wrote:
>> > Le jeudi 21 janvier 2010 à 23:16, Luca Tettamanti a écrit :
>> > > I encountered the same problem on my machine. The bug appeared after a
>> > > recent upgrade, I've downgraded to 0.7.5-4 and I can connect with
>> > > virt-manager again.
>> >
>> > I noticed libvirt only crashed at the first connection with Virt-manager. 
>> > If I
>> > start libvirt again and try to reconnect it works. I can confirm all Debian
>> > revisions of libvirt 0.7.5 are affected by that bug.
>> >
>> > See the upstream bug report 
>> > https://bugzilla.redhat.com/show_bug.cgi?id=556815
>> > for more informations.
>>
>> The stack trace matches what I'm seeing on my machine, however 0.7.5-4 works
>> fine here. I only connect via ssh though.
> The trace lacks the glibc part (libc6-dbg).

Yeah, this is production machine...

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7f8115bb8910 (LWP 17259)]
strlen () at ../sysdeps/x86_64/strlen.S:31
31  ../sysdeps/x86_64/strlen.S: No such file or directory.
in ../sysdeps/x86_64/strlen.S
Current language:  auto; currently asm
(gdb) bt
#0  strlen () at ../sysdeps/x86_64/strlen.S:31
#1  0x7f8119508516 in *__GI___strdup (s=0x63735f74736f6850
) at strdup.c:42
#2  0x0041d1ff in remoteDispatchNodeDeviceLookupByName
(server=, client=,
conn=0x14ea030, hdr=, rerr=0x7f8115bb7e30,
args=, ret=0x7f8115bb7e80)
at remote.c:5401
#3  0x00424ab1 in remoteDispatchClientCall (server=, client=0x7f810c000ac0, msg=0x7f810c000c10)
at dispatch.c:506
#4  0x00424e63 in remoteDispatchClientRequest
(server=0x14c7570, client=0x7f810c000ac0, msg=0x7f810c000c10)
at dispatch.c:388
#5  0x0041826c in qemudWorker (data=) at
libvirtd.c:1522
#6  0x7f81197e973a in start_thread (arg=) at
pthread_create.c:300
#7  0x7f811955a6dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#8  0x in ?? ()
(gdb) disas
Dump of assembler code for function strlen:
0x7f81195087b0 :  mov%rdi,%rcx
0x7f81195087b3 :  mov%rdi,%r8
0x7f81195087b6 :  and$0xfff0,%rdi
0x7f81195087ba : pxor   %xmm1,%xmm1
0x7f81195087be : or $0x,%esi
0x7f81195087c1 : movdqa (%rdi),%xmm0
0x7f81195087c5 : sub%rdi,%rcx
0x7f81195087c8 : lea0x10(%rdi),%rdi
0x7f81195087cc : pcmpeqb %xmm1,%xmm0
0x7f81195087d0 : shl%cl,%esi
0x7f81195087d2 : pmovmskb %xmm0,%edx
0x7f81195087d6 : xor%eax,%eax
0x7f81195087d8 : neg%r8
0x7f81195087db : and%esi,%edx
0x7f81195087dd : jne0x7f81195087f3 
0x7f81195087df : movdqa (%rdi),%xmm0
0x7f81195087e3 : lea0x10(%rdi),%rdi
0x7f81195087e7 : pcmpeqb %xmm1,%xmm0
0x7f81195087eb : pmovmskb %xmm0,%edx
0x7f81195087ef : test   %edx,%edx
0x7f81195087f1 : je 0x7f81195087df 
0x7f81195087f3 : lea-0x10(%rdi,%r8,1),%rdi
0x7f81195087f8 : bsf%edx,%eax
0x7f81195087fb : add%rdi,%rax
0x7f81195087fe : retq
End of assembler dump.

strdup is called by make_nonnull_node_device (which is inlined):
dev_dst->name = strdup(dev_src->name);

Luca



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#565983: libvirt-bin: libvirtd crashes when accessed through virt-manager

[Luca Tettamanti]

On Thu, Jan 21, 2010 at 11:49:47PM +0100, Laurent Léonard wrote:
> Le jeudi 21 janvier 2010 à 23:16, Luca Tettamanti a écrit :
> > I encountered the same problem on my machine. The bug appeared after a
> > recent upgrade, I've downgraded to 0.7.5-4 and I can connect with
> > virt-manager again.
> 
> I noticed libvirt only crashed at the first connection with Virt-manager. If 
> I 
> start libvirt again and try to reconnect it works. I can confirm all Debian 
> revisions of libvirt 0.7.5 are affected by that bug.
> 
> See the upstream bug report 
> https://bugzilla.redhat.com/show_bug.cgi?id=556815 
> for more informations.

The stack trace matches what I'm seeing on my machine, however 0.7.5-4 works
fine here. I only connect via ssh though.

Luca



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#565983: [Pkg-libvirt-maintainers] Bug#565983: libvirt-bin: libvirtd crashes when accessed through virt-manager

[Luca Tettamanti]

On Fri, Jan 22, 2010 at 9:22 AM, Guido Günther  wrote:
> On Thu, Jan 21, 2010 at 11:16:30PM +0100, Luca Tettamanti wrote:
>> Package: libvirt-bin
>> Version: 0.7.5-4
>> Followup-For: Bug #565983
>>
>> Hello,
>> I encountered the same problem on my machine. The bug appeared after a 
>> recent upgrade,
>> I've downgraded to 0.7.5-4 and I can connect with virt-manager again.
> Could somebody please add a gdb backtrace?

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7f860b001910 (LWP 3755)]
0x7f860e9517c1 in strlen () from /lib/libc.so.6
(gdb) bt
#0  0x7f860e9517c1 in strlen () from /lib/libc.so.6
#1  0x7f860e951516 in strdup () from /lib/libc.so.6
#2  0x0041d1ff in remoteDispatchNodeDeviceLookupByName
(server=, client=,
conn=0x1390eb0, hdr=, rerr=0x7f860b000e30,
args=, ret=0x7f860b000e80)
at remote.c:5401
#3  0x00424ab1 in remoteDispatchClientCall (server=, client=0x13b5c20, msg=0x13ed170)
at dispatch.c:506
#4  0x00424e63 in remoteDispatchClientRequest
(server=0x1394570, client=0x13b5c20, msg=0x13ed170) at dispatch.c:388
#5  0x0041826c in qemudWorker (data=) at
libvirtd.c:1522
#6  0x7f860ec3273a in start_thread () from /lib/libpthread.so.0
#7  0x7f860e9a36dd in clone () from /lib/libc.so.6
#8  0x in ?? ()

I'm connecting via qemu+ssh.
Additional information: the daemon crashes only on the first
connection; if I restart it and retry then virt-manager can connect.
However if I close virt-manager and reconnect libvirt dies again.

HTH,
Luca



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#565983: libvirt-bin: libvirtd crashes when accessed through virt-manager

[Luca Tettamanti]

Package: libvirt-bin
Version: 0.7.5-4
Followup-For: Bug #565983

Hello,
I encountered the same problem on my machine. The bug appeared after a recent 
upgrade,
I've downgraded to 0.7.5-4 and I can connect with virt-manager again.

-- System Information:
Debian Release: 5.0.3
  APT prefers stable
  APT policy: (700, 'stable'), (600, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-trunk-amd64 (SMP w/16 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 libvirt-bin depends on:
ii  adduser   3.110  add and remove users and groups
ii  hal   0.5.11-8   Hardware Abstraction Layer
ii  libavahi-client3  0.6.23-3lenny1 Avahi client library
ii  libavahi-common3  0.6.23-3lenny1 Avahi common library
ii  libc6 2.10.2-5   Embedded GNU C Library: Shared lib
ii  libcap-ng00.6.2-4An alternate posix capabilities li
ii  libdevmapper1.02. 2:1.02.27-4The Linux Kernel Device Mapper use
ii  libgcrypt11   1.4.5-1LGPL Crypto library - runtime libr
ii  libgnutls26   2.8.5-2the GNU TLS library - runtime libr
ii  libparted1.8-12   1.8.8.git.2009.07.19-5 The GNU Parted disk partitioning s
ii  libpciaccess0 0.10.3-1   Generic PCI access library for X
ii  libreadline6  6.1-1  GNU readline and history libraries
ii  libsasl2-22.1.23.dfsg1-5 Cyrus SASL - authentication abstra
ii  libudev0  150-2  libudev shared library
ii  libuuid1  2.16.2-0   Universally Unique ID library
ii  libvirt0  0.7.5-4library for interfacing with diffe
ii  libxenstore3.03.2.1-2Xenstore communications library fo
ii  libxml2   2.7.6.dfsg-1   GNOME XML library
ii  logrotate 3.7.1-5Log rotation utility

Versions of packages libvirt-bin recommends:
ii  bridge-utils   1.4-5 Utilities for configuring the Linu
ii  dnsmasq-base   2.45-1+lenny1 A small caching DNS proxy and DHCP
ii  iptables   1.4.2-6   administration tools for packet fi
ii  netcat-openbsd 1.89-3TCP/IP swiss army knife
pn  qemu   (no description available)

Versions of packages libvirt-bin suggests:
pn  policykit-1(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#561472: iceweasel: Wrong "what's new" URL

[Luca Tettamanti]

On Thu, Dec 17, 2009 at 2:28 PM, Mike Hommey  wrote:
> On Thu, Dec 17, 2009 at 02:19:30PM +0100, Luca Tettamanti wrote:
>> Package: iceweasel
>> Version: 3.5.6-1
>> Severity: minor
>>
>> Hello,
>> after an update iceweasel opens this "What's new" page:
>>
>> http://en-us.www.mozilla.com/en-US/iceweasel/3.5.6/whatsnew/
>>
>> which does not exists. The correct URL contains "firefox" as product name:
>>
>> http://en-us.www.mozilla.com/en-US/firefox/3.5.6/whatsnew/
>
> Arguably, none of the above is correct.

Hum, ok the Debian package may contain other modifications but I
suppose that it has _at least_ the changes from the upstream package.
And the second URL does not result in a 404 ;-)

Luca



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#561472: iceweasel: Wrong "what's new" URL

[Luca Tettamanti]

Package: iceweasel
Version: 3.5.6-1
Severity: minor

Hello,
after an update iceweasel opens this "What's new" page:

http://en-us.www.mozilla.com/en-US/iceweasel/3.5.6/whatsnew/

which does not exists. The correct URL contains "firefox" as product name:

http://en-us.www.mozilla.com/en-US/firefox/3.5.6/whatsnew/

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32 (SMP w/2 CPU cores; PREEMPT)
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 iceweasel depends on:
ii  debianutils   3.2.2  Miscellaneous utilities specific t
ii  fontconfig2.6.0-4generic font configuration library
ii  libc6 2.10.1-2   GNU C Library: Shared libraries
ii  libglib2.0-0  2.22.3-1   The GLib library of C routines
ii  libgtk2.0-0   2.18.3-1   The GTK+ graphical user interface 
ii  libnspr4-0d   4.8.2-1NetScape Portable Runtime Library
ii  libstdc++64.4.2-5The GNU Standard C++ Library v3
ii  procps1:3.2.8-2  /proc file system utilities
ii  psmisc22.8-1 utilities that use the proc file s
ii  xulrunner-1.9.1   1.9.1.6-1  XUL + XPCOM application runner

iceweasel recommends no packages.

Versions of packages iceweasel suggests:
ii  latex-xft-fonts 1.6.4-1  TrueType versions of some TeX font
ii  libkrb531.6.dfsg.4~beta1-5lenny1 MIT Kerberos runtime libraries
ii  mozplugger  1.13.0-1 Plugin allowing external viewers t
pn  ttf-mathematica(no description available)
ii  xfonts-mathml   3Type1 Symbol font for MathML
pn  xprint (no description available)
pn  xulrunner-1.9.1(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#559356: [Pkg-libvirt-maintainers] Bug#559356: libvirt-bin: libvirtd fails to start (SELinux)

[Luca Tettamanti]

On Fri, Dec 4, 2009 at 10:33 AM, Guido Günther  wrote:
> Hi Luca,
> On Thu, Dec 03, 2009 at 10:41:04PM +0100, Luca Tettamanti wrote:
>> Package: libvirt-bin
>> Version: 0.7.4-1
>> Severity: normal
>>
>> Hello,
>> libvirtd fails to start when SELinux is active on the system; this the
>> output of the program:
>>
>> 22:31:41.249: warning : qemudStartup:907 : Unable to create cgroup for 
>> driver: No such device or address
>> 22:31:41.311: error : SELinuxInitialize:115 : cannot open SELinux virtual 
>> domain context file '/etc/selinux/default/contexts/virtual_domain_context': 
>> No such file or directory
>> 22:31:41.311: error : qemudSecurityInit:764 : Failed to start security driver
>> 22:31:41.311: error : virStateInitialize:832 : Initialization of QEMU state 
>> driver failed
>> 22:31:41.312: error : main:3155 : Driver state initialization failed
>> 22:31:41.312: warning : qemudDispatchSignalEvent:383 : Shutting down on 
>> signal 3
>>
>> /etc/selinux/default/contexts/virtual_domain_context is not provided by the
>> selinux-policy-default package...
> Fedora has it though:
>
> http://cvs.fedoraproject.org/viewvc//rpms/selinux-policy/F-12/selinux-policy.spec?view=markup
>
> Since I'm not running SELinux: could you have a look at the Fedora
> policy and see if the files are suitable?

With both virtual_domain_context and virtual_image_context from F12
the daemon starts, but then I'm unable to start any VM:

ERRORinternal error unable to start guest: libvir: Security
Labeling error : unable to set security context
'system_u:system_r:svirt_t:s0:c206,c208': Invalid argument
libvir: Security Labeling error : unable to set security context
'system_u:object_r:svirt_image_t:s0:c206,c208' on
'/var/lib/libvirt/images/winxp-am.img': Invalid argument

I have virt.pp loaded, and the operation fails even with SELinux in
permissive mode :(
I'm unable to load virt.pp from F-12, it seems that other modules are required:

libsepol.permission_copy_callback: Module virt depends on permission
module_request in class system, not satisfied (No such file or
directory).
libsemanage.semanage_link_sandbox: Link packages failed (No such file
or directory).
semodule:  Failed!

I'm not _that_ expert with SELinux (and I'd rather not mess up my
server too much...), you may want to disable selinux support in the
package at least until an appropriate policy is available... feel free
to bounce this bug to the selinux guys.

Luca



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#559356: libvirt-bin: libvirtd fails to start (SELinux)

[Luca Tettamanti]

Package: libvirt-bin
Version: 0.7.4-1
Severity: normal

Hello,
libvirtd fails to start when SELinux is active on the system; this the
output of the program:

22:31:41.249: warning : qemudStartup:907 : Unable to create cgroup for driver: 
No such device or address
22:31:41.311: error : SELinuxInitialize:115 : cannot open SELinux virtual 
domain context file '/etc/selinux/default/contexts/virtual_domain_context': No 
such file or directory
22:31:41.311: error : qemudSecurityInit:764 : Failed to start security driver
22:31:41.311: error : virStateInitialize:832 : Initialization of QEMU state 
driver failed
22:31:41.312: error : main:3155 : Driver state initialization failed
22:31:41.312: warning : qemudDispatchSignalEvent:383 : Shutting down on signal 3

/etc/selinux/default/contexts/virtual_domain_context is not provided by the
selinux-policy-default package...

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32 (SMP w/2 CPU cores; PREEMPT)
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 libvirt-bin depends on:
ii  adduser   3.111  add and remove users and groups
ii  hal   0.5.13-6   Hardware Abstraction Layer
ii  libavahi-client3  0.6.25-2   Avahi client library
ii  libavahi-common3  0.6.25-2   Avahi common library
ii  libc6 2.10.1-2   GNU C Library: Shared libraries
ii  libcap-ng00.5.1-1Development and header files for l
ii  libdbus-1-3   1.2.16-2   simple interprocess messaging syst
ii  libdevmapper1.02. 2:1.02.39-1The Linux Kernel Device Mapper use
ii  libgnutls26   2.8.3-1the GNU TLS library - runtime libr
ii  libhal1   0.5.13-6   Hardware Abstraction Layer - share
ii  libparted1.8-12   1.8.8.git.2009.07.19-5 The GNU Parted disk partitioning s
ii  libreadline6  6.0-5  GNU readline and history libraries
ii  libsasl2-22.1.23.dfsg1-3 Cyrus SASL - authentication abstra
ii  libselinux1   2.0.89-4   SELinux runtime shared libraries
ii  libuuid1  2.16.1-4   Universally Unique ID library
ii  libvirt0  0.7.4-1library for interfacing with diffe
ii  libxenstore3.03.4.2-2Xenstore communications library fo
ii  libxml2   2.7.6.dfsg-1   GNOME XML library
ii  logrotate 3.7.8-4Log rotation utility

Versions of packages libvirt-bin recommends:
ii  bridge-utils  1.4-5  Utilities for configuring the Linu
ii  dnsmasq-base  2.47-3 A small caching DNS proxy and DHCP
ii  iptables  1.4.5-1administration tools for packet fi
ii  netcat-openbsd1.89-3 TCP/IP swiss army knife
pn  qemu   (no description available)

Versions of packages libvirt-bin suggests:
ii  policykit-1   0.95-1 framework for managing administrat

-- 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#544155: please test this GRUB snapshot

[Luca Tettamanti]

On Thu, Sep 10, 2009 at 11:25 PM, Robert Millan  wrote:
> On Thu, Sep 10, 2009 at 09:31:44PM +0200, Maik Zumstrull wrote:
>>
>> Still broken, not noticably different.
>
> There we go again:
>
>  http://people.debian.org/~rmh/ati/dacfix4/
>
> Luca: Last July you helped me debug a problem related to vga= parameter
> (bug #535026).  There's a new bug (which probably doesn't affect you),
> and I need to restructure the code I wrote to fix your problem.  If
> you could test the package in URL above and confirm it doesn't cause a
> regression for you, I'd appreciate it.

I had to compile from the tarball + patch since I'm on amd64; the
package works fine with vesafb and packed colors.

Luca



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#540352: rdesktop: it keymap is incorrect

[Luca Tettamanti]

Package: rdesktop
Version: 1.6.0-2
Severity: normal
Tags: patch

When using an Italian keyboad (and the Italian keymap) the remote host does
not pick up '{' and '}'; on the keyboard the curly brackets are on
the same key as the square brackets (and are select with shift+altrg modifier).

I've already reported this upstream:
http://sourceforge.net/tracker/?func=detail&atid=381349&aid=2829062&group_id=24366

In the mean time it might be worth carrying it in debian package.

Index: keymaps/it
===
--- keymaps/it  (revision 1505)
+++ keymaps/it  (working copy)
@@ -58,11 +58,11 @@
 egrave 0x1a
 eacute 0x1a shift
 bracketleft 0x1a altgr
-dead_abovering 0x1a shift altgr
+braceleft 0x1a shift altgr
 plus 0x1b
 asterisk 0x1b shift
 bracketright 0x1b altgr
-dead_macron 0x1b shift altgr
+braceright 0x1b shift altgr
 ae 0x1e altgr
 AE 0x1e shift altgr
 ssharp 0x1f altgr

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.31-rc5-00246-g90bc1a6 (SMP w/2 CPU cores; PREEMPT)
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 rdesktop depends on:
ii  libc6 2.9-21 GNU C Library: Shared libraries
ii  libssl0.9.8   0.9.8k-3   SSL shared libraries
ii  libx11-6  2:1.2.2-1  X11 client-side library

rdesktop recommends no packages.

rdesktop suggests no packages.

-- no debconf information

-- debsums errors found:
debsums: checksum mismatch rdesktop file /usr/share/rdesktop/keymaps/it



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#535026: patch, please test

[Luca Tettamanti]

On Fri, Jul 24, 2009 at 5:33 PM, Robert Millan wrote:
> Please try this one.

Ok, this patch works fine with 8bit color mode.

thanks,
Luca



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#535026: patch, please test

[Luca Tettamanti]

On Thu, Jul 23, 2009 at 8:04 PM, Robert Millan wrote:
> On Thu, Jul 23, 2009 at 06:07:52PM +0200, Luca Tettamanti wrote:
>> On Thu, Jul 23, 2009 at 2:10 AM, Robert Millan wrote:
>> > On Wed, Jul 22, 2009 at 09:31:50PM +0200, Luca Tettamanti wrote:
>> >>
>> >> The patch for the size of FB is not sufficient; applying the color
>> >> hack makes vesafb work:
>> >
>> > Great.  We're almost finished.  Please could you test:
>> >
>> >  - Whether the color hack alone is sufficient, or the patch for FB size
>> >    is also needed.
>>
>> The color hack is sufficient.
>>
>> >  - Attached patch to (hopefully) fix color properly instead of the hack.
>>
>> It doesn't work. This is what vesafb picks up:
>>
>> vesafb: framebuffer at 0xe000, mapped to 0xc9001010, using
>> 768k, total 768k
>> vesafb: mode is 1024x768x8, linelength=1024, pages=0
>> vesafb: scrolling: redraw
>> vesafb: Pseudocolor: size=0:1:1:1, shift=0:0:0:0
>
> What vga= paramter are you using?  0x305 ?

Yes.

> What does "vbeinfo" GRUB command
> (with unpatched GRUB) print for this mode (0x105, as you need to substract
> 0x200)?

Ah. Packed color...

> What does "linux16 /linux.img vga=ask" say about this mode?

Well it just list the modes (and - yes - 0x305 is present)

> Do other modes work?

All modes work except for the ones using packed color format (8 bits).

Luca



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#535026: patch, please test

[Luca Tettamanti]

On Thu, Jul 23, 2009 at 2:10 AM, Robert Millan wrote:
> On Wed, Jul 22, 2009 at 09:31:50PM +0200, Luca Tettamanti wrote:
>>
>> The patch for the size of FB is not sufficient; applying the color
>> hack makes vesafb work:
>
> Great.  We're almost finished.  Please could you test:
>
>  - Whether the color hack alone is sufficient, or the patch for FB size
>    is also needed.

The color hack is sufficient.

>  - Attached patch to (hopefully) fix color properly instead of the hack.

It doesn't work. This is what vesafb picks up:

vesafb: framebuffer at 0xe000, mapped to 0xc9001010, using
768k, total 768k
vesafb: mode is 1024x768x8, linelength=1024, pages=0
vesafb: scrolling: redraw
vesafb: Pseudocolor: size=0:1:1:1, shift=0:0:0:0

screen_info dump:
orig_x = 0x0, orig_y =  0x0
ext_mem_k = 0x8000
orig_video_page = 0x0
orig_video_mode = 0x3
orig_video_cols = 0x0
orig_video_ega_bx = 0x0
orig_video_lines = 0x0
orig_video_isVGA = 0x23
orig_video_points = 0x10
lfb_width / lfb_height / lfb_depth = 1024x768x8
lfb_base = 0xe000, lfb_size = 0xc
cl_magic = 0xa33f, cl_offset = 0x1000
lfb_linelength = 0x400
red_size = 0x1, red_pos = 0x0
green_size = 0x1, green_pos = 0x0
blue_size = 0x1, blue_pos = 0x0
rsvd_size = 0x0, rsvd_pos = 0x0
vesapm = 0x0:0x0
pages = 0x0
vesa_attributes = 0x0
capabilities = 0x0

Luca



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#535026: patch, please test

[Luca Tettamanti]

On Tue, Jul 21, 2009 at 10:56 PM, Robert Millan wrote:
> On Tue, Jul 21, 2009 at 10:07:05PM +0200, Luca Tettamanti wrote:
>>
>> Sorry for the confusion, linux16 is working fine, linux does not. A
>> patched kernel with linux16 reports:
>>
>> [...]
>>
>> I'm running 1.96+20090709-1 which already contains the patch to the
>> capability field. Grub reports:
>>
>> screen_info dump:
>> orig_x = 0x0, orig_y =  0x0
>> ext_mem_k = 0x8000
>> orig_video_page = 0x0
>> orig_video_mode = 0x3
>> orig_video_cols = 0x0
>> orig_video_ega_bx = 0x0
>> orig_video_lines = 0x0
>> orig_video_isVGA = 0x23
>> orig_video_points = 0x10
>> lfb_width / lfb_height / lfb_depth = 1024x768x8
>> lfb_base = 0xe000, lfb_size = 0xc
>> cl_magic = 0xa33f, cl_offset = 0x1000
>> lfb_linelength = 0x400
>> red_size = 0x0, red_pos = 0x0
>> green_size = 0x0, green_pos = 0x0
>> blue_size = 0x0, blue_pos = 0x0
>> rsvd_size = 0x0, rsvd_pos = 0x0
>> vesapm = 0x0:0x0
>> pages = 0x0
>> vesa_attributes = 0x0
>> capabilities = 0x0
>
> Thanks Luca.  I suspect lfb_size, ${color}_size or maybe vesa_attributes to
> be the culprit.
>
> For lfb_size I already made a patch [1], please could you test and see if it
> solves the problem?
>
> But I got a hunch that "blank screen" has something to do those color
> variables.  For a quick hack see attachment.

The patch for the size of FB is not sufficient; applying the color
hack makes vesafb work:

vesafb: framebuffer at 0xe000, mapped to 0xc9001010, using
1536k, total 16384k
vesafb: mode is 1024x768x8, linelength=1024, pages=0
vesafb: scrolling: redraw
vesafb: Pseudocolor: size=8:8:8:8, shift=0:0:0:0

Luca



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#535026: patch, please test

[Luca Tettamanti]

On Sat, Jul 4, 2009 at 4:16 PM, Robert Millan wrote:
> On Fri, Jul 03, 2009 at 06:10:01PM +0200, Luca Tettamanti wrote:
>> The last update to grub didn't fix the bug for me, I still have a blank FB.
>> vesafb still reports bogus information:
>>
>> vesafb: framebuffer at 0xe000, mapped to 0xc9001010, using
>> 768k, total 768k
>> vesafb: mode is 1024x768x8, linelength=1024, pages=0
>> vesafb: scrolling: redraw
>> vesafb: Pseudocolor: size=0:0:0:0, shift=0:0:0:0
>
> Please tell me the output of:
>
>  A) A *patched* Linux being loaded by "linux16" command, using the
>     patch in:
>     http://lists.gnu.org/archive/html/grub-devel/2009-06/txteL9T65YdVL.txt
>
>     This could be what you already provided in
>     http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=535026#43
>     except your followup comment "vesafb is not picking up the right options"
>     contradicts that (linux16 *is* the old loader, and it is supposed to
>     work.  If linux16 doesn't work, we have an entirely different problem).

Sorry for the confusion, linux16 is working fine, linux does not. A
patched kernel with linux16 reports:

screen_info dump:
orig_x = 0x0, orig_y =  0x4
ext_mem_k = 0x
orig_video_page = 0x0
orig_video_mode = 0x3
orig_video_cols = 0x50
orig_video_ega_bx = 0x3
orig_video_lines = 0x19
orig_video_isVGA = 0x23
orig_video_points = 0x10
lfb_width / lfb_height / lfb_depth = 1024x768x8
lfb_base = 0xe000, lfb_size = 0x100
cl_magic = 0x0, cl_offset = 0x0
lfb_linelength = 0x400
red_size = 0x8, red_pos = 0x0
green_size = 0x8, green_pos = 0x0
blue_size = 0x8, blue_pos = 0x0
rsvd_size = 0x8, rsvd_pos = 0x0
vesapm = 0x0:0x9eda
pages = 0x0
vesa_attributes = 0xbb
capabilities = 0x0

vesafb is happy:

vesafb: framebuffer at 0xe000, mapped to 0xc9001010, using
1536k, total 16384k
vesafb: mode is 1024x768x8, linelength=1024, pages=18
vesafb: scrolling: redraw
vesafb: Pseudocolor: size=8:8:8:8, shift=0:0:0:0

>  B) Linux (patched or not), being loaded by "linux" command, using the
>     GRUB patch in:
>     http://lists.gnu.org/archive/html/grub-devel/2009-06/txtFlQanGk4Pv.txt
>     *plus* the patch I'm attaching.

I'm running 1.96+20090709-1 which already contains the patch to the
capability field. Grub reports:

screen_info dump:
orig_x = 0x0, orig_y =  0x0
ext_mem_k = 0x8000
orig_video_page = 0x0
orig_video_mode = 0x3
orig_video_cols = 0x0
orig_video_ega_bx = 0x0
orig_video_lines = 0x0
orig_video_isVGA = 0x23
orig_video_points = 0x10
lfb_width / lfb_height / lfb_depth = 1024x768x8
lfb_base = 0xe000, lfb_size = 0xc
cl_magic = 0xa33f, cl_offset = 0x1000
lfb_linelength = 0x400
red_size = 0x0, red_pos = 0x0
green_size = 0x0, green_pos = 0x0
blue_size = 0x0, blue_pos = 0x0
rsvd_size = 0x0, rsvd_pos = 0x0
vesapm = 0x0:0x0
pages = 0x0
vesa_attributes = 0x0
capabilities = 0x0

the information itself is consistent with what is picked up by vesafb
(which the patch suggested for A), which later shows:

vesafb: framebuffer at 0xe000, mapped to 0xc9001010, using
768k, total 768k
vesafb: mode is 1024x768x8, linelength=1024, pages=0
vesafb: scrolling: redraw
vesafb: Pseudocolor: size=0:0:0:0, shift=0:0:0:0

In this case screen stays blank.

HTH,
Luca



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#535026: patch, please test

[Luca Tettamanti]

The last update to grub didn't fix the bug for me, I still have a blank FB.
vesafb still reports bogus information:

vesafb: framebuffer at 0xe000, mapped to 0xc9001010, using
768k, total 768k
vesafb: mode is 1024x768x8, linelength=1024, pages=0
vesafb: scrolling: redraw
vesafb: Pseudocolor: size=0:0:0:0, shift=0:0:0:0

Luca



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#535026: patch, please test

[Luca Tettamanti]

On Wed, Jul 1, 2009 at 3:54 AM, Robert Millan wrote:
> Please could you test if this patch helps?

It doesn't work. The output of your patched kernel is unchanged while
vesafb picks a different memory size:

vesafb: framebuffer at 0xe000, mapped to 0xc2001010, using
1536k, total 16384k
vesafb: mode is 1024x768x8, linelength=1024, pages=0
vesafb: scrolling: redraw
vesafb: Pseudocolor: size=0:0:0:0, shift=0:0:0:0

The color data is still wrong though. screen_info is copied from boot
params, which your patched kernel dumps correctly... wtf?

Luca



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#535026: Bug#534944: grub-pc: text mode virtual terminals blank

[Luca Tettamanti]

On Tue, Jun 30, 2009 at 6:40 PM, Robert Millan wrote:
> On Tue, Jun 30, 2009 at 04:33:37PM +0200, Luca Tettamanti wrote:
>> On Mon, Jun 29, 2009 at 7:28 PM, Robert Millan wrote:
>> > Hi again,
>> >
>> > I'm uploading 1.96+20090629-1, which includes some cleanup in the Linux
>> > loader.  It's possible your problem might disappear with this version,
>> > please report.
>>
>> No joy.
>
> Hi,
>
> Then your bug is #535026.  #534944 was confirmed to be fixed by Arthur.  I'm
> changing CC to 535...@bugs.debian.org.

I have radeon mobility (M76) card and I'm not using KMS. I also don't
get stale content on text VTs (just black screen).

>> I see the message that "vga" parameter is deprecated. The mode I'm
>> using is 773 (1024x768x256).
>
> Ok.  That's 0x305 aka 1024x768x8, which is supposed to be detected & handled
> already.
>
>> This is the output of a patched kernel, loaded with linux16:
>>
>> orig_x = 0x0, orig_y =  0x0
>> ext_mem_k = 0x
>> orig_video_page = 0x0
>> orig_video_mode = 0x3
>> orig_video_cols = 0x50
>> orig_video_ega_bx = 0x3
>> orig_video_lines = 0x19
>> orig_video_isVGA = 0x1
>> orig_video_points = 0x10
>> lfb_width / lfb_height / lfb_depth = 0x0x0
>> lfb_base = 0x0, lfb_size = 0x0
>> cl_magic = 0x0, cl_offset = 0x0
>> lfb_linelength = 0x0\n
>> red_size = 0x0, red_pos = 0x0
>> green_size = 0x0, green_pos = 0x0
>> blue_size = 0x0, blue_pos = 0x0
>> rsvd_size = 0x0, rsvd_pos = 0x0
>> vesapm = 0x0:0x0
>> pages = 0x0
>> vesa_attributes = 0x0
>> capabilities = 0x0
>
> This looks like text mode.  I assume you didn't pass "vga=773" to linux16?
> I need you to include that parameter in your test.

Ops, right:

orig_x = 0x0, orig_y =  0x1
ext_mem_k = 0x
orig_video_page = 0x0
orig_video_mode = 0x3
orig_video_cols = 0x50
orig_video_ega_bx = 0x3
orig_video_lines = 0x19
orig_video_isVGA = 0x23
orig_video_points = 0x10
lfb_width / lfb_height / lfb_depth = 1024x768x8
lfb_base = 0xe000, lfb_size = 0x100
cl_magic = 0x0, cl_offset = 0x0
lfb_linelength = 0x400
red_size = 0x8, red_pos = 0x0
green_size = 0x8, green_pos = 0x0
blue_size = 0x8, blue_pos = 0x0
rsvd_size = 0x8, rsvd_pos = 0x0
vesapm = 0xc000:0x9eda
pages = 0x12
vesa_attributes = 0xbb
capabilities = 0x0

vesafb is not picking up the right options:

vesafb: framebuffer at 0xe000, mapped to 0xc2001010, using
768k, total 768k
vesafb: mode is 1024x768x8, linelength=1024, pages=0
vesafb: scrolling: redraw
vesafb: Pseudocolor: size=0:0:0:0, shift=0:0:0:0

both pages and Pseudocolor values look wrong. With older grub I get:

vesafb: framebuffer at 0xe000, mapped to 0xc2001010, using
1536k, total 16384k
vesafb: mode is 1024x768x8, linelength=1024, pages=18
vesafb: scrolling: redraw
vesafb: Pseudocolor: size=8:8:8:8, shift=0:0:0:0

Luca



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#534944: grub-pc: text mode virtual terminals blank

[Luca Tettamanti]

On Mon, Jun 29, 2009 at 7:28 PM, Robert Millan wrote:
> Hi again,
>
> I'm uploading 1.96+20090629-1, which includes some cleanup in the Linux
> loader.  It's possible your problem might disappear with this version,
> please report.

No joy.

> Note: Try it in text mode first (run "terminal_output console" in GRUB
> prompt).  If that _does_ work, try from gfxterm then.

Nope, it doesn't make any difference. What seems important is the
"vga" option on the kernel command line. If I leave it out then I see
the console (using either terminal_output console or gfxterm).

This change may be related:

2009-06-08  Robert Millan  
* loader/i386/linux.c (grub_cmd_linux): When processing `vga=', use
as fallback an equivalent option without depth.

I see the message that "vga" parameter is deprecated. The mode I'm
using is 773 (1024x768x256).

This is the output of a patched kernel, loaded with linux16:

orig_x = 0x0, orig_y =  0x0
ext_mem_k = 0x
orig_video_page = 0x0
orig_video_mode = 0x3
orig_video_cols = 0x50
orig_video_ega_bx = 0x3
orig_video_lines = 0x19
orig_video_isVGA = 0x1
orig_video_points = 0x10
lfb_width / lfb_height / lfb_depth = 0x0x0
lfb_base = 0x0, lfb_size = 0x0
cl_magic = 0x0, cl_offset = 0x0
lfb_linelength = 0x0\n
red_size = 0x0, red_pos = 0x0
green_size = 0x0, green_pos = 0x0
blue_size = 0x0, blue_pos = 0x0
rsvd_size = 0x0, rsvd_pos = 0x0
vesapm = 0x0:0x0
pages = 0x0
vesa_attributes = 0x0
capabilities = 0x0

L



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#534944: grub-pc: text mode virtual terminals blank

[Luca Tettamanti]

Package: grub-pc
Version: 1.96+20090628-1
Severity: normal

I'm seeing the same behaviour, the problem appeared after upgrading from
1.96+20090603-2.

I do not auto-start the graphical login screen (i.e. the system is configured
to stay in text mode), so the problem seems unrelated to X. The kernel is
configured to use vesafb, but not output is displayed (grub menu itself is
fine).

-- Package-specific info:

### BEGIN /etc/grub.d/40_custom ###
[cut, sample entry]
menuentry "2.6.30-08503-g4e8a237" {
set root=(hd0,5)
linux /bzImage-2.6.30-08503-g4e8a237 root=/dev/mapper/main-system ro 
vga=773 video=vesafb:ypan,mtrr:3 selinux=0
initrd /initrd.img-2.6.30-08503-g4e8a237
}
*** END /boot/grub/grub.cfg

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable-i386
  APT policy: (500, 'unstable-i386'), (500, 'transitional-i386'), (500, 
'transitional'), (500, 'stable-i386'), (500, 'unstable'), (500, 'stable'), (1, 
'experimental-i386'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.30-rc8-00034-g81ee1ba (SMP w/2 CPU cores; PREEMPT)
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 grub-pc depends on:
ii  debconf [debconf-2.0]1.5.26  Debian configuration management sy
ii  grub-common  1.96+20090628-1 GRand Unified Bootloader, version 
ii  libc62.9-13  GNU C Library: Shared libraries
ii  ucf  3.0018  Update Configuration File: preserv

grub-pc recommends no packages.

Versions of packages grub-pc suggests:
ii  desktop-base  5.0.5  common files for the Debian Deskto
ii  genisoimage   9:1.1.9-1  Creates ISO-9660 CD-ROM filesystem
pn  os-prober  (no description available)

-- debconf information:
* grub-pc/linux_cmdline:
* grub-pc/chainload_from_menu.lst: true
* grub-pc/install_devices: /dev/sda



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#527137: lwresd: cannot be stopped - wrong pid file

[Luca Tettamanti]

Package: lwresd
Version: 1:9.6.0.dfsg.P1-2
Severity: normal
Tags: patch

Hello,
lwresd creates its pid file under /var/run/lwresd/, but the init.d
script thinks that the file is under /var/run/named and fails to stop
the daemon.

This simple patch fixes the problem:

--- a/etc/init.d/lwresd 2009-05-05 21:35:45.0 +0200
+++ b/etc/init.d/lwresd 2009-05-05 21:35:55.0 +0200
@@ -44,7 +44,7 @@
 stop)
log_daemon_msg "Stopping domain name service" $NAME
if start-stop-daemon --stop --quiet  \
-   --pidfile /var/run/named/$NAME.pid --exec $DAEMON; then
+   --pidfile /var/run/lwresd/$NAME.pid --exec $DAEMON; then
log_end_msg 0
else
log_end_msg 1

The alternative is to force lwresd to write its pid file in
/var/run/named with "-i /var/run/named/$NAME.pid".


-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: i386 (x86_64)

Kernel: Linux 2.6.30-rc4-kgdb-dirty (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.utf8)
Shell: /bin/sh linked to /bin/bash

Versions of packages lwresd depends on:
ii  adduser  3.102   Add and remove users and groups
ii  libbind9-50  1:9.6.0.dfsg.P1-2   BIND9 Shared Library used by BIND
ii  libc62.9-4   GNU C Library: Shared libraries
ii  libcap2  2.11-2  support for getting/setting POSIX.
ii  libdb4.7 4.7.25-6Berkeley v4.7 Database Libraries [
ii  libdns50 1:9.6.0.dfsg.P1-2   DNS Shared Library used by BIND
ii  libgssapi-krb5-2 1.6.dfsg.4~beta1-11 MIT Kerberos runtime libraries - k
ii  libisc50 1:9.6.0.dfsg.P1-2   ISC Shared Library used by BIND
ii  libisccc50   1:9.6.0.dfsg.P1-2   Command Channel Library used by BI
ii  libisccfg50  1:9.6.0.dfsg.P1-2   Config File Handling Library used 
ii  libldap-2.4-22.4.15-1.1  OpenLDAP libraries
ii  liblwres50   1:9.6.0.dfsg.P1-2   Lightweight Resolver Library used 
ii  libssl0.9.8  0.9.8g-14   SSL shared libraries
ii  libxml2  2.7.3.dfsg-1GNOME XML library

Versions of packages lwresd recommends:
ii  libnss-lwres  0.93-5 NSS module for using bind9's lwres

Versions of packages lwresd suggests:
ii  bind9utils 1:9.6.0.dfsg.P1-2 Utilities for BIND

-- no debconf information

-- 
"Ricorda sempre che sei unico, esattamente come tutti gli altri".



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#526823: libc6 2.9-9 broke DNS resolver again

[Luca Tettamanti]

On Tue, May 5, 2009 at 12:38 AM, Bastian Blank  wrote:
> On Mon, May 04, 2009 at 11:55:22PM +0200, Luca Tettamanti wrote:
>> To recap: my ADSL router receives two requests and sends back *two*
>> answers; to the A query it replies with the expected data, to the 
>> query it replies "NotImpl" (see the tcpdump in the first email).
>
> I doubt that this behaviour is allowed. "Not implemented" is a response
> to the query type, aka standard query or inverse query, not to the
> contents of the query.[1]

I see, I though that "not implemented" was linked to the qtype, not to
the opcode. So, yes, the router is broken, thanks for explaining.

> This behaviour also violates the transparency considerations.[2]

I'm pretty sure that my router predates that RFC :P

Luca



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#526823: libc6 2.9-9 broke DNS resolver again

[Luca Tettamanti]

On Mon, May 4, 2009 at 10:57 PM, Aurelien Jarno  wrote:
> On Mon, May 04, 2009 at 10:32:09PM +0200, Luca Tettamanti wrote:
>> On Mon, May 4, 2009 at 10:11 PM, Aurelien Jarno  wrote:
>> > On Mon, May 04, 2009 at 09:59:22PM +0200, Luca Tettamanti wrote:
>> >> The option single-request works, the automagic workaround does not,
>> >
>> > That's a good news.
>> >
>> >> i.e. I always see the two requests going out in parallel.
>> >> Actually I'm not sure I understand how it's supposes to work: if the
>> >> first request fails usually the caller gives up, no?
>> >
>> > The first request done by a program should timeout, and the second
>> > request by the same program should then be done sequentially, like when
>> > "single-request" is set.
>>
>> That's not what is happening though. I try to open a page in konqueror
>> (I also tried other programs, it's not specific to konqueror): I see
>> two request (A and ) going out at the same time; konqueror says
>> it's unable to resolve the address - so far so good. I try to reload
>
> That's the problem. When I say it should timeout, I mean it should take
> long time to resolve, but at the end an answer should be returned.

Ah ok, __libc_res_nsend should to statp->retry queries, which by
default is 2 (confirmed by gdb).
send_dg() returns 1 (reply), the socket is then closed; return value
is 1 and control goes back to
__libc_res_nquery.

At this point we have the two answers:

hp = {id = 27765, rd = 1, tc = 1, aa = 0, opcode = 5, qr = 0, rcode =
1, cd = 0, ad = 0, unused = 0, ra = 1,
  qdcount = 128, ancount = 1, nscount = 2, arcount = 0}
hp2 = {id = 6, rd = 1, tc = 0, aa = 0, opcode = 0, qr = 1, rcode =
0, cd = 0, ad = 0, unused = 0, ra = 1,
  qdcount = 256, ancount = 512, nscount = 0, arcount = 0}

The error in first one is FORMERR (I'd expect NOTIMP...), which is
treated as an unrecoverable failure even if the second one succeeded.
answer contains a 76bytes of reply:

756c 2b81 8000 0100 0200  0003 6674  ul+...ft
7002 6974 0664 6562 6961 6e03 6f72 6700  p.it.debian.org.
0001 0001 c00c 0005 0001  02f5 000d  
0366 7470 0462 6f66 6802 6974 00c0 2f00  .ftp.bofh.it../.
0100 0100 0063 9400 04d5 5c08.c\.

which seems sensible to me (ftp.it.debian.org is the name that I
request, and it's a CNAME for ftp.bofh.it).

To recap: my ADSL router receives two requests and sends back *two*
answers; to the A query it replies with the expected data, to the 
query it replies "NotImpl" (see the tcpdump in the first email). When
both queries and sent in parallel __libc_res_nquery consider an
unrecoverable failure an error in any of the two (even if one of them
is valid): the logic should be reversed: the query was successful if
we get _at least_ one response.

After careful pondering I think that my router is actually sane  (IOW,
it doesn't discard  requests - it correctly replies that it does
not support that query); I think that it's a real bug in glibc.

Luca



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#526823: libc6 2.9-9 broke DNS resolver again

[Luca Tettamanti]

On Mon, May 4, 2009 at 10:11 PM, Aurelien Jarno  wrote:
> On Mon, May 04, 2009 at 09:59:22PM +0200, Luca Tettamanti wrote:
>> The option single-request works, the automagic workaround does not,
>
> That's a good news.
>
>> i.e. I always see the two requests going out in parallel.
>> Actually I'm not sure I understand how it's supposes to work: if the
>> first request fails usually the caller gives up, no?
>
> The first request done by a program should timeout, and the second
> request by the same program should then be done sequentially, like when
> "single-request" is set.

That's not what is happening though. I try to open a page in konqueror
(I also tried other programs, it's not specific to konqueror): I see
two request (A and ) going out at the same time; konqueror says
it's unable to resolve the address - so far so good. I try to reload
the page and I still see both requests going out at the same time
(failure again). With single-request I see the first query, its answer
and only then the second query and its reply - as expected.
Furthermore I fear the workaround won't work for one-shot programs,
like apt helpers, right?

Luca



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#526823: libc6 2.9-9 broke DNS resolver again

[Luca Tettamanti]

On Mon, May 4, 2009 at 6:45 AM, Aurelien Jarno  wrote:
> On Sun, May 03, 2009 at 08:54:07PM +0200, Luca Tettamanti wrote:
>> Package: libc6
>> Version: 2.9-9
>> Severity: normal
>>
>> Hello, I was affected by the resolver bug that was solved in 2.9-7; as of 
>> 2.9-9
>> the resolver stopped working again. The automatic workaround that is 
>> mentioned
>> in the changelog is not working, and "single-request" in resolv.conf doesn't
>> seem to have any effect either.
>>
>> Here's a dump of the resolver trying to get the address of google.com:
>>
>> 14:11:00.754265 IP (tos 0x0, ttl 64, id 45448, offset 0, flags [DF], proto 
>> UDP (17), length 60)
>>     10.0.0.3.60486 > 10.0.0.138.53: [udp sum ok] 39108+ A? www.google.com. 
>> (32)
>> 14:11:00.754303 IP (tos 0x0, ttl 64, id 45449, offset 0, flags [DF], proto 
>> UDP (17), length 60)
>>     10.0.0.3.60486 > 10.0.0.138.53: [udp sum ok] 48015+ ? 
>> www.google.com. (32)
>> 14:11:00.759312 IP (tos 0x0, ttl 64, id 1324, offset 0, flags [none], proto 
>> UDP (17), length 60)
>>     10.0.0.138.53 > 10.0.0.3.60486: [udp sum ok] 48015 NotImp q: ? 
>> www.google.com. 0/0/0 (32)
>> 14:11:00.817710 IP (tos 0x0, ttl 64, id 1325, offset 0, flags [none], proto 
>> UDP (17), length 144)
>>     10.0.0.138.53 > 10.0.0.3.60486: 39108 q: A? www.google.com. 5/0/0 
>> www.google.com. CNAME www.l.google.com.[|domain]
>>
>> The DNS server (it's my ADSL router) responds NotImp to the  query (it 
>> does
>> not support IPv6). The reply (CNAME) to the A query seems correct though.
>>
>
> Could you please try the glibc from http://temp.aurel32.net/glibc-test/ ?
> I have backported a few more patch from upstream, but I have no way to
> know if they change something or not.

The option single-request works, the automagic workaround does not,
i.e. I always see the two requests going out in parallel.
Actually I'm not sure I understand how it's supposes to work: if the
first request fails usually the caller gives up, no?

Luca



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#526823: libc6 2.9-9 broke DNS resolver again

[Luca Tettamanti]

Package: libc6
Version: 2.9-9
Severity: normal

Hello, I was affected by the resolver bug that was solved in 2.9-7; as of 2.9-9
the resolver stopped working again. The automatic workaround that is mentioned
in the changelog is not working, and "single-request" in resolv.conf doesn't
seem to have any effect either.

Here's a dump of the resolver trying to get the address of google.com:

14:11:00.754265 IP (tos 0x0, ttl 64, id 45448, offset 0, flags [DF], proto UDP 
(17), length 60)
10.0.0.3.60486 > 10.0.0.138.53: [udp sum ok] 39108+ A? www.google.com. (32)
14:11:00.754303 IP (tos 0x0, ttl 64, id 45449, offset 0, flags [DF], proto UDP 
(17), length 60)
10.0.0.3.60486 > 10.0.0.138.53: [udp sum ok] 48015+ ? www.google.com. 
(32)
14:11:00.759312 IP (tos 0x0, ttl 64, id 1324, offset 0, flags [none], proto UDP 
(17), length 60)
10.0.0.138.53 > 10.0.0.3.60486: [udp sum ok] 48015 NotImp q: ? 
www.google.com. 0/0/0 (32)
14:11:00.817710 IP (tos 0x0, ttl 64, id 1325, offset 0, flags [none], proto UDP 
(17), length 144)
10.0.0.138.53 > 10.0.0.3.60486: 39108 q: A? www.google.com. 5/0/0 
www.google.com. CNAME www.l.google.com.[|domain]

The DNS server (it's my ADSL router) responds NotImp to the  query (it does
not support IPv6). The reply (CNAME) to the A query seems correct though.

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.30-rc3-00329-g0c8454f (SMP w/2 CPU cores; PREEMPT)
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 libc6 depends on:
ii  libgcc1   1:4.3.3-8  GCC support library

libc6 recommends no packages.

Versions of packages libc6 suggests:
pn  glibc-doc  (no description available)
ii  locales   2.9-7  GNU C Library: National Language (

-- debconf information:
* glibc/upgrade: true
  glibc/disable-screensaver:
  glibc/restart-failed:
* glibc/restart-services: vsftpd openbsd-inetd mysql exim4 cups cron atd




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#449064: fixed

[Luca Tettamanti]

Andrew Pollock wrote:

On Sat, Apr 11, 2009 at 10:48:22PM +0200, Luca Tettamanti wrote:

Hi,
version 3.1.2-1 of dhcp3-client fixes the issue for me.


That's interesting, because I did not make any of the changes I mentioned
earlier in this bug to dhclient-script in this release,


I tried downgrading to 3.1.1-6 and the problem reappeared; however I was 
also hit by the 'silly MTU' issue (I forgot about it, I had a workaround 
in post-up); 576 bytes is too small for IPv6, the behavior I was 
observing was a side effect of the wrong MTU.


Luca



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#449064: fixed

[Luca Tettamanti]

Hi,
version 3.1.2-1 of dhcp3-client fixes the issue for me.

Luca



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#449064: dhcp3-client: breaks IPv6 networking

[Luca Tettamanti]

Package: dhcp3-client
Version: 3.0.6.dfsg-1
Severity: normal

*** Please type your report below this line ***

I'm trying to configure a dual stack machine (IPv4 + IPv6) but version 3
of the DHCP client seems to disrupt IPv6 networking.

IPv6 is autoconfigured using the prefix advertised by the router, while
IPv4 is configured using DHCP.

Problem is that as soon as dhclient is run for the ethernet interface
IPv6 networking is *completely* disabled on that interface.

If I try to manually set the address I get:

nb-core2:/etc# ip -6 addr add 2001:5c0:etc dev eth0
RTNETLINK answers: No buffer space available

I don't even see eth0 anymore under:

/proc/sys/net/ipv6/conf/

The only way to get back IPv6 is to rmmod the driver of the ethernet
card.
IPv6 only works fine; i.e. if I simply to:

ifconfig eth0 up (instead of using ifup)

the interface is brought up, the link local address is created and after
that the global address is configured using the advertisement from the
router. At this point IPv6 is working, but if I try to start dhclient I
loose it again.

Furthermore, version 2 of the client (dhcp-client 2.0pl5dfsg1-20) works
fine in this setup.

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.22-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.utf8)
Shell: /bin/sh linked to /bin/bash

Versions of packages dhcp3-client depends on:
ii  debconf [debconf-2.0]   1.5.14   Debian configuration management sy
ii  debianutils 2.25 Miscellaneous utilities specific t
ii  dhcp3-common3.0.6.dfsg-1 common files used by all the dhcp3
ii  libc6   2.6.1-5  GNU C Library: Shared libraries

dhcp3-client recommends no packages.

-- debconf information:
  dhcp3-client/dhclient-needs-restarting:
  dhcp3-client/dhclient-script_moved:


Luca
-- 
La somma dell'intelligenza sulla terra e` una costante.
La popolazione e` in aumento.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#427516: Bad DNS hangs squid

[Luca Tettamanti]

Christian Weeks ha scritto: 
> And this is where it hangs.
> 
> It's clear that squid does not like that 255.255.255.255 IP Address, and 
> not surprising really.
> 
> The problem is that squid is completely wedged:
> 
> proxy10678  0.2  0.0  0 0 ?DJun03   2:38 [squid]

Uninterruptible sleep in kernel mode, probably it's not squid fault.
The output of sysrq-t when squid is hung could be interesting.
 
> I have tried to remove the /var/run/squid.pid file, and restart squid, 
> but it fails, because this dead process still has my port (3128) bound.

This is expected, the process is alive but blocked somewhere in the
kernel.

> The only recovery is a full machine reboot, which is not good. Luckily,
> I run this in a Xen VM, otherwise I would have some really bad problems.

Hum, this could be Xen PV net driver that's confused by the reserved
address.

Luca
-- 
La somma dell'intelligenza sulla terra e` una costante.
La popolazione e` in aumento.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#425767: apt-listbugs crashes on libstdc++6

[Luca Tettamanti]

Package: apt-listbugs
Version: 0.0.77
Severity: normal

Hello,
it seems that apt-listbugs doesn't like libstdc++6 package:

[EMAIL PROTECTED]:~# apt-get install libstdc++6
Reading package lists... Done
Building dependency tree... Done
The following packages will be upgraded:
  libstdc++6
1 upgraded, 0 newly installed, 0 to remove and 701 not upgraded.
Need to get 0B/312kB of archives.
After unpacking 24.6kB of additional disk space will be used.
WARNING: The following packages cannot be authenticated!
  libstdc++6
Authentication warning overridden.
Reading package fields... Done
Reading package status... 0%/usr/lib/ruby/1.8/debian.rb:900:in `initialize': 
nested *?+ in regexp: /Package:\s(libstdc++6) (RegexpError)
/   from /usr/lib/ruby/1.8/debian.rb:900:in `new'
from /usr/lib/ruby/1.8/debian.rb:900:in `initialize'
from /usr/sbin/apt-listbugs:1011:in `new'
from /usr/sbin/apt-listbugs:1011:in `create'
from /usr/sbin/apt-listbugs:1391
E: Sub-process /usr/sbin/apt-listbugs apt || exit 10 returned an error code (10)
E: Failure running script /usr/sbin/apt-listbugs apt || exit 10


-- System Information:
Debian Release: 4.0
  APT prefers oldstable
  APT policy: (500, 'oldstable'), (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.22-rc2-libata-g080e8927-dirty (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.utf8)
Shell: /bin/sh linked to /bin/bash

Versions of packages apt-listbugs depends on:
ii  apt 0.6.46.4-0.1 Advanced front-end for dpkg
ii  libdpkg-ruby1.8 0.3.1modules/classes for dpkg on ruby 1
ii  libhttp-access2-ruby1.8 2.0.6-3  HTTP accessing library for ruby
ii  libintl-gettext-ruby1.8 0.11-5   Gettext wrapper for Ruby 1.8
ii  libruby1.8 [libzlib-ruby1.8 1.8.5-3  Libraries necessary to run Ruby 1.
ii  libxml-parser-ruby1.8   0.6.8-2  Interface of expat for the scripti
ii  ruby1.8.1-8  An interpreter of object-oriented 

apt-listbugs recommends no packages.

-- no debconf information

-- 
Software is like sex; it's better when it's free.
Linus Torvalds


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#417151: kvm-ifup is broken

[Luca Tettamanti]

Il Sun, Apr 01, 2007 at 09:24:21PM +0300, Baruch Even ha scritto: 
> * [EMAIL PROTECTED] <[EMAIL PROTECTED]> [070401 20:41]:
> > On my system the default route has both an explicit metric and a realm,
> > so it looks like this:
> > 
> > default via 10.0.0.138 dev br0  metric 1 realm 10
> > 
> > Since the output of 'ip route ls' does not have a fixed format I suggest
> > to use the following awk program:
> > 
> > switch=$(ip route ls | awk '/^default / { for(i=0;i<$NF;i++) { if ($(i) == 
> > "dev") print $(i+1) }}')
> > 
> > which matches the default route and prints the field following the 'dev'
> > token (which is always the interface name).
> 
> Thanks for the bug report and the fix!
> 
> I'll put that in my repository and hope to upload another version with
> some other bug fixes, I'll also forward this to upstream from where this
> script came originally.

Ah, I didn't noticed that it was 'qemu-ifup' renamed.

Anyway I think that a more appropriate "fix" is getting the interface
name from a config file.
The user may want to use a different interface with e.g. VMs brigded on
the LAN (say br0 on eth0) and the default route on the WAN (eth1).
Furthermore more than one default route can be set, this will confuse
the script...

Luca
-- 
Runtime error 6D at f000:a12f : user incompetente


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#401393: Please test the attached patch for against lilo 22.7.3-1.3

[Luca Tettamanti]

Il Wed, Jan 31, 2007 at 03:22:13PM +0100, Loïc Minier ha scritto: 
> tags 401393 + patch
> stop
> 
> Hi,
> 
>  This is a followup for Debian bug .
> 
>  Could people experiencing this bug please test the attached
>  lilo_22.7.3-1.4.diff against lilo 22.7.3-1.3?

Tested here. Works fine with root on LVM.

Luca
-- 
"L'amore consiste nell'essere cretini insieme." -- P. Valery

Bug#403420: kvm-source: kvm module loads but no /dev/kvm

[Luca Tettamanti]

Ritesh Raj Sarraf wrote:
> Anyway. I manually loaded the kvm and kvm-intel module with which the ref
> count for kvm went to 1. But still no messages in dmesg and starting the kvm
> application complained the same message.

You should check 2 things:

- udev: KVM uses a dynamic minor hence you need udev to create the
  device node.
  You may manually lookup major:minor in /sys/class/misc/kvm/dev, but you
  have to recheck every time because the numbers may change.
- BIOS: 'vmx' flag only means "the hardware can do it"; BIOS support
  must be present and enabled (i.e. proper microcode must be uploaded)
  in order to use it.

HTH,
Luca
-- 
"Ci sono le balle, le megaballe e le statistiche".
 Mark Twain


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#369107: localepurge reports bogus freed space: bytes instead of KBytes?

[Luca Tettamanti]

Il Sun, May 28, 2006 at 12:58:25AM +0200, Paul Seelig ha scritto: 
> On Sat, May 27, 2006 at 04:57:48PM +0200, [EMAIL PROTECTED] wrote:
> > Package: localepurge
> > Version: 0.5.1
> > Severity: normal
> > Tags: patch
> > 
> > 
> > Hello,
> > after upgrade from 0.4.1 localepurge reports silly freed disk space,
> > like:
> > 
> > localepurge: Disk space freed in /usr/share/locale: 14107933K
> > localepurge: Disk space freed in /usr/share/man: 559906K
> > 
> > Total disk space freed by localepurge: 14667839K
> 
> Hi kronos!
> 
> This has already been fixed before your bug report with the upload of
> version 0.5.2.

Ops, I did not notice the new package, maybe I reported before the
upload. You may close the bug.

Luca
-- 
Se non sei parte della soluzione, allora sei parte del problema.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]