Cutter-v2.3.3-Linux-x86_64.AppImage crashed

[qux-bbb]

Cutter-v2.3.3-Linux-x86_64.AppImage crashed

[karliss]

@djwesty

That's to be expected if you are still using the same old buggy version you will get the same old bugs. So unless you are using a dev build you will have to wait until next patch release to get a version with the fix.

I hope this won't discourage you from making comments in future, just a little advice for doing it even better helping keepi issue tracker organized.

In general "same here" type comments for an issue are useful only in few situations:

• if they provide some new additional information
• issue is in early unconfirmed state, it's unclear what platforms or versions are affected or attempts to reproduce it have been successful

Once the issues has been reproduced by developers or even patched (as can be seen in comments above) telling that the old unpatched version still has the bug on roughly the same OS as other reports isn't useful anymore, unless you were testing and able to repeat the bug with patched version meaning that fix is incomplete.

If you are affected by issue but don't have any new information to add please use the reaction button and thumbs up the issue. It is still useful to gauge how many people are affected by the problem and choosing how to prioritize them.

[karliss]

Yes, if the crash happens after right clicking it's probably the same issue as #3308 .

You can try the CI build from pull request here https://github.com/rizinorg/cutter/actions/runs/8056481691

[XVilka]

Could you please provide a stacktrace? I think it might be the same issue as #3305

[qux-bbb]

Could you please provide a stacktrace? I think it might be the same issue as #3305

How can I get a stacktrace?

[qux-bbb]

Maybe it relates to #3308, but I don't know.

[qux-bbb]

The CI build works. Thank you!

[djwesty]

I am experiencing the same issue with the 2.3.3 x86-64 app image on ubuntu 20.04

[djwesty]

Understood, thanks for explaining.

At first glance it seemed like this issue was closed without redress but now I see it's solved in the upcoming patch

Thanks for the hard work