PintaProject / Pinta

Simple GTK# Paint Program
http://www.pinta-project.com/
MIT License
1.87k stars 277 forks source link

Constant crash #1014

Open marshallovski opened 2 months ago

marshallovski commented 2 months ago

Description Everytime I open Pinta, it crashes after a few seconds without a reason or errors.

To Reproduce

  1. Install Pinta from Flatpak
  2. Open Pinta
  3. Wait a few seconds
  4. Crash!

Additional Info

https://github.com/user-attachments/assets/fa54abe4-ae03-4f92-b96b-3b2635ced57a

Logs (translated):

Note that the directories 

'/var/lib/flatpak/exports/share'
'/home/user/.local/share/flatpak/exports/share'

are not located at the search path set using the variable
environment variable XDG_DATA_DIRS, so programs installed by Flatpak may not appear on your desktop.
appear on your desktop until you restart your session.

(pinta:2): GdkPixbuf-CRITICAL **: 14:34:26.132: gdk_pixbuf_calculate_rowstride: assertion 'width > 0' failed

(pinta:2): GdkPixbuf-CRITICAL **: 14:34:26.132: gdk_pixbuf_calculate_rowstride: assertion 'width > 0' failed

after that "GdkPixbuf-CRITICAL" errors Pinta's still working.

Version OS: Debian 12 bookworm x86_64 Pinta ver.: 2.1.2 from Flatpak

EDIT: I'm using KDE 5.27.5 in Wayland session. And my videocard is AMD Radeon RX580, if it's important.

cameronwhite commented 2 months ago

Thanks for the report!

Those "GdkPixbuf" messages are unrelated / harmless, I think, and show up normally. It's very odd that there isn't any stack trace from the crash, though, which makes this very tricky to diagnose. I don't think I've seen any similar reports to this

I'm not sure offhand if it's possible to run a debugger like gdb on a flatpak process, but using that to see a stack trace of where it's crashing would be helpful. I suspect there's something happening on the GTK side of things, since a hard crash like that most likely is from native code.

badcel commented 2 months ago

You could try to use a GNOME session and see what happens.

marshallovski commented 2 months ago

You could try to use a GNOME session and see what happens.

Of course I can't, GNOME will ruin my whole system, including KDE.