Bug 789733
Summary: | [gtk themes] nm-applet crashes in KDE with oxygen-gtk theme (SIGSEGV) | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | carasin <carasin.berlogue> | ||||||||||||||
Component: | gtk3 | Assignee: | Matthias Clasen <mclasen> | ||||||||||||||
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||
Severity: | unspecified | Docs Contact: | |||||||||||||||
Priority: | unspecified | ||||||||||||||||
Version: | 16 | CC: | dcbw, jklimes, mclasen, me, rdieter | ||||||||||||||
Target Milestone: | --- | ||||||||||||||||
Target Release: | --- | ||||||||||||||||
Hardware: | i686 | ||||||||||||||||
OS: | Unspecified | ||||||||||||||||
Whiteboard: | abrt_hash:f5398bf98c488dca3c96808e3f2d22ca5d56f728 | ||||||||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||
Doc Text: | Story Points: | --- | |||||||||||||||
Clone Of: | Environment: | ||||||||||||||||
Last Closed: | 2012-03-20 15:52:15 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
carasin
2012-02-12 18:52:36 UTC
Created attachment 561246 [details]
File: event_log
Created attachment 561247 [details]
File: pwd
Created attachment 561248 [details]
File: backtrace
Created attachment 561249 [details]
File: smolt_data
Created attachment 561250 [details]
File: maps
Created attachment 561251 [details]
File: dso_list
I be want to say additional information. This bug is affected only if nm-applet used in KDE. In gnome, xfce this bug is not affected. I would not be so sure. Perhaps, it should be tested in different DE with GTK3 theme Oxygen-GTK3,- for example, in XFCE & GNOME 3. It seems to me that trouble is in the missing icon files somewhere at the path /usr/share/icons/* I would not be so sure. Perhaps, it should be tested in different DE with GTK3 theme Oxygen-GTK3,- for example, in XFCE & GNOME 3. It seems to me that trouble is in the missing icon files somewhere at the path /usr/share/icons/* carasin, thanks for the reproducer in the description! I am able to reproduce the crash under KDE with your steps. Reloading of KDE is not necessary, just editing ~/.config/gtk-3.0/settings.ini and starting nm-applet: 1. yum install oxygen-gtk3 2. put [Settings] gtk-theme-name = oxygen-gtk into ~/.config/gtk-3.0/settings.ini 3. nm-applet 4. left click on the nm-applet icon (in the system tray) --> "Connect to Hidden Wireless Network..." 5. nm-applet crashes I've run the applet in gdb and found that the crash happens in gtkwidget.c:_gtk_widget_draw_internal(). Last two lines there are: 1) context = gtk_widget_get_style_context (widget); 2) _gtk_style_context_coalesce_animation_areas (context, widget); But (1) return NULL and (2) crashes trying to access it. The NULL is returned because the 'widget' has been freed before in g_emit_signal(): (gdb) s _gtk_widget_draw_internal (clip_to_size=1, cr=0x3c1f8a7860, widget=0x10307e0 [GtkToggleButton]) at gtkwidget.c:5722 5722 g_signal_emit (widget, widget_signals[DRAW], (gdb) p widget $1 = 0x10307e0 [GtkToggleButton] (gdb) p *widget $2 = {parent_instance = {g_type_instance = {g_class = 0x1048c10}, ref_count = 2, qdata = 0x0}, priv = 0x1030820} (gdb) watch *0x10307e0 Hardware watchpoint 4: *0x10307e0 (gdb) c Continuing. [Thread 0x7fffba7fc700 (LWP 16816) exited] Hardware watchpoint 4: *0x10307e0 Old value = 17075216 New value = 0 g_type_free_instance (instance=0x10307e0) at gtype.c:1935 1935 memset (instance, 0xaa, type_total_instance_size_I (node)); (gdb) bt #0 g_type_free_instance (instance=0x10307e0) at gtype.c:1935 #1 0x00000032322319d3 in g_value_unset (value=0x7fffbc004730) at gvalue.c:276 #2 0x00000032322261cb in g_signal_emit_valist (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>, var_args=<optimized out>) at gsignal.c:3063 #3 0x0000003232226352 in g_signal_emit (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>) at gsignal.c:3090 #4 0x00000030a268e1da in _gtk_widget_draw_internal (clip_to_size=1, cr=0x3c1f8a7860, widget=0x10307e0) at gtkwidget.c:5722 #5 _gtk_widget_draw_internal (widget=0x10307e0, cr=0x3c1f8a7860, clip_to_size=<optimized out>) at gtkwidget.c:5698 #6 0x00000030a24ce62e in gtk_container_propagate_draw (container=<optimized out>, child=0x10307e0, cr=0x3c1f8a7860) at gtkcontainer.c:3342 #7 0x00000030a24c321f in gtk_combo_box_draw (widget=0x10432e0 [GtkComboBox], cr=0x3c1f8a7860) at gtkcombobox.c:2772 #8 0x00000030a2552848 in _gtk_marshal_BOOLEAN__BOXED (closure=0x67afd0, return_value=0x7fffffffbba0, n_param_values=<optimized out>, param_values=0x164b320, invocation_hint=<optimized out>, marshal_data=<optimized out>) at gtkmarshalers.c:85 #9 0x00000030a267ca60 in gtk_widget_draw_marshaller (closure=0x67afd0, return_value=0x7fffffffbba0, n_param_values=2, param_values=0x164b320, invocation_hint=<optimized out>, marshal_data=<optimized out>) at gtkwidget.c:819 I'm not sure why the widget is freed, but it definitely depends on the oxygen theme. Having searched further, I discovered that line -GtkComboBox-appears-as-list: 1; in /usr/share/themes/oxygen-gtk/gtk-3.0/gtk.css causes the problem. If the line is removed or the value is changed to 0, the crash doesn't appear. So, either there is a bug in glib/gtk theming or rather oxygen theme is at fault. Some links: https://projects.kde.org/projects/playground/artwork/oxygen-gtk/repository https://bugs.kde.org/show_bug.cgi?id=261971 similar bugs: https://bugzilla.redhat.com/show_bug.cgi?id=749768 https://bugzilla.redhat.com/show_bug.cgi?id=706461 I'm moving the bug to gtk3 so that someone with the knowledge could look at the problem. Jirka Klimes, thanks for your work and workaround. Awaiting the further solution to this problem. Backtrace analysis found this bug to be similar to bug #799637, closing as duplicate. This comment is automatically generated. *** This bug has been marked as a duplicate of bug 799637 *** |