[Ubuntu-x-swat] [Bug 1564156] Re: xenial: invalid opcode when using llvmpipe
On a whim, I just checked in on this with the 20160601 Xenial daily amd64 ISO (sha1sum e07c8b4df1fc71a487fafb309bd318041a65774f), and everything works great: http://cdimages.ubuntu.com/xenial/daily-live/pending/ So seems things are on track for this not being a problem in the 16.04.1 release. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1564156 Title: xenial: invalid opcode when using llvmpipe To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1564156/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1564156] Re: xenial: invalid opcode when using llvmpipe
Okay, seems that "Download updates while installing" has no effect with the Ubiquity version on the 16.04 ISOs. I filed a bug against Ubiquity for this, would appreciate if someone could confirm my findings: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1580232 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1564156 Title: xenial: invalid opcode when using llvmpipe To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1564156/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1564156] Re: xenial: invalid opcode when using llvmpipe
** Description changed: [Description updated to reflect state of 16.04 release ISO] == In summary == If you have an Intel Skylake (6th gen) CPU and an NVIDIA GPU (or possibly other GPUs that likewise require use of the llvmpipe opengl software fallback), a work-around is needed to install Ubuntu 16.04 desktop. To work-around this, you'll need to: 1) Choose "Install Ubuntu" in the pre-boot menu (rather than "Try Ubuntu without installing") 2) Check "Download updates while installing Ubuntu" + ** Note: "Download updates while installing Ubuntu" doesn't currently + seem to be working. If after installing 16.04 on effected Skylake + hardware you find that Unity/Compiz is broken, switch to a VT with + Control+Alt+F1, login, and then run: + + sudo apt-get update + sudo apt-get dist-upgrade + + You should see the `libllvm3.8` package get updated. After a reboot, + Unity/Compiz should be working. + == In detail == The Ubuntu 16.04 desktop ISOs include libllvm3.8 1:3.8-2ubuntu1, which has a bug that results in invalid JIT code generation when using the mesa llvmpipe opengl software fallback on Skylake CPUs. When you encounter this bug, Unity/Compiz will fail to start, and you'll see something like this in dmesg: [ 2092.557913] traps: compiz[10155] trap invalid opcode ip:7efc940030d4 sp:7ffccd914ea0 error:0 libllvm3.8 1:3.8-2ubuntu3 fixes this issue, but the fix did not make it onto the 16.04 release ISOs. It will be included on the 16.04.1 ISOs. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1564156 Title: xenial: invalid opcode when using llvmpipe To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1564156/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1564156] Re: xenial: invalid opcode when using llvmpipe
Hmm, I just tried this on Skylake hardware, and "Download updates while installing" isn't doing the trick. Could be that "Download updates while installing" is broken on the 16.04 ISOs, or this could be a result of the phased updates done by the Ubuntu Software Updater and related components that use the same code paths. So after installing Ubuntu 16.04, Unity/Compiz was broken. I had to switch to a VT with Control+Alt+F1, login, and then run: sudo apt-get update sudo apt-get dist-upgrade Which gave me the updated libllvm3.8 package. Then after a reboot, everything is shiny and working. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1564156 Title: xenial: invalid opcode when using llvmpipe To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1564156/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1564156] Re: xenial: invalid opcode when using llvmpipe
** Description changed: [Description updated to reflect state of 16.04 release ISO] == In summary == If you have an Intel Skylake (6th gen) CPU and an NVIDIA GPU (or possibly other GPUs that likewise require use of the llvmpipe opengl software fallback), a work-around is needed to install Ubuntu 16.04 desktop. To work-around this, you'll need to: 1) Choose "Install Ubuntu" in the pre-boot menu (rather than "Try Ubuntu without installing") 2) Check "Download updates while installing Ubuntu" == In detail == - The Ubuntu 16.04 desktop ISOs includes libllvm3.8 1:3.8-2ubuntu1, which + The Ubuntu 16.04 desktop ISOs include libllvm3.8 1:3.8-2ubuntu1, which has a bug that results in invalid JIT code generation when using the mesa llvmpipe opengl software fallback on Skylake CPUs. When you encounter this bug, Unity/Compiz will fail to start, and you'll see something like this in dmesg: [ 2092.557913] traps: compiz[10155] trap invalid opcode ip:7efc940030d4 sp:7ffccd914ea0 error:0 libllvm3.8 1:3.8-2ubuntu3 fixes this issue, but the fix did not make it onto the 16.04 release ISOs. It will be included on the 16.04.1 ISOs. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1564156 Title: xenial: invalid opcode when using llvmpipe To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1564156/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1564156] Re: xenial: invalid opcode when using llvmpipe
Abhinav, Sounds like you're encountering a different bug, or perhaps your ISO file is corrupted. Have you verified the checksum of your download? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1564156 Title: xenial: invalid opcode when using llvmpipe To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1564156/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1564156] Re: xenial: invalid opcode when using llvmpipe
** Description changed: [Description updated to reflect state of 16.04 release ISO] == In summary == If you have an Intel Skylake (6th gen) CPU and an NVIDIA GPU (or possibly other GPUs that likewise require use of the llvmpipe opengl software fallback), a work-around is needed to install Ubuntu 16.04 desktop. To work-around this, you'll need to: 1) Choose "Install Ubuntu" in the pre-boot menu (rather than "Try Ubuntu without installing") 2) Check "Download updates while installing Ubuntu" - ** Note the above work-around wont work till - llvm-toolchain-3.8 1:3.8-2ubuntu3 lands in xenial-updates (it's currently only in xenial-proposed). FIXME: update description once this happens. - == In detail == The Ubuntu 16.04 desktop ISOs includes libllvm3.8 1:3.8-2ubuntu1, which has a bug that results in invalid JIT code generation when using the mesa llvmpipe opengl software fallback on Skylake CPUs. When you encounter this bug, Unity/Compiz will fail to start, and you'll see something like this in dmesg: [ 2092.557913] traps: compiz[10155] trap invalid opcode ip:7efc940030d4 sp:7ffccd914ea0 error:0 libllvm3.8 1:3.8-2ubuntu3 fixes this issue, but the fix did not make it - onto the 16.04 release ISO. It will be included on the 16.04.1 ISO. + onto the 16.04 release ISOs. It will be included on the 16.04.1 ISOs. ** Changed in: system76 Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1564156 Title: xenial: invalid opcode when using llvmpipe To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1564156/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1564156] Re: xenial: invalid opcode when using llvmpipe
** Description changed: - Currently it's impossible to install from xenial-desktop-amd64.iso on a - wide range of hardware with Nvidia GPUs. + [Description updated to reflect state of 16.04 release ISO] - The problem is invalid opcode(s) when using llvmpipe (the software - opengl fallback, used when using Unity with the Nouveau driver). The - result is that compiz crashes over and over; Upstart will continue to - restart compiz till it gives up. To confirm whether this bug is - happening, switch to a VT and check dmesg, in which you'll see something - like: + == In summary == + + If you have an Intel Skylake (6th gen) CPU and an NVIDIA GPU (or + possibly other GPUs that likewise require use of the llvmpipe opengl + software fallback), a work-around is needed to install Ubuntu 16.04 + desktop. + + To work-around this, you'll need to: + + 1) Choose "Install Ubuntu" in the pre-boot menu (rather than "Try Ubuntu + without installing") + + 2) Check "Download updates while installing Ubuntu" + + ** Note the above work-around wont work till + llvm-toolchain-3.8 1:3.8-2ubuntu3 lands in xenial-updates (it's currently only in xenial-proposed). FIXME: update description once this happens. + + == In detail == + + The Ubuntu 16.04 desktop ISOs includes libllvm3.8 1:3.8-2ubuntu1, which + has a bug that results in invalid JIT code generation when using the + mesa llvmpipe opengl software fallback on Skylake CPUs. + + When you encounter this bug, Unity/Compiz will fail to start, and you'll + see something like this in dmesg: [ 2092.557913] traps: compiz[10155] trap invalid opcode ip:7efc940030d4 sp:7ffccd914ea0 error:0 - A workable solution seems to be to re-build mesa against llvm-3.6-dev, - libclang-3.6-dev (rather that 3.8). This would get us a working Xenial - ISO for the effected hardware. Post 16.04 release, this could be - revisited, and mesa in Xenial could possibly switch back to llvm 3.8 - once this issue is resolved. - - I have mesa test packages built against llvm 3.6 here: - - https://launchpad.net/~jderose/+archive/ubuntu/mesa/+packages - - I couldn't test the installation without a re-spun ISO, but I did - confirm that after updating to the mesa packages in my PPA, I could - again use Unity. So I'm pretty sure this will fix installing from the - ISO as well. - - My hunch is that llvm 3.8 is generating invalid code during its JIT - compilation for llvmpipe, but it could also be the result of memory - corruption. Either way, building mesa against llvm 3.6 seems to be quick - the fix. - - Note this is a regression from 14.04.4 and 15.10, both of which install - fine on the hardware effected by this bug. - - For concrete examples of System76 hardware effected by this: - - 1) All Skylake laptops with 970m, 980m, and 980gtx GPUs - - 2) All Skylake and Haswell-E desktops with 970gtx and 980gtx GPUs - (although strangely, things seem to work with when you connect to a - monitor over HDMI, but always fails when connecting to a monitor over - DisplayPort) - - Note that none of the above failed tested scenarios are using Optimus: - all are using discrete GPU configurations. - - In my testing thus far on the effected hardware, the install always - fails if you choose "Try Ubuntu without installing". The install usually - seems to work when you choose "Install Ubuntu", but even this 2nd - scenario sometimes fails (and when it does, you'll see the same "trap - invalid opcode" bits in dmesg). - - Also note that so far I've only tested amd64, haven't tested i386. - - I suspect there is some deeper weirdness here, but at this point - System76 is just trying to make sure we have a Xenial ISO from which - customers can re-install Ubuntu. - - Old description - === - Currently Unity on Xenial is unusable when the llvmpipe software fallback is used, at least on certain hardware. - - For example, from dmesg: - - [ 2092.557913] traps: compiz[10155] trap invalid opcode ip:7efc940030d4 sp:7ffccd914ea0 error:0 - [ 2093.109485] traps: compiz[10192] trap invalid opcode ip:7f38ac01a0d4 sp:7ffe5ed737e0 error:0 - [ 2093.718863] traps: compiz[10212] trap invalid opcode ip:7fe6900010d4 sp:7ffd55804020 error:0 - - This definitely effects hardware we've tested with NVIDIA 970m and 980m - GPUs (when using the nouveau driver), and probably effects others as - well. - - Although strangely, with some NVIDIA 900 series hardware we're not - seeing this bug when using the nouveau driver. This will be investigated - further. - - In the current state, it's not possible to install Xenial on effected - hardware using recent daily desktop amd64 ISOs. - - Note this problem exists both when run against mesa 11.1.2-1ubuntu2 in - Xenial proper, and when run against mesa 11.2.0~rc4-1ubuntu0.1 from - ppa:canonical-x/x-staging. (The later test was done with the System76 - imaging system using an image with ppa:canonical-x/x-staging and - nvidia-361 pre-installed, then removing nvidia-361 and
[Ubuntu-x-swat] [Bug 1564156] Re: xenial: invalid opcode when using llvmpipe
Just confirmed on Skylake hardware that llvm-toolchain-3.8 from proposed fixes this issue on Skylake hardware using llvmpipe. Thanks! ** Changed in: system76 Status: Triaged => Fix Committed ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1564156 Title: xenial: invalid opcode when using llvmpipe To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1564156/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1564156] Re: xenial: invalid opcode when using llvmpipe
After further investigating, it seems this bug doesn't effect Haswell-E after all, sorry about the confusion. Will continue to report back as we learn more. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1564156 Title: xenial: invalid opcode when using llvmpipe To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1564156/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1564156] Re: xenial: invalid opcode when using llvmpipe
I can confirm that tjaalton's above test packages fix the problem on a Skylake laptop with an i7-6700 CPU and an Nvidia 970m GPU when using the nouveau driver. I installed libllvm3.8_3.8-2ubuntu1.1_amd64.deb from a VT then rebooted, and now I have working Unity again. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1564156 Title: xenial: invalid opcode when using llvmpipe To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1564156/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1564156] Re: xenial: invalid opcode when using llvmpipe
Oh, and another bit of information: our laptops all use embedded Display Port for their connection to the internal screen, and in this case, this bug always manifests. So at least in our testing so far, both eDP and DP seem to be effected. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1564156 Title: xenial: invalid opcode when using llvmpipe To manage notifications about this bug go to: https://bugs.launchpad.net/system76/+bug/1564156/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1564156] Re: xenial: invalid opcode when using llvmpipe
So there seems to be a curious pattern with this bug (which might provide an important hint): on desktop systems with 970 GTX or 980 GTX cards, this bug always seems to happen when connected to a monitor over DisplayPort, but does *not* seem to happen when connected to a monitor over HDMI. We'll investigate this more carefully as soon as there's a new Xenial daily build available (with the 4.4.0-18-generic kernel). -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1564156 Title: xenial: invalid opcode when using llvmpipe To manage notifications about this bug go to: https://bugs.launchpad.net/system76/+bug/1564156/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1561685] Re: x-staging: 1.18.2-2ubuntu0.1 host breaks arrow keys on qemu guest
** Changed in: xorg-server (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1561685 Title: x-staging: 1.18.2-2ubuntu0.1 host breaks arrow keys on qemu guest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1561685/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1561685] Re: x-staging: 1.18.2-2ubuntu0.1 host breaks arrow keys on qemu guest
Correction: this is fixed as of 1.18.3-1ubuntu2. 1.18.3-1ubuntu1 still had this problem. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1561685 Title: x-staging: 1.18.2-2ubuntu0.1 host breaks arrow keys on qemu guest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1561685/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1561685] Re: x-staging: 1.18.2-2ubuntu0.1 host breaks arrow keys on qemu guest
I'm no longer having this problem as of 1.18.3-1ubuntu1. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1561685 Title: x-staging: 1.18.2-2ubuntu0.1 host breaks arrow keys on qemu guest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1561685/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1561685] Re: x-staging: 1.18.2-2ubuntu0.1 host breaks arrow keys on qemu guest
Okay, I just tried this on an Intel GPU system, and it has the same problem. Arrow keys are broken with 1.18.2-2ubuntu0.1, but work fine with 1.18.1-1ubuntu4. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1561685 Title: x-staging: 1.18.2-2ubuntu0.1 host breaks arrow keys on qemu guest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1561685/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1561685] [NEW] x-staging: 1.18.2-2ubuntu0.1 host breaks arrow keys on qemu guest
Public bug reported: This is an odd one. 1.18.2-2ubuntu0.1 (on the host) breaks the arrow keys on qemu guests. Actually, I'm not sure it breaks the arrow keys on the guest in all scenarios, but it at least breaks them in the pre-boot menu when trying to install a qemu VM from an ISO. For example, if I try to install a qemu VM from ubuntu-14.04.4-desktop- amd64.iso (in BIOS-mode): 1) I hit shift to get to the menu, hit enter to choose English (both of which work) 2) Nothing happens when I hit the down arrow key to try and select "Install Ubuntu" 3) I hit F4 (which works) to open the Mode selector, but then nothing happens when I hit the down arrow to try and select "OEM install (for manufactures)" After I downgraded xserver-common, xserver-xorg-core to the 1.18.1-1ubuntu4 packages in Xenial proper, everything works fine again (which is how I narrowed this bug down to xorg-server). I also didn't have this problem when using 1.18.2-1ubuntu0.3 from the x-staging PPA (which I had been using for several weeks), so it seems that 1.18.2-2ubuntu0.1 introduced this regression. Note that this issues seems to break all the arrow keys, not just the down arrow key. If I hit shift to get to the menu, none of the arrow keys do anything if I try to select a different language. Or if hit enter to choose English and then hit F3 to open the Keymap selector, none of the arrow keys work for selecting a different Keymap. As far as the guest goes, I've tried the desktop amd64 ISO for 14.04.4, 15.10, and the latest Xenial daily, all in both BIOS-mode and UEFI-mode. In all six scenarios, the arrow keys don't work. Same problem with the server amd64 ISOs (although I only tried BIOS-mode in this case). Normally I use '-vga qxl', but I also tried '-vga std' on a whim, and the result is the same: the arrow keys don't work. One final note is that the arrow keys work fine when used with any other application on the host. qemu is the only place I've found any issues. Oh, and in case it's relevant, I have an NVIDIA 970m GPU and am using the nvidia-361 proprietary driver. Later today I'll test this with Nouveau, and will also try this on an Intel GPU system. But as this seems related to keyboard input rather than the GPU driver, my hunch is the result will be the same. ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Description changed: This is an odd one. 1.18.2-2ubuntu0.1 (on the host) breaks the arrow keys on qemu guests. Actually, I'm not sure it breaks the arrow keys on the guest in all scenarios, but it at least breaks them in the pre-boot menu when trying to install a qemu VM from an ISO. For example, if I try to install a qemu VM from ubuntu-14.04.4-desktop- amd64.iso (in BIOS-mode): 1) I hit shift to get to the menu, hit enter to choose English (both of which work) 2) Nothing happens when I hit the down arrow key to try and select "Install Ubuntu" 3) I hit F4 (which works) to open the Mode selector, but then nothing happens when I hit the down arrow to try and select "OEM install (for manufactures)" After I downgraded xserver-common, xserver-xorg-core to the 1.18.1-1ubuntu4 packages in Xenial proper, everything works fine again (which is how I narrowed this bug down to xorg-server). I also didn't have this problem when using 1.18.2-1ubuntu0.3 from the x-staging PPA (which I had been using for several weeks), so it seems that 1.18.2-2ubuntu0.1 introduced this regression. Note that this issues seems to break all the arrow keys, not just the down arrow key. If I hit shift to get to the menu, none of the arrow keys do anything if I try to select a different language. Or if hit enter to choose English and then hit F3 to open the Keymap selector, none of the arrow keys work for selecting a different Keymap. As far as the guest goes, I've tried the desktop amd64 ISO for 14.04.4, 15.10, and the latest Xenial daily, all in both BIOS-mode and UEFI-mode. In all six scenarios, the arrow keys don't work. Same problem with the server amd64 ISOs (although I only tried BIOS-mode in this case). Normally I use '-vga qxl', but I also tried '-vga std' on a whim, and the result is the same: the arrow keys don't work. - One final note is that the arrow keys work find when used with any other + One final note is that the arrow keys work fine when used with any other application on the host. qemu is the only place I've found any issues. Oh, and in case it's relevant, I have an NVIDIA 970m GPU and am using the nvidia-361 proprietary driver. Later today I'll test this with Nouveau, and will also try this on an Intel GPU system. But as this seems related to keyboard input rather than the GPU driver, my hunch is the result will be the same. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu.
[Ubuntu-x-swat] [Bug 1484279] Re: [FFe] Mesa 11.0.0
Likewise, I've been doing extensive testing with mesa 11 from the x-staging PPA on Haswell, Broadwell, and Skylake hardware, haven't hit any issues. Timo, when do you expect mesa 11 to at least hit wily-proposed? I'll admit it makes me a bit nervous that mesa 11 isn't in wily proper yet :D -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1484279 Title: [FFe] Mesa 11.0.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1484279/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1484279] Re: [FFe] Mesa 11.0.0
Quick question: mesa11 depends on libllvm3.7, but libllvm3.7 is still in universe. Is there a plan to promote libllvm3.7 to main? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1484279 Title: [FFe] Mesa 11.0.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1484279/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1484279] Re: [FFe] Mesa 11.0.0
Oops, never mind... I see that libllvm3.7 being in main is mentioned in the summary, sorry for the noise! -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1484279 Title: [FFe] Mesa 11.0.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1484279/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1484279] Re: [FFe] Mesa 11.0.0
Timo, Awesome, thanks for the quick fix! I'll test it under qemu as soon as the builds are finished. Thanks! -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1484279 Title: [FFe] Mesa 11.0.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1484279/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1484279] Re: [FFe] Mesa 11.0.0
Timo, 11.0.0~rc2-1ubuntu1~ppa2 seems shiny with Unity under qemu. Thanks! -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1484279 Title: [FFe] Mesa 11.0.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1484279/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1484279] Re: [FFe] Mesa 11.0.0
I've started testing the mesa 11 rc2 packages here: https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging One issue I've hit is that with mesa 11 rc2 installed, Unity will no longer run under qemu (note I'm testing with an amd64 VM, Wily host and Wily guest). Attaching the full unit7.log file, but my hunch is the key failure from the log is: Compiz (opengl) - Fatal: glXQueryExtensionsString is NULL for screen 0 Thanks! ** Attachment added: "unity7.log" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1484279/+attachment/4456917/+files/unity7.log -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1484279 Title: [FFe] Mesa 11.0.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1484279/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1465706] Re: SRU: New upstream releases of nvidia for 14.04.3
I spent a lot of time beating on the proposed Trusty nvidia-346 (346.82-0ubuntu0.2) and nvidia-340 (340.76-0ubuntu0.1) packages yesterday, and things seem solid to me. Package upgrade/downgrade paths I tested: 331 -- 340 331 -- 346 340 -- 346 346 -- 340 I tested that things work correctly re stopping nvidia-persistenced when removing/purging 340/346, and I gave them my usually does Unity seem to work? sanity check and ran the unigine-valley demo. Everything seems good. I also tested the upgrade from the 346.59 packages currently in the System76 stable Trusty PPA, which although not of direct concern to Ubuntu is something I still needed to check and also attests to the overall correctness of these proposed packages. The upgrade from our 346.59 to the proposed 346.82 works swimmingly. However, I'm not personally comfortable removing verification-failed, adding the verification-done tag as the one thing I couldn't test is Optimus (as System76 doesn't sell any Optimus hardware). Note I only tested nvidia-340/nvidia-346, didn't directly test nvidia-340-updates/nvidia-346-updates. But AFAIK, the two flavors are currently identical, so I'd expect the results to be the same. Also note that I tested with the 3.16 and 3.19 kernels, but did not yet test with the 3.13 kernel. In summary: from my perspective, these proposed packages are good to go after someone else can test on Optimus hardware and test under the 3.13 kernel (and I'll test with the 3.13 kernel tomorrow if I have a chance). Thanks! -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1465706 Title: SRU: New upstream releases of nvidia for 14.04.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1465706/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1479524] Re: Totem Crashes at launch from missing libwayland-egl
+1 on getting this properly fixed in the mesa Depends, but at least fixing it in the ISO manifest is a huge step forward. Thanks! -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1479524 Title: Totem Crashes at launch from missing libwayland-egl To manage notifications about this bug go to: https://bugs.launchpad.net/system76/+bug/1479524/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1323006] Re: touchpad too sensitive. focus jumps all over document on text input
Maarten, System76 has been using a patched unity-settings-daemon that launches syndaemon with: syndaemon -i 0.75 -K -R This has worked extremely well for us on Trusty (and we have solid customer survey data confirming that this has greatly improved the user experience). However, something strange is going on with xserver-xorg-input-synaptics in Utopic. If you get syndaemon into its disabled state by typing a quick burst of characters, you can often keep it stuck in this disabled state by moving your finger back and forth on the track pad. It seems as if the inactivity countdown isn't starting till there is a period when neither any keypresses nor any mouse movement has happened. Can you think of any changes that might have cause this behavior? Steps to reproduce: 1) open gedit 2) move finger back and forth on clickpad, confirm that cursor is moving back and forth 3) while continuing to move finger back and forth on the clickpad, type a few characters... cursor should disappear 4) cursor should be re-enabled around 0.75 seconds after you stop typing, but sometimes it will remain stuck in the disabled mode as long as there is more or less continuous motion on the clickpad 5) if stuck in the disabled state, it seems briefly lifting your finger off the track pad is reliable way to unstick it -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1323006 Title: touchpad too sensitive. focus jumps all over document on text input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1323006/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
