I can confirm this is still an issue, here's GNOME's crash log:

Jun 12 21:26:23 KenoArchDesktop gnome-shell[1023]: JS ERROR: Error: Requiring Geoclue, version none: Typelib file for namespace 'Geoclue' (any version) not found
                                                   @resource:///org/gnome/shell/misc/weather.js:3:7
                                                   @resource:///org/gnome/shell/ui/dateMenu.js:10:7
                                                   @resource:///org/gnome/shell/ui/panel.js:819:5
                                                   @resource:///org/gnome/shell/ui/main.js:22:7
                                                   @<main>:1:31
Jun 12 21:26:23 KenoArchDesktop gnome-shell[1023]: Execution of main.js threw exception: Script <main> threw an exception
Jun 12 21:26:23 KenoArchDesktop org.gnome.Shell.desktop[1023]: (EE) failed to read Wayland events: Connection reset by peer
Jun 12 21:26:23 KenoArchDesktop gnome-session[982]: gnome-session-binary[982]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Jun 12 21:26:23 KenoArchDesktop gnome-session-binary[982]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Jun 12 21:26:23 KenoArchDesktop gnome-session-binary[982]: Unrecoverable failure in required component org.gnome.Shell.desktop

The issue is solved for me by the update of [nonprism/gnome-settings-daemon].

This issue can be closed.

i have coupled this issue and another to #1884 - gnome has always been troublesome for nonprism - im not sure what can be done

re this PKGBUILD: https://lists.parabola.nu/pipermail/dev/2019-August/007402.html

freemor - did you apply theova's changes?

theova - does this issue still exist?

theova - does this issue still exist?

I think the issue exists, if nonprism/gnome-settings-daemon has not the same version as the other gnome packages.
A while ago, the issue didn't exist. At the time you asked, it did.

I have sent the PKGBUILDS for nonprism/gnome-settings-daemon and nonprism/gnome-online-accounts to the mailing list.
Installing the newer version solves the issue for me again.

PKGBUILS:
https://lists.parabola.nu/pipermail/dev/2019-November/007490.html
https://lists.parabola.nu/pipermail/dev/2019-November/007491.html

I crowed to soon: When writing the last post, I had [geoclue] still installed. (But, still I think, the issue was gone a while ago.) Now, Gnome/Gdm does not start anymore...

I get the same error as kenogo:

$ journalctl /usr/bin/gnome-shell
...
Nov 16 15:38:35 RainbowWarrior gnome-shell[18291]: JS ERROR: Error: Requiring Geoclue, version none: Ty>
                                                   @resource:///org/gnome/shell/misc/weather.js:3:7
                                                   @resource:///org/gnome/shell/ui/dateMenu.js:11:7
                                                   @resource:///org/gnome/shell/ui/panel.js:774:5
                                                   @resource:///org/gnome/shell/ui/main.js:29:7
                                                   @<main>:1:31

Installing [extra/geoclue] and [nonprism/gnome-settings-daemon (v 3.34.1)] let me start gnome as usual. Furhermore the [nonprism/gnome-settings-daemon (v 3.34.1) builds fine.
I am interested to help to maintain [nonprism/gnome-settings-daemon] and work on this bug. But at the moment, I have no idea how to further investigate the issue.

Might it be a problem of [gnome-shell] ?

Any help would be highly appreciated.

Looks like I missed gnome-online-accounts. when bringing stuff up to date. I'll take a look

I've brought gnome-online-accounts up-to-date. Hope that fixes it but looking more closely at that error I'm wonderng is gnome-shell itself now requires geoclue

Hmmmm.....

Looks like the geoclue2 list might be growing:

├─gnome-clocks
├─gnome-initial-setup
├─gnome-maps
├─gnome-settings-daemon
├─gnome-weather

Might be easier to do a tiny nudge to geoclue to make it always return a location in the middle of the Pacific Ocean. then just put that in as nonprism/geoclue
be less work to maintain that then chase down everything that keeps adding geoclue support

Looking at geoclue. It has both a geoclue.conf file with a fair bit of granularity and
many build options to disable a bunch of stuff. a geoclue that returns a mock or no location may not be that hard

freemor wrote:

I've brought gnome-online-accounts up-to-date. Hope that fixes it but looking more closely at that error I'm wonderng is gnome-shell itself now requires geoclue

I will have a look at it. At least 'gnome-shell' does not have a direct/indirect dependency of geoclue when having enabled [nonprism].

freemor wrote:

Looking at geoclue. It has both a geoclue.conf file with a fair bit of granularity and
many build options to disable a bunch of stuff. a geoclue that returns a mock or no location may not be that hard

Yes, that might be easier.

It is proposed here to just mask geoclue as follows:

sudo systemctl disable geoclue.service
sudo systemctl mask geoclue.service

Probably this should be discussed in a new issue/on the mailing list?

briliant - make it nova-scotia - or saskatuan - no one lives there :)

even better: the south pole (-1,-1,-1); where the clocks always read: 'NaN' - tip of the hat to penguins

I like the south pole idea. (because of the penguins :) )

I think creating a neutered version of geoclue would be better fo several reasons. but I'll follow your suggestion and move this part of the discussion over to the mailing list.

I am still not able to start gnome.

Version of involved packages:

pacman -Qi gnome-shell | grep Version                                              
Version         : 1:3.34.2-1

pacman -Qi gnome-settings-daemon | grep Version
Version         : 3.34.1+1+ge1fc4599-1.nonprism1

pacman -Qi gnome-online-accounts| grep Version
Version         : 3.34.1-1.nonprism1

(gnome-settings-daemon is the package as proposed on the mailing list).

By searching the gnome-shell repository I found, that gnome-shell has not a small amount of code related to geoclue. So the probable dependency of gnome-shell seems more and more likely to me.

Are we clear about patching gnome packages vs. patching geoclue?

If we patch geoclue, what is the status? Then I can put more effort into that.

just as a cross-reference, this is a link to the discussion regarding geoclue

https://lists.parabola.nu/pipermail/dev/2019-November/007513.html

i just installed GNOME (without nonprism) and all three of the pre-configured sessions (gnome, gnome+xorg, gnome-classic) started with no problem

$ pacman -Qi gnome-shell gnome-settings-daemon gnome-online-accounts  | grep -E 'Name|Repository|Version'
Name            : gnome-shell
Version         : 1:3.34.2-1
Name            : gnome-settings-daemon
Version         : 3.34.1+1+ge1fc4599-1
Name            : gnome-online-accounts
Version         : 3.34.1-1

after enabling [nonprism],and syncing without downgrades, GNOME still ran fine

# pacman -Syu
Packages (6) evolution-data-server-3.34.2-1.nonprism1
             gnome-online-accounts-3.34.1-1.nonprism1
             icedove-1:68.2.2-2.parabola1.nonprism1
             libpurple-2.13.0-9.nonprism2  pidgin-2.13.0-9.nonprism2
             webkit2gtk-2.26.2-2.nonprism1

after the downgrades, GNOME does not start - so this could be just a matter of putting 'gnome-settings-daemon' at the same version as gnome-shell

# pacman -Syuu
warning: gnome-settings-daemon: downgrading from version 3.34.1+1+ge1fc4599-1 to version 3.32.1-1.nonprism1
warning: gnome-weather: downgrading from version 3.34.0-1 to version 3.26.0-1.nonprism1
warning: grilo-plugins: downgrading from version 0.3.10-1 to version 0.3.5-1.nonprism1
Packages (3) gnome-settings-daemon-3.32.1-1.nonprism1
             gnome-weather-3.26.0-1.nonprism1  grilo-plugins-0.3.5-1.nonprism1

after installing gnome-settings-daemon per theova's PKGBUILD, gnome is running as expected

re: https://lists.parabola.nu/pipermail/dev/2019-December/007577.html

Most helpful right now would be if Theova and others could grab the patched geoclue2 and test it to see if things like gnome-weather etc, etc, etc can determine their location.

Some thing may have multiple ways of doing so and geoclue returning "location unavailable" might trigger the fall backs so that would need to be teased out too.
Tho as pointed out by others completely hiding location without something hiding your IP and not using JS is a very hard task.

bill-auger wrote:

after installing gnome-settings-daemon per theova's PKGBUILD, gnome is running as expected

I can reprduce your report. However the point is, that after installing [your-privacy] and thus removing [geoclue], I am no more able to start gnome. (I tried also a new patched version 3.34.2 of gnome-settings-daemon)

freemor wrote:

Most helpful right now would be if Theova and others could grab the patched geoclue2 and test it to see if things like gnome-weather etc, etc, etc can determine their location.

Ok, I'll test it.