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 113059 - Nautilus crashed when closing
Nautilus crashed when closing
Status: RESOLVED DUPLICATE of bug 77331
Product: nautilus
Classification: Core
Component: general
2.2.x
Other Linux
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2003-05-15 13:07 UTC by Mick Wever
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.1/2.2



Description Mick Wever 2003-05-15 13:01:07 UTC
Package: nautilus
Severity: normal
Version: 2.0.6
Synopsis: Nautilus crashed when closing
Bugzilla-Product: nautilus
Bugzilla-Component: general
BugBuddy-GnomeVersion: 2.0 (2.0.3)

Description:
Description of Problem:
Closing one nautilus window caused crash.

Steps to reproduce the problem:
1. Close window via 'x' button.

Actual Results:
all nautilus windows hang & error dialog.

Expected Results:
no hang, no error :)

How often does this happen?
not reproducable.





Debugging Information:

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

(no debugging symbols found)...[New Thread 16384 (LWP 1380)]
[New Thread 32769 (LWP 1389)]
[New Thread 16386 (LWP 1390)]
[New Thread 32771 (LWP 1391)]
[New Thread 49156 (LWP 1392)]
[New Thread 65541 (LWP 1393)]
[New Thread 81926 (LWP 1394)]
[New Thread 98311 (LWP 1395)]
[New Thread 114696 (LWP 1396)]
[New Thread 131081 (LWP 1397)]
[New Thread 147466 (LWP 1398)]
0x408f583a in waitpid ()
   from /lib/i686/libpthread.so.0

Thread 1 (Thread 16384 (LWP 1380))

  • #0 waitpid
    from /lib/i686/libpthread.so.0
  • #1 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 __pthread_sighandler
    from /lib/i686/libpthread.so.0
  • #3 <signal handler called>
  • #4 g_list_prepend
    from /usr/lib/libglib-2.0.so.0
  • #5 directory_load_one
    at nautilus-directory-async.c line 987
  • #6 new_files_callback
    at nautilus-directory-async.c line 1503
  • #7 dispatch_get_file_info_callback
    from /usr/lib/libgnomevfs-2.so.0
  • #8 dispatch_job_callback
    from /usr/lib/libgnomevfs-2.so.0
  • #9 g_idle_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #10 g_main_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #11 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #12 g_main_context_iterate
    from /usr/lib/libglib-2.0.so.0
  • #13 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #14 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 main
  • #16 __libc_start_main
    from /lib/i686/libc.so.6
  • #0 waitpid
    from /lib/i686/libpthread.so.0




------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-05-15 09:01 -------

The original reporter (mick@machina.no) of this bug does not have an account here.
Reassigning to the exporter, unknown@bugzilla.gnome.org.
Reassigning to the default owner of the component, nautilus-maint@bugzilla.gnome.org.

Comment 1 Elijah Newren 2003-05-25 16:01:36 UTC
Can you also get this crash with nautilus version 2.2.x?
Comment 2 mck 2003-05-26 15:06:42 UTC
Sorry, I only have version 2.2.1 installed. Must not have noticed that
option in BugBuddy.
Comment 3 Elijah Newren 2003-05-26 18:26:59 UTC
Really?!?  This must be a bug with bug-buddy--it's supposed to
automatically obtain the version number if it can (and leave that
field blank if it can't).  Bug-buddy reported your nautilus version as
2.0.6.  So I need to file a bug-buddy report, I guess.  Just so I
don't look dumb, can you verify for me how you determined your
nautilus version?  Also, what distribution (and version) are you running?
Comment 4 mck 2003-05-27 13:00:43 UTC
RedHat 9 (upgraded from 8). 

$uname -a
Linux butterfly.machina.no 2.4.20-13.9 #1 Mon May 12 11:03:52 EDT 2003
i686 athlon i386 GNU/Linux

$nautilus --version
Gnome nautilus 2.2.1

Comment 5 mck 2003-05-27 14:55:28 UTC
I am using some new gnome-vfs-fam rpms.
See bug 111147
Comment 6 Elijah Newren 2003-05-28 03:16:41 UTC
Ok, well I'll email the bugsquad about how best to report a bug
against bug-buddy for this.  Meanwhile, I'm going to set
version->2.2.x, set severity->critical & priority->high (it's a
crasher), add GNOMEVER2.2 and bugsquad keywords, and reopen.
Comment 7 Elijah Newren 2003-05-28 03:17:03 UTC
...and mark as new.
Comment 8 mwehner 2003-09-26 10:18:50 UTC
This is a dup of bug 77331.

*** This bug has been marked as a duplicate of 77331 ***