segmentation fault with glxgears [solved] [closed]

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
1
down vote

favorite












I get segmentation fault when I try glxgear love compton (my compositor)...



This is the output when I do $ gdb glxgears.
Here is the backtrace.



Thread 1 "glxgears" received signal SIGSEGV, Segmentation fault.
0x00007ffff3a6f896 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
(gdb) bt
#0 0x00007ffff3a6f896 in ?? ()
from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#1 0x00007ffff3a70693 in ?? ()
from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#2 0x00007ffff3859eda in ?? ()
from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#3 0x00007ffff393bcba in ?? ()
from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#4 0x00007ffff393befd in ?? ()
from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#5 0x00007ffff393bfe1 in ?? ()
from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#6 0x00007ffff3829ce8 in ?? ()
from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#7 0x00005555555564ce in ?? ()
#8 0x0000555555555c48 in ?? ()
#9 0x00007ffff71151c1 in __libc_start_main (main=0x555555555780, argc=1,
argv=0x7fffffffe138, init=<optimized out>, fini=<optimized out>,
rtld_fini=<optimized out>, stack_end=0x7fffffffe128)
at ../csu/libc-start.c:308
#10 0x000055555555627a in ?? ()


Ok, fixed, I had the same problem







share|improve this question














closed as off-topic by Jeff Schaller, Kusalananda, dhag, Stephen Kitt, Andy Dalton Feb 16 at 19:17


This question appears to be off-topic. The users who voted to close gave this specific reason:


  • "Questions describing a problem that can't be reproduced and seemingly went away on its own (or went away when a typo was fixed) are off-topic as they are unlikely to help future readers." – Jeff Schaller, Kusalananda, dhag, Stephen Kitt, Andy Dalton
