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

Bug#740451: [libqtmultimediakit1] libqtmultimediakit1 has a hard dependency on pulse audio



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

Package: libqtmultimediakit1
Version: 1.2.0-3+b1
Severity: normal

After many wasted hours trying to understand how to get ppsspp's Qt
interface to use ALSA, I ironically find it does a very poor job
(whose fault that is I dont know...), but I must report here on my
related findings regardless.

The way libqtmultimediakit1 is built from qtmobility results in a hard
dependency with pulse audio, which is presumably unacceptable as pulse
should not be a requirement to use the very important Qt framework (I
run a pure ALSA system after fleeing the broken pulse as a n00b long
ago). Upstream is flagging this as a packaging issue -
https://bugreports.qt-project.org/browse/QTBUG-29742 - which feels
dubious, but thats why I'm reporting here.

In the qtmobility source, because there is no special platform config
(features/platformconfig) for our environment, when the 'configure'
script is ran it determines what features to include based on what it
can compile at the time (see line 601 onwards). I have the pulse audio
headers installed as other packages depend on them (but I don't use
pulse, and this is fine as I don't expect the presence of these
headers to break unrelated stuff).

When pulse is detected, the audio plugin 'libqtmedia_pulse.so' is
compiled, BUT ALSA SUPPORT ISNT. See 'multimedia/audio/audio.pri' at
the bottom, it literally looks for pulse audio and only if it isn't
enabled, enables ALSA!

The end result is a user with a pure ALSA system running a program
that uses libqtmultimediakit1 and getting a permanent hang when audio
is first used, as libqtmedia_pulse.so cannot cope with no running
pulse audio server  (see previously-mentioned
https://bugreports.qt-project.org/browse/QTBUG-29742 - I don't see why
its acceptable to do this either...).

Please can the pulse audio dependency be clearly marked and
libqtmultimediakit1 be built in an ALSA-supported form separately?

Thanks


- --- System information. ---
Architecture: amd64
Kernel:       Linux 3.12-1-amd64

Debian Release: jessie/sid
  990 testing         security.debian.org
  990 testing         ftp.uk.debian.org
  500 unstable        ignorantguru.github.com
  500 unstable        ftp.uk.debian.org
  500 quodlibet-unstable www.student.tugraz.at
    1 experimental    ftp.uk.debian.org

- --- Package information. ---
Depends                                (Version) | Installed
================================================-+-=============
libasound2                           (>= 1.0.16) |
libc6                                  (>= 2.14) |
libgcc1                             (>= 1:4.1.1) |
libgl1-mesa-glx                                  |
 OR libgl1                                       |
libglib2.0-0                         (>= 2.31.8) |
libgstreamer-plugins-base0.10-0     (>= 0.10.29) |
libgstreamer0.10-0                  (>= 0.10.31) |
libpulse0                            (>= 0.99.1) |
libqt4-network                      (>= 4:4.8.1) |
libqt4-opengl                       (>= 4:4.8.1) |
libqtcore4                          (>= 4:4.8.1) |
libqtgui4                           (>= 4:4.8.1) |
libstdc++6                            (>= 4.1.1) |
libx11-6                                         |
libxext6                                         |
libxml2                              (>= 2.6.27) |
libxv1                                           |


Package's Recommends field is empty.

Suggests             (Version) | Installed
==============================-+-===========
qtmobility-l10n                | 1.2.0-3

- -- 
Libre software on Github: https://github.com/OmegaPhil
FSF member #9442
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Icedove - http://www.enigmail.net/

iQIcBAEBAgAGBQJTEhIFAAoJEBfSPH39wvOPX/UP/0TjA1d6mg1M9b9T3MQgwa4m
Yzts1evFdpM4WQZzc7Agxv8mryMClsI32YwpEYQOJMFYUOIu1NcicbGtLCWQ76dJ
M+BpeJUjyqzj0HONNhxiLxrkDLECXiG2vYFM0GkOoe0Ax7/NDR50pb+eR4HfZyhh
EoW5A0/5F8ezS5v9F8W1cN/2BT2HSQ7sMoSb8OtwxgrWG/az8Edbf0wZE4/od8Gc
/UFyZ3r8kJX9H3fKRCNcDOAQy59YPdatJlzNbPdaQJhkH6jU8IYDxdmGGp/yJrDP
HfjhjG4HodjgcLFv3c6wlvc8G/ci3pk2UVtxKzGRzZx4SvFf6ZxtjxJk8rpg+XhR
OksLWNNcL2oHYGsu/ZNMM52OdlA2X70Kg/vkM4jWLWTyeqV35SU5bzmXdJcFPkws
QozNOpjHpiP7VM4RmoEKXmUo3+P6Vr4CPts5uPpsRrB9KkwaPe9skU38BODZl/Fo
IKhMSso/BqfRCJxBPGKR0/nIDvZtoE8X2+2yFMoXXEOfR7/k12N5OWqgW9/7GozO
ae0dz0fkh5g4dbcoJKohbaotUbdB+ghYjqQQMm2dx1Ma7YTzho3XmXJAHiY1VpHX
d28tKdi1EP0kuaC6LLrp0nNCZiVYsldErjClXpXTN0TNE6smNeQwo112LaX+csm4
ube/63lDw5K1hD1pLQIU
=4MFY
-----END PGP SIGNATURE-----


Reply to: