Qt6 defers the URL resolution to the component that actually uses the
property. Which means that the images are now resolved relatively to the
corresponding sddm component (Background, ComboBox) instead of a theme.
Work around that by pinning resource URLs to the theme path with
`Qt.resolvedUrl()`.
Fixes following error:
```
file:///usr/lib64/qt6/qml/SddmComponents/ComboBox.qml:105:9: QML Image: Cannot open: file:///usr/lib64/qt6/qml/SddmComponents/angle-down.png
```
The background and the screenshot are omitted, as we don't intend to use
these images.
Source: github.com/sddm/sddm@501129294be1487f753482c29949fc1c19ef340e
License: CC-BY-SA-3.0 AND MIT
There are issues with escaping and arguments splitting that we're unable
to solve at the moment. For example, `.desktop` files with whitespaces
and other characters treated specially by Sway in the `Exec=` field
are known to be broken[1][2].
Removing `-run-command`/`-run-shell-command` costs us pid-based
workspace assignment. I.e. the applications that take a while to load
will appear on the current workspace instead of the one they were
launched on.
That is at least partially mitigated by the fact that the app will
inherit `XDG_ACTIVATION_TOKEN` and `DESKTOP_STARTUP_ID` variables
created for for `exec rofi` command with a default lifetime of 30s[3].
But not all applications or UI frameworks support that.
This could be revisited later, once we have a solution that correctly
escapes the command to pass it through `swaymsg exec`.
[1]: https://i3wm.org/docs/userguide.html#exec_quoting
[2]: https://github.com/swaywm/sway/issues/5931
[3]: https://gitlab.freedesktop.org/wlroots/wlroots/-/blob/0.16/types/wlr_xdg_activation_v1.c#L361
The output pollutes the journal and doesn't seem to be useful:
```
unknown[657924]: [
unknown[657924]: {
unknown[657924]: "success": true
unknown[657924]: }
unknown[657924]: ]
```
We recommend use of application launcher in installation instructions
but Anaconda won't start until xhost application is started.
It's already solved by starting xhost app in ~/.bashrc, however, that
won't work for a launcher because it's not sourcing ~/.bashrc. To solve
this, start xhost by Sway configuration file on Live.
- Drop %%check - as Sway does not report the result in an exit code, it
wasn't useful during the package build.
- Update sddm version requirement. The patch is now applied in Fedora.
As we're no longer using 50-fedora.conf as an entrypoint, it's better to
make config names stable and remove underlying tools from the names.
This way we are free to change the implementation while users will use
the same filename for overrides. I.e. 90-bar.conf should be created in
the user config directory no matter which bar we use in the default
config.
