Bug#609441: Opened additional bugs for each ALSA problem

2011-02-19 Thread Karsten Malcher
Because this bug is assigned to phonon by the ALSA-Team now, i have opened bugs in ALSA for the ALSA-problems for each 
soundchip:


http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=614074
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=614076
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=614079


In the time between i tried to manually edit the /usr/share/alsa/alsa.conf
The errors changed when i try to play a sound with aplay, but it does not work 
up to now.

~$ aplay /usr/lib/openoffice/basis3.2/share/gallery/sounds/drama.wav
ALSA lib confmisc.c:768:(parse_card) cannot find card '0'
ALSA lib conf.c:4170:(_snd_config_evaluate) function snd_func_card_driver returned error: Datei oder Verzeichnis nicht 
gefunden
ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings 

ALSA lib conf.c:4170:(_snd_config_evaluate) function snd_func_concat returned error: Datei oder Verzeichnis nicht 
gefunden
ALSA lib confmisc.c:1251:(snd_func_refer) error evaluating name 

ALSA lib conf.c:4170:(_snd_config_evaluate) function snd_func_refer returned error: Datei oder Verzeichnis nicht 
gefunden
ALSA lib conf.c:4649:(snd_config_expand) Evaluate error: Datei oder Verzeichnis nicht gefunden 


ALSA lib pcm.c:2190:(snd_pcm_open_noupdate) Unknown PCM default
aplay: main:654: Fehler beim Öffnen des Gerätes: Datei oder Verzeichnis nicht 
gefunden


I think the tip from the ALSA-Team is correct.
It is just a problem in the ALSA-configuration.
But i don't know how to define a pcm.!default for phonon which is designed for a 
default:card=Intel?

Something have been mixed up by the ALSA-Team!
You can see it because the configuration is something to run with pulseaudio, but pulseaudio is not installed in the 
standard installation. And i don't want to use pulseaudio.

But there are libraries for pulseaudio installed:

~$ dpkg -l | grep pulse
ii  libpulse-mainloop-glib0  0.9.21-3+b1   
PulseAudio client libraries (glib support)
ii  libpulse00.9.21-3+b1   
PulseAudio client libraries
ii  vlc-plugin-pulse 1.1.3-1squeeze2   
PulseAudio plugin for VLC

When you have a look at the dependencies for libpulse0, pulseaudio should be 
installed, but it isn't:
Dependencies:
0.9.21-3+b1 - libasyncns0 (0 (null)) libc6 (2 2.4) libcap2 (2 2.10) libdbus-1-3 (2 1.1.1) libgdbm3 (2 1.8.3) libice6 (2 
1:1.0.0) libsm6 (0 (null)) libsndfile1 (2 1.0.20) libwrap0 (2 7.6-4~) libx11-6 (0 (null)) libxtst6 (0 (null)) pulseaudio 
(0 (null)) pavucontrol (3 0.9.8)



Where and how is the alsa.conf generated?
What is going wrong in the generated configuration?

This questions must be answered to solve the problems.

Best regards
Karsten




--
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4d5fdfd4.8000...@dct.mine.nu



Re: Bug#609441: Opened additional bugs for each ALSA problem

2011-02-19 Thread Lisandro Damián Nicanor Pérez Meyer
On Saturday 19 February 2011 12:20:52 Karsten Malcher wrote:
 Because this bug is assigned to phonon by the ALSA-Team now, 

Seeing your reply in [0], it's seems it's not a phonon problem. 

[0] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=609441#110

Elimar or someone else of the alsa team, is there anything I can do to help 
you to check if it's a phonon problem or not?

[snip]

 When you have a look at the dependencies for libpulse0, pulseaudio should
 be installed, but it isn't: Dependencies:
 0.9.21-3+b1 - libasyncns0 (0 (null)) libc6 (2 2.4) libcap2 (2 2.10)
 libdbus-1-3 (2 1.1.1) libgdbm3 (2 1.8.3) libice6 (2 1:1.0.0) libsm6 (0
 (null)) libsndfile1 (2 1.0.20) libwrap0 (2 7.6-4~) libx11-6 (0 (null))
 libxtst6 (0 (null)) pulseaudio (0 (null)) pavucontrol (3 0.9.8)

Having pulse libs installed is normal, even if you don't have pulseaudio. Or 
at least that's what I have in all my sistems and I have sound ;-)

 Where and how is the alsa.conf generated?

