You are not logged in.
I just installed the new fluxbox-devel 0.9.9 package, and for some reason, the 'Exit' menu function does not exit fluxbox, I just get a blank screen. I have to CTRL+ALT+Backspace to get out.
Anyone else have this problem? I can rebuild it if necessary, but I just wanted to know if this is something I should report upstream, or if it's specific to Arch.
Thanks.
Arch 0.6 - Kernel 2.6.5 - Fluxbox 0.9.8
Offline
Same here, but fluxbox quits/freezes, I can still use the mouse and other programs. I quit x with ctrl+alt+backspace anyway, so I didn't notice it yet.
Offline
I updated to fluxbox-devel 0.9.9 yesterday morning and don't have that problem.
"No live organism can continue for long to exist sanely under conditions of absolute reality; even larks and katydids are supposed, by some, to dream." - S. Jackson
Offline
yep, I've got the same freeze/hang problem, here.
-- Linux! Isn't it time?
Offline
me too - it hangs on exit
Offline
I use fluxbox devel... but I run KDM so exit works Ok.
Mr Green
Mr Green
Offline
did you used fluxbox and then changed to fluxbox-devel ? or directly using fluxbox-devel (never used fluxbox)?
i suspect that some configs in ~/.fluxbox/ may be version-dependend
(i use fluxbox - once tried fluxbox-devel and was not so happy with it being slower and *very* unstable as it should be as a -devel version)
good luck finding out where the trouble is/was
The impossible missions are the only ones which succeed.
Offline
Speaking as one who hasn't had any problems, I started off with the release version of fluxbox, then changed to fluxbox-devel at, IIRC, version 0.9.8. I don't use KDM/GDM/XDM, just an .xinitrc and "startx" after booting. And I haven't seen any instability, nor does fluxbox-devel seem noticeably slower (nor faster) to me than release. I'm very pleased with it, not least for the "Remember" function, which is an easy way to set default size/placement for certain programs that I regularly keep on certain workspaces. I haven't done much with the GUI "enhancements" (rounded corners? yuck!). But if dp's right and there are some wonky configs causing problems for people, I'd be happy to post any particular file for comparison purposes, if that would help.
"No live organism can continue for long to exist sanely under conditions of absolute reality; even larks and katydids are supposed, by some, to dream." - S. Jackson
Offline
did you used fluxbox and then changed to fluxbox-devel ? or directly using fluxbox-devel (never used fluxbox)?
i suspect that some configs in ~/.fluxbox/ may be version-dependend
(i use fluxbox - once tried fluxbox-devel and was not so happy with it being slower and *very* unstable as it should be as a -devel version)
good luck finding out where the trouble is/was
I had fluxbox installed for about an hour before I discovered fluxbox-devel in pacman -although I have always had all my configs for both version (I have swapped back and forth before) in the same place
What file could likely be causing this?
Offline
The only real problem I have with fluxbox is background setting I have to install Eterm to get background to work (fbsetbg)
unless you know different
oops thread napping again :oops:
As for speed have not noticed any difference...
I'll give .xinitrc a try & let you know...
Mr Green
Mr Green
Offline
I also only use .xinitrc and startx to start flux...
Offline
No if I use .xinitrc & startx then exit I end up back at console.....
Mr Green
(Anyway I like using KDM looks pretty )
Mr Green
Offline
can you post your .xinitrc file? (the people with trouble exiting)
you should have "fluxbox" as last entry in list - following killall-commands of other daemons/programms you set to start before fluxbox
The impossible missions are the only ones which succeed.
Offline
The only real problem I have with fluxbox is background setting I have to install Eterm to get background to work (fbsetbg)
unless you know different
Mr. G, according to fbsetbg website, you can uninstall Eterm if you wish, if you first copy Esetroot to a safe place. See:
http://www.xs4all.nl/~hanb/software/flu … setbg.html
I was under the impression that fbsetbg would work even if you don't have Esetroot, since it is just a wrapper that makes use of other tools to set the background -- Esetroot or whatever else it can find. Since I started with fluxbox release, which did recommend Esetroot/Eterm over anything else, I installed it and simply left it. So I've never tried fbsetbg with anything other than Esetroot. I don't really use Eterm, but it doesn't bother me to have it.
oops thread napping again :oops:
Bad, bad, bad.
"No live organism can continue for long to exist sanely under conditions of absolute reality; even larks and katydids are supposed, by some, to dream." - S. Jackson
Offline
Thank you .... I installed Eterm but I do not it I use aterm (fast) but your link may help me figure out how to remove Eterm for good
Thank you
Mr Green (o thread napping again :oops: )
Mr Green
Offline
take a look at ~/.fluxbox/fbsetroot or bsetroot or something... that should define commands you can use instead of eterm to display stuff on the root.
I used to use qiv.
Another option is to have the background set by the login manager and use the same background after login. I've done this with kdm.
ion doesn't support backgrounds on tilable workspaces. Only on floating ones.
Dusty
Offline
I saw the exact same problem on 3 different boxes that all had been working fine previously.
Could the maintainer or someone please post a link to the actual previous package for fluxbox-devel which was working perfectly fine?
update:
here is a link to the previous fluxbox-devel pkg that works fine, i just installed it and things were back to being fully functional again
Offline
I found that with 0.9.8 you could no longer navigate the root menu with the arrow keys--fixed in 0.9.9. I actually prefer the Arch version of 0.1.14, since it incorporates Mr. Kita's menukey patch, where you can bind your own keystrokes to rootmenu navigation.
As for Eterm, you can, if you have windowmaker installed, use wmsetbg or you can install xli, qiv or xv---I forget which one is an Arch package, but I think one of them is. On FreeBSD I use xli. (If you have ImageMagik installed for other purposes, that also works. )
I have a page on fluxbox that goes into that stuff at
http://home.nyc.rr.com/computertaijutsu/fluxbox.html
I haven't had the exit problem on devel version.
Offline
In init file I have
fbsetbg -f <path to image file>
but it will only work if Eterm is installed
Dustys Idea of using KDM background might be an option......
Scottro ...Great site lots of very useful information....
Mr Green
Mr Green
Offline
you can also install the feh package. If you look at the following url it will list what apps will work with fbsetbg other then just Esetroot. http://www.xs4all.nl/~hanb/software/flu … setbg.html
Hope that helps.
Offline
Thank you
(don't tell anyone I'm looking into fbdesk !! I miss my icons )
Thats what I love about Linux you never stop learning.....
Mr Green
Mr Green
Offline
well, with the previous fluxbox-devel version everything works fine
I dont use any of the features what were mentioned in one of the above posts so I dont miss anything. I dont log into gui as root ever, I just use root privs in eterm.
nonetheless reverting back to the older fluxbox-devel pkg worked and obviously it was something that may not have affected everyone but did affect more than just one person.
and mr.green - if you check the download section of easylinuxguide.com, there is a section on fluxbox that includes many re-written styles and backgrounds - you can just use those or even edit one of those files and include the path to your background which makes it appear permanentyl until you change it, just another thought
cheers all 8)
Offline
Thank you :-)
Mr Green
Offline
http://www.easylinuxguide.com/downloads … creen2.jpg
very tasty :-)
yum yum I'm hungry for more
Mr Green
Mr Green
Offline
Well I spoke too soon. Last night, and again today, I am now having the problem of fluxbox-devel 0.9.9. freezing when I try to exit. Have to do Ctrl+Alt+Backspace to shut it down. Also saw my CPU stuck at 100% when I tried to restart X (using startx), once, but that hasn't happened again (yet!). I wonder if there is a conflict somewhere as this didn't start happening until after yesterday's pacman -Syu, though there really weren't very many packages to upgrade.
"No live organism can continue for long to exist sanely under conditions of absolute reality; even larks and katydids are supposed, by some, to dream." - S. Jackson
Offline