GNOME Bugzilla – Bug 267886
crash when selecting folder in the add filter rule dialog
Last modified: 2004-10-11 22:40:03 UTC
Distribution: Debian testing/unstable Package: Evolution Priority: Normal Version: GNOME2.8.0 2.0.1 Gnome-Distributor: Ubuntu Synopsis: crash when selecting folder in the add filter rule dialog Bugzilla-Product: Evolution Bugzilla-Component: Mailer Bugzilla-Version: 2.0.1 BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: when creating a filter in "add filter rule" dialog, after selecting "click here to select a folder", if you create more than one directory and click on "click here to select a folder" evolution crashes Steps to reproduce the crash: 1. select "create rule from message\filter on subject" 2. select "click here to select a folder" 3. select "new", give a folder name, and select create 4. leave the newly created folder as current folder and select new. 5. type a folder name, and select create. 6. select ok 7. crash when select " click here to select a folder" Expected Results: should be able to select a folder How often does this happen? everytime Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/evolution-2.0' (no debugging symbols found)...Using host libthread_db library "/lib/tls/i686/cmov/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)...(no debugging symbols found)...(no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread 1091724288 (LWP 6355)] [New Thread 1133517744 (LWP 6379)] [Thread debugging using libthread_db enabled] [New Thread 1091724288 (LWP 6355)] [New Thread 1133517744 (LWP 6379)] [Thread debugging using libthread_db enabled] [New Thread 1091724288 (LWP 6355)] [New Thread 1133517744 (LWP 6379)] (no debugging symbols found)...[New Thread 1124731824 (LWP 6374)] (no debugging symbols found)...[New Thread 1116339120 (LWP 6373)] (no debugging symbols found)...[New Thread 1107766192 (LWP 6360)] (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)...(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 __kernel_vsyscall ()
+ Trace 50913
Thread 1 (Thread 1091724288 (LWP 6355))
Unknown reporter: nicolas.crouzet@gmail.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.
*** This bug has been marked as a duplicate of 264377 ***