Help - Search - Members - Calendar
Full Version: Oops...xinitrc
OESF Forums > Distros, Development, and Model Specific Forums > Distro Support and Discussion > pdaXrom
T3_slider
Well, I seem to have messed up Openbox by installing fluxbox. I installed the theme package in one of the threads and it felt the need to hijack my .xinitrc (I was going to have an xinitrc.fluxbox and a startfluxbox like I have for XFCE). Since I can't seem to find the default .xinitrc for openbox anywhere, could someone help me out and post theirs? It seems like a waste to reflash just when I got everything running perfectly when I could simply replace the .xinitrc (and although I could make a new .xinitrc and get it up and running, I'm not good enough to get it to the exact state it started in).

I would be eternally grateful if someone could help me out...(and I would make a backup of it in case this happened again!)
Jon_J
I would help, but where is it located?
I have pdaxii13
Meanie
QUOTE(T3_slider @ Feb 11 2007, 11:31 AM)
Well, I seem to have messed up Openbox by installing fluxbox. I installed the theme package in one of the threads and it felt the need to hijack my .xinitrc (I was going to have an xinitrc.fluxbox and a startfluxbox like I have for XFCE). Since I can't seem to find the default .xinitrc for openbox anywhere, could someone help me out and post theirs? It seems like a waste to reflash just when I got everything running perfectly when I could simply replace the .xinitrc (and although I could make a new .xinitrc and get it up and running, I'm not good enough to get it to the exact state it started in).

I would be eternally grateful if someone could help me out...(and I would make a backup of it in case this happened again!)
*


the default matchbox .xinitrc is actually /usr/bin/mbsession
.xinitrc is just a symlink to it, so just symlink it back
T3_slider
Thanks so much Meanie -- your infinite wisdom never ceases to amaze me. ;-)

And thank-you for offering your help, Jon_J.
radiochickenwax
Did you get fluxbox to run on the 3200? How long did it take to load?

I'm having a similar problem in this thread:

http://www.oesf.org/forums/index.php?showtopic=23202

... fluxbox loads, but takes maybe 5 minutes or so... and only the older version (0.9.10) works for me.
T3_slider
Fluxbox does load, but it takes about 1 minute and 20 seconds (Not as long as you describe, but still quite long). I think I'm going to abandon fluxbox because there isn't really a speed increase compared to XFCE. IceWM, however, is blazingly fast, so I plan on using XFCE for normal use and IceWM for heavy-duty stuff that doesn't run smoothly or quickly on XFCE (and KDE occasionally when I have some free time).
Capn_Fish
I compiled my own Fluxbox on r121, and it loads in ~15 seconds with Feh and Torsmo. You could try doing the same, it's really easy.

Alternatively, I could post my package, should anybody care to try it. No guarantees dor 2.4.x kernels, but it may work.
Capn_Fish
I forgot to say that changing the theme from Sn33z to some other theme I got seemed to make it load much faster.
scheck.r
Same here on beta3, it takes ~12 seconds to load and I am using Sn33z theme. So something must be wrong in your setup. I am using the latest package from here:
http://www.oesf.org/forums/index.php?showtopic=21726&st=30
I also tried IceWM and both have the same speed, I measured the time to load a bunch of software and it takes exactly the same amount of time.
radiochickenwax
QUOTE(Capn_Fish @ Feb 11 2007, 06:47 PM)
I compiled my own Fluxbox on r121, and it loads in ~15 seconds with Feh and Torsmo. You could try doing the same, it's really easy.


I did compile it. No speed increase in beta3 or pdaxii13.

QUOTE(T3_slider @ Feb 11 2007, 06:18 PM)
Fluxbox does load, but it takes about 1 minute and 20 seconds (Not as long as you describe, but still quite long).


The only version that works for me is 9.10 as I mentioned in the other thread. I think I probably had similar load times in beta3 on my 3200, but since I've been using pdaxii13, fluxbox is a lot slower, and everything else is a lot faster.

I had a lot of packages on CF and SD, and that would take about five minutes for "ipkg-link" to figure out on every card insert.

After switching to pdaxii13, where most packages are installed on the internal microdrive, the "ipkg-link" wait-time is reduced to nearly nothing. But fluxbox is that much slower. This is the only program that seems so much slower for me.

It's really frustrating because I just can't bring myself to embrace openbox, which runs very smoothly. It gets in my way for all kinds of things.

I'm an electrical engineering student in university, and I do almost all of my school work on my Zaurus. I spend a lot of time taking screenshots of my notes and books which are heavily ridden with diagrams and mathematical typography that just isn't possible to represent in ASCII without TeX formatting So I spend a lot of time with LaTeX and DVIPNG compiling toolchains, and this is sometimes just too slow compared to just using:

