I've done quite a bit of searching, here and elsewhere, and just haven't seen anything else quite like this, and it's been ages since I've posted a question around here, so I figure I'm due.
I just bought a brand new Dell XPS m1330 and I'm running Slackware current (from an ISO made on 01/08/2008).
I know, I know. If it's in current, it's probably not stable. Humor me for a moment; I think this issue probably has a relatively simple configuration related solution, I'm just out of ideas as to what it might be.
Everything works great (well, except for the POS on-board Broadcom wired ethernet... but that's another story). Slackware-current as of 01/08/08 was on 18.104.22.168, and KDE 3.5.7. I've spent the better part of yesterday getting things installed, configured, and tweaked to the way I like them. I encountered an odd problem with sound that seems to be common on this laptop, based on my searching, where sound works fine through the headphone jack, but doesn't come out of the speakers.
I resolved this by downloading the latest stable Alsa source and compiled and installed it. Worked perfectly after that.
Since I had everything working, I edited /etc/inittab and switched from runlevel 3 to runlevel 4, using KDM as my login manager.
And then when I log into KDE from the login manager as a non-root user, sound no-worky. It squawks about "device /dev/dsp can't be opened (Permission denied)" or so it claims.
When I try to run "alsamixer" it comes back and says "alsamixer: function snd_ctl_open failed for default: no such device".
So this is clearly permissions related, since it works fine under root... but why should changing runlevel have anything to do with this?
When I switch back to runlevel 3 I can log in as a non-root user and "startx" to fire up KDE and sound works fine.
Any suggestions as to what I permissions should be looking at? It surely couldn't be permissions directly on /dev/dsp, could it?