Summary: | dev-qt/qt-mobility's QtMultimediaKit hangs if built with pulseaudio but PA isn't running | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Georg Rudoy <0xd34df00d> |
Component: | [OLD] Library | Assignee: | Qt Bug Alias <qt> |
Status: | RESOLVED FIXED | ||
Severity: | normal | Keywords: | PATCH, UPSTREAM |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://bugreports.qt-project.org/browse/QTBUG-29742 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
The freeze backtrace.
The proposed patch. |
Description
Georg Rudoy
2014-06-03 16:58:40 UTC
Created attachment 378176 [details]
The freeze backtrace.
Created attachment 378178 [details, diff]
The proposed patch.
Thanks Georg. You should submit the patch upstream via gerrit, otherwise the chances that it'll be accepted are zero. Thanks, I'll try to figure out their patch inclusion process. Meanwhile, is there any chance for the inclusion of this patch in Gentoo tree? (In reply to Georg Rudoy from comment #4) > Meanwhile, is there any chance for the inclusion of this patch in Gentoo > tree? Yes, but give me some time, I'm busy with other things atm. Sure, that wasn't a way to hurry you, but rather a question about patch inclusion policy. For example, Debian doesn't accept patches to packages that weren't included into upstream's VCS. Some other distros also have quite strict reviewing practices. Thanks again. Hi Georg, did you manage to submit the patch upstream via gerrit? (In reply to Davide Pesavento from comment #7) > Hi Georg, did you manage to submit the patch upstream via gerrit? Hi Davide, Not really. I never did that before, and frankly I'm a little bit lazy to clone the whole Qt repo and follow their clumsy submitting policy. Moreover, the resolution and comments in the bug ( https://bugreports.qt-project.org/browse/QTBUG-29742 ) make me think that they're not going to accept anything to QtMobility: > Before Qt 5, QtMultimedia was part of the Qt Mobility project, which is not maintained anymore. As the bug is related to Qt4, I doubt it's worth it. For the record, this is fixed on qtmultimedia's 5.3 branch as of yesterday https://codereview.qt-project.org/87383 Closing wrt comment #9 |