Bug 418128 - location.services.mozilla.com
Summary: location.services.mozilla.com
Status: RESOLVED DUPLICATE of bug 419677
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_nightcolor (show other bugs)
Version: 5.14.3
Platform: Debian unstable Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-02-24 10:03 UTC by arne anka
Modified: 2020-07-14 21:45 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
location.services.mozilla.com (53.70 KB, image/png)
2020-02-24 10:03 UTC, arne anka
Details

Note You need to log in before you can comment on or make changes to this bug.
Description arne anka 2020-02-24 10:03:50 UTC
Created attachment 126371 [details]
location.services.mozilla.com

I go to
System Settings -> Display and Monitor -> Display Configuration
and popup appears telling me that something is wrong with an SSL request to

location.services.mozilla.com

I tested with a few other settings entries, bit it is consistently the Display and Monitor entry that pops the error (and a rather useless at that -- what is one to do with "NO, there were errors: Unknown error" anyway?).

a) why is the display setup causing a request to location.services.mozilla.com?
b) why is Plasma issuing a request to location.services.mozilla.com at all without asking for consent prior to it?

SOFTWARE/OS VERSIONS
Linux 5050pc002 5.4.0-4-amd64 #1 SMP Debian 5.4.19-1 (2020-02-13) x86_64 GNU/Linux
KDE Plasma Version: 5.17.5
KDE Frameworks Version: 5.62.0
Qt Version: 5.12.5
Comment 1 Daniel 2020-07-14 21:45:17 UTC
a) Mozilla Location services are used when using the automatic time night color feature. KDE's data provider's geolocation module does the request

b) I opened a report a while ago which address this issue: 419677

I fully agree, that no unapparent third party requests should be made.

You can disable the third party request by manually specifiyng  the location you are at.

*** This bug has been marked as a duplicate of bug 419677 ***