Closed aquarichy closed 8 months ago
Hmm, just experienced this with Signal's flatpak as well.
Someone has created a bug on libnotify for this:
Where a user notes its impact on Element.
Give, 4-5 hours for the baseapp update to be published, then rebuild Element against it via https://buildbot.flathub.org/#/apps/im.riot.Riot. Thanks
@SISheogorath ^
So has anybody triggered this rebuild? It seems easy to fix here, now that it's fixed upstream.
Unfortunately, this bug in the linter needs to be fixed before triggering a build https://github.com/flathub/flatpak-builder-lint/issues/183 else it'd fail.
bot, build
It's an issue :D Build was triggered here https://buildbot.flathub.org/#/builders/6/builds/72141
https://buildbot.flathub.org/#/builders/6/builds/72142, should be published in 4-5 hours
Mhm, decided to speed-run the publishing. (I know, not overly popular among the flathub maintainers, sorry). Updates should be rolling out within the next minutes!
The updated Flatpak on Flathub resolves the issue in my testing. Yahoo! Thank you.
Since recently upgrading my Element flatpak from Flathub, clicking on notifications now causes Element to crash. Using the most recent commit, 4e01ebe0d1b235afdd9cb16d49a0952fd108fb5d, it still crashes.
I went through recent commits of im.riot.Riot and found:
System:
I haven't debugged Flatpaks before so any direction on what I can look at to help find the issue would be great.
I will see if I can debug it further, since updating the platform seems like a big change.