The itask guy mentioned emerald in his instructions and the demo video shows the emerald mgr flipping around with other apps.

Really? Well, he should know I suppose.

I'm not sure ( I don't have it installed at the moment, but I think emerald relies on libdecoration.so, which on my system is broken ( it's got a recursive dependancy on itself ). This breaks a number of plugins too. revdep-rebuild picks it up. Maybe this is why emerald doesn't work? I don't know. I've never tried. But seriously, E's got loads more functionality than emerald. Port the theme _________________David Hicks' plea. Was it:

a) I plead guilty, or
b) Please let me out of here and end the torture

The itask guy mentioned emerald in his instructions and the demo video shows the emerald mgr flipping around with other apps.

Really? Well, he should know I suppose.

I'm not sure ( I don't have it installed at the moment, but I think emerald relies on libdecoration.so, which on my system is broken ( it's got a recursive dependancy on itself ). This breaks a number of plugins too. revdep-rebuild picks it up. Maybe this is why emerald doesn't work? I don't know. I've never tried. But seriously, E's got loads more functionality than emerald. Port the theme

Just a fwiw, I sent him an email and he says emerald definitely works in ecomp (I guess for shadows or whatever) but stopped working on his nvidia card recently (said ati is still ok). I was hoping to try that (but have an nvidia card) because using dropshadow module I get ghost shadows from each app on all the desktops it's not on

I also asked why most of my sticky stuff wasn't stuck and he said it was a code error so I reinstalled and that fixed it.

He also said changing compiz plugins to "ecomp" is all it takes to use them but I tried every unlisted ecomp plugin in compiz-fusion and none did anything (he said there's no guarantee any of the others would work anyway so I was mostly just hoping).

I've just set up a brand new system ( which I was going to clone around the office ) and installed ecomorph, but the damned desktop plugins won't reliably load. Initially I wanted cube & cube rotate, but now I'd just settle for *any* of the desktop plugins.

At the moment, if I start E from a login manager, it always skips the desktop plugins, so when I switch to another desktop, all the windows from all other desktops are still visible ( as E's being started with the -evil switch ).

If I start E from a console, most of the time the desktop plugins don't activate. But if I kill ecomorph and restart it, one will *sometimes* load.

I've had similar+other problems including both of yours (some things would work at login and others wouldn't but if I killed ecomorph after I logged in and restarted it then everything I have set in it works; or whatever is on one desktop is duplicated on all the other desktops (incl non-sticky stuff) even though pager shows desktops are changing).

I installed using the itask/ecomorph instructions this last time, not the ebuild; just reinstalled everything a couple days ago.

I use entrance and login as non-root (nvidia card/released prop driver). I changed the session file to just

and now run "/usr/local/bin/ecomorph ccp dbus > /dev/null &" from a csh startup script that e17 runs at login; everything seems to run fine this way.

One thing I've noticed is I have to be careful which plugins I use and which options in them I alter (defining a skydome in cube distorts the uncubed desktop, stops expo from working, etc.). I've also noticed some undefined conflicts w/a couple other plugins enabled (forgot which but it made ring switcher act like a second shift switcher, etc.).

Many of the plugins don't seem to do anything and others are fragile and cause other problems so once I got things settled I don't really fiddle with them. It's more or less "ok, how much can I get away with before stuff breaks" and once I hit it I stop messing with them

I mention that in case your problem is rooted in a plugin conflict; if it helps to try my default.ini as an experiment let me know and I'll post/pm it.

edit: incidentally I installed compiz-fusion+emerald, emerald starts but doesn't do anything, so removed both and my setup is just the layman e17 overlay + the ecomorph web page installs if it matters.

sometimes windows appear in a blank white - but if i click on the places where normaly the buttons.. are it works
so i could iconify and enlarge the window - sometimes the started application appear as it should do

swithching to next desktop shows a lot of shaddows from the opened windows on the other desktop

itask-ng gives sometimes a blank white space from left to right screen
the hight is the maximumscale from the icons

die-hard, I was with those problems too. If I install eet-1.0 it complains about libeet.so.0, if I install eet-0.* it complains about libeet.so.1

I installed the newest version and manually installed the old one into /usr/local, then symlinked the lib to /usr/lib. No complainings anymore _________________"Nolite arbitrari quia venerim mittere pacem in terram non veni pacem mittere sed gladium" (Yeshua Ha Mashiach)

Hi everyone! I'm pretty bad at this stuff, but I always wanted to try compiz (and didn't want to give up my e), so I was excited to hear about this. But I must be doing something wrong. I got the ecomorph stuff off of layman following gimpel's layman instructions. From my understanding, this not only included ecomorph, but the modified e-r1 that was prepared for ecomorph by gimpel. Anyway, so when I tried to merge ecomorph, it got git and its deps first (these seem to work fine), but the new e fails. The error message seems quite long, and I'm not sure exactly what went wrong. Is it okay if I get ecomorph without the new e, or will it not work at all? This is what e gives me when I try to get the new one (which it seems git is getting):

You can edit "po" out of the "SUBDIRS" line in either Makefile or Makefile.am if you want; that will stop it from building and bypass whatever the problem is. I think they're language files or some crap so if you're english it shouldn't make any difference.

Probably would be best to cut it from Makefile.am before the makefiles are generated (in case "po" is propagated elsewhere). I didn't use the ecomorph ebuild so don't know how you'd catch it if it's rolled in amongst other pkgs - maybe just watch the screen? It's possible to ctl-z just as the problem pkg is untar'd, make the edit, save, then "fg".

What I'd do if this was a stand-alone thing or if ecomorph ebuild will accept that it's been installed and not re-do it, is to "ebuild <path to problem ebuild> unpack", go to the unpacked dir, edit/save Makefile.am. Then "ebuild <> compile" and "ebuild <> merge". Proceed w/ecomorph merge from there.

Thanks nordic bro. If it's a language problem, I think I may know what caused it. I've been having minor locale bugs since I set up my system for Japanese input. It's never caused any problems, as it always just says it falls back to the standard locale ("C" or POSIX). I wonder if that's what's causing this problem? I'll try and sort it out, and if it's still a problem, I'll try editing out the line in the makefile like you suggested.

Not a language problem per se but IMM something in the tar itself is broken. In years of compiling stuff on my own, those infrequent times I hit a snag it is invariably something to do with po files. The whole thing is fragile or error prone or aren't checked well or who knows what. So while I'd be surprised if there's anything in your env that can get around this (and would like to hear if you get it going that way), most likely you will need to compile around it.

VanDan, I'm with the very same problem that you're having. It all used to work some time ago... but now I get only this bugged cube =P_________________"Nolite arbitrari quia venerim mittere pacem in terram non veni pacem mittere sed gladium" (Yeshua Ha Mashiach)

ecomorph code afaik hasn't been updated in months and e17 has. it's most likely you are never going to get it to compile/work as-is.

looks like ecomorph has been updated for newer e17 code; start at the first msg after "aug 22" (I'm guessing you will need to do this by hand, not an ebuild). I haven't updated e for months so I think I'm going to give this a try too - should be 'fun'

since I brought this up last I figure I should add that he's changed the list of msgs on his site.

last night when he posted the new tars his notice was the last msg on the link. this morning when I looked there were a bunch of problems ppl had that followed his notice.

now I looked again and he's removed all those posts of problems and again his notice is the final msg. sounds like he moved those problem posts to the "issues" tab so ppl will probably want to be sure to look through those before starting.

edit: hmm, I don't see any of the problems in issues tab that ecomorph ppl were posting since last night; maybe they were just nimrod problems the user(s) got sorted out on their own. or it was fixed in the compiz tar which has a little bit newer of a timestamp than the rest.

* This is a LIVE SOURCES ebuild.
* That means there are NO promises it will work.
* If it fails to build, FIX THE CODE YOURSELF
* before reporting any issues.
*
* ERROR: x11-wm/e-9999-r1 failed.
* Call stack:
* ebuild.sh, line 49: Called src_unpack
* environment, line 2771: Called git_src_unpack
* environment, line 2167: Called git_fetch
* environment, line 2149: Called die
* The specific snippet of code:
* ${EGIT_UPDATE_CMD} ${EGIT_OPTIONS} origin ${EGIT_BRANCH}:${EGIT_BRANCH} || die "${EGIT}: can't update from ${EGIT_REPO_URI}.";
* The die message:
* git.eclass: can't update from git://staff.get-e.org/users/jeffdameth/e.git.
*
* If you need support, post the topmost build error, and the call stack if relevant.
* A complete build log is located at '/var/tmp/portage/x11-wm/e-9999-r1/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/x11-wm/e-9999-r1/temp/environment'.
*
VaioTux e #