| Summary: | Network disconnected on start | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | lnxusr |
| Component: | Networking in general | Assignee: | Jan Grulich <jgrulich> |
| Status: | RESOLVED INTENTIONAL | ||
| Severity: | critical | CC: | jgrulich, pgkos.bugzilla |
| Priority: | NOR | ||
| Version First Reported In: | master | ||
| Target Milestone: | 1.0 | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
lnxusr
2017-06-19 16:13:21 UTC
Check whether your connection is configured to be automatically activated, otherwise you will end up doing it manually. (In reply to Jan Grulich from comment #1) > Check whether your connection is configured to be automatically activated, > otherwise you will end up doing it manually. Yes, it's set to automatically connect and allow all users to connect, although the advanced button next to this option is grayed out. Ok, maybe there will be something in NetworkManager logs, can you please attach them here? You can use "journalctl -u NetworkManager --since today" I am not sure if this is the same bug, but I have a similar problem since plasma 5.10. By default, my ethernet connection is named enp2s0. If I try to edit this connection (e.g. static IP address or name), I cannot save the changes (they are completely ignored, Apply button is greyed-out). I can add an another connection with a custom name, and then manually connect to it, then it works, but only until a reboot. Then I have to manually connect via my connection, as it still automatically connects to enp2s0. Then I tried another method - I tried to edit the enp2s0 connection using nmtui. After I made the changes and tried to save them, I got the following error message in nmtui: Unable to save connection: message recipient disconnected from message bus without replying Then I opened dbus-monitor --session, and, while monitoring, I opened nmtui and edited the connection. The issue disappeared! Somehow having the dbus monitor in the background prevented the issue from happening. Now I have a fully working and configured connection which persists across reboots. (In reply to pgkos.bugzilla from comment #4) > I am not sure if this is the same bug, but I have a similar problem since > plasma 5.10. > > By default, my ethernet connection is named enp2s0. If I try to edit this > connection (e.g. static IP address or name), I cannot save the changes (they > are completely ignored, Apply button is greyed-out). > > I can add an another connection with a custom name, and then manually > connect to it, then it works, but only until a reboot. Then I have to > manually connect via my connection, as it still automatically connects to > enp2s0. > > Then I tried another method - I tried to edit the enp2s0 connection using > nmtui. After I made the changes and tried to save them, I got the following > error message in nmtui: > > > Unable to save connection: message recipient disconnected from message bus > without replying > > > Then I opened dbus-monitor --session, and, while monitoring, I opened nmtui > and edited the connection. The issue disappeared! Somehow having the dbus > monitor in the background prevented the issue from happening. > > Now I have a fully working and configured connection which persists across > reboots. See bug 383505. Closing. The initial problem doesn't really seem to be problem in plasma-nm. The other issues where you are unable to edit your connection is duplicate of bug 383505. Bulk transfer as requested in T17796 |