unity-control-center crashes when nvidia driver is in use (nvidia-prime)

StacktraceTop:
 __glXReadReply (dpy=dpy@entry=0xf457a0, size=size@entry=4, dest=dest@entry=0x7fff76b1c0bc, reply_is_always_array=reply_is_always_array@entry=0 '\000') at indirect.c:70
 __indirect_glGetTexLevelParameteriv (target=34039, level=0, pname=4096, params=0x7fff76b1c0bc) at indirect.c:3819
 _cogl_texture_driver_size_supported (ctx=0x12efd50, gl_target=<optimized out>, gl_intformat=<optimized out>, gl_format=<optimized out>, gl_type=<optimized out>, width=<optimized out>, height=1) at ./driver/gl/gl/cogl-texture-driver-gl.c:483
 _cogl_texture_rectangle_can_create (ctx=0x12efd50, width=1, height=1, internal_format=COGL_PIXEL_FORMAT_RGBA_8888_PRE, error=0x7fff76b1c1a8) at ./cogl-texture-rectangle.c:139
 cogl_texture_rectangle_new_from_bitmap (bmp=bmp@entry=0x1296500, internal_format=internal_format@entry=COGL_PIXEL_FORMAT_RGBA_8888_PRE, error=error@entry=0x7fff76b1c1a8) at ./cogl-texture-rectangle.c:294

Thanks, that's an nvidia issue

Status changed to 'Confirmed' because the bug affects multiple users.

Please type the following command in a terminal:

sudo nvidia-bug-report.sh

and attach the resulting nvidia-bug-report.log.gz.

Also, please attach the following file:
/var/log/gpu-manager.log

The bug does not reoccur after changing to intel mode, rebooting, changing to nvidia mode, loging out and back in. None the less, following are the dumps.

In between this dump and the previous dump, there was an Xserver crash. Don't know if it influences the data.

I can see from dmesg that you're using Bumblebee. Please make sure to remove all the bumblebee related packages (but bbswitch) and try again.

Bumblebee has been removed but there where still config files remaining which where then removed by using synaptic -> Mark for complete removal. Before the config files where removed, bumblebeed was tried to be spawned, but failed, as shown in the log. In this state there were no crashes and everything worked as it should.

After removing the residual config files, there is no longer any mention of bumblebeed in dmesg.

I'm unable to reproduce the problem on my system. Can you still reproduce it on an updated system? If so, I'll have a look at the code to see what's going on.

I'm still getting this crash on an updated system, using the latest NVIDIA drivers. My card:

    01:00.0 VGA compatible controller: NVIDIA Corporation GK107M [GeForce GT 640M Mac Edition] (rev a1)

The error I'm getting is:

libGL error: failed to load driver: swrast

(unity-control-center:24230): Gdk-ERROR **: The program 'unity-control-center' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadLength (poly request too large or internal Xlib length erro'.
  (Details: serial 227 error_code 16 request_code 155 (GLX) minor_code 1)
  (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)

I get this exact same error. It works fine until I plug in an external monitor to the display port.

I still see this crash on my Ubuntu 16.04.3 laptop (no external monitor connect), without any bumblebee installed.

$ unity-control-center
get chip id failed: -1 [13]
param: 4, val: 0
[intel_init_bufmgr:1193] Error initializing buffer manager.

(unity-control-center:1874): GLib-CRITICAL **: g_strsplit: assertion 'string != NULL' failed
Segmentation fault (core dumped)

NVidia binary driver 384.90

I ran `setsid unity` but that led to a complete mess: no window chrome or taskbar, Alt+Tab disabled, login loop etc.