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 534562 - crash in Open Folder: Looking at windows netwo...
crash in Open Folder: Looking at windows netwo...
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-05-23 22:59 UTC by samuel.saunders
Modified: 2008-05-23 23:19 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description samuel.saunders 2008-05-23 22:59:15 UTC
Version: 2.20.0

What were you doing when the application crashed?
Looking at windows network drive


Distribution: Debian lenny/sid
Gnome Release: 2.22.1 2008-04-08 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.22-2-amd64 #1 SMP Thu Aug 30 23:43:59 UTC 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 449417216 vsize: 449417216 resident: 31961088 share: 17043456 rss: 31961088 rss_rlim: 18446744073709551615
CPU usage: start_time: 1211583665 rtime: 361 utime: 322 stime: 39 cutime:0 cstime: 0 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)
[Thread debugging using libthread_db enabled]
[New Thread 0x2b4492fd4200 (LWP 25112)]
(no debugging symbols found)
0x00002b448c7caedf in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 0x2b4492fd4200 (LWP 25112))

  • #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 <signal handler called>
  • #5 ??
  • #6 ??
    from /usr/lib/libglib-2.0.so.0
  • #7 ??
  • #8 ??
  • #9 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #10 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #11 ??
    from /usr/lib/libglib-2.0.so.0
  • #12 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #13 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 ??
  • #15 __libc_start_main
    from /lib/libc.so.6
  • #16 ??
  • #17 ??
  • #18 ??
  • #0 waitpid
    from /lib/libpthread.so.0


----------- .xsession-errors (640 sec old) ---------------------
(gnome-panel:24989): GConf-WARNING **: Directory `/apps/panel/toplevels/bottom_panel_screen1/screen' was not being monitored by GConfClient 0x6bfd80
(gnome-panel:24989): GConf-WARNING **: Directory `/apps/panel/toplevels/top_panel_screen1/screen' was not being monitored by GConfClient 0x6bfd80
** Message: File monitoring not supported in the compiled version of gnome-vfs: bookmarks won't be monitored.
seahorse nautilus module initialized
** (nautilus:24994): WARNING **: Hit unhandled case 38 (Service not available) in fm_report_error_loading_directory
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: full-authentication!!!
Initializing gnome-mount extension
seahorse nautilus module initialized
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-05-23 23:19:34 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 522534 ***