Version-Release number of selected component: gnome-music-3.26.1-1.fc27 Additional info: reporter: libreport-2.9.3 backtrace_rating: 3 cmdline: python3 /usr/bin/gnome-music crash_function: g_time_zone_unref executable: /usr/bin/python3.6 journald_cursor: s=890623c7e3fa421d80dfbb0dbf8e8b83;i=54e23;b=8bc68ce9d2d346eb9613ba59e5df1a5e;m=58c8aea60;t=55f644f585c76;x=cf0f95d3260704ce kernel: 4.13.16-300.fc27.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 g_time_zone_unref at gtimezone.c:210 #1 g_date_time_unref at gdatetime.c:483 #2 g_value_unset at gvalue.c:275 #3 free_value at data/grl-related-keys.c:95 #4 g_hash_table_insert_node at ghash.c:997 #5 g_hash_table_insert_internal at ghash.c:1235 #6 grl_data_set_boxed at data/grl-data.c:529 #7 ffi_call_unix64 at ../src/x86/unix64.S:76 #8 ffi_call at ../src/x86/ffi64.c:525 #9 ??
Created attachment 1362116 [details] File: backtrace
Created attachment 1362117 [details] File: cgroup
Created attachment 1362118 [details] File: core_backtrace
Created attachment 1362119 [details] File: cpuinfo
Created attachment 1362120 [details] File: dso_list
Created attachment 1362121 [details] File: environ
Created attachment 1362122 [details] File: exploitable
Created attachment 1362123 [details] File: limits
Created attachment 1362124 [details] File: maps
Created attachment 1362125 [details] File: mountinfo
Created attachment 1362126 [details] File: open_fds
Created attachment 1362127 [details] File: proc_pid_status
Similar problem has been detected: Music sometimes crashes for no reason at all. Everytime it happened so far it was happily playing music in the background when BAM (bam not audible) and it crashed. reporter: libreport-2.9.3 backtrace_rating: 3 cmdline: python3 /usr/bin/gnome-music crash_function: g_time_zone_unref executable: /usr/bin/python3.6 journald_cursor: s=61ed76bdfd914f54a0224ef144f4cf32;i=184cf8;b=dfcde4fa108943f9a0b2adcbcf53f612;m=c8fe6e905;t=55fe92bcbd7b7;x=6b05a5747e1b5dc6 kernel: 4.13.16-300.fc27.x86_64 package: gnome-music-3.26.1-1.fc27 reason: python3.6 killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Listened to music reporter: libreport-2.9.3 backtrace_rating: 3 cmdline: python3 /usr/bin/gnome-music crash_function: g_time_zone_unref executable: /usr/bin/python3.6 journald_cursor: s=ddb505ac1a8c452fba200075a61a4c42;i=1c030;b=e6062d8de75d406aa992cf29628ce972;m=12ed66012;t=565d29051707e;x=8b545c058a12b5f0 kernel: 4.15.4-300.fc27.x86_64 package: gnome-music-3.26.2-1.fc27 reason: python3.6 killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. 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 '27'. 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 27 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 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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.