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 558290 - crash in Open Folder: trying to empty the tras...
crash in Open Folder: trying to empty the tras...
Status: RESOLVED DUPLICATE of bug 480179
Product: nautilus
Classification: Core
Component: general
2.24.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-10-28 19:51 UTC by lornebeswick
Modified: 2008-10-28 19:53 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24



Description lornebeswick 2008-10-28 19:51:23 UTC
Version: 2.24.1

What were you doing when the application crashed?
trying to empty the trash. it had like 7GB in it from an accidentally copied and pasted backup of something.


Distribution: Unknown
Gnome Release: 2.24.1 2008-10-25 (Archlinux)
BugBuddy Version: 2.24.1

System: Linux 2.6.27-ARCH #1 SMP PREEMPT Sun Oct 26 10:36:46 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: ClearlooksClassic
Icon Theme: gnome

Memory status: size: 40050688 vsize: 40050688 resident: 16236544 share: 12349440 rss: 16236544 rss_rlim: 18446744073709551615
CPU usage: start_time: 1225224742 rtime: 25 utime: 20 stime: 5 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 0xb69c6930 (LWP 7150)]
0xb7f19424 in __kernel_vsyscall ()

Thread 1 (Thread 0xb69c6930 (LWP 7150))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/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 run_bug_buddy
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 check_if_gdb
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #6 bugbuddy_segv_handle
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #7 <signal handler called>
  • #8 gconf_client_remove_dir
    from /usr/lib/libgconf-2.so.4
  • #9 nautilus_actions_config_gconf_reader_finalize
    from /usr/lib/nautilus/extensions-2.0/libnautilus-actions.so
  • #10 g_object_unref
    from /usr/lib/libgobject-2.0.so.0
  • #11 nautilus_actions_instance_dispose
    from /usr/lib/nautilus/extensions-2.0/libnautilus-actions.so
  • #12 g_object_unref
    from /usr/lib/libgobject-2.0.so.0
  • #13 free_module_objects
  • #14 eel_debug_shut_down
    from /usr/lib/libeel-2.so.2
  • #15 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (24267 sec old) ---------------------
fixme:wininet:InternetGetConnectedState always returning LAN connection.
fixme:wininet:InternetGetConnectedState always returning LAN connection.
fixme:wininet:InternetGetConnectedState always returning LAN connection.
fixme:wininet:InternetGetConnectedState always returning LAN connection.
fixme:wininet:InternetGetConnectedState always returning LAN connection.
fixme:wininet:InternetGetConnectedState always returning LAN connection.
fixme:wininet:InternetGetConnectedState always returning LAN connection.
fixme:wininet:InternetGetConnectedState always returning LAN connection.
fixme:wininet:InternetGetConnectedState always returning LAN connection.
fixme:wininet:InternetGetConnectedState always returning LAN connection.
fixme:wininet:InternetGetConnectedState always returning LAN connection.
fixme:wininet:InternetGetConnectedState always returning LAN connection.
fixme:wininet:InternetGetConnectedState always returning LAN connection.
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 A. Walton 2008-10-28 19:53:12 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 ***