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:4028
#1 instance_dispose at base-window.c:529
#3 cact_main_window_quit at cact-main-window.c:1356
#8 _gtk_action_emit_activate at gtkaction.c:795
#9 gtk_action_activate at gtkaction.c:826
#10 button_clicked at gtktoolbutton.c:771
#11 _g_closure_invoke_va at gclosure.c:831
#14 gtk_real_button_released at gtkbutton.c:1712
#15 _g_closure_invoke_va at gclosure.c:831
#18 gtk_button_button_release at gtkbutton.c:1604
Created attachment 1005172 [details]
Created attachment 1005173 [details]
Created attachment 1005174 [details]
Created attachment 1005175 [details]
Created attachment 1005176 [details]
Created attachment 1005177 [details]
Created attachment 1005178 [details]
Created attachment 1005179 [details]
Created attachment 1005180 [details]
Created attachment 1005181 [details]
Can you describe a little more detailed what happend?
Did this issue occurs frequently ?
... my crystal ball is dead......
Another user experienced a similar problem:
Running the Alpha 32-bit live ISO in VirtualBox. Clickd on Caja-actions Config tool, Clicked one or 2 tabs out of curiosity then clicked the Quit icon.
reason: caja-actions-config-tool killed by SIGSEGV
runlevel: N 5
I can easily reproduce it on Mate 20150704 Nigthly Rawhide installed as qemu-kvm guest
Description of the problem:
caja-actions-config-tool crashes after closing it.
Version-release number of selected component:
Happens every time I try to reproduce it.
Steps to reproduce:
1. Launch caja-actions-config-tool from the system menu of Mate.
2. Close the tool
The tool crashes and abrt catches the exception
The tool should exit cleanly
FAF report: https://retrace.fedoraproject.org/faf/reports/727370/
After glib2 and gnome update to stable the issue is gone.
Same as every release.
I'm so bored of this nonsense........
From my perspective of using Fedora 22 MATE on both my machine at work and my PCs at home this bug has been fixed.
(In reply to Paul Thomas from comment #15)
> From my perspective of using Fedora 22 MATE on both my machine at work and
> my PCs at home this bug has been fixed.
But you reported it from a f22 Alpha 32-bit live ISO in VirtualBox.
I could it only reproduce in f23 dev or f22 dev phases, now it works here in f23.
Same in all my f22/f21 installations.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.