[Fedora-i18n-bugs] [Bug 477690] New: libchewing multilib conflict
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: libchewing multilib conflict
https://bugzilla.redhat.com/show_bug.cgi?id=477690
Summary: libchewing multilib conflict
Product: Fedora
Version: 10
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: libchewing
AssignedTo: dchen(a)redhat.com
ReportedBy: phil(a)fifi.org
QAContact: extras-qa(a)fedoraproject.org
CC: dchen(a)redhat.com, fedora-i18n-bugs(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
Description of problem:
yum install libchewing.i386 libchewing.x86_64
yeilds:
file /usr/share/chewing/fonetree.dat from install of
libchewing-0.3.2-0.fc10.i386 conflicts with file from package
libchewing-0.3.2-0.fc10.x86_64
Version-Release number of selected component (if applicable):
libchewing-0.3.2-0.fc10
--
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.
11 years, 8 months
[Fedora-i18n-bugs] [Bug 517789] New: Droid Sans overrides default Japanese desktop 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: Droid Sans overrides default Japanese desktop font
https://bugzilla.redhat.com/show_bug.cgi?id=517789
Summary: Droid Sans overrides default Japanese desktop font
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: google-droid-fonts
AssignedTo: nicolas.mailhot(a)laposte.net
ReportedBy: petersen(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: nicolas.mailhot(a)laposte.net,
fedora-fonts-bugs-list(a)redhat.com,
fedora-i18n-bugs(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
Target Release: ---
Description of problem:
I was just testing a f12alpha spin and discovered that Droid Sans
seems to override the default Japanese desktop font.
How reproducible:
every time
Steps to Reproduce:
1. yum install google-droid-sans-fonts
2. login to gnome desktop
3. run gucharmap
Actual results:
Most kanji glyphs are shown with Droid Sans.
Expected results:
Default Japanese IPA font to be used for Japanese characters.
Additional info:
Not sure why the Droid fonts were pulled into the spin.
This affects whole Japanese desktop and gdm, etc.
--
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.
11 years, 8 months
[Fedora-i18n-bugs] [Bug 528140] New: [hi_IN][ta_IN] TimeZone in Clock is Boston by default
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: [hi_IN][ta_IN] TimeZone in Clock is Boston by default
https://bugzilla.redhat.com/show_bug.cgi?id=528140
Summary: [hi_IN][ta_IN] TimeZone in Clock is Boston by default
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Keywords: i18n
Severity: medium
Priority: low
Component: gnome-panel
AssignedTo: rstrode(a)redhat.com
ReportedBy: aalam(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: rstrode(a)redhat.com, fedora-i18n-bugs(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
Target Release: ---
Created an attachment (id=364235)
--> (https://bugzilla.redhat.com/attachment.cgi?id=364235)
Screenshot for s-c-date and gnome-clock
Description of problem:
After installation and setting Default Timezone Kolkata, Clock is showing
Default Timezone (added by Default) Boston (after Fresh installation).
Version-Release number of selected component (if applicable):
gnome-panel-2.28.0-2.fc12.x86_64
system-config-date-1.9.52-1.fc12.noarch
libgweather-2.28.0-1.fc12.x86_64
How reproducible:
Everytime
Steps to Reproduce:
1. fresh install with Hindi (hi_IN) locale
2. login with Hindi
3. Click on clock/Task Top-Right Side
Actual results:
Boston is added by Default
Expected results:
Either should be default for locale or s-c-date's Zone
Additional info:
Screenshot
--
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.
11 years, 8 months
[Fedora-i18n-bugs] [Bug 498706] New: Key bindings don't work after restart
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: Key bindings don't work after restart
https://bugzilla.redhat.com/show_bug.cgi?id=498706
Summary: Key bindings don't work after restart
Product: Fedora
Version: 9
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 save keybindings, but its do not work after restart and require reset
it after each boot.
Version-Release number of selected component (if applicable):
# rpm -q stardict
stardict-3.0.1-9.fc9.i386
How reproducible:
Stardict load after boot by any DE (or restored within session). Go to
Preferencies, setup Modifier with wich scan will be doing. Close setting
window.
After that all work fine in this session. After restart computer, scan window
do not appear when defined keys pressed. But, when going into preferencies,
defined keys saved (sic!) and start working just after close window without any
manipulations with it!
--
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.
11 years, 9 months
[Fedora-i18n-bugs] [Bug 651263] New: [abrt] stardict-3.0.1-22.fc14: Process /usr/bin/stardict was killed by signal 6 (SIGABRT)
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: [abrt] stardict-3.0.1-22.fc14: Process /usr/bin/stardict was killed by signal 6 (SIGABRT)
https://bugzilla.redhat.com/show_bug.cgi?id=651263
Summary: [abrt] stardict-3.0.1-22.fc14: Process
/usr/bin/stardict was killed by signal 6 (SIGABRT)
Product: Fedora
Version: 14
Platform: i686
OS/Version: Unspecified
Status: NEW
Status Whiteboard: abrt_hash:de3000b4d6701d07ee141c36ab0911d18698121c
Severity: medium
Priority: low
Component: stardict
AssignedTo: dchen(a)redhat.com
ReportedBy: maamoun4188(a)live.fr
QAContact: extras-qa(a)fedoraproject.org
CC: zhu(a)redhat.com, dchen(a)redhat.com,
i18n-bugs(a)lists.fedoraproject.org,
supercyper1(a)gmail.com
Classification: Fedora
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: stardict
component: stardict
executable: /usr/bin/stardict
kernel: 2.6.35.6-48.fc14.i686
package: stardict-3.0.1-22.fc14
reason: Process /usr/bin/stardict was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1289269328
uid: 500
--
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.
11 years, 9 months
[Fedora-i18n-bugs] [Bug 586763] New: smc-dyuthi-fonts isn't usable
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: smc-dyuthi-fonts isn't usable
https://bugzilla.redhat.com/show_bug.cgi?id=586763
Summary: smc-dyuthi-fonts isn't usable
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: madan-fonts
AssignedTo: pnemade(a)redhat.com
ReportedBy: tagoh(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: petersen(a)redhat.com, pnemade(a)redhat.com,
psatpute(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org
Classification: Fedora
Target Release: ---
Description of problem:
madan-fonts is supposed to work for Nepali font though, it doesn't have enough
glyph coverage in fontconfig.
Version-Release number of selected component (if applicable):
madan-fonts-2.000-2.fc13.noarch
How reproducible:
always
Steps to Reproduce:
1.fc-match -v "Madan"|grep -E " lang"|grep ne
2.
3.
Actual results:
No output
Expected results:
the lang spec should contains ne.
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.
11 years, 10 months
[Fedora-i18n-bugs] [Bug 649624] New: [abrt] translate-toolkit-1.8.0-1.fc13: __init__.py:1596:start:error: [Errno 98] Address already in use
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: [abrt] translate-toolkit-1.8.0-1.fc13: __init__.py:1596:start:error: [Errno 98] Address already in use
https://bugzilla.redhat.com/show_bug.cgi?id=649624
Summary: [abrt] translate-toolkit-1.8.0-1.fc13:
__init__.py:1596:start:error: [Errno 98] Address
already in use
Product: Fedora
Version: 13
Platform: x86_64
OS/Version: Unspecified
Status: NEW
Status Whiteboard: abrt_hash:a4a09b6e
Severity: medium
Priority: low
Component: translate-toolkit
AssignedTo: dwayne(a)translate.org.za
ReportedBy: dtdraganov(a)yahoo.com
QAContact: extras-qa(a)fedoraproject.org
CC: dwayne(a)translate.org.za,
i18n-bugs(a)lists.fedoraproject.org
Classification: Fedora
abrt version: 1.1.13
architecture: x86_64
component: translate-toolkit
executable: /usr/bin/tmserver
kernel: 2.6.34.7-61.fc13.x86_64
package: translate-toolkit-1.8.0-1.fc13
reason: __init__.py:1596:start:error: [Errno 98] Address already in use
release: Fedora release 13 (Goddard)
time: 1288852184
uid: 500
backtrace
-----
__init__.py:1596:start:error: [Errno 98] Address already in use
Traceback (most recent call last):
File "/usr/bin/tmserver", line 27, in <module>
tmserver.main()
File "/usr/lib/python2.6/site-packages/translate/services/tmserver.py", line
195, in main
wsgi.launch_server(options.bind, options.port, application.rest)
File "/usr/lib/python2.6/site-packages/translate/misc/wsgi.py", line 84, in
launch_server
server(host, port, app)
File "/usr/lib/python2.6/site-packages/translate/misc/wsgi.py", line 72, in
launch_server_cherrypy
server.start()
File "/usr/lib/python2.6/site-packages/cherrypy/wsgiserver/__init__.py", line
1596, in start
raise socket.error, msg
error: [Errno 98] Address already in use
Local variables in innermost frame:
info: [(2, 1, 6, '', ('127.0.0.1', 55555))]
af: 2
canonname: ''
self: <cherrypy.wsgiserver.CherryPyWSGIServer object at 0x1b96050>
proto: 6
msg: error(98, 'Address already in use')
host: 'localhost'
res: (2, 1, 6, '', ('127.0.0.1', 55555))
socktype: 1
sa: ('127.0.0.1', 55555)
port: 55555
--
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.
11 years, 10 months
[Fedora-i18n-bugs] [Bug 668660] New: [abrt] fcitx-3.6.3-6.20100602svn_utf8.fc14: strcat: Process /usr/bin/fcitx was killed by signal 6 (SIGABRT)
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: [abrt] fcitx-3.6.3-6.20100602svn_utf8.fc14: strcat: Process /usr/bin/fcitx was killed by signal 6 (SIGABRT)
https://bugzilla.redhat.com/show_bug.cgi?id=668660
Summary: [abrt] fcitx-3.6.3-6.20100602svn_utf8.fc14: strcat:
Process /usr/bin/fcitx was killed by signal 6
(SIGABRT)
Product: Fedora
Version: 14
Platform: x86_64
OS/Version: Unspecified
Status: NEW
Status Whiteboard: abrt_hash:e00bc6b6b57ae100edee55871c72747025495092
Severity: medium
Priority: low
Component: fcitx
AssignedTo: supercyper1(a)gmail.com
ReportedBy: zchen22(a)gmail.com
QAContact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org,
liangsuilong(a)gmail.com, robinlee.sysu(a)gmail.com,
supercyper1(a)gmail.com
Classification: Fedora
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/fcitx -D
component: fcitx
crash_function: strcat
executable: /usr/bin/fcitx
kernel: 2.6.35.10-74.fc14.x86_64
package: fcitx-3.6.3-6.20100602svn_utf8.fc14
rating: 4
reason: Process /usr/bin/fcitx was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1294727665
uid: 500
How to reproduce
-----
1. typing a number of characters
2.
3.
--
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.
11 years, 10 months
[Fedora-i18n-bugs] [Bug 677932] New: [abrt] translate-toolkit-1.8.1-1.fc14: tmdb.py:116:init_database:OperationalError: database schema has changed
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: [abrt] translate-toolkit-1.8.1-1.fc14: tmdb.py:116:init_database:OperationalError: database schema has changed
https://bugzilla.redhat.com/show_bug.cgi?id=677932
Summary: [abrt] translate-toolkit-1.8.1-1.fc14:
tmdb.py:116:init_database:OperationalError: database
schema has changed
Product: Fedora
Version: 14
Platform: x86_64
OS/Version: Unspecified
Status: NEW
Status Whiteboard: abrt_hash:bdc77e95
Severity: unspecified
Priority: unspecified
Component: translate-toolkit
AssignedTo: dwayne(a)translate.org.za
ReportedBy: davematel(a)gmail.com
QAContact: extras-qa(a)fedoraproject.org
CC: dwayne(a)translate.org.za,
i18n-bugs(a)lists.fedoraproject.org
Classification: Fedora
abrt version: 1.1.14
architecture: x86_64
cmdline: /usr/bin/python /usr/bin/tmserver -b localhost -p 55555 -d
/home/DaveMatel8888/.virtaal/tm.db --min-similarity=70 --max-candidates=5
component: translate-toolkit
executable: /usr/bin/tmserver
kernel: 2.6.35.10-74.fc14.x86_64
package: translate-toolkit-1.8.1-1.fc14
reason: tmdb.py:116:init_database:OperationalError: database schema has changed
release: Fedora release 14 (Laughlin)
time: 1296137039
uid: 500
backtrace
-----
tmdb.py:116:init_database:OperationalError: database schema has changed
Traceback (most recent call last):
File "/usr/bin/tmserver", line 27, in <module>
tmserver.main()
File "/usr/lib/python2.7/site-packages/translate/services/tmserver.py", line
194, in main
prefix="/tmserver", source_lang=options.source_lang,
target_lang=options.target_lang)
File "/usr/lib/python2.7/site-packages/translate/services/tmserver.py", line
49, in __init__
self.tmdb = tmdb.TMDB(tmdbfile, max_candidates, min_similarity, max_length)
File "/usr/lib/python2.7/site-packages/translate/storage/tmdb.py", line 66,
in __init__
self.init_database()
File "/usr/lib/python2.7/site-packages/translate/storage/tmdb.py", line 116,
in init_database
self.cursor.executescript(script)
OperationalError: database schema has changed
Local variables in innermost frame:
self: <translate.storage.tmdb.TMDB object at 0x26ba090>
script: '\nCREATE TABLE IF NOT EXISTS sources (\n sid INTEGER PRIMARY KEY
AUTOINCREMENT,\n text VARCHAR NOT NULL,\n context VARCHAR DEFAULT
NULL,\n lang VARCHAR NOT NULL,\n length INTEGER NOT
NULL\n);\nCREATE INDEX IF NOT EXISTS sources_context_idx ON sources
(context);\nCREATE INDEX IF NOT EXISTS sources_lang_idx ON sources
(lang);\nCREATE INDEX IF NOT EXISTS sources_length_idx ON sources
(length);\nCREATE UNIQUE INDEX IF NOT EXISTS sources_uniq_idx ON sources (text,
context, lang);\n\nCREATE TABLE IF NOT EXISTS targets (\n tid INTEGER
PRIMARY KEY AUTOINCREMENT,\n sid INTEGER NOT NULL,\n text VARCHAR
NOT NULL,\n lang VARCHAR NOT NULL,\n time INTEGER DEFAULT NULL,\n
FOREIGN KEY (sid) references sources(sid)\n);\nCREATE INDEX IF NOT EXISTS
targets_sid_idx ON targets (sid);\nCREATE INDEX IF NOT EXISTS targets_lang_idx
ON targets (lang);\nCREATE INDEX IF NOT EXISTS targets_time_idx ON targets
(time);\nCREATE UNIQUE INDEX IF NOT EXISTS targets_uniq_idx ON targets (sid,
text, lang);\n'
How to reproduce
-----
1.just errered on its own
2.
3.
--
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.
11 years, 10 months
[Fedora-i18n-bugs] [Bug 678707] New: [abrt] uim-gtk2-1.6.1-1.fc14: symbol_name_hash: Process /usr/bin/uim-im-switcher-gtk was killed by signal 11 (SIGSEGV)
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: [abrt] uim-gtk2-1.6.1-1.fc14: symbol_name_hash: Process /usr/bin/uim-im-switcher-gtk was killed by signal 11 (SIGSEGV)
https://bugzilla.redhat.com/show_bug.cgi?id=678707
Summary: [abrt] uim-gtk2-1.6.1-1.fc14: symbol_name_hash:
Process /usr/bin/uim-im-switcher-gtk was killed by
signal 11 (SIGSEGV)
Product: Fedora
Version: 14
Platform: i686
OS/Version: Unspecified
Status: NEW
Status Whiteboard: abrt_hash:fa6ec9c30bcfc058c94ae6d55b676c0ec49c67ca
Severity: unspecified
Priority: unspecified
Component: uim
AssignedTo: tagoh(a)redhat.com
ReportedBy: amreg.redhat(a)free.fr
QAContact: extras-qa(a)fedoraproject.org
CC: tagoh(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org
Classification: Fedora
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 21271 bytes
cmdline: uim-im-switcher-gtk
component: uim
Attached file: coredump, 12046336 bytes
crash_function: symbol_name_hash
executable: /usr/bin/uim-im-switcher-gtk
kernel: 2.6.35.11-83.fc14.i686
package: uim-gtk2-1.6.1-1.fc14
rating: 4
reason: Process /usr/bin/uim-im-switcher-gtk was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1298067354
uid: 500
How to reproduce
-----
1. Trying to switch to uim-anthy via shortcut key to input (in romaji) a
japanese word I found in a book into kiten application, in order to find a
translation.
2.
3.
--
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.
11 years, 10 months