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 530491 - crash in Open Folder:
crash in Open Folder:
Status: RESOLVED DUPLICATE of bug 508751
Product: nautilus
Classification: Core
Component: general
2.20.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-04-29 05:35 UTC by Paul Rawson
Modified: 2008-04-29 07:14 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description Paul Rawson 2008-04-29 05:35:54 UTC
Version: 2.20.0

What were you doing when the application crashed?



Distribution: Gentoo Base System release 2.0.0
Gnome Release: 2.20.3 2008-02-03 (Gentoo)
BugBuddy Version: 2.20.1

System: Linux 2.6.24-gentoo-r3 #11 SMP PREEMPT Thu Apr 24 03:57:09 PDT 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 78741504 vsize: 78741504 resident: 24317952 share: 14045184 rss: 24317952 rss_rlim: 4294967295
CPU usage: start_time: 1209447304 rtime: 97 utime: 90 stime: 7 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb76446c0 (LWP 12886)]
0xb7f47410 in __kernel_vsyscall ()

Thread 1 (Thread 0xb76446c0 (LWP 12886))

  • #0 __kernel_vsyscall
  • #1 waitpid
    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 google_breakpad::ExceptionHandler::InternalWriteMinidump
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #7 google_breakpad::ExceptionHandler::HandleException
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #8 <signal handler called>
  • #9 _gdk_keymap_key_is_modifier
    from /usr/lib/libgdk-x11-2.0.so.0
  • #10 translate_key_event
    from /usr/lib/libgdk-x11-2.0.so.0
  • #11 gdk_event_translate
    from /usr/lib/libgdk-x11-2.0.so.0
  • #12 _gdk_events_queue
    from /usr/lib/libgdk-x11-2.0.so.0
  • #13 gdk_event_dispatch
    from /usr/lib/libgdk-x11-2.0.so.0
  • #14 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #15 g_main_context_iterate
    from /usr/lib/libglib-2.0.so.0
  • #16 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #17 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #18 main
  • #19 __libc_start_main
    from /lib/libc.so.6
  • #20 _start
  • #0 __kernel_vsyscall


----------- .xsession-errors (1878 sec old) ---------------------
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
gecko: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3200003 (Evince Doc)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
gecko: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
firefox-bin exited with non-zero status (1)
/opt/vmware/workstation/lib/bin/vmware: /opt/vmware/workstation/lib/lib/libpng12.so.0/libpng12.so.0: no version information available (required by /usr/lib/libcairo.so.2)
using /home/plrca2/.azureus/gentoo.config
/usr/bin/azureus: line 72: /dev/stderr: Permission denied
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-04-29 07:14:38 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 508751 ***