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 768270 - sigbart in create_info_label_security
sigbart in create_info_label_security
Status: RESOLVED OBSOLETE
Product: NetworkManager
Classification: Platform
Component: nm-applet
1.2.x
Other Linux
: Normal normal
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2016-07-01 09:08 UTC by Sebastien Bacher
Modified: 2020-11-12 14:25 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Sebastien Bacher 2016-07-01 09:08:11 UTC
The bug has been reported in the Ubuntu error tracker and started since the backported some 1.2 fixes to our 1.2.0 stable version, including that one

https://git.gnome.org/browse/network-manager-applet/commit/?h=nma-1-2&id=1fe93d23fac15bdaaca4c51e526725616a15678d

stacktrace of the issue

"

  • #0 __GI_raise
    at ../sysdeps/unix/sysv/linux/raise.c line 54
  • #1 __GI_abort
    at abort.c line 89
  • #2 g_assertion_message
  • #3 g_assertion_message_expr
    at /build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gtestutils.c line 2452
  • #4 create_info_label_security
    at applet-dialogs.c line 213
  • #5 info_dialog_add_page
    at applet-dialogs.c line 597
  • #6 info_dialog_update
    at applet-dialogs.c line 941
  • #7 applet_info_dialog_show
    at applet-dialogs.c line 968
  • #8 g_closure_invoke
    at /build/glib2.0-7IO_Yw/glib2.0-2.48.1/./gobject/gclosure.c line 804
  • #9 signal_emit_unlocked_R
    at /build/glib2.0-7IO_Yw/glib2.0-2.48.1/./gobject/gsignal.c line 3629
  • #10 g_signal_emit_valist
    at /build/glib2.0-7IO_Yw/glib2.0-2.48.1/./gobject/gsignal.c line 3385
  • #11 g_signal_emit
    at /build/glib2.0-7IO_Yw/glib2.0-2.48.1/./gobject/gsignal.c line 3441

Comment 1 Sebastien Bacher 2016-07-01 09:14:00 UTC
the ubuntu source seems 1 line off compared the 1.2 stable version, the assert is on l212 there
Comment 2 Thomas Haller 2016-07-01 10:34:46 UTC
Inside the client, the client must expect that a connection exposed by NetworkManager may be invalid. For example, if new API/libnm adds a new setting type (for example to support the new MACSEC device), then an older libnm version in the client is not yet aware of that new setting type and the connection (which is valid for the server with it's new version), appears invalid to the client. The client must gracefully handle that.

The assertion however indicates that the connection has no NMSettingConnection value. While that may theoretically happen (and should be accepted by the client), it's not clear why that would actually happen.

This bug report doesn't contain enough information about why the setting-connection is missing. The circumstances of the crash should be described. What were you doing, what was happening, what software components (and versions) were involved, is it reproducible, how often does it happen, etc.
Comment 3 Sebastien Bacher 2016-07-01 13:18:06 UTC
> This bug report doesn't contain enough information about why

Right, sorry but that's all we have, there are no user report to bug tracker just errors collecting stats and those are automatic and don't prompt user for a description. 

Thanks for the comment, feel free to close the bug as incomplete or such if it's not actable without details, we can reopen the day we get extra info.
Comment 4 Thomas Haller 2016-07-01 13:27:55 UTC
let's leave it open, but in my opinion it needs more information to be nailed down... if somebody knows how to reproduce it, that would be valuable.... Thanks!

(setting to NEEDINFO for now)
Comment 5 André Klapper 2020-11-12 14:25:40 UTC
bugzilla.gnome.org is being shut down in favor of a GitLab instance. 
We are closing all old bug reports and feature requests in GNOME Bugzilla which have not seen updates for a long time.

If you still use NetworkManager and if you still see this bug / want this feature in a recent and supported version of NetworkManager, then please feel free to report it at https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/

Thank you for creating this report and we are sorry it could not be implemented (workforce and time is unfortunately limited).