I was able to make some progress after adding the *screenshare* flag globally to my make.conf file and re-emerging @world. Now, I can get screen sharing working when using tools like OBS, so the core functionality works. However, when I try using google meet to share my screen, it will last for about 10 seconds before crashing. The following message appears in dmesg during the crash:
*[ 371.878847] notification-da[4638]: segfault at 3 ip 0000000000000003 sp 00007ffeb603abc8 error 14 in notification-daemon[55fb9db8c000+7000] likely on CPU 21 (core 5, socket 0)[ 371.878861] Code: Unable to access opcode bytes at 0xffffffffffffffd9.* On Tue, Dec 26, 2023 at 9:16 PM Jamie Getty <jamieget...@gmail.com> wrote: > I have tried running *dbus-run-session sway* manually (sway is already > running when I ran this but I wanted to see what errors I got regarding > xdg-desktop-portal) and here is what I get as output: > > jamie@localhost ~ $ dbus-run-session sway > > > > > *amdgpu: amdgpu_cs_ctx_create2 failed. (-13)00:00:00.025 [wlr] > [types/wlr_drm_lease_v1.c:715] No DRM backend supplied, failed to create > wlr_drm_lease_v1_manager2023-12-26 21:10:39 - [swaybg-1.2.0/main.c:582] > wl_display_roundtrip failed00:00:00.034 [wlr] [xwayland/sockets.c:63] > Failed to bind socket @/tmp/.X11-unix/X0: Address already in use2023-12-26 > 21:10:39 - [swaybg-1.2.0/main.c:289] Could not find config for output WL-1 > ((null))* > PipeWire already running, exiting. > (Use 'gentoo-pipewire-launcher restart' to restart PipeWire and > WirePlumber.) > dbus-daemon[4539]: [session uid=1000 pid=4539] Activating service > name='org.a11y.Bus' requested by ':1.2' (uid=1000 pid=4563 comm="waybar -b > bar-0") > dbus-daemon[4539]: [session uid=1000 pid=4539] Successfully activated > service 'org.a11y.Bus' > [2023-12-26 21:10:39.717] [info] Using configuration file > /home/jamie/.config/waybar/config > [2023-12-26 21:10:39.717] [info] Using CSS file > /home/jamie/.config/waybar/style.css > dbus-daemon[4539]: [session uid=1000 pid=4539] Activating service > name='org.freedesktop.portal.Desktop' requested by ':1.1' (uid=1000 > pid=4563 comm="waybar -b bar-0") > dbus-daemon[4539]: [session uid=1000 pid=4539] Activating service > name='org.freedesktop.portal.Documents' requested by ':1.4' (uid=1000 > pid=4583 comm="/usr/libexec/xdg-desktop-portal") > dbus-daemon[4539]: [session uid=1000 pid=4539] Activating service > name='org.freedesktop.impl.portal.PermissionStore' requested by ':1.5' > (uid=1000 pid=4589 comm="/usr/libexec/xdg-document-portal") > dbus-daemon[4539]: [session uid=1000 pid=4539] Successfully activated > service 'org.freedesktop.impl.portal.PermissionStore' > dbus-daemon[4539]: [session uid=1000 pid=4539] Successfully activated > service 'org.freedesktop.portal.Documents' > fusermount3: failed to access mountpoint /run/user/1000/doc: Permission > denied > > > > > > > > > > > > > *error: fuse init failed: Can't mount path > /run/user/1000/doc(/usr/libexec/xdg-desktop-portal:4583): > xdg-desktop-portal-WARNING **: 21:10:39.742: Failed to load RealtimeKit > property: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name > org.freedesktop.RealtimeKit1 was not provided by any .service > files(/usr/libexec/xdg-desktop-portal:4583): xdg-desktop-portal-WARNING **: > 21:10:39.742: Failed to load RealtimeKit property: > GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name > org.freedesktop.RealtimeKit1 was not provided by any .service > files(/usr/libexec/xdg-desktop-portal:4583): xdg-desktop-portal-WARNING **: > 21:10:39.742: Failed to load RealtimeKit property: > GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name > org.freedesktop.RealtimeKit1 was not provided by any .service > files(/usr/libexec/xdg-desktop-portal:4583): xdg-desktop-portal-WARNING **: > 21:10:39.742: No skeleton to export(/usr/libexec/xdg-desktop-portal:4583): > xdg-desktop-portal-WARNING **: 21:10:39.742: Choosing wlr.portal for > org.freedesktop.impl.portal.ScreenCast via the deprecated UseIn > key(/usr/libexec/xdg-desktop-portal:4583): xdg-desktop-portal-WARNING **: > 21:10:39.742: The preferred method to match portal implementations to > desktop environments is to use the portals.conf(5) configuration file* > dbus-daemon[4539]: [session uid=1000 pid=4539] Activating service > name='org.freedesktop.impl.portal.desktop.wlr' requested by ':1.4' > (uid=1000 pid=4583 comm="/usr/libexec/xdg-desktop-portal") > *2023/12/26 21:10:39 [ERROR] - config: no config file found* > dbus-daemon[4539]: [session uid=1000 pid=4539] Successfully activated > service 'org.freedesktop.impl.portal.desktop.wlr' > dbus-daemon[4539]: [session uid=1000 pid=4539] Successfully activated > service 'org.freedesktop.portal.Desktop' > dbus-daemon[4581]: Activating service name='org.a11y.atspi.Registry' > requested by ':1.0' (uid=1000 pid=4563 comm="waybar -b bar-0") > basic_string::_M_create > dbus-daemon[4581]: Successfully activated service 'org.a11y.atspi.Registry' > SpiRegistry daemon is running with well-known name - > org.a11y.atspi.Registry > [2023-12-26 21:10:39.746] [warning] Waybar has been built without rfkill > support. > [2023-12-26 21:10:39.860] [info] Bar configured (width: 1920, height: 26) > for output: WL-1 > > > On Tue, Nov 28, 2023 at 12:31 AM Arsen Arsenović <ar...@gentoo.org> wrote: > >> >> Jamie Getty <jamieget...@gmail.com> writes: >> >> > I'm not sure what you mean by *wrap it in dbus-run-session*. >> > I use SDDM as my display manager and I start Sway from there. >> > My sway config also contains this line, as previously mentioned: >> > >> > *# Enable screen sharingexec --no-startup-id >> > dbus-update-activation-environment --all* >> > >> > However, I noticed that if I try running this line by itself in a >> terminal, >> > I get this output: >> > >> > >> > *jamie@localhost ~ $ exec --no-startup-id >> > dbus-update-activation-environment --allbash: exec: --: invalid >> optionexec: >> > usage: exec [-cl] [-a name] [command [argument ...]] [redirection ...]* >> >> Sway configs aren't shells scripts. In shell, you'd run >> 'dbus-update-activation-environment --all' alone. Does qdbus --session >> output any errors or just a bunch of names and numbers? >> >> SDDM should set up a D-Bus session bus, I believe. >> >> I'm quite sure that your D-Bus session bus is not working properly >> because of the error you initially posted. >> >> > On Sun, Nov 26, 2023 at 11:37 PM Arsen Arsenović <ar...@gentoo.org> >> wrote: >> > >> >> Hi Jamie, >> >> >> >> Jamie Getty <jamieget...@gmail.com> writes: >> >> >> >> > How do I ensure I have a dbus user session running? Those links just >> lead >> >> > to forum posts with varying issues and I'm not sure which to follow. >> >> > Here are the dbus-related process I have running: >> >> >> >> Make sure to wrap it in dbus-run-session. See >> >> https://wiki.gentoo.org/wiki/Sway#Starting_Sway >> >> >> >> Then add the >> >> >> >> exec --no-startup-id dbus-update-activation-environment --all >> >> >> >> ... line from the screen sharing troubleshooting entry. >> >> -- >> >> Arsen Arsenović >> >> >> >> >> -- >> Arsen Arsenović >> > > > -- > Sincerely, > Jamie > -- Sincerely, Jamie
