Search the Community
Showing results for tags 'solved!'.
-
Hi, I have been a user for quite a while but my server was down for a while, so when I got it back online and started updates, it doesn't find Windowmaker anymore. I am on 1.4, but just played with the next on the live install and see the same. I see it upstream in the Gentoo packages. Is there a reason for it being omitted or am I doing something not quite right? I prefer not to find a different distro as this has been a great ride after coming here from Gentoo to easily keep systemd out of my machine. That being said, maybe there is a way to slurp it in without breaking stuff on my side that I have not explored yet? Since I thought that maybe my older system without updates may have caused some of the issue, since I can't even remember how long I have been over to Funtoo.... I also bet I dragged in some old Gentoo stuff/behaviors/configurations.
-
Kernel configuration (that i'd always used) in a new installation of Funtoo 1.4 hang at boot: the system freeze after message "random: fast init done". To solve it i must use initramfs The same kernel configuration work well (without initramfs) in any other installation of Funtoo/Gentoo: for example, in my old installation of Funtoo, updated to 1.4 release, the kernel normally boot without initramfs. I search on web but i don't find what's the problem.
-
message is "die 'Aborting due to serious QA concern with RUNPATH/RPATH" Has anyone run into this and solved it?
-
Core system working well, including X. Problem is getting KDE to start; it doesn't. Tried sddm first - followed suggestions, adding it to /etc/conf.d/xdm DISPLAYMANAGER="sddm". That caused the system to hang when rc started xdm - got a blank screen with the mouse cursor, but nothing worked beyond that. Rebooted with the sysresqcd to log onto the system and delete xdm (with sddm as displaymanager) from the rc-update default setting. I've heard good things about gdm, but found no mention of someone using it to start KDE, and no instructions for how to aim the displaymanager at KDE, much less any other desktop environment. BTW, I followed what directions I could find as far as setting up sddm, including other users experiences with the frozen login screen. I'm stumped! (Again!)
-
Hi, I've installed Textlive2019 following these instrunctions: https://www.tug.org/texlive/quickinstall.html I add to my .bashrc file these lines: PATH=$PATH:/usr/local/texlive/2019/bin/x86_64-linux export PATH MANPATH=$MANPATH:/usr/local/texlive/2019/texmf/doc/man export MANPATH INFOPATH=$INFOPATH:/usr/local/texlive/2019/texmf/doc/info export INFOPATH If I run kile from terminal it works fine, If I run it from applications menu it couldn't load texlive. I also add the path in /etc/profile. How can I set path in a correct manner?
-
Disclaimer: I used Gentoo back when it was still v.1.0 and drobbins still administered it. Used it for some years. (Sort of the perpetual newb!) Came over to Funtoo "just 'cuz" and built a nice, usable install with kde. Enjoyed it for a couple of years, then noticed that an upgrade was available. I upgraded, but the internet connection was borked following the upgrade; I figured the easiest (well, maybe not the easiest!) job would be to do a complete reinstall. So I did. Everything has gone well EXCEPT for the re-install of KDE. The USE flags are killing me! I cannot find an acceptable combo that satisfies Portage/emerge to let me install the set. I know that KDE developers work to make ALL their apps play nice with one another, so why are there so many conflicts that, supposedly, require specific USE flags to install properly? It's not like the use of USE flags is universal among Linux distros! So far as I know, Gentoo and Funtoo are unique among distros in using them, yet KDE doesn't build their apps predicated upon the incorporation of USE flags to complicate the issue! Are the specific USE flag requirements for a package set by Gentoo/Funtoo developers? Any workarounds?
-
Where is gfxmode set when you do ego boot update It keeps going to 640x480. Also when I build grub myself, the grub-mkconfig outputs a vastly different file than ego does. How can I fix this?
