Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 620266 - Evolution crashes when reply is called for (before any composer window is opened)
Evolution crashes when reply is called for (before any composer window is ope...
Status: CLOSED NOTABUG
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: gtkhtml3 (Show other bugs)
6.1
All Linux
low Severity medium
: rc
: ---
Assigned To: Matthew Barnes
desktop-bugs@redhat.com
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-08-01 18:00 EDT by Matěj Cepl
Modified: 2010-08-01 18:17 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-08-01 18:17:43 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
backtrace (27.16 KB, text/plain)
2010-08-01 18:00 EDT, Matěj Cepl
no flags Details

  None (edit)
Description Matěj Cepl 2010-08-01 18:00:04 EDT
Created attachment 435916 [details]
backtrace

Description of problem:
When I have selected message in Evolution and I press Ctrl-R evolution crashes.

Version-Release number of selected component (if applicable):
gtkhtml3-3.30.1-1.el6.x86_64
evolution-data-server-2.28.3-9.el6.x86_64
evolution-2.28.3-8.el6.x86_64
evolution-spamassassin-2.28.3-8.el6.x86_64
evolution-data-server-doc-2.28.3-9.el6.noarch
evolution-data-server-debuginfo-2.28.3-9.el6.x86_64
evolution-data-server-devel-2.28.3-9.el6.x86_64


How reproducible:
two out of two

Steps to Reproduce:
1.see above
2.
3.
  
Actual results:
evolution crashes

Expected results:
new window with opened composer is opened

Additional info:
Comment 2 Matěj Cepl 2010-08-01 18:17:43 EDT
This is PEBKAC ... I had too new gtkhtml3 library (from the times I played with the most recent Evolution here).

Closing as NOTABUG ashamed

Note You need to log in before you can comment on or make changes to this bug.