Bug 134584
Summary: | string search in messages, garbles up highlight and text message | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Tino Meinen <a.t.meinen> |
Component: | evolution | Assignee: | Matthew Barnes <mbarnes> |
Status: | CLOSED CANTFIX | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3 | CC: | darren, mattdm |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://members.chello.nl/a.t.meinen/evohighlight.png | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-10-30 15:19:09 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Tino Meinen
2004-10-04 20:08:55 UTC
this bug is still present in evolution-2.0.2-1 I filed the bug upstream in ximian's bugzilla, but apparently this is a fedora problem. It might be related to a wrong gtkhtml package? This is the relevant ximian bug: http://bugzilla.ximian.com/show_bug.cgi?id=68463 I think it's a gtkhtml3 bug. I'm seeing similar symptoms (no highlighting at all, in fact), with gtkhtml3-3.3.2-3 What version are you running? (we're running the gtkhtml 3.3.* branch in order to make use of Owen Taylor's work on improved Pango support there; I believe most other people are running the 3.2.* branch - so this could explain why it's a FC3-specific bug) Thanks for looking into this. I was feeling kinda lonely in here...:) I was using gtkhtml3-3.3.2-3 as well. But on a fc2 system, with a gtkhtml3-3.1.16-2 version evolution2 shows the same problems. Note: When you search for just the occurance of one word, you usually do not see any highlighting at all. If you type part of a whole sentence, if you are lucky, some words will highlight (partly). Alright I think a found a pattern. If you type in a word, and then, repeat the same word minus the last letter, you'll find the the word highlights (minus) the last letter. (so for example if you type the words: "directory director" the word directory will have the letters 'director' highlighted.) Hope that helps Another thing is, that if you search with enough words, somethimes the displaying of the header of the message gets garbeld up. Hope that all makes sense. it is still present in the latest versions of evolution/html on fc3 final. Any news on this? The bug is still present in evolution 2.0.4 for FC3. In addition to comment #6 : it doesn't make a difference if you search for: "directory director" or "director directory". In both cases the word directory will have the letters director highlighted. Just to add a "me too" to this bug report. I see *exactly* the described behaviour. This is on FC3 with evo 2.0.2. I'll report back when evo 2.0.4 is available from updates-released. Fedora Core 3 is now maintained by the Fedora Legacy project for security updates only. If this problem is a security issue, please reopen and reassign to the Fedora Legacy product. If it is not a security issue and hasn't been resolved in the current FC5 updates or in the FC6 test release, reopen and change the version to match. Thank you! Closing per lack of response to previous request for information. This bug was originally filed against a much earlier version of Fedora Core, and significant changes have taken place since the last version for which this bug is confirmed. It has remained in NEEDINFO status for quite a long period of time, asking for confirmation on a more recent (still fully supported) version of Fedora Core. Note that FC3 and FC4 are supported by Fedora Legacy for security fixes only. Please install a still supported version and retest. If it still occurs on FC5 or FC6, please reopen and assign to the correct version. Otherwise, if this a security issue, please change the product to Fedora Legacy. Thanks, and we are sorry that we did not get to this bug earlier. |