It doesn't happen for me, I just am a compiz developer and am not sure
what I am supposed to do with that bug ;)
--
Blank Empathy see image attach
https://bugs.launchpad.net/bugs/571918
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Omer,
please see my comment in the Gnome bug tracker
(https://bugzilla.gnome.org/show_bug.cgi?id=617147#c12) and explain to
me the reasoning for saying that a completely empty client (!) window is
caused purely (!) by the window manager. Maybe something in compiz
triggers the problem, but an empty
** Bug watch added: GNOME Bug Tracker #617147
https://bugzilla.gnome.org/show_bug.cgi?id=617147
** Also affects: empathy via
https://bugzilla.gnome.org/show_bug.cgi?id=617147
Importance: Unknown
Status: Unknown
--
** Message: console message: undefined @1: ReferenceError: Can't f
I'm not sure where you see the bug. Yes, XRaiseWindow is covered by focus
stealing prevention. If there is newer activity in the focussed window, raising
the requested window will be denied and the demands_attention hint will be set
on the window.
So far that's works-as-intended.
What exactly d
Upstream fix:
http://git.compiz.org/fusion/plugins/widget/commit/?id=9355319cff2d5d3f8b0699a1e20e729b0e618f74
--
Widget layer disappears when interacting with applications within the widget
layer
https://bugs.launchpad.net/bugs/356374
You received this bug notification because you are a member o
To clarify upstream's opinion: ;-)
glXWaitX is a wait operation. That obviously means for it to work, there
must be a performance impact (as all GL rendering is stalled until all X
rendering is done). How big the actual performance impact is, depends on
a lot of factors (graphics card power, amoun
Also, what are your settings for the detect_outputs option on _screen
1_?
--
Clipped area for multiple X screens with different dimensions
https://bugs.launchpad.net/bugs/331918
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-
Note: smspillaz' comment in the IRC log is flat out wrong. Of course
compiz supports two screens with different resolutions. The issue with
multi-screen and compiz usually only is two different graphics cards. If
you e.g. have ATI + Nvidia, you need two different libGL.so loaded in
one process, whi
I don't think there's much point in asking myself ;)
I can't reproduce it with abiword either, though.
--
Gnome file chooser/selector is way to small
https://bugs.launchpad.net/bugs/75324
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
-
I would like to look into what makes it fail under compiz, but I have
_not_ been able to reproduce it using compiz from git master and gtk+
2.14.5 (Fedora 10). I do see the resize-after-window-map problem,
though. The window size constraining code in compiz is essentially
untouched between 0.7.8 an
Datadog: The issue at hand is _not_ the issue solved by Aaron's patch. It is,
however, the same issue as discussed here:
http://www.nvnews.net/vbulletin/showthread.php?t=122043.
As one can see, Nvidia acknowleged the problem and is looking into it.
--
Titlebar incorrectly drawn with geforce 5/6
This is a Gdk bug, see gnome-bugzilla link.
** Bug watch added: GNOME Bug Tracker #524110
http://bugzilla.gnome.org/show_bug.cgi?id=524110
** Also affects: gtk2 via
http://bugzilla.gnome.org/show_bug.cgi?id=524110
Importance: Unknown
Status: Unknown
** Changed in: compiz (Ubuntu)
*** This bug is a duplicate of bug 246714 ***
https://bugs.launchpad.net/bugs/246714
** This bug has been marked a duplicate of bug 246714
spatial nautilus windows drift when using compiz
--
evince window moves on reload
https://bugs.launchpad.net/bugs/253438
You received this bug notific
The "evince opens maximized, then resizes itself" issue as well as the
"spatial nautilus windows move down/right on every reopen" are fixed in
Gtk 2.12.10...don't know when/if that will land in Hardy, though.
--
window placement problems with compiz
https://bugs.launchpad.net/bugs/189257
You rece
This is not a compiz problem. Pidgin must tell Compiz that it's iconified and
not minimized, and it must tell Compiz where it's iconified to.
In rythmbox, this is done in the rb_shell_set_visibility function in
shell/rb-shell.c.
** Also affects: pidgin
Importance: Undecided
Status: New
This is an Evince problem.
Upstream bug report including explanation:
http://bugzilla.gnome.org/show_bug.cgi?id=524112
Upstream fix: http://svn.gnome.org/viewvc/evince?view=revision&revision=2987
** Changed in: compiz (Ubuntu)
Status: Confirmed => Invalid
--
Evince presentations start in
I have picked that up ;)
A usability fixed switcher can be found here:
http://gitweb.compiz-fusion.org/?p=users/maniac/staticswitcher;a=summary
You can expect that to show up as Compiz Fusion plugin eventually.
--
Compiz default Application Switcher (Alt+Tab) is difficult to use
https://bugs.la
While I personally can't reproduce the problem, I think the problem may
be the one in this Gnome bug:
http://bugzilla.gnome.org/show_bug.cgi?id=524110
At least this bug causes Rhythmbox sometimes being incorrectly placed by
the amount of frame size when switching between small and full mode.
--
For the OP: If you want to launch one compiz per screen, you can do so by
running
DISPLAY=:0.0 compiz --only-current-screen
DISPLAY=:0.1 compiz --only-current-screen
--
slow gtk popup menus with gtk dual head
https://bugs.launchpad.net/bugs/149764
You received this bug notification because you a
Here is the requested upstream comment:
http://lists.freedesktop.org/archives/compiz/2007-April/001916.html
--
Enabling Desktop Effects, some part of firefox, thunderbird and evolution
windows are black for few seconds when I deminimize them.
https://bugs.launchpad.net/bugs/113086
You received t
This is a bug in Crystal which assumes a reparenting WM and does no error
checking at all.
See here for analysis and explanation:
http://bugs.opencompositing.org/show_bug.cgi?id=359
--
kde-window-decorator crashes with sigsegv if the mouse wheel is rolled over
titlebar in Crystal deco
https://
Although I'm obviously biased (as the one who wrote ring), I have to say that I
really, really doubt there is a leak that may fill several hundred megabytes of
memory inside ring.
Besides the usual boilerplate code that every compiz plugin has, there is only
one place of allocation where a 8 byt
This is a gnome-screenshot bug.
See here: https://bugs.freedesktop.org/show_bug.cgi?id=9357 for the explanation.
** Also affects: gnome-utils (Ubuntu)
Importance: Undecided
Status: New
** Changed in: compiz (Ubuntu)
Status: New => Invalid
--
Alt+PrntSc does not include window b
The workspace switcher applet of the gnome-panel (gnome-
panel/applet/wncklet/workspace-switcher.c, function applet_scroll)
should use the viewport functions instead of the workspace functions
when Compiz is used. As it already has support for Compiz, this has
obviously just slipped through.
BTW,
Even better would be if gedit used libwnck so that the detection logic
only needs to be implemented once.
--
Compiz breaks gedit workspace grouping behavoir
https://bugs.launchpad.net/bugs/150132
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
To elaborate a bit more on this statement:
It's not a driver bug, but a known limitation of the AIGLX texture-from-pixmap
implementations.
It's explained in Kristian Hoegsbergs excellent blog posting:
http://hoegsberg.blogspot.com/2007/08/redirected-direct-rendering.html
--
putting glxgears bel
26 matches
Mail list logo