| Summary: | Gimp fails to launch, displaying a gegl:introspect error. | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Richard Houser <rick> |
| Component: | RPM Packages | Assignee: | All Packagers <pkg-bugs> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | High | CC: | luigiwalser, shlomif |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | gegl-0.4.28-1.mga8.src.rpm, gimp-2.10.22-1.mga8.src.rpm | CVE: | |
| Status comment: | |||
|
Description
Richard Houser
2020-12-31 18:28:41 CET
Thank you for reporting this. One imagines that Gimp used to work, and has stopped doing so after recent updates? I confirm the fault, with the same lib64gegl0.4_0-0.4.28-1.mga8; the fault is very recent because I used Gimp - recently! Gimp itself has not been updated since Oct. lib64gegl0.4_0-0.4.28-1.mga8.x86_64 has *just* been updated, among over 100 other pkgs. I wish I had tried Gimp before doing them... $ urpmq --requires gimp | grep gegl libgegl-0.4.so.0()(64bit) libgegl-npd-0.4.so()(64bit) [I do not have this one] $ urpmq --whatrequires lib64gegl0.4_0 ... gimp ... I have no other GEGL pkgs (such as 'gegl'), so do not think they matter here. Since Gimp has not just changed, it seems better to suspect initially gegl. This has no fixed maintainer, so assigning this bug globally; CC'ing DavidW who just did the 0.4.28 commit; and Shlomi for Gimp 2.10.22 in case Gimp needs fiddling re the new gegl. I have upped the importance because Gimp is such a major application to not work. Assignee:
bugsquad =>
pkg-bugs That stinks. The new gegl should have been called 0.5.0 to make clear it was a development version. Oh well, we'll have to update to gimp 2.99.4. In progress. Hopefully everything rebuilds fine vs. the new libgimp. Should be good to go when your mirror syncs in a few hours. Thanks for the report. Resolution:
(none) =>
FIXED I confirm gimp launches now. Thank you! |