Hello
I use Wings3d v 2.2.9 with Ubuntu 22.04
I can no longer make a UV mapping. A window opens with internal error?
thank you for your help
Can you attach a screenshot of Wings3d with the error shown?
I'm assuming you are not getting any wings_crash.dump file on you desktop.
Hello
Indeed, I have no bug feedback. How do I view the screenshot?
Thank you for your help
Quote:Indeed, I have no bug feedback. How do I view the screenshot?
when you start the UV window and get that
"A window opens with internal error?", please use the option for the whole screen capture (PRTSC) as shown in the following article:
Methods to take screenshots on Ubuntu 22.04 LTS
I ask for it because we need a tip about what can be happening from your side.
I work on Windows, but I have a Ubuntu 22.04 partition which I can't experience the problem you are reporting.
Are you using Wings3D natively on linux or via Flatpak?
Hello
I tried with Wing3D from Synapic, then Flatpak with always the same problem when cutting the segments
Thank you
I can't find the old version available
I had some time to boot up my Ubuntu 22.04 partition and check what you reported.
I installed Wings3D via Synaptic as you did and I got a different error message of yours when trying to Unfold the UV mesh.
I also installed the Wings3D from the official repository and in this case I got a hard crash.
Which didn't happen when I was running on Ubuntu 20.04.
By running it from my development environment I get the messages bellow which the problem seems to be something related to the GDK - something that was changed from one to other Ubuntu version:
Quote:((Erlang:2): Gdk-ERROR **: 17:12:08.000: 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 26127 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.)
I tried to use Wings3D via Flatpak and the same hard crash happen.
Hello :)
so I have to wait for an update of Ubuntu or wings3D :(
thank you for your help :)