You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Building Slic3r non-planar master merge in Ubuntu-20.04 for WSL2 in Windows 10, the code builds as expected but unable to run GUI. Error message as follows:
perl slic3r.pl --gui
(slic3r.pl:21646): dbind-WARNING **: 08:24:59.598: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-d7cnsxG1gH: Connection refused
(slic3r.pl:21646): Gdk-ERROR **: 08:25:00.772: The program 'slic3r.pl' received an X Window System error.
This probably reflects a bug in the program.
The error was 'GLXBadContext'.
(Details: serial 630 error_code 151 request_code 147 (GLX) minor_code 6)
(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
The text was updated successfully, but these errors were encountered:
Building Slic3r non-planar master merge in Ubuntu-20.04 for WSL2 in Windows 10, the code builds as expected but unable to run GUI. Error message as follows:
perl slic3r.pl --gui
(slic3r.pl:21646): dbind-WARNING **: 08:24:59.598: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-d7cnsxG1gH: Connection refused
(slic3r.pl:21646): Gdk-ERROR **: 08:25:00.772: The program 'slic3r.pl' received an X Window System error.
This probably reflects a bug in the program.
The error was 'GLXBadContext'.
(Details: serial 630 error_code 151 request_code 147 (GLX) minor_code 6)
(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
The text was updated successfully, but these errors were encountered: