I don't think this was a fluke.
Reading the description and the symptoms this seems exactly what we have
been experiencing on three of our HP DL380 G6 servers. These three
server are identical (modulo disk capacity) and serve as our test beds
for Ubuntu Server 10.04 (freshly installed as of
Looks like I found it. The VM in my case is trying to access
/sys/devices/pci:00/:00:1e.0/:01:04.4/usb6/devnum
but the abstractions/libvirt-qemu profile only allows
/sys/bus/usb/devices/ r,
/sys/devices/*/*/usb[0-9]*/** r,
when it should (also) allow
Jamie, yes this fixes it. thank you!
I notice however some redundancies between abstractions/libvirt-qemu and
usr.lib.libvirt.virt-aa-helper? At least the line /sys/bus/usb/devices/
r, appears in both, don't know if that matters any, though. So that's
good :)
But now I have discovered something
Oh and it seems that disconnecting/detaching an USB device from the
running VM doesn't work at all? virt-manager complains:
Device could not be removed from the running machine.
This change will take effect after the next VM reboot
But this has probably nothing to do with AppArmor and may just
Interestingly, or perhaps not, merely running /etc/init.d/apparmor stop
isn't enough. I stop AppArmor, restart Libvirt and then start my VMs.
However upon starting a VM an AppArmor profile still gets loaded and
thus AppArmor denies access to the USB device I want to pass through. I
have to run
Looks like I found it. The VM in my case is trying to access
/sys/devices/pci:00/:00:1e.0/:01:04.4/usb6/devnum
but the abstractions/libvirt-qemu profile only allows
/sys/bus/usb/devices/ r,
/sys/devices/*/*/usb[0-9]*/** r,
when it should (also) allow
Jamie, yes this fixes it. thank you!
I notice however some redundancies between abstractions/libvirt-qemu and
usr.lib.libvirt.virt-aa-helper? At least the line /sys/bus/usb/devices/
r, appears in both, don't know if that matters any, though. So that's
good :)
But now I have discovered something
Oh and it seems that disconnecting/detaching an USB device from the
running VM doesn't work at all? virt-manager complains:
Device could not be removed from the running machine.
This change will take effect after the next VM reboot
But this has probably nothing to do with AppArmor and may just
I'm sorry to post to this bug that has a status of Fix released but I
am not sure it is really fixed. I have a situation similar too the
original poster's concerning a USB card reader that won't make it past
AppArmor it seems. Using libvirt-bin 0.7.5-5ubuntu27.
Situation: one of our servers was
I'm sorry to post to this bug that has a status of Fix released but I
am not sure it is really fixed. I have a situation similar too the
original poster's concerning a USB card reader that won't make it past
AppArmor it seems. Using libvirt-bin 0.7.5-5ubuntu27.
Situation: one of our servers was
Can also confirm the problem still exists and that changing terminal
size fixed it.
I only used the commandline interface of aptitude, i.e. the non-ncurses
one. I am somewhat baffled, how can the terminal size crash a program?
Never heard of that before :)
--
aptitude assert failure: *** glibc
Would also like to see this fixed for karmic. Using python-vmbuilder
0.11.3-0ubuntu1 and the same error occurs when trying to use a 10G LVM
volume as a --raw device. I assume this is the same bug.
sudo vmbuilder kvm ubuntu --debug --verbose -m 2048 --raw=/dev/mapper/vg
--storage-lv--chat_root
You are right of course, /etc/fstab on the guest contains /dev/sdXY
entries. These get generated by
/usr/share/pyshared/VMBuilder/plugins/ubuntu/feisty.py as you mentioned.
After changing all /dev/sdXY to /dev/vdXY I can indeed boot happily
:)
What threw me off was that QEMU did not (and does
Would also like to see this fixed for karmic. Using python-vmbuilder
0.11.3-0ubuntu1 and the same error occurs when trying to use a 10G LVM
volume as a --raw device. I assume this is the same bug.
sudo vmbuilder kvm ubuntu --debug --verbose -m 2048 --raw=/dev/mapper/vg
--storage-lv--chat_root
You are right of course, /etc/fstab on the guest contains /dev/sdXY
entries. These get generated by
/usr/share/pyshared/VMBuilder/plugins/ubuntu/feisty.py as you mentioned.
After changing all /dev/sdXY to /dev/vdXY I can indeed boot happily
:)
What threw me off was that QEMU did not (and does
Thanks for the comment, but how do you figure? I did not change anything
after the fact, I modified the template used for installation and setup
of the guest domain.
First, it seems to depend on the bus type whether the virtual disks are
at all visible to QEMU, as can be seen from the
Thanks for the comment, but how do you figure? I did not change anything
after the fact, I modified the template used for installation and setup
of the guest domain.
First, it seems to depend on the bus type whether the virtual disks are
at all visible to QEMU, as can be seen from the
Public bug reported:
Binary package hint: libvirt-bin
I can reproduce that trying to use bus='virtio' for virtual disks in the
definition of a libvirt domain makes virtual disks thus defined
disappear in the eyes of KVM/QEMU. This leads to error messages like the
following when booting, as well
** Attachment added: Domain definition for guest foo, using virtio for block
devices
http://launchpadlibrarian.net/38748978/foo.xml
--
Using virtio for block devices makes disks and partitions disappear in KVM/QEMU
(using vmbuilder and libvirt)
https://bugs.launchpad.net/bugs/517067
You
Public bug reported:
Binary package hint: libvirt-bin
I can reproduce that trying to use bus='virtio' for virtual disks in the
definition of a libvirt domain makes virtual disks thus defined
disappear in the eyes of KVM/QEMU. This leads to error messages like the
following when booting, as well
** Attachment added: Domain definition for guest foo, using virtio for block
devices
http://launchpadlibrarian.net/38748978/foo.xml
--
Using virtio for block devices makes disks and partitions disappear in KVM/QEMU
(using vmbuilder and libvirt)
https://bugs.launchpad.net/bugs/517067
You
This bug doesn't seem to have gotten much attention since July last year
but I can report that the issue still exists on Karmic using libvirt-bin
0.7.0-1ubuntu13.1:
$ virsh reboot foo1
Connecting to uri: qemu:///system
error: Failed to reboot domain foo1
error: this function is not supported by
This bug doesn't seem to have gotten much attention since July last year
but I can report that the issue still exists on Karmic using libvirt-bin
0.7.0-1ubuntu13.1:
$ virsh reboot foo1
Connecting to uri: qemu:///system
error: Failed to reboot domain foo1
error: this function is not supported by
** Description changed:
--
External SATA (eSATA) removable disk detected as system-internal
https://bugs.launchpad.net/bugs/153768
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I just ran into this bug as well. Using Kubuntu 9.04 (KDE 4.2.4) and an
Maudio Delta Audiophile 2496. The funny thing is that this is a quite
fresh install and everything worked fine until a day ago when I
installed, then uninstalled some gstreamer-related packages
(libgstreamer0.10-dev,
You know, it is really no problem to simply create the necessary file in
/etc/modprobe.d and put the options line in there like Nick suggested. I
find this workaround cleaner than letting the bluetooth module load and
then explicitly unload it later.
The following will create the file
I seem to be able to confirm that problem with the latest Alpha (6) of
Kubuntu. Knetworkmanager shows the network in question but connecting to
it simply doesn't work. The Gnome applet nm-applet on the other hand
works just fine. Hope this gets fixed in time.
--
network manager broken
Still a problem and a very annoying one, to say the least. There doesn't
even seem to be a hackish, dirty workaround. What does it take to get a
bluetooth mouse working in Hardy?
--
bluetooth mouse stopped working after bluez-utils and bluetooth update [hardy]
Obviously what needs to happen is for the maintainer of ubuntu-xen-
desktop to get enough time and leisure to take on this problem. At least
either remove the dependency on xenman (convirt) or create a package for
it.
However, there apparently *is* no maintainer who feels responsible for
this
During installation I selected that the server should be an OpenSSH as
well as a PostgreSQL server. Other than that I did nothing special as
far as I recall. After 'apt-get update', 'apt-get upgrade' and a reboot
I wanted to create a database for Horde. That's when I discovered that
PostgreSQL
I should have made this clearer, but I really do use
'/etc/init.d/postgresql-8.3 start' (as opposed to
'/etc/init.d/postgresql start') for starting the server.
That doesn't change anything, though. There is still no server to be
started.
--
PostgreSQL 8.3 server package very incomplete (missing
Interesting. I have removed, purged and reinstalled the PostgreSQL
packages by means of 'aptitude remove --purge ~npostgresql' countless
times last night, but any new installation always resulted in the same
behaviour I described above.
However, using 'dpkg -P postgresql-8.3
Public bug reported:
Binary package hint: postgresql-8.3
Running a standard 'apt-get install postgresql' on a freshly installed
Ubuntu 8.04 server should result in a working PostgreSQL installation in
/var/lib/postgresql/8.3 with configuration files accessible from
/etc/postgresql/8.3, as
Quoting Asa Zernik:
Just saying, it's not like Ubuntu is any more dependent on sudo than any other
*X system.
--
Well by default the root user (UID 0) has no password set and is as such
effectively disabled (passwd -l root). Sure you can sudo su or sudo
-s but that is a function of sudo and
It's still a month or so before Hardy will be released so hopefully this
bug will get the attention it needs. No need to be disappointed just yet
:)
--
[madwifi] NetworkManager 0.6.6-0ubuntu1 fails to connect to wireless network
https://bugs.launchpad.net/bugs/199802
You received this bug
This is still or again a problem in Hardy (Alpha 6, current as of
today). When closing the lid of my Thinkpad T41p I get these messages in
/var/log/acpid. No need to mention that putting the laptop to sleep
doesn't work.
[Thu Mar 13 00:16:50 2008] received event button/lid LID 0080 0002
Same here on a Thinkpad T41p using Kubuntu Hardy Alpha 6 and a WPA2
wireless network. Manually invoking wpa_supplicant and dhclient works
fine, wpa_supplicant.conf contains the following:
network = {
proto = WPA2
ssid = MYSSID
key_mgmt = WPA-PSK
pairwise = CCMP
psk = MYKEY
priority =
Public bug reported:
Binary package hint: kdepim
It is probably not right to report this here, but neither is it right,
IMHO, to bug Jonathan Riddel via personal e-Mail, so I'll take my
chances here.
As mentioned [1] KDE 3.5.8 was released a few days ago and apparently
most of it has already
Hello,
excuse my trying to take advantage of the momentum this bug report seems
to still have, but I have a somewhat related issue accessing a removable
external SATA (eSATA) disk formatted with Ext3. I am using the latest
Kubuntu 7.10 (which by now should be all but properly released) with KDE
Public bug reported:
Binary package hint: hal
I have posted about this in bug 115768 as well and will copy most of
what I've written there.
I am using the latest Kubuntu 7.10 (which by now should be all but
properly released) with KDE 3.5.7:
Linux thehostname 2.6.22-14-generic #1 SMP Sun Oct
** Attachment added: lshal output. The disk in question can be found as
HD501LJ.
http://launchpadlibrarian.net/10055168/lshal.txt
--
External SATA (eSATA) removable disk (formatted with Ext3) not mounted
automatically: hal-storage-fixed-mount refused uid 1000
** Attachment added: dmesg.txt
http://launchpadlibrarian.net/10055169/dmesg.txt
--
External SATA (eSATA) removable disk (formatted with Ext3) not mounted
automatically: hal-storage-fixed-mount refused uid 1000
https://bugs.launchpad.net/bugs/153768
You received this bug notification because
** Attachment added: hal.log
http://launchpadlibrarian.net/10055170/hal.log
--
External SATA (eSATA) removable disk (formatted with Ext3) not mounted
automatically: hal-storage-fixed-mount refused uid 1000
https://bugs.launchpad.net/bugs/153768
You received this bug notification because you
** Attachment added: devices.txt
http://launchpadlibrarian.net/10055171/devices.txt
--
External SATA (eSATA) removable disk (formatted with Ext3) not mounted
automatically: hal-storage-fixed-mount refused uid 1000
https://bugs.launchpad.net/bugs/153768
You received this bug notification
Just to report back, 4.3.2-0ubuntu3 (on Gutsy) fixed the problem for me.
Thanks Jonathan!
--
On a multihead Xinerama setup, menus in qt4 apps are displayed in wrong places
https://bugs.launchpad.net/bugs/135882
You received this bug notification because you are a member of Kubuntu
Team, which is
Apparently the broken patches are applied in the new versions provided
by Ubuntu as well. I see the same menu placement behaviour with
libqt4-(core|gui) in version 4.3.2-0ubuntu2. I have yet to try the
updated Debian versions (see [1] and [2] in previous comment).
--
On a multihead Xinerama
Stefan,
when installing the Debian packages for 4.3.1-1 (qt4-x11/4.3.1-1) I had
no problems whatsoever, no need to force anything. Some development
packages (libqt4-*-dev) I had to uninstall because they depended
directly on the libqt4-core and -gui packages provided by Ubuntu but
that was all.
Stefan,
no wonder you had problems manually installing the Debian packages; they
worked fine for me since I run Gutsy, not Feisty. Anyway, will test once
I'm home.
Thank you Jonathan for (hopefully) fixing this PITA! :) Much
appreciated.
--
On a multihead Xinerama setup, menus in qt4 apps are
For the record, and until this is fixed, an easy and dirty way to work
around this bug is to download the Debian packages of libqt4-core [1]
and libqt4-gui [2] and install them using dpkg -i. After the restart of
an affected Qt4 application the problem is gone. If yet to notice any
ill side
Please see bug #135882 for an explanation and a possible workaround.
--
Qt popups on wrong monitor with TwinView/xinerama
https://bugs.launchpad.net/bugs/145217
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
Same problem for me as well with a Canon LiDE30.
--
some usb_devices fault if usb_suspend enabled
https://bugs.launchpad.net/bugs/85488
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Public bug reported:
Binary package hint: hal
I suspect this is a HAL issue but I haven't found a similar bug filed.
Using:
Kubuntu 7.04
hal-0.5.8.1-4ubuntu12
Third generation iPod (FAT-formatted and connected via firewire).
Problem description:
Plugging in the iPod doesn't draw any reaction
Thanks for the hint Adrian!
To make this work fully I had to execute kcmshell thinkpad, activate
Run Thinkpad Buttons KMilo plugin and deactivate Change volume in
software. Then I had to go to System Settings, Advanced, Service
Manager, select KMilo, stop the service, then restart it.
After that
*** This bug is a duplicate of bug 51537 ***
https://bugs.launchpad.net/bugs/51537
The following I also posted in bug #76091.
To make this work fully I had to execute kcmshell thinkpad, activate
Run Thinkpad Buttons KMilo plugin and deactivate Change volume in
software. Then I had to go to
Please see bug #76091 for a workaround on this problem.
--
Wrong handling of volume buttons on IBM Thinkpad notebooks
https://bugs.launchpad.net/bugs/51537
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
I, too, can confirm this on my Thinkpad T41p and an up-to-date Edgy.
Is there a way to disable this behaviour and just rely on the hardware
mixing capabilities of our Thinkpads?
--
Wrong handling of volume buttons on IBM Thinkpad notebooks
https://launchpad.net/bugs/51537
--
ubuntu-bugs
Public bug reported:
Binary package hint: kdeutils
First: the volume keys (volume up, volume down, mute) work fine.
Using a Thinkpad T41p with Kubuntu 6.10 I had to install kmilo-legacy
and enable it in the KDE control centre. That apparently was the only
way to get on-screen display messages
*** This bug is a duplicate of bug 37275 ***
I think I found another incarnation of this error. Running Kubuntu Edgy,
with kde-guidance 0.7.0-0ubuntu4 on my Thinkpad T41p with a Radeon M10
(FireGL T2) and the open source drivers from Xorg.
I don't think it has to do with numbers getting i18n'd
101 - 158 of 158 matches
Mail list logo
