[Fedora-i18n-bugs] [Bug 488877] New: no response on xterm after switching IM
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: no response on xterm after switching IM
https://bugzilla.redhat.com/show_bug.cgi?id=488877
Summary: no response on xterm after switching IM
Product: Fedora
Version: 10
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: imsettings
AssignedTo: tagoh(a)redhat.com
ReportedBy: tagoh(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: jfrieben(a)hotmail.com, tagoh(a)redhat.com,
fedora-i18n-bugs(a)redhat.com
Depends on: 488773
Estimated Hours: 0.0
Classification: Fedora
Target Release: ---
Clone Of: 488773
To keeps an issue in summary on track separately because the root cause is
different.
+++ This bug was initially created as a clone of Bug #488773 +++
Created an attachment (id=334166)
--> (https://bugzilla.redhat.com/attachment.cgi?id=334166)
X session errors caused by enabling SCIM
Description of problem:
After updating libgxim to release 0.3.2-4.fc10, xterm shows some regression:
when running a program with a noticeable amount of text output (e.g. 'ls -R
/'), then imsettings-applet starts grabbing a significant amount of CPU share
of up to 10%. Note that SCIM is disabled at this point.
After opening GNOME menu item "Input Method" and enabling SCIM which is
disabled by default, xterm does not accept any input from the keyboard anymore
unlike gnome-terminal which continues to do so.
Version-Release number of selected component (if applicable):
libgxim-0.3.2-4.fc10.x86_64
How reproducible:
Always.
Steps to Reproduce:
1. Open GNOME session.
2. Start a program in an xterm window producing text output.
3. Run 'top' in a different window.
4. Open "Input Method" from GNOME menu and enable SCIM.
Actual results:
- Noticeable CPU load caused by imsettings-applet.
- Xterm unresponsive after enabling SCIM via "Input Method" dialog window.
Expected results:
Normal behaviour of xterm just as gnome-terminal.
Additional info:
Reverting libgxim to release 0.3.1-1.fc10 allows to restore normal operation.
--
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.
14 years, 5 months
[Fedora-i18n-bugs] [Bug 488773] New: libgxim-0.3.2-4.fc10: enabling SCIM blocks xterm and causes important CPU load
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: libgxim-0.3.2-4.fc10: enabling SCIM blocks xterm and causes important CPU load
https://bugzilla.redhat.com/show_bug.cgi?id=488773
Summary: libgxim-0.3.2-4.fc10: enabling SCIM blocks xterm and
causes important CPU load
Product: Fedora
Version: 10
Platform: x86_64
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: libgxim
AssignedTo: tagoh(a)redhat.com
ReportedBy: jfrieben(a)hotmail.com
QAContact: extras-qa(a)fedoraproject.org
CC: tagoh(a)redhat.com, fedora-i18n-bugs(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
Created an attachment (id=334166)
--> (https://bugzilla.redhat.com/attachment.cgi?id=334166)
X session errors caused by enabling SCIM
Description of problem:
After updating libgxim to release 0.3.2-4.fc10, xterm shows some regression:
when running a program with a noticeable amount of text output (e.g. 'ls -R
/'), then imsettings-applet starts grabbing a significant amount of CPU share
of up to 10%. Note that SCIM is disabled at this point.
After opening GNOME menu item "Input Method" and enabling SCIM which is
disabled by default, xterm does not accept any input from the keyboard anymore
unlike gnome-terminal which continues to do so.
Version-Release number of selected component (if applicable):
libgxim-0.3.2-4.fc10.x86_64
How reproducible:
Always.
Steps to Reproduce:
1. Open GNOME session.
2. Start a program in an xterm window producing text output.
3. Run 'top' in a different window.
4. Open "Input Method" from GNOME menu and enable SCIM.
Actual results:
- Noticeable CPU load caused by imsettings-applet.
- Xterm unresponsive after enabling SCIM via "Input Method" dialog window.
Expected results:
Normal behaviour of xterm just as gnome-terminal.
Additional info:
Reverting libgxim to release 0.3.1-1.fc10 allows to restore normal operation.
--
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.
14 years, 5 months
[Fedora-i18n-bugs] [Bug 490919] New: imsettings slows down frame rates significantly in Linux Gaming. (10-30 FPS)
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: imsettings slows down frame rates significantly in Linux Gaming. (10-30 FPS)
https://bugzilla.redhat.com/show_bug.cgi?id=490919
Summary: imsettings slows down frame rates significantly in
Linux Gaming. (10-30 FPS)
Product: Fedora
Version: 4
Platform: i386
OS/Version: Linux
Status: NEW
Severity: urgent
Priority: low
Component: imsettings
AssignedTo: tagoh(a)redhat.com
ReportedBy: nikitis(a)gmail.com
QAContact: extras-qa(a)fedoraproject.org
CC: tagoh(a)redhat.com, fedora-i18n-bugs(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
Clone Of: 488976
Description of problem: The new release of imsettings-0.105.1-4.fc10 causes
games to slowdown 10-30 Frames Per Second.
Version-Release number of selected component (if applicable):
imsettings-0.105.1-4.fc10
How reproducible: 100%
Steps to Reproduce:
1.Enter into World of Warcraft (My example), Log in.
2.Start Frames Per Second Counter (Ctrl+R)
3.Move or press any key or hold any key and frames will drop.
Actual results: The Game beings to slow down as keys are pressed or held.
Expected results: The Game should not experience any frame loss as a result of
a key press. Especially not to the degree of 10-30 FPS. Maybe only a couple
of frames maximum as the screen is processing new data when turning etc.
imsettings inside of libgxim 3.1-1 functions properly in this respect, and was
the last known working version if imsettings.
Additional info:I was working with a developer and started the bug report
488976 because of this issue, and he decided it was working well enough for an
update release. Before inside the games if you turned left, and let go, you
would continue to turn left and that wasn't supposed to happen. With
sync_on_forward set to true with new version of imsettings-0.105.1-4.fc10, that
issue is fixed however there is now a regression in the fact that there is a
Frames per second loss when a key is pressed or held which results in a very
bad gaming experience. Sometimes game slows to a crawl.
I have a GeForce 8600 GT by Nvidia, dual core intel processor at 3.0 Ghz, 4GB's
of RAM running FC10 i386. I did not experience this slowdown until
libgxim-0.3.2-4.fc10 package was released.
Starting new bug report to fix this regression.
--
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.
14 years, 5 months
[Fedora-i18n-bugs] [Bug 471927] New: imsettings causes window manager confusion in Xfce
by Red Hat Bugzilla
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.
14 years, 5 months
[Fedora-i18n-bugs] [Bug 503185] New: Can't open skk-e21.el
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: Can't open skk-e21.el
https://bugzilla.redhat.com/show_bug.cgi?id=503185
Summary: Can't open skk-e21.el
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: ddskk
AssignedTo: petersen(a)redhat.com
ReportedBy: yamato(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: petersen(a)redhat.com, fedora-i18n-bugs(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
Target Release: ---
Created an attachment (id=345907)
--> (https://bugzilla.redhat.com/attachment.cgi?id=345907)
Fixes this bug.
Description of problem:
To use ddskk(ddskk-12.2.0-12.fc11.noarch) on emacs(emacs-22.3-11.fc11.x86_64),
emacs complains "Can't find skk-e21.el".
In SKK-MK of the ddskk package , which is part of ddskk build system, the
version number of emacs is checked to decide whether skk-e21.el should be
installed or not. The SKK-MK expects emacs-21 to install skk-e21.el. However,
emacs on F11 is emacs-22. There is a gap.
Attached patch is taken from upstream skk code. In the patch mule version is
checked instead of emacs version to decide whether skk-e21.el should be
installed or not.
Version-Release number of selected component (if applicable):
ddskk-12.2.0-12.fc11.noarch
emacs-22.3-11.fc11.x86_64
How reproducible:
Steps to Reproduce:
1. install the packages.
2. emacs
3. M-x load-library: skk
Actual results:
"Can't find skk-e21.el" is messaged.
Expected results:
Skk works fine.
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.
14 years, 5 months
[Fedora-i18n-bugs] [Bug 519328] New: [ibus-chewing] inconsistent between normal mode and plain Zhuyin mode.
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: [ibus-chewing] inconsistent between normal mode and plain Zhuyin mode.
https://bugzilla.redhat.com/show_bug.cgi?id=519328
Summary: [ibus-chewing] inconsistent between normal mode and
plain Zhuyin mode.
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: ASSIGNED
Severity: medium
Priority: low
Component: ibus-chewing
AssignedTo: dchen(a)redhat.com
ReportedBy: dchen(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: phuang(a)redhat.com, dchen(a)redhat.com,
fedora-i18n-bugs(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
Target Release: ---
Description of problem:
For input sequence "ej3" (ㄍㄨ3),why the number of
candidates varies with the selection of "Plain Zhuyin mode"?
The number of candidates is 20 when "Plain Zhuyin mode" is enabled.
And the number will be 59 if the "Plain Zhuyin mode" is disabled.
Version-Release number of selected component (if applicable):
ibus-chewing-1.2.0-20090818
How reproducible:
Always
Steps to Reproduce:
1. Turn on ibus-chewing
2. Make sure "Plain Zhuyin mode" and "Use space to select" are on.
3. Type "ej3"
4. Press space to enter candidate selection mode.
5. Use space to cycle through the candidate, there are 20 candidates.
6. Clear the preedit buffer.
6. Deselect "Plain Zhuyin mode" .
3. Type "ej3"
4. Press space to enter candidate selection mode.
5. Use space to cycle through the candidate, there are 59 candidates.
Actual results:
"Plain Zhuyin mode" on: 20 candidates.
"Plain Zhuyin mode" off: 59 candidates.
Expected results:
Both of them should show 59 candidates.
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.
14 years, 6 months
[Fedora-i18n-bugs] [Bug 481156] New: S-c-language crashes while installing new language - zero division error
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: S-c-language crashes while installing new language - zero division error
https://bugzilla.redhat.com/show_bug.cgi?id=481156
Summary: S-c-language crashes while installing new language -
zero division error
Product: Fedora
Version: 10
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: system-config-language
AssignedTo: psatpute(a)redhat.com
ReportedBy: jreznik(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: psatpute(a)redhat.com, fedora-i18n-bugs(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
Target Release: ---
Description of problem: S-c-language crashes while installing new language with
traceback zero division error.
Version-Release number of selected component (if applicable):
system-config-language-1.3.2-3.fc10.noarch
How reproducible: install new language support, occurred once
Steps to Reproduce:
1. select new language, click ok
2. let new language install in the next dialog
Actual results:
Traceback (most recent call last):
File "/usr/share/system-config-language/gui_progress.py", line 101, in
callback
pct = amount/float(total)
ZeroDivisionError: float division
error: python callback <bound method GuiTransactionProgress.callback of
<gui_progress.GuiTransactionProgress instance at 0x7f0a28085200>> failed,
aborting!
Expected results:
S-c-language not crashing
--
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.
14 years, 6 months
[Fedora-i18n-bugs] [Bug 520379] New: "cups_no.po" files should be renamed to cups_nb.po
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: "cups_no.po" files should be renamed to cups_nb.po
https://bugzilla.redhat.com/show_bug.cgi?id=520379
Summary: "cups_no.po" files should be renamed to cups_nb.po
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Severity: low
Priority: low
Component: cups
AssignedTo: twaugh(a)redhat.com
ReportedBy: petersen(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: twaugh(a)redhat.com, petersen(a)redhat.com,
jmccann(a)redhat.com, rstrode(a)redhat.com,
kanarip(a)kanarip.com, psatpute(a)redhat.com,
fedora-i18n-bugs(a)redhat.com, rmaximo(a)cfl.rr.com,
jpopelka(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
Target Release: ---
Clone Of: 509753
+++ This bug was initially created as a clone of Bug #509753 +++
Description of problem:
In Norwegian, we have two written languages called 'nynorsk' and 'bokmål'. They
are both official and equal. The naming scheme shown in Fedora is inconsistent
and a bit confusing.
When I boot up my live CD, I can choose keyboard layout and system language to
use before I log in. Here you have one called 'Bokmal, Norwegian (Norge)', one
called 'Norsk (nynorsk) (Noreg)' and one just called 'Norwegian (Norway)'.
I think that showing one called just 'Norwegian (Norway)' must be wrong, as we
have two different written languages ones which both are Norwegian.
That nynorsk ('Norsk (nynorsk) (Noreg)') and bokmål ('Bokmål, Norwegian
(Norge)') has so different naming schemes is also a potentional problem.
On the English translation, I believe 'Norwegian Nynorsk (Norway)' and
'Norwegian Bokmål (Norway)' would be the best naming scheme, to keep it in line
with what the other languages are called.
--- Additional comment from psatpute(a)redhat.com on 2009-07-07 00:50:51 EDT ---
while booting anaconda shows language list
so moving bug to anaconda
--- Additional comment from clumens(a)redhat.com on 2009-07-07 10:37:19 EDT ---
The language selection on the livecd is actually provided by gdm, so moving
this bug on along.
--- Additional comment from petersen(a)redhat.com on 2009-08-31 04:50:36 EDT ---
This is not really gdm's fault.
I see current F12 carries at least two translation files for
Norwegian (ie "no_NO") from cups and grep.
So I guess the simplest solution is to rename the .po files
to Bokmål (nb).
I guess.
--
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.
14 years, 6 months
[Fedora-i18n-bugs] [Bug 520051] New: [deva] Need fontconfig rules for Samyak Devanagari font
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: [deva] Need fontconfig rules for Samyak Devanagari font
https://bugzilla.redhat.com/show_bug.cgi?id=520051
Summary: [deva] Need fontconfig rules for Samyak Devanagari
font
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: samyak-fonts
AssignedTo: psatpute(a)redhat.com
ReportedBy: pnemade(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: fedora-fonts-bugs-list(a)redhat.com,
psatpute(a)redhat.com, fedora-i18n-bugs(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
Target Release: ---
Created an attachment (id=359012)
--> (https://bugzilla.redhat.com/attachment.cgi?id=359012)
fontconfig rules for Samyak Devanagari
Description of problem:
Need to add fontspecific fontconfig rule file.
Version-Release number of selected component (if applicable):
samyak-fonts-1.2.1-6.fc12
How reproducible:
always
Steps to Reproduce:
1.
2.
3.
Actual results:
No fontconfig rule for Samyak Devanagari font
Expected results:
Should have fontconfig rule for Samayak Devanagari font
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.
14 years, 6 months