GNOME Bugzilla – Bug 602673
crash in GNOME Commander:
Last modified: 2009-12-07 11:55:50 UTC
Version: 1.2.8.2 What were you doing when the application crashed? Distribution: Solaris Express Community Edition snv_127 X86 Gnome Release: 2.28.0 2009-10-26 (Sun Microsystems, Inc.) BugBuddy Version: 2.28.0 X Vendor: Sun Microsystems, Inc. X Vendor Release: 10605000 Selinux: No Accessibility: Disabled GTK+ Theme: nimbus Icon Theme: nimbus GTK+ Modules: canberra-gtk-module, gnomebreakpad Memory status: size: 151220224 vsize: 151220224 resident: 26525696 share: 4128768 rss: 26525696 rss_rlim: 0 CPU usage: start_time: 1258926417 rtime: 54 utime: 373050 stime: 175166 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/gnome-commander' 1783: gnome-commander fd6c3d65 waitid (0, 6fc, 80467b0, 3) fd673335 waitpid (6fc, 804686c, 0, fd9ab60d) + 65 fd9aba14 g_spawn_sync (0, 8452e60, 0, 4, 0, 0) + 418 fd9abe28 g_spawn_command_line_sync (84526e0, 0, 0, 0, 804698c) + 5c fd201e4f __1cNrun_bug_buddy6Fpkclp0_b_ (82a4888, 6f7, 0, fd201ff2) + f3 fd2020d6 __1cMcheck_if_gdb6F_v_ (400, fd751000, 8046a1c, fd6be765, b, 0) + 12e fd201a94 __1cUbugbuddy_segv_handle6Fi_v_ (b, 0, 8046ad0, ffbffeff, ffff, fd4e2a00) + 64 fd6be765 __sighndlr (b, 0, 8046ad0, fd201a30) + 15 fd6b161f call_user_handler (b) + 2af fd6b184f sigacthandler (b, 0, 8046ad0) + df --- called from signal handler with signal 11 (SIGSEGV) --- fd9a5efb g_utf8_collate_key (8447680, 12) + 83 fd9a63eb g_utf8_collate_key_for_filename (8447680, ffffffff) + 2ff 08131fbb __1cUgnome_cmd_file_setup6FpnMGnomeCmdFile_pnQGnomeVFSFileInfo_pnLGnomeCmdDir__v_ (841ff28, 8440718, 83a8410) + bb 0811d651 __1cbBgnome_cmd_dir_new_from_info6FpnQGnomeVFSFileInfo_pnLGnomeCmdDir__3_ (8440718, 83a8410) + 1a1 0811deaf __1cQcreate_file_list6FpnLGnomeCmdDir_pnG_GList__3_ (83a8410, 8332aa0) + 19f 0811df88 __1cMon_list_done6FpnLGnomeCmdDir_pnG_GList_nOGnomeVFSResult__v_ (83a8410, 8332aa0, 0) + 68 080ecb29 __1cNblocking_list6FpnLGnomeCmdDir__v_ (83a8410, 0) + b9 080ec955 __1cMdirlist_list6FpnLGnomeCmdDir_i_v_ (83a8410, 0) + 85 0811e3fc __1cbAgnome_cmd_dir_relist_files6FpnLGnomeCmdDir_i_v_ (83a8410, 0) + 8c 0811e4e4 __1cYgnome_cmd_dir_list_files6FpnLGnomeCmdDir_i_v_ (83a8410, 0) + d4 0812e48c __1cUGnomeCmdFileSelectorNset_directory6MpnLGnomeCmdDir__v_ (83ce358, 83a8410) + 2dc 08130b20 __1cOset_connection6FpnUGnomeCmdFileSelector_pnLGnomeCmdCon_pnLGnomeCmdDir__v_ (83ce358, 83110d8, 83a8410) + 1b0 0812f1a5 __1cUGnomeCmdFileSelectorOset_connection6MpnLGnomeCmdCon_pnLGnomeCmdDir__v_ (83ce358, 83110d8, 0) + 165 08144133 __1cEinit6FpnPGnomeCmdMainWin__v_ (83b3800, 83b3280, 0, 0) + 973 fda4b1bc g_type_create_instance (83b2f00, fda1c460, 83c2ef8, fda3303d) + 58c fda33056 g_object_constructor (83b2f00, 3, 834d308, fda322e2) + 2a fda326b5 g_object_newv (83b2f00, 0, 0, fda32c29) + 3e1 fda32fde g_object_new_valist (83b2f00, 0, 80471f4, fda3226e) + 3c6 fda322cb g_object_new (83b2f00, 0, 8047204, fe48dd56) + 67 fe48dd75 gtk_type_new (83b2f00, 0) + 35 081442d3 __1cWgnome_cmd_main_win_new6F_pnK_GtkWidget__ (feffb804, 8304798, 829d8d8, 82a5848, 8047324, 8047258) + 13 08170f2e main (1, 8047264, 804726c, 80ec1a8) + 1be 080ec23d _start (1, 804738c, 0, 804739c, 80473e4, 8047418) + 7d
could be related to bug 599178
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 bug 599178 ***