Closing this bug with Won't fix as this kernel / release is no longer supported.
Please feel free to open a new bug report if you're still experiencing this on
a newer release (Bionic 18.04.3 / Disco 19.04)
Thanks!
** Changed in: linux (Ubuntu)
Status: Incomplete => Won't Fix
--
You
Per Ångström, this bug was reported a while ago and there hasn't been
any activity in it recently. We were wondering if this is still an
issue? If so, could you please test for this with the latest development
release of Ubuntu? ISO images are available from
** Tags removed: regression-potential
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bugs.launchpad.net/bugs/510004
Title:
[lucid regression] random graphics effects after resume from suspend
to
I installed Lucid Lynx to another partition on the same machine. I can
now see the artifacts only briefly before the login screen, but apart
from that the graphics corruption is gone.
--
[lucid regression] random graphics effects after resume from suspend to RAM
I have now updated to Lucid Lynx final, running 2.6.32-22-generic. The
graphics corruption is still present after resume from suspend.
--
[lucid regression] random graphics effects after resume from suspend to RAM
https://bugs.launchpad.net/bugs/510004
You received this bug notification because
I have the same issue with an XPS 1210 (with an nvidia 7400 card).
Interestingly, I have no nvidia drivers installed and nor do I have
compositing/effects enabled.
I am using Kubuntu 4.4.2 and suspend/resume is not working for me -
sometimes I get the artifacts on screen. Sometimes I have a long
** Attachment added: pm-suspend.log
http://launchpadlibrarian.net/43774958/pm-suspend.log
--
[lucid regression] random graphics effects after resume from suspend to RAM
https://bugs.launchpad.net/bugs/510004
You received this bug notification because you are a member of Ubuntu-X,
which is
Chase Douglas wrote:
As per comment #77, I'm closing out this bug.
status:Confirmed → Invalid
What does Invalid mean in this context?
For the record: With nvidida 195.36.15 and kernel 2.6.32-17-generic
#26-Ubuntu, I'm still seeing the same corrupted graphics after resume
from
@Per:
Sorry, I misread your comment and thought things were working on the
Lucid kernel. I'm moving this back to Triaged then.
** Changed in: linux (Ubuntu)
Status: Invalid = Triaged
--
[lucid regression] random graphics effects after resume from suspend to RAM
I have what sounds like a similar problem on my Thinkpad T41, which has
an ATI RV250 GPU. This is 32 bit Lucid, upgraded from Karmic.
Suspend/resume worked fine in Karmic. I'm using the default open-source
ATI drivers. This is a really old GPU by the way.
Hibernate/resume works fine in Lucid.
@Martin Spacek:
Since your issue is different, you need to find a bug that looks like
your issue, or open a new one.
Thanks
--
[lucid regression] random graphics effects after resume from suspend to RAM
https://bugs.launchpad.net/bugs/510004
You received this bug notification because you are a
As per comment #77, I'm closing out this bug.
** Changed in: nvidia-graphics-drivers (Ubuntu)
Status: Confirmed = Invalid
** Changed in: linux (Ubuntu)
Status: Incomplete = Invalid
--
[lucid regression] random graphics effects after resume from suspend to RAM
** Changed in: pm-utils (Ubuntu)
Status: Fix Released = Fix Committed
** Changed in: pm-utils (Ubuntu)
Status: Fix Committed = Fix Released
--
[lucid regression] random graphics effects after resume from suspend to RAM
https://bugs.launchpad.net/bugs/510004
You received this bug
I don't normally check these things as Ubuntu usually doesn't do this sort of
thing, but the only driver I can load in Lucid is 195.36.08 (the 173 driver
fails), which is from my understanding a beta driver. The latest production is
190.53 from Nvidia's website. Now is this not a bit crazy for
Indeed it looks like the current Nvidia drivers may be bad:
http://linuxers.org/article/linux-nvidia-drivers-might-also-have-gpu-fan-speed-issue
I am switching to nouveau as I quite like my laptop!
--
[lucid regression] random graphics effects after resume from suspend to RAM
@mbawsa: The 195.36.15 driver which I linked to above fixes the gpu fan
issue and so should be safe, as is the 190.53 driver.
--
[lucid regression] random graphics effects after resume from suspend to RAM
https://bugs.launchpad.net/bugs/510004
You received this bug notification because you are a
Thanks Alex, but I still question the logic on why a beta driver and
ONLY a beta driver was selected for an LTS.
--
[lucid regression] random graphics effects after resume from suspend to RAM
https://bugs.launchpad.net/bugs/510004
You received this bug notification because you are a member of
Have noticed that now I don't get corruption after resuming (after a fix
to pm-utils I think) but instead X crashes upon resuming, leaving me
staring at the gdm login screen.
Just noticed Nvidia just released an updated driver: 195.36.15 which may
fix this second issue, from
I have downgraded to nvidia 173.14.22 and that gets rid of the corrupted
graphics. I still have to switch between virtual consoles until I can
eventually activate the display.
--
[lucid regression] random graphics effects after resume from suspend to RAM
https://bugs.launchpad.net/bugs/510004
Upgrading to kernel 2.6.33-020633-generic solves all issues for me. I
cannot use nvidia 173.14.22 with that kernel, but 195.36.03 works fine.
--
[lucid regression] random graphics effects after resume from suspend to RAM
https://bugs.launchpad.net/bugs/510004
You received this bug notification
Per's test on the latest kernel gives us some good information. On top
of that, we have made a decision to base Lucid on the 2.6.32 kernel, but
with the drm stack backported from 2.6.33. The first official kernel
with the .33 drm stack has yet to be released, but there is a test
kernel available
Downgrading to nvidia-current_190.53-0ubuntu14 unfortunately doesn't fix
this for me - see attached screen shot and notice white blocks behind
panel and docky windows.
At this stage since the release notes say:
Because of the new alternatives system used for nvidia driver packages,
the nvidia
@Per Angstrom - I am seeing exactly the same corruption on my MacBook
Pro 5,1, with an NVIDIA 9600M GT GPU running latest Lucid with Nvidia
195.36.03 - I noticed that Nvidia have released an updated driver
195.36.08 (ie .03 - .08) - I will try and test this later when I get
home.
@Bryce: Are you
Just noticed 2 other comments confirming similarly back in bug #488720 -
ie. comments 19, 20 and 21 in that bug report suggest that reverting to
the old 190.53 driver should fix this - will also test this and report
back.
--
[lucid regression] random graphics effects after resume from suspend to
Are you planning on shipping .08 in Lucid since its now the latest
stable release from Nvidia ...
Not from what I see at ftp://download.nvidia.com/XFree86/Linux-x86_64/,
which still shows 190.53 as the latest stable driver.
... and MAY help to solve this issue
What in the change log
@Noel: It is the latest stable release -
http://www.nvnews.net/vbulletin/showthread.php?t=122606 - 190.53 is the
old stable release.
Nothing in particular makes me think it could help solved this except
maybe 'Fixed a bug that caused screen corruption after an application
released a
It's been a few days that I haven't booted into Lucid, but today I find
the resume experience even worse than before: not only is the display
garbled after resuming, but now I see seemingly randomly blinking pixels
in a pattern that changes as the screen is updated.
Thanks for your efforts
A snapshot showing how bad it looks today.
** Attachment added: 2010-02-26.png
http://launchpadlibrarian.net/39812744/2010-02-26.png
--
[lucid regression] random graphics effects after resume from suspend to RAM
https://bugs.launchpad.net/bugs/510004
You received this bug notification
Maybe this is interesting: I find that even after exiting KDE, forcing a
restart of X (ALT-sysreq+k) and entering Gnome, I can still see some
pixels changing color.
--
[lucid regression] random graphics effects after resume from suspend to RAM
https://bugs.launchpad.net/bugs/510004
You received
@Per:
Can you run xwininfo on one of the corrupted displays after you resume,
and then paste the output here? We have a theory that hinges on the
result of the properties Backing Store State and Save Under State.
Thanks
--
[lucid regression] random graphics effects after resume from suspend to
@Bryce:
Can you take a look at this bug? It's getting a little beyond the grasp
of our understanding in the kernel team.
Thanks
--
[lucid regression] random graphics effects after resume from suspend to RAM
https://bugs.launchpad.net/bugs/510004
You received this bug notification because you
OK, this is after resume:
xwininfo: Window id: 0x160001e x-nautilus-desktop
Absolute upper-left X: 0
Absolute upper-left Y: 0
Relative upper-left X: 0
Relative upper-left Y: 0
Width: 1280
Height: 800
Depth: 24
Visual: 0x21
Visual Class: TrueColor
Border width: 0
Class:
Well that's unfortunate. It rejects our theory that X wasn't keeping the
window data around and was leaving that up to the graphics card, which
may have dropped the data during the resume.
So this is really getting close to the we can't support nvidia closed
source driver issue, but perhaps Bryce
@Chase Douglas
I disagree.
To me it seems to be the same bug.
It can be triggered by suspend/resume or by switching betreen multiple X
sessions.
--
[lucid regression] random graphics effects after resume from suspend to RAM
https://bugs.launchpad.net/bugs/510004
You received this bug
@andoreasu:
The original issue is: After a suspend/resume of a single X session,
artifacts are seen and switching between VTs fixes some, but not all, of
the issues.
Your issue is: After a suspend/resume with multiple X sessions, one of
the X sessions hangs indefinitely (Christian
I have the same problem, but I think I think the real problem here is not
suspend/resume but VT handling.
using the suggestion to remove add_parameters --quirk-no-chvt works for me --
but only I have have only one user logged in.
If I have more than one user logged in (= more than one X server
@andoreasu:
Your issues are different than those discussed in this bug. I suggest
opening a new bug to deal with the resume failure on multiple X
sessions.
Thanks
--
[lucid regression] random graphics effects after resume from suspend to RAM
https://bugs.launchpad.net/bugs/510004
You received
I get the impression that KDE is more severely affected by this bug than
Gnome: KDE is barely usable after resume, with large portions of the
display more or less permanently blanked out, whereas Gnome can be made
to repaint more of the screen.
--
[lucid regression] random graphics effects after
A screen shot of my KDE desktop a few minutes after I have resumed from
suspend.
** Attachment added: kde-a-while-after-resume.png
http://launchpadlibrarian.net/39141495/kde-a-while-after-resume.png
--
[lucid regression] random graphics effects after resume from suspend to RAM
*** This bug is a duplicate of bug 488720 ***
https://bugs.launchpad.net/bugs/488720
As I tried to explain above, I have applied the patch and I'm still
having the same problems as before. Am I now the only one left with
random graphics after resume?
--
[lucid regression] random graphics
Sorry, unduplicating again then.
** This bug is no longer a duplicate of bug 488720
Suspend/resume with nvidia driver fails
--
[lucid regression] random graphics effects after resume from suspend to RAM
https://bugs.launchpad.net/bugs/510004
You received this bug notification because you are
The fix #448720 worked for me as well.
I have a Dell XPS M1330 with GeForce 8400M GS.
--
[lucid regression] random graphics effects after resume from suspend to RAM
https://bugs.launchpad.net/bugs/510004
You received this bug notification because you are a member of Ubuntu-X,
which is
@Per:
Which driver are you using? nvidia or nv (or vesa)?
Thanks
--
[lucid regression] random graphics effects after resume from suspend to RAM
https://bugs.launchpad.net/bugs/510004
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
@Chase:
nvidia.
--
[lucid regression] random graphics effects after resume from suspend to RAM
https://bugs.launchpad.net/bugs/510004
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in ubuntu.
Christian, it seems that at least the quirks handling seems to work. You
are using the proprietary nvidia driver, which does not need any quirks
(and thus pm-utils disables them, just like hal did). Also, at least the
original reporter's problem
@Per:
There is a current issue with nvidia resume in lucid that is being
tracked in bug 488720. Can you check if the solution noted there fixes
everything for you? If it does, please mark this bug as a duplicate of
it. If not, please describe the behavior that still persists after
attempting the
I take it the solution was to edit /usr/lib/pm-utils/sleep.d/98-video-
quirk-db-handler and remove add_parameters --quirk-no-chvt in the
using_nvidia block. Well I did that, and sorry, I see no difference at
all.
The screen is still garbled and it takes some virtual-terminal switching
until the
After resuming, if I just wait patiently without trying to switch
between virtual consoles, I can see the screen flicker from time to
time. It seems that is only after waiting for some thirty seconds that
the VT-switching trick will work.
--
[lucid regression] random graphics effects after
@Chase: the fix from bug #488720 worked for me, thanks for the hint!
My nvidia card is: GeForce 8500 GT
N.B.: the problem also occurred with the nv-driver.
--
[lucid regression] random graphics effects after resume from suspend to RAM
https://bugs.launchpad.net/bugs/510004
You received this
The fix in bug #488720 worked for me, too.
--
[lucid regression] random graphics effects after resume from suspend to RAM
https://bugs.launchpad.net/bugs/510004
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in ubuntu.
*** This bug is a duplicate of bug 488720 ***
https://bugs.launchpad.net/bugs/488720
** This bug has been marked a duplicate of bug 488720
Suspend/resume with nvidia driver fails
--
[lucid regression] random graphics effects after resume from suspend to RAM
Martin,
thanks for having a look into it.
I've done a suspend as you've suggested, please see the files attached.
Luckily, I can ssh into my computer, so I could get some more data.
After a resume, the X server is using nearly 100% of the cpu (I could
only take a screenshot). I did an strace of
** Attachment added: 2010-02-09-x-server-load.png
http://launchpadlibrarian.net/38933293/2010-02-09-x-server-load.png
--
[lucid regression] random graphics effects after resume from suspend to RAM
https://bugs.launchpad.net/bugs/510004
You received this bug notification because you are a
** Attachment added: x-strace.log
http://launchpadlibrarian.net/38933372/x-strace.log
** Changed in: pm-utils (Ubuntu)
Status: Incomplete = Confirmed
--
[lucid regression] random graphics effects after resume from suspend to RAM
https://bugs.launchpad.net/bugs/510004
You received
As hal is in the process of being deprecated, the suspend quirks were
integrated into pm-utils (see https://wiki.ubuntu.com/Halsectomy). Could there
be something missing or gone wrong with the conversion? It looks to me as if
the system does not use the proper quirks for the hardware when
Christian,
indeed quirks handling was broken in pm-utils until last week. Do you
have 1.3.0~rc3-1? Can you please try again with that one?
If it does not work still, please do
sudo rm /var/log/pm-suspend.log
sudo PM_DEBUG=true pm-suspend
then resume (or reboot if it's broken) and attach
What is the Triage/How to fix it?
--
[lucid regression] random graphics effects after resume from suspend to RAM
https://bugs.launchpad.net/bugs/510004
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in ubuntu.
If a but report is triaged it doesn't mean that there is a fix already
available. It just means to the developers, that the bug is confirmed
and that there is enough information about it, so that someone can pick
the problem up and work on it.
--
[lucid regression] random graphics effects after
Not sure, if this is helpful, but
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/513890 seems to be
similar. All reports about this kind of problem seem to use 2.6.32 +
nvidia. I have tested resume with 2.6.31, but same problem with that.
I noticed, that I can switch to tty1. At first,
** Tags added: regression-potential
--
[lucid regression] random graphics effects after resume from suspend to RAM
https://bugs.launchpad.net/bugs/510004
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in ubuntu.
Switching between the vts works only sometimes, so it is not a reliable
workaround. The graphic was normal after a resume on karmic, even with
version 190 of the nvidia drivers. I've tried the linux kernel 2.6.33
(from the ubuntu kernel archive) on lucid, but it didn't work either.
--
[lucid
apport information
** Tags added: apport-collected
** Description changed:
On this laptop, resume from suspend to RAM barely works under Lucid,
while it works flawlessly under Jaunty.
These are the most salient aberrations:
1) The display comes back in a strange pattern of random
apport information
** Changed in: linux (Ubuntu)
Status: Incomplete = New
** Description changed:
On this laptop, resume from suspend to RAM barely works under Lucid,
while it works flawlessly under Jaunty.
These are the most salient aberrations:
1) The display comes back in a
** Changed in: linux (Ubuntu)
Status: New = Triaged
--
[lucid regression] random graphics effects after resume from suspend to RAM
https://bugs.launchpad.net/bugs/510004
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers
Per,
Would you mind running apport-collect -p linux 510004
to get us the rest of the data.
Thanks,
-JFo
** Changed in: linux (Ubuntu)
Status: New = Incomplete
** Changed in: linux (Ubuntu)
Importance: Undecided = Low
--
[lucid regression] random graphics effects after resume
Anyone could try to remove plymouth and see it works? From bug #510524.
--
[lucid regression] random graphics effects after resume from suspend to RAM
https://bugs.launchpad.net/bugs/510004
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
I just checked: removing plymouth does not make any difference for me.
--
[lucid regression] random graphics effects after resume from suspend to RAM
https://bugs.launchpad.net/bugs/510004
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
No better luck with latest nvidia-current, 190.53-0ubuntu12.
--
[lucid regression] random graphics effects after resume from suspend to RAM
https://bugs.launchpad.net/bugs/510004
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
** Summary changed:
- [lucid regression] strange resume from suspend to RAM
+ [lucid regression] random graphics effects after resume from suspend to RAM
** Description changed:
- Binary package hint: pm-utils
-
On this laptop, resume from suspend to RAM barely works under Lucid,
while it
I doubt that this problem is related to the nvidia driver. I tested a
suspend from the virtual terminal (stopped X and unloaded the nvidia
module) - after resume, the monitor is black with some white rectangles
but switches to standby soon. Switching to a vt with ctrl-alt-f* does
not work.
A good way to create new wallpapers...
** Attachment added: Screenshot-3.png
http://launchpadlibrarian.net/38643878/Screenshot-3.png
--
[lucid regression] random graphics effects after resume from suspend to RAM
https://bugs.launchpad.net/bugs/510004
You received this bug notification
71 matches
Mail list logo
