Problem networkmanager Ubuntu 20.04

Hi, I have a weird problem:
I need to use https://client.wvd.microsoft.com/arm/webclient/ and since last weeks it doesn't work anymore.
We tested several Computers and the result was: Windows, Android, Mac, Manjaro, Debian and Ubuntu 22.04 worked. Zorin 16 and Ubuntu 20.04 doesn't work.
Searching for the mirror we tested dig and pin:

gerhardbeck@arbeitszimmer-zorin ~> dig client.wvd.microsoft.com

; <<>> DiG 9.16.1-Ubuntu <<>> client.wvd.microsoft.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 34331
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;client.wvd.microsoft.com.	IN	A

;; Query time: 32 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Di Mai 23 12:32:39 CEST 2023
;; MSG SIZE  rcvd: 53

gerhardbeck@arbeitszimmer-zorin ~> ping client.wvd.microsoft.com
ping: client.wvd.microsoft.com: Temporärer Fehler bei der Namensauflösung

The Nameserver is

Current DNS Server: 192.168.178.1   

With

dig @192.168.178.1 client.wvd.microsoft.com

;; ANSWER SECTION:
client.wvd.microsoft.com. 20	IN	CNAME	client.privatelink-global.wvd.microsoft.com.
client.privatelink-global.wvd.microsoft.com. 20	IN CNAME client.privatelink.wvd.microsoft.com.
client.privatelink.wvd.microsoft.com. 20 IN CNAME rdweb.wvd.microsoft.com.
rdweb.wvd.microsoft.com. 20	IN	CNAME	rdweb.privatelink-global.wvd.microsoft.com.
rdweb.privatelink-global.wvd.microsoft.com. 20 IN CNAME	rdweb.privatelink.wvd.microsoft.com.
rdweb.privatelink.wvd.microsoft.com. 20	IN CNAME rdweb-prod-geo.trafficmanager.net.
rdweb-prod-geo.trafficmanager.net. 14 IN CNAME	mrs-weur0c100-rdweb-prod.wvd-ase-weur0c100-prod.p.azurewebsites.net.
mrs-weur0c100-rdweb-prod.wvd-ase-weur0c100-prod.p.azurewebsites.net. 14	IN CNAME waws-prod-am2-ce03ae4d.sip.p.azurewebsites.windows.net.
waws-prod-am2-ce03ae4d.sip.p.azurewebsites.windows.net.	498 IN CNAME waws-prod-am2-ce03ae4d.cloudapp.net.
waws-prod-am2-ce03ae4d.cloudapp.net. 10	IN A	137.117.171.26

all works.
As I tested several computers on different routers and places it seems to be an ubuntu20.04 problem. It also works with Ubuntu 22.04

Any idea how I can solve that problem?
Is there a chance to get the networkmanager updated in Zorin to the current version?

If it worked on Debian, it really should have worked on Ubuntu 20.04 or Zorin 16...
Is it possible to try testing on Zorin OS 16 Lite (maybe using the LiveUSB) and see if it works?
I am reading the documentation on it and saw a curious thing.

Well, I don't have a chance to test it the next days.
But it shouldn't be a problem in my network, therefore anyone might test it with Zorin Lite

I'm not sure whether you're right that it should work on Ubuntu as it worked on Debian. As far as I know Network Manager is a gnome application...

I based that on the current stable package versions.

Off the cuff, might I ask how you narrowed this down to the network manager?

as dig @192.168.178.1 client.wvd.microsoft.com works. 192.168.178.1 is the DNS Server.
Therefore it seems to be a problem network manager resolves client.wvd.microsoft.com
If you have any other idea to narrow down the problem it is very welcome

1 Like

Just tested it. ping and dig also have problems on Zorin 16 lite

1 Like

Are you running Zorin OS on a VM?
Do you have Firewall enabled or disabled?

I definitely agree with you as to DNS, but I have sifted through and compared the config files for Ubuntu 20.04 and Ubuntu 22.04 and Zorin OS 16. I can find no differences between them. I do not believe that the ZorinGroup would have had need to change any of them for Zorin OS, either.

You may need to check your Azure NSG configurations. But I also wonder if the issue is as simple as the name "Ubuntu" and the name "Zorin".
I have not found anywhere that Azure would reference the LSB-Release file...

