Package: fluxbox Version: 0.9.11-1
Hi!
Some time ago I submitted a bug report about fbrun crashing the X-Server at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=291672&archive=yes. Somewhere in the mail traffic I mentioned that my .xsession-errors file was full of:
Failed to read: session.screen0.followModel Setting default value Failed to read: session.screen0.window.focus.alpha Setting default value Failed to read: session.screen0.window.unfocus.alpha Setting default value Failed to read: session.screen0.menu.alpha Setting default value [...]
In the same time, menu transparency did not work (just because the default value == non-transparent was taken), but also changing in the menu itself did not result in any change; after re-opening the menu, it was back at 255.
I know resolved this issue and hope that someone who is close to the
source can change it appropriately. The thing is that my ~/.fluxbox/init
file had 0600 permissions, i.e. only myself could read and write that
file. After changing it to 0644, everything - including the fbrun thingy
and menu transparency, works fine. I think that somewhere in fluxbox.cc
there needs to be a change made. I'm not really familiar with C++ or X
programming, but I found the following: (I took the source files from
the fluxbox.org-devdocs.)
- line 00493: setupConfigFiles() is called which checks the existence of
init, menu and keys (I think) with a stat call and creates them if they
are non-existing
- line 00503: some weird thing with m_fluxbox_pid = XInternAtom(disp,
"_BLACKBOX_PID", False) is done
- line 00521: some more weird stuff happens ("weird" means that I don't
understand it *grin*): pid_t bpid = getpid();
- line 01614: XrmGetFileDatabase() is called to get some kind of
database out of the init file
I think the last thing is the critical point.
http://static.cray-cyber.org/Documentation/NEC_SX_R10_1/G1AE02E/CHAP15.HTML
says about XrmGetFileDatabase(): "If it cannot open the specified file,
XrmGetFileDatabase returns NULL." So I don't exactly know what happens,
but this function call seems to use a different user id than the user's
one, which is quite a pity. I'd be happy to have that changed by someone :-)Bye Tobias
--
Justice through Precision
-- Inscription on the AI pyramid
signature.asc
Description: OpenPGP digital signature
