Problems with SuSE 8.2 and Celestia

General discussion about Celestia that doesn't fit into other forums.
Topic author
antman49443
Posts: 4
Joined: 03.09.2003
With us: 21 years 3 months

Problems with SuSE 8.2 and Celestia

Post #1by antman49443 » 03.09.2003, 20:47

I am running SuSE Linux 8.2 Desktop version and installed celestia 1.3 from a SuSE RPM using YAST. After installing using YAST, there is a celestia folder in /opt/kde3/share/apps with all sorts of goodies and then an executable file in /opt/kde3/bin. I try to open the executable file in bin and it does nothing. Should this file be in the apps file with the rest of the files or am I totally messed up :(

Any help would be appreciated!

Christophe
Developer
Posts: 944
Joined: 18.07.2002
With us: 22 years 4 months
Location: Lyon (France)

Post #2by Christophe » 03.09.2003, 21:09

It's normal, the executable and the data files are in separate directories.

Try running celestia from a shell window, the normal output looks like this:

Code: Select all

chris@tux:~> celestia
nStars: 112523
Initializing ARB vertex programs . . .
Loading ARB vertex program: shaders/diffuse_arb.vp
Loading ARB vertex program: shaders/specular_arb.vp
Loading ARB vertex program: shaders/haze_arb.vp
Loading ARB vertex program: shaders/bumpdiffuse_arb.vp
Loading ARB vertex program: shaders/bumphaze_arb.vp
Loading ARB vertex program: shaders/shadowtex_arb.vp
Loading ARB vertex program: shaders/diffuse_texoff_arb.vp
Loading ARB vertex program: shaders/rings_arb.vp
Loading ARB vertex program: shaders/ringshadow_arb.vp
Loading ARB vertex program: shaders/night_arb.vp
Loading ARB vertex program: shaders/glossmap_arb.vp
All ARB vertex programs loaded successfully.
render path: 5


And the window should of course appear.
Christophe

Topic author
antman49443
Posts: 4
Joined: 03.09.2003
With us: 21 years 3 months

Post #3by antman49443 » 04.09.2003, 19:21

Christophe:
Thanks for the quick reply! I should've warned you I am somewhat new to Linux. I've been 'using' Mandrake and SuSE for about a year but have been able to avoid using a shell window for the most part, so my instincts in the shell window are "poisoned" by my experience with DOS.

Here's what I did after reading your post:
1. opened shell window
2. entered "SU" and my root pass word
3. entered "cd /opt/kde3/bin" # (this is where the executable file was)
4. typed in 'celestia" and pressed the "enter" key

results:
bash: celestia: command not found

Does this mean the installation is corrupt and I should try another download or my shell skills are as bad as I think they are? :oops:

Any help is greatly appreciated!

Christophe
Developer
Posts: 944
Joined: 18.07.2002
With us: 22 years 4 months
Location: Lyon (France)

Post #4by Christophe » 04.09.2003, 20:02

antman49443 wrote:Here's what I did after reading your post:
1. opened shell window
2. entered "SU" and my root pass word
3. entered "cd /opt/kde3/bin" # (this is where the executable file was)
4. typed in 'celestia" and pressed the "enter" key

results:
bash: celestia: command not found


Firstly you don't need to be root to run Celestia. Depending on how your system is set up you could even have problems running X applications from a 'su'-ed shell.

You also don't need to be in the directory were the executable file is to run it. When you run a command from a shell, the shell looks for the corresponding executable in all the directories listed in your PATH variable and only there! So if '.' (current working directory) is not in your PATH and if /opt/kde/bin is not either, it won't find it even if run from /opt/kde/bin.

'.' is normaly NOT in your PATH, this is to avoid security problems. To run an executable in the current directory you need to prepend './', e.g. ./celestia
or you could also do /opt/kde/bin/celestia from anywhere.

Now, /opt/kde/bin should be in your PATH if /opt/kde is the directory where KDE is installed, otherwise KDE wouldn't work at all.

To check what is in your PATH run:
echo $PATH
Christophe

jamarsa
Posts: 326
Joined: 31.03.2003
With us: 21 years 8 months
Location: San Sebastian (Spain)

Post #5by jamarsa » 04.09.2003, 20:26

No, /opt/kde3/bin isn't in the path, because despite the lack of the current directory in the PATH variable, if celestia resides in /opt/kde3/bin and this directory is listed in the path it should run it!! Obvious, isn't it?

You should add it to the PATH:

export PATH=$PATH:/opt/kde3/bin

or move celestia binary to, for example, /usr/local/bin (if it is listed in your PATH).

Or more simple, run it with the complete path:

/opt/kde3/bin/celestia (that's what you should see in your desktop link properties)

Christophe
Developer
Posts: 944
Joined: 18.07.2002
With us: 22 years 4 months
Location: Lyon (France)

Post #6by Christophe » 04.09.2003, 20:36

Yes I know /opt/kde/bin is not in the PATH, but then how is KDE working? My point was that something is not set up correctly, maybe KDE is not installed in /opt/kde?
Christophe

Topic author
antman49443
Posts: 4
Joined: 03.09.2003
With us: 21 years 3 months

Post #7by antman49443 » 05.09.2003, 13:30

Christophe and Javier:

Thanks for the suggestions.

I tried both suggestions:
1. First /opt/kde3/bin was listed when I did echo $PATH
2. I checked in /opt/kde3/bin and found files like kde-config, kded, kdeeject, kdeinit, etc. --- I'm guessing this is where KDE is.
3. When I ran Celestia using both your suggestions I get the following message back:
:relocation error: /opt/kde3/bin/celestia: undefined symbol:
__ti11KMainWindow

This sounds like Christophe suggested, something is not set up correctly. Any suggestions?

Christophe
Developer
Posts: 944
Joined: 18.07.2002
With us: 22 years 4 months
Location: Lyon (France)

Post #8by Christophe » 05.09.2003, 13:40

antman49443 wrote:I tried both suggestions:
1. First /opt/kde3/bin was listed when I did echo $PATH
2. I checked in /opt/kde3/bin and found files like kde-config, kded, kdeeject, kdeinit, etc. --- I'm guessing this is where KDE is.
3. When I ran Celestia using both your suggestions I get the following message back:
:relocation error: /opt/kde3/bin/celestia: undefined symbol:
__ti11KMainWindow


Are you sure the Celestia package you installed was for your version of SuSE? It looks like a library version mismatch.
Christophe

Topic author
antman49443
Posts: 4
Joined: 03.09.2003
With us: 21 years 3 months

Post #9by antman49443 » 05.09.2003, 15:12

Christophe: Thanks for all your help. I think you've got it--I was using a version for SuSE8.1 instead of 8.2
I'll regroup and try again.
Thanks again.


Return to “Celestia Users”