Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

The transition from UV Segmenting to AutoUV window is causing a crash [Ubuntu] #513

Open
Micheus opened this issue Nov 16, 2022 · 1 comment
Open

The transition from UV Segmenting to AutoUV window is causing a crash [Ubuntu] #513

Micheus opened this issue Nov 16, 2022 · 1 comment

Comments

@Micheus
Copy link
Collaborator

Micheus commented Nov 16, 2022

After we choose the UV Mapping option and then define all the edges for cut, by applying any unwrap method Wings3D is crashing suddenly without any advise or report.

That is happening in Ubuntu 22.04, but it was not present in 20.04.

That is the message in the Erlang console:

(Erlang:16669): Gdk-ERROR **: 10:31:06.389: The program 'Erlang' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
(Details: serial 18035 error_code 8 request_code 151 (GLX) minor_code 11)
(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)

This report comes from this Wings3D's forum thread: UV mapping problem on Ubuntu
@m4v
Copy link

m4v commented Oct 18, 2023

I'm having the same problem with version 2.3 in Ubuntu 22.04.

(Erlang:282140): Gdk-ERROR **: 00:01:37.762: The program 'Erlang' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
  (Details: serial 13831 error_code 8 request_code 152 (GLX) minor_code 11)
  (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.)
[1]    282140 trace trap (core dumped)  ./wings

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@m4v @Micheus