From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dimakakos Dimos Subject: Re: GNOME: System sound suddenly stopped working and sound controls are disabled Date: Fri, 10 Jan 2020 00:10:45 +0200 Message-ID: <87y2ugcmca.fsf@gmail.com> References: <16f8b8a5f79.e0a3a63359073.4095705770725625338@zoho.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:37642) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ipg0x-0008U6-Ts for help-guix@gnu.org; Thu, 09 Jan 2020 17:10:53 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ipg0w-0005pb-Fn for help-guix@gnu.org; Thu, 09 Jan 2020 17:10:51 -0500 Received: from mail-lf1-x131.google.com ([2a00:1450:4864:20::131]:43937) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1ipg0w-0005gG-4B for help-guix@gnu.org; Thu, 09 Jan 2020 17:10:50 -0500 Received: by mail-lf1-x131.google.com with SMTP id 9so6385363lfq.10 for ; Thu, 09 Jan 2020 14:10:49 -0800 (PST) Received: from localhost ([2a02:214a:8023:0:b804:f8d8:1a42:c24a]) by smtp.gmail.com with ESMTPSA id t9sm33316lfl.51.2020.01.09.14.10.46 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 09 Jan 2020 14:10:47 -0800 (PST) In-reply-to: <16f8b8a5f79.e0a3a63359073.4095705770725625338@zoho.com> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane-mx.org@gnu.org Sender: "Help-Guix" To: help-guix@gnu.org sirgazil writes: > I guix pulled, reconfigured the system and upgraded my profile packages yesterday. After rebooting, I had sound. But today, I logged out, and then logged back in and sound was lost. Additionally, GNOME sound controls look grayed out (https://multimedialib.files.wordpress.com/2020/01/sound-controls-disabled-2020-01-09.png) and turning up the volume there does nothing. > > Anyone else has this problem? I've encountered this problem lately, though it has occured like three times and I haven't pinpointed the issue. It usually happens after a long time of uptime in a gnome session and logging out and back in fixes it. I'll try to provide more info when this happens again.