On 22/07/2024 11:16, Hans Verkuil wrote: > On 22/07/2024 10:28, Hans Verkuil wrote: >> On 19/07/2024 23:19, Gregor Jasny wrote: >>> Hello Hans, >>> >>> On 19.07.24 08:19, Hans Verkuil wrote: >>>> Hi Gregor, >>>> >>>> The last v4l-utils release is over half a year ago, and Nicolas would like to >>>> have a new release that includes the new v4l2-tracer utility. >>>> >>>> Do you have time to prepare a new release? >>> >>> I released and tagged 1.28.0. >>> >>> While preparing the updated Debian package I wondered if I could safely switch from Qt5 to Qt6. Do you see any blockers? >> >> Unfortunately, I just tested this and the colors are all wrong with Qt6. >> >> Also, qvidcap dumps core, even with Qt5. > > This I just fixed in commit f09b2c091d90228547433f11f94015b9ecfeff13. > > I believe that this has always been wrong, it just surfaced for the first > time due to other changes. > > Now that qvidcap works again I see that qvidcap produces the correct colors, but qv4l2 > doesn't (that's with Qt6, Qt5 is fine). > > I'll try to find out what the difference is, hopefully it is easy. Another commit fixing a crash: 60e4ac8949f034120c1c1820f210c7f70a85f2d9 This too needs to be backported to the 1.28 branch. Still looking at the openGL issues in qv4l2. Regards, Hans > > Regards, > > Hans > >> >> I'm looking that the core dump issue, but Qt6 support probably needs to be >> disabled until I have time to figure out what is going on with the colors. >> >> I'll keep you updated. >> >> Regards, >> >> Hans >> > >
