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 511290 - crash in Open Folder: told it to open a new fo...
crash in Open Folder: told it to open a new fo...
Status: RESOLVED DUPLICATE of bug 355018
Product: nautilus
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
: 511292 511293 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-01-22 16:23 UTC by mkohn
Modified: 2008-01-25 13:59 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description mkohn 2008-01-22 16:23:05 UTC 
Version: 2.18.3

What were you doing when the application crashed?
told it to open a new folder and getting the permissions for it


Distribution: Gentoo Base System release 1.12.9
Gnome Release: 2.20.1 2008-01-18 (Gentoo)
BugBuddy Version: 2.18.1

System: Linux 2.6.23-gentoo #3 SMP Fri Jan 18 15:21:55 EST 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Gonxical
Icon Theme: Neu

Memory status: size: 273657856 vsize: 273657856 resident: 34562048 share: 21594112 rss: 34562048 rss_rlim: 18446744073709551615
CPU usage: start_time: 1200942901 rtime: 707 utime: 660 stime: 47 cutime:0 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
0x00002b6b17748a1f in waitpid () from /lib/libpthread.so.0

+ Trace 186343

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 ??
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 strcmp
    from /lib/libc.so.6
  • #4 ??
  • #5 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #6 ??
    from /usr/lib/libgobject-2.0.so.0
  • #7 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #8 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #9 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #10 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #11 ??
    from /usr/lib/libgobject-2.0.so.0
  • #12 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #13 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #14 gtk_list_store_remove
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 gtk_list_store_clear
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 ??
  • #17 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #18 ??
    from /usr/lib/libgobject-2.0.so.0
  • #19 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #20 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #21 nautilus_file_emit_changed
  • #22 nautilus_directory_emit_change_signals
  • #23 nautilus_file_changed
  • #24 ??
  • #25 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #26 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #27 ??
    from /usr/lib/libglib-2.0.so.0
  • #28 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #29 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #30 main 


----------- .xsession-errors ---------------------
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7fff993fd000
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-01-23 10:26:37 UTC 
*** Bug 511292 has been marked as a duplicate of this bug. ***
Comment 2 Cosimo Cecchi 2008-01-23 10:26:47 UTC 
*** Bug 511293 has been marked as a duplicate of this bug. ***
Comment 3 Cosimo Cecchi 2008-01-25 13:59:27 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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