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#60770 - [nm-connection-editor] 1.8.19dev+21+geebf7f95-1 breaks gnome-shell startup

Attached to Project: Arch Linux
Opened by Stijn Opheide (stijnopheide) - Sunday, 11 November 2018, 15:37 GMT
Last edited by Jan de Groot (JGC) - Friday, 10 May 2019, 08:23 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Jan Alexander Steffens (heftig)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description: When nm-connection-editor 1.8.19dev is installed, it breaks startup of the gnome-shell. The system boots normally until the graphical user interface target is reached and a black screen with cursor is shown. The mouse pointer is visible too and can be moved. You can switch to another tty.

I believe the relevant lines in the log are:
Nov 11 11:04:01 herz gnome-shell[780]: JS ERROR: Error: Requiring NMA, version none: Typelib file for namespace 'NMA' (any version) not found
@resource:///org/gnome/shell/misc/modemManager.js:5:7
@resource:///org/gnome/shell/ui/status/network.js:20:7
_init@resource:///org/gnome/shell/ui/panel.js:706:13
wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
_Base.prototype._construct@resource:///org/gnome/gjs/modules/_legacy.js:18:5
newClass@resource:///org/gnome/gjs/modules/_legacy.js:114:32
_ensureIndicator@resource:///org/gnome/shell/ui/panel.js:1132:25
wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
_updateBox@resource:///org/gnome/shell/ui/panel.js:1143:29
wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
_updatePanel@resource:///org/gnome/shell/ui/panel.js:1053:9
wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
_init@resource:///org/gnome/shell/ui/panel.js:831:9
wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
_Base.prototype._construct@resource:///org/gnome/gjs/modules/_legacy.js:18:5
newClass@resource:///org/gnome/gjs/modules/_legacy.js:114:32
_initializeUI@resource:///org/gnome/shell/ui/main.js:184:13
start@resource:///org/gnome/shell/ui/main.js:133:5
@<main>:1:31
Nov 11 11:04:01 herz gnome-shell[780]: Execution of main.js threw exception: Script <main> threw an exception
Nov 11 11:04:01 herz gnome-shell[780]: g_param_spec_unref: assertion 'G_IS_PARAM_SPEC (pspec)' failed
Nov 11 11:04:01 herz gnome-shell[780]: g_param_spec_unref: assertion 'G_IS_PARAM_SPEC (pspec)' failed
...
Nov 11 11:04:01 herz gnome-shell[780]: g_param_spec_unref: assertion 'G_IS_PARAM_SPEC (pspec)' failed
Nov 11 11:04:01 herz gnome-shell[780]: g_param_spec_unref: assertion 'G_IS_PARAM_SPEC (pspec)' failed
Nov 11 11:04:01 herz gnome-shell[780]: g_param_spec_unref: assertion 'G_IS_PARAM_SPEC (pspec)' failed
Nov 11 11:04:01 herz org.gnome.Shell.desktop[780]: (EE) failed to read Wayland events: Connection reset by peer
Nov 11 11:04:01 herz gnome-session[772]: gnome-session-binary[772]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Nov 11 11:04:01 herz gnome-session-binary[772]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Nov 11 11:04:01 herz gnome-session-binary[772]: Unrecoverable failure in required component org.gnome.Shell.desktop
Nov 11 11:04:01 herz at-spi-bus-launcher[1715]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":1024"
Nov 11 11:04:01 herz at-spi-bus-launcher[1715]: after 21 requests (21 known processed) with 0 events remaining.
Nov 11 11:04:01 herz gdm[473]: GdmDisplay: display lasted 2.313664 seconds

The entire journalctl file of the boot is attached.

Additional info:
* I will report on the last working version, 1.8.16-1 is definitely still ok. Will have to test 1.8.18-1 and 1.8.18-2 later today.
* I did not find any upstream bugs, however I found an (I believe) identical issue in ClearLinux: https://github.com/clearlinux/clr-bundles/issues/52 and a discussion on the ubuntu forums https://ubuntuforums.org/archive/index.php/t-2385745.html

