palica

all the setup commands are run as root. there is no "own profile" there is only "system profile". changing profile requires being root or using sudo.

https://developer.github.com/v3/guides/using-ssh-agent-forwarding/
especially check the server config not overriding your user config (AllowAgentForwarding, ForwardAgent)

1.3 is not ready for any testing if you are not a developer. so stick with 1.2

this is known and reported already in the right place.
https://bugs.funtoo.org/browse/FL-5205
 

ttyS0 is serial console. that error means you either don't have serial console or it is not connected to ttyS0
 
how to get rid of this message - correct the cause of the error message.
 
what server are you using? what do you mean with serial console connection?

take a look at /etc/conf.d/hostname
 
 

try
sysctl net.ipv6.conf.eth0.autoconf=0 sysctl net.ipv6.conf.eth0.accept_ra=0  

emerge ecryptfs-utils with suid useflag.

Please follow https://www.funtoo.org/LXD
 
lxc is a dependency for lxd
looks like problem with uid/gid maps
show me your /etc/subuid and /ect/subgid please
did you restart lxd after changing the values in subuid/subgid?
 

seems to me that the two subarch are not compatible. so piledriver is not supported on ryzen. just guessing here. You will need to reinstall at least the @system part of the installation.
I would backup /home and /etc and /var/lib/portage/world and use a stage3 that supports ryzen or just a plain generic_64bit and run a emerge @world after you copy the /etc /var/lib/portage/world back.
 

you will have to delete /etc/portage/repos.conf symlink and create a normal directory and populate it as shown below ...
/etc/portage # ❯❯❯ ls -alF repos.conf total 108 drwxr-xr-x 1 root root 696 Feb 7 21:17 ./ drwxr-xr-x 1 root root 504 Jan 30 03:12 ../ -rw-r--r-- 1 root root 90 Feb 13 19:39 ego-core-hw-kit -rw-r--r-- 1 root root 116 Feb 13 19:39 ego-core-kit -rw-r--r-- 1 root root 90 Feb 13 19:39 ego-desktop-kit -rw-r--r-- 1 root root 82 Feb 13 19:39 ego-dev-kit -rw-r--r-- 1 root root 90 Feb 13 19:39 ego-editors-kit -rw-r--r-- 1 root root 86 Feb 13 19:39 ego-games-kit -rw-r--r-- 1 root root 86 Feb 13 19:39 ego-gnome-kit -rw-r--r-- 1 root root 90 Feb 13 19:39 ego-haskell-kit -rw-r--r-- 1 root root 84 Feb 13 19:39 ego-java-kit -rw-r--r-- 1 root root 82 Feb 13 19:39 ego-kde-kit -rw-r--r-- 1 root root 84 Feb 13 19:39 ego-lang-kit -rw-r--r-- 1 root root 98 Feb 13 19:39 ego-lisp-scheme-kit -rw-r--r-- 1 root root 86 Feb 13 19:39 ego-media-kit -rw-r--r-- 1 root root 90 Feb 13 19:39 ego-ml-lang-kit -rw-r--r-- 1 root root 82 Feb 13 19:39 ego-net-kit -rw-r--r-- 1 root root 81 Feb 13 19:39 ego-nokit -rw-r--r-- 1 root root 84 Feb 13 19:39 ego-perl-kit -rw-r--r-- 1 root root 82 Feb 13 19:39 ego-php-kit -rw-r--r-- 1 root root 88 Feb 13 19:39 ego-python-kit -rw-r--r-- 1 root root 84 Feb 13 19:39 ego-ruby-kit -rw-r--r-- 1 root root 90 Feb 13 19:39 ego-science-kit -rw-r--r-- 1 root root 92 Feb 13 19:39 ego-security-kit -rw-r--r-- 1 root root 84 Feb 13 19:39 ego-text-kit -rw-r--r-- 1 root root 84 Feb 13 19:39 ego-xfce-kit -rw-r--r-- 1 root root 84 Feb 13 19:39 ego-xorg-kit -rw-r--r-- 1 root root 200 Feb 7 21:17 layman.conf copy or link the files from /var/git/meta-repo/repos.conf to /etc/portage/repos.conf as shown above
here is a oneliner to link all files from meta-repo to portage
cd /var/git/meta-repo/repos.conf; for i in *;do ln -s $i /etc/portage/repos.conf/ego-$i;done create your overlay file such as layman.conf or local.conf or whatever and put your overlay settings there.
 

