After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 399329 - Show Desktop: Non responsive after a w...
Show Desktop: Non responsive after a w...
Status: RESOLVED INCOMPLETE
Product: gtk+
Classification: Platform
Component: Widget: Other
2.10.x
Other All
: Normal critical
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2007-01-22 10:09 UTC by Thomas Wood
Modified: 2007-02-27 04:01 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Thomas Wood 2007-01-22 10:09:38 UTC 
Version: 2.16.3

Non responsive after a while


Distribution: Debian 4.0
Gnome Release: 2.17.5 2007-01-15 (JHBuild)
BugBuddy Version: 2.17.3
Comment 1 Thomas Wood 2007-01-22 10:12:16 UTC 
Uh, apparently bug buddy is not being helpful. Here is the backtrace:

+ Trace 104244

  • #0 __lll_mutex_lock_wait
    from /lib/tls/libc.so.6
  • #1 _L_mutex_lock_33
    from /lib/tls/libc.so.6
  • #2 IA__g_object_unref
    at gobject.c line 1750
  • #3 fork
    from /lib/tls/libc.so.6
  • #4 fork
    from /lib/tls/libpthread.so.0
  • #5 libgnomeui_segv_handle
    at gnome-ui-init.c line 849
  • #6 <signal handler called>
  • #7 _int_malloc
    from /lib/tls/libc.so.6
  • #8 malloc
    from /lib/tls/libc.so.6
  • #9 IA__g_malloc
    at gmem.c line 131
  • #10 IA__g_strdup
    at gstrfuncs.c line 91
  • #11 value_copy_string
    at gvaluetypes.c line 275
  • #12 IA__g_value_copy
    at gvalue.c line 119
  • #13 IA__g_value_transform
    at gvalue.c line 341
  • #14 IA__gdk_screen_get_setting
    at gdkevents-x11.c line 2943
  • #15 gtk_settings_get_property
    at gtksettings.c line 629
  • #16 IA__g_object_get_valist
    at gobject.c line 659
  • #17 IA__g_object_get
    at gobject.c line 1222
  • #18 _gtk_rc_context_get_default_font_name
    at gtkrc.c line 1684
  • #19 _gtk_style_init_for_settings
    at gtkstyle.c line 383
  • #20 gtk_style_init
    at gtkstyle.c line 410
  • #21 IA__g_type_create_instance
    at gtype.c line 1561
  • #22 g_object_constructor
    at gobject.c line 1041
  • #23 IA__g_object_newv
    at gobject.c line 937
  • #24 IA__g_object_new_valist
    at gobject.c line 981
  • #25 IA__g_object_new
    at gobject.c line 795
  • #26 clearlooks_rc_style_create_style
    at ./src/clearlooks_rc_style.c line 446
  • #27 gtk_rc_init_style
    at gtkrc.c line 2339
  • #28 IA__gtk_rc_get_style
    at gtkrc.c line 1980
  • #29 gtk_widget_reset_rc_style
    at gtkwidget.c line 4818
  • #30 reset_rc_styles_recurse
    at gtkwidget.c line 5352
  • #31 gtk_fixed_forall
    at gtkfixed.c line 453
  • #32 IA__gtk_container_forall
    at gtkcontainer.c line 1261
  • #33 reset_rc_styles_recurse
    at gtkwidget.c line 5355
  • #34 gtk_bin_forall
    at gtkbin.c line 133
  • #35 IA__gtk_container_forall
    at gtkcontainer.c line 1261
  • #36 reset_rc_styles_recurse
    at gtkwidget.c line 5355
  • #37 gtk_table_forall
    at gtktable.c line 931
  • #38 IA__gtk_container_forall
    at gtkcontainer.c line 1261
  • #39 reset_rc_styles_recurse
    at gtkwidget.c line 5355
  • #40 gtk_bin_forall
    at gtkbin.c line 133
  • #41 IA__gtk_container_forall
    at gtkcontainer.c line 1261
  • #42 reset_rc_styles_recurse
    at gtkwidget.c line 5355
  • #43 IA__gtk_widget_reset_rc_styles
    at gtkwidget.c line 5365
  • #44 gtk_rc_reset_widgets
    at gtkrc.c line 1595
  • #45 reset_styles_idle
    at gtkicontheme.c line 602
  • #46 g_idle_dispatch
    at gmain.c line 3928
  • #47 IA__g_main_context_dispatch
    at gmain.c line 2045
  • #48 g_main_context_iterate
    at gmain.c line 2677
  • #49 IA__g_main_loop_run
    at gmain.c line 2881
  • #50 IA__gtk_main
    at gtkmain.c line 1148
  • #51 main
    at main.c line 98 






