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
Created attachment 842147 [details] File: backtrace
Created attachment 842148 [details] File: cgroup
Created attachment 842149 [details] File: core_backtrace
Created attachment 842150 [details] File: dso_list
Created attachment 842151 [details] File: environ
Created attachment 842152 [details] File: exploitable
Created attachment 842153 [details] File: limits
Created attachment 842154 [details] File: maps
Created attachment 842155 [details] File: open_fds
Created attachment 842156 [details] File: proc_pid_status
Created attachment 842157 [details] File: var_log_messages
Can you describe a little more detailed what happend? Did this issue occurs frequently ?
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.