Jump to content
  • 1
nigga-china

Problems after updating Funtoo to 1.3

Question

Well, I did "ego sync" and then "emerge -auDN @world" and the packages just were been updated after long hours. So I reboot my notebook and then... Some programs were not recognized (e.g., I typed "ls" and it said something like "ls is not a command"). So I checked the PATH variable and there was too few paths in it. So I tried to put others paths like "/bin, /usr/local/bin" and others and finally I could launch dwm and open my browser ... And now I'm here.

Does anybody have an idea of how to fix this issue? Well, I know that there is some files that sets the PATH var, but if a program changed it I think the program might could change another things too...

Share this post


Link to post
Share on other sites

7 answers to this question

Recommended Posts

  • 0

Did either of you find a way to recover from this issue.  

I can boot to sddm and when I attempt to login the sessions freezes.

Switch over to tty2 I can log in but PATH is not set properly.  Also ROOTPATH returns blank.

env-update does not seem to change anything, seems as the config file (is not being read)

Questions: 

What should the default user PATH variables: /bin:/usr/bin:/usr/local/bin .........

Default ROOTPATH: ?

Do you have any tips on troubleshooting this type of issue?

 

Thank You

Keith

 

Share this post


Link to post
Share on other sites
  • 0

root filesytem

total 112
drwxr-xr-x  20 root root  4096 May 30 11:16 .
drwxr-xr-x  20 root root  4096 May 30 11:16 ..
drwxr-xr-x   2 root root  4096 May 30 15:15 bin
drwxr-xr-x   5 root root  4096 Dec 31  1969 boot
drwxr-xr-x  19 root root  3500 Jun  4 22:08 dev
drwxr-xr-x 102 root root  4096 Jun  4 22:08 etc
drwxr-xr-x   3 root root  4096 May 30 08:56 home
lrwxrwxrwx   1 root root     5 May 30 11:16 lib -> lib64
drwxr-xr-x  16 root root 12288 May 30 15:13 lib64
drwx------   2 root root 16384 Dec 21  2016 lost+found
drwxr-xr-x   6 root root  4096 May 30 08:56 mnt
drwxr-xr-x   7 root root  4096 May 30 08:56 opt
dr-xr-xr-x 130 root root     0 Jun  4 22:08 proc
drwx------  20 root root  4096 Jun  4 10:28 root
drwxr-xr-x  23 root root   660 Jun  4 22:08 run
drwxr-xr-x   2 root root 12288 May 30 15:13 sbin
drwxr-xr-x   2 root root  4096 May 30 08:56 srv
dr-xr-xr-x  13 root root     0 Jun  4 22:08 sys
drwxrwxrwt   5 root root 20480 Jun  4 22:08 tmp
-rwxr-xr-x   1 root root   168 Mar 25  2018 uns.sh
drwxr-xr-x  13 root root  4096 May 30 08:56 usr
drwxr-xr-x  15 root root  4096 May 30 17:03 var


Home Directory

total 12
drwxr-xr-x  3 root     root     4096 May 30 08:56 .
drwxr-xr-x 20 root     root     4096 May 30 11:16 ..
-rw-r--r--  1 root     root        0 May 30 08:56 .keep_sys-apps_baselayout-0
drwxr-xr-x 54 savasten savasten 4096 Jun  4 22:10 savasten

 

 

 

Share this post


Link to post
Share on other sites
  • 0

Yeah I did that. I may have hijacked this thread incorrectly.  This error occurred after upgrading to 1.3 maintenance release 1.

Share this post


Link to post
Share on other sites
  • 0

Thanks to someone on the IRC I found the fix. It was suggested that I try changing my default shell back from zsh to bash and that fixed the issue.   Now I just need to fix zsh. Thank you

Command to change the default change the user default shell:  chsh

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...