** Changed in: linuxmint
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1667158
Title:
Regression: Borders of windows and desktop background are displayed
Agree.
On 05/06/2017 22:31, Mike Gresens wrote:
> So this bug should be closed?!
>
> ** Description changed:
>
> + == Update4: ==
> +
> + The nvidia driver 375.66 is now part of the default repo.
> + Since the bugfix is contained in this driver, we should close the bug?!
> +
>== Update3: ==
Here the nvidia driver 375.66 installed via default repo works fine too.
No problems.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1667158
Title:
Regression: Borders of windows and desktop
So this bug should be closed?!
** Description changed:
+ == Update4: ==
+
+ The nvidia driver 375.66 is now part of the default repo.
+ Since the bugfix is contained in this driver, we should close the bug?!
+
== Update3: ==
nvidia delivered a new driver: 375.66
Contains the same
Driver Version 375.66 update is now available in the official 17.04
repositories.
Just updated and tested. The problem is fixed for me now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1667158
Would like to see driver 375.66 in the official 17.04 repositories too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1667158
Title:
Regression: Borders of windows and desktop background are
Any chances we will see driver 375.66 in the official 17.04
repositories?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1667158
Title:
Regression: Borders of windows and desktop background are
Here the nvidia driver 375.66 installed via ppa works fine too. No
problems.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1667158
Title:
Regression: Borders of windows and desktop background are
** Description changed:
== Update3: ==
nvidia delivered a new driver: 375.66
Contains the same bugfix as 381.09 beta
- Unfortunately the driver is not yet available via Graphics Drivers PPA
+
+ This driver can now be installed via ppa from Graphics Drivers Team and
+ sudo apt-get
Just installed 375.66 from the Graphic Drivers PPA (updated about a hour ago),
and it fixed the suspension bug for me. All the windows and applications appear
just fine.
So far I have not encountered any other bugs.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Description changed:
+ == Update3: ==
+
+ nvidia delivered a new driver: 375.66
+
+ Contains the same bugfix as 381.09 beta
+ Unfortunately the driver is not yet available via Graphics Drivers PPA
+
+ Should driver 375.66 become the default driver for Ubuntu 17.04 -
+ available without PPA
Hi at all. With Driver 381 are the artefacts gone, but after waking up
is the performance extremly low! I've tested with phoronix-test-suite
benchmark xonotic. My system is a Notebook with i7-7700HQ with NVIDIA
GTX 1060 mobile. Does andybode has the same problem?
--
You received this bug
I am using cairo-dock alongside unity launcher. An issue I do encounter
with using 381.09, is that after waking, certain icons/applet like gnome
terminal, idle_python, gedit, Pidgin, musicplayer would not appear
correctly unless a new GUI of these app is created/deleted. For music
player I have to
I also installed ppa 381.09 on Ubuntu 17.04 and so far, it works fine :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1667158
Title:
Regression: Borders of windows and desktop background are
For me, 381.09 addressed the fat white borders around windows. However,
cool-retro-term comes back with a completely white window. I can type
"exit" into it to shut it down, & it acts normally after relaunching it.
I haven't yet identified other programs unhappy after a resume under
381.09 - in
@SunBear
Thanks for confirmation.
After some debate with nvidia devtalk, I tried different kernel (4.9 vs 4.4LTS)
and fan operates after resume from sleep/hib.
This was due to fan speed control being done by motherboard and not nvidia
driver. I'm on a laptop.
Thanks to all for tour input!
@kcm.
I tried both scenario. Before and after suspend. GPU performances are similar.
I have tried another test. While running the nbody simulation, I went into
suspend mode. After waking, i found the nobody simulation stopped. However, i
could not restart it because:
"Error: only 0 Devices
For me with driver 381.09 the fan works fine (starting at ca. 50°C) and max.
temperature < 70°C.
After suspend/resume all works fine too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1667158
Title:
@SunBear
Just to confirm I made my issue clear:
This only happens to me on resume after suspend/hib. cycle, then and
only then fan STOPS WORKING and consequently TEMPS rise, GPU throttles,
etc.
Before sleep/suspend/hib. all is ok with temps/ fan rotation.
Only after resume from sleep I get
I installed 381 using the ppa and it's working fine, so thanks to SunBear.
Temperature seems OK but since I'm on laptop (ASUS X751L with Geforce 940M -
running Xenial) of course there is no specific fan for Graphic card. For
information I'm adding 2 screenshots of sensors, before and after using
@experimencer Thanks again. It helped me tied over this period. ;)
@huiprobable To solve your issue, I think you have to run the script
after passing password authentication. You might want to try driver
381.09 instead since it is now available.
--
You received this bug notification because you
@kcm.
I ran GPU calculations
/NVIDIA_CUDA-8.0_Samples/5_Simulations/nbody/nbody and also
https://www.airtightinteractive.com/demos/ribbons/ for about 20 mins.
Nvidia X Server Setting --> GPU 0 - (GForce GTX Titan)
--> Thermal Setting showed:
Temperature = 72 to 75 degrees C, Fan speed =
Rolled back to 375.39, besides graph. corruption, the fan not kicking in after
resume from suspend issue is also true.
Can anyone verify if this also happens with your system regardless of driver
version?
You've got to run some 3d stuff to get the heat up like (firefox/chrome/vivaldi)
Did the ppa 381 install, seems fine after suspend/hib. resume on
graphics/windows corruption issue but GPU fan STOPS WORKING!!
Only GPU throttling but NO FAN KICKING IN
Restart X won't fix it, only reboot.
Now it's getting dangerous...
HW: Clevo N150RD i7-6700HQ 16Gb Nvidia GTX960M
Distributor
** Description changed:
== Update2: ==
nvidia delivered a new driver: 381.09 beta
https://devtalk.nvidia.com/default/topic/1002788
From release notes:
"Fixed a regression that caused corruption in certain applications, such
as window border shadows in Unity, after resuming
Ok, got it, found the PPA here: https://launchpad.net/~graphics-
drivers/+archive/ubuntu/ppa and using synaptic installed the Nvidia 381
beta driver in my Xenial 16.04.01, and it seems to fix the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thanks @sunbear-c22 for sharing my workaround
(https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-375/+bug/1667158/comments/12), simpler vesion in Bash shell that
I'm currently using after resume from suspend:
kill $(ps -eo pid,comm | grep "compiz" | grep -v grep | awk '{print
I have updated to Nvidia 381.09 driver via the ppa update route too.
No problems at all.
For me this bug is solved with new driver.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1667158
Title:
I have updated to Nvidia 381.09 driver via the ppa update route. The bad
window borders caused by drivers 375.39 and 378.13 do not appear in this
new driver. In my system, on the first reboot(after installing 381.09),
I did get a black screen partially obscuring my unity desktop for a
short while
** Description changed:
== Update2: ==
nvidia delivered a new driver: 381.09 beta
https://devtalk.nvidia.com/default/topic/1002788
From release notes:
"Fixed a regression that caused corruption in certain applications, such
as window border shadows in Unity, after resuming
Michael from the "Graphics Drivers" Team has already uploaded the new
381.09 beta driver in their ppa 2 hours ago. So those using this ppa
select this driver update soon.
For those not using it, this is the simplest way to have your nvidia
graphic driver updated with the latest. You can access it
lol ... just happened to me ...
Fortunately, one can switch to console (Ctl-Alt-F1) and apply code of Pavel's
link (post #51), which is roughly what I did to recover, after trying to
install 'nouveau' driver (installation succeeded via apt but system was looping
on login page).
--
You
@Pavel Thank you for the reminder. ;)
Yes, I agree with you. Do manual installation if you are prepared to
spend quite a bit of time tinkering about. Else, a user will find
themselves having to go through a steep learning curve about lightdm,
systemd, Xorg, Grub2, kdms and administrator bash
@SunBear, I just want to warning everyone, that drivers from the Nvidia
site (*.run files) if you try to install them could brake your system. For
more details see here:
http://askubuntu.com/questions/727995/login-loop-after-installing-nvidia-drivers-on-ubuntu-14-04
(also it's true for 16.x).
@MikeGresens Thanks for updating. According to the Nvidia update note on
381.09, it is suppose to fix the badborder issue. However, the ppa
:graphics-drivers/ppa team has not uploaded it yet. To use it, the
appropriate driver has to be manually downloaded (use the hyperlink
provided in the webpage
** Description changed:
- == Update: ==
+ == Update2: ==
nvidia delivered a new driver: 381.09 beta
https://devtalk.nvidia.com/default/topic/1002788
From release notes:
"Fixed a regression that caused corruption in certain applications, such
as window border shadows in Unity,
I ran into the same issue, and the method suggested by #13 fixes it.
However, it also bypassed the password prompt when I try to wake up the
computer from sleep (suspend). However, I'd like to recover the password
protection when awakening from sleep. How should I do that?
--
You received this
https://devtalk.nvidia.com/default/topic/1002788
Does the new nvidia driver 381.09 beta work?
Does the driver solve this bug?
** Description changed:
== Update: ==
- Nvidia states that the bug will be fixed in the next release:
** Description changed:
== Update: ==
- Nvidia states that the bug will be fixed in the next release:
https://devtalk.nvidia.com/default/topic/990898/linux/suspend-corrupts-window-manager-after-upgrade-to-378-09/2.
However no timeline for the next release was mentioned.
+ Nvidia states that
** Description changed:
== Update: ==
- Nvidia states that the bug will be fixed in the next release:
https://devtalk.nvidia.com/default/topic/990898/linux/suspend-corrupts-window-manager-after-upgrade-to-378-09/2
+ Nvidia states that the bug will be fixed in the next release:
Hi Jan. I saw your email summarising the alternative solutions. Note, it
was email to me instead of appearing in launchpad bug report. Maybe you
can fix that so others can read?
On 03/04/2017 14:02, Jan Rathmann wrote:
> ** Description changed:
>
> + == Update: ==
> + Nvidia states that the
** Description changed:
+ == Update: ==
+ Nvidia states that the bug will be fixed in the next release:
https://devtalk.nvidia.com/default/topic/990898/linux/suspend-corrupts-window-manager-after-upgrade-to-378-09/2
+
+ == Possible workarounds for the time being ==
+
+ - Install nvidia-340
I don't know if it's a bug in the driver, but for comparison, 375.39
works fine on Debian Stretch / GNOME, there are no glitches after resume
from suspend, on the same machine where this happens in Yakkety, in my
case.
--
You received this bug notification because you are a member of Ubuntu
So, what is current status?
Is it a bug in nvidia-driver 375.39 and 378.13 (both delivered 2017-02-14)?!
Does nvidia know about this bug??
Will nvidia deliver a bugfix?
Can we change the driver versions in our repositories (using 375.26 and
378.09) to avoid the show-stopper? I am using Gtx1080
Update on my findings:
There are 3 versions of Ubuntu 16.04 LTS to date:
1. Ubuntu 16.04 LTS (released on 21st Apr 2016)
2. Ubuntu 16.04.1 LTS (Released on 21st Jul 2016)
3. Ubuntu 16.04.2 LTS (Released on 16th Feb 2017)
However, there appear to be two major versions of Linux kernel used for
Update on my findings:
There are 2 versions of Ubuntu 16.04 LTS to date:
1. Ubuntu 16.04.1 LTS (Released on 21st Jul 2016)
2. Ubuntu 16.04.2 LTS (Released on 16th Feb 2017)
Temporary Solution that worked on my system:
Ubuntu 16.04.1 --- refer to to comment 13.
Correction. Try
compiz --replace &
Note:
1. w/o the '&' symbol, the command runs in the foreground and if you press
Ctrl+C to terminate it accidentally, all windows title and menu bar disappears,
and keyboard input to terminal can become unresponsive. Have to reboot system.
2. with the '&'
I have tried the below command on command line.
compiz --replace
I got a lot of warnings and 2 errors, namely:
ERROR 2017-04-01 02:04:52 unity.glib.dbus.server GLibDBusServer.cpp:538 DBus
name lost 'org.gnome.Shell'
ERROR 2017-04-01 02:04:52 unity.glib.dbus.server GLibDBusServer.cpp:538 DBus
@SvenNeuhaus Hello. Did you save the fixbadborders script in folder
/lib/systemd/system-sleep and make the file executable as mentioned in
comment #13?
On 30/03/2017 18:13, Sven Neuhaus wrote:
> Same here. When I kill compiz it does not get started again
> automatically.. how come? (I'm on
This affects me as well. I use the following to reset my compiz:
killall compiz -HUP
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1667158
Title:
Regression: Borders of windows and desktop
GTX660 + 16.04 here, same bug.
Restarting Compiz is not a good workaround, since it also messes up the
location of windows on virtual desktops.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1667158
Same here. When I kill compiz it does not get started again
automatically.. how come? (I'm on 16.04)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1667158
Title:
Regression: Borders of windows and
Same for me (large white borders full of random-disposed black and red
dots, plus various lines ...), Asus X751L laptop with NVidia Geforce
940M (375.39 proprietary driver) running Ubuntu 16.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Not just borders. I suspect it is anything drawn from images held in
graphics card memory. All of these images should be invalidated on
resume, but instead we just get whatever junk is present. I have
applications where the entire display area is corrupted. These
applications do use volatile
Related to bug #1292830.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1667158
Title:
Regression: Borders of windows and desktop background are displayed
badly after suspend/resume
To manage
Same for me
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1667158
Title:
Regression: Borders of windows and desktop background are displayed
badly after suspend/resume
To manage notifications
Same bug.
Ubuntu 16.04.2 LTS,
Core i7 6700hq,
Nvidia GTX 950m
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1667158
Title:
Regression: Borders of windows and desktop background are displayed
I am seeing this issue as well afte rupdating to latest NVIDIA driver.
Running:
-
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=14.04
DISTRIB_CODENAME=trusty
DISTRIB_DESCRIPTION="Ubuntu 14.04.5 LTS"
-
Nvidia Driver:
375.39
-
Nvidia 560M video card.
--
You received this bug notification because you are a
Same thing for me. Borders all pixely and crappy after resume from
suspend. CompizConfig disabling "Fading Windows" in Effects fixed it for
me. Thanks for the suggestion to disable effects. Screenshot of ugly
window attached.
** Attachment added: "Window with pixel border"
Same in Mint 18.1 Serena w/ Mate desktop
Distributor ID: LinuxMint
Description:Linux Mint 18.1 Serena
Release:18.1
Codename: serena
367 was fine, 375 get the messed up boarders on menu and panels.
Official distro drivers only. No ppa's.
** Also affects: linuxmint
Importance:
Same bug. And now, the drivers 375.39 are the Nvidia drivers from the
official Ubuntu repository !
Ubuntu 16.04.2 LTS,
Core i7 6700hq,
Nvidia GTX 1070.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Same ugly borders when resuming from suspend.
Ubuntu: 16.04.2 LTS
Lenovo Y580
VGA: NVIDIA Corporation GK107M [GeForce GTX 660M]
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1667158
Title:
Same here. Except, this now happens on every resume from suspend with
the latest nvidia 375.39-0ubuntu0.16.10.1 driver. Before this upgrade,
it happened once or twice (with daily suspend-resume cycle) in total
since I upgraded from 16.04 to 16.10 last year.
--
You received this bug notification
If there are people on Yakkety who can't use nvidia-340 for their card,
this command should work to temporarily downgrade to nvidia-367:
sudo apt install nvidia-367=367.57-0ubuntu3 libcuda1-367=367.57-0ubuntu3
nvidia-opencl-icd-367=367.57-0ubuntu3
I have not tested if this will also work on
** Summary changed:
- Borders of pop-up windows are displayed badly
+ Regression: Borders of windows and desktop background are displayed badly
after suspend/resume
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
65 matches
Mail list logo
