“Error found when loading /etc/profile”





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







5















The following problem persists even after upgrading from 17.10 to 18.04:



After upgrading my Kubuntu 17.04 to 17.10 by running



do-release-upgrade


I get the following error message after each reboot.



Error found when loading /etc/profile:nn/usr/share/im-    
config/data/21_ibus.rc line 6: /usr/bin/ibus-daemon: No such
file or directorynnAs a result the session will not be configured correctly.
You should fix the problem as soon as feasible.


IMG:



cat -n /usr/share/im-config/data/21_ibus.rc


Line 6 reads:



IBUS_ENABLE_SYNC_MODE=0 /usr/bin/ibus-daemon --daemonize --xim --address 'unix:tmpdir=/tmp/ibus'


Unfortunately I don't know what this is. Indeed there is no file /usr/bin/ibus-daemon



Also:



bruni@Inspiron-5547:~$ sudo apt purge ibus
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package 'ibus' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.


How could I fix the problem as soon as feasible?



why is there a /usr/share/im-config/data/21_ibus.rc used when ibus is not installed?



EDIT
I guess the culprit in my /etc/profile is the file /etc/profile.d/input-method-config.sh



This reads:



# /etc/profile.d/input-method-config.sh              
#
# This is a temporary measure which works around
# https://launchpad.net/bugs/1720250

if [ -z "$XDG_CURRENT_DESKTOP" -o -n "$GTK_IM_MODULE" ]; then
return
fi

. /etc/X11/Xsession.d/70im-config_launch
if [ "$IM_CONFIG_PHASE" = 1 ]; then
export IM_CONFIG_PHASE=2
. /usr/share/im-config/xinputrc.common
if [ -r "$IM_CONFIG_XINPUTRC_USR" ]; then
. $IM_CONFIG_XINPUTRC_USR
elif [ -r "$IM_CONFIG_XINPUTRC_SYS" ]; then
. $IM_CONFIG_XINPUTRC_SYS
fi
export XMODIFIERS
export GTK_IM_MODULE
export QT_IM_MODULE
export QT4_IM_MODULE
export CLUTTER_IM_MODULE
fi


also:



echo $XDG_CURRENT_DESKTOP                                                
KDE


and



echo $GTK_IM_MODULE
ibus


I guess the problem is that $GTK_IM_MODULE returns ibus, even though ibus is not installed and not used.



Installing ibus removes the problem described in the question at hand, but leads to the more severe problem described in this question, so I removed ibus again.










share|improve this question

























  • 17.10 uses a new desktop and wayland, A reboot will likely solve the issue

    – ravery
    Oct 20 '17 at 13:51











  • @ravery I don't know if the new desktop should be relevant as I use Kubuntu (KDE), but I will reboot as soon as my backup is in place.

    – Bruni
    Oct 20 '17 at 13:53











  • KDE does not use wayland; however, the update still might have changed the profile.

    – ravery
    Oct 20 '17 at 13:55











  • @ravery Reboot did not solve the problem.

    – Bruni
    Oct 20 '17 at 14:20











  • I got the same error after do-release-upgrade from 18.04 to 18.10

    – stokito
    Oct 20 '18 at 18:12


















5















The following problem persists even after upgrading from 17.10 to 18.04:



After upgrading my Kubuntu 17.04 to 17.10 by running



do-release-upgrade


I get the following error message after each reboot.



Error found when loading /etc/profile:nn/usr/share/im-    
config/data/21_ibus.rc line 6: /usr/bin/ibus-daemon: No such
file or directorynnAs a result the session will not be configured correctly.
You should fix the problem as soon as feasible.


IMG:



cat -n /usr/share/im-config/data/21_ibus.rc


Line 6 reads:



IBUS_ENABLE_SYNC_MODE=0 /usr/bin/ibus-daemon --daemonize --xim --address 'unix:tmpdir=/tmp/ibus'


Unfortunately I don't know what this is. Indeed there is no file /usr/bin/ibus-daemon



Also:



bruni@Inspiron-5547:~$ sudo apt purge ibus
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package 'ibus' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.


How could I fix the problem as soon as feasible?



