palica

this has to be fixed in the translations, it has been corrected in English original. Since it is a wiki you can edit it yourself. Please do so if you have time to make the experience for all users better.

eix-sync works for me on my PCs (it pulls also meta-repo changes automaticaly) so no need to use any custom scripts.

it is actually meld that wants glib to be compiled with dbus flag. Does this still bother you? I run it now on my system and meld wants >=glib-2.48.2 with dbus.

what is the exact error message and what is the output of lspci

steps to reproduce, please (stage, what livecd you are using, ...) error shown, please what is in dmesg, please

please use bugs.funtoo.org for ebuild requests and version bumps in the future. Oleg is already working on the bump.

good

I don't understand. Yes, you will have to upgrade some packages. Report back once done and you tested vlc :)

it should, if you are using legacy bios mbr. ok let me know after reboot if system works.

yes.

Funtoo tries to test stuff internally by the devs and not "leave" the testing to normal users that sometimes don't have a clue. So that is why funtoo is using gcc-5.4.0 to compile stages and also as default compiler. There are already stages that are getting build with gcc-6.3.0 and there soon will be a new toolchain upgrade/release for all. You are welcome to join the #funtoo-dev on freenode (IRC) if you have time and resources and would like to help test new stuff.

does it work? now add packages one by one.

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

put only those 4 lines in /etc/portage/make.conf please

@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

it was down @Otakku

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

maybe we need something like a status page?

are you using swap? paste free -m

znavko, please follow the Install guide on www.funtoo.org - https://www.funtoo.org/Install if you cannot/or don't want to - paste every single file that you have in /etc/portage so /etc/portage/make.conf /etc/portage/package.* ... /var/lib/portage/world emerge --info But frankly, it will take so much time to resolve it, that a reinstall is probably a better and faster solution. Also don't use -O3 period. Quote from gentoo wiki: Once you get familiar with funtoo and portage you can then switch, but starting with funtoo and doing all sorts of crazy things that you don't understand is just a waste of time for everybody.

We’d love to help you. To improve your chances of getting an answer, here are some tips: Search, and research ...and keep track of what you find. Even if you don't find a useful answer elsewhere on the site, including links to related questions that haven't helped can help others in understanding how your question is different from the rest. Write a title that summarizes the specific problem The title is the first thing potential answerers will see, and if your title isn't interesting, they won't read the rest. So make it count: Pretend you're talking to a busy colleague and have to sum up your entire question in one sentence: what details can you include that will help someone identify and solve your problem? Include any error messages, key APIs, or unusual circumstances that make your question different from similar questions already on the site. Spelling, grammar and punctuation are important! Remember, this is the first part of your question others will see - you want to make a good impression. If you're not comfortable writing in English, ask a friend to proof-read it for you. If you're having trouble summarizing the problem, write the title last - sometimes writing the rest of the question first can make it easier to describe the problem. Examples: Bad: Is there command to do what it needs? Good: How can I apply changes proposed by emerge? Bad: Problem update system Good: Why does the compile of dev-libs/boost-1.63.0 fail with x86_64-pc-linux-gnu-g++: internal compiler error: Killed (program cc1plus)? Introduce the problem before you post any code In the body of your question, start by expanding on the summary you put in the title. Explain how you encountered the problem you're trying to solve, and any difficulties that have prevented you from solving it yourself. The first paragraph in your question is the second thing most readers will see, so make it as engaging and informative as possible. Help others reproduce the problem Not all questions benefit from including code. Here are some guidelines: Include just enough code to allow others to reproduce the problem. For portage errors include all the relevant info and output. Include all relevant tags Try to include a tag for the language, library, and specific API your question relates to. If you start typing in the tags field, the system will suggest tags that match what you've typed - be sure and read the descriptions given for them to make sure they're relevant to the question you're asking! See also: What are tags, and how should I use them? Proof-read before posting! Now that you're ready to ask your question, take a deep breath and read through it from start to finish. Pretend you're seeing it for the first time: does it make sense? Try reproducing the problem yourself, in a fresh environment and make sure you can do so using only the information included in your question. Add any details you missed and read through it again. Now is a good time to make sure that your title still describes the problem! Post the question and respond to feedback After you post, leave the question open in your browser for a bit, and see if anyone comments. If you missed an obvious piece of information, be ready to respond by editing your question to include it. If someone posts an answer, be ready to try it out and provide feedback! Look for help asking for help In spite of all your efforts, you may find your questions poorly-received. Don't despair! Learning to ask a good question is a worthy pursuit, and not one you'll master overnight. Here are some additional resources that you may find useful: Writing the perfect question How do I ask and answer homework questions? How to debug small programs Meta discussions on asking questions How to ask questions the smart way — long but good advice.

@znavko: I think you are over-complicating it here with your setup. So what are you trying to do? Why add all this stuff to your make.conf? Did you follow the installation guide? Why do you think you need -O3? Why do you specify all these CPU_FLAGS ? ...

can this be due to bad connection over modem? I don't think OS is the cause of your problems. Is everything with the cable, modem, connection ok? Can you test the reliability with a different device?

what problem are you seeing again? maybe there is something wrong with your hardware if it stops working, maybe there was something wrong with xfce and maybe there is something wrong with lxde. It is hard to tell if you don't provide any context. Do you have anything in the logs, anything in dmesg ... I would also suggest you try to run software compiled with "supported" CFLAGS as was already suggested. I don't see any problem with the last emerge lxde-meta lxde-common ... What do you mean: Why are you compiling your system with -O3? How are you recompiling it? There are just too many variables involved.

when you make changes to use flags it makes sense to upgrade @world first and then do other stuff. So try emerge -avuDN --with-bdeps=y --newrepo @world and paste any conflicts here