@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.

@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 I never had instabilities too. But since the app is unconfined, I understand that users are reluctant to install it just for some logs.

@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 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

@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.

@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 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.

@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...

@domubpkm Ah, sure. arm64

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

@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.

@messayisto and @stanwood When the bug occurs, I can reproduce exactly the issues you descibe. But right now they are all gone here. So something must trigger it.

Could you please try the build from the latest pipeline? When building there was an error with a regex that is used for parsing a file name. Just a shot in the dark. But it can't hurt (hopefully ).

Although part of me expects it to fix it, just to come back later.

Maybe everyone who has that issue, please try to remember what you did before when this happens. Did you import or save a file? Open another file? Is this only with new files or also with existing files? Do you have some content in clipboard...

Just guessing, whatever you do, but maybe you can reproduce it somehow which then would give us a better idea where to start fixing.

@domubpkm I just tested tedit, had the issue with the crash. Then I tried something and installed a new build, now everything is gone again. Even if there are no changes on code side.

I am quite sure its nothing related to OTA7. But I am afraid I have no idea what exactly is the reason for the crashes. They are gone here now. Please try clearing the apps cache and maybe another reboot. Although I am aware that this is no good solution.

@lduboeuf Not sure if I may need to "reset" my lxd images. There might be something wrong there? The debian control is pulled from the repo, right?

@danfro Ok, so far I had to manually install those packages:

libpolkit-agent-1-dev:arm64
gcovr (including lcov)
libtrust-store-dev:arm64
libdeviceinfo-dev:arm64

Although the last one I haven't got installed yet, apt in the shell seems stuck when "setting up snapd". I guess that isn't really needed? can we drop all snaps stuff?

@danfro Ah, forgot the arch.

@lduboeuf said in error while installing lomiri-systems-settings:

sudo apt install libpolkit-agent-1-dev

Hmm. That might be the problem:

Err:16 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 libglib2.0-dev amd64 2.64.6-1~ubuntu20.04.4
  404  Not Found [IP: 2620:2d:4000:1::102 80]
Get:17 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 libpolkit-gobject-1-dev amd64 0.105-26ubuntu1.3 [59.9 kB]
Get:18 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 libpolkit-agent-1-dev amd64 0.105-26ubuntu1.3 [22.2 kB]
Err:3 http://security.ubuntu.com/ubuntu focal-updates/main amd64 uuid-dev amd64 2.34-0.1ubuntu9.3
  404  Not Found [IP: 2620:2d:4000:1::102 80]
Err:4 http://security.ubuntu.com/ubuntu focal-updates/main amd64 libblkid-dev amd64 2.34-0.1ubuntu9.3
  404  Not Found [IP: 2620:2d:4000:1::102 80]
Err:5 http://security.ubuntu.com/ubuntu focal-updates/main amd64 libmount-dev amd64 2.34-0.1ubuntu9.3
  404  Not Found [IP: 2620:2d:4000:1::102 80]

@lduboeuf Can I do that via shell and then exit shell and run crossbuilder again?

@lduboeuf I even grabbed a brand new clone of lomiri-system-settings and tried with that to make sure there is no bug in my local copy.