https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2844
xvi <xvi@xxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|Normal |Major
Summary|Wireshark on MacOS does not |Wireshark on MacOS does not
|run when launched from case |run when there are spaces in
|sensitive filesystem |its path
Version|1.0.2 |1.0.4
--- Comment #3 from xvi <xvi@xxxxxxxx> 2008-10-28 14:06:39 PDT ---
It seems my first diagnostic was wrong indeed. The trouble comes from
some space in the path to the application. It was contained in a
"Wireshark 1.0.x" folder, this leaded to looking for Wireshark-bin
instead of wireshark-bin in the Resources/bin folder, I misinterpreted
this message as a case problem.
(corrected summary accordingly)
To reproduce the error, put Wireshark in a folder named "Name With
Space" and run it.
When launched from a terminal, this is what happens:
mac-pro:~ pascal$ /Users/pascal/Desktop/Name\ With\
Space/Wireshark.app/Contents/MacOS/Wireshark
/Users/pascal/Desktop/Name With
Space/Wireshark.app/Contents/Resources/bin/wireshark: line 82:
/Users/pascal/Desktop/Name With Space/Wireshark.app/Contents/Resources/bin/Name
With
wireshark-bin: No such file or directory
/Users/pascal/Desktop/Name With
Space/Wireshark.app/Contents/Resources/bin/wireshark: line 82: exec:
/Users/pascal/Desktop/Name With Space/Wireshark.app/Contents/Resources/bin/Name
With
wireshark-bin: cannot execute: No such file or directory
Changing line 19 of Resources/bin/wireshark from:
APPNAME=`basename $0`
to
APPNAME=`basename "$0"`
seems to correct the problem.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
