@arubislander I changed the "chromium.sh" in the exec field to just "chromium". To my knowledge, I'm pretty sure I can just set a command in the Exec field, and the "chromium" command is another way to open chromium. However, upon opening the app from the launcher, nothing happens still.

@lduboeuf I had a look to your link. I can see the following line: framework: ubuntu-sdk-16.04.5 However, your CMakeList.txt file shows: set(CLICK_FRAMEWORK "ubuntu-sdk-20.04") I guess it does not matter since you can build the app. I am struggling with this issue. I installed clickable in my desktop machine (20.04) but want to develop the app for my BQ 4.5 (Xenial, 16.04). Although I have manually changed the lines in the apparmor file from 20.04 to 16.04, { "policy_groups": [], "policy_version": 16.04 } it still complains when I tried to build the click package: - security:policy_version_matches_framework:phonehome.apparmor 16.04 != 20.04 (ubuntu-sdk-20.04.1) http://askubuntu.com/q/686347 The provided link does not consider this ubuntu versions, but I guess 16.04 should be valid. I have consistently introduce set(CLICK_FRAMEWORK "ubuntu-sdk-16.04") in the json file, but without luck. I do not know why clickable insists in 20.04, when none file has this version number typed.

@zezba9000 said in Ubuntu 16.04 BQ Aquaris M10 Mir app dev issues.: I'm not familiar with "Libertine". Does this make it easier to dev on X11? You have more info on this? There is some information on using Libertine containers in the UBports documenten. It can be found by following this link. It is framed in the context of running desktop applications, but it works just as well for commandline applications also.

@Bolly I actually stopped backing up teleports. It doesn't make sense anyway since all data are in the cloud. They were just old backups I did years ago. I think I included everything in the app data folder

@PerlMax said in Custom builder for a library: How can I start a app from the terminal, so that I can see error messages? Running clickable logs should let you see the log messages for your app, if there are any. However, given what you've posted already, it seems you are running a bash script, which runs some other process, which has hit a SIGABRT condition. Perl is not really a supported language for building UT applications, so we'd need to see your code (preferably in a git repository) to be able to help much further. Whatever you are running on the first line of your script is failing. If it is perl, then you might want to also check the system log on your device (/var/log/syslog) for possible apparmor DENIALs.

Here I am with answer to the my own question. RTFM! clickable log command very useful.

Volla X23: ubuntu-sdk-20.04 sysbench --test=cpu --num-threads=2 --cpu-max-prime=20000 run 1924 events per second sysbench --test=cpu --num-threads=2 --cpu-max-prime=20000 run 1927 events per second sysbench --test=cpu --num-threads=8 --cpu-max-prime=20000 run 4222 events per second sysbench --test=memory --num-threads=4 run Total operations: 69640008 (696072.68 per second) 68007.82 MiB transferred (6799.51 MiB/sec) sysbench --test=mutex --num-threads=64 run total time: 4.2907s

@domubpkm Delta chat seems to be an interesting project. Unfortunately, I have not read anything about pop3 support. But thanks a lot!

@arubislander Thank you. Yes, I deleted the app with the UT-Tweak Tool and installed it fresh...I then installed the phone fresh with the installer ( rc & devel ) and installed the app again, same result... I now have a USB stick with me

@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