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.12.5-302.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 magazine_cache_push_magazine at gslice.c:706 #1 thread_memory_magazine2_unload at gslice.c:815 #2 g_slice_free1 at gslice.c:1106 #3 g_type_free_instance at gtype.c:1938 #4 g_cclosure_marshal_VOID__OBJECTv at gmarshal.c:1316 #5 _g_closure_invoke_va at gclosure.c:840 #8 gtk_container_remove at gtkcontainer.c:1240 #9 _gtk_tree_view_column_unset_tree_view at gtktreeviewcolumn.c:1359 #10 gtk_tree_view_remove_column at gtktreeview.c:11241 #11 gtk_tree_view_destroy at gtktreeview.c:1616
Created attachment 842037 [details] File: backtrace
Created attachment 842038 [details] File: cgroup
Created attachment 842039 [details] File: core_backtrace
Created attachment 842040 [details] File: dso_list
Created attachment 842041 [details] File: environ
Created attachment 842042 [details] File: exploitable
Created attachment 842043 [details] File: limits
Created attachment 842044 [details] File: maps
Created attachment 842045 [details] File: open_fds
Created attachment 842046 [details] File: proc_pid_status
Created attachment 842047 [details] File: var_log_messages
Can you describe a little more detailed what happend? Did this issue occurs frequently ?
Hello, ABRT tried to report a caja crash, but didn't because: "--- Running report_uReport --- A bug was already filed about this problem: Bugzilla: URL=https://bugzilla.redhat.com/show_bug.cgi?id=1046721" mate-file-manager-1.6.3-2.fc20 I'm running Mate on F20. Caja had three tabs open. I clicked the eject icon for a remote server I was connected to via sftp. Then, I right-clicked on the button for Caja, shown in the panel that has buttons for all of the running applications. I clicked "Close". Caja crashed. --James https://retrace.fedoraproject.org/faf/reports/306198/
Like James above, I tried to report this through ABRT, but it just noted: > --- Running report_Bugzilla --- > Logging into Bugzilla at https://bugzilla.redhat.com > Checking for duplicates > Bug is already reported: 1046721 > Logging out > Status: CLOSED INSUFFICIENT_DATA https://bugzilla.redhat.com/show_bug.cgi?id=1046721 I had mounted and ejected many different SD cards. Finally, I closed the caja window (open on 'Computer') and received the crash notification. $ rpm -qa mate-file* mate-file-manager-schemas-1.6.3-1.fc20.i686 mate-file-manager-extensions-1.6.3-1.fc20.i686 mate-file-manager-sendto-1.6.0-2.fc20.i686 mate-file-manager-image-converter-1.6.0-2.fc20.i686 mate-file-manager-1.6.3-1.fc20.i686 mate-file-archiver-1.6.1-0.1.git95ebd69.fc20.i686
I had the same crash now...
There is some data that I can provide to help you in solving this problem? Thanks since now!
Ok, reopened. to have fresh backtrace would be helpful. Go to var/tmp/abrt/folder-of-the-abrt-alarm/ If there is no backtrace run abrt-action-analyze-ccpp-local Then check the backtrace for missing debuginfo files, ie 0x00007f5ca06a1ab0 0x00007f5ca06cba54 Yes * /lib64/libdbus-1.so.3 (*) means the debuginfo file is missing. Install it and run abrt-action-generate-backtrace Also a detailed as possible description is needed for forwarding a issue to upstream.
(In reply to Wolfgang Ulbrich from comment #17) > Ok, reopened. > to have fresh backtrace would be helpful. > Go to var/tmp/abrt/folder-of-the-abrt-alarm/ > If there is no backtrace run > abrt-action-analyze-ccpp-local > Then check the backtrace for missing debuginfo files, ie > 0x00007f5ca06a1ab0 0x00007f5ca06cba54 Yes * /lib64/libdbus-1.so.3 > (*) means the debuginfo file is missing. > Install it and run > abrt-action-generate-backtrace > > Also a detailed as possible description is needed for forwarding a issue to > upstream. Hi, I got the backtrace, but I couldn't install the debuginfo... how can I do it? I'm attaching the backtrace here, is this can be useful...
Created attachment 914825 [details] Backtrace
Backtrace looks good, all debuginfo packages are installed. But can you give us a detailed description or steps to reproduce?
closed, package are renamed to caja