Emerging fluxbox works without a problem, but after that I have no bsetroot (meaning the background stays black when fluxbox is started) and in stderr I see: BScreen::parseMenuFile: [stylesdir/stylesmenu] error, /usr/local/share/fluxbox/styles does not exist and similar messages. I think /usr/local/share/commonbox would be right, but I don't know where the problem is. Because no file is found, the menu is very tiny (Reset, Exit and xterm). My USE-Flags: USE="x86 oss avi crypt cups encode foomaticdb gif imlib jpeg gnome libg++ libwww mad motif mpeg ncurses nls pdflib png qt quicktime sdl spell svga truetype xml2 xmms xv zlib gdbm berkdb slang readline java X tcpd pam ssl perl python oggvorbis gtk opengl 3dnow aalib acpi acpi4linux alsa apache2 bonobo cdr dga dvd ethereal faad ffmpeg gd gtk2 hostap-noplx imagemagick imlib2 maildir mmx moznocompose moznoirc moznomail mysql openssh php plotutils samba sse vim-with-x -apm -arts -kde -mikmod -gpm" Reproducible: Always Steps to Reproduce: 1. Use my USE-Flags (don't know if that is the problem) 2. emerge rsync && emerge fluxbox 3. export DISPLAY=:0 && fluxbox Actual Results: fluxbox compiles and starts, but wants files from the wrong directory. Additionally bsetroot is missing. Expected Results: It should read /usr/local/share/commonbox and provide bsetroot. I started installing from stage3 and used some GRPs, but that should be gone now (emerge -u world).
wrt bsetroot, this program is very old, and afaik was never distributed as part of fluxbox. in gentoo, *box wms depend on another package called commonbox-utils which until recently included bsetroot and bsetbg. this legacy tools have been replaced by the much more powerful fbsetbg (wrapper script) and feh, and imlib2 bg setter that supports transparency and many other features missing in bsetroot. as for the /usr/local, Gentoo uses /usr as the standard prefix, so your themes can be found in /usr/share/commonbox/styles the menu you are seeing is the fluxbox default, checkout commonbox-menugen (also included in commonbox-utils) for a simple way to quickly build your menu file. for example, commonbox-menugen -gk -o ~/.fluxbox/menu will output a menu derived from any installed gnome and kde menu items Cheers, tseng
PS, I just noticed that you filed this bug under severity "blocker." We take out Bugzilla pretty seriously, and blocker is our hightest priority. Please think twice before using it, almost all bugs are of the "normal" variety, our bug wranglers will adjust the severity if it is really nessecary Lemme know if my comment has straightened all of this out for you, I hope you will checkout the scripts and be one happy user ;) Thanks!
Hello! Thanks for the fast answer, but I am not satisfied. I expect "emerge <program>" to check dependencies and install the programs that are needed. In this case Fluxbox wants (!) bsetroot (and not the new thing), so it should get bsetroot (I use Esetroot because of Eterm, but that is not part of the problem). Of course it would be possible to "fix" fluxbox to not use bsetroot. I wonder why I was able to change the background the day before yesterday, when bsetroot never was a part of fluxbox. Perhaps I did emerge something that belongs to it, but I doubt that. Fluxbox without bsetroot (or another working tool) is no real fluxbox, in my opinion. That is part of the reason for "blocker". Regarding the path: I know where I can find the styles, but fluxbox does not. It is just wrong that an emerge fluxbox puts stuff in place A but loooks in place B. Please fix that, either way. Now, my reasons for "blocker". The description is: "The bug prevents you from testing or developing the software" It does! Everyone who emerges fluxbox is unable to do anything, because a) bsetroot is missing and no other tool can be selected b) the menu is just unusable c) important files can not be found I know the user could fix the path and generate an own menu, but that is not the sense of gentoo. I am sorry, if I misunderstood your meaning if blocker, but in my opinion the description of blocker fits in this case. So, I still don't understand why emerging fluxbox without ~x86 provides an unusable fluxbox and that should be OK.
Hey man, thanks for the input! I noticed that the script includes a hardcoded (minus prefix) path to the styles directory, I will fix this to point to the commonbox dir. Also I'll try and make it generate a better default menu (this is done in pkg_postinstall in commonbox-utils) for people w/o a KDE or Gnome menu. Maybe I will do this via USE flags? If USE="gnome", add gnome menu items to the fluxbox menu.. this seems sensible. As for bsetroot, I am guessing you are looking for this because themes are hardcoded to use bsetroot /their/bg/image? My first two points are strictly opinion: first, bsetroot is very old and not very useful compared to newer tools, and second, the wallpapers included in most styles are horribly ugly. my third point is that setRootCommand is about the most horribly insecure thing i have ever seen, as it allows someone to run an arbitrary command w/o any effort. newer blackbox style (not based on the original code) have dropped this in favor of setting your bg via .xinitrc or another startup script. All that being said, i made the decision to drop bsetroot very unilaterally, as I failed to find someone who used *box and commonbox-utils to comment. I am currently considering making bsetroot its own package. This might be triggered by a commonbox USE flag... if commonbox is set, it will use our customized file layout, and install my scripts, if unset, it will install to /usr/share/$yourbox and also grab bsetroot. Comments on this approach? TIA for your time and ideas.
Hi again! That styles-fix might be needed in blackbox, too (I just emerged it and it does not work, but I have not looked at it further). I understand that bsetroot ist old and stuff, but fact is: "emerge fluxbox" on a fresh gentoo needs bsetroot at some time. Perhaps it is the default script, perhaps it is fluxbox-stuff, I don't know. So, if you want to kill bsetroot (that's OK to me), fix that "call to bsetroot" before you kill it. That "customized file layout" you are talking about sounds good and, if I understood it correctly, should be default. PS: What does TIA mean?
*** Bug 30910 has been marked as a duplicate of this bug. ***
Until we come up with a better solution to this, I have hardmasked 0.5 of commonbox-utils, which reverts to the old bsetroot install. For those following along, esp. Carsten, feel free to contact me on irc.oftc.net in #gentoo or a pm. --tseng
Package masked, and I will surely take bsetroot/bsetbg into account in future versions. Closing the bug, but I still welcome comments from interested parties via email or irc. --tseng