I tested it one 3 Zorin 16 pro, 1 Zorin 16 lite, 1 other light Linux based on Ubuntu 20.04 all not one VM, not behind a firewall, 2 different DSL Providers.
Someone else tested it on Ubuntu 20.04 : Link didn't work and 22.04: link worked.
Manjaro: worked
Win, Android: always worked
Debian: worked

Therefore it just seems logical to close down the problem on Ubuntu 20.04

@Aravisian does the https://client.wvd.microsoft.com/ webpage load on your computers and using which OS?

To Azure NSG:
I can't configure any Azure configurations. And the company told me they dind't change anything.
But I don't see how the problem could be there as the linked site is first of all just a microsoft side to login to azure.
And secondly it works with several OS... :thinking:

Any idea how to narrow down the problem?

Zorin OS 16.2 Lite and the webpage does not load, no.

Well... Looking into this, I found that Canonical partnered with Microsoft for Azure support back when it was Zorin OS 12.
It appears that there is an "azure" kernel for Ubuntu.
So, I opened Synaptic Package manager and searched:
linux-azure- and came up with the Linuz-azure-5.11-headers-5.11.0-1007
Also were included are Cloud Tools and Tools.
It may be that Manjaro and the later Ubuntu include these by default whereas Zorin OS does not.
You might try using Synaptic to install the Linuz-azure-5.11-headers-5.11.0-1028, Linuz-azure-5.11-tools-5.11.0-1028 and Linuz-azure-5.11-cloud-tools-5.11.0-1028

Once done, reboot and test.
Or Boot into the Azure Kernel from advanced Options for Zorin -- I am not sure on this as I have no experience with Azure...

But that cant be the problem as it worked last week and I had no software installed.
And it doesn't explain why the nameserver is causing a problem

Just out of curiosity, does this service downkoad a small .exe file to make a connection? I am only asking as when I was working from home using a different flavour of GNU/Linux I found that I could point Remmina remote to the small cpub.exe file and login to secure connection to both shared resource server and my Desktop (Z:/ drive) and only required one login whereas in Windows needed to enter user and password three times. Appreciate Azure is a different kettle of fish to logging in to secure website.

No, it does not. This page is a complete web remote desktop

Good point.
@gerhardbeck , I am stumped.

Hi all,

As this seems a very interesting case, I also investigated a bit into client.wvd.microsoft.com.

  • DNS resolution fails with systemd-resolved stub resolver 245.4. from Ubuntu 20.04, Zorin 16.2
  • DNS resolution works with systemd-resolved stub resolver 249.11 from Ubuntu 22.04
  • DNS resolution fails with unbound from all versions I tried:
    • unbound 1.9.4 from Ubuntu 20.04, Zorin 16.2,
    • unbound 1.13.1 from Ubuntu 22.04
    • unbound 1.13.1 from Debian 11

And the workaround is:

sudo ln -sf /run/systemd/resolve/resolv.conf /etc/resolv.conf

Now to all the details:

client.wvd.microsoft.com has a long cname cascade until it resolves to IP adresses, as we can see if it works:

host client.wvd.microsoft.com
client.wvd.microsoft.com is an alias for client.privatelink-global.wvd.microsoft.com.
client.privatelink-global.wvd.microsoft.com is an alias for client.privatelink.wvd.microsoft.com.
client.privatelink.wvd.microsoft.com is an alias for rdweb.wvd.microsoft.com.
rdweb.wvd.microsoft.com is an alias for rdweb.privatelink-global.wvd.microsoft.com.
rdweb.privatelink-global.wvd.microsoft.com is an alias for rdweb.privatelink.wvd.microsoft.com.
rdweb.privatelink.wvd.microsoft.com is an alias for rdweb-prod-geo.trafficmanager.net.
rdweb-prod-geo.trafficmanager.net is an alias for mrs-weur1c102-rdweb-prod.wvd-ase-weur1c102-prod.p.azurewebsites.net.
mrs-weur1c102-rdweb-prod.wvd-ase-weur1c102-prod.p.azurewebsites.net is an alias for waws-prod-am2-d2c3e1b3.sip.p.azurewebsites.windows.net.
waws-prod-am2-d2c3e1b3.sip.p.azurewebsites.windows.net is an alias for waws-prod-am2-d2c3e1b3.cloudapp.net.
waws-prod-am2-d2c3e1b3.cloudapp.net has address 13.69.82.138

