Hide Forgot
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
Created attachment 829039 [details] File: backtrace
Created attachment 829040 [details] File: cgroup
Created attachment 829041 [details] File: core_backtrace
Created attachment 829042 [details] File: dso_list
Created attachment 829043 [details] File: environ
Created attachment 829044 [details] File: exploitable
Created attachment 829045 [details] File: limits
Created attachment 829046 [details] File: maps
Created attachment 829047 [details] File: open_fds
Created attachment 829048 [details] File: proc_pid_status
Created attachment 829049 [details] File: var_log_messages
What were you doing when this happened? Can you duplicate it?
Nothing that I know of; as far as I remember, calibre wasn't even in the foreground. And no, I can't reproduce this.
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
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.
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.