After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 447378 - Segmentation fault when deleting tiff file
Segmentation fault when deleting tiff file
Status: RESOLVED FIXED
Product: gtk+
Classification: Platform
Component: Widget: GtkFileChooser
2.10.x
Other Linux
: Normal critical
: ---
Assigned To: gtk-bugs
Federico Mena Quintero
Depends on:
Blocks:
 
 
Reported: 2007-06-14 01:13 UTC by Amadeus
Modified: 2010-02-22 03:14 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
the targa file that have to be saved as tiff (192.02 KB, image/x-tga)
2007-06-14 01:14 UTC, Amadeus 		Details

Description Amadeus 2007-06-14 01:13:19 UTC 
I can crash Gimp everytime with the following procedure:

start gimp with: gimp flipped.blue.tga
Save the picture as flipped.blue.tiff
Open the "open file chooser"
Select "flipped.blue.tiff" so it is shown in the preview to the right.
Goto bash: rm flipped.blue.tiff

(script-fu:29064): LibGimpBase-WARNING **: script-fu: wire_read(): error

[1]+  Segmentation fault      gimp flipped.blue.tga
Comment 1 Amadeus 2007-06-14 01:14:11 UTC 
Created attachment 89923 [details]
the targa file that have to be saved as tiff
Comment 2 Sven Neumann 2007-06-14 06:06:48 UTC 
Almost certainly a file-chooser problem. Please check for duplicates in the GTK+ product. And please specify what version of GTK+ you are using.
Comment 3 Sven Neumann 2007-06-14 06:41:39 UTC 
I can reproduce this using gtk+ 2.10.13. A moment after the file is deleted on disk, the file entry listed above it (flipped.blue.tga) is removed from the file-chooser. The file-chooser still shows the deleted file but with a corrupted filename. There are warnings on the console at this point:

Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text()

Changing the selection in the file-chooser then causes a crash:

+ Trace 140852

  • #8 file_model_node_get_info
  • #9 get_list_file_info
  • #10 list_icon_data_func
  • #11 IA__gtk_tree_view_column_cell_set_cell_data
  • #12 gtk_tree_view_expose 






Comment 4


Sven Neumann





          2007-06-14 06:48:12 UTC
        



I've played with it a little more. This is independent of the file names being used. Sometimes it works, sometimes it crashes immidiately:





+
Trace
    140854






    

  • 
#7
<signal handler called>

    • 

  • 
#8
IA__gtk_file_info_get_display_name

    • 

  • 
#9
list_name_data_func

    • 

  • 
#10
IA__gtk_tree_view_column_cell_set_cell_data

    • 

  • 
#11
gtk_tree_view_expose

    • 













Comment 5


Amadeus





          2007-06-14 12:37:54 UTC
        



I (reporter) is using gtk 2.10.12 on Fedora 7.







Comment 6


airfullbete





          2007-07-01 18:36:45 UTC
        



I too confirm this bug. Here is another procedure that doesn't require the attachment.

1. Open Gimp
2. Create a new image
3. Save as Untitled.tif
4. Open the Save as dialog again and highlight "Untitled.tif" in the file list.
5. "rm Untitled.tif" on a command line.

gimp: fatal error: Segmentation fault


I've had problems with saving tif files for a while (at least 6-8 months, probably more, I can't remember). I have not filled a bug report yet because I'm unable to constantly reproduce the crash. However gimp crashes very often after saving a file to tif format following these steps:
1) An image is saved under file.tif
2) Then the file is saved under file.xcf
3) And again the file is saved under file.tif
4) The newly created file.tif is moved or deleted with a bash command.
Immediately after step 4 gimp crashes even if no file-chooser dialog is opened.

I suspect my problem might be linked with the current bug.

I'm using gtk2-2.10.12-1.fc6 and gimp svn (Revision: 22834) on Fedora 6.

By the way, I'm unable to get a stack trace in gdb because I'm unable to get to the crash point while running the debugger. Gdb halts before.
1) gdb gimp
2) > run
3) I create a new image and open the save as dialog and enter "file.tif"
4) When I click on "Save" I get (from gdb)
Couldn't get registers: No such process.
The (truncated) stack trace at this point is:




+
Trace
    145099






    

  • 
#0
__kernel_vsyscall

    • 

  • 
#1
fork

    
                from
                /lib/libc.so.6

    

    • 

  • 
#2
fork

    
                from
                /lib/libpthread.so.0

    

    • 

  • 
#3
g_spawn_error_quark

    
                from
                /lib/libglib-2.0.so.0

    

    • 

  • 
#4
g_spawn_async_with_pipes

    
                from
                /lib/libglib-2.0.so.0

    

    • 

  • 
#5
g_spawn_async

    
                from
                /lib/libglib-2.0.so.0

    

    • 

  • 
#6
gimp_plug_in_open

    
                at gimpplugin.c
                  line
                  358

    

    • 

  • 
#7
gimp_plug_in_manager_call_run

    
                at gimppluginmanager-call.c
                  line
                  169

    

    • 

  • 
#8
gimp_plug_in_procedure_execute

    
                at gimppluginprocedure.c
                  line
                  221

    

    • 

  • 
#9
gimp_procedure_execute

    
                at gimpprocedure.c
                  line
                  327

    

    • 

  • 
#10
gimp_pdb_execute_procedure_by_name_args

    
                at gimppdb.c
                  line
                  320

    

    • 

  • 
#11
gimp_pdb_execute_procedure_by_name

    
                at gimppdb.c
                  line
                  431

    

    • 

  • 
#12
file_save

    
                at file-save.c
                  line
                  137

    

    • 

  • 
#13
file_save_dialog_response

    
                at file-save-dialog.c
                  line
                  514

    

    • 

  • 
#14
g_cclosure_marshal_VOID

    
                from
                /lib/libgobject-2.0.so.0

    

    • 

  • 
#48
g_main_loop_run

    
                from
                /lib/libglib-2.0.so.0

    

    • 

  • 
#49
app_run

    
                at app.c
                  line
                  246

    

    • 

  • 
#50
main

    
                at main.c
                  line
                  381

    

    • 
















Comment 7


Javier Jardón (IRC: jjardon)





          2009-11-25 00:24:50 UTC
        



You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you.

Can you please check again if the issue you reported here still happens in a recent version of GTK+ and update this report by adding a comment and adjusting the 'Version' field?

Again thank you for reporting this and sorry that it could not be fixed for the version you originally used here.

Set to NEEDINFO, so without feedback this report will be closed as INCOMPLETE after 6 weeks.






Comment 8


Javier Jardón (IRC: jjardon)





          2010-02-22 02:17:47 UTC
        



Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!






Comment 9


Amadeus





          2010-02-22 02:26:38 UTC
        



Works with
gimp-2.6.8-1.fc11.x86_64