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 131963 - Reproducible crash after closing last of few spatial-mode windows
Reproducible crash after closing last of few spatial-mode windows
Status: RESOLVED DUPLICATE of bug 117579
Product: gtk+
Classification: Platform
Component: .General
2.3.x
Other Linux
: High critical
: ---
Assigned To: gtk-bugs
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-01-19 22:55 UTC by alexander.winston
Modified: 2005-08-15 01:50 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description alexander.winston 2004-01-19 22:55:53 UTC
Distribution: Debian testing/unstable
Package: nautilus
Severity: normal
Version: GNOME
      2
   .
      5
   .
      2
    2.5.4
Gnome-Distributor: 
      GARNOME
   
Synopsis: Reproducible crash after closing last of few spatial-mode windows
Bugzilla-Product: nautilus
Bugzilla-Component: general
Bugzilla-Version: 2.5.4
BugBuddy-GnomeVersion: 2.0 (2.5.2)
Description:
Description of the crash:
After opening a handful of spatial-mode Nautilus windows, I began to
close each one of them individually within a matter of two or three
seconds. After closing the last window, Nautilus crashed and Bug Buddy
appeared. I was using Metacity as my window manager.

Steps to reproduce the crash:
1. Double-click on Computer.
2. Traverse the file system about three folders or so down.
3. Close each window, one by one.

Expected Results:
Closure without incident. :)

How often does this happen?
Almost everytime that I close the last window in a group of several.

Additional Information:
I am running Debian GNU/Linux Sid (Unstable) as of 2004-01-19 together
with Garnome 0.29.1 compiled on 2004-01-19 with CFLAGS="-ggdb3 -O0
-pipe".


Debugging Information:

Backtrace was generated from '/home/aew/garnome/bin/nautilus'

[New Thread 1091137888 (LWP 2919)]
[New Thread 1105329104 (LWP 2925)]
[New Thread 1091137888 (LWP 2919)]
[New Thread 1105329104 (LWP 2925)]
[New Thread 1091137888 (LWP 2919)]
[New Thread 1105329104 (LWP 2925)]
[New Thread 1104055248 (LWP 2924)]
[New Thread 1102891984 (LWP 2923)]
[New Thread 1102629840 (LWP 2922)]
[New Thread 1102367696 (LWP 2921)]
[New Thread 1102105552 (LWP 2920)]
0x40cc4331 in __waitpid_nocancel () from /lib/tls/libpthread.so.0

Thread 1 (Thread 1091137888 (LWP 2919))

  • #0 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #1 libgnomeui_segv_handle
    at gnome-ui-init.c line 738
  • #2 <signal handler called>
  • #3 gdk_event_translate
    at gdkevents-x11.c line 822
  • #4 _gdk_events_queue
    at gdkevents-x11.c line 2028
  • #5 gdk_event_dispatch
    at gdkevents-x11.c line 2088
  • #6 g_main_dispatch
    at gmain.c line 1752
  • #7 g_main_context_dispatch
    at gmain.c line 2300
  • #8 g_main_context_iterate
    at gmain.c line 2381
  • #9 g_main_loop_run
    at gmain.c line 2601
  • #10 gtk_main
    at gtkmain.c line 1158
  • #11 main
    at nautilus-main.c line 328
  • #0 __waitpid_nocancel
    from /lib/tls/libpthread.so.0

Comment 1 alexander.winston 2004-01-19 22:58:02 UTC
Bumping priority to High and adding the exact version number.
Comment 2 Matthew Gatto 2004-01-20 05:39:04 UTC
probably a dup of bug 117579 since the fix for that bug didnt get into
GNOME-2.5.2, but ill reassign to gtk+ dudes let them decide
Comment 3 Soren Sandmann Pedersen 2004-01-20 19:26:14 UTC

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