It's not clear to me why you would want to kill the ibus-daemon process
in the first place. It's setup (via im-config) to be started and
configured at login.
As regards commands to start ibus from terminal it differs depending on
the desktop environment.
GNOME:
ibus-daemon --panel disable --xim -d
Other desktop environments:
ibus-daemon --xim -d
In situations where ibus crashes somehow, and IM inputting stops
working, you normally can do:
ibus restart
to fix it.
** Changed in: ibus (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1922186
Title:
ibus very difficult to restart
Status in ibus package in Ubuntu:
Incomplete
Bug description:
After closing ibus by task bar -> icon -> rightclick -> `Close` it
seems to be impossible to restart it.
Here some ways that should work and how they fail:
1) Menu -> ibus
-----------------
- opens iBus settings
- starts ibus service
Problems:
- No keyboard input is actually processed; I.e. cannot use keyboard then.
- Service is not daemonized; I.e. as soon as the iBus settings window is
closed, the services quits.
Suggestion:
- No keyboard input possible seems to be a bug -> should be fixed.
- Service should be daemonized at this point
2) terminal -> `ibus start`
---------------------------
Problems:
- This command does not exist. One has to know, that `ibus-daemon` is the
one they are searching for.
Suggestions:
- Implement this command to start the daemon from here
3) terminal -> `ibus-daemon &` / `ibus-daemon -d`
-------------------------------------------------
- brings up ibus with usable keyboard (good)
Problems:
- As soon as terminal gets closed, ibus-daemon quits
4) terminal -> `nohup ibus-daemon &`
-------------------------------------------------
- brings up ibus with usable keyboard (good)
Problem:
- As soon as terminal gets closed, ibus-daemon quits (very strange.
something I wouldn't expect from a `nohup` call, by the way).
System
=======
- I use ibus in conjunction with ibus-anthy
lsb_release -rd
----------------------
Description: Ubuntu 20.10
Release: 20.10
apt-cache policy ibus
----------------------
ibus:
Installed: 1.5.23-0ubuntu1
Candidate: 1.5.23-0ubuntu1
Version table:
*** 1.5.23-0ubuntu1 500
500 http://archive.ubuntu.com/ubuntu groovy/main amd64 Packages
100 /var/lib/dpkg/status
apt-cache policy ibus-anthy
----------------------
ibus-anthy:
Installed: 1.5.11-1build1
Candidate: 1.5.11-1build1
Version table:
*** 1.5.11-1build1 500
500 http://archive.ubuntu.com/ubuntu groovy/universe amd64 Packages
100 /var/lib/dpkg/status
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: ibus 1.5.23-0ubuntu1
ProcVersionSignature: Ubuntu 5.8.0-45.51-generic 5.8.18
Uname: Linux 5.8.0-45-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.5
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Thu Apr 1 15:33:00 2021
RebootRequiredPkgs:
linux-image-5.8.0-48-generic
linux-base
linux-image-5.8.0-49-generic
linux-base
SourcePackage: ibus
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1922186/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
