Your message dated Wed, 4 Jun 2014 23:23:04 -0400
with message-id
<CANTw=mnsvk1zvvopxhndxw5tmnmhaxukzoqtqvrzqyvrmtx...@mail.gmail.com>
and subject line Re: [Pkg-chromium-maint] Bug#733932: chromium: Abort on failed
assertion with ALSA playback
has caused the Debian Bug report #733932,
regarding chromium: Abort on failed assertion with ALSA playback
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 [email protected]
immediately.)
--
733932: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733932
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: chromium
Version: 31.0.1650.63-1
Severity: grave
Tags: upstream
Justification: renders package unusable
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
*** Preliminary note: I will NOT submit this bug upstream as I refuse to use
*** a bug tracker for which I need an account with a major spyware provider.
Chromium crashes when playing back audio through plain ALSA. Apparently,
it runs into an assertion that fails, because the code lacks sanity
checks on stuff returned by ALSA library code beforehand.
[26258:26285:0102/124617:ERROR:audio_manager_base.cc(422)] Not implemented
reached in virtual std::string
media::AudioManagerBase::GetDefaultOutputDeviceID()
[26258:26278:0102/124617:ERROR:audio_manager_base.cc(422)] Not implemented
reached in virtual std::string
media::AudioManagerBase::GetDefaultOutputDeviceID()
ALSA lib pcm.c:7986:(snd_pcm_set_params) Unable to get period size for
PLAYBACK: Invalid argument
chromium --password-store=detect: pcm_params.c:170: snd1_pcm_hw_param_get_min:
Assertion !snd_interval_empty(i)' failed.
Aborted
- -- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.11-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/mksh
Versions of packages chromium depends on:
ii chromium-inspector 31.0.1650.57-1
ii gconf-service 3.2.6-1
ii libasound2 1.0.27.2-3
ii libatk1.0-0 2.10.0-2
ii libc6 2.17-97
ii libcairo2 1.12.16-2
ii libcups2 1.6.4-2
ii libdbus-1-3 1.6.18-1
ii libexpat1 2.1.0-4
ii libfontconfig1 2.11.0-2
ii libfreetype6 2.5.1-1
ii libgcc1 1:4.8.2-10
ii libgconf-2-4 3.2.6-1
ii libgcrypt11 1.5.3-2
ii libgdk-pixbuf2.0-0 2.28.2-1
ii libglib2.0-0 2.36.4-1
ii libgnome-keyring0 3.8.0-2
ii libgtk2.0-0 2.24.22-1
ii libjpeg8 8d-1
ii libnspr4 2:4.10.2-1
ii libnss3 2:3.15.3-1
ii libpango-1.0-0 1.36.0-1
ii libpangocairo-1.0-0 1.36.0-1
ii libspeechd2 0.7.1-6.3
ii libspeex1 1.2~rc1.1-1
ii libstdc++6 4.8.2-10
ii libudev1 204-5
ii libx11-6 2:1.6.2-1
ii libxcomposite1 1:0.4.4-1
ii libxdamage1 1:1.1.4-1
ii libxext6 2:1.3.2-1
ii libxfixes3 1:5.0.1-1
ii libxi6 2:1.7.2-1
ii libxml2 2.9.1+dfsg1-3
ii libxrender1 1:0.9.8-1
ii libxslt1.1 1.1.28-2
ii libxss1 1:1.2.2-1
ii libxtst6 2:1.2.2-1
ii xdg-utils 1.1.0~rc1+git20111210-7
chromium recommends no packages.
Versions of packages chromium suggests:
ii chromium-l10n 31.0.1650.63-1
- -- no debconf information
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.15 (GNU/Linux)
iQJOBAEBCAA4BQJSxVMhMRpodHRwczovL3d3dy5kb21pbmlrLWdlb3JnZS5kZS9n
cGctcG9saWN5LnR4dC5hc2MACgkQt5o8FqDE8pbJZhAAlKuNL1gEomaUI5OFHliI
Sj4S5oiy4GOxD0FOr16hITttDw7YsFj11a5pTf7uLzRXVqGAUiTMlwvJmuTxkEJj
pb+2/0WuBNRav7rMrVNkh7aWT+RTjNPVOlAP4Qle8Z7iiCvtF+jVK3EGIE6PJZz3
hHDpQlmylE0zXq39dUiqcqQNu7RAGfe7DX4kcpLoFuQHfItNywHwNIKtHgAR8DB+
1G24N3R7lVPFs0uWdM8ulK3qca1ObBAMNHSfeRftvmoCj3xS6gm3i8oz/Nx2Hjl+
IMx50r6LNYqGgQAOnfHOMtvg+sJOdakhjVFmOh9cZlGd0eJx8CA6uuy71/W5in2l
EUTyMqyuoUXTWbRsmoQk1S67ynP6uzDZHGWVaWaBZ+3POuRHsvEGX+tzVM5MvbXP
HJ2SPztMHUq6Ygp/aDS4aHLwMuwjYs074i1MDgVMK64xx2Kf9BjVmhUDSdHEjNnw
fumN67kXXo9Ox5XJYpqfCyUta9B9dmdawdc5wrI8WP+dRBa9JCow4kUDP6Rtb0nG
l/kwZZYnodi+XmbE/xCCXgxrIbGlH/Rr2GUHFY71PH/D3j/eiSqGBCTOu+d6b12b
wc7LDALl1z7EQyY9l891gGwLCdQUK/qPVuJrtzPZCMEX6HKO9GcCyalIrI6bKMqI
G7Ud5XoGprl0JiLQa7a20UQ=
=Fj1f
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
version: 35.0.1916.114-1
The patch is applied in this version, so this should be fixed now.
Best wishes,
Mike
--- End Message ---
