-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
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
Crashes on Arch Linux/KDE Plasma #142
Comments
More stuff (was gonna make an issue, but then I forgot and AriaMoradi made it for me):
Also, here are some system details for context (click to expand): Version Info
And I also made a full dump of the output from Working GTK Settings
Broken GTK Settings
|
can you enable |
And full logs is there on OP: Suwayomi/Suwayomi-Server#38 (comment) |
I opened an issue on the KDE bug tracker here, as this might be an issue with Breeze: https://bugs.kde.org/show_bug.cgi?id=434955 (I'll close it if it's a SystemTray issue and not a Breeze issue.) |
ran the latest build to tachidesk with
the main difference I noticed between those logs and the logs from a working theme (ignoring the fact that it, you know, works) is that the following is logged when it works: +(java:359859): dbind-WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-S8eFMpHB00: No such file or directory (which is interesting, because you think the warning would only be logged when it doesn't work? Other than that, I don't see much useful info.) |
Fixed. I've got it working on Manjaro-KDE, and Arch-Gnome. SWT on Arch-Gnome has some... errors?, but it still works. I will be recording those, and pushing the fix to 4.1, since the systemtray still works, but with errors, and only with SWT. The only errors now that I have seen, which are out of my control, is |
Original issue: Suwayomi/Suwayomi-Server#38
Summary
Users get repeated errors like below and then experience a crash that I failed to fix with a try-catch
The issue seems to be connected to gtk themes.
The text was updated successfully, but these errors were encountered: