Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by cardinal

  1. The php-7.4.11.ebuild src_prepare function has a conditional that is wrong. if use apache2; then eapply "${FILESDIR}/php-iodbc-header-location.patch" || die fi if use iodbc; then eapply "${FILESDIR}/apache.patch" || die fi eapply_user If apache2 use is enabled the apache.patch must be applied to prevent build failure. The workaround is to enable iodbc use , then apache.patch is applied, and php will build successfully. Reference: https://bugs.funtoo.org/browse/FL-7122
  2. emerge --info Read the output to verify python3_6 is not included in the USE flag variables PYTHON_SINGLE_TARGET or PYTHON_TARGETS This is what I have on my system with no python3_6 installed. PYTHON_SINGLE_TARGET="python3_7" PYTHON_TARGETS="python3_7 python2_7" If you see python3_6 then you have set an override for it in /etc/portage/repos.conf or some other location that needs to be removed. After you remove without rebooting ego sync followed by emerge -avuDN @world will trigger a rebuild of any modules that were built against python3_6 to be rebuilt against python3_7 if it's supported. If you have modules only supported by python3_6 you will either remove the modules and python3_6 or leave both installed.
  3. Bug Report: https://bugs.funtoo.org/browse/FL-7460 This is assigned to a contributor to be fixed, but it hasn't been updated for 10 days. Click the bug report link, login to bugs.funtoo.org, upper right under People click Vote for this issue and Start watching this issue.
  4. drobbins removed rust-kit but didn't move all the packages it contained to lang-kit. I created a bug report referencing this forum thread: https://bugs.funtoo.org/browse/FL-7479
  5. Not a bug, portage on my system can see /var/git/meta-repo/kits/rust-kit/virtual/cargo rj@funtoo ~ $ ego query v virtual/cargo virtual/cargo| slot| repo --------------+-----+-------------------- * 1.37.0| 0| rust-kit/1.37-prime rj@funtoo ~ $ ego query v librsvg gnome-base/librsvg| slot| repo -------------------+-----+--------------------- * 2.46.4-r1| 2| gnome-kit/3.36-prime 2.48.4| | gnome-kit/3.36-prime rj@funtoo ~ $ equery g librsvg-2.46.4-r1 | grep cargo [ 1] virtual/cargo-1.37.0 rj@funtoo ~ $ equery g librsvg-2.48.4 | grep cargo [ 1] virtual/cargo-1.37.0
  6. There are at least three possible reasons xauth can't create ~/.Xauthority and xorg-server can't create /tmp/.X0-lock 1. The partition{s} containing /tmp and /home are mounted read-only. 2. The partition{s} containing /tmp and /home have no free space. 3. The permissions are wrong and too restrictive for /tmp and ~/ Footnote: ~/ is an abbreviation for /home/<your regular users name here> you are currently logged into.
  7. Search /var/log/messages and /var/log/sddm.log for error messages related to your problem. Reference: https://bugs.gentoo.org/728550 - sys-libs/pam-1.4.0-r1 breaks kde-plasma/kwallet-pam-5.19.1 auto unlock of wallet during login problem starts with the newer version of pam that is not in funtoo's portage yet.
  8. The partition{s} for the root filesystem / and /home must be mounted read/write, yours appear to be mounted read only. Check /etc/fstab and remove a ro option if it exists. The /etc/fstab for mounting the partition for / on my funtoo install: UUID=8c41a40b-5166-4c6c-9819-0713ffca423d / ext4 noatime 0 1 Funtoo is installed on my system on one partition /dev/sda9 and it is rw rj@funtoo ~ $ mount /dev/sda9 on / type ext4 (rw,noatime)
  9. The problem your having is not a bug but an issue with your install. I am attaching my build log in case it may provide a clue to the origin of the problem on your system. sys-kernel:debian-sources-lts-4.19.132_p1:20200916-235334.log.xz
  10. There is no bug report about the failure to mv/rename all the files in /boot by appending their existing names with -debian-sources or -debian-sources-lts You could either go to the root of the file system and extract the ./boot directory which contains the kernel,initramfs,and SystemMap files from the stage3 tarball or copy them from /var/tmp/portage/sys-kernel/debian-sources-lts-4.19.132_p1/image.
  11. drobbins announced End Of Life on March 1, 2020 for 1.3-release. drobbins removed the libvpx mask from funtoo-cautionary. Now that media-kit/1.4-release/media-libs/libvpx-1.9.0 is unmasked you should be able to install mate after you remove/revert any configurations you made that may cause a block or conflict and set the mate mix-ins. These outputs are from my system: emerge -pv mate emerge --info epro list ego kit
  12. https://bugs.funtoo.org/browse/FL-6561 >=libvpx-1.8.0 globally masked you could disable vpx use flag globally in /etc/portage/make.conf to eliminate any need for libvpx. I need vpx for ffmpeg and it was preventing the x265 update. I comment out the mask which is temporary which allowed the update to proceed. rj@funtoo /var/git/meta-repo/kits/core-kit/profiles/package.mask $ sudo nano funtoo-cautionary # Allow firefox to merge cleanly #>=media-libs/libvpx-1.8 You could also add the libvpx-1.7.0.ebuild from the 1.3-release branch to a local overlay.
  13. Remove MAKEOPTS="-j13" from /etc/portage/make.conf, try building with MAKEOPTS="-j2" I was able to build dev-lang/spidermonkey-60.5.2_p0-r3 on my core2duo system, build log is attached.dev-lang:spidermonkey-60.5.2_p0-r3:20200827-140855.log.xz
  14. Fixed: https://bugs.funtoo.org/browse/FL-7392 Sync and update.
  15. An issue report at bugs.funtoo.org is needed. libffado-2.4.1 pulled in by jack2 with ieee1394 use flag requires libxmlpp-2.40.1 that is designated to slot 2.6 (dev-cpp/libxmlpp:2.6) libxmlpp-3.0.1-r1 the only version available in funtoo is designated to slot 3.0 (SLOT="3.0") A temporary workaround is to disable ieee1394 for jack2
  16. From the most recent entry in the change log which is for 5.0 We replaced the default Window Manager from LxQT to LXDE + openbox
  17. Did you configure openrc to start elogind ? After regular user login, before running startx is the user session listed when you run loginctl ? rj@funtoo ~ $ loginctl SESSION UID USER SEAT TTY 2 1000 rj seat0 tty1 Reference: https://www.funtoo.org/GNOME_First_Steps#A_few_finishing_touches
  18. Configuring Funtoo Scripts instructions begins on https://www.funtoo.org/Networking Using Funtoo Scripts for DHCP
  19. Use https://repology.org/repositories/statistics https://repology.org/repositories/graphs to compare package quantity and package versions between different linux distributions.
  20. The username and password used for forums should work for bugs. Did you 2fa authenticate using your cell phone number with sms ? Try to login here: https://auth.funtoo.org/login, Fixed luit-1.1.1-r1 is masked in xorg-kit/1.20-release. Broken luit-1.1.1 which should be removed is unmasked and located in core-gl-kit/2.0-release. This is why we see the error again from FL-7169 Replacing luit-1.1.1.ebuild in core-gl-kit with luit-1.1.1-r1.ebuild solves the problem. Reference new bug report : https://bugs.funtoo.org/browse/FL-7308
  21. Don't use a subarch that includes CPU_FLAGS that are not supported by the CPU of the target hardware(intel64-silvermont) or compiler(intel64-ivybridge). Reference the Funtoo CPU Guide to find it's subarch, then go to the subarch download page to find it's CPU_FLAGS. Reference intel64-nehalem subarch download page to find it's CPU_FLAGS. The atom(silvermont) cpu and the i5(ivybridge) cpu support all the CPU_FLAGS in the intel64-nehalem subarch. Yes, you could use the intel-nehalem subarch on the i5 to build software for the atom. It would be a problem if you are building to run on an older CPU that doesn't support all the nehalem CPU_FLAGS. If you are only building packages for the atom then use intel64-silvermont on the i5 . Don't use intel64-ivybridge subarch on the i5 to build packages for atom because the atom doesn't have avx. generic_64 : mmx mmxext sse sse2 intel64-nehalem : mmx mmxext popcnt sse sse2 sse3 sse4_1 sse4_2 ssse3 intel64-silvermont: aes mmx mmxext popcnt sse sse2 sse3 sse4_1 sse4_2 ssse3 intel64-ivybridge: aes avx mmx mmxext popcnt sse sse2 sse3 sse4_1 sse4_2 ssse3
  22. 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
  23. Replace /bin/chroot with the output from this command: which chroot
  24. A regular user must be a member of the wheel group to use su. Click the link for instructions on adding the important groups. Reference: Create a Regular User
  25. Log in as the regular user that can't su to root. Type groups and hit Enter. Post the output.
  • Create New...