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 436071 - Nautilus crashes when trying to execute '#'
Nautilus crashes when trying to execute '#'
Status: RESOLVED FIXED
Product: nautilus
Classification: Core
Component: general
2.18.x
Other other
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
: 445429 490615 492817 497366 498583 499365 502402 503988 504279 504285 514251 514747 514748 516145 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-05-05 09:51 UTC by Vincent Rivière
Modified: 2008-02-13 00:23 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Vincent Rivière 2007-05-05 09:51:51 UTC
Distribution: Debian lenny/sid
Package: nautilus
Severity: Normal
Version: GNOME2.14.3 2.14.3
Gnome-Distributor: Debian
Synopsis: Nautilus crashes when trying to execute '#'
Bugzilla-Product: nautilus
Bugzilla-Component: general
Bugzilla-Version: 2.14.3
BugBuddy-GnomeVersion: 2.0 (2.14.1)
Description:
Description of the crash:
Nautilus crashes when trying to execute '#' from the Execute dialog
box.

Steps to reproduce the crash:
1. Start a Gnome session
2. Type Ctrl+L
3. Type # and validate


Expected Results:
Error message and no crash.

How often does this happen?
Everytime

Additional Information:
If nautilus is started from konsole in a KDE session, additional
information printed on the console :
(nautilus:5115): GLib-CRITICAL **: g_filename_display_basename:
assertion `filename != NULL' failed



Debugging Information:

Backtrace was generated from '/usr/bin/nautilus'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1225693504 (LWP 5115)]
[New Thread -1227760720 (LWP 5118)]
(no debugging symbols found)
0xb7f21410 in ?? ()




------- Bug created by bug-buddy at 2007-05-05 09:51 -------


Unknown version 2.14.3 in product nautilus.  Setting version to "2.14.x".

Comment 1 Pedro Villavicencio 2007-05-05 13:58:53 UTC
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 2 Vincent Rivière 2007-05-07 15:49:07 UTC
I Hope this is better.
Run from KDE.

$ gdb --args nautilus
GNU gdb 6.4.90-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".

(gdb) r
Starting program: /usr/bin/nautilus
Failed to read a valid object file image from memory.
[Thread debugging using libthread_db enabled]
[New Thread -1225820480 (LWP 4473)]
[New Thread -1227822160 (LWP 4476)]
[New Thread -1232532560 (LWP 4484)]
[New Thread -1240925264 (LWP 4485)]
[New Thread -1249317968 (LWP 4486)]
[Thread -1232532560 (LWP 4484) exited]
[Thread -1240925264 (LWP 4485) exited]
[Thread -1249317968 (LWP 4486) exited]
[New Thread -1249317968 (LWP 4489)]
[Thread -1249317968 (LWP 4489) exited]
[New Thread -1249317968 (LWP 4490)]
[New Thread -1240925264 (LWP 4491)]

(nautilus:4473): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed

(nautilus:4473): Gtk-CRITICAL **: gtk_label_set_label: assertion `str != NULL' failed

(nautilus:4473): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed

(nautilus:4473): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed

(nautilus:4473): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed

(nautilus:4473): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed

Program received signal SIGSEGV, Segmentation fault.

Thread NaN (LWP 4473)

  • #0 compare_by_display_name
    at nautilus-file.c line 1806
  • #1 nautilus_file_compare_for_sort
    at nautilus-file.c line 2159
  • #2 fm_icon_view_compare_files
    at fm-icon-view.c line 2052
  • #3 compare_files
    at fm-icon-view.c line 2064
  • #4 compare_files_cover
    at fm-directory-view.c line 2670
  • #5 g_list_foreach
    from /usr/lib/libglib-2.0.so.0
  • #6 g_list_foreach
    from /usr/lib/libglib-2.0.so.0
  • #7 g_list_foreach
    from /usr/lib/libglib-2.0.so.0
  • #8 g_list_foreach
    from /usr/lib/libglib-2.0.so.0
  • #9 g_list_foreach
    from /usr/lib/libglib-2.0.so.0
  • #10 sort_files
    at fm-directory-view.c line 2677
  • #11 process_new_files
    at fm-directory-view.c line 2755
  • #12 done_loading_callback
    at fm-directory-view.c line 3143
  • #13 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #14 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #15 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #16 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #17 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #18 nautilus_directory_emit_done_loading
    at nautilus-directory.c line 776
  • #19 dequeue_pending_idle_callback
    at nautilus-directory-async.c line 902
  • #20 directory_load_callback
    at nautilus-directory-async.c line 1029
  • #21 gnome_vfs_job_get_count
    from /usr/lib/libgnomevfs-2.so.0
  • #22 ??
  • #23 ??
  • #24 ??
  • #25 ??
  • #26 ??
  • #27 ??
    from /usr/lib/libglib-2.0.so.0
  • #28 ??
  • #29 g_slice_alloc
    from /usr/lib/libglib-2.0.so.0
  • #30 g_source_is_destroyed
    from /usr/lib/libglib-2.0.so.0
  • #31 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #32 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #33 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #34 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #35 main
    at nautilus-main.c line 406
  • #36 __libc_start_main
    from /lib/tls/i686/cmov/libc.so.6
  • #37 _start
    at ../sysdeps/i386/elf/start.S line 119

