[SOLVED] Problems with CCSM

[Jupiter]

nice tool
BUT damn it looks fugly,,, really needs at least some texture background.
Plugin layout is nice BUT like when going into the General Options, there
are fields that are not well defined at all and seem really confusing as far
as usage. A good example of this is the "Opacity Window Values and
Opacity Windows". Theres got to be a better way of doing this AND
defining what it is. There is no close button either, which sucks when
we are entering data in a field and compiz crashes, we lose deco's at this
point and there is no way to close the ccsm window. Talking about crashes,
it happens often when entering data,,,Example: when entering the data for
Image files "which is not well defined either" in the Desktop Cube plugin, compiz
crashes. When i say it is not well defined, i am talking about having a better
description so that someone who is not familiar with things "MOST USERS", know
what it is. Is it image for top, bottom, wallpaper, what is it. Maybe use the empty
space on the left "under plugin name" to put a discription of the field you have
clicked on. Click in the Skydome field to enter data and 2 out 5 times, compiz crashes.

I like this tool and see great potential. I post these comments to help the developer
know how it appears from a user's point of view and, to point out some bugs. I hope this
helps. And thanks for all your work.

[maniac]

First of all - thanks for the feedback! :)


nice tool
BUT damn it looks fugly,,, really needs at least some texture background.

I'm not sure I can agree to this - black-on-white still is the most reabable ;)

[quote:f0b87]
Plugin layout is nice BUT like when going into the General Options, there
are fields that are not well defined at all and seem really confusing as far
as usage. A good example of this is the "Opacity Window Values and
Opacity Windows". Theres got to be a better way of doing this AND
defining what it is.
[/quote:f0b87]
That's a matter of core's metadata - we just read this XML file and display the options accordingly.

[quote:f0b87]
There is no close button either, which sucks when
we are entering data in a field and compiz crashes, we lose deco's at this
point and there is no way to close the ccsm window.
[/quote:f0b87]
Is it that important to close CCSM at this point? ;)

[quote:f0b87]
Talking about crashes,
it happens often when entering data,,,Example: when entering the data for
Image files "which is not well defined either" in the Desktop Cube plugin, compiz
crashes. When i say it is not well defined, i am talking about having a better
description so that someone who is not familiar with things "MOST USERS", know
what it is. Is it image for top, bottom, wallpaper, what is it. Maybe use the empty
space on the left "under plugin name" to put a discription of the field you have
clicked on. Click in the Skydome field to enter data and 2 out 5 times, compiz crashes.
[/quote:f0b87]
I think another idea could be to display the long decription as a tooltip - what do you think of that?

For the crashes: Can you please try to provide a backtrace for those? The crashhandler plugin generates backtraces in /tmp/compiz-crash-<pid>.out ... just have a look at the file time and upload the matching one. This will help us in debugging the problem.

[SmSpillaz]

I must say that this is excellent work on CCSM ;-)

However - If there is one thing that I really dont like about it - it is the fact that I have to scroll on the main settings page. And the plugins are so evenly spaced and so big that it takes up a lot of screen real-estate. So instead of just having a "List" of plugins on the main page, put something more interesting there - such as "Your most recently used settings," - Quick things to configure, A slider bar like the one in bsm-- and then have a "Current information" Tab with the plugins that are/ are not enabled (Make these buttons smaller btw)

Then on the sides- have the plugin groups - Window management, effects etc.

Other than that its BRILLIANT WORK!

BTW - Put the plugins iNotify, DBUS, FUSE, Video, Regex, GConf and KConf into the "Core options" group. And Thumbnails belong in window management

[xout]

today i upgraded my gentoo-xeffects overlay. well, i recognized the new ebuild "ccsm" and didn't hesitate to emerge the package. it was compiled without errors ;)
but when i'm trying to fire up ccsm, i get the following import error:

