Upgrade from 3.5.5 to 3.5.7 now my KPowersave & KNetworkManager will not dock

Ever since I upgraded from KDE 3.5.5 to 3.5.7 on my openSuSE
10.2 box the 
KPowersave and KNetworkManager consistently do not dock
themselves into the 
system tray. Once I close just KNetworkManager and reopen
it, it will then 
dock and KPowersave will magicly follow. 

The only thing I have in ~/.kde/Autostart is: 

cat .kde/Autostart/startberyl.sh
#! /bin/sh
rm ~/.beryl-managerrc
beryl-manager
beryl --use-copy

Also, my SuperKaramba's on my desktop do not always come up,
but this is NOT 
consistent, sometimes they come up and sometimes they don't.


superkaramba --version
Qt: 3.3.8
KDE: 3.5.7 "release 52.1"
SuperKaramba: 0.42

beryl --version
beryl-core 0.2.0

Any help avalible is greatly appreciated. 

-- 
How much can you know about yourself, you've never been in a
fight? I don't 
wanna die without any scars. So come on; hit me

___________________________________________________
This message is from the kde-linux mailing list.
Account management:  http
s://mail.kde.org/mailman/listinfo/kde-linux.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.h
tml.

On Thursday 12 July 2007, Ben Kevan wrote:
> Ever since I upgraded from KDE 3.5.5 to 3.5.7 on my
openSuSE 10.2 box the
> KPowersave and KNetworkManager consistently do not dock
themselves into the
> system tray. Once I close just KNetworkManager and
reopen it, it will then
> dock and KPowersave will magicly follow.
>
> The only thing I have in ~/.kde/Autostart is:
>
> cat .kde/Autostart/startberyl.sh
> #! /bin/sh
> rm ~/.beryl-managerrc
> beryl-manager
> beryl --use-copy
>
> Also, my SuperKaramba's on my desktop do not always
come up, but this is
> NOT consistent, sometimes they come up and sometimes
they don't.

You could try to start Beryl right away instead of first
starting with KWin 
and then later replacing it with a different window
manager.

The KDE startup script startkde will start whatever program
the environment 
variable KDEWM points to and only start KWin if the variable
is not set.

You can set this variable either somewhere globally
(depending on your 
distribution) or through KDE's environment extenter
mechanism.

For doing the latter, create a file with .sh extension in
$HOME/.kde/env/ 
(might need to create this directory) and set KDEWM to
whatever executable 
starts beryl.

Cheers,
Kevin

-- 
Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring

___________________________________________________
This message is from the kde-linux mailing list.
Account management:  http
s://mail.kde.org/mailman/listinfo/kde-linux.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.h
tml.

On Thursday 12 July 2007 10:13:41 am Kevin Krammer wrote:
> On Thursday 12 July 2007, Ben Kevan wrote:
> > Ever since I upgraded from KDE 3.5.5 to 3.5.7 on
my openSuSE 10.2 box the
> > KPowersave and KNetworkManager consistently do not
dock themselves into
> > the system tray. Once I close just KNetworkManager
and reopen it, it will
> > then dock and KPowersave will magicly follow.
> >
> > The only thing I have in ~/.kde/Autostart is:
> >
> > cat .kde/Autostart/startberyl.sh
> > #! /bin/sh
> > rm ~/.beryl-managerrc
> > beryl-manager
> > beryl --use-copy
> >
> > Also, my SuperKaramba's on my desktop do not
always come up, but this is
> > NOT consistent, sometimes they come up and
sometimes they don't.
>
> You could try to start Beryl right away instead of
first starting with KWin
> and then later replacing it with a different window
manager.
>
> The KDE startup script startkde will start whatever
program the environment
> variable KDEWM points to and only start KWin if the
variable is not set.
>
> You can set this variable either somewhere globally
(depending on your
> distribution) or through KDE's environment extenter
mechanism.
>
> For doing the latter, create a file with .sh extension
in $HOME/.kde/env/
> (might need to create this directory) and set KDEWM to
whatever executable
> starts beryl.
>
> Cheers,
> Kevin

Thank you Kevin for the response. I must add, that even when
I am not starting 
using Beryl, I also have the same issue, but seems to really
only not dock 
the KNetworkManager and not both KNetworkManager and
KPowersave. 

Also, with setting up Beryl as the WM, would it allow me to
run 
beryl --use-copy as a command, or will it only except beryl?
Also, would 
beryl-manager still have to be run via script to start? 

Thanks

Ben

Ben

-- 
How much can you know about yourself, you've never been in a
fight? I don't 
wanna die without any scars. So come on; hit me

___________________________________________________
This message is from the kde-linux mailing list.
Account management:  http
s://mail.kde.org/mailman/listinfo/kde-linux.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.h
tml.

On Thursday 12 July 2007 10:13:41 am Kevin Krammer wrote:
> On Thursday 12 July 2007, Ben Kevan wrote:
> > Ever since I upgraded from KDE 3.5.5 to 3.5.7 on
my openSuSE 10.2 box the
> > KPowersave and KNetworkManager consistently do not
dock themselves into
> > the system tray. Once I close just KNetworkManager
and reopen it, it will
> > then dock and KPowersave will magicly follow.
> >
> > The only thing I have in ~/.kde/Autostart is:
> >
> > cat .kde/Autostart/startberyl.sh
> > #! /bin/sh
> > rm ~/.beryl-managerrc
> > beryl-manager
> > beryl --use-copy
> >
> > Also, my SuperKaramba's on my desktop do not
always come up, but this is
> > NOT consistent, sometimes they come up and
sometimes they don't.
>
> You could try to start Beryl right away instead of
first starting with KWin
> and then later replacing it with a different window
manager.
>
> The KDE startup script startkde will start whatever
program the environment
> variable KDEWM points to and only start KWin if the
variable is not set.
>
> You can set this variable either somewhere globally
(depending on your
> distribution) or through KDE's environment extenter
mechanism.
>
> For doing the latter, create a file with .sh extension
in $HOME/.kde/env/
> (might need to create this directory) and set KDEWM to
whatever executable
> starts beryl.
>
> Cheers,
> Kevin

Thank you Kevin for the response. I must add, that even when
I am not starting 
using Beryl, I also have the same issue, but seems to really
only not dock 
the KNetworkManager and not both KNetworkManager and
KPowersave. 

Also, with setting up Beryl as the WM, would it allow me to
run 
beryl --use-copy as a command, or will it only except beryl?
Also, would 
beryl-manager still have to be run via script to start? 

Thanks

Ben

Ben

-- 
How much can you know about yourself, you've never been in a
fight? I don't 
wanna die without any scars. So come on; hit me

___________________________________________________
This message is from the kde-linux mailing list.
Account management:  http
s://mail.kde.org/mailman/listinfo/kde-linux.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.h
tml.

On Friday 13 July 2007, Ben Kevan wrote:

> Thank you Kevin for the response. I must add, that even
when I am not
> starting using Beryl, I also have the same issue, but
seems to really only
> not dock the KNetworkManager and not both
KNetworkManager and KPowersave.

Hmm, weird.

> Also, with setting up Beryl as the WM, would it allow
me to run
> beryl --use-copy as a command, or will it only except
beryl? Also, would
> beryl-manager still have to be run via script to
start?

I am afraid I don't know. Haven't used Beryl myself. You
probably will still 
have to start it, though you can also do this in the
extender script, since 
everything in it will be executed just like any other part
of startkde

Cheers,
Kevin

-- 
Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring

___________________________________________________
This message is from the kde-linux mailing list.
Account management:  http
s://mail.kde.org/mailman/listinfo/kde-linux.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.h
tml.