GNOME Bugzilla – Bug 641620
crash in File Manager: crash jhappens during lo...
Last modified: 2011-02-06 01:17:38 UTC
Version: 2.30.1 What were you doing when the application crashed? crash jhappens during logon from a user on Gnome some Time before I changed the Name from the Server from Server HP-N36L to HP-Server. After this I had a lot of trouble with the Samba configuration and I deleted this user and creted later on new Distribution: OpenIndiana Development oi_148 X86 Gnome Release: 2.30.2 2010-11-26 (The OpenIndiana Project) BugBuddy Version: 2.30.0 X Vendor: OpenIndiana, based on X.Org Foundation & OpenSolaris sources X Vendor Release: 10707000 Selinux: No Accessibility: Disabled GTK+ Theme: nimbus Icon Theme: nimbus GTK+ Modules: canberra-gtk-module, gnomebreakpad Memory status: size: 215367680 vsize: 215367680 resident: 48603136 share: 90112 rss: 48603136 rss_rlim: 0 CPU usage: start_time: 1296929132 rtime: 104 utime: 714491 stime: 329398 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/nautilus' 2845: nautilus ----------------- lwp# 1 -------------------------------- feee2517 waitid (0, b21, 8047150, 3) fee92005 waitpid (b21, 80471fc, 0, fdd81547) + 65 fdd81595 __1cVrun_bug_buddy_solaris6F_v_ (feeb76d9, fef60000, 804723c, feeddb05, b, 0) + 69 fdd81607 __1cUbugbuddy_segv_handle6Fi_v_ (b, 0, 80472f0, fee7a8c6, feeb76b4, fe732a40) + 67 feeddb05 __sighndlr (b, 0, 80472f0, fdd815a0) + 15 feed09de call_user_handler (b) + 2a2 feed0c22 sigacthandler (b, 0, 80472f0) + f2 --- called from signal handler with signal 11 (SIGSEGV) --- 08107007 directory_belongs_in_scripts_menu (0, 81fd4b8, 83860b0, 83860ac) + 37 08107135 update_scripts_menu (835c9d8, 0, 0, 810cd8e) + 101 0810d2f2 real_update_menus (835c9d8) + ff6 0811647e fm_icon_view_update_menus (835c9d8, 82b7e80, 8047698, 80fddbc) + 4e 080fddd7 real_update_menus (835c9d8, 82b7e80, 80476b8, 810fcc0) + 97 0810fcd5 fm_directory_view_update_menus (835c9d8, 50) + 71 08102fff update_menus_timeout_callback (835c9d8, fea9e774, 0, fe9ebe6c) + 4f fe9ebe82 g_timeout_dispatch (83af710, 8102fb0, 835c9d8, 8047770) + 26 fe9ea05f g_main_context_dispatch (825a458, 0, 837fef8, f) + 25f fe9ea70d g_main_context_iterate (825a458, 1, 1, 8232da0) + 46d fe9ead4b g_main_loop_run (837e048, 837e048, e7, fdf80ff5) + 1d7 fdf810a3 gtk_main (80478f0, feedb526, 8047968, 0, 0, 0) + bf 080d053b main (1, 8047a14, 8047a1c, 80bf25f) + 7bb 080bf2bd _start (1, 8047b28, 0, 8047b31, 8047b68, 8047b96) + 7d ----------------- lwp# 3 -------------------------------- feedda6b lwp_park (0, f384fe08, 0) feed705d cond_wait_queue (83b1718, 8299208, f384fe08, feed72a6) + 60 feed7483 cond_wait_common (83b1718, 8299208, f384fe08, feed76c6) + 1eb feed771e __cond_timedwait (83b1718, 8299208, f384fe88, feed77b0) + 66 feed77c1 cond_timedwait (83b1718, 8299208, f384fe88, feed77f4) + 27 feed780c pthread_cond_timedwait (83b1718, 8299208, f384fe88, fe711b1c) + 24 fe711b66 g_cond_timed_wait_posix_impl (83b1718, 8299208, f384ff38, fe9c0615) + 5a fe9c0695 g_async_queue_pop_intern_unlocked (82991e8, 0, f384ff38, fe9c0ab9) + 91 fe9c0b0d g_async_queue_timed_pop (82991e8, f384ff38, 83dbff8, fea137b1) + 65 fea1386d g_thread_pool_wait_for_new_pool (838c3e8, fea9e774, 4d4d916f, d5d35, fea9f8c4, 0) + cd fea13ac4 g_thread_pool_thread_proxy (838c318, 838c3e8, 208, fea12285) + 184 fea123a5 g_thread_create_proxy (838c3e8, fef60000, f384ffe8, feedd72e) + 131 feedd783 _thrp_setup (fe4b1240) + 9b feedda30 _lwp_start (fe4b1240, 0, 0, 0, 0, 0)
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 bug 625799 ***