Downgrading to 1.8.16-1 works. Pacman log:
[2018-11-11 11:29] [PACMAN] Running 'pacman -R libnma'
[2018-11-11 11:29] [PACMAN] Running 'pacman -R libnma nm-connection-editor'
[2018-11-11 11:32] [PACMAN] Running 'pacman -U /var/cache/pacman/pkg/nm-connection-editor-1.8.16-1-x86_64.pkg.tar.xz'
[2018-11-11 11:32] [ALPM] transaction started
[2018-11-11 11:32] [ALPM] removed libnm-gtk (1.8.19dev+21+geebf7f95-1)
[2018-11-11 11:32] [ALPM] downgraded nm-connection-editor (1.8.19dev+21+geebf7f95-1 -> 1.8.16-1)
[2018-11-11 11:32] [ALPM] transaction completed
[2018-11-11 11:32] [ALPM] running 'glib-compile-schemas.hook'...
[2018-11-11 11:32] [ALPM] running 'gtk-update-icon-cache.hook'...
[2018-11-11 11:32] [ALPM] running 'systemd-update.hook'...
[2018-11-11 11:32] [ALPM] running 'update-desktop-database.h

I'm unsure if this issue is related to nm-connection-editor, libnm-gtk or libnma or the upgrade/replacement of any of them.
This task depends upon

Closed by  Jan de Groot (JGC)
Friday, 10 May 2019, 08:23 GMT
Reason for closing:  Fixed
Comment by Stijn Opheide (stijnopheide) - Tuesday, 20 November 2018, 10:23 GMT
Last working version is 1.8.18-1.
As of version 1.8.18-2 the dependency libnm-gtk-1.8.19dev+21+geebf7f95-1 is installed and startup of gnome is broken.
Comment by Jan Alexander Steffens (heftig) - Monday, 10 December 2018, 18:21 GMT
Is libnma not installed? It's a dependency of nm-connection-editor.
Comment by Stijn Opheide (stijnopheide) - Friday, 14 December 2018, 15:22 GMT
Hi Jan,

yes, it is installed:

❯ pacman -Qi libnma
Name : libnma
Version : 1.8.19dev+21+geebf7f95-1
Description : NetworkManager GUI client library
Architecture : x86_64
URL : https://wiki.gnome.org/Projects/NetworkManager/
Licenses : GPL LGPL
Groups : None
Provides : None
Depends On : libnm gcr gtk3 iso-codes mobile-broadband-provider-info
Optional Deps : None
Required By : None
Optional For : None
Conflicts With : None
Replaces : None
Installed Size : 709.00 KiB
Packager : Jan Alexander Steffens (heftig) <jan.steffens@gmail.com>
Build Date : Sat 27 Oct 2018 18:52:49 CEST
Install Date : Thu 08 Nov 2018 14:42:00 CET
Install Reason : Installed as a dependency for another package
Install Script : No
Validated By : Signature

When I upgrade / downgrade nm-connection-editor, libnm-gtk gets installed too. Here are the relevant sections from pacman.log

[2018-11-20 11:16] [PACMAN] Running 'pacman -U /var/cache/pacman/pkg/nm-connection-editor-1.8.18-2-x86_64.pkg.tar.xz'
[2018-11-20 11:16] [ALPM] transaction started
[2018-11-20 11:16] [ALPM] installed libnm-gtk (1.8.19dev+21+geebf7f95-1)
[2018-11-20 11:16] [ALPM] upgraded nm-connection-editor (1.8.18-1 -> 1.8.18-2)
[2018-11-20 11:16] [ALPM] transaction completed
[2018-11-20 11:16] [ALPM] running 'glib-compile-schemas.hook'...
[2018-11-20 11:16] [ALPM] running 'gtk-update-icon-cache.hook'...
[2018-11-20 11:16] [ALPM] running 'systemd-update.hook'...
[2018-11-20 11:16] [ALPM] running 'update-desktop-database.hook'...

>> rebooted here, fails with the error from the bug report.

