[SOLVED] ccsm does still not work

[xerxesmc]

i emerged compcomm from xeffects overlay and i use Kristian's script, but ccsm does not work, i can start it with `ccsm` but no change takes effect... am i missing something?

[Deciare]

I don't understand the question. What part of ccsm does not work? Do you receive an error message when trying to start it (from a console)? Are your plugins not listed? Are the options you change not taking effect? Are certain options missing?

I may not be able to help you, but if you explain your problem in greater detail, maybe someone else can.

[DeathCarrot]

Unlike beryl, changes aren't instant - you need to restart compiz for them to come into effect.

Anyone know when we might be rid of this restarting thing? It's a serious pain because if I have several windows open I can only restart compiz a few times before I run out of video memory (and that's with a 640MB card) and get black windows, at which point I either need to restart X or switch to xfwm...

[Deciare]

I use the ccp plugin with ccsm and the flat-file configuration backend, and as far as I know, changes to my configuration always take effect instantly.

Might you be using a different combination of configuration-related things?

[DeathCarrot]

That's what I use as well =/ To start compiz I use:
[code:73379]compiz --replace --sm-disable ccp
emerald --replace &[/code:73379]
I have flat-file config selected in ccsm (only one I have available as I'm on neither kde or gnome).

edit: and using compiz-manager doesn't help.

[Deciare]

Do you have the Inotify, Dbus, GLib, or User Space Filesystem plugins enabled? I thought one of them might be helping the configuration stay up-to-date, but I don't have any of them enabled...

All I know is that any time ~/.css/CompComm1.ini (that's the name of the profile I'm using) changes, even if I modify it in an editor or overwrite it with another file, CompComm's configuration updates instantly. I don't know what mechanism it might be using to achieve that.

[xerxesmc]

i have installed the go-compiz-trayicon and now everything is working like in beryl, immediately :D

[DeathCarrot]

I see inotify is the plugin that is supposed to enable the beryl-type behaviour, unfortunately when I start compiz I get:
[code:1f414]inotify_init: Function not implemented
compiz (core): Couldn't activate plugin 'inotify'[/code:1f414]
:|

I'll try updating...
edit: Doesn't work... Oh well. :(

[maniac]

I see inotify is the plugin that is supposed to enable the beryl-type behaviour, unfortunately when I start compiz I get:
[code:91078]inotify_init: Function not implemented
compiz (core): Couldn't activate plugin 'inotify'[/code:91078]
:|

I'll try updating...
edit: Doesn't work... Oh well. :(
You don't need the inotify plugin if you use ccp, however, the ccs library uses inotify internally and needs it for applying changes instantly. It looks like the inotify implementation in your distribution is broken, at least the message "Function not implemented" looks like that. What distribution do you use?

[DeathCarrot]

Gentoo (x86_64), xeffects repo.

[Jupiter]

Gentoo (x86_64), xeffects repo.
Try re emerging in this order. "exclude the ones you don't use"
[code:9af86]emerge -av1 compiz bcop ccs-lib emerald compcomm-plugins-main compcomm-plugins-extra compcomm-plugins-unsupported ccs-backend-kconfig ccs-python ccs-backend-gconf emerald-themes ccsm compcomm[/code:9af86]

[DeathCarrot]

Earlier today I unmerged them all, cleared distfiles/git-src and emerged them again (in that exact order) - no change.
What difference does merging them with -1 make? The manpage says
"Emerge as normal, but do not add the packages to the world file for later updating."
but I'm not sure what that means in practice..

[Jupiter]

Earlier today I unmerged them all, cleared distfiles/git-src and emerged them again (in that exact order) - no change.
What difference does merging them with -1 make? The manpage says
"Emerge as normal, but do not add the packages to the world file for later updating."
but I'm not sure what that means in practice..

The one is good to use in this case so you don't have compcomm updating when you
do a world update. I make it a general rule to always go to the gitweb page and see
if there is an update and what changes were made, before i update compcomm. And
I always go through the forum first and see if problems and what kind are being reported
for the latest updates. We have to keep in mind that this is alpha software and an
update can break your existing install/setup. So it is a good idea not to update blindly.
http://gitweb.opencompositing.org/?o=age

I don't know weather this inotify error is a problem as i don't even have it enabled and
i have no problem with changes taking instant effect when i make them.

[Deciare]

I don't know weather this inotify error is a problem as i don't even have it enabled and i have no problem with changes taking instant effect when i make them.
As maniac mentioned in [url=http://www.opencompositing.org/viewtopic.php?p=3742#p3742:20d1f]an earlier post[/url:20d1f], ccp internally uses inotify to keep track of changes made to the configuration, and doesn't rely on the inotify plugin. The fact that inotify isn't compiled into DeathCarrot's kernel (CONFIG_INOTIFY and CONFIG_INOTIFY_USER) is probably the problem.

Excellent point.
I do have it enabled in the kernel myself so it makes sense why it works for me.

[DeathCarrot]

Hmm, and thus the plot thickens. Both INOTIFY and INOTIFY_USER do seem to be compiled into the kernel.
I doubt it's related but I also tend to have a lot of graphical glitches with compiz. For example with the Resize Info and Desktop Wall plugins whenever there's graphical overlay, transparencies tend to get screwed up (it's like the buffer isn't being cleared/written to properly).

edit: btw, thanks for the tip about checking gitweb Jupiter :)

[Deciare]

According to [url=http://article.gmane.org/gmane.mail.imap.dovecot/13106/match=failed+function+implemented:b2bc2]something I Googled[/url:b2bc2], there may be an issue with whether glibc recognises that your kernel supports inotify, too. Try rebuilding glibc against a version of kernel headers that match the kernel version you're currently running (>=2.6.13 in both cases)?

[DeathCarrot]

Good call on the glibc, it seems to be functioning as intended now :D I'm sure I've built glibc for this kernel before as this is the only kernel I've used since I built the machine a few months back (2.6.18), but simply rebuilding (well, upgrading, went up from 2.4 to 2.5) glibc worked :) Thanks!

[Jupiter]

Good call on the glibc, it seems to be functioning as intended now :D I'm sure I've built glibc for this kernel before as this is the only kernel I've used since I built the machine a few months back (2.6.18), but simply rebuilding (well, upgrading, went up from 2.4 to 2.5) glibc worked :) Thanks!

Deciare saves the day,,,,,,,AGAIN
Good work

Don't forget to mark the thread solved DeathCarrot, please.

[Deciare]

*does a little victory dance* Whoo! I'm glad I was able to help. ^_^

And it's good that your system was awarded with a package upgrade, too!

[DeathCarrot]

Don't forget to mark the thread solved DeathCarrot, please.
I would, but not my thread :)

[Jupiter]

Don't forget to mark the thread solved DeathCarrot, please.
I would, but not my thread :)

.... I went ahead and took care of it.