On Wednesday, 15 April 2020 11:48:05 BST Dale wrote:
> Peter Humphrey wrote:
> > Hello list,
> > 
> > After the switch to elogind yesterday, chronyd now won't run. It complains
> > "Could not get user/group of ntp." I remerged chrony with USE=-ntp, but it
> > didn't help. I know that several people here use chrony, so what is your
> > experience?
> > 
> > Secondly, this morning when I started firefox to listen to BBC Radio 3, as
> > usual, I had no sound. Then I remembered that alsa-utils was unmerged
> > during the switch to elogind yesterday, so I remerged it and ran
> > alsamixer to unmute the master. Still no sound.
> > 
> > This box has two sound devices:
> > 
> > # lspci | grep Audio
> > 00:1b.0 Audio device: Intel Corporation C610/X99 series chipset HD Audio
> > Controller (rev 05)
> > 01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere
> > HDMI
> > Audio [Radeon RX 470/480 / 570/580/590]
> > 
> > The first of those is the one I use; the AMD device is part of the VGA
> > card and not used. I'd have to get myself some kind of HDMI cable to
> > split the sound out if I wanted to use it.
> > 
> > Should I assume that firefox is trying to use the AMD device? In that
> > case, how do I redirect it? There's no sound configuration panel under
> > multimedia in KDE system settings; only cddb.
> 
> I use chrony here and haven't ran into that problem, yet.  Give me some
> time tho.  ;-) 

I added version 3.5 to my keywords file and remerged. It now runs fine. It must 
have been failing for some time, because when it did start it reported a time 
error of 14s.

Bug https://bugs.gentoo.org/700094#c9 refers.

> As to the sound problem, I'd try logging out of the GUI, restarting
> elogind or rebooting, and then trying again.  One thing I've noticed
> about elogind, if it or something it depends on triggers the need for a
> restart, it causes some weird problems.  Once restarted, everything
> works as it should.

Still chasing this one. So far I've reverted to last Sunday's backup and I'm 
putting in a few updates at a time to isolate the guilty party. I forgot to 
say before that I don't get the beep from KDE shutting down either.

-- 
Regards,
Peter.




Reply via email to