Celestia and Googleearth doesn' start [Solved]

Discussions Regarding Software

Moderator: Moderators

Celestia and Googleearth doesn' start [Solved]

Postby asy1410 » Wed May 08, 2013 11:10

I setup a new version of Sabayon XFCE. Googleearth, Celestia and gthumb is beginning to start and crashes. The Terminal says:
Code: Select all
[email protected] ~ $ celestia
Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 9: reading configurations from ~/.fonts.conf is deprecated.
Xlib:  extension "GLX" missing on display ":0.0".

(celestia:12668): GdkGLExt-WARNING **: Window system doesn't support OpenGL.
[email protected] ~ $ googleearth
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Google Earth has caught signal 11.



We apologize for the inconvenience, but Google Earth has crashed.
 This is a bug in the program, and should never happen under normal
 circumstances. A bug report and debugging data have been written
 to this text file:

    /home/sabayon/.googleearth/crashlogs/crashlog-518a2043.txt

Please include this file if you submit a bug report to Google.
[email protected] ~ $


Any help would be appreciated.

Thks

Artur

Moderator edit: Added Code tags. Please use Code button when posting lengthy console output
Last edited by asy1410 on Thu May 09, 2013 21:27, edited 1 time in total.
asy1410
Baby Hen
 
Posts: 17
Joined: Sun Apr 15, 2012 21:28

Re: Celestia and Googleearth doesn' start

Postby Fitzcarraldo » Wed May 08, 2013 14:06

Which manufacturer and model of GPU does your PC have?

Are the symlinks for the OpenGL libraries set up correctly?

If you're using an open-source driver (e.g. xf86-video-ati, xf86-video-nouveau, xf86-video-nv, xf86-video-ati or xf86-video-intel), as root user in a Konsole/Terminal window:

Code: Select all
eselect opengl set xorg-x11

If you're using a closed-source driver then, instead of the above, you'd need to enter the following if it's nvidia-drivers ("nvidia" in xorg.conf):

Code: Select all
eselect opengl set nvidia

or the following if it's ati-drivers ("fglrx" in xorg.conf):

Code: Select all
eselect opengl set ati

You can tell what the current symlinks are configured to be by using the following command:

Code: Select all
eselect opengl list
User avatar
Fitzcarraldo
Sagely Hen
 
Posts: 7981
Joined: Sat Mar 10, 2007 5:40
Location: United Kingdom

Re: Celestia and Googleearth doesn' start

Postby nickdanger » Wed May 08, 2013 17:01

I have ATI Radeon HD 7850 graphics. To get Celestia working I used the steps Fitzcarraldo listed above. I also had to do one more step to keep Celestia from crashing. In a terminal screen, (as SU) I entered:
Code: Select all
# eselect mesa list
# eselect mesa set 32bit sw classic


The idea being to switch mesa for 32bit software from gallium to classic. I do not think you need to do this if you are using the ATI proprietary drivers (fglrx), but if you are using ATI and the open source radeon drivers as supplied with the distro, then it is worth a try.
N.D.
nickdanger
Simple Hen
 
Posts: 89
Joined: Mon Aug 10, 2009 4:02

Re: Celestia and Googleearth doesn' start

Postby asy1410 » Thu May 09, 2013 9:31

thank you for your help. I have done, what you said, but the programs are not starting.
I have an Dell XPS L502X with Nvidia and I'm using the nouveau driver. All other programs are running perfect. For example Gimp, Gwenview, VLC or vbox. In virtualbox both programs are running?

thks in advance

Artur
asy1410
Baby Hen
 
Posts: 17
Joined: Sun Apr 15, 2012 21:28

Re: Celestia and Googleearth doesn' start

Postby Fitzcarraldo » Thu May 09, 2013 12:53

From what I read quite frequently, the nouveau driver is not very good (e.g. Nouveau vs. NVIDIA Linux Comparison Shows Shortcomings, April 23 2013). I never got it working on a relative's laptop, for example.

Anyway, you could try the work-around given in the Arch Linux Forums post: [SOLVED] Googleearth, 64 bit, nVidia and Nouveau driver.
User avatar
Fitzcarraldo
Sagely Hen
 
Posts: 7981
Joined: Sat Mar 10, 2007 5:40
Location: United Kingdom

Re: Celestia and Googleearth doesn' start [Solved]

Postby asy1410 » Thu May 09, 2013 21:33

Hey you are super,
in the moment I got an update and everything is working perfect. Nouveau is not perfect, you are absolutely right, but you are!
Thank you so much.

best regards

Artur
Last edited by asy1410 on Thu May 09, 2013 21:53, edited 1 time in total.
asy1410
Baby Hen
 
Posts: 17
Joined: Sun Apr 15, 2012 21:28

Re: Celestia and Googleearth doesn' start [Solved]

Postby asy1410 » Thu May 09, 2013 21:47

Moderator edit: Added Code tags. Please use Code button when posting lengthy console output

I would like to do it right in future and to learn. Please what is the Code button? How to use it? I'm coming from Mac and I was disappointed because they are leaving more and more the OS. I switched to Sabayon and in my opinion it is next generation of OS. Much better then all other I tested.

Thank you

Artur

:D at least in Sabayon is running more then in Mac and the troubles are less for me
asy1410
Baby Hen
 
Posts: 17
Joined: Sun Apr 15, 2012 21:28

Re: Celestia and Googleearth doesn' start [Solved]

Postby Fitzcarraldo » Thu May 09, 2013 23:58

asy1410, when you click on the 'New Topic' button or 'Post Reply' button (as opposed to the 'Quick Reply' button) you'll see a row of buttons along the top of the box in which you enter your text. If you click on those buttons they insert 'tags' in the box. For example, if I click on the B button then the following appears in the box at the current position of the cursor:

Code: Select all
[b][/b]

Any text you then enter between those two 'tags' appears in bold in the final post.

These tags are called BBCode tags, or just 'BBCode' for short.

If you click on the Code button then the following BBCode appears in the box at the current position of the cursor:

Code: Select all
[code][/code]

Any text you enter between the two code tags will appear in a code box in the post, and if there are many lines of text then the forum software (phpBB) automatically adds a scroll bar so that you can easily scroll up and down the text without having to scroll (or page up/down) the whole post.

Actually, you don't even need to click on those buttons if you know the BBCode tags by heart. For example, in typing this post I just typed the BBCode tags, as I know them well.

You can find various tutorials on BBCode on the Web, but the first one to read would be the one by the writers of phpBB: phpBB - BBCode guide. (You can use the URL button to create a link like the one I have just entered.)

Note that many forums use the phpBB software, and there are several versions of it. The SL forums are using phpBB3. Also, as phpBB is very configurable, forum creators and administrators do not always bother to include all the features, or they decide to configure things to look different from other forums that use phpBB. The SL forums don't support every single possible BBCode tag but include the most useful ones. For example, the following text:

Code: Select all
[s]Let's draw a line through this sentence.[/s]

looks like the following when I submit this post: Let's draw a line through this sentence.

In order to stop the phpBB software from parsing my examples above, I placed code tags around them. I did that because the code tags tell the phpBB software to assume anything between the code tags is source code that the poster wants to be quoted verbatim, i.e. exactly as it appears in the source code file or console output that the poster is quoting. So I fooled the phpBB software into displaying the BBCode tags by pretending it was source code.

I hope that helps you. Have fun posting!
User avatar
Fitzcarraldo
Sagely Hen
 
Posts: 7981
Joined: Sat Mar 10, 2007 5:40
Location: United Kingdom

Re: Celestia and Googleearth doesn' start [Solved]

Postby asy1410 » Sat May 11, 2013 19:18

Thank you very much for your effort Fitzcarraldo,

for me it's always a pleasure to learn.

Best regards

Artur
asy1410
Baby Hen
 
Posts: 17
Joined: Sun Apr 15, 2012 21:28


Return to Software in General

Who is online

Users browsing this forum: No registered users and 3 guests

cron