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 375291 - crash in Network file browser: RIght clicked on the net...
crash in Network file browser: RIght clicked on the net...
Status: RESOLVED DUPLICATE of bug 374002
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-11-14 21:22 UTC by Dan Ratje
Modified: 2006-11-15 02:27 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Dan Ratje 2006-11-14 21:22:07 UTC
What were you doing when the application crashed?
RIght clicked on the network server.  This server happens to be a "smb" server, with several shares. 


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.18-1.2849.fc6 #1 SMP Fri Nov 10 12:36:14 EST 2006 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Enforcing
Accessibility: Disabled
----------- .xsession-errors ---------------------
** (nautilus:2927): CRITICAL **: nautilus_window_info_set_status: assertion `NAUTILUS_IS_WINDOW_INFO (window)' failed
** (nautilus:2927): CRITICAL **: nautilus_window_info_set_status: assertion `NAUTILUS_IS_WINDOW_INFO (window)' failed
(nautilus:2927): Eel-WARNING **: Trying to add a callback for preferences/background_set that already exists.
(nautilus:2927): Eel-WARNING **: Trying to add a callback for preferences/background_color that already exists.
(nautilus:2927): Eel-WARNING **: Trying to add a callback for preferences/background_filename that already exists.
** (nautilus:2927): CRITICAL **: nautilus_window_info_get_window_type: assertion `NAUTILUS_IS_WINDOW_INFO (window)' failed
** (nautilus:2927): CRITICAL **: nautilus_window_info_get_ui_manager: assertion `NAUTILUS_IS_WINDOW_INFO (window)' failed
** (bug-buddy:3170): WARNING **: Couldn't load icon for Open Folder
--------------------------------------------------

Memory status: size: 133545984 vsize: 0 resident: 133545984 share: 0 rss: 31477760 rss_rlim: 0
CPU usage: start_time: 1163538937 rtime: 0 utime: 758 stime: 0 cutime:715 cstime: 0 timeout: 43 it_real_value: 0 frequency: 0

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 -1208460544 (LWP 2927)]
(no debugging symbols found)
0x00856402 in __kernel_vsyscall ()

Thread 1 (Thread -1208460544 (LWP 2927))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 gtk_ui_manager_remove_ui
    from /usr/lib/libgtk-x11-2.0.so.0
  • #5 nautilus_marshal_BOOLEAN__POINTER
  • #6 fm_directory_view_bump_zoom_level
  • #7 fm_directory_view_bump_zoom_level
  • #8 fm_directory_view_update_menus
  • #9 fm_directory_view_bump_zoom_level
  • #10 g_source_get_current_time
    from /lib/libglib-2.0.so.0
  • #11 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #12 g_main_context_check
    from /lib/libglib-2.0.so.0
  • #13 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #14 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 POA_Nautilus_MetafileMonitor__init
  • #16 __libc_start_main
    from /lib/libc.so.6
  • #17 g_cclosure_marshal_VOID__ENUM
  • #0 __kernel_vsyscall

Comment 1 Dan Ratje 2006-11-14 21:25:53 UTC
The title of this bug is misleading.  I was using the network file browser when it crashed. Am changing the title.
Comment 2 André Klapper 2006-11-15 02:27:56 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 374002 ***