Marking as new, setting priority->high, severity->critical,
version->2.4.x. Adding GNOMEVER2.4, GNOMEVER2.5, STACKTRACE keywords.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

As far as I can see, all dups of this are from GNOME 2.4- but given
the number of dups, Dave, Alex, could you take a look and verify that
it isn't also present in 2.6? Thanks.

Unfortunately none of the backtraces have debug information, so its
very hard to debug this. Also, all the crashes seem to be in an assert
of something like that, so there should be some output (maybe in
.Xsession-errors, or stdout) when this happens. Getting that might
also help.

I bet its hard to find dups of this that really have debug info in
them, since the crash really isn't in
nautilus_icon_container_move_icon. That is just the closest
non-private symbol before where the crash is, and unfortnately there
is about 1700 lines of code between nautilus_icon_container_move_icon
and the next public symbol.

The easiest way to get a good trace is if someone who can easily
reproduce this somehow installs debug info for eel and nautilus.

Ah, i know this one!

The real backtrace is something like:

+ Trace 44768

And the crash is at:

g_assert (GTK_IS_WINDOW (gtk_widget_get_toplevel (widget)));

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

Bug 119370 is the dup-head for the version with debug info. That
particular bug has a good backtrace. It also mentions that this bug
has similarities with bug 117931. They fail in different places, but
it looks like the core reason for it (there is no toplevel widget for
the view) is the same.

So, what seems to happen is:

externally to nautilus, a file is created. Nautilus picks up this, and
creates an icon for it. When showing the icon its not realized, so we
realize it, to realize it we also realize the parent widget (which was
unrealized), and realizing the nautilus-icon-view tries to set the
icon view as the focus widget of the window, but somehow the view
doesn't have a parent toplevel window.

Questions:
None of the bugs mention opening of new windows, just creation of new
files. Why isn't the icon view already realized? And why isn't it in a
 toplevel window?

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

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

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

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

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

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

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

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

Anyone object to closing this until we get a dup from 2.6? Alex, Dave, Martin?

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

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

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

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

No dups with Nautilus > 2.4, marking NEEDINFO for now.

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

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

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

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

I observed a crash with similar symptoms on GNOME-2.7 recently (i.e. Nautilus
crashed while a large number of files were added or deleted), but I have no
backtrace to show from it, and I can't confirm it is the same problem.

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

I close this bug.

No crash with 4000 files.

mkdir ~/Desktop/test -p
with nautilus : open the directory
After, I launch a python script to make the same thing and hope to get the same
bug. But nothing with 4000 files.

My script :  
#!/usr/bin/env python

import os,string

for i in range (1, 4000):
    fichier = open ("test%04d"%i, 'w')
    fichier.write("toto")
    fichier.close

Nautilus Version : 
stef@ubuntu:~/Desktop/test $ nautilus --version
Gnome nautilus 2.8.1
stef@ubuntu:~/Desktop/test $ 

I checked my script on another ubuntu "hoary" and I don't get this error .

Nautilus version on my hoary ubuntu : 2.9.90

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

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

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