** Summary changed:
- [fglrx] fglrx + compiz fusion won't resume
+ [fglrx] fglrx + compiz fusion won't resume [EPR#260329]
--
[fglrx] fglrx + compiz fusion won't resume [EPR#260329]
https://bugs.launchpad.net/bugs/197209
You received this bug notification because you are a member of Ubuntu
** Changed in: fglrx
Status: Confirmed = Triaged
** Summary changed:
- [fglrx] fglrx + compiz fusion won't resume [EPR#260329]
+ fglrx + compiz fusion won't resume[AMD Feature#7647] [EPR#260329]
--
fglrx + compiz fusion won't resume[AMD Feature#7647] [EPR#260329]
** Changed in: fglrx
Importance: Undecided = Medium
Status: New = Confirmed
--
[fglrx] fglrx + compiz fusion won't resume
https://bugs.launchpad.net/bugs/197209
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Resume just hang with Jaunty.
1) Suspend ok
2) Resume starts to work, there's the unlocking (username,password) widget on
the screen but no text inside it. Mourse cursor moves for awhile (~1min) but
then it also freezes. Hard-drive light shows some activity. Magic keys
(Alt-SysRd-REISUB) do
** Attachment added: Xorg.0.log
http://launchpadlibrarian.net/19914857/Xorg.0.log
--
[fglrx] fglrx + compiz fusion won't resume
https://bugs.launchpad.net/bugs/197209
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I think the importance should be bumbed up as hanging when resuming may
cause data loss. Especially when resume is half way up.
--
[fglrx] fglrx + compiz fusion won't resume
https://bugs.launchpad.net/bugs/197209
You received this bug notification because you are a member of Ubuntu
Bugs, which
Also attaching Xorg.0.log.old (does ubuntu copy Xorg.0.log to old
automatically now upon reboot? That's nice) because there's some
interesting messages there (see the end);
[mi] EQ overflowing. The server is probably stuck in an infinite loop.
[mi] mieqEnequeue: out-of-order valuator event;
/var/log/messages also contains ASIC hang message:
Nov 24 23:29:00 gandalf kernel: [34547.824138] [fglrx] ASIC hang happened
Nov 24 23:29:00 gandalf kernel: [34547.824159] Pid: 6643, comm: Xorg Tainted: P
2.6.27-8-generic #1
Nov 24 23:29:00 gandalf kernel: [34547.824164]
Nov 24 23:29:00
** Changed in: fglrx-installer (Ubuntu)
Importance: Undecided = Medium
Status: New = Confirmed
--
[fglrx] fglrx + compiz fusion won't resume
https://bugs.launchpad.net/bugs/197209
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug is sufficient to forward upstream now.
** Changed in: fglrx-installer (Ubuntu)
Status: Confirmed = Triaged
** Changed in: linux-restricted-modules-2.6.24 (Ubuntu)
Status: Confirmed = Won't Fix
** Also affects: fglrx
Importance: Undecided
Status: New
--
[fglrx]
** Also affects: fglrx-installer (Ubuntu)
Importance: Undecided
Status: New
--
[fglrx] fglrx + compiz fusion won't resume
https://bugs.launchpad.net/bugs/197209
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
The bug is also in Intrepid
Ok, here is my Xorg.0.log and output of lspci -vvnn.
To reproduce, you need to have Compiz running when suspending. Upon
resume, the screen will stay blank. When Compiz was running but you turn
it off just before resuming (eg fusion-icon) suspend and resume work
fine.
** Attachment added: lspci-vvnn.log
http://launchpadlibrarian.net/19115169/lspci-vvnn.log
--
[fglrx] fglrx + compiz fusion won't resume
https://bugs.launchpad.net/bugs/197209
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
[This is an automated message]
As of Intrepid (8.10), we have a dedicated package 'fglrx-installer' for
fglrx bugs, which now includes a process for upstreaming bugs to AMD.
http://bugs.launchpad.net/ubuntu/+source/fglrx-installer
To transition your bug into the new fglrx-package, we need
Dear Dave,
I put those files where you told me, and had one perfect suspend/resume!
But when I tried again for a few times, the screen remained black. If I
manually start metacity before suspending, all is fine, as expected.
I will do some more testing
It is a shame the Ubuntu-devs don't pick
on Mon Oct 27 2008, Crackh34d bartmacco-AT-hotmail.com wrote:
Dear Dave,
I put those files where you told me, and had one perfect suspend/resume!
But when I tried again for a few times, the screen remained black. If I
manually start metacity before suspending, all is fine, as expected.
I
Dear Dave, I also have a T60p and have used an early version of your
script on Hardy, and it worked fine with fusion-icon.
Today I installed the Intrepid RC, and suspend was working with the open
source Radeon driver, but I get ´bars´ of screen corruption when
resuming. I installed the fglrx
Hello Bart,
with Intrepid I do not need those script anymore. I have a T60 with
fglrx enabled and supend and hibernate works out of the box. No need for
compiz workaround anymore.
Do you upgraded or is this a fresh installation?
Regards,
Thilo
--
[fglrx] fglrx + compiz fusion won't resume
I forgot to chmod the file 00compiz, so I did that. But it doesn't make
any difference, after five attempts I only get a blank screen upon
resume.
Installing fusion-icon didnt change anything either, even if compiz is
launched through it
--
[fglrx] fglrx + compiz fusion won't resume
This is a fresh installation. I tweaked nothing at first, I tried suspending as
soon as I could.
Do you have a T60 with X1400?? I have a T60p with a FireGL V5250 ( Which is
basically a x1600/x1650 I believe)
A friend of mine has exactly the same notebook as me and can't suspend
either with a
It is a T60 with a X1400. The only thing I did was to modify the kernel
parameters. GRUB passes vga=794 acpi_sleep=s3_bios pci=bios to the
kernel. I do not know if this (acpi_sleep=...) is still needed but it
has fixed some of my suspend problems years ago.
--
[fglrx] fglrx + compiz fusion won't
I tried adding those commands to GRUB, but to no avail...
--
[fglrx] fglrx + compiz fusion won't resume
https://bugs.launchpad.net/bugs/197209
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Hi Bart,
on Sun Oct 26 2008, Crackh34d bartmacco-AT-hotmail.com wrote:
Dear Dave, I also have a T60p and have used an early version of your
script on Hardy, and it worked fine with fusion-icon.
Today I installed the Intrepid RC, and suspend was working with the open
source Radeon driver,
on Sun Oct 26 2008, schlehmil mail-AT-schlehmil.org wrote:
It is a T60 with a X1400. The only thing I did was to modify the kernel
parameters. GRUB passes vga=794 acpi_sleep=s3_bios pci=bios to the
kernel. I do not know if this (acpi_sleep=...) is still needed but it
has fixed some of my
Hello Dave,
no it is not. Suspend also fails with X1400 on my T60 or X300 on my old
T43 on Ubuntu Hardy without the scripts you have posted above. With
Intrepid everthing works fine for me. Do not know if this bug has been
fixed in ATI binary driver or in compiz.
Regards,
Thilo
--
[fglrx]
** Tags added: valid-xorg-conf
--
[fglrx] fglrx + compiz fusion won't resume
https://bugs.launchpad.net/bugs/197209
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Thanks to Dave for all his efforts. I'm still struggling with a
'looping' problem on resume. Sometimes on resume I begin to immediately
RE-suspend. Any ideas?
--
[fglrx] fglrx + compiz fusion won't resume
https://bugs.launchpad.net/bugs/197209
You received this bug notification because you
You're welcome, and I'm afraid I don't have any ideas. I suggest
looking for the relevant logs; you can start with
/var/log/pm-suspend.log. Also, there may be a way to control the
verbosity of logging; think /etc/pm/...
--
[fglrx] fglrx + compiz fusion won't resume
** Attachment added: 00-compiz-stop.sh
http://launchpadlibrarian.net/15208399/00-compiz-stop.sh
--
[fglrx] fglrx + compiz fusion won't resume
https://bugs.launchpad.net/bugs/197209
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Update: I have installed fglrx 8-5 which allowed me to remove some of
the chvt hacks that caused flashing. They're still in the enclosed
scripts, but commented out. Please uncomment them if you're using an
earlier version.
I cleaned up some stylistic things in /etc/pm/sleep.d/00compiz (attached
dave:
I missed the fact that removing the os.kill call is a problem when the
parent process is still alive. Is there an easy way to make this call
not throwing an error when the process with that ID is not alive
anymore?
alex:
If your are not using any docking station you can comment out line
schlehmil: you can check for the process first using ps, or use a more
pythonic approach (asking forgiveness is easier than asking
permission):
try:
os.kill(ppid)
except:
pass
it would be better to make that
except SomeExceptionType:
if you can find out which exception is
DaveAbrahams: Sorry if my wording was vague -- suspend/resume absolutely
does not work for me under compiz without your scripts. I just tested
again to be sure.
To summarize and clarify, here were my results with suspend/resume using
fglrx and compiz:
- Default Hardy state (no scripts, no
Hello Dave,
I also tried your suspend/resume fix and also experienced problems with compiz
not being restarted after resume because the parent process died too. I am not
using compiz-fusion btw.
On my installation compiz.real is a child process of /usr/bin/compiz which
actually is a wrapper
schlemil: yes, that is undoubtedly the right approach. Unfortunately I
don't have much time to work on this for the next week, so perhaps you'd
like to take a stab at it?
--
[fglrx] fglrx + compiz fusion won't resume
https://bugs.launchpad.net/bugs/197209
You received this bug notification
Same as jsteinhart, I installed fusion-icon and now compiz and
suspend/resume are working fine, so I guess the resume script can only
restore compiz if it was launched by fusion-icon. Thanks
--
[fglrx] fglrx + compiz fusion won't resume
https://bugs.launchpad.net/bugs/197209
You received this
** Attachment added: 00compiz
http://launchpadlibrarian.net/14561597/00compiz
--
[fglrx] fglrx + compiz fusion won't resume
https://bugs.launchpad.net/bugs/197209
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Ok Dave I finally modified your scripts. If you are not using fusion-
icon the script died before when you resume because the parent process
died already. To fix this my modified script saves the environment of
the parent process before it dies and reloads it after resume. It is my
first attempt
schlemil:
* I like your general approach.
* Using a pickle is a good idea (especially for a python newbie)!
* Might as well stop writing the list of parent IDs into /var/run/pm-suspend,
now, though -- you can always ask the dict for its keys
* Perhaps the pickle ought to be stored under
schlehmil:
Aside from a bit of flickering, your script is working for me without
using fusion-icon. Window decorations are loaded upon resume. Thanks a
lot.
--
[fglrx] fglrx + compiz fusion won't resume
https://bugs.launchpad.net/bugs/197209
You received this bug notification because you are a
I am using your 2008-05-14 scripts. Suspend is working fine, it also
resumes, but without borders. Apparently it fails to re-launch compiz. I
receive a notification in the tray of an error with 00compiz. I attach
my pm log, where I can see an error. Thanks
** Attachment added: pm-suspend-log
I have the same error -- it's the call to psenviron(pid) for a process
that no longer exists, which causes an exception to be thrown.
I changed the script to catch the exception and simply set e to an empty
dictionary to see if that helped. As usual, my blind, ignorant hacking
did not help
lusisto, resuming without borders is a known problem at the moment,
using Dave's scripts. You can install the fusion-icon package which will
allow you to restart compiz easily. To do this, run: sudo aptitude
install fusion-icon in a terminal.
You'll want to make fusion-icon run on startup. To do
I just installed fusion-icon (thanks for the pointer, Alex). I ran it
and added it to session startup apps, and now everything works
flawlessly. fusion-icon (along with DaveAbrahams' PM scripts, of course)
actually fixes all of the problems I'd been having.
pm-suspend.log is now free from errors,
The borders come back for me, but I should have noted that I only tested
my scripts with fusion-icon and thought it would probably work for the
other methods of launching compiz. I guess the script is making some
incorrect assumptions about the other launching processes.
jsteinhart: if you are
Here's what I've got currently. Aside from some annoying screen
flashing, everything seems to be working. I had to rewrite it in Python
because my bash-fu is just not strong enough to deal with all the
whitespace/quoting issues. Nobody should be forced to program bash
anyway ;-). I'll attach
** Attachment added: 00-compiz-stop.sh
http://launchpadlibrarian.net/14513703/00-compiz-stop.sh
--
[fglrx] fglrx + compiz fusion won't resume
https://bugs.launchpad.net/bugs/197209
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
There hasn't been any progress in the past few days; I thought I'd just
inquire about any updates anyone may have. Dave, how is that script
coming along? I've had very good luck suspending and resuming with your
script and reloading compiz with fusion-icon.
--
[fglrx] fglrx + compiz fusion won't
Dave:
Still using 25-compiz-stop.sh. This is extremely strange, but when I
suspend for periods of less than 1.5 hours or so, resume works perfectly
every time. If it's any longer than that, I get the 100% CPU bug, every
time. The past three nights I have suspended and in the morning upon
resume I
Dave:
I've used your scripts from the gmane.org (and have chmodded both +x). I
have also added the set -x and set +x as instructed, and can
successfully resume for short periods (without window borders upon
resume). Running Reload Window Manager from compiz-icon reloads compiz
correctly.
I have
Alex,
That's very odd; it appears that by the time 00-compiz-stop.sh gets to
run, there are no processes named 'compiz.real' that were spawned by
other processes (e.g. compiz-icon). When you get back to a normal state
it would be instructive to see the result of 'ps faux' on your system.
Before
The scripts have worked pretty well for me a few times now. I do notice
that the load (not CPU) starts VERY high but does drop over time and
doesn't seem to cause any major issues. What I have noticed is that the
cube feature of compiz seems to disappear in favor of a 2 paned wall.
Any ideas?
Resuming worked fine using the gmane.org scripts after several hours of
suspending. I will post here tomorrow morning after 8 hours of
suspending (while I'm sleeping) and let you know what happens.
Attached is the output of ps faux | tee -a ~/ps_faux after resuming
from today's suspend I
I am quite the noob, but I was able to use DaveAbrahams' hack listed in
the url above to successfully resume!
First, I did the chmod command given by Alex above, and then used that
second command to copy the two files (after I renamed them once
downloaded) to the two different folders as
I too had 1 success of 1 so far with the scripts on the gmane.org page!
I wasn't about to call it a success yet, but feel much more confident.
I used Dave's Compiz Fusion Icon trick to reload the windows manager.
It might be easier than dropping into VT and typing it by hand...
Mike
PS - Thanks
Rob: the missing window borders are expected unless you are using the
partial solution at http://news.gmane.org/find-
root.php?message_id=%3c87y76n7w19.fsf%40mcbain.luannocracy.com%3e. In
particular, /etc/pm/sleep.d/00compiz is responsible for re-launching the
compiz process. If, even with that
Mike,
* The docking station issue is real
(https://bugs.launchpad.net/ubuntu/+bug/218760).
* I see the same stuck for 11s message. If you google for it you'll
see that many others do, too. For me it seems to be benign when all my
suspend/resume workarounds are in place. Some people think
I'd really love to get something working but am struggling greatly.
My suspend procedure goes into text mode before powering down.
Upon resume, I see a flashing cursor in the upper right. Sometimes that
stays there, sometimes it goes black. Sometimes I can ctrl+alt+F2 back
to a text login
Mike Phillips:
I suggest you make some changes in your /etc/default/acpi-support file.
gksudo gedit /etc/default/acpi-support
Change SAVE_VBE_STATE=true to SAVE_VBE_STATE=false
Change POST_VIDEO=true to POST_VIDEO=false
Reboot and you may have better luck.
--
[fglrx] fglrx + compiz fusion
Alex: I'm surprised that 25-compiz-stop.sh is actually working for you.
It doesn't work for me in its current form. If it's working for you, it
would be a good thing to log everything it is doing so we can see what's
going on.
I think the problem with fusion-icon may be that it tries to restart
I do usually doc my T60p into a port replicator but not always. I had
some success 2 times in a row! But then I saw a bug that CPU0 is stuck
for 11s. I also noticed the load was unusually high but processor use
was ok. I tried a manual powernod stop before suspend and no good
either.
I'm
Dave, thanks so much for the script. As of this AM, I tried a suspend
(worked fine) but resume did not...
Mike
--
[fglrx] fglrx + compiz fusion won't resume
https://bugs.launchpad.net/bugs/197209
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
It turns out that you can do this even a bit more simply. My current
script looks like this:
CHVT=`which chvt`
chvt() {
killall -s 15 compiz.real
while pgrep compiz.real; do sleep 0.1; done
$CHVT $1
unset -f chvt
}
I happen to be running fusion-icon, so when the machine resumes
Dave,
I registered just to message you. I've also got a T61 with a FireGL5200, and
the suspend/restore bug in compiz is what forced me to abandon my last bout
with linux. Does your patch fix our problem? On behalf of all other lurkers on
the 'net, thank you so much for putting your time into
Dave:
The script you attached on 2008-05-01 (25-compiz-stop.sh) seems to have
fixed the problem. I have suspended and resumed greater than 15 times
without a hiccup. Interestingly enough, fusion-icon seemed to cause
problems, so I simply removed it and now things seem to be working
perfectly. I
Curious to see if this works, as I'm stuck the same way on my T60p (ATI
5250) too. Is this a bit of a hack using metacity? I'd rather fix the
issue than do an end around.
Mike
--
[fglrx] fglrx + compiz fusion won't resume
https://bugs.launchpad.net/bugs/197209
You received this bug
DaveAbrahams: Any progress on that real version?
--
[fglrx] fglrx + compiz fusion won't resume
https://bugs.launchpad.net/bugs/197209
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
@Alex Strabala: Thanks for asking. Sorry, I've just been busy. I have
all the necessary elements but it will be at least a few more days
before I can put them together.
--
[fglrx] fglrx + compiz fusion won't resume
https://bugs.launchpad.net/bugs/197209
You received this bug notification
@Mike Phillips: It's all hacks, since we're working around a bug. The
alternative hack is to kill compiz directly and then re-start it in
whichever way it was launched. I wasn't sure how well the windows would
be restored in that case, so I felt more comfortable replacing it with
another window
I could in theory get some traction by placing a script in
/etc/pm/sleep.d, but I've tried that -- it appears to get called too
late... I'm unable to effectively replace compiz with metacity :(
--
[fglrx] fglrx + compiz fusion won't resume
https://bugs.launchpad.net/bugs/197209
You received this
The actual bug is an interaction with chvt, which is the first thing pm-
utils does. One has to get in before chvt and invoke metacity. One way
to do that is something like this file, which would go in
/etc/pm/config.d/00-compiz-stop
# override the real chvt to stop compiz before doing anything
After resume with compiz, when I ssh into my T60p running the 32-bit
kernel with a FireGL v5200, I also get the 100% cpu problem.
When I wrote I have various partially-working scripts for suspend.d/resume.d
to address this I meant to write that I have *found* such scripts on the web.
See
I should add that this is almost certainly a hardware-related issue. My
Dell Inspiron 9300 with ATI Mobility Radeon x300 suspends and resumes
just fine with fglrx and compiz.
--
[fglrx] fglrx + compiz fusion won't resume
https://bugs.launchpad.net/bugs/197209
You received this bug notification
My inability to work around this bug appears to be due to
https://bugs.launchpad.net/ubuntu/+source/gnome-power-
manager/+bug/220383
Sheesh.
--
[fglrx] fglrx + compiz fusion won't resume
https://bugs.launchpad.net/bugs/197209
You received this bug notification because you are a member of Ubuntu
I am also running a T60p with a 5250 and have very similar symptoms as
Niklas Hofer.
Running 64bit kernel. With compiz enabled, suspend works fine, but upon
resume i get a blank screen. Can recover by resetting X with CTRL+PrtSc
.
After I disabled compiz without a restart, I could resume fine
Has someone filed a bug for the 100% CPU problem? It's awful! It's the
only thing keeping me from using compiz fusion on hardy!
--
[fglrx] fglrx + compiz fusion won't resume
https://bugs.launchpad.net/bugs/197209
You received this bug notification because you are a member of Ubuntu
Bugs, which
I have a T60p with Mobility FireGL V5250, running fglrx 8.4 (some
problem with distro 8.3) on a 32bit Hardy, distupgraded form gutsy. I
can confirm this bug.
Without compiz (running 'metacity --replace' before suspending), supend (and
resume) works (tried 3 times in a row).
With compiz, the
I am on x86_32:
$ uname -a
Linux mcbain 2.6.24-16-generic #1 SMP Thu Apr 10 13:23:42 UTC 2008 i686
GNU/Linux
I'll give the backtracing approach a try, but my machine is so close to
Niklas' that I'm not optimistic we'll get new information.
--
[fglrx] fglrx + compiz fusion won't resume
Actually it's worse than that. The Backtracing instructions start out
by giving me ambiguous answers (pgrep Xorg yields two PIDs, neither of
which is Xorg, but instead X) and end by giving me no useful
information. gdb says that the process is not being run even though
top says that it is taking
** Attachment added: gdb-2.log
http://launchpadlibrarian.net/13583481/gdb-2.log
--
[fglrx] fglrx + compiz fusion won't resume
https://bugs.launchpad.net/bugs/197209
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I have the mobility radeon X1400, and suspend and resume work always.
The only problem I have is sometimes there will be 100% (and I mean
100%) CPU usage on resume, but only when compiz is enabled. Another
interesting point is that this only seems to happen when I suspend for
long periods of time
@Alex, from your description you seem to be having a different problem
than the original reporter; please file it as a separate bug report.
@DaveAbrahams, are you also running the 64 bit version? (Check uname
-a). Also, your files didn't show a backtrace or error message - please
install dbg
Yes, I can confirm it! Actually I thought suspend was hopeless until I
ssh'd into the resumed machine with the black screen and I noticed this
line at the end of Xorg.0.log:
(II) AIGLX: Suspending AIGLX clients for VT switch
Then I did /etc/init.d/gdm stop and killed Xorg and related processes,
** Attachment added: Oops, I meant this one seems to end with a failure
http://launchpadlibrarian.net/13545773/Xorg.0.log.old
--
[fglrx] fglrx + compiz fusion won't resume
https://bugs.launchpad.net/bugs/197209
You received this bug notification because you are a member of Ubuntu
Bugs,
** Attachment added: xorg.conf
http://launchpadlibrarian.net/13545792/xorg.conf
** Changed in: linux-restricted-modules-2.6.24 (Ubuntu)
Status: Incomplete = Confirmed
--
[fglrx] fglrx + compiz fusion won't resume
https://bugs.launchpad.net/bugs/197209
You received this bug
I have various partially-working scripts for suspend.d/resume.d to
address this, and will attach my working versions in the morning when I
can think straight.
--
[fglrx] fglrx + compiz fusion won't resume
https://bugs.launchpad.net/bugs/197209
You received this bug notification because you are a
Can anyone else reproduce this issue? If not within a couple months I
guess we can close it as invalid.
--
[fglrx] fglrx + compiz fusion won't resume
https://bugs.launchpad.net/bugs/197209
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Sorry, due to this and other problems I switched to the i386 edition a
couple of weeks ago which works fine with fglrx and suspend. I don't
have the 64bit edition installed anyway to test this anymore.
--
[fglrx] fglrx + compiz fusion won't resume
https://bugs.launchpad.net/bugs/197209
You
** Summary changed:
- fglrx + compiz fusion won't resume
+ [fglrx] fglrx + compiz fusion won't resume
--
[fglrx] fglrx + compiz fusion won't resume
https://bugs.launchpad.net/bugs/197209
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
89 matches
Mail list logo
