Bug 1226169
Summary: | No option to add mobile broadband - No modem identified by NetworkManager | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Rishabh Das <rishabh5290> | ||||
Component: | plasma-nm | Assignee: | KDE SIG <kde-sig> | ||||
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 22 | CC: | dcbw, jgrulich, jklimes, kde-sig, psimerda | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2015-06-01 07:20:53 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Rishabh Das
2015-05-29 06:23:21 UTC
Actual results: Expected results: Let's find if there is a problem in KDE's editor/applet or in Networkmanager/ModemManager itself. What editor do you use for creating the connection profile, KDE one? Can you try with nm-connection-editor binary? Could you attach 'journalctl -b -u NetworkManager' logs? Created attachment 1032398 [details]
journalctl logs for NetworkManager
(In reply to Jirka Klimes from comment #2) > Let's find if there is a problem in KDE's editor/applet or in > Networkmanager/ModemManager itself. > > What editor do you use for creating the connection profile, KDE one? > Can you try with nm-connection-editor binary? Looks like this is an issue with KDE's connection editor. I was able to create a Mobile Broadband connection with nm-connection-editor. > Could you attach 'journalctl -b -u NetworkManager' logs? I have attached the logs since the point device was plugged in to the point where the status changes to registered. *** This bug has been marked as a duplicate of bug 1225426 *** |