GNOME Bugzilla – Bug 453164
crash in Calendar: 1) read a memo 2) for ar...
Last modified: 2008-01-08 18:13:25 UTC
What were you doing when the application crashed? 1) read a memo 2) for around 1 minute 3) memo content disappears suddenly 4) click that memo again to try to bring it back 5) crash Almost everytime I can reproduce this. Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: VistaBut Icon Theme: Tango Memory status: size: 208527360 vsize: 208527360 resident: 54992896 share: 43204608 rss: 54992896 rss_rlim: 4294967295 CPU usage: start_time: 1183397125 rtime: 450 utime: 411 stime: 39 cutime:38 cstime: 13 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' Using host libthread_db library "/lib/libthread_db.so.1". `shared object read from target memory' has disappeared; keeping its symbols. [Thread debugging using libthread_db enabled] [New Thread -1208195360 (LWP 5087)] [New Thread -1297089648 (LWP 5174)] [New Thread -1446917232 (LWP 5173)] [New Thread -1329620080 (LWP 5123)] [New Thread -1308640368 (LWP 5117)] 0x00889402 in __kernel_vsyscall ()
+ Trace 145299
Thread 5 (Thread -1308640368 (LWP 5117)): #-1 0x00889402 in __kernel_vsyscall () No symbol table info available. Thread 4 (Thread -1329620080 (LWP 5123)): #-1 0x00889402 in __kernel_vsyscall () No symbol table info available. Thread 3 (Thread -1446917232 (LWP 5173)): #-1 0x00889402 in __kernel_vsyscall () No symbol table info available. Thread 2 (Thread -1297089648 (LWP 5174)): #-1 0x00889402 in __kernel_vsyscall () No symbol table info available. Thread 1 (Thread -1208195360 (LWP 5087)): #-1 0x00889402 in __kernel_vsyscall () No symbol table info available. ----------- .xsession-errors --------------------- Variable "var_args" is not available. Variable "is_active" is not available. Variable "var_args" is not available. Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded --------------------------------------------------
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 224322 ***
Hello xinzhen, I would like to ask you if you are still able to reproduce this bug. I would like to reproduce it myself, but no luck, it works as expected. You wrote you can reproduce (even around half year ago), so I would like to ask you for a help, if you can, of course. I guess you had there some text selected, in the memo preview, because without a selection it should work properly. Can you try if it depends on the part of selected text please? Or the way how you selected the text in preview? (like from top to bottom or opposite, or something.) You wrote above you clicked on the task again to see it, I guess you did it by mouse (hence the click word, right?) From the stack trace it seems that you placed focus back to preview. (To be honest I'm not sure what to ask, so it seems a bit strange.)