No QtMultimedia backends found. Only QMediaDevices, QAudioDevice, QSoundEffect, QAudioSink, and QAudioSource are available.
Warning: java.lang.NullPointerException: Attempt to invoke virtual method 'void android.media.AudioManager.registerAudioDeviceCallback(android.media.AudioDeviceCallback, android.os.Handler)' on a null object reference
at org.qtproject.qt.android.multimedia.QtAudioDeviceManager.registerAudioHeadsetStateReceiver(QtAudioDeviceManager.java:65)
at org.qtproject.qt.android.QtNative.startQtApplication(Native Method)
at org.qtproject.qt.android.QtNative$$ExternalSyntheticLambda2.run(Unknown Source:0)
at org.qtproject.qt.android.QtThread$1.run(QtThread.java:25)
at java.lang.Thread.run(Thread.java:1015)
Available cameras:
[]
None:0-->Warning: Failed to initialize QCamera "Not available"
None:0-->Warning: Failed to initialize QMediaCaptureSession "Not available"
None:0-->Warning: Failed to create QVideoSink "Not available"
6 June 2025
Can you file a bug report with the logs and how you were running everything?
https://wiki.qt.io/Qt_for_Python/Reporting_Bugs
java.lang.NullPointerException: Attempt to invoke virtual method 'void org.qtproject.qt.android.multimedia.QtMultimediaUtils$OrientationListener.enable()' on a null object reference
at org.qtproject.qt.android.multimedia.QtMultimediaUtils.enableOrientationListener(QtMultimediaUtils.java:62)
at org.qtproject.qt.android.QtNative.startQtApplication(Native Method)
at org.qtproject.qt.android.QtNative$$ExternalSyntheticLambda2.run(Unknown Source:0)
at org.qtproject.qt.android.QtThread$1.run(QtThread.java:25)
at java.lang.Thread.run(Thread.java:1015)
i have create a bug report https://bugreports.qt.io/browse/PYSIDE-3116
rainzeeasyncio is cursed😇
i am not very familiar with python. but seem like python has too many ways to do async things, which against what python's "There should be one-- and preferably only one --obvious way to do it."
Yunhe Guoi am not very familiar with python. but seem like python has too many ways to do async things, which against what python's "There should be one-- and preferably only one --obvious way to do it."
Python has one very pythonic and unique way to do async things. That is implemented in Python very well. The problem comes from Python extensions like PySide, which have to play well with both worlds. Qt has a very different event loop than Python's, and you can either ignore one or try to bend over and marry the two worlds. And that does not have a unique solution but depends on design considerations and expected scope of the solution. And is really hard to get right.
Christian Tismer-SperlingPython has one very pythonic and unique way to do async things. That is implemented in Python very well. The problem comes from Python extensions like PySide, which have to play well with both worlds. Qt has a very different event loop than Python's, and you can either ignore one or try to bend ove
That's also true for lifetime/ownership management 😅
AdrianIf you have questions about QtAsyncio, I can do my best to try to answer them.
The biggest question is, why did we leave a half-finished code at that time? Was it because we encountered challenges in development, or was it because we simply ran out of time?
For a long time, I’ve believed that the development of the QtAsyncIO module is the most important thing for Qt for Python. As I discussed with this gentleman @ctismer before, we both agreed that it would be a milestone in truly improving the development experience of Qt for Python. Unfortunately, it seems that apart from you and him, the rest of the team doesn’t seem very interested in it.
@adrianghc Do you think there are any smarter solutions besides the current design? Maybe it can be implemented very simply, is it possible?
rainzee@adrianghc Do you think there are any smarter solutions besides the current design? Maybe it can be implemented very simply, is it possible?
I'm sure I don't have the best possible implementation, but I don't think it can be done fundamentally simpler, no.
rainzeeFor a long time, I’ve believed that the development of the QtAsyncIO module is the most important thing for Qt for Python. As I discussed with this gentleman @ctismer before, we both agreed that it would be a milestone in truly improving the development experience of Qt for Python. Unfortunately, it
This is very nice to read, because when I was working on it, I had no clue if anybody would ever use or care about it. 😄
AdrianThis is very nice to read, because when I was working on it, I had no clue if anybody would ever use or care about it. 😄
I believe anyone who has truly used PySide for programming has been tormented by the boilerplate code for asynchronous signal operations, to the point of praying to God, “Adrian, come back!”
There has always been interest, it's only about availability. There are many ideas that are not developed further because of not having enough people. I really hope you don't expect this team is huge :) besides Christian and myself, there are 3 other people, and one of them doesn't even have time due to another project.
rainzeeFor a long time, I’ve believed that the development of the QtAsyncIO module is the most important thing for Qt for Python. As I discussed with this gentleman @ctismer before, we both agreed that it would be a milestone in truly improving the development experience of Qt for Python. Unfortunately, it
It's also quite possible that people actually had to work to make a living, and didn't have the time for it.
Cristián 🥑From the two remaining btw, the task are: type hints, ios support, qt python scripting (to be released soon), adapting the api to latest qt developments, the tooling, the development of shiboken, and our build system
The improvements to PySide's stub files are fantastic and have significantly enhanced the development experience. With each new release, it just keeps getting better. However, in my personal view, the priority for iOS might not be that high. Python has become increasingly popular over the years, especially due to machine learning. Many environments are difficult to set up in C++, but they are very straightforward in Python. I think Qt has provided the most powerful GUI framework support in this process. But now, because of the cumbersome boilerplate code and poor development experience, I see many people complaining about the lack of support for asynchronous operations.
Cristián 🥑And please keep filing issues. That will help a lot of someone starts working on it in the future
Ссылка
click to show
click to show
I will. I have submitted many issues and received very prompt responses. I am also a core developer of Flunet Design https://github.com/zhiyiYo/PyQt-Fluent-Widgets/tree/PySide6 (Because of the mistake, our commits is gone.)and many other component libraries in the PySide community. I hope PySide will get better and better.
rainzeeI will. I have submitted many issues and received very prompt responses. I am also a core developer of Flunet Design https://github.com/zhiyiYo/PyQt-Fluent-Widgets/tree/PySide6 (Because of the mistake, our commits is gone.)and many other component libraries in the PySide community. I hope PySide wil
This is really cool!