Description of problem: Just opening the application. Version-Release number of selected component: gnome-music-3.20.2-2.fc24 Additional info: reporter: libreport-2.7.1 backtrace_rating: 4 cmdline: python3 /usr/bin/gnome-music crash_function: _g_log_abort executable: /usr/bin/python3.5 global_pid: 24325 kernel: 4.5.7-300.fc24.x86_64 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project reproducible: Not sure how to reproduce the problem runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 _g_log_abort at gmessages.c:325 #3 g_wakeup_new at gwakeup.c:161 #4 g_main_context_new at gmain.c:653 #5 initable_init at gdbusproxy.c:1935 #6 g_initable_new_valist at ginitable.c:228 #7 g_initable_new at ginitable.c:146 #8 gvfs_metadata_proxy_new_for_bus_sync at metadata-dbus.c:1397 #9 meta_tree_get_metadata_proxy at metatree.c:173 #10 get_tree_for_device at metatree.c:2851 #11 meta_lookup_cache_lookup_path at metatree.c:3365
Created attachment 1173894 [details] File: backtrace
Created attachment 1173895 [details] File: cgroup
Created attachment 1173896 [details] File: core_backtrace
Created attachment 1173897 [details] File: dso_list
Created attachment 1173898 [details] File: environ
Created attachment 1173899 [details] File: limits
Created attachment 1173900 [details] File: maps
Created attachment 1173901 [details] File: mountinfo
Created attachment 1173902 [details] File: namespaces
Created attachment 1173903 [details] File: open_fds
Created attachment 1173904 [details] File: proc_pid_status
Created attachment 1173905 [details] File: var_log_messages
Similar problem has been detected: Music crashes reliably when started here. reporter: libreport-2.7.2 backtrace_rating: 4 cmdline: python3 /usr/bin/gnome-music crash_function: _g_log_abort executable: /usr/bin/python3.5 global_pid: 11897 kernel: 4.7.4-200.fc24.x86_64 package: gnome-music-3.20.2-2.fc24 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project reason: python3.5 killed by SIGTRAP 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.