"unable to load VPN connection editor" when adding VPN connection

Bug #1992475 reported by Eduard Kachur
50
This bug affects 11 people
Affects Status Importance Assigned to Milestone
network-manager-fortisslvpn (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu
Description: Ubuntu Kinetic Kudu (development branch)
Release: 22.10
2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center
network-manager-fortisslvpn:
  Installed: 1.2.10-0ubuntu3
  Candidate: 1.2.10-0ubuntu3
  Version table:
 *** 1.2.10-0ubuntu3 500
        500 http://ua.archive.ubuntu.com/ubuntu kinetic/universe amd64 Packages
        100 /var/lib/dpkg/status
network-manager-fortisslvpn-gnome:
  Installed: 1.2.10-0ubuntu3
  Candidate: 1.2.10-0ubuntu3
  Version table:
 *** 1.2.10-0ubuntu3 500
        500 http://ua.archive.ubuntu.com/ubuntu kinetic/universe amd64 Packages
        100 /var/lib/dpkg/status

3) What you expected to happen
When adding a VPN connection for Forti, configuration GUI appears.

4) What happened instead
unable to load VPN connection editor message in Identity tab
/var/log/syslog

Oct 11 16:22:42 ekachur-nout gnome-control-c[4110]: A floating object was finalized. This means that someone#012called g_object_unref() on an object that had only a floating#012reference; the initial floating reference is not owned by anyone#012and must be removed with g_object_ref_sink().
Oct 11 16:22:42 ekachur-nout gnome-control-c[4110]: message repeated 5 times: [ A floating object was finalized. This means that someone#012called g_object_unref() on an object that had only a floating#012reference; the initial floating reference is not owned by anyone#012and must be removed with g_object_ref_sink().]
Oct 11 16:22:45 ekachur-nout systemd[2532]: Started Application launched by gnome-session-binary.
Oct 11 16:22:47 ekachur-nout gnome-control-c[4110]: invalid (NULL) pointer instance
Oct 11 16:22:47 ekachur-nout gnome-control-c[4110]: g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
Oct 11 16:22:47 ekachur-nout gnome-control-c[4110]: file properties/nm-fortisslvpn-editor.c: line 484 (nm_fortisslvpn_editor_new): should not be reached
Oct 11 16:22:58 ekachur-nout gnome-shell[2649]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in network-manager-fortisslvpn (Ubuntu):
status: New → Confirmed
Revision history for this message
Marius Gedminas (mgedmin) wrote :

> Oct 11 16:22:47 ekachur-nout gnome-control-c[4110]: file properties/nm-fortisslvpn-editor.c: line 484 (nm_fortisslvpn_editor_new): should not be reached

This indicates that nm-fortisslvpn-dialog.ui could not be loaded. nm-fortisslvpn-dialog.ui has

    <requires lib="gtk+" version="3.4"/>

gnome-control-center in Ubuntu 22.10 uses GTK 4, not GTK 3.

The Ubuntu package is based on bersion 1.2.10, which is 3 years old. Upstream has ported to GTK 4 already. I think this package needs a SRU on the basis that this bug makes it unusable.

(Debian is still stuck on version 1.2.8, ouch.)

Revision history for this message
Eduard Kachur (glite) wrote :
Revision history for this message
Eduard Kachur (glite) wrote :
Revision history for this message
Milos Ivanovic (mivanovic) wrote :

This bug also affects Ubuntu 23.04.

Revision history for this message
Boris Erdmann (boris-erdmann) wrote :

Can confirm it affects Ubuntu 23.04.
Can confirm the above workaround using the Debian Bookworm packages.

Revision history for this message
P.Constantine (pconstantine) wrote :

I can confirm that workaround does NOT work on 22.04
Because it requires `libnma-gtk4-0` which does not exist in 22.04

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.