[Ubuntu-x-swat] [Bug 1661486] [NEW] nouveau write fault, CTXSW_TIMEOUT, hangs the display

2017-02-02 Thread Daniel Barrett
Public bug reported: A few hours after upgrading to the latest kernel and plasma (using apt upgrade) in Xenial 16.04LTS, my computer display hung with: Feb 2 20:36:16 snorkack kernel: [83600.290217] nouveau :01:00.0: fifo: write fault at 27c000 engine 00 [GR] client 0e [GPC0/GPCCS] reas

[Ubuntu-x-swat] [Bug 1644335] Re: Do not know

2017-02-02 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. https://bugs.launchpad.net/bugs/1644335

[Ubuntu-x-swat] [Bug 1647158] Re: chart cpu

2017-02-02 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. https://bugs.launchpad.net/bugs/1647158

[Ubuntu-x-swat] [Bug 1619142] Re: [MRE] Update to 1.18.4

2017-02-02 Thread Timo Aaltonen
** Description changed: [Impact] Update xserver to new minor release 1.18.4 in order to gain bugfixes from upstream. [Test case] - Install and run, see that it's being used. + Install and run, check /var/log/Xorg.0.log that it's being used, and that input/output works as they did with t

[Ubuntu-x-swat] [Bug 1655724] Re: Should not break systemd in trusty, conflicts with snapd

2017-02-02 Thread Steve Langasek
Hello Dimitri, or anyone else affected, Accepted xorg-server-lts-xenial into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xorg- server-lts-xenial/2:1.18.3-1ubuntu2.3~trusty1 in a few hours, and then in the -proposed repository. Please help u

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

2017-02-02 Thread Gary Caine
Already did, but just tried again. Still get login loop According to what I've seen it's 304.134-0ubuntu1.16.10.1 not 304.134-0ubuntu0.16.10.1 that fixed the problem in 16.04 Note the 0ubuntu1 not 0ubuntu0 If i try to load 304.134-0ubuntu1.16.10.1 I get this mesage E: Version '304.134-0ubuntu1

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

2017-02-02 Thread Brian Murray
Please try this version of the package - 304.134-0ubuntu0.16.10.1. -- 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/1639180 Title: no login possible after update to nvidia 3

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

2017-02-02 Thread Gary Caine
yes the problem is in 16.10 Yakkety -- 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/1639180 Title: no login possible after update to nvidia 304.132 To manage notifications

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

2017-02-02 Thread comu
Ok, sorry. I thought Ubuntu Xenial was Ubuntu 16.10... but 16.10 is Yakkety. So the problem is in Ubuntu 16.10. -- 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/1639180 Tit

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

2017-02-02 Thread Gary Caine
I just tried installing Nvidia again and still same login loop problem. -- 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/1639180 Title: no login possible after update to nvi

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

2017-02-02 Thread Gary Caine
Just reread your message it's version 304.134-unbuntu1 that fixed the problem in 16.104 not 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. https://bugs.launchpad.net/bugs/1639180 Title: no login

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

2017-02-02 Thread Gary Caine
What is availble in 16.10 is -0ubuntu0 not -0ubuntu1 -- 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/1639180 Title: no login possible after update to nvidia 304.132 To man

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

2017-02-02 Thread Brian Murray
The versions of nvida-304 in 16.04 and 16.10. seem the same. They were released on the same day and copied from the X staging PPA. https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to n

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

2017-02-02 Thread Brian Murray
** Also affects: nvidia-graphics-drivers-304 (Ubuntu Yakkety) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-304 (Ubuntu Yakkety) Status: New => Triaged ** Changed in: nvidia-graphics-drivers-304 (Ubuntu Yakkety) Importance: Undecided => Critical --

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

2017-02-02 Thread comu
Moreover, what I don't understand is why people said that they have the version nvidia 304.134-0ubuntu0.16.04.1 in Ubuntu 16.10. I have checked it, and in Ubuntu 16.10 the available version is this one: 304.134-0ubuntu0.16.10.1 (note the difference in the lasts digits). Maybe both oh them are t

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

2017-02-02 Thread comu
Brian, nobody had said that the problem was solved for Ubuntu 16.10. If you read their messages, they only said that the new version of the driver (nvidia 304.134-0ubuntu0.16.10.1) is already published on the repos. However, when I install this new version, my computer don't login, so the proble

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

2017-02-02 Thread Gary Caine
I have NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] (rev a2) with 16.10 nvidia-304 304.134-0ubuntu1 isn't available just nvidia-304 304.134-0ubuntu0 which still cause the login loop -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-

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

2017-02-02 Thread Gary Caine
I agree it's not solved on 16.10 I believe there is an open bug about it on 16.10 but I can't find it. -- 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/1639180 Title: no lo

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

2017-02-02 Thread Brian Murray
On Thu, Feb 02, 2017 at 10:44:32PM -, comu wrote: > Please reopen the bug. The problem is not solved on Ubuntu 16.10 Could you provide some more information about how you tested and what leads you believe that this not fixed. Plenty of people have indicated, with details, that it works for the

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

2017-02-02 Thread comu
Please reopen the bug. The problem is not solved on Ubuntu 16.10 -- 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/1639180 Title: no login possible after update to nvidia 304

[Ubuntu-x-swat] [Bug 1661409] [NEW] Remove obsolete X drivers from the archive

2017-02-02 Thread Timo Aaltonen
Public bug reported: The kernel has a KMS driver for these since 2012 or so, and they should use the fallback driver on X (modesetting). ** Affects: xserver-xorg-video-ast (Ubuntu) Importance: Undecided Status: New ** Affects: xserver-xorg-video-cirrus (Ubuntu) Importance: Und

[Ubuntu-x-swat] [Bug 1639896] Re: Backport support for AMD Polaris

2017-02-02 Thread Timo Aaltonen
no, it's a separate source package used on 16.04.2 and up, this one is for 16.04{,.1} -- 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/1639896 Title: Backport support for AMD Polaris To manage no

[Ubuntu-x-swat] [Bug 1577573] Re: segmentation fault during X startup 16.04

2017-02-02 Thread Dylan A.
Hi Balazs, Do you still have this issue using Zesty and the last package of openchrome (1:0.5.0-3)? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-openchrome in Ubuntu. https://bugs.launchpad.net/bugs/1577573 Title: segmen

[Ubuntu-x-swat] [Bug 1639896] Re: Backport support for AMD Polaris

2017-02-02 Thread Amr Ibrahim
xserver-xorg-video-amdgpu-hwe-16.04 (1.1.2-1~16.04.1) is in xenial- proposed. Should it be dropped and replaced with this SRU? -- 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/1639896 Title: Backp

[Ubuntu-x-swat] [Bug 1656620] Re: Discoloration in some XFCE icons and window borders

2017-02-02 Thread Sam Rosewood
Does somebody know will this bug affect to Ubuntu 16.0.2 that will be released in a week (http://news.softpedia.com/news/ubuntu-16-04-2-lts-delayed-until-february-9-due-to-serious-boot-regression-512445.shtml)? Or they have a time to fix it? As I know, it will include new mesa etc. I checked Lub

[Ubuntu-x-swat] [Bug 1586260] Re: System freeze & no display if set External monitor as primary (Performance mode)

2017-02-02 Thread Brian Murray
** Changed in: xorg-server-lts-xenial (Ubuntu) Status: New => 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/1586260 Title: System freeze & no display if set External monit

[Ubuntu-x-swat] [Bug 1590553] Re: Xmir -rootless: Buttons are randomly unclickable (popups vanish instantly)

2017-02-02 Thread Brian Murray
** Also affects: xorg-server-lts-xenial (Ubuntu) Importance: Undecided Status: New ** Changed in: xorg-server-lts-xenial (Ubuntu) Status: New => Invalid ** Changed in: xorg-server-lts-xenial (Ubuntu Xenial) Status: New => Fix Committed -- You received this bug notificati

[Ubuntu-x-swat] [Bug 1591356] Re: keyboard autorepeat in Xmir apps & GTK-on-Mir does not work

2017-02-02 Thread Brian Murray
** Also affects: xorg-server-lts-xenial (Ubuntu) Importance: Undecided Status: New ** Changed in: xorg-server-lts-xenial (Ubuntu) Status: New => Invalid ** Changed in: xorg-server-lts-xenial (Ubuntu Xenial) Status: New => Invalid ** Also affects: xorg-server (Ubuntu Trust

[Ubuntu-x-swat] [Bug 1613708] Re: [regression] Xmir: Some buttons are unclickable after rotating the screen

2017-02-02 Thread Brian Murray
** Also affects: xorg-server-lts-xenial (Ubuntu) Importance: Undecided Status: New ** Changed in: xorg-server-lts-xenial (Ubuntu) Status: New => Invalid ** Changed in: xorg-server-lts-xenial (Ubuntu Xenial) Status: New => Invalid ** Also affects: xorg-server (Ubuntu Trust

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

2017-02-02 Thread Brian Murray
** Changed in: xorg-server-lts-xenial (Ubuntu Xenial) Status: New => Invalid ** Changed in: xorg-server-lts-xenial (Ubuntu Yakkety) Status: New => Invalid ** Also affects: xorg-server (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: xorg-server-lts-xenia

[Ubuntu-x-swat] [Bug 1617925] Re: Xmir: Received an unknown 11 event

2017-02-02 Thread Brian Murray
** Also affects: xorg-server-lts-xenial (Ubuntu) Importance: Undecided Status: New ** Also affects: xorg-server (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: xorg-server-lts-xenial (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in:

[Ubuntu-x-swat] [Bug 1617932] Re: Xmir with glamor is spending 11% of its CPU time in epoxy_has_gl_extension

2017-02-02 Thread Brian Murray
** Also affects: xorg-server-lts-xenial (Ubuntu) Importance: Undecided Status: New ** Also affects: xorg-server (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: xorg-server-lts-xenial (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in:

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

2017-02-02 Thread Brian Murray
** Also affects: xorg-server-lts-xenial (Ubuntu) Importance: Undecided Status: New ** Changed in: xorg-server-lts-xenial (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server-lts-xenial in U

[Ubuntu-x-swat] [Bug 1636573] Re: xinit flooding syslog

2017-02-02 Thread fmf
Same here: I finally learned how to update the two packages to the latest version as in message #11 and also upgraded PyOpenSSL with sudo easy_install --upgrade PyOpenSSL but today I got the disk completely filled by .xsessio-errors -- You received this bug notification because you are a member o

[Ubuntu-x-swat] [Bug 1661263] [NEW] printer

2017-02-02 Thread blain
Public bug reported: i cant configure my printers ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: i386

[Ubuntu-x-swat] [Bug 1636573] Re: xinit flooding syslog

2017-02-02 Thread MoiZie
Despite my earlier comment December 10th, this bug is occurring again as of a couple of days ago. I'll try updating to the latest openssl package again... -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/