[2018-11-20 11:19] [PACMAN] Running 'pacman -U /var/cache/pacman/pkg/nm-connection-editor-1.8.18-1-x86_64.pkg.tar.xz'
[2018-11-20 11:20] [ALPM] transaction started
[2018-11-20 11:20] [ALPM] removed libnm-gtk (1.8.19dev+21+geebf7f95-1)
[2018-11-20 11:20] [ALPM] downgraded nm-connection-editor (1.8.18-2 -> 1.8.18-1)
[2018-11-20 11:20] [ALPM] transaction completed
[2018-11-20 11:20] [ALPM] running 'glib-compile-schemas.hook'...
[2018-11-20 11:20] [ALPM] running 'gtk-update-icon-cache.hook'...
[2018-11-20 11:20] [ALPM] running 'systemd-update.hook'...
[2018-11-20 11:20] [ALPM] running 'update-desktop-database.hook'...

Between upgrading/downgrading nm-connection-editor there is no change in the installed libnma
Comment by Emiliano (esauvisky) - Sunday, 30 December 2018, 21:48 GMT
Can confirm, this has been happening to me since the release of gnome-shell 3.30 on august.
I have both libnm 1.14.1dev and libnma 1.8.18-2 installed. Journal output is identical to OP's.
Updating nm-connection-editor 1.8.18-2 prompts to install libnm-gtk 1.8.18-2.
Downgrading nm-connection-editor to 1.8.18-1 solves the problem.

(Thanks for finding the culprit, had my system frozen on an august snapshot w/o updates because of this!)
Comment by Jan Alexander Steffens (heftig) - Sunday, 30 December 2018, 21:50 GMT
gnome-shell is fine here. I can't reproduce your problem.
Comment by Stijn Opheide (stijnopheide) - Tuesday, 12 February 2019, 13:00 GMT
Can confirm problem still persists in version 1.8.20-1. Workaround also still works.
Comment by Jan de Groot (JGC) - Tuesday, 12 February 2019, 15:13 GMT
Can't reproduce and there's no such package as libnm-gtk anymore.
Comment by Stijn Opheide (stijnopheide) - Sunday, 03 March 2019, 19:31 GMT
Hi Jan,

what other information would you need to investigate this problem?
Comment by Eli Schwartz (eschwartz) - Monday, 04 March 2019, 00:01 GMT
An explanation for how you could possibly get the following error:

Nov 11 11:04:01 herz gnome-shell[780]: JS ERROR: Error: Requiring NMA, version none: Typelib file for namespace 'NMA' (any version) not found

This is saying that it's fatally erroring due to being unable to import the file /usr/lib/girepository-1.0/NMA-1.0.typelib

You've asserted that you have the libnma package installed on your system, as you should. So then, why doesn't libnma actually work on your system? Do you have mismatched versions of things installed? Is the .typelib file actually present on your system, as pacman -Qi libnma says it should be?

...

Regarding the "identical issues" you found for clearlinux and Ubuntu... you're right, those are both the exact same issue. In both cases, another Linux distribution *incorrectly* did not have a package dependency on the libnma typelib, and in both cases, the distribution fixed the issue by... adding a dependency on the typelib.

Arch Linux has always had a dependency on the typelib, so this has never been broken for us. If it is broken for you, then it is because your system has a broken installation of libnma.
Comment by Stijn Opheide (stijnopheide) - Thursday, 14 March 2019, 12:30 GMT
Thanks Eli, that explanation helped me fix the issue.

Indeed, there was no file /usr/lib/girepository-1.0/NMA-1.0.typelib on my system, although pacman -Qi libnma did report libnma being installed.
After running pacman -S libnma (which displayed a few warnings, see attachment), the file is present and gnome starts as expected.

Now, as to what might have gone wrong: before upgrading to nm-connection-editor 1.8.19dev, my system was about 5 to 6 months behind. Is it possible that the order in which packages are installed / uninstalled played a role in the file not being there? This might also explain why there weren't any other bug reports about this specific issue.

Anyway, problem is solved, as a summary if people encounter this issue, manually updating libnma after a pacman -Syu will solve it.

Thanks for the help!