Comment 2


Vincent Untz





          2007-01-22 16:39:33 UTC
        



Is it always the same stack trace when you interrupt the process?

Can you easily reproduce?

What version of gnome-panel do you have? (2.16.3 doesn't exist)






Comment 3


Thomas Wood





          2007-01-22 22:53:50 UTC
        



I have SVN trunk.

I'm not sure how it's reproducible, since I only noticed anything had crashed when trying to do alt-f2.






Comment 4


Sebastien Bacher





          2007-01-26 11:14:19 UTC
        



Ubuntu bug about that (feisty gnome-panel 2.17.90): https://launchpad.net/gnome-panel/+bug/81520 with a debug backtrace: http://librarian.launchpad.net/5854694/Stacktrace.txt

The Ubuntu bug is a crash not a hang though






Comment 5


Sebastien Bacher





          2007-01-30 14:48:14 UTC
        



Other Ubuntu crash about that: https://launchpad.net/ubuntu/+source/gnome-panel/+bug/82146






Comment 6


Sebastien Bacher





          2007-01-30 14:51:35 UTC
        



might be a GTK bug from the backtrace






Comment 7


Sebastien Bacher





          2007-01-30 15:58:49 UTC
        



From the Ubuntu bug:





+
Trace
    106560






    

  • 
#0
_int_malloc

    
                from
                /lib/tls/i686/cmov/libc.so.6

    

    • 

  • 
#1
malloc

    
                from
                /lib/tls/i686/cmov/libc.so.6

    

    • 

  • 
#2
IA__g_malloc

    
                at gmem.c
                  line
                  131

    

    • 

  • 
#3
IA__g_strdup

    
                at gstrfuncs.c
                  line
                  91

    

    • 

  • 
#4
value_copy_string

    
                at gvaluetypes.c
                  line
                  275

    

    • 

  • 
#5
IA__g_value_copy

    
                at gvalue.c
                  line
                  119

    

    • 

  • 
#6
IA__g_value_transform

    
                at gvalue.c
                  line
                  341

    

    • 

  • 
#7
IA__gdk_screen_get_setting

    
                at gdkevents-x11.c
                  line
                  2943

    

    • 













Comment 8


Vincent Untz





          2007-01-30 16:03:43 UTC
        



Moving to GTK+ since there's really nothing related to the panel/applets in there.






Comment 9


Matthias Clasen





          2007-01-30 16:25:12 UTC
        



A crash in malloc is a pretty strong hint at memory corruption happening earlier.

Please try to run the offending application under valgrind and see if anything comes up.






Comment 10


Andrew Conkling





          2007-01-31 03:06:21 UTC
        



(In reply to comment #9)
> A crash in malloc is a pretty strong hint at memory corruption happening
> earlier.
> 
> Please try to run the offending application under valgrind and see if anything
> comes up.

I haven't been able to reproduce this, at least not in my case. I had upgraded gnome-app-install and app-install-data on the initial crash (and I just tried reinstalling them to no avail).

Can anyone else reproduce this?






Comment 11


Thomas Wood





          2007-01-31 09:54:00 UTC
        



I haven't had this occur again, so I'll close as incomplete.






Comment 12


Andrew Conkling





          2007-02-27 04:01:09 UTC
        



I haven't been able to reproduce this crash, but I do have a valgrind log. I'm not sure if it's useful, but I'm going on days without reproducing the crash, which is very odd. :(

http://librarian.launchpad.net/6552390/valgrind.log.601