Supported boot parameters
rollback=<on|yes|1> Do a rollback of specified snapshot. zfs_debug=<on|yes|1> Debug the initrd script zfs_force=<on|yes|1> Force importing the pool. Should not be necessary. zfs=<off|no|0> Don't try to import ANY pool, mount ANY filesystem or even load the module. rpool=<pool> Use this pool for root pool. bootfs=<pool>/<dataset> Use this dataset for root filesystem. root=<pool>/<dataset> Use this dataset for root filesystem. root=ZFS=<pool>/<dataset> Use this dataset for root filesystem. root=zfs:<pool>/<dataset> Use this dataset for root filesystem. root=zfs:AUTO Try to detect both pool and rootfs In all these cases, <dataset> could also be <dataset>@<snapshot>.
Booting from snapshot:
Enter the snapshot for the root= parameter like in this example:
linux /ROOT/funtoo-1@/boot/vmlinuz root=ZFS=rpool/ROOT/funtoo-1@some_snapshot ro boot=zfs $bootfs quiet This will clone the snapshot rpool/ROOT/funtoo-1@some_snapshot into the filesystem rpool/ROOT/funtoo-1_some_snapshot and use that as root filesystem. The original filesystem and snapshot is left alone in this case.
 

remove DEFAULT and main-repo from the overlay.conf

that is the new theme for icons
if you wish to switch themes - you will find it in Preferences :)

make sure portage owns the distfiles directory and change it accordingly also for git3-src
drwxr-xr-x 1 portage portage 274506 28. led 21.50 /var/cache/portage/distfiles/

[ebuild  N     ] sci-mathematics/rstudio-1.1.383::science-kit  USE="-dedicated -server" 207,262 KiB
compiled for me without problems. If you are still experiencing problems let us know. When possible supplying also ebuild.log.

actually the easiest way is to switch to media-kit/1.2-prime there is darktable there in 2.4.0 version.
 
ego config set kits media-kit 1.2-prime ego sync emerge -av darktable  

not ideal fix, but will solve the situation for now.

glsa-check doesn't provide an up-to-date information for Funtoo. Funtoo also backports lots of security fixes for the forked packages, so the information that you get with --list affected could be inaccurate or wrong.
There is a open bug for glsa-check tool for funtoo
in BFO https://bugs.funtoo.org/browse/FL-3832?jql=text ~ "glsa"
so you can subscribe to the bug and get update once such a tool is ready for funtoo. Until then you will have to check gentoo's GLSA list and check the README.rst in the kit of the package for example here:
https://github.com/funtoo/core-kit/blob/1.0-prime/README.rst
Funtoo also tries to audit forked ebuilds every 30 days. You can see all stale packages on this webpage:
http://ports.funtoo.org/stale/
If you want to help and use any of the packages that are listed as "stale" you can check if they are affected by any know vulnerabilities and report those on https://bugs.funtoo.org where they will be squashed as fast as possible.
Thank you in advance.

No problem. I have noticed some other things in your setup that you should fix.
experimental is not supported anymore. I would recommend to switch to current. Manual edit is probably necessary.
there is already 2.3.18 released and it makes sense to have portage the latest stable version as it is the core of funtoo/gentoo.
you are using gcc-6.3.0 from your local overlay and I would recommend to switch to gcc-6.4.0 that can be found in core-kit and use that as anything else could be seen as unsupported.
From all these mix-ins you need only no-emul-linux-x86 and gnome all the other ones come inherited from desktop or workstation ...
and other packages that come from ::gentoo repo give me information that you need to run
emerge -avuDN --newrepo @world to migrate all packages from the old ports-2012 to the new meta-repo/kits setup.
Let me know if you need something else.

changing /etc/boot.conf to this should work
boot { generate grub default "Funtoo Linux genkernel" timeout 3 } "Funtoo Linux" { kernel bzImage[-v] } "Funtoo Linux genkernel" { kernel kernel-debian-sources-x86_64[-v] initrd initramfs-debian-sources-x86_64[-v] params += real_root=auto rootfstype=auto } "memtest86+" { type linux16 kernel /memtest86.bin }  

yes, please use 3.20-prime.

@Sandro, I would like to redirect you here -
The topic title should be edited from "VLC doesn't run very well" to something more concrete like: Random flashes or black frames in VLC while playing movies in fullscreen
Try to add more information, that you think could be relevant to the problem. Like driver used, kernel version, is it only for certain videos or for all, fullscreen/windowed...
Also try to update to media-kit:1.1-prime by issuing these commands
 

I would start over from a fresh install. Just backup your data and wipe the partition.
Your processor is Silvermont according to this https://en.wikipedia.org/wiki/List_of_Intel_Pentium_microprocessors#"Bay_Trail-M"_(22_nm) Grab this stage3 from build.funtoo.org - funtoo-current/x86-64bit/intel64-silvermont/2017-12-09/stage3-intel64-silvermont-funtoo-current-2017-12-09.tar.xz these are the settings already active in the stage3 so no need to set them by hand  
add only these settings to the make.conf:
 
run these commands:
 

 
update your system:
 

 
emerge lxde-meta:
 

 
continue the installation according to:
https://www.funtoo.org/Install#Configuring_your_system
report back here how it went
 

Mixing NetworkManager and manual wpa_supplicant will not work. Pick only one approach.
- NetworkManager: set it up in the applet or using CLI
- wpa_supplicant & dhcpcd: disable NetworkManager and enable wpa_supplicant and dhcpcd services and set your credential in /etc/wpa_supplicant/wpa_supplicant.conf using the wpa_pass utility