public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] supreme annoyances:
Date: Fri, 23 Apr 2021 09:12:56 +0100	[thread overview]
Message-ID: <7903047.T7Z3S40VBb@lenovo.localdomain> (raw)
In-Reply-To: <d0966dd1-ad7b-b130-4728-50b24e21c5a5@verizon.net>

[-- Attachment #1: Type: text/plain, Size: 2443 bytes --]

On Thursday, 22 April 2021 14:42:14 BST Alan Grimes wrote:
> A
> 
> I have to wait during boot while DHCP tries to bring up eth0  (cable is
> plugged into eth1) and then manually turn off eth0 and turn on eth1 each
> time, can't find where this behavior is configured, /etc is a MAZE

Set a desired metric for the interfaces in your /etc/conf.d/net, following 
guidance in /usr/share/doc/netifrc-*/net.example.bz2 to change their 
priorities, or disable with rc-update the interface you have no use for and do 
not want to have it starting up regularly.


> B.
> 
> Everery. Single. Time. I have to run pavucontrol imediately after
> launching X11 and force select the working sound config, it used to
> always work but on this motherboard it refuses to save this working
> setting and forces me to manually do it Every F'ing Time.

Check your user is a member of the audio group.  If you're not using one of 
the desktop profiles (eselect profile list) then also check the ACLs for /dev/
snd/controlC*.

Check the pavucontrol configuration tab and disable the built-in audio profile 
corresponding to the audio card you don't want to use (e.g. HDMI) - if this is 
the setting which you want to change.

Take a look at ~/.config/pulse and tweak manually the settings you need/want 
per user, or for system wide settings walk through /etc/pulse/.

I'm not at a pulse equipped PC at present to dig any deeper, but the above 
should set you on the right path.  This reference page is also useful, in case 
you're missing something in your setup:

https://wiki.gentoo.org/wiki/PulseAudio


> C.
> 
> Now this is a Real Problem, after updating a few days ago, THE GODDAMN
> FONTS DO NOT RENDER, in half of the websites I visit with chromium. Rn
> there is massive wierdness going on with chromium and glibc

Chromium is a beast to compile and have stopped using it.  In the past I had 
come across similar bugs, which were fixed on a subsequent version.  Using 
stable versions minimises such problems, but from what I recall didn't do away 
with hiccups 100% of the time.  Alternative browsers may be the way to go, at 
least temporarily.


> D.
> 
> WTF, I just installed sys-kernel/vanilla-sources-5.11.15, rebooted, ran
> update again, and now it's unavailable, this is like 3 days.. Updating
> kernel sucks because of nvidia drivers. =\

Vanilla sources are not stable, so they'll drop off the tree when a better/
newer minor version shows up.

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      parent reply	other threads:[~2021-04-23  8:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <d0966dd1-ad7b-b130-4728-50b24e21c5a5.ref@verizon.net>
2021-04-22 13:42 ` [gentoo-user] supreme annoyances: Alan Grimes
2021-04-22 15:43   ` Neil Bothwick
2021-04-23  8:12   ` Michael [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7903047.T7Z3S40VBb@lenovo.localdomain \
    --to=confabulate@kintzios.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox