Difference between revisions of "Fs2 open on Linux/ERROR: "Web cursor bitmap not found.""
From FreeSpace Wiki
(New page: ERROR: "Web cursor bitmap not found. This usually means that the executable is being run outside the directory you installed Freespace2 to. Please move the executable to that directory...) |
|||
| (2 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
| + | {{Page Navigation| | ||
| + | BookName=[[The fs2_open on Linux Guide]]| | ||
| + | CurrentPage=ERROR: "Web cursor bitmap not found."|ERROR: "Web cursor bitmap not found."| | ||
| + | PrevPage=[[Fs2_open on Linux/Common Runtime Errors|Common Runtime Errors]]| | ||
| + | NextPage=[[Fs2_open on Linux/I18n and Key mapping problems|I18n and Key mapping problems]]}} | ||
| + | <p></p> | ||
ERROR: "Web cursor bitmap not found. This usually means that the executable is being run | ERROR: "Web cursor bitmap not found. This usually means that the executable is being run | ||
outside the directory you installed Freespace2 to. Please move the executable to that | outside the directory you installed Freespace2 to. Please move the executable to that | ||
| Line 5: | Line 11: | ||
Have your user take owenership of the .vp files, run as root: | Have your user take owenership of the .vp files, run as root: | ||
$ chown <user> /path/to/vpfiles/ -R | $ chown <user> /path/to/vpfiles/ -R | ||
| + | |||
| + | [[Category:FreeSpace Open on Linux|Web cursor bitmap not found]] | ||
Latest revision as of 18:16, 24 September 2008
| « Common Runtime Errors | The fs2_open on Linux Guide ERROR: "Web cursor bitmap not found." |
I18n and Key mapping problems » |
ERROR: "Web cursor bitmap not found. This usually means that the executable is being run outside the directory you installed Freespace2 to. Please move the executable to that directory and try again" at graphics/2d.cpp:1402
A common error. This happens when fs2_open can't find the .vp files or that your user doesn't have the permissions to access them. If you are using a start up script(like the one found here) it's most likly the a permission problem. Have your user take owenership of the .vp files, run as root:
$ chown <user> /path/to/vpfiles/ -R
