[Ubuntu-x-swat] [Bug 1637032] Re: The screen keeps flashing (even in text terminal mode)

2016-11-18 Thread Poldi
Somebody in the Forum suggested to add the output of inxi, so here it is llist@LeosGameLaptop:~/Downloads$ inxi -G Graphics: Card-1: Intel 4th Gen Core Processor Integrated Graphics Controller Card-2: NVIDIA GM204M [GeForce GTX 970M] Display Server: X.Org 1.18.4 driver: N/A

[Ubuntu-x-swat] [Bug 1637032] Re: The screen keeps flashing (even in text terminal mode)

2016-11-18 Thread Poldi
I should have been more precise when indicating that I have the same problem when booting from the LiveCD. I'm getting the flashing screen at the Welcome screen after booting the LiveCD (where it asks you if you want to try Ubuntu) -- You received this bug notification because you are a member

[Ubuntu-x-swat] [Bug 1637316] Re: Screen flickering/tearing on Ubuntu 16.10 64-bit on kernel version 4.8.0-26-generic

2016-11-18 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu.

[Ubuntu-x-swat] [Bug 1620013] Re: GPU Hang [i915 / drm] crashes whole session; triggered by LibreOffice dialog boxes (regression)

2016-11-18 Thread Launchpad Bug Tracker
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu.

[Ubuntu-x-swat] [Bug 1639051] Re: gnome3 has black screen after upgrade: 304.131-0ubuntu0.14.04.2, 304.132-0ubuntu0.14.04.2

2016-11-18 Thread Konrad
Nvidia is investigating this bug: https://devtalk.nvidia.com/default/topic/968892/linux/geforce-7300le-with-304-132-glxinfo-fails-now-with-quot-x-error-of-failed-request-badvalue-quot-/2 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to

[Ubuntu-x-swat] [Bug 1480673] Re: [ELAN 3320KD-3100] Asus T300 CHI bluetooth Touchpad is recognized incorrectly

2016-11-18 Thread TJ
** Bug watch added: freedesktop.org Bugzilla #98770 https://bugs.freedesktop.org/show_bug.cgi?id=98770 ** Also affects: xinput-calibrator via https://bugs.freedesktop.org/show_bug.cgi?id=98770 Importance: Unknown Status: Unknown ** Project changed: xinput-calibrator => libinput

[Ubuntu-x-swat] [Bug 1590590] Re: Touchpad not recognized on Dell Latitude E7470 Ultrabook

2016-11-18 Thread bagl0312
@chmelab @pmonas indeed I was wondering if this kind of fix are expected to be backported to relevant older kernels. In this case it should be backported at least to the 4.4.x series. I have experience of other bug fixes backported to previous kernel versions, so this should be the case also for

[Ubuntu-x-swat] [Bug 1641974] Re: xinput setting is reseted after a hibernation

2016-11-18 Thread t4eg
** Package changed: fcitx (Ubuntu) => xinput (Ubuntu) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xinput in Ubuntu. https://bugs.launchpad.net/bugs/1641974 Title: xinput setting is reseted after a hibernation To manage notifications

[Ubuntu-x-swat] [Bug 1641974] [NEW] xinput setting is reseted after a hibernation

2016-11-18 Thread Launchpad Bug Tracker
You have been subscribed to a public bug: I use ~/.xprofile to run a command 'xinput disable "device"'. This works well and disables the device on a first boot time. But after a hibernation, that device is enabled again. On Ubuntu 16.04 LTS, I have no problem. I'd like to disable a device

[Ubuntu-x-swat] [Bug 1590590] Re: Touchpad not recognized on Dell Latitude E7470 Ultrabook

2016-11-18 Thread Adam
@chmelab It's not currently fixed in 4.4.x; the question is whether it's going to be fixed in the 4.4.x kernel at any point in the future, and if so, when. (from my point of view I'd rather not move away from LTS unless absolutely necessary) -- You received this bug notification because you are

[Ubuntu-x-swat] [Bug 1590590] Re: Touchpad not recognized on Dell Latitude E7470 Ultrabook

2016-11-18 Thread Petr Chmelar
No @bagl0312, this is not fixed in Linux p37470 4.4.0-47-generic #68-Ubuntu SMP Wed Oct 26 19:39:52 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux I spoke to some Dell representatives and they told me that anyone with Premium Support can report the this issue and they are supposed to fix it, because

[Ubuntu-x-swat] [Bug 1639180] Re: no login possible after update to nvidia 304.132

2016-11-18 Thread Nick Lott
Just hit this and judging from various comments online lots of other people have to. You might want to withdraw version 304.132... -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.

[Ubuntu-x-swat] [Bug 1642929] Re: no screen output prior to login while in docking station

2016-11-18 Thread kringalf
Hardware is a DELL LATITUDE E6530 -- 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/1642929 Title: no screen output prior to login while in docking station To manage notifications about this bug

[Ubuntu-x-swat] [Bug 1642929] [NEW] no screen output prior to login while in docking station

2016-11-18 Thread kringalf
Public bug reported: while the laptop is in the docking station there is no output on any monitor as long as i'm not logged into kde. The output stops right after the password for the encrypted root disk and the screens stay blank until i login to kde if i start outside the docking station i

[Ubuntu-x-swat] [Bug 1568604] Re: Mouse cursor lost when unlocking with Intel graphics

2016-11-18 Thread Martin Pitt
I don't see anythign left to sponsor here, so unsubscribing sponsors now. Please re-subscribe when you upload further patches. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu.

[Ubuntu-x-swat] [Bug 1636397] Re: Fix modesetting slave output names

2016-11-18 Thread Launchpad Bug Tracker
This bug was fixed in the package xorg-server - 2:1.18.4-1ubuntu6.1 --- xorg-server (2:1.18.4-1ubuntu6.1) yakkety; urgency=medium * modesetting-unifdef-slave-support.diff: Fix modesetting slave output names. (LP: #1636397) -- Timo Aaltonen Tue, 01 Nov

[Ubuntu-x-swat] [Bug 1636397] Re: Fix modesetting slave output names

2016-11-18 Thread Martin Pitt
unity8 tests have always been brittle; the autopilot ones (which use X) succeeded, while the QML ones (which don't use X) didn't, so this appears unrelated. -- 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 1636397] Re: Fix modesetting slave output names

2016-11-18 Thread Launchpad Bug Tracker
This bug was fixed in the package xorg-server - 2:1.18.4-0ubuntu0.2 --- xorg-server (2:1.18.4-0ubuntu0.2) xenial; urgency=medium * modesetting-unifdef-slave-support.diff: Fix modesetting slave output names. (LP: #1636397) -- Timo Aaltonen Tue, 01 Nov

[Ubuntu-x-swat] [Bug 1636397] Update Released

2016-11-18 Thread Martin Pitt
The verification of the Stable Release Update for xorg-server has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you