GNOME Bugzilla – Bug 431043
nautilus loops on SIGSEGV when opening "#"
Last modified: 2008-03-14 10:32:33 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.
+ Trace 128795
Thread 47899527502704 (LWP 19678)
(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
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.
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!