You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Occasionally, attempting to enable a Wireguard connection in the network manager applet does not work. Rather, clicking on the toggle ends up selecting a different wireless network than the currently connected one, and the wireguard connection is not enabled. It's almost as if the click is being passed through to some menu item underneath the Wireguard Connections section.
When this does happen, I notice that the width of the menu is also wider than usual. It's possible that this tends to occur after using an external monitor, suspending the laptop, and then resuming using the build-in laptop display.
Steps to reproduce
Unfortunately, I don't know how to reproduce this. This seems to occur maybe 10% of the time. I thought I would create an issue in case others experience something similar.
Expected behavior
Enabling a wireguard connection should just enable the wireguard connection and not switch wireless networks.
Additional information
No response
The text was updated successfully, but these errors were encountered:
Distribution
Arch
Package version
Cinnamon 6.4.9
Graphics hardware in use
Radeon 780M
Frequency
Only occasionally
Bug description
Occasionally, attempting to enable a Wireguard connection in the network manager applet does not work. Rather, clicking on the toggle ends up selecting a different wireless network than the currently connected one, and the wireguard connection is not enabled. It's almost as if the click is being passed through to some menu item underneath the Wireguard Connections section.
When this does happen, I notice that the width of the menu is also wider than usual. It's possible that this tends to occur after using an external monitor, suspending the laptop, and then resuming using the build-in laptop display.
Steps to reproduce
Unfortunately, I don't know how to reproduce this. This seems to occur maybe 10% of the time. I thought I would create an issue in case others experience something similar.
Expected behavior
Enabling a wireguard connection should just enable the wireguard connection and not switch wireless networks.
Additional information
No response
The text was updated successfully, but these errors were encountered: