Bug 1097439

Summary: [abrt] caja: magazine_chain_pop_head(): caja killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Sam Tygier <samtygier>
Component: cajaAssignee: Wolfgang Ulbrich <raveit65.sun>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 21CC: cutnioff, dan.mashal, fedora, mkpdev, raveit65.sun, zpd1047
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:b7e4d70ff1127c8c4ecc414e5f1706ef623f8f36
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-12-02 03:11:46 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 Sam Tygier 2014-05-13 20:20:56 UTC 
Description of problem:
got this after unmounting and unplugging an android phone attached by USB

Version-Release number of selected component:
caja-1.8.1-1.fc21

Additional info:
reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        caja
crash_function: magazine_chain_pop_head
executable:     /usr/bin/caja
kernel:         3.15.0-0.rc5.git1.1.fc21.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 magazine_chain_pop_head at gslice.c:544
 #1 magazine_chain_prepare_fields at gslice.c:617
 #2 magazine_cache_push_magazine at gslice.c:691
 #3 thread_memory_magazine2_unload at gslice.c:809
 #4 g_slice_free1 at gslice.c:1094
 #5 g_type_free_instance at gtype.c:1938
 #6 gtk_container_destroy at gtkcontainer.c:1073
 #11 gtk_object_dispose at gtkobject.c:421
 #13 gtk_toolbar_forall at gtktoolbar.c:2529
 #14 gtk_container_destroy at gtkcontainer.c:1073
Comment 1 Sam Tygier 2014-05-13 20:20:59 UTC 
Created attachment 895248 [details]
File: backtrace
Comment 2 Sam Tygier 2014-05-13 20:21:01 UTC 
Created attachment 895249 [details]
File: cgroup
Comment 3 Sam Tygier 2014-05-13 20:21:04 UTC 
Created attachment 895250 [details]
File: core_backtrace
Comment 4 Sam Tygier 2014-05-13 20:21:06 UTC 
Created attachment 895251 [details]
File: dso_list
Comment 5 Sam Tygier 2014-05-13 20:21:08 UTC 
Created attachment 895252 [details]
File: environ
Comment 6 Sam Tygier 2014-05-13 20:21:11 UTC 
Created attachment 895253 [details]
File: exploitable
Comment 7 Sam Tygier 2014-05-13 20:21:13 UTC 
Created attachment 895254 [details]
File: limits
Comment 8 Sam Tygier 2014-05-13 20:21:15 UTC 
Created attachment 895255 [details]
File: maps
Comment 9 Sam Tygier 2014-05-13 20:21:18 UTC 
Created attachment 895256 [details]
File: open_fds
Comment 10 Sam Tygier 2014-05-13 20:21:20 UTC 
Created attachment 895257 [details]
File: proc_pid_status
Comment 11 Sam Tygier 2014-05-13 20:21:22 UTC 
Created attachment 895258 [details]
File: var_log_messages
Comment 12 Wolfgang Ulbrich 2014-08-26 20:15:56 UTC 
*** Bug 1132298 has been marked as a duplicate of this bug. ***
Comment 13 Sergei S. Rublёv 2014-09-10 08:48:32 UTC 
Another user experienced a similar problem:

My mom was copying and viewing photographs from attached SD flash card

reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        caja
crash_function: magazine_chain_pop_head
executable:     /usr/bin/caja
kernel:         3.15.10-200.fc20.x86_64
package:        caja-1.8.1-5.fc20
reason:         caja killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 14 Wolfgang Ulbrich 2014-10-23 17:26:39 UTC 
Is the problem still exists with the latest updates?
Comment 15 Wolfgang Ulbrich 2014-10-23 17:28:01 UTC 
And why use your mom rawhide?
Comment 16 Sergei S. Rublёv 2014-11-04 15:00:23 UTC 
No, recently there were no such bugs, and the system was updated.

My mom is using my OS. My OS is RFremix 20, not exactly Fedora 20. It has some additional repositories attached. There are several "rawhide" repos in yumex's repo list, but they are turned off by derault installation of RFremix. My uname -a is 

Linux ssr-rfremix 3.16.6-203.fc20.x86_64 #1 SMP Sat Oct 25 12:44:32 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
Comment 17 Fedora End Of Life 2015-11-04 14:57:01 UTC 
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '21'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 21 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 18 Fedora End Of Life 2015-12-02 03:11:50 UTC 
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.