Bug 714051 - Evo crashing on message load
Summary: Evo crashing on message load
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: rawhide
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-17 09:13 UTC by Tomáš Bžatek
Modified: 2015-03-03 23:01 UTC (History)
4 users (show)

Fixed In Version: evolution-3.1.3-1.fc16
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-07-19 15:29:29 UTC
Type: ---

Attachments (Terms of Use)
backtrace (18.80 KB, text/plain)
2011-06-17 09:13 UTC, Tomáš Bžatek 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Tomáš Bžatek 2011-06-17 09:13:23 UTC 
Created attachment 505215 [details]
backtrace

evolution-3.1.2-2.fc16.x86_64
gtk3-3.1.6-1.fc16.x86_64
glib2-2.29.8-1.fc16.x86_64
gtkhtml3-4.1.2-1.fc16.x86_64

How reproducible:
always

Steps to Reproduce:
1. Click the specific message in inbox in order to display it
2. Wait several seconds, UI looks frozen
3. segfault
  
Additional info:
Can provide the message privately if needed.

See attachment for more info.


(evolution:32325): Gtk-CRITICAL **: gtk_icon_source_set_pixbuf: assertion `pixbuf == NULL || GDK_IS_PIXBUF (pixbuf)' failed


0x00007ffff58f3d77 in gtk_icon_source_set_pixbuf (source=0x2312d20, pixbuf=0x7fffffffcf04) at gtkiconfactory.c:2187
2187	  g_return_if_fail (pixbuf == NULL || GDK_IS_PIXBUF (pixbuf));


Might be a gtk3 problem?
Comment 1 Milan Crha 2011-06-17 13:05:49 UTC 
Feel free to send me the message (preferably zipped) and I'll try to reproduce on my machine. The point of the first runtime critical warning will be crucial, I suppose. But to save your time, I would try to reproduce it myself first. Thanks in advance.
Comment 2 Tomáš Bžatek 2011-07-19 15:29:29 UTC 
Seems to be working fine now with evolution-3.1.3-1.fc16
Note You need to log in before you can comment on or make changes to this bug.