[Solved] Sound problem in Slackware 13 Current KDE 4.3

AuroraZero · 11-22-2009, 04:18 PM

I just upgraded from Slackware 13 to Slackware 13 current. My sound card, which is ATI Technologies Inc IXP SB400 AC'97 Audio Controller (rev 01), Worked perfectly before the upgrade. Now when I boot up I get the message "The audio playback device ATI IXP rev 1 with unknown codec (ATI IXP AC97) does not work. Falling back to.

I have done alsa configure and alsa mixer they both work. Kmix on the other hand does not. When I try to run kmix from a console as root I get <unknown program name>(3886)/: KUniqueApplication: Cannot find the D-Bus session server: "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."

<unknown program name>(3885)/: KUniqueApplication: Pipe closed unexpectedly.

I also have done a little research through the console. An lscpi -v gives me this for the sound card:

00:14.5 Multimedia audio controller: ATI Technologies Inc IXP SB400 AC'97 Audio Controller(rev01)
Subsystem: Hewlett-Packard Company Device 3085
Flags: bus master, 66MHz, slow devsel, latency 64, IRQ17
Memory at b0003400 (32-bit, non-prefetchable) [size=256]
Capabilities: [40] MSI: Enable- Count=1/1 Maskable- 64bit-
Kernel driver in use: ATI IXP AC97 controller
Kernel modules: snd-atiixp

Everything appears normal to me so far. I am stumped here, and have been for almost a week. This is driving me insane. I know they have had some problems with KDE4 and sound but this is ridiculous. The worst part is I have sound but nothing else works.I can not control anything about it.

Any help will appreciated. I do not care if the idea is off the wall throw it out there and I might try it.

wildwizard · 11-22-2009, 04:45 PM

Quote:

Originally Posted by AuroraZero

The audio playback device ATI IXP rev 1 with unknown codec (ATI IXP AC97) does not work. Falling back to.

Failed upgrade.

Have you read the change logs regarding phonon & qt?
Have you checked the packages installed match exactly with what is now in current?
Have you tried removing ~/.kde and restarting kde?

AuroraZero · 11-22-2009, 06:09 PM

I have read those change logs and they did not give me a hint. I also checked the packages twice just to make sure I had it correct. As for the deleting of ~/.kde I just did this and it did nothing but change my theme.

AuroraZero · 11-22-2009, 06:38 PM

Upon further investigation I have found this problem only in user mode. When I log into the root account everything works as it should.

AuroraZero · 11-22-2009, 07:56 PM

I finally solved this problem. As it turned out the owner of the /.dbus/ folder was screwed up. I used chown user:user /home/user/.dbus/ -R to fix it and rebooted. Worked like a charm.

Drakeo · 11-22-2009, 09:41 PM

after your upgraded in current you must also do a slackpkg install-new
let me know if you did that.

AuroraZero · 11-22-2009, 11:49 PM

Yes I did do that.I just think it was a fluke that caused this.

lpallard · 04-20-2010, 06:39 PM

AuroraZero,

I'm glad you got it fixed! However, I have the exact same problem.... I tried to change the owner of .dbus and all recurrent folder/files to my user ID and GID but no success....

I reinstalled alsa and xine (using slackpkg reinstall alsa & xine) but still no success....

I can lauch alsamixer as root, but no effect...

I am using Slack 13 32bit and KDE Version 4.3.1 that I updated from the stock 4.2 or so....

Any clue whats going on?? thats irritating.. no music, no movies, no web media AHH!

Thanks1

rfernandez · 04-20-2010, 06:45 PM

Are you in the "audio" group?

lpallard · 04-20-2010, 07:55 PM

YOU SAVED ME!!!!

I wasnt member of "audio!"..

Thanks!!!

wildwizard · 04-21-2010, 03:36 AM

Should be no need for the audio group.

Perhaps your missing the 'plugdev' group which is responsible for a lot more.

rfernandez · 04-21-2010, 08:09 AM

I really don't know why, but if you login to KDE as root (yes, I've done that before), and login as user after that, you lost the sound privileges. In that case, putting myself on the audio group solved this problem for me.

T3slider · 04-21-2010, 01:30 PM

Quote:

Originally Posted by wildwizard

Should be no need for the audio group.

Perhaps your missing the 'plugdev' group which is responsible for a lot more.

Code:

$ ls -l /dev/audio
crw-rw---- 1 root audio 14, 4 2010-04-21 14:14 /dev/audio
$ ls -l /dev/snd/
total 0
crw-rw---- 1 root audio 116,  0 2010-04-21 10:13 controlC0
crw-rw---- 1 root audio 116,  4 2010-04-21 10:13 hwC0D0
crw-rw---- 1 root audio 116, 24 2010-04-21 10:13 pcmC0D0c
crw-rw---- 1 root audio 116, 16 2010-04-21 10:13 pcmC0D0p
crw-rw---- 1 root audio 116, 25 2010-04-21 10:13 pcmC0D1c
crw-rw---- 1 root audio 116, 17 2010-04-21 10:13 pcmC0D1p
crw-rw---- 1 root audio 116, 26 2010-04-21 10:13 pcmC0D2c
crw-rw---- 1 root audio 116,  1 2010-04-21 14:14 seq
crw-rw---- 1 root audio 116, 33 2010-04-21 10:13 timer
$ ls -l /dev/dsp
crw-rw---- 1 root audio 14, 3 2010-04-21 14:14 /dev/dsp

I would say there most certainly is a reason to put yourself in the audio group.

lpallard · 04-21-2010, 05:27 PM

Quote:

Should be no need for the audio group.

Maybe, but it did it! I dont understand KDE enough to comment, but I thought to let people know that it worked like a charm!!

Alien Bob · 04-21-2010, 05:42 PM

Quote:

Originally Posted by wildwizard

Should be no need for the audio group.

Perhaps your missing the 'plugdev' group which is responsible for a lot more.

In order to use audio hardware your user needs to be in the "audio" group. Especially if you boot your computer to runlevel 4 (graphical login).
When logging in from the console, your user will implicitly be added to the "audio" group (and others - and only for the duration of your console session) in order to be able to use the local hardware peripherals. These enhanced privileges will not always carry through into X-Window, and that's why it is recommended to add your user explicitly.

Eric