CODE
import Equation098.png


Which lets me take screenshots of just tiny little rectangles in my display that I won't have to crop later on.

Openbox (or XFCE) won't let me switch windows around very easily without displaying a lot of useless information such as which workspace I'm on and what the title of the window is that I just switched to, whereas "lighter" window managers such as blackbox, twm, or fluxbox just stay out of my way.

I'm sure there are some configuration options to change this behavior in openbox, but I already spend what I feel is far too much time RTFMing when I have a lot of higher priority tasks, and fluxbox, used to just work for me, whereas as of beta3, it's a little annoying.

I used to use blackbox way back when... I used this for WinXP a lot too. Click here if you're interested. But I've since grown really accustomed to fluxbox's tabs, and it's kinda difficult for me to go without them.

Besides, I can't find the "bbkeys" package anywhere, and it seems to refuse to build from source code for me right now, without recompiling the blackbox source code, which I spent awhile last night trying to do, but ultimately gave up on after a lot of errors on "iconv".

QUOTE(Capn_Fish @ Feb 11 2007, 06:47 PM)
No guarantees dor 2.4.x kernels, but it may work.


I've been putting off upgrading to rc121 until it seems a little more stable. Looks like my best bets for now are just to switch back to standard beta3 or learn to deal with openbox.

Well, hopefully that's not too much ranting for you all. Thank you for your input everyone, it does help a lot. Please keep me informed (on this thread) if you use pdaxii13 on a 3200 with fluxbox.
Capn_Fish
What about IceWM? It's pretty light, especially if you don't use the ROX desktop. I find it to be fairly similar to Fluxbox.
radiochickenwax
QUOTE(Capn_Fish @ Feb 11 2007, 10:52 PM)
What about IceWM? It's pretty light, especially if you don't use the ROX desktop. I find it to be fairly similar to Fluxbox.
*


IceWM is fast, but it doesn't support tabbing.

See
http://fluxbox.sourceforge.net/docbook/en/html/x234.html

and

http://en.wikipedia.org/wiki/Tabbed_document_interface

Fluxbox is the probably best for this IMHO. Can open lots of programs in a single window, and reconfigure their placements etc. Also supports automatic resizing of overly large windows.

I've compiled devil's pie

http://www.burtonini.com/blog/computers/devilspie

which I'm trying to incoporate with blackbox, but this still isn't quite the same (yet).
Also, I'm fairly certain FVWM can do tabs as I've seen in this document

http://fvwm.lair.be/viewtopic.php?t=724&si...ba12f561cbf3a8e

...but that seems like a lot to setup, whereas in fluxbox it just works. Also, I think FVWM is due for a rebuild on pdaxrom, and I'm not about to try that just yet.

I flashed back to beta3 by the way, and fluxbox does load up in about 1-2 minutes, but like T3_Slider said:

QUOTE(T3_slider @ Feb 11 2007, 06:18 PM)
Fluxbox does load, but it takes about 1 minute and 20 seconds (Not as long as you describe, but still quite long).


I don't know what pdaxii13 does to make this take so much longer, but it does something. However, the amount of things that pdaxii13 fixes for me outweighs the single thing it's broken so far... which is just fluxbox. So I'm back to my original starting point, of trying to either find a different WM, or learning to deal with openbox.
Jon_J
QUOTE(Meanie @ Feb 10 2007, 08:48 PM)
QUOTE(T3_slider @ Feb 11 2007, 11:31 AM)
Well, I seem to have messed up Openbox by installing fluxbox. I installed the theme package in one of the threads and it felt the need to hijack my .xinitrc (I was going to have an xinitrc.fluxbox and a startfluxbox like I have for XFCE). Since I can't seem to find the default .xinitrc for openbox anywhere, could someone help me out and post theirs? It seems like a waste to reflash just when I got everything running perfectly when I could simply replace the .xinitrc (and although I could make a new .xinitrc and get it up and running, I'm not good enough to get it to the exact state it started in).

I would be eternally grateful if someone could help me out...(and I would make a backup of it in case this happened again!)
*


the default matchbox .xinitrc is actually /usr/bin/mbsession
.xinitrc is just a symlink to it, so just symlink it back
*


I have pdaxii13-akita5.3.4 on NAND only.
I just installed iceWM_1.2.30 and iceWM-pdaxrom and dependencies and I couldn't get it to start.
It just tried starting X, then would drop back to the console.
I couldn't get it running and was now without a GUI. sad.gif
I read this thread:
Icewm- How Do I Start It?
http://www.oesf.org/forums/index.php?showtopic=21044&hl=

