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 585950 - crash in File Browser: Closing a Nautilus windo...
crash in File Browser: Closing a Nautilus windo...
Status: RESOLVED DUPLICATE of bug 584745
Product: nautilus
Classification: Core
Component: general
2.26.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-06-16 07:45 UTC by evoq70
Modified: 2009-06-16 20:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26


Attachments
Stack trace with debugging symbols. (8.70 KB, text/plain)
2009-06-16 17:05 UTC, evoq70
Details

Description evoq70 2009-06-16 07:45:35 UTC
Version: 2.26.2

What were you doing when the application crashed?
Closing a Nautilus window.


Distribution: Debian squeeze/sid
Gnome Release: 2.26.1 2009-04-14 (Debian)
BugBuddy Version: 2.26.0

System: Linux 2.6.26-2-686 #1 SMP Thu Mar 26 01:08:11 UTC 2009 i686
X Vendor: The X.Org Foundation
X Vendor Release: 60900000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Shiki-Wise
Icon Theme: Brit-Icons
GTK+ Modules: gnomebreakpad

Memory status: size: 84271104 vsize: 84271104 resident: 21913600 share: 17633280 rss: 21913600 rss_rlim: 18446744073709551615
CPU usage: start_time: 1245138258 rtime: 124 utime: 113 stime: 11 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6e7d760 (LWP 6305)]
[New Thread 0xb3711b90 (LWP 6313)]
[New Thread 0xb6a46b90 (LWP 6306)]
0xb7fdc424 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6e7d760 (LWP 6305))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 ??
  • #7 exit
    from /lib/i686/cmov/libc.so.6
  • #8 __libc_start_main
    from /lib/i686/cmov/libc.so.6
  • #9 ??
  • #0 __kernel_vsyscall


----------- .xsession-errors (36326 sec old) ---------------------
(nautilus:5854): Eel-WARNING **: "nautilus-metafile.c: metafiles" hash table still has 2 elements at quit time (keys above)
(nautilus:5854): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 2 elements at quit time
Shutting down nautilus-image-converter extension
Shutting down nautilus-gdu extension
Shutting down nautilus-open-terminal extension
Gtk-Message: (for origin information, set GTK_DEBUG): failed to retrieve property `GtkTreeView::odd-row-color' of type `GdkColor' from rc file value "((GString*) 0x93b00d0)" of type `GString'
Gtk-Message: (for origin information, set GTK_DEBUG): failed to retrieve property `GtkTreeView::odd-row-color' of type `GdkColor' from rc file value "((GString*) 0x84c49c0)" of type `GString'
OpenOffice path is '/usr/lib/openoffice'
Gtk-Message: (for origin information, set GTK_DEBUG): failed to retrieve property `GtkTreeView::odd-row-color' of type `GdkColor' from rc file value "((GString*) 0x96d8c20)" of type `GString'
** (gnome-panel:5718): WARNING **: Could not connect to session manager: Could not get owner of name 'org.gnome.SessionManager': no such name
** (gnome-panel:5718): WARNING **: Could not connect to session manager: Could not get owner of name 'org.gnome.SessionManager': no such name
--------------------------------------------------
Comment 1 A. Walton 2009-06-16 09:33:57 UTC
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 and reopen this bug or report a new one. Thanks in advance!
Comment 2 evoq70 2009-06-16 17:05:08 UTC
Created attachment 136748 [details]
Stack trace with debugging symbols.

As requested, I've reproduced the problem and have attached the stack trace. Cheers.
Comment 3 Fabio Durán Verdugo 2009-06-16 20:47:29 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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