i18n-bugs May 2010

i18n-bugs@lists.fedoraproject.org

2 participants
438 discussions

[Fedora-i18n-bugs] [Bug 544085] New: [abrt] crash detected in transifex-0.6-3.fc12
by Red Hat Bugzilla 30 Sep '10

30 Sep '10

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: [abrt] crash detected in transifex-0.6-3.fc12 https://bugzilla.redhat.com/show_bug.cgi?id=544085 Summary: [abrt] crash detected in transifex-0.6-3.fc12 Product: Fedora Version: 12 Platform: i686 OS/Version: Linux Status: NEW Status Whiteboard: abrt_hash:7d935e6f Severity: medium Priority: low Component: transifex AssignedTo: ivazqueznet(a)gmail.com ReportedBy: gmathisz(a)gmail.com QAContact: extras-qa(a)fedoraproject.org CC: ivazqueznet(a)gmail.com, diegobz(a)gmail.com, fedora-i18n-bugs(a)redhat.com Estimated Hours: 0.0 Classification: Fedora abrt 1.0.0 detected a crash. How to reproduce ----- 1.as user from the terminal 2. ./manage.py syncdb 3. Comment: I was trying to configure transifex backtrace ----- Summary: TB7d935e6f base.py:170:_cursor:OperationalError: unable to open database file Traceback (most recent call last): File "./manage.py", line 20, in <module> execute_manager(settings) File "/usr/lib/python2.6/site-packages/django/core/management/__init__.py", line 362, in execute_manager utility.execute() File "/usr/lib/python2.6/site-packages/django/core/management/__init__.py", line 303, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/usr/lib/python2.6/site-packages/django/core/management/base.py", line 195, in run_from_argv self.execute(*args, **options.__dict__) File "/usr/lib/python2.6/site-packages/django/core/management/base.py", line 222, in execute output = self.handle(*args, **options) File "/usr/lib/python2.6/site-packages/django/core/management/base.py", line 351, in handle return self.handle_noargs(**options) File "/usr/lib/python2.6/site-packages/django/core/management/commands/syncdb.py", line 49, in handle_noargs cursor = connection.cursor() File "/usr/lib/python2.6/site-packages/django/db/backends/__init__.py", line 81, in cursor cursor = self._cursor() File "/usr/lib/python2.6/site-packages/django/db/backends/sqlite3/base.py", line 170, in _cursor self.connection = Database.connect(**kwargs) OperationalError: unable to open database file Local variables in innermost frame: self: <django.db.backends.sqlite3.base.DatabaseWrapper object at 0x95139dc> settings_dict: {'DATABASE_OPTIONS': {}, 'DATABASE_NAME': '/usr/share/transifex/transifex.db.sqlite', 'TIME_ZONE': 'UTC', 'DATABASE_PORT': '', 'DATABASE_PASSWORD': '', 'DATABASE_HOST': '', 'DATABASE_USER': ''} kwargs: {'detect_types': 3, 'database': '/usr/share/transifex/transifex.db.sqlite'} cmdline: python ./manage.py syncdb component: transifex executable: /usr/share/transifex/manage.py kernel: 2.6.31.6-145.fc12.i686.PAE package: transifex-0.6-3.fc12 uuid: 7d935e6f -- 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.

1 3

[Fedora-i18n-bugs] [Bug 544933] New: [abrt] crash detected in scim-1.4.9-4.fc12
by Red Hat Bugzilla 30 Sep '10

30 Sep '10

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: [abrt] crash detected in scim-1.4.9-4.fc12 https://bugzilla.redhat.com/show_bug.cgi?id=544933 Summary: [abrt] crash detected in scim-1.4.9-4.fc12 Product: Fedora Version: 12 Platform: i686 OS/Version: Linux Status: NEW Status Whiteboard: abrt_hash:ad1de4feea702b69ccbeb7d6bf069b78a22c1cb2 Severity: medium Priority: low Component: scim AssignedTo: phuang(a)redhat.com ReportedBy: m_runwal(a)yahoo.com QAContact: extras-qa(a)fedoraproject.org CC: petersen(a)redhat.com, phuang(a)redhat.com, fedora-i18n-bugs(a)redhat.com Estimated Hours: 0.0 Classification: Fedora abrt 1.0.0 detected a crash. Comment: Just logged in and Got this crash report. Attached file: backtrace cmdline: /usr/lib/scim-1.0/scim-panel-gtk --display :0.0 -c socket -d --no-stay component: scim executable: /usr/lib/scim-1.0/scim-panel-gtk kernel: 2.6.31.6-145.fc12.i686 package: scim-1.4.9-4.fc12 rating: 4 reason: Process was terminated by signal 6 -- 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.

