Public bug reported:
After the 6:9.20-0ubuntu0.14.04.1 security update, playing an XVID
stream in an AVI container segfaults decoding video frames. Reverting
to 6:9.11-2ubuntu2 works -- I can't find a .deb for the previous 9.18
release, but this system was playing videos without issue until
I have backported 9c17d665fdc5f0ab74500a14c30627014c11b2c0 to v1.3.1 and
verified that it does fix the issue. That backport is attached, though
some functions were moved between v1.3.1 and v1.3.3 -- I don't know if
it would be preferable to carry the backport or to move Ubuntu forward
to 1.3.3 or
I have verified that 4bbe1029f2fb6cd1c102794951a944c62fdbd0e6 "qemu: fix
ifindex array reported to systemd" introduced this bug since it added a
call to virNetDevGetIndex for all VIR_DOMAIN_NET_TYPE_ETHERNET devices
with a known name, even if the device hasn't been created yet. I
believe
Public bug reported:
Starting up a VM with the following definition fails in libvirt
1.3.1-1ubuntu10 with "error: Unable to get index for interface vm28_0: No such
device":
If I remove the definition, the VM starts, but with the
interface named
Apologies for the delay. I can't even seem to reproduce the original
issue on the affected hardware before upgrading, so I can't confirm the
fix in vivid or wily.
I'd be fine with closing this can (no longer) reproduce—maybe my
recollection is playing funny tricks on me.
--
You received this
Apologies for the delay. I can't even seem to reproduce the original
issue on the affected hardware before upgrading, so I can't confirm the
fix in vivid or wily.
I'd be fine with closing this can (no longer) reproduce—maybe my
recollection is playing funny tricks on me.
--
You received this
Public bug reported:
The following applies to the 3.13 in trusty.
When transferring data at = around 100Mbps, the IOMMU logs errors such as:
AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x001c
address=0x3000 flags=0x0050]
I have locally cherry-picked 7a9810e7bd99:
apport information
** Attachment added: AudioDevicesInUse.txt
https://bugs.launchpad.net/bugs/139/+attachment/4275497/+files/AudioDevicesInUse.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/139/+attachment/4275502/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/139
Title:
apport information
** Attachment added: IwConfig.txt
https://bugs.launchpad.net/bugs/139/+attachment/4275500/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/139
Title:
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/139/+attachment/4275501/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/139
Title:
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/139/+attachment/4275506/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/139
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/139/+attachment/4275503/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/139
apport information
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/139/+attachment/4275498/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/139
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/139/+attachment/4275505/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/139/+attachment/4275499/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/139
apport information
** Attachment added: ProcEnviron.txt
https://bugs.launchpad.net/bugs/139/+attachment/4275504/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/139
apport information
** Tags added: apport-collected trusty
** Description changed:
The following applies to the 3.13 in trusty.
When transferring data at = around 100Mbps, the IOMMU logs errors such as:
AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x001c
apport information
** Attachment added: WifiSyslog.txt
https://bugs.launchpad.net/bugs/139/+attachment/4275510/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/139
dmesg files attached via the apport-collect utility. This bug is way up
at 3909 - 3930 seconds in them -- there's a lot of suspend/resume junk
after that.
Upstream discussion is at
http://thread.gmane.org/gmane.linux.kernel/1746901. This patch landed
in 3.16 as commit
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/139/+attachment/4275508/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/139
Title:
apport information
** Attachment added: PulseList.txt
https://bugs.launchpad.net/bugs/139/+attachment/4275507/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/139
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/139/+attachment/4275509/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/139
Title:
Public bug reported:
In the thread at
http://thread.gmane.org/gmane.comp.emulators.kvm.devel/127042/focus=129294,
three commits were identified to fix live migration for qemu 2.0 (at
least), which I am using on trusty. I would like to get these pulled-in
by the package maintainer.
I have
Public bug reported:
In the thread at
http://thread.gmane.org/gmane.comp.emulators.kvm.devel/127042/focus=129294,
three commits were identified to fix live migration for qemu 2.0 (at
least), which I am using on trusty. I would like to get these pulled-in
by the package maintainer.
I have
That's awesome. I just got a chance to test it out, and with a couple
hiccups (below), I seem to have successfully migrated a guest from a
precise host to a new trusty one.
It looks like qemu failed to build in Serge's PPA due to the spice that
also lives in that PPA. I built the qemu from the
That's awesome. I just got a chance to test it out, and with a couple
hiccups (below), I seem to have successfully migrated a guest from a
precise host to a new trusty one.
It looks like qemu failed to build in Serge's PPA due to the spice that
also lives in that PPA. I built the qemu from the
This is also blocking a precise - trusty migration for me.
Would it be possible / feasible to provide a pc-1.0-precise machine
type in qemu for trusty and an updated libvirt for precise that allows
you to change the machine attribute on the type element for migration,
so I could specify a
This is also blocking a precise - trusty migration for me.
Would it be possible / feasible to provide a pc-1.0-precise machine
type in qemu for trusty and an updated libvirt for precise that allows
you to change the machine attribute on the type element for migration,
so I could specify a
Then perhaps this is a documentation bug instead. --hint force_hosts
is the currently-documented method in the Compute Administration Manual:
http://docs.openstack.org/trunk/openstack-compute/admin/content/specify-
host-to-boot-instances-on.html
--
You received this bug notification because you
Then perhaps this is a documentation bug instead. --hint force_hosts
is the currently-documented method in the Compute Administration Manual:
http://docs.openstack.org/trunk/openstack-compute/admin/content/specify-
host-to-boot-instances-on.html
--
You received this bug notification because you
I ran into the same problem. It seems that HostState.passes_filters
gets called with different data in filter_properties than it expects.
The attached patch makes it work, but I doubt it's a completely correct
solution, since I don't handle more than one host in the force_hosts
list.
** Patch
I ran into the same problem. It seems that HostState.passes_filters
gets called with different data in filter_properties than it expects.
The attached patch makes it work, but I doubt it's a completely correct
solution, since I don't handle more than one host in the force_hosts
list.
** Patch
Public bug reported:
I upgraded an AMD64 machine to 12.04, and I cannot complete the upgrade
due to insatiable dependencies with libreoffice. libreoffice-core
3.5.2-2ubuntu1 is the only version of libreoffice-core available in the
repository, but libreoffice-common 3.5.1-1ubuntu5 is the latest
Public bug reported:
Binary package hint: bluez
I have a bluetooth keyboard and mouse, and they do not seem to be
pairing properly in karmic. My Palm Centro, however, paired just fine.
Since the keyboard and mouse aren't paired, when they disconnect (i.e. I
move my laptop somewhere else), they
It does appear that the kernel in -proposed resolves this issue.
--
Matt Mullins
--
IPsec problems: setkey error invalid keymsg length, racoon spins in busy loop
https://bugs.launchpad.net/bugs/308604
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
Binary package hint: linux-image-2.6.27-9-generic
When I upgraded from hardy to intrepid, my IPsec configuration stopped
working. The first symptom I noticed was upon boot, racoon was spinning
itself in a busy loop, sucking up all of one CPU. After tinkering with
setkey
It has also fixed problems with sound after hibernating on my Gateway
6510GZ (Intel AC'97 audio). Thank you guys. I hope this can make it
into the official repositories soon.
--
[Feisty] Inaudible audio upon resuming from suspend-to-disk
https://bugs.launchpad.net/bugs/80893
You received this
38 matches
Mail list logo
