Bug 181039

Summary:	x11-wm/fluxbox fails to run if ~/.fluxbox/startup doesn't have execute set
Product:	Gentoo Linux	Reporter:	Charlie Nolan <funnyman3595>
Component:	Current packages	Assignee:	Jim Ramsay (lack) (RETIRED) <lack>
Status:	RESOLVED FIXED
Severity:	major	CC:	tercel
Priority:	High
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Charlie Nolan 2007-06-06 02:37:21 UTC

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.

Comment 1 Jakub Moc (RETIRED) gentoo-dev

2007-06-06 06:25:13 UTC

Erm... You /home is mounted noexec?

Comment 2 Charlie Nolan 2007-06-06 19:58:39 UTC

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.

Comment 3 Jakub Moc (RETIRED) gentoo-dev

2007-06-06 20:03:55 UTC

Which fluxbox version is this about?

Comment 4 Charlie Nolan 2007-06-06 20:12:02 UTC

Stable (1.0_rc3)

Comment 5 Jim Ramsay (lack) (RETIRED) gentoo-dev

2007-06-06 22:02:29 UTC

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.