Greetings everyone! I just browsed the forum here and didn't find any threads for this. I've just switched from KDE to Fluxbox. It's not that I don't like KDE, I just wanted to use something that starts faster and uses fewer resources. And since FB has KDE support I can still use my kicker panel and run most KDE programs. I think my question is simple and I'm probably overlooking the answer. This is on a laptop so I'm trying to run klaptop_check when FB starts. Here is my ~/.fluxbox/apps file

[startup] {aumix -L}
[startup] {xscreensaver -no-splash &}
[startup] {kicker}
[startup] {klaptop_check}

aumix, xscreensaver and kicker start correctly, but klaptop doesn't. I keep having to open an xterm and type klaptop_check manually. I noticed that wether it's running or not it doesn't appear in a ps x list. Is that correct?

The laptop is a HP Pavilion ze4315 running Slackware 10.1 (with all the security updates), KDE 3.4.2 and Fluxbox 0.9.13. Need to know anything else?

Thanks!

I don't know if this will help at all, but you could try putting in your ~/.fluxbox/startup file. That's another place that fluxbox will look for startup programs.

Thank you for the quick reply. I have tried that before. I tried having klaptop and xscreensaver in the startup file but it seemed to do nothing. That was before I added kicker and aumix. It's worth trying again so I will.

Funny thing - I just turned my laptop on again a while ago. When I started kdm, logged in and loaded Fluxbox, I actually got an error message related to klaptop. I don't remember the exact words (should've written it down) but the gist was that it couldn't load because a network dcopserver wasn't running. But it loaded anyway and this time failed to load the xscreensaver daemon. I wonder, could the [startup] order have some affect? Or is there another KDE background component required? Maybe somebody knows a better laptop battery status daemon that I could use.

Well, I tried using the ~/.fluxbox/startup file again with no success. Just like the first time I tried, none of what I put in it gets started. It's as if Fluxbox ignores the startup file. So it's back in the apps file where it at least autostarts once in a while. Kicker, aumix and xscreensaver all autostart fine everytime, but klaptop is still being fussy. It still only produced a message that one time. Launching it from an xterm always works fine. Any ideas why won't it autostart properly? Any suggestions for better laptop battery status monitors?

Hi,

maybe here are some ways to solve your problem:
if you start your x-window-system with "xinit" or "startx" you can use the file /home/user/.xinitrc which looks a bit like this:

fbpager &
gkrellm &
fluxbox startup

if you start your xwindowsystem with a diplay manager (eg. xdm) you use the same content and put in /home/user/.xsession
Don't forget the "&" if an application should stay on the desktop.


Hope it helps.

Viele Grüße
Arvid

PS: Also a nice tool to see battery-status is gkrellm

Thanks. I've tried loading klaptop in .fluxbox/apps, .fluxbox/startup, .xsession and now .xinit. It just refuses to load with the desktop.

I didn't know I already had gkrellm. It's pretty cool and starts properly from .fluxbox/apps so I'll use it. It starts faster than klaptop (doesn't have to load all those libs) so that's even more appropriate for Fluxbox.

Nothing really runs from the startup file? Only thing I can think of is that your startup file is either incorrect or it does not have execute permissions...

You could try launching KDE and checking which background programs it starts... then launch them in the order they are launched in KDE, if possible.

Thanks for the idea. the .x files are executable and have proper permissions. The other listed programs load: aumix and xscreensaver. klaptop has always worked fine in KDE. gkrellm works fine in Fluxbox. I'm happy with this setup. After getting more used to Fluxbox I think I'd rather not use KDE programs as they require more overhead.