SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have a strange question and I hope you can solve it...
my default runlevel is 4, and I use xdm as a login manager. I found a nice set of files to make the login scr een look nice. Furthermore I use a shading aterm so that my console looks nice as well...
The xdm files loads its own bsetroot: /usr/bin/X11/bsetroot -mod 4 4 -fg rgb:7b/7b/7b -bg rgb:84/84/84 &
and the fluxbox style file loads its own as well: rootCommand: bsetbg ~/graphix/backgrounds1024/background2.jpg
well this doesnt work right with a shading aterm... In fluxbox the background file gets loaded properly, but when I start aterm with -sh 40, it shades the first bsetroot command, instead of the fluxbox background file... in this way I get this strange shaded modula pattern that bsetroot starts, whereas it should shade the background file, to have a nice result...
Any ideas how to make aterm shade my fluxbox background file, instead of the xdm bsetroot stuff?
and fyi when I run aterm -tr it is completely transparent. -tint also works properly...
cheers,
rogier
btw running, slack 10, fluxbox 0.14.1 (or other way around, the new versions suck)...
Did you try to comment (add a #) the bsetroot in xdm ?
I agree with your opinion about fluxbox new version for the too heavy styles features, it lost its
spirit although some cool configuration options have been added
I was stuck on flux 0.1.14 for quite a while before upgrading to the newer version. I couldn't imagine using flux without the external tabs. But now that I've upgraded, I wouldn't have it any other way. I agree that some of the new styling features are a bit excessive, but you don't have to use them if you don't want to. And the improvements in functionality are fantastic. One of the best is the "fbsetbg" wrapper. It chooses the best background setter from those available on your particular system.
I was having the same transparency problems with bsetbg, and as soon as I installed fbsetbg, the problems vanished. If you don't want a newer fluxbox (or fbsetbg), you can use a different background setter in your style or init file. The best for use with aterms/other transparency are "esetroot" and "wmsetbg". Both work fine for me. esetroot seems to be the best and comes with Eterm. I would recommend installing Eterm from a slack package (I've heard compiling it from source is a bear), and then just swap esetroot for bsetbg and your problems should be fixed. If you don't want to bother installing Eterm, wmsetbg is installed by default with a full slack install.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.