tedit development and design discussion

danfro

@stanwood No worries. First make sure you get the right artifacts file. Most devices are arm64 (64bit), but some older ones are armhf (32bit). Download that file on your device and extract it in file manager. Then hop into that folder and go builds/aarch64-linux-gnu/app. There you should find a .click file. Click on that, you should be asked to open it with another app. Pick OpenStore there to install it.

domubpkm

@danfro The difficulty is that now we don't even see the artifacts with morph! Could you link the artifact here please ! arm64

danfro

@domubpkm Ah, sure. arm64

Btw. Lionel did already create a fix for gitlab. Should be coming soon.

domubpkm

@danfro Thanks ! No crash (currently) with the artifact. However, with the latest official built, I cleared the cache, and I didn't get any crashes after that too.

danfro

@domubpkm Thanks for testing. Yes, clearing the cache did help before too. I assume when I build the app with clickable, this clears the cache as well. No idea why something in the cache can make the app crash though...

messayisto

@danfro Installed from artifacts, cleared the cache again, app still crashes.

domubpkm

@danfro I don't know anything about it, but couldn't it have something to do with the size of Tedit's cache?

stanwood

@messayisto Same here: Deleting cache + config + data does not help.

danfro

@domubpkm App cache is handled automatically. I don't think there is anything I can do about the size, except maybe clear cache every time tedit is closed.

danfro

@stanwood and @messayisto very strange. Just to be safe, did you also try a reboot?

Could you please check the apps log and see if there is anything in it? All I see is an error about a binding llp in TextInputPopover. But that is also when not crashing, so likely not related.

Hard to track down if not reproducible. But a very annoying bug...

domubpkm

@danfro said in tedit development and design discussion:

maybe clear cache every time tedit is closed.

Why not if it's possible and even if it may not be the whole reason for the bug.
That said everything is ok for me (for now...).

stanwood

@danfro So I shut the device down during the night as I used to, and started up this morning. No change.
Don't know where to find the logs (I'm not keen on installing apps such as "Log Viewer", which can lead to system instabilities).

domubpkm

Lionel did already create a fix for gitlab

Thanks for this !! @lduboeuf . Really needed currently.

messayisto

@danfro https://dpaste.com/ATTBQZVFR
hope that helps

danfro

@messayisto Thanks a lot. Although sadly this doesn't help much. The only error is the "binding loop" one, which I get also without crashes. So not related I assume.

danfro

@stanwood Logs can be pulled via journalctl. To grab the logs for tedit, you can run in terminal

journalctl --user -u lomiri-app-launch--application-click--tedit.danfro_tedit_3.4.0--.service >>tedit.log

stanwood

@danfro Thank you.

I could successfully pair an ADB shell connexion between my smartphone and my PC (Xubuntu 24.04).

If I run

adb shell journalctl

I have thousands and thousands lines in return.

But if I run:

stanwood@stanwood-K53SV:~$ adb shell journalctl --user -u lomiri-app-launch--application-click--tedit.danfro_tedit_3.4.0--.service >>tedit.log
stanwood@stanwood-K53SV:~$

then, as you can see above, I have nothing returning. Sorry I'm really noobs on technical commands and stuffs like that... should I change "user" by "phablet" or something else?

Thank you and sorry once again for my very limited technical knowledge.

danfro

@stanwood No worries, trust me, I started like that some years ago as UT user. We all learn by doing this kind of testing. I had to actually search a while through Logviewers code to retrieve this command.

First a suggestion in case you don't know yet. You can run just adb shell to open a terminal on the device. Then you can run commands as normal. It doesn't need to be adb shell COMMAND. (I find this more convenient)

The full command writes all the log output into a file called tedit.log. That is done by the last part >> tedit.log It kind of forwards output to a file. To see the output on screen just ommit this part and run only

journalctl --user -u lomiri-app-launch--application-click--tedit.danfro_tedit_3.4.0--.service

stanwood

@danfro Got it! I just notice that a log file named "tedit.log" has been created in my home directory on my PC, funny isn't it?
So I could pick it up in my Thunar files manager and copy - paste the information of a sequence below. So here we go:

Dec 02 22:38:15 ubuntu-phablet systemd[2701]: Started lomiri-app-launch--application-click--tedit.danfro_tedit_3.4.0--.service.
Dec 02 22:38:15 ubuntu-phablet aa-exec[18696]: library "eglSubDriverAndroid.so" not found
Dec 02 22:38:15 ubuntu-phablet aa-exec[18696]: Creating a QMirClientScreen now
Dec 02 22:38:19 ubuntu-phablet aa-exec[18696]: file:///usr/lib/aarch64-linux-gnu/qt5/qml/Lomiri/Components/1.3/TextInputPopover.qml:56:9: QML Action: Binding loop detected for property "enabled"
Dec 02 22:38:19 ubuntu-phablet systemd[2701]: lomiri-app-launch--application-click--tedit.danfro_tedit_3.4.0--.service: Main process exited, code=killed, status=11/SEGV
Dec 02 22:38:19 ubuntu-phablet systemd[2701]: lomiri-app-launch--application-click--tedit.danfro_tedit_3.4.0--.service: Failed with result 'signal'.

I can provide you more sequences if you need, although there are not so much differences.

Hope it could help.

domubpkm

@stanwood

@stanwood said in tedit development and design discussion:

I'm not keen on installing apps such as "Log Viewer", which can lead to system instabilities)

https://open-store.io/app/logviewer.ruditimmer is a great click easy to use. I Never had any problems or instabilities with this .click .