DacoTaco

what ? Thunderbird exists…

You are correct. Its just that wayland is not as cut and dry of “everyone should switch to wayland, it works 100%” because thats not true.
Ye, my comment should have been “wayland support is experimental on some distros” and not “wayland is experimental” to be more correct but hey, if people could stop shouting at me to switch to wayland because it just works, id be happy.

I know a few distros have switched, and i support it 1000%!
I know ive had a few glitches in linux mint which suggests they need to fix some stuff with cinnamon in wayland still ( and a few other apps ), hence my stance towards wayland atm. I love every piece of it but imma wait a liiiitle longer. The reason i think op’s issues came from either wayland or fedora because on debian-based distros ive had no issues on my framework 16, nor on the framework 13’s that are at the office ( ubuntu, linux mint, windows )

Edit: just gave it another go as i recently upgraded linux mint. Keyboard layout was stuck to us so altgr didnt work. Teams window could also not be double clicked to maximize and remote desktop via remmina was acting odd, like my mouse had shifted to the right. Desktop wallpaper was also shifted. Like i said, experimental on some systems :)

Then you shouldnt have picked wayland, period. There is a reason its still experimental. And in general, hearing you talk, im not sure linux is your thing in general. Even in linux mint i have to poke in cli once in a while…

EDIT: as i mentioned below,i just gave it another go as i recently upgraded linux mint. Keyboard layout was stuck to us so altgr didnt work. Teams window could also not be double clicked to maximize and remote desktop via remmina was acting odd, like my mouse had shifted to the right. Desktop wallpaper was also shifted. Like i said, experimental on some systems ( in this case linux mint ) :)

Framework 16 with the same display and linux mint user.
Pushed towards fedora? What? I also have no issues whatsoever with the screen or igpu of amd, so i wonder what you were using there and with what chipset.
Ive been daily driving mine for nearly a year now ( amd chipset and igpu) and none of those issues at all…

Fair enough, but then you are kinda asking for it if youre doing fishy shit. They need, and i do mean need, to somehow verify the actions being done are from a normal user and not a botnet or other fishy activity…

But its a server setting to need phone verification. Im on a ton of servers and never provided them my phone number. One server changed access rights manually for my username because i refused to give discord my phone number when they enabled the verification requirement haha.
Also, their response is terrible haha

For me audio sharing doesnt work at all haha

Only in servers that enabled that verification. Its a server setting

Haha, pruiskes. Had door dat het iets van discussie was maar wtf is de reden. Lovin’ it though, echt zalige gesprekken xD

Hahahahahaha, frikandel hahaha. Ich glaube er hat haha

Kein Scheiß, haha
Es ist nur ein lustiges, zufälliges “was zum fick” um online zu gehen haha

Ich habe etwas verpasst, was zum fick ist hier los??? o.O ( belgian, using translation )

I know, hence why i said youre not wrong but the example was wrong :p
Also, its more complex than that. Some teams can, some cant. And if they can it all depends on what project or context. The business world isnt that cut and dry hehe

Not saying youre wrong, but you took the wrong project as an example hehe.
Visual code is not open source. Its core is, but visual code isnt. The difference is what visual code ships with, on top of its core.
Its like saying chrome == chromium ( it isnt ).

Visual code comes with a lot of features, addins and other stuff that isnt in the core.
.net debugger for example, is not found in vscodium ( build of the vscode core ). And there is more stuff i cant think of now but have come across. Source: been using vscodium for a few months instead of vscode

Fair, and ill edit my post accordingly!

There are teams that are allowed, and within those companies are teams that are directly related to foss projects because those companies are in the foundation or supports of the foundation. However, thats doesnt mean every (product) team in the company is allowed to or that they can do or change whatever they like. Its a complex mess

Thats just dual booting. That wont work with the law if the contract says anything created using company hardware is theirs.
And yes, some companies need to give you a green light to work on projects in your free time, because they might have a team doing similar things somewhere, it might compete in something they would like to do in the future or like you said, might use company know how which is a huge nono. Its bs imo, but those clauses and rules are found in some employment agreements.
Remember, always read your employment agreements!

Yes, but not all devs within microsoft are allowed to work on non-ms foss projects. I assume wsl devs are allowed to send stuff to linux but visual studio devs probably are not.

And not every team is allowed to do that.
Also, youre telling somebody who has worked with big companies not allowing it in their employer contract that he is lying? Riiiight…
A lot of google devs also are not allowed to do any linux work outside of work without explicit permissions because of all the internal docs, teams and other work being done on linux from within google. Development rights is an absolute mess, legally.
I usually dont care and do what is right, despite what my emploter contract says, but i have gotten in trouble for it

I agree they should have sent a patch to the grub source, but keep in mind big software companies like microsoft, Verizon, … do not normally allow their product teams to send a patch or PR to open source projects. This is because in their contract it states that all code written on and during company times is owned by the company. This means that it is impossible for them to make a patch or PR because it would conflict with the projects licence and fact its open source.
This changes when the team explicitly works on the foss product/project like the ms wsl team or the team working on linux supporting azure hardware, but that is an exception. I do not believe the microsoft kernel/bootloader team is allowed to send patches to grub.

Its a terrible thing, and it shouldnt be, but thats the fact of the world atm.