Bug 602932 - gedit can not run if filesystem path contains spaces
gedit can not run if filesystem path contains spaces
Status: RESOLVED FIXED
Product: gedit
Classification: Applications
Component: general
2.28.x
Other Mac OS
: Normal normal
: ---
Assigned To: Gedit maintainers
Gedit maintainers
:
Depends on:
Blocks:
  Show dependency tree
 
Reported: 2009-11-25 13:02 UTC by Randall Wood
Modified: 2009-11-28 18:22 UTC (History)
2 users (show)

See Also:
GNOME target: ---
GNOME version: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Randall Wood 2009-11-25 13:02:52 UTC 
If the path to the gedit application bundle contains spaces, gedit fails to launch.

Running gedit from the command line in Terminal.app produces the following if the path to gedit contains a space:

/Applications/Additional Applications/gedit.app/Contents/MacOS/gedit: line 14: cd: /Applications/Additional: No such file or directory
/Applications/Additional Applications/gedit.app/Contents/MacOS/gedit: line 56: /Contents/MacOS/gedit-bin: No such file or directory
/Applications/Additional Applications/gedit.app/Contents/MacOS/gedit: line 56: exec: /Contents/MacOS/gedit-bin: cannot execute: No such file or directory
/Applications/Additional Applications/gedit.app/Contents/MacOS/gedit: line 54: /Contents/Resources/libexec/gconfd-2: No such file or directory

When gedit is launched from the Finder in this case, the MacOS visibly launches gedit (the icon does the launch thing), but gedit silently fails and never appears in the Dock. Moving gedit to a folder that does not have any spaces in its path allows gedit to work as expected.
Comment 1 jessevdk@gmail.com 2009-11-28 18:22:29 UTC 
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.
Note You need to log in before you can comment on or make changes to this bug.