Bug 1044103

Summary: [abrt] mate-file-manager: g_type_check_instance(): caja killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Wouter <heyveld>
Component: mate-file-managerAssignee: Dan Mashal <dan.mashal>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: dan.mashal, fedora, rdieter, red, stefano
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/57fc8b2b9643569075853e925fbee770475bf10a
Whiteboard: abrt_hash:a777cb0c52bb08cced697d9f0a2422afd89d9485
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-04-21 09:21:11 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Wouter 2013-12-17 19:49:19 UTC 
Description of problem:
Looked for multiple copies of a particular file on an external harddive. Copied the file name in the search bar and hit the <enter> key, then Caja terminated. 

Version-Release number of selected component:
mate-file-manager-1.6.3-0.10.gitbf47018.fc19

Additional info:
reporter:       libreport-2.1.10
backtrace_rating: 4
cmdline:        caja -n
crash_function: g_type_check_instance
executable:     /usr/bin/caja
kernel:         3.11.10-200.fc19.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 g_type_check_instance at gtype.c:4106
 #1 g_signal_connect_data at gsignal.c:2435
 #2 set_pending_icon_to_reveal at caja-icon-container.c:657
 #3 end_renaming_mode at caja-icon-container.c:9201
 #4 caja_icon_container_clear at caja-icon-container.c:7108
 #5 fm_icon_view_clear at fm-icon-view.c:535
 #6 _g_closure_invoke_va at gclosure.c:840
 #9 load_directory at fm-directory-view.c:9378
 #10 fm_directory_view_load_location at fm-directory-view.c:2475
 #11 load_new_location at caja-window-manage-views.c:1498

Potential duplicate: bug 990290
Comment 1 Wouter 2013-12-17 19:49:28 UTC 
Created attachment 837906 [details]
File: backtrace
Comment 2 Wouter 2013-12-17 19:49:31 UTC 
Created attachment 837907 [details]
File: cgroup
Comment 3 Wouter 2013-12-17 19:49:33 UTC 
Created attachment 837908 [details]
File: core_backtrace
Comment 4 Wouter 2013-12-17 19:49:35 UTC 
Created attachment 837909 [details]
File: dso_list
Comment 5 Wouter 2013-12-17 19:49:36 UTC 
Created attachment 837910 [details]
File: environ
Comment 6 Wouter 2013-12-17 19:49:38 UTC 
Created attachment 837911 [details]
File: limits
Comment 7 Wouter 2013-12-17 19:49:40 UTC 
Created attachment 837912 [details]
File: maps
Comment 8 Wouter 2013-12-17 19:49:42 UTC 
Created attachment 837913 [details]
File: open_fds
Comment 9 Wouter 2013-12-17 19:49:44 UTC 
Created attachment 837914 [details]
File: proc_pid_status
Comment 10 Wouter 2013-12-17 19:49:46 UTC 
Created attachment 837915 [details]
File: var_log_messages
Comment 11 Wolfgang Ulbrich 2013-12-25 07:30:34 UTC 
forwarded to upstream
https://github.com/mate-desktop/caja/issues/220
Comment 12 Davide Repetto 2014-01-10 11:46:47 UTC 
Another user experienced a similar problem:

Closing a caja window (full of video thumbnails) caused the crash.

reporter:       libreport-2.1.10
backtrace_rating: 4
cmdline:        caja -n
crash_function: g_type_check_instance
executable:     /usr/bin/caja
kernel:         3.12.6-200.fc19.x86_64
package:        mate-file-manager-1.6.3-0.10.gitbf47018.fc19
reason:         caja killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 13 Wolfgang Ulbrich 2014-03-22 14:45:43 UTC 
Upstream can't reproduce this issue.
Does this issue still exists or was it a one shot?
Comment 14 Wouter 2014-03-24 20:40:32 UTC 
(In reply to Wolfgang Ulbrich from comment #13)
> Upstream can't reproduce this issue.
> Does this issue still exists or was it a one shot?

I've tried to reproduce the error. This did not succeed. However, I've upgraded my pc from F19 to F20.
Comment 15 Wolfgang Ulbrich 2014-04-21 09:21:11 UTC 
(In reply to Wouter from comment #14)
> (In reply to Wolfgang Ulbrich from comment #13)
> > Upstream can't reproduce this issue.
> > Does this issue still exists or was it a one shot?
> 
> I've tried to reproduce the error. This did not succeed. However, I've
> upgraded my pc from F19 to F20.

Ok,feel free to post here if this issue happens again.