sound: startx vs kdm
Dirk van Deun
works in KDE if I start the graphical environment with startx, but
not if I log in via kdm (or xdm for that matter) ?
"Notification from Phonon:
The audio playback device HDA Nvidia (ALC885 Analog) does not work.
Falling back to ."
This does not happen when I start KDE with startx.
Dirk van Deun
--
Ceterum censeo Redmond delendum
Clemens Ladisch
> Has anybody got an idea where to start looking for the cause if sound
> works in KDE if I start the graphical environment with startx, but
> not if I log in via kdm (or xdm for that matter) ?
Probably the permissions on the device nodes in /dev/snd/.
HTH
Clemens
Dirk van Deun
: > works in KDE if I start the graphical environment with startx, but
: > not if I log in via kdm (or xdm for that matter) ?
: Probably the permissions on the device nodes in /dev/snd/.
Turns out that I simply hadn't added myself to the audio group. Still
don't understand why it did work (in the same account) in a session
started with startx then...
Eric Hameleers
> : > Has anybody got an idea where to start looking for the cause if sound
> : > works in KDE if I start the graphical environment with startx, but
> : > not if I log in via kdm (or xdm for that matter) ?
>
> : Probably the permissions on the device nodes in /dev/snd/.
>
> Turns out that I simply hadn't added myself to the audio group. Still
> don't understand why it did work (in the same account) in a session
> started with startx then...
If you logon from the local console, Slackware will automatically add
your account to several hardware peripheral-related groups (like
autio,video, cdrom, plugdev) for the duration of your login session.
If you run startx, you will have automatic full access to your hardware.
When you login through the graphical logon manager, Slackware does not
assume you are doing a local logon per se (just like with a ssh
session, you could be connecting remotely). In this case, you are
expected to add your account to the relevant groups beforehand.
Eric
Logan Rathbone
> If you logon from the local console, Slackware will automatically add
> your account to several hardware peripheral-related groups (like
> autio,video, cdrom, plugdev) for the duration of your login session.
> If you run startx, you will have automatic full access to your hardware.
> When you login through the graphical logon manager, Slackware does not
> assume you are doing a local logon per se (just like with a ssh
> session, you could be connecting remotely). In this case, you are
> expected to add your account to the relevant groups beforehand.
Interesting. How is this handled? What files designate which groups
user accounts with automatically be added to when you logon from the
local console?
Sylvain Robitaille
> What files designate which groups user accounts with automatically be
> added to when you logon from the local console?
See CONSOLE_GROUPS in /etc/login.defs
I would argue that it's incorrect to state that "Slackware" adds the
user to the group when logging in on a console, but not with a display
manager, when in fact it's "login" that sets up the groups. That
Slackware uses this particular login program is relevant, but the
functionality certainly isn't limited to Slackware, since any Linux
distribution using the same login program, suitably configured would do
the same.
The answer to the OP, then, is "because /bin/login adds your user to
groups that permit access to certain hardware, while [kx]dm do not."
--
----------------------------------------------------------------------
Sylvain Robitaille s...@encs.concordia.ca
Systems analyst / AITS Concordia University
Faculty of Engineering and Computer Science Montreal, Quebec, Canada
----------------------------------------------------------------------