GNOME Bugzilla – Bug 436071
Nautilus crashes when trying to execute '#'
Last modified: 2008-02-13 00:23:42 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 ?? ()
+ Trace 132520
------- 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".
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!
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.
+ Trace 132911
Thread NaN (LWP 4473)
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 ***
nazgul, sure with marking it as a dup? the stacktraces are totally different to me
*** Bug 445429 has been marked as a duplicate of this bug. ***
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
+ Trace 157226
IN Ubuntu I get a hang with 2.18.1 but we have quite some duplicates, thus confirming
28 dups total, 25 in the last 30 days. not yet a gnome blocker, but on a good way...
duplicate of bug #324365?
Fixed the crash in svn.
*** Bug 490615 has been marked as a duplicate of this bug. ***
*** Bug 492817 has been marked as a duplicate of this bug. ***
*** Bug 497366 has been marked as a duplicate of this bug. ***
*** Bug 499365 has been marked as a duplicate of this bug. ***
*** Bug 498583 has been marked as a duplicate of this bug. ***
*** Bug 502402 has been marked as a duplicate of this bug. ***
*** Bug 503988 has been marked as a duplicate of this bug. ***
*** Bug 504279 has been marked as a duplicate of this bug. ***
*** Bug 504285 has been marked as a duplicate of this bug. ***
*** Bug 514251 has been marked as a duplicate of this bug. ***
*** Bug 514747 has been marked as a duplicate of this bug. ***
*** Bug 514748 has been marked as a duplicate of this bug. ***
*** Bug 516145 has been marked as a duplicate of this bug. ***