#727 644 on ~/.fluxbox/startup causes not able to be execute.

closed-fixed
nobody
None
5
2007-03-28
2007-03-27
mezz
No

After I updated fluxbox to 1.0 rc3 in FreeBSD ports and I now am collecting a few of reports from a few of users for not able to start their Fluxbox anymore. This problem only affect on users that don't have ~/.fluxbox. The startfluxbox creates ~/.fluxbox/startup and chmod it to 644 that causes startup not able to be execute. I had to backout the rev 4600 (644 -> 755 in util/startfluxbox.in) in our Fluxbox ports tree to solve it.

http://svn.berlios.de/viewcvs/fluxbox?rev=4600&view=rev

Discussion

  • Logged In: YES
    user_id=1538990
    Originator: NO

    That just replaces one problem with another. Now somebody with a noexec mounted home directory won't be able to run fluxbox. The correct solution is to change the second-to-last line in startfluxbox to exec sh "$startup", which I've now done in svn.

     
    • status: open --> closed-fixed