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 521682 - patch for bug 517676 makes nautilus crash
patch for bug 517676 makes nautilus crash
Status: RESOLVED FIXED
Product: glib
Classification: Platform
Component: gio
2.15.x
Other Linux
: Normal blocker
: ---
Assigned To: Alexander Larsson
gtkdev
Depends on:
Blocks:
 
 
Reported: 2008-03-10 22:24 UTC by Diego González
Modified: 2008-03-12 19:28 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
a fix (1.44 KB, patch)
2008-03-10 22:57 UTC, Samuel Cormier-Iijima
none Details | Review
and one without debugging outputs (1.40 KB, patch)
2008-03-10 23:04 UTC, Samuel Cormier-Iijima
none Details | Review

Description Diego González 2008-03-10 22:24:20 UTC
Nautilus crashes when starting up, this is the back trace:

  • #0 free
    from /lib/i686/cmov/libc.so.6
  • #1 IA__g_free
    at gmem.c line 190
  • #2 IA__g_strfreev
    at gstrfuncs.c line 2434
  • #3 g_themed_icon_set_property
    at gthemedicon.c line 113
  • #4 object_set_property
    at gobject.c line 697
  • #5 g_object_constructor
    at gobject.c line 1060
  • #6 IA__g_object_newv
    at gobject.c line 937
  • #7 IA__g_object_new_valist
    at gobject.c line 1027
  • #8 IA__g_object_new
    at gobject.c line 795
  • #9 IA__g_themed_icon_new_with_default_fallbacks
    at gthemedicon.c line 325
  • #10 update_from_hal
    from /usr/lib/gio/modules/libgiohal-volume-monitor.so
  • #11 ??
  • #12 ??
    from /lib/i686/cmov/libc.so.6
  • #13 ??
    from /usr/lib/libhal.so.1
  • #14 ??
    from /usr/lib/libglib-2.0.so.0
  • #15 ??
  • #16 ??
  • #17 ??
  • #18 IA__g_malloc
    at gmem.c line 131

Comment 1 Samuel Cormier-Iijima 2008-03-10 22:57:29 UTC
Created attachment 107021 [details] [review]
a fix

My mistake, this was due to a really stupid typo. Can you see if this patch fixes it?
Comment 2 Samuel Cormier-Iijima 2008-03-10 23:04:09 UTC
Created attachment 107023 [details] [review]
and one without debugging outputs
Comment 3 Matthias Clasen 2008-03-12 19:28:43 UTC
This was fixed in 2.16.1