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 536145 - crash in Open Folder:
crash in Open Folder:
Status: RESOLVED DUPLICATE of bug 522534
Product: nautilus
Classification: Core
Component: general
2.20.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-06-02 00:52 UTC by fbny71
Modified: 2008-06-02 09:29 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description fbny71 2008-06-02 00:52:06 UTC 
Version: 2.20.0

What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.22.2 2008-05-29 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.25-2-powerpc #1 Tue May 27 17:07:13 UTC 2008 ppc
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 71933952 vsize: 71933952 resident: 26443776 share: 17580032 rss: 26443776 rss_rlim: 4294967295
CPU usage: start_time: 1212366050 rtime: 1727 utime: 1582 stime: 145 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x48041160 (LWP 9036)]
(no debugging symbols found)
0x0ec48290 in waitpid () from /lib/libpthread.so.0

+ Trace 199358

Thread 1 (Thread 0x48041160 (LWP 9036))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #2 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 ??
  • #5 <signal handler called>
  • #6 ??
  • #7 ??
  • #8 ??
    from /usr/lib/libglib-2.0.so.0
  • #9 ??
  • #10 ??
  • #11 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #12 ??
    from /usr/lib/libglib-2.0.so.0
  • #13 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #14 ??
    from /usr/lib/libglib-2.0.so.0
  • #15 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #16 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #17 ??
  • #18 ??
    from /lib/libc.so.6
  • #19 __libc_start_main
    from /lib/libc.so.6
  • #20 ??
  • #0 waitpid
    from /lib/libpthread.so.0 


----------- .xsession-errors (142 sec old) ---------------------
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
seahorse nautilus module initialized
Initializing gnome-mount extension
Window manager warning: last_user_time (251924676) is greater than comparison timestamp (2619304).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_AC
Window manager warning: 0x1c00081 (Synaptic) appears to be one of the offending windows with a timestamp of 251924676.  Working around...

(synaptic:9074): Gtk-CRITICAL **: gtk_tree_view_unref_tree_helper: assertion `node != NULL' failed
seahorse nautilus module initialized
Initializing gnome-mount extension
** (gnome-power-preferences:9673): WARNING **: DBUS error: Could not get owner of name 'org.gnome.ScreenSaver': no such name
** (gnome-power-preferences:9673): DEBUG: proxy is NULL, maybe the daemon responsible for org.gnome.ScreenSaver is not running?
--------------------------------------------------
Comment 1 Gianluca Borello 2008-06-02 09:29:02 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 522534 ***