Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: pinyin keep crash when CPU load high.
https://bugzilla.redhat.com/show_bug.cgi?id=586292
Summary: pinyin keep crash when CPU load high.
Product: Red Hat Enterprise Linux 6
Version: 6.0
Platform: i686
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: ibus-pinyin
AssignedTo: phuang(a)redhat.com
ReportedBy: phuang(a)redhat.com
QAContact: desktop-bugs(a)redhat.com
CC: eng-i18n-bugs(a)redhat.com, phuang(a)redhat.com,
i18n-bugs(a)lists.fedoraproject.org, biaji.cn(a)gmail.com
Depends on: 552445
Group: rhel_beta
Classification: Red Hat
Target Release: ---
Clone Of: 552445
+++ This bug was initially created as a clone of Bug #552445 +++
Description of problem:
Can't use pinyin input method when in high cpu load condition. Pinyin keep
crashing. You have to restart from applet and after a while , it crashed again.
Version-Release number of selected component (if applicable):
ibus-libs-1.2.0.20091204-2.fc12.i686
ibus-gtk-1.2.0.20091204-2.fc12.i686
ibus-pinyin-1.2.0.20090915-1.fc12.noarch
ibus-1.2.0.20091204-2.fc12.i686
How reproducible:
Do some CPU consuming work, and input characters using ibus-pinyin.
Steps to Reproduce:
1. Do some CPU consuming work
2. input something using ibus-pinyin
3. BOOM!!!
Actual results:
it crash again and again. input panel disappear and can't using ctrl-space
shortcut to call out pinyin input method again.
Expected results:
nothing special happened
Additional info:
After crash, the daemon complained:
(ibus-daemon:29976): IBUS-WARNING **: org.freedesktop.DBus.Error.NoReply: Did
not receive a reply. Possible causes include: the remote application did not
send a reply, the message bus security policy blocked the reply, the reply
timeout expired, or the network connection was broken.
--- Additional comment from phuang(a)redhat.com on 2010-01-20 03:45:54 EST ---
Please try new ibus.
http://admin.fedoraproject.org/updates/F12/FEDORA-2010-0385
--- Additional comment from phuang(a)redhat.com on 2010-04-07 22:41:06 EDT ---
Fixed in ibus-pinyin-1.3.1-1.fc12
--
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.
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.20091204-2.fc12
https://bugzilla.redhat.com/show_bug.cgi?id=556551
Summary: [abrt] crash in ibus-1.2.0.20091204-2.fc12
Product: Fedora
Version: 12
Platform: i686
OS/Version: Linux
Status: NEW
Status Whiteboard: abrt_hash:87031497776eb697f15e9313fe995dfcbfd21411
Severity: medium
Priority: low
Component: ibus
AssignedTo: phuang(a)redhat.com
ReportedBy: atgf0127(a)126.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.3 detected a crash.
Attached file: backtrace
cmdline: python /usr/share/ibus/ui/gtk/main.py
component: ibus
executable: /usr/bin/python
kernel: 2.6.31.9-174.fc12.i686.PAE
package: ibus-1.2.0.20091204-2.fc12
rating: 4
reason: Process was terminated by signal 11 (Segmentation fault)
--
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.
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 ibus-1.2.0.20091204-2.fc12
https://bugzilla.redhat.com/show_bug.cgi?id=549295
Summary: [abrt] crash detected in ibus-1.2.0.20091204-2.fc12
Product: Fedora
Version: 12
Platform: i686
OS/Version: Linux
Status: NEW
Status Whiteboard: abrt_hash:159699374710fe1f59b21b22fb7c9005a2e00e39
Severity: medium
Priority: low
Component: ibus
AssignedTo: phuang(a)redhat.com
ReportedBy: m_runwal(a)yahoo.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.0 detected a crash.
Attached file: backtrace
cmdline: /usr/bin/ibus-daemon --xim
component: ibus
executable: /usr/bin/ibus-daemon
kernel: 2.6.31.6-166.fc12.i686
package: ibus-1.2.0.20091204-2.fc12
rating: 4
reason: Process was terminated by signal 11
--
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.
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.
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.
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.
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.
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.
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.
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.