Bug#647606: [Pkg-libvirt-maintainers] Bug#647606: [libvirt-bin] virsh screenshot domain not working (cannot get screenshot of domain using virsh)
I tried now directly using monitor in kvm and its command 'screendump picture' = worked well, correct picture was created as rawbits PPM image. virsh screenshot testdomain picture2 = hangs forever... Did you try taking a screeshot with kvm directly? -- Guido -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#647606: [Pkg-libvirt-maintainers] Bug#647606: [libvirt-bin] virsh screenshot domain not working (cannot get screenshot of domain using virsh)
Hi, I tested both virsh and python ways, both do work well with 0.9.7~rc2 ! Thanks a lot. David Pravec Thanks for testing! I tried to reproduce this with libvirt-0.9.7~rc2 and it works. Could you check if this version (in experimental) works for you? -- Guido -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#647606: [libvirt-bin] virsh screenshot domain not working (cannot get screenshot of domain using virsh)
Package: libvirt-bin Version: 0.9.6-2 Severity: normal --- Please enter the report below this line. --- when i am trying to get screenshot using libvirt, my code blocks forever, waiting for image data which are not coming. This happens when i do use libvirt from python as a library, and also when i use command 'virsh screenshot domain', which should fetch domain screenshot and save it into file. Some people on #virsh irc channel told me that its working on other systems, one of them confirmed that his sid machine also doesnt work well. This might mean its a packaging issue... I was not able to fully identify reason for this failure, as the python code is waiting forever for some C library... When i was testing following code, the problem occurs in last line: stream.recvAll(handler, fd) (it never calls the handler, just waiting forever) - #!/usr/bin/python -u import libvirt, os def handler(stream, buf, opaque): fd = opaque os.write(fd, buf) uri = qemu:///system vmname = test1 filename = screenshot.dat connection = libvirt.open(uri) domain = connection.lookupByName(vmname) stream = connection.newStream(0) mimetype = domain.screenshot(stream, 0, 0) print mimetype:, mimetype fd = os.open(filename, os.O_WRONLY | os.O_TRUNC | os.O_CREAT, 0644) stream.recvAll(handler, fd) - --- System information. --- Architecture: amd64 Kernel: Linux 3.0.0-2-amd64 Debian Release: wheezy/sid 550 unstable ftp.cz.debian.org 500 testing security.debian.org 500 testing ftp.cz.debian.org --- Package information. --- Depends (Version) | Installed ==-+- libavahi-client3 (= 0.6.16) | 0.6.30-5 libavahi-common3 (= 0.6.16) | 0.6.30-5 libblkid1 (= 2.17.2) | 2.19.1-5 libc6 (= 2.11) | 2.13-21 libcap-ng0 | 0.6.6-1 libdevmapper1.02.1 (= 2:1.02.20) | 2:1.02.67-1 libgcrypt11 (= 1.4.5) | 1.5.0-3 libgnutls26 (= 2.12.6.1-0) | 2.12.12-1 libnl1 (= 1.1) | 1.1-7 libparted0debian1 (= 2.2-1) | 2.3-8 libpcap0.8 (= 0.9.8) | 1.1.1-10 libpciaccess0 | 0.12.1-2 libreadline6 (= 6.0) | 6.2-7 libsasl2-2 | 2.1.25.dfsg1-2 libudev0 (= 0.140) | 172-1 libvirt0 (= 0.9.6-2) | 0.9.6-2 libxenstore3.0 (= 3.2.0) | 4.1.1-3 libxml2 (= 2.7.4) | 2.7.8.dfsg-5 libyajl1 (= 1.0.5) | 1.0.12-1 adduser | 3.113 logrotate | 3.7.8-6 gettext-base | 0.18.1.1-5 Recommends (Version) | Installed ==-+- netcat-openbsd | 1.89-4 bridge-utils | 1.5-2 dnsmasq-base (= 2.46-1) | 2.59-2 iptables (= 1.4.10) | 1.4.12-1 qemu-kvm | 0.15.1+dfsg-1 OR qemu (= 0.9.1) | 0.15.0+dfsg-1 libxml2-utils | 2.7.8.dfsg-5 gawk | 1:3.1.8+dfsg-0.1 ebtables | 2.0.9.2-2 dmidecode | 2.11-4 iproute | 20110629-1 parted | 2.3-8 Suggests (Version) | Installed ==-+-=== policykit-1 | 0.102-1 radvd |
Bug#606035: grub-pc: grub-install /dev/md0 fails (RAID-1)
Package: grub-pc Version: 1.98+20100804-8 Severity: important When installing fresh squeeze using fai i came to a problem with Raid-1 again. grub-pc version: 1.98+20100804-8 FAI failed to install on /dev/md0 device (raid-1 on /dev/sda1 and /dev/sdb1) Here is error i saw when ri was unning grub chrooted to new system on /target manually: --beg--- grub-install --no-floppy --modules=lvm raid /dev/md0 /usr/sbin/grub-setup: error: can't open /dev/md/0: No such file or directory. --end--- note -- there is no /dev/md/0-- i want to install on /dev/md0, which is there! in device map, there is only (hd0) and (hd1) -- mapped to sda and sdb, this works as workaround for me: --beg--- grub-install --no-floppy --modules=lvm raid (md0) Installation finished. No error reported --end--- Michael Tautschnig helped me to find this workaround for my fai installation, but still it would be nice to have grub working when we want to install on /dev/md0 Output of grub-install --debug /dev/md0 is here (its interesting near end): ==beg + setup_verbose=--verbose + bootdir=/boot + echo grub + sed s,x,x, + grubdir=/boot/grub + device_map=/boot/grub/device.map + grub_probe=/usr/sbin/grub-probe --device-map=/boot/grub/device.map + [ i386-pc = i386-pc ] + set /usr/sbin/grub-setup dummy + test -f /usr/sbin/grub-setup + : + set /usr/bin/grub-mkimage dummy + test -f /usr/bin/grub-mkimage + : + set /usr/sbin/grub-mkdevicemap dummy + test -f /usr/sbin/grub-mkdevicemap + : + mkdir -p /boot/grub + test no = yes + test -f /boot/grub/device.map + : + sed -n /^([fh]d[0-9]*)/s/\(^(.*)\).*/\1/p /boot/grub/device.map + sort + sed -n 1p + uniq -d + tmp= + test -n + test -f /boot/grub/915resolution.mod + basename /boot/grub/915resolution.mod + [ 915resolution.mod != menu.lst ] + rm -f /boot/grub/915resolution.mod + test -f /boot/grub/acpi.mod + basename /boot/grub/acpi.mod + [ acpi.mod != menu.lst ] + rm -f /boot/grub/acpi.mod + test -f /boot/grub/affs.mod + basename /boot/grub/affs.mod + [ affs.mod != menu.lst ] + rm -f /boot/grub/affs.mod + test -f /boot/grub/afs.mod + basename /boot/grub/afs.mod + [ afs.mod != menu.lst ] + rm -f /boot/grub/afs.mod + test -f /boot/grub/afs_be.mod + basename /boot/grub/afs_be.mod + [ afs_be.mod != menu.lst ] + rm -f /boot/grub/afs_be.mod + test -f /boot/grub/aout.mod + basename /boot/grub/aout.mod + [ aout.mod != menu.lst ] + rm -f /boot/grub/aout.mod + test -f /boot/grub/at_keyboard.mod + basename /boot/grub/at_keyboard.mod + [ at_keyboard.mod != menu.lst ] + rm -f /boot/grub/at_keyboard.mod + test -f /boot/grub/ata.mod + basename /boot/grub/ata.mod + [ ata.mod != menu.lst ] + rm -f /boot/grub/ata.mod + test -f /boot/grub/ata_pthru.mod + basename /boot/grub/ata_pthru.mod + [ ata_pthru.mod != menu.lst ] + rm -f /boot/grub/ata_pthru.mod + test -f /boot/grub/befs.mod + basename /boot/grub/befs.mod + [ befs.mod != menu.lst ] + rm -f /boot/grub/befs.mod + test -f /boot/grub/befs_be.mod + basename /boot/grub/befs_be.mod + [ befs_be.mod != menu.lst ] + rm -f /boot/grub/befs_be.mod + test -f /boot/grub/biosdisk.mod + basename /boot/grub/biosdisk.mod + [ biosdisk.mod != menu.lst ] + rm -f /boot/grub/biosdisk.mod + test -f /boot/grub/bitmap.mod + basename /boot/grub/bitmap.mod + [ bitmap.mod != menu.lst ] + rm -f /boot/grub/bitmap.mod + test -f /boot/grub/bitmap_scale.mod + basename /boot/grub/bitmap_scale.mod + [ bitmap_scale.mod != menu.lst ] + rm -f /boot/grub/bitmap_scale.mod + test -f /boot/grub/blocklist.mod + basename /boot/grub/blocklist.mod + [ blocklist.mod != menu.lst ] + rm -f /boot/grub/blocklist.mod + test -f /boot/grub/boot.mod + basename /boot/grub/boot.mod + [ boot.mod != menu.lst ] + rm -f /boot/grub/boot.mod test -f /boot/grub/bsd.mod + basename /boot/grub/bsd.mod + [ bsd.mod != menu.lst ] + rm -f /boot/grub/bsd.mod + test -f /boot/grub/bufio.mod + basename /boot/grub/bufio.mod + [ bufio.mod != menu.lst ] + rm -f /boot/grub/bufio.mod + test -f /boot/grub/cat.mod + basename /boot/grub/cat.mod + [ cat.mod != menu.lst ] + rm -f /boot/grub/cat.mod + test -f /boot/grub/chain.mod + basename /boot/grub/chain.mod + [ chain.mod != menu.lst ] + rm -f /boot/grub/chain.mod + test -f /boot/grub/cmostest.mod + basename /boot/grub/cmostest.mod + [ cmostest.mod != menu.lst ] + rm -f /boot/grub/cmostest.mod + test -f /boot/grub/cmp.mod + basename /boot/grub/cmp.mod + [ cmp.mod != menu.lst ] + rm -f /boot/grub/cmp.mod + test -f /boot/grub/configfile.mod + basename /boot/grub/configfile.mod + [ configfile.mod != menu.lst ] + rm -f /boot/grub/configfile.mod + test -f /boot/grub/cpio.mod + basename /boot/grub/cpio.mod + [ cpio.mod != menu.lst ] + rm -f /boot/grub/cpio.mod + test -f /boot/grub/cpuid.mod + basename /boot/grub/cpuid.mod + [ cpuid.mod != menu.lst ] + rm -f /boot/grub/cpuid.mod + test -f /boot/grub/crc.mod + basename /boot/grub/crc.mod + [ crc.mod != menu.lst ] + rm -f /boot/grub/crc.mod + test -f /boot/grub/crypto.mod + basename
Bug#326984: fontconfig: Bitstream Vera missing chars for Central Europe. Use DejaVu as preferred font.
Package: fontconfig Version: 2.3.2-1 Severity: important Please use DejaVu fonts (package ttf-dejavu) as default and preferred font. Defaulting to Bitstream Vera is not working for central european nations. DejaVu is derived from Bitstream Vera, having added important missing characters. It is probably the best font out there. DejaVu homepage: http://dejavu.sourceforge.net/ Problem: DejaVu fonts are not even listed in /etc/fonts/fonts.conf, and they should be on the first line, so apps asking for 'sans', 'serif' or 'mono' will get DejaVu fonts by default. Moreover, just editing local.conf didnt work for me. After reading http://lists.freedesktop.org/pipermail/fontconfig/2003-April/000229.html i created local.conf: =local.conf=== alias familysans-serif/family prefer familyDejaVu Sans/family /prefer /alias alias familyserif/family prefer familyDejaVu Serif/family /prefer /alias alias familymonospace/family prefer familyDejaVu Sans Mono/family /prefer /alias =/local.conf the result of defoma-reconfigure was making me angry a lot: .. Updating category cid.. Fontconfig error: local.conf, line 7: junk after document element Fontconfig error: local.conf, line 7: junk after document element Updating font configuration of gs... .. 'Error' was on the line containing second 'alias'. No junk there... Few tests revealed local.conf can have only one alias tag inside. why? This problem (bug?) maybe should be in separate bug report, but i am using it as an argument - Editing local.conf will not save us. Please change default configuration. David Pravec -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12-danix-2 Locale: LANG=cs_CZ, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C) Versions of packages fontconfig depends on: ii debconf [debconf-2.0] 1.4.58 Debian configuration management sy ii defoma 0.11.8-0.1 Debian Font Manager -- automatic f ii gsfonts-x11 0.17 Make Ghostscript fonts available t ii libc6 2.3.5-6 GNU C Library: Shared libraries an ii libfontconfig1 2.3.2-1 generic font configuration library ii msttcorefonts 1.2 Installer for Microsoft TrueType c ii ttf-bitstream-vera 1.10-3 The Bitstream Vera family of free ii ttf-freefont20031008-1.1 Freefont Serif, Sans and Mono True ii ucf 2.001Update Configuration File: preserv fontconfig recommends no packages. -- debconf information: fontconfig/subpixel_rendering: Automatic fontconfig/enable_bitmaps: false fontconfig/hinting_type: Native -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
