hick518

How can I find out which installed package satisfies the requirements of a virtual package. For instance, my system has virtual/cron installed. 'equery depgraph virtual/cron' shows this: * Searching for cron in virtual ... * dependency graph for virtual/cron-0 `-- virtual/cron-0 amd64 `-- sys-process/vixie-cron-4.1-r14 (sys-process/vixie-cron) amd64 `-- sys-process/bcron-0.10 (sys-process/bcron) amd64 `-- sys-process/cronie-1.5.0-r1 (sys-process/cronie) amd64 `-- sys-process/dcron-4.5-r1 (sys-process/dcron) amd64 `-- sys-process/fcron-3.2.1-r1 (sys-process/fcron) amd64 [ virtual/cron-0 stats: packages (6), max depth (1) ] * dependency graph for virtual/cron-0-r1 `-- virtual/cron-0-r1 ~amd64 `-- sys-process/cronie-1.5.0-r1 (sys-process/cronie) amd64 `-- sys-process/vixie-cron-4.1-r14 (sys-process/vixie-cron) amd64 `-- sys-process/bcron-0.10 (sys-process/bcron) amd64 `-- sys-process/dcron-4.5-r1 (sys-process/dcron) amd64 `-- sys-process/fcron-3.2.1-r1 (sys-process/fcron) amd64 `-- sys-process/systemd-cron-1.5.4 (sys-process/systemd-cron) amd64 [ virtual/cron-0-r1 stats: packages (7), max depth (1) ] Is there a command that would tell that I have cronie installed, and that is satisfying the requirement of the virtual package? Or do I need to simply go through the above list and check for each package?

A few weeks ago I switched to kits, following the instructions at https://github.com/funtoo/meta-repo. Today I went back to that site and I see the instructions have changed. For instance, the symbolic link is different and several lines have been added near the end of the instructions. What am I supposed to do now? Should I undo what I did a few weeks ago, and follow the new instructions? And is there some method in place to inform me of these changes, so I don't have to get lucky by stumbling across them on the internet?

I have several Funtoo systems, and I use one machine as my build machine. That machine creates binary packages which the other systems are configured to use. The systems all use different video cards, so in make.conf I have: VIDEO_CARDS="intel i915 nouveau radeon r600 vesa" This all worked fine on xorg 1.18.something (I think it was 1.18.4). But after moving to kits, xorg got downgraded to 1.17.4 and I'm having problems. Specifically, xdm is crashing on my system with a radeon video card, because it's trying to load the intel driver. I'm not sure what caused this behavior. To fix it, hopefully temporarily, I've changed make.conf to read: VIDEO_CARDS="nouveau radeon r600 vesa" And then I removed libva-intel-driver and xf86-video-intel. I'm not sure if removing that first package was necessary. After I removed the second one, xdm would start up. How can I fix this? I'd really like to be able to build my xorg packages with the intel drivers included so that my packages work on all my machines, like they used to.

Thanks dhudson. That command seems to give the info I needed.

Thanks pytony. Is that something that needs to be run regularly, or only under certain conditions?

Prior to the introduction of kits, 'equery list --portage-tree <package>' would show me all versions of <package> available, and indicate which version(s) I had installed. Now that I'm using kits, it produces no useful output. Is this a bug? Or is there a new option I can use instead of --portage-tree?

I'd like to know what 'epro update' does as well. I've seen it referenced a few times on this forum. But 'man epro' does not contain any info on the 'update' option. I'm still wading my way through the change to kits, and it's not clear to me if I need to run 'epro update'.

This worked, thanks. And a subsequent 'emerge -auDN @world' worked as well, with no errors. I've seen this before -- sometimes packages fail to upgrade during 'emerge -auDN @world', but the same packages can be upgraded via 'emerge packagename'. Can anybody tell me why?

Actually, I was able to upgrade @world by excluding only xf86-input-evdev. So I am fully updated except for some xorg-related stuff. Any ideas what I should do to update those? Am I going to have to unmerge them all, then emerge them again? (And hope that nothing goes wrong?) # emerge -auDN @world These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild UD ] x11-base/xorg-drivers-1.17 [1.18-r1] [ebuild UD ] x11-base/xorg-server-1.17.4-r2 [1.18.4] USE="nptl%*" [ebuild UD ] x11-drivers/xf86-input-evdev-2.9.2 [2.10.3] [blocks b ] >=x11-drivers/xf86-input-evdev-2.10 (">=x11-drivers/xf86-input-evdev-2.10" is blocking x11-base/xorg-server-1.17.4-r2) Oops! Conflicts have been encountered: >>> x11-drivers/xf86-video-nouveau-1.0.12:0/0::xorg-kit, installed, wants x11-base/xorg-server:0/1.18.4= >>> x11-drivers/xf86-video-vesa-2.3.4:0/0::xorg-kit, installed, wants x11-base/xorg-server:0/1.18.4= >>> x11-drivers/xf86-input-synaptics-1.8.3:0/0::xorg-kit, installed, wants x11-base/xorg-server:0/1.18.4= >>> x11-drivers/xf86-input-keyboard-1.8.1:0/0::xorg-kit, installed, wants x11-base/xorg-server:0/1.18.4= >>> x11-drivers/xf86-input-mouse-1.9.1:0/0::xorg-kit, installed, wants x11-base/xorg-server:0/1.18.4= >>> x11-drivers/xf86-video-vmware-13.1.0:0/0::xorg-kit, installed, wants x11-base/xorg-server:0/1.18.4= My candidates are: >>> x11-base/xorg-server-1.17.4-r2:0/1.17.4::xorg-kit, ebuild scheduled for merge has SLOT 0/1.17.4 >>> x11-base/xorg-server-1.18.4:0/1.18.4::gentoo, installed has SLOT 0/1.18.4 >>> x11-base/xorg-server-1.18.4:0/1.18.4::gentoo, installed, wants >=x11-base/xorg-drivers-1.18 My candidates are: >>> x11-base/xorg-drivers-1.17:0/0::xorg-kit, ebuild scheduled for merge has SLOT 0/0 >>> x11-base/xorg-drivers-1.18-r1:0/0::gentoo, installed has SLOT 0/0 We hope this informational output has been useful in identifying the problem. We are continually working to reduce conflicts. Do not hesitate to report a bug at https://bugs.funtoo.org. Thank you! :)

# emerge -av xorg-server xf86-input-synaptics xf86-video-vesa xf86-input-mouse xf86-video-nouveau xf86-input-keyboard These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild UD ] x11-base/xorg-server-1.17.4-r2:0/1.17.4::xorg-kit [1.18.4:0/1.18.4::gentoo] USE="ipv6 kdrive nptl%* suid udev xephyr xnest xorg -dmx -doc -glamor (-libressl) -minimal (-selinux) -static-libs (-systemd) -tslib -unwind -wayland -xvfb" 5,656 KiB [ebuild R ] x11-drivers/xf86-input-synaptics-1.8.3::xorg-kit [1.8.3::gentoo] 473 KiB [ebuild R ] x11-drivers/xf86-video-vesa-2.3.4::xorg-kit [2.3.4::gentoo] 279 KiB [ebuild R ] x11-drivers/xf86-input-mouse-1.9.1::xorg-kit [1.9.1::gentoo] 341 KiB [ebuild R ] x11-drivers/xf86-video-nouveau-1.0.12::xorg-kit [1.0.12::gentoo] 586 KiB [ebuild R ] x11-drivers/xf86-input-keyboard-1.8.1::xorg-kit [1.8.1::gentoo] 312 KiB [blocks B ] >=x11-drivers/xf86-input-evdev-2.10 (">=x11-drivers/xf86-input-evdev-2.10" is blocking x11-base/xorg-server-1.17.4-r2) Total: 6 packages (1 downgrade, 5 reinstalls), Size of downloads: 7,645 KiB Conflict: 1 block (1 unsatisfied) Oops! Conflicts have been encountered: >>> x11-base/xorg-server, wants xorg-server >>> x11-drivers/xf86-input-evdev-2.10.3:0/0::gentoo, installed, wants >=x11-base/xorg-server-1.18[udev] >>> x11-drivers/xf86-input-evdev-2.10.3:0/0::gentoo, installed, wants x11-base/xorg-server:0/1.18.4= >>> x11-drivers/xf86-video-vmware-13.1.0:0/0::gentoo, installed, wants x11-base/xorg-server:0/1.18.4= My candidates are: >>> x11-base/xorg-server-1.17.4-r2:0/1.17.4::xorg-kit, ebuild scheduled for merge has SLOT 0/1.17.4 >>> x11-base/xorg-server-1.18.4:0/1.18.4::gentoo, installed has SLOT 0/1.18.4 We hope this informational output has been useful in identifying the problem. We are continually working to reduce conflicts. Do not hesitate to report a bug at https://bugs.funtoo.org. Thank you! :) * Error: The above package list contains packages which cannot be * installed at the same time on the same system. x11-drivers/xf86-input-evdev-2.10.3:0/0::gentoo, installed pulled in by x11-drivers/xf86-input-evdev required by x11-base/xorg-drivers-1.18-r1:0/0::gentoo, installed For more information about Blocked Packages, please refer to the following section of the Gentoo Linux x86 Handbook (architecture is irrelevant): https://wiki.gentoo.org/wiki/Handbook:X86/Working/Portage#Blocked_packages

After following the instructions at https://github.com/funtoo/meta-repoI attempted to 'emerge -auDN @world'. It's not going well. I'm getting the following message. Oops! Conflicts have been encountered: >>> x11-drivers/xf86-input-synaptics-1.8.3:0/0::gentoo, installed, wants x11-base/xorg-server:0/1.18.4= >>> x11-drivers/xf86-video-vesa-2.3.4:0/0::gentoo, installed, wants x11-base/xorg-server:0/1.18.4= >>> x11-drivers/xf86-input-mouse-1.9.1:0/0::gentoo, installed, wants x11-base/xorg-server:0/1.18.4= >>> x11-drivers/xf86-video-nouveau-1.0.12:0/0::gentoo, installed, wants x11-base/xorg-server:0/1.18.4= >>> x11-drivers/xf86-input-keyboard-1.8.1:0/0::gentoo, installed, wants x11-base/xorg-server:0/1.18.4= My candidates are: >>> x11-base/xorg-server-1.17.4-r2:0/1.17.4::xorg-kit, ebuild scheduled for merge has SLOT 0/1.17.4 >>> x11-base/xorg-server-1.18.4:0/1.18.4::gentoo, installed has SLOT 0/1.18.4 >>> x11-base/xorg-server-1.18.4:0/1.18.4::gentoo, installed, wants >=x11-base/xorg-drivers-1.18 My candidates are: >>> x11-base/xorg-drivers-1.17:0/0::xorg-kit, ebuild scheduled for merge has SLOT 0/0 >>> x11-base/xorg-drivers-1.18-r1:0/0::gentoo, installed has SLOT 0/0 We hope this informational output has been useful in identifying the problem. We are continually working to reduce conflicts. Do not hesitate to report a bug at https://bugs.funtoo.org. Thank you! :) I'm still a little unclear how kits are supposed to work, so it's possible I've done something wrong. I was running Funtoo stable, and I'd like to minimize my daily updates. So /etc/ego.conf does not have any kits defined.

Thank you. Blocking addthis.com removed it.

Firefox 55.0.3 on Windows, in this particular case. I am running Adblock Plus, but right-clicking the slider does not give me a "block this..." option. I see now that if I make my web browser window wider (wider than I consider comfortable for reading a lot of text), the slider will end up in a border as the text centers itself in the too-wide browser window. If I had to estimate, it requires the web browser to be at least 1000 pixels wide for the slider to uncover the text. I guess I could use that as a workaround, but I'd still really like to know how to hide or remove it.

How can I get rid of the social media slider that appears on all Funtoo web pages? It blocks the text on the left-hand side of the page. I have clicked to "hide" it, but as soon as I scroll the web page down even one line, it pops up again. As an example: http://www.funtoo.org/News:Kits_Are_Go_(And_Ego_Needs_a_Manual_Bump)

Installing mutt 1.7.2-r2 fixed my problem. That version required a change in USE flags. It was also masked on my stable system. /etc/portage/package.use: mail-client/mutt -berkdb -tokyocabinet /etc/portage/package.accept_keywords: =mail-client/mutt-1.7.2-r2 ~amd64 I'm not sure where the problem crept in, but now I'm back in business. Thanks for the help, Cardinal.

I see you've got a different version installed than I do. Just to be clear, the problem is not that mutt fails to connect. It's that it's presenting me with a certificate that I do not recognize and it never did this before. In fact, one time I chose to reject the certificate and it connected me to gmail anyway. But still it asks me to accept or reject the certificate each time I run mutt. I won't have much time for this until next week, but I'll post back any findings. Thanks for your help, Cardinal. mail-client/mutt Available versions: *1.5.23-r7 1.5.24-r2{tbz2} ~1.7.2 ~1.7.2-r1 ~1.7.2-r2 {berkdb crypt debug doc gdbm gnutls gpg +hcache idn imap kerberos libressl lmdb mbox nls nntp notmuch pop qdbm sasl selinux sidebar slang smime smtp ssl tokyocabinet vanilla} Installed versions: 1.5.24-r2{tbz2}(05:15:14 PM 01/31/2017)(berkdb crypt gdbm gpg imap mbox nls sasl smtp ssl tokyocabinet -debug -doc -gnutls -idn -kerberos -libressl -nntp -pop -qdbm -selinux -sidebar -slang -smime) Homepage: http://www.mutt.org/ Description: A small but very powerful text-based mail client

My wifi is working now that I switched to a new access point with 802.11n. It is running DD-WRT. The other two access points I tried (which I could not connect to) were 802.11g. I tried upgrading one of them to DD-WRT and that didn't improve anything. So I think maybe the lack of wireless-N on my original access points was the problem. My wifi card was able to see the 802.11g access points, but would fail to get an IP address or sometimes fail on authentication. My guess is that the wifi card attempted to switch to 802.11n, which the access point couldn't handle. I don't know if this would be a bug in wicd or in the ath10k firmware. If anyone has suggestions of how to troubleshoot this, I will try to figure it out. I will try to connect to other 802.11g access points as the opportunity arises, and will regularly update linux-firmware and wicd to see if I get any improvements.

Turns out it was only working very intermittently. I fixed the problem by getting rid of avahi. Cups browsing worked without it, and it turned out avahi was the source of my troubles. I will post my configuration once I get the chance (I don't have access to the systems in question at the moment).

Cardinal, I checked my Google My Account settings and they match yours. I tried running Mutt as a different user on the same system and I get the same behavior (it asks me to accept or reject a certificate). What command did you run to get the mutt info at the bottom of your post? I tried 'emerge -pv mutt' but that output is slightly different.

Sometime around the beginning of this year, Mutt (my email client) started asking me to accept a certificate when I try to access my gmail account. I have not accepted it yet and have instead been using gmail's web interface. But that's pretty annoying and I want to get Mutt working again. I've tested on a Devuan system and it works normally (like my Funtoo system did until a couple months ago). I'm not sure if it's a bug or a problem with my configuration (which I don't think has changed). Could somebody test their Funtoo system and let me know what you find? 1) Start Mutt: mutt 2) Connect to a mailbox: c 3) Enter the details: imaps://imap.gmail.com:993 On a working system, you should get prompted for a username. But on my broken system, I get the following, at which point I hit Ctrl-C to stop (neither accepting or rejecting the certificate). Any testing or insight into my problem would be appreciated. This certificate belongs to: GeoTrust Global CA Unknown GeoTrust Inc. Unknown Unknown This certificate was issued by: Unknown Unknown Equifax Equifax Secure Certificate Authority Unknown This certificate is valid from May 21 04:00:00 2002 GMT to Aug 21 04:00:00 2018 GMT Fingerprint: 2E7D B2A3 1D0E 3DA4 B25F 49B9 542A 2E1A

Thanks Cardinal. It looks like the guy in the first link is even using the same revision as me, so there is hope. I should have clarified this earlier: iwconfig shows the wifi card, and wicd sees my two access points. But on one access point it fails to get an IP address, and on the other it fails on my security password (and I verified several times that the password is correct). I had considered this to be a sort of half-working wifi card, and I thought the remaining firmware errors were causing the problem. Maybe not, though.

I've installed linux-firmware, which provided many of the firmware files needed for my wifi card, but I've still got some errors in /var/log/messages: Dec 9 15:07:33 acer kernel: [ 13.938036] ath10k_pci 0000:02:00.0: firmware: failed to load ath10k/pre-cal-pci-0000:02:00.0.bin (-2) Dec 9 15:07:33 acer kernel: [ 13.938037] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/pre-cal-pci-0000:02:00.0.bin failed with error -2 Dec 9 15:07:33 acer kernel: [ 13.938047] ath10k_pci 0000:02:00.0: firmware: failed to load ath10k/cal-pci-0000:02:00.0.bin (-2) Dec 9 15:07:33 acer kernel: [ 13.938048] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/cal-pci-0000:02:00.0.bin failed with error -2 equery l linux-firmware * Searching for linux-firmware ... [IP-] [ ] sys-kernel/linux-firmware-99999999:0 I verified that wifi does work with a USB dongle, so I'm pretty sure I don't have a configuration issue with wicd or with my access point. I ran the following two commands and neither produced any output, so it seems that nothing in portage provides the files that /var/log/messages is complaining it can't find. equery belongs pre-cal-pci-0000:02:00.0.bin equery belongs cal-pci-0000:02:00.0.bin Any ideas what could be wrong? Do I just have hardware that's not supported? This is a brand-new laptop. lspci -v 02:00.0 Network controller: Qualcomm Atheros Device 0042 (rev 31) Subsystem: Lite-On Communications Inc Device 08a6 Flags: bus master, fast devsel, latency 0, IRQ 131 Memory at b1000000 (64-bit, non-prefetchable) [size=2M] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable+ Count=1/8 Maskable+ 64bit- Capabilities: [70] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [148] Virtual Channel Capabilities: [168] Device Serial Number 00-00-00-00-00-00-00-00 Capabilities: [178] Latency Tolerance Reporting Capabilities: [180] L1 PM Substates Kernel driver in use: ath10k_pci Kernel modules: ath10k_pci By the way, I am using debian-sources-4.8.7.

I encountered the same issue while using LightDM. I edited this wiki page to include instructions for "needing" dbus: http://www.funtoo.org/Package:Lightdm I don't know if all display managers would require dbus (but now we know there are at least two: GDM and LightDM). So I don't know if this is truly a bug in the xdm init script, or just something that admins need to be aware of when installing these particular display managers. Reading http://www.funtoo.org/Package:OpenRC I see that "need declares a hard dependency - net always needs to be started before this service does" and "use is a soft dependency - if dns, logger or netmount is in this runlevel start it before, but we don't care if it's not in this runlevel." So I think another way for us to solve this problem is to add dbus to our default runlevel. Then xdm wouldn't have to specify 'rc_need="dbus"'. There is an old gentoo bug about this topic as well: https://bugs.gentoo.org/show_bug.cgi?id=390609

Bug is resolved. https://bugs.funtoo.org/browse/FL-3237

This is the first time I've ever used genkernel. I did not supply my own config file, so I assume I used the default one. You are talking about /usr/src/linux/.config, right?