sound issue on openSUSE 11.0 Acer Asprire one - solved

Dieter Jurzitza dieter.jurzitza at t-online.de
Sun Feb 8 09:17:11 PST 2009


Dear listmembers,
@Everyone:
thank you for all of your replies, and as Kay says, it should not be 
neccessary to add your user to the group "audio" and ought to be handled by 
hal (according to my knowledge), what obviously does not happen here.

My relating this stuff to the missing cdrom stems from the fact that I did 
never hear of anyone having issues with the sound system on 11.0 and a second 
computer with 11.0 does not behave like this and sound works like a charm. 
But that computer is equipped with a cdrom device. Howerver, this was just 
guessing, I can hardly imagine that different sound drivers would be 
handled differently by hal, so I thought it must be related to the hardware 
in some different regard.

So, at the end I've been putting myself onto the journey to update to the 
latest hal from 11.1. It takes you to upgrade some packages in order to get 
this done, but I can tell that it was helpful, I can access sound now without 
being member of the group audio. Hence something similar should be neccessary 
for Paul Menzel, but I do not know about the details for debian.


@Kay,
well, we've had had this type of discussion regarding the ssh'd user listening 
to the microphone, didn't we :-)))).

And I am sure opinions may differ in this regard - IMHO there are good reasons 
to accept access to the audio subsystem from a ssh'd login and it can be a 
pain to do support work over a remote access if you cannot access devices the 
same way that your customer does.

Though I totally agree that the example you provide with someone listening to 
the microphone should be avoided - but I am sure that can be done without 
totally blocking the audio subsystem (and all other devices ...) from remote. 
Or scanning - what the heck to call it a problem that I can access my scanner 
_device_ from ssh - nonsense! To help my customer from remote I need to be 
able to mirror the problem he is facing by 100%. By blocking this approach 
entirely all remote management gets more difficult.

And I have been attempting to get through the hints on how to make this work 
for ssh'd access anyway, but without success. IMHO hal is a mess with regard 
to configuration, the documentation is - carefully speaking - difficult to 
read and even more difficult to understand.


Thanks again,
take care



Dieter Jurzitza

-- 
-----------------------------------------------------------

                               |
                                \
                 /\_/\           |
                | ~x~ |/-----\   /
                 \   /-       \_/
  ^^__   _        /  _  ____   /
 <°°__ \- \_/     |  |/    |  |
  ||  ||         _| _|    _| _|

if you really want to see the pictures above - use some font
with constant spacing like courier! :-)
-----------------------------------------------------------Am Sonntag, 8. 
Februar 2009 11:30:54 schrieb Kay Sievers:
> 2009/2/8 Paul Menzel <pm.debian at googlemail.com>:
******


More information about the hal mailing list