tedit development and design discussion

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 .

danfro

@domubpkm I never had instabilities too. But since the app is unconfined, I understand that users are reluctant to install it just for some logs.

domubpkm

@danfro said in tedit development and design discussion:

But since the app is unconfined, I understand that users are reluctant to install it just for some logs

Yes. But it can't be otherwise for you who are used to developing .click?

danfro

@stanwood Btw. thanks for your logs. The second last line looks familiar to me. The part Main process exited, code=killed, status=11/SEGV might be a trace.

Just got a broken tedit again. But I don't have this message in Logviewer. Interesting, in terminal I get this message too, but from systemd service, not tedit. So filtering seems to be handled different there. I will have to ask other developers maybe if they have an idea.

domubpkm

@danfro I am not making a cause and effect relationship, I am describing what happened (volla 22 OTA 7) while everything was ok for some time:

installation of Mimi 0.1.3 then crash of Lomiri at the 1st search under duckduckgo.
clear cache config data then uninstall Mimi.
copy data in Tedit with prolonged finger presses: Tedit crashes.
copy data with virtual keyboard: ok.
copy data with prolonged finger presses: ok again.

danfro

@domubpkm Thanks for the report. Sounds like it may be related to clipboard and/or long press copy/past. Although that may not explain why it cashes when swiping. But its something to look into.

domubpkm

@danfro It seems that changing channels (i went from stable to devel) is enough to crash the copy with a long press. Works again without crashing after a copy with the keyboard.

danfro

@domubpkm I will need to investigate the copy/paste functions of the TextArea. That might conflict with system clipboard. But not today, its Christmas. Have a nice time everone and I hope you can spend some days in peace and with friends+family.