Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: [kde session]ibus systray icon 2 icons in desktop and one is not dock in system
tray
https://bugzilla.redhat.com/show_bug.cgi?id=480891
Summary: [kde session]ibus systray icon 2 icons in desktop and
one is not dock in system tray
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Keywords: i18n
Severity: medium
Priority: low
Component: ibus
AssignedTo: phuang(a)redhat.com
ReportedBy: aalam(a)redhat.com
QAContact: fedora-i18n-bugs(a)redhat.com
CC: phuang(a)redhat.com, fedora-i18n-bugs(a)redhat.com
Estimated Hours: 0.0
Classification: Fedora
Target Release: ---
Description of problem:
using Fresh kde4 session, I have two ibus icons on my desktop and one ibus icon
was out of tray.
Version-Release number of selected component (if applicable):
ibus-0.1.1.20081023-3.fc11.i386
How reproducible:
Everytime during login
Steps to Reproduce:
1. run kde session (fresh if you can by remove ~/.kde/)
2.
3.
Actual results:
2 icons are there and only one dock in system tray
Expected results:
1) Should it not be only 1 icon per session?
Additional info:
1) I have 1 X session running on my mission
2)ps -auxx|grep ibus
Warning: bad syntax, perhaps a bogus '-'? See /usr/share/doc/procps-3.2.7/FAQ
aalam 3649 0.0 0.6 11200 6628 ? S 11:34 0:00 python
/usr/bin/ibus
aalam 3708 0.0 0.7 12468 7944 ? S 11:34 0:00 python
/usr/share/ibus/daemon/ibusdaemon.py
aalam 3711 0.0 0.7 12224 7500 ? S 11:35 0:00 python
/usr/share/ibus/gconf/main.py
aalam 3712 0.2 2.4 73312 24956 ? S 11:35 0:02 python
/usr/share/ibus/ui/gtk/main.py
aalam 3713 0.0 0.4 15772 4056 ? S 11:35 0:00
/usr/bin/ibus-x11 --kill-daemon
aalam 3739 0.0 0.7 12592 7812 ? S 11:35 0:00 python
/usr/share/ibus-m17n/engine/main.py pa:jhelum
root 4192 0.0 0.0 4484 716 pts/2 S+ 11:47 0:00 grep ibus
3)
kdebase-4.1.96-1.fc11.i386
--
Configure bugmail:
https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are on the CC list for the bug.