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 · 8 comments
Open

Constant crash #1014

marshallovski opened this issue Oct 1, 2024 · 8 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.

@mikeloeven
Copy link

mikeloeven commented Dec 31, 2024

I am experiencing the same issue although when I launch the app I dont even get a window. Running most recent popos trying to launch via console in verbose mode gives me this

Gtk-Message: 07:50:24.564: Failed to load module "canberra-gtk-module"
Gtk-Message: 07:50:24.565: Failed to load module "canberra-gtk-module"
System.TypeInitializationException: The type initializer for 'Pinta.Core.PintaCore' threw an exception.
---> System.ArgumentOutOfRangeException: Index and length must refer to a location within the string. (Parameter 'length')
at System.String.ThrowSubstringArgumentOutOfRange(Int32 startIndex, Int32 length)
at System.String.Substring(Int32 startIndex, Int32 length)
at Pinta.Core.PaintDotNetPalette.Load(IFile file)
at Pinta.Core.Palette.Load(IFile file)
at Pinta.Core.PaletteManager.PopulateSavedPalette()
at Pinta.Core.PaletteManager..ctor()
at Pinta.Core.PintaCore..cctor()
--- End of inner exception stack trace ---
at Pinta.Core.PintaCore.get_Chrome()
at Pinta.MainClass.ExceptionManager_UnhandledException(UnhandledExceptionArgs args)
at GLib.ExceptionManager.RaiseUnhandledException(Exception e, Boolean is_terminal)

manually reinstalled canberra-gtk-module via APT and rebooted system to be safe issue still persists

@cameronwhite
Copy link
Member

I am experiencing the same issue although when I launch the app I dont even get a window. Running most recent popos trying to launch via console in verbose mode gives me this

I think that is a separate issue based on the stack trace - it sounds like the palette file is perhaps corrupted? Could you attach the palette.txt from your settings directory (it should be something like ~/.config/Pinta/palette.txt, but might be elsewhere if you're using flatpak or snap, e.g. https://unix.stackexchange.com/a/697214)
You should be able to delete that file to resolve the issue, but it would be helpful to know what it contains.

@mikeloeven
Copy link

palette.txt

@mikeloeven
Copy link

doesn't seem to be the issue deleting that did not resolve

@cameronwhite
Copy link
Member

Thanks, yeah using that palette file also doesn't trigger the crash for me.
Which Pinta version and installation method (e.g. flatpak / snap / distro package) are you using?

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

5 participants
@cameronwhite @badcel @mikeloeven @marshallovski and others