From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id C2397158091 for ; Wed, 15 Jun 2022 16:29:59 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 7897EE091F; Wed, 15 Jun 2022 16:29:53 +0000 (UTC) Received: from jroy.ca (jroy.ca [23.29.118.128]) by pigeon.gentoo.org (Postfix) with ESMTP id F30AFE0907 for ; Wed, 15 Jun 2022 16:29:52 +0000 (UTC) Received: from [10.0.0.125] (vpn.jroy.ca [184.161.108.223]) by jroy.ca (Postfix) with ESMTPSA id B0A12259A50 for ; Wed, 15 Jun 2022 12:29:51 -0400 (EDT) Message-ID: <3d342c8a-c8d0-7723-6a8b-221350510c1f@jroy.ca> Date: Wed, 15 Jun 2022 12:29:54 -0400 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.10.0 Subject: Re: [gentoo-user] KDE Plasma sound not working Content-Language: en-US To: gentoo-user@lists.gentoo.org References: <3675527.kQq0lBPeGt@wstn> <4747643.31r3eYUQgx@wstn> From: Julien Roy In-Reply-To: <4747643.31r3eYUQgx@wstn> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Archives-Salt: 8c58e4fb-c37d-485b-a50a-91611e311b3c X-Archives-Hash: 8717bdfaed42381d3f94e57586271c2b 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. 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. Also, did you check `dmesg` to see if there are any errors related to the audio device/driver? Try `dmesg --level=err,warn` Regards, Julien