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 131861 - Holding down F2 and clicking on desktop, having objects selected crashes nautilus
Holding down F2 and clicking on desktop, having objects selected crashes naut...
Status: RESOLVED FIXED
Product: nautilus
Classification: Core
Component: File and Folder Operations
2.5.x
Other Linux
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
: 130928 135631 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2004-01-18 20:26 UTC by Sven Arvidsson
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Entire 2.5.x stack trace (somewhat long) (65.02 KB, text/plain)
2004-01-19 02:28 UTC, Elijah Newren 		Details

Description Sven Arvidsson 2004-01-18 20:26:52 UTC 
If you select a file, shortcut etc. and try to rename it using the F2 key
but change your mind and abort by clicking somewhere else, nautilus segfaults.

Steps to reproduce:

1. Select object.
2. Hold down F2 key.
3. Click somewhere else (desktop).
4. Nautilus crashes. (Segmentation fault)
Comment 1 Elijah Newren 2004-01-19 02:22:30 UTC 
I was able to reproduce, but it took me a while.  Basically I opened a
nautilus window for my home directory, selected the file, held down F2
while clicking several times in totally different locations.  I've
duplicated this both under nautilus-2.4.x (a vanilla Fedora 1 install)
and under nautilus-2.5.x (from CVS head about a month or so ago).  The
two stack traces look different to me, but the interesting thing is
that the 2.5 trace looks like bug 75817/bug 75076 (closed long ago due
to not being able to reproduce though it showed up multiple times). 
I'll cut and paste both the traces here.  First, I'll cut & paste the
2.4 trace (sorry, no debugging symbols in this one):

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

(no debugging symbols found)...Using host libthread_db library
"/lib/tls/libthread_db.so.1".
(no debugging symbols found)...
<snip>
(no debugging symbols found)...[Thread debugging using libthread_db
enabled]
[New Thread -1084577920 (LWP 25394)]
[New Thread -1090286672 (LWP 1001)]
[New Thread -1090020432 (LWP 1000)]
[New Thread -1087239248 (LWP 25429)]
[New Thread -1086973008 (LWP 25428)]
[New Thread -1086706768 (LWP 25427)]
(no debugging symbols found)...
<snip>
(no debugging symbols found)...(no debugging symbols found)...
0x00bdcc32 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2

+ Trace 43330

  • #0 _dl_sysinfo_int80
    from /lib/ld-linux.so.2
  • #1 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 fm_directory_view_get_directory_as_file
  • #5 bonobo_socket_add_id
    from /usr/lib/libbonoboui-2.so.0
  • #6 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #7 bonobo_closure_invoke_va_list
    from /usr/lib/libbonobo-2.so.0
  • #8 bonobo_closure_invoke
    from /usr/lib/libbonobo-2.so.0
  • #9 ??
  • #10 ??
  • #11 ??
    from /usr/lib/libgobject-2.0.so.0
  • #12 ??
  • #13 ??
  • #14 ??
  • #15 ??
    from /usr/lib/libgobject-2.0.so.0
  • #16 ??
  • #17 ??
  • #18 ??
  • #19 g_closure_unref
    from /usr/lib/libgobject-2.0.so.0 






Comment 2


Elijah Newren





          2004-01-19 02:27:53 UTC
        



The 2.5.x stacktrace is huge, so I'm going to attach it.  I'll still
cut-and-paste part of it here so that the simple-dup-finder can pick
up on it.

Backtrace was generated from '/opt/gnome2/bin/nautilus'
...




+
Trace
    43332






    

  • 
#0
_dl_sysinfo_int80

    
                from
                /lib/ld-linux.so.2

    

    • 

  • 
#1
__waitpid_nocancel

    
                from
                /lib/tls/libpthread.so.0

    

    • 

  • 
#2
libgnomeui_segv_handle

    
                at gnome-ui-init.c
                  line
                  738

    

    • 

  • 
#3
<signal handler called>

    • 

  • 
#4
rename_file_callback

    
                at fm-directory-view.c
                  line
                  5144

    

    • 

  • 
#5
marshal_VOID__USER_DATA_STRING

    
                at bonobo-ui-component.c
                  line
                  221

    

    • 

  • 
#6
g_closure_invoke

    
                at gclosure.c
                  line
                  437

    

    • 

  • 
#7
bonobo_closure_invoke_va_list

    
                at bonobo-types.c
                  line
                  415

    

    • 

  • 
#8
bonobo_closure_invoke

    
                at bonobo-types.c
                  line
                  478

    

    • 

  • 
#9
impl_Bonobo_UIComponent_execVerb

    
                at bonobo-ui-component.c
                  line
                  158

    

    • 

  • 
#10
_ORBIT_skel_small_Bonobo_UIComponent_execVerb

    
                at Bonobo-common.c
                  line
                  1196

    

    • 

  • 
#11
ORBit_c_stub_invoke

    
                at poa.c
                  line
                  2584

    

    • 

  • 
#12
Bonobo_UIComponent_execVerb

    
                at Bonobo-stubs.c
                  line
                  1227

    

    • 

  • 
#13
real_exec_verb

    • 













Comment 3


Elijah Newren





          2004-01-19 02:28:56 UTC
        



Created attachment 23506 [details]
Entire 2.5.x stack trace (somewhat long)






Comment 4


Martin Wehner





          2004-01-23 02:01:33 UTC
        



*** Bug 130928 has been marked as a duplicate of this bug. ***






Comment 5


Martin Wehner





          2004-02-06 21:39:24 UTC
        



I've commited a fix to both branches today: rename_file_callback()
wasn't checking if the selection is still valid, so it crashed over a
null pointer when one unselects quickly after starting a rename.






Comment 6


Matthew Gatto





          2004-03-04 03:32:29 UTC
        



*** Bug 135631 has been marked as a duplicate of this bug. ***