Bug#495553: bash's failglob option makes freecol print its usage message

[Vincent Fourmond]

  Hello,

On Mon, Aug 18, 2008 at 3:42 PM, Steve Cotton
<steve0001 at s.cotton.clara.co.uk> wrote:
> For my primary user:
> When started from the command line with no options, freecol just prints the
> usage message to stderr and exits.  Adding any option makes it work (tried
> with --windowed, --splash, --no-sound).
> This also happens when started from the window-manager's menu.
>
> For a second user id on the same machine, it runs fine.
>
>
> The difference is that the primary user's .bashrc includes
>  set failglob
> if /usr/games/freecol is called with no arguments, this makes
> the final line's "$@" expand to "failglob".

  Many thanks for this information. I'll have to dig a little further
to know which way this should be corrected - I might be wrong, but it
seems to me there that bash is not doing its expansion correctly in
this case (in the light of a brief reading of bash's manpage
concerning failglob).

  Regards,

      Vincent