| Summary: | Segmentation fault when opening a gimp script-fu console | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Juergen Harms <juergen.harms> |
| Component: | RPM Packages | Assignee: | Shlomi Fish <shlomif> |
| Status: | RESOLVED WORKSFORME | QA Contact: | |
| Severity: | major | ||
| Priority: | Normal | CC: | fundawang, zen25000 |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | gimp | CVE: | |
| Status comment: | |||
|
Description
Juergen Harms
2013-02-15 09:11:51 CET
Is this related to https://bugs.mageia.org/show_bug.cgi?id=7351 ?
Manuel Hiebel
2013-02-16 16:44:57 CET
Assignee:
bugsquad =>
shlomif While that sounds like pure speculation, anything's possible. The fix for that was upstream in 2.8.1, so you could check to see if you can reproduce it with 2.8.0 before it was fixed upstream. You can rebuild gimp from SVN revision 282663 to check. If it works in 2.8.0, you should report it upstream. Generating a backtrace in either case would also be helpful. CC:
(none) =>
fundawang I am not the right person to do this. I am totally ignorant about script-fu, just hit the problem while exploring alternatives to ImageMagick - did not wont to let an un-announced bug hang around in Mageia3. I can't reproduce this in two Cauldron systems, i586 in VM and x86_64 which is my main system. The examples in the console help seem to work as expected. CC:
(none) =>
zen25000 Thank you for verifying. I verified on my side again, and now dont get the error any more. I have no explanation (fully updated 64-bit caudron on real hardware). After initially getting the segfault, I had re-booted into my Mageia2 system, seen that the fu console is OK there, booted back into cauldron for writing the bugzilla report, getting the segfault whenever I tried. In the meantime, 5 update-packages arrived and were installed, but - speculating again - nothing which looks like having any influence with respect to this bug. Sorry for the noise. (In reply to comment #5) > Thank you for verifying. I verified on my side again, and now dont get the > error any more. I have no explanation (fully updated 64-bit caudron on real > hardware). > Closing as WORKSFORME then. Thanks for the report. Status:
NEW =>
RESOLVED |