Project

General

Profile

Freedom Issue #3303

Pacage "kguiaddons" has references to Google Maps

martie - almost 2 years ago - . Updated almost 2 years ago.

Status:
confirmed
Priority:
bug
Assignee:
-
% Done:

0%

Description

  • steps to reproduce:

pacman -S dolphin
pacman -Qo /usr/share/applications/google-maps-geo-handler.desktop

  • actual result:

Mentioned file is owned by kguiaddons

After installing file manager Dolphin this package installed as a dependency.

This package added desktop file which only use is to access Google Maps

History

#1

Updated by bill-auger almost 2 years ago

  • Status changed from unconfirmed to confirmed
  • Description updated (diff)
$ grep -v ^Name /usr/share/applications/google-maps-geo-handler.desktop
[Desktop Entry]
Type=Application
Exec=kde-geo-uri-handler --coordinate-template "https://www.google.com/maps/@<LAT>,<LON>,<Z>" --query-template "https://www.google.com/maps/search/<Q>" --fallback "https://www.google.com/maps/" %u
Icon=map-globe
MimeType=x-scheme-handler/geo;
Terminal=false
NoDisplay=true

it would be important to know what this is used for - the desktop file itself would not access anything - it is a URI handler

if it does nothing unless invoked by the user, its probably not a problem - but it could be used as an unattended geo-location feature in some client programs, which would be an anti-feature (WRT to those program, not necessarily this package)

#2

Updated by bill-auger almost 2 years ago

  • File deleted (kguiaddons.txt)
#3

Updated by martie almost 2 years ago

"if it does nothing unless invoked by the user, its probably not a problem" - isn't it still proposing non-libre software, which is prohibited by Free System Distribution Guidelines?

#4

Updated by bill-auger almost 2 years ago

it is accessing data from a remote service - remote services are neither free nor non-free, according to the four freedoms; because the software in question, is running on someone else's computer

if remote services pose any conflict with the FSDG, it is either because they are SaaSS, or because the connections are not initiated or known by the user (an anti-feature)

i dont believe that geo-location qualifies as SaaSS - it may; but i dont recall anyone suggesting that it does - it is usually more of a privacy concern; but only if the local software contacts the geo-location server without the user's knowledge

Also available in: Atom PDF