Bug 1046814 - [abrt] mate-file-manager: magazine_cache_push_magazine(): caja killed by SIGSEGV
Summary: [abrt] mate-file-manager: magazine_cache_push_magazine(): caja killed by SIGSEGV
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: mate-file-manager
Version: 20
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Dan Mashal
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:51f7b476a96254171d93a8fe776...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-27 00:05 UTC by mazdac
Modified: 2014-05-06 15:31 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-01-12 11:11:25 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (30.29 KB, text/plain)
2013-12-27 00:05 UTC, mazdac
no flags Details
File: cgroup (172 bytes, text/plain)
2013-12-27 00:05 UTC, mazdac
no flags Details
File: core_backtrace (33.45 KB, text/plain)
2013-12-27 00:05 UTC, mazdac
no flags Details
File: dso_list (11.12 KB, text/plain)
2013-12-27 00:05 UTC, mazdac
no flags Details
File: environ (1.31 KB, text/plain)
2013-12-27 00:05 UTC, mazdac
no flags Details
File: exploitable (117 bytes, text/plain)
2013-12-27 00:05 UTC, mazdac
no flags Details
File: limits (1.29 KB, text/plain)
2013-12-27 00:06 UTC, mazdac
no flags Details
File: maps (54.78 KB, text/plain)
2013-12-27 00:06 UTC, mazdac
no flags Details
File: open_fds (4.58 KB, text/plain)
2013-12-27 00:06 UTC, mazdac
no flags Details
File: proc_pid_status (930 bytes, text/plain)
2013-12-27 00:06 UTC, mazdac
no flags Details
File: var_log_messages (1.00 KB, text/plain)
2013-12-27 00:06 UTC, mazdac
no flags Details

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.


Note You need to log in before you can comment on or make changes to this bug.