Bug 952338 - [abrt] mate-panel-1.5.6-1.fc18: gtk_widget_get_parent: Process /usr/bin/mate-panel was killed by signal 11 (SIGSEGV)
Summary: [abrt] mate-panel-1.5.6-1.fc18: gtk_widget_get_parent: Process /usr/bin/mate-...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: mate-panel
Version: 18
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Dan Mashal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:0504178ab7367663945899d207c...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-04-15 17:34 UTC by Pavel Sergeev
Modified: 2013-07-14 18:03 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-14 18:03:27 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (27.44 KB, text/plain)
2013-04-15 17:34 UTC, Pavel Sergeev
no flags Details
File: cgroup (130 bytes, text/plain)
2013-04-15 17:34 UTC, Pavel Sergeev
no flags Details
File: core_backtrace (2.66 KB, text/plain)
2013-04-15 17:34 UTC, Pavel Sergeev
no flags Details
File: dso_list (10.25 KB, text/plain)
2013-04-15 17:34 UTC, Pavel Sergeev
no flags Details
File: environ (1.57 KB, text/plain)
2013-04-15 17:35 UTC, Pavel Sergeev
no flags Details
File: limits (1.29 KB, text/plain)
2013-04-15 17:35 UTC, Pavel Sergeev
no flags Details
File: maps (54.01 KB, text/plain)
2013-04-15 17:35 UTC, Pavel Sergeev
no flags Details
File: open_fds (2.28 KB, text/plain)
2013-04-15 17:35 UTC, Pavel Sergeev
no flags Details
File: proc_pid_status (930 bytes, text/plain)
2013-04-15 17:35 UTC, Pavel Sergeev
no flags Details
File: var_log_messages (503 bytes, text/plain)
2013-04-15 17:35 UTC, Pavel Sergeev
no flags Details
File: xsession_errors (558 bytes, text/plain)
2013-04-15 17:35 UTC, Pavel Sergeev
no flags Details

Description Pavel Sergeev 2013-04-15 17:34:40 UTC
Description of problem:
I have done two actions:
1. Removed one mate panel
2. Tried to add "Window List" to other panel.

One of this steps causes this issue.

Version-Release number of selected component:
mate-panel-1.5.6-1.fc18

Additional info:
backtrace_rating: 4
cmdline:        mate-panel
crash_function: gtk_widget_get_parent
executable:     /usr/bin/mate-panel
kernel:         3.8.5-201.fc18.x86_64
uid:            1000
ureports_counter: 1

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:48
 #2 mate_panel_applet_locked_change_notify at applet.c:192
 #3 g_cclosure_marshal_VOID__STRINGv at gmarshal.c:1004
 #4 _g_closure_invoke_va at gclosure.c:840
 #7 g_settings_real_change_event at gsettings.c:288
 #8 ffi_call_unix64 at ../src/x86/unix64.S:75
 #9 ffi_call at ../src/x86/ffi64.c:486
 #10 g_cclosure_marshal_generic_va at gclosure.c:1550
 #11 _g_closure_invoke_va at gclosure.c:840

Comment 1 Pavel Sergeev 2013-04-15 17:34:44 UTC
Created attachment 736000 [details]
File: backtrace

Comment 2 Pavel Sergeev 2013-04-15 17:34:50 UTC
Created attachment 736001 [details]
File: cgroup

Comment 3 Pavel Sergeev 2013-04-15 17:34:53 UTC
Created attachment 736002 [details]
File: core_backtrace

Comment 4 Pavel Sergeev 2013-04-15 17:34:56 UTC
Created attachment 736003 [details]
File: dso_list

Comment 5 Pavel Sergeev 2013-04-15 17:35:00 UTC
Created attachment 736004 [details]
File: environ

Comment 6 Pavel Sergeev 2013-04-15 17:35:02 UTC
Created attachment 736005 [details]
File: limits

Comment 7 Pavel Sergeev 2013-04-15 17:35:06 UTC
Created attachment 736006 [details]
File: maps

Comment 8 Pavel Sergeev 2013-04-15 17:35:09 UTC
Created attachment 736007 [details]
File: open_fds

Comment 9 Pavel Sergeev 2013-04-15 17:35:16 UTC
Created attachment 736008 [details]
File: proc_pid_status

Comment 10 Pavel Sergeev 2013-04-15 17:35:18 UTC
Created attachment 736009 [details]
File: var_log_messages

Comment 11 Pavel Sergeev 2013-04-15 17:35:21 UTC
Created attachment 736010 [details]
File: xsession_errors

Comment 12 Dan Mashal 2013-04-15 23:07:00 UTC
Which panel did you remove? The top of the bottom?

Which panel did you try to add window list to?

Comment 13 Pavel Sergeev 2013-04-16 18:43:52 UTC
I have tried to reproduce the issue:
1. Install group "MATE Desktop"
2. Restart system, login
3. Remove the bottom panel ("Delete This Panel" in context menu)
Last step causes the mate-panel crash.

Adding "Window List" is not required.

Comment 14 Dan Mashal 2013-04-17 06:51:16 UTC
1) How are you installing Fedora? via what media? 

2) What command are you using to install mate? What is  the exact yum command?

3) What do you choose when you install fedora? Minimal? Gnome desktop? what?

Comment 15 Pavel Sergeev 2013-04-17 17:06:10 UTC
1) Fedora-18-x86_64 DVD
2) yum groupinstall "Mate Desktop"
3) KDE

Also I'm able to reproduce mate-panel crash by the following steps:
1. Add new panel
2. Add "Window list" to the panel
3. Delete the panel
But looks like, stack traces are different. New bug id is 953222.

Comment 16 Claudio 2013-04-19 23:47:20 UTC
Dragged app launcher on the panel in a quick movement instead of selecting it.

backtrace_rating: 4
cmdline:        mate-panel
crash_function: gtk_widget_get_parent
executable:     /usr/bin/mate-panel
kernel:         3.8.6-203.fc18.i686
package:        mate-panel-1.5.6-1.fc18
reason:         Process /usr/bin/mate-panel was killed by signal 11 (SIGSEGV)
uid:            1000
ureports_counter: 1

Comment 17 Dan Mashal 2013-04-21 04:00:08 UTC
Use the netinstaller. or yum install @mate

Comment 18 Claudio 2013-04-21 21:02:43 UTC
I had no problems deleting my top panel and then adding apps to the bottom one. Just this minor incident.

Comment 19 Wolfgang Ulbrich 2013-07-08 15:58:58 UTC
Did this issue still exits with an updated MATE desktop, we're are on 1.6.x ?

Comment 20 Claudio 2013-07-14 13:45:31 UTC
Cannot replicate it with mate-panel 1.6.0-3, 32 bit version.

Comment 21 Wolfgang Ulbrich 2013-07-14 18:03:27 UTC
Thank you for feedback. I'm glad to hear theat the issue seems to be fixed with 1.6.x.
I will close the issue now, but feel free to post the here if it happens again.
I will re-open the report then.


Note You need to log in before you can comment on or make changes to this bug.