GNOME Bugzilla – Bug 358172
2.16: crash in nautilus-file.c:295
Last modified: 2007-10-19 23:11:34 UTC
What were you doing when the application crashed? Abrir una conexión ssh con la aplicación Nautilus. Try to open a ssh connection whit Nautilus Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.0 2006-09-04 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 89624576 vsize: 0 resident: 89624576 share: 0 rss: 34811904 rss_rlim: 0 CPU usage: start_time: 1159433231 rtime: 0 utime: 4948 stime: 0 cutime:3897 cstime: 0 timeout: 1051 it_real_value: 0 frequency: 1031 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1226471760 (LWP 4186)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 73496
Thread 1 (Thread -1226471760 (LWP 4186))
*** Bug 365423 has been marked as a duplicate of this bug. ***
confirming as per duplicates, bug triagers are also very allowed to do the same, guenther. ;-)
*** Bug 373937 has been marked as a duplicate of this bug. ***
*** Bug 374173 has been marked as a duplicate of this bug. ***
*** Bug 375744 has been marked as a duplicate of this bug. ***
*** Bug 376577 has been marked as a duplicate of this bug. ***
*** Bug 378028 has been marked as a duplicate of this bug. ***
*** Bug 380851 has been marked as a duplicate of this bug. ***
*** Bug 381273 has been marked as a duplicate of this bug. ***
*** Bug 382827 has been marked as a duplicate of this bug. ***
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
*** Bug 383968 has been marked as a duplicate of this bug. ***
*** Bug 384176 has been marked as a duplicate of this bug. ***
*** Bug 383969 has been marked as a duplicate of this bug. ***
*** Bug 386356 has been marked as a duplicate of this bug. ***
I tried to reproduce it with debug symbols installed. Sorry, I could not find for all libraries the corresponding debug symbols (e.g libc.so.6, libgnomevfs-2.so.0 -> somehow a mismatch from my installed versions to the versions of the debug symbol packages...). Anyway, I hope it helps! ------------------------------------------------------------------------------ Dump start ------------------------------------------------------------------------------ Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 104837120 vsize: 0 resident: 104837120 share: 0 rss: 31903744 rss_rlim: 0 CPU usage: start_time: 1166259932 rtime: 0 utime: 2944 stime: 0 cutime:2707 cstime: 0 timeout: 237 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/nautilus' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1226455376 (LWP 4486)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 94625
Thread 1 (Thread -1226455376 (LWP 4486))
------------------------------------------------------------------------------ Dump end ------------------------------------------------------------------------------
hp.mu: looks pretty good, thanks a lot. you're running the latest stable ubuntu, with all updates installed?
Andre Klapper: yes, as far as I know. At least the software update manager tells me this! The only software that I installed directly was realplayer 10.0.8.805 (gold).
*** Bug 382001 has been marked as a duplicate of this bug. ***
bug 386635 could be another duplicate
*** Bug 389869 has been marked as a duplicate of this bug. ***
*** Bug 391910 has been marked as a duplicate of this bug. ***
*** Bug 392327 has been marked as a duplicate of this bug. ***
*** Bug 397295 has been marked as a duplicate of this bug. ***
*** Bug 397751 has been marked as a duplicate of this bug. ***
*** Bug 398193 has been marked as a duplicate of this bug. ***
*** Bug 400007 has been marked as a duplicate of this bug. ***
*** Bug 400422 has been marked as a duplicate of this bug. ***
*** Bug 403451 has been marked as a duplicate of this bug. ***
*** Bug 402893 has been marked as a duplicate of this bug. ***
*** Bug 408530 has been marked as a duplicate of this bug. ***
*** Bug 410873 has been marked as a duplicate of this bug. ***
*** Bug 364674 has been marked as a duplicate of this bug. ***
.xsession-errors extract from bug 378872: ----------- .xsession-errors --------------------- ** ERROR **: file nautilus-file.c: line 295 (add_to_link_hash_table_list): assertion failed: (g_list_find (list, file) == NULL) aborting... ** ERROR **: file nautilus-file.c: line 295 (add_to_link_hash_table_list): assertion failed: (g_list_find (list, file) == NULL) aborting...
The same simple question - is there any precise instructions to reproduce this problem? For example here file is added to the link hash twice. But it's really not clear what circumstances lead to that situation. How is it possible to add the same link to the file twice?
i think that bug 408283 is somehow related, it's about removing from a hash table list: "remove_from_link_hash_table_list", "g_list_find (list, file) != NULL")
I'm not sure how the hashtable gets out of whack, but i added some code to make this "safe" and changed the asserts to g_warnings. We still have an issue here, but at least it won't crash.
*** Bug 408283 has been marked as a duplicate of this bug. ***
*** Bug 412044 has been marked as a duplicate of this bug. ***
*** Bug 412448 has been marked as a duplicate of this bug. ***
*** Bug 415269 has been marked as a duplicate of this bug. ***
*** Bug 416219 has been marked as a duplicate of this bug. ***
*** Bug 409867 has been marked as a duplicate of this bug. ***
*** Bug 417550 has been marked as a duplicate of this bug. ***
*** Bug 417982 has been marked as a duplicate of this bug. ***
*** Bug 423336 has been marked as a duplicate of this bug. ***
*** Bug 422418 has been marked as a duplicate of this bug. ***
*** Bug 421384 has been marked as a duplicate of this bug. ***
*** Bug 424352 has been marked as a duplicate of this bug. ***
*** Bug 426455 has been marked as a duplicate of this bug. ***
*** Bug 429480 has been marked as a duplicate of this bug. ***
*** Bug 430270 has been marked as a duplicate of this bug. ***
*** Bug 428773 has been marked as a duplicate of this bug. ***
*** Bug 430670 has been marked as a duplicate of this bug. ***
*** Bug 430711 has been marked as a duplicate of this bug. ***
*** Bug 432561 has been marked as a duplicate of this bug. ***
*** Bug 433103 has been marked as a duplicate of this bug. ***
*** Bug 433108 has been marked as a duplicate of this bug. ***
*** Bug 435102 has been marked as a duplicate of this bug. ***
*** Bug 437832 has been marked as a duplicate of this bug. ***
*** Bug 438278 has been marked as a duplicate of this bug. ***
*** Bug 438523 has been marked as a duplicate of this bug. ***
*** Bug 441535 has been marked as a duplicate of this bug. ***
*** Bug 442542 has been marked as a duplicate of this bug. ***
*** Bug 443663 has been marked as a duplicate of this bug. ***
*** Bug 447853 has been marked as a duplicate of this bug. ***
*** Bug 448716 has been marked as a duplicate of this bug. ***
*** Bug 448225 has been marked as a duplicate of this bug. ***
*** Bug 450358 has been marked as a duplicate of this bug. ***
*** Bug 452117 has been marked as a duplicate of this bug. ***
*** Bug 455054 has been marked as a duplicate of this bug. ***
*** Bug 457383 has been marked as a duplicate of this bug. ***
*** Bug 468450 has been marked as a duplicate of this bug. ***
*** Bug 467804 has been marked as a duplicate of this bug. ***
we have only 2.16 duplicates here. i will close this ticket according to comment 37 as we assume that this has been fixed. if anybody can reproduce this issue with version 2.18 or later, please do reopen this report. thanks.
*** Bug 474067 has been marked as a duplicate of this bug. ***
*** Bug 472025 has been marked as a duplicate of this bug. ***
*** Bug 479229 has been marked as a duplicate of this bug. ***