Will it ever get fixed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1261916
Title:
Missing letters in spice client session with KVM guest
To manage notifications about this bug go to:
Public bug reported:
just doing the aptitude install trove-api, error during installation.
2015-05-04 00:23:33.722 30339 TRACE root OperationalError:
(OperationalError) unable to open database file None None
Probably it requires a database configuration, to start. Have a prompt
for the db
Public bug reported:
just doing the aptitude install trove-api, error during installation.
2015-05-04 00:23:33.722 30339 TRACE root OperationalError:
(OperationalError) unable to open database file None None
Probably it requires a database configuration, to start. Have a prompt
for the db
Public bug reported:
Upgraded from 14.04 to 14.10
virt-manager
Version: 1:1.0.1-0ubuntu2
libvirt-bin
Version: 1.2.8-0ubuntu11
The USB Host device, no longer gets mapped in to the guest VM.
Using qemu-kvm for virtualization, with virt-manager.
Tried different types of devices and host OSs,
On Ubuntu 14.10 with Gnome3 still doesn't turn the screen off or lock,
with
unity-settings-daemon 14.04.0+14.10.20141014-0ubuntu1
even using the screen lock shortcut doesn't work.
Fresh install from the network installation.
--
You received this bug notification because you are a member of
Public bug reported:
Upgraded from 14.04 to 14.10
virt-manager
Version: 1:1.0.1-0ubuntu2
libvirt-bin
Version: 1.2.8-0ubuntu11
The USB Host device, no longer gets mapped in to the guest VM.
Using qemu-kvm for virtualization, with virt-manager.
Tried different types of devices and host OSs,
If I delete the VM, leave the storage intact, and create it again, It's
okay. The configuration that it creates is different, but the USB works
thru spice.
Seems to have been some changes made in how the usb redirects are made,
probably virt-manager should take this in to account, and migrate the
Public bug reported:
I think the hard disk choosen was wrong.
Runnning on an Intel RAID.
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: ubiquity 2.20.0
ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
Uname: Linux 3.16.0-23-generic x86_64
NonfreeKernelModules: wl
ApportVersion:
Since I've upgraded to 13.10, my raid5 on the intel software raid
doesn't mount with the dmraid. I use an older 3.8 kernel I was using on
my 13.04.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1241086
Continues to not work for me. But at the initramfs prompt I'm able to manually
mount
Could the signed version for UEFI ( linux-signed-
image-3.11.0-13-generic ) of the same kernel, not have been updated with
the patch in proposed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1241086
kernel linux-image-3.11.0-13-generic doesn't solve the problem, continue
to get the device-mapper: table252:0:raid45:unknown target type
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1241086
Title:
I got an intel software raid, running a raid 5
And updated to saucy.
I think it maybe related.
I can no longer boot with the new kernel 3.11. Only the 3.8 from precise.
When it drops to the initramfs command-line and i issue a dmraid -a y
for my raid I get this:
device-mapper:
I was checking the patch, In the vanilla kernel 3.11.6 the symbols have
changed
Symbol: MD_RAID456 [=m]
│ Type : tristate
│ Prompt: RAID-4/RAID-5/RAID-6 mode
│ Location:
│ - Device Drivers
│ - Multiple devices driver support (RAID and LVM) (MD [=y])
│ - RAID
I think this is the problem in dmraid/lib/activate/activate.c
static struct type_handler {
const enum type type;
int (*f) (struct lib_context * lc, char **table, struct raid_set * rs);
} type_handler[] = {
{ t_undef, dm_undef }, /* Needs to stay here! */
{
Public bug reported:
Just installing the package
ProblemType: Package
DistroRelease: Ubuntu 13.04
Package: cinder-common 1:2013.1.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6
Uname: Linux 3.8.0-30-generic x86_64
ApportVersion: 2.9.2-0ubuntu8.3
Architecture: amd64
Date:
Public bug reported:
Just installing the package
ProblemType: Package
DistroRelease: Ubuntu 13.04
Package: cinder-common 1:2013.1.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6
Uname: Linux 3.8.0-30-generic x86_64
ApportVersion: 2.9.2-0ubuntu8.3
Architecture: amd64
Date:
I compiled the package from source and it started ok, I think the
problem is with the binary package and the dependencies it's compiled
are not the ones being shipped in 12.10 because of the JS LOG: IBus
version is too old
James can you compile gnome-shell package from source and see if it
starts
My Gnome-shell also crashes with a similar error.
JS LOG: IBus version is too old
Window manager warning: Log level 16: Unable to register authentication agent:
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: An authentication agent
already exists for the given subject
JS ERROR: !!!
[195114.020132] iwlagn :02:00.0: Error sending REPLY_QOS_PARAM: time out
after 500ms.
[195114.020142] iwlagn :02:00.0: Failed to update QoS
[195114.520080] iwlagn :02:00.0: Error sending REPLY_RXON: time out after
500ms.
[195114.520090] iwlagn :02:00.0: Error clearing ASSOC_MSK
19 matches
Mail list logo
