public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Peter Humphrey <peter@prh.myzen.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] KDE Plasma sound not working
Date: Thu, 16 Jun 2022 17:20:37 +0100	[thread overview]
Message-ID: <2636502.mvXUDI8C0e@wstn> (raw)
In-Reply-To: <4721078.GXAFRqVoOG@wstn>

On Thursday, 16 June 2022 17:10:38 BST Peter Humphrey wrote:
> On Wednesday, 15 June 2022 17:29:54 BST Julien Roy wrote:
> > On 6/15/22 06:52, Peter Humphrey wrote:
> > > I do something like that by copying a good user account as a basis for
> > > the
> > > next iteration. The problem is just the fineness of granularity that's
> > > needed, now that a coarse grain hasn't helped. Hey-ho. Here we must go
> > > again...
> > 
> > What is certain is that the issue is caused by a file in your home
> > directory, since creating a new user fixes the problem.
> 
> Having spent several hours at this today, I've concluded that the problem is
> caused by the Startpage add-on to Firefox. Specifically, startpage 1.3 and
> Firefox 71.10. Early in the stepwise setting everything up, I started

91.10.

> Firefox, set its typefaces and so on, then installed Startpage. The sound
> system stopped working instantly. I removed Startpage and the sound came
> back. A reboot confirmed that no lasting damage had been done. So, I'm now
> using 'EU Startpage - Unofficial', which seems to working well so far.
> 
> > What may help you to be more specific with this would be to list what
> > files were modified since the last time audio worked; for example, `find
> > $HOME -mtime 0` will show files modified in the last 24 hours
> > 
> > You might want to run this command on .config or .kde directories to see
> > what could have changed, although it's true that it might take a while
> > to pin point it...
> > 
> > Another option, since you mention that you re-created your user multiple
> > times, is to just delete specific folders, reboot, and try audio. Maybe
> > start with .config as that would be the most obvious culprit. If that
> > doesn't work, try .kde (not sure if that folder is in ~/  or ~/.config),
> > then other directories.
> 
> I'll stick with the system I have for the moment, thanks. I'll also report
> the problem to the developers.
> 
> > Also, did you check `dmesg` to see if there are any errors related to
> > the audio device/driver? Try `dmesg --level=err,warn`
> 
> Thanks for your ideas, Julien.


-- 
Regards,
Peter.





  reply	other threads:[~2022-06-16 16:20 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-15  2:00 [gentoo-user] KDE Plasma sound not working Peter Humphrey
2022-06-15  2:21 ` Julien Roy
2022-06-15 10:52   ` Peter Humphrey
2022-06-15 16:29     ` Julien Roy
2022-06-15 17:29       ` Michael
2022-06-16 16:10       ` Peter Humphrey
2022-06-16 16:20         ` Peter Humphrey [this message]
2022-06-17  1:28         ` Julien Roy
2022-06-17  6:35           ` Peter Humphrey
2022-06-17  8:55             ` Michael
2022-06-17 11:19               ` Peter Humphrey
2022-06-17 14:27                 ` Michael
2022-06-17 14:51                   ` Anna “CyberTailor”
2022-06-18 11:53         ` Peter Humphrey
2022-06-18 12:30           ` Julien Roy
2022-06-18 13:51             ` Peter Humphrey
2022-06-15  2:50 ` Julien Roy
2022-06-15 17:42 ` Michael

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=2636502.mvXUDI8C0e@wstn \
    --to=peter@prh.myzen.co.uk \
    --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