Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 08/13/2019 in all areas

  1. 8 points
    drobbins

    1.4 is (almost!) ready to go!

    Hey everyone, 1.4 is almost ready to be released. Thanks so much to everyone who has contributed pull requests for 1.4 and tested 1.4. There's still a bunch of work to do, but there always will be and I believe 1.4 will be our most well-tested release so far. After 1.4 is released, we will start development on 2.0, to be released some time in the Fall (Sept/Oct timeframe). I've been thinking about the release schedule a lot and I think that aiming for a .0 release every Fall seems to be a good idea. This means the work is completed well before the winter holidays, and fall in the US is a good season of change and looking forward to new things. What I have left to do for 1.4 is to update the ARM builds to 1.4 and then also to update our documentation, release notes, upgrade steps and related docs. I want to incorporate the new video cards mix-ins into the official installation steps and not leave it to just be a "First Steps" item after install. This way, people can use the install docs to get their desktop environment of choice up and running, too. I hope to get all this completed in the next few days.
  2. 6 points
    Greetings during unusual times -- I wanted to let everyone know that the following ebuilds are currently being auto-updated using our new, amazing autogen framework. That means we will always have current versions: www-client/firefox-bin www-client/google-chrome www-client/google-chrome-beta www-client/google-chrome-unstable www-client/brave-bin app-admin/pass app-admin/passwordsafe net-misc/anydesk-bin mail-client/thunderbird-bin net-im/discord-bin net-im/zoom-bin net-im/slack-bin More are on the way! For those working remotely, I recommend checking out zoom-bin (Zoom meetings) as well as anydesk-bin (AnyDesk) for fast remote desktop. They work great under Funtoo. Enjoy, and stay safe. -Daniel
  3. 5 points
    drobbins

    Updated Python Eclasses and Autogen

    Hi All, To get ready for future improvements to Funtoo, I am adopting a multi-phased approach to 'fix Python'. First step is to address some issues that exist in the Gentoo python eclasses. I've updated these eclasses to be at least somewhat better than they are in Gentoo. These changes will be hitting the tree in an hour or so. For new ebuilds, you can now use the following rather than enumerating every single version of Python: PYTHON_COMPAT=( python3+ ) Because the minimum version of python3 we support is 3.7, this will ensure that the ebuild will be marked compatible with 3.7 and later versions of Python. Using the '+' symbol is the preferred way to mark ebuilds using PYTHON_COMPAT because it eliminates the time-consuming process used in Gentoo of tagging every single python-using ebuild when a new version of Python comes out. I don't know how they deal with this but it is a lot of wasted energy. Also supported in the new eclasses are the following: PYTHON_COMPAT=( python2+ ) # python2_7, python3_7, and beyond PYTHON_COMPAT=( python3_7+ ) # same as python3+ since we start counting at 3_7 PYTHON_COMPAT=( python3_8+ ) # should be self-explanatory... PYTHON_COMPAT=( python3_9+ ) Note that pypy and pypy3 still need to be manually specified, and it is fine to combine as in the usual way: PYTHON_COMPAT=( python3+ pypy3 ) And another important change I made to the eclass is that any ebuilds still referencing python3_5 or python3_6 will be 'auto-upgraded' to python3_7 compatibility with no user intervention. So this could close a whole slew of bugs. I'm also enabling eclass support for the upcoming Python 3.9. IMPORTANT FOR ALL USERS: These changes will result in all of your Python-based and Python-using packages being rebuilt. This rebuild is for cosmetic purposes only -- it's due to a weirdness in emerge and the eclasses -- and really is optional and doesn't actually result in any changes except changes to the /var/db/pkg database USE flags. Therefore, these rebuilds can be completed at your convenience as they are not important. More adventurous users may look for ways to write a script to update /var/db/pkg so that these rebuilds are unnecessary -- if you attempt this, please back up /var/db/pkg first and read the following technical note! TECHNICAL NOTE: Due to how Gentoo implemented the python eclasses, our deprecation of python3_5 and python3_6 in PYTHON_TARGETS will result in some ebuilds going from 'PYTHON_SINGLE_TARGET' mode to just regular 'PYTHON_TARGET' mode. What you will see is that some ebuilds will be turning off python_single_target_python3_7. This is OK. This is just how the eclasses were written by Gentoo -- PYTHON_SINGLE_TARGET is only enabled when there is more than one active implementation of Python in PYTHON_COMPAT. Otherwise it just falls back to using PYTHON_TARGETS. On another note, our continued use of auto-generation continues to go well with many more packages now in the tree that are auto-generated. Expect this direction to continue. Best, Daniel
  4. 4 points
    drobbins

    1.4 -- Even More New Stuff

    There has been a lot of updates to Funtoo Linux 1.4 since its release -- most of these not officially announced. So it would be a good idea to make an official announcement of many of them: SELinux Updates Firefox and Firefox-bin 69, updated thunderbird. New gfxcard-nvidia-legacy mix-in for older drivers. Updated NVIDIA drivers to latest releases. Conky updated. kde-plasma merge fixes. mesa merge fixes and version bump. ffpmeg updated to latest release, with fixes for arm-64bit. Latest Spotify release added. Openrc net-online major improvements. New Language added: crystal (check it out) debian-sources/debian-sources-lts updates and now compile using your -march settings (since custom-cflags is now enabled by default.) Prior to this they compiled using generic 64-bit optimizations on x86-64bit. New encrypted-root mix-in to be used to enable LUKS in genkernel/debian-sources(-lts). To use, enable this mix-in and re-build your debian-sources(-lts) kernel. Rust-kit is now at 1.37-prime New dev-lua/lua and fixes for lua-using packages. Ebuilds using lua-5.2+ should use the new dev-lua/lua ebuild (not the legacy dev-lua/lua.) fwupd bumped to 1.3.1 nginx, nginx-unit, dovecot, php, mariadb vivaldi updated dovecot updated Anything I forgot? Follow up in this discussion thread. MANY OF THESE FIXES WERE SUBMITTED BY OUR USERS! Thanks to bcowan, perfinion, jhan, tux, tczaude, KlipKyle, scottfurry and anyone I forgot to mention for making Funtoo better for everyone πŸ™‚ πŸ™‚ πŸ™‚
  5. 3 points
    drobbins

    Funtoo Linux 1.4 MR 5 stages available

    Funtoo Linux stages have been updated to contain the latest stuff in Funtoo: GNOME 3.36.2, latest Mesa/GL stack, support for Intel Iris graphics ("epro mix-in -gfxcard-intel +gfxcard-intel-iris; emerge -auDN @world for those who want to try), and many other updates. Download here: https://www.funtoo.org/Subarches Install docs here: https://www.funtoo.org/Install Enjoy!
  6. 3 points
    Hi All, core-gl-kit is now on 2.0-release by default. You will see updates to many packages. Now available are Intel Iris graphics, which is much faster and supported on modern Intel integrated graphics chipsets. To use Intel Iris, perform the following steps: # epro mix-ins -gfxcard-intel +gfxcard-intel-iris # emerge -auDN @world --jobs=3 If you want to continue with the classic drivers, or are not using Intel integrated graphics at all, you can just do the world update to get updates. Please report any issues you encounter to bugs.funtoo.org! There have been major updates to packages so I am expecting some bugs (and some have already been reported and fixed.)
  7. 3 points
    Everyone, New 1.4 Maintenance Release 4 stages have been built. These include GNOME 3.34.5 as well as updated Firefox and other packages. As we continue to expand the use of our autogen framework (metatools) , more and more desktop packages are staying up-to-date automatically. Enjoy the new builds -- they are now available for download via www.funtoo.org and our CDN77-powered CDN. Best, Daniel
  8. 3 points
    GNOME 3.34.1 is ready for use and will become the default version of GNOME in 1.4-release in a few days. If you would like to use it now, you can add the following to /etc/ego.conf: [kits] gnome-kit = 3.34-prime Then ego sync, emerge -auDN @world, emerge @preserved-rebuild, and restart xdm and you should be in business. If you would like to avoid upgrading to GNOME 3.34, now is the time to insert the following code into /etc/ego.conf: [kits] gnome-kit = 3.32-prime Then, in a few days when 3.34-prime becomes active, you will stick with 3.32-prime and not get the updates until you want them.
  9. 3 points
    drobbins

    Funtoo Linux 1.4 Released!

    Hey everyone -- Funtoo Linux 1.4 is now to be considered officially released! Some changes in the last several weeks include: Updating to gcc-9.2.0 to address an upstream compilation bug (thanks: calrama) Additional testing/fixing of dependencies (thanks: sandro and others) New debian-sources and debian-sources-lts kernels (thanks: bcowan) Debian-sources-lts will now default to using "custom-cflags" USE by default, which will give you a more optimized kernel. -march settings from your subarch mix-in will be applied to your kernel compilation as well. This appears to result in a noticeable performance improvement. Many thanks to jhan, digifuzzy, klipkyle, librin.so.1, niranjan, sandro and everyone else (sorry if I forgot to mention you) for making this the most tested and most community-focused release of Funtoo ever! I will continue to update documentation on the wiki relating to 1.4, and of course, 1.4 development continues with pull requests and issues reported to bugs.funtoo.org. I hope to start 2.0 development in about a month. Also note -- we now have a "Announcement Discussion" forum visible from the main forums page which allows posts and is open to discussing any announcements. Best, Daniel
  10. 3 points
    drobbins

    Funtoo Linux 1.4 Released!

    Please see the following for more info: Release Notes: https://www.funtoo.org/Release_Notes/1.4-release Upgrading from 1.3: https://www.funtoo.org/Upgrade_Instructions/1.4-release Download and Install: https://www.funtoo.org/Install/Introduction
  11. 2 points
    Just going to follow up with some more info. First, thanks to pross for pointing out I had a typo in the 'epro' command above, now fixed! πŸ™‚ The difference between Intel Iris and 'classic' Intel is that 'classic' Intel uses the xf86-video-intel driver (with ebuild of same name), which has classically been the way you get accelerated video with Intel Integrated graphics. The Iris graphics uses the more generic 'modesetting' driver (no special ebuild for this), and uses a gallium-based driver which is now a part of media-libs/mesa so xf86-video-intel is not used at all. During testing I found that if you have xf86-video-intel installed, you *won't* get the Iris graphics. xf86-video-intel seems to have priority and will get initialized first. So if you are doing troubleshooting or not using the magic mix-ins, you'll want to make sure that xf86-video-intel is not installed if you want to use Iris. The way to check what driver is being used -- the definitive way -- is to look at /var/log/Xorg.0.log and search for 'modesetting' and 'intel' and determine which if any are initialized. In some circumstances, you may see references to both so you need to look very carefully at the end to see which one is active. Now, about the mix-ins themselves which handle all the complication for you, so you just set the right one and don't have to tweak everything by hand. The gfxcard-intel (gfxcard-intel-classic) and gfxcard-intel-iris mix-ins do the 'magic' for you -- gfxcard-intel-iris will MASK xf86-video-intel, and enable video_cards_gallium-iris, which along with a dep in xorg-drivers will BLOCK xf86-video-intel from being installed (forcing it to be uninstalled.) Thus, the "magic" that gets your system in the proper state for Iris. The mix-ins live in /var/git/meta-repo/kits/core-gl-kit/profiles/funtoo/mix-ins if you want to look at their exact settings. You will see there also associated USE flags associated with each mix-in that are passed to the mesa ebuild which are different for the classic and Iris configuration.
  12. 2 points
    Hi all, GNOME 3.36.2 has hit the tree, as well as an OpenSSL update and updates to Docker. To update, perform the following: # ego sync # emerge -auDN @world --jobs=3 # emerge @preserved-rebuild While GNOME is upgrading, apps may not launch. This is normal. After upgrading GNOME, a reboot is recommended to flush out all older GNOME processes and start up a GNOME 3.36.2 environment.
  13. 2 points
    A full set of Funtoo Linux 1.4 maintenance release 2 stages has been uploaded to build.funtoo.org. These stages include: GNOME 3.34.2 Updates to debian-sources-lts (4.19.87_p1) Updated Linux firmware Updated firefox Various other fixes If you are already using 1.4, you can get all these updates via a regular ego sync and world update. But if you are planning to install 1.4 from scratch, these builds are up-to-date.
  14. 2 points
    drobbins

    Funtoo is now on Discord

    Hey Everyone, We're now supporting Discord as an official Funtoo online community. Join via this link: https://discord.gg/BNUSpUU Forums discussion thread for this announcement here: Best, Daniel
  15. 2 points
    You and I are on the cusp of a political discussion here πŸ™‚ but I would argue that even "reputable" sites these days are spewing propaganda, so there is no substitute for critical thinking. We do not live in an ethical age. Whether intentional or the result of our modern echo chamber, there is misleading information EVERYWHERE online and I couldn't really tell you ANY trustworthy source of information that I would tell you that you could trust implicitly. Even Associated Press and Reuters seem horribly compromised and full of spin! Every journalist seems to want to write an atomic bomb of a news story and go though such extreme lengths to try to inject bias while remaining 'factual' -- it would be comical if it weren't so sad. Assuming a posture of skepticism and "it's probably not as bad as it sounds" is highly recommended when looking at sources of information online. Politics is the art of getting a ton of people pissed off and then leveraging that energy -- and doing this online is known to be extremely effective. So you just have to be wary. Don't be a pawn. Now, as for the other issues you raised, I guess I can read and think about those now that I've vented πŸ™‚
  16. 2 points
    drobbins

    SOLVED: Container Host Out of Space

    @tux yes LXD has its limitations compared to OpenVZ -- I still miss OpenVZ a lot. But LXD is gradually improving. I have plans to offer a lot more to users with hosting and I am hoping to actually realize these plans in a month or so -- let's see if things go as planned πŸ™‚ (Note: it should help with this issue.)
  17. 2 points
    Hey All, I've gone ahead and updated Funtoo Linux 1.4 to contain the latest implementation of SELinux from Gentoo. SELinux is working well under Funtoo now. To use it, see the SELinux page on the Funtoo wiki. Also reference the https://wiki.gentoo.org/wiki/SELinux/Installation and https://wiki.gentoo.org/wiki/SELinux pages for documentation reference. These Gentoo wiki pages were originally put together by SwiFT and are excellent, and the SELinux team has kept them up-to-date (I must give credit where credit is due πŸ™‚. We need to work on our modest SELinux wiki page here to improve it: https://www.funtoo.org/SELinux If you are new to SELinux, here are the basic steps. Enable the SELinux mix-in, emerge the SELinux tools as well as policies, rebuild world and etc-update, apply security labels to files, enable in kernel in "permissive mode" -- where it just logs things but doesn't "block" anything, and then start to play. In your /etc/boot.conf, you'll want to add "security=selinux enforcing=0" to your "params +=" line and re-run "ego boot update" to get the kernel booting properly. This is assuming you are using debian-sources or debian-sources-lts. Funtoo is also helping perfinion (find him in #gentoo-base on freenode) in Gentoo test the SELinux-next security policies. Here is how you can test them: 1. Add the following to package.keywords: sec-policy/selinux-* ** 2. Then emerge @selinux-rebuild to reinstall all the 9999 policies (to be used with 2.9 userspace) 3. Do a full relabel. 4. Reboot. Then, you can run and start auditd which will generate logs of what SELinux activity is going on. After your initial reboot into the new SELinux, start auditd with empty logs, and keep it running as you go about your business. After a few days of using Funtoo as you normally would, these logs can be useful to the SELinux team to determine if the new policies are working as expected. Of particular interest is the use of elogind under SELinux. Once using the new SELinux-next policies, 'ps auxfZ | grep logind' should be in the systemd_logind_t domain. Thanks to perfinion and the SELinux team for moving SELinux forward! Let's help them πŸ™‚
  18. 1 point
    cardinal

    gimp failed to start

    File an issue report at bugs.funtoo.org rj@funtoo ~ $ gimp (gimp:14880): GLib-GObject-CRITICAL **: 10:19:51.172: g_param_spec_internal: assertion 'is_valid_property_name (name)' failed gimp: fatal error: Segmentation fault (gimp-org-pagecurl:14912): LibGimpBase-WARNING **: 10:19:51.227: gimp-org-pagecurl: gimp_wire_read(): error Always try to start a program in terminal when it fails by clicking shortcut in start menu. The error message enabled me to find the closed upstream bug report and a temporary workaround. https://gitlab.gnome.org/GNOME/gimp/-/issues/4392
  19. 1 point
    drobbins

    * Error: circular dependencies

    I've already found the issue and resolved it. πŸ™‚ Fix should be in the tree on next regen, in about 25 minutes.
  20. 1 point
    lego12239

    acct-user/acct-group seems wrong

    Hi, all. Am only for me this seems strange? User/group management with packages is wrong, imho. If gentoo wants constant uid/gid for some daemons, why doesn't simply tell package maintainers to do this with enewuser/enewgroup? Why this strange idea?..
  21. 1 point
    drobbins

    Fixing meta-repo issues

    Today I made a mistake and updated meta-repo using my older environment instead of the newer one I had set up recently. This resulted in some problems with meta-repo. I have fixed the problems but you may need to perform a few steps to 'fix' things if you did an ego sync today (Feb 6 2020) If you have synced today, you may need to rm -rf /var/git/meta-repo && ego sync as the branches got out of sync with their git history. You will know this because when you ego sync, it will tell you that 'history has diverged' (if you look at git output) and you'll see output from git like "please tell me who you are" (wanting your name and email) because it's trying to do a merge commit rather than fast-forwarding. You may also see editors-kit not sync successfully. If you didn't sync today, you should be fine and everything should continue working next sync. The fix should be pretty easy -- sorry for the issue.
  22. 1 point
    Some more updates headed your way: nvidia-drivers-440.44 now available. Remember that you will also need to emerge nvidia-kernel-drivers for your kernel to make the kernel modules available. steam-nvidia-launcher is now at 1.5. Fixed are annoying gtk+ dialog messages when starting up the launcher, and also FL-6907 (thanks @nrc) the pulseaudio config hard-coded for UID 1000.
  23. 1 point
    Recent Funtoo News: GNOME 3.34.3 is now available in Funtoo (as part of gnome-kit 3.34-prime, the default kit) A Gentoo dev found that it is theoretically possible for arbitrary users on the system to locallly 'exploit' a package while it is being built. Portage-2.3.78-r1 addresses this by removing 'other' permissions from /var/tmp/portage. ego-2.8.0 is released with updated sync code.
  24. 1 point
    Running 32-bit Win apps requires 32-bit wine. The wine available in 1.4 is 64-bit and will not run 32-bit Win binaries. The following is a quick writeup on how I did it. There are other ways, possibly better, but this one is mine and I stand by it. πŸ™‚ I opted to use a chrooted 32-bit environment in which I installed Gentoo and wine. I started by making a ~/gentoo folder and downloading a current 32-bit Gentoo stage3 in it: mkdir gentoo cd gentoo wget <stage3_URL> You need to be root for the following steps sudo su tar xpf <stage3> cp /etc/resolv.conf /home/<username>/gentoo/etc And then follow the installation steps in the Gentoo manual mount -t proc none proc mount --rbind /sys sys mount --rbind /dev dev env -i HOME=/root TERM=$TERM /bin/chroot . bash -l # export PS1="(chroot) $PS1" (chroot)# emerge-webrsync (chroot)# emerge --sync (chroot)# eselect profile list and select a desktop profile. For me it was #5, default/linux/x86/17.0/desktop (stable). The desktop profile brings in Xorg which will be needed later for wine anyway. (chroot)# eselect profile set 5 Edit make.conf to add the correct MAKEOPTS ("-j7" worked for me) then do a world update, and go do something else for a couple of hours. (chroot)# emerge -avuDN @world Once done, set up Xserver redirection in chroot so it displays the image on the host. On the host: xauth list will show you the "magic" cookie of your host display. Put it into .Xauthority on the chroot: sudo xauth extract <path_to_chroot>/root/.Xauthority <hostname>/unix:0 where <hostname> is the name of your host machine (mine is eb1) (edit) NB when you log out of your host then log back in, the cookie changes so you will have to redo the line above, or X redirection will stop working. In the chroot, verify that the cookie is set correctly: (chroot)# xauth list should show the same as on the host Also set the DISPLAY variable in chroot: (host) echo $DISPLAY should show ":0.0" (chroot)# export DISPLAY=":0.0" You can add the above line to /etc/profile in Gentoo so it gets automatically set every time you enter the chroot. Verify that it works. In chroot run xcalc (you may have to install xcalc first), and it should display on the host. (chroot)# xcalc If no errors, emerge wine in the chroot and configure it. You should have a 32-bit wine now, ready to run 32-bit Windows binaries (minus configuring, figuring out missing libs etc - but this is beyond the scope of this writeup) (chroot)# emerge wine Final size of the chroot Gentoo on my disk was close to 4.5GB.
  25. 1 point
    joachin

    pangomm & libreoffice error

    Hey guys, having some problems trying to install pango mm: pangomm and libreoffice-bin: !!! Multiple package instances within a single package slot have been pulled !!! into the dependency graph, resulting in a slot conflict: dev-libs/boost:0 (dev-libs/boost-1.65.0:0/1.65.0::core-kit, ebuild scheduled for merge) pulled in by dev-libs/boost:0/1.65.0 required by (app-office/libreoffice-bin-6.2.4.2:0/0::desktop-kit, ebuild scheduled for merge) ^^^^^^^^^ (dev-libs/boost-1.70.0:0/1.70.0::core-kit, installed) pulled in by >=dev-libs/boost-1.65.1:0/1.70.0= required by (sys-fs/cryfs-0.10.2:0/0::core-kit, installed) ^^ ^^^^^^^^^^^^^^^^ (and 1 more with the same problem) app-text/hunspell:0 (app-text/hunspell-1.6.2-r1:0/1.6::text-kit, ebuild scheduled for merge) pulled in by app-text/hunspell:0/1.6 required by (app-office/libreoffice-bin-6.2.4.2:0/0::desktop-kit, ebuild scheduled for merge) ^^^^^^ (app-text/hunspell-1.7.0:0/1.7::text-kit, installed) pulled in by app-text/hunspell:0/1.7= required by (kde-frameworks/sonnet-5.59.0:5/5.59::kde-kit, installed) ^^^^^^^ (and 1 more with the same problem) NOTE: Use the '--verbose-conflicts' option to display parents omitted above It may be possible to solve this problem by using package.mask to prevent one of those packages from being selected. However, it is also possible that conflicting dependencies exist such that they are impossible to satisfy simultaneously. If such a conflict exists in the dependencies of two different packages, then those packages can not be installed simultaneously. You may want to try a larger value of the --backtrack option, such as --backtrack=30, in order to see if that will solve this conflict automatically. For more information, see MASKED PACKAGES section in the emerge man page or refer to the Gentoo Handbook. Thanks!
  26. 1 point
    klipkyle

    corrupt meta-repo

    All the repos are git repositories. So usually the easiest way is to clone a fresh copy of the meta-repo. mv /var/git/meta-repo /var/git/meta-repo.old ego sync ego will clone a fresh copy of the meta-repo from Github. Since this is a case where Virtualbox crashed, I also recommend performing file system checks if they have not been performed automatically.
  27. 1 point
    Hi Everyone, I"ve posted a new YouTube video which I hope you find useful. Troubleshooting is an important topic and something worth reflecting on.
  28. 1 point
    @ennui AppArmor is enabled again, and for a bit the dovecot mess resurfaced. But I disabled the dovecot profiles this should have already been resolved. If necessary, reboot your container and it should be fine.
  29. 1 point
    @ennui sorry don't have access to funtoo infrastructure anymore. you'll have to wait for drobbins to answer this one.
  30. 1 point
    Hi All, I've upgraded our authentication framework, and you should be able to log in. But the migration was not without hiccups. You should be able to log in to forums, wiki, bugs, code.funtoo.org and friends. You might notice that some bugs on bugs.funtoo.org have my name listed as "drobbins#1". This isn't because I think I'm awesome, but because our migration triggered some bad behavior in JIRA and I need to repair its user database. It's annoying, but very fixable, and I'll get to this soon, and should continue to work in the meantime. If you have login issues, please message me privately on the forums, or contact me directly on discord or telegram (links on the main wiki page.)
  31. 1 point
    drobbins

    New steam-nvidia-launcher

    Steam now has an official launcher script to make it easier to use, called "steam-nvidia-launcher". I've updated the Steam documentation at https://www.funtoo.org/Steam to now direct users to use the launcher script instead. It's easier to use and more robust, as you just have one script that does everything from download the docker image, to create the container, to start the container if it already exists and needs to be started locally. steam-nvidia-launcher also fixes a bug where the Steam container wouldn't start consistently after a reboot. Launcher is available here. Remember to consult the wiki (link above) for usage info: https://code.funtoo.org/bitbucket/users/drobbins/repos/docker-steam/browse/steam-nvidia-launcher
  32. 1 point
    upc0d3

    AMD FirePro V4900 - Configuration help

    Hi @jhan, @nrc, With your help, I manage to fix the issues. What I was missing was to remerge the linux-firmware after doing correct configuration of the mesa and xorg-drivers. Thanks a lot!
  33. 1 point
    stamasd

    Flatpak

    Since 1.3 was released I've been using this Gentoo overlay (using the local repository method) to install flatpak and Steam in it: https://github.com/fosero/flatpak-overlay It works well even after upgrading to 1.4
  34. 1 point
    Fixed masking compat32.
  35. 1 point
    Hi folks O/ few years ago I wonder about a friendly version of Gentoo and Funtoo, the gentoo community don't liked, but I keep did some tests but I didn't continue, well, few week ago I start again, but this time only a Funtoo Friendly version, and now I have something really beginning. the project will resume in few flavors and one version with a overlay with update packages and few extra. the funtoo flavors are X+openbox, gnome and Plasma, they are just the Funtoo Stage3 Generic with few packages and some configuration. and has one version with plasma, but with an overlay with few update packages and other stuffs, a stage more out of the box, I want make something to people learn about gentoo/funtoo or for who use the system without spent hours to build the system. the webiste will be done in the next weeks, and the stages will be available in the next days "sorry, I'm with one pc now, and the net is a turtle". website -> https://bentoo.info/ binhost -> http://binhost.bentoo.info github repos : overlay -> https://github.com/lucascouts/bentoo configurations -> https://github.com/lucascouts/bentoo-cfg I don't know if the funtoo community will like but anyway I'll forward with this project, but will be great if few users could help with feedback or criticisms. thank you anyway ?
  36. 1 point
    calrama

    Funtoo is now on Discord

    (Quote emphasis mine) That may be the case from your perspective and that's perfectly fine. The reason why I made a sad reaction to the announcement (and the update) is because mine is different. To the best of my knowledge Discord requires sending all your voice data to their servers with only transport encryption, not end-to-end, so there's no reason to believe they aren't storing it. If you think conventional data breaches are dangerous, consider what would happen if a criminal element got access to a vast amount of such voice data (impersonation being only the most obvious one). You may call me paranoid, but in recent times this risk is unacceptable to me. My personal issue with Telegram is one of trust in their technology. MTProto 1's numerous unexplained oddities are well known and haven't all been addressed in version 2. This, combined with the fact that the principal mind behind their design is not a cryptographer, marks Telegram as "do not touch with a ten foot pole" for me. Don't get me wrong, I generally love shiny new technology and I do recognize the immense convenience both of these tools have for a vast amount of people, but I will not use something just because it's shiny and more convenient for other people. It also needs to not be a regression from existing technology for me, which both of these two tools are. I'm happy in the sense that more people are likely to join the Funtoo community. I'm sad that it had to be these two technologies, for the reasons I mentioned.
  37. 1 point
    drobbins

    Funtoo is now on Discord

    For those who may not understand the embracing of next-gen communication clients... it's really not about the technology here. We have people who use Discord and Telegram already, and do not like IRC. I, personally, am really enjoying the newer communities over freenode. I feel like there's too much rumors/OSS politics on freenode these days. I spend my time on freenode dealing with this crap rather than having fun and moving Funtoo forward. I see too much weird community dynamics -- too much drama, and we're sitting right next to the Gentoo channels and there is often unpleasant "overspray" I need to deal with -- things like "hey drobbins, did you see that person X is saying thing Y about Funtoo and/or you in channel Z?" Then I feel obligated to personally deal with it. If you are someone who loves freenode and the freenode community, you should be there. I have been using freenode since before it was called freenode. I remember when lilo (now deceased, and relentlessly attacked by his detractors) ran the show. Freenode, despite its reputation for being the place on the Internet for OSS-related chat, has always been a rough place socially to some degree. The truth is that there are a lot of options for Funtoo users to find a community that works for them, and I'm really happy to be not just on Discord but on Telegram too: https://t.me/funtoolinux The important thing is to find a community that is a positive environment for you, that gives you energy rather than takes it away, so for these reasons I am very glad for Discord and now Telegram and think everyone should be too πŸ™‚ The newer technology is also nice -- like being able to edit posts, post actual screenshots into the channel for support purposes, funny gifs, voice support, *amazing mobile clients*, etc etc etc. -Daniel
  38. 1 point
    Everyone, GNOME stages are now officially part of Funtoo. These beefy stages (that was a Larry the Cow pun) weigh in at about 1.4GB and include the following goodies: GNOME 3.32 Mozilla Firefox Popular graphics drivers already enabled metalog, vim, linux-firmware Same debian-sources-lts kernel that is in our regular stage3 multicast DNS/avahi enabled by default The install docs have been updated to include references to these new GNOME stages. You can find them for download on the Subarch pages or on https://build.funtoo.org. Also note that we should now have LXD images for every subarch which will allow you to set up optimized Funtoo-in-Funtoo environments using LXD. Of course, these are fully optimized stages and we plan to continue to offer these moving forward.
  39. 1 point
    @lefsha Funtoo *does* include ALL ebuilds from Gentoo -- I think it is just a matter of trying to understand the difference between Funtoo and Gentoo. Funtoo Linux 1.4 is based on a 21 Jun 2019 snapshot of Gentoo Linux, plus a variety of package updates in selected areas. Such as: GNOME 3.32, gcc 9.2.0 default, latest mesa, libglvnd enabled by default, Debian kernels, nginx, mariadb, other server packages, etc, etc. updated by me as well as Funtoo Users. So think "Funtoo = Gentoo snapshot + goodies." In general, you should have everything in Gentoo automatically, at least what was in Gentoo at the time of the snapshot. And key areas of Funtoo that users wanted updates for -- they submitted pull requests to code.funtoo.org to update these packages. If a package is out of date, no problem -- submit a pull request (PR) to code.funtoo.org, and it will be updated. When we start Funtoo Linux 2.0 development, we will use a Gentoo snapshot from late 2019 as the foundation for the next release. The goal is to do this every 3 months. We are working on picking up the pace of our release model and things are starting to move very, very quickly, so I wouldn't worry too much about Funtoo being 'behind' Gentoo. See https://forums.funtoo.org/topic/2998-14-even-more-new-stuff/ for info on what has been added in the last 20 days. Funtoo Linux is a semi-rolling release, with actual true releases. Once you get used to it, it shouldn't be an issue, but maybe a pull request is in your future? Best, Daniel
  40. 1 point
    My compliments for the new funtoo, it works perfectly.
  41. 1 point
    bcowan

    nvidia modules not installing.

    For now you can use the 390.129 in my overlay: https://github.com/bradlyatc/funtoo-overlay/tree/master/x11-drivers
  42. 1 point
    bcowan

    cannot grab -march

    I filed a bug for this, https://bugs.funtoo.org/browse/FL-6664 it should be fixed now.
  43. 1 point
    sacviper

    cannot grab -march

  44. 1 point
    bcowan

    cannot grab -march

    It is fine to use generic arch, if that is what you *really* want shrug. If you do want generic then you need to add -custom-cflags to USE or package.use for debian-sources-lts
  45. 1 point
    I reported problem and solution here: https://bugs.funtoo.org/browse/FL-6645
  46. 1 point
    drobbins

    How to run Steam in Funtoo/LXD

    I've removed the PDEPEND from nvidia-drivers so they don't automatically install nvidia-kernel-modules. But nvidia-kernel-modules has nvidia-drivers as a dependency. So if you are installing on bare metal, do emerge nvidia-kernel-modules and you will get everything you need, and if you are installing in container, emerge nvidia-drivers and it will skip the modules. This should be in the live tree for 1.4 already.
  47. 1 point
    drobbins

    How to run Steam in Funtoo/LXD

    In my testing, the --exclude method did not work and I manually modified the PDEPEND in nvidia-drivers in /var/git/meta-repo/kits for now as a local work-around. Just a note -- you will likely need to do this too. Other option is to also --exclude nvidia-drivers and then do an emerge -1 nvidia-drivers --exclude nvidia-kernel-modules after the big emerge.
  48. 1 point
    palica

    How do I ask a good question?

    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.
  49. 1 point
    rage

    funtoo logo ideas

    I had two new ideas for this, 1) Fortissimo symbol This one is a bit of a math joke- funfun (fun x 2); which is expressed by the above symbol.. 2) Something involving an exclamation point! Funtoo is fun and exciting! So it only makes sense that the logo includes a symbol that depicts the same energy.
  50. 1 point
    AdiosKid

    funtoo logo ideas

    Maybe that ??
×
×
  • Create New...