Crash induced by HTile rewrite about mirage HOT 10 CLOSED

I have no way to test this, and no idea what could be happening from the trace (except "some property did something")... can you try commenting code in HTile to find what line is causing the issue? If that's not enough, is there a way to test (e.g. VM) Sailfish from an x86 Linux, and can you reproduce the crash in it? If yes, can you write about or link to the steps to start from scratch?

from mirage.

That's right, its hard to reproduce without ARM hardware. As you don't have any pointers, I will try to see what can I dig out from it. Will have to make it easier to debug, so I can change QML on device and see how it works without recompile. Shouldn't be too hard, just will replace QRC path with a regular one, I think. I'll let you know how it goes...

from mirage.

About QRC, you can use the dev flag (qmake mirage.pro CONFIG+=dev) to compile a binary that loads from the filesystem instead.

from mirage.

Turns out that this crash can be fixed by using resources.qrc that is located in the root of source dir and has files referred to as src/... and not ../src. Probably some weird Qt bug or expectation, same goes for Qt 5.14.

Right now hitting something else leading to a crash while typing a message. That has been there bit before as well, but not that frequent.

from mirage.

Looks like 5.14 is behaving better than 5.12 in terms of a crash on typing. But both require resources to be in the source code tree, by the look of it

from mirage.

Sorry for the late response. I'm not sure I understand everything you mentioned about resources.qrc, could you make a branch with the modifications that work for you?

from mirage.

No problem. Can you tell which requirements have changed from previous release, so I can change flatpak scripts accordingly.

from mirage.

For Mirage:

• uvloop removed
• nio 0.12+ required

For matrix-nio:

• attrs removed

from mirage.

attrs seems to be pulled by jsonschema, uvloop gone in the new manifest, nio you updated already. Still have to test THIS issue, let's hope it will disappear with new flatpak manifest - at least one of the versions is not showing it yet on mobile

from mirage.

Closing as I cannot reproduce this anymore using Mirage 0.5.0/flatpak.

from mirage.