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 487185 - crash in Open Folder: Trying to connect to a n...
crash in Open Folder: Trying to connect to a n...
Status: RESOLVED DUPLICATE of bug 478212
Product: nautilus
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-10-16 15:36 UTC by Kevin
Modified: 2007-10-19 22:28 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Kevin 2007-10-16 15:36:07 UTC 
Version: 2.18.3

What were you doing when the application crashed?
Trying to connect to a network share on a Windows pc.  Network made up of 2 pcs; 1 Linux FC7 and 1 winxp home.


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glider
Icon Theme: gnome

Memory status: size: 115970048 vsize: 115970048 resident: 38666240 share: 20824064 rss: 38666240 rss_rlim: 4294967295
CPU usage: start_time: 1192354795 rtime: 1500 utime: 1387 stime: 113 cutime:1 cstime: 1 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 -1208551712 (LWP 3117)]
[New Thread -1231631472 (LWP 16175)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 170592

Thread 1 (Thread -1208551712 (LWP 3117))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/libc.so.6
  • #6 abort
    from /lib/libc.so.6
  • #7 g_logv
    from /lib/libglib-2.0.so.0
  • #8 g_log
    from /lib/libglib-2.0.so.0
  • #9 g_assert_warning
    from /lib/libglib-2.0.so.0
  • #10 nautilus_connect_background_to_file_metadata
  • #11 ??
  • #12 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #13 ??
    from /lib/libgobject-2.0.so.0
  • #14 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #15 ??
    from /lib/libgobject-2.0.so.0
  • #16 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #17 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #18 fm_directory_view_begin_loading
  • #19 ??
  • #20 ??
  • #21 ??
  • #22 ??
    from /lib/libglib-2.0.so.0
  • #23 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #24 ??
    from /lib/libglib-2.0.so.0
  • #25 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #26 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #27 main
  • #0 __kernel_vsyscall 


----------- .xsession-errors ---------------------
** (nautilus:3117): WARNING **: Hit unhandled case 24 (Operation not permitted) in fm_report_error_loading_directory
closing
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: full-authentication!!!
** (nautilus:3117): WARNING **: No description found for mime type "x-directory/smb-share" (file is "documents"), please tell the gnome-vfs mailing list.
** (nautilus:3117): WARNING **: destroyed file still being monitored
** ERROR **: file nautilus-directory-background.c: line 621 (nautilus_connect_background_to_file_metadata): assertion failed: (NAUTILUS_IS_FILE (old_file))
aborting...
--------------------------------------------------
Comment 1 Christian Kirbach 2007-10-19 22:28:00 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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