Bug 9078 - Segmentation fault when opening a gimp script-fu console
Summary: Segmentation fault when opening a gimp script-fu console
Status: RESOLVED WORKSFORME
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Shlomi Fish
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-15 09:11 CET by Juergen Harms
Modified: 2013-02-19 10:14 CET (History)
2 users (show)

See Also:
Source RPM: gimp
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Juergen Harms 2013-02-15 09:11:51 CET 
Description of problem:

Segmentation fault when opening a gimp script-fu console


Version-Release number of selected component (if applicable):
gimp-2.8.2-3.mga3


How reproducible:
100%


Steps to Reproduce:
1. Launch gimp from a command-line
2. Do Filters -> Script-Fu -> Console

You get
/usr/lib64/gimp/2.0/plug-ins/script-fu: fatal error: Segmentation fault
Comment 1 Juergen Harms 2013-02-15 09:13:47 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
Source RPM: (none) => gimp

Comment 2 David Walser 2013-02-18 01:52:11 CET 
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

Comment 3 Juergen Harms 2013-02-18 08:54:10 CET 
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.
Comment 4 Barry Jackson 2013-02-18 19:51:17 CET 
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

Comment 5 Juergen Harms 2013-02-18 20:27:21 CET 
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.
Comment 6 Shlomi Fish 2013-02-19 10:14:08 CET 
(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
Resolution: (none) => WORKSFORME
Note You need to log in before you can comment on or make changes to this bug.