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

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

[superiums]

[-- 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

Re: the right way to start a WM session of wayland

[classabbyamp]

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

New comment by classabbyamp on void-packages repository

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

Comment:
does it work with dbus-run-session instead of dbus-launch? 

Re: the right way to start a WM session of wayland

[superiums]

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

New comment by superiums on void-packages repository

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

Comment:
> does it work with dbus-run-session instead of dbus-launch?

it acts like dbus-launch.

Re: the right way to start a WM session of wayland

[superiums]

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

New comment by superiums on void-packages repository

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

Comment:
and I found another thing, 
- if start WM directly, fcitx5-rime **NOT work** in chromium.
- if start WM with dbus-launch , fcitx5-rime **works** in chromium. 

Re: the right way to start a WM session of wayland

[classabbyamp]

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

New comment by classabbyamp on void-packages repository

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

Comment:
you have the dbus system service enabled too?

these softwares may require XDG_RUNTIME_DIR, do you use elogind/dumb_runtime_dir/pam_rundir? 

Re: the right way to start a WM session of wayland

[superiums]

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

New comment by superiums on void-packages repository

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

Comment:
yes, i have the dbus service enabled.
XDG_RUNTIME_DIR is run/user/1000

i have dbus-daemon and elogind-daemon runing in ps.

every service keep default after install, except elogind. i removed this from /var/service because i use greetd, greetd will report "elogind service is already launched" error if not remove it. seems elogind was started by greetd. also, i have seen this ps runing after remove.

i don't use dumb_runtime_dir/pam_rundir.

Re: the right way to start a WM session of wayland

[github-actions]

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

New comment by github-actions[bot] on void-packages repository

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

Comment:
Issues become stale 90 days after last activity and are closed 14 days after that.  If this issue is still relevant bump it or assign it.

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

[github-actions]

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

Closed issue by superiums on void-packages repository

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

Description:
there'are 2 ways to start a WM session for sway/wayfire/...
no matter start the WM from tty manually, or let DM load the session for WM, or start a command by DM.
1. run sway/wayfire directly.
2. run sway/wayfire by dbus: `dbus-launch wayfire`


i am using greetd and tui-greeter.
## Way 1, launch WM directly
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 2, lauch WM by dbus

if i use this command to let the DM start the WM
```
cmd='tuigreet -cmd dbus-launch wayfire'
```
or type ` dbus-launch wayfire` in tty

- gvfs  works.

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

```
error: Failed to inhibit: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: on path org.freedesktop.portal.Inhibit object not found“/org/freedesktop/portal/desktop”interface
```
- some program fails, like celluloid
can't be started by GUI, both in thunar or wofi.
but can be started by terminal,  with the same error reported above.
all packages like xdg-desktop-portal ,  xdg-desktop-portal-wlr already installed.