GNOME Bugzilla – Bug 274110
Crashed when adding Filter rules using Create Folder, then Create Another Folder inside that.
Last modified: 2005-04-10 02:29:00 UTC
Distribution: SuSE Linux 9.2 (i586) Package: Evolution Priority: Normal Version: GNOME2.6. 2.0.1 Gnome-Distributor: SUSE Synopsis: Crashed when adding Filter rules using Create Folder, then Create Another Folder inside that. Bugzilla-Product: Evolution Bugzilla-Component: Mailer Bugzilla-Version: 2.0.1 BugBuddy-GnomeVersion: 2.0 (2.6.0) Description: Description of the crash: Was right clicking on emails and selecting Create Rule from Message. Then created a folder. Then created a folder under that one. Then tried to select that subfolder when it crashed. Steps to reproduce the crash: 1. See above 2. 3. Expected Results: Not crash. How often does this happen? So far first time after doing it about 20-30 times. Additional Information: Freshly installed system, but had just downloaded over 3,000+ emails from server to this new (Suse 9.2) system. Debugging Information: Backtrace was generated from '/opt/gnome/bin/evolution-2.0' (no debugging symbols found)...Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread 1093141376 (LWP 15563)] [New Thread 1149246384 (LWP 20122)] [Thread debugging using libthread_db enabled] [New Thread 1093141376 (LWP 15563)] [New Thread 1149246384 (LWP 20122)] [Thread debugging using libthread_db enabled] [New Thread 1093141376 (LWP 15563)] [New Thread 1149246384 (LWP 20122)] [New Thread 1131715504 (LWP 15578)] [New Thread 1133816752 (LWP 15575)] [New Thread 1125809072 (LWP 15573)] [New Thread 1123707824 (LWP 15572)] [New Thread 1121606576 (LWP 15571)] [New Thread 1116433328 (LWP 15570)] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0xffffe410 in ?? ()
+ Trace 57351
Thread 1 (Thread 1093141376 (LWP 15563))
Unknown reporter: hawke@hawkes-haven.com, changed to bugbuddy-import@ximian.com. Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
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. Matches the stack trace in bug 269857, which has been marked as a duplicate of 264377. *** This bug has been marked as a duplicate of 264377 ***