Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

device not managed #10

Open
liuhangcheng opened this issue Sep 15, 2016 · 5 comments
Open

device not managed #10

liuhangcheng opened this issue Sep 15, 2016 · 5 comments

Comments

@liuhangcheng
Copy link

every time when i boot up , i need to restart network manager to get it managed, and when the first time restart the hardware address will be 00.00.00.00.00, and the 2nd time will be true address

@mmhobi7
Copy link

mmhobi7 commented Mar 5, 2017

sudo service network-manager restart

@mmhobi7
Copy link

mmhobi7 commented Mar 14, 2017

[ 7632.313727] ModemManager[1193]: segfault at 0 ip 0000564621fd3ab7 sp 00007ffe866559e0 error 4 in ModemManager[564621f9c000+11f000]
To go along with it

@LorenzoAncora
Copy link

I have the same problem of @liuhangcheng and @aaahh.

ModemManager[9214]: segfault at 0 ip 000055fb8a442c47 sp 00007fffd3c55d10 error 4 in ModemManager[55fb8a408000+122000]

@WildfootW
Copy link

I have the same problem

[  120.392276] ModemManager[985]: segfault at 0 ip 0000000000431ab3 sp 00007ffefcea5940 error 4 in ModemManager[400000+103000]

@mmhobi7
Copy link

mmhobi7 commented Jul 28, 2018

I think I fixed it by restarting networkManager

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants