@ublurk said in QTCreator Error: @lduboeuf it a clickable project and it is launched from the project folder. ok, i see, it fails to recognize the project configuration. You sometimes need to re-run cmake or re-scan the project. Did you answer "Y" to the "Do you want Clickable to setup a QtCreator project for you? [Y/n]: Y" What kind of project it is , QML or cpp ? I've just tried with a "fresh" QML project, and it works the first time. ( clickable 8.0.1 ) But sometimes you need to tune the project, especially if you ran clickable desktop before on the project. In that case a clickable clean should do the trick. Or see Build configuration. Eg. toggle the "initial configuration" then click on "re-configure with initial Parameters" [image: 1709896263499-capture-d-%C3%A9cran-de-2024-03-08-12-10-39.png]

@tera I understand now. It's something quite common to struggle with the makefiles (at least for me) If you follow a simple example with one of the templates provided with clickable it can help you better understand how things are intended. Best of luck with your attempt. When I see people make a single repository to compile for several targets, I feel overwelmed

another solution is to use limavm with ubuntu instance , then install docker on it

@mschmids after deleting some messages in the recycle bin on the email server, older then the dangling messages in dekko2, the later ones are now gone as well.

@AdhithAdhi I've installed it via apt-get install after I switched the file system to read/write. But there is another way to manually install it which could be the better way: https://learn.microsoft.com/en-us/dotnet/core/install/linux-scripted-manual#manual-install

Formally speaking, "Wahoooooooooo!" Many, many thanks to Jami.

Just to add to this. While I have not been able to actually process the QVideoFrame yet (meaning I have not been able to covert properly to QImage as all I have is a black image using the QVideoFrame::map or black image with some distortions using the alternate QOpenGLContext method outlined here - while it all says it is valid and not null :crying_face:), I have discovered that in order to use the OpenGL Context one can create QWindow and use its surface like so: https://github.com/qt/qtmultimedia/blob/5.12/src/plugins/avfoundation/mediaplayer/avfvideoframerenderer.mm#L123 Took me a while to figure out how to use it though as it didn't work for me and was crashing the app right on start when the code was part of a plugin (QObject). Unfortunately I was not able to Google it properly (didn't bump into anything that would say that usage is incorect), however with some luck and a lot of trial and error I found out it works when one creates this in the main.cpp file and then simply replies on the QOpenGLContext::currentContext(). And then considering QVideoFrame::map works on UT as part of the Camera QML object I would presume both methods need to work somehow :(. I am just obviously not doing something properly as it is failing for me as described above ^. https://github.com/qt/qtmultimedia/blob/5.12/src/multimedia/video/qvideoframe.cpp#L1094

@kugiigi yeah, lets call it HUD. that is also costumizable by the user. Its not a perfect solution. But its good enough.

@Moem No for the moment. I don't Know. I don't can install Ubuntu touch In My Redmi 8 because have Android 10 miui 12

@Talkless said in How to pass environment variables (like QT_LOGGING_RULES)?: So if apps are run in container (using clickable desktop), how do I pass environment variables, such as QT_LOGGING_RULES=lomiri.deprecations.debug=true per this suggestion: lomiri.deprecations: At least 1 Ubuntu.* QML type is in use. Ubuntu.* type is deprecated and is provided for compatibility. To print what types are being in use, set "QT_LOGGING_RULES=lomiri.deprecations.debug=true" environment variable. Maybe by adding it to the Exec line of the .desktop file ?

@Aloys many thanks for your work. I published your click file. If you want to change anything on the open store page please ask.

@Ced In the new release, the font size is configurable via settings.

@arubislander Hello, that's all right. I think I know which command is meant by "autoremove". I should have added something else, namely the following, if a package is suggested to be deleted, write it out first and reinstall it. Personally, I have always done it this way. Of course this is a danger for others. But nevertheless, you are absolutely right in this situation. Because a lot depends on the port. The Xiaomi Redmi Note 9 MerlinX port was particularly bad. I learned a lot from Fuseteam there. In this sense, thanks for the feedback. Of course I don't want to destroy any devices! I don't think the device was that good ( MerlinX Port ).

@javperan yup, looks like the template has changed since. Currently, I'd probably change line 360: await serviceWorkerLoader.loadServiceWorker(serviceWorker).catch(e => { to: await serviceWorkerLoader.loadServiceWorker(null).catch(e => { Basically, I'm trying to find the section of the code that checks for the service worker, which is in line 117: loadServiceWorker(settings) { if (settings == null) { // In the future, settings = null -> uninstall service worker? console.debug("Null serviceWorker configuration. Skipping."); return Promise.resolve(); } ... Here you can see it checks if 'settings' is null, and seems to handle it gracefully, so any way you can force it to run through that if statement would work fine.

Unfortunately, what I need is not to append flags, but to remove the existing ones which I can't find any way to do. I can do the following in my main.cpp file: qDebug() << qgetenv("QTWEBENGINE_CHROMIUM_FLAGS"); qputenv("QTWEBENGINE_CHROMIUM_FLAGS", "--anything-i-want"); But the output from the getenv is just "", so I'm not sure where its getting the flags from. The addition of the chromium flag is indeed working, but the final command line shown by chrome://gpu is this: (which includes the --disable-gpu at the end) webglcpptest --anything-i-want --browser-subprocess-path=/usr/lib/x86_64-linux-gnu/qt5/libexec/QtWebEngineProcess --application-name=webglcpptest.red --no-sandbox --enable-threaded-compositing --disable-speech-api --enable-features=AllowContentInitiatedDataUrlNavigations,NetworkServiceInProcess,TracingServiceInProcess --disable-features=MojoVideoCapture,FontSrcLocalMatching,UseSkiaRenderer,DnsOverHttpsUpgrade,ConsolidatedMovementXY,InstalledApp,BackgroundFetch,SmsReceiver,WebPayments,WebUSB,PictureInPicture --disable-gpu It doesn't seem possible to override the existing flag with another, I've tried things like --disable-gpu=false and so on, I've tried finding a way to comment out the rest of the flags, even tried a buffer overflow to get rid of the last flag... So I have to find where the flags are coming from and remove them.