Results 1 to 3 of 3

Thread: Missing mesa-libGLU for Google Earth

  1. #1

    Default Missing mesa-libGLU for Google Earth

    I am back to the nouveau driver, as Nvidia dumped support for my graphics card in the latest 396.18 installer. Everything seems to work with nouveau, with one exception: Google Earth now offers a splash screen on load, shows a small square of starry background, then nothing else.


    I uninstalled the program, downloaded the latest version from Google, ran:


    Code:
    zypper in google-earth-pro-stable-current.x86_64.rpm
    and got:


    Code:
    Problem: nothing provides mesa-libGLU needed by google-earth-pro-stable-7.3.1.4507-0.x86_64
     Solution 1: do not install google-earth-pro-stable-7.3.1.4507-0.x86_64
     Solution 2: break google-earth-pro-stable-7.3.1.4507-0.x86_64 by ignoring some of its dependencies
    and couldn't find mesa-libGLU in the repositories.


    This recent forum thread:


    https://forums.opensuse.org/showthre...n-7-3-1-4507-0


    suggested I try "Solution 2." I did (after checking that libGLU1 is in), but without luck. Google Earth installed, but with the same behavior as before.


    Any troubleshooting steps will be appreciated!

  2. #2

    Default AW: Missing mesa-libGLU for Google Earth

    Quote Originally Posted by Tuner View Post
    I am back to the nouveau driver, as Nvidia dumped support for my graphics card in the latest 396.18 installer.
    And?

    The 390.xx series is still available and maintained, probably for years...

    You do need to patch 390.48 currently to work with kernel 4.16, but I'd expect the next release will just work.
    And the nvidia repo does contain a patched driver meanwhile, so you could use that.

    Regarding Google-Earth, I think it is a 32bit application even if the rpm is 64bit (unless that changed recently), so try to install Mesa-libGLU1-32bit as well.

  3. #3

    Default Re: Missing mesa-libGLU for Google Earth

    Mesa-libGLU1-32bit. Got it; thanks, Wolf.

    Nouveau began showing some idiosyncratic behavior after I wrote the post above, so I may stick with the patched 390.48 after all.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •