[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#369292: marked as done (artsd crashes when playing any sound)



Your message dated Sun, 28 May 2006 19:31:26 -0400
with message-id <200605281931.27702.chrsmrtn@debian.org>
and subject line Bug#369292: artsd crashes when playing any sound
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Package: arts
Version: 1.5.3-1
Severity: Grave
Justification: No sound in KDE

Hi,

I'm Ramiro Cano.

Since the last dist-upgrade, artsd always crashes when trying to play
any sound. So, it happens that it begins to open KDE crash windows until
I close the session. The next time I open, it offers me the option of
disable the arts sound system and I only get the error once, I suppose
that when the KDE start sound should be.

The backtrace of the error is:

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/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)
[Thread debugging using libthread_db enabled]
[New Thread -1208502592 (LWP 4789)]
(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)
0xffffe410 in __kernel_vsyscall ()
#0  0xffffe410 in __kernel_vsyscall ()
#1  0x4964c393 in waitpid () from /lib/tls/i686/cmov/libc.so.6
#2  0x080548fe in ?? ()
#3  0x000012c3 in ?? ()
#4  0x00000000 in ?? ()

AFAICT it's not a problem of ALSA sound system, because I tried to play
a sound with mpg123 in a terminal session and it sounds correctly.

Information on package versions:

master@blingdenstone:~$ dpkg -l | grep arts |cut -f 1,3,18-32
- --output-delimiter=' ' -d' '
ii arts               1.5.3-1
ii artsbuilder        3.5.2-2+b2
ii libarts1-akode     3.5.2-2+b2
ii libarts1-audiofile 3.5.2-2+b2
ii libarts1-mpeglib   3.5.2-2+b2
ii libarts1-xine      3.5.2-2+b2
ii libarts1c2a        1.5.3-1
ii libartsc0          1.5.3-1
ii libartsc0-dev      1.5.3-1
master@blingdenstone:~$ dpkg -l | grep kde-core |cut -f 1,3,18-29
- --output-delimiter=' ' -d' '
ii kde-core           47
master@blingdenstone:~$ dpkg -l | grep libc6 |cut -f 1,3,18-35
- --output-delimiter=' ' -d' '
ii libc6              2.3.6-9
ii libc6-dev          2.3.6-9
ii libc6-i686         2.3.6-9
master@blingdenstone:~$ uname -a
Linux blingdenstone 2.6.16 #1 PREEMPT Mon Mar 20 15:35:40 CET 2006 i686
GNU/Linux
master@blingdenstone:~$

Information on hardware:

System: Toshiba Satellite A50-522 laptop
Sound card: Intel 82801DB-ICH4
Chipset: SigmaTel STAC9750,51

I have absolutely no idea about where is the failure, but if I can
provide any information that helps with the bug solving, just let me know.

Thanks a lot for your work and for all the time you spend on it.

Regards,

Ramiro Cano.

- --
+--------------------------+------------+
|            (o_   powered |Death Master|
|(o_   (o_   //\     by    +------------+
|(/)_  (\)_  V_/_ GNU/LiNUX             |
+-------+-------------------------------+
|GPG KEY|   6FAB 9799 C61A A7D2 A409    |
+-------+   8A53 6F6F 3938 AF95 93E1    |
| KeyID: 0xAF9593E1 (¡Verificar firma!) |
+-------+-------------------------------+
|E-MAIL |      EN             PUNTO     |
+-------+      ^^             ^^^^^     |
| death_master ~~   hpn-sec   ~~~~~ net |
| death_master ~~ clubhackers ~~~~~ com |
| death_master ~~ wadalbertia ~~~~~ com |
| death_master ~~ forohxclive ~~~~~ org |
| death.master ~~ telefonica  ~~~~~ net |
+-------+-------------------------------+
|URL    |  http://www.death-master.tk/  |
+-------+-------------------------------+

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQIVAwUBRHobVG9vOTivlZPhAQKPVQ/7BACGpyQMDex8GsDYVJIKRaUGZhh6xFAz
21dV81qvUjmK73Ca6oRGB0O+V0LtfPIEi0vxAJtO3AAgSDsaFcKe1Q65++bAz4IQ
kUdAy6Nn5OMW2L+XhaLBDp5FU/P3G9RIFvfdbFgfHhcsPvx5EFzVuPbz0ev5F7ew
+FaDCGcSbAEEiklp0vQ45WZ95+3GxCRfTNpyDI1Sg1j30DOw5qNKV88HFDOVU5Uo
MyZIi9f+Uj5c696Zcrnmc8dAcNGoH/Gfg8Th/1KXBPaeJEEexm2i9YL76hz70L+E
stRh3MJ+t5cwYJfdFAcuR+Ren2uK+D1l2qxCUkLDLcTik06+xJsqTBGaRHW8qoN3
I2jjSD2a2rf02V02Oiw9SjJwkxo8KianFZGcMd1puZucy+DbmOaVdSBEFPpcJJm3
hqyJzo5eTPMkBNj/seTb5r3HdUc9i0qua+7esITOruamoICdb/5zCfzdJfMXJqRk
rbm/iO8aDJyqyri9Ug179JmkHxc/h9VrojzQ3ZuJyofpezfvERMdgyyb52HS69w+
yDOdHTFWIiWV0cfXFGJrOzTU/1DjMAKZUwj45dOrPCrF5RvDnGtBj9wHRq6+F1cD
Nnbrtm+R4dRpYOZNLCEjZXzutfYJZaSc0gd2STDPPmoc5X8OJ3lfdiAYgCffYYUv
+mlA08cR6pE=
=x0c0
-----END PGP SIGNATURE-----


--- End Message ---
--- Begin Message ---
On Sunday 28 May 2006 18:50, Death Master wrote:
> I have to apologize. I just dist-upgraded and I realized that this
> bug is in fact a bug of the ALSA system, specifically from libasound.
>
> With the upgrade, the bug changed but it's still there. Anyway, I
> know now that arts is NOT the problem.
>
> You can close this thread.

No problem, closed.

Cheers,
Christopher Martin

--- End Message ---

Reply to: