helge17 / tuxguitar

Improve TuxGuitar and provide builds
Other
303 stars 29 forks source link

Print Preview crashes app #404

Open guiv42 opened 4 weeks ago

guiv42 commented 4 weeks ago

Operating system: Kubuntu 22.04 (issue is not reproduced on Ubuntu 22.04) TuxGuitar version: 1.6.3beta1 TuxGuitar installation: .deb package provided here in this repo Procedure to reproduce:

note: it's not 100% reproducible

guiv42 commented 4 weeks ago

introduced by 8328e271531d916c818ddb746d98bb121f5a8380, Update SWT on Linux to 4.21

I understand that (K)Ubuntu 22.04 ships SWT 4.20 (Paquet libswt-glx-gtk-4-jni package?), so I tested with SWT 4.20. Other symptoms (error logs), but still it crashes app.

guiv42 commented 4 weeks ago

not reproduced on Kubuntu 24.04

helge17 commented 4 weeks ago

On my system, the print preview window sometimes(?) opens in full screen, sometimes as a very small line somewhere(?) on the screen, today in the top left corner of the screen, but I remember it being in other places, too:

grafik

So maybe TuxGuitar didn't really crash and you just need to find and close the print preview window to make TuxGuitar respond again?

grafik

And, if I remember correctly, TuxGuitar itself is sometimes started as a mini-window you can hardly find.

guiv42 commented 3 weeks ago

I confirm the app crashes. Not always, and with different symptoms:

Also with different error logs (non-exhaustive list):

This looks like a (tricky) threading issue

guiv42 commented 5 days ago

Issue still present in kubuntu 22.04 after upgrading SWT to 4.26

The program 'TuxGuitar' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadRequest (invalid request code or no such operation)'.
  (Details: serial 71213 error_code 1 request_code 0 (core protocol) minor_code 0)
  (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.)

and still can't reproduce in kubuntu 24.04. No idea how to get further in this analysis :(