[Ubuntu-x-swat] [Bug 1178502] Re: Update Depends on Uninstallable xorg-input-abi-19

After upgrading my Trusty system for kernel 3.13 to kernel 4.4 the touchpad of my XPS 13 9333 (2014) is not working any more. I have found a possible solution on https://ubuntuforums.org/showthread.php?t=2322413 and I hav thus tried to install xserver-xorg-input-synaptics. The apt-get output is:

[Ubuntu-x-swat] [Bug 1631288] Re: XV video screen always on top

dabrain, I am closing this report because as per https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1631288/comments/4 the bug has been fixed in the latest development version of Ubuntu. This is a significant bug in Ubuntu. If you need a fix for the bug in previous versions of Ubuntu, please

[Ubuntu-x-swat] [Bug 1631964] [NEW] Password required twice returning from suspend

Public bug reported: Clean install - no updates available. Also present on a previous install. Suspend machine and restart. Lock screen requiring password - enter password and return to suspended desktop. Within a few seconds machine locks and password is required once more. Using the same

[Ubuntu-x-swat] [Bug 1631964] Re: Password required twice returning from suspend

This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1631964 ** Tags added: iso-testing -- You received this bug notification because you are a member of Ubuntu-X, which is

[Ubuntu-x-swat] [Bug 1632063] [NEW] nvidia-304 304.131-0ubuntu3: nvidia-304 kernel module failed to build

Public bug reported: Upgrade from 14 to 16, error installing nvidia 304 driver ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-304 304.131-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21 Uname: Linux 4.4.0-42-generic x86_64 .tmp.unity_support_test.0:

[Ubuntu-x-swat] [Bug 1632063] Re: nvidia-304 304.131-0ubuntu3: nvidia-304 kernel module failed to build

** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1632063 Title: nvidia-304 304.131-0ubuntu3: nvidia-304 kernel module failed to build

[Ubuntu-x-swat] [Bug 1632063] Re: nvidia-304 304.131-0ubuntu3: nvidia-304 kernel module failed to build

*** This bug is a duplicate of bug 1366925 *** https://bugs.launchpad.net/bugs/1366925 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1366925, so it is being marked as such. Please

Re: [Ubuntu-x-swat] [Bug 1631519] Re: No X on boot with external monitor connected

I have tried two monitors of different brands and a random television. The resolution selected is 1920x1080. On Mon, Oct 10, 2016 at 7:19 PM, Mathieu Trudel-Lapierre < mathieu...@gmail.com> wrote: > Could you please try with a different monitor or share more of the > details of how you are

[Ubuntu-x-swat] [Bug 1632165] [NEW] modesetting driver unbearably slow on MacBookPro12, 1

Public bug reported: After upgrading to Yakkey, I found the graphics performance of my MacBookPro12,1 (13", 2015, retina/hidpi display) became unbearably slow - switching workspaces, playing games, even just scrolling web browser tabs was visibly slower. The computer became constantly warm, and

[Ubuntu-x-swat] [Bug 1632165] Re: modesetting driver unbearably slow on MacBookPro12, 1

A few more points about this. When I first stated looking into this, I found Xorg reporting a few things: - No access to /dev/fb0 (since I wasn't in the video group) - Acceleration seemed to be disabled However after adding myself to the video group (for access to the FB and DRI devices), and

[Ubuntu-x-swat] [Bug 1631519] Re: No X on boot with external monitor connected

These are working with 16.04 perfectly, I updated to 16.10 and had to restore from backups to get back to 16.10. Then I booted from the live- cd to capture this bug. Scenarios: 1. mDP to HDMI cable connected to a 1080p monitor (Dell E248Wfp); that is the simple example and they all fail with

[Ubuntu-x-swat] [Bug 1583538] Re: Minecraft (Java on Xmir) crashes with: OpenGL: ~~ERROR~~ RuntimeException: No OpenGL context found in the current thread.

** Changed in: xorg-server (Ubuntu) Status: Incomplete => Confirmed ** Changed in: xorg-server (Ubuntu) Importance: Undecided => Medium -- 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 1575516] Re: Mir is just a black screen and mouse cursor on Nvidia GTX 900 (and sometimes "Failed to schedule page flip")

** Changed in: canonical-devices-system-image Importance: Undecided => Critical -- 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/1575516 Title: Mir is just a black screen and mouse cursor on

[Ubuntu-x-swat] [Bug 1631519] Re: No X on boot with external monitor connected

Also, the bug was opened with the system running BIOS version 2.57: dmi.bios.version: G2ET97WW (2.57 ) I have upgraded to the latest version and recreated there as well: Version: G2ETA7WW (2.67 ) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed

[Ubuntu-x-swat] [Bug 1631519] Re: No X on boot with external monitor connected

I managed to reproduce it once trying to move from the on-laptop miniDP connector to the dock's full-size DP connector -- then I had a black background (well, no backgound) and the window trails. It looks to me like an issue in compiz, but it might really be X. In doubt, I'm not going to change

[Ubuntu-x-swat] [Bug 1366925] Re: nvidia-* kernel module failed to build [error: code model ‘kernel’ not supported in the 32 bit mode]

** Summary changed: - nvidia-331 331.38-0ubuntu7.1: nvidia-331 kernel module failed to build for kenel 3.16.2 [error: code model ‘kernel’ not supported in the 32 bit mode] + nvidia-* kernel module failed to build [error: code model ‘kernel’ not supported in the 32 bit mode] -- You received

[Ubuntu-x-swat] [Bug 1632165] Re: modesetting driver unbearably slow on MacBookPro12, 1

** Changed in: xorg-server (Ubuntu) Importance: Undecided => High -- 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/1632165 Title: modesetting driver unbearably slow on MacBookPro12,1

[Ubuntu-x-swat] [Bug 1632011] Re: Xorg crashed with SIGABRT

*** This bug is a duplicate of bug 1629769 *** https://bugs.launchpad.net/bugs/1629769 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1629769, so is being marked as such.

[Ubuntu-x-swat] [Bug 1631964] Re: Password required twice returning from suspend

In addition - see a pulseaudio crash when returning from suspend. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1631964 Title: Password required twice returning from

[Ubuntu-x-swat] [Bug 1631288] Re: XV video screen always on top

I have been trying 4.8.1(yakety version) kernel with 16.04 ditribution but the bug still exists. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1631288 Title: XV video screen always on top To

[Ubuntu-x-swat] [Bug 1631288] Re: XV video screen always on top

Dear Christopher, I had a try this morning with a 4.8.1 kernel which is the one used by Yakkety Yak and it does not fix the issue either. :( -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1631288

[Ubuntu-x-swat] [Bug 1631519] Re: No X on boot with external monitor connected

I've tried this on my own Lenovo Thinkpad X230 (also a 2306CTO), and I can't reproduce the issue at all. I've tried both the dock's full-sized DP connector and miniDP on the laptop itself (undocked), both work with no issues at all, and no artifacts on the external screen (or the panel, for that

[Ubuntu-x-swat] [Bug 1631519] Re: No X on boot with external monitor connected

Could you please try with a different monitor or share more of the details of how you are using this, such as which resolution is picked? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1631519

[Ubuntu-x-swat] [Bug 1632165] Re: modesetting driver unbearably slow on MacBookPro12, 1

I feel your pain. This seems to be a duplicate of bug 1612863, but see also the Chrome- specific modesetting performance regression bug 1615871. -- 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 1632165] Re: modesetting driver unbearably slow on intel graphics

** Summary changed: - modesetting driver unbearably slow on MacBookPro12,1 + modesetting driver unbearably slow on intel graphics ** Tags added: performance regression -- 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 1632165] Re: modesetting driver unbearably slow on MacBookPro12, 1

Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg-server (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu.

Re: [Ubuntu-x-swat] [Bug 1632165] Re: modesetting driver unbearably slow on intel graphics

On Tue, Oct 11, 2016 at 2:35 PM, Daniel van Vugt wrote: > I have two theories at least: > 1. modesetting can't deal with hiDPI very well; or > 2. compiz/unity7 is falling back to software rendering under the > modesetting driver. > > Can you please test #2? Just

[Ubuntu-x-swat] [Bug 1632165] Re: modesetting driver unbearably slow on intel graphics

** No longer affects: lightdm (Ubuntu) -- 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/1632165 Title: modesetting driver unbearably slow on intel graphics To manage notifications about

[Ubuntu-x-swat] [Bug 1619919] Re: Cursor jump sometimes by touchpad button

Hi, I have the exact same problem on a Dell XPS 13. 1 out of 20-40 clicks on the touchpad result a pointer jump and a "random" click. It's very annoying. Cheers -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in

[Ubuntu-x-swat] [Bug 1632165] Re: modesetting driver unbearably slow on intel graphics

modesetting works just fine on my broadwell with a 3200x1800 screen, so hidpi is not to blame -- 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/1632165 Title: modesetting driver unbearably

[Ubuntu-x-swat] [Bug 1632165] Re: modesetting driver unbearably slow on intel graphics

btw, gdm probably runs with user permissions? Try another dm -- 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/1632165 Title: modesetting driver unbearably slow on intel graphics To manage

[Ubuntu-x-swat] [Bug 1632165] Re: modesetting driver unbearably slow on intel graphics

Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lightdm (Ubuntu) Status: New => Confirmed -- 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/1632165

[Ubuntu-x-swat] [Bug 1632165] Re: modesetting driver unbearably slow on intel graphics

I have two theories at least: 1. modesetting can't deal with hiDPI very well; or 2. compiz/unity7 is falling back to software rendering under the modesetting driver. Can you please test #2? Just tap the Super key to open the Unity7 dash. Is it translucent or solid coloured? Also, failure to set

[Ubuntu-x-swat] [Bug 1632165] Re: modesetting driver unbearably slow on intel graphics

Alright then... Does gdm let you log in to Unity7 (is it installed)? If so try that and see if it's any smoother (which would make part of the problem the Gnome compositor). -- 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 1612863] Re: Modesetting driver on intel in 16.10 is choppy and not smooth

*** This bug is a duplicate of bug 1632165 *** https://bugs.launchpad.net/bugs/1632165 Would it be better to make this a duplicate of bug 1632165? ** This bug has been marked a duplicate of bug 1632165 modesetting driver unbearably slow on MacBookPro12,1 -- You received this bug

[Ubuntu-x-swat] [Bug 1612863] Re: Intel graphics drivers on 16.10 , choppy and not smooth

*** This bug is a duplicate of bug 1632165 *** https://bugs.launchpad.net/bugs/1632165 Confirmed by duplicate. But see also Chrome bug 1615871. ** Changed in: xorg (Ubuntu) Importance: Low => High ** Changed in: xorg (Ubuntu) Status: Incomplete => Confirmed ** Package changed:

[Ubuntu-x-swat] [Bug 1619919] Re: Cursor jump sometimes by touchpad button

just made an observation, it happens when I use my middle finger to move the mouse and click with index finger. Sometimes the double touch of middle/index finger is interpreted as mouse move, the jump is more or less the same distance as if i had moved the index to the middle finger position . --

[Ubuntu-x-swat] [Bug 1632165] Re: modesetting driver unbearably slow on intel graphics

If gdm runs with user permissions how does/should Gnome Shell get access to /dev/dri/* etc? I assume it's not broken for everyone... -- 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/1632165

[Ubuntu-x-swat] [Bug 1632165] Re: modesetting driver unbearably slow on intel graphics

also, you are not supposed to be on the video group, and glamor should be enabled by default. so attach xorg log without those "tweaks" -- 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 1583538] Re: Minecraft (Java on Xmir) crashes with: OpenGL: ~~ERROR~~ RuntimeException: No OpenGL context found in the current thread.

BTW, same bug in plain Xmir without Libertine. ** Changed in: libertine Status: Triaged => Invalid -- 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/1583538 Title: Minecraft (Java

[Ubuntu-x-swat] [Bug 1583538] Re: Minecraft (Java on Xmir) crashes with: OpenGL: ~~ERROR~~ RuntimeException: No OpenGL context found in the current thread.

** Summary changed: - [desktop] Error creating OpenGL context using Java + Minecraft (Java on Xmir) crashes with: OpenGL: ~~ERROR~~ RuntimeException: No OpenGL context found in the current thread. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed

[Ubuntu-x-swat] [Bug 1583538] Re: Minecraft (Java on Xmir) crashes with: OpenGL: ~~ERROR~~ RuntimeException: No OpenGL context found in the current thread.

Confirmed but incomplete. I can reproduce the Minecraft crash, but Xrandr reports a valid list of modes and all other OpenGL (GLX and EGL) apps work fine in the same Xmir server. Looks like a bug on the Java side...? ** Changed in: xorg-server (Ubuntu) Status: Confirmed => Incomplete --

[Ubuntu-x-swat] [Bug 1583538] Re: Minecraft (Java on Xmir) crashes with: OpenGL: ~~ERROR~~ RuntimeException: No OpenGL context found in the current thread.

Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg-server (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu.