GNOME Bugzilla – Bug 365638
[g_log 4x nautilus_directory_async_state_changed] crash in CD/DVD Creator
Last modified: 2007-12-12 13:27:47 UTC
What were you doing when the application crashed? I logged out. Did a soft reboot. Then the login screen failed to load and it loaded an alternative one. After loging in all my programs started to crash. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 58736640 vsize: 0 resident: 58736640 share: 0 rss: 12218368 rss_rlim: 0 CPU usage: start_time: 1161937748 rtime: 0 utime: 41 stime: 0 cutime:38 cstime: 0 timeout: 3 it_real_value: 0 frequency: 0 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 -1226606928 (LWP 7527)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 78725
Thread 1 (Thread -1226606928 (LWP 7527))
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 366233 ***
Don't see how these stacktraces are the same issue. REOPENing.
*** Bug 366213 has been marked as a duplicate of this bug. ***
confirming as per duplicates.
*** Bug 386354 has been marked as a duplicate of this bug. ***
*** Bug 394850 has been marked as a duplicate of this bug. ***
*** Bug 403968 has been marked as a duplicate of this bug. ***
*** Bug 403398 has been marked as a duplicate of this bug. ***
*** Bug 406897 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 375769 has been marked as a duplicate of this bug. ***
*** Bug 410524 has been marked as a duplicate of this bug. ***
Since reporting this bug, I have completed all software updates. I have also installed all dbg's. Since then, the failure has changed. Here is what I am doing to create the crash: Using XWinLogon Windows X Server, I create a new session using the following options: SET PATH=C:\xwinlogon SET DISPLAY=:0 start XWin_GL.exe :0 -clipboard -trayicon -bs start xterm -e /usr/X11R6/bin/ssh -Y *****vall@192.168.0.217 gnome-session I enter in the correct password, an Cygwin window opens and brings up Bug Buddy with the following details: Memory status: size: 26652672 vsize: 0 resident: 26652672 share: 0 rss: 9150464 rss_rlim: 0 CPU usage: start_time: 1172325828 rtime: 0 utime: 26 stime: 0 cutime:22 cstime: 0 timeout: 4 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/libexec/evolution-alarm-notify' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1233230160 (LWP 8252)] [New Thread -1234527328 (LWP 8293)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 113509
Thread 1 (Thread -1233230160 (LWP 8252))
*** Bug 411726 has been marked as a duplicate of this bug. ***
*** Bug 418590 has been marked as a duplicate of this bug. ***
*** Bug 419922 has been marked as a duplicate of this bug. ***
*** Bug 434004 has been marked as a duplicate of this bug. ***
*** Bug 442381 has been marked as a duplicate of this bug. ***
*** Bug 449665 has been marked as a duplicate of this bug. ***
*** Bug 452294 has been marked as a duplicate of this bug. ***
*** Bug 452296 has been marked as a duplicate of this bug. ***
*** Bug 468267 has been marked as a duplicate of this bug. ***
*** Bug 469172 has been marked as a duplicate of this bug. ***
no duplicates in the last 60 days, and no reports from 2.18 and 2.20. assuming that this bug has been fixed in the meantime and closing as obsolete. anybody running into this problem on gnome 2.18 or 2.20, please reopen this report! thanks.