#565491 [fluxbox] Doesn't start programs

Package:
fluxbox
Source:
fluxbox
Description:
Highly configurable and low resource X11 Window manager
Submitter:
Peter Fritzsche
Date:
2010-03-29 09:57:03 UTC
Severity:
normal
#565491#5
Date:
2010-01-16 11:29:37 UTC
From:
To:
I have a machine running thightvncserver as user program. As window manager
fluxbox was choosen. When I now make a right click on the background the
application menu pops up and I can click on any menu entry..... but then the
program doesn't open. I tried with several programs, but no one works. I
tested also openbox and it seems that it works there.

Is there any debug option I can use to get more information from fluxbox?
#565491#10
Date:
2010-01-16 15:19:34 UTC
From:
To:
Hey Peter,

Is this reproducible? What march is the host / client?

Could you try getting a backgrace with debugging info?

# apt-get build-dep fluxbox
$ apt-get source fluxbox
$ cd fluxbox-1.1.1-6
$ DEB_BUILD_OPTIONS=nostrip debuild
# dpkg -i ../fluxbox_*.deb

Also a strace would be fantastic for us mere mortals.

Thanks Pete!

Paul
#565491#15
Date:
2010-01-16 17:18:14 UTC
From:
To:
PT> Hey Peter,

PT> Is this reproducible? What march is the host / client?

PT> Could you try getting a backgrace with debugging info?

Paul
He already did backgrace with debug information. See above:)

PT> # apt-get build-dep fluxbox
PT> $ apt-get source fluxbox
PT> $ cd fluxbox-1.1.1-6
PT> $ DEB_BUILD_OPTIONS=nostrip debuild
PT> # dpkg -i ../fluxbox_*.deb

PT> Also a strace would be fantastic for us mere mortals.

PT> Thanks Pete!
#565491#20
Date:
2010-01-16 17:54:39 UTC
From:
To:
PT>> Could you try getting a backgrace with debugging info?

TPT> Paul
TPT> He already did backgrace with debug information. See above:)


Oh, it is my mistake, I've confused bugreports
:)
#565491#25
Date:
2010-03-28 11:33:14 UTC
From:
To:
I think I found the problem. (Just read fbrun source code, but rest will
probably work the same). Execl is used to start the program using "$SHELL -c
myprogram". This cannot work because I use zsh and output of my $SHELL is zsh
- which of course cannot be found by execl (needs full path).

Setting shell in my screenrc to /bin/zsh worked around that problem.
#565491#30
Date:
2010-03-28 15:40:19 UTC
From:
To:
Severity: important
thanks

I'm taking a look into this now. Thanks Peter!
#565491#35
Date:
2010-03-29 09:54:17 UTC
From:
To:
Paul Tagliamonte wrote:
wrote:

I think the best idea would be to read env['SHELL'] - if that exists then
check if we are allowed to execute that file (and that it exists and is not a
folder). If it is not a valid shell then just do what is done when no
env['SHELL'] is set - use /bin/sh as shell

Best regards,
	Peter