[Bug 1926760] [NEW] display is flickering and not responsive from login screen
Public bug reported: display is flickering and not responsive from login screen, before even typing anything. This happens with kernels newer than 5.8.0-48-generic, i.e -49 and -50. On the occasion I was able to boot in, I was using a recovery mode and display was deemed unknown. I am not sure if this is because of recovery mode settings. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 30 12:33:44 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0162] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation Motherboard [1849:0162] InstallationDate: Installed on 2020-07-04 (300 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic root=UUID=3cea77a7-cb0e-4309-8963-651539349612 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/13/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.00 dmi.board.name: Z77 Extreme4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.00:bd07/13/2012:br4.6:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ77Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal resolution third-party-packages ubuntu ** Description changed: display is flickering and not responsive from login screen, before even typing anything. - This happens with kernels older than 5.8.0-48-generic, at least -49 and - -50. + This happens with kernels newer than 5.8.0-48-generic, i.e -49 and -50. On the occasion I was able to boot in, I was using a recovery mode and display was deemed unknown. I am not sure if this is because of recovery mode settings. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 30 12:33:44 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: - Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0162] (rev 09) (prog-if 00 [VGA controller]) -Subsystem: ASRock Incorporation Motherboard [1849:0162] + Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0162] (rev 09) (prog-if 00 [VGA controller]) + Subsystem: ASRock Incorporation Motherboard [1849:0162] InstallationDate: Installed on 2020-07-04 (300 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic root=UUID=3cea77a7-cb0e-4309-8963-651539349612 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/13/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.00 dmi.board.name: Z77 Extr
[Bug 1072206] Re: [nvidia] Window content is black or transparent
I'm still experiencing similar behaviour, now without the proprietary driver and on ubuntu 16.04. If I am using a video player such as mplayer, the issue is easily reproducible. Happy to help, seeing as I seem to be able to trigger this almost on demand. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1072206 Title: [nvidia] Window content is black or transparent To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1072206/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1615304] Re: running the atom editor and pressing alt-tab causes compiz to freeze and crash
The only information from perf I found was just this line, which I believe I copied from the `perf top` but not particularly convinced this will be of much help, but hopefully it may be useful in correlating any existing 14.00% libnvidia-glcore.so.352.63 [.] 0x01822cc6 ◈ 11.03% libc-2.19.so [.] syscall ▒ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1615304 Title: running the atom editor and pressing alt-tab causes compiz to freeze and crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1615304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1615304] Re: running the atom editor and pressing alt-tab causes compiz to freeze and crash
I managed to reproduce this under the debugger, however it took several tries for it to reproduce, suggesting this may be a possible race condition. Furthermore, I have noticed the bug shows itself in the form of either (1) mouse moves, but no screen updates. A crash ensues within 5-10 seconds (2) no mouse moves or screen updates. No crash, compiz remains using 100% of cpu (1 core) on the faulting thread. I gathered some output from gdb and top: #0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x7f59cab22d25 in ?? () from /usr/lib/nvidia-352/libGL.so.1 #2 0x7f59cab22a23 in ?? () from /usr/lib/nvidia-352/libGL.so.1 #3 0x7f59c2d300b3 in ?? () from /usr/lib/nvidia-352/libnvidia-glcore.so.352.63 #4 0x7f59c2c97b1d in ?? () from /usr/lib/nvidia-352/libnvidia-glcore.so.352.63 #5 0x7f59c2c98e17 in ?? () from /usr/lib/nvidia-352/libnvidia-glcore.so.352.63 #6 0x7f59c2c1c5b5 in ?? () from /usr/lib/nvidia-352/libnvidia-glcore.so.352.63 #7 0x7f59caaf54fe in glXDestroyPixmap () from /usr/lib/nvidia-352/libGL.so.1 #8 0x7f59cade58b0 in TfpTexture::~TfpTexture() () from /usr/lib/compiz/libopengl.so #9 0x7f59cade5919 in TfpTexture::~TfpTexture() () from /usr/lib/compiz/libopengl.so #10 0x7f59cade4dcd in GLTexture::List::~List() () from /usr/lib/compiz/libopengl.so #11 0x7f59c92fcf49 in DecorTexture::~DecorTexture() () from /usr/lib/compiz/libdecor.so #12 0x7f59c92fd010 in DecorScreen::releaseTexture(DecorTexture*) () from /usr/lib/compiz/libdecor.so #13 0x7f59c9303f9a in Decoration::~Decoration() () from /usr/lib/compiz/libdecor.so #14 0x7f59c9304059 in Decoration::~Decoration() () from /usr/lib/compiz/libdecor.so #15 0x7f59c9300b2a in DecorWindow::update(bool) () from /usr/lib/compiz/libdecor.so #16 0x7f59c930534b in DecorScreen::handleEvent(_XEvent*) () from /usr/lib/compiz/libdecor.so #17 0x7f59d712773f in CompScreen::handleEvent(_XEvent*) () from /usr/lib/libcompiz_core.so.ABI-20140123 #18 0x7f59d712773f in CompScreen::handleEvent(_XEvent*) () from /usr/lib/libcompiz_core.so.ABI-20140123 #19 0x7f59c0a85d90 in ResizeLogic::handleEvent(_XEvent*) () from /usr/lib/compiz/libresize.so #20 0x7f59d712773f in CompScreen::handleEvent(_XEvent*) () from /usr/lib/libcompiz_core.so.ABI-20140123 #21 0x7f59d712773f in CompScreen::handleEvent(_XEvent*) () from /usr/lib/libcompiz_core.so.ABI-20140123 #22 0x7f59c0650591 in RegexScreen::handleEvent(_XEvent*) () from /usr/lib/compiz/libregex.so #23 0x7f59d712773f in CompScreen::handleEvent(_XEvent*) () from /usr/lib/libcompiz_core.so.ABI-20140123 #24 0x7f59c043dbad in PlaceScreen::handleEvent(_XEvent*) () from /usr/lib/compiz/libplace.so #25 0x7f59d712773f in CompScreen::handleEvent(_XEvent*) () from /usr/lib/libcompiz_core.so.ABI-20140123 #26 0x7f59d712773f in CompScreen::handleEvent(_XEvent*) () from /usr/lib/libcompiz_core.so.ABI-20140123 #27 0x7f59bbbe37ee in MoveScreen::handleEvent(_XEvent*) () from /usr/lib/compiz/libmove.so #28 0x7f59d712773f in CompScreen::handleEvent(_XEvent*) () from /usr/lib/libcompiz_core.so.ABI-20140123 #29 0x7f59d712773f in CompScreen::handleEvent(_XEvent*) () from /usr/lib/libcompiz_core.so.ABI-20140123 #30 0x7f59baaeb40d in WorkaroundsScreen::handleEvent(_XEvent*) () from /usr/lib/compiz/libworkarounds.so #31 0x7f59d712773f in CompScreen::handleEvent(_XEvent*) () from /usr/lib/libcompiz_core.so.ABI-20140123 #32 0x7f59ba8d104a in FadeScreen::handleEvent(_XEvent*) () from /usr/lib/compiz/libfade.so #33 0x7f59d712773f in CompScreen::handleEvent(_XEvent*) () from /usr/lib/libcompiz_core.so.ABI-20140123 #34 0x7f59c951f87c in BaseSwitchScreen::handleEvent(_XEvent*) () from /usr/lib/compiz/libcompiztoolbox.so #35 0x7f59d712773f in CompScreen::handleEvent(_XEvent*) () from /usr/lib/libcompiz_core.so.ABI-20140123 #36 0x7f59d712777b in CompScreenImpl::alwaysHandleEvent(_XEvent*) () from /usr/lib/libcompiz_core.so.ABI-20140123 #37 0x7f59d710179d in PrivateScreen::processEvents() () from /usr/lib/libcompiz_core.so.ABI-20140123 #38 0x7f59d71352e7 in CompEventSource::callback() () from /usr/lib/libcompiz_core.so.ABI-20140123 #39 0x7f59d562835f in Glib::Source::dispatch_vfunc(_GSource*, int (*)(void*), void*) () from /usr/lib/x86_64-linux-gnu/libglibmm-2.4.so.1 #40 0x7f59d511ace5 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #41 0x7f59d511b048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #42 0x7f59d511b30a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #43 0x7f59d70f60eb in compiz::private_screen::EventManager::startEventLoop(_XDisplay*) () from /usr/lib/libcompiz_core.so.ABI-20140123 #44 0x00401951 in main () top: $ cat compiz-top top - 22:40:59 up 11 min, 4 users, load average: 1.07, 0.67, 0.38 Tasks: 285 total, 2 running, 283 sleeping, 0 stopped, 0
[Bug 1615304] Re: running the atom editor and pressing alt-tab causes compiz to freeze and crash
The same sort of behaviour has been experienced, although not as easily reproducible, when using firefox with multiple open windows spread across different workspaces. ** Description changed: + Running the atom editor (www.atom.io) on ubuntu 14.04 with gnome-panel + + compiz leads to compiz crash when pressing alt-tab to switch to a + different window. + + 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description: Ubuntu 14.04.5 LTS Release: 14.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center compiz: Installed: 1:0.9.11.3+14.04.20160425-0ubuntu1 Candidate: 1:0.9.11.3+14.04.20160425-0ubuntu1 Version table: *** 1:0.9.11.3+14.04.20160425-0ubuntu1 0 500 http://ie.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:0.9.11+14.04.20140409-0ubuntu1 0 500 http://ie.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 3) What you expected to happen I expected ctrl-tab to switch me to a different window. 4) What happened instead The environment freezes, despite mouse still moving. No application or item in the windowing system responds and ultimately compiz crashes (~5 seconds later), leading up to black screen followed by a default graphical login prompt. This bug is fully reproducible in my environment and I'm eager to help debug it. ** Description changed: Running the atom editor (www.atom.io) on ubuntu 14.04 with gnome-panel + compiz leads to compiz crash when pressing alt-tab to switch to a different window. + Reproduces every time. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description: Ubuntu 14.04.5 LTS Release: 14.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center compiz: Installed: 1:0.9.11.3+14.04.20160425-0ubuntu1 Candidate: 1:0.9.11.3+14.04.20160425-0ubuntu1 Version table: *** 1:0.9.11.3+14.04.20160425-0ubuntu1 0 500 http://ie.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:0.9.11+14.04.20140409-0ubuntu1 0 500 http://ie.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 3) What you expected to happen I expected ctrl-tab to switch me to a different window. 4) What happened instead The environment freezes, despite mouse still moving. No application or item in the windowing system responds and ultimately compiz crashes (~5 seconds later), leading up to black screen followed by a default graphical login prompt. This bug is fully reproducible in my environment and I'm eager to help debug it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1615304 Title: running the atom editor and pressing alt-tab causes compiz to freeze and crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1615304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1615304] [NEW] running the atom editor and pressing alt-tab causes compiz to freeze and crash
Public bug reported: Running the atom editor (www.atom.io) on ubuntu 14.04 with gnome-panel + compiz leads to compiz crash when pressing alt-tab to switch to a different window. Reproduces every time. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description:Ubuntu 14.04.5 LTS Release:14.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center compiz: Installed: 1:0.9.11.3+14.04.20160425-0ubuntu1 Candidate: 1:0.9.11.3+14.04.20160425-0ubuntu1 Version table: *** 1:0.9.11.3+14.04.20160425-0ubuntu1 0 500 http://ie.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:0.9.11+14.04.20140409-0ubuntu1 0 500 http://ie.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 3) What you expected to happen I expected ctrl-tab to switch me to a different window. 4) What happened instead The environment freezes, despite mouse still moving. No application or item in the windowing system responds and ultimately compiz crashes (~5 seconds later), leading up to black screen followed by a default graphical login prompt. This bug is fully reproducible in my environment and I'm eager to help debug it. ** Affects: compiz (Ubuntu) Importance: Undecided Status: New ** Summary changed: - running atom and alt-tab causes compiz to crash + running atom and pressing alt-tab causes compiz to freeze and crash ** Summary changed: - running atom and pressing alt-tab causes compiz to freeze and crash + running the atom editor and pressing alt-tab causes compiz to freeze and crash ** Description changed: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description: Ubuntu 14.04.5 LTS Release: 14.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center compiz: - Installed: 1:0.9.11.3+14.04.20160425-0ubuntu1 - Candidate: 1:0.9.11.3+14.04.20160425-0ubuntu1 - Version table: - *** 1:0.9.11.3+14.04.20160425-0ubuntu1 0 - 500 http://ie.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages - 100 /var/lib/dpkg/status - 1:0.9.11+14.04.20140409-0ubuntu1 0 - 500 http://ie.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages - + Installed: 1:0.9.11.3+14.04.20160425-0ubuntu1 + Candidate: 1:0.9.11.3+14.04.20160425-0ubuntu1 + Version table: + *** 1:0.9.11.3+14.04.20160425-0ubuntu1 0 + 500 http://ie.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages + 100 /var/lib/dpkg/status + 1:0.9.11+14.04.20140409-0ubuntu1 0 + 500 http://ie.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 3) What you expected to happen - I expected to switch to a different window when I pressed ctrl+tab. + I expected ctrl-tab to switch me to a different window. 4) What happened instead - The environment freezes, despite mouse still moves but no application or - item in the windowing system responds and ultimately compiz crashes, - leading up to black screen followed by a default login prompt. + The environment freezes, despite mouse still moving. No application or + item in the windowing system responds and ultimately compiz crashes (~5 + seconds later), leading up to black screen followed by a default + graphical login prompt. - This bug is fully reproducible in my environment. + This bug is fully reproducible in my environment and I'm eager to help + debug it. If I find time, I might begin the investigation. ** Description changed: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description: Ubuntu 14.04.5 LTS Release: 14.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center compiz: Installed: 1:0.9.11.3+14.04.20160425-0ubuntu1 Candidate: 1:0.9.11.3+14.04.20160425-0ubuntu1 Version table: *** 1:0.9.11.3+14.04.20160425-0ubuntu1 0 500 http://ie.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:0.9.11+14.04.20140409-0ubuntu1 0 500 http://ie.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 3) What you expected to happen I expected ctrl-tab to switch me to a different window. 4) What happened instead The environment freezes, despite mouse still moving. No application or item in the windowing system responds and ultimately compiz crashes (~5 seconds later), leading up to black screen followed by a default graphical login prompt. This bug is fully reproducible in my environment and I'm eager to help - debug it. If I find time, I might begin the investigation. + debug it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.l
[Bug 1072206] Re: [nvidia] Window content is black or transparent
I seem to be reproducing this bug or similar on Ubuntu 14.04, using gnome-panel (gnome classic) + compiz, gtx 600 (driver: nvidia-352.63). The comments in #80 and #79 hit close to home. I can reproduce it easily by running 'mplayer video' and pressing alt- tab. This renders compiz unusable and cpu usage for compiz goes to 100% usage and stays as such until killed. Occasionally compiz will crash instead of hanging, but I think there may be some specific interactions/key presses, part of my futile attempts at recovering the session while not fully unusable (even if it's already going berzerk by then) that causes it to end up crashing rather than hanging. FWIW, I've Attached gdb backtrace of all threads. I also recorded the perf events for compiz after reproducing the issue using mplayer. Alternatively, I have noticed that this started to happen more frequently when I began to use more than one firefox window open (I don't think tab count matters much as I've always been a tab hoarder and I have reduced substantially now). I did experience similar behavior with flash based multimedia content in full screen and alt-tab to switch back to the browser. It does not reproduce easily tough. This behavior started to be noticed about 3 months ago (could be less, could be more, I can't be any more precise, I'm afraid) Would be great to root cause it and I am happy to help. ** Attachment added: "gdb backtrace of compiz" https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1072206/+attachment/4547182/+files/compiz-100pc-cpu.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1072206 Title: [nvidia] Window content is black or transparent To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1072206/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1007002] Re: Xen VCPUs hotplug does not work
The problem is not reproducible using the images below in a Lucid guest on XenServer 6.0.2 linux-image-3.5.0-030500rc1-generic_3.5.0-030500rc1.201206022335_amd64.deb linux-image-extra-3.5.0-030500rc1-generic_3.5.0-030500rc1.201206022335_amd64.deb (Images supplied by Joseph Salisbury, see comment above) ** Tags removed: needs-upstream-testing ** Tags added: kernel-fixed-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1007002 Title: Xen VCPUs hotplug does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1007002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