cheers,
Stijn.
Comment by Emiliano (esauvisky) - Thursday, 14 March 2019, 16:11 GMT
Unfortunately it still doesn't work for me.

The typelib file exists in my system, I have libnma 1.8.21dev+3+gb4c365b1-1 installed, and when I tried updating nm-connection-editor to 1.8.21dev+3+gb4c365b1-1 the issue came back:

mar 14 12:47:48 emi-arch gnome-shell[2532]: JS ERROR: Error: Requiring NMA, version none: Typelib file for namespace 'NMA' (any version) not found
@resource:///org/gnome/shell/misc/modemManager.js:5:7
@resource:///org/gnome/shell/ui/status/network.js:20:7
_init@resource:///org/gnome/shell/ui/panel.js:706:13
wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
_Base.prototype._construct@resource:///org/gnome/gjs/modules/_legacy.js:18:5
newClass@resource:///org/gnome/gjs/modules/_legacy.js:114:32
_ensureIndicator@resource:///org/gnome/shell/ui/panel.js:1133:25
wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
_updateBox@resource:///org/gnome/shell/ui/panel.js:1144:29
wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
_updatePanel@resource:///org/gnome/shell/ui/panel.js:1053:9
wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
_init@resource:///org/gnome/shell/ui/panel.js:831:9
wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
_Base.prototype._construct@resource:///org/gnome/gjs/modules/_legacy.js:18:5
newClass@resource:///org/gnome/gjs/modules/_legacy.js:114:32
_initializeUI@resource:///org/gnome/shell/ui/main.js:184:13
start@resource:///org/gnome/shell/ui/main.js:133:5
@<main>:1:31
mar 14 12:47:48 emi-arch gnome-shell[2532]: Execution of main.js threw exception: Script <main> threw an exception
mar 14 12:47:48 emi-arch gnome-session[2291]: gnome-session-binary[2291]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
mar 14 12:47:48 emi-arch gnome-session[2291]: gnome-session-binary[2291]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly
mar 14 12:47:48 emi-arch gnome-session-binary[2291]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
mar 14 12:47:48 emi-arch gnome-session-binary[2291]: Unrecoverable failure in required component org.gnome.Shell.desktop


How is it possible that the file is still not being found? Any ideas how could I attempt to debug it a bit more?


Also, my problem also began after leaving the system without updating for a couple months, so there's something in common.
@stijnopheide, could you please tell me exactly which versions of the packages libnma and nm-connection-editor are working for you right now?
Comment by Stijn Opheide (stijnopheide) - Saturday, 16 March 2019, 08:16 GMT
Name : libnma
Version : 1.8.21dev+3+gb4c365b1-1

Name : nm-connection-editor
Version : 1.8.21dev+3+gb4c365b1-1

this works for me now.
Comment by Emiliano (esauvisky) - Wednesday, 08 May 2019, 00:37 GMT
Still having this issue on Gnome 3.32.

Somehow I got a broken installation with no fallback besides freezing nm-connection-editor@1.8.16-1, which most likely is root cause of several connection issues I'm having lately :(

Any ideas on how could I force a "clean reinstall" or where to find more verbose information?
Comment by Emiliano (esauvisky) - Wednesday, 08 May 2019, 22:01 GMT
Issue was fixed by manually upgrading and compiling nm-connection-editor to the latest git version via AUR.

These are the relevant package versions installed via AUR:
network-manager-applet-git 1.8.21.dev.r56.gcc3893be-1
networkmanager-git 1.19.2.r23116.gdb46d9b82-1
nm-connection-editor-git 1.8.21.dev.r56.gcc3893be-1
libnm-git 1.19.2.r23116.gdb46d9b82-1
libnm-gtk-git 1.8.21.dev.r56.gcc3893be-1
libnma-git 1.8.21.dev.r56.gcc3893be-1
Comment by Jan de Groot (JGC) - Friday, 10 May 2019, 08:22 GMT
You're using git snapshots of networkmanager from the unstable development branch. As you're not using the official packages, we cannot support this.

We cannot reproduce this and Stijn mentions it's fixed on his system, so I'm closing this bug now.

Loading...