Results 1 to 8 of 8

Thread: Chrome crashes OpenSuse

  1. #1

    Default Chrome crashes OpenSuse

    Since this morning I have a very strange bug going on.

    For example whenever I try to log into facebook on google chrome, opensuse goes to User Login screen.
    http://gfycat.com/BlushingTerrificGrunion thats what i mean.

    I think it might have something to do with the firewall.
    By the way on firefox I dont have this problem.

    Its hard to figure out what is written in the console before the user login screen appears, but I can figure it out if it is necessary.

    Thanx in advance for any help.

  2. #2

    Default Re: Chrome crashes OpenSuse

    Quote Originally Posted by JakobAbfalter View Post
    I think it might have something to do with the firewall.
    No.
    It has definitely NOTHING to do with the firewall.
    Firewall problems cannot make your graphical session (Xorg) crash.

    Most likely that's a graphics driver issue.

    Somebody had the same issue recently on the opensuse mailinglist.
    For him re-installing the nvidia driver fixed it. (there was an xorg-x11-server update, if you installed the nvidia driver "the hard way" the update overwrites a part of the driver, because the driver overwrites system libraries on installation in the first place)
    http://lists.opensuse.org/opensuse/2.../msg00824.html

    So, what graphics card/driver are you using?
    Install "Mesa-demo-x" if it is not installed already, and post the output of:
    Code:
    glxinfo | grep render

  3. #3

    Default Re: Chrome crashes OpenSuse

    The command you posted seem not to be working for me:
    Code:
    jakob@linux-hkem:~> glxinfo | grep render > out.txt
    X Error of failed request:  BadWindow (invalid Window parameter)
      Major opcode of failed request:  154 (NV-GLX)
      Minor opcode of failed request:  4 ()
      Resource id in failed request:  0x4e00003
      Serial number of failed request:  33
      Current serial number in output stream:  33
    Im using this grafic card:
    Code:
    NVIDIA Corporation GT215M [GeForce GTS 360M] [10de:0cb1] (rev a2)

  4. #4

    Default Re: Chrome crashes OpenSuse

    Quote Originally Posted by JakobAbfalter View Post
    The command you posted seem not to be working for me:
    Code:
    jakob@linux-hkem:~> glxinfo | grep render > out.txt
    X Error of failed request:  BadWindow (invalid Window parameter)
      Major opcode of failed request:  154 (NV-GLX)
      Minor opcode of failed request:  4 ()
      Resource id in failed request:  0x4e00003
      Serial number of failed request:  33
      Current serial number in output stream:  33
    And there you have it.
    Your nvidia driver is not working.

    Reinstall it.

  5. #5

    Default Re: Chrome crashes OpenSuse

    thank you.
    Reinstalling the driver did indeed fix it.

  6. #6

    Default Re: Chrome crashes OpenSuse

    Quote Originally Posted by JakobAbfalter View Post
    thank you.
    Reinstalling the driver did indeed fix it.
    If you install the driver by downloading and installing the .run file from NVidia's homepage, you have to reinstall it whenever there is an update to xorg-x11-server, Mesa-libGL1, or the kernel. (as I said, it replaces two system libraries with each own version, namely libglx and libGL)

    That's why I always recommend (and prefer myself) to use the ready-made RPMs from the nvidia repo.
    Those install the driver in a way that it will still work after such an update.

    But the RPMs won't work of course if you use a different kernel than the one included in openSUSE...
    Last edited by wolfi323; 26-Apr-2014 at 05:00.

  7. #7
    Join Date
    Sep 2012
    Posts
    7,096

    Default Re: Chrome crashes OpenSuse

    Quote Originally Posted by wolfi323 View Post

    But the RPMs won't work of course if you use a different kernel than the one included in openSUSE...
    Actually RPMs build module on user system, so it should still work.

  8. #8

    Default Re: Chrome crashes OpenSuse

    Quote Originally Posted by arvidjaar View Post
    Actually RPMs build module on user system, so it should still work.
    Yes, but AFAIK they only do so at installation time. When you install another kernel, only a symlink to the already built module is created.

    I suppose this link mechanism wouldn't work in this case when you upgrade the kernel (especially from 3.11 to 3.14 or similar) and already have the driver RPMs installed.
    Last edited by wolfi323; 26-Apr-2014 at 06:39.

Posting Permissions

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