[Bug 1371233] Re: USB 3.0 connection is unreliable + xHCI xhci_drop_endpoint called with disabled ep

2015-05-12 Thread NightShade
tim@desktop-tim:~$ uname -a Linux desktop-tim 4.0.1-040001-generic #201504290935 SMP Wed Apr 29 09:36:55 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux No bug, I'll pull the other kernels down and test them over the next few days -- You received this bug notification because you are a member of

[Bug 1371233] Re: USB 3.0 connection is unreliable + xHCI xhci_drop_endpoint called with disabled ep

2015-05-01 Thread NightShade
I was having the same problem with a number of USB3 harddisks, upgrading to 4.0.1 from the mainline PPA has fixed it for me. I think it might be triggered by my Yubikey security key. I get WARN Event TRB for slot 8 ep 4 with no TDs queued? when gpg accesses the key. -- You received this bug

[Bug 1387303] Re: regression: gnome-keyring components can't be disabled anymore

2015-01-15 Thread NightShade
Installing the package from Vivid on my Utopic desktop has fixed my problems with my Yubikey neo acting as a smart card, thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1387303 Title:

[Bug 453335] Re: apparmor complains about write access to a readonly file

2015-01-06 Thread NightShade
I think this is actually causing a moderately serious regression with snapshots. If you look at the contents of an apparmor define for an example VM the deny that silences the error here also prevents snapshot commits from working and because the error is hidden makes this extra difficult to

[Bug 1004606] Re: virsh create-snapshot fails to create external snapshot (blockdev-snapshot-sync fails in json monitor)

2015-01-06 Thread NightShade
I think I have found the cause of this problem, in bug number 453335 an apparmor fix was put in place to deny access to certain read only media and also to hide the error message about access being denied. I think this is causing the duplicate entries in apparmor and also hiding the errors about

[Bug 453335] Re: apparmor complains about write access to a readonly file

2015-01-06 Thread NightShade
Correction the bug number for the other bug is #1004606 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/453335 Title: apparmor complains about write access to a readonly file To manage notifications

[Bug 1004606] Re: virsh create-snapshot fails to create external snapshot (blockdev-snapshot-sync fails in json monitor)

2015-01-06 Thread NightShade
I believe this is the problematic git commit: http://libvirt.org/git/?p=libvirt.git;a=commitdiff;h=d0d4b8ad76d3e8a859ee90701a21a3f003a22c1f;hp=dae7054b7697d30f2b88cd5dff3dfb954323d40b -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1004606] Re: virsh create-snapshot fails to create external snapshot (blockdev-snapshot-sync fails in json monitor)

2015-01-06 Thread NightShade
Definitely still a problem in utopic, I think the issue is caused by this part of the apparmor config: /var/lib/libvirt/images/openwrt-x86-kvm_guest-combined-ext4.img- zfs-1.qcow2 is my current snapshot and I am trying to commit it back to

[Bug 1004606] Re: virsh create-snapshot fails to create external snapshot (blockdev-snapshot-sync fails in json monitor)

2015-01-06 Thread NightShade
Experimenting further if I take out the seclabel line (shown below) from my VM definition everything works as expected with snapshots. seclabel type='dynamic' model='apparmor' relabel='yes'/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 1223730] Re: mDNS failure with openvswitch 1.10

2014-02-01 Thread NightShade
Definitely still a bug -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1223730 Title: mDNS failure with openvswitch 1.10 To manage notifications about this bug go to:

[Bug 1223730] Re: mDNS failure with openvswitch 1.10

2014-02-01 Thread NightShade
Definitely still a bug -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1223730 Title: mDNS failure with openvswitch 1.10 To manage notifications about this bug go to:

[Bug 1223730] Re: mDNS failure with openvswitch 1.10

2013-12-02 Thread NightShade
I've now updated to Saucy and I still have the same problem on multiple machines with openswitch. I have a KVM test machine that has a ubuntu VM running on it plugged into a vswitch that is in turn plugged in via the quad port bond you can see here. Iron is the KVM host, the host shows no mDNS

[Bug 1223730] Re: mDNS failure with openvswitch 1.10

2013-12-02 Thread NightShade
I've now updated to Saucy and I still have the same problem on multiple machines with openswitch. I have a KVM test machine that has a ubuntu VM running on it plugged into a vswitch that is in turn plugged in via the quad port bond you can see here. Iron is the KVM host, the host shows no mDNS

[Bug 1223730] Re: mDNS failure with openvswitch 1.10

2013-10-18 Thread NightShade
Ah sorry, I had updated to the latest OVS version from saucy by enabling the saucy repos and just updating relevant libvirt and OVS packages. The show command I included was run on 1.9 after I downgraded again to get printing working (printers found via mDNS) I've looked at the packets on the

[Bug 1223730] Re: mDNS failure with openvswitch 1.10

2013-10-18 Thread NightShade
Ah sorry, I had updated to the latest OVS version from saucy by enabling the saucy repos and just updating relevant libvirt and OVS packages. The show command I included was run on 1.9 after I downgraded again to get printing working (printers found via mDNS) I've looked at the packets on the

[Bug 1223730] [NEW] mDNS failure with openvswitch 1.10

2013-09-11 Thread NightShade
Public bug reported: I have upgraded my Ubuntu 13.04 KVM test machine to the latest version of QEMU/openvswitch/libvirt and I am having problems with mDNS. I've not upgraded the kernel on the host machine so I am using current (3.8.0-30). Fully internal openvswitch: VM - VM mDNS works VM -

[Bug 1223730] Re: mDNS failure with openvswitch 1.10

2013-09-11 Thread NightShade
openvswitch setup root@tim-6460b:~# ovs-vsctl show ccdda6ff-e90d-41f5-9f87-5e68f562b73c Bridge private Port private Interface private type: internal Bridge internal Port internal Interface internal type: internal

[Bug 1223730] [NEW] mDNS failure with openvswitch 1.10

2013-09-11 Thread NightShade
Public bug reported: I have upgraded my Ubuntu 13.04 KVM test machine to the latest version of QEMU/openvswitch/libvirt and I am having problems with mDNS. I've not upgraded the kernel on the host machine so I am using current (3.8.0-30). Fully internal openvswitch: VM - VM mDNS works VM -

[Bug 1223730] Re: mDNS failure with openvswitch 1.10

2013-09-11 Thread NightShade
openvswitch setup root@tim-6460b:~# ovs-vsctl show ccdda6ff-e90d-41f5-9f87-5e68f562b73c Bridge private Port private Interface private type: internal Bridge internal Port internal Interface internal type: internal

[Bug 584668] Re: iscsi_trgt: scsi_cmnd_start(1035) Unsupported 85

2010-06-19 Thread NightShade
This seems to be related to the iscsi opcode ATA COMMAND PASS THROUGH (16) However I'm not sure what is triggering it, could it be related to spinning down of disk during idle? -- iscsi_trgt: scsi_cmnd_start(1035) Unsupported 85 https://bugs.launchpad.net/bugs/584668 You received this bug