The advice there didn't help either, then I found this thread that I'm replying to now.
I decided to rename /home/root/.xinitrc to .xinitrc2, then made a new symlink as meanie suggested.
I am now able to get back into the matchbox/rox GUI. smile.gif
At first I tried just creating the symlink as meanie suggested, but got a message that this symlink already existed.
This is why I renamed the original one, (which iceWM had symlinked to it's own file, "icewm-session")
I then uninstalled all iceWM related stuff and the one dependency that I needed for it.
I'll try iceWM later when I know more about changing window managers.
Capn_Fish
Have you tried the .xinitrc files that I posted in the ultimate ICEWM configuration thread? icewm-session seems to not work...so avoid using theicewm-pdaxrom package.
Jon_J
I wasn't sure how or what to install, so I just installed icewm_1.2.30_armv5tel.ipk
It didn't seem to work, and I wasn't sure of it's dependencies, so I looked at the packages file in the feed (mail.pdaxrom.org-1.1.0beta1-C1000-C3100) and installed imlib and icewm-pdaxrom. Those were the only dependencies that I didn't already have installed.
It doesn't uninstall cleanly either. I found a file remaining in my /usr/bin folder called ice-session (not sure of the correct name now, it was created by icewm, but it is not in either of the above 2 *.ipks)
It was causing some odd behavior in ROX. Every time I opened and closed my /mnt/cf folder it asked if I wanted to unmount it. This behavior never happened before.
I also wasn't able to retain my bold fonts settings in gtk-switch that controls the fonts in ROX folders and dialogs.
Capn_Fish
Try reinstalling just ICEWM & imlib, NOT icewm-pdaxrom, then use one of the .xinitrcs I posted...see if that lets you get into it.
Jon_J
I have it running by using the second .xinitrc file you posted.
There is only a small taskbar, and I cannot seem to be able to find my programs or filesystem.
I have some questions.
I scrolled through the menu choices, but all the entries are empty. Shouldn't my programs, and/or categories be visible, such as "Office" Games" "System" ?
I guess I need to download the entire manual and read it.
How do I get back to ROX/openbox and back to icewm?
It saves a lot of space with the narrow taskbar.
Do I need to re-read that icewm thread to access my programs with the "Menu" key on the Zaurus?
It looks nice, but there is no wallpaper. Like I said, I need to figure this out, the main thing is how to switch back and forth from iceWM to ROX and back.

EDIT: I went back to ROX/openbox in the meantime. I'll read up on iceWM.
Do you know how I can download the iceWM manual? It's a bunch of linked pages, I wish it was all on one page or a PDF.
This is how I am switching back and forth for now.
I keep 2 copies of my (openbox symlink .xinitrc as 2 different filenames)
I also have (iceWM .xinitrc as a different name)
When I want to switch, I just exit X, then rename the appropriate file and type startx
Capn_Fish
I think there's a binary called icewmbg, or something like that, that will set a background.

The easiest way to switch between WMs, IMO, is to copy the startx script to a script called startx2, then edit the copy to look for .xinitrc2 instead of .xinitrc (you can obviously change names as you see fit).

I don't know about the programs issue...It worked fine for me. It may have something to do with icewm-pdaxrom.

Hope that helped.
Jon_J
QUOTE(Capn_Fish @ Apr 6 2007, 09:50 PM)
I don't know about the programs issue...It worked fine for me. It may have something to do with icewm-pdaxrom.
*

I didn't install icewm-pdaxrom, as you suggested.
Capn_Fish
QUOTE(Jon_J @ Apr 6 2007, 09:52 PM)
QUOTE(Capn_Fish @ Apr 6 2007, 09:50 PM)
I don't know about the programs issue...It worked fine for me. It may have something to do with icewm-pdaxrom.
*

I didn't install icewm-pdaxrom, as you suggested.
*


I was referring to the previous installation...No idea if it may have done something, but you never know. I'm mostly guessing.
Jon_J
QUOTE(Capn_Fish @ Apr 6 2007, 09:50 PM)
The easiest way to switch between WMs, IMO, is to copy the startx script to a script called startx2, then edit the copy to look for .xinitrc2 instead of .xinitrc (you can obviously change names as you see fit).
*

I'm looking at a second copy of startx
Do I rename all instances of .xinitrc in this file?
I found 2 places where .xinitrc is referenced.
I'm thinking the only one that needs edited is this one, am I correct?
"userclientrc=$HOME/.xinirtc"

Thanks again, I'll fiddle with this some more and see if I can get it to work the way it should.
Capn_Fish
QUOTE(Jon_J @ Apr 6 2007, 10:10 PM)
QUOTE(Capn_Fish @ Apr 6 2007, 09:50 PM)
The easiest way to switch between WMs, IMO, is to copy the startx script to a script called startx2, then edit the copy to look for .xinitrc2 instead of .xinitrc (you can obviously change names as you see fit).
*

I'm looking at a second copy of startx
Do I rename all instances of .xinitrc in this file?
I found 2 places where .xinitrc is referenced.
I'm thinking the only one that needs edited is this one, am I correct?
"userclientrc=$HOME/.xinirtc"

Thanks again, I'll fiddle with this some more and see if I can get it to work the way it should.
*


I think that's the only one I changed (I have a Fluxbox/JWM setup).

EDIT: You only need to edit one; the other is commented out anyway (you could chage it for consistency).
Jon_J
That worked, thank you. Now I only need to figure out how to get my apps, taskbar, folders on desktop, and the Zaurus "Menu" key working.
Right now, the only thing that I can do is change the themes available for the menu and taskbar.
This doesn't seem as easy to use as ROX. I wonder if mimetypes are working? That doesn't matter now anyway because I cannot browse my files outside a terminal.
EDIT:
I'm able to launch applications in the terminal, (that is if I can remember the name of the executable...)
desertrat
QUOTE(radiochickenwax @ Feb 12 2007, 12:00 AM)
IceWM is fast, but it doesn't support tabbing.

See
http://fluxbox.sourceforge.net/docbook/en/html/x234.html

Excuse my ignorance but what exactly does tabbing do? From what I could make out it allows you to group arbitrary sets of programs into tabbed windows. If so, I really can't see any huge useability benefits - can someone enlighten me?

QUOTE
I don't know what pdaxii13 does to make this take so much longer, but it does something.

Just a wild guess, it rebuilds the menus each time you start? I know thats what icewm in official feed does (until I fixed it smile.gif).
radiochickenwax
QUOTE(desertrat @ Apr 7 2007, 07:37 AM)
QUOTE
I don't know what pdaxii13 does to make this take so much longer, but it does something.

Just a wild guess, it rebuilds the menus each time you start? I know thats what icewm in official feed does (until I fixed it smile.gif).
*



I was actually referring to fluxbox, not icewm in a different thread:

http://www.oesf.org/forums/index.php?showt...3202&hl=fluxbox



QUOTE(desertrat @ Apr 7 2007, 07:37 AM)
QUOTE(radiochickenwax @ Feb 12 2007, 12:00 AM)
IceWM is fast, but it doesn't support tabbing.

See
http://fluxbox.sourceforge.net/docbook/en/html/x234.html

Excuse my ignorance but what exactly does tabbing do? From what I could make out it allows you to group arbitrary sets of programs into tabbed windows. If so, I really can't see any huge useability benefits - can someone enlighten me?
*



I don't about *enlightening* you...smile.gif but I'll tell you what it does for me. Say I have 5 windows open in gimp, Maybe the main window, tool options, color palette, etc... it's pretty common for me to find myself in such a situation.

Using fluxbox tabs, I can contain all of those windows into a bar. Now, let's say that I've also got 3 more xpdf windows open, because I need to find info from 3 books on the same or similar subject. So I put all of those windows together into a bar.

Now I've apparently only got two windows open, and I can cycle between them using Alt+Tab, however, inside of each window is an additional set of windows that I can cycle through using Meta+Tab.

It's sorta like virtual desktops, but instead of using workspaces, it uses the same one. It's probably not for everyone, but it suits me fairly nicely, since I tend to have a lot of windows open simultaneously.

Also, in the text file "~/.fluxbox/groups" I can set specific windows to always open in tabs, so gimp can *always* have only one window that contains all of it's additional windows. Using this, I can open say, 10 image-viewing windows (I use xzgv) and 10 leafpad windows that will only display two windows at a time.

Another benefit of fluxbox is that it supports setting a default window size for each program. So if gqview or inkscape is too large for the display, just resize it, tell fluxbox to remember the configuration, and it will never be too large again, unless you erase the text file.
Capn_Fish
I currently have tabs turned off in Fluxbox because I couldn't figure out how to group windows. It's probably really obvious, but I'd like to know how. Care to share?
radiochickenwax
QUOTE(Capn_Fish @ Apr 7 2007, 09:20 PM)
I currently have tabs turned off in Fluxbox because I couldn't figure out how to group windows. It's probably really obvious, but I'd like to know how. Care to share?
*


- In ~/.fluxbox/init:

put

CODE
session.tabs:    true


- There's more options, but that *should* just turn them on.
- Restart or reconfigure fluxbox (from the root menu)
- Middle click and drag a title bar onto another title bar to group two windows, middle-click and drag away to ungroup.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2014 Invision Power Services, Inc.