Packaging request #2128
Bug #1884: nonprism and gnome
[nonprism/gnome-online-accounts]: Cannot start GNOME after activating nonprism
After having activated nonprism in /etc/pacman.conf and downgrading the system to the nonprism-packages, I cannot start gnome-session anymore from the tty.
The following packages were downgraded (pacman -Syuu):
warning: evolution-data-server: downgrading from version 3.30.3-1 to version 3.28.5-2.nonprism1 warning: gnome-online-accounts: downgrading from version 3.30.0-1 to version 3.28.0-1.nonprism1 warning: gnome-settings-daemon: downgrading from version 188.8.131.52-1 to version 3.26.2-1.nonprism1 warning: grilo-plugins: downgrading from version 0.3.8-1 to version 0.3.5-1.nonprism1 warning: webkit2gtk: downgrading from version 2.22.5-1 to version 2.22.4-1.nonprism1
Deactivating nonprism and upgrading let me start gnome again.
I don't know, which of them is the cause of the problem... Please tell me, If I should provide more logs.
I can confirm this is still an issue, here's GNOME's crash log:
Jun 12 21:26:23 KenoArchDesktop gnome-shell: 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: Execution of main.js threw exception: Script <main> threw an exception Jun 12 21:26:23 KenoArchDesktop org.gnome.Shell.desktop: (EE) failed to read Wayland events: Connection reset by peer Jun 12 21:26:23 KenoArchDesktop gnome-session: gnome-session-binary: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Jun 12 21:26:23 KenoArchDesktop gnome-session-binary: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Jun 12 21:26:23 KenoArchDesktop gnome-session-binary: Unrecoverable failure in required component org.gnome.Shell.desktop
Updated by bill-auger 6 months ago
- Priority changed from bug to wish
- Tracker changed from Bug to Packaging request
i have not looked into this; but offhand, i will guess that this is not a bug really - it is probably just the [nonprism] packages doing their intended job of preventing privacy leaks
the error above shows that the 'geoclue' program is not found - 'geoclue' is a geo-location program which is considered to be privacy-invasive; so that is something that the [nonprism] repos exists specifically to remove
perhaps gnome can be made to function without that feature; but for now it appears that gnome can not be used with the [nonprism] repos - assuming this is some new feature, i will mark this as a packaging request until we know more - it could be a bug though, if this is a regression that was addressed in this past
Updated by bill-auger about 1 month ago
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?
Updated by freemor about 1 month ago
- % Done changed from 0 to 40
- Priority changed from wish to broken
- Status changed from fixed to in progress
nonprism/evolution-data-server x86_64 and i686 now up-to-date
nonprism/gnome-settings-daemon x86_64 and i686 now up-to-date
nonprism/webkit2gtk on i686 is still lagging I'll need to bring the no-SSE stuff over from Arch32 and rebuild it (hopefully Wednesday.
Will build the ARMv7h packages when I get a few moments to fire them up on Beefcake
Bill-Auger if you have whatever VM srill rolled can you see if gnome+nonprism on x86_64 now functions. Just don't have time to roll one right now and i am busy tomorow.
Updated by theova about 1 month ago
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.
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: 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 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
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].
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?