** Changed in: xserver-xorg-video-intel (Ubuntu)
Assignee: Bryce Harrington (bryceharrington) => Rasyid (cid79-m)
** Changed in: xserver-xorg-video-intel (Ubuntu)
Assignee: Rasyid (cid79-m) => (unassigned)
--
very corrupt X after suspend/resume
https://bugs.launchpad.net/bugs/133118
Yo
With two positive feedbacks I consider this verified, thank you! Copied
to gutsy-updates.
** Tags added: verification-done
** Tags removed: verification-needed
** Changed in: xserver-xorg-video-intel (Ubuntu Gutsy)
Status: Fix Committed => Fix Released
--
very corrupt X after suspend/re
I've been running this (and other) patches to the intel driver since
gutsy was released, on 945GM hardware. I've not seen any bugs which I'd
attribute to this change.
The patch was applied upstream too:
http://gitweb.freedesktop.org/?p=xorg/driver/xf86-video-
intel.git;a=commit;h=b8770f710729d616
If you have evidence that this doesn't regress on other hardware and
fixes this bug, then we can move this to -updates. Jimmy's response
seems to suggest that it works for him. Can you also test this yourself
on your hardware, or know someone else who has?
--
very corrupt X after suspend/resume
h
Thank you Martin! the simple update fixed my troubles!
--
very corrupt X after suspend/resume
https://bugs.launchpad.net/bugs/133118
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubu
Martin, can this be marked as Fix Released?
--
very corrupt X after suspend/resume
https://bugs.launchpad.net/bugs/133118
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
htt
Jimmy,
if by "Peter's patch" you mean the solution to this bug (broken
graphical display after suspend to RAM), then please enable System ->
Administration -> Software sources -> Updates -> gutsy-proposed, update
your system, and tell us here whether the problem was fixed for you.
--
very corrup
hey guys,
i'm very new to the linux OS, but joined because i heard Ubuntu was
relatively user-friendly. i thought i was adequate with computers until
i ran into alot of little snags with ubuntu 7.10 on my dell 700m laptop.
i also have the shutdown problem and in my search, found this thread and
th
I can hibernate and wake back up on a Toshiba Libretto U105, with Gutsy
proposed updates enabled and installed. I turned Compiz back on and
tried, and the first experience is moderately positive. There was still
a bit of an artefact when I turned the machine back on but it was
quickly covered by
** Tags added: hw-specific
** Tags removed: hwspecific
--
very corrupt X after suspend/resume
https://bugs.launchpad.net/bugs/133118
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ub
** Tags added: hwspecific
--
very corrupt X after suspend/resume
https://bugs.launchpad.net/bugs/133118
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.
I'm moderately sure I was running the gutsy-proposed version, but I
can't easily be sure because I have now upgraded the affected machine to
Hardy, sorry!
--
very corrupt X after suspend/resume
https://bugs.launchpad.net/bugs/133118
You received this bug notification because you are a member of U
Chris Jones, anyone else with that hardware, can you please test the
package in gutsy-proposed and give feedback here? Thank you!
** Tags added: verification-needed
--
very corrupt X after suspend/resume
https://bugs.launchpad.net/bugs/133118
You received this bug notification because you are a
Sponsored and accepted into gutsy-proposed, please test.
** Changed in: xserver-xorg-video-intel (Ubuntu Gutsy)
Status: In Progress => Fix Committed
--
very corrupt X after suspend/resume
https://bugs.launchpad.net/bugs/133118
You received this bug notification because you are a member of
I don't know what exactly is going on, but this problem returned as of
today (I'm not aware of any package upgrades so I am baffled to say the
least). Is anyone else seeing this?
Regards,
K.
--
very corrupt X after suspend/resume
https://bugs.launchpad.net/bugs/133118
You received this bug notif
I am just adding this comment for the reference.
I had the same problem with Thinkpad X40. I have filed another bug
report (#164456), because I failed to find this thread first.
Downloading the package from http://www2.eng.cam.ac.uk/~pcjc2/ubuntu/
solved the problem. My thinkpad is now waking u
Ack'ed this patch for SRU.
** Changed in: xserver-xorg-video-intel (Ubuntu Gutsy)
Assignee: (unassigned) => Bryce Harrington (bryceharrington)
Status: New => In Progress
--
very corrupt X after suspend/resume
https://bugs.launchpad.net/bugs/133118
You received this bug notification b
Fixed in hardy. Please do not reopen hardy tasks for already fixed bugs.
Use release tasks for this.
** Changed in: compiz (Ubuntu Gutsy)
Status: New => Invalid
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Fix Committed => Fix Released
--
very corrupt X after suspend/r
Subscribing ubuntu-sru, for Gutsy.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Fix Released => Fix Committed
--
very corrupt X after suspend/resume
https://bugs.launchpad.net/bugs/133118
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
** Changed in: xserver-xorg-video-intel (Debian)
Status: New => Fix Released
--
very corrupt X after suspend/resume
https://bugs.launchpad.net/bugs/133118
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs maili
** Description changed:
Binary package hint: xserver-xorg-video-intel
I am running an updated gutsy install on a Thinkpad X40 (so i855GM graphics)
with the -intel driver. I enabled Desktop Effects last night and the two times
I have done a suspend/resume cycle since then, on resuming, is
** Description changed:
Binary package hint: xserver-xorg-video-intel
I am running an updated gutsy install on a Thinkpad X40 (so i855GM graphics)
with the -intel driver. I enabled Desktop Effects last night and the two times
I have done a suspend/resume cycle since then, on resuming, is
For the record, here is peter's patch:
Index: xserver-xorg-video-intel-2.1.1/src/i830_driver.c
===
--- xserver-xorg-video-intel-2.1.1.orig/src/i830_driver.c 2007-10-21 22:08
:58.0 +0100
+++ xserver-xorg-video-intel-2.1.1/
Super, thanks Chris..
I've seen that backtrace before, my notes remind me that I got it
myself, resuming from suspend, so its not an 855 specific issue. I'm
collecting Xorg bactraces here, and will try to go over them and figure
out which bugs they correspond to when I've got some free time. (I've
Attached is a complete X log that includes some successful
suspend/resumes and ends with a resume that segfaults the X server.
** Attachment added: "Xorg.0.log.old"
http://launchpadlibrarian.net/10297070/Xorg.0.log.old
--
very corrupt X after suspend/resume
https://bugs.launchpad.net/bugs/133
@Chris Jones - yes I've seen this happen a couple of times. I wasn't
aware that X was crashing. Next time it happens I'll grab the log too.
--
very corrupt X after suspend/resume
https://bugs.launchpad.net/bugs/133118
You received this bug notification because you are a member of Ubuntu
Bugs, w
Is anyone else seeing occasional segfaults of X on resume with this
driver? (the symptom would be that when you resume you get a login
screen rather than a screensaver dialog)
I've lost the log, but the next time it happens I will be sure to grab
it.
--
very corrupt X after suspend/resume
https:
So, what are the odds we'd get a backport of this for Gutsy?
--
very corrupt X after suspend/resume
https://bugs.launchpad.net/bugs/133118
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lis
xserver-xorg-video-intel (2:2.1.1-0ubuntu10) hardy; urgency=low
[ Bryce Harrington ]
[Peter Clifton]
* 08_fix_855_3D_state.diff
- Emit the invariant 3D state to the GPU during EnterVT after
marking the 3D state as clobbered. This fixes / works around
textured surface corrupti
dmontalvao, sounds like your experiencing a different bug. There are
various open bugs, but I'm not sure which fits the issue you're seeing.
Can you file a separate bug for that problem (or identify any of the
existing ones which match your symptoms)?
--
very corrupt X after suspend/resume
https:
Peter's test package (10-21) didn't solve my problem... :(
I can actually suspend, introduce the password to unlock the session,
but it freezes after that and I have to hard boot.
I didn't try to hibernate.
Ty anyway!
--
very corrupt X after suspend/resume
https://bugs.launchpad.net/bugs/13311
Khashayar,
One more thought and than I quit giving mayby useless information... I
stated:
anyhow I had already tried Peter Clifton's driver and another from a few
days earlier. It all didn't make any difference due to my xorg.conf
being on i810.. Sorry I didn't know,
This is not exactly true. ev
Khashayar,
Thank you very much It works way better now, but don't know too well what
the hack is happening
As you told me I looked at /etc/X11/xorg.conf and the line there was Driver
"i810" already... So since I did the upgrade to gutsy via the update menu is
must have been like this as I
Hey Anco,
If you want to try to switch back to i810 temporarily, the only thing you need
to do is to edit /etc/X11/xorg.conf (open a terminal and enter "gksu gedit
/etc/X11/xorg.conf"). Then look for the line that reads
Driver "intel"
It's under the "device" section. Change it t
I just tried the this latest driver too on my toshiba R15-S829
82852/855GM
For me no luck at all even closing my laptop lid often gives a full
crash, Dark, after hitting Fn-F5 to change output one centimeter
garbidge in the top off the screen, rest of the screen last picture
before closing the lid
This works excellently for me, too! Thanks very much, Peter!
--
very corrupt X after suspend/resume
https://bugs.launchpad.net/bugs/133118
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lis
Thank you Peter! Your driver fixes my suspend/resume problems. Yay!
--
very corrupt X after suspend/resume
https://bugs.launchpad.net/bugs/133118
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b
So am I correct in assuming that for me, with Toshiba Libretto U105,
intel driver (lspci sez 82852/855GM), I should be able to turn Compiz
back on when/if xserver-xorg-video-intel is upgraded, without breaking
suspend/hibernate (assuming this goes in)?
--
very corrupt X after suspend/resume
https
Peter's driver allows me to suspend and resume correctly also. Intel
Corporation 82852/855GM Integrated Graphics Device (rev 02) on HP
nx5000.
--
very corrupt X after suspend/resume
https://bugs.launchpad.net/bugs/133118
You received this bug notification because you are a member of Ubuntu
Bugs
Fantastic!! I don't know what patches have gone in, but suspend/resume
now works flawlessly (well, I've only tried one cycle so far and that
worked just fine)! Thanks a lot to everyone involved! I'm indebted :-)
--
very corrupt X after suspend/resume
https://bugs.launchpad.net/bugs/133118
You rec
Setting compiz to invalid since this is an X driver bug
** Changed in: compiz (Ubuntu)
Status: New => Invalid
--
very corrupt X after suspend/resume
https://bugs.launchpad.net/bugs/133118
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
Peter's latest test package solves this bug for me.
--
very corrupt X after suspend/resume
https://bugs.launchpad.net/bugs/133118
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu
It worked beautifully for me. Both suspend to RAM and hibernate work
correctly now.
--
very corrupt X after suspend/resume
https://bugs.launchpad.net/bugs/133118
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mail
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Triaged => In Progress
--
very corrupt X after suspend/resume
https://bugs.launchpad.net/bugs/133118
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs ma
Dear all,
For your testing enjoyment:
http://www2.eng.cam.ac.uk/~pcjc2/ubuntu/xserver-xorg-video-intel_2.1.1-0ubuntu10~pcjc2.2_i386.deb
This encorporates all other unreleased fixes I've been working on, and
an additional line which aims to reset the 3D state of the card after VT
switch. This may
Thanks for the new package, Peter. Unfortunately, I still have the same
behaviour. However, I'm not getting this in the logs anymore:
(EE) intel(0): I830 Vblank Pipe Setup Failed 0
--
very corrupt X after suspend/resume
https://bugs.launchpad.net/bugs/133118
You received this bug notification be
http://www2.eng.cam.ac.uk/~pcjc2/ubuntu/xserver-xorg-video-
intel_2.1.1-0ubuntu10~pcjc2_i386.deb
Is my latest attempt to avoid the various crash on VT switch bugs being
seen with the 855 hardware, but doesn't address the possible causes for
this bug directly.
--
very corrupt X after suspend/resu
I just tried both of them as well. The first one (0ubuntu8~bwh1) causes
a lockup before the computer has entered sleep mode. It looks as if the
crash is caused by the VT switching but I'm not sure.
The second package results in the original behaviour: A seemingly
working cursor against a black sc
Bryce: I just tested both of those packages and neither appears to fix
this bug.
For kicks, I also tried the X :1 trick and after killing the second X
server my laptop hung ;)
--
very corrupt X after suspend/resume
https://bugs.launchpad.net/bugs/133118
You received this bug notification because
climatewarrior, thanks for pointing that out, however it looks like just
a workaround, not a true fix.
Khashayar Naderehvandi, that could be a fix; that actually came out of
work we have been doing for bug 127101. After mentioning it upstream,
Jesse came up with that patch. You can test Jesse's
I'm seeing a similar problem on my laptop (i885GM) -- after resume,
textures are all black. I discovered that if I start a second X session
and close out of it again, textures work again. I even confirmed that
immediately after resuming, if a second X session is started and
stopped, resuming the
Bryce, could this be the solution:
http://gitweb.freedesktop.org/?p=xorg/driver/xf86-video-
intel.git;a=commit;h=c94cdfd6ddbc580523737f596e97b96a7ce100b9?
--
very corrupt X after suspend/resume
https://bugs.launchpad.net/bugs/133118
You received this bug notification because you are a member of U
Never mind. I just fixed it with this.
http://ubuntuforums.org/showthread.php?t=350265
--
very corrupt X after suspend/resume
https://bugs.launchpad.net/bugs/133118
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs m
I have the same exact video card on a Dell Latitude X300 laptop. Suspend
and hibernate worked perfectly on Feisty but now I upgraded to Gutsy
Release candidate and suspend doesnt work at all. I hace compiz fusion
enabled and it works perfectly. I also had it in Feisty and suspend
worked with that t
** Changed in: xserver-xorg-video-intel (Debian)
Status: Unknown => New
--
very corrupt X after suspend/resume
https://bugs.launchpad.net/bugs/133118
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing li
** Bug watch added: Debian Bug tracker #424952
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=424952
** Also affects: xserver-xorg-video-intel (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=424952
Importance: Unknown
Status: Unknown
--
very corrupt X after suspen
In general I don't think it should matter, however I am a little
concerned our drm might be dated. But in any case, I'm hopeful that if
we have to postpone it to Hardy, that between upgrading our mesa, drm,
and xserver, if there are any version mismatches, they'll be squared
away at that point.
-
I was just browsing the Xorg list archives looking for the thread bryce
mentioned when I noticed this:
http://lists.freedesktop.org/archives/xorg/2007-October/028963.html
Could it be because we're mixing and matching different bits of X
releases?
--
very corrupt X after suspend/resume
https://b
the new deb didn't work for me. I guess this needs to pass on to
hardy...
--
very corrupt X after suspend/resume
https://bugs.launchpad.net/bugs/133118
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ub
Here's a deb of the patch on fdo 11432, if anyone would like to test it:
http://people.ubuntu.com/~bryce/Testing/intel/xserver-xorg-video-
intel_2.1.1-0ubuntu3~bwh1_i386.deb
Others have confirmed that DRI is busted with this git head driver, so I
suspect it's not worth further testing work. Howe
Personally, I suspend/resume multiple times a day, so either version of the
driver is going to leave me with largely unusable 3D. I guess it would be more
useful to have the old driver and know that I can at least restart the server
if I want to run google earth or whatever.
If we can't fix it t
I say rather acceleration than not. I mean, I might not have the same problem
as others here, but even without the fix, suspend/resume works (sometimes) if
compiz is not running. Then all one needs to do to get acceleration back on is
to restart the server.
Please don't add this fix.
Also, has
Hmm... well do you guys feel that slow rendering is an improvement over
corruption, or should we hold off until a proper fix is available?
I'm assuming the corruption went away because the rendering got
clobbered, but I'll browse through the changelog to see what exactly
caused the change.
--
v
with the git deb I have no accelerated rendering, so resume seems to
work. But that's not a surprise, I guess, since there's no aiglx to
start with. Attached log...
** Attachment added: "log of intel driver from git"
http://launchpadlibrarian.net/9807883/Xorg.0.log
--
very corrupt X after sus
I powered down, booted up, suspended, resumed, ran a GL app or two.
Attached is the Xorg log.
** Attachment added: "Xorg.0.log"
http://launchpadlibrarian.net/9802181/Xorg.0.log
--
very corrupt X after suspend/resume
https://bugs.launchpad.net/bugs/133118
You received this bug notification bec
err, obviously I forgot to attach any kind of errors:
-([EMAIL PROTECTED])-(~)- glxgears
libGL error: drmMap of framebuffer failed (Invalid argument)
libGL error: reverting to (slow) indirect rendering
--
very corrupt X after suspend/resume
https://bugs.launchpad.net/bugs/133118
You received thi
Thanks very much Bryce.
Interestingly, GL textures are no longer corrupted on resume, but
rendering is falling back to indirect so is rather slow.
--
very corrupt X after suspend/resume
https://bugs.launchpad.net/bugs/133118
You received this bug notification because you are a member of Ubuntu
B
On the off chance that this issue is fixed already upstream, I've
packaged up the current git HEAD of the -intel driver:
http://people.ubuntu.com/~bryce/Testing/intel/
Would someone mind giving this .deb a spin? If this addresses the
issue, we could try to identify which change fixed it and back
Bryce, I did try with "Modules" first and Xorg refused to accept my
config file. I changed it to "Module" per xorg.conf's manpage.
--
very corrupt X after suspend/resume
https://bugs.launchpad.net/bugs/133118
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
Bryce, thanks for the fix on xserver-xorg-core. With that patch I no
longer have problems going into suspend (as expected), but I'm still
having problems waking up. So, I guess there were two different problems
after all.
--
very corrupt X after suspend/resume
https://bugs.launchpad.net/bugs/1331
Chris, note it's "Modules" not "Module" - this might explain why you're
still seeing the message?
I doubt it fixes it, but I've uploaded a new xserver today that fixes an
error in mesa that causes it to inappropriately free too many visuals
when switching video modes. I'd be a little surprised if
Hi again,
I am really sorry to be spamming this bugreport. I' m just commenting to say
say that I was probably mistaken in my last comment. Right now I'm using the
old i810 driver and suspend + resume works just fine with compiz running. The
failure I referred to before must have been due to som
By the way, I don't think this is a problem with the actual intel driver
(if, indeed, I have the same problem as the original reporter). I tried
to suspend and resume using the old i810-driver to narrow down the
problem, and it failed also. In ubuntu versions prior to gutsy I've
always been able to
I think I'm seeing the same bug on a lifebook p7010 (although it behaves
somewhat differently). After suspend I get black screen with the cursor.
The cursor can be moved around, but nothing else works (can't click
things in the dark, ctrl-alt-backspace doesn't work, etc.). The only
thing that I can
(fwiw, I didn't trim down the config specifically for this - that *is*
my X config ;)
I tried with:
Section "Module"
Disable "sil164"
EndSection
and it didn't make a difference, but interestingly it still printed out
the "detecting sil164" messages you quoted from the logs.
I'll try and ins
** Changed in: xserver-xorg-video-intel (Ubuntu)
Target: ubuntu-7.10-beta => ubuntu-7.10-rc
--
very corrupt X after suspend/resume
https://bugs.launchpad.net/bugs/133118
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ub
Thanks for trimming the xorg.conf down so much. There's a number of
errors and warnings in your log file, although none that look like
they'd cause the problem you're seeing. This one looks unusual; I've
not see this before:
(II) Module sil164: vendor="X.Org Foundation"
compiled for 1.3.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Incomplete => Triaged
--
very corrupt X after suspend/resume
https://bugs.launchpad.net/bugs/133118
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mai
Photo of corrupted display.
Interestingly, this is actually a little different to what I've seen
previously - this is more solid areas of colour where before it would
have been more akin to static noise.
Hopefully you can see that this is me browsing the Places menu (with
tooltip), with a couple
Xorg.0.log (I did a reboot, logged in, started compiz, suspended,
resumed, took a photo, killed compiz and ran metacity, then copied the
logfile)
** Attachment added: "Xorg log"
http://launchpadlibrarian.net/9478811/Xorg.0.log
--
very corrupt X after suspend/resume
https://bugs.launchpad.net/
xorg.conf (this one is quite minimal, basically I tried to rip out
everything that I could, but I don't think it should be related, since
Soren sees this too).
** Attachment added: "xorg.conf"
http://launchpadlibrarian.net/9478831/xorg.conf
--
very corrupt X after suspend/resume
https://bugs.
Can you attach your /var/log/Xorg.0.log from after the corruption has
occurred, and your /etc/X11/xorg.conf? Also, if it would be possible,
please attach a photo or screenshot of the screen that displays the
corruption.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Assignee: (unassigned)
** Changed in: xserver-xorg-video-intel (Ubuntu)
Importance: Undecided => High
Target: None => ubuntu-7.10-beta
--
very corrupt X after suspend/resume
https://bugs.launchpad.net/bugs/133118
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug cont
Bryce: the description I set originally is probably quite misleading.
It's not X that's corrupted, it's just 3D textures (ie every window in
compiz, or any textured surface in a GL application with/without compiz
running).
I will grab all of the tribes tomorrow and start going backwards to find
on
Has this been always happening with all tribes, or can you narrow it to
one tribe where it worked, and another where it stopped?
Fwiw, there are a lot of suspend/resume laptop issues, although I think
this is the first I've read where it comes back with corrupted X.
Usually it doesn't come back at
the corruption certainly will go away if compiz dies and metacity is resumed,
because at that point the windows are rendered onscreen and aren't using 3D
textures.
It's purely 3D textures that are corrupted (to confirm this, switch back to
metacity, suspend, resume and run some 3d application, s
I saw this as well using Compize Fusion, but when I disabled "Sync to
VBlank" in CompizConfig Settings Manager -> Display Settings, the visual
noise went away after about five seconds after coming out of suspend,
but usually taking down Compiz in the process. Running Metacity, I've
had no problems.
** Description changed:
- Binary package hint: compiz
+ Binary package hint: xserver-xorg-video-intel
- I am not sure if this is a compiz bug or an Xorg bug.
-
- I am running an updated gutsy install on a Thinkpad X40 (so i855GM graphics)
with the -intel driver. I enabled Desktop Effects last
I just want to note I *do* in fact also see this :)
--
very corrupt X after suspend/resume
https://bugs.launchpad.net/bugs/133118
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu
I see this, as does Soren Hansen at least.
It is not a compiz bug because it affects all 3D textures. Running xscreensaver
hacks with textures shows similar problems.
To re-state - after resuming from suspend, every 3D texture is replaced
with the wrong memory. I can see patterns in it, but it's
** Changed in: compiz (Ubuntu)
Status: New => Confirmed
--
very corrupt X after suspend/resume
https://bugs.launchpad.net/bugs/133118
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@l
I have zero third repositories enabled and the gutsy install is up to
date.
-([EMAIL PROTECTED])-(~)- dpkg -l | grep compiz
ii compiz1:0.5.2-0ubuntu3
ii compiz-core 1:0.5.2-0ubuntu3
ii compiz-fusion-plugins-extra 0.
What version of Compiz are you running, and from what repository?
Thanks,
Justin M. Wray
--
very corrupt X after suspend/resume
https://bugs.launchpad.net/bugs/133118
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
relevant output of lspci -vvnn:
00:02.0 VGA compatible controller [0300]: Intel Corporation 82852/855GM
Integrated Graphics Device [8086:3582] (rev 02) (prog-if 00 [VGA])
Subsystem: IBM Unknown device [1014:0557]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
94 matches
Mail list logo
