Red Hat Bugzilla – Bug 1279101
[abrt] mate-panel: g_type_check_instance_is_fundamentally_a(): mate-panel killed by SIGSEGV
Last modified: 2016-12-20 10:29:59 EST
Description of problem:
This problem happens often whe I log out and then log in again.
It happened before with F22 and is still happening now with F23.
Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (10 frames)
#0 g_type_check_instance_is_fundamentally_a at gtype.c:4030
#2 container_child_background_set at mate-panel-applet-frame-dbus.c:240
#3 g_simple_async_result_complete at gsimpleasyncresult.c:801
#4 set_applet_property_cb at mate-panel-applet-container.c:560
#5 g_task_return_now at gtask.c:1104
#6 g_task_return at gtask.c:1162
#7 g_dbus_connection_call_done at gdbusconnection.c:5702
#8 g_task_return_now at gtask.c:1104
#9 complete_in_idle_cb at gtask.c:1118
#14 gtk_main at gtkmain.c:1268
Potential duplicate: bug 1238820
Created attachment 1091090 [details]
Created attachment 1091091 [details]
Created attachment 1091092 [details]
Created attachment 1091093 [details]
Created attachment 1091094 [details]
Created attachment 1091095 [details]
Created attachment 1091096 [details]
Created attachment 1091097 [details]
Created attachment 1091098 [details]
Created attachment 1091099 [details]
Created attachment 1091100 [details]
Please test http://koji.fedoraproject.org/koji/taskinfo?taskID=11750807
Here i've revert the commit which was mentioned in https://bugzilla.redhat.com/show_bug.cgi?id=1238820#c17
But this can also bring back https://bugzilla.redhat.com/show_bug.cgi?id=1192722
If this build fix your issue than we have a base to discuss this at upstream.
opps, wrong link.
Here's the one for f23 builds http://koji.fedoraproject.org/koji/taskinfo?taskID=11750854
Now, i run for my self in this issue :)
During session logout i saw the abrt alarm, but the panel doesn't crashed.
So it looks like the panel didn't closed cleanly, or abrt think it is aseqfault if the panel closed.
The abrt notification with session start is only the repeated notification if the session ends.
Did you test my scratch builds?
Otherwise i assume you don't want that try to fix your problems.
Another user experienced a similar problem:
I installed the Xfce Desktop from my Mate desktop and rebooted the system. After the system rebooted I logged into the Xfce session/desktop. After the login I saw the error and reported it.
reason: mate-panel killed by SIGSEGV
runlevel: N 5
New attempt from upstream to fix this issue.
Scratch build for all branches please test, as upstream and me couldn't reproduce the issue you help is needed.
mate-panel-1.12.2-2.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-46287aa373
mate-panel-1.12.2-2.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-46287aa373
mate-panel-1.12.2-2.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.
This is still happening with mate-panel-1.14.1-1.fc23.
Can you please attach a new stacktrace?
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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'
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 23 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 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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
Thank you for reporting this bug and we are sorry it could not be fixed.