After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 779776 - Should be ported to libnm/libnma
Should be ported to libnm/libnma
Status: RESOLVED DUPLICATE of bug 789811
Product: gnome-shell
Classification: Core
Component: network-indicator
3.18.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2017-03-08 22:25 UTC by Michael Biebl
Modified: 2017-11-02 18:45 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Michael Biebl 2017-03-08 22:25:05 UTC
Like other GNOME components such as gnome-control-center [1] or gnome-intial-setup [2], gnome-shell should be ported from libnm-glib/libnm-gtk to libnm/libnm

This affects 

src/shell-network-agent.[ch]
js/ui/status/network.js
js/ui/components/networkAgent.js
js/misc/modemManager.js


[1] https://git.gnome.org/browse/gnome-control-center/commit/?id=9183d3494788486600856df5115f11486ecb20a8
[2] https://git.gnome.org/browse/gnome-initial-setup/commit/?id=c1d702360dbe9075e6ab2215bc01d5c9fd3451ed
Comment 1 Florian Müllner 2017-03-08 22:46:11 UTC
FWIW, I've had a work-in-progress branch for this for a while, but haven't found the time to finish it up.
Comment 2 Michael Biebl 2017-05-15 17:06:59 UTC
Hi Florian

(In reply to Florian Müllner from comment #1)
> FWIW, I've had a work-in-progress branch for this for a while, but haven't
> found the time to finish it up.

Has there been any progress?

With  https://bugzilla.gnome.org/show_bug.cgi?id=777179 fixed, gnome-shell seems to be the last GNOME component still requiring libnm-glib/libnm-util/libnm-gtk
Comment 3 Michael Biebl 2017-05-16 17:02:33 UTC
So, I ran into a nasty issue regarding a port to libnm. 
Apparently, there are a couple of extensions using the libnm-glib based typelib.

I used https://codesearch.debian.net/search?q=imports.gi.NetworkManager to find
 gnome-shell-extension-show-ip
 gnome-shell-extension-system-monitor
 gnome-shell-extension-disconnect-wifi
which are shipped in Debian. Search for "network" at  https://extensions.gnome.org/ there are probably a couple more.

For testing purposes I converted on those extensions to use the NM typelib.
This lead to a hard crash of gnome-shell, as mixing of libnm-glib/libnm-util and libnm is apparently not allowed:

Mai 16 06:44:00 pluto gnome-shell[1811]: JS LOG: System monitor applet init from /usr/share/gnome-shell/extensions/system-monitor@paradoxxx.zero.gmail.com
Mai 16 06:44:00 pluto gnome-shell[1811]: JS LOG: System monitor applet enabling
Mai 16 06:44:00 pluto gnome-shell[1811]: libnm-util symbols detected; Mixing libnm with libnm-util/libnm-glib is not supported
Mai 16 06:44:00 pluto kernel: traps: gnome-shell[1811] trap int3 ip:7fcd3b590261 sp:7fff04292630 error:0
Mai 16 06:44:00 pluto kernel:  in libglib-2.0.so.0.5000.3[7fcd3b540000+112000]
Mai 16 06:44:00 pluto gnome-session-binary[1469]: Unrecoverable failure in required component org.gnome.Shell.desktop

Florian, do you have any idea how we can solve this problem or ensure gnome-shell and the extensions are upgraded in lockstep?

I can reasonably solve that on the Debian side for extensions that have been installed via a package.
For extensions that have been installed via https://extensions.debian.org, it becomes trickier, especially since gnome-shell has disabled the version check for extensions since 3.22.
Comment 4 Marc-Antoine Perennou 2017-06-05 07:29:40 UTC
Isn't it possible to install come kind of override which just causes an error when trying to load the legacy APIs instead of actually loading them?
Comment 5 Michael Biebl 2017-06-17 21:50:41 UTC
Florian, any thoughts/updates?
Comment 6 Florian Müllner 2017-11-02 18:45:00 UTC
Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 789811 ***