Jump to content


Funtoo Linux BDFL
  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by drobbins

  1. There are troubleshooting steps here: https://www.funtoo.org/Steam#Container_Validation Try them, let us know your results.
  2. @cardinal that isn't really a fix for the issue, just a workaround. @kundor yes, this is a bug. A couple of weeks ago, our upstream vim had issues, so I forked vim and vim-core. But I did not grab gvim. It should be reported to bugs.funtoo.org and we'll get it fixed. Thanks 🙂
  3. 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
  4. @john123 yes! This is a good idea. Please see if we have an issue open for it on the bug tracker and if not open one to track progress. Thank you.
  5. I would probably need to play with it a bit to see, but make sure that *all* sandboxing is disabled. There is now a network-sandbox which could be causing the failures regarding network interface.
  6. @minou666 yes sometimes I miss Montreal -- it has a place in my heart. I do have some family there, but I am not very close to them. I grew up in Montreal in the 70's and early 80's as a kid and there was a lot more youthful energy in the city. Today it feels more 'dead' (maybe that is a bit too harsh) or quieter, or maybe a bit too refined. People have grown up. Youthful neighborhoods are filled with older people. Not as many young families. No 'electricity' or that feeling that you are part of a special thing at a special time in history. You feel that people are a bit more in the 9-5 grind, or maybe better to say the work routine of mid-life, with still some good life balance, but it is routine. Not bad, but in contrast to earlier times quite sedate. It feels a bit sad to me because when I was a kid there, it was alive. Now it feels sort of like a modern version of a very good sports car that has lost some of it's 'magic', like the soul has been refined out. You will find some exceptions to this in some areas, and it's still a wonderful city -- I am just talking about the overall impression which was significant -- I was left with a feeling that despite it being a lovely city, it did not have the same magic I was hoping to experience. Maybe Montreal is laying dormant until it awakens again. For a good city to visit I recommend visiting Lviv, Ukraine. I was there relatively recently and it had very good energy. In a strange way I feel like you may feel more of a connection to the old Montreal in Lviv, on the other side of the world. Very different but similar energy. If you go there I think you will see what I mean (and if not, then I think you will still enjoy it 🙂. It is a city with a lot of history at a special point in time trying to make sense of itself in the world and you can feel that. The exchange rate also makes it a very inexpensive place to visit. I also like Capitol Hill in Washington DC as a great place to be. Unlike US politics, everyone there is friendly and laid back, good Metro, walkable, outdoor markets, lots of things to do and see, and parks that are actually used by families. There is activity without the feeling of people being 'busy'. Best, Daniel
  7. This may be due to some portage sandboxing not being disabled and not working in qemu. Can you paste your /etc/make.conf in the chroot?
  8. Also you seem to not understand that debian-sources-lts is 1) Funtoo's official kernel and 2) very up-to-date when it comes to security fixes. You are free to run your own kernel but the debian-sources-lts kernel you see is not "a very old debian kernel." Please read this: I truly do not understand why people do not grasp this. Do we not mention this in enough places? Maybe I need to add a paragraph about it in the Install Docs?
  9. Hey everyone, Funtoo Linux 1.4 maintenance release 3 has been available for a few days, and includes our official WebKit builds, updated security-patched kernels and GNOME 3.34.3 pre-built. Also of note: the addition of the new WebKit temporarily broke wayland builds. This is now resolved and GNOME now builds correctly with the wayland mix-in. Also, important: The #funtoo freenode channel will be shut down in around 24 hours, as I no longer use freenode so I can't continue to op the channel there. Please switch to our official chat on Discord and Telegram. Thanks! Telegram: more informal: https://t.me/funtoolinux Discord: "official" chat: https://discord.gg/BNUSpUU
  10. 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.
  11. @walterw the advantages of debian-sources-lts are numerous and I'll go into more detail below but the primary reason to use this kernel is that debian-sources-lts IS SUPPORTED, and gentoo-sources IS NOT so you should not really use it with Funtoo. I know lots of people just assume they can start using Funtoo just like they were using Gentoo, but I encourage you to use Funtoo as it is intended to be used, and that is with the debian-sources-lts kernel. The advantages of debian-sources-lts: It generally doesn't randomly break things due to API changes in the kernel, since it's a 'long term stable' kernel. It's faster (optimized for your arch by default) It has the latest CVEs and fixes for Intel side-channel attacks and it is updated frequently, like around once a month. It is ready for use in production, such as on servers in datacenters. This is a huge benefit. It is compatible with NVIDIA drivers and doesn't require these to have special patches to work. It is Debian's kernel and as their stable kernel it is tested by thousands of people, a lot more than test gentoo-sources. It's the one used by the majority of Funtoo users so it is also tested in Funtoo as well. Much less likely to experience problems. It is the kernel *I* use on my laptop, workstations, and also used on Funtoo servers. So that means something I think. It comes pre-built on stage3 tarballs. Massively speeds up install on new systems. Not a minor benefit. If you use it and build it with USE='binary' (the default), things will 'just work' because this is a full modular kernel and has all common functionality enabled. If you use your own kernel, often you will need to recompile to enable some feature you forgot, and things might not work (virtualbox, random package that uses a kernel feature). Quite a few bugs on the bug tracker and problems on the support forums are tracked to 'different custom kernel'. So I think the advantages are numerous. The reason you should not use gentoo-sources is that I don't think you can say any of these things about gentoo-sources. When using a kernel where you can't afford it to be flaky, it is best to build on a vetted kernel and debian-sources-lts is just plain vetted to a much more significant degree. EDIT: the result of all these benefits are: more stability and less time wasted.
  12. @dkg I agree it's confusing. I recommend a clean reinstall rather than an upgrade if at all possible. Gentoo doesn't handle upgrades well and thus Funtoo inherits these problems. I hope to address them in the future but the first step was to attempt to document the upgrade instructions.
  13. For now I have updated the install instructions so people know to run the chown command before ego sync. I will address this in future stages.
  14. This is a legitimate bug. To work around the issue, perform the following before performing an ego sync: # install -d /var/git -o 250 -g 250 Sync will then complete successfully.
  15. I can reproduce this issue so it looks like with an issue with the new stages or ego. I am investigating.
  16. From an install instructions perspective, they are correct. You should remove python-3.6 as Funtoo Linux 1.4 does not have python-3.6 and instead has python-3.7. So if you are upgrading your system to 1.4 and want your system to be set up that way, it is necessary to remove python-3.6.
  17. Some additional important info -- If you are a previous user of steam-nvidia-launcher (1.5) then you will likely need to manually wipe your existing Steam container as the steam-nvidia-launcher currently doesn't do this for you. What you do is do a "docker ps -a" and get the container ID of the container, then "docker rm" it. (the container should not be running) When you use steam-nvidia-launcher next, it will re-create the container, but "hook in" to your existing Steam settings and downloads in ~/SteamData in your home directory. You will now be running 1.6 of the container. Automatically upgrading steam containers is something I want to add to future versions of the launcher beyond 1.6. Another important note is that the new webkit currently is missing a dependency needed for Wayland support. This is a relatively easy fix, and once a bug is opened on the bug tracker for this I can post details on how to send a PR to fix it. Since I do not use wayland, I forgot to add this ebuild. And I wanted to get the new webkit out ASAP since several things in Funtoo were broken in funtoo due to what we could call 'the (now resolved) webkit-gtk situation'.
  18. @dkg I am assuming you are experiencing the bug under Funtoo since you are posting on the Funtoo forums. In that case, open the bug on the Funtoo bug tracker. You should not open bugs for issues you experience under Funtoo on the Gentoo bug tracker. So yes, if my assumptions are correct, then close the bug as invalid on the Gentoo bug tracker and open one on the Funtoo bug tracker. If you are experiencing the identical issue on a Gentoo box, then yes, you report the issue you are experiencing on Gentoo to the Gentoo bug tracker. But since you are posting here about a Funtoo issue, and you opened a bug on the Gentoo bug tracker, this is wrong. Just because you also use Gentoo does not entitle you to report Funtoo bugs to the Gentoo bug tracker. This is not helpful at all since I don't see the issue, so the issue will NOT get fixed in Funtoo. I hope that makes sense.
  19. @dkg you should really not file Funtoo bugs on the Gentoo bug tracker. It is an issue in Funtoo, not Gentoo. Please close the bug as invalid on Gentoo's bug tracker and file it on Funtoo's bug tracker.
  20. @kratsy-tony you can "steam-nvidia-launcher attach" to attach to a running container and edit /root/steam.sh. But I think I know why the container didn't update ... keep reading below. BTW, that's really cool that you were able to use the steam-nvidia-launcher under Optimus -- I hadn't tested that. The audio issue *should* be fixed with 1.6, but you *may* need to "blow away" your old container to fix the audio issue, now that I think about it. I don't think the launcher is checking to make sure the container is 1.6 so it's running your existing 1.5 container. Do a "docker ps -a", grab the container ID, then do "docker rm <container-id>". When you use steam-nvidia-launcher the next time, the container will be recreated and you'll have a 1.6 container. Edit: also note your existing downloads should be preserved since they are bind-mounted into the ~/SteamData directory in your home dir on your host.
  21. @dkg you may find that some of the 'left over' things depending on 3.6 are actually 'old'/deprecated and can be removed. For example, pycrypto is old, and should be deleted, and pycryptodome is now being used in its place.
  22. Debian-sources-lts-4.19.98_p1 is now unmasked in the tree with the latest security fixes for Intel. Also available is a new steam-nvidia-launcher 1.6 with fixed audio. The big news is that Funtoo is using a new approach with webkit-gtk. For those who don't know, or need a refresher, webkit-gtk is an ebuild that is part of GNOME. It provides Web browser (HTML rendering + javascript) functionality. In fact, webkit-gtk is just a snapshot of the sources of WebKit (https://webkit.org) which is the foundation of many modern Web browsers, and is actively developed primarily by Apple and other contributors. GNOME just grabs a version of these sources and puts them in a tarball and gives it a version number. Interestingly, although Apple appears to be the primary commercial contributor to WebKit, the WebKit project was actually started by KDE. Learn more here: https://en.wikipedia.org/wiki/WebKit We decided to stop using GNOME's webkit-gtk. Why did we do this? Our Webkit-gtk ebuild started experiencing issues when we upgraded GNOME or some other ebuild recently. In tracking down the problem, I found our current webkit-gtk ebuild, which is the latest upstream stable release from GNOME, was actually very out-of-date and still riddled with bugs that were already fixed in webkit.org's current WebKit. It became very frustrating to work with and there wasn't an easy fix like adding a 'simple patch' or set of patches to fix the situation. So I couldn't just tweak things and get webkit-gtk working well. And the build process used in the ebuild was also unreliable. So rather than try to patch all the significant bugs in webkit-gtk, I took a very recent (2020-01-30) snapshot of WebKit, and applied minor patching to it to get it working under GNOME. The webkit-gtk (now webkit) ebuild was also heavily reworked to build from WebKit sources using the official process, which is very similar to the method that Apple and other use to build WebKit. I also removed a lot of extra USE variables that can be used to tweak WebKit functionality, but can also be used to *break* WebKit if you are not careful. I kept the essential USE variables that we *need* to be able to adjust (X, wayland, etc.) The result is that we are now using our own WebKit that is very lightly forked from upstream WebKit. When you update your system, you will likely see both webkit and webkit-gtk getting merged. webkit-gtk- is now simply a virtual/placeholder ebuild that depends on the 'real' net-libs/webkit ebuild, which is our essentially rewritten ebuild. This resolved issues with Evolution HTML rendering not working recently , as well as malfunctioning of midori and other webkit-based browsers. The bug that started this effort can be found here: https://bugs.funtoo.org/browse/FL-6956 I am currently updating our stages to include the new WebKit, prebuilt in our gnome stage. For those upgrading, the sources of WebKit are 1GB and it takes a long time to compile (typically 20 minutes to an hour) because it is a whole lot of code.
  23. This bug was reported to the bug tracker at https://bugs.funtoo.org/browse/FL-6748 .
  24. 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.
  • Create New...