why is there a /usr/share/im-config/data/21_ibus.rc used when ibus is not installed?



EDIT
I guess the culprit in my /etc/profile is the file /etc/profile.d/input-method-config.sh



This reads:



# /etc/profile.d/input-method-config.sh              
#
# This is a temporary measure which works around
# https://launchpad.net/bugs/1720250

if [ -z "$XDG_CURRENT_DESKTOP" -o -n "$GTK_IM_MODULE" ]; then
return
fi

. /etc/X11/Xsession.d/70im-config_launch
if [ "$IM_CONFIG_PHASE" = 1 ]; then
export IM_CONFIG_PHASE=2
. /usr/share/im-config/xinputrc.common
if [ -r "$IM_CONFIG_XINPUTRC_USR" ]; then
. $IM_CONFIG_XINPUTRC_USR
elif [ -r "$IM_CONFIG_XINPUTRC_SYS" ]; then
. $IM_CONFIG_XINPUTRC_SYS
fi
export XMODIFIERS
export GTK_IM_MODULE
export QT_IM_MODULE
export QT4_IM_MODULE
export CLUTTER_IM_MODULE
fi


also:



echo $XDG_CURRENT_DESKTOP                                                
KDE


and



echo $GTK_IM_MODULE
ibus


I guess the problem is that $GTK_IM_MODULE returns ibus, even though ibus is not installed and not used.



Installing ibus removes the problem described in the question at hand, but leads to the more severe problem described in this question, so I removed ibus again.










share|improve this question

























  • 17.10 uses a new desktop and wayland, A reboot will likely solve the issue

    – ravery
    Oct 20 '17 at 13:51











  • @ravery I don't know if the new desktop should be relevant as I use Kubuntu (KDE), but I will reboot as soon as my backup is in place.

    – Bruni
    Oct 20 '17 at 13:53











  • KDE does not use wayland; however, the update still might have changed the profile.

    – ravery
    Oct 20 '17 at 13:55











  • @ravery Reboot did not solve the problem.

    – Bruni
    Oct 20 '17 at 14:20











  • I got the same error after do-release-upgrade from 18.04 to 18.10

    – stokito
    Oct 20 '18 at 18:12














5












5








5








The following problem persists even after upgrading from 17.10 to 18.04:



After upgrading my Kubuntu 17.04 to 17.10 by running



do-release-upgrade


I get the following error message after each reboot.



Error found when loading /etc/profile:nn/usr/share/im-    
config/data/21_ibus.rc line 6: /usr/bin/ibus-daemon: No such
file or directorynnAs a result the session will not be configured correctly.
You should fix the problem as soon as feasible.


IMG:



cat -n /usr/share/im-config/data/21_ibus.rc


Line 6 reads:



IBUS_ENABLE_SYNC_MODE=0 /usr/bin/ibus-daemon --daemonize --xim --address 'unix:tmpdir=/tmp/ibus'


Unfortunately I don't know what this is. Indeed there is no file /usr/bin/ibus-daemon



Also:



bruni@Inspiron-5547:~$ sudo apt purge ibus
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package 'ibus' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.


How could I fix the problem as soon as feasible?



why is there a /usr/share/im-config/data/21_ibus.rc used when ibus is not installed?



EDIT
I guess the culprit in my /etc/profile is the file /etc/profile.d/input-method-config.sh



This reads:



# /etc/profile.d/input-method-config.sh              
#
# This is a temporary measure which works around
# https://launchpad.net/bugs/1720250

if [ -z "$XDG_CURRENT_DESKTOP" -o -n "$GTK_IM_MODULE" ]; then
return
fi

. /etc/X11/Xsession.d/70im-config_launch
if [ "$IM_CONFIG_PHASE" = 1 ]; then
export IM_CONFIG_PHASE=2
. /usr/share/im-config/xinputrc.common
if [ -r "$IM_CONFIG_XINPUTRC_USR" ]; then
. $IM_CONFIG_XINPUTRC_USR
elif [ -r "$IM_CONFIG_XINPUTRC_SYS" ]; then
. $IM_CONFIG_XINPUTRC_SYS
fi
export XMODIFIERS
export GTK_IM_MODULE
export QT_IM_MODULE
export QT4_IM_MODULE
export CLUTTER_IM_MODULE
fi


