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 118135 - Closing and opening properties while select custom icon is open segfaults Nautilus
Closing and opening properties while select custom icon is open segfaults Nau...
Status: RESOLVED FIXED
Product: nautilus
Classification: Core
Component: File and Folder Operations
2.3.x
Other Linux
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2003-07-23 18:14 UTC by Chris Altmann
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Patch for this bug. Also posted to list (1.54 KB, patch)
2003-07-24 19:01 UTC, Chris Altmann 		none Details | Review
ChangeLog entry for this patch (798 bytes, patch)
2003-07-25 18:55 UTC, Chris Altmann 		none Details | Review

Description Chris Altmann 2003-07-23 18:12:47 UTC 
Distribution: Red Hat Linux release 8.0 (Psyche)
Package: nautilus
Severity: normal
Version: GNOME2.3.4 2.3.7
Gnome-Distributor: GNOME.Org
Synopsis: Closing and opening properties while select custom icon is open segfaults Nautilus
Bugzilla-Product: nautilus
Bugzilla-Component: general
Bugzilla-Version: 2.3.7
BugBuddy-GnomeVersion: 2.0 (2.3.3.1)
Description:
Description of the crash:
Closing and opening the properties dialog for a file while the "select
custom icon" dialog is open segfaults Nautilus. It only seems to happen
the first few times after a fresh startup of GNOME


Steps to reproduce the crash:
0. Start GNOME, open a nautilus window with files in it
1. Open a properties dialog for a file
2. Click "select custom icon" button
3. Close the properties dialog
4. Open another properties dialog on the same file
5. Click OK in the "select custom icon" dialog
6. Segfault

Expected Results:
Not segfault. Expected application of custom icon.

How often does this happen?
Happens at least once after a fresh startup of GNOME

Additional Information:



Debugging Information:

Backtrace was generated from '/opt/gnome23cvs/bin/nautilus'

[New Thread 8192 (LWP 14411)]
[New Thread 16385 (LWP 14412)]
[New Thread 8194 (LWP 14413)]
[New Thread 16387 (LWP 14414)]
[New Thread 24580 (LWP 14427)]
0x420ae169 in wait4 () from /lib/i686/libc.so.6

+ Trace 38963

Thread 1 (Thread 8192 (LWP 14411))

  • #0 wait4
    from /lib/i686/libc.so.6
  • #1 __DTOR_END__
    from /lib/i686/libc.so.6
  • #2 waitpid
    from /lib/i686/libpthread.so.0
  • #3 libgnomeui_segv_handle
    at gnome-ui-init.c line 738
  • #4 __pthread_sighandler
    from /lib/i686/libpthread.so.0
  • #5 <signal handler called>
  • #6 set_icon_callback
    at fm-properties-window.c line 3714
  • #7 icon_selected
    at eel-gnome-extensions.c line 290
  • #8 g_cclosure_marshal_VOID__INT
    at gmarshal.c line 216
  • #9 g_closure_invoke
    at gclosure.c line 437
  • #10 signal_emit_unlocked_R
    at gsignal.c line 2822
  • #11 g_signal_emit_valist
    at gsignal.c line 2554
  • #12 g_signal_emit
    at gsignal.c line 2612
  • #13 gtk_dialog_response
    at gtkdialog.c line 826
  • #14 action_widget_activated
    at gtkdialog.c line 533
  • #15 g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #16 g_closure_invoke
    at gclosure.c line 437
  • #17 signal_emit_unlocked_R
    at gsignal.c line 2822
  • #18 g_signal_emit_valist
    at gsignal.c line 2554
  • #19 g_signal_emit
    at gsignal.c line 2612
  • #20 gtk_button_clicked
    at gtkbutton.c line 555
  • #21 gtk_real_button_released
    at gtkbutton.c line 1044
  • #22 g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #23 g_type_class_meta_marshal
    at gclosure.c line 514
  • #24 g_closure_invoke
    at gclosure.c line 437
  • #25 signal_emit_unlocked_R
    at gsignal.c line 2752
  • #26 g_signal_emit_valist
    at gsignal.c line 2554
  • #27 g_signal_emit
    at gsignal.c line 2612
  • #28 gtk_button_released
    at gtkbutton.c line 547
  • #29 gtk_button_button_release
    at gtkbutton.c line 960
  • #30 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 82
  • #31 g_type_class_meta_marshal
    at gclosure.c line 514
  • #32 g_closure_invoke
    at gclosure.c line 437
  • #33 signal_emit_unlocked_R
    at gsignal.c line 2860
  • #34 g_signal_emit_valist
    at gsignal.c line 2564
  • #35 g_signal_emit
    at gsignal.c line 2612
  • #36 gtk_widget_event_internal
    at gtkwidget.c line 3269
  • #37 gtk_propagate_event
    at gtkmain.c line 2268
  • #38 gtk_main_do_event
    at gtkmain.c line 1503
  • #39 gdk_event_dispatch
    at gdkevents-x11.c line 2064
  • #40 g_main_dispatch
    at gmain.c line 1721
  • #41 g_main_context_dispatch
    at gmain.c line 2269
  • #42 g_main_context_iterate
    at gmain.c line 2350
  • #43 g_main_loop_run
    at gmain.c line 2570
  • #44 gtk_main
    at gtkmain.c line 1093
  • #45 main
    at nautilus-main.c line 280
  • #46 __libc_start_main
    from /lib/i686/libc.so.6
  • #0 wait4
    from /lib/i686/libc.so.6 




------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-07-23 14:12 -------

Unknown version 2.3.7 in product nautilus. Setting version to the default, "unspecified".
Reassigning to the default owner of the component, nautilus-maint@bugzilla.gnome.org.
Comment 1 Chris Altmann 2003-07-24 19:01:57 UTC 
Created attachment 18574 [details] [review]
Patch for this bug. Also posted to list
Comment 2 Chris Altmann 2003-07-25 18:55:54 UTC 
Created attachment 18606 [details] [review]
ChangeLog entry for this patch
Comment 3 Elijah Newren 2003-07-25 21:33:51 UTC 
Appears to be a unique stack trace as well.  I'm setting priority to
high because of the patch, adding the STACKTRACE (due to the debugging
symbols) and bugsquad keywords, and marking as new.
Comment 4 Dave Camp 2003-08-03 16:54:08 UTC 
patch applied, thanks