[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, 7 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, 7 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, 7 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, 7 months
[Fedora-i18n-bugs] [Bug 483181] New: msggrep segfaults when $ anchor is used
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: msggrep segfaults when $ anchor is used
https://bugzilla.redhat.com/show_bug.cgi?id=483181
Summary: msggrep segfaults when $ anchor is used
Product: Fedora
Version: 9
Platform: i686
URL: https://savannah.gnu.org/bugs/index.php?25437
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: gettext
AssignedTo: petersen(a)redhat.com
ReportedBy: sflaniga(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: ---
Description of problem:
msggrep segfaults when $ anchor is used in regex
Version-Release number of selected component (if applicable):
0.17-4.fc9
How reproducible:
About 15 out of 16 runs.
Steps to Reproduce:
1.echo a=b | msggrep -P -K -e '^a$'
Actual results:
Segmentation fault (15/16 runs) or
no matches (1/16 runs)
Expected results:
One matching string
Additional info:
May be connected to https://savannah.gnu.org/bugs/index.php?25437. (My locally
compiled gettext-0.17 doesn't segfault, but never returns the expected
matches.)
--
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, 8 months
[Fedora-i18n-bugs] [Bug 493563] New: language packages are less than upstream release
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: language packages are less than upstream release
https://bugzilla.redhat.com/show_bug.cgi?id=493563
Summary: language packages are less than upstream release
Product: Fedora
Version: 10
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: kde-l10n
AssignedTo: than(a)redhat.com
ReportedBy: aalam(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: rdieter(a)math.unl.edu, than(a)redhat.com,
kevin(a)tigcc.ticalc.org, ltinkl(a)redhat.com,
fedora-i18n-bugs(a)redhat.com, smparrish(a)gmail.com
Estimated Hours: 0.0
Classification: Fedora
Target Release: ---
Description of problem:
Our release is missing various package, where upstream released those
our build:http://koji.fedoraproject.org/koji/buildinfo?buildID=92086
Upstream: ftp://ftp.kde.org/pub/kde/stable/4.2.1/src/kde-l10n/
I have list of few packages:
Bengali India (bn-IN)
Gujarati (gu)
Kannada (kn)
Maithili (mai)
Marithi (mr)
Version-Release number of selected component (if applicable):
kde-l10n-<LANG>-4.2.1.1
How reproducible:
Steps to Reproduce:
1. search for any of above lang pack on fedora rawhide
2.
3.
Actual results:
Not Available
Expected results:
can be as upstream providing
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, 8 months
[Fedora-i18n-bugs] [Bug 468964] New: scim-python-pinyin db file too big!
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: 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.
14 years, 8 months
[Fedora-i18n-bugs] [Bug 500760] New: UI bug of "Enable input method" checkbox
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: UI bug of "Enable input method" checkbox
https://bugzilla.redhat.com/show_bug.cgi?id=500760
Summary: UI bug of "Enable input method" checkbox
Product: Fedora
Version: rawhide
Platform: i386
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: ibus-pinyin
AssignedTo: phuang(a)redhat.com
ReportedBy: lili(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: jlaska(a)redhat.com, phuang(a)redhat.com,
fedora-i18n-bugs(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
Created an attachment (id=343902)
--> (https://bugzilla.redhat.com/attachment.cgi?id=343902)
UI of ibus
Description of problem:
In"Enable input method" checkbox,some words are not clear, have some empty
string in the sentence
Version-Release number of selected component (if applicable):
How reproducible:
100%
Steps to Reproduce:
1.Choose System->Preferences->Input Method (or run im-chooser)
2. "Enable input method" checkbox pops up
3. check the UI ,see more from attached image.
Actual results:
Expected results:
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, 8 months
[Fedora-i18n-bugs] [Bug 497946] New: ibus-daemon should not fail silently
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-daemon should not fail silently
https://bugzilla.redhat.com/show_bug.cgi?id=497946
Summary: ibus-daemon should not fail silently
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: ibus
AssignedTo: phuang(a)redhat.com
ReportedBy: wtogami(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: phuang(a)redhat.com, fedora-i18n-bugs(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
Target Release: ---
ibus-1.1.0.20090423-1.fc11
Currently ibus-daemon can fail to startup under certain circumstances like
socket directory owned by another user. It currently fails silently, so the
user has no idea why it failed.
ibus-daemon should pop-up and tell the user it failed to start, and why.
ibus-daemon should probably run:
ibus-x11 --fail "fail message here"
--
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, 8 months
[Fedora-i18n-bugs] [Bug 504270] New: [Fonts-Indic][te_IN] - GSUB shape with SSA and HA are wrong.
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: [Fonts-Indic][te_IN] - GSUB shape with SSA and HA are wrong.
https://bugzilla.redhat.com/show_bug.cgi?id=504270
Summary: [Fonts-Indic][te_IN] - GSUB shape with SSA and HA are
wrong.
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Keywords: i18n
Severity: medium
Priority: low
Component: fonts-indic
AssignedTo: rbhalera(a)redhat.com
ReportedBy: smaitra(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: smaitra(a)redhat.com, rbhalera(a)redhat.com,
fedora-fonts-bugs-list(a)redhat.com,
fedora-i18n-bugs(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
Target Release: ---
Description of problem:
GSUB shape with SSA (0C37) and HA (0C39) is showing wrong in the font.
Its positioning for the lower part of the composed character, should be
below-right aligned which is now aligned as below-middle.
As of now The Image that is given to our Internal web page, is hand drawn and
partly wrong also. But, the lower part alignment is Perfect there which is
showing right-aligned.
These specific Combinations are given below :
68. U+0C24 U+0C4D U+0C37 త్ష TA + HALANT + SSA => In image main character
must be corrected as in font and in font the position of sub character(which is
at the bottom) should be corrected as in image.
70. U+0C24 U+0C4D U+0C39 త్హ TA + HALANT + HA => In image main character must
be corrected as in font and in font the position of sub character(which is at
the bottom) should be corrected as in image.
103. U+0C28 U+0C4D U+0C37 న్ష NA + HALANT + SSA => In image main character
must be corrected as in font and in font the position of sub character(which is
at the bottom) should be corrected as in image.
105. U+0C28 U+0C4D U+0C39 న్హ NA + HALANT + HA => In image main character
must be corrected as in font and in font the position of sub character(which is
at the bottom) should be corrected as in image.
140. U+0C2E U+0C4D U+0C39 మ్హ MA + HALANT + HA => In image main character
must be corrected as in font and in font the position of sub character(which is
at the bottom) should be corrected as in image.
175. U+0C2F U+0C4D U+0C39 య్హ YA + HALANT + HA => In image main character
must be corrected as in font and in font the position of sub character(which is
at the bottom) should be corrected as in image.
208. U+0C30 U+0C4D U+0C37 ర్ష RA + HALANT + SSA => In image main character
must be corrected as in font and in font the position of sub character(which is
at the bottom) should be corrected as in image.
210. U+0C30 U+0C4D U+0C39 ర్హ RA + HALANT + HA => In image main character
must be corrected as in font and in font the position of sub character(which is
at the bottom) should be corrected as in image.
243. U+0C32 U+0C4D U+0C37 ల్ష LA + HALANT + SSA => In image main character
must be corrected as in font and in font the position of sub character(which is
at the bottom) should be corrected as in image.
245. U+0C32 U+0C4D U+0C39 ల్హ LA + HALANT + HA => In image main character
must be corrected as in font and in font the position of sub character(which is
at the bottom) should be corrected as in image.
278. U+0C35 U+0C4D U+0C37 వ్ష VA + HALANT + SSA => In image main character
must be corrected as in font and in font the position of sub character(which is
at the bottom) should be corrected as in image.
280. U+0C35 U+0C4D U+0C39 వ్హ VA + HALANT + HA => In image main character
must be corrected as in font and in font the position of sub character(which is
at the bottom) should be corrected as in image.
Version-Release number of selected component (if applicable):
lohit-telugu-fonts-2.3.8-1.fc11
How reproducible:
Always
Steps to Reproduce:
1. Start system with FC11 or Latest
2. Change the ibus with RAWCODE
3. Open Gedit
4. Type the combination's Unicode as given above.
5. Observe the lower part of the composed character.
Actual results:
Its showing below-middle alignment.
Expected results:
It should be below-right alignment.
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, 8 months