OESF Portal | OESF Forum | OESF Wiki | LinuxPDA | #planetgemini chat on matrix.org | #gemini-pda chat on Freenode | #zaurus and #alarmz chat on Freenode | ELSI (coming soon) | Ibiblio

IPB

Welcome Guest ( Log In | Register )

2 Pages V   1 2 >  
Reply to this topicStart new topic
> Oops...xinitrc, Help?
T3_slider
post Feb 10 2007, 05:31 PM
Post #1





Group: Members
Posts: 125
Joined: 26-December 06
Member No.: 13,449



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!)
Go to the top of the page
 
+Quote Post
Jon_J
post Feb 10 2007, 05:47 PM
Post #2





Group: Members
Posts: 1,853
Joined: 31-December 05
From: Illinois USA
Member No.: 8,821



I would help, but where is it located?
I have pdaxii13
Go to the top of the page
 
+Quote Post
Meanie
post Feb 10 2007, 05:48 PM
Post #3





Group: Members
Posts: 2,803
Joined: 21-March 05
From: Sydney, Australia
Member No.: 6,686



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
Go to the top of the page
 
+Quote Post
T3_slider
post Feb 10 2007, 06:00 PM
Post #4





Group: Members
Posts: 125
Joined: 26-December 06
Member No.: 13,449



Thanks so much Meanie -- your infinite wisdom never ceases to amaze me. ;-)

And thank-you for offering your help, Jon_J.
Go to the top of the page
 
+Quote Post
radiochickenwax
post Feb 10 2007, 06:24 PM
Post #5





Group: Members
Posts: 158
Joined: 21-November 04
Member No.: 5,548



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:

https://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.
Go to the top of the page
 
+Quote Post
T3_slider
post Feb 11 2007, 10:18 AM
Post #6





Group: Members
Posts: 125
Joined: 26-December 06
Member No.: 13,449



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).
Go to the top of the page
 
+Quote Post
Capn_Fish
post Feb 11 2007, 10:47 AM
Post #7





Group: Members
Posts: 2,342
Joined: 30-July 06
Member No.: 10,575



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.
Go to the top of the page
 
+Quote Post
Capn_Fish
post Feb 11 2007, 10:47 AM
Post #8





Group: Members
Posts: 2,342
Joined: 30-July 06
Member No.: 10,575



I forgot to say that changing the theme from Sn33z to some other theme I got seemed to make it load much faster.
Go to the top of the page
 
+Quote Post
scheck.r
post Feb 11 2007, 11:13 AM
Post #9





Group: Members
Posts: 320
Joined: 5-December 04
From: Paris, France
Member No.: 5,776



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:
https://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.
Go to the top of the page
 
+Quote Post
radiochickenwax
post Feb 11 2007, 12:41 PM
Post #10





Group: Members
Posts: 158
Joined: 21-November 04
Member No.: 5,548



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.
Go to the top of the page
 
+Quote Post
Capn_Fish
post Feb 11 2007, 02:52 PM
Post #11





Group: Members
Posts: 2,342
Joined: 30-July 06
Member No.: 10,575



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.
Go to the top of the page
 
+Quote Post
radiochickenwax
post Feb 11 2007, 04:00 PM
Post #12





Group: Members
Posts: 158
Joined: 21-November 04
Member No.: 5,548



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.
Go to the top of the page
 
+Quote Post
Jon_J
post Apr 6 2007, 05:10 PM
Post #13





Group: Members
Posts: 1,853
Joined: 31-December 05
From: Illinois USA
Member No.: 8,821



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?
https://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.
Go to the top of the page
 
+Quote Post
Capn_Fish
post Apr 6 2007, 05:34 PM
Post #14





Group: Members
Posts: 2,342
Joined: 30-July 06
Member No.: 10,575



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.
Go to the top of the page
 
+Quote Post
Jon_J
post Apr 6 2007, 05:49 PM
Post #15





Group: Members
Posts: 1,853
Joined: 31-December 05
From: Illinois USA
Member No.: 8,821



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.
Go to the top of the page
 
+Quote Post

2 Pages V   1 2 >
Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 



RSS Lo-Fi Version Time is now: 22nd November 2019 - 11:06 AM