SuSE 9.1: partial sound loss after upgrade to KDE 3.3.2
 

Well, after spending alot of time tinkering after my last KDE update (actually managed to repair everything that broke:D ), I decided to upgrade to KDE3.3.2.

Guess what?... Something broke.:rolleyes:

The current problem is that, although I have sound with video and audio applications, I have no sound within KDE itself (no notifications, startup, logging...nada). This is something I cannot accept, as I have grown quite accustomed to KDE's sounds. They comfort me.;)

Has anyone else had a similar problem? I am completely perplexed by this particular problem, and any suggestions on how to fix would be greatly appreciated.

As I have the same problem - yet unresolved I might add.

Apparently, for some people - logging out of KDE. renaming (or deleting)
your ~/.kde/share/config/knotifyrc file and then logging back into KDE works.

As for others, they just renamed thier entire ~/.kde directory and then
copied back some of thier KDE settings.
(not sure if that just does the same thing as deleting knotifyrc or
if there is something else that needs to changed for them)

Wish I was so lucky
-tw

I'll give those two options a try myself and report back on the results.

EDIT: Just tried both options, no change. Looks like my luck's not any better than your's.:(

Hear is the output from a cat I ran on the arts daemon, at least part with the error. Any ideas?

ALSA lib pcm_hw.c:563:(snd_pcm_hw_start) SNDRV_PCM_IOCTL_START failed: Broken pipe
ALSA lib pcm_hw.c:563:(snd_pcm_hw_start) SNDRV_PCM_IOCTL_START failed: Broken pipe
can't register Arts::MidiManager
There are already artsd objects registered, looking if they are active...
ALSA lib pcm_hw.c:563:(snd_pcm_hw_start) SNDRV_PCM_IOCTL_START failed: Broken pipe

Kde 3.3.2 and sound
 

Update your alsa, alsa-devel and alsa-tools from the packman site or from apt and the problem goes away....or go into kde control center and select OSS as your sound server instead of "auto detect"

No go on that idea either. I already tried the update from packman's site, as well as trying the mods to the sound system.

Any other suggestions?

Arts was the problem. Problem solved.:D

For tw001_tw, and anyone who was experiencing the same sound problem as myself, downgrade to the arts package from version 3.3.1 of KDE. There seems to be a problem with the way arts was chatting with alsa. After changing from the arts-1.3.1 that's packaged with 3.3.2 to the arts-1.3.1 from 3.3.1, full audio is restored.

--a little experimenting never hurt anyone--

Any suggestion where to find the 3.3.1 version of arts-1.3.1? The only thing I see on the ftp site is the arts-1.3.2 dated 12/10 -- i.e. part of the 3.3.2 release.

The KDE mirrors have 3.3.1 for SuSE. Just have a look through one of the ftp servers, and you should find arts-1.3.1. It should solve the problem, but I can't promise anything.(worked on my sys, though)

--darkmatter--

Ah! Didn't think to check the KDE mirrors.

Thanks, I'll give that a shot tonight. Hope they have packages for SuSE 9.2!

I hate replying to my own posts...

Answer: Nope. But I decided to be brave, and grabbed the packages for 9.1:

For anyone else running 9.2 who wants to try the fix, here's what I did:

S.

partial sounds, will this break other programs.
 

Im running suse 9.2 with kde3.3.2 and except for system sounds all is well. I tried to go back to the older pagekage
but it says that i have to uninstall a lot of kde programs that depend on the new kde arts. So if i do what you say will
break my programs? like rythmbox or anything that may have been installed while running the 3.3.2 stuff.

Joey, if you follow the steps I gave above, I don't think it'll break anything. Obviously, YMMV and all that, but I haven't had any problems, nor have I had to reinstall anything.

Still not working
 

Hi I did what you said but still no system sounds. i did however notice that after running the restart command that the last line said:

TiMidity starting in ALSA server mode
Opening sequencer port: 128:0 128:1 128:2 128:3

but it just sit there and didnt do anything so i had to do a Ctrl C to get the prompt again to log out.

Odd indeed.

Unfortunately, I don't know anything about timidity, so I can't give you any direct help there. You might try restarting the computer, just to be sure that everything is actually starting cleanly.

Or if you would rather not do that, try (as root) wait a few seconds, and then do . If you get the same hang after timidity runs, I'd suggest reinstalling timidity -- perhaps it's looking for something specific in the version of alsa you had installed when you installed timidity.

Sorry I can't be of more help than that.

S.