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 556366 - crash in File Browser: I was starting Firefox
crash in File Browser: I was starting Firefox
Status: RESOLVED DUPLICATE of bug 480179
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-10-15 05:46 UTC by rcanseco
Modified: 2008-10-16 09:25 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description rcanseco 2008-10-15 05:46:32 UTC 
Version: 2.22.5.1

What were you doing when the application crashed?
I was starting Firefox


Distribution: Ubuntu 8.04 (hardy)
Gnome Release: 2.22.3 2008-07-09 (Ubuntu)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-18-generic #1 SMP Wed May 28 20:27:26 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glossy
Icon Theme: gnome

Memory status: size: 259391488 vsize: 259391488 resident: 193732608 share: 17104896 rss: 193732608 rss_rlim: 4294967295
CPU usage: start_time: 1224047766 rtime: 17085 utime: 14220 stime: 2865 cutime:4976 cstime: 462 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xb6b8f720 (LWP 9960)]
[New Thread 0xb4a51b90 (LWP 9972)]
0xb7fcf410 in __kernel_vsyscall ()

+ Trace 208204

Thread 1 (Thread 0xb6b8f720 (LWP 9960))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/tls/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 gconf_client_remove_dir
    from /usr/lib/libgconf-2.so.4
  • #7 ??
    from /usr/lib/nautilus/extensions-2.0/libnautilus-actions.so
  • #8 g_object_unref
    from /usr/lib/libgobject-2.0.so.0
  • #9 ??
    from /usr/lib/nautilus/extensions-2.0/libnautilus-actions.so
  • #10 g_object_unref
    from /usr/lib/libgobject-2.0.so.0
  • #11 free_module_objects
    at nautilus-module.c line 219
  • #12 eel_debug_shut_down
    from /usr/lib/libeel-2.so.2
  • #13 main
    at nautilus-main.c line 578
  • #0 __kernel_vsyscall 


----------- .xsession-errors ---------------------
Remember to register some spam and ham messages before you
use bogofilter to evaluate mail for its probable spam status!
Can't open file 'wordlist.db' in directory '/home/rodrigo/.bogofilter'.
error #2 - No such file or directory.
Remember to register some spam and ham messages before you
use bogofilter to evaluate mail for its probable spam status!
Can't open file 'wordlist.db' in directory '/home/rodrigo/.bogofilter'.
error #2 - No such file or directory.
Remember to register some spam and ham messages before you
use bogofilter to evaluate mail for its probable spam status!
Cannot access memory at address 0x0
Cannot access memory at address 0x0
--------------------------------------------------
Comment 1 André Klapper 2008-10-16 09:25:34 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 ***