Description of problem: after turning on the pc that was in sleep mode Version-Release number of selected component: mate-media-1.20.2-1.fc29 Additional info: reporter: libreport-2.10.0 backtrace_rating: 4 cmdline: mate-volume-control-applet crash_function: gtk_widget_get_frame_clock executable: /usr/bin/mate-volume-control-applet journald_cursor: s=21b578d6a08b46ce8b766cca8f9eb9b0;i=6250a;b=4849a30de34a4dd58b4fb3a67d41d2b9;m=59b5fa637;t=5854228724745;x=df139656512fd638 kernel: 5.0.3-200.fc29.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Potential duplicate: bug 1523656
Created attachment 1549593 [details] File: backtrace
Created attachment 1549594 [details] File: cgroup
Created attachment 1549595 [details] File: core_backtrace
Created attachment 1549596 [details] File: cpuinfo
Created attachment 1549597 [details] File: dso_list
Created attachment 1549598 [details] File: limits
Created attachment 1549599 [details] File: maps
Created attachment 1549600 [details] File: mountinfo
Created attachment 1549601 [details] File: open_fds
Created attachment 1549602 [details] File: proc_pid_status
What was the problem except you did get a notice from abrt tool and filed out a report? Any collateral damages?
Similar problem has been detected: Clicked on media volume control icon to change volume and it crashed. reporter: libreport-2.10.0 backtrace_rating: 4 cmdline: mate-volume-control-applet crash_function: gtk_widget_get_frame_clock executable: /usr/bin/mate-volume-control-applet journald_cursor: s=77eb5fea214740d2805579746ede885f;i=11024;b=eb00d8ac485f4b88b5b9cef9583c4ac4;m=1ec879ad27a;t=586f7e6834cc3;x=f992864fe0cdbe5e kernel: 4.20.16-200.fc29.x86_64 package: mate-media-1.20.2-1.fc29 reason: mate-volume-control-applet killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: opened this page on opera browser (ver.60.0.3255.70): https://www.livenewsmag.com/bbc-news-uk-live-stream/ reporter: libreport-2.10.0 backtrace_rating: 4 cmdline: mate-volume-control-applet crash_function: gtk_widget_get_frame_clock executable: /usr/bin/mate-volume-control-applet journald_cursor: s=0777edf281aa44229d7d2cf1773bee2e;i=e521;b=7886c4aa78b14e039233b15c86d3dd84;m=91ed05ba8;t=58826a4424528;x=96ede871c0450e35 kernel: 5.0.10-200.fc29.x86_64 package: mate-media-1.20.2-1.fc29 reason: mate-volume-control-applet killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
(In reply to Wolfgang Ulbrich from comment #11) > What was the problem except you did get a notice from abrt tool and filed > out a report? > Any collateral damages? Also got this regulary on F30. The damages are: 1) One has to click on a popup to restart the applet. 2) Each time a core of 300M is silently dumped to $HOME. Found this just by accident, having already 6 coredupms stored. 6*300=1.8G, not that funny, isn't it?
*** Bug 1749825 has been marked as a duplicate of this bug. ***
https://github.com/mate-desktop/mate-media/issues/89
Similar problem has been detected: The system is fairly busy: there are two gpus (each driven by a cpu thread) running folding@home and six other threads running other (BOINC) floating point intensive clients. I was watching a youtube video when the sound applet terminated. reporter: libreport-2.10.1 backtrace_rating: 4 cmdline: /usr/libexec/mate-volume-control-applet crash_function: gtk_widget_get_frame_clock executable: /usr/libexec/mate-volume-control-applet journald_cursor: s=a219208673b54ad089e9e1ec7da7ea0e;i=4668b;b=957eed2f16fa4ae89ed72f0d5255686b;m=2f26f0bedc;t=5928b480de2f8;x=50832d7fa26cb47e kernel: 5.2.13-200.fc30.x86_64 package: mate-media-1.22.1-1.fc30 reason: mate-volume-control-applet killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. 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 '29'. 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 29 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 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 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.
Still have this regularly, now with Fedora 31. Please re-open.