SavvyBeardedFish

joined 1 year ago
[–] SavvyBeardedFish@reddthat.com 1 points 3 weeks ago (1 children)

Additionally you can try and force use amdgpu rather than radeon, by setting the kernel flags:

radeon.cik_support=0 radeon.si_support=0 amdgpu.cik_support=1 amdgpu.si_support=1 amdgpu.dc=1

Source

[–] SavvyBeardedFish@reddthat.com 0 points 3 weeks ago (2 children)

Device initalization failed according to the Xorg logs;

  1. Dump your firmware version
  2. Dump your kernel version
  3. Dump your kernel logs (dmesg or journalctl -k)

No bios update, but you most likely received both microcode updates (which is what will fix/mitigate the Intel issue, the bios is only to ensure everybody gets the microcode update) and firmware updates (from linux-firmware)

Of course non-mainlined (i.e. not in the linux kernel) firmware is a bit more iffy, luckily it's getting slowly better with OEMs using fwupd for those scenarios

[–] SavvyBeardedFish@reddthat.com 6 points 3 months ago* (last edited 3 months ago) (2 children)

Running: swaymsg for_window "[app_id=mpv] opacity 0.5"

Works as expected on my end, are you missing just executing for_window?

Note, you can also add multiple rules in the same execution, e.g.

for_window {
    [app_id=mpv] opacity 0.85
    [app_id=LibreWolf] opacity 0.85
}

Also, note that app_id of LibreWolf is capitalized in that manner. You can get that information [app_id, shell etc] by running swaymsg -t get_tree

[–] SavvyBeardedFish@reddthat.com 1 points 7 months ago

Breaking Linux every week or every other week? That's almost impressive!

[–] SavvyBeardedFish@reddthat.com 4 points 8 months ago (2 children)

I've used: User Agent Switcher

Successfully using;

  1. Whitelist mode
  2. Domain = teams.microsoft.com
  3. UserAgentString = Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/118.0.0.0 Safari/537.36
[–] SavvyBeardedFish@reddthat.com 6 points 8 months ago (1 children)

They support meetings in Firefox so it's a bit weird why they would block calls... They're effectively the same thing

Additionally, if you change your userAgent to be Chrome things are working pretty good in Firefox as far as I've tried it (not too extensively)

[–] SavvyBeardedFish@reddthat.com 2 points 1 year ago* (last edited 1 year ago)

From: This thread

Seems like you can try and debug the execution by running switcherooctl launch *application*, which should (manually) do the same as when you right click and click Launch with dedicated GPU, because I think Mint is using switcheroo, same as Gnome is.

But would then hopefully log some debug information for you in the terminal itself

[–] SavvyBeardedFish@reddthat.com 4 points 1 year ago (2 children)

I've tried running steam with the dedicated GPU option

What exactly are you running to choose the dedicated vs integrated GPU?

I also get the freezing issue without running with the dedicated GPU when I launch steam but found that launching directly to the steam settings window from the menu reduces the chances of freezing.

Hmmm, whenever this happens, it might be worth looking at the kernel logs, see if something crashes. You can check them with either

journalctl -k -xef or dmesg

Kernel: 5.15.0-82-generic

In general it's recommended to stay on newer kernels/mesa when using the open source GPU drivers, could be worthwhile trying to update that (think there's a PPA you can pull from)