With a fresh emerge, fluxbox fails to start due to incorrect permissions on ~/.fluxbox/startup Reproducible: Always Steps to Reproduce: 1. Delete ~/.fluxbox/ (if any) 2. emerge fluxbox 3. Attempt to start fluxbox. Actual Results: fluxbox fails to start, giving this .xsession-errors: /etc/X11/gdm/PreSession/Default: Registering your session with wtmp and utmp /etc/X11/gdm/PreSession/Default: running: /usr/X11R6/bin/sessreg -a -w /var/log/wtmp -u /var/run/utmp -x "/var/gdm/:20.Xservers" -h "" -l ":20" "funnyman3595" /etc/X11/gdm/Xsession: Beginning session setup... /etc/X11/gdm/Xsession: Setup done, will execute: /usr/bin/ssh-agent -- startfluxbox /usr/bin/startfluxbox: line 89: /home/fm//.fluxbox/startup: Permission denied /usr/bin/startfluxbox: line 89: exec: /home/fm//.fluxbox/startup: cannot execute: Success Expected Results: Fluxbox starts. ~/.fluxbox/startup needs to be chmodded u+x.
Erm... You /home is mounted noexec?
Nope. It is, however, on a separate partition from /: /dev/sda5 / ext3 defaults,user_xattr 0 1 /dev/sda6 /home ext3 defaults,user_xattr 0 0 As I said, it's just the file permissions that need to be changed. If I run: chmod u+x ~/.fluxbox/startup it works fine.
Which fluxbox version is this about?
Stable (1.0_rc3)
Yes, this bug is known to upstream and is currently fixed in their svn. I have added the appropriate patch in fluxbox-1.0_rc3-r3. In the mean time, you don't need to 'chmod +x' your ~/.fluxbox/startup - This bug only manifests itself if the 'startfluxbox' script creates the ~/.fluxbox/startup file. Your second attempt at running fluxbox after experiencing this failure should behave normally with no intervention needed between attempts.
