GNOME Bugzilla – Bug 747760
Totem crashes with nvidia proprietary driver
Last modified: 2015-04-13 08:55:48 UTC
Totem, cheese and gnome maps crashes with nvidia binary driver. Works fine with mesa. I don't know if its related or not but all gnome-shell animations are lagging(low fps) with gtx660. Everything was fine before upgrading to 3.16. I'm on arch x86_64. https://bugs.archlinux.org/task/44531 totem: (totem:4180): Gdk-ERROR **: The program 'totem' received an X Window System error. This probably reflects a bug in the program. The error was 'BadMatch (invalid parameter attributes)'. (Details: serial 399 error_code 8 request_code 154 (GLX) minor_code 31) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Trace/breakpoint trap (core dumped) cheese: (cheese:4086): Gdk-ERROR **: The program 'cheese' received an X Window System error. This probably reflects a bug in the program. The error was 'BadMatch (invalid parameter attributes)'. (Details: serial 461 error_code 8 request_code 154 (GLX) minor_code 31) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Trace/breakpoint trap (core dumped) gnome-maps: (org.gnome.Maps:4345): Gdk-ERROR **: The program 'org.gnome.Maps' received an X Window System error. This probably reflects a bug in the program. The error was 'BadMatch (invalid parameter attributes)'. (Details: serial 805 error_code 8 request_code 154 (GLX) minor_code 31) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Trace/breakpoint trap (core dumped)
Reassigning to clutter...
Thanks for taking the time to report this. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of bug 747489 ***