Hi and welcome to devnet, Did you already follow this pinned thread about accessing the bug report system ? In between, I updated the bug report with your findings but don't hesitate to try again and add more context as needed.

I've added a task for that: https://qt-project.atlassian.net/browse/QTBUG-151640

I’ve run into similar issues with custom macros, and it seems the update tool doesn’t expand them before checking for Q_OBJECT. Maybe defining the macro through the appropriate preprocessor options or using a wrapper that the tool can recognize could help. It would be great to find a solution that avoids having to modify every source file individually.

Unlikely, the internal mechanism is different, and I furthermore cannot reproduce any crash with OP's sample. @Qoissi Please provide more detail - which version of Qt and which version of PyQt? Is the crash due to a Python exception or in native code? Can you provide a stack trace?

@Christian-Ehrlicher , I added below line in main.cpp but nothing changed in Debian 12. QApplication::setStyle(QStyleFactory::create("Fusion")); MainWindow w; Regards, Mucip:)

@VikMorroHun said in blocked: cmake: command not found: In Linux I got more than 6000 hits How did you search to get 6000 hits?

Hi, and welcome! @BRNany said in CMAKE_AUTORCC was removed from the default cmake project?: My question is: WHY ISN'T AUTORCC ENABLED BY DEFAULT? If I create a project using "CMake with Qt 5 compatibility", the AUTORCC is already enabled by default... @SGaist is correct. CMAKE_AUTORCC is discouraged now: https://qt-project.atlassian.net/browse/QTBUG-87643 https://qt-project.atlassian.net/browse/QTBUG-141364 explicity process each .qrc file using qt_add_resources(). The recommended approach in Qt 6 is to NOT have a *.qrc file at all. Instead, add your files directly to qt_add_resources().

Welcome to the forum! It would useful if you can expand on your use case and motivation for running multiple applications under X11 with no window manager at all, not even twm. A minimal reproducible setup would also be required for it to ever progress. It is quite possible that this is the result of a bug in the xcb platform plugin, but it is also quite an unusual setup (Qt can work on X11 without a WM, but it is more intended for kiosk like setups).

Indeed. I filed https://qt-project.atlassian.net/browse/QTBUG-151608 on the matter.

You're welcome! @crazy-stone said in Looking for Qt commercial licensing sales contact in China (Application Development): Do you happen to have more direct contact information for the sales representative in China? I don't have direct contact to a specific sales representative, sorry. Did you try to ring the phone number for Shanghai Sales inquiries? +86 21 51748525 Another option, since you have an evaluation license, is to log into https://account.qt.io/s/support-center and create an "Account" or "Sales" request.

@SamuraiDestroy Qt widget layouts is a dark art. Everything you do in Designer is saved in (fairly) readable XML in the generated .ui file, nothing else. You can look at that to try to figure what is going on, and if you are really stuck you can paste it here and people can tell you what you need so long as they understand what you are trying to achieve.

Hi, Additional info about the 0 byte component: WebAssembly category node (0 bytes) with multithread and singlethread nodes below it was added between the 6.12 development releases and that causes the MaintenanceTool view to not look right if you had previous development release installed. Run "Update components" before "Add or remove components" to fix the "Add or remove..." view. Fresh installs and upcoming releases will not see this issue.

@ziller thank you very much. cd qtcreator SIGNING_IDENTITY=- ./scripts/build.py --src . --build ../build_qtcreator --qt-path ../install_qt --llvm-path ../libclang --no-sbom --no-dmg --no-zip This works. cd build_qtcreator cmake -G Ninja "-DCMAKE_PREFIX_PATH=../install_qt;../libclang" ../qtcreator cmake --build . --parallel cmake --install . --prefix ../install_qtcreator cmake --install . --prefix ../install_qtcreator --component Dependencies This terminates with errors: ERROR: codesign verification error: ERROR: "/Users/valentingorelov/Projects/qt/install_qtcreator/Qt Creator.app: code has no resources but signature indicates they must be present\nIn subcomponent: /Users/valentingorelov/Projects/qt/install_qtcreator/Qt Creator.app/Contents/Frameworks/QtQuick3DXr.framework\n" but the resulting app bundle works on my machine. I suppose the reason may be the documentation which has not been built. A small remark about what I am trying to achieve. I do not need a fully signed relocatable app bundle which can be installed on any machine. I just want to try to develop a small feature for Qt Creator. But this feature depends on Info.plist and will not work if I run Qt Creator from the build directory. If I understand correctly, the idea behind just cmake --install . was to achieve exactly this: non-relocatable app bundle for debug purposes which does not contain dependencies. And it works if I build Qt Creator against the Qt from Homebrew. But when Qt Creator is build against self-built Qt, this approach does not work and I need to build a full-fledged app bundle with all the dependencies. cmake --install . --prefix ../install_qtcreator --component Dependencies step takes a lot of time and it is not convenient for debugging.

Hi and welcome to devnet, AFAICT, this one should be included. Usually the license part of the module documentation gives that information and if a module belongs to a more specific commercial product such as Qt for Automotive it is also stated in the documentation. Since you are a commercial customer don't hesitate to contact the Qt Company directly to clear your doubts. With that said, that module has been deprecated in favor of Qt Graphs that you might want to consider as well.

@Axel-Spoerl Sorry. It looks like the black rectangle isn't a regression, but rather the implementation of dark mode support. In version 6.8, dark mode wasn't applied automatically. If the system color theme is light, both versions look identical. Qt 6.8.3, Dark theme, scale 100%: [image: 71a73ecd-1d25-45ed-8f99-4f2ec5c51524.png] Qt 6.12.0, Light theme, scale 100%: [image: 8b33cb68-132d-4875-abc8-16958c5d9507.png] Interestingly, even at 100% scale, the scrollbar looks a bit jagged in both versions, even though the scrollbar itself is straight. However, Fusion.ScrollBar looks good. Thank You. [image: 31dff5ec-b1ac-45f7-a7c0-780738a887fd.png] Should I close the topic as resolved?