How to connect to ibus-daemon

Clash Royale CLAN TAG#URR8PPP up vote
1
down vote
favorite
In my terminal on Kubuntu 16.04 I frequently see the following:
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory
QFileSystemWatcher: failed to add paths: /home/iris/.config/ibus/bus
Bus::open: Can not get ibus-daemon's address.
IBusInputContext::createInputContext: no connection to ibus-daemon
It happens, for example, when I open a pdf with okular but it seems to happen in many instances, also when I've left my computer unattended for a while. I have not found anything that can help me get rid of these messages, maybe also because I don't know why I get these messages so I don't know very well what to search for. I've found this which suggests I start IBus in 'system -> preferences', but I have no clue where to find it in Kubuntu 16.04. I can only find 'system settings' which does not seem to be what I need.
I would like to know what this message means and how to prevent it from showing (I assume it indicates something is not working properly)
command-line kubuntu system ibus preferences
add a comment |Â
up vote
1
down vote
favorite
In my terminal on Kubuntu 16.04 I frequently see the following:
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory
QFileSystemWatcher: failed to add paths: /home/iris/.config/ibus/bus
Bus::open: Can not get ibus-daemon's address.
IBusInputContext::createInputContext: no connection to ibus-daemon
It happens, for example, when I open a pdf with okular but it seems to happen in many instances, also when I've left my computer unattended for a while. I have not found anything that can help me get rid of these messages, maybe also because I don't know why I get these messages so I don't know very well what to search for. I've found this which suggests I start IBus in 'system -> preferences', but I have no clue where to find it in Kubuntu 16.04. I can only find 'system settings' which does not seem to be what I need.
I would like to know what this message means and how to prevent it from showing (I assume it indicates something is not working properly)
command-line kubuntu system ibus preferences
1
That would make the question longer, but maybe that is better. I'll edit the question and add this information.
â Iris Hijne
Mar 6 at 9:34
this is a much better question; unfortunately I do not have the answer. however, check that the path mention exists
â ravery
Mar 6 at 9:45
Thanks, and indeed the path doesn't exist. There is no ibus in /home/iris/.config/
â Iris Hijne
Mar 6 at 9:48
I see exactly the same message when I open a pdf using okular from the terminal. Until now, I usually launch pdfs by clicking on them in Dolphin. Launching applications from the terminal is usual when trying to troubleshoot something. It isn't the preferred route. In short, don't worry unless something isn't working with the application, in this case okular.
â DK Bose
Mar 6 at 9:49
Incidentally, this terminal message doesn't show up in Kubuntu 18.04.
â DK Bose
Mar 6 at 9:57
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
In my terminal on Kubuntu 16.04 I frequently see the following:
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory
QFileSystemWatcher: failed to add paths: /home/iris/.config/ibus/bus
Bus::open: Can not get ibus-daemon's address.
IBusInputContext::createInputContext: no connection to ibus-daemon
It happens, for example, when I open a pdf with okular but it seems to happen in many instances, also when I've left my computer unattended for a while. I have not found anything that can help me get rid of these messages, maybe also because I don't know why I get these messages so I don't know very well what to search for. I've found this which suggests I start IBus in 'system -> preferences', but I have no clue where to find it in Kubuntu 16.04. I can only find 'system settings' which does not seem to be what I need.
I would like to know what this message means and how to prevent it from showing (I assume it indicates something is not working properly)
command-line kubuntu system ibus preferences
In my terminal on Kubuntu 16.04 I frequently see the following:
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory
QFileSystemWatcher: failed to add paths: /home/iris/.config/ibus/bus
Bus::open: Can not get ibus-daemon's address.
IBusInputContext::createInputContext: no connection to ibus-daemon
It happens, for example, when I open a pdf with okular but it seems to happen in many instances, also when I've left my computer unattended for a while. I have not found anything that can help me get rid of these messages, maybe also because I don't know why I get these messages so I don't know very well what to search for. I've found this which suggests I start IBus in 'system -> preferences', but I have no clue where to find it in Kubuntu 16.04. I can only find 'system settings' which does not seem to be what I need.
I would like to know what this message means and how to prevent it from showing (I assume it indicates something is not working properly)
command-line kubuntu system ibus preferences
command-line kubuntu system ibus preferences
edited Mar 6 at 9:40
asked Mar 6 at 9:25
Iris Hijne
63
63
1
That would make the question longer, but maybe that is better. I'll edit the question and add this information.
â Iris Hijne
Mar 6 at 9:34
this is a much better question; unfortunately I do not have the answer. however, check that the path mention exists
â ravery
Mar 6 at 9:45
Thanks, and indeed the path doesn't exist. There is no ibus in /home/iris/.config/
â Iris Hijne
Mar 6 at 9:48
I see exactly the same message when I open a pdf using okular from the terminal. Until now, I usually launch pdfs by clicking on them in Dolphin. Launching applications from the terminal is usual when trying to troubleshoot something. It isn't the preferred route. In short, don't worry unless something isn't working with the application, in this case okular.
â DK Bose
Mar 6 at 9:49
Incidentally, this terminal message doesn't show up in Kubuntu 18.04.
â DK Bose
Mar 6 at 9:57
add a comment |Â
1
That would make the question longer, but maybe that is better. I'll edit the question and add this information.
â Iris Hijne
Mar 6 at 9:34
this is a much better question; unfortunately I do not have the answer. however, check that the path mention exists
â ravery
Mar 6 at 9:45
Thanks, and indeed the path doesn't exist. There is no ibus in /home/iris/.config/
â Iris Hijne
Mar 6 at 9:48
I see exactly the same message when I open a pdf using okular from the terminal. Until now, I usually launch pdfs by clicking on them in Dolphin. Launching applications from the terminal is usual when trying to troubleshoot something. It isn't the preferred route. In short, don't worry unless something isn't working with the application, in this case okular.
â DK Bose
Mar 6 at 9:49
Incidentally, this terminal message doesn't show up in Kubuntu 18.04.
â DK Bose
Mar 6 at 9:57
1
1
That would make the question longer, but maybe that is better. I'll edit the question and add this information.
â Iris Hijne
Mar 6 at 9:34
That would make the question longer, but maybe that is better. I'll edit the question and add this information.
â Iris Hijne
Mar 6 at 9:34
this is a much better question; unfortunately I do not have the answer. however, check that the path mention exists
â ravery
Mar 6 at 9:45
this is a much better question; unfortunately I do not have the answer. however, check that the path mention exists
â ravery
Mar 6 at 9:45
Thanks, and indeed the path doesn't exist. There is no ibus in /home/iris/.config/
â Iris Hijne
Mar 6 at 9:48
Thanks, and indeed the path doesn't exist. There is no ibus in /home/iris/.config/
â Iris Hijne
Mar 6 at 9:48
I see exactly the same message when I open a pdf using okular from the terminal. Until now, I usually launch pdfs by clicking on them in Dolphin. Launching applications from the terminal is usual when trying to troubleshoot something. It isn't the preferred route. In short, don't worry unless something isn't working with the application, in this case okular.
â DK Bose
Mar 6 at 9:49
I see exactly the same message when I open a pdf using okular from the terminal. Until now, I usually launch pdfs by clicking on them in Dolphin. Launching applications from the terminal is usual when trying to troubleshoot something. It isn't the preferred route. In short, don't worry unless something isn't working with the application, in this case okular.
â DK Bose
Mar 6 at 9:49
Incidentally, this terminal message doesn't show up in Kubuntu 18.04.
â DK Bose
Mar 6 at 9:57
Incidentally, this terminal message doesn't show up in Kubuntu 18.04.
â DK Bose
Mar 6 at 9:57
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1012347%2fhow-to-connect-to-ibus-daemon%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
1
That would make the question longer, but maybe that is better. I'll edit the question and add this information.
â Iris Hijne
Mar 6 at 9:34
this is a much better question; unfortunately I do not have the answer. however, check that the path mention exists
â ravery
Mar 6 at 9:45
Thanks, and indeed the path doesn't exist. There is no ibus in /home/iris/.config/
â Iris Hijne
Mar 6 at 9:48
I see exactly the same message when I open a pdf using okular from the terminal. Until now, I usually launch pdfs by clicking on them in Dolphin. Launching applications from the terminal is usual when trying to troubleshoot something. It isn't the preferred route. In short, don't worry unless something isn't working with the application, in this case okular.
â DK Bose
Mar 6 at 9:49
Incidentally, this terminal message doesn't show up in Kubuntu 18.04.
â DK Bose
Mar 6 at 9:57