Tiny Core Linux
Tiny Core Extensions => TCE Q&A Forum => Topic started by: schultzter on October 14, 2010, 09:16:35 PM
-
I was really anxious to give LXDE a try (LXDE2 extension) and it worked great, but out of curiousity I wanted to try a few other DE's/WM's.
I tried OpenBox but I think there's configuration left-over from LXDE (which incorporates OpenBox) since not all the menu options did anything; the string "LXDE" showed-up a few times; and apps were in the menu I didn't have loading any more!
What are the configuration files that LXDE might have setup for OpenBox that I need to remove in-order start fresh with just OpenBox?
Thanks,
-
Delete ~/.config/openbox folder.
-
Cool. That worked.
I'm onto IceWM now. Not sure what I'll stick with, but I didn't like that I couldn't see anywhere which applications were running in OpenBox (IceWM and FluxBox both show the apps across the top). I imagine there's some panel I could add to OpenBox to make that happen, I might try that later.
Thanks again for you help.
-
I use tint2 with openbox. I have tried a number of others but it remains my favourite.
One day I wiil try out rox panel properly as well. puppeee linux uses that (if selected). Looks quite interesting.
-
I installed menumaker and then I typed:
mmaker -vf OpenBox3to generate the applications menu but I don't see the ondemand items :(
-
Okay, I've switched by to OpenBox (openbox.tcz and obconf.tcz) are in OnBoot in AppsAudit (and onboot.lst) and so is tint2.tcz.
But when I right-click the background to get the OpenBox menu the "OpenBox Configuration Menu" option doesn't do anything.
I notice that obconf is NOT in /usr/local/bin although according to AppBrowser's File's tab for obconf.tcz that's where it should be.
If I run the Paneltint2 application I get the Panel theming app but I have no idea how to get the panel to display on my desktop!?
Thanks,
-
Well, the OpenBox Configuration Menu is showing up now.
That doesn't seem to help me with tint2 though. I still don't have a panel anywhere on my desktop!
Any ideas anyone?!
-
I can start tint2 manually, from a terminal window, and putting it in the background keeps it running.
From the tint2 wiki (http://code.google.com/p/tint2/wiki/Install#Autorun_tint2_in_Openbox) it says to put the start-up command in openbox's autostart.sh, which I did, but it still doesn't start automatically.
Is there somewhere else I should put the command to launch tint2 so that it starts up automatically?
Thanks,
-
.X.d/ is the directory for additional items to start at X startup. It is sourced in .xsession.
Create file .X.d/tint2 which contains the single line tint2.
It will start backgrounded when X starts. You can Exit to Prompt and then type startx to try this.
-
Yes put it in .X.d and remember to add '&' to the command.
Openbox's autostart command is not invoked because of the particular generic way of invoking window managers in tinycore. I have puzzled a bit about it but couldn't see an obvious solution. Perhaps one exists but my very limited script programming prevents me from seeing one.
-
Good evening...
I did as roberts said and added a file .X.d called tint2 with a single line/word in it "tint2" and re-started X and it worked.
The file is NOT executable but it is readable by all.
There is no ampersand after the tint2 in the file, it seems to work fine.
Thanks for your help.
BTW, is some doc on the boot sequence of TC and what's so particular about how window managers/desktop's are started?
-
Look at .profile.
-
Look at .profile.
Was that in response to my question about the boot sequence or the particularities of how TC starts window managers?
I can see from the last four lines of .profile how it checks three things then (typically) runs startx, which does a bit more prep work and then (presumably) launches .xsession.
I'm going to have review it a bit more. But I'm surprised that autostart.sh isn't called once openbox is executed - assuming it's part of the openbox-way and not a standard.
-
Typically openbox gets called by openbox-session.sh which calls autostart.sh. However, the generic handling of window managers in tcl handles only the base name of a window manager - there is no provision for the -session tacked on to the end.
Perhaps it would be as simple as renaming some files, I don't know, or using aliases.