Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: JTextArea & JTextField do not send XIM_SET_IC_FOCUS & XIM_UNSET_IC_FOCUS events to XIM server
https://bugzilla.redhat.com/show_bug.cgi?id=462412
Summary: JTextArea & JTextField do not send XIM_SET_IC_FOCUS &
XIM_UNSET_IC_FOCUS events to XIM server
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Severity: high
Priority: high
Component: java-1.6.0-openjdk
AssignedTo: langel(a)redhat.com
ReportedBy: shawn.p.huang(a)gmail.com
QAContact: extras-qa(a)fedoraproject.org
CC: mark(a)klomp.org, langel(a)redhat.com, lkundrak(a)v3.sk,
fedora-i18n-bugs(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
Description of problem:
JTextArea & JTextField do not send XIM_SET_IC_FOCUS & XIM_UNSET_IC_FOCUS to XIM
server.
When JTextArea & JTextField work with XIM input methods, it do not set or unset
ic focus via XIM protocol. So XIM server can not handle focus for Java
application properly. I did not try other java widgets, maybe they have this
problem too.
Version-Release number of selected component (if applicable):
java-1.6.0-openjdk-demo-1.6.0.0-0.20.b11.fc10.i386
java-1.6.0-openjdk-1.6.0.0-0.20.b11.fc10.i386
java-1.6.0-openjdk-plugin-1.6.0.0-0.20.b11.fc10.i386
How reproducible:
Always
Steps to Reproduce:
1.
2.
3.
Actual results:
JTextArea & JTextField do not send XIM_SET_IC_FOCUS & XIM_UNSET_IC_FOCUS events
to XIM server.
Expected results:
JTextArea & JTextField send XIM_SET_IC_FOCUS & XIM_UNSET_IC_FOCUS events to XIM
server, when they get or lose focus.
Additional info:
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: No icon for im-chooser
https://bugzilla.redhat.com/show_bug.cgi?id=468829
Summary: No icon for im-chooser
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: medium
Component: gcin
AssignedTo: candyz0416(a)gmail.com
ReportedBy: tagoh(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: petersen(a)redhat.com, candyz0416(a)gmail.com,
fedora-i18n-bugs(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
Description of problem:
gcin.conf has ICON definition but the file described there isn't available.
Version-Release number of selected component (if applicable):
gcin-1.4.2-4.fc10
How reproducible:
always
Steps to Reproduce:
1.run im-chooser
2.see ICON in /etc/X11/xinit/xinput.d/gcin.conf
3.rpm -qf $ICON in gcin.conf
Actual results:
1. no icon available for gcin
3. error: file /usr/share/icons/gcin/gcin.png: No such file or directory
Expected results:
the right thing should be set to ICON.
Additional info:
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: scim-python : Unowned directories
https://bugzilla.redhat.com/show_bug.cgi?id=473665
Summary: scim-python : Unowned directories
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Severity: low
Priority: low
Component: scim-python
AssignedTo: phuang(a)redhat.com
ReportedBy: bugs.michael(a)gmx.net
QAContact: extras-qa(a)fedoraproject.org
CC: phuang(a)redhat.com, fedora-i18n-bugs(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
One or more directories are not included within this
package and/or its sub-packages:
=> scim-python-pinyin-0.1.13rc1-1.fc10.i386 (rawhide-development-i386)
/usr/share/scim-python/data
=> scim-python-xingma-0.1.13rc1-1.fc10.i386 (rawhide-development-i386)
/usr/share/scim-python/engine/XingMa
/usr/share/scim-python/engine/XingMa/tables
=> scim-python-xingma-cangjie-0.1.13rc1-1.fc10.i386 (rawhide-development-i386)
/usr/share/scim-python/engine/XingMa
/usr/share/scim-python/engine/XingMa/tables
=> scim-python-xingma-erbi-0.1.13rc1-1.fc10.i386 (rawhide-development-i386)
/usr/share/scim-python/engine/XingMa
/usr/share/scim-python/engine/XingMa/tables
=> scim-python-xingma-wubi-0.1.13rc1-1.fc10.i386 (rawhide-development-i386)
/usr/share/scim-python/engine/XingMa
/usr/share/scim-python/engine/XingMa/tables
=> scim-python-xingma-zhengma-0.1.13rc1-1.fc10.i386 (rawhide-development-i386)
/usr/share/scim-python/engine/XingMa
/usr/share/scim-python/engine/XingMa/tables
Note: It may be necessary to include directories in multiple
packages.
[...]
Further information:
https://fedoraproject.org/wiki/Packaging/ReviewGuidelines
MUST: A package must own all directories that it creates. If it does not
create a directory that it uses, then it should require a package which
does create that directory.
https://fedoraproject.org/wiki/Packaging/Guidelines#FileAndDirectoryOwnersh…https://fedoraproject.org/wiki/Packaging/UnownedDirectories
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: race condition in XIM handling
https://bugzilla.redhat.com/show_bug.cgi?id=465392
Summary: race condition in XIM handling
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: medium
Component: scim
AssignedTo: shawn.p.huang(a)gmail.com
ReportedBy: tagoh(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: petersen(a)redhat.com, shawn.p.huang(a)gmail.com,
fedora-i18n-bugs(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
Description of problem:
if one sends the key event to SCIM too much and too faster, the application,
such as emacs and xterm freezes.
Version-Release number of selected component (if applicable):
scim-1.4.7-32.fc10
How reproducible:
always as long as it's on the above condition
Steps to Reproduce:
1.change the keyboard repeat setting to make this easier to see, like
gconftool-2 -s -t int /desktop/gnome/peripherals/keyboard/delay 100 and
gconftool-2 -s -t int /desktop/gnome/peripherals/keyboard/rate 110
2.open xterm with XMODIFIERS=@im=SCIM
3.keep pressing a key until it freezes
Actual results:
freeze
Expected results:
should handles it properly
Additional info:
What exactly happened on this race condition issue is:
https://bugzilla.redhat.com/show_bug.cgi?id=452849#c19
Quote from XIM specification:
In on-demand-synchronous method, the IM library always receives
XIM_FORWARD_EVENT or XIM_COMMIT message as a synchronous request. Also, the IM
Server needs to synchronously process the correspondent reply from the IM
library and the following XIM_FORWARD_EVENT message sent from the IM library
when any of the event causes the IM Server to send XIM_FORWARD_EVENT or
XIM_COMMIT message to the IM library, so that the input service is consistent.
If the IM library gets the control back from the application after receiving
the synchronous request, the IM library replies for the synchronous request
before processing any of the events. In this time, the IM Server blocks
XIM_FORWARD_EVENT message which is sent by the IM library, and handles it after
receiving the reply. Howerver, the IM Server handles the other protocols /at
any time/.
So in the case at the above URL, XIM server has to process XIM_SET_IC_VALUES
regardless of waiting for XIM_SYNC_REPLY.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: imsettings causes window manager confusion in Xfce
https://bugzilla.redhat.com/show_bug.cgi?id=471927
Summary: imsettings causes window manager confusion in Xfce
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: medium
Component: imsettings
AssignedTo: tagoh(a)redhat.com
ReportedBy: kevin(a)tummy.com
QAContact: extras-qa(a)fedoraproject.org
CC: tagoh(a)redhat.com, fedora-i18n-bugs(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
If the imsettings and imsettings-xfce packages are installed xfwm4 settings are
confused and don't think xfwm4 is the window manager.
1. Install imsettings-xfce
2. yum groupinstall XFCE
3. login and choose Xfce as your desktop.
4. right click on the desktop
5. choose settings manager
6. choose either "Window Manager" or "Window Manager Tweaks".
7. You will get a message:
"These settings cannot work with your current window manager (imsetting-xim)"
The code in xfwm4 hasn't changed in years here. It does:
wm_name = gdk_x11_screen_get_window_manager_name (gdk_screen_get_default
());
if (g_ascii_strcasecmp (wm_name, "Xfwm4"))
{
xfce_err (_("These settings cannot work with your current window
manager (%s)"), wm_name);
return;
}
Is imsettings changing the gdk default window manager somehow?
Removing imsettings causes everything to work as normal.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: scim-python-pinyin db file too big!
https://bugzilla.redhat.com/show_bug.cgi?id=468964
Summary: scim-python-pinyin db file too big!
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: medium
Component: scim-python
AssignedTo: shawn.p.huang(a)gmail.com
ReportedBy: petersen(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: shawn.p.huang(a)gmail.com, fedora-i18n-bugs(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
Description of problem:
The py.db file in scim-python-pinyin is 120MB it seems very big: eg scim-pinyin
Steps to Reproduce:
1. du -sh /usr/share/scim-python/engine/PinYin
2. du -sh /usr/share/scim/pinyin
Actual results:
1. 121M
2. 4.5M
Expected results:
1. similar to scim-pinyin
Additional info:
This means we can't currently use scim-python-pinyin as default IM on Live
images.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: emacs should disable XIM by default
https://bugzilla.redhat.com/show_bug.cgi?id=465214
Summary: emacs should disable XIM by default
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: medium
Component: emacs
AssignedTo: coldwell(a)redhat.com
ReportedBy: petersen(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: coldwell(a)redhat.com, fedora-i18n-bugs(a)redhat.com
Blocks: 438944
Estimated Hours: 0.0
Classification: Fedora
Description of problem:
XIM (X Input Method protocol) is pretty intrusive for Emacs users specially for
SCIM which defaults to using C-Space as its hotkey, and anyway Emacs provides
its own superior builtin input methods designed for native input. I propose
that we turn off XIM by default Emacs for fedora. It can still be enabled by
users using the X resource useXIM.
Steps to Reproduce:
1. Run Emacs with SCIM enabled.
2. Press C-Space
Actual results:
2. SCIM is enabled
Expected results:
2. mark to be set
Additional info:
Emacs is capable of input most major Asian languages adequately by itself and
also can support has package that support anthy, scim-bridge and uim via elisp,
therefore is no need to have XIM enabled by default any longer.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: anaconda doesn't render glyphs with the proper font
https://bugzilla.redhat.com/show_bug.cgi?id=467982
Summary: anaconda doesn't render glyphs with the proper font
Product: Fedora
Version: rawhide
Platform: i386
OS/Version: Linux
Status: NEW
Keywords: Regression
Severity: medium
Priority: medium
Component: anaconda
AssignedTo: anaconda-maint-list(a)redhat.com
ReportedBy: tagoh(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: anaconda-maint-list(a)redhat.com, dcantrell(a)redhat.com,
fedora-i18n-bugs(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
Created an attachment (id=321105)
--> (https://bugzilla.redhat.com/attachment.cgi?id=321105)
Screenshot
Description of problem:
When I select Japanese on the language selection with today's rawhide tree, it
looks like anaconda is rendering some glyphs with Chinese font.
Version-Release number of selected component (if applicable):
anaconda-11.4.1.50
How reproducible:
always
Steps to Reproduce:
1.Select Japanese on the language selection
2.See a notice for beta after pressing Next button twice.
3.
Actual results:
some glyphs looks like from Chinese font.
Expected results:
should be from Japanese font.
Additional info:
This is a regression. it worked before.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: Hotkeys has no response and "Go To" window couldn't be inputted.
https://bugzilla.redhat.com/show_bug.cgi?id=462041
Summary: Hotkeys has no response and "Go To" window couldn't be
inputted.
Product: Fedora
Version: 9
Platform: All
OS/Version: Linux
Status: NEW
Keywords: i18n
Severity: medium
Priority: medium
Component: fontforge
AssignedTo: kevin(a)tummy.com
ReportedBy: cchance(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: petersen(a)redhat.com, roozbeh(a)gmail.com,
fedora-fonts-bugs-list(a)redhat.com,
fedora-i18n-bugs(a)redhat.com
Depends on: 462038
Estimated Hours: 0.0
Classification: Fedora
+++ This bug was initially created as a clone of Bug #462038 +++
Description of problem:
#1: Hotkeys are not responded.
#2: "Go To" window couldn't be inputted.
Version-Release number of selected component (if applicable):
fontforge-20080828-1.fc10.i386
How reproducible:
Always.
Steps to Reproduce:
1. Start fontforge from gnome-terminal.
2. Try hotkeys like Alt-F.
3. Observe symptom #1.
4. Select View > Goto from menu.
5. Try to input something in the input field.
6. Observe symptom #2.
Actual results:
#1. No response.
#2. Couldn't be inputted.
Expected results:
#1. File sub-menu pops up.
#2. Data is inputted in field.
Additional info:
HEAD of F9 has same issue as well.
--- Additional comment from cchance(a)redhat.com on 2008-09-12 02:26:49 EDT ---
`LANG=C fontforge [FILE]` resolves as workaround.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: Hotkeys has no response and "Go To" window couldn't be inputted.
https://bugzilla.redhat.com/show_bug.cgi?id=462038
Summary: Hotkeys has no response and "Go To" window couldn't be
inputted.
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Keywords: i18n
Severity: medium
Priority: medium
Component: fontforge
AssignedTo: kevin(a)tummy.com
ReportedBy: cchance(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: roozbeh(a)gmail.com, fedora-fonts-bugs-list(a)redhat.com,
fedora-i18n-bugs(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
Description of problem:
#1: Hotkeys are not responded.
#2: "Go To" window couldn't be inputted.
Version-Release number of selected component (if applicable):
fontforge-20080828-1.fc10.i386
How reproducible:
Always.
Steps to Reproduce:
1. Start fontforge from gnome-terminal.
2. Try hotkeys like Alt-F.
3. Observe symptom #1.
4. Select View > Goto from menu.
5. Try to input something in the input field.
6. Observe symptom #2.
Actual results:
#1. No response.
#2. Couldn't be inputted.
Expected results:
#1. File sub-menu pops up.
#2. Data is inputted in field.
Additional info:
HEAD of F9 has same issue as well.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.