[code:5faac]ccsm
Traceback (most recent call last):
File "/usr/bin/ccsm", line 22, in ?
import ccs
ImportError: /usr/lib64/python2.4/site-packages/ccs.so: undefined symbol: ccsStringListToEdges[/code:5faac]

is there a kind of workaround that would fix the problem?

edit: naah, just recognized, that this thread is located in the dev-section. sry for my post! should i just open a new thread in the user-section?

[maniac]

today i upgraded my gentoo-xeffects overlay. well, i recognized the new ebuild "ccsm" and didn't hesitate to emerge the package. it was compiled without errors ;)
but when i'm trying to fire up ccsm, i get the following import error:

[code:7a1e1]ccsm
Traceback (most recent call last):
File "/usr/bin/ccsm", line 22, in ?
import ccs
ImportError: /usr/lib64/python2.4/site-packages/ccs.so: undefined symbol: ccsStringListToEdges[/code:7a1e1]

is there a kind of workaround that would fix the problem?

edit: naah, just recognized, that this thread is located in the dev-section. sry for my post! should i just open a new thread in the user-section?

No problem for this small problem ;)
You have to update/recompile ccs-lib from compcomm/compiz-configuration-system/libraries/ccs-lib - but I dunno your gentoo package name for it.

[Jupiter]

I think another idea could be to display the long decription as a tooltip - what do you think of that?

For the crashes: Can you please try to provide a backtrace for those? The crashhandler plugin generates backtraces in /tmp/compiz-crash-<pid>.out ... just have a look at the file time and upload the matching one. This will help us in debugging the problem.

thank you very much for the response maniac
i think "display the long decription as a tooltip" is a great idea
and thanks for the tip on the crash handler, i will start using it when i report
bugs
other than that,,, this is a great tool to compliment compcomm

EDIT: my compcomm update finished as i finished this thread, AWESOME
thanks again for being responsive, one question, what is the "Filter" field on
the left top?

[Jupiter]

what is the proper syntax for using?
Opacity Window Value
and
Opacity Window

[maniac]

I think another idea could be to display the long decription as a tooltip - what do you think of that?

For the crashes: Can you please try to provide a backtrace for those? The crashhandler plugin generates backtraces in /tmp/compiz-crash-<pid>.out ... just have a look at the file time and upload the matching one. This will help us in debugging the problem.

thank you very much for the response maniac
i think "display the long decription as a tooltip" is a great idea
and thanks for the tip on the crash handler, i will start using it when i report
bugs
other than that,,, this is a great tool to compliment compcomm

Most likely the long description will be shown on the left pane on hovering an option :)

[quote:9297f]
EDIT: my compcomm update finished as i finished this thread, AWESOME
thanks again for being responsive, one question, what is the "Filter" field on
the left top?
[/quote:9297f]
You have to thank marex for it :)
The idea behind the filter input box is to be able to search for plugins. It's not working ATM however.

[quote:9297f]
what is the proper syntax for using?
Opacity Window Value
and
Opacity Window
[/quote:9297f]
With those two you can set the initial opacity for windows. "Opacity window" contains a list of matches and "Opacity window value" the corresponding opacity value. Obviously, you need equal number of entries in both lists ;)

[Jupiter]

[quote:8a207]
what is the proper syntax for using?
Opacity Window Value
and
Opacity Window

With those two you can set the initial opacity for windows. "Opacity window" contains a list of matches and "Opacity window value" the corresponding opacity value. Obviously, you need equal number of entries in both lists ;)[/quote:8a207]
i have been trying different combinations of window class, title, name, etc,,,
and i can't get it to work
i may not be using it properly
i enter in "Opacity Window" Name=kwrite, n:kwrite, c:Kwrite or just kwrite, i get the same error
with anything i enter
and then in Opacity Window Value i enter any number and get this error
[code:8a207]raceback (most recent call last):
File "/usr/bin/ccsm", line 329, in Add
val = self._Edit()
File "/usr/bin/ccsm", line 450, in _Edit
return e.get_text()
NameError: global name 'e' is not defined
[/code:8a207]
i get the same error if i use window types
toolbar, menu, utility, normal
so am thinking i am not using proper syntax

