Hide Forgot
Description of problem: I just started Gnome music and then it crashed Version-Release number of selected component: gnome-music-3.19.92-1.fc24 Additional info: reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: python3 /usr/bin/gnome-music crash_function: magazine_chain_pop_head executable: /usr/bin/python3.5 global_pid: 2939 kernel: 4.4.5-300.fc23.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 magazine_chain_pop_head at gslice.c:539 #1 thread_memory_magazine1_alloc at gslice.c:842 #2 g_slice_alloc at gslice.c:1016 #3 g_slist_prepend at gslist.c:254 #4 g_object_notify_queue_add at gobject.c:311 #5 object_set_property at gobject.c:1430 #6 g_object_new_internal at gobject.c:1815 #7 g_object_new_valist at gobject.c:2040 #8 g_async_initable_new_valist_async at gasyncinitable.c:422 #9 g_async_initable_new_async at gasyncinitable.c:339
Created attachment 1140376 [details] File: backtrace
Created attachment 1140377 [details] File: cgroup
Created attachment 1140378 [details] File: core_backtrace
Created attachment 1140379 [details] File: dso_list
Created attachment 1140380 [details] File: environ
Created attachment 1140381 [details] File: exploitable
Created attachment 1140382 [details] File: limits
Created attachment 1140383 [details] File: maps
Created attachment 1140384 [details] File: mountinfo
Created attachment 1140385 [details] File: namespaces
Created attachment 1140386 [details] File: open_fds
Created attachment 1140387 [details] File: proc_pid_status
Created attachment 1140388 [details] File: var_log_messages
Similar problem has been detected: Just started Gnome music and tried to switch to the artist view reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: python3 /usr/bin/gnome-music crash_function: magazine_chain_pop_head executable: /usr/bin/python3.5 global_pid: 3061 kernel: 4.4.5-300.fc23.x86_64 package: gnome-music-3.20.0-1.fc24 reason: python3.5 killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 '24'. 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 24 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 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.