[Ubuntu-x-swat] [Bug 1641275] [NEW] apitrace:i386 not installable, depending on missing package python-imaging:i386

2016-11-11 Thread Jani Kärkkäinen
Public bug reported: Cannot install package apitrace:i386. There is a missing dependency on python-imaging:i386 (see: https://bugs.launchpad.net/ubuntu/+source /python-imaging/+bug/1641274) --- The following packages have unmet dependencies: apitrace:i386 : Depends: python-imaging:i386 but it

[Ubuntu-x-swat] [Bug 1570653] Re: LG 31MU97-B Black 31" 4K Monitor not detected properly

2016-11-11 Thread madbiologist
Improvements and bug fixes for your graphics card should eventually filter down from the latest kernels into the stable kernel series, and from then into Ubuntu. If you want to make sure of that, you can file an upstream bug report at bugzilla.kernel.org -- You received this bug notification

[Ubuntu-x-swat] [Bug 1570653] Re: LG 31MU97-B Black 31" 4K Monitor not detected properly

2016-11-11 Thread madbiologist
** Changed in: xorg (Ubuntu) Status: Incomplete => Confirmed -- 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/1570653 Title: LG 31MU97-B Black 31" 4K Monitor not detected properly To

[Ubuntu-x-swat] [Bug 1579596] Re: [amdgpu] [TOPAZ 1002:6900] System failed to resume from suspend with amdgpu loaded.

2016-11-11 Thread Anthony Wong
** Changed in: hwe-next Status: New => Invalid ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Status: Incomplete => Won't Fix ** Changed in: linux (Ubuntu) Status: Invalid => Won't Fix ** Changed in:

[Ubuntu-x-swat] [Bug 1619033] Re: System is freezing

2016-11-11 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 1508407] Re: libre office impress display broken gradient in slide show

2016-11-11 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New => Confirmed -- 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/1508407 Title:

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

2016-11-11 Thread Jim Byrnes
I also cannot log on since the update to 304.132. Ubuntu 14.04 Geforce 9100 Right now I am using the nouveau driver but it is not a satisfactory solution. I have two monitors and with the nouveau driver one runs at a much lower resolution that the other. With the 304.131 driver this was not the

[Ubuntu-x-swat] [Bug 1641233] Re: nvidia-304 (not installed): nvidia-304 kernel module failed to build

2016-11-11 Thread Scott Cowles Jacobs
Lubuntu noticed that I had 304.131-0ubuntu3, and Software Updates offered to install the (non-fixed) 304.132-0ubuntu1. In the changelog displayed, I noted that there was a 304.131-0ubuntu4 and 304.131-0ubuntu5. but the latest I found at the above website was 304.131-0ubuntu3. I see from the

[Ubuntu-x-swat] [Bug 1641233] Re: nvidia-304 (not installed): nvidia-304 kernel module failed to build

2016-11-11 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-304 (Ubuntu) Status: New => Confirmed -- 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 1641233] [NEW] nvidia-304 (not installed): nvidia-304 kernel module failed to build