If this question can be reworded to fit the rules in the help center, please edit the question.
















    up vote
    1
    down vote

    favorite












    I get segmentation fault when I try glxgear love compton (my compositor)...



    This is the output when I do $ gdb glxgears.
    Here is the backtrace.



    Thread 1 "glxgears" received signal SIGSEGV, Segmentation fault.
    0x00007ffff3a6f896 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
    (gdb) bt
    #0 0x00007ffff3a6f896 in ?? ()
    from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
    #1 0x00007ffff3a70693 in ?? ()
    from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
    #2 0x00007ffff3859eda in ?? ()
    from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
    #3 0x00007ffff393bcba in ?? ()
    from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
    #4 0x00007ffff393befd in ?? ()
    from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
    #5 0x00007ffff393bfe1 in ?? ()
    from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
    #6 0x00007ffff3829ce8 in ?? ()
    from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
    #7 0x00005555555564ce in ?? ()
    #8 0x0000555555555c48 in ?? ()
    #9 0x00007ffff71151c1 in __libc_start_main (main=0x555555555780, argc=1,
    argv=0x7fffffffe138, init=<optimized out>, fini=<optimized out>,
    rtld_fini=<optimized out>, stack_end=0x7fffffffe128)
    at ../csu/libc-start.c:308
    #10 0x000055555555627a in ?? ()


    Ok, fixed, I had the same problem







    share|improve this question














    closed as off-topic by Jeff Schaller, Kusalananda, dhag, Stephen Kitt, Andy Dalton Feb 16 at 19:17


    This question appears to be off-topic. The users who voted to close gave this specific reason:


    • "Questions describing a problem that can't be reproduced and seemingly went away on its own (or went away when a typo was fixed) are off-topic as they are unlikely to help future readers." – Jeff Schaller, Kusalananda, dhag, Stephen Kitt, Andy Dalton
    If this question can be reworded to fit the rules in the help center, please edit the question.














      up vote
      1
      down vote

      favorite









      up vote
      1
      down vote

      favorite











      I get segmentation fault when I try glxgear love compton (my compositor)...



      This is the output when I do $ gdb glxgears.
      Here is the backtrace.



      Thread 1 "glxgears" received signal SIGSEGV, Segmentation fault.
      0x00007ffff3a6f896 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
      (gdb) bt
      #0 0x00007ffff3a6f896 in ?? ()
      from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
      #1 0x00007ffff3a70693 in ?? ()
      from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
      #2 0x00007ffff3859eda in ?? ()
      from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
      #3 0x00007ffff393bcba in ?? ()
      from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
      #4 0x00007ffff393befd in ?? ()
      from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
      #5 0x00007ffff393bfe1 in ?? ()
      from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
      #6 0x00007ffff3829ce8 in ?? ()
      from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
      #7 0x00005555555564ce in ?? ()
      #8 0x0000555555555c48 in ?? ()
      #9 0x00007ffff71151c1 in __libc_start_main (main=0x555555555780, argc=1,
      argv=0x7fffffffe138, init=<optimized out>, fini=<optimized out>,
      rtld_fini=<optimized out>, stack_end=0x7fffffffe128)
      at ../csu/libc-start.c:308
      #10 0x000055555555627a in ?? ()


      Ok, fixed, I had the same problem







      share|improve this question














      I get segmentation fault when I try glxgear love compton (my compositor)...



      This is the output when I do $ gdb glxgears.
      Here is the backtrace.



      Thread 1 "glxgears" received signal SIGSEGV, Segmentation fault.
      0x00007ffff3a6f896 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
      (gdb) bt
      #0 0x00007ffff3a6f896 in ?? ()
      from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
      #1 0x00007ffff3a70693 in ?? ()
      from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
      #2 0x00007ffff3859eda in ?? ()
      from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
      #3 0x00007ffff393bcba in ?? ()
      from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
      #4 0x00007ffff393befd in ?? ()
      from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
      #5 0x00007ffff393bfe1 in ?? ()
      from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
      #6 0x00007ffff3829ce8 in ?? ()
      from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
      #7 0x00005555555564ce in ?? ()
      #8 0x0000555555555c48 in ?? ()
      #9 0x00007ffff71151c1 in __libc_start_main (main=0x555555555780, argc=1,
      argv=0x7fffffffe138, init=<optimized out>, fini=<optimized out>,
      rtld_fini=<optimized out>, stack_end=0x7fffffffe128)
      at ../csu/libc-start.c:308
      #10 0x000055555555627a in ?? ()


      Ok, fixed, I had the same problem









      share|improve this question













      share|improve this question




      share|improve this question








      edited Feb 16 at 18:26

























      asked Feb 16 at 18:08









      Raúl Ulises Martín Hernández

      62




      62




      closed as off-topic by Jeff Schaller, Kusalananda, dhag, Stephen Kitt, Andy Dalton Feb 16 at 19:17


      This question appears to be off-topic. The users who voted to close gave this specific reason:


      • "Questions describing a problem that can't be reproduced and seemingly went away on its own (or went away when a typo was fixed) are off-topic as they are unlikely to help future readers." – Jeff Schaller, Kusalananda, dhag, Stephen Kitt, Andy Dalton
      If this question can be reworded to fit the rules in the help center, please edit the question.




      closed as off-topic by Jeff Schaller, Kusalananda, dhag, Stephen Kitt, Andy Dalton Feb 16 at 19:17


      This question appears to be off-topic. The users who voted to close gave this specific reason:


      • "Questions describing a problem that can't be reproduced and seemingly went away on its own (or went away when a typo was fixed) are off-topic as they are unlikely to help future readers." – Jeff Schaller, Kusalananda, dhag, Stephen Kitt, Andy Dalton
      If this question can be reworded to fit the rules in the help center, please edit the question.

























          active

          oldest

          votes






















          active

          oldest

          votes













          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes

          Popular posts from this blog

          How to check contact read email or not when send email to Individual?

          Displaying single band from multi-band raster using QGIS

          How many registers does an x86_64 CPU actually have?