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 563593 - crash in Computer: closing nautilus
crash in Computer: closing nautilus
Status: RESOLVED DUPLICATE of bug 480179
Product: nautilus
Classification: Core
Component: general
2.20.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
: 563660 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-12-07 20:32 UTC by bluewolf
Modified: 2008-12-08 21:19 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description bluewolf 2008-12-07 20:32:11 UTC 
Version: 2.20.0

What were you doing when the application crashed?
closing nautilus


Distribution: Debian 5.0
Gnome Release: 2.22.3 2008-09-18 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.26-1-686-bigmem #1 SMP Wed Nov 26 20:00:34 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks-DarkLime
Icon Theme: hydroxygen

Memory status: size: 360898560 vsize: 360898560 resident: 42631168 share: 31014912 rss: 42631168 rss_rlim: 4294967295
CPU usage: start_time: 1228681927 rtime: 242 utime: 195 stime: 47 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xb69fc9a0 (LWP 7971)]
0xb7f10424 in __kernel_vsyscall ()

+ Trace 210572

Thread 1 (Thread 0xb69fc9a0 (LWP 7971))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 IA__g_spawn_sync
    at /tmp/buildd/glib2.0-2.16.6/glib/gspawn.c line 374
  • #3 IA__g_spawn_command_line_sync
    at /tmp/buildd/glib2.0-2.16.6/glib/gspawn.c line 682
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #6 <signal handler called>
  • #7 gconf_client_remove_dir
    from /usr/lib/libgconf-2.so.4
  • #8 ??
    from /usr/lib/nautilus/extensions-1.0/libnautilus-actions.so
  • #9 ??
  • #10 ??
    from /usr/lib/nautilus/extensions-1.0/libnautilus-actions.so
  • #11 ??
  • #0 __kernel_vsyscall 


----------- .xsession-errors (22 sec old) ---------------------
Initializing nautilus-open-terminal extension
Initializing nautilus-image-converter extension
Initializing nautilus-share extension
Nautilus-Share-Message: REFRESHING SHARES
Nautilus-Share-Message: ------------------------------------------
Nautilus-Share-Message: spawn arg "net"
Nautilus-Share-Message: spawn arg "usershare"
Nautilus-Share-Message: spawn arg "info"
Nautilus-Share-Message: end of spawn args; SPAWNING
Nautilus-Share-Message: returned from spawn: SUCCESS: 
Nautilus-Share-Message: exit code 0
Nautilus-Share-Message: caller wants GKeyFile
Nautilus-Share-Message: success from calling net usershare and parsing its output
Nautilus-Share-Message: ------------------------------------------
--------------------------------------------------
Comment 1 Bruno Boaventura 2008-12-07 21:35:32 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 Sergio Infante Montero 2008-12-08 11:08:08 UTC 
*** Bug 563660 has been marked as a duplicate of this bug. ***
Comment 3 André Klapper 2008-12-08 21:19:43 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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