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 431043 - nautilus loops on SIGSEGV when opening "#"
nautilus loops on SIGSEGV when opening "#"
Status: RESOLVED OBSOLETE
Product: nautilus
Classification: Core
Component: File and Folder Operations
2.18.x
Other All
: Normal critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-04-18 15:11 UTC by C de-Avillez
Modified: 2008-03-14 10:32 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description C de-Avillez 2007-04-18 15:11:02 UTC
Steps to reproduce:
1. Open Nautilus
2. Select Go/Location
3. enter '#' WITHOUT the quotes
4. infinite loop results.

Can also be triggered with "nautilus --no-desktop file:///#"


Stack trace:
hggdh@xango:~$ gdb --args nautilus --no-desktop file:///#
GNU gdb 6.6-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 "x86_64-linux-gnu"...
Using host libthread_db library "/lib/libthread_db.so.1".
(gdb) set print pretty
(gdb) set print array
(gdb) continue
The program is not being run.
(gdb) run
Starting program: /usr/bin/nautilus --no-desktop file:///\#
[Thread debugging using libthread_db enabled]
[New Thread 47899527502704 (LWP 19678)]
Initializing gnome-mount extension
seahorse nautilus module initialized
[New Thread 1082132800 (LWP 19699)]
[New Thread 1090525504 (LWP 19700)]
[New Thread 1098918208 (LWP 19701)]
[New Thread 1107310912 (LWP 19702)]
[New Thread 1115703616 (LWP 19703)]
[New Thread 1124096320 (LWP 19704)]
[New Thread 1132489024 (LWP 19705)]
[New Thread 1140881728 (LWP 19709)]
[New Thread 1149274432 (LWP 19710)]
[New Thread 1157667136 (LWP 19711)]
sys:1: Warning: g_filename_display_basename: assertion `filename != NULL' failed

** (nautilus:19678): CRITICAL **: nautilus_information_panel_set_uri: assertion `initial_title != NULL' failed
[Thread 1140881728 (LWP 19709) exited]
[Thread 1082132800 (LWP 19699) exited]
[Thread 1090525504 (LWP 19700) exited]
[Thread 1124096320 (LWP 19704) exited]
[Thread 1132489024 (LWP 19705) exited]
[Thread 1107310912 (LWP 19702) exited]
[Thread 1115703616 (LWP 19703) exited]
[Thread 1098918208 (LWP 19701) exited]
[Thread 1157667136 (LWP 19711) exited]
[Thread 1149274432 (LWP 19710) exited]
[New Thread 1149274432 (LWP 19715)]
[New Thread 1107310912 (LWP 19716)]
[New Thread 1124096320 (LWP 19717)]
[New Thread 1157667136 (LWP 19718)]

Program received signal SIGSEGV, Segmentation fault.

Thread 47899527502704 (LWP 19678)

  • #0 compare_by_display_name
    at nautilus-file.c line 1829
  • #1 nautilus_file_compare_for_sort
    at nautilus-file.c line 2182
  • #2 g_list_sort_real
    at glist.c line 583
  • #3 g_list_sort_real
    at glist.c line 629
  • #4 g_list_sort_real
    at glist.c line 629
  • #5 g_list_sort_real
    at glist.c line 629
  • #6 sort_files
    at fm-directory-view.c line 2689
  • #7 process_new_files
    at fm-directory-view.c line 2767
  • #8 done_loading_callback
    at fm-directory-view.c line 3175
  • #9 IA__g_closure_invoke
    at gclosure.c line 490
  • #10 signal_emit_unlocked_R
    at gsignal.c line 2440
  • #11 IA__g_signal_emit_valist
    at gsignal.c line 2199
  • #12 IA__g_signal_emit
    at gsignal.c line 2243
  • #13 dequeue_pending_idle_callback
    at nautilus-directory-async.c line 914
  • #14 directory_load_callback
    at nautilus-directory-async.c line 1041
  • #15 dispatch_job_callback
    at gnome-vfs-job.c line 237
  • #16 IA__g_main_context_dispatch
    at gmain.c line 2045
  • #17 g_main_context_iterate
    at gmain.c line 2677
  • #18 IA__g_main_loop_run
    at gmain.c line 2881
  • #19 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #20 main
    at nautilus-main.c line 548
(gdb) set print array
(gdb) print *file_1
$1 = {
  parent_slot = {
    g_type_instance = {
      g_class = 0xb76800
    }, 
    ref_count = 3, 
    qdata = 0x121fa00
  }, 
  details = 0x1224de0
}
(gdb) print *name_1
Cannot access memory at address 0x0
(gdb) print *file_2
$2 = {
  parent_slot = {
    g_type_instance = {
      g_class = 0xb76800
    }, 
    ref_count = 3, 
    qdata = 0x121f880
  }, 
  details = 0x121f020
}
(gdb) print *name_2
Cannot access memory at address 0x0
(gdb) continue
Continuing.
[Thread 1082132800 (LWP 21752) exited]
[Thread 1090525504 (LWP 21753) exited]
[Thread 1098918208 (LWP 21754) exited]
[Thread 1107310912 (LWP 21755) exited]
[Thread 1115703616 (LWP 21756) exited]

Program received signal SIGSEGV, Segmentation fault.
compare_by_display_name (file_1=0x1224dc0, file_2=0x121f000) at nautilus-file.c:1829
1829    in nautilus-file.c
(gdb) quit
The program is running.  Exit anyway? (y or n) y


Other information:
Ubuntu original Launchpad bug: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/107253
Comment 1 C de-Avillez 2008-03-11 09:38:19 UTC
Last update from downstream states that behaviour has changed, and now icons for '/' start to appear on the desktop.

After a while (one minute, per reporter) system stops responding, and needs to be rebooted.
Comment 2 Cosimo Cecchi 2008-03-14 10:32:33 UTC
This does not happen anymore with 2.22, (you get an error dialog saying "Couldn't display "#".". It might have been fixed in the transition from GnomeVFS to GIO during the 2.21 development cycle. Closing this report as OBSOLETE, please reopen it if you still find this bug with Nautilus >= 2.22, thanks!