-
Notifications
You must be signed in to change notification settings - Fork 0
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
Troubleshoot ublue-os/bluefin#575 #3
Conversation
In the above commit, the Slack Flatpak app is able to open links. |
In the above commit, the Slack Flatpak app is able to open links. |
The above commit resulted in the following changes in
The Slack Flatpak app is able to open links. |
In the above commit, the Slack Flatpak app is unable to open links. |
In the above commit, the Slack Flatpak app is able to open links! |
In the above commit, the Slack Flatpak app is still able to open links. |
In the above commit, the Slack Flatpak app is no longer able to open links! This suggests that something in either ublue-user-flatpak-manager.service or ublue-user-setup.service the proximal cause of the loss of ability to open links in Flatpak apps like Slack. |
In the above commit, the Slack Flatpak app is able to open links! |
In the above commit, the Slack Flatpak app is able to open links! This suggests that ublue-user-setup.service is the proximal cause of the loss of ability to open links in Flatpak apps like Slack. |
In the above commit, the Slack Flatpak app is no longer able to open links! This confirms that ublue-user-setup.service is the proximal cause of the loss of ability to open links in Flatpak apps like Slack. In the above commit, kdeconnectd, xwaylandvideobr, SyncThingy, and crow all crash and make core dumps. |
In the above commit, the Slack Flatpak app is able to open links again! This double-confirms that ublue-user-setup.service is the proximal cause of the loss of ability to open links in Flatpak apps like Slack. In the above commit, kdeconnectd, xwaylandvideobr, SyncThingy, and crow all don't crash and make core dumps. This confirms that ublue-user-setup.service is the proximal cause of those crashes. Interesting! The ublue-user-setup.service doesn't really seem to do very much 🤔 🤔 |
Interestingly, in the above commit, the Slack Flatpak app is unable to open links, and I get crashes of kdeconnectd, xwaylandvideobr, SyncThingy, and crow! Note: Here is the status of the
|
…for xdg-desktop-autostart
In the above commit, the Slack Flatpak app is able to open links again! This confirms that ublue-user-setup.service's requirement of xdg-desktop-autostart.target is the proximal cause of the loss of ability to open links in Flatpak apps like Slack. In the above commit, kdeconnectd, xwaylandvideobr, SyncThingy, and crow all don't crash and make core dumps. This confirms that ublue-user-setup.service's requirement of xdg-desktop-autostart.target is the proximal cause of those crashes. Note: Here is the status of the
Here are the units which depend on xdg-desktop-autostart.target:
Here are the units which plasma-workspace.target depends on:
We can see that normally plasma-workspace.target starts xdg-desktop-autostart.target and (via graphical-session.target) xdg-desktop-portal.service:
Here are the units which depend on ublue-user-setup.service:
In this case, default.target is the default systemd target for the user:
According to https://man.archlinux.org/man/systemd.special.7#UNITS_MANAGED_BY_THE_USER_SERVICE_MANAGER , the user default.target is started by default is the main target of the user session. https://wiki.archlinux.org/title/systemd/User interprets this as meaning that "When a systemd user instance starts, it brings up the per user target default.target". Additional observations:
These observations suggest that the behavior of |
In the above commit, the Slack Flatpak app is unable to open links, and I get crashes of kdeconnectd, xwaylandvideobr, SyncThingy, and crow. This suggests that the problems are not caused by the possibility of ublue-user-setup.service starting before xdg-desktop-autostart.service. Here are the units which depend on xdg-desktop-autostart.target:
As expected, ublue-user-setup adds a dependency. Here are the units which depend on xdg-desktop-portal.service:
Interestingly, this is the same as in the previous commit where everything was working. So I can't see a clear link between the weird behavior of xdg-desktop-portal and the brokenness of the various I looked at the
It will be interesting to see what would happen if we changed |
In the above commit, the Slack Flatpak app is unable to open links, and I get crashes of kdeconnectd, xwaylandvideobr, SyncThingy, and crow. This suggests that the problems are not caused by the possibility of ublue-user-setup.service starting before xdg-desktop-autostart.service. I'm guessing everything else is the same, too. |
In the above commit, the Slack Flatpak app is able to open links again, and I no longer get crashes of kdeconnectd, xwaylandvideobr, SyncThingy, and crow. However, it looks like I didn't correctly change the dependency to bluefin-firstboot:
|
In the above commit, the Slack Flatpak app is able to open links, and I don't get crashes of kdeconnectd, xwaylandvideobr, SyncThingy, and crow. Additionally, ublue-user-setup.service does indeed depend on bluefin-firstboot:
And now xdg-desktop-autostart.service is no longer depended upon by ublue-user-setup.service:
This suggests that we might we able to work around whatever bizarre interaction is caused by As expected (because bluefin-firstboot is still directly/indirectly depended upon by ublue-user-setup.service), I am still getting the same errors in yafti:
Beyond seeing whether we still get these errors when bluefin-firstboot is not a direct/indirect dependency of ublue-user-setup.service, it would also be useful to bisect the various applications contained in xdg-desktop-autostart.target to see whether we can isolate an interaction with xdg-desktop-portal:
|
Everything is still the same in the above commit - so changing |
In the above commit, everything is still the same - including the errors from |
As expected, in the above commit, the Slack Flatpak app is unable to open links, and I get crashes of kdeconnectd, xwaylandvideobr, SyncThingy, and crow. This establishes a starting point for bisecting which applications in xdg-desktop-autostart.target could be having weird interactions with xdg-desktop-portal when their start is driven by default.target via ublue-user-setup.service rather than being driven by plasma-workspace-wayland.target via plasma-workspace.target. |
As expected, in the above commit, the Slack Flatpak app is unable to open links, and I no longer get crashes of xwaylandvideobr, SyncThingy, and crow, but I still get crashes of kdeconnectd. |
In the above commit, the Slack Flatpak app is still unable to open links, and I don't get crashes of xwaylandvideobr, SyncThingy, and crow, but I still get crashes of kdeconnectd. |
As expected, in the above commit, the Slack Flatpak app is still unable to open links, and I don't get crashes of xwaylandvideobr, SyncThingy, and crow, but I still get crashes of kdeconnectd. |
As expected, in the above commit, the Slack Flatpak app is still unable to open links, and I don't get crashes of xwaylandvideobr, SyncThingy, and crow, but I still get crashes of kdeconnectd. |
In the above commit, the Slack Flatpak becomes able to open links! And, as expected, I don't get crashes of kdeconnectd. So including |
In the above commit, the Slack Flatpak becomes unable to open links. So including Requires=app-org.kde.kdeconnect.daemon@autostart.service is both necessary and sufficient to break something with xdg-desktop-portal. I'm guessing that kdeconnect is interacting in some weird way with xdg-desktop-portal, and that either KDE Connect or something else on Bluefin (e.g. GSConnect) has the same kind of interaction with xdg-desktop-portal on Bluefin. |
This issue should be resolved by #6 |
This PR either fixes or works around the root cause of ublue-os#575.
This PR is made to use GitHub Actions to build OS images so that I can try to bisect changes made by my Bluefin-based Containerfile to troubleshoot the manifestation of ublue-os#575 in this repository, according to the troubleshooting plan I described in ublue-os#575 (comment)