Ubuntu Gnome Error after updating to Ubuntu 17.10

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP








up vote
0
down vote

favorite












after updating ubuntu gnome, I get a black screen with an error window every time I log in. I can just click ok and continue, but after a month or so of ignoring it I figured I should fix it. Anybody able to help me?



The error window looks like this:



Error found when loading /etc/profile:

Locale: Cannot set LC_ALL to default locale: No such file or directory
Locale: Cannot set LC_ALL to default locale: No such file or directory

As a result the session will not be configured correctly. You should fix the problem as soon as feasible.


The file contains these lines:




# /etc/profile: system-wide .profile file for the Bourne shell (sh(1))
# and Bourne compatible shells (bash(1), ksh(1), ash(1), ...).

if [ "$PS1-" ]; then
 if [ "$BASH-" ] && [ "$BASH" != "/bin/sh" ]; then
 # The file bash.bashrc already sets the default PS1.
 # PS1='h:w$ '
 if [ -f /etc/bash.bashrc ]; then
 . /etc/bash.bashrc
 fi
 else
 if [ "`id -u`" -eq 0 ]; then
 PS1='# '
 else
 PS1='$ '
 fi
 fi
fi

if [ -d /etc/profile.d ]; then
 for i in /etc/profile.d/*.sh; do
 if [ -r $i ]; then
 . $i
 fi
 done
 unset i
fi






gnome login 17.10







share|improve this question























  • have you looked at etc/profile to see what the line is pointing to? can you add to your post the contents of etc/profile .. just checked my profile and I don't see LC_ALL so it may be something you have installed that is setting that "path" I looked up LC_ALL and found it has something to do with It forces applications to use the default language for output and probably not really necessary.. you probably can get away with commenting out that line in the file by adding a # before it .. but again .. it would be best if we could see the file and see if we can see an error in the line.
    – John Orion
    Mar 29 at 18:10










  • Ok thanks, there you go, I added it!
    – Sojan Janso
    Mar 29 at 22:11











  • hmm ok that's odd ... the LC_ALL isn't even listed. I expected to see something like LC_ALL=en_US.UTF-8 or something like that .....ok it also looks in /etc/profile.d .. check /etc/profile.d folder and see if there are any files in there and if any of those files list the LC_ALL line. if you still don't see it check your ~/.profile and see if LC_ALL is listed in there. I found something close in a file called cedilla-portuguese.sh that says export LC_CTYPE="$LC_IDENTIFICATION%.*.UTF-8" but nothing that says LC_ALL= sorry, im just guessing, im not real familiar with this error
    – John Orion
    Mar 29 at 23:35











  • I have a suspicion that something like export LC_ALL="$LC_IDENTIFICATION%.*.UTF-8" is somewhere and not "set" right or is not getting the information needed from ${LC_IDENTIFICATION% so you are getting that error and since it repeats it may be in there twice or in two different files in the profiles.d ... again .. guessing :(
    – John Orion
    Mar 29 at 23:43











  • All I found was in /etc/profile.d/vte-2.29.sh in wich there is: # This is important to make sure string manipulation is handled # byte-by-byte. LC_ALL=C str="$1" while [ -n "$str" ]; do safe="$str%%[!a-zA-Z0-9/:_.-!'()~]*" printf "%s" "$safe" str="$str#"$safe"" if [ -n "$str" ]; then printf "%%%02X" "'$str" str="$str#?" fi done )
    – Sojan Janso
    Mar 30 at 2:36















up vote
0
down vote

favorite












after updating ubuntu gnome, I get a black screen with an error window every time I log in. I can just click ok and continue, but after a month or so of ignoring it I figured I should fix it. Anybody able to help me?



The error window looks like this:



Error found when loading /etc/profile:

Locale: Cannot set LC_ALL to default locale: No such file or directory
Locale: Cannot set LC_ALL to default locale: No such file or directory

As a result the session will not be configured correctly. You should fix the problem as soon as feasible.


The file contains these lines:




# /etc/profile: system-wide .profile file for the Bourne shell (sh(1))
# and Bourne compatible shells (bash(1), ksh(1), ash(1), ...).

if [ "$PS1-" ]; then
 if [ "$BASH-" ] && [ "$BASH" != "/bin/sh" ]; then
 # The file bash.bashrc already sets the default PS1.
 # PS1='h:w$ '
 if [ -f /etc/bash.bashrc ]; then
 . /etc/bash.bashrc
 fi
 else
 if [ "`id -u`" -eq 0 ]; then
 PS1='# '
 else
 PS1='$ '
 fi
 fi
fi

if [ -d /etc/profile.d ]; then
 for i in /etc/profile.d/*.sh; do
 if [ -r $i ]; then
 . $i
 fi
 done
 unset i
fi






gnome login 17.10







share|improve this question























  • have you looked at etc/profile to see what the line is pointing to? can you add to your post the contents of etc/profile .. just checked my profile and I don't see LC_ALL so it may be something you have installed that is setting that "path" I looked up LC_ALL and found it has something to do with It forces applications to use the default language for output and probably not really necessary.. you probably can get away with commenting out that line in the file by adding a # before it .. but again .. it would be best if we could see the file and see if we can see an error in the line.
    – John Orion
    Mar 29 at 18:10










  • Ok thanks, there you go, I added it!
    – Sojan Janso
    Mar 29 at 22:11











  • hmm ok that's odd ... the LC_ALL isn't even listed. I expected to see something like LC_ALL=en_US.UTF-8 or something like that .....ok it also looks in /etc/profile.d .. check /etc/profile.d folder and see if there are any files in there and if any of those files list the LC_ALL line. if you still don't see it check your ~/.profile and see if LC_ALL is listed in there. I found something close in a file called cedilla-portuguese.sh that says export LC_CTYPE="$LC_IDENTIFICATION%.*.UTF-8" but nothing that says LC_ALL= sorry, im just guessing, im not real familiar with this error
    – John Orion
    Mar 29 at 23:35











  • I have a suspicion that something like export LC_ALL="$LC_IDENTIFICATION%.*.UTF-8" is somewhere and not "set" right or is not getting the information needed from ${LC_IDENTIFICATION% so you are getting that error and since it repeats it may be in there twice or in two different files in the profiles.d ... again .. guessing :(
    – John Orion
    Mar 29 at 23:43











  • All I found was in /etc/profile.d/vte-2.29.sh in wich there is: # This is important to make sure string manipulation is handled # byte-by-byte. LC_ALL=C str="$1" while [ -n "$str" ]; do safe="$str%%[!a-zA-Z0-9/:_.-!'()~]*" printf "%s" "$safe" str="$str#"$safe"" if [ -n "$str" ]; then printf "%%%02X" "'$str" str="$str#?" fi done )
    – Sojan Janso
    Mar 30 at 2:36













up vote
0
down vote

favorite









up vote
0
down vote

favorite











after updating ubuntu gnome, I get a black screen with an error window every time I log in. I can just click ok and continue, but after a month or so of ignoring it I figured I should fix it. Anybody able to help me?



The error window looks like this:



Error found when loading /etc/profile:

Locale: Cannot set LC_ALL to default locale: No such file or directory
Locale: Cannot set LC_ALL to default locale: No such file or directory

As a result the session will not be configured correctly. You should fix the problem as soon as feasible.


The file contains these lines:




# /etc/profile: system-wide .profile file for the Bourne shell (sh(1))
# and Bourne compatible shells (bash(1), ksh(1), ash(1), ...).

if [ "$PS1-" ]; then
 if [ "$BASH-" ] && [ "$BASH" != "/bin/sh" ]; then
 # The file bash.bashrc already sets the default PS1.
 # PS1='h:w$ '
 if [ -f /etc/bash.bashrc ]; then
 . /etc/bash.bashrc
 fi
 else
 if [ "`id -u`" -eq 0 ]; then
 PS1='# '
 else
 PS1='$ '
 fi
 fi
fi

if [ -d /etc/profile.d ]; then
 for i in /etc/profile.d/*.sh; do
 if [ -r $i ]; then
 . $i
 fi
 done
 unset i
fi






gnome login 17.10







share|improve this question















after updating ubuntu gnome, I get a black screen with an error window every time I log in. I can just click ok and continue, but after a month or so of ignoring it I figured I should fix it. Anybody able to help me?



The error window looks like this:



Error found when loading /etc/profile:

Locale: Cannot set LC_ALL to default locale: No such file or directory
Locale: Cannot set LC_ALL to default locale: No such file or directory

As a result the session will not be configured correctly. You should fix the problem as soon as feasible.


The file contains these lines:




# /etc/profile: system-wide .profile file for the Bourne shell (sh(1))
# and Bourne compatible shells (bash(1), ksh(1), ash(1), ...).

if [ "$PS1-" ]; then
 if [ "$BASH-" ] && [ "$BASH" != "/bin/sh" ]; then
 # The file bash.bashrc already sets the default PS1.
 # PS1='h:w$ '
 if [ -f /etc/bash.bashrc ]; then
 . /etc/bash.bashrc
 fi
 else
 if [ "`id -u`" -eq 0 ]; then
 PS1='# '
 else
 PS1='$ '
 fi
 fi
fi

if [ -d /etc/profile.d ]; then
 for i in /etc/profile.d/*.sh; do
 if [ -r $i ]; then
 . $i
 fi
 done
 unset i
fi






gnome login 17.10




gnome login 17.10






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Mar 29 at 22:05

























asked Mar 29 at 17:51









Sojan Janso

365




365











  • have you looked at etc/profile to see what the line is pointing to? can you add to your post the contents of etc/profile .. just checked my profile and I don't see LC_ALL so it may be something you have installed that is setting that "path" I looked up LC_ALL and found it has something to do with It forces applications to use the default language for output and probably not really necessary.. you probably can get away with commenting out that line in the file by adding a # before it .. but again .. it would be best if we could see the file and see if we can see an error in the line.
    – John Orion
    Mar 29 at 18:10










  • Ok thanks, there you go, I added it!
    – Sojan Janso
    Mar 29 at 22:11











  • hmm ok that's odd ... the LC_ALL isn't even listed. I expected to see something like LC_ALL=en_US.UTF-8 or something like that .....ok it also looks in /etc/profile.d .. check /etc/profile.d folder and see if there are any files in there and if any of those files list the LC_ALL line. if you still don't see it check your ~/.profile and see if LC_ALL is listed in there. I found something close in a file called cedilla-portuguese.sh that says export LC_CTYPE="$LC_IDENTIFICATION%.*.UTF-8" but nothing that says LC_ALL= sorry, im just guessing, im not real familiar with this error
    – John Orion
    Mar 29 at 23:35











  • I have a suspicion that something like export LC_ALL="$LC_IDENTIFICATION%.*.UTF-8" is somewhere and not "set" right or is not getting the information needed from ${LC_IDENTIFICATION% so you are getting that error and since it repeats it may be in there twice or in two different files in the profiles.d ... again .. guessing :(
    – John Orion
    Mar 29 at 23:43











  • All I found was in /etc/profile.d/vte-2.29.sh in wich there is: # This is important to make sure string manipulation is handled # byte-by-byte. LC_ALL=C str="$1" while [ -n "$str" ]; do safe="$str%%[!a-zA-Z0-9/:_.-!'()~]*" printf "%s" "$safe" str="$str#"$safe"" if [ -n "$str" ]; then printf "%%%02X" "'$str" str="$str#?" fi done )
    – Sojan Janso
    Mar 30 at 2:36

















  • have you looked at etc/profile to see what the line is pointing to? can you add to your post the contents of etc/profile .. just checked my profile and I don't see LC_ALL so it may be something you have installed that is setting that "path" I looked up LC_ALL and found it has something to do with It forces applications to use the default language for output and probably not really necessary.. you probably can get away with commenting out that line in the file by adding a # before it .. but again .. it would be best if we could see the file and see if we can see an error in the line.
    – John Orion
    Mar 29 at 18:10










  • Ok thanks, there you go, I added it!
    – Sojan Janso
    Mar 29 at 22:11











  • hmm ok that's odd ... the LC_ALL isn't even listed. I expected to see something like LC_ALL=en_US.UTF-8 or something like that .....ok it also looks in /etc/profile.d .. check /etc/profile.d folder and see if there are any files in there and if any of those files list the LC_ALL line. if you still don't see it check your ~/.profile and see if LC_ALL is listed in there. I found something close in a file called cedilla-portuguese.sh that says export LC_CTYPE="$LC_IDENTIFICATION%.*.UTF-8" but nothing that says LC_ALL= sorry, im just guessing, im not real familiar with this error
    – John Orion
    Mar 29 at 23:35











  • I have a suspicion that something like export LC_ALL="$LC_IDENTIFICATION%.*.UTF-8" is somewhere and not "set" right or is not getting the information needed from ${LC_IDENTIFICATION% so you are getting that error and since it repeats it may be in there twice or in two different files in the profiles.d ... again .. guessing :(
    – John Orion
    Mar 29 at 23:43











  • All I found was in /etc/profile.d/vte-2.29.sh in wich there is: # This is important to make sure string manipulation is handled # byte-by-byte. LC_ALL=C str="$1" while [ -n "$str" ]; do safe="$str%%[!a-zA-Z0-9/:_.-!'()~]*" printf "%s" "$safe" str="$str#"$safe"" if [ -n "$str" ]; then printf "%%%02X" "'$str" str="$str#?" fi done )
    – Sojan Janso
    Mar 30 at 2:36
















have you looked at etc/profile to see what the line is pointing to? can you add to your post the contents of etc/profile .. just checked my profile and I don't see LC_ALL so it may be something you have installed that is setting that "path" I looked up LC_ALL and found it has something to do with It forces applications to use the default language for output and probably not really necessary.. you probably can get away with commenting out that line in the file by adding a # before it .. but again .. it would be best if we could see the file and see if we can see an error in the line.
– John Orion
Mar 29 at 18:10




have you looked at etc/profile to see what the line is pointing to? can you add to your post the contents of etc/profile .. just checked my profile and I don't see LC_ALL so it may be something you have installed that is setting that "path" I looked up LC_ALL and found it has something to do with It forces applications to use the default language for output and probably not really necessary.. you probably can get away with commenting out that line in the file by adding a # before it .. but again .. it would be best if we could see the file and see if we can see an error in the line.
– John Orion
Mar 29 at 18:10












Ok thanks, there you go, I added it!
– Sojan Janso
Mar 29 at 22:11





Ok thanks, there you go, I added it!
– Sojan Janso
Mar 29 at 22:11













hmm ok that's odd ... the LC_ALL isn't even listed. I expected to see something like LC_ALL=en_US.UTF-8 or something like that .....ok it also looks in /etc/profile.d .. check /etc/profile.d folder and see if there are any files in there and if any of those files list the LC_ALL line. if you still don't see it check your ~/.profile and see if LC_ALL is listed in there. I found something close in a file called cedilla-portuguese.sh that says export LC_CTYPE="$LC_IDENTIFICATION%.*.UTF-8" but nothing that says LC_ALL= sorry, im just guessing, im not real familiar with this error
– John Orion
Mar 29 at 23:35





hmm ok that's odd ... the LC_ALL isn't even listed. I expected to see something like LC_ALL=en_US.UTF-8 or something like that .....ok it also looks in /etc/profile.d .. check /etc/profile.d folder and see if there are any files in there and if any of those files list the LC_ALL line. if you still don't see it check your ~/.profile and see if LC_ALL is listed in there. I found something close in a file called cedilla-portuguese.sh that says export LC_CTYPE="$LC_IDENTIFICATION%.*.UTF-8" but nothing that says LC_ALL= sorry, im just guessing, im not real familiar with this error
– John Orion
Mar 29 at 23:35













I have a suspicion that something like export LC_ALL="$LC_IDENTIFICATION%.*.UTF-8" is somewhere and not "set" right or is not getting the information needed from ${LC_IDENTIFICATION% so you are getting that error and since it repeats it may be in there twice or in two different files in the profiles.d ... again .. guessing :(
– John Orion
Mar 29 at 23:43





I have a suspicion that something like export LC_ALL="$LC_IDENTIFICATION%.*.UTF-8" is somewhere and not "set" right or is not getting the information needed from ${LC_IDENTIFICATION% so you are getting that error and since it repeats it may be in there twice or in two different files in the profiles.d ... again .. guessing :(
– John Orion
Mar 29 at 23:43













All I found was in /etc/profile.d/vte-2.29.sh in wich there is: # This is important to make sure string manipulation is handled # byte-by-byte. LC_ALL=C str="$1" while [ -n "$str" ]; do safe="$str%%[!a-zA-Z0-9/:_.-!'()~]*" printf "%s" "$safe" str="$str#"$safe"" if [ -n "$str" ]; then printf "%%%02X" "'$str" str="$str#?" fi done )
– Sojan Janso
Mar 30 at 2:36





All I found was in /etc/profile.d/vte-2.29.sh in wich there is: # This is important to make sure string manipulation is handled # byte-by-byte. LC_ALL=C str="$1" while [ -n "$str" ]; do safe="$str%%[!a-zA-Z0-9/:_.-!'()~]*" printf "%s" "$safe" str="$str#"$safe"" if [ -n "$str" ]; then printf "%%%02X" "'$str" str="$str#?" fi done )
– Sojan Janso
Mar 30 at 2:36
















active

oldest

votes











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',
convertImagesToLinks: true,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
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%2f1020342%2fubuntu-gnome-error-after-updating-to-ubuntu-17-10%23new-answer', 'question_page');

);

Post as a guest






















active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes















 

draft saved


draft discarded















































 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1020342%2fubuntu-gnome-error-after-updating-to-ubuntu-17-10%23new-answer', 'question_page');

);

Post as a guest
































































-

Popular posts from this blog

pylint3 and pip3 broken

Image
Clash Royale CLAN TAG #URR8PPP up vote 0 down vote favorite I have tried sudo apt remove --purge on various packages. I get the same when I reinstall. I have also tried reinstall using aptitude. This does not work. My current workaround is to run pylint3 as root, which works, but is bad practice. pip3 $ pip3 Traceback (most recent call last): File "/usr/lib/python3/dist-packages/pip/_vendor/__init__.py", line 33, in vendored __import__(vendored_name, globals(), locals(), level=0) ImportError: No module named 'pip._vendor.pkg_resources' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/bin/pip3", line 9, in <module> from pip import main File "/usr/lib/python3/dist-packages/pip/__init__.py", line 13, in <module> from pip.exceptions import InstallationError, CommandError, PipError File "/usr/lib/python3/dist-packages/pip/exceptions.py", line 6, ...
Read more

Missing snmpget and snmpwalk

Image
Clash Royale CLAN TAG #URR8PPP up vote 0 down vote favorite I have installed Zabbix appliance, directly preinstalled and found that there is missing snmpwalk and snmpget commands. I tried to install it with: apt-get install net-snmp-utils but I have error message: Unable to locate package. I have also check what from SNMP is preinstalled and there is: libsnmp-base libsnmp30:amd64 snmp-mibs-downloader snmpd snmptrapd snmptrapfmt How can I install snmpget and snmpwalk ? snmp zabbix share | improve this question edited Jan 29 at 10:10 Yaron 8,552 7 18 38 asked Jan 29 at 9:51 Alfista 1 apt install snmp perhaps ? If named differently - apt cache snmp – fugitive Jan 29 at 10:00 add a comment  |  up vote 0 down vote favorite I have installed Zabbix appliance, directly preinstalled and found that there is missing snmpwalk and snmpget commands. I tried...
Read more

How to enroll fingerprints to Ubuntu 17.10 with VFS491

Image
Clash Royale CLAN TAG #URR8PPP up vote 1 down vote favorite I decided to switch from Windows to Ubuntu 17.10, I meet it like 8 years ago and I didn't decided to switch until now (haha). Well, my actual device is an HP Probook 4540s with a Validity fingerprint sensor (VFS491). The fingerprint sensor worked fine on Windows but I can't get it to work in Ubuntu. The device is recognized as 138a:003d but is not detected as a fingerprint scanner by some apps like Fingerprint GUI. I want to use the fingerprint scanner to log in into my user account in Ubuntu but it doesn't supports fingerprints without special software and the drivers of the fingerprint scanner are available for Windows but not for any Linux distribution. I found something on GitHub (https://github.com/eekpie/libfprint) about the integration of the VFS491 in libfprint and I think it can help but I don't know what to do with it, so that's why I need the help of the community to do it since I am...
Read more