Opened 7 weeks ago
Last modified 6 weeks ago
#69525 new defect
gimp2 does not open image files on (on ppc?)
Reported by: | barracuda156 | Owned by: | |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.9.1 |
Keywords: | snowleopard, powerpc | Cc: | mascguy (Christopher Nielsen) |
Port: | gimp2 |
Description
I get the following error when trying to open random files like screenshots:
Plug-in crashed: "file-png" (/opt/local/lib/gimp/2.0/plug-ins/file-png/file-png) The dying plug-in may have messed up GIMP's internal state. You may want to save your images and restart GIMP to be on the safe side.
Same error for jpeg and png. What may cause this?
- S. Just not to forget, we need
legacysupport.redirect_bins gimp
for gimp* ports, otherwise there is a disaster on launch withmalloc
errors.
Change History (2)
comment:1 follow-up: 2 Changed 6 weeks ago by ryandesign (Ryan Carsten Schmidt)
comment:2 Changed 6 weeks ago by mascguy (Christopher Nielsen)
@kencu also provided the following suggestion, to help with generating a detailed crash report:
If I were a gimp developer, and with this amount of information, the next thing I might ask you to do would be to launch gimp using lldb like this:
lldb gimpthen after the initial flurry of activity have you type:
runand then, presuming it crashes again with "fatal error: Segmentation fault: 11", I would have you type:
btto get the stack trace, and then copy that information and paste it into the bug report.
Note: See
TracTickets for help on using
tickets.
You'll have to search the gimp issue tracker or elsewhere on the Internet and see what people say. I found this issue in which the last comments identify it as an out-of-memory problem that occurs on 32-bit systems, but I don't know if it's exactly the same issue as yours:
https://gitlab.gnome.org/GNOME/gimp/-/issues/4428
If there was truly a crash, as the error message suggests, then check if macOS wrote a crash log file; if it did, attach it; maybe it helps pinpoint why the crash occurred.