[SOLVED] Google Earth - grey screen

More GE problems.
Now, when I start GE, I get nothing displayed.  Just a blank, black screen where the Earth image should be and a blank, grey screen when I zoom in.  (Just to make it clear, all the menus, sidebars etc are displayed correctly, it's just the Earth display that's affected.)
Googling the issue shows that a number of people are experiencing this problem with Intel graphics drivers, but I have nvidia (nvidia-304xx driver) and the only suggested fix, to untick 'atmosphere' in the View menu, does not work.
Is anyone else experiencing this?
Does anyone have any suggestions as to what I can do?
Many thanks,
David Shaw
Last edited by dtmc (2013-02-01 19:32:25)

I experience the same problem with Google earth 7. I have "fixed" it by installing google-earth6 (available from the AUR).

Similar Messages

  • [SOLVED] Google Earth doesn't work with xf86-video-ati

    Hi all,
    I'm having a problem with the open-source ATI drivers.  I haven't had much luck finding out anything from anywhere else, so I'm hoping someone here can help.
    Whenever I start Google Earth, the graphics run EXTREMELY slowly, almost as if it's running on a system with low memory.  I'm running an Acer Extensa 4420 with an AMD Athlon 64 X2 dual-core 64-bit processor with 2GB of RAM.  As mentioned before, I'm running on the open-source xf86-video-ati drivers, but this is the only app that gives me problems.  GL screensavers run fine, and glxgears runs without any significant input.  Running Google Earth in terminal also gives no output. 
    And I'm not sure if this is related, but closing Google Earth also crashes X.
    Here's xorg.conf:
    Section "Module"
    Load "extmod"
    Load "dbe"
    Load "record"
    #Free86-DGA extension within that module.
    SubSection "extmod"
    Option "omit xfree86-dga" # don't initialise the DGA extension
    EndSubSection
    # This loads the font modules
    # Load "type1"
    Load "freetype"
    # Load "xtt"
    # This loads the GLX module
    Load "glx"
    # This loads the DRI module
    Load "dri"
    Load "drm"
    Load "synaptics"
    EndSection
    # Files section. This allows default font and rgb paths to be set
    Section "Files"
    # Multiple FontPath entries are allowed (which are concatenated together),
    # as well as specifying multiple comma-separated entries in one FontPath
    # command (or a combination of both methods)
    FontPath "/usr/share/fonts/misc"
    FontPath "/usr/share/fonts/100dpi:unscaled"
    FontPath "/usr/share/fonts/75dpi:unscaled"
    FontPath "/usr/share/fonts/TTF"
    FontPath "/usr/share/fonts/Type1"
    # FontPath "/usr/lib/X11/fonts/local/"
    # FontPath "/usr/lib/X11/fonts/misc/"
    # FontPath "/usr/lib/X11/fonts/75dpi/:unscaled"
    # FontPath "/usr/lib/X11/fonts/100dpi/:unscaled"
    # FontPath "/usr/lib/X11/fonts/Type1/"
    # FontPath "/usr/lib/X11/fonts/TrueType/"
    # FontPath "/usr/lib/X11/fonts/freefont/"
    # FontPath "/usr/lib/X11/fonts/75dpi/"
    # FontPath "/usr/lib/X11/fonts/100dpi/"
    # The module search path. The default path is shown here.
    # ModulePath "/usr/lib/modules"
    EndSection
    # Server flags section.
    Section "ServerFlags"
    # Uncomment this to cause a core dump at the spot where a signal is
    # received. This may leave the console in an unusable state, but may
    # provide a better stack trace in the core dump to aid in debugging
    # Option "NoTrapSignals"
    # Uncomment this to disable the <Ctrl><Alt><Fn> VT switch sequence
    # (where n is 1 through 12). This allows clients to receive these key
    # events.
    # Option "DontVTSwitch"
    # Uncomment this to disable the <Ctrl><Alt><BS> server abort sequence
    # This allows clients to receive this key event.
    Option "DontZap" "no"
    # Uncomment this to disable the <Ctrl><Alt><KP_+>/<KP_-> mode switching
    # sequences. This allows clients to receive these key events.
    # Option "Dont Zoom"
    # Uncomment this to disable tuning with the xvidtune client. With
    # it the client can still run and fetch card and monitor attributes,
    # but it will not be allowed to change them. If it tries it will
    # receive a protocol error.
    # Option "DisableVidModeExtension"
    # Uncomment this to enable the use of a non-local xvidtune client.
    # Option "AllowNonLocalXvidtune"
    # Uncomment this to disable dynamically modifying the input device
    # (mouse and keyboard) settings.
    # Option "DisableModInDev"
    # Uncomment this to enable the use of a non-local client to
    # change the keyboard or mouse settings (currently only xset).
    # Option "AllowNonLocalModInDev"
    Option "AutoAddDevices" "False"
    EndSection
    # Input devices
    # Core keyboard's InputDevice section
    Section "InputDevice"
    Identifier "Keyboard1"
    Driver "kbd"
    Option "AutoRepeat" "500 30"
    # Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
    # Option "Xleds" "1 2 3"
    # Option "LeftAlt" "Meta"
    # Option "RightAlt" "ModeShift"
    # To customise the XKB settings to suit your keyboard, modify the
    # lines below (which are the defaults). For example, for a non-U.S.
    # keyboard, you will probably want to use:
    # Option "XkbModel" "pc105"
    # If you have a US Microsoft Natural keyboard, you can use:
    # Option "XkbModel" "microsoft"
    # Then to change the language, change the Layout setting.
    # For example, a german layout can be obtained with:
    # Option "XkbLayout" "de"
    # or:
    # Option "XkbLayout" "de"
    # Option "XkbVariant" "nodeadkeys"
    # If you'd like to switch the positions of your capslock and
    # control keys, use:
    # Option "XkbOptions" "ctrl:swapcaps"
    # These are the default XKB settings for Xorg
    # Option "XkbRules" "xorg"
    # Option "XkbModel" "pc105"
    # Option "XkbLayout" "us"
    # Option "XkbVariant" ""
    # Option "XkbOptions" ""
    # Option "XkbDisable"
    Option "XkbRules" "xorg"
    Option "XkbModel" "acer_laptop"
    Option "XkbLayout" "us,de"
    Option "XkbOptions" "grp:lwin_switch,grp_led:num,eurosign:e"
    EndSection
    # Core Pointer's InputDevice section
    Section "InputDevice"
    # Identifier and driver
    Identifier "Mouse1"
    Driver "mouse"
    Option "Protocol" "Auto" # Auto detect
    Option "Device" "/dev/input/mice"
    # Mouse-speed setting for PS/2 mouse.
    # Option "Resolution" "256"
    # Baudrate and SampleRate are only for some Logitech mice. In
    # almost every case these lines should be omitted.
    # Option "BaudRate" "9600"
    # Option "SampleRate" "150"
    # Mouse wheel mapping. Default is to map vertical wheel to buttons 4 & 5,
    # horizontal wheel to buttons 6 & 7. Change if your mouse has more than
    # 3 buttons and you need to map the wheel to different button ids to avoid
    # conflicts.
    Option "ZAxisMapping" "4 5 6 7"
    # Emulate3Buttons is an option for 2-button mice
    # Emulate3Timeout is the timeout in milliseconds (default is 50ms)
    # Option "Emulate3Buttons"
    # Option "Emulate3Timeout" "50"
    # ChordMiddle is an option for some 3-button Logitech mice
    # Option "ChordMiddle"
    EndSection
    Section "InputDevice"
    Identifier "Touchpad"
    Driver "synaptics"
    Option "AlwaysCore" "true" # send events to CorePointer
    #Option "Device" "/dev/input/mice"
    Option "Device" "/dev/psaux"
    Option "Protocol" "auto-dev"
    Option "SHMConfig" "false" # configurable at runtime? security risk
    Option "LeftEdge" "1700" # x coord left
    Option "RightEdge" "5300" # x coord right
    Option "TopEdge" "1700" # y coord top
    Option "BottomEdge" "4200" # y coord bottom
    Option "FingerLow" "25" # pressure below this level triggers release
    Option "FingerHigh" "30" # pressure above this level triggers touch
    Option "MaxTapTime" "180" # max time in ms for detecting tap
    Option "VertEdgeScroll" "true" # enable vertical scroll zone
    Option "HorizEdgeScroll" "true" # enable horizontal scroll zone
    Option "CornerCoasting" "true" # enable continuous scroll with finger in corner
    Option "CoastingSpeed" "0.30" # corner coasting speed
    Option "VertScrollDelta" "100" # edge-to-edge scroll distance of the vertical scroll
    Option "HorizScrollDelta" "100" # edge-to-edge scroll distance of the horizontal scroll
    Option "MinSpeed" "0.10" # speed factor for low pointer movement
    Option "MaxSpeed" "0.60" # maximum speed factor for fast pointer movement
    Option "AccelFactor" "0.0020" # acceleration factor for normal pointer movements
    Option "VertTwoFingerScroll" "true" # vertical scroll anywhere with two fingers
    Option "HorizTwoFingerScroll" "true" # horizontal scroll anywhere with two fingers
    Option "TapButton1" "1"
    Option "TapButton2" "2"
    EndSection
    # Other input device sections
    # this is optional and is required only if you
    # are using extended input devices. This is for example only. Refer
    # to the xorg.conf man page for a description of the options.
    # Section "InputDevice"
    # Identifier "Mouse2"
    # Driver "mouse"
    # Option "Protocol" "MouseMan"
    # Option "Device" "/dev/mouse2"
    # EndSection
    # Section "InputDevice"
    # Identifier "spaceball"
    # Driver "magellan"
    # Option "Device" "/dev/cua0"
    # EndSection
    # Section "InputDevice"
    # Identifier "spaceball2"
    # Driver "spaceorb"
    # Option "Device" "/dev/cua0"
    # EndSection
    # Section "InputDevice"
    # Identifier "touchscreen0"
    # Driver "microtouch"
    # Option "Device" "/dev/ttyS0"
    # Option "MinX" "1412"
    # Option "MaxX" "15184"
    # Option "MinY" "15372"
    # Option "MaxY" "1230"
    # Option "ScreenNumber" "0"
    # Option "ReportingMode" "Scaled"
    # Option "ButtonNumber" "1"
    # Option "SendCoreEvents"
    # EndSection
    # Section "InputDevice"
    # Identifier "touchscreen1"
    # Driver "elo2300"
    # Option "Device" "/dev/ttyS0"
    # Option "MinX" "231"
    # Option "MaxX" "3868"
    # Option "MinY" "3858"
    # Option "MaxY" "272"
    # Option "ScreenNumber" "0"
    # Option "ReportingMode" "Scaled"
    # Option "ButtonThreshold" "17"
    # Option "ButtonNumber" "1"
    # Option "SendCoreEvents"
    # EndSection
    # Monitor section
    # Any number of monitor sections may be present
    Section "Monitor"
    Identifier "Acer Laptop"
    # HorizSync is in kHz unless units are specified.
    # HorizSync may be a comma separated list of discrete values, or a
    # comma separated list of ranges of values.
    # NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
    # USER MANUAL FOR THE CORRECT NUMBERS.
    HorizSync 31.5 - 57.0
    # HorizSync 30-64 # multisync
    # HorizSync 31.5, 35.2 # multiple fixed sync frequencies
    # HorizSync 15-25, 30-50 # multiple ranges of sync frequencies
    # VertRefresh is in Hz unless units are specified.
    # VertRefresh may be a comma separated list of discrete values, or a
    # comma separated list of ranges of values.
    # NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
    # USER MANUAL FOR THE CORRECT NUMBERS.
    VertRefresh 50-90
    EndSection
    # Graphics device section
    # Any number of graphics device sections may be present
    # Standard VGA Device:
    Section "Device"
    Identifier "Standard VGA"
    VendorName "Unknown"
    BoardName "Unknown"
    # The chipset line is optional in most cases. It can be used to override
    # the driver's chipset detection, and should not normally be specified.
    # Chipset "generic"
    # The Driver line must be present. When using run-time loadable driver
    # modules, this line instructs the server to load the specified driver
    # module. Even when not using loadable driver modules, this line
    # indicates which driver should interpret the information in this section.
    Driver "vga"
    # The BusID line is used to specify which of possibly multiple devices
    # this section is intended for. When this line isn't present, a device
    # section can only match up with the primary video device. For PCI
    # devices a line like the following could be used. This line should not
    # normally be included unless there is more than one video device
    # intalled.
    # BusID "PCI:0:10:0"
    # VideoRam 256
    # Clocks 25.2 28.3
    EndSection
    # Device configured by xorgconfig:
    Section "Device"
    Identifier "ATI Radeon"
    Driver "radeon"
    #VideoRam 262144
    # Insert Clocks lines here if appropriate
    Option "AGPMode" "4"
    Option "ColorTiling" "on"
    Option "AccelMethod" "EXA"
    Option "EnablePageFlip" "on"
    Option "AGPFastWrite" "yes"
    Option "EXAVSync" "yes"
    Option "ForceTVOut" "true"
    Option "TVStandard" "ntsc"
    EndSection
    # Screen sections
    # Any number of screen sections may be present. Each describes
    # the configuration of a single screen. A single specific screen section
    # may be specified from the X server command line with the "-screen"
    # option.
    Section "Screen"
    Identifier "Screen 1"
    Device "ATI Radeon"
    Monitor "Acer Laptop"
    DefaultDepth 24
    Subsection "Display"
    Depth 8
    Modes "1280x1024" "1024x768" "800x600" "640x480"
    ViewPort 0 0
    EndSubsection
    Subsection "Display"
    Depth 16
    Modes "1280x1024" "1024x768" "800x600" "640x480"
    ViewPort 0 0
    EndSubsection
    Subsection "Display"
    Depth 24
    Modes "1200x800"
    ViewPort 0 0
    EndSubsection
    EndSection
    # ServerLayout sections.
    # Any number of ServerLayout sections may be present. Each describes
    # the way multiple screens are organised. A specific ServerLayout
    # section may be specified from the X server command line with the
    # "-layout" option. In the absence of this, the first section is used.
    # When now ServerLayout section is present, the first Screen section
    # is used alone.
    Section "ServerLayout"
    # The Identifier line must be present
    Identifier "Simple Layout"
    # Each Screen line specifies a Screen section name, and optionally
    # the relative position of other screens. The four names after
    # primary screen name are the screens to the top, bottom, left and right
    # of the primary screen. In this example, screen 2 is located to the
    # right of screen 1.
    Screen "Screen 1"
    # Each InputDevice line specifies an InputDevice section name and
    # optionally some options to specify the way the device is to be
    # used. Those options include "CorePointer", "CoreKeyboard" and
    # "SendCoreEvents".
    InputDevice "Mouse1" "CorePointer"
    InputDevice "Touchpad" "SendCoreEvents"
    InputDevice "Keyboard1" "CoreKeyboard"
    EndSection
    Section "DRI"
    Mode 0666
    EndSection
    Here's my drirc:
    <driconf>
    <device screen="0" driver="r300">
    <application name="Default">
    <option name="force_s3tc_enable" value="false" />
    <option name="texture_coord_units" value="8" />
    <option name="fthrottle_mode" value="2" />
    <option name="disable_stencil_two_side" value="false" />
    <option name="tcl_mode" value="3" />
    <option name="texture_depth" value="0" />
    <option name="fp_optimization" value="0" />
    <option name="def_max_anisotropy" value="1.0" />
    <option name="no_rast" value="false" />
    <option name="command_buffer_size" value="8" />
    <option name="round_mode" value="0" />
    <option name="dither_mode" value="0" />
    <option name="disable_lowimpact_fallback" value="true" />
    <option name="texture_image_units" value="8" />
    <option name="disable_s3tc" value="false" />
    <option name="color_reduction" value="1" />
    <option name="vblank_mode" value="1" />
    </application>
    <application name="Google Earth" executable="googleearth">
    </application>
    </device>
    </driconf>
    Last edited by coolpyrofreak (2009-07-03 05:56:18)

    I had the same problem (slow googleearth) with ATI Technologies Inc Radeon Mobility U1 (IGP 320m).
    This .drirc solves it. I don't have an xorg.conf.
    - no need for the 'disable_lowimpact_fallback' option
    - no need to turn off 'atmosphere'
    cat .drirc
    <driconf>
    <device screen="0" driver="radeon">
    <application name="Default">
    <option name="force_s3tc_enable" value="false" />
    <option name="no_rast" value="false" />
    <option name="fthrottle_mode" value="2" />
    <option name="tcl_mode" value="3" />
    <option name="texture_depth" value="0" />
    <option name="def_max_anisotropy" value="1.0" />
    <option name="no_neg_lod_bias" value="false" />
    <option name="texture_units" value="3" />
    <option name="dither_mode" value="0" />
    <option name="hyperz" value="true" />
    <option name="round_mode" value="0" />
    <option name="color_reduction" value="1" />
    <option name="vblank_mode" value="0" />
    <option name="allow_large_textures" value="1" />
    </application>
    </device>
    </driconf>

  • [Solved] Google Earth has caught signal 11

    I'm trying to run Google Earth 7 (latest, AUR: google-earth), but it alway crash after splash screen, output from terminal:
    aurelio@Victor-A /opt/google/earth/free % google-earth
    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/aurelio/.googleearth/crashlogs/crashlog-516f104c.txt
    Please include this file if you submit a bug report to Google.
    and file crashlog-516f104c.txt :
    Major Version 7
    Minor Version 0
    Build Number 0003
    Build Date Feb 26 2013
    Build Time 17:19:26
    OS Type 3
    OS Major Version 3
    OS Minor Version 8
    OS Build Version 4
    OS Patch Version 0
    Crash Signal 11
    Crash Time 1366233164
    Up Time 1.72212
    Stacktrace from glibc:
    ./libgoogleearth_free.so(+0x1e9f8b)[0xf7611f8b]
    ./libgoogleearth_free.so(+0x1ea1d3)[0xf76121d3]
    linux-gate.so.1(__kernel_sigreturn+0x0)[0xf77c4400]
    Thanks in advance!
    Last edited by hotvic (2013-04-18 22:06:54)

    I've got google-earth alongside google-earth6 and for some reason it isn't working on x86_64, but it is working on i686.  It gives me this crashlog:
    Major Version 6
    Minor Version 2
    Build Number 0002
    Build Date Apr 14 2012
    Build Time 01:09:37
    OS Type 3
    OS Major Version 3
    OS Minor Version 15
    OS Build Version 5
    OS Patch Version 0
    Crash Signal 11
    Crash Time 1405604918
    Up Time 4.43429
    Stacktrace from glibc:
    ./libgoogleearth_free.so(+0xc645b)[0xf76d445b]
    ./libgoogleearth_free.so(+0xc66a3)[0xf76d46a3]
    linux-gate.so.1(__kernel_sigreturn+0x0)[0xf7786b20]
    /opt/google/earth/legacy/libmeasure.so(_ZN5earth7measure5state19MeasureStateContext10OnLoggedInERKNS_4evll11StatusEventE+0x22)[0xe93f3a82]
    /opt/google/earth/legacy/libevll.so(_ZN5earth4evll21ConnectionContextImpl11FinishLoginEv+0x4ce)[0xf2d7dc3e]
    /opt/google/earth/legacy/libevll.so(_ZN5earth4evll7APIImpl17NotifyInitializedEv+0x165)[0xf2a5c5c5]
    /opt/google/earth/legacy/libevll.so(_ZN5earth4evll17RenderContextImpl4initERKNS0_8InitInfoE+0x362)[0xf29db8b2]
    ./librender.so(_ZN12RenderWidget6SetApiEPN5earth4evll3APIE+0x83)[0xf4890b13]
    ./librender.so(_ZN5earth6render12RenderWindow12createWidgetEv+0x148)[0xf4876418]
    ./libgoogleearth_free.so(_ZN5earth6client12ModuleWidget9showEventEP10QShowEvent+0x85)[0xf76a23b5]
    ./libQtGui.so.4(_ZN7QWidget5eventEP6QEvent+0x770)[0xf6a45a60]
    ./libQtGui.so.4(_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent+0xac)[0xf69e269c]
    ./libQtGui.so.4(_ZN12QApplication6notifyEP7QObjectP6QEvent+0x484)[0xf69ed6c4]
    ./libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x78)[0xf7479ba8]
    ./libQtGui.so.4(_ZN14QWidgetPrivate11show_helperEv+0x145)[0xf6a476d5]
    ./libQtGui.so.4(_ZN14QWidgetPrivate14show_recursiveEv+0x7d)[0xf6a473cd]
    ./libQtGui.so.4(_ZN14QWidgetPrivate12showChildrenEb+0xc5)[0xf6a474b5]
    ./libQtGui.so.4(_ZN14QWidgetPrivate11show_helperEv+0x61)[0xf6a475f1]
    ./libQtGui.so.4(_ZN7QWidget10setVisibleEb+0x1db)[0xf6a47a2b]
    ./libQtGui.so.4(_ZN14QWidgetPrivate12showChildrenEb+0x170)[0xf6a47560]
    ./libQtGui.so.4(_ZN14QWidgetPrivate11show_helperEv+0x61)[0xf6a475f1]
    ./libQtGui.so.4(_ZN14QWidgetPrivate14show_recursiveEv+0x7d)[0xf6a473cd]
    ./libQtGui.so.4(_ZN14QWidgetPrivate12showChildrenEb+0xc5)[0xf6a474b5]
    ./libQtGui.so.4(_ZN14QWidgetPrivate11show_helperEv+0x61)[0xf6a475f1]
    ./libQtGui.so.4(_ZN7QWidget10setVisibleEb+0x1db)[0xf6a47a2b]
    ./libQtGui.so.4(_ZN14QWidgetPrivate12showChildrenEb+0x170)[0xf6a47560]
    ./libQtGui.so.4(_ZN14QWidgetPrivate11show_helperEv+0x61)[0xf6a475f1]
    ./libQtGui.so.4(_ZN14QWidgetPrivate14show_recursiveEv+0x7d)[0xf6a473cd]
    ./libQtGui.so.4(_ZN14QWidgetPrivate12showChildrenEb+0xc5)[0xf6a474b5]
    ./libQtGui.so.4(_ZN14QWidgetPrivate11show_helperEv+0x61)[0xf6a475f1]
    ./libQtGui.so.4(_ZN7QWidget10setVisibleEb+0x1db)[0xf6a47a2b]
    ./libQtGui.so.4(_ZN14QWidgetPrivate12showChildrenEb+0x170)[0xf6a47560]
    ./libQtGui.so.4(_ZN14QWidgetPrivate11show_helperEv+0x61)[0xf6a475f1]
    ./libQtGui.so.4(_ZN7QWidget10setVisibleEb+0x1db)[0xf6a47a2b]
    ./libQtGui.so.4(_ZN14QWidgetPrivate12showChildrenEb+0x170)[0xf6a47560]
    ./libQtGui.so.4(_ZN14QWidgetPrivate11show_helperEv+0x61)[0xf6a475f1]
    ./libQtGui.so.4(_ZN7QWidget10setVisibleEb+0x1db)[0xf6a47a2b]
    ./libQtGui.so.4(_ZN14QWidgetPrivate12showChildrenEb+0x170)[0xf6a47560]
    ./libQtGui.so.4(_ZN14QWidgetPrivate11show_helperEv+0x61)[0xf6a475f1]
    ./libQtGui.so.4(_ZN7QWidget10setVisibleEb+0x1db)[0xf6a47a2b]
    ./libQtGui.so.4(_ZN7QWidget10showNormalEv+0x5c)[0xf6a3516c]
    ./libgoogleearth_free.so(_ZN10MainWindow18readScreensizeInfoEv+0xdef)[0xf769bacf]
    ./libgoogleearth_free.so(_ZN5earth6client11Application12SetupMainWinENS0_3Kvw7ProductEb+0x334)[0xf76db8c4]
    ./libgoogleearth_free.so(_ZN5earth6client11Application3runEv+0x7d2)[0xf76e2e22]
    ./libgoogleearth_free.so(+0xc511b)[0xf76d311b]
    ./libgoogleearth_free.so(earthmain+0x249)[0xf76d36f9]
    ./googleearth-bin[0x804878b]
    /usr/lib32/libc.so.6(__libc_start_main+0xde)[0xf512be2e]
    I have google-earth installed because I keep having problems with google-earth6, but google-earth is painfully nonresponsive.  (Break a new thread if necessary, but it is Signal 11).  The font thing is moved to aur, and rebuilding the package from scratch doesn't change anything.

  • [SOLVED]google earth - black layout menu

    I have installed google earth, everything runs, just menu layout is in black color - menu is readable.. what should be white in menu layout is black and font is grey
    nvidia binary installed
    Last edited by xhc (2012-06-24 12:09:38)

    solution was in root directory in file: gtkrc-2.0

  • [SOLVED]Google Earth and LSB

    Good Morning Fellow Archers,
    I've got an up to date x64 Arch install. I wanted to install Google-Earth from the AUR but was not able. I tried both packages, and both of them are failing looking for LSB-3. The current LSB in the repository is rev 4.
    I followed one thread where I manually created a link for a lsb-3 install, and both google-earth packages still fail.
    I do have the multi-libs enabled as I have one app that uses wine32 and it's happy. And the NVidia lib32 stuff is all there too.
    I have X-Plane 9, which is a 32 bit app only, and it runs fine so I know the x32libs are all in place and working.
    I think the long-term solve is for the google-earth AUR maintainers to square away their builds for lsb-4....but I'm not an expert in package builds or I'd jump in and help.....but reality is that I am not an expert.
    In the meantime....how do I make this work without pounding a 'square' peg into a 'round' hole?
    Assistance will be sincerely appreciated!
    Dave
    PS: Yes...I did try to follow the wiki article too.....
    Last edited by dcbdbis (2011-03-03 19:21:36)

    Thank you for the response. I have it installed and it works perfectly. THANK YOU.
    The solve was simple. I was brain-locked on the lsb in the arch repository, and was not taking note of that I needed the lsb from the AUR.
    This was totally my error.
    Again, thank you for the response.
    Dave............

  • [SOLVED] google earth strange interface

    hello there. I'm actually using the google-earth version: 5.1.3509.4636-2
    I got a bar which I cannot remove. How can I solve this?
    Last edited by quarkup (2009-12-18 12:57:11)

    okay it is solved.
    using different theme for google earth than bespin solves the problem.
    just add in the Exec entry of the .desktop file the '-style oxygen' flag
    the file is located in /usr/share/applications/googleearth.desktop
    [Desktop Entry]
    Encoding=UTF-8
    Name=Google Earth
    GenericName=3D planet viewer
    Comment=Explore, search and discover the planet
    Exec=/usr/bin/googleearth -style oxygen %f
    Terminal=false
    MultipleArgs=false
    Type=Application
    Icon=/usr/share/pixmaps/googleearth-icon.png
    Categories=Application;Network
    MimeType=application/vnd.google-earth.kml+xml;application/vnd.google-earth.kmz;application/earthviewer;application/keyhole
    or change the google-earth launcher /usr/bin/googleearth
    and add the flag. should be something as simple as
    #!/bin/sh
    GOOGLEEARTH_DATA_PATH="/opt/google-earth"
    LD_LIBRARY_PATH=.:${GOOGLEEARTH_DATA_PATH}:${LD_LIBRARY_PATH}
    export LD_LIBRARY_PATH
    cd "${GOOGLEEARTH_DATA_PATH}/"
    exec "./googleearth-bin" -style oxygen $*
    Last edited by quarkup (2009-12-18 13:25:35)

  • [SOLVED] Google Earth signal 11 again

    I'm getting the now infamous 'signal 11' error when trying to run Google Earth.
    I've tried the suggestions in https://bbs.archlinux.org/viewtopic.php?id=114992 with no luck and also reinstalling GE and all its dependencies.
    Does anyone have any more ideas I can try?
    System is i686 with nvidia graphics.  Crash log is at http://pastebin.com/W4X4AgXd
    Many thanks,
    David Shaw
    Last edited by dtmc (2013-01-02 22:28:37)

    I was caught out by "GE has caught signal 11" a couple of days ago (using nouveau driver with nvidia hardware). I don't have any .drirc or dri file (as mentioned in old thread 114992). However, I copied librarian.launchpad.net/7037027/libGL.so.1 into the directory /opt/google/earth/free/, and this got GE working, although the video quality wasn't so good. Then I installed ia32-libs in my copy of debian in virtualbox, then copied /usr/lib32/libGL.so.1.2 from there, as libGL.so.1, back to arch to replace the one from launchpad.net. GE is now working perfectly.
    I don't really understand any of the above. This is my 2nd installation, on a separate drive, but otherwise using the same hardware as the first, which was done using the official media. This one is from releng.archlinux.org, 2012/04/10_04, netinstall, x86_64. On the first, I couldn't get alsa to work and had to use oss for sound. With this one, alsa worked out the box, which is very nice. However, in addition to this google earth thing, I had significant trouble configuring an automatic wireless connection, and a problem with my samba server.
    Oops - I had failed to install lib32-nouveau-dri !!!
    Last edited by pralias47 (2012-05-07 06:10:39)

  • [solved] Google Earth does not show embedded pictures

    I'm using the Google Earth AUR package.
    When I click on the little blue squares in the satellite view, only a big white placeholder window for the picture is shown, but no picture is embedded. Only a small question mark is shown in the middle of a the rather large white window, clicking on it brings me to Firefox, showing the picture in Panoramio. Please help me! How can I enable the embedded pictures?
    Last edited by SanskritFritz (2009-03-31 07:53:17)

    oops, forgot this, sorry
    [frank@HomeC ~]$ LD_LIBRARY_PATH="/opt/google-earth/" ldd /opt/google-earth/googleearth-bin
    linux-gate.so.1 => (0xb8011000)
    libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0xb7fe1000)
    libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0xb7ef0000)
    libQtCore.so.4 => /usr/lib/libQtCore.so.4 (0xb7d2c000)
    libQtGui.so.4 => /usr/lib/libQtGui.so.4 (0xb75dd000)
    libQtNetwork.so.4 => /usr/lib/libQtNetwork.so.4 (0xb751b000)
    libQtWebKit.so.4 => /usr/lib/libQtWebKit.so.4 (0xb6e1c000)
    libgoogleearth_lib.so => /opt/google-earth/libgoogleearth_lib.so (0xb6d04000)
    libm.so.6 => /lib/libm.so.6 (0xb6cde000)
    libc.so.6 => /lib/libc.so.6 (0xb6b97000)
    libpthread.so.0 => /lib/libpthread.so.0 (0xb6b7f000)
    libbase.so => /opt/google-earth/libbase.so (0xb6acb000)
    libge_net.so => /opt/google-earth/libge_net.so (0xb6a7c000)
    libgeobase.so => /opt/google-earth/libgeobase.so (0xb6759000)
    /lib/ld-linux.so.2 (0xb8012000)
    libz.so.1 => /usr/lib/libz.so.1 (0xb6745000)
    libgthread-2.0.so.0 => /usr/lib/libgthread-2.0.so.0 (0xb6741000)
    librt.so.1 => /lib/librt.so.1 (0xb6737000)
    libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0xb6682000)
    libdl.so.2 => /lib/libdl.so.2 (0xb667e000)
    libpng12.so.0 => /usr/lib/libpng12.so.0 (0xb6658000)
    libSM.so.6 => /usr/lib/libSM.so.6 (0xb6650000)
    libICE.so.6 => /usr/lib/libICE.so.6 (0xb6637000)
    libXi.so.6 => /usr/lib/libXi.so.6 (0xb662f000)
    libXrender.so.1 => /usr/lib/libXrender.so.1 (0xb6627000)
    libXrandr.so.2 => /usr/lib/libXrandr.so.2 (0xb6621000)
    libXfixes.so.3 => /usr/lib/libXfixes.so.3 (0xb661c000)
    libXcursor.so.1 => /usr/lib/libXcursor.so.1 (0xb6613000)
    libXinerama.so.1 => /usr/lib/libXinerama.so.1 (0xb660f000)
    libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0xb658a000)
    libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0xb655f000)
    libXext.so.6 => /usr/lib/libXext.so.6 (0xb6550000)
    libX11.so.6 => /usr/lib/libX11.so.6 (0xb6433000)
    libssl.so.0.9.8 => /usr/lib/libssl.so.0.9.8 (0xb63eb000)
    libcrypto.so.0.9.8 => /usr/lib/libcrypto.so.0.9.8 (0xb6295000)
    libsqlite3.so.0 => /usr/lib/libsqlite3.so.0 (0xb621b000)
    libIGCore.so => /opt/google-earth/libIGCore.so (0xb6124000)
    libIGUtils.so => /opt/google-earth/libIGUtils.so (0xb60fc000)
    libapiloader.so => /opt/google-earth/libapiloader.so (0xb60f8000)
    libauth.so => /opt/google-earth/libauth.so (0xb6061000)
    libcommon.so => /opt/google-earth/libcommon.so (0xb5f7c000)
    libcomponentframework.so => /opt/google-earth/libcomponentframework.so (0xb5f72000)
    libmath.so => /opt/google-earth/libmath.so (0xb5f3c000)
    libmoduleframework.so => /opt/google-earth/libmoduleframework.so (0xb5f2e000)
    libport.so => /opt/google-earth/libport.so (0xb5f24000)
    librender.so => /opt/google-earth/librender.so (0xb5e8f000)
    libIGMath.so => /opt/google-earth/libIGMath.so (0xb5e46000)
    ./libminizip.so => not found
    libfusioncommon.so => /opt/google-earth/libfusioncommon.so (0xb5e40000)
    libcurl.so.4 => /usr/lib/libcurl.so.4 (0xb5dfe000)
    ./libminizip.so => not found
    ./libminizip.so => not found
    libpcre.so.0 => /lib/libpcre.so.0 (0xb5dcc000)
    libuuid.so.1 => /lib/libuuid.so.1 (0xb5dc8000)
    libexpat.so.1 => /usr/lib/libexpat.so.1 (0xb5da2000)
    libXau.so.6 => /usr/lib/libXau.so.6 (0xb5d9e000)
    libxcb.so.1 => /usr/lib/libxcb.so.1 (0xb5d85000)
    libGL.so.1 => /usr/lib/libGL.so.1 (0xb5ccb000)
    libGLU.so.1 => /usr/lib/libGLU.so.1 (0xb5c5c000)
    libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0xb5c56000)
    libGLcore.so.1 => /usr/lib/libGLcore.so.1 (0xb4d40000)
    libnvidia-tls.so.1 => /usr/lib/libnvidia-tls.so.1 (0xb4d3e000)

  • [***SOLVED***] Google Earth

    I tried today to Install Google Earth from the Google Sources.
    [jada@arch-01 ~]$ su
    Password:
    [root@arch-01 jada]# cd /home/jada/install
    [root@arch-01 install]# ./GoogleEarthLinux.bin
    bash: ./GoogleEarthLinux.bin: Permission denied
    Permission denied ?
    What did I make wrong?
    Last edited by JaDa (2007-08-09 21:36:00)

    Thank's @pressh & @Fackamato
    The "work around" I got from here !
    wrote:Root doesn't have permission to connect to your X server.
    http://gentoo-wiki.com/HOWTO_X.org#Allo … r_su.27ing:
    Allow root to start X applications after su'ing:
    File: /etc/profile
    export XAUTHORITY="${HOME}/.Xauthority"
    Thank's all

  • Google earth crashing[SOLVED]

    The current AUR PKGBUILD doesn't run on this system.  I have an ati x200m using opensource drivers (radeon).  I installed an older package 5.0.xx and I get less errors but it still crashes.  I am guessing this is a video issue, but whatever it is I can't google a way to fix it.  Any suggestions?
    Failed to load "/opt/google-earth/libevll.so" because "/opt/google-earth/libevll.so: undefined symbol: gluNewTess"
    EDIT: I've also rebuilt with this version - google-earth-5.1.3535.3218-1, I am getting the same error message.
    EDIT SOLVED: I needed to install freeglut.  This was not necessary on my desktop because I am using nvidia drivers.
    Last edited by empthollow (2010-07-19 05:45:53)

    The current AUR PKGBUILD doesn't run on this system.  I have an ati x200m using opensource drivers (radeon).  I installed an older package 5.0.xx and I get less errors but it still crashes.  I am guessing this is a video issue, but whatever it is I can't google a way to fix it.  Any suggestions?
    Failed to load "/opt/google-earth/libevll.so" because "/opt/google-earth/libevll.so: undefined symbol: gluNewTess"
    EDIT: I've also rebuilt with this version - google-earth-5.1.3535.3218-1, I am getting the same error message.
    EDIT SOLVED: I needed to install freeglut.  This was not necessary on my desktop because I am using nvidia drivers.
    Last edited by empthollow (2010-07-19 05:45:53)

  • Google Earth shows white screen

    Hi I am using Arch Linux 64 bit latest. I have an nvidia graphics card (8600 GTS). I have installed google earth from the AUR and from the google earth website but with both of them they just show a white screen. Help Anyone?

    Well heck, right now I'm running Mandriva 2009.0 x86-64 and GE is not in repos, and from google.com it cant find GTK libraries! Then I installed it using an RPM and it installed the libs so I'm good.
    Anyhow, back to work. I was searching for GE 64 bit errors and found this message. I read in another message that you should try going to [View]->[Atomosphere] and disable that (im on Windows away from home right now so I cant see if that option still exists, esp. since this is not my computer LOL) and see if that fixes your problem. If not, there was an issue with Mono once that caused GE to show a white screen the more you zoomed in. Maybe thats it? IDK cuz I havent used Arch in over a month and a quarter now so...

  • Grey screen with apple logo and buffering how to solve problem ?

    When starting my mac book pro it comes up with the grey screen with the apple logo and the buffering symbol , I have tried to reboot in safe mode and that doesn't work. I do not have my installation disc for the OS X 10.7.5 and was wondering if I used an external hard drive to back up all my files and then got a lion installation USB from amazon, would that solve my problem and make sure I don't lose my files ? Do you have any other suggestions ?

    Please read this whole message before doing anything.
    This procedure is a diagnostic test. It won’t solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
    The purpose of this exercise is to determine whether the problem is caused by third-party system modifications that load automatically at startup or login. Boot in safe mode. First, disconnect all wired peripherals except keyboard, mouse, and monitor, if applicable. The instructions provided by Apple are as follows:
    Be sure your Mac is shut down.
    Press the power button.
    Immediately after you hear the startup tone, hold the Shift key. The Shift key should be held as soon as possible after the startup tone, but not before the tone.
    Release the Shift key when you see the gray Apple icon and the progress indicator (looks like a spinning gear).
    During startup, you will see "Safe Boot" on the login screen, which appears even if you normally log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
    Safe mode is slower than normal, and some things won’t work at all, including your login items.
    Same problem?
    After testing, reboot as usual (i.e., not in safe mode.)

  • Grey screen after update (Solved)

    I solved this one myself eventually, but it took several hours.
    After updating one of the MacBook Pros in my office, the computer was stuck at the grey screeb (Apple Logo and spinning wheel) and would not progress.
    1) First I rebooted the computer (no luck)
    2) Then I booted from an install DVD and checked for errors (no errors reported)
    3) Then I did a "repair permissions", which did find and repair some permissions
    3a) Then I repeated the "verify disk" which again reported no errors.
    4) Then I rebooted in safe mode, but it still would not progress past the grey screen.
    5) Then I rebooted in verbose mode, and saw the error that LoginWindow was crashing.
    6) I rebooted in Single User Mode, since I am familiar with Unix and Linux.
    I looked in the /Library/Logs/CrashReporter/ folder, and there were a LOT of files with loginwindow-timestamp-computername.dump where timestamp is the date/time of the crash and computername is the name of the computer.
    The most recent of these reports that a library /usr/lib/libbz2.1.0.dylib is missing.
    I looked on a different MacBook Pro, and behold ls -l tells me that libbz2.1.0.dylib should be a symbolic link to libbz2.1.0.5.dylib (the newer file DOES exist on the machine that will not boot)
    The following steps will be "scary" for anyone not familiar with Unix / Linux command line, but they resulted in the computer booting
    mount -w /
    (remount the hard disk with write permissions)
    cd /usr/lib
    (change to the folder with the missing file pointer)
    ln -s libbz2.1.0.5.dylib libbz2.1.0.dylib
    (create the missing symbolic link)
    reboot
    (command to restart the computer)
    and IT WORKED
    The computer in question is now working, and reports that it is running version 10.5.8

    Hello,
    I've had this problem twice, and each occurred after a security update.
    What helped me was the following:
    -Take out your powercord and your battery. Press the power button for about 5 seconds.
    -Then, insert your battery and powercord, start the computer, and hold down AppleCTRL+PR.
    From what I understand, one of these two steps resets the power management system on the macbook.
    After you perform these two steps, your computer may still hang at the grey screen with the apple logo. However! Let it hang for about 5-10 minutes and it will automatically restart, and boot properly.
    You can also try calling Apple support on your friend's behalf ... they were more than helpful.
    Blackbook Core Duo   Mac OS X (10.4.9)  

  • Google Earth only shows black screen with yellow lines on Lion 10.7

    Hi, I am having trouble with running the Google Earth plug in my browser. Everytime I switch to "earth" mode, all I see is a black screen and yellow lines. I was able to rectify the issue in Google Earth itself by turning off Atmosphere but I can't do that in my browser and I use a website that utilizes Google Earth within a browser, so I'd really like to figure this out. I'm running Lion 10.7 on a X1600 128 MB dedicated graphics card. Maybe the graphics card is not good enough? Although I would have thought it could handle Google Earth.... Any ideas? Thanks!

    Hi thanks for all the concern and replies. I've tried all that.
    I had just got it back from the shop last Friday. It was there for around two weeks. It was a faulty GPU (when you see garbled display that's consisten when booting it the GPU). I have a strong feeling it's related to the Lion install 10.7 or 10.7.1 and may be similar to reports of Mac laptops overheating. It's good the GPU is removable, it might have taken 3 week or a month if it had been the whole board.
    It's a blessing in disguise though as with all or most cases because I also got to have the LCD replaced for excessive backlight bleeding (in my opinion), the dead pixel from the previous LCD isn't there anymore (though under the glass there're some smudges but nothing crucial). The backlight bleeding is still the same though in my opinion but at least it's new.
    It's a great thing I bought Applecare. I didn't buy it for the iPhone because that's more durable (my iPhone 3G's 3 years old now and it's still solid. Although there are scratches and a crack at the back at the bottom, got sqeezed under the table I think when I sat). I think Applecare is a good recommend for things that get hot like desktop and laptop Macs(are the iOS considered Macs btw?) which are twice or thrice the price of iOS devices.
    Gbu.

  • Google Earth Screen Capture

    Does anyone know of a way to capture the effect of Google Earth zeroing in on a location. For example, I am editing some hunting footage from an area in Texas and would like to show a graphic zooming in from a shot of the entire US to a much smaller area. I can get it on my screen in Google Earth, but can I capture that and pull it into FCE?

    I did this for free using a screen capture tool called Copernicus that allows you to capture a quicktime video directly from selected portions of your screen. It was tricky because the frame capture rate was only 2 frames per second with the CPU load of google earth doing its thing. I got around this by changing Google Earth's flying speed in its preferences->touring tab. I was able to crop out the text at the bottom of the frame by sizing the google earth window to larger than 640x480 and then capturing only the center portion of the window. If you want to get 720x480, you need to make sure your window width is greater than 720 wide, which oversamples the vertical. This gets sampled down when you take it to video editing.
    If you want to spend money on it, I seem to remember somewhere in the on-line Google Earth Plus or Pro documentation seeing something about being able to record Google Earth output directly to a video file. This would obviously be a lot better quality, without all the frame-rate handsprings I had to go through. I guess the money must have been more than I was interested in spending at the time.
    PS. For an extra cool effect, start with the entire globe visible, and flick it west to east to get the world spinning, then click your location to get the fly-in to start. Its tricky to get it spinning at a slow enough speed, but the result is quite nifty.

Maybe you are looking for