home bbs files messages ]

Forums before death by AOL, social media and spammers... "We can't have nice things"

   alt.os.linux.suse      Suse is actually not that bad      138,051 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 137,560 of 138,051   
   Andrew to JJarcor   
   Re: OpenSUSE 15.4 Audio Problem   
   29 Jul 22 18:58:37   
   
   From: Doug@hyperspace.vogon.gov   
      
   JJarcor wrote:   
   > Am 28.07.22 um 14:13 schrieb Andrew:   
   >> Andrew wrote:   
   >>> (I have posted most of this in a similar form to comp.os.linux.hardware)   
   >>>   
   >>> My PC has been active since 2018, whatever OpenSUSE Leap level was   
   >>> current then was installed, all of the versions since then were   
   >>> loaded in turn.  I had to reinstall Leap 15.3 from scratch once but   
   >>> that was for a totally different reason.  Audio has never been a   
   >>> problem, now it is.   
   >>>   
   >>> Audio no longer works after a boot.  The workaround is to insert the   
   >>> headphone plug and to remove it again *while content is being   
   >>> played*. Pulling and reinserting the loudspeaker plug into the   
   >>> line-out socket works in exactly the same way.   
   >>>   
   >>> According to my Asus A320M-K MoBo description, I have a "Realtek   
   >>> ALC 887-VD2 High Definition Audio CODEC" on board.  The sound module   
   >>> is snd_hda_intel.   
   >>> When I start playing content, the correct modules are duly loaded.   
   >>> No additional modules are loaded once I have applied the workaround.   
   >>>   
   >>> There are various pulseaudio messages in the system logs but I don't   
   >>> know which of those can be considered normal and which indicate a   
   >>> problem.   
   >>> Noticeable in the log of a 15.3 startup was a "Stopping User Manager   
   >>> for UID 465..." (appears to be user "sddm", the SDDM daemon).  This   
   >>> did not appear in the 15.4 log.   
   >>>   
   >>> Something which did appear in the 15.4 log but not in the earlier one   
   >>> was:   
   >>> dbus-daemon[839]: [system] Failed to activate service 'org.bluez':   
   >>> timed out (service_start_timeout=25000ms)   
   >>> kded5[9493]: kf.bluezqt: PendingCall Error: "Failed to activate   
   >>> service 'org.bluez': timed out (service_start_timeout=25000ms)"   
   >>> pulseaudio[10257]: GetManagedObjects() failed:   
   >>> org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible   
   >>> causes include: the remote application did not send a reply, the   
   >>> message bus security policy blocked the reply, the reply timeout   
   >>> expired, or the network connection was broken.   
   >>> PackageKit: daemon quit   
   >>>   
   >>> Does anyone have a clue what is going on here, or how to debug this   
   >>> s***?   
   >>   
   >> To summarise:   
   >> - If I boot my system, sound does not work (cable to speakers at the   
   >> rear) until I insert the headphone cable, and withdraw it again.   
   >> - If I log out and log in again, sound does not work . . .   
   >> - If I put the machine to Sleep and wake it up again, no problems.   
   >>   
   >> Now the fun one, I created a new User and logged into that userid   
   >> after a boot.  Sound works.   
   >>   
   >> Something went wrong with my main user account when I upgraded from   
   >> Leap 15.3 to 15.4.   
   >> This is a pretty much vanilla kde setup.   
   >>   
   >> Which settings do I need to nuke in order to simulate having a new   
   >> user-account?  If this means deleting config files, no problem.   
   >   
   > Well, my approach to solve this would be to make a backup of the _main   
   > user_ home path, best using tar to preserve all meta data and  personell   
   > settings.   
   > As second step I suggest to copy the home path of your second and   
   > working user to use it as the main users.  Then reboot and look what   
   > happens.   
   > May be to copy only the /home/second_user/.config - path into the path   
   > of the main user may help as well.   
   > ___   
   >   
   > Regards   
   >    JJenssen   
      
   I'm considering something along the lines of "mv .config .config.bad"   
   but that is a bit of a last resort.  The .config of the working account   
   has very little in there, the account is only there so I can test stuff   
   like this.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca