GNOME Bugzilla – Bug 443410
crash in svg gdk-pixbuf-loader
Last modified: 2008-07-07 16:04:29 UTC
What were you doing when the application crashed? Trying to create a rule based on sender in Evolution. 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:47:07 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 673173504 vsize: 673173504 resident: 50941952 share: 23842816 rss: 50941952 rss_rlim: 18446744073709551615 CPU usage: start_time: 1180837273 rtime: 1064 utime: 998 stime: 66 cutime:25 cstime: 10 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912739572512 (LWP 5082)] [New Thread 1094719824 (LWP 5253)] [New Thread 1115699536 (LWP 5166)] [New Thread 1126455632 (LWP 5125)] [New Thread 1084229968 (LWP 5096)] (no debugging symbols found) 0x00002aaaad8bf89f in waitpid () from /lib64/libpthread.so.0
+ Trace 137677
Thread 1 (Thread 46912739572512 (LWP 5082))
----------- .xsession-errors (8 sec old) --------------------- Major opcode: 157 Minor opcode: 6 Resource id: 0x64 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x161e703 X Error: BadPixmap (invalid Pixmap parameter) 4 Major opcode: 54 Minor opcode: 0 Resource id: 0x1401a88 X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 157 Minor opcode: 6 Resource id: 0x64 --------------------------------------------------
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. Thanks in advance!
*** Bug 446548 has been marked as a duplicate of this bug. ***
*** Bug 450740 has been marked as a duplicate of this bug. ***
*** Bug 451555 has been marked as a duplicate of this bug. ***
*** Bug 454451 has been marked as a duplicate of this bug. ***
*** Bug 459887 has been marked as a duplicate of this bug. ***
*** Bug 456219 has been marked as a duplicate of this bug. ***
*** Bug 449029 has been marked as a duplicate of this bug. ***
*** Bug 456482 has been marked as a duplicate of this bug. ***
trace from bug 456482:
+ Trace 151357
probably a fedora7 gtk+ issue, reported downstream as https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=250014
*** Bug 461514 has been marked as a duplicate of this bug. ***
dear reporters, can you please tell us which versions of gtk+ and evolution you are *exactly* using? to get this information, just open a gnome terminal window (applications -> system tools -> terminal), enter "rpm -q evolution" and "rpm -q gtk2", and post the output here as a new comment. thanks a lot in advance for your help getting this fixed!
As mentioned on Bug 456482 : I do not think the problem has gone away, but formally the version is whatever was current in the Fedora 7 repositories at the time I reported the bug. Looking through my yum log files that would seem to have been evolution.x86_64 2.10.3-1.fc7 (updated 8 July) gtk2.x86_64 2.10.13-1.fc7 (updated 20 June) gtk+.x86_64 1.2.10-57.fc7 (7 June) Current versions are: evolution-2.10.3-2.fc7 gtk2-2.10.14-3.fc7 gtk+-1.2.10-57.fc7 (only this one is the same as above) Allan.
Attempting to reproduce the bug (following the Bug 456482 recipe) with the current versions shown in Comment 13 gave an instance of Bug 445445 (which does not leave a stack trace). [Downstream ticket has been updated.]
*** Bug 465585 has been marked as a duplicate of this bug. ***
*** Bug 475268 has been marked as a duplicate of this bug. ***
*** Bug 475653 has been marked as a duplicate of this bug. ***
*** Bug 476022 has been marked as a duplicate of this bug. ***
*** Bug 489304 has been marked as a duplicate of this bug. ***
*** Bug 482307 has been marked as a duplicate of this bug. ***
*** Bug 482006 has been marked as a duplicate of this bug. ***
*** Bug 480519 has been marked as a duplicate of this bug. ***
*** Bug 478849 has been marked as a duplicate of this bug. ***
*** Bug 476660 has been marked as a duplicate of this bug. ***
*** Bug 487668 has been marked as a duplicate of this bug. ***
The stacktrace in comment #10 only shows GLib/GTK+ symbols. Do we know for sure that this is an Evolution bug or should this be reassigned to GTK+?
*** Bug 509251 has been marked as a duplicate of this bug. ***
*** Bug 510923 has been marked as a duplicate of this bug. ***
*** Bug 506894 has been marked as a duplicate of this bug. ***
*** Bug 512266 has been marked as a duplicate of this bug. ***
Anyone seeing this on Fedora 8 or later?
*** Bug 493378 has been marked as a duplicate of this bug. ***
It seems as it is that bug introduced in fedora 8 whichs number I've forget. So I'm closing this is OBSOLETE.