Bug 1279060
| Summary: | [abrt] mate-panel: gtk_widget_get_parent(): mate-panel killed by SIGSEGV | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Yonatan <yonatan.el.amigo> | ||||||||
| Component: | mate-panel | Assignee: | Wolfgang Ulbrich <fedora> | ||||||||
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 23 | CC: | fedora, mauricio.pronet, paulim_developerweb, stefano | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | i686 | ||||||||||
| OS: | Unspecified | ||||||||||
| URL: | https://retrace.fedoraproject.org/faf/reports/bthash/ddc084ffd17aed723eddf29f069a28be1e624f43 | ||||||||||
| Whiteboard: | abrt_hash:0504178ab7367663945899d207ca5907b7726ee0;VARIANT_ID=workstation; | ||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2016-08-13 18:24:13 UTC | Type: | --- | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Attachments: |
|
||||||||||
|
Description
Yonatan
2015-11-07 15:15:18 UTC
Created attachment 1090974 [details]
File: backtrace
Created attachment 1090975 [details]
File: cgroup
Created attachment 1090976 [details]
File: core_backtrace
Can you provide a valid description? Steps to reproduce? Did this issue occurs frequently ? Is the problem still exists with the latest updates? *** Bug 1329883 has been marked as a duplicate of this bug. *** Damon Hill 2016-04-24 07:11:34 EDT Description of problem: I was trying to move a just created launcher to the first place, where the default launchers were blocked Version-Release number of selected component: mate-panel-1.12.2-1.fc23 Additional info: reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: mate-panel crash_function: gtk_widget_get_parent executable: /usr/bin/mate-panel global_pid: 9080 kernel: 4.4.7-300.fc23.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 gtk_widget_get_parent at gtkwidget.c:6483 #1 mate_panel_applet_get_panel_widget at applet.c:50 #2 mate_panel_applet_locked_change_notify at applet.c:196 #3 g_cclosure_marshal_VOID__STRINGv at gmarshal.c:1794 #4 _g_closure_invoke_va at gclosure.c:864 #7 g_settings_real_change_event at gsettings.c:386 #8 ffi_call_unix64 at ../src/x86/unix64.S:76 #9 ffi_call at ../src/x86/ffi64.c:525 #10 g_cclosure_marshal_generic_va at gclosure.c:1600 #11 _g_closure_invoke_va at gclosure.c:864 stacktrace: https://bugzilla.redhat.com/attachment.cgi?id=1150122 @ Damon Hill Can you please don't file out private reports and clean the report from private data before sending, because Mate upstream don't have a bugzilla account and can't read such reports. My private time is rare and i don't want forward reports by hand. Thank you PS: there is a checkbox in abrt GUI which is enable by default in f23. ................what a bad idea from abrt guys. Sadly no answer from reporter! |