GNOME Bugzilla – Bug 270622
Crash: Wath shout I say somthing is going wrong
Last modified: 2006-10-13 00:08:40 UTC
Distribution: SuSE Linux 9.2 (i586) Package: Evolution Priority: Normal Version: GNOME2.6. 2.0.1 Gnome-Distributor: SUSE Synopsis: Wath shout I say somthing is going wrong Bugzilla-Product: Evolution Bugzilla-Component: Calendar Bugzilla-Version: 2.0.1 BugBuddy-GnomeVersion: 2.0 (2.6.0) Description: Description of the crash: Steps to reproduce the crash: 1. 2. 3. Expected Results: How often does this happen? Additional Information: 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 1093124992 (LWP 12067)] [New Thread 1209838512 (LWP 1811)] [Thread debugging using libthread_db enabled] [New Thread 1093124992 (LWP 12067)] [New Thread 1209838512 (LWP 1811)] [Thread debugging using libthread_db enabled] [New Thread 1093124992 (LWP 12067)] [New Thread 1209838512 (LWP 1811)] [New Thread 1129196464 (LWP 13859)] [New Thread 1126988720 (LWP 12124)] [New Thread 1124887472 (LWP 12123)] [New Thread 1122786224 (LWP 12118)] [New Thread 1120525232 (LWP 12117)] [New Thread 1117350832 (LWP 12092)] [New Thread 1115249584 (LWP 12091)] (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 53605
Thread 1 (Thread 1093124992 (LWP 12067))
Unknown reporter: t-riedl@ti.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.
Looks like addressbook preview pane wasn't inited properly.
*** Bug 300600 has been marked as a duplicate of this bug. ***
*** Bug 302462 has been marked as a duplicate of this bug. ***
Marking this bug as verified as its not reproducible in 2.0.4.
(In reply to comment #4) > Marking this bug as verified as its not reproducible in 2.0.4. This is a totally wrong reason for verifying! Please do *NOT* do this. Poornima, for starters, you can *not* verify an issue to be fixed, if you could not reproduce it reliably before. Could you? FWIW, bug 361462 now got a matching stacktrace...