also:



echo $XDG_CURRENT_DESKTOP                                                
KDE


and



echo $GTK_IM_MODULE
ibus


I guess the problem is that $GTK_IM_MODULE returns ibus, even though ibus is not installed and not used.



Installing ibus removes the problem described in the question at hand, but leads to the more severe problem described in this question, so I removed ibus again.










share|improve this question
















The following problem persists even after upgrading from 17.10 to 18.04:



After upgrading my Kubuntu 17.04 to 17.10 by running



do-release-upgrade


I get the following error message after each reboot.



Error found when loading /etc/profile:nn/usr/share/im-    
config/data/21_ibus.rc line 6: /usr/bin/ibus-daemon: No such
file or directorynnAs a result the session will not be configured correctly.
You should fix the problem as soon as feasible.


IMG:



cat -n /usr/share/im-config/data/21_ibus.rc


Line 6 reads:



IBUS_ENABLE_SYNC_MODE=0 /usr/bin/ibus-daemon --daemonize --xim --address 'unix:tmpdir=/tmp/ibus'


Unfortunately I don't know what this is. Indeed there is no file /usr/bin/ibus-daemon



Also:



bruni@Inspiron-5547:~$ sudo apt purge ibus
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package 'ibus' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.


How could I fix the problem as soon as feasible?



why is there a /usr/share/im-config/data/21_ibus.rc used when ibus is not installed?



EDIT
I guess the culprit in my /etc/profile is the file /etc/profile.d/input-method-config.sh



This reads:



# /etc/profile.d/input-method-config.sh              
#
# This is a temporary measure which works around
# https://launchpad.net/bugs/1720250

if [ -z "$XDG_CURRENT_DESKTOP" -o -n "$GTK_IM_MODULE" ]; then
return
fi

. /etc/X11/Xsession.d/70im-config_launch
if [ "$IM_CONFIG_PHASE" = 1 ]; then
export IM_CONFIG_PHASE=2
. /usr/share/im-config/xinputrc.common
if [ -r "$IM_CONFIG_XINPUTRC_USR" ]; then
. $IM_CONFIG_XINPUTRC_USR
elif [ -r "$IM_CONFIG_XINPUTRC_SYS" ]; then
. $IM_CONFIG_XINPUTRC_SYS
fi
export XMODIFIERS
export GTK_IM_MODULE
export QT_IM_MODULE
export QT4_IM_MODULE
export CLUTTER_IM_MODULE
fi


also:



echo $XDG_CURRENT_DESKTOP                                                
KDE


and



echo $GTK_IM_MODULE
ibus


I guess the problem is that $GTK_IM_MODULE returns ibus, even though ibus is not installed and not used.



Installing ibus removes the problem described in the question at hand, but leads to the more severe problem described in this question, so I removed ibus again.







ibus 17.10






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Feb 20 at 6:45









karel

61.1k13132155




61.1k13132155










asked Oct 20 '17 at 13:45









BruniBruni

5,41642857




5,41642857













  • 17.10 uses a new desktop and wayland, A reboot will likely solve the issue

    – ravery
    Oct 20 '17 at 13:51











  • @ravery I don't know if the new desktop should be relevant as I use Kubuntu (KDE), but I will reboot as soon as my backup is in place.

    – Bruni
    Oct 20 '17 at 13:53











  • KDE does not use wayland; however, the update still might have changed the profile.

    – ravery
    Oct 20 '17 at 13:55











  • @ravery Reboot did not solve the problem.

    – Bruni
    Oct 20 '17 at 14:20











  • I got the same error after do-release-upgrade from 18.04 to 18.10

    – stokito
    Oct 20 '18 at 18:12



















  • 17.10 uses a new desktop and wayland, A reboot will likely solve the issue

    – ravery
    Oct 20 '17 at 13:51











  • @ravery I don't know if the new desktop should be relevant as I use Kubuntu (KDE), but I will reboot as soon as my backup is in place.

    – Bruni
    Oct 20 '17 at 13:53











  • KDE does not use wayland; however, the update still might have changed the profile.

    – ravery
    Oct 20 '17 at 13:55











  • @ravery Reboot did not solve the problem.

    – Bruni
    Oct 20 '17 at 14:20











  • I got the same error after do-release-upgrade from 18.04 to 18.10

    – stokito
    Oct 20 '18 at 18:12

















17.10 uses a new desktop and wayland, A reboot will likely solve the issue

– ravery
Oct 20 '17 at 13:51





17.10 uses a new desktop and wayland, A reboot will likely solve the issue

– ravery
Oct 20 '17 at 13:51













@ravery I don't know if the new desktop should be relevant as I use Kubuntu (KDE), but I will reboot as soon as my backup is in place.

– Bruni
Oct 20 '17 at 13:53





@ravery I don't know if the new desktop should be relevant as I use Kubuntu (KDE), but I will reboot as soon as my backup is in place.

– Bruni
Oct 20 '17 at 13:53













KDE does not use wayland; however, the update still might have changed the profile.

– ravery
Oct 20 '17 at 13:55





KDE does not use wayland; however, the update still might have changed the profile.

– ravery
Oct 20 '17 at 13:55













@ravery Reboot did not solve the problem.

– Bruni
Oct 20 '17 at 14:20





@ravery Reboot did not solve the problem.

– Bruni
Oct 20 '17 at 14:20













I got the same error after do-release-upgrade from 18.04 to 18.10

– stokito
Oct 20 '18 at 18:12





I got the same error after do-release-upgrade from 18.04 to 18.10

– stokito
Oct 20 '18 at 18:12










5 Answers
5






active

oldest

votes


















5














Same thing happened to my when upgrading Mate to 17.10.



I went to System -> Preferences -> Look and Feel -> Language Support.



I'd previously selected English (UK) as my menu/windows language so on first opening this up I was prompted to upgrade, which I did.



My intention, and what I went on to do, was to change the "keyboard input method system" from "XIM" to "None". Rebooted, and that seemed to clear the error message at login without any other ill effects - so far!



My logic... I don't have ibus on my machine and I didn't see the need for it if I don't need exotic fonts. My default display manager is lightdm, so that would trip the first condition in the 21_ibus.rc file, taking me to line 6, which seems to disable the IBUS_SYNC mode and force XIM. Again, not installing ibus, so can't use the ibus-deamon, therefore I can't have the XIM option - so I switched the keyboard option, as indicated above, and that seemed to work.



To do that on KDE open a terminal and type



 im-config -n none


Suspect it's a minor configuration issue, but would welcome learning if there's a more robust solution.






