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.

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

Constant crash #1014

Open
marshallovski opened this issue Oct 1, 2024 · 3 comments
Open

Constant crash #1014

marshallovski opened this issue Oct 1, 2024 · 3 comments
Labels

Comments

@marshallovski
Copy link

marshallovski commented Oct 1, 2024

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

2024-10-01.14-34-23.mp4

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
Copy link
Member

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
Copy link
Contributor

badcel commented Oct 2, 2024

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

@marshallovski
Copy link
Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants