Bug 1523656

Created attachment 1364882 [details]
File: backtrace

Created attachment 1364883 [details]
File: cgroup

Created attachment 1364884 [details]
File: core_backtrace

Created attachment 1364885 [details]
File: cpuinfo

Created attachment 1364886 [details]
File: dso_list

Created attachment 1364887 [details]
File: environ

Created attachment 1364888 [details]
File: limits

Created attachment 1364889 [details]
File: maps

Created attachment 1364890 [details]
File: mountinfo

Created attachment 1364891 [details]
File: open_fds

Created attachment 1364892 [details]
File: proc_pid_status

Dupe of Bug 1418334 and Bug 1500478 , unless you want a new bug for F27

*** Bug 1418334 has been marked as a duplicate of this bug. ***

*** Bug 1500478 has been marked as a duplicate of this bug. ***

What i really want is that you open a report at upstream, before we close this one as a duplicate for a f28 report ;-)

Similar problem has been detected:

Tried to adjust the volume from the system tray.

reporter:       libreport-2.9.3
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=231ee633655a4b48904ea77f622b035c;i=24f8d8;b=65cb20f178c64ddab860d84ee0ec373c;m=587ff51f6;t=56191393e6431;x=579c03e53c42f535
kernel:         4.14.8-300.fc27.x86_64
package:        mate-media-1.19.1-1.fc27
reason:         mate-volume-control-applet killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

*** Bug 1532342 has been marked as a duplicate of this bug. ***

Similar stacktrace here in a upstream report.
https://github.com/mate-desktop/mate-media/issues/104
Sadly, this is a gtk+ function.

*** Bug 1538628 has been marked as a duplicate of this bug. ***

Similar problem has been detected:

I think it should have to do with a install/remove I performed following recoms from bugzilla forum about a warning
at every time I logged in related to the blueman package & following a dnf-by upgrading task from fedora 25, 
then 26 ther 27 to.
What I did was `$sudo dnf install blueberry && dnf remove blueman`. 
It resolved the warning at login issue but got into this when starting using my bluetooth headphones.

reporter:       libreport-2.9.3
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=46d500e166ba489d888a578fbf229c47;i=2111a2;b=d9adf75e85584548ada73f406d2d3245;m=9d1fdf0;t=563a3b9812273;x=873cd124bdefa7f2
kernel:         4.14.14-300.fc27.x86_64
package:        mate-media-1.19.1-1.fc27
reason:         mate-volume-control-applet killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Yes, blueman is obsolete,  you should use blueberry for Mate.
But, i suggest to open a report against blueberry as we have a different trigger for the issue.
At least it crashes somewhere in a gtk function in the stacktrace from this report and at upstream.

Similar problem has been detected:

plug-out and then plug-in external display's USB interface (with sound device, keyboard, mouse).

reporter:       libreport-2.9.1
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=64fbb6000c134b0fb26f889066a37842;i=7056e;b=8d8b9e6d8606488ca4f51e45aa24a16e;m=756addba6;t=5657f4e439189;x=fcec1de7719ee2d1
kernel:         4.14.18-200.fc26.x86_64
package:        mate-media-1.18.2-1.fc26
reason:         mate-volume-control-applet killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Similar problem has been detected:

Starting a song in rhythmbox

reporter:       libreport-2.9.3
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=b0fd28a48c3e497fb4bb0da91df759c4;i=54af8;b=749775ad35a64145a901671015b402e6;m=1de4170070;t=566c16591a913;x=735925582dfe749e
kernel:         4.15.6-300.fc27.x86_64
package:        mate-media-1.19.1-1.fc27
reason:         mate-volume-control-applet killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

*** Bug 1650293 has been marked as a duplicate of this bug. ***

Still an issue in 1.20.1-1.fc28.x86_64

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.

Similar problem has been detected:

increased the volume with the mouse wheel

reporter:       libreport-2.9.5
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=8d58127f4ccd40c093075fa94c9121c6;i=15fc1;b=bcb54f4a20714d19987706305df51956;m=3c7f68762c;t=57f6506f6ae66;x=c54f49fb5c2c6045
kernel:         4.19.13-200.fc28.x86_64
package:        mate-media-1.20.2-1.fc28
reason:         mate-volume-control-applet killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Similar problem has been detected:

just a click on the volume-ctl icon, nothing special

reporter:       libreport-2.9.5
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=43e4cbb1df1a4de393c2e34155d7c3b1;i=fa2c2;b=adaf00b804724f20bfa6c84b7fc7a10c;m=3501422970;t=57ff3576c273b;x=7792620a6427db52
kernel:         4.18.18-200.fc28.x86_64
package:        mate-media-1.20.2-1.fc28
reason:         mate-volume-control-applet killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            2128

Similar problem has been detected:

After selecting the volume/sound icon in the top panel, it crashes while on bluetooth sometimes.  The icon will also disapper until after a full restart.

reporter:       libreport-2.9.5
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=c6ad565aed5d4c4f8bd80b85a340c84a;i=80b8;b=2d92a5aedc9749b4b7f0de5675a54c7e;m=815e7cf70d;t=581a38ddb75d7;x=64bcaa4e41883c7b
kernel:         4.20.4-100.fc28.x86_64
package:        mate-media-1.20.2-1.fc28
reason:         mate-volume-control-applet killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. 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 '28'.

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 28 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 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.