Bug 1011261

Summary: [abrt] nautilus-3.9.92-1.fc21: magazine_chain_pop_head: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Christopher Meng <i>
Component: nautilusAssignee: Matthias Clasen <mclasen>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: bugzilla, bugzilla, ccecchi, mclasen, miabbott, nhjest, scottt.tw, smitna
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:7b97ddb2e3c6da1f936013779aecae56423d6a93
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 10:25:58 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
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 Christopher Meng 2013-09-23 23:55:37 UTC 
Version-Release number of selected component:
nautilus-3.9.92-1.fc21

Additional info:
reporter:       libreport-2.1.7
backtrace_rating: 4
cmdline:        nautilus
crash_function: magazine_chain_pop_head
executable:     /usr/bin/nautilus
kernel:         3.12.0-0.rc1.git5.2.fc21.i686+PAE
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (9 frames)
 #0 magazine_chain_pop_head at gslice.c:545
 #1 thread_memory_magazine1_alloc at gslice.c:848
 #2 g_slice_alloc at gslice.c:1007
 #3 g_list_append at glist.c:232
 #4 _gdk_event_queue_append at gdkevents.c:148
 #5 _gdk_x11_display_queue_events at gdkeventsource.c:344
 #6 gdk_display_get_event at gdkdisplay.c:327
 #11 g_main_context_iteration at gmain.c:3773
 #12 g_application_run at gapplication.c:1635

Potential duplicate: bug 718677
Comment 1 Christopher Meng 2013-09-23 23:55:44 UTC 
Created attachment 801967 [details]
File: backtrace
Comment 2 Christopher Meng 2013-09-23 23:55:47 UTC 
Created attachment 801968 [details]
File: cgroup
Comment 3 Christopher Meng 2013-09-23 23:55:51 UTC 
Created attachment 801970 [details]
File: core_backtrace
Comment 4 Christopher Meng 2013-09-23 23:55:54 UTC 
Created attachment 801971 [details]
File: dso_list
Comment 5 Christopher Meng 2013-09-23 23:55:58 UTC 
Created attachment 801972 [details]
File: environ
Comment 6 Christopher Meng 2013-09-23 23:56:01 UTC 
Created attachment 801973 [details]
File: exploitable
Comment 7 Christopher Meng 2013-09-23 23:56:04 UTC 
Created attachment 801974 [details]
File: limits
Comment 8 Christopher Meng 2013-09-23 23:56:08 UTC 
Created attachment 801975 [details]
File: maps
Comment 9 Christopher Meng 2013-09-23 23:56:12 UTC 
Created attachment 801976 [details]
File: open_fds
Comment 10 Christopher Meng 2013-09-23 23:56:15 UTC 
Created attachment 801977 [details]
File: proc_pid_status
Comment 11 Christopher Meng 2013-09-23 23:56:18 UTC 
Created attachment 801978 [details]
File: var_log_messages
Comment 12 Jaroslav Reznik 2015-03-03 15:06:13 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Comment 13 Nicholas 2015-06-30 20:39:35 UTC 
Another user experienced a similar problem:

Left it on overnight, suddenly crashed. 

reporter:       libreport-2.6.0
backtrace_rating: 4
cmdline:        /usr/bin/nautilus --gapplication-service
crash_function: magazine_chain_pop_head
executable:     /usr/bin/nautilus
global_pid:     8424
kernel:         4.0.6-300.fc22.x86_64
package:        nautilus-3.16.2-1.fc22
reason:         nautilus killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 14 Nicholas 2015-08-06 18:10:03 UTC 
Another user experienced a similar problem:

Was tabbed out, and it suddenly crashed.

reporter:       libreport-2.6.2
backtrace_rating: 4
cmdline:        /usr/bin/nautilus --gapplication-service
crash_function: magazine_chain_pop_head
executable:     /usr/bin/nautilus
global_pid:     2805
kernel:         4.1.3-200.fc22.x86_64
package:        nautilus-3.16.2-2.fc22
reason:         nautilus killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 15 Nicholas 2015-08-12 01:36:50 UTC 
Another user experienced a similar problem:

Was browsing the web, and it suddenly crashed.

reporter:       libreport-2.6.2
backtrace_rating: 4
cmdline:        /usr/bin/nautilus --gapplication-service
crash_function: magazine_chain_pop_head
executable:     /usr/bin/nautilus
global_pid:     2707
kernel:         4.1.3-201.fc22.x86_64
package:        nautilus-3.16.2-2.fc22
reason:         nautilus killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 16 bugzilla 2015-08-15 20:30:19 UTC 
Another user experienced a similar problem:

symbol view from a directory with around 200 jpgs

reporter:       libreport-2.6.2
backtrace_rating: 4
cmdline:        /usr/bin/nautilus --gapplication-service
crash_function: magazine_chain_pop_head
executable:     /usr/bin/nautilus
global_pid:     3206
kernel:         4.1.4-200.fc22.x86_64
package:        nautilus-3.16.2-2.fc22
reason:         nautilus killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            13301
Comment 17 Fedora End Of Life 2016-07-19 10:25:58 UTC 
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.