GNOME Bugzilla – Bug 467564
crash in Tasks: 1. application executed ...
Last modified: 2007-08-21 11:54:46 UTC
Version: 2.10 What were you doing when the application crashed? 1. application executed automatically on system start 2. enabled filter 3. moved filtered mails to another folder 4. removed filter 5. clicked on first mail and while opening switched application window to full screen 6. now application functional part didn't change size but main screen takes all desktop size 7. Bug reporting tool Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 118849536 vsize: 118849536 resident: 40255488 share: 32780288 rss: 40255488 rss_rlim: 4294967295 CPU usage: start_time: 1187331563 rtime: 120 utime: 110 stime: 10 cutime:1 cstime: 3 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208953120 (LWP 2527)] [New Thread -1269830768 (LWP 2686)] [New Thread -1236624496 (LWP 2629)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 155846
Thread 1 (Thread -1208953120 (LWP 2527))
----------- .xsession-errors --------------------- Major opcode: 54 Minor opcode: 0 Resource id: 0x1400211 X Error: BadPixmap (invalid Pixmap parameter) 4 Major opcode: 54 Minor opcode: 0 Resource id: 0x14001ee X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 158 Minor opcode: 6 Resource id: 0x14001ee X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 158 Minor opcode: 6 Resource id: 0x6f --------------------------------------------------
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 and reopen this bug or report a new one. Thanks in advance!
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 431459 ***