This is probably new, and thats why its now causing issues (and not in the past). I see other recent reports as well, eg. DNS error in Linux when trying to reach client.wvd.microsoft.com - Microsoft Q&A

Here the details on how it breaks for unbound (as I get there logs easier):

root@nc01:~# unbound-host -v -d -t a client.wvd.microsoft.com
[1684946047] libunbound[2439105:0] notice: init module 0: validator
[1684946047] libunbound[2439105:0] notice: init module 1: iterator
[1684946047] libunbound[2439105:0] info: resolving client.wvd.microsoft.com. A IN
[1684946047] libunbound[2439105:0] info: priming . IN NS
[1684946047] libunbound[2439105:0] info: response for . NS IN
[1684946047] libunbound[2439105:0] info: reply from <.> 2001:7fd::1#53
[1684946047] libunbound[2439105:0] info: query response was ANSWER
[1684946047] libunbound[2439105:0] info: priming successful for . NS IN
[1684946047] libunbound[2439105:0] info: response for client.wvd.microsoft.com. A IN
[1684946047] libunbound[2439105:0] info: reply from <.> 2001:7fd::1#53
[1684946047] libunbound[2439105:0] info: query response was REFERRAL
[1684946047] libunbound[2439105:0] info: response for client.wvd.microsoft.com. A IN
[1684946047] libunbound[2439105:0] info: reply from <com.> 2001:503:39c1::30#53
[1684946047] libunbound[2439105:0] info: query response was REFERRAL
[1684946047] libunbound[2439105:0] info: response for client.wvd.microsoft.com. A IN
[1684946047] libunbound[2439105:0] info: reply from <microsoft.com.> 150.171.10.39#53
[1684946047] libunbound[2439105:0] info: query response was REFERRAL
[1684946047] libunbound[2439105:0] info: resolving ns2-01.azure-dns.net. AAAA IN
[1684946047] libunbound[2439105:0] info: resolving ns2-01.azure-dns.net. A IN
[1684946047] libunbound[2439105:0] info: response for ns2-01.azure-dns.net. AAAA IN
[1684946047] libunbound[2439105:0] info: reply from <.> 2001:7fe::53#53
[1684946047] libunbound[2439105:0] info: query response was REFERRAL
[1684946047] libunbound[2439105:0] info: response for ns2-01.azure-dns.net. A IN
[1684946047] libunbound[2439105:0] info: reply from <.> 2001:500:12::d0d#53
[1684946047] libunbound[2439105:0] info: query response was REFERRAL
[1684946047] libunbound[2439105:0] info: response for ns2-01.azure-dns.net. AAAA IN
[1684946047] libunbound[2439105:0] info: reply from <net.> 2001:500:856e::30#53
[1684946047] libunbound[2439105:0] info: query response was REFERRAL
[1684946047] libunbound[2439105:0] info: response for ns2-01.azure-dns.net. A IN
[1684946047] libunbound[2439105:0] info: reply from <net.> 192.12.94.30#53
[1684946047] libunbound[2439105:0] info: query response was REFERRAL
[1684946047] libunbound[2439105:0] info: response for ns2-01.azure-dns.net. A IN
[1684946047] libunbound[2439105:0] info: reply from <azure-dns.net.> 150.171.21.1#53
[1684946047] libunbound[2439105:0] info: query response was ANSWER
[1684946047] libunbound[2439105:0] info: response for client.wvd.microsoft.com. A IN
[1684946047] libunbound[2439105:0] info: reply from <wvd.microsoft.com.> 150.171.21.1#53
[1684946047] libunbound[2439105:0] info: query response was CNAME
[1684946047] libunbound[2439105:0] info: resolving client.wvd.microsoft.com. A IN
[1684946047] libunbound[2439105:0] info: response for ns2-01.azure-dns.net. AAAA IN
[1684946047] libunbound[2439105:0] info: reply from <azure-dns.net.> 2620:1ec:8ec:700::2#53
[1684946047] libunbound[2439105:0] info: query response was ANSWER
[1684946047] libunbound[2439105:0] info: response for client.wvd.microsoft.com. A IN
[1684946047] libunbound[2439105:0] info: reply from <wvd.microsoft.com.> 150.171.21.1#53
[1684946047] libunbound[2439105:0] info: query response was nodata ANSWER
[1684946047] libunbound[2439105:0] info: response for client.wvd.microsoft.com. A IN
[1684946047] libunbound[2439105:0] info: reply from <wvd.microsoft.com.> 2620:1ec:8ec:700::1#53
[1684946047] libunbound[2439105:0] info: query response was CNAME
[1684946047] libunbound[2439105:0] info: resolving client.wvd.microsoft.com. A IN
[1684946047] libunbound[2439105:0] info: response for client.wvd.microsoft.com. A IN
[1684946047] libunbound[2439105:0] info: reply from <wvd.microsoft.com.> 150.171.21.1#53
[1684946047] libunbound[2439105:0] info: query response was nodata ANSWER
[1684946047] libunbound[2439105:0] info: response for client.wvd.microsoft.com. A IN
[1684946047] libunbound[2439105:0] info: reply from <wvd.microsoft.com.> 150.171.21.1#53
[1684946047] libunbound[2439105:0] info: query response was CNAME
[1684946047] libunbound[2439105:0] info: resolving client.wvd.microsoft.com. A IN
[1684946047] libunbound[2439105:0] info: response for ns2-01.azure-dns.net. AAAA IN
[1684946047] libunbound[2439105:0] info: reply from <azure-dns.net.> 2620:1ec:8ec:700::2#53
[1684946047] libunbound[2439105:0] info: query response was ANSWER
[1684946047] libunbound[2439105:0] info: response for client.wvd.microsoft.com. A IN
[1684946047] libunbound[2439105:0] info: reply from <wvd.microsoft.com.> 2620:1ec:8ec:700::1#53
[1684946047] libunbound[2439105:0] info: query response was CNAME
[1684946047] libunbound[2439105:0] info: resolving client.wvd.microsoft.com. A IN
[1684946047] libunbound[2439105:0] info: response for client.wvd.microsoft.com. A IN
[1684946047] libunbound[2439105:0] info: reply from <wvd.microsoft.com.> 150.171.21.1#53
[1684946047] libunbound[2439105:0] info: query response was CNAME
[1684946047] libunbound[2439105:0] info: resolving client.wvd.microsoft.com. A IN
[1684946047] libunbound[2439105:0] info: response for client.wvd.microsoft.com. A IN
[1684946047] libunbound[2439105:0] info: reply from <wvd.microsoft.com.> 2620:1ec:8ec:700::1#53
[1684946047] libunbound[2439105:0] info: query response was CNAME
[1684946047] libunbound[2439105:0] info: resolving client.wvd.microsoft.com. A IN
[1684946047] libunbound[2439105:0] info: response for client.wvd.microsoft.com. A IN
[1684946047] libunbound[2439105:0] info: reply from <net.> 192.31.80.30#53
[1684946047] libunbound[2439105:0] info: query response was REFERRAL
[1684946047] libunbound[2439105:0] info: resolving tm1.edgedns-tm.info. AAAA IN
[1684946047] libunbound[2439105:0] info: resolving tm1.edgedns-tm.info. A IN
[1684946047] libunbound[2439105:0] info: response for tm1.edgedns-tm.info. A IN
[1684946047] libunbound[2439105:0] info: reply from <.> 2001:500:a8::e#53
[1684946047] libunbound[2439105:0] info: query response was REFERRAL
[1684946047] libunbound[2439105:0] info: response for tm1.edgedns-tm.info. AAAA IN
[1684946047] libunbound[2439105:0] info: reply from <.> 192.112.36.4#53
[1684946047] libunbound[2439105:0] info: query response was REFERRAL
[1684946047] libunbound[2439105:0] info: response for tm1.edgedns-tm.info. AAAA IN
[1684946047] libunbound[2439105:0] info: reply from <info.> 199.254.49.1#53
[1684946047] libunbound[2439105:0] info: query response was REFERRAL
[1684946047] libunbound[2439105:0] info: response for tm1.edgedns-tm.info. AAAA IN
[1684946047] libunbound[2439105:0] info: reply from <edgedns-tm.info.> 2620:1ec:bda:10::24#53
[1684946047] libunbound[2439105:0] info: query response was ANSWER
[1684946047] libunbound[2439105:0] info: response for tm1.edgedns-tm.info. AAAA IN
[1684946047] libunbound[2439105:0] info: reply from <edgedns-tm.info.> 2620:1ec:bda:10::24#53
[1684946047] libunbound[2439105:0] info: query response was nodata ANSWER
[1684946047] libunbound[2439105:0] info: response for tm1.edgedns-tm.info. A IN
[1684946047] libunbound[2439105:0] info: reply from <info.> 199.254.48.1#53
[1684946047] libunbound[2439105:0] info: query response was REFERRAL
[1684946047] libunbound[2439105:0] info: response for tm1.edgedns-tm.info. A IN
[1684946047] libunbound[2439105:0] info: reply from <edgedns-tm.info.> 150.171.21.4#53
[1684946047] libunbound[2439105:0] info: query response was ANSWER
[1684946047] libunbound[2439105:0] info: response for client.wvd.microsoft.com. A IN
[1684946047] libunbound[2439105:0] info: reply from <trafficmanager.net.> 13.107.222.240#53
[1684946047] libunbound[2439105:0] info: query response was CNAME
[1684946047] libunbound[2439105:0] info: resolving client.wvd.microsoft.com. A IN
[1684946047] libunbound[2439105:0] info: response for client.wvd.microsoft.com. A IN
[1684946047] libunbound[2439105:0] info: reply from <net.> 192.55.83.30#53
[1684946047] libunbound[2439105:0] info: query response was REFERRAL
[1684946047] libunbound[2439105:0] info: response for client.wvd.microsoft.com. A IN
[1684946047] libunbound[2439105:0] info: reply from <azurewebsites.net.> 150.171.21.224#53
[1684946047] libunbound[2439105:0] info: query response was CNAME
[1684946047] libunbound[2439105:0] info: resolving client.wvd.microsoft.com. A IN
[1684946047] libunbound[2439105:0] info: response for client.wvd.microsoft.com. A IN
[1684946047] libunbound[2439105:0] info: reply from <azurewebsites.net.> 2620:1ec:8ec:700::e0#53
[1684946047] libunbound[2439105:0] info: query response was nodata ANSWER
[1684946047] libunbound[2439105:0] info: response for client.wvd.microsoft.com. A IN
[1684946047] libunbound[2439105:0] info: reply from <azurewebsites.net.> 150.171.21.224#53
[1684946047] libunbound[2439105:0] info: query response was CNAME
[1684946047] libunbound[2439105:0] info: resolving client.wvd.microsoft.com. A IN
[1684946047] libunbound[2439105:0] info: response for client.wvd.microsoft.com. A IN
[1684946047] libunbound[2439105:0] info: reply from <net.> 2001:500:d937::30#53
[1684946047] libunbound[2439105:0] info: query response was REFERRAL
[1684946047] libunbound[2439105:0] info: response for client.wvd.microsoft.com. A IN
[1684946047] libunbound[2439105:0] info: reply from <windows.net.> 150.171.10.39#53
[1684946047] libunbound[2439105:0] info: query response was REFERRAL
[1684946047] libunbound[2439105:0] info: resolving ns4-05.azure-dns.info. AAAA IN
[1684946047] libunbound[2439105:0] info: resolving ns4-05.azure-dns.info. A IN
[1684946047] libunbound[2439105:0] info: response for ns4-05.azure-dns.info. AAAA IN
[1684946047] libunbound[2439105:0] info: reply from <info.> 2001:500:1c::1#53
[1684946047] libunbound[2439105:0] info: query response was REFERRAL
[1684946047] libunbound[2439105:0] info: response for ns4-05.azure-dns.info. A IN
[1684946047] libunbound[2439105:0] info: reply from <info.> 2001:500:1b::1#53
[1684946047] libunbound[2439105:0] info: query response was REFERRAL
[1684946047] libunbound[2439105:0] info: response for ns4-05.azure-dns.info. AAAA IN
[1684946047] libunbound[2439105:0] info: reply from <azure-dns.info.> 208.84.5.3#53
[1684946047] libunbound[2439105:0] info: query response was ANSWER
[1684946047] libunbound[2439105:0] info: response for ns4-05.azure-dns.info. A IN
[1684946047] libunbound[2439105:0] info: reply from <azure-dns.info.> 208.84.5.4#53
[1684946047] libunbound[2439105:0] info: query response was ANSWER
[1684946047] libunbound[2439105:0] info: response for ns4-05.azure-dns.info. AAAA IN
[1684946047] libunbound[2439105:0] info: reply from <azure-dns.info.> 2620:1ec:bda:700::2#53
[1684946047] libunbound[2439105:0] info: query response was ANSWER
[1684946047] libunbound[2439105:0] info: response for client.wvd.microsoft.com. A IN
[1684946047] libunbound[2439105:0] info: reply from <azurewebsites.windows.net.> 208.84.5.5#53
[1684946047] libunbound[2439105:0] info: query response was nodata ANSWER
[1684946047] libunbound[2439105:0] info: response for client.wvd.microsoft.com. A IN
[1684946047] libunbound[2439105:0] info: reply from <azurewebsites.windows.net.> 208.84.5.5#53
[1684946047] libunbound[2439105:0] info: query response was nodata ANSWER
[1684946047] libunbound[2439105:0] info: response for client.wvd.microsoft.com. A IN
[1684946047] libunbound[2439105:0] info: reply from <azurewebsites.windows.net.> 2620:1ec:bda:700::5#53
[1684946047] libunbound[2439105:0] info: query response was CNAME
[1684946047] libunbound[2439105:0] info: resolving client.wvd.microsoft.com. A IN
Host client.wvd.microsoft.com not found: 2(SERVFAIL). (error)

