Bug 1034530

Summary: [abrt] calibre-1.9.0-4.fc20: magazine_chain_pop_head: Process /usr/bin/python2.7 was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: igor.redhat <igor.redhat>
Component: calibreAssignee: Kevin Fenzi <kevin>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: chkr, frankly3d, kevin, mbacovsk, nushio, zbyszek
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/b98b66f5b6aa6e1cc17b7daf782abb975c94920a
Whiteboard: abrt_hash:ee669636b9f4f05286d6358524169d5c6b0a5e02
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-30 00:45:06 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 igor.redhat@gmail.com 2013-11-26 03:52:54 UTC
Version-Release number of selected component:
calibre-1.9.0-4.fc20

Additional info:
reporter:       libreport-2.1.9
backtrace_rating: 4
cmdline:        python2 /usr/bin/calibre
crash_function: magazine_chain_pop_head
executable:     /usr/bin/python2.7
kernel:         3.11.8-300.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            500

Truncated backtrace:
Thread no. 1 (10 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_slice_alloc0 at gslice.c:1042
 #4 g_type_create_instance at gtype.c:1850
 #5 g_object_new_internal at gobject.c:1746
 #8 _g_local_file_new at glocalfile.c:304
 #9 g_daemon_vfs_get_file_for_path at gdaemonvfs.c:394
 #10 ih_event_callback at inotify-helper.c:181
 #11 ip_event_dispatch at inotify-path.c:493

Comment 1 igor.redhat@gmail.com 2013-11-26 03:53:08 UTC
Created attachment 829039 [details]
File: backtrace

Comment 2 igor.redhat@gmail.com 2013-11-26 03:53:12 UTC
Created attachment 829040 [details]
File: cgroup

Comment 3 igor.redhat@gmail.com 2013-11-26 03:53:17 UTC
Created attachment 829041 [details]
File: core_backtrace

Comment 4 igor.redhat@gmail.com 2013-11-26 03:53:21 UTC
Created attachment 829042 [details]
File: dso_list

Comment 5 igor.redhat@gmail.com 2013-11-26 03:53:24 UTC
Created attachment 829043 [details]
File: environ

Comment 6 igor.redhat@gmail.com 2013-11-26 03:53:28 UTC
Created attachment 829044 [details]
File: exploitable

Comment 7 igor.redhat@gmail.com 2013-11-26 03:53:32 UTC
Created attachment 829045 [details]
File: limits

Comment 8 igor.redhat@gmail.com 2013-11-26 03:53:38 UTC
Created attachment 829046 [details]
File: maps

Comment 9 igor.redhat@gmail.com 2013-11-26 03:53:41 UTC
Created attachment 829047 [details]
File: open_fds

Comment 10 igor.redhat@gmail.com 2013-11-26 03:53:45 UTC
Created attachment 829048 [details]
File: proc_pid_status

Comment 11 igor.redhat@gmail.com 2013-11-26 03:53:49 UTC
Created attachment 829049 [details]
File: var_log_messages

Comment 12 Kevin Fenzi 2013-11-28 19:44:52 UTC
What were you doing when this happened?

Can you duplicate it?

Comment 13 igor.redhat@gmail.com 2013-11-29 04:26:54 UTC
Nothing that I know of; as far as I remember, calibre wasn't even in the foreground. And no, I can't reproduce this.

Comment 14 igor.redhat@gmail.com 2014-01-18 04:33:44 UTC
Another user experienced a similar problem:

Calibre was in the background, I wasn't interacting with it when the crash happened.

reporter:       libreport-2.1.11
backtrace_rating: 4
cmdline:        python2 /usr/bin/calibre
crash_function: magazine_chain_pop_head
executable:     /usr/bin/python2.7
kernel:         3.12.7-300.fc20.x86_64
package:        calibre-1.9.0-4.fc20
reason:         python2.7 killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            500

Comment 15 Fedora End Of Life 2015-05-29 09:51:24 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 '20'.

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 20 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 16 Fedora End Of Life 2015-06-30 00:45:06 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.