Bug 22531 - networkmanager segfault when trying to connect w/ bluetooth tethering / bnep0
Summary: networkmanager segfault when trying to connect w/ bluetooth tethering / bnep0
Status: RESOLVED DUPLICATE of bug 21685
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 6
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-02-06 01:42 CET by Christian Lohmaier
Modified: 2018-02-08 12:07 CET (History)
2 users (show)

See Also:
Source RPM: networkmanager-1.8.0-1.mga6.src.rpm
CVE:
Status comment:


Attachments
patch to fix the issue, taken from arch#54076 (757 bytes, patch)
2018-02-06 01:43 CET, Christian Lohmaier
Details | Diff

Description Christian Lohmaier 2018-02-06 01:42:08 CET
Description of problem:
Try to use bluetooth tethering by connecting to your phone (I use corresponding menu from gnome-menu, but any other networkmanager tool gives same result):

NetworkManager[883]: <info>  [1517855956.3374] dhcp4 (bnep0): activation: beginning transaction (timeou
NetworkManager[883]: ((src/platform/nm-platform.c:2650)): assertion '<dropped>' failed
NetworkManager[883]: g_array_sort_with_data: assertion 'array != NULL' failed
kernel: NetworkManager[883]: segfault at 8 ip 00000000004a5ff2 sp 00007ffd219ae5e0 error 4 in NetworkMa


As a result of networkmanager crash, dhcp is not triggered (can fix that by running "dhclient bnep0"), and NM fails to acknowledge the device afterwards:
when trying to setup VPN connection it fails with 

result="fail" reason="Could not find source connection."

Version-Release number of selected component (if applicable):
1.8.0

How reproducible:
always

Steps to Reproduce:
1. enable bluetooth tethering on your mobile
2. try to enable the bt internet connection via networkmanager
3. fails to init properly, no internet connection

(can get internet by manually running dhclient as outlined above, but even after that enabling VPN is not possible using networkmanager)
Comment 1 Christian Lohmaier 2018-02-06 01:43:20 CET
Created attachment 9951 [details]
patch to fix the issue, taken from arch#54076
Comment 2 Jani Välimaa 2018-02-07 11:12:10 CET
I'll check this one. I think I'm going to update nm to the latest stable in 1.8 series.

Status: NEW => ASSIGNED
Assignee: bugsquad => jani.valimaa
CC: (none) => jani.valimaa

Comment 3 Jani Välimaa 2018-02-07 17:14:51 CET
Pushed networkmanager 1.8.6 which should fix the issue and includes fixes also for bug 21685. Please test new nm from core/updates_testing.

Assignee: jani.valimaa => qa-bugs

Comment 4 Thomas Backlund 2018-02-08 12:07:59 CET
 Track NetworkManager update in a single update bug to not confuse QA / testers...

Please doa all follow-up comments in the other report

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

CC: (none) => tmb
Status: ASSIGNED => RESOLVED
Resolution: (none) => DUPLICATE


Note You need to log in before you can comment on or make changes to this bug.