Here how its not working with systemd-resolved in Zorin 16.2:

resolvectl query client.wvd.microsoft.com
client.wvd.microsoft.com: resolve call failed: CNAME loop detected, or CNAME resolving disabled on 'waws-prod-am2-ce03ae4d.sip.p.azurewebsites.windows.net'

Public DNS resolvers and devices like the resolver in the fritzbox are not affected and resolve the name fine, thats why a dig @8.8.8.8 client.wvd.microsoft.com works fine.

As a workaround you can disable the usage of the systemd-resolved stub resolver by replacing the symlink /etc/resolv.conf with a different target:

sudo ln -sf /run/systemd/resolve/resolv.conf /etc/resolv.conf

And then it also works on Zorin 16:

chris@zorin:~$ host client.wvd.microsoft.com
client.wvd.microsoft.com is an alias for client.privatelink-global.wvd.microsoft.com.
client.privatelink-global.wvd.microsoft.com is an alias for client.privatelink.wvd.microsoft.com.
client.privatelink.wvd.microsoft.com is an alias for rdweb.wvd.microsoft.com.
rdweb.wvd.microsoft.com is an alias for rdweb.privatelink-global.wvd.microsoft.com.
rdweb.privatelink-global.wvd.microsoft.com is an alias for rdweb.privatelink.wvd.microsoft.com.
rdweb.privatelink.wvd.microsoft.com is an alias for rdweb-prod-geo.trafficmanager.net.
rdweb-prod-geo.trafficmanager.net is an alias for mrs-weur1c103-rdweb-prod.wvd-ase-weur1c103-prod.p.azurewebsites.net.
mrs-weur1c103-rdweb-prod.wvd-ase-weur1c103-prod.p.azurewebsites.net is an alias for waws-prod-am2-4fda7789.sip.p.azurewebsites.windows.net.
waws-prod-am2-4fda7789.sip.p.azurewebsites.windows.net is an alias for waws-prod-am2-4fda7789.cloudapp.net.
waws-prod-am2-4fda7789.cloudapp.net has address 40.68.18.120

This workaround survives reboots and according to the manpage(8) of systemd-resolved.service is also a proper way how to instruct systemd-resolved how to behave.

3 Likes

That worked! Thanks a lot for your great work!

Notice that the ultimate culprit is systemd. Would be curious to know if say you were running Antix which does not have any element of systemd that it would work flawlessly. It also would seem that now Poettinger is working for Microsoft, GNU/Linux is in more danger of being controlled by corporations instead of community led Operating Systems. To add more salt on the wound GNU/Linux devs could face heavy fines from Europe if an application does not work.