From: Divan Santana <divan@santanas.co.za>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: 37369@debbugs.gnu.org, help-guix@gnu.org
Subject: Re: bug#37369: Getting network-manager-openconnect to work
Date: Sat, 28 Sep 2019 16:00:25 +0200 [thread overview]
Message-ID: <87h84wttae.fsf@santanas.co.za> (raw)
In-Reply-To: <20190927163735.c4cjjuh4r6i6de3c@pelzflorian.localdomain>
pelzflorian (Florian Pelz) <pelzflorian@pelzflorian.de> writes:
> Hello!
>
> There might be a workaround:
>
> NetworkManager stopped segfaulting for me after I “edited” the
> openconnect VPN connection in nm-connection-editor without making any
> changes to the connection. Apparently this fixed get_secrets_done_cb
> being passed what GDB calls an “<incomplete type>” as the connection
> and crashing in nm_connection_get_setting_by_name. I need to repeat
> this nm-connection-editor editing after every reboot.
>
> Does editing the VPN connection in nm-connection-editor fix the
> problem for you, Divan Santana?
I'll let you know.
> No patch at all is required for me. nmtui works fine without the patch.
> This issue is not present in Arch Linux using the more recent
> NetworkManager 1.20.2. I have not yet attempted to upgrade Guix’
> NetworkManager to a more recent version.
next prev parent reply other threads:[~2019-09-28 14:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-10 9:57 Getting network-manager-openconnect to work Divan Santana
2019-09-10 11:21 ` pelzflorian (Florian Pelz)
2019-09-11 7:38 ` bug#37369: " Efraim Flashner
2019-09-11 11:39 ` pelzflorian (Florian Pelz)
2019-09-11 20:46 ` Ludovic Courtès
2019-09-12 5:34 ` pelzflorian (Florian Pelz)
2019-09-16 15:57 ` Ludovic Courtès
2019-09-16 16:06 ` pelzflorian (Florian Pelz)
2019-09-27 16:37 ` bug#37369: " pelzflorian (Florian Pelz)
2019-09-28 14:00 ` Divan Santana [this message]
2019-09-28 14:16 ` Divan Santana
2019-09-28 15:34 ` pelzflorian (Florian Pelz)
2019-09-29 7:54 ` pelzflorian (Florian Pelz)
2019-09-28 16:47 ` pelzflorian (Florian Pelz)
2019-10-03 11:51 ` Divan Santana
2019-09-16 11:53 ` pelzflorian (Florian Pelz)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h84wttae.fsf@santanas.co.za \
--to=divan@santanas.co.za \
--cc=37369@debbugs.gnu.org \
--cc=help-guix@gnu.org \
--cc=pelzflorian@pelzflorian.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).