guidedog fails if $SHELL set
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
guidedog (Debian) |
Fix Released
|
Unknown
|
|||
guidedog (Ubuntu) |
Fix Released
|
Medium
|
Luca Falavigna |
Bug Description
Binary package hint: guidedog
If you have the SHELL environment variable set to a non-Bourne-like shell (e.g., /bin/tcsh), then guidedog will fail to perform its actions.
To reproduce:
$ apt-get install tcsh # (-:
$ env SHELL=/bin/tcsh guidedog
$ # or "chsh /bin/tcsh" then log out and back in
click Enable Routing
click Apply
click Continue
Expected:
guidedog enables routing.
Actual:
An alert box appears with the message, "export: Command not found."
It appears that guidedog is sending some Bourne shell commands to whatever program $SHELL is set to. guidedog should ignore $SHELL and always use /bin/sh or /bin/bash.
guidedog is in Universe. I'm not sure whether this is the best place to report this bug. Hopefully, if it isn't, someone will yell at me -- er, constructively suggest a better course of action. (-: The Upstream, www.simonzone.com, seems dead -- the last release was in 2003.
Related branches
Changed in guidedog: | |
status: | Unknown → New |
Changed in guidedog: | |
assignee: | nobody → dktrkranz |
importance: | Undecided → Medium |
status: | Confirmed → In Progress |
Changed in guidedog: | |
status: | New → Fix Released |
Fix for this and bug #217232.