1 7

[Fedora-i18n-bugs] [Bug 577575] New: [abrt] crash in scim-1.4.9-4.fc12: Process /usr/lib64/scim-1.0/scim-panel-gtk was killed by signal 6 (SIGABRT)
by Red Hat Bugzilla 30 Sep '10

30 Sep '10

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: [abrt] crash in scim-1.4.9-4.fc12: Process /usr/lib64/scim-1.0/scim-panel-gtk was killed by signal 6 (SIGABRT) https://bugzilla.redhat.com/show_bug.cgi?id=577575 Summary: [abrt] crash in scim-1.4.9-4.fc12: Process /usr/lib64/scim-1.0/scim-panel-gtk was killed by signal 6 (SIGABRT) Product: Fedora Version: 12 Platform: x86_64 OS/Version: Linux Status: NEW Status Whiteboard: abrt_hash:317599895cb4f8238af79a785c10a695ffb090c8 Severity: medium Priority: low Component: scim AssignedTo: phuang(a)redhat.com ReportedBy: dcwilbur(a)earthlink.net QAContact: extras-qa(a)fedoraproject.org CC: petersen(a)redhat.com, phuang(a)redhat.com, fedora-i18n-bugs(a)redhat.com, pwu(a)redhat.com Estimated Hours: 0.0 Classification: Fedora abrt 1.0.8 detected a crash. architecture: x86_64 Attached file: backtrace cmdline: /usr/lib64/scim-1.0/scim-panel-gtk --display :0.0 -c socket -d --no-stay component: scim executable: /usr/lib64/scim-1.0/scim-panel-gtk kernel: 2.6.31.12-174.2.22.fc12.x86_64 package: scim-1.4.9-4.fc12 rating: 4 reason: Process /usr/lib64/scim-1.0/scim-panel-gtk was killed by signal 6 (SIGABRT) release: Fedora release 12 (Constantine) -- 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.

1 8

[Fedora-i18n-bugs] [Bug 575536] New: [abrt] crash in scim-1.4.9-4.fc12: Process /usr/lib/scim-1.0/scim-panel-gtk was killed by signal 11 (SIGSEGV)
by Red Hat Bugzilla 30 Sep '10

30 Sep '10

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: [abrt] crash in scim-1.4.9-4.fc12: Process /usr/lib/scim-1.0/scim-panel-gtk was killed by signal 11 (SIGSEGV) https://bugzilla.redhat.com/show_bug.cgi?id=575536 Summary: [abrt] crash in scim-1.4.9-4.fc12: Process /usr/lib/scim-1.0/scim-panel-gtk was killed by signal 11 (SIGSEGV) Product: Fedora Version: 12 Platform: i686 OS/Version: Linux Status: NEW Status Whiteboard: abrt_hash:265ffdd16de4fba6d8a03306554c97189fb18add Severity: medium Priority: low Component: scim AssignedTo: phuang(a)redhat.com ReportedBy: shinkoi2005(a)gmail.com QAContact: extras-qa(a)fedoraproject.org CC: petersen(a)redhat.com, phuang(a)redhat.com, fedora-i18n-bugs(a)redhat.com, pwu(a)redhat.com Estimated Hours: 0.0 Classification: Fedora abrt 1.0.8 detected a crash. architecture: i686 Attached file: backtrace cmdline: /usr/lib/scim-1.0/scim-panel-gtk --display :0.0 -c socket -d --no-stay component: scim executable: /usr/lib/scim-1.0/scim-panel-gtk kernel: 2.6.32.9-70.fc12.i686.PAE package: scim-1.4.9-4.fc12 rating: 4 reason: Process /usr/lib/scim-1.0/scim-panel-gtk was killed by signal 11 (SIGSEGV) release: Fedora release 12 (Constantine) -- 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.

1 6

[Fedora-i18n-bugs] [Bug 565386] New: Follow upon the font packaging policy (fontconfig)
by Red Hat Bugzilla 14 Sep '10

