[Fedora-i18n-bugs] [Bug 493172] New: Dead keys not working in some applications (xterm, emacs)
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: Dead keys not working in some applications (xterm, emacs)
https://bugzilla.redhat.com/show_bug.cgi?id=493172
Summary: Dead keys not working in some applications (xterm,
emacs)
Product: Fedora
Version: 10
Platform: i686
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: imsettings
AssignedTo: tagoh(a)redhat.com
ReportedBy: joyr(a)netikka.fi
QAContact: extras-qa(a)fedoraproject.org
CC: tagoh(a)redhat.com, fedora-i18n-bugs(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
Created an attachment (id=337405)
--> (https://bugzilla.redhat.com/attachment.cgi?id=337405)
X session error log
Description of problem:
Not sure if this is the correct component to report on.
Dead keys stopped working for some applications, not sure when.
I'm using Gnome, layout is Finland layout, keyboard model is Evdev-managed
keyboard.
They seem to work in all GTK applications (tested: gedit, firefox, x-chat) and
also QT applications (qtconfig-qt4), but not on some (xterm, emacs).
Also tried with Sweden layout and Generic 105-key (Intl) PC model with same
problems. I'm unable to set the "Default" radio-button in keyboard preferences
but the layout changes if I drag&drop the wanted layout to first in list.
Version-Release number of selected component (if applicable):
# rpm -qa imsettings* scim* xkey* xterm* emacs* *font* *xim* | sort
abyssinica-fonts-1.0-2.fc8.noarch
baekmuk-ttf-fonts-common-2.2-9.fc10.noarch
baekmuk-ttf-fonts-gulim-2.2-9.fc10.noarch
bitmap-fonts-0.3-6.fc10.noarch
cjkunifonts-uming-0.2.20080216.1-11.fc10.noarch
dejavu-fonts-2.26-2.fc10.noarch
dejavu-fonts-experimental-2.26-2.fc10.noarch
emacs-22.3-4.fc10.i386
emacs-common-22.3-4.fc10.i386
emacs-gnuplot-4.2.3-1.fc10.i386
emacs-lua-20071122-5.fc9.noarch
emacs-nxml-mode-0.20041004-7.fc10.noarch
fontconfig-2.6.0-3.fc10.i386
fontconfig-devel-2.6.0-3.fc10.i386
fontpackages-filesystem-1.20-1.fc10.noarch
ghostscript-fonts-5.50-19.fc10.noarch
imsettings-0.105.1-4.fc10.i386
imsettings-libs-0.105.1-4.fc10.i386
jomolhari-fonts-0.003-5.fc10.noarch
kacst-fonts-2.0-1.fc10.noarch
khmeros-fonts-base-5.0-3.fc10.noarch
liberation-fonts-1.04.92-1.fc10.noarch
libfontenc-1.0.4-6.fc10.i386
libfontenc-devel-1.0.4-6.fc10.i386
libgxim-0.3.2-4.fc10.i386
libXfont-1.3.3-1.fc10.i386
libXfont-devel-1.3.3-1.fc10.i386
lklug-fonts-0.2.2-6.fc10.noarch
lohit-fonts-bengali-2.3.1-1.fc10.noarch
lohit-fonts-gujarati-2.3.1-1.fc10.noarch
lohit-fonts-hindi-2.3.1-1.fc10.noarch
lohit-fonts-kannada-2.3.1-1.fc10.noarch
lohit-fonts-maithili-2.3.1-1.fc10.noarch
lohit-fonts-malayalam-2.3.1-1.fc10.noarch
lohit-fonts-oriya-2.3.1-1.fc10.noarch
lohit-fonts-punjabi-2.3.1-1.fc10.noarch
lohit-fonts-tamil-2.3.1-1.fc10.noarch
lohit-fonts-telugu-2.3.1-1.fc10.noarch
padauk-fonts-2.4-2.fc10.noarch
paktype-fonts-2.0-2.fc8.noarch
scim-1.4.7-35.fc10.i386
scim-anthy-1.2.7-1.fc10.i386
scim-bridge-0.4.15-8.fc10.i386
scim-bridge-gtk-0.4.15-8.fc10.i386
scim-bridge-qt-0.4.15-8.fc10.i386
scim-chewing-0.3.3-0.fc10.i386
scim-hangul-0.3.2-4.fc9.i386
scim-libs-1.4.7-35.fc10.i386
scim-m17n-0.2.2-3.fc9.i386
scim-python-0.1.13rc1-1.fc10.i386
scim-python-pinyin-0.1.13rc1-1.fc10.i386
scim-qtimm-0.9.4-11.fc10.i386
scim-rawcode-1.4.7-35.fc10.i386
smc-fonts-meera-04.1-1.fc10.noarch
stix-fonts-0.9-7.fc10.noarch
texlive-texmf-errata-fonts-2007-4.fc9.noarch
texlive-texmf-fonts-2007-26.fc10.noarch
thaifonts-scalable-0.4.9-3.fc9.noarch
un-core-fonts-dotum-1.0.2-0.6.080608.fc10.noarch
urw-fonts-2.4-6.fc10.noarch
vlgothic-fonts-20090204-2.fc10.noarch
vlgothic-fonts-common-20090204-2.fc10.noarch
xkeyboard-config-1.4-7.fc10.noarch
xorg-x11-fonts-100dpi-7.2-6.fc9.noarch
xorg-x11-fonts-75dpi-7.2-6.fc9.noarch
xorg-x11-fonts-ISO8859-1-100dpi-7.2-6.fc9.noarch
xorg-x11-fonts-ISO8859-1-75dpi-7.2-6.fc9.noarch
xorg-x11-fonts-misc-7.2-6.fc9.noarch
xorg-x11-fonts-Type1-7.2-6.fc9.noarch
xorg-x11-font-utils-7.2-6.fc10.i386
xterm-242-2.fc10.i386
How reproducible:
Always.
Steps to Reproduce:
1. start xterm or emacs
2. try to input ~ using dead-key combination of "altgr" + "~" + "space"
Actual results:
xterm: A plain space character.
emacs: Error message "<dead-tilde> is undefined"
Expected results:
I should be getting the correct character "~".
Additional info:
The following error message comes from imsettings-applet everytime I press any
key on xterm (including modifiers like shift and alt):
[BUG][ 1238531428.714163] xim_proxy_client_protocol_real_xim_forward_event: The
pending key event counter is overflowed
And the following warning comes from imsettings-applet when I start xterm:
W[ 1238531541.790674]:Error while processing a value type NestedList: Error
while processing a value type XFontSet: Unable to compose a value type XFontSet
properly due to the size difference: expected size: 129, actual size: 132
--
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, 5 months
[Fedora-i18n-bugs] [Bug 522048] New: [abrt] crash detected in ibus-1.2.0.20090904-2.fc12
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] crash detected in ibus-1.2.0.20090904-2.fc12
https://bugzilla.redhat.com/show_bug.cgi?id=522048
Summary: [abrt] crash detected in ibus-1.2.0.20090904-2.fc12
Product: Fedora
Version: rawhide
Platform: i686
OS/Version: Linux
Status: NEW
Status Whiteboard: abrt_hash:08997608
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: ---
abrt detected a crash.
How to reproduce
-----
1.
2.
3.
Additional information
======
Attached files
----
backtrace
cmdline
-----
python /usr/share/ibus/ui/gtk/main.py
component
-----
ibus
executable
-----
/usr/share/ibus/ui/gtk/main.py
kernel
-----
2.6.31-0.204.rc9.fc12.i686
package
-----
ibus-1.2.0.20090904-2.fc12
uuid
-----
08997608
--
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, 5 months
[Fedora-i18n-bugs] [Bug 488877] New: no response on xterm after switching IM
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 response on xterm after switching IM
https://bugzilla.redhat.com/show_bug.cgi?id=488877
Summary: no response on xterm after switching IM
Product: Fedora
Version: 10
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: imsettings
AssignedTo: tagoh(a)redhat.com
ReportedBy: tagoh(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: jfrieben(a)hotmail.com, tagoh(a)redhat.com,
fedora-i18n-bugs(a)redhat.com
Depends on: 488773
Estimated Hours: 0.0
Classification: Fedora
Target Release: ---
Clone Of: 488773
To keeps an issue in summary on track separately because the root cause is
different.
+++ This bug was initially created as a clone of Bug #488773 +++
Created an attachment (id=334166)
--> (https://bugzilla.redhat.com/attachment.cgi?id=334166)
X session errors caused by enabling SCIM
Description of problem:
After updating libgxim to release 0.3.2-4.fc10, xterm shows some regression:
when running a program with a noticeable amount of text output (e.g. 'ls -R
/'), then imsettings-applet starts grabbing a significant amount of CPU share
of up to 10%. Note that SCIM is disabled at this point.
After opening GNOME menu item "Input Method" and enabling SCIM which is
disabled by default, xterm does not accept any input from the keyboard anymore
unlike gnome-terminal which continues to do so.
Version-Release number of selected component (if applicable):
libgxim-0.3.2-4.fc10.x86_64
How reproducible:
Always.
Steps to Reproduce:
1. Open GNOME session.
2. Start a program in an xterm window producing text output.
3. Run 'top' in a different window.
4. Open "Input Method" from GNOME menu and enable SCIM.
Actual results:
- Noticeable CPU load caused by imsettings-applet.
- Xterm unresponsive after enabling SCIM via "Input Method" dialog window.
Expected results:
Normal behaviour of xterm just as gnome-terminal.
Additional info:
Reverting libgxim to release 0.3.1-1.fc10 allows to restore normal operation.
--
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, 5 months
[Fedora-i18n-bugs] [Bug 488773] New: libgxim-0.3.2-4.fc10: enabling SCIM blocks xterm and causes important CPU load
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: libgxim-0.3.2-4.fc10: enabling SCIM blocks xterm and causes important CPU load
https://bugzilla.redhat.com/show_bug.cgi?id=488773
Summary: libgxim-0.3.2-4.fc10: enabling SCIM blocks xterm and
causes important CPU load
Product: Fedora
Version: 10
Platform: x86_64
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: libgxim
AssignedTo: tagoh(a)redhat.com
ReportedBy: jfrieben(a)hotmail.com
QAContact: extras-qa(a)fedoraproject.org
CC: tagoh(a)redhat.com, fedora-i18n-bugs(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
Created an attachment (id=334166)
--> (https://bugzilla.redhat.com/attachment.cgi?id=334166)
X session errors caused by enabling SCIM
Description of problem:
After updating libgxim to release 0.3.2-4.fc10, xterm shows some regression:
when running a program with a noticeable amount of text output (e.g. 'ls -R
/'), then imsettings-applet starts grabbing a significant amount of CPU share
of up to 10%. Note that SCIM is disabled at this point.
After opening GNOME menu item "Input Method" and enabling SCIM which is
disabled by default, xterm does not accept any input from the keyboard anymore
unlike gnome-terminal which continues to do so.
Version-Release number of selected component (if applicable):
libgxim-0.3.2-4.fc10.x86_64
How reproducible:
Always.
Steps to Reproduce:
1. Open GNOME session.
2. Start a program in an xterm window producing text output.
3. Run 'top' in a different window.
4. Open "Input Method" from GNOME menu and enable SCIM.
Actual results:
- Noticeable CPU load caused by imsettings-applet.
- Xterm unresponsive after enabling SCIM via "Input Method" dialog window.
Expected results:
Normal behaviour of xterm just as gnome-terminal.
Additional info:
Reverting libgxim to release 0.3.1-1.fc10 allows to restore normal operation.
--
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, 5 months
[Fedora-i18n-bugs] [Bug 490919] New: imsettings slows down frame rates significantly in Linux Gaming. (10-30 FPS)
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: imsettings slows down frame rates significantly in Linux Gaming. (10-30 FPS)
https://bugzilla.redhat.com/show_bug.cgi?id=490919
Summary: imsettings slows down frame rates significantly in
Linux Gaming. (10-30 FPS)
Product: Fedora
Version: 4
Platform: i386
OS/Version: Linux
Status: NEW
Severity: urgent
Priority: low
Component: imsettings
AssignedTo: tagoh(a)redhat.com
ReportedBy: nikitis(a)gmail.com
QAContact: extras-qa(a)fedoraproject.org
CC: tagoh(a)redhat.com, fedora-i18n-bugs(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
Clone Of: 488976
Description of problem: The new release of imsettings-0.105.1-4.fc10 causes
games to slowdown 10-30 Frames Per Second.
Version-Release number of selected component (if applicable):
imsettings-0.105.1-4.fc10
How reproducible: 100%
Steps to Reproduce:
1.Enter into World of Warcraft (My example), Log in.
2.Start Frames Per Second Counter (Ctrl+R)
3.Move or press any key or hold any key and frames will drop.
Actual results: The Game beings to slow down as keys are pressed or held.
Expected results: The Game should not experience any frame loss as a result of
a key press. Especially not to the degree of 10-30 FPS. Maybe only a couple
of frames maximum as the screen is processing new data when turning etc.
imsettings inside of libgxim 3.1-1 functions properly in this respect, and was
the last known working version if imsettings.
Additional info:I was working with a developer and started the bug report
488976 because of this issue, and he decided it was working well enough for an
update release. Before inside the games if you turned left, and let go, you
would continue to turn left and that wasn't supposed to happen. With
sync_on_forward set to true with new version of imsettings-0.105.1-4.fc10, that
issue is fixed however there is now a regression in the fact that there is a
Frames per second loss when a key is pressed or held which results in a very
bad gaming experience. Sometimes game slows to a crawl.
I have a GeForce 8600 GT by Nvidia, dual core intel processor at 3.0 Ghz, 4GB's
of RAM running FC10 i386. I did not experience this slowdown until
libgxim-0.3.2-4.fc10 package was released.
Starting new bug report to fix this regression.
--
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, 5 months
[Fedora-i18n-bugs] [Bug 471927] New: imsettings causes window manager confusion in Xfce
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: imsettings causes window manager confusion in Xfce
https://bugzilla.redhat.com/show_bug.cgi?id=471927
Summary: imsettings causes window manager confusion in Xfce
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: medium
Component: imsettings
AssignedTo: tagoh(a)redhat.com
ReportedBy: kevin(a)tummy.com
QAContact: extras-qa(a)fedoraproject.org
CC: tagoh(a)redhat.com, fedora-i18n-bugs(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
If the imsettings and imsettings-xfce packages are installed xfwm4 settings are
confused and don't think xfwm4 is the window manager.
1. Install imsettings-xfce
2. yum groupinstall XFCE
3. login and choose Xfce as your desktop.
4. right click on the desktop
5. choose settings manager
6. choose either "Window Manager" or "Window Manager Tweaks".
7. You will get a message:
"These settings cannot work with your current window manager (imsetting-xim)"
The code in xfwm4 hasn't changed in years here. It does:
wm_name = gdk_x11_screen_get_window_manager_name (gdk_screen_get_default
());
if (g_ascii_strcasecmp (wm_name, "Xfwm4"))
{
xfce_err (_("These settings cannot work with your current window
manager (%s)"), wm_name);
return;
}
Is imsettings changing the gdk default window manager somehow?
Removing imsettings causes everything to work as normal.
--
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, 5 months
[Fedora-i18n-bugs] [Bug 524883] New: cpi setting not used accurately
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: cpi setting not used accurately
https://bugzilla.redhat.com/show_bug.cgi?id=524883
Summary: cpi setting not used accurately
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: paps
AssignedTo: tagoh(a)redhat.com
ReportedBy: twaugh(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: tagoh(a)redhat.com, fedora-i18n-bugs(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
Target Release: ---
Created an attachment (id=362101)
--> (https://bugzilla.redhat.com/attachment.cgi?id=362101)
ppd.ppd
Description of problem:
When used as texttopaps, the 'cpi' option is only used to scale the font to the
nearest integer point size. This isn't nearly good enough: it must be *exact*.
The reason is that it is used for controlling the number of columns of text
print, and this needs to be set to e.g. 132, or 80, or whatever is required.
Unfortunately the only way to set it is indirectly, via 'cpi'. Of course this
depends on the page size used, as well as the printer margins.
Here is a test case for verifying that it is operating correctly. The CUPS
filter 'texttops' passes this test, and 'texttopaps' must as well. The test
case consists of a PPD 'ppd.ppd', an input file '132.txt', and a command line
given below.
Version-Release number of selected component (if applicable):
paps-0.6.8-10.fc12.x86_64
How reproducible:
100%
Steps to Reproduce:
PPD=ppd.ppd \
/usr/lib/cups/filter/texttopaps 1 tim '' 1 \
'cpi=17.6 lpi=6.7 page-bottom=36 page-left=36 \
page-right=36 page-top=36 scaling=100' 132.txt > out.ps
Actual results:
See actual.jpg.
Expected results:
When viewing the resulting PostScript (with, say, evince), the result should
look as in expected.jpg: in particular, there should be exactly 132 characters
per line, and the output should fit on a single side of US Letter paper.
--
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, 5 months
[Fedora-i18n-bugs] [Bug 503185] New: Can't open skk-e21.el
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: Can't open skk-e21.el
https://bugzilla.redhat.com/show_bug.cgi?id=503185
Summary: Can't open skk-e21.el
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: ddskk
AssignedTo: petersen(a)redhat.com
ReportedBy: yamato(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: petersen(a)redhat.com, fedora-i18n-bugs(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
Target Release: ---
Created an attachment (id=345907)
--> (https://bugzilla.redhat.com/attachment.cgi?id=345907)
Fixes this bug.
Description of problem:
To use ddskk(ddskk-12.2.0-12.fc11.noarch) on emacs(emacs-22.3-11.fc11.x86_64),
emacs complains "Can't find skk-e21.el".
In SKK-MK of the ddskk package , which is part of ddskk build system, the
version number of emacs is checked to decide whether skk-e21.el should be
installed or not. The SKK-MK expects emacs-21 to install skk-e21.el. However,
emacs on F11 is emacs-22. There is a gap.
Attached patch is taken from upstream skk code. In the patch mule version is
checked instead of emacs version to decide whether skk-e21.el should be
installed or not.
Version-Release number of selected component (if applicable):
ddskk-12.2.0-12.fc11.noarch
emacs-22.3-11.fc11.x86_64
How reproducible:
Steps to Reproduce:
1. install the packages.
2. emacs
3. M-x load-library: skk
Actual results:
"Can't find skk-e21.el" is messaged.
Expected results:
Skk works fine.
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, 5 months
[Fedora-i18n-bugs] [Bug 519328] New: [ibus-chewing] inconsistent between normal mode and plain Zhuyin mode.
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: [ibus-chewing] inconsistent between normal mode and plain Zhuyin mode.
https://bugzilla.redhat.com/show_bug.cgi?id=519328
Summary: [ibus-chewing] inconsistent between normal mode and
plain Zhuyin mode.
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: ASSIGNED
Severity: medium
Priority: low
Component: ibus-chewing
AssignedTo: dchen(a)redhat.com
ReportedBy: dchen(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: phuang(a)redhat.com, dchen(a)redhat.com,
fedora-i18n-bugs(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
Target Release: ---
Description of problem:
For input sequence "ej3" (ㄍㄨ3）,why the number of
candidates varies with the selection of "Plain Zhuyin mode"?
The number of candidates is 20 when "Plain Zhuyin mode" is enabled.
And the number will be 59 if the "Plain Zhuyin mode" is disabled.
Version-Release number of selected component (if applicable):
ibus-chewing-1.2.0-20090818
How reproducible:
Always
Steps to Reproduce:
1. Turn on ibus-chewing
2. Make sure "Plain Zhuyin mode" and "Use space to select" are on.
3. Type "ej3"
4. Press space to enter candidate selection mode.
5. Use space to cycle through the candidate, there are 20 candidates.
6. Clear the preedit buffer.
6. Deselect "Plain Zhuyin mode" .
3. Type "ej3"
4. Press space to enter candidate selection mode.
5. Use space to cycle through the candidate, there are 59 candidates.
Actual results:
"Plain Zhuyin mode" on: 20 candidates.
"Plain Zhuyin mode" off: 59 candidates.
Expected results:
Both of them should show 59 candidates.
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, 6 months
[Fedora-i18n-bugs] [Bug 526355] New: ibus is updated in testing, please rebuild against new libraries
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: ibus is updated in testing, please rebuild against new libraries
https://bugzilla.redhat.com/show_bug.cgi?id=526355
Summary: ibus is updated in testing, please rebuild against new
libraries
Product: Fedora
Version: 11
Platform: All
OS/Version: Linux
Status: NEW
Severity: urgent
Priority: low
Component: ibus-chewing
AssignedTo: dchen(a)redhat.com
ReportedBy: webmaster(a)aus-city.com
QAContact: extras-qa(a)fedoraproject.org
CC: phuang(a)redhat.com, dchen(a)redhat.com,
fedora-i18n-bugs(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
Description of problem:
Resolving Dependencies
--> Running transaction check
---> Package ibus.i586 0:1.2.0.20090927-1.fc11 set to be updated
---> Package ibus-anthy.i586 0:1.2.0.20090917-1.fc11 set to be updated
--> Processing Dependency: kasumi for package:
ibus-anthy-1.2.0.20090917-1.fc11.i586
---> Package ibus-gtk.i586 0:1.2.0.20090927-1.fc11 set to be updated
--> Processing Dependency: libibus.so.0 for package:
ibus-chewing-1.2.0.20090917-1.fc11.i586
--> Processing Dependency: libibus.so.0 for package:
ibus-hangul-1.1.0.20090328-2.fc11.i586
--> Processing Dependency: libibus.so.0 for package:
ibus-rawcode-1.0.0.20090303-3.fc11.i586
--> Processing Dependency: libibus.so.0 for package:
ibus-m17n-1.1.0.20090211-5.fc11.i586
---> Package ibus-libs.i586 0:1.2.0.20090927-1.fc11 set to be updated
---> Package ibus-pinyin.noarch 0:1.2.0.20090915-1.fc11 set to be updated
--> Processing Dependency: python-enchant for package:
ibus-pinyin-1.2.0.20090915-1.fc11.noarch
--> Running transaction check
--> Processing Dependency: libibus.so.0 for package:
ibus-chewing-1.2.0.20090917-1.fc11.i586
--> Processing Dependency: libibus.so.0 for package:
ibus-hangul-1.1.0.20090328-2.fc11.i586
--> Processing Dependency: libibus.so.0 for package:
ibus-rawcode-1.0.0.20090303-3.fc11.i586
--> Processing Dependency: libibus.so.0 for package:
ibus-m17n-1.1.0.20090211-5.fc11.i586
---> Package kasumi.i586 0:2.4-2.fc11 set to be updated
---> Package python-enchant.i586 0:1.3.1-4.fc11 set to be updated
--> Finished Dependency Resolution
ibus-m17n-1.1.0.20090211-5.fc11.i586 from installed has depsolving problems
--> Missing Dependency: libibus.so.0 is needed by package
ibus-m17n-1.1.0.20090211-5.fc11.i586 (installed)
ibus-chewing-1.2.0.20090917-1.fc11.i586 from installed has depsolving problems
--> Missing Dependency: libibus.so.0 is needed by package
ibus-chewing-1.2.0.20090917-1.fc11.i586 (installed)
ibus-rawcode-1.0.0.20090303-3.fc11.i586 from installed has depsolving problems
--> Missing Dependency: libibus.so.0 is needed by package
ibus-rawcode-1.0.0.20090303-3.fc11.i586 (installed)
ibus-hangul-1.1.0.20090328-2.fc11.i586 from installed has depsolving problems
--> Missing Dependency: libibus.so.0 is needed by package
ibus-hangul-1.1.0.20090328-2.fc11.i586 (installed)
--> Running transaction check
---> Package ibus-libs.i586 0:1.2.0.20090927-1.fc11 set to be updated
--> Processing Dependency: ibus-libs = 1.2.0.20090927-1.fc11 for package:
ibus-1.2.0.20090927-1.fc11.i586
--> Processing Dependency: libibus.so.1 for package:
ibus-gtk-1.2.0.20090927-1.fc11.i586
--> Processing Dependency: libibus.so.1 for package:
ibus-1.2.0.20090927-1.fc11.i586
--> Finished Dependency Resolution
ibus-1.2.0.20090927-1.fc11.i586 from updates has depsolving problems
--> Missing Dependency: ibus-libs = 1.2.0.20090927-1.fc11 is needed by
package ibus-1.2.0.20090927-1.fc11.i586 (updates)
ibus-1.2.0.20090927-1.fc11.i586 from updates has depsolving problems
--> Missing Dependency: libibus.so.1 is needed by package
ibus-1.2.0.20090927-1.fc11.i586 (updates)
ibus-gtk-1.2.0.20090927-1.fc11.i586 from updates has depsolving problems
--> Missing Dependency: libibus.so.1 is needed by package
ibus-gtk-1.2.0.20090927-1.fc11.i586 (updates)
--> Running transaction check
---> Package ibus.i586 0:1.2.0.20090927-1.fc11 set to be updated
--> Processing Dependency: ibus >= 1.2.0 for package:
ibus-pinyin-1.2.0.20090915-1.fc11.noarch
--> Processing Dependency: ibus >= 1.2.0.20090904 for package:
ibus-anthy-1.2.0.20090917-1.fc11.i586
---> Package ibus-gtk.i586 0:1.2.0.20090927-1.fc11 set to be updated
---> Package ibus-libs.i586 0:1.2.0.20090927-1.fc11 set to be updated
--> Finished Dependency Resolution
ibus-pinyin-1.2.0.20090915-1.fc11.noarch from updates has depsolving problems
--> Missing Dependency: ibus >= 1.2.0 is needed by package
ibus-pinyin-1.2.0.20090915-1.fc11.noarch (updates)
ibus-anthy-1.2.0.20090917-1.fc11.i586 from updates has depsolving problems
--> Missing Dependency: ibus >= 1.2.0.20090904 is needed by package
ibus-anthy-1.2.0.20090917-1.fc11.i586 (updates)
Packages skipped because of dependency problems:
ibus-1.2.0.20090927-1.fc11.i586 from updates
ibus-anthy-1.2.0.20090917-1.fc11.i586 from updates
ibus-gtk-1.2.0.20090927-1.fc11.i586 from updates
ibus-libs-1.2.0.20090927-1.fc11.i586 from updates
ibus-pinyin-1.2.0.20090915-1.fc11.noarch from updates
kasumi-2.4-2.fc11.i586 from fedora
python-enchant-1.3.1-4.fc11.i586 from fedora
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, 6 months