Device initalization failed according to the Xorg logs;
- Dump your firmware version
- Dump your kernel version
- Dump your kernel logs (
dmesg
orjournalctl -k
)
Device initalization failed according to the Xorg 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
Could it be an issue with the Nvidia drivers, boot with acpi=off and then install the (proprietary) nvidia drivers and then reboot to see if it boots normally now?
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
Breaking Linux every week or every other week? That’s almost impressive!
I’ve used: User Agent Switcher
Successfully using;
teams.microsoft.com
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/118.0.0.0 Safari/537.36
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)
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