From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - lib 0001305]: some odd conditions cause gnomemeeting to crash on takeoff - they blame libasound
Date: Wed, 3 Aug 2005 08:58:57 +0200 [thread overview]
Message-ID: <32e7bca8ec224db49097923e919fed8b@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1305>
======================================================================
Reported By: zsd
Assigned To:
======================================================================
Project: ALSA - lib
Issue ID: 1305
Category: 1_pcm - digital audio
Reproducibility: always
Severity: major
Priority: normal
Status: new
======================================================================
Date Submitted: 08-03-2005 03:42 CEST
Last Modified: 08-03-2005 08:58 CEST
======================================================================
Summary: some odd conditions cause gnomemeeting to crash on
takeoff - they blame libasound
Description:
Here is what I reported to the gnomemeeting people:
Steps to reproduce the crash:
1. start it
Expected Results:
It should run
How often does this happen?
Every time
Admittedly, this was vague, and I finally tracked it down (see "Steps to
reproduce" below).
But first, here was the gnomemeeting traceback:
Backtrace was generated from '/usr/bin/gnomemeeting'
(no debugging symbols found)...Using host libthread_db library
"/lib/libthread_db.so.1".
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...[Thread debugging using
libthread_db enabled]
[New Thread 16384 (LWP 16377)]
0x41498497 in waitpid () from /lib/libpthread.so.0
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=0 0x41498497 in waitpid
() from /lib/libpthread.so.0
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1 0x400985c4 in
libgnomeui_module_info_get () from
/usr/lib/libgnomeui-2.so.0
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=2 0x41496be5 in
__pthread_sighandler () from /lib/libpthread.so.0
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=3 <signal handler
called>
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=4 0x4183beda in
snd_ctl_close () from /usr/lib/libasound.so.2
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=5 0x41bf9155 in
PSoundChannelALSA::UpdateDictionary ()
from /usr/lib/pwlib/devices/sound/alsa_pwplugin.so
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=6 0x41bf919a in
PSoundChannelALSA::GetDeviceNames ()
from /usr/lib/pwlib/devices/sound/alsa_pwplugin.so
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=7 0x41bf88a5 in
PSoundChannelALSA_GetDeviceNames ()
from /usr/lib/pwlib/devices/sound/alsa_pwplugin.so
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=8 0x41340fea in
PSoundChannel::GetDeviceNames ()
from /usr/lib/libpt_linux_x86_r.so.1.8.3
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=9 0x413411a9 in
PSoundChannel::GetDeviceNames ()
from /usr/lib/libpt_linux_x86_r.so.1.8.3
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=10 0x41341229 in
PSoundChannel::GetDefaultDevice ()
from /usr/lib/libpt_linux_x86_r.so.1.8.3
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=11 0x40fe98fe in
H323EndPoint::H323EndPoint ()
from /usr/lib/libh323_linux_x86_r.so.1.15.2
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=12 0x0807c832 in
GMH323EndPoint::GMH323EndPoint ()
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=13 0x08079852 in
GnomeMeeting::GnomeMeeting ()
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=14 0x080941b2 in main ()
Thread 1 (Thread 16384 (LWP 16377)):
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=0 0x41498497 in waitpid
() from /lib/libpthread.so.0
No symbol table info available.
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1 0x400985c4 in
libgnomeui_module_info_get () from
/usr/lib/libgnomeui-2.so.0
No symbol table info available.
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=2 0x41496be5 in
__pthread_sighandler () from /lib/libpthread.so.0
No symbol table info available.
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=3 <signal handler
called>
No symbol table info available.
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=4 0x4183beda in
snd_ctl_close () from /usr/lib/libasound.so.2
No symbol table info available.
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=5 0x41bf9155 in
PSoundChannelALSA::UpdateDictionary ()
from /usr/lib/pwlib/devices/sound/alsa_pwplugin.so
No symbol table info available.
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=6 0x41bf919a in
PSoundChannelALSA::GetDeviceNames ()
from /usr/lib/pwlib/devices/sound/alsa_pwplugin.so
No symbol table info available.
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=7 0x41bf88a5 in
PSoundChannelALSA_GetDeviceNames ()
from /usr/lib/pwlib/devices/sound/alsa_pwplugin.so
No symbol table info available.
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=8 0x41340fea in
PSoundChannel::GetDeviceNames ()
from /usr/lib/libpt_linux_x86_r.so.1.8.3
No symbol table info available.
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=9 0x413411a9 in
PSoundChannel::GetDeviceNames ()
from /usr/lib/libpt_linux_x86_r.so.1.8.3
No symbol table info available.
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=10 0x41341229 in
PSoundChannel::GetDefaultDevice ()
from /usr/lib/libpt_linux_x86_r.so.1.8.3
No symbol table info available.
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=11 0x40fe98fe in
H323EndPoint::H323EndPoint ()
from /usr/lib/libh323_linux_x86_r.so.1.15.2
No symbol table info available.
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=12 0x0807c832 in
GMH323EndPoint::GMH323EndPoint ()
No symbol table info available.
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=13 0x08079852 in
GnomeMeeting::GnomeMeeting ()
No symbol table info available.
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=14 0x080941b2 in main ()
No symbol table info available.
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=0 0x41498497 in waitpid
() from /lib/libpthread.so.0
======================================================================
----------------------------------------------------------------------
zsd - 08-03-05 04:01
----------------------------------------------------------------------
The following didn't get into the bug report above... here is info on how
to reproduce the bug:
I have discovered a set of conditions which cause this bug to manifest
itself.
First, after submitting the bug report I discovered that gnomemeeting was
working if I used a USB webcam that used the ov511 module and DID NOT have
a
built-in mic. I usually use a Logitech webcam (which uses pwc+pwcx
modules
under 2.4.xx) but which also has a built in mic (which uses the
snd-usb-audio).
Next I discovered that when I created a new user on my computer which was
NOT in
the "audio" group, gnomemeeting did not crash and burn on takeoff when
using the
Logitech web cam. However, the config druid did not register the USB mic
as an
option.
After a lot of searching, I discovered that /dev/snd/pcmC1D0c was missing
(presumably clobbered by udev in a 2.6.1x kernel I use some times) and
that
restoring this file brought the world back to its previous blissful
state.
It is interesting that being in the audio group is a significant
difference
here, because even with the audio devices (/dev/snd/*, /dev/dsp*,
/dev/mixer*,
...) chmod'ed to 666, the user w/o "audio" could run gnomemeeting, while
the
user with "audio" could not.
Obviously, the missing file is a local config problem that was my fault (I
could
gripe about udev, but that's another story), however,
(a) the connection with me being in the audio group is mysterious, and
(b) a more gracefull error message (or actually working regardless) would
be nicer.
----------------------------------------------------------------------
schorpp - 08-03-05 08:58
----------------------------------------------------------------------
i know this backtrace from debian-pre-sarge times a few months ago and also
had some problems with alsa 1.0.8.
use gm >= 1.2.1 and alsa >= 1.0.9 and update your system libs.
Issue History
Date Modified Username Field Change
======================================================================
08-03-05 03:42 zsd New Issue
08-03-05 04:01 zsd Note Added: 0005611
08-03-05 08:58 schorpp Note Added: 0005612
======================================================================
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
next reply other threads:[~2005-08-03 6:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-03 6:58 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-02-28 23:59 [ALSA - lib 0001305]: some odd conditions cause gnomemeeting to crash on takeoff - they blame libasound bugtrack
2005-12-30 22:53 bugtrack
2005-08-03 2:01 bugtrack
2005-08-03 1:42 bugtrack
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=32e7bca8ec224db49097923e919fed8b@bugtrack.alsa-project.org \
--to=bugtrack@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox