Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15835] New: Incompatibility between network-manager and libcurl 8.4
Date: Mon, 30 Oct 2023 07:44:37 +0000	[thread overview]
Message-ID: <bug-15835-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=15835

            Bug ID: 15835
           Summary: Incompatibility between network-manager and libcurl
                    8.4
           Product: buildroot
           Version: 2023.02.6
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned@buildroot.uclibc.org
          Reporter: chhitz@gmx.net
                CC: buildroot@uclibc.org
  Target Milestone: ---

In buildroot 2023.02.6 libcurl was updated from 8.3 to 8.4. This new libcurl
version triggers an issue in network-manager:
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/1756

In our case the command `nmcli device disconnect` will always time-out when
called when connected to the internet and having the connection check enabled.

Applying the path from above mentioned issue to network-manager fixes the
issue.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

             reply	other threads:[~2023-10-30  7:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-30  7:44 bugzilla [this message]
2023-10-31 20:30 ` [Buildroot] [Bug 15835] Incompatibility between network-manager and libcurl 8.4 bugzilla
2023-11-07 21:57 ` bugzilla

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-15835-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@uclibc.org \
    /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