Bug#749191: network-manager does not auto connect to wireless connection after system start anymore

2016-05-26 Thread Vladimir K
With network-manager 1.2.2-1 wireless hotspot profile is being auto-activated successfully during boot or daemon restart. For my situation (hotspot) the bug is resolved. For client profiles I've never experienced this bug.

Bug#749191: network-manager does not auto connect to wireless connection after system start anymore

2014-07-24 Thread Michael Meier
Package: network-manager Version: 0.9.10.0-1 Followup-For: Bug #749191 I just installed the systemd-sysv package, so effectly switching to the systemd startup service. With this service it reconnects automatically again. So i guess there's somekind of depedency issue when using sysv.

Bug#749191: network-manager does not auto connect to wireless connection after system start anymore

2014-07-22 Thread Michael Meier
Package: network-manager Version: 0.9.10.0-1 Followup-For: Bug #749191 also after updating to 0.9.10.0-1 this bug still exists. restarting the network manager service makes it auto connect... service network-manager restart Also for the new version there are no more information in the syslog. It

Bug#749191: network-manager does not auto connect to wireless connection after system start anymore

2014-06-27 Thread Vladimir K
It seems I have a variation of this bug. In my case Network Manager autoconnects to wireless networks in infrastructure mode successfully. But for profile set to ap mode autoconnect fails with message: device state change: unavailable - disconnected (reason 'supplicant-available') Manually

Bug#749191: network-manager does not auto connect to wireless connection after system start anymore

2014-05-28 Thread Antonio Marcos López Alonso
Hi, Metooing here but in KDE and using an Ethernet connection. This used to work fine when I had a dynamic IP (DHCP) served by my router but since a couple of weeks I had to change to a static IP scheme, deleted the automatic profile in network manager's tray icon and added a manual

Bug#749191: network-manager does not auto connect to wireless connection after system start anymore

2014-05-24 Thread Michael Meier
Package: network-manager Version: 0.9.8.10-2 Severity: normal When starting the system network-manager does not automatically connect to wireless connections marked as connect automatically. One has to connect to them by hand. Once connected it tries to automatically reconnect when it looses

Bug#749191: [Pkg-utopia-maintainers] Bug#749191: network-manager does not auto connect to wireless connection after system start anymore

2014-05-24 Thread Michael Biebl
Am 25.05.2014 01:46, schrieb Michael Meier: Package: network-manager Version: 0.9.8.10-2 Severity: normal When starting the system network-manager does not automatically connect to wireless connections marked as connect automatically. One has to connect to them by hand. Once connected it

Bug#749191: [Pkg-utopia-maintainers] Bug#749191: network-manager does not auto connect to wireless connection after system start anymore

2014-05-24 Thread Ronney Meier
Am 24.5.2014 18:51, schrieb Michael Biebl: Am 25.05.2014 01:46, schrieb Michael Meier: Package: network-manager Version: 0.9.8.10-2 Severity: normal When starting the system network-manager does not automatically connect to wireless connections marked as connect automatically. One has to

Bug#749191: [Pkg-utopia-maintainers] Bug#749191: network-manager does not auto connect to wireless connection after system start anymore

2014-05-24 Thread Michael Biebl
Am 25.05.2014 02:06, schrieb Ronney Meier: Am 24.5.2014 18:51, schrieb Michael Biebl: Am 25.05.2014 01:46, schrieb Michael Meier: Package: network-manager Version: 0.9.8.10-2 Severity: normal When starting the system network-manager does not automatically connect to wireless connections

Bug#749191: [Pkg-utopia-maintainers] Bug#749191: network-manager does not auto connect to wireless connection after system start anymore

2014-05-24 Thread Michael Meier
Am 24.5.2014 19:28, schrieb Michael Biebl: below the output of syslog. When it connects at 18:50 it's because I manually told it so. I'm not really sure how to get any output from wpa_supplicant at systemstart... you can simply restart wpa_supplicant. wpa-supplicant is no service, at least