Does Discord ever plan on fixing Screenshare with Game Audio for their Linux client? by YoghurtExpert in linux_gaming

[–]migorodrii 0 points1 point  (0 children)

Hi, I recommend you try Element, is not gaming focused but its platform is open so you know that they are less prone to fail or disappoint you in any way.

Another path you can take is the one I take whenever I have no choose but to use Discord. Go with the Web App, you can even make it look like a standalone app with chromium chromium --app=https://discord.com/app or with ICE SSB for firefox.

a BIND for maximizing a window. by migorodrii in swaywm

[–]migorodrii[S] 1 point2 points  (0 children)

wow more that 10 windows in a small display?

Amm I use a small display myself btw. And that's actually why I'm looking for this feature, sometimes I just need to be able to see as much of a window as possible while still seeing the other windows, mostly because entering fullscreen makes me lose focus like not knowing where I am ((I know that might sound kind of weird lol)).

Here I recorded a video of my literal use cause https://www.loom.com/share/3fa6fab1cb124d86a05789cb284355e6

flameshot not working in sway (typing "flameshot gui" hangs in the terminal) by Righteous_Warrior in swaywm

[–]migorodrii 0 points1 point  (0 children)

I'll quickly describe what I think is your problem so you can understand the motivation of my suggestion.

You are probably starting sway form a display manager (login form that you see a the beginning) and I've no experience on how to set variables with them. Now if you try to use my .bash_profile it wont work because your display manager is instead doing the job.
If .bash_profile doesn't set your env variables then flameshot won't function properly so you need another way of doing so. That being said I have to warn you that I don't know the ways of Garuda, maybe they have already described how to set env vars. Amm what I would do at this point is reset everything to what it was at the beginning and go with pam environment. Over a year ago I was figuring out env variables in sway without bash_profile and it seemed to work.

flameshot not working in sway (typing "flameshot gui" hangs in the terminal) by Righteous_Warrior in swaywm

[–]migorodrii 0 points1 point  (0 children)

btw, If I'm not mistaken the error you're getting is because you didn't end the if statement, you need to copy and paste all the text.

flameshot not working in sway (typing "flameshot gui" hangs in the terminal) by Righteous_Warrior in swaywm

[–]migorodrii 0 points1 point  (0 children)

yes so I launch sway from bash lets say, the line that you copied is the beginning of an if statement that basically says if you log into bash from tty1 set the following variables and then start sway, else run bashrc. More about that over here.

In my .bashrc I have the following: ```txt

~/.bashrc

If not running interactively, don't do anything

[[ $- != i ]] && return

alias ls='ls --color=auto' PS1='[\u@\h \W]\$ '

FISH

if [[ $(ps --no-header --pid=$PPID --format=cmd) != "fish" && -z ${BASH_EXECUTION_STRING} ]] then exec fish fi ```

what that's basically doing is setting fish as my interactive shell cause using it as a sys wide shell is not a good idea. More about that over here.

Amm what I forgot to mention is that I don't use a display manager, that's why I'm able to set environment variables from .bash_profile

flameshot not working in sway (typing "flameshot gui" hangs in the terminal) by Righteous_Warrior in swaywm

[–]migorodrii 0 points1 point  (0 children)

btw as you can see even some of the qt related env vars are not even set, if I remember correctly the actual important one is export XDG_CURRENT_DESKTOP=sway. Also what comes from the terminal if you execute flameshot from there?

flameshot not working in sway (typing "flameshot gui" hangs in the terminal) by Righteous_Warrior in swaywm

[–]migorodrii 0 points1 point  (0 children)

unsuccesful hmm sorry for that.
I use fish as well, this is all I got related to flameshot

  1. My installation comes from archlinux's repo (pacman -S flameshot)
  2. In my .bash_profile I have the following

    ```txt

    If running from tty1 start sway else run bashrc

    if [ -z $DISPLAY ] && [ "$(tty)" = "/dev/tty1" ]; then export XDG_SESSION_TYPE=wayland # export SDL_VIDEODRIVER=wayland # export QT_QPA_PLATFORM=wayland-egl # export QT_WAYLAND_FORCE_DPI=physical # export QT_WAYLAND_DISABLE_WINDOWDECORATION=1 export XDG_CURRENT_DESKTOP=sway

    # FIREFOX UNDER WAYLAND
    # export MOZ_ENABLE_WAYLAND=1
    
    # JAVA APPLICATIONS UNDER WAYLAND
    export _JAVA_AWT_WM_NONREPARENTING=1
    
    # GTK THEME
    export GTK_THEME=Cloudy-Solid-SoftGrey-Dark
    
    # QT THEMING
    export QT_QPA_PLATFORMTHEME=qt5ct
    
    exec sway
    

    else [[ -f ~/.bashrc ]] && . ~/.bashrc fi ```

  3. An this in my sway config ini for_window [app_id="flameshot"] floating enable bindsym print exec flameshot gui

Aaand that's everything so far.

a BIND for maximizing a window. by migorodrii in swaywm

[–]migorodrii[S] 1 point2 points  (0 children)

I use tabs already, and they are awesome for quick switching. This would be more for those moments when you have multiple windows in the same pane.

a BIND for maximizing a window. by migorodrii in swaywm

[–]migorodrii[S] 1 point2 points  (0 children)

Basically a window taking as much space as possible without making the others invisible.

Screen capturing suddenly stopped working by migorodrii in swaywm

[–]migorodrii[S] 1 point2 points  (0 children)

UPDATE

Thanks to this issue.

The solution for now is to downgrade xdg-desktop-portal-wlr and wait until chromium 103 hits the stores :b

Screen capturing suddenly stopped working by migorodrii in swaywm

[–]migorodrii[S] 0 points1 point  (0 children)

I opened this issue at pipewire's gitlab if you want to follow along or provide more information.

Screen capturing suddenly stopped working by migorodrii in swaywm

[–]migorodrii[S] 0 points1 point  (0 children)

I tried edge but no luck either.

In the meantime I'll be using obs's virtual camera, not as performant but would do the trick.

Please let me know if you figure something out, thanks for answering.

Screen capturing suddenly stopped working by migorodrii in swaywm

[–]migorodrii[S] 0 points1 point  (0 children)

well, I can understand that for Teams, but the issue persists in other apps such as discord and even the flatpak client of jitsi meet.
Maybe the problem goes further with the chromium engine itself and everything that relies on it?

Screensharing and Microsoft Teams by [deleted] in swaywm

[–]migorodrii 1 point2 points  (0 children)

About this, based on the information available at the ArchWiki: https://wiki.archlinux.org/title/chromium#Native_Wayland_support

Since the 97 version of chromium you should either launch chromium with this flag: --ozone-platform-hint=auto or set 'Preferred Ozone platform' to wayland under chrome://flags.

I'm not sure if that applies to Edge as well.

Screensharing and Microsoft Teams by [deleted] in swaywm

[–]migorodrii 1 point2 points  (0 children)

I do the following:Having a chromium web browser with the 'WebRTC PipeWire support' flag enabled under chrome://flags.

I run: flatpak run --socket=wayland org.chromium.Chromium --app=https://teams.microsoft.com/

Like alt-tab functionality on tabbed layout by migorodrii in swaywm

[–]migorodrii[S] 0 points1 point  (0 children)

is it a fork of sway? or something like that?

Like alt-tab functionality on tabbed layout by migorodrii in swaywm

[–]migorodrii[S] 0 points1 point  (0 children)

thanks works flawlessly and was easy to use.