Bug 1091837

Summary: gtk3: SIGSEGV in gtk_tree_model_filter_row_deleted()
Product: [Fedora] Fedora Reporter: Avvocato Andrea Marengoni <avv.marengoni>
Component: gtk3Assignee: Matthias Clasen <mclasen>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: avv.marengoni, ccecchi, derrick_moser, fedora, jklimes, mclasen, metherid, michel, mstuff, spoyarek, thomas.moschny
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/3f62d06570b4a97f14c2526790133d422f494a09
Whiteboard: abrt_hash:e29c83d75a3543fd789d3de2cbae17789604fd38
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 20:19:49 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Avvocato Andrea Marengoni 2014-04-28 07:31:36 UTC
Version-Release number of selected component:
shotwell-0.15.1-1.fc20

Additional info:
reporter:       libreport-2.2.1
backtrace_rating: 4
cmdline:        shotwell /run/media/andrea/3065-3637/DCIM/100MEDIA/PTDC0015.JPG
crash_function: gtk_tree_model_filter_row_deleted
executable:     /usr/bin/shotwell
kernel:         3.13.10-200.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 gtk_tree_model_filter_row_deleted at gtktreemodelfilter.c:2584
 #5 gtk_tree_model_row_deleted at gtktreemodel.c:1867
 #6 emit_row_deleted_for_row at gtkfilesystemmodel.c:331
 #7 remove_file at gtkfilesystemmodel.c:1912
 #8 gtk_file_system_model_monitor_change at gtkfilesystemmodel.c:1257
 #9 ffi_call_unix64 at ../src/x86/unix64.S:76
 #10 ffi_call at ../src/x86/ffi64.c:522
 #11 g_cclosure_marshal_generic_va at gclosure.c:1550
 #12 _g_closure_invoke_va at gclosure.c:840
 #15 emit_cb at gfilemonitor.c:392

Comment 1 Avvocato Andrea Marengoni 2014-04-28 07:31:42 UTC
Created attachment 890349 [details]
File: backtrace

Comment 2 Avvocato Andrea Marengoni 2014-04-28 07:31:43 UTC
Created attachment 890350 [details]
File: cgroup

Comment 3 Avvocato Andrea Marengoni 2014-04-28 07:31:46 UTC
Created attachment 890351 [details]
File: core_backtrace

Comment 4 Avvocato Andrea Marengoni 2014-04-28 07:31:50 UTC
Created attachment 890352 [details]
File: dso_list

Comment 5 Avvocato Andrea Marengoni 2014-04-28 07:31:52 UTC
Created attachment 890353 [details]
File: environ

Comment 6 Avvocato Andrea Marengoni 2014-04-28 07:31:54 UTC
Created attachment 890354 [details]
File: exploitable

Comment 7 Avvocato Andrea Marengoni 2014-04-28 07:31:56 UTC
Created attachment 890355 [details]
File: limits

Comment 8 Avvocato Andrea Marengoni 2014-04-28 07:31:59 UTC
Created attachment 890356 [details]
File: maps

Comment 9 Avvocato Andrea Marengoni 2014-04-28 07:32:02 UTC
Created attachment 890357 [details]
File: open_fds

Comment 10 Avvocato Andrea Marengoni 2014-04-28 07:32:06 UTC
Created attachment 890358 [details]
File: proc_pid_status

Comment 11 Avvocato Andrea Marengoni 2014-04-28 07:32:08 UTC
Created attachment 890359 [details]
File: var_log_messages

Comment 12 Jirka Klimes 2014-07-23 17:46:15 UTC
This seems like a problem in Gtk3. There are many bugs with the same backtrace in different programs.
This might be related:
https://mail.gnome.org/archives/commits-list/2012-November/msg00502.html
https://mail.gnome.org/archives/commits-list/2011-February/msg05789.html
https://mail.gnome.org/archives/gtk-app-devel-list/2014-March/msg00064.html

Comment 13 Jirka Klimes 2014-07-23 17:47:20 UTC
*** Bug 1010739 has been marked as a duplicate of this bug. ***

Comment 14 Jirka Klimes 2014-07-23 17:48:22 UTC
*** Bug 1110493 has been marked as a duplicate of this bug. ***

Comment 15 Jirka Klimes 2014-07-23 17:50:36 UTC
*** Bug 1063046 has been marked as a duplicate of this bug. ***

Comment 16 Jirka Klimes 2014-07-23 17:54:20 UTC
See also bug 997255 and bug 1047322 that were closed by the original components. But the backtrace is the same.

Comment 17 Fedora End Of Life 2015-05-29 11:41:46 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora  'version'
of '20'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 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 this bug is closed as described in the policy above.

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.

Comment 18 Fedora End Of Life 2015-06-29 20:19:49 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.