[Fedora-i18n-bugs] [Bug 484536] New: various smc-fonts have wrong default glyphs
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: various smc-fonts have wrong default glyphs
https://bugzilla.redhat.com/show_bug.cgi?id=484536
Summary: various smc-fonts have wrong default glyphs
Product: Fedora
Version: rawhide
Platform: All
OS/Version: All
Status: NEW
Severity: medium
Priority: low
Component: smc-fonts
AssignedTo: psatpute(a)redhat.com
ReportedBy: roozbeh(a)gmail.com
QAContact: extras-qa(a)fedoraproject.org
CC: fedora-fonts-bugs-list(a)redhat.com,
psatpute(a)redhat.com, rajeeshknambiar(a)gmail.com,
fedora-i18n-bugs(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
Various fonts in the smc-fonts package, especially smc-fonts-meera, which is
installed on every Fedora machine because of being being "default" in compts,
have default glyphs shaped like an R in circle for some Malayalam characters.
For example, Meera has the following default glyphs in places that it should
not have: U+0D44, U+0D62, U+0D63, U+0D71, U+0D72, U+0D73, U+0D74, U+0D79,
U+0D7A, U+0D7B U+0D7C, U+0D7D, U+0D7E, U+0D7F
Also, there are several default glyphs in places that Unicode may use for
future encoding of Malayalam characters, like U+0D00 and U+0D29.
All those R in cirlces should be removed from the font, to make the font
Unicode-complying. Alternatively, Meera can be replaced by a standard font.
--
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, 2 months
[Fedora-i18n-bugs] [Bug 484621] New: culmus-fonts needs compat package for upgrades
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: culmus-fonts needs compat package for upgrades
https://bugzilla.redhat.com/show_bug.cgi?id=484621
Summary: culmus-fonts needs compat package for upgrades
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: culmus-fonts
AssignedTo: rbhalera(a)redhat.com
ReportedBy: petersen(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: petersen(a)redhat.com, rbhalera(a)redhat.com,
fedora-i18n-bugs(a)redhat.com
Blocks: 446451
Estimated Hours: 0.0
Classification: Fedora
Target Release: ---
Description of problem:
Since culmus-fonts has now been subpackaged for F11 it needs a compat
subpackage for smooth updating from F10, etc.
Version-Release number of selected component (if applicable):
culmus-fonts-0.102-1.fc11
Actual results:
No culmus-fonts-compat so can't upgrade.
Expected results:
culmus-fonts-compat which obsoletes previous culmus-fonts correctly.
Additional info:
http://fedoraproject.org/wiki/Packaging/NamingGuidelines#Renaming.2Frepla...
--
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, 2 months
[Fedora-i18n-bugs] [Bug 473665] New: scim-python : Unowned directories
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 : 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#FileAndDirectoryOwner...
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.
14 years, 3 months
[Fedora-i18n-bugs] [Bug 513258] New: Freeze on start
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: Freeze on start
https://bugzilla.redhat.com/show_bug.cgi?id=513258
Summary: Freeze on start
Product: Fedora
Version: 11
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: stardict
AssignedTo: cchance(a)redhat.com
ReportedBy: pahan(a)hubbitus.info
QAContact: extras-qa(a)fedoraproject.org
CC: cchance(a)redhat.com, zhu(a)redhat.com,
fedora-i18n-bugs(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
Description of problem:
Stardict start loading, splash screen appeared and then freezes. This splash
don't disappeared anymore and nothing happened too,
I think strace information may be useful there:
$ strace stardict 2>&1
[many sniped]
fcntl64(25, F_SETFD, FD_CLOEXEC) = 0
mmap2(NULL, 10489856, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_ANONYMOUS|MAP_STACK, -1, 0) = 0xb3183000
mprotect(0xb3183000, 4096, PROT_NONE) = 0
clone(child_stack=0xb3b833d4,
flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CLONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID,
parent_tidptr=0xb3b83bd8, {entry_number:6, base_addr:0xb3b83b70, limit:1048575,
seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:1, seg_not_present:0,
useable:1}, child_tidptr=0xb3b83bd8) = 25804
fcntl64(24, F_GETFL) = 0x2 (flags O_RDWR)
fcntl64(24, F_SETFL, O_RDWR|O_NONBLOCK) = 0
send(23,
"\0\0\0\0\0\0\0\0007\0\0\0\0\0\0\0\0\0\0\0\2\0\0\0\1\0\0\0\0\0\0\0\n"..., 55,
MSG_NOSIGNAL) = 55
gettimeofday({1248284635, 243627}, NULL) = 0
mmap2(NULL, 10489856, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_ANONYMOUS|MAP_STACK, -1, 0) = 0xb25ff000
mprotect(0xb25ff000, 4096, PROT_NONE) = 0
clone(child_stack=0xb2fff3d4,
flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CLONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID,
parent_tidptr=0xb2fffbd8, {entry_number:6, base_addr:0xb2fffb70, limit:1048575,
seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:1, seg_not_present:0,
useable:1}, child_tidptr=0xb2fffbd8) = 25805
futex(0x8482ff0, FUTEX_UNLOCK_PI_PRIVATE, 13299700) = 0
futex(0x8483014, FUTEX_WAIT_PRIVATE, 1, NULL) = ? ERESTARTSYS (To be restarted)
--- SIGCHLD (Child exited) @ 0 (0) ---
futex(0x8483014, FUTEX_WAIT_PRIVATE, 1, NULL) = 0
futex(0x8482ff0, FUTEX_LOCK_PI_PRIVATE, 1) = 0
send(21, "W"..., 1, MSG_NOSIGNAL) = -1 ENOTSOCK (Socket operation on
non-socket)
write(21, "W"..., 1) = 1
futex(0xb2fffbd8, FUTEX_WAIT, 25805, NULL
So very spurious seems child die and then unlimited wait some futex.
Version-Release number of selected component (if applicable):
$ rpm -q stardict
stardict-3.0.1-17.fc11.i586
How reproducible:
Always
--
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, 3 months
[Fedora-i18n-bugs] [Bug 507794] New: S-c-tools cleanup: add uninstall support - suggestion
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-tools cleanup: add uninstall support - suggestion
https://bugzilla.redhat.com/show_bug.cgi?id=507794
Summary: S-c-tools cleanup: add uninstall support - suggestion
Product: Fedora
Version: rawhide
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: there's no possibility for user to uninstall language
support installed by s-c-language.
Actual results:
User can't uninstall language support installed by this tool.
Expected results:
User can uninstall language support installed by this tool.
Additional info:
This bug report is part of "System Configuration Tools Cleanup Project". Don't
hesitate to ask project maintainers for any kind of help.
--
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, 3 months
[Fedora-i18n-bugs] [Bug 513895] New: new IME does not show up in ibus-setup
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: new IME does not show up in ibus-setup
https://bugzilla.redhat.com/show_bug.cgi?id=513895
Summary: new IME does not show up in ibus-setup
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: ibus
AssignedTo: phuang(a)redhat.com
ReportedBy: petersen(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: ---
Description of problem:
When I install a new IME it does not show up immediately in ibus-setup.
Version-Release number of selected component (if applicable):
ibus-1.1.0.20090612-1.fc11
How reproducible:
every time
Steps to Reproduce:
1. yum install ibus-chewing
2. run ibus-setup to add chewing IME
Actual results:
2. Chewing IME does not appear in the list of IMEs.
Expected results:
2. Chewing IME to be available without restarting ibus.
--
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, 3 months
[Fedora-i18n-bugs] [Bug 465392] New: race condition in XIM handling
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: 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.
14 years, 4 months
[Fedora-i18n-bugs] [Bug 475904] New: no sound in startdict
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 sound in startdict
https://bugzilla.redhat.com/show_bug.cgi?id=475904
Summary: no sound in startdict
Product: Fedora
Version: 10
Platform: i386
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: stardict
AssignedTo: cchance(a)redhat.com
ReportedBy: jianliang79(a)gmail.com
QAContact: extras-qa(a)fedoraproject.org
CC: cchance(a)redhat.com, zhu(a)redhat.com,
fedora-i18n-bugs(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
Description of problem:
I have installed WyabdcRealPeopleTTS sound library but stardict can't read
words for me. Another abnormal thing about sound is that now I can't even hear
the sound when the mouse pointer entering the buttons of stardict. I remember
in the previous version I can hear a little sound when the mouse pointer
entering one of the button of stardict.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
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, 4 months
[Fedora-i18n-bugs] [Bug 501665] New: [mai_IN] No input method available in KDE applications
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: [mai_IN] No input method available in KDE applications
https://bugzilla.redhat.com/show_bug.cgi?id=501665
Summary: [mai_IN] No input method available in KDE applications
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: ibus
AssignedTo: phuang(a)redhat.com
ReportedBy: pnemade(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: ---
Description of problem:
When started KDE in mai_IN, no input method available.
Version-Release number of selected component (if applicable):
ibus-1.1.0.20090508-3.fc11.x86_64
How reproducible:
always
Steps to Reproduce:
1.Start KDE in mai_IN
2.open kwrite/kate
3. unable to input
Actual results:
unable to input in KDE in mai_IN locale
Expected results:
Should be able to input in KDE in mai_IN locale
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, 4 months