We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The application crashes when scrolling through the content. This happens only the first time after restart. In the next launches it works stably.
application does not crash
rssguard.log
OS: Operating System: Fedora Linux 41 KDE Plasma Version: 6.2.3 KDE Frameworks Version: 6.8.0 Qt Version: 6.8.0 Kernel Version: 6.11.8-300.fc41.x86_64 (64-bit) Graphics Platform: Wayland
RSS Guard version: RSS Guard 4.5.1
The text was updated successfully, but these errors were encountered:
Well, several issues.
When you see ampty "Add account" dialog, that means that RSS Guard plugins were not loaded - this is very very likely deployment problem.
When you see driver not loaded problem, that means you have Qt deployment problem.
Both problems are likely upstream and not caused by the RSS Guard itself.
I did not test RSS Guard with Qt 6.8.0 extensively yet, so it might also be that there is new regression or not-yet-seen RSS Guard bug.
Sorry, something went wrong.
martinrotter
No branches or pull requests
Brief description of the issue
The application crashes when scrolling through the content. This happens only the first time after restart. In the next launches it works stably.
How to reproduce the bug?
What was the expected result?
application does not crash
What actually happened?
application does not crash
Debug log
rssguard.log
Operating system and version
OS:
Operating System: Fedora Linux 41
KDE Plasma Version: 6.2.3
KDE Frameworks Version: 6.8.0
Qt Version: 6.8.0
Kernel Version: 6.11.8-300.fc41.x86_64 (64-bit)
Graphics Platform: Wayland
RSS Guard version: RSS Guard 4.5.1
The text was updated successfully, but these errors were encountered: