Compiz 0.8.8 was released 2011-03-30. It fixes some rather annoying window stacking problems. Changes, as per NEWS: - Various focus and stacking fixes. - Removed usages [sic] of deprecated GTK API. - Fixed drawing of switcher background with KDE4 window decorator.
*bump* Please add to testing/~arch?
Created attachment 275703 [details] compiz 0.8.8 ebuilds I've updated the ebuilds for overlay use. As I'm an KDE user, I can't comment on the gconf or gnome side of things, but these ebuilds work like a charm for me. I will add another package later for the diffs so that the devs can easily see what's changed. There also are quite a few files that aren't needed anymore. In the meantime, I'm always glad about comments if this tarball also works-for-you.
In compiz-fusion-0.8.8 why is MY_PV=0.8.4 and ccsm set to 0.8.4 looks as though it should be PV and simple-ccsm in the ebuild? Comments? Change- >=x11-apps/ccsm-${MY_PV} to >=x11-apps/simple-ccsm-${PV} when simple-ccsm is pulled in then it would also have the right >=dev-python/compizconfig-python-${PV}
Created attachment 275937 [details] this version uses simple-ccsm-0.8.8 This version of the ebuild will use simple-ccsm instead of ccsm and when simple-ccsm is called it will pull in >=dev-python/compizconfig-python-0.8.8
Neither ccsm nor compizconfig-python were updated to 0.8.8 because neither received a single code commit on the 0.8 branch. That's why they're "stuck" on 0.8.4. You are right though in that there's a mistake in the simple-ccsm ebuild. This one should have MY_PV=0.8.4 as well for the aforementioned reason.
Yes ...my bad ...assuming a 'branch' would be complete ;-) ccsm is required as is compizconfig-python installed w/ -gconf and using gconf-backend from package
Created attachment 275959 [details] updated simple-ccsm-0.8.8.ebuild
I've been running this on the desktop for about a week Calculating dependencies... done! [ebuild R ] x11-wm/compiz-0.8.8 USE="cairo dbus fuse gnome gtk svg -gconf -kde" 0 kB [?=>1] one issue I've noticed...if firefox is on a screen and I send it to a new workspace it will end up behind the desktop background (an edge peeked out) I cannot bring such applications to the foreground. I cannot figure out how to do the cube faces with my windows on it. It switches desktops as if it was a spinning cube and the windows are wobbly. Most of the affects i try seem to work fine. It looks as though some options disable others and it would be easy to mess these up in ccsm. Haven't tried simple-ccsm yet.
Created attachment 277515 [details] ebuild for libdrm-2.4.26 tested and working locally tested ebuild
cannot confirm any issue as reported in comment #8 PBKBAC
Working great on amd64 with nvidia blob and gnome 2. Thank you for the ebuilds!
Also tested on ~amd64, because of dbus flag removal in 0.8.4 (some user reported failure, so mask the flag maybe have been more appropriated. Obviously users that have the correct behavior will not seek it on the bugtracker, thus not reporting it works or too late) I noticed no more flickering in xterm trayfreq (https://bugs.gentoo.org/show_bug.cgi?id=388643) icon in stalonetray sometimes doesn't refresh (Merely unrelated to compiz, but on the trayfreq, even it worked fine using compiz-0.8.4) tested with nvidia-driver not tested with nouveau driver (will try it and report later)
I can also confirm that this compiz-0.8.8.ebuilds are working well. So what's up with the desktop-effects maintainers not to apply any updates forever?
compiz-0.8.8 fixes bug 375883 Works well with nvidia blog and intel g45 (kernel 2.6.39) Please, include into the portage tree.
Compiz was package.mask'ed today and is scheduled to be removed in 30 days. If you care about keeping compiz in Gentoo and are willing to maintain the ebuilds, now is the time to come forward and say so. Read http://www.gentoo.org/proj/en/qa/proxy-maintainers/index.xml what would be needed from your side.
Hmmm... Why is it being removed? Why is this the announcement location/style?
This is really very bad news.
Official announcement was made to the gentoo-dev mailing list: http://archives.gentoo.org/gentoo-dev/msg_7890ae9f8247f2250655116b24af6f54.xml
I guess we are relegated to keeping the ebuild for 0.8.6 or 0.8.8 in a local overlay until they can't be used anymore. That could be a long time from now, or not...
(In reply to comment #18) > Official announcement was made to the gentoo-dev mailing list: > http://archives.gentoo.org/gentoo-dev/msg_7890ae9f8247f2250655116b24af6f54.xml I forgot to CC gentoo-dev-announce. I've fixed that now.
compiz has no critical bugs, works quite well for many users. What for to remove it?
These ebuilds worked fine for me
KDE-4.7.4 (~ amd64, GCC-4.6.2): Compiz-0.8.8 works fine. Together with the effects.
These packages will be removed, because there is no one to be a maintainer. It seems Gentoo developers don't use compiz much or don't have much time to maintain the packages. But if someone can be a proxy maintainer, some Gentoo developers including me would become a commiter for you. Please read http://www.gentoo.org/proj/en/qa/proxy-maintainers/index.xml and consider to become a proxy maintainer.
What for to remove something that just works? Gentoo involves many orphaned packages. Ebuilds for 0.8.8 from here works for many user, and this is the last stable release. Compiz is not dead, the ebuilds for latest stable compiz are ready and there are no critical bugs. Why to remove? Why not to put 0.8.8 into portage and to orphan this packages? Perhaps in nearest future someone will take this.
Why compiz is not here http://www.gentoo.org/proj/en/qa/treecleaners/maintainer-needed.xml but is planned to be removed in a month?
(In reply to comment #26) > Why compiz is not here > > http://www.gentoo.org/proj/en/qa/treecleaners/maintainer-needed.xml > > but is planned to be removed in a month? Because the metadata.xml file doesn't have maintainer-needed@g.o tag. Completely unrelated to this bug. Try Comment #24 again.
If no one else wants to step in as maintainer, seem I need to offer to do it to prevent it from getting dropped from portage.
(In reply to comment #28) > If no one else wants to step in as maintainer, seem I need to offer to do it to > prevent it from getting dropped from portage. Please, do it and save compiz in portage!
*subscribed to bug* I have copied and bumped compiz ebuilds in my overlay but i am surely do not want compiz ebuilds disappear from main tree, so if gentoo developers still need proxy maintainer - i am ready for that...
(In reply to comment #30) > *subscribed to bug* > I have copied and bumped compiz ebuilds in my overlay but i am surely do not > want compiz ebuilds disappear from main tree, so if gentoo developers still > need proxy maintainer - i am ready for that... previosly add patch for kwin >=4.8 //ну ты понел
Hey count also me in if help is needed :)
Created attachment 306469 [details] libcompizconfig-0.8.8.ebuild Yesterday I encountered the problem related at: https://bugs.launchpad.net/compiz-libcompizconfig/+bug/936840 patch is available for c++ version of compiz, not for c (<0.9)
(In reply to comment #30) > *subscribed to bug* > I have copied and bumped compiz ebuilds in my overlay but i am surely do not > want compiz ebuilds disappear from main tree, so if gentoo developers still > need proxy maintainer - i am ready for that... Thanks. Let's start to rescue compiz. I'll be a committer for this package. We should start from bumping to upstream stable version 0.8.8 first? Where can I find updated version of your (or any others willing to be maintainer) ebuild?
(In reply to comment #34) > Where can I find updated version of your (or any others willing to be > maintainer) ebuild? In my overlay - https://github.com/Pinkbyte/pinkbyte-overlay It's also in layman(named pinkbyte) Ebuilds in my overlay are just bumped, no other significant changes made, except for libnotify patch(i removed it)
(In reply to comment #35) > (In reply to comment #34) > > Where can I find updated version of your (or any others willing to be > > maintainer) ebuild? > > In my overlay - https://github.com/Pinkbyte/pinkbyte-overlay > It's also in layman(named pinkbyte) > Ebuilds in my overlay are just bumped, no other significant changes made, > except for libnotify patch(i removed it) Thanks. I'll add DEPEND on dev-util/intltools and commit to the tree assigning you as a maintainer. BTW, could you also be a maintainer for following other desktop-effect packages? # Mask compiz for last-rites unless someone steps up # to maintain it. Removal in 30 days. dev-python/compizconfig-python x11-apps/ccsm x11-apps/fusion-icon x11-apps/simple-ccsm x11-libs/compiz-bcop x11-libs/compizconfig-backend-gconf x11-libs/compizconfig-backend-kconfig4 x11-libs/libcompizconfig x11-plugins/compiz-plugins-extra x11-plugins/compiz-plugins-main x11-plugins/compiz-plugins-unsupported x11-themes/emerald-themes x11-wm/compiz-fusion x11-wm/emerald
(In reply to comment #36) > BTW, could you also be a maintainer for following other desktop-effect > packages? > > ... Sure, no problem
Pinkbyte, I just tried your overlay, and x11-plugins/compiz-plugins-extra-0.8.8-r9999 fails to compile. I get libnotify error (even with USE=-libnotify) notification.c: In function 'notifyLogMessage': notification.c:110:34: error: too many arguments to function 'notify_notification_new' /usr/include/libnotify/notification.h:114:21: note: declared here make[3]: *** [notification.lo] Error 1 There was a version of libnotify patch for 0.8.8 around somewhere here (worked for me) but I can't find it. If you want it, I can attach it here, but I don't remember where I got it from.
(In reply to comment #38) > Pinkbyte, I just tried your overlay, and > x11-plugins/compiz-plugins-extra-0.8.8-r9999 fails to compile. > > I get libnotify error (even with USE=-libnotify) > > > > notification.c: In function 'notifyLogMessage': > notification.c:110:34: error: too many arguments to function > 'notify_notification_new' > /usr/include/libnotify/notification.h:114:21: note: declared here > make[3]: *** [notification.lo] Error 1 > > > There was a version of libnotify patch for 0.8.8 around somewhere here > (worked for me) but I can't find it. If you want it, I can attach it here, > but I don't remember where I got it from. Please find it and i will include it in ebuild. I use libnotify and did not test compilation without it, but i am definitely sure, that i through away libnotify patch, because of no time to adapt and test it...
Created attachment 307097 [details, diff] patch compiz-plugins-extra-0.8.8-libnotify.patch
Ok, attached a patch. But note, that your compiz-plugins-extra fails to build for me both with +libnotify and -libnotify. I use x11-libs/libnotify-0.7.4. I get the same error in both cases.
(In reply to comment #40) > Created attachment 307097 [details, diff] [details, diff] > patch compiz-plugins-extra-0.8.8-libnotify.patch Thank you for the patch. (In reply to comment #41) > Ok, attached a patch. But note, that your compiz-plugins-extra fails to > build for me both with +libnotify and -libnotify. I use > x11-libs/libnotify-0.7.4. I get the same error in both cases. You are right - without patch(and with installed libnotify) compiz-plugins-extra-0.8.8 from my overlay did not compile no matter use-flag 'libnotify' set or not. So, this patch should be applied for both cases. I will add it to my overlay and this patch should be in portage tree too...
Compiz ebuild proposed in the Pinkbyte overlay is issued from version who dropped dbus support. It has been reported that dbus will make compiz crash whatever. So dbus flag has been dropped from compiz. I can send some command to compiz via command line without any issues, it's working pretty well and sometimes useful (even I don't use it much). I suggest: 1) inform people from this issue with einfo, and use package.use 2) masking the dbus flag But not removing dbus flag.
Created attachment 307879 [details, diff] Patch from stuff overlay. For x11-wm/compiz with +kde to compile against kde-4.8.
Pinkbyte, you probably forgot to manifest x11-plugins/compiz-plugins-unsupported after removing old ebuilds. I'm getting this error: !!! A file listed in the Manifest could not be found: /var/lib/layman/pinkbyte/x11-plugins/compiz-plugins-unsupported/compiz-plugins-unsupported-0.8.4-r9999.ebuild And I've attached a patch obtained from stuff overlay. It is necessary for x11-wm/compiz with +kde USE flag to compile against kde-4.8. It seems that the patch does not affect compilation on kde-4.7.
(In reply to comment #45) > Pinkbyte, you probably forgot to manifest > x11-plugins/compiz-plugins-unsupported after removing old ebuilds. I'm > getting this error: > !!! A file listed in the Manifest could not be found: > /var/lib/layman/pinkbyte/x11-plugins/compiz-plugins-unsupported/compiz- > plugins-unsupported-0.8.4-r9999.ebuild > > And I've attached a patch obtained from stuff overlay. It is necessary for > x11-wm/compiz with +kde USE flag to compile against kde-4.8. > It seems that the patch does not affect compilation on kde-4.7. Issue with manifest fixed. Thank you for reporting it. Patch for kwin 4.8 and higher added with checking on currently installed version of kwin(picked from stuff overlay, thanks to megabaks).
Hi, I'm so happy to see all of you help packages maintained here. But let's split bugs so that I can handle them well. I've filled bug #410979 to track what should be fixed to remove the masks. Please fill/add any bugs not listed on the tracker bug.
Pinkbyte, seems like compiz-kde-4.8.patch for x11-wm/compiz is missing. Error message: !!! A file listed in the Manifest could not be found: /var/lib/layman/pinkbyte/x11-wm/compiz/files/compiz-kde-4.8.patch
(In reply to comment #48) > Pinkbyte, seems like compiz-kde-4.8.patch for x11-wm/compiz is missing. Thanks for reporting, now it is fixed
bug #365121 didn't find the cause of problem and just waited for -0.8.8. So let's restore dbus USE flag and see if the problem is still there or not.
(In reply to comment #50) > bug #365121 didn't find the cause of problem and just waited for -0.8.8. So > let's restore dbus USE flag and see if the problem is still there or not. I have restored dbus USE flag in my overlay's ebuild. Compilation with it was successful
(In reply to comment #51) > (In reply to comment #50) > > bug #365121 didn't find the cause of problem and just waited for -0.8.8. So > > let's restore dbus USE flag and see if the problem is still there or not. > > I have restored dbus USE flag in my overlay's ebuild. Compilation with it > was successful ok, thanks. do you think it's ready to go to main repository? If so I'll do the work and close this bug.
(In reply to comment #52) > ok, thanks. do you think it's ready to go to main repository? If so I'll do > the work and close this bug. Well, i can say that all of compiz-related ebuilds that i used(i do not use fusion-icon, so i can not say what about it) are in status 'works for me'. I use compiz with KDE4 and earlier(in comment #33) there was some GNOME-related problem, that i could not reproduce, because i do not have test environment with both GNOME and compiz installed. But, anyway, i think that ebuilds are ready to be included in main portage tree
(In reply to Comment 53) This bug signaled in comment 33 is not related to gnome but to gtk. I don't use gnome and just run compiz in standalone mode (ccp). commit 1f6a921158b5a4fa80ea2e844ce25aad04101aaf Author: Michael Natterer <mitch@lanedo.com> Date: Fri Sep 16 16:12:23 2011 +0200 gtk: allow to specify accelerators in a platform-independent way Introduce <Primary> in accelerator strings, which resolves to GDK_CONTROL_MASK on X11/Win23, and to GDK_META_MASK on quartz. Also serialize CONTROL/META as <Primary> depending on the platform. gtk/gtkaccelgroup.c | 36 ++++++++++++++++++++++++++++++++++++ 1 files changed, 36 insertions(+), 0 deletions(-) depending on the platform ! I'm on amd64 like lot of other people on the thread
You can also take at the bitting comment from compiz lead developer on: https://code.launchpad.net/~compiz-team/compiz-libcompizconfig/0.9.5 See: 429. By Sam Spilsbury on 2012-03-05 I don't copy this comment here.
Hey people, I can also testify on my side that everything works fine with 0.8.8. Here are the packages/versions I have: ccsm-0.8.4 compiz-0.8.8 compiz-bcop-0.8.8 compiz-plugins-extra-0.8.8 compiz-plugins-main-0.8.8 compiz-plugins-unsupported-0.8.8 compizconfig-backend-gconf-0.8.8 compizconfig-python-0.8.4 libcompizconfig-0.8.8 BTW. I'm running these with GNOME, for a month or so now. Some previous nuisances such as small tooltips being garbled and white screen when switching ttys are gone. I'd concur that it's pretty much stable. I'm using expo, wall, animations, window previews, scale...
Let me just add here that compiz + wall plugin + xfce4-plugin is affected by a bug described here: http://www.mail-archive.com/dev@lists.compiz-fusion.org/msg00530.html
(In reply to comment #57) > Let me just add here that compiz + wall plugin + xfce4-plugin is affected by > a bug described here: > http://www.mail-archive.com/dev@lists.compiz-fusion.org/msg00530.html Is it a new bug in 0.8.8 version? The way it is described, it seems to be a known issue that should have been around forever.
Added and unmasked x11-wm/compiz-0.8.8. Thanks.
Sorry for not being clear. It's been around for a long time, although I don't think that it affected xfce-panel so long ago as 2009 (maybe I had something different in my system). I just wanted to point out that current compiz still is affected by a bug that is quite serious for xfce users. Maybe even ebuild should warn a user about it if xfce4-panel is detected (and suggest a work-around).
