Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#63352 - [gnome-shell] gnome-shell fails to start

Attached to Project: Arch Linux
Opened by Norbert Pfeiler (npfeiler) - Saturday, 03 August 2019, 17:06 GMT
Last edited by Eli Schwartz (eschwartz) - Monday, 23 September 2019, 13:15 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

Description:
Aug 03 18:55:37 mobile gnome-shell[1102]: JS ERROR: Error: No signal 'captured-event::nonmotion' on object 'MetaStage'
TouchpadWorkspaceSwitchAction<@resource:///org/gnome/shell/ui/windowManager.js:464:9
WindowManager<@resource:///org/gnome/shell/ui/windowManager.js:1069:19
_initializeUI@resource:///org/gnome/shell/ui/main.js:166:10
start@resource:///org/gnome/shell/ui/main.js:124:5
@<main>:1:31
Aug 03 18:55:37 mobile gnome-shell[1102]: Execution of main.js threw exception: Script <main> threw an exception
Aug 03 18:55:37 mobile gnome-session[1072]: gnome-session-binary[1072]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Aug 03 18:55:37 mobile gnome-session-binary[1072]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1


gnome-shell 1:3.32.2+11+g1c6abf378-1

downgrading to 1:3.32.2+6+g8b9874089-1 fixes the problem


Steps to reproduce:
update, reboot
This task depends upon

Closed by  Eli Schwartz (eschwartz)
Monday, 23 September 2019, 13:15 GMT
Reason for closing:  Not a bug
Additional comments about closing:  The gnome ecosystem on Arch relies on using the exact same commits for everything, AUR packages are responsible for making sure they match the rest of the ecosystem in the official repos.
Comment by Kristof Jozsa (kjozsa) - Sunday, 04 August 2019, 15:01 GMT
issue confirmed, same problem, same resolution. That's a blocker, it renders the whole desktop environment completely unusable, possibly causing headaches for many newcomers :|
Comment by Daniel Landau (dlandau) - Monday, 05 August 2019, 12:09 GMT
I disagree strongly with "Severity: Low". This renders the whole system useless, even GDM refused to start.
Comment by Norbert Pfeiler (npfeiler) - Tuesday, 06 August 2019, 13:48 GMT
I’m using a custom mutter package (based on 3.32.2). Unfortunately the current extra/mutter PKGBUILD doesn’t build so i cannot update it:
fatal: bad object a2507cd51a248e2ee50eb64479f47e5da2564535

From a repo perspective i can understand that the combination of random git packages is working, but it’s definitely annoying when you try to work with it outside of that.
It would definitely help if the package specified that it relied on a specific (git) version of another package.
Also, i’m not sure i like that some patches are applied here that are not only regression/severe bug fixes.

I kinda expect to get upstream version of software. (official Arch philosophy could be argued here)

With all that, i’m not even sure updating mutter would fix the issue now, just figured from the correlating changes…
Comment by Kristof Jozsa (kjozsa) - Sunday, 25 August 2019, 10:48 GMT
I suspect that the package `mutter-topicons-cpu-use-fix` was causing the problem. Once replacing this one with `extra/mutter`, I no longer have issues with gnome-shell 1:3.32.2+11+g1c6abf378-1.
Comment by Eli Schwartz (eschwartz) - Sunday, 25 August 2019, 18:20 GMT
So just to be clear, the problem only manifests when using a custom mutter package?

The solution seems clear: your custom mutter package must use the same git commit as the [extra] package.

(And no, I don't happen to agree with packaging non-release commits for software, you will notice that that is only common in the gnome desktop stack, but I'm sure the gnome ecosystem maintainer has his reasons, so there is nothing to be done here unless the actual repository packages are broken.)

> I’m using a custom mutter package (based on 3.32.2). Unfortunately the current extra/mutter PKGBUILD doesn’t build so i cannot update it:
fatal: bad object a2507cd51a248e2ee50eb64479f47e5da2564535

Please open a separate bug report about this. Packages which no longer build from source are definitely problems.
Comment by Daniel Landau (dlandau) - Monday, 23 September 2019, 12:18 GMT
I think this can be closed now as gnome-shell 3.34 is out and using a 3.32 mutter with it fails to start with a missing .so error. Using only packages from [extra] is not broken.

Loading...