Bug 179820 - [cal] canidate windows position is random
Summary: [cal] canidate windows position is random
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution-data-server
Version: 5
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Dave Malcolm
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: SCIM
TreeView+ depends on / blocked
 
Reported: 2006-02-03 06:04 UTC by Lawrence Lim
Modified: 2014-03-26 00:53 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-02-20 11:14:07 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
an example of candiate window position itself randomly (117.67 KB, image/png)
2006-02-03 06:04 UTC, Lawrence Lim
no flags Details

Description Lawrence Lim 2006-02-03 06:04:12 UTC
Description of problem:
When using scim with evolution, the candidate windows for scim seems to be
positioned randomly. Sometimes at the bottom of the screen, and for the
screenshot, it is positioned in the middle of the screen. 

Version-Release number of selected component (if applicable):
evolution-2.5.4-2
evolution-data-server-1.5.4-2
scim-1.4.2-9

How reproducible:
Always

Steps to Reproduce:
1.start evolution in any CJK locale
2.goto View->Calendar
3.In the calendar's day view, click on 2.300PM
4.ctrl-space to activate scim
5.select Anthy (japan IME)
6. enter aka SPACE SPACE
  
Actual results:
candidate pops up in random position

Expected results:
on the spot or over the spot?

Additional info:

Comment 1 Lawrence Lim 2006-02-03 06:04:13 UTC
Created attachment 124094 [details]
an example of candiate window position itself randomly

Comment 2 Rahul Sundaram 2006-02-20 11:14:07 UTC

These bugs are being closed since a large number of updates have been released
after the FC5 test1 and test2 releases. Kindly update your system by running yum
update as root user or try out the third and final test version of FC5 being
released in a short while and verify if the bugs are still present on the system
.Reopen or file new bug reports as appropriate after confirming the presence of
this issue. Thanks


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