[Fedora-i18n-bugs] [Bug 696476] New: [bn][bn-IN]Combinations with Consonant+09CB+special characters fail on Openoffice.org writer
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: [bn][bn-IN]Combinations with Consonant+09CB+special characters fail on Openoffice.org writer
https://bugzilla.redhat.com/show_bug.cgi?id=696476
Summary: [bn][bn-IN]Combinations with Consonant+09CB+special
characters fail on Openoffice.org writer
Product: Fedora
Version: 14
Platform: Unspecified
OS/Version: Unspecified
Status: NEW
Severity: unspecified
Priority: unspecified
Component: ibus
AssignedTo: tfujiwar(a)redhat.com
ReportedBy: runab(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: tfujiwar(a)redhat.com,
i18n-bugs(a)lists.fedoraproject.org,
shawn.p.huang(a)gmail.com
Classification: Fedora
Story Points: ---
Description of problem:
Combinations with various Bengali consonant characters (0995-09B9)+09CB+special
characters (0981-0983) cause Openoffice.org writer to crash unexpectedly, after
ibus, ibus-libs, ibus-gtk2, ibus-gtk3 packages are updated.
Version-Release number of selected component (if applicable):
openoffice.org-writer-3.3.0-9.3.fc14
ibus-libs-1.3.9-3.fc14
ibus-gtk2-1.3.9-3.fc14
ibus-1.3.9-3.fc14
ibus-gtk3-1.3.9-3.fc14
How reproducible:
Steps to Reproduce:
1. Add Bengali=>Probhat and Inscript keyboards from ibus-preferences to enable
them
2. Start openoffice.org writer
3. Enable Probhat keyboard by choosing it from the ibus panel applet
4. Write the following combination:
* 099C + 09CB + 0981
actual key strokes: j]>
to display: জোঁ
* 0995 + 09CB + 0982
actual key strokes: k]L
to display: কোং
* 09B9 + 09CB + 0983
actual key strokes: h]H
to display: হোঃ
Actual results:
Openoffice.org writer crashes
Expected results:
Combinations to be displayed and application should not crash.
Additional info:
1. The bug can be replicated with direct unicode input as well
2. The consonant value can be replaced with any in the range, and same results
are seen. The special character may or may not be different in each case.
3. With no change in the Openoffice.org (and its dependency) packages, these
combinations worked as expected on the ibus GA versions (1.3.9-3.fc14)
--
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 707100] New: after upgrade from F14->F15, firefox run in English, when desktop is in native locale (pa_IN)
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: after upgrade from F14->F15, firefox run in English, when desktop is in native locale (pa_IN)
https://bugzilla.redhat.com/show_bug.cgi?id=707100
Summary: after upgrade from F14->F15, firefox run in English,
when desktop is in native locale (pa_IN)
Product: Fedora
Version: 15
Platform: Unspecified
OS/Version: Unspecified
Status: NEW
Keywords: i18n
Severity: unspecified
Priority: unspecified
Component: firefox
AssignedTo: gecko-bugs-nobody(a)fedoraproject.org
ReportedBy: aalam(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: gecko-bugs-nobody(a)fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org
Classification: Fedora
Story Points: ---
Description of problem:
after upgrade from F14->F15, firefox run in English, when desktop is in native
locale (pa_IN).
Version-Release number of selected component (if applicable):
firefox-4.0.1-2.fc15.x86_64
xulrunner-2.0.1-1.fc15.x86_64
How reproducible:
everytime
Steps to Reproduce:
1. upgraded from Fedora 14 to Fedora 15, where Fedra 14 has Native Desktop
(Punjabi)
2. after upgrade run Firefox
3. check interface
Actual results:
it is in English
Expected results:
it should be in Punjabi
Additional info:
1) Fresh install is working Proper (in native locale)
2) [aalam@amd6core ~]$ locale
LANG=pa_IN.UTF-8
LC_CTYPE="pa_IN.UTF-8"
LC_NUMERIC="pa_IN.UTF-8"
LC_TIME="pa_IN.UTF-8"
LC_COLLATE="pa_IN.UTF-8"
LC_MONETARY="pa_IN.UTF-8"
LC_MESSAGES="pa_IN.UTF-8"
LC_PAPER="pa_IN.UTF-8"
LC_NAME="pa_IN.UTF-8"
LC_ADDRESS="pa_IN.UTF-8"
LC_TELEPHONE="pa_IN.UTF-8"
LC_MEASUREMENT="pa_IN.UTF-8"
LC_IDENTIFICATION="pa_IN.UTF-8"
LC_ALL=
--------
[aalam@amd6core ~]$ ls
/usr/lib64/firefox-4/langpacks/langpack-pa-IN\(a)firefox.mozilla.org.xpi
---
--
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 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, 10 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, 10 months
[Fedora-i18n-bugs] [Bug 700662] New: [abrt] imsettings-1.2.2-1.fc15: g_variant_type_info_check: Process /usr/libexec/imsettings-daemon 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] imsettings-1.2.2-1.fc15: g_variant_type_info_check: Process /usr/libexec/imsettings-daemon was killed by signal 6 (SIGABRT)
https://bugzilla.redhat.com/show_bug.cgi?id=700662
Summary: [abrt] imsettings-1.2.2-1.fc15:
g_variant_type_info_check: Process
/usr/libexec/imsettings-daemon was killed by signal 6
(SIGABRT)
Product: Fedora
Version: 15
Platform: i686
OS/Version: Unspecified
Status: NEW
Status Whiteboard: abrt_hash:7440faa7c953000a0183d65a7e9e94868ef7e271
Severity: unspecified
Priority: unspecified
Component: imsettings
AssignedTo: tagoh(a)redhat.com
ReportedBy: jussi.eloranta(a)csun.edu
QAContact: extras-qa(a)fedoraproject.org
CC: tagoh(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org
Classification: Fedora
Story Points: ---
abrt version: 2.0.1
comment: system startup and login (xfce)
executable: /usr/libexec/imsettings-daemon
cmdline: /usr/libexec/imsettings-daemon
component: imsettings
package: imsettings-1.2.2-1.fc15
kernel: 2.6.38.3-18.fc15.i686.PAE
crash_function: g_variant_type_info_check
reason: Process /usr/libexec/imsettings-daemon was killed by signal 6 (SIGABRT)
uid: 500
architecture: i686
username: eloranta
os_release: Fedora release 15 (Lovelock)
time: 1304005728
rating: 4
Text file: event_log, 20473 bytes
Text file: maps, 7588 bytes
Binary file: coredump, 17903616 bytes
Text file: dsos, 6502 bytes
Text file: backtrace, 13908 bytes
environ
-----
SHELL=/bin/tcsh
DBUS_STARTER_ADDRESS=unix:abstract=/tmp/dbus-PGylbtm8H8,guid=d59d9b7d14897b105778abbf00000092
XDG_SESSION_COOKIE=ee9fdef512c9d271eab4a29700000007-1304005727.450166-424493650
XDG_RUNTIME_DIR=/run/user/eloranta
DISPLAY=:0
DESKTOP_SESSION=xfce
WINDOWPATH=7
PATH=/usr/local/bin:/usr/bin:/bin
GDMSESSION=xfce
USERNAME=eloranta
XDG_SESSION_ID=4
DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-PGylbtm8H8,guid=d59d9b7d14897b105778abbf00000092
XAUTHORITY=/var/run/gdm/auth-for-eloranta-GXv3R2/database
USER=eloranta
DBUS_STARTER_BUS_TYPE=session
GNOME_KEYRING_PID=2394
SHLVL=1
PWD=/home/eloranta
GDM_LANG=
GNOME_KEYRING_CONTROL=/tmp/keyring-fjVPIw
LANG=en_US.UTF-8
_=/usr/bin/dbus-launch
LOGNAME=eloranta
HOME=/home/eloranta
build_ids
-----
e059d57b917964c7ff204ba5472454221b6af2d3
7a79a1582581d1bb8ea720be0ea02ab0c39565ef
c16193cfe3eb02dc1d2451177325f25a02ce714e
4f246402bc5efc60b6397798257580d1fb549856
9ab1595028e3421e37442d01b1147b7717d9616b
feaad496c95c4960f08a77a17e68255f910ffa46
b9a366d75242dddd9d6643cfa18bc7150298a677
9b74e05fa75cf73df1da0c05a7b1528f0ec8a0f0
b19c85dd97c0f3236fcdb90cb7188bb48eb14b4b
9875b7a06c05d94de9c11873ca863f1d2a209771
49931b2c4aee842fba3a4d908ca1f425b52eeae5
9c6c9cb0c87e6b092f5b58b6b6a61fc747716158
7b0516e9b3f6502abb6b3ab1b65fb406d7d48902
07fd351eaaba30fe082a836e29c03d5f11f45edd
b7682082f141bd7b161d2b102f3565b085cd3975
227e2ab56775cf69dde662fc8244445b47a8097c
5cf14e251978e8f9192ad52b396136d7f9f22f26
a240ab21b06de9d167272d0ed01518f9061a4064
6c62db659622616558823abb1c12f7c216fed997
a92cb122dade4873c5b0aaf6a35ebc5fd445fa90
826bb4d8376c62b913b61301b276adab50e11c5a
ae98d5096e9484f9e48e47d6e9957da782a29bb1
cf985ddf51e05e2edc4f4bbdae7917a83a046f9a
4e3943fcffaceedfc0149e59e6404371ec367c2f
f5972ca949be5ea714d53769e532478f9d1b6f56
54e9dc874e550ab0f4c29f24a050c88a28d883d7
41c674f9af95d12f6a66cb6722158fb029b002ae
41431d1e894aad478f157b2595991f6492e705d1
46f453b1b9fdd1140a7da1ea4d956c14917081c1
af97663d7b1eb6064f63b0bd30df9dcd6357aad3
28b8cc9cda751c67558ec59cc16019154ebf56ae
4fdeb1d08939640c6023c52bdd9bff72d4d00b51
2ca8544b0ff9269420c23a0ac22da52b7894148b
7875646b4ab3ceb0c3fbcf0293d913c02fd140b7
62f95e57bc5d5c38b28fd960790a5c0989dd587b
--
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 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, 11 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, 11 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, 11 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, 11 months