Some problems with beryl on OpenSuSE

[deloco]

Hi there... Once again I have a problem with Beryl...
Since Ubuntu 7.04 is available now, I thought It would be good to upgrade... So my system said goodbye and now I installed Ubuntu 7.04 and OpenSuSE 10.2.
I have not tried to install Beryl in Ubuntu since then, but in OpenSuSE.
Well... actually everything seems to work, but I don't get Beryl controlled... Istart it with a script in ~/.kde/Autostart with the following content:
[quote:1c94d]
beryl-xgl --replace &
emerald --replace &
#beryl-manager &
kiba-dock &
[/quote:1c94d]
The reason for the commented line which starts beryl-manager is that beryl-manager somehow crashes my beryl-session...
I already tried to only start Beryl-Manager (which starts Beryl automatically) but that didn't start emerald...
It's all so confusing and hard to discribe...

So my actual problem is, that I can't start beryl-manager to configure Beryl and Emerald in a cool way...

The other Problem is, that all Pop-Up-Menus (including the KDE-Menu) have an ugly fat border... I don't know how to get rid of it...

Oh and one last question: What the heck is compcomm???

[gummybearx]

i have that problem too. (the fat white borders). reloading emerald will fix it.
im in gnome, and i just started beryl-manager in sessions config. u may try to use aquamarine instead, it may be causing the crash in kde.

have u actually gotten beryl-man started sucessfully?

[deloco]

To make that clear: I don't have beryl-manager started at the moment! I start beryl and emerald seperated in the startscript, but when I run Beryl-manager in that script too, it starts beryl a second time and seems to crash it, therefore going back to normal KDE... I'll try to restart just emerald... But
maybe that solves the problem... I did that. It solves the problem. No borders. But that's no solution... I don't want to restart emerald after every reboot... I'll try now to switch the order of the startscript... Maybe that helps...

[deloco]

YEAH BOY!
Okay, reconfiguring my berylstartscript has done it!!!
It looks now like this:
[quote:e90b2]
beryl-manager &
beryl-xgl --replace &
emerald --replace &
kiba-dock &
[/quote:e90b2]
So I first start Beryl-Manager, then again Beryl and Emerald and then the kiba-dock.
I don't know yet, if it is required to restart beryl and emerald, but it now works, so I won't change the script in the near future...

@gummybearx: You should try to restart emerald in the session-manager too...
After Beryl-Manager is loaded can you add the command "emerald --replace" in the gnome-session-manager? That should restart emerald right after beryl-manger has been started and therefore ged rid of the ugly-borders...

[deloco]

Not quiet done yet...
After the systemstart this mornig the ugly fat borders are there again. Reload emerald via Beryl-Manager does the job and they're gone, but that's still no solution... I'll keep trying...

[cybertaz]

remove the transparency in the kcontrol. It should be in Kcontrol->Desktop->window behavior->transparency(?). That is KDE's attempt at transparent windows. it can, and will cause problems with Beryl.

[deloco]

Hm... I disabled the transparency of kde... Didn't change a thing...
While trying to change different things I disabled the kiba-dock (removed the kiba dock-entry in my startscript, so it looks like this:
[quote:1beb1]
beryl-manager &
beryl-xgl --replace &
emerald --replace &
[/quote:1beb1]
Any hints why the beryl-manger doesn't get loaded anymore?
I'm starting to really do not understand what's going on with my system...

[cybertaz]

have you tried this?

Making Beryl start automatically

Method 1
If you are using the KDE Desktop Environment:

Simply type (as user, not root):

ln -s /usr/bin/beryl-manager ~/.kde/Autostart/beryl-manager
ln -s /usr/bin/beryl ~/.kde/Autostart/beryl

Then remove your custom script. This creates links to the beryl and beryl-manager files. (emerald will autostart with these)

[some-guy]

you can also do
[code:66b69]beryl-xgl --replace &
emerald --replace &
beryl-manager --no-force-window-manager --no-force-window-decorator &
[/code:66b69] 8)

[deloco]

I'll try both of your Ideas... But... If it is so simple to start Beryl via symbolic links in autostart... why does every tutorial tell you to make a startscript or something like this?

[deloco]

Actually the Fisrt method, the symbolic links, start beryl, but the ugly borders are there...
The second method, beryl-manager with additional options work very well... But Beryl-Manager doesn't seem to be started :-( I really don't know what to do anymore...

Well... for now, the borders are gone and I don't need the manager that much, so it will do...