Bug#1059158: libreoffice-core-nogui: Can't open a spreadsheet from python uno because libforuilo.so is missing.
Package: libreoffice-core-nogui Version: 4:7.4.7-1 Severity: important Dear Maintainer, * What led up to the situation? tried to open an existing spreadsheet using python uno * What exactly did you do (or not do) that was effective (or ineffective)? after adding libforuilo.so found in the libreoffice-core, to /usr/lib/libreoffice/program, opening an existing spreadsheet succeeded * What was the outcome of this action? no document was opened, no feedback * What outcome did you expect instead? that it was possible to open an existing or new spreadsheet using loadComponentFromURL -- Package-specific info: All deployed bundled extensions: All deployed shared extensions: All deployed user extensions: Experimental features enabled: Java (javaldx): /usr/lib/jvm/java-17-openjdk-armhf/lib/arm/client:/usr/lib/jvm/java-17-openjdk-armhf/lib/arm/server:/usr/lib/jvm/java-17-openjdk-armhf/lib/arm/native_threads:/usr/lib/jvm/java-17-openjdk-armhf/lib/arm Java: http://openoffice.org/2004/java/framework/1.0; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;> file:///usr/lib/jvm/java-17-openjdk-armhf -- System Information: Debian Release: 12.0 merged-usr: no Architecture: armhf (armv7l) Kernel: Linux 6.1.65-v7+ (SMP w/4 CPU threads) Kernel taint flags: TAINT_CRAP Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages libreoffice-core-nogui depends on: ii fontconfig 2.14.1-4 ii fonts-opensymbol 4:102.12+LibO7.4.7-1 ii libabsl20220623 20220623.1-1 ii libboost-locale1.74.01.74.0+ds1-21 ii libc62.36-9+deb12u3 ii libcairo21.16.0-7 ii libclucene-contribs1v5 2.3.3.4+dfsg-1.1 ii libclucene-core1v5 2.3.3.4+dfsg-1.1 ii libcurl3-gnutls 7.88.1-10+deb12u4 ii libdconf10.40.0-4 ii libeot0 0.01-5+b1 ii libexpat12.5.0-1 ii libexttextcat-2.0-0 3.4.5-1 ii libfontconfig1 2.14.1-4 ii libfreetype6 2.12.1+dfsg-5 ii libgcc-s112.2.0-14 ii libglib2.0-0 2.74.6-2 ii libgpgmepp6 1.18.0-3+b1 ii libgraphite2-3 1.3.14-1 ii libharfbuzz-icu0 6.0.0+dfsg-3 ii libharfbuzz0b6.0.0+dfsg-3 ii libhunspell-1.7-01.7.1-1 ii libhyphen0 2.8.8-7 ii libicu72 72.1-3 ii libjpeg62-turbo 1:2.1.5-2 ii liblcms2-2 2.14-2 ii libldap-2.5-02.5.13+dfsg-5 ii libmythes-1.2-0 2:1.2.5-1 ii libnspr4 2:4.35-1 ii libnss3 2:3.87.1-1 ii libnumbertext-1.0-0 1.0.11-1 ii libopenjp2-7 2.5.0-2 ii liborcus-0.17-0 0.17.2-2+b2 ii libpng16-16 1.6.39-2 ii libpoppler12622.12.0-2+b1 ii libraptor2-0 2.0.15-4 ii librdf0 1.0.17-3 ii libreoffice-common 4:7.4.7-1 ii librevenge-0.0-0 0.0.5-3 ii libstdc++6 12.2.0-14 ii libtiff6 4.5.0-6+deb12u1 ii libuno-cppu3 4:7.4.7-1 ii libuno-cppuhelpergcc3-3 4:7.4.7-1 ii libuno-sal3 4:7.4.7-1 ii libuno-salhelpergcc3-3 4:7.4.7-1 ii libwebp7 1.2.4-0.2+deb12u1 ii libxml2 2.9.14+dfsg-1.3~deb12u1 ii libxmlsec1 1.2.37-2 ii libxmlsec1-nss 1.2.37-2 ii libxslt1.1 1.1.35-1 ii uno-libs-private 4:7.4.7-1 ii ure 4:7.4.7-1 ii zlib1g 1:1.2.13.dfsg-1 Versions of packages libreoffice-core-nogui recommends: ii libpaper-utils 1.1.29 libreoffice-core-nogui suggests no packages. Versions of packages libreoffice-common depends on: ii libnumbertext-data 1.0.11-1 ii libreoffice-style-colibre 4:7.4.7-1 ii ucf3.0043+nmu1 ii ure4:7.4.7-1 Versions of packages libreoffice-common recommends: ii apparmor3.0.8-3 ii fonts-liberation2 2.1.5-1 ii libexttextcat-data 3.4.5-1 ii poppler-data0.4.12-1 ii python3-uno 4:7.4.7-1 ii xdg-utils 1.1.3-4.1 Versions of packages libreoffice-common suggests: ii libreoffice-style-colibre [libreoffice-style] 4:7.4.7-1 Versions of packages libreoffice-java-common depends on: ii liblibreoffice-java 4:7.4.7-1 ii libreoffice-common 4:7.4.7-1 ii libunoloader-java4:7.4.7-1 ii ure-java 4:7.4.7-1 Versions of packages fonts-opensymbol recommends: ii fontconfig 2.14.1-4 Versions of packages ure-java depends on: ii libc62.36-9+deb12u3 ii libgcc-s112.2.0-14 ii libstdc++6 12.2.0-14 ii libuno-cppu3 4:7.4.7-1 ii libuno-cppuhelpergcc3-3 4:7.4.7-1 ii libuno-sal3 4:7.4.7-1 ii libuno-salhelpergcc3-3 4:7.4.7-1 ii libunoloader-java4:7.4.7-1 ii
Bug#644430: closed by Niels Thykier ni...@thykier.net (Re: installer should give warning when creating GPT without BIOS BOOT partition)
so was this addressed in =7 versions? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#644389: suspect non-working mdadm.conf created during install
It's not the wrong hostname, it is what was current when the array was created. yes, but i think it's the hostname when the initramfs was created for the installer. At least we should make sure this is the case. Could you investigate what the 'hostname' command outputs on the d-i shell, just before creating an array in partman during the install? i checked and it behaves like expected: it reports '(none)' up to the point where i set it to 'file'. afterwards it reports 'file'. i installed _without_ RAID and used guided partitioning this time. after the system is installed i took a look into /target and there was the hetzner-mdadm.conf more evidence for the d-i deploys standard initramfs with broken/suspect/unupdated mdadm.conf: 1) initramfs has an old timestamp (2011-08-27) and contains a comment that it was autogenerated that day sha1sum is: a8f016e70843f108ae05ab0ef874eaad231005c8 initrd.img-2.6.32-5-amd64 2) last time i configured two arrays, but mdadm.conf contains three. my problem is, that i cannot find it on the install medium (or a file big enough to hold it, tat actually contains it). There are three ways forward, really: 1. figure out a way by which the initramfs is updated when the hostname is changed; there's only one way and it's updating the initramfs when nessessary (RAID config) and remove it when not needed. 2. make sure the admin knows that changing the hostname requires telling mdadm; 3. provide a debconf setting to disable the homehost feature (setting it toignore). the UUIDs are different, that's why the array don't get assembled. since you should now be able to reproduce (even without RAID) i'll trash those VM images. cheers pille DEVICE partitions HOMEHOST system ARRAY /dev/md/0 metadata=1.2 UUID=f6de5584:d9dbce39:090f16ff:f795e54c name=hetzner:0 ARRAY /dev/md/1 metadata=1.2 UUID=0e065fee:15dea43e:f4ed7183:70d519bd name=hetzner:1 ARRAY /dev/md/2 metadata=1.2 UUID=ce4dd5a8:d8c2fdf4:4612713e:06047473 name=hetzner:2 # mdadm.conf # # Please refer to mdadm.conf(5) for information about this file. # # by default, scan all partitions (/proc/partitions) for MD superblocks. # alternatively, specify devices to scan, using wildcards if desired. DEVICE partitions # auto-create devices with Debian standard permissions CREATE owner=root group=disk mode=0660 auto=yes # automatically tag new arrays as belonging to the local system HOMEHOST system # instruct the monitoring daemon where to send mail alerts MAILADDR root # definitions of existing MD arrays ARRAY /dev/md/0 metadata=1.2 UUID=f6de5584:d9dbce39:090f16ff:f795e54c name=hetzner:0 ARRAY /dev/md/1 metadata=1.2 UUID=0e065fee:15dea43e:f4ed7183:70d519bd name=hetzner:1 ARRAY /dev/md/2 metadata=1.2 UUID=ce4dd5a8:d8c2fdf4:4612713e:06047473 name=hetzner:2 # This file was auto-generated on Sat, 27 Aug 2011 19:16:33 + # by mkconf 3.1.4-1+8efb9d1
Bug#644374: partclone.reiserfs is not installed
Package: partclone Version: 0.2.29-1 Severity: important hi, partclone from wheezy doesn't contain /usr/sbin/partclone.reiserfs, so there's no support to backup reiser3 volumes. -- System Information: Debian Release: 6.0.2 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-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 partclone depends on: ii e2fslibs 1.42~WIP-2011-07-02-1 ext2/ext3/ext4 file system librari ii libc6 2.11.2-10 Embedded GNU C Library: Shared lib ii libcomerr2 1.41.12-4stable1 common error description library ii libncursesw5 5.7+20100313-5shared libraries for terminal hand ii libntfs10 2.0.0-1+b1library that provides common NTFS ii libuuid1 2.17.2-9 Universally Unique ID library partclone recommends no packages. partclone 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#644389: suspect non-working mdadm.conf created during install
Package: mdadm Version: 3.1.4-1+8efb9d1 Severity: critical Tags: d-i Justification: breaks the whole system during install of squeeze i partitioned my disks and setup different MD-RAID devices using the partition tool. the corresponding /dev/mdX devices were created properly and i went on creating LVM ontop of it and successfully installed the system. first boot into my new system failed because the root FS could not be found, leaving me in a initramfs-shell. i assembled my RAID devices by hand and compared /etc/mdadm/mdadm.conf (inside initramfs) with 'mdadm --examine --scan', which listed completely different UUIDs. the count of my MD-devices was ok, but all names were prefixed with hostname 'hetzner'. after booting, fixing (the systems) /etc/mdadm/mdadm.conf and update-initramfs all went fine. i don't remember the exact content, but install generated a mdadm.conf like: ARRAY /dev/md/0 metadata=1.2 UUID=12345678:12345678:12345678:12345678 name=hetzner:0 ARRAY /dev/md/1 metadata=1.2 UUID=24680135:24680135:24680135:24680135 name=hetzner:1 ARRAY /dev/md/2 metadata=1.2 UUID=abcdef12:abcdef12:abcdef12:abcdef12 name=hetzner:2 (UUIDs are made up) disks used were new empty and had no affiliation to hetzner online AG you can search the net for 'name=hetzner: mdadm.conf' to yield probably the original UUIDs. pille --- initrd.img-2.6.32-5-amd64: 47498 blocks 3718babf31303bc28114430ec0182e14 ./etc/mdadm/mdadm.conf d24ed7389311fb002ff017c8acb3a032 ./lib/modules/2.6.32-5-amd64/kernel/drivers/md/dm-mirror.ko 4818680648975a4d4181181df95de446 ./lib/modules/2.6.32-5-amd64/kernel/drivers/md/dm-log.ko bb013669544366b71ebd8b335a7d8b0a ./lib/modules/2.6.32-5-amd64/kernel/drivers/md/dm-mod.ko ee2079d7e0bf4da6b64af9e579f6c0ae ./lib/modules/2.6.32-5-amd64/kernel/drivers/md/raid456.ko b210dd35ca38b2e33637351a979561c9 ./lib/modules/2.6.32-5-amd64/kernel/drivers/md/multipath.ko 0c8325eb1abcf4ad33e45a20d44c5bf8 ./lib/modules/2.6.32-5-amd64/kernel/drivers/md/dm-crypt.ko f25a213d65a481b66cfdbf8f6453aacf ./lib/modules/2.6.32-5-amd64/kernel/drivers/md/dm-region-hash.ko cc5177855661025115a2ef74d0d394d6 ./lib/modules/2.6.32-5-amd64/kernel/drivers/md/raid0.ko -- System Information: Debian Release: 6.0.2 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-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 mdadm depends on: ii debconf 1.5.36.1 Debian configuration management sy ii libc6 2.11.2-10Embedded GNU C Library: Shared lib ii lsb-base3.2-23.2squeeze1 Linux Standard Base 3.2 init scrip ii udev164-3/dev/ and hotplug management daemo Versions of packages mdadm recommends: ii exim4-daemon-light [mail 4.72-6+squeeze2 lightweight Exim MTA (v4) daemon ii module-init-tools3.12-1 tools for managing Linux kernel mo mdadm suggests no packages. -- debconf information: mdadm/autostart: true mdadm/mail_to: root mdadm/initrdstart_msg_errmd: mdadm/initrdstart: all mdadm/initrdstart_msg_errconf: mdadm/initrdstart_notinconf: false mdadm/initrdstart_msg_errexist: mdadm/initrdstart_msg_intro: mdadm/autocheck: true mdadm/initrdstart_msg_errblock: mdadm/start_daemon: true -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#644389: suspect non-working mdadm.conf created during install
i assembled my RAID devices by hand How? something like: mdadm --assemble /dev/md1 /dev/sd[abcd]4 but all names were prefixed with hostname 'hetzner'. What names? You mean the name= attribute in the mdadm --examine output? excactly. Please provide the exact original and new UUIDs, don't expect me to search the Net for them (I am offline right now). unfortunately i cannot provide you with those. if i could i would have done so, already. the install was a week ago and i don't have any backups of a broken config. don't expect me to memorize UUIDs. Also, did you change the hostname? no. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#644389: suspect non-working mdadm.conf created during install
In this case there is very little I can do. I have done multiple squeeze installs with RAID, and upgrades, and I have not seen this problem. Unless you can reproduce this bug, I cannot do anything but keep this report open. i've just reproduced such a failing install inside a KVM. see (combined) screenshot attached from first boot. i've snapshotted the VM at different stages and can provide you with one that just boots for the first time (snapshot3, see screenshot). tell me if you're interrested in investigating it. here's a log of what i did: booted http://cdimage.debian.org/debian-cd/current-live/amd64/iso-hybrid/debian-live-6.0.2-amd64-rescue.iso (sha1=0e5d9409719e657de4cbd9f355545cdc4c869038) expert text install selected some udebs (parted, reiserfs, squash, virtio) hostname = file.lan partition manual for all 4 disks: GPT p1: 6MB BIOS BOOT p2: 250MB RAID1 BOOT p3: 768MB SWAP p4: 3.3GB RAID6 VG/PV configure sw raid: md0: RAID1 /dev/sd[a-d]2: /boot (ext2) md1: RAID6 /dev/sd[a-d]4: LVM PV (VG=vg-sys) configure LVM: LV system: /dev/md1 (4GB) / (reiserfs) snapshot1 install system (normal) install grub finish snapshot2 reboot snapshot3 cheers pille attachment: screenshot.png
Bug#644428: grub2 does not install into all disks MBR when using a MD-RAID1
Package: grub2 Version: grub-pc 1.98+201008ß4-14 Severity: normal Tags: d-i when installing a new squeeze system i noticed that it's not possible to make grub install into multiple MBRs using the installer. since my boot partition is on a RAID1 i'd like grub to be installed with redundancy, too. IMHO ubuntu supports this. workaround: after install: for DISK in sdb sdc sdd; do grub-install /dev/$DISK; done probably this is an issue when upgrading grub, too. -- System Information: Debian Release: 6.0.2 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-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 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#644430: installer should give warning when creating GPT without BIOS BOOT partition
Package: installer Version: installer of squeeze 6.0.2 Severity: wishlist Tags: d-i when installing squeeze on GPT grub needs a special BIOS BOOT partition to fake MBR. there should be a warning/advise when creating a GPT that you need a small special partition. it's a lot of extra work to learn this the hard way (grub install to MBR fails) after you spent 1h on partitioning multiple disks and adding layers like RAID, LVM and crypt on it after installing the system. of course it's just my fault to have done this for the first time, without reading all the GPT specs, but the installer inveigled me. -- System Information: Debian Release: 6.0.2 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-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 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#644389: suspect non-working mdadm.conf created during install
So it looks like during install time, in d-i, the system were named hetzer (most likely due to DHCP), and all md arrays were created using that name. And later on, it fails to boot with actual hostname. i' don't know if it's the initramfs shipped with d-i, but today i did an offline install. no net, no DHCP, no hetzner datacenter. i completely understand what happens as i'm able to boot the system by manually assembling the array and fixing the problem, but how the wrong hostname slips into the initramfs should be investigated by debians devs. Note that mdadm.conf in initrd contains name hetzer, while actual arrays are named file. that's what i'm talking about. Is your real hostname file ? yes. pille -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#618463: please backport mdadm-3.2.2-1 to current stable
hi, i've suffered from the same bug and spent the last three days resizing the (physical GPT) partitions of my underlying raid6 devices and trying to grow the array. i did disk-by-disk rebuilds in order to make mdadm notice the new space, but it didn't work. today i stumbled upon this bug and reviewed the mdadm changelog, which fixes this bug. i sucessfully grew the array using the version from nightly install CD. please backport from testing to stable. thanks pille -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#580380: Fwd: Re: serial support
hi marco, do you have any reference to your upstream conversation? pille Original Message Subject: Re: serial support Date: Wed, 12 May 2010 13:05:04 -0500 From: Mike Christie micha...@cs.wisc.edu To: pille pille+open-is...@struction.de CC: open-is...@googlegroups.com On 05/12/2010 12:47 PM, pille wrote: On 05/12/2010 07:45 PM, Mike Christie wrote: Which message in there are you referring to? the one i quoted is #27 (http://bugs.debian.org/580380#27) There is not some sort of config option to turn on/off serial number support in the initiator. scsi_id sends SG IO requests to get the serial info and the initiators just process that IO like any other IO. It does not know or care where it is coming from. Could you ask the person on the debain bugzilla to point to the upstream reply. I can then comment on that thread directly. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#580380: report on testing
hi, tested on a machine running squeeze/testing at the moment. still nothing under /dev/disk/by-id/ but under /dev/disk/by-path/. strange detail: /etc/udev/rules.d/ is nearly empty (only 70-persistent-cd.rules). but there's one thing that got better: xen2:~# /lib/udev/scsi_id -g -x /dev/sda ID_SCSI=1 ID_VENDOR=Novell ID_VENDOR_ENC=Novell\x20\x20 ID_MODEL=00cb045d-d54e-df ID_MODEL_ENC=00cb045d-d54e-df ID_REVISION=0 ID_TYPE=disk xen2:~# echo $? 0 udev is now 153 pille -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#580380: udev: no /dev/disk/by-id/ symlink for ISCSI device created
hi marco, Version: 0.125-7+lenny3 I have no idea if iSCSI is supported by this old version of udev. looks like people with another iSCSI initiator can use it: http://forum.proxmox.com/threads/3805#post21558 Please try the one from unstable. can't do so at the moment, but will try next week. this breaks several programs that depend on the later symlink for detecting storage. Exactly how do they depend on specific persistent symlinks? proxmox detects and integrates different kinds of (shared) storage and uses these links to identify. for cross-reference the obove URI points to the bug discussion in their forum. pille -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#580380: udev: no /dev/disk/by-id/ symlink for ISCSI device created
Package: udev Version: 0.125-7+lenny3 Severity: important *** Please type your report below this line *** I use ISCSI targets provided by a novell-cluster. They are /dev/sda and /dev/sdb. there are symlinks created by /dev/udev/rules.d/60-persistent-storage.rules in /dev/disk/by-path/ but not in /dev/disk/by-id/. this breaks several programs that depend on the later symlink for detecting storage. the output of: kvm2:/# /lib/udev/scsi_id -g -x -s /dev/sda is empty. return code is 1. (same for sdb) -- kvm2:/# ls -lR /dev/disk/ $ /dev/disk/: total 0 drwxr-xr-x 2 root root 220 2010-05-05 16:26 by-id drwxr-xr-x 2 root root 200 2010-05-05 16:34 by-path drwxr-xr-x 2 root root 140 2010-05-05 16:34 by-uuid /dev/disk/by-id: total 0 lrwxrwxrwx 1 root root 16 2010-05-05 16:26 cciss-3600508b1001fa00db63847790006 - ../../cciss/c0d0 lrwxrwxrwx 1 root root 18 2010-05-05 16:26 cciss-3600508b1001fa00db63847790006-part1 - ../../cciss/c0d0p1 lrwxrwxrwx 1 root root 18 2010-05-05 16:26 cciss-3600508b1001fa00db63847790006-part2 - ../../cciss/c0d0p2 lrwxrwxrwx 1 root root 10 2010-05-05 16:26 dm-name-pve-data - ../../dm-2 lrwxrwxrwx 1 root root 10 2010-05-05 16:26 dm-name-pve-root - ../../dm-1 lrwxrwxrwx 1 root root 10 2010-05-05 16:26 dm-name-pve-swap - ../../dm-0 lrwxrwxrwx 1 root root 10 2010-05-05 16:26 dm-uuid-LVM-Y15dbr4aw8jzwh2fTKo7bbuiQvKHtZJk0OdZILt70Ub2kHueW2trUK5UTiQF7WbI - ../../dm-0 lrwxrwxrwx 1 root root 10 2010-05-05 16:26 dm-uuid-LVM-Y15dbr4aw8jzwh2fTKo7bbuiQvKHtZJkVD0HjP8PDdeC8tt6YlbIleKg93UIfV99 - ../../dm-1 lrwxrwxrwx 1 root root 10 2010-05-05 16:26 dm-uuid-LVM-Y15dbr4aw8jzwh2fTKo7bbuiQvKHtZJkwtVQ1ghe5loFyHkDQilPqB4dnGmhcNot - ../../dm-2 /dev/disk/by-path: total 0 lrwxrwxrwx 1 root root 9 2010-05-05 16:34 ip-192.168.2.5:3260-iscsi-iqn.1984-08.com.novell:00cb045d-d54e-df11-aab5-0013d4b31141-lun-0 - ../../sdb lrwxrwxrwx 1 root root 10 2010-05-05 16:34 ip-192.168.2.5:3260-iscsi-iqn.1984-08.com.novell:00cb045d-d54e-df11-aab5-0013d4b31141-lun-0-part1 - ../../sdb1 lrwxrwxrwx 1 root root 9 2010-05-05 16:32 ip-192.168.2.5:3260-iscsi-iqn.1984-08.com.novell:80e2a210-bd3c-df11-a70d-0013d4b3103c-lun-0 - ../../sda lrwxrwxrwx 1 root root 9 2010-05-05 16:26 pci-:00:1f.1-ide-0:0 - ../../hda lrwxrwxrwx 1 root root 16 2010-05-05 16:26 pci-:04:01.0-cciss-c0d0 - ../../cciss/c0d0 lrwxrwxrwx 1 root root 18 2010-05-05 16:26 pci-:04:01.0-cciss-c0d0-part1 - ../../cciss/c0d0p1 lrwxrwxrwx 1 root root 18 2010-05-05 16:26 pci-:04:01.0-cciss-c0d0-part2 - ../../cciss/c0d0p2 /dev/disk/by-uuid: total 0 lrwxrwxrwx 1 root root 10 2010-05-05 16:26 1e5cc8df-def4-442e-a333-6f42d43fa453 - ../../dm-1 lrwxrwxrwx 1 root root 10 2010-05-05 16:26 343e2c29-d0b7-401f-9114-bc06f5ebabd6 - ../../dm-0 lrwxrwxrwx 1 root root 10 2010-05-05 16:34 3aa6fe95-40e1-4ab2-9ae2-cc3a7f892ac4 - ../../sdb1 lrwxrwxrwx 1 root root 18 2010-05-05 16:26 40a36c98-0051-4ba8-a0fc-59a3652edf93 - ../../cciss/c0d0p1 lrwxrwxrwx 1 root root 10 2010-05-05 16:26 74f6c635-e8fc-4285-b897-a80032ac92f9 - ../../dm-2 -- # kvm2:/# lsscsi -v [0:0:0:0]diskNovell 80e2a210-bd3c-df 0 /dev/sda dir: /sys/bus/scsi/devices/0:0:0:0 [/sys/devices/platform/host0/session1/target0:0:0/0:0:0:0] [1:0:0:0]diskNovell 00cb045d-d54e-df 0 /dev/sdb dir: /sys/bus/scsi/devices/1:0:0:0 [/sys/devices/platform/host1/session2/target1:0:0/1:0:0:0] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#573574: xen-hypervisor-3.4-i386: xen-hypervisor does not boot inside KVM machine
Package: xen-hypervisor-3.4-i386 Version: 3.4.3~rc3-1 Severity: normal i want to run the xen-hypervisor inside a KVM machine. hypervisor is booting - blanks screen and stops before loading dom0. it may sound strange to run a VM inside a VM, but i need this for testing. the virtualized domUs should be run paravirtualized. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.32-trunk-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash xen-hypervisor-3.4-i386 depends on no packages. Versions of packages xen-hypervisor-3.4-i386 recommends: ii xen-utils-3.43.4.3~rc3-1 XEN administrative tools Versions of packages xen-hypervisor-3.4-i386 suggests: pn xen-docs-3.4 none (no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#573574: [Pkg-xen-devel] Bug#573574: xen-hypervisor-3.4-i386: xen-hypervisor does not boot inside KVM machine
In general I think one would consider this sort of issue to be a problem with the containing VMM (i.e. KVM in this case) in the first instance. i'll agree with you, but last week booting the _lenny_ xen dom0 kernel (2.6.26-2-xen-686 - 2.6.26-21lenny3) booted until it ran into another issue. however, it's also possible to treat each VMM as an architecture ;-) cheers pille -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#573574: [Pkg-xen-devel] Bug#573574: xen-hypervisor-3.4-i386: xen-hypervisor does not boot inside KVM machine
So it sounds like a change to the kernel has caused this issue to arise? no. testing kernel never worked. stable kernel with testing hypervisor stopped working. The hypervisor remained the same? no, i retested because the hypervisor in testing was upgraded. pille -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#402974: fix in etch
hi, if there's a simple patch for this annoying bug for over a year, why wasn't it fixed in current stable release. please to so, since i'm tired of patching it on all machines. pille -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#327024: 127.000.000.001 is dead, long live 127.0.0.1, or hostname: Unknown host
Package: libc6 Version: 2.3.5-6 Severity: serious Hallo, I have the (bad, it seems) habitude of putting leading zeroes in the IP-addresses in /etc/hosts. eg. 127.000.000.001 localhost.localdomain localhost 192.168.001.002 ghp-medp4.ghp.be ghp-medp4 Since I ran aptitude last weekend (3/9/2005), and libc6 was upgraded (amongst others!), I have the following problem: # hostname ghp-medp4 # hostname -v -f gethostname()=`ghp-medp4' Resolving `ghp-medp4' ... hostname: Unknown host This system could not send mail anymore, using sendmail, which reported stat=Data format error, so I started looking for the cause. It took me a couple of hours before I was so desperate that I removed the leading zeroes from the ip-addresses in /etc/hosts, and lo and behold: # hostname -v -f gethostname()=`ghp-medp4' Resolving `ghp-medp4' ... Result: h_name=`ghp-medp4.ghp.be' Result: h_aliases=`ghp-medp4' Result: h_addr_list=`192.168.1.52' ghp-medp4.ghp.be -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.13 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) -- no debconf information __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