14 Sep '10

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: Follow upon the font packaging policy (fontconfig) https://bugzilla.redhat.com/show_bug.cgi?id=565386 Summary: Follow upon the font packaging policy (fontconfig) Product: Red Hat Enterprise Linux 6 Version: 6.0 Platform: All OS/Version: Linux Status: NEW Severity: medium Priority: low Component: culmus-fonts AssignedTo: psatpute(a)redhat.com ReportedBy: tagoh(a)redhat.com CC: petersen(a)redhat.com, psatpute(a)redhat.com, fedora-i18n-bugs(a)redhat.com Depends on: 565385 Group: rhel_beta Estimated Hours: 0.0 Classification: Red Hat Target Release: --- Clone Of: 565385 +++ This bug was initially created as a clone of Bug #565385 +++ Description of problem: Since 61-64 is reserved for the low priority LGC fonts, Hebrew font should be moved to the range of 65-69. Aside from that, there are no Generic names rule (http://fedoraproject.org/wiki/Fontconfig_packaging_tips#Generic_names) in any fontconfig config files. every fonts should be assigned to either of sans/sans-serif/monospace. Version-Release number of selected component (if applicable): culmus-fonts-0.104-1.fc13. -- 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.

1 9

[Fedora-i18n-bugs] [Bug 597234] New: [abrt] crash in ibus-fbterm-0.9.1-7.fc13: raise: Process /usr/bin/ibus-fbterm was killed by signal 6 (SIGABRT)
by Red Hat Bugzilla 14 Sep '10

14 Sep '10

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: [abrt] crash in ibus-fbterm-0.9.1-7.fc13: raise: Process /usr/bin/ibus-fbterm was killed by signal 6 (SIGABRT) https://bugzilla.redhat.com/show_bug.cgi?id=597234 Summary: [abrt] crash in ibus-fbterm-0.9.1-7.fc13: raise: Process /usr/bin/ibus-fbterm was killed by signal 6 (SIGABRT) Product: Fedora Version: 13 Platform: i686 OS/Version: Linux Status: NEW Status Whiteboard: abrt_hash:d1fcef574700d0ba6e509d6da61d1cd7619017d5 Severity: medium Priority: low Component: ibus-fbterm AssignedTo: cchance(a)redhat.com ReportedBy: cyrusyzgtt(a)gmail.com QAContact: extras-qa(a)fedoraproject.org CC: cchance(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org Classification: Fedora abrt 1.1.0 detected a crash. architecture: i686 Attached file: backtrace cmdline: ibus-fbterm component: ibus-fbterm crash_function: raise executable: /usr/bin/ibus-fbterm global_uuid: d1fcef574700d0ba6e509d6da61d1cd7619017d5 kernel: 2.6.33.4-95.fc13.i686.PAE package: ibus-fbterm-0.9.1-7.fc13 rating: 4 reason: Process /usr/bin/ibus-fbterm was killed by signal 6 (SIGABRT) release: Fedora release 13 (Goddard) How to reproduce ----- 1.sudo setcap sudo setcap cap_sys_tty_config+ep /usr/bin/fbterm 2.ctrl+alt+F4>>tty4>>login homeuser, 3.fbterm then "ctrl+space" -- 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.

1 4

[Fedora-i18n-bugs] [Bug 586765] New: Rename 65-madan.conf to 65-0-madan.conf
by Red Hat Bugzilla 08 Sep '10

08 Sep '10

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: Rename 65-madan.conf to 65-0-madan.conf https://bugzilla.redhat.com/show_bug.cgi?id=586765 Summary: Rename 65-madan.conf to 65-0-madan.conf 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: According to http://fedoraproject.org/wiki/I18N/Indic#Fonts_list and the testing result of Bug#578041, the config file should be renamed to 65-0- to avoid the unwilling affection of 65-nonlatin.conf since we are expecting madan-fonts as the default Nepali font. Version-Release number of selected component (if applicable): madan-fonts-2.000-2.fc13.noarch Additional info: See Bug#578041 for more details. -- 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.

1 9

[Fedora-i18n-bugs] [Bug 566871] New: [abrt] crash in ibus-1.2.0.20100111-2.fc12
by Red Hat Bugzilla 03 Sep '10

