-
Notifications
You must be signed in to change notification settings - Fork 2
Conversation
Started test build 106746 |
Started test build 106747 |
Will have to investigate this one... [EDIT] UpdateQt6Core5Compat is missing from the KDE runtime: https://invent.kde.org/packaging/flatpak-kde-runtime/-/issues/26 Workaround for now is to just build it ourselves. |
Started test build 106751 |
Started test build 106753 |
Build 106753 failed |
Started test build 106754 |
Build 106746 failed |
Build 106747 failed |
Build 106751 failed |
Started test build 106756 |
Build 106756 failed |
Okay, so now it at least builds fine, but it fails to validate the dimensions of the RSS Guard icon for not being a perfect square. 🤡 @martinrotter I'll add the icon here for now just to test this Qt 6 build, but for the next release, can you please fix this ~REALLY IMPORTANT~ icon validation issue? Thanks! EDIT: I've sent a pull request here. |
Build 106754 failed |
Started test build 106765 |
Started test build 106766 |
Build 106766 successful
|
Started test build 106768 |
Build 106768 successful
|
Yup, it definitely fixes it: qt6-hovering-fd-leak-fixed.mp4Nevertheless, I'll be using this Qt 6 build for a while just to make sure there are no obvious bugs. |
Build 106765 failed |
Okay, so after leaving RSS Guard running for about 3 days straight, I can confirm that the file descriptor leak issue is gone for good! The switch to Qt 6 causes only two minimal differences, but they should only affect GNOME users with a very specific setup. The first issue is simply the placeholder text in input fields being hard to read (reported to upstream here), but it only affects people using QGnomePlatform/adwaita-qt, which are components used to better integrate Qt apps running on GNOME. The second issue is related to system tray notifications. On the Qt 5 build, notifications were sent directly to GNOME's "notification center", also thanks to QGnomePlatform, but now, they are displayed as a balloon like this (which I think it's how it is on KDE?): For me, this is not a big deal and it's actually better to read than GNOME's notification center. Nevertheless, this has been already fixed, but there's no release with the fix just yet. To sum up, if you are okay with the changes, I think this PR could be postponed to the next RSS Guard release, so I can drop the patches and make the PR cleaner. |
In fact, I believe that this could/should be merged right now. Feel free to rearrange the PR to make it cleaner and then let me know and I will merge. |
Awesome! Well, the PR is pretty much ready at this point. Just keep in mind that if you want to merge this right now, on the next RSS Guard release you'll have to modify the manifest a bit and remove the left over files, because the two fixes that I'm using here have already been upstreamed by you here and here. So for the next release you'd just delete lines 56 through 65 and then delete these two files: |
Started test build 108278 |
Build 108278 successful
|
@martinrotter Please merge this one instead of #31 (which I also included here). Thank you! |
I just want to test if this fixes martinrotter/rssguard#565, once and for all.
My current setup:
Currently, there doesn't seem to leak file descriptors as badly as before (presumably caused by just calling
QSystemTrayIcon::isSystemTrayAvailable()
), so that's good.However, there is this other horrible leak triggered by just hovering links in the WebView (caused by
QWebEngineView::setHtml()
?):hovering-fd-leak.mp4
The commands I used in the video:
flatpak run com.github.rssguard -w
(to launch RSS Guard with "basic" WebView support)watch -n.1 'bash -c "echo fd count: ±$(ls -l /proc/$(pidof rssguard)/fd | wc -l)"'
(to monitor fd count)However, I've been experimenting with Arch Linux's official build of RSS Guard, which only recently switched to building with Qt 6. From my testing, the same fd leak above does not happen in the Qt 6 build, so I want to see if this hopefully fixes the Flatpak package as well!
Closes #31