Bug 1046814

Summary: [abrt] mate-file-manager: magazine_cache_push_magazine(): caja killed by SIGSEGV
Product: [Fedora] Fedora Reporter: mazdac
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: 20CC: bugzilla, dan.mashal, greatauk37, raveit65.sun, rdieter, samtygier, stefano
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/032f8467e71dc54dc3ee98e18cba52d3343fe04d
Whiteboard: abrt_hash:51f7b476a96254171d93a8fe7763160615ddabed
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-01-12 11:11:25 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 mazdac 2013-12-27 00:05:38 UTC 
Version-Release number of selected component:
mate-file-manager-1.6.3-1.fc20

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

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 magazine_cache_push_magazine at /usr/lib64/libglib-2.0.so.0
 #1 thread_memory_magazine2_unload.isra.11 at /usr/lib64/libglib-2.0.so.0
 #2 g_slice_free1 at /usr/lib64/libglib-2.0.so.0
 #3 g_type_free_instance at /usr/lib64/libgobject-2.0.so.0
 #4 gtk_container_destroy at /usr/lib64/libgtk-x11-2.0.so.0
 #9 gtk_object_dispose at /usr/lib64/libgtk-x11-2.0.so.0
 #11 gtk_toolbar_forall at /usr/lib64/libgtk-x11-2.0.so.0
 #12 gtk_container_destroy at /usr/lib64/libgtk-x11-2.0.so.0
 #17 gtk_object_dispose at /usr/lib64/libgtk-x11-2.0.so.0
 #19 gtk_table_forall at /usr/lib64/libgtk-x11-2.0.so.0
Comment 1 mazdac 2013-12-27 00:05:45 UTC 
Created attachment 842147 [details]
File: backtrace
Comment 2 mazdac 2013-12-27 00:05:48 UTC 
Created attachment 842148 [details]
File: cgroup
Comment 3 mazdac 2013-12-27 00:05:52 UTC 
Created attachment 842149 [details]
File: core_backtrace
Comment 4 mazdac 2013-12-27 00:05:55 UTC 
Created attachment 842150 [details]
File: dso_list
Comment 5 mazdac 2013-12-27 00:05:57 UTC 
Created attachment 842151 [details]
File: environ
Comment 6 mazdac 2013-12-27 00:05:59 UTC 
Created attachment 842152 [details]
File: exploitable
Comment 7 mazdac 2013-12-27 00:06:01 UTC 
Created attachment 842153 [details]
File: limits
Comment 8 mazdac 2013-12-27 00:06:07 UTC 
Created attachment 842154 [details]
File: maps
Comment 9 mazdac 2013-12-27 00:06:10 UTC 
Created attachment 842155 [details]
File: open_fds
Comment 10 mazdac 2013-12-27 00:06:12 UTC 
Created attachment 842156 [details]
File: proc_pid_status
Comment 11 mazdac 2013-12-27 00:06:14 UTC 
Created attachment 842157 [details]
File: var_log_messages
Comment 12 Wolfgang Ulbrich 2013-12-29 09:31:14 UTC 
Can you describe a little more detailed what happend?
Did this issue occurs frequently ?
Comment 13 Don Swaner 2014-01-21 22:03:04 UTC 
I got a similar SIGSEGV for caja. I tried to duplicate the problem, and was not able to do so.  The actions preceeding the SIGSEGV were: 1) insert kindle; 2) select extra pane; 3) copy file to kindle; 4) close kindle window; 5) eject kindle; 6) select close ALL windows (even though only one window was open).  The second time these actions were performed there was no SIGSEGV.

The automatic bug reporting tool would not let me report the bug, even though it pointed to this bug which has been closed for insufficient data.