03 Sep '10

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: [abrt] crash in ibus-1.2.0.20100111-2.fc12 https://bugzilla.redhat.com/show_bug.cgi?id=566871 Summary: [abrt] crash in ibus-1.2.0.20100111-2.fc12 Product: Fedora Version: 12 Platform: x86_64 OS/Version: Linux Status: NEW Status Whiteboard: abrt_hash:97bc69bce01cda40ec5cfbc31ed4a16766f23bc9 Severity: medium Priority: low Component: ibus AssignedTo: phuang(a)redhat.com ReportedBy: mark.richards(a)gmail.com QAContact: extras-qa(a)fedoraproject.org CC: phuang(a)redhat.com, fedora-i18n-bugs(a)redhat.com Estimated Hours: 0.0 Classification: Fedora abrt 1.0.6 detected a crash. architecture: x86_64 Attached file: backtrace cmdline: python /usr/share/ibus/ui/gtk/main.py component: ibus executable: /usr/bin/python kernel: 2.6.31.12-174.2.3.fc12.x86_64 package: ibus-1.2.0.20100111-2.fc12 rating: 4 reason: Process was terminated by signal 11 (Segmentation fault) release: Fedora release 12 (Constantine) -- 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.

1 5

[Fedora-i18n-bugs] [Bug 526854] New: running firstboot as user in non-English locales gives utf8 backtrace
by Red Hat Bugzilla 02 Sep '10

02 Sep '10

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: running firstboot as user in non-English locales gives utf8 backtrace https://bugzilla.redhat.com/show_bug.cgi?id=526854 Summary: running firstboot as user in non-English locales gives utf8 backtrace Product: Fedora Version: rawhide Platform: All OS/Version: Linux Status: NEW Severity: low Priority: low Component: firstboot AssignedTo: clumens(a)redhat.com ReportedBy: petersen(a)redhat.com QAContact: extras-qa(a)fedoraproject.org CC: clumens(a)redhat.com, fedora-i18n-bugs(a)redhat.com Estimated Hours: 0.0 Classification: Fedora Target Release: --- Description of problem: When firstboot is run in a locale uses non-ascii characters firstboot backtrace Version-Release number of selected component (if applicable): firstboot-1.109-1.fc12 How reproducible: every time Steps to Reproduce: 1. LANG=de_DE.UTF-8 firstboot 2. LANG=ja_JP.UTF-8 firstboot 3. etc Actual results: Traceback (most recent call last): File "/usr/lib64/python2.6/logging/__init__.py", line 773, in emit stream.write(fs % msg.encode("UTF-8")) UnicodeDecodeError: 'ascii' codec can't decode byte 0xe3 in position 27: ordinal not in range(128) Expected results: translation of $ LANG=C firstboot firstboot ERROR: You must be root to run firstboot. 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.

1 7

[Fedora-i18n-bugs] [Bug 500731] New: Switching on/off behaves weird when compositing enabled
by Red Hat Bugzilla 02 Sep '10

02 Sep '10

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: Switching on/off behaves weird when compositing enabled https://bugzilla.redhat.com/show_bug.cgi?id=500731 Summary: Switching on/off behaves weird when compositing enabled Product: Fedora Version: rawhide Platform: All OS/Version: Linux Status: NEW Severity: medium Priority: low Component: ibus AssignedTo: phuang(a)redhat.com ReportedBy: martin.sourada(a)gmail.com QAContact: extras-qa(a)fedoraproject.org CC: phuang(a)redhat.com, fedora-i18n-bugs(a)redhat.com Estimated Hours: 0.0 Classification: Fedora Description of problem: Turning ibus on or off does frequently makes the tool window either semitransparently reapear after switching to another window (and is not clickable/working) or not appear (save for its shadow and it is clickable/working). I can seem to trigger this only when I have compositing in metacity enabled. Tried chewing and anthy inputs, both suffer from this. Version-Release number of selected component (if applicable): ibus-1.1.0.20090508-1.fc11.i586 How reproducible: seems to be always reproducible sans some applications (e.g. when switching to ibus settings window, it seems to behave correctly) Steps to Reproduce: 1. turn on metacity compositing (gconf->apps->metacity->general->compositin_manager) 2. open two gtk applications that take input from keyboard (e.g. two gnome-terminals) 3. switch to and fro between those two applications while randomly turning ibus on and off Actual results: Usually after turning it off and switching to other window, the toolbox reappear (but is semitransparent and not clickable/working), switching back, turning on and off again and switching again to the other window seems to work as expeced. Switch back to the first window and turn it on again, usually blank (fully transparent) toolbox appears. Turning off and on again fix it (or switching again to and fro between the two applications without explicitly turning it on/off). Expected results: Turns on and off without the strange side effects. Additional info: It seems impossible to make a screenshot of the not-appearing one, hitting print screen makes it reappear. Screenshot of the "false positive" is at https://www.redhat.com/archives/fedora-test-list/2009-May/png1jbZyCgtB3.png -- 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.

1 15

← Newer
1
...
5
6
7
8
9
10
11
...
44
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

i18n-bugs May 2010