[ISSUE] the right way to start a WM session of wayland

[superiums <superiums@users.noreply.github.com>]

[-- Attachment #1: Type: text/plain, Size: 1808 bytes --]

New issue by superiums on void-packages repository

https://github.com/void-linux/void-packages/issues/40313

Description:
there'are 3 ways to start a WM session for sway/wayfire/...
1.  start the WM from tty manually.
2.  let DM load the session for WM.
3. start a command by DM.


i am using greetd and tui-greeter.
## Way 2
if i use the way 2, all things works but except gvfs. 
- gvfs fails
thunar report the gvfs was not work currectly, and there's no vols appear in left panel of thunar.
for tracering the issue, all of them report an GLIB error.
for example , this is the report of gvfs debug , using comomand GVFS_DEBUG=1 $(find /usr/lib* -name gvfsd 2>/dev/null) --replace 2>&1 | tee gvfsd.log :

```
(process:14320): GLib-GObject-CRITICAL **: 11:21:21.921: g_object_new_with_properties: assertion 'G_TYPE_IS_OBJECT (object_type)' failed

(process:14320): GLib-GIO-CRITICAL **: 11:21:21.924: g_volume_monitor_get_mounts: assertion 'G_IS_VOLUME_MONITOR (volume_monitor)' failed

(process:14320): GLib-GObject-WARNING **: 11:21:21.924: invalid (NULL) pointer instance

(process:14320): GLib-GObject-CRITICAL **: 11:21:21.924: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(process:14320): GLib-GObject-WARNING **: 11:21:21.924: invalid (NULL) pointer instance

(process:14320): GLib-GObject-CRITICAL **: 11:21:21.924: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
```
- obs-studio works in this way.

## Way 3

if i use this command to let the DM start the WM
```
cmd='tuigreet -cmd dbus-launch wayfire'
```
- gvfs  works.

- but obs-studio can't take screen record (no `capture screen source (pipewire)` appears), cant' start virtual camera.

report no interface found on dbus org.desktop.xdg.portal