2016-11-11 Thread Scott Cowles Jacobs
Public bug reported: I had used nvidia-304 successfully in Lubuntu 16.04. With Lubuntu 16.10, it would not load into the kernel. I just recently downloaded a fixed 304.132 version, which loaded into the kernel, and was usable, but a program (Hugin) which had started up fine under nouveau (but

[Ubuntu-x-swat] [Bug 1641215] [NEW] nvidia driver 304 fails to load libGLU, GLX errors

2016-11-11 Thread Galen Thurber
Public bug reported: resulting setup is useless for openGL and SDL rendering is very slow kernels 4.4.0-47 -45 xubuntu 16.04 64bit ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic

[Ubuntu-x-swat] [Bug 1641055] Re: startx, lightdm fail to start

2016-11-11 Thread Remi Meier
After deleting the .Xauthority file, I can now successfully log into a Unity session. The problem seems to be gone (rebooting worked fine after this). Maybe somebody can figure out how I got into this situation, but otherwise the bug can be closed as far as I'm concerned. -- You received this

[Ubuntu-x-swat] [Bug 1641055] Re: startx, lightdm fail to start

2016-11-11 Thread Remi Meier
If I *remove* xserver-xorg-video-intel, lightdm is able to show me the login screen. However, there is corruption on the screen and trying to log into a Unity or Gnome session just shows a blank screen and then puts me back into the login screen after 1 second. -- You received this bug

[Ubuntu-x-swat] [Bug 1570653] Re: LG 31MU97-B Black 31" 4K Monitor not detected properly

2016-11-11 Thread kelargo
following the instructions on http://penguindreams.org/blog/running-a-lg31mu97-on-linux-at-4096x2160 -at-60hz/ the monitor is now able to display at 4096x2160_60. my current kernel is - Linux music 4.4.0-45-lowlatency #66-Ubuntu SMP PREEMPT Wed Oct 19 14:57:51 UTC 2016 x86_64 x86_64 x86_64

[Ubuntu-x-swat] [Bug 1196239] Re: Add support for fake modes on laptop screens which only have one

2016-11-11 Thread Nick Dedekind
I was just including my example as another plus point for fake modes ("scale" in this case didn't mean "output scaling". If we had the fake modes then output scaling wouldn't really be required in this case, as we would have a set of mutually inclusive modes to chose from. -- You received this

[Ubuntu-x-swat] [Bug 1575000] Re: font glyph corruption on dialog box

2016-11-11 Thread Walter Garcia-Fontes
** No longer affects: xorg-server -- 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/1575000 Title: font glyph corruption on dialog box To manage notifications about this bug go to:

[Ubuntu-x-swat] [Bug 1575000] Re: font glyph corruption on dialog box

2016-11-11 Thread Timo Aaltonen
tumbleweed.. tested or not, the bug should be closed with latest updates ** Changed in: xorg-server (Ubuntu Xenial) Status: Incomplete => Fix Released -- 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 1585094] Re: Random stuck keys on Lenovo Yoga 13

2016-11-11 Thread vak
This issue is *very* likely to have smth to do with the other issue mentioned in Description above, i was not seeing this for a long time already and it appeared again similarly to sticky arrow keys: Nov 11 10:26:19 yogi kernel: [37507.484136] atkbd serio0: Unknown key released (translated set

[Ubuntu-x-swat] [Bug 1238914] Re: Random stuck keys on Lenovo Yoga 13

2016-11-11 Thread vak
The bug went away after some package update for several months (wow!) in 16.04 -- therefore I refused to run updates all this time to get a bit of "normal life" during typing ;) A few days ago I did an update and the damn bug returned... several years of suffering from this Bug. BTW, guys, what

[Ubuntu-x-swat] [Bug 1585094] Re: Random stuck keys on Lenovo Yoga 13

2016-11-11 Thread vak
trying to re-open ** Changed in: xorg (Ubuntu) Status: Expired => New -- 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/1585094 Title: Random stuck keys on Lenovo Yoga 13 To manage

[Ubuntu-x-swat] [Bug 1585094] Re: Random stuck keys on Lenovo Yoga 13

2016-11-11 Thread vak
not really expired. The bug went away after some package update for several months (wow!) in 16.04 -- therefore I refused to run updates all this time to get a bit of "normal life" during typing ;) A few days ago I did an update and the damn bug returned... several years of suffering from this

[Ubuntu-x-swat] [Bug 1641055] [NEW] startx, lightdm fail to start

2016-11-11 Thread Remi Meier
Public bug reported: After updating from 16.04 to 16.10, lightdm doesn't start. Adding 'nomodeset' for booting allows it to start, but apparently lacks all acceleration. Trying different kernels doesn't help, including the one from 16.04. Sorry for brevity, I'm writing this on my phone...