I've actually stopped using compiz (because of this bug and othera), but
after reading Sam's blog about the very recent improvements (like fixing
window moving, performance improvements) i decided to try the latest
code (rev3530 lp:compiz). this bug still persists and through a
conversation in the
@Alistair
You are experiencing a different bug than the one in this report - if
you are not able to reliably reproduce the bug using the same steps that
everyone else has ( including myself! and i can reproduce it every time!
).
You should be opening a bug report of your own, since clearly all
@Alistair. Fine
it is a different bug (that i can reproduce EVERY single time, following
the EXACT same instructions in this bug report - and the bug appears to
be the exact same, with the exception of the blank windows appearing
black - although they used to appear white (for the longest
@alistair
I'd like to point out something that i have noticed in the last few
days, that contradicts a previous statement of yours;
It's not true to say this is entirely an nvidia bug. After all, this
bug is a regression. It does not happen with any other compositing
window manager, and it does
@Jan
that is a very long-winded comment. You could have probably not
mentioned half of that stuff and more accurately gotten to your point.
On the issue of black-windows - it IS the exact same bug - *not a
different one*. On some people's machines it used to appear white (like
at the time of
@Alistair
development at compiz.org died quite a while ago... I don't think anyone
is building the 0.9.x series from git at this point (and if i remember
correctly, compiz 0.9.x is somewhat broken at git.compiz.org anyway.)
- By vanilla i mean compiz built from the master branch, here @
@Niclus @ Alistair
I am running the beta nvidia driver 310.14 - the bug still exists. In
fact, i have run every nvidia driver leading upto the current beta,
including all of the stable nvidia driver releases inbetween ~ they ALL
exhibit the blank window problem, if you try to reproduce the
@ Matthias
You are totally correct. This bug still exists.
Clint may not be experiencing it, but 'vanilla-compiz' built yesterday,
still exhibits this bug on my machine.
As a side note, switching workspaces and then switching back to the
workspace where the black windows was originally, also
Sorry, i meant my bug report @ the new nvidia forum is there.
the main page for the new linux nvidia forum is here:
https://devtalk.nvidia.com/default/board/98/linux/
anyways, please do sign up and add your voice to my thread.
cheerz
--
You received this bug notification because you are a
@quequotion
I have been using that 302.17 since the day it was released (with
clamping on - im pretty sure that is the default, now).
in the one or two situations where i see a little white, it has no
effect.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Out of curiosity, is anyone whom is affected by this bug NOT using
Ubuntu?
I ask because i can't produce this bug and I am an Nvidia user
(302.11-beta) ... The only time i can produce white windows, is by
messing with the shadow radius settings in the 'window decoration'
plugin. Which i filed
@Daniel Sam
Ah, that makes sense - i guess it wasn't a bad thing to mention then,
if it caught a bug that could've potentially affected other bug report
'priorities'
cheerz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Sam
why did you mark this bug from important 'high' to 'undecided'? (in
compiz) is this something that isn't going to be addressed because it's
been fixed in Ubuntu (only)?
This bug has been around for months now, it didn't exist previously and
is a pesky annoyance that actually makes grid a
I'm not using Unity, and am using compiz with Arch(linux).
I believe this bug is in compiz itself. I have a had time reproducing
it, but compiz does lose windows, occasionally.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Daniel
This bug actually affects nearly all plugins / effects - from animation
effects; such as zoom or glide 2, to things like windows in scale and
expo too, here is a screenshot of expo;
[url=http://ompldr.org/vZGtiZA][img]http://ompldr.org/tZGtiZA[/img][/url]
I only point this out, because
this bug also affects me, I've been meaning to add myself.
With workspace-switching (CTRL+ALT+ARROW key) i don't notice it much,
but when moving windows around in expo - from workspace to workspace, i
get flickering.
I hadn't used expo in quite some time, but obviously for now (until the
bug is
I'm affected by this bug.
I also use Nvidia but am running Archlinux.
This bug just appeared for me today or possibly last night.
** Also affects: compiz (Arch Linux)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs,
ya this error is onyl have fixed as of sept 1st updatesyesterday i couldn't
open
update manager while today it opened, however clicking on partial upgrade
caused it to crash again..obviuosly though, it is the frontend as the command
line works just fine..
--
update-manager crashed with
hey everyone,
i have installed the kernel realtime dutchman has provided the link to,
and it solved alll of my issues.. mainly the fact that my cpu's weren't being
handled properly and
i had the IOWAIT issue that was sucking up my cpu. thank you so much! i am
running a fairly custom
setup not
one other quick note if someone knows the answer...??!?
how do i set SOUND_CARD_IRQ...?as requested by -
realTimeConfigQuickScan.pl
it is the only parameter in this diagnostic that i don't have in order. i have
scoured around the net
to find an answer with no luck i realize this is a bit
20 matches
Mail list logo