share|improve this answer

































    3














    I had the same issue after upgrade to 17.10. Temporary work around by set the keyboard input method system to none in language support.






    share|improve this answer
























    • Where is that setting in Kubuntu?

      – Bruni
      Oct 25 '17 at 6:15



















    1














    You appear to be affected by this bug I would suggest that you subscribe to it so that you can be notified about progress. You should also click and answer the "Does this bug affect you?" question so that the developers can get an idea of the extent of the issue.






    share|improve this answer
























    • I am not sure this is indeed the case. I am able to write in Greek, english and German (Αβγδςüäö) without any problems. Also this bug seems to be quite old whereas I have encountered the above message only after updating from 17.04 to 17.10.

      – Bruni
      Oct 20 '17 at 14:12











    • @Bruni I'm not certain either, it could be a regression, or not. However as the bug was never Assigned and I can't seem to find anything that states it was fixed, it seemed a logical response. Perhaps someone will come along and provide an answer that's more to your liking. Cheers! :-)

      – Elder Geek
      Oct 20 '17 at 14:19



















    1














    Bruni: I don't use KDE, nor fcitx, so can't directly check, but nearest thing I can find to help show you options I was referring to is here...



    http://www.makeuseof.com/tag/write-language-linux/



    ...where you can see the "keyboard input method system" for GTK, and, what I assume is the equivalent "Configure input method" for KDE.



    Again, I don't have ibus, so there's no point trying to start xim server from ibus deamon, which is why selecting "None" is a convenient fix for my requirements. If you have fcitx installed and you have fcitx set in your "Configure input method" and you're still tripping an ibus trap then there's a configuration problem somewhere down the /etc/profile.






    share|improve this answer
























    • Thank. I am aware of these settings. However, there is no option to select the backend.

      – Bruni
      Oct 26 '17 at 6:34



















    0














    I run into almost the same error. I have reinstalled ibus using Synaptic. All Good now!



    ibus Synaptic reinstall



    I hope it works for you as well.






    share|improve this answer


























    • Hello and welcome to askubuntu. As already mentioned in the question, installing ibus was not an option for me, as this led to a much more severe problem.

      – Bruni
      Mar 24 at 8:16












    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "89"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f966775%2ferror-found-when-loading-etc-profile%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    5 Answers
    5






    active

    oldest

    votes








    5 Answers
    5






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    5














    Same thing happened to my when upgrading Mate to 17.10.



    I went to System -> Preferences -> Look and Feel -> Language Support.



    I'd previously selected English (UK) as my menu/windows language so on first opening this up I was prompted to upgrade, which I did.



    My intention, and what I went on to do, was to change the "keyboard input method system" from "XIM" to "None". Rebooted, and that seemed to clear the error message at login without any other ill effects - so far!



    My logic... I don't have ibus on my machine and I didn't see the need for it if I don't need exotic fonts. My default display manager is lightdm, so that would trip the first condition in the 21_ibus.rc file, taking me to line 6, which seems to disable the IBUS_SYNC mode and force XIM. Again, not installing ibus, so can't use the ibus-deamon, therefore I can't have the XIM option - so I switched the keyboard option, as indicated above, and that seemed to work.



    To do that on KDE open a terminal and type



     im-config -n none


    Suspect it's a minor configuration issue, but would welcome learning if there's a more robust solution.






    share|improve this answer






























      5














      Same thing happened to my when upgrading Mate to 17.10.



      I went to System -> Preferences -> Look and Feel -> Language Support.



      I'd previously selected English (UK) as my menu/windows language so on first opening this up I was prompted to upgrade, which I did.



      My intention, and what I went on to do, was to change the "keyboard input method system" from "XIM" to "None". Rebooted, and that seemed to clear the error message at login without any other ill effects - so far!



      My logic... I don't have ibus on my machine and I didn't see the need for it if I don't need exotic fonts. My default display manager is lightdm, so that would trip the first condition in the 21_ibus.rc file, taking me to line 6, which seems to disable the IBUS_SYNC mode and force XIM. Again, not installing ibus, so can't use the ibus-deamon, therefore I can't have the XIM option - so I switched the keyboard option, as indicated above, and that seemed to work.



      To do that on KDE open a terminal and type



       im-config -n none


      Suspect it's a minor configuration issue, but would welcome learning if there's a more robust solution.






      share|improve this answer




























        5












        5








        5







        Same thing happened to my when upgrading Mate to 17.10.



        I went to System -> Preferences -> Look and Feel -> Language Support.



        I'd previously selected English (UK) as my menu/windows language so on first opening this up I was prompted to upgrade, which I did.



        My intention, and what I went on to do, was to change the "keyboard input method system" from "XIM" to "None". Rebooted, and that seemed to clear the error message at login without any other ill effects - so far!



        My logic... I don't have ibus on my machine and I didn't see the need for it if I don't need exotic fonts. My default display manager is lightdm, so that would trip the first condition in the 21_ibus.rc file, taking me to line 6, which seems to disable the IBUS_SYNC mode and force XIM. Again, not installing ibus, so can't use the ibus-deamon, therefore I can't have the XIM option - so I switched the keyboard option, as indicated above, and that seemed to work.



        To do that on KDE open a terminal and type



         im-config -n none


        Suspect it's a minor configuration issue, but would welcome learning if there's a more robust solution.






        share|improve this answer















        Same thing happened to my when upgrading Mate to 17.10.



        I went to System -> Preferences -> Look and Feel -> Language Support.



        I'd previously selected English (UK) as my menu/windows language so on first opening this up I was prompted to upgrade, which I did.



        My intention, and what I went on to do, was to change the "keyboard input method system" from "XIM" to "None". Rebooted, and that seemed to clear the error message at login without any other ill effects - so far!



        My logic... I don't have ibus on my machine and I didn't see the need for it if I don't need exotic fonts. My default display manager is lightdm, so that would trip the first condition in the 21_ibus.rc file, taking me to line 6, which seems to disable the IBUS_SYNC mode and force XIM. Again, not installing ibus, so can't use the ibus-deamon, therefore I can't have the XIM option - so I switched the keyboard option, as indicated above, and that seemed to work.



        To do that on KDE open a terminal and type



         im-config -n none


        Suspect it's a minor configuration issue, but would welcome learning if there's a more robust solution.







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Jun 27 '18 at 16:34









        Bruni

        5,41642857




        5,41642857










        answered Oct 25 '17 at 14:07









        CrerarCrerar

        661




        661

























            3














            I had the same issue after upgrade to 17.10. Temporary work around by set the keyboard input method system to none in language support.






            share|improve this answer
























            • Where is that setting in Kubuntu?

              – Bruni
              Oct 25 '17 at 6:15
















            3














            I had the same issue after upgrade to 17.10. Temporary work around by set the keyboard input method system to none in language support.






            share|improve this answer
























            • Where is that setting in Kubuntu?

              – Bruni
              Oct 25 '17 at 6:15














            3












            3








            3







            I had the same issue after upgrade to 17.10. Temporary work around by set the keyboard input method system to none in language support.






            share|improve this answer













            I had the same issue after upgrade to 17.10. Temporary work around by set the keyboard input method system to none in language support.







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Oct 25 '17 at 1:30









            Jeff YeJeff Ye

            311




            311













            • Where is that setting in Kubuntu?

              – Bruni
              Oct 25 '17 at 6:15



















            • Where is that setting in Kubuntu?

              – Bruni
              Oct 25 '17 at 6:15

















            Where is that setting in Kubuntu?

            – Bruni
            Oct 25 '17 at 6:15





            Where is that setting in Kubuntu?

            – Bruni
            Oct 25 '17 at 6:15











            1














            You appear to be affected by this bug I would suggest that you subscribe to it so that you can be notified about progress. You should also click and answer the "Does this bug affect you?" question so that the developers can get an idea of the extent of the issue.






            share|improve this answer
























            • I am not sure this is indeed the case. I am able to write in Greek, english and German (Αβγδςüäö) without any problems. Also this bug seems to be quite old whereas I have encountered the above message only after updating from 17.04 to 17.10.

              – Bruni
              Oct 20 '17 at 14:12











            • @Bruni I'm not certain either, it could be a regression, or not. However as the bug was never Assigned and I can't seem to find anything that states it was fixed, it seemed a logical response. Perhaps someone will come along and provide an answer that's more to your liking. Cheers! :-)

              – Elder Geek
              Oct 20 '17 at 14:19
















            1














            You appear to be affected by this bug I would suggest that you subscribe to it so that you can be notified about progress. You should also click and answer the "Does this bug affect you?" question so that the developers can get an idea of the extent of the issue.






            share|improve this answer
























            • I am not sure this is indeed the case. I am able to write in Greek, english and German (Αβγδςüäö) without any problems. Also this bug seems to be quite old whereas I have encountered the above message only after updating from 17.04 to 17.10.

              – Bruni
              Oct 20 '17 at 14:12











            • @Bruni I'm not certain either, it could be a regression, or not. However as the bug was never Assigned and I can't seem to find anything that states it was fixed, it seemed a logical response. Perhaps someone will come along and provide an answer that's more to your liking. Cheers! :-)

              – Elder Geek
              Oct 20 '17 at 14:19














            1












            1








            1







            You appear to be affected by this bug I would suggest that you subscribe to it so that you can be notified about progress. You should also click and answer the "Does this bug affect you?" question so that the developers can get an idea of the extent of the issue.






            share|improve this answer













            You appear to be affected by this bug I would suggest that you subscribe to it so that you can be notified about progress. You should also click and answer the "Does this bug affect you?" question so that the developers can get an idea of the extent of the issue.







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Oct 20 '17 at 14:01









            Elder GeekElder Geek

            27.6k1055130




            27.6k1055130













            • I am not sure this is indeed the case. I am able to write in Greek, english and German (Αβγδςüäö) without any problems. Also this bug seems to be quite old whereas I have encountered the above message only after updating from 17.04 to 17.10.

              – Bruni
              Oct 20 '17 at 14:12











            • @Bruni I'm not certain either, it could be a regression, or not. However as the bug was never Assigned and I can't seem to find anything that states it was fixed, it seemed a logical response. Perhaps someone will come along and provide an answer that's more to your liking. Cheers! :-)

              – Elder Geek
              Oct 20 '17 at 14:19



















            • I am not sure this is indeed the case. I am able to write in Greek, english and German (Αβγδςüäö) without any problems. Also this bug seems to be quite old whereas I have encountered the above message only after updating from 17.04 to 17.10.

              – Bruni
              Oct 20 '17 at 14:12











            • @Bruni I'm not certain either, it could be a regression, or not. However as the bug was never Assigned and I can't seem to find anything that states it was fixed, it seemed a logical response. Perhaps someone will come along and provide an answer that's more to your liking. Cheers! :-)

              – Elder Geek
              Oct 20 '17 at 14:19

















            I am not sure this is indeed the case. I am able to write in Greek, english and German (Αβγδςüäö) without any problems. Also this bug seems to be quite old whereas I have encountered the above message only after updating from 17.04 to 17.10.

            – Bruni
            Oct 20 '17 at 14:12





            I am not sure this is indeed the case. I am able to write in Greek, english and German (Αβγδςüäö) without any problems. Also this bug seems to be quite old whereas I have encountered the above message only after updating from 17.04 to 17.10.

            – Bruni
            Oct 20 '17 at 14:12













            @Bruni I'm not certain either, it could be a regression, or not. However as the bug was never Assigned and I can't seem to find anything that states it was fixed, it seemed a logical response. Perhaps someone will come along and provide an answer that's more to your liking. Cheers! :-)

            – Elder Geek
            Oct 20 '17 at 14:19





            @Bruni I'm not certain either, it could be a regression, or not. However as the bug was never Assigned and I can't seem to find anything that states it was fixed, it seemed a logical response. Perhaps someone will come along and provide an answer that's more to your liking. Cheers! :-)

            – Elder Geek
            Oct 20 '17 at 14:19











            1














            Bruni: I don't use KDE, nor fcitx, so can't directly check, but nearest thing I can find to help show you options I was referring to is here...



            http://www.makeuseof.com/tag/write-language-linux/



            ...where you can see the "keyboard input method system" for GTK, and, what I assume is the equivalent "Configure input method" for KDE.



            Again, I don't have ibus, so there's no point trying to start xim server from ibus deamon, which is why selecting "None" is a convenient fix for my requirements. If you have fcitx installed and you have fcitx set in your "Configure input method" and you're still tripping an ibus trap then there's a configuration problem somewhere down the /etc/profile.






            share|improve this answer
























            • Thank. I am aware of these settings. However, there is no option to select the backend.

              – Bruni
              Oct 26 '17 at 6:34
















            1














            Bruni: I don't use KDE, nor fcitx, so can't directly check, but nearest thing I can find to help show you options I was referring to is here...



            http://www.makeuseof.com/tag/write-language-linux/



            ...where you can see the "keyboard input method system" for GTK, and, what I assume is the equivalent "Configure input method" for KDE.



            Again, I don't have ibus, so there's no point trying to start xim server from ibus deamon, which is why selecting "None" is a convenient fix for my requirements. If you have fcitx installed and you have fcitx set in your "Configure input method" and you're still tripping an ibus trap then there's a configuration problem somewhere down the /etc/profile.






            share|improve this answer
























            • Thank. I am aware of these settings. However, there is no option to select the backend.

              – Bruni
              Oct 26 '17 at 6:34














            1












            1








            1







            Bruni: I don't use KDE, nor fcitx, so can't directly check, but nearest thing I can find to help show you options I was referring to is here...



            http://www.makeuseof.com/tag/write-language-linux/



            ...where you can see the "keyboard input method system" for GTK, and, what I assume is the equivalent "Configure input method" for KDE.



            Again, I don't have ibus, so there's no point trying to start xim server from ibus deamon, which is why selecting "None" is a convenient fix for my requirements. If you have fcitx installed and you have fcitx set in your "Configure input method" and you're still tripping an ibus trap then there's a configuration problem somewhere down the /etc/profile.






            share|improve this answer













            Bruni: I don't use KDE, nor fcitx, so can't directly check, but nearest thing I can find to help show you options I was referring to is here...



            http://www.makeuseof.com/tag/write-language-linux/



            ...where you can see the "keyboard input method system" for GTK, and, what I assume is the equivalent "Configure input method" for KDE.



            Again, I don't have ibus, so there's no point trying to start xim server from ibus deamon, which is why selecting "None" is a convenient fix for my requirements. If you have fcitx installed and you have fcitx set in your "Configure input method" and you're still tripping an ibus trap then there's a configuration problem somewhere down the /etc/profile.







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Oct 26 '17 at 1:04









            OwlyOwly

            211




            211













            • Thank. I am aware of these settings. However, there is no option to select the backend.

              – Bruni
              Oct 26 '17 at 6:34



















            • Thank. I am aware of these settings. However, there is no option to select the backend.

              – Bruni
              Oct 26 '17 at 6:34

















            Thank. I am aware of these settings. However, there is no option to select the backend.

            – Bruni
            Oct 26 '17 at 6:34





            Thank. I am aware of these settings. However, there is no option to select the backend.

            – Bruni
            Oct 26 '17 at 6:34











            0














            I run into almost the same error. I have reinstalled ibus using Synaptic. All Good now!



            ibus Synaptic reinstall



            I hope it works for you as well.






            share|improve this answer


























            • Hello and welcome to askubuntu. As already mentioned in the question, installing ibus was not an option for me, as this led to a much more severe problem.

              – Bruni
              Mar 24 at 8:16
















            0














            I run into almost the same error. I have reinstalled ibus using Synaptic. All Good now!



            ibus Synaptic reinstall



            I hope it works for you as well.






            share|improve this answer


























            • Hello and welcome to askubuntu. As already mentioned in the question, installing ibus was not an option for me, as this led to a much more severe problem.

              – Bruni
              Mar 24 at 8:16














            0












            0








            0







            I run into almost the same error. I have reinstalled ibus using Synaptic. All Good now!



            ibus Synaptic reinstall



            I hope it works for you as well.






            share|improve this answer















            I run into almost the same error. I have reinstalled ibus using Synaptic. All Good now!



            ibus Synaptic reinstall



            I hope it works for you as well.







            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited Nov 18 '18 at 20:55









            David Foerster

            28.7k1367113




            28.7k1367113










            answered Nov 18 '18 at 20:18









            CiprianCiprian

            12




            12













            • Hello and welcome to askubuntu. As already mentioned in the question, installing ibus was not an option for me, as this led to a much more severe problem.

              – Bruni
              Mar 24 at 8:16



















            • Hello and welcome to askubuntu. As already mentioned in the question, installing ibus was not an option for me, as this led to a much more severe problem.

              – Bruni
              Mar 24 at 8:16

















            Hello and welcome to askubuntu. As already mentioned in the question, installing ibus was not an option for me, as this led to a much more severe problem.

            – Bruni
            Mar 24 at 8:16





            Hello and welcome to askubuntu. As already mentioned in the question, installing ibus was not an option for me, as this led to a much more severe problem.

            – Bruni
            Mar 24 at 8:16


















            draft saved

            draft discarded




















































            Thanks for contributing an answer to Ask Ubuntu!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f966775%2ferror-found-when-loading-etc-profile%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            How to change which sound is reproduced for terminal bell?

            Can I use Tabulator js library in my java Spring + Thymeleaf project?

            Title Spacing in Bjornstrup Chapter, Removing Chapter Number From Contents