libvirt 1.3.1-1ubuntu10.5 works for me.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1591695
Title:
libvirt-guest.sh will neve
Thanks for clarifying this. Of course you can refer to me. Thanks for
looking at this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1591695
Title:
libvirt-guest.sh will never sucessfully shutdown m
so have to say that I am worried about the xen:/// discussion. If it's
about moving the actual hypervisor URI somwhere else then fine but if you
remove xen handling than please state how shutdown should be done using other
packages.
Best regards
Omar Siam
--
You received this bug notificat
So I saw my patch is not good enough to be incorporated into the latest bug fix
release libvirt (1.3.1-1ubuntu10.2). Perhaps we should have a discussion about
it then.
If you ask me you broke my setup with your fix and I would actually like to
avoid that in the future.
Best Regards
Omar Siam
** Patch added: "better patch"
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1591695/+attachment/4682217/+files/libvirt-guests-exclude-dom0.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
** Patch added: "libvirt-guests.sh.in.patch"
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1591695/+attachment/4682215/+files/libvirt-guests.sh.in.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
Public bug reported:
In function list list_guests() al list of running guests for some uri is
produced which now looks like
xen:/// uuid
uuid
uuid
A list like this is processed as if the 2nd uuid etc. are uris. That
causes the script to only shut donw one virtual machine
My fix is to make the l
Changed Mainboard to some ASUS. Works for me now.
** Summary changed:
- Kernel crashes on dom0 startup when dom0_mem is set
+ Kernel crashes on dom0 startup when dom0_mem is set if BIOS is buggy (e. g.
GA-78LMT-USB3 Rev 5.0 BIOS FA)
** Description changed:
Description: Ubuntu 16.04 LTS
Re
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1577018/+attachment/4669761/+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/1577018
Titl
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1577018/+attachment/4669754/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/15770
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1577018/+attachment/4669758/+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/1577018
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1577018/+attachment/4669751/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1577018
Title:
Kernel
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1577018/+attachment/4669757/+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/1577018
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1577018/+attachment/4669755/+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/1577018
Title:
Kern
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1577018/+attachment/4669752/+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/1577018
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1577018/+attachment/4669756/+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/1577018
Title:
Kern
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1577018/+attachment/4669763/+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/1577018
Ti
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1577018/+attachment/4669759/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/157
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1577018/+attachment/4669762/+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/1577018
Title:
Ke
apport information
** Attachment added: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/1577018/+attachment/4669750/+files/AlsaInfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1577018
Title:
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1577018/+attachment/4669760/+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/1577018
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1577018/+attachment/4669753/+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/1577018
Title:
yes, yesterdays 4.6.0-040600rc7-generic still crashes if set and boots
if not.
** Tags added: kernel-bug-exists-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
I'm pretty sure that most of the information I just added already are in the
archive I attached to my original report. Was to creative I think. Just in
case: This report was generated _after deleting the offending kernel command
line_. The nature of this bug is that a kernel later than 4.2.0 jus
Above message is cut short so to make myself clear: This is the pronblem:
mapping kernel into physical memory
about to get started...
(XEN) d0v0 Unhandled invalid opcode fault/trap [#6, ec=]
(XEN) domain_crash_sync called from entry.S: fault at 82d08022a583
create_bounce_frame+0x12b/0x13a
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1577018/+attachment/4652730/+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/1577018
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1577018/+attachment/4652724/+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/1577018
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1577018/+attachment/4652734/+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/1577018
Title:
Ke
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1577018/+attachment/4652726/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/15770
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1577018/+attachment/4652725/+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/1577018
Title:
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1577018/+attachment/4652723/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1577018
Title:
Kernel
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1577018/+attachment/4652733/+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/1577018
Titl
apport information
** Tags added: apport-collected xenial
** Description changed:
Description: Ubuntu 16.04 LTS
Release: 16.04
linux-image-generic:
Installiert: 4.4.0.21.22
Installationskandidat: 4.4.0.21.22
Versionstabelle:
*** 4.4.0.21.22 500
500
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1577018/+attachment/4652731/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/157
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1577018/+attachment/4652727/+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/1577018
Title:
Kern
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1577018/+attachment/4652728/+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/1577018
Title:
Kern
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1577018/+attachment/4652732/+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/1577018
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1577018/+attachment/4652729/+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/1577018
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1577018/+attachment/4652735/+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/1577018
Ti
Public bug reported:
Description:Ubuntu 16.04 LTS
Release:16.04
linux-image-generic:
Installiert: 4.4.0.21.22
Installationskandidat: 4.4.0.21.22
Versionstabelle:
*** 4.4.0.21.22 500
500 http://at.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100
I think I saw some patch (ubuntu only?) that adds wep support even if nothing
is advertised but only in certain cases. Nothing is added if you manually try
to add a network.
I added a note to my upstream bug but I didn't mention this behavior I observed
in my originial bug report upstream and I
That kernel patch will fix the encryption reporting and ruin my
detection patch in any kernel where this will be incorportated. That
makes things work to some extend, but you won't get any signal strength
for the network you are connected.
--
You received this bug notification because you are a m
Submited patch to kernel bug thread. Filed upstream bug
https://bugzilla.gnome.org/show_bug.cgi?id=673717
** Bug watch added: GNOME Bug Tracker #673717
https://bugzilla.gnome.org/show_bug.cgi?id=673717
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
I suggest this patch which doesn't rely on string comparison of driver
names that much.
** Patch added: "ipw2x00-no-nl80211.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/973241/+attachment/3024916/+files/ipw2x00-no-nl80211.patch
--
You received this bug notification because you
ok that patch obviously solves the problem for all ipw2100 und ipw2200
owners but there are potentially some more drivers affected by the
strange kernel behavior of not reporting a non nl80211 compliant driver
to userspace (at least not in an way nm understands). If I assume that
every driver that
Filed an upstream bug: https://bugzilla.kernel.org/show_bug.cgi?id=43049
I didn't check with 22.35 but the changelog doesn't list any changes in
wireless so I assume it was not fixed accidently.
** Bug watch added: Linux Kernel Bug Tracker #43049
http://bugzilla.kernel.org/show_bug.cgi?id=4304
Filed a kernel bug
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/973241).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/971628
Title:
Can't use WPA with ipw2200
To manage notifications abou
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/973241
Title:
ipw2200 driver doesn't report any capabilities or wireless properties
using the nl80211 interface to network-manager
To manage notificat
Public bug reported:
I filed this as a bug to network manager first
(https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/971628). Using
standard network-manager nm-tool (and subsequently all tools built upon nm)
reports
- Device: eth1 [SERVANTS-WLAN]
Should the nl80211 interface be patched out of the kernel? Or patcheed
to report encryption capabilities? This interface doesn't even report
that wep is supported and thats plain wrong. I agree with you that this
patch isn't the best way to solve this. I just asked myself: if I can
call the nl8
Public bug reported:
If some driver implements wext interface and nl80211 interface the
latter is preferred. With the ipw2200 driver this implementation doesn't
yield any encryption capabilites but the wext interface is never
consulted. If the order of the function calls is reversed in wifi-
utils
51 matches
Mail list logo
