Description of problem: Simply run Filters->Web->Slide and the error occurs. Version-Release number of selected component: gimp-2.8.2-6.fc17 Additional info: libreport version: 2.0.18 abrt_version: 2.0.18 cmdline: /usr/bin/python /usr/lib64/gimp/2.0/plug-ins/py-slice.py -gimp 15 14 -run 0 kernel: 3.6.8-2.fc17.x86_64 backtrace: :py-slice.py:181:slice:RuntimeError: Procedure 'gimp-file-save' has been called with an invalid ID for argument 'drawable'. Most likely a plug-in is trying to work on a layer that doesn't exist any longer. : :Traceback (most recent call last): : File "/usr/lib64/gimp/2.0/python/gimpfu.py", line 699, in response : dialog.res = run_script(params) : File "/usr/lib64/gimp/2.0/python/gimpfu.py", line 361, in run_script : return apply(function, params) : File "/usr/lib64/gimp/2.0/plug-ins/py-slice.py", line 119, in pyslice : left, right, top, bottom, i, j, "")) : File "/usr/lib64/gimp/2.0/plug-ins/py-slice.py", line 181, in slice : pdb.gimp_file_save(temp_image, temp_drawable, filename, filename) :RuntimeError: Procedure 'gimp-file-save' has been called with an invalid ID for argument 'drawable'. Most likely a plug-in is trying to work on a layer that doesn't exist any longer. : :Local variables in innermost frame: :src: 'bizarre_0_0.jpg' :right: 100 :image_path: '/home/tajindersinghnamdhari/images' :bottom: 30 :postfix: '' :top: 0 :j: 0 :temp_drawable: <gimp.Layer '(null)'> :filename: '/home/tajindersinghnamdhari/images/bizarre_0_0.jpg' :i: 0 :image_basename: 'bizarre' :image: <gimp.Image 'WebDesign2.xcf'> :drawable: None :temp_image: <gimp.Image 'Untitled'> :image_extension: 'jpg' :left: 0
Created attachment 666516 [details] File: executable
Created attachment 666517 [details] File: environ
Created attachment 666518 [details] File: smolt_data
Created attachment 666519 [details] File: core_backtrace
Sorry for the late response. I can't reproduce the bug that you described with the current GIMP package (2.8.4-3), i.e. I've attempted slicing an image into 2 rows, 2 columns and it worked for me. Can you reproduce this? If yes, please attach the image file with which you triggered the problem and describe in detail what you did (i.e. all steps, all settings of the plug-in and so forth). Thanks!
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.