Comment 3 Christian Kirbach 2007-05-07 20:36:00 UTC
It is not the "execute" dialog, it is the location bar. known bug.

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 324365 ***
Comment 4 André Klapper 2007-08-22 19:38:33 UTC
nazgul, sure with marking it as a dup? the stacktraces are totally different to me
Comment 5 André Klapper 2007-08-22 19:43:20 UTC
*** Bug 445429 has been marked as a duplicate of this bug. ***
Comment 6 Christian Kirbach 2007-08-22 22:15:54 UTC
The traces differ, but so do the Gnome versions.


Given the number of dups in Bug 445429 that at least some are with 2.18 I will unduplicate

relevant trace of last mentioned bug

  • #3 <signal handler called>
  • #4 compare_by_display_name
    at nautilus-file.c line 1828
  • #5 nautilus_file_compare_for_sort
    at nautilus-file.c line 2181
  • #6 fm_icon_view_compare_files
    at fm-icon-view.c line 2044
  • #7 compare_files
    at fm-icon-view.c line 2056
  • #8 compare_files_cover
    at fm-directory-view.c line 2681
  • #9 g_list_sort_real
    at glist.c line 583
  • #10 g_list_sort_real
    at glist.c line 629
  • #11 g_list_sort_real
    at glist.c line 629
  • #12 g_list_sort_real
    at glist.c line 629
  • #13 g_list_sort_real
    at glist.c line 629
  • #14 sort_files
    at fm-directory-view.c line 2688
  • #15 process_new_files
    at fm-directory-view.c line 2766
  • #16 done_loading_callback
    at fm-directory-view.c line 3174
  • #17 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #18 IA__g_closure_invoke
    at gclosure.c line 490

Comment 7 Christian Kirbach 2007-08-22 22:16:41 UTC
IN Ubuntu I get a hang with 2.18.1 but we have quite some duplicates, thus confirming
Comment 8 André Klapper 2007-08-22 22:30:13 UTC
28 dups total, 25 in the last 30 days. not yet a gnome blocker, but on a good way...
Comment 9 Sebastien Bacher 2007-08-23 09:58:20 UTC
duplicate of bug #324365?
Comment 10 Alexander Larsson 2007-08-24 11:53:43 UTC
Fixed the crash in svn.
Comment 11 Bruno Boaventura 2007-10-27 11:17:50 UTC
*** Bug 490615 has been marked as a duplicate of this bug. ***
Comment 12 Christoph Wolk 2007-11-03 01:38:27 UTC
*** Bug 492817 has been marked as a duplicate of this bug. ***
Comment 13 palfrey 2007-11-16 16:13:49 UTC
*** Bug 497366 has been marked as a duplicate of this bug. ***
Comment 14 Susana 2007-11-24 18:39:51 UTC
*** Bug 499365 has been marked as a duplicate of this bug. ***
Comment 15 Susana 2007-11-24 18:40:04 UTC
*** Bug 498583 has been marked as a duplicate of this bug. ***
Comment 16 Cosimo Cecchi 2007-12-10 14:04:18 UTC
*** Bug 502402 has been marked as a duplicate of this bug. ***
Comment 17 André Klapper 2007-12-17 12:21:57 UTC
*** Bug 503988 has been marked as a duplicate of this bug. ***
Comment 18 Susana 2007-12-18 22:38:01 UTC
*** Bug 504279 has been marked as a duplicate of this bug. ***
Comment 19 Susana 2007-12-18 22:38:11 UTC
*** Bug 504285 has been marked as a duplicate of this bug. ***
Comment 20 Cosimo Cecchi 2008-02-04 13:21:32 UTC
*** Bug 514251 has been marked as a duplicate of this bug. ***
Comment 21 Gianluca Borello 2008-02-07 09:21:35 UTC
*** Bug 514747 has been marked as a duplicate of this bug. ***
Comment 22 Gianluca Borello 2008-02-07 09:21:43 UTC
*** Bug 514748 has been marked as a duplicate of this bug. ***
Comment 23 Cosimo Cecchi 2008-02-13 00:23:42 UTC
*** Bug 516145 has been marked as a duplicate of this bug. ***