See http://www.alsa-project.org/main/index.php/Asoundrc and 
http://alsa.opensrc.org/.asoundrc.

 What is going wrong in the generated configuration?

My experience tells me that you normally don't have an alsa.conf except if you 
have more than one card or want to do something special. But the people of the 
ALSA team are far more experienced than me in this, so believe them if they 
say the contrary ;-)

Kinds regards, Lisandro.

-- 
2: Windows con las funciones que realiza se clasifica como:
* Un bug
Damian Nadales
http://mx.grulic.org.ar/lurker/message/20080307.141449.a70fb2fc.es.html

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.


Bug#609441: Opened additional bugs for each ALSA problem

2011-02-19 Thread Elimar Riesebieter
* Lisandro Damián Nicanor Pérez Meyer [110219 13:10 -0300]:
 On Saturday 19 February 2011 12:20:52 Karsten Malcher wrote:
  Because this bug is assigned to phonon by the ALSA-Team now, 
 
 Seeing your reply in [0], it's seems it's not a phonon problem. 
 
 [0] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=609441#110
 
 Elimar or someone else of the alsa team, is there anything I can do to help 
 you to check if it's a phonon problem or not?

See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=614076#10

Elimar

-- 
  Never make anything simple and efficient when a way 
  can be found to make it complex and wonderful ;-)


signature.asc
Description: Digital signature


Bug#261150: marked as done (default-x-display-manager asked at inflated priority)

2011-02-19 Thread Debian Bug Tracking System
Your message dated Sat, 19 Feb 2011 18:09:22 +
with message-id e1pqrfc-00019f...@franck.debian.org
and subject line Bug#613491: Removed package(s) from unstable
has caused the Debian Bug report #261150,
regarding default-x-display-manager asked at inflated priority
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
261150: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=261150
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: xdm,gdm,kdm
Severity: normal

xdm, gdm, and kde all ask the shared/default-x-display-manager at high
priority. Debconf policy is that high priority is for items that don't
have a reasonable default. I think that as long as any of xdm, gdm, or
kdm is the default, that qualifies as a reaonable default display
manager; each of them is usable. If there's some alternatives-style 
ranking going on to rank more usable display managers higher and make
them more likely to be the default, that's even better.

Anyway, right now an install of debian with gdm and kdm asks which to
use, even at high priority, and I think that's an unnecessary question
to ask for a high priority install.

-- 
see shy jo

-- 
see shy jo


signature.asc
Description: Digital signature
---End Message---
---BeginMessage---
Version: 2.20.11-4+rm

Dear submitter,

as the package gdm has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see http://bugs.debian.org/613491

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@debian.org.

Debian distribution maintenance software
pp.
Alexander Reichle-Schmehl (the ftpmaster behind the curtain)

---End Message---


Bug#609441: Opened additional bugs for each ALSA problem

2011-02-19 Thread Karsten Malcher

Hi Lisandro,



Seeing your reply in [0], it's seems it's not a phonon problem.
   


Yes - that's saying everyone who has proved this bug,
from the ALSA-Team and the father of phonon.

But the Debian-Team has pushed it back to phonon.



Having pulse libs installed is normal, even if you don't have pulseaudio. Or
at least that's what I have in all my sistems and I have sound ;-)
   


Congratulations that you have sound! :-)

I only have correct sound on 1 of 6 PC's i have installed Squeeze.
And you can read many of similiar problems in the forums of Debian and 
Ubuntu.

So this problem should be fixed ...

   

Where and how is the alsa.conf generated?
 

Seehttp://www.alsa-project.org/main/index.php/Asoundrc  and
http://alsa.opensrc.org/.asoundrc.
   


That's interesting.
But when i rename the alsa.conf to alsa.conf.bak and try to restart 
ALSA, then ALSA is crying for it:


~$ /etc/init.d/alsa-utils restart
Shutting down ALSA...warning: 'alsactl store' failed with error message 
'ALSA lib conf.c:3617:(snd_config_update_r) Cannot access file 
/usr/share/alsa/alsa.conf

ALSA lib control.c:882:(snd_ctl_open_noupdate) Invalid CTL hw:1
alsactl: get_controls:552: snd_ctl_open error: No such file or 
directory'...failed.
Setting up ALSA...warning: 'alsactl restore' failed with error message 
'ALSA lib conf.c:3617:(snd_config_update_r) Cannot access file 
/usr/share/alsa/alsa.conf

ALSA lib control.c:882:(snd_ctl_open_noupdate) Invalid CTL hw:1
alsactl: set_controls:1409: snd_ctl_open error: No such file or directory
ALSA lib conf.c:3617:(snd_config_update_r) Cannot access file 
/usr/share/alsa/alsa.conf

ALSA lib control.c:882:(snd_ctl_open_noupdate) Invalid CTL hw:1
ALSA lib conf.c:3617:(snd_config_update_r) Cannot access file 
/usr/share/alsa/alsa.conf

ALSA lib control.c:882:(snd_ctl_open_noupdate) Invalid CTL hw:1
alsactl: set_controls:1409: snd_ctl_open error: No such file or 
directory'...ALSA lib conf.c:3617:(snd_config_update_r) Cannot access 
file /usr/share/alsa/alsa.conf

ALSA lib control.c:882:(snd_ctl_open_noupdate) Invalid CTL hw:1
amixer: Mixer attach hw:1 error: No such file or directory
ALSA lib conf.c:3617:(snd_config_update_r) Cannot access file 
/usr/share/alsa/alsa.conf

ALSA lib control.c:882:(snd_ctl_open_noupdate) Invalid CTL hw:1
amixer: Mixer attach hw:1 error: No such file or directory
ALSA lib conf.c:3617:(snd_config_update_r) Cannot access file 
/usr/share/alsa/alsa.conf

ALSA lib control.c:882:(snd_ctl_open_noupdate) Invalid CTL hw:1

   

What is going wrong in the generated configuration?
 

My experience tells me that you normally don't have an alsa.conf except if you
have more than one card or want to do something special. But the people of the
   


Why is the alsa.conf existent after a fresh installation of Squeeze with 
only onboard-sound?



ALSA team are far more experienced than me in this, so believe them if they
say the contrary ;-)
   


I have posted the response of the ALSA-Team in the bug report above.


Kinds regards, Lisandro.

   

Regards
Karsten



--
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4d600f5e.8050...@dct.mine.nu



Processed: reopening 261150

2011-02-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 reopen 261150
Bug #261150 {Done: Debian FTP Masters ftpmas...@ftp-master.debian.org} 
[xdm,gdm,kdm] default-x-display-manager asked at inflated priority
'reopen' may be inappropriate when a bug has been closed with a version;
you may need to use 'found' to remove fixed versions.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
261150: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=261150
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.129814297731384.transcr...@bugs.debian.org



Re: Bug#609441: Opened additional bugs for each ALSA problem

2011-02-19 Thread Elimar Riesebieter
* Karsten Malcher [110219 19:43 +0100]:
[...]
 Where and how is the alsa.conf generated?
 Seehttp://www.alsa-project.org/main/index.php/Asoundrc  and
 http://alsa.opensrc.org/.asoundrc.
 
 That's interesting.
 But when i rename the alsa.conf to alsa.conf.bak and try to restart ALSA,
 then ALSA is crying for it:

Be care ful deleting system files is /usr/share/.
/usr/share/alsa/alsa.conf is installed unpatched as provided from
upstream.

Elimar

-- 
  You cannot propel yourself forward by
  patting yourself on the back.


signature.asc
Description: Digital signature


Bug#609441: Opened additional bugs for each ALSA problem

2011-02-19 Thread Karsten Malcher

Am 19.02.2011 22:25, schrieb Elimar Riesebieter:


Be care ful deleting system files is /usr/share/.
   


Of course - i just renamed it temporary.


/usr/share/alsa/alsa.conf is installed unpatched as provided from
upstream.
   


It is just coming as original deployed from ALSA?
Then it is really an (internal) ALSA problem.
Besides - my bug at ALSA is still open.

I assumed it is created somehow at the installation.
When you plugin a new sound hardware (like a webcam with sound), then 
KDE is automatically doing something with the configuration so you can 
use it.
What part of KDE is activ here - it can't be phonon because it is just 
an API or not?


And there is also the Jack Audio Connection Kit existant.
Can it be used to solve this problems here?
Must phonon be the standard (default) Sound-API for KDE?


Elimar

   


Karsten



--
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4d604a13.8090...@dct.mine.nu