[compiz] free from GLX_EXT_texture_from_pixmap
You might have hear this before. I just came across it today. from http://blog.beryl-project.org/ I am running your svn and have noticed this non-tfp Beryl, what is this? It is exactly what it sounds like, an early attempt (with some success I might add) to make Beryl run without the need for texture_from_pixmap. No more black window bug from nvidia, no more Xgl, no more AIGLX. Oh yeah… and its faster than Xgl/AIGLX (nvidia beta performance looks to be about the same). The code is all thanks to Onestone who is a true bling hero, and the idea itself originates from the Project Looking Glass people. Kudos to them and their great work, we hope to incorporate more of their experience to Beryl’s code base in the form of optimizations and improvements. it seems to be still in it's infancy though. Even if it's not as good/fast as the GLX extension, it's still nice to have an alternative path in case the extension is not available. -Ioannis ___ compiz mailing list compiz@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/compiz
Re: [compiz] drag-n-drop
thanks. Now I've got it. It's another little feature that enhances productivity. Originally I thought I could drag and drop while in scale mode (a more advanced concept). Of course that would require the objects to be alive during scale mode (I think I've seen a discussion about this, related to Xorg input methods). -Ioannis Who wrote: For me it shows itself when I do the following: (the 'Sloppy Focus' option of the scale plugin must be ON - perhaps this counts as a bug?) Drag an icon Activate Scale (either by dragging the icon to the top corner or using the key) Hover over the window you want to drop the icon on The windows unscale with the chosen window on top Hope that helps Who On 1/5/07, Ioannis Nousias [EMAIL PROTECTED] wrote: what is the new scale-plugin dragdrop feature and how does one make use of it? thanks ___ compiz mailing list compiz@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/compiz ___ compiz mailing list compiz@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/compiz ___ compiz mailing list compiz@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/compiz
[compiz] sync request issue
It seems that the latest updates have partly solved the annoying nvidia driver bug with black windows (for NV2x cards). I can simply invoke compiz like that: compiz --replace gconf and everything works fine, no black windows or windows that don't update. I say partly because performance is sluggish now. Whatever these new updates do, they seem to bypass the driver's problem and possibly hit a slower rendering path. it's good that at least it works now in some way. Thanks David, et all Let's hope nvidia will soon release a drive fix for this annoying bug that's been out for ages! -Ioannis ___ compiz mailing list compiz@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/compiz
Re: [compiz] sync request issue
Ioannis Nousias wrote: It seems that the latest updates have partly solved the annoying nvidia driver bug with black windows (for NV2x cards). I can simply invoke compiz like that: compiz --replace gconf and everything works fine, no black windows or windows that don't update. I say partly because performance is sluggish now. Whatever these new updates do, they seem to bypass the driver's problem and possibly hit a slower rendering path. it's good that at least it works now in some way. Thanks David, et all Let's hope nvidia will soon release a drive fix for this annoying bug that's been out for ages! -Ioannis ___ compiz mailing list compiz@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/compiz sorry, I was quick to post before. Invoking compiz like this: compiz --indirect-rendering --replace gconf will have all windows displayed properly, but of course you'll get bad performance. Also I've noticed XV isn't working (mplayer -vo xv). I get the following error: X11 error: BadAlloc (insufficient resources for operation) Anyway, the black windows issue is not a compiz problem but an nvidia driver one, so ignore this. Something else I've noticed is that the session management has changed as well. Now it's more persistent. I've invoked compiz several times with the --replace option and I ended up having multiple compiz entries in my session manager. Calling metacity --replace failed as well and I was back to compiz again. The --sm-disable works and prevents that from happening. -Ioannis ___ compiz mailing list compiz@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/compiz
[compiz] blur plugin and GL_ARB_fragment_program extension
The blur plugin has GL_ARB_fragment_program extension as a prerequisite. At least that's what I'm getting by looking at screen.c. I think there should be a check for the CompScreen::fragmentProgram flag somewhere in blur.c to prevent it from loading or at least executing a null pointer. I get a crash in line blur.c:1858, because CompScreen::programEnvParameter4f is zero. I have a NV28 with 1.0-9631 binary drivers and a rv250 with Xorg7.1 drivers, none of which have the above extension. thanks PS: compiz from today's git version ___ compiz mailing list compiz@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/compiz
Re: [compiz] gtk-window-decorator - No window borders
Brad Ison wrote: Ioannis Nousias wrote: is the the decoration plugin included in the /apps/compiz/general/allscreens/options/active_plugins key? I have it third after gconf and inotify plugin. Brad Ison wrote: Hi, I have a strange problem with gtk-window-decorator. I've tried 0.3.6 the latest from git, but with either I don't get any window borders when running gwd. I hope its not something simple I've missed but I've searched around and not found anything. gwd never segfaults or even displays any warnings or anything for that matter. It just doesn't draw the borders. I've tried every combination of gconf settings (setting use_metacity_theme to false etc) and tried changing my metacity theme. It still will not draw any borders. I'm running Ubuntu Feisty with all the latest updates using an ATI x850 with the free r300 driver and Mesa 6.5.2. Compiz itself works alright though I have some weird issues with windows not redrawing, but I expect that is due to using a somewhat experimental video driver. I can't seem to explain why the window borders aren't being drawn though. Any ideas? ___ compiz mailing list compiz@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/compiz Please correct me if I'm wrong, but as of 0.3.6 at least, decoration is no longer a plugin to be loaded but a library that gwd is linked to, right? mind you I'm not a compiz developer, but I know this: The libdecoration is a static library used to design window decorators like gwd. This design decision was made to maximize code reuse for any window decorator developed for compiz. as for the decoration plugin it's still there and enables the functionality for compiz to support window decorators. So please added to you active_plugins list :-D ___ compiz mailing list compiz@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/compiz
Re: [compiz] gtk-window-decorator - No window borders
Brad Ison wrote: Ioannis Nousias wrote: Brad Ison wrote: Ioannis Nousias wrote: is the the decoration plugin included in the /apps/compiz/general/allscreens/options/active_plugins key? I have it third after gconf and inotify plugin. Brad Ison wrote: Hi, I have a strange problem with gtk-window-decorator. I've tried 0.3.6 the latest from git, but with either I don't get any window borders when running gwd. I hope its not something simple I've missed but I've searched around and not found anything. gwd never segfaults or even displays any warnings or anything for that matter. It just doesn't draw the borders. I've tried every combination of gconf settings (setting use_metacity_theme to false etc) and tried changing my metacity theme. It still will not draw any borders. I'm running Ubuntu Feisty with all the latest updates using an ATI x850 with the free r300 driver and Mesa 6.5.2. Compiz itself works alright though I have some weird issues with windows not redrawing, but I expect that is due to using a somewhat experimental video driver. I can't seem to explain why the window borders aren't being drawn though. Any ideas? ___ compiz mailing list compiz@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/compiz Please correct me if I'm wrong, but as of 0.3.6 at least, decoration is no longer a plugin to be loaded but a library that gwd is linked to, right? mind you I'm not a compiz developer, but I know this: The libdecoration is a static library used to design window decorators like gwd. This design decision was made to maximize code reuse for any window decorator developed for compiz. as for the decoration plugin it's still there and enables the functionality for compiz to support window decorators. So please added to you active_plugins list :-D No decoration plugin is installed in $prefix/lib/compiz/ just the libdecoration libraries are installed into $prefix/lib/. If I do add decoration to active_plugins compiz won't find it and will remove it from the list. When I first saw this happening I too thought this was the problem. So, I went into $prefix/lib/compiz/ and copied the libdecoration files installed to $prefix/lib/ into the compiz directory as if they were a plugin. But, when compiz goes to load the decoration plugin then it complains about not being able to lookup getCompPluginInfo in libdecoration.so - I see the getCompPluginInfo function in decoration.c though. So at this point I'm not sure what to think. As for xorg 7.2, as Gerd mentioned in another reply that using 7.1 may be a problem, it hit the Feisty repos today and I am using it. Though I don't know if all the relevant proto / driver packages are updated yet. the /usr/lib/compiz/libdecoration.so is different form the /usr/lib/libdecoration.so.0.0.0 the first one is the plugin and the second one the shared library for gtk-window-decorator I can see that gtk-window-decorator loads this (using ldd) libdecoration.so.0 = /usr/lib/libdecoration.so.0 I don't know why the packages would miss the plugin, but when you compile compiz from git check if the decoration gets compiled. hope that helps ___ compiz mailing list compiz@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/compiz
Re: [compiz] Re: --skip-gl-yield
Joel Calado wrote: On Thu, 2007-04-19 at 11:32 +0100, Colin Guthrie wrote: AFAIK, this is just an argument that is used internally by beryl. It sets an environment variable and then restarts itself to pick up on it. If you set the environment variable manually before running compiz do things work for you? e.g. GL_YIELD=NOTHING compiz your normal arg list Col Nope, no can do. It still lags like hell :( ___ compiz mailing list compiz@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/compiz I think the variable is '__GL_YIELD', i.e.: __GL_YIELD=NOTHING compiz ... also try '--loose-binding' ___ compiz mailing list compiz@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/compiz
[compiz] [PATCH] segfault when loading plugins with incompatible ABI
loading plugins with older ABI caused compiz to crash. Here is a simple
patch to avoid it. Basically in both cases the counters have some random
value (large) but the array pointers are NULL, causing the crash.
-Ioannis
diff --git a/src/plugin.c b/src/plugin.c
index 4c7c45c..fc9bd61 100644
--- a/src/plugin.c
+++ b/src/plugin.c
@@ -484,7 +484,7 @@ checkPluginDeps (CompPlugin *p)
CompPluginDep *deps = p-vTable-deps;
int nDeps = p-vTable-nDeps;
-while (nDeps--)
+while (deps nDeps--)
{
switch (deps-rule) {
case CompPluginRuleBefore:
@@ -537,6 +537,7 @@ pushPlugin (CompPlugin *p)
return FALSE;
}
+if (p-vTable-features)
for (i = 0; i p-vTable-nFeatures; i++)
{
plugin = findActivePluginWithFeature
(p-vTable-features[i].name, 0);
___
compiz mailing list
compiz@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/compiz
[compiz] Fedora 7 and Compiz 0.3.6
Just a quick question, Any ideas why Fedora 7 is still on Compiz 0.3.6? Currently the main repository has 0.3.6 and the development one has 0.4. Shouldn't it be 0.4 for the main and 0.5 for the development? Does 0.4 break anything? -Ioannis ___ compiz mailing list compiz@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/compiz
Re: [compiz] Fedora 7 and Compiz 0.3.6
that's true. Nevertheless, packages get updated throughout the life of a Fedora release. For instance, Fedora 7 came with metacity 2.18.0 and now the repos have 2.18.3. Even beryl got updated from 0.2.0 to 0.2.1 Sam Spilsbury wrote: I think Compiz 0.4 was released after the fedora 7 feature freeze. On 6/26/07, *Ioannis Nousias* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Just a quick question, Any ideas why Fedora 7 is still on Compiz 0.3.6? Currently the main repository has 0.3.6 and the development one has 0.4. Shouldn't it be 0.4 for the main and 0.5 for the development? Does 0.4 break anything? -Ioannis ___ compiz mailing list compiz@lists.freedesktop.org mailto:compiz@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/compiz http://lists.freedesktop.org/mailman/listinfo/compiz ___ compiz mailing list compiz@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/compiz
Re: [compiz] [ANNOUNCE] compiz-0.6.0
Danny Baumann wrote: Hi, Additionally, a git clone of the source tree: git clone git://git.freedesktop.org/git/xorg/app/compiz will include a signed compiz-0.6.0 tag which points to a commit named: 6218259ff6ec71a1eb6e9062646d63794947747e which can be verified with: git verify-tag compiz-0.6.0 and can be checked out with a command such as: git checkout -b build compiz-0.6.0 Unfortunately I noticed today that release 0.6.0 contains a bad problem that allows e.g. desktop windows being stacked over normal windows when they are mapped. This results in normal windows and/or panels not being visible when compiz is launched with the Gnome or KDE session until the desktop window is restacked once (e.g. by clicking on it if the Raise on click option is enabled). I will release a 0.6.2 ASAP that fixes that problem, but until then, please either apply this commit to the release tarball: http://gitweb.freedesktop.org/?p=xorg/app/compiz.git;a=commit;h=b6c6acc70261d0942977441914c23e7a1c99215e or continue to use the compiz-0.6 branch. My apologies for letting this bad mistake slip in the stable release and sorry for the inconvenience. Regards, Danny ___ compiz mailing list compiz@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/compiz it's probably best to have 'release candidates'. ioannis ___ compiz mailing list compiz@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/compiz
