Qt 6.7 status
* Qt 6.7.1 preparations are still ongoing
* Unfortunately couple of new p0 issues reported. Fixes are in &
dependency update round is ongoing
* The target is to get new packages for testing as soon as possible and
release Qt 6.7.1 Mon 20th of May
Qt 6.8 status
> -Original Message-
> From: Development On Behalf Of
> Sami Varanka via Development
> Sent: Tuesday, May 14, 2024 6:42 PM
> To: development@qt-project.org
> Subject: [Development] QtGraphs final API review
>
> Hi everybody!
> QtGraphs will be out of TP in 6.8, and now we need to do the
On Tuesday 14 May 2024 13:24:12 GMT-7 Ilya Fedin wrote:
> On Tue, 14 May 2024 12:59:29 -0700
>
> Thiago Macieira wrote:
> > Assuming that Canonical did not patch libgdk,
>
> Well, that is a very optimistic assumption:
>
On Tue, 14 May 2024 12:59:29 -0700
Thiago Macieira wrote:
> Assuming that Canonical did not patch libgdk,
Well, that is a very optimistic assumption:
http://archive.ubuntu.com/ubuntu/pool/main/g/gtk+3.0/gtk+3.0_3.24.33-1ubuntu2.1.debian.tar.xz
I see 24 pathes in there.
> this is stuck trying
On Tuesday 14 May 2024 12:30:42 GMT-7 Thiago Macieira wrote:
> Those may be inlines. If I try addr2line, then the frames are:
Using gdb instead of addr2line:
frame 6:
Line 116 of "x11/../../../../../gdk/x11/gdkproperty-x11.c" starts at address
0x773d8
and ends at 0x773eb .
frame 7:
Line
On Tuesday 14 May 2024 12:30:42 GMT-7 Thiago Macieira wrote:
> Those may be inlines. If I try addr2line, then the frames are:
> gdk_x11_atom_to_xatom_for_display at ??:?
> gdk_x11_lookup_xdisplay at ??:?
> gdk_x11_display_broadcast_startup_message at ??:?
> gdk_x11_drag_context_get_type at ??:?
>
On Tuesday 14 May 2024 12:13:29 GMT-7 Thiago Macieira wrote:
> #6 0x7fe3fc6e93d8 in gdk_x11_atom_to_xatom_for_display () at
> /lib/x86_64- linux-gnu/libgdk-3.so.0
773d3: e8 58 7f fb ff call 2f330
773d8: 4c 89 e6mov%r12,%rsi
That would mean
On Tuesday 14 May 2024 11:44:24 GMT-7 Thiago Macieira wrote:
> Think in terms of side-effects. It doesn't care how Qt does it, but the
> side- effect of what we are doing could be important, since we're sharing
> libxcb internal state, the xcb_connection (I think), and the X11 server
> itself.
On Tue, 14 May 2024 11:44:24 -0700
Thiago Macieira wrote:
> On Tuesday 14 May 2024 09:23:50 GMT-7 Ilya Fedin wrote:
> > I fail to imagine how that could be... gtk shouldn't care how Qt
> > gets DPI and especially it shouldn't make it hang on XInternAtom
> > (which makes X server either to get an
On Tuesday 14 May 2024 09:23:50 GMT-7 Ilya Fedin wrote:
> I fail to imagine how that could be... gtk shouldn't care how Qt gets
> DPI and especially it shouldn't make it hang on XInternAtom (which
> makes X server either to get an integer from its internal string-integer
> map or increment the
On Tue, 14 May 2024 09:06:04 -0700
Thiago Macieira wrote:
> On Tuesday 14 May 2024 08:25:14 GMT-7 Ilya Fedin wrote:
> > No, they don't, they only adding re-reading RESOURCE_MANAGER
> > property on the X11 root window once they update.
> >
> > The only thing I can assume is that the order of
On Tuesday 14 May 2024 08:25:14 GMT-7 Ilya Fedin wrote:
> No, they don't, they only adding re-reading RESOURCE_MANAGER property
> on the X11 root window once they update.
>
> The only thing I can assume is that the order of Qt+gtk requests is
> triggering some bug in X server and it hangs... But
On Tue, 14 May 2024 08:09:43 -0700
Thiago Macieira wrote:
> [Re-adding the list]
>
> On Tuesday 14 May 2024 08:02:05 GMT-7 Ilya Fedin wrote:
> > The thing is that I need debug symbols for those system libraries to
> > understand what is going on... Is there no way to get them on the
> > CI?
>
[Re-adding the list]
On Tuesday 14 May 2024 08:02:05 GMT-7 Ilya Fedin wrote:
> The thing is that I need debug symbols for those system libraries to
> understand what is going on... Is there no way to get them on the CI?
I don't think you do. I think you have enough information there: it's trying
On Tuesday 14 May 2024 07:30:01 GMT-7 Ilya Fedin wrote:
> I have a long standing (1.5 years) problem with
> https://codereview.qt-project.org/c/qt/qtbase/+/427313 that the CI
> hangs on so-called "cmptest". Previously the CI just reported that
> timeout has happened and I had no idea what exactly
I have a long standing (1.5 years) problem with
https://codereview.qt-project.org/c/qt/qtbase/+/427313 that the CI
hangs on so-called "cmptest". Previously the CI just reported that
timeout has happened and I had no idea what exactly happened.
Asking reviewers to get a backtrace to see where it
Hi everybody!
QtGraphs will be out of TP in 6.8, and now we need to do the final API review.
This API review commit is created manually as QtGraphs has a too complex
CMakeLists.txt for our API review script. More information can be found at
https://bugreports.qt.io/browse/QTQAINFRA-6317. Here
17 matches
Mail list logo