[maniac]

[quote:11502]
what is the proper syntax for using?
Opacity Window Value
and
Opacity Window

With those two you can set the initial opacity for windows. "Opacity window" contains a list of matches and "Opacity window value" the corresponding opacity value. Obviously, you need equal number of entries in both lists ;)
i have been trying different combinations of window class, title, name, etc,,,
and i can't get it to work
i may not be using it properly
i enter in "Opacity Window" Name=kwrite, n:kwrite, c:Kwrite or just kwrite, i get the same error
with anything i enter
[/quote:11502]
You have the following options:
type= for window type matching (e.g. type=toolbar | type=normal)[/*:m:11502]
state= for window state matching (e.g. state=skiptaskbar & state=shaded[/*:m:11502]
xid= for window X id matching[/*:m:11502]
override_redirect=0|1 for override_redirect status[/*:m:11502]
You can also form more complicated statements like ((type=normal) & (override_redirect=1)) | (state=shaded)

If you also load the regex plugin, you have more options:
class= for window class matching[/*:m:11502]
title= for window title matching[/*:m:11502]

[quote:11502]
and then in Opacity Window Value i enter any number and get this error
[code:11502]raceback (most recent call last):
File "/usr/bin/ccsm", line 329, in Add
val = self._Edit()
File "/usr/bin/ccsm", line 450, in _Edit
return e.get_text()
NameError: global name 'e' is not defined
[/code:11502]
i get the same error if i use window types
toolbar, menu, utility, normal
so am thinking i am not using proper syntax
[/quote:11502]
Oh, this looks like a bug. Will have a look into this.

EDIT: Fixed. Copy'n'Waste, as usual ;)

[Jupiter]

you'r a maniac....... thank you
i will bookmark this,,, it will help me to help others

this info WILL need to be in the new wiki
when it is up and running

[Jupiter]

works like a charm,,,, you maniac
hehe

thanks

[Jupiter]

ok next question

is there an xprop command to get X and Y position of a window
so i can use this info for the Place Window Plugin

[DarkElven]

hello, i'm a gentoo user and this are my packages i have allready installed from xeffects overlay, http://wklej.org/id/23bf11542a my problem is that if i try to run ccsm i have a little crash, strace has an output http://up.wklej.org/download.php?id=19c ... 3d585e4c22 (http://up.wklej.org/download.php?id=19ca14e7ea6328a42e0eb13d585e4c22)

[Treviño]

Running CCSM from latest git (but I'm talking about something running since about a week ) I get a "simple":
Segmentation fault (Core dumped)

What's wrong? :roll:

EDIT: A small backtrace:
[quote:f6306]Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1210406704 (LWP 29048)]
ccsContextDestroy (context=0x0) at main.c:1061
1061 if (context->backend)[/quote:f6306]
I think it should refer to libccs

EDIT2: Fixed, the ccsm problem was due to me (an old ccs-python file installed around in my system :P), the segfault has been fixed by onestone (thanks also for supporting!) :P

[Jupiter]

UPDATE:
Did an update this morning and so far with regular desktop use, I am not getting any crashes.
CCSM seems to be working very well. I am no longer experiencing any crashes when enabling
or disabling plugins. I am no longer experiencing crashes when right click title bar or cut and
paste into CCSM paths "skydome path field". It would be great to add Keeguon's tray icon
to the project. viewtopic.php?f=16&t=408 (http://forums.opencompositing.org/viewtopic.php?f=16&t=408)

Excellent progress. It seems CompComm is ready for beta testing by the users.

[franzrogar]

Jupiter, all problems you mention were due to blur and switcher plugins in Compiz. I had same issues :)

[Jupiter]

Jupiter, all problems you mention were due to blur and switcher plugins in Compiz. I had same issues :)


They seem to be fixed now.....