Author Topic: [EN] on every boot a n annoying start job for network manager (Read 6337 times)

dieres · « **Reply #15 on:** 2016/09/10, 14:50:12 »

Change from sddm to lightdm doesn't solve the Problem here, but after DU this day the error disappeared on my system.

vilde · « **Reply #16 on:** 2016/09/10, 16:16:49 »

Just did a d-u, unfortunately no change here so I'm back to ceni again.

Edit: Maybe I'm wrong but I feel that most of the problem I had with siduction since systemd introduced are related to systemd. I don't know very much about this but maybe it is that systemd has its tentacles everywhere and therefore it feels like it has to do with a lot of problems?

ayla · « **Reply #17 on:** 2016/09/11, 00:04:07 »

Hi,

I had had the same issue since a few weeks or so. As on dieres system the problem disapeared after the d-u today.

Code: [Select]

cal@thendara:~$ apt-cache policy network-manager
network-manager:
  Installiert:           1.4.0-3
  Installationskandidat: 1.4.0-3
  Versionstabelle:
 *** 1.4.0-3 500
        500 http://httpredir.debian.org/debian unstable/main amd64 Packages
        100 /var/lib/dpkg/status
cal@thendara:~$ apt-cache policy plasma-nm
plasma-nm:
  Installiert:           4:5.7.4-1
  Installationskandidat: 4:5.7.4-1
  Versionstabelle:
 *** 4:5.7.4-1 500
        500 http://httpredir.debian.org/debian unstable/main amd64 Packages
        100 /var/lib/dpkg/status
cal@thendara:~$ apt-cache policy sddm
sddm:
  Installiert:           0.14.1~1-gecb903e-1
  Installationskandidat: 0.14.1~1-gecb903e-1
  Versionstabelle:
 *** 0.14.1~1-gecb903e-1 500
        500 http://ftp.uni-stuttgart.de/siduction/extra unstable/main amd64 Packages
        100 /var/lib/dpkg/status
     0.13.0-1 500
        500 http://httpredir.debian.org/debian unstable/main amd64 Packages
cal@thendara:~$ apt-cache policy systemd
systemd:
  Installiert:           231-5
  Installationskandidat: 231-5
  Versionstabelle:
 *** 231-5 500
        500 http://httpredir.debian.org/debian unstable/main amd64 Packages
        100 /var/lib/dpkg/status

greets
ayla

vilde · « **Reply #18 on:** 2016/09/12, 09:45:10 »

After a new d-u with new systemd today I tried with n-m again but still the same shit here.

Code: [Select]

vilde@vilde_dator:~$ apt-cache policy network-manager*
network-manager-pptp:
  Installerad: (ingen)
  Kandidat:    1.2.2-1
  Versionstabell:
     1.2.2-1 500
        500 http://httpredir.debian.org/debian unstable/main amd64 Packages
network-manager-iodine:
  Installerad: (ingen)
  Kandidat:    1.2.0-1
  Versionstabell:
     1.2.0-1 500
        500 http://httpredir.debian.org/debian unstable/main amd64 Packages
network-manager-iodine-gnome:
  Installerad: (ingen)
  Kandidat:    1.2.0-1
  Versionstabell:
     1.2.0-1 500
        500 http://httpredir.debian.org/debian unstable/main amd64 Packages
network-manager-strongswan:
  Installerad: (ingen)
  Kandidat:    1.3.1-2
  Versionstabell:
     1.3.1-2 500
        500 http://httpredir.debian.org/debian unstable/main amd64 Packages
network-manager-openconnect-gnome:
  Installerad: (ingen)
  Kandidat:    1.2.2-1
  Versionstabell:
     1.2.2-1 500
        500 http://httpredir.debian.org/debian unstable/main amd64 Packages
network-manager-ssh:
  Installerad: (ingen)
  Kandidat:    1.2.1-1
  Versionstabell:
     1.2.1-1 500
        500 http://httpredir.debian.org/debian unstable/main amd64 Packages
network-manager-vpnc:
  Installerad: (ingen)
  Kandidat:    1.2.2-1
  Versionstabell:
     1.2.2-1 500
        500 http://httpredir.debian.org/debian unstable/main amd64 Packages
network-manager-gnome:
  Installerad: 1.4.0-2
  Kandidat:    1.4.0-2
  Versionstabell:
 *** 1.4.0-2 500
        500 http://httpredir.debian.org/debian unstable/main amd64 Packages
        100 /var/lib/dpkg/status
network-manager:
  Installerad: 1.4.0-3
  Kandidat:    1.4.0-3
  Versionstabell:
 *** 1.4.0-3 500
        500 http://httpredir.debian.org/debian unstable/main amd64 Packages
        100 /var/lib/dpkg/status
network-manager-openvpn:
  Installerad: (ingen)
  Kandidat:    1.2.4-1
  Versionstabell:
     1.2.4-1 500
        500 http://httpredir.debian.org/debian unstable/main amd64 Packages
network-manager-ssh-gnome:
  Installerad: (ingen)
  Kandidat:    1.2.1-1
  Versionstabell:
     1.2.1-1 500
        500 http://httpredir.debian.org/debian unstable/main amd64 Packages
network-manager-dev:
  Installerad: (ingen)
  Kandidat:    1.4.0-3
  Versionstabell:
     1.4.0-3 500
        500 http://httpredir.debian.org/debian unstable/main amd64 Packages
network-manager-openvpn-gnome:
  Installerad: (ingen)
  Kandidat:    1.2.4-1
  Versionstabell:
     1.2.4-1 500
        500 http://httpredir.debian.org/debian unstable/main amd64 Packages
network-manager-vpnc-gnome:
  Installerad: (ingen)
  Kandidat:    1.2.2-1
  Versionstabell:
     1.2.2-1 500
        500 http://httpredir.debian.org/debian unstable/main amd64 Packages
network-manager-openconnect:
  Installerad: (ingen)
  Kandidat:    1.2.2-1
  Versionstabell:
     1.2.2-1 500
        500 http://httpredir.debian.org/debian unstable/main amd64 Packages
network-manager-pptp-gnome:
  Installerad: (ingen)
  Kandidat:    1.2.2-1
  Versionstabell:
     1.2.2-1 500
        500 http://httpredir.debian.org/debian unstable/main amd64 Packages
vilde@vilde_dator:~$ apt-cache policy sddm
sddm:
  Installerad: 0.14.1~1-gecb903e-1
  Kandidat:    0.14.1~1-gecb903e-1
  Versionstabell:
 *** 0.14.1~1-gecb903e-1 500
        500 http://packages.siduction.org/extra unstable/main amd64 Packages
        100 /var/lib/dpkg/status
     0.13.0-1 500
        500 http://httpredir.debian.org/debian unstable/main amd64 Packages
vilde@vilde_dator:~$ apt-cache policy systemd
systemd:
  Installerad: 231-6
  Kandidat:    231-6
  Versionstabell:
 *** 231-6 500
        500 http://httpredir.debian.org/debian unstable/main amd64 Packages
        100 /var/lib/dpkg/status

ayla · « **Reply #19 on:** 2016/09/12, 15:10:52 »

upgradet systemd to 231-6 during a d-u today. No change here, still boots fast.

vilde · « **Reply #20 on:** 2016/09/12, 15:31:23 »

ayla, you are on kde, I'm on xfce, maybe there is some different there. You have plasma n-m I have network-manager-gnome, maybe that is belonging to the xfce part?

hendrikL · « **Reply #21 on:** 2016/09/12, 15:38:56 »

please post

Code: [Select]

systemctl status network-manager.service

Code: [Select]

systemctl status wpa_supplicant.service

Code: [Select]

cat /etc/network/interfaces

ayla · « **Reply #22 on:** 2016/09/12, 15:42:13 »

@ vilde: I guess so, but the issue was the same, so I thougt it's not depending on the flavour. But whatever it may be, maybe it's fixed now just for kde...

vilde · « **Reply #23 on:** 2016/09/12, 16:19:41 »

Code: [Select]

root@vilde_dator:/home/vilde# systemctl status network-manager.service
● NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
   Active: active (running) since mån 2016-09-12 08:43:53 CEST; 7h ago
     Docs: man:NetworkManager(8)
 Main PID: 656 (NetworkManager)
    Tasks: 3 (limit: 4915)
   CGroup: /system.slice/NetworkManager.service
           └─656 /usr/sbin/NetworkManager --no-daemon

sep 12 16:01:31 vilde_dator NetworkManager[656]: <info>  [1473688891.329
sep 12 16:06:46 vilde_dator NetworkManager[656]: <info>  [1473689206.991
sep 12 16:06:47 vilde_dator NetworkManager[656]: <info>  [1473689207.354
sep 12 16:06:47 vilde_dator NetworkManager[656]: <info>  [1473689207.392
sep 12 16:12:02 vilde_dator NetworkManager[656]: <info>  [1473689522.998
sep 12 16:12:03 vilde_dator NetworkManager[656]: <info>  [1473689523.357
sep 12 16:12:03 vilde_dator NetworkManager[656]: <info>  [1473689523.382
sep 12 16:17:18 vilde_dator NetworkManager[656]: <info>  [1473689838.946
sep 12 16:17:19 vilde_dator NetworkManager[656]: <info>  [1473689839.304
sep 12 16:17:19 vilde_dator NetworkManager[656]: <info>  [1473689839.332
root@vilde_dator:/home/vilde# systemctl status wpa_supplicant.service 
● wpa_supplicant.service - WPA supplicant
   Loaded: loaded (/lib/systemd/system/wpa_supplicant.service; disabled;
   Active: active (running) since mån 2016-09-12 08:43:54 CEST; 7h ago
 Main PID: 3678 (wpa_supplicant)
    Tasks: 1 (limit: 4915)
   CGroup: /system.slice/wpa_supplicant.service
           └─3678 /sbin/wpa_supplicant -u -s -O /run/wpa_supplicant

sep 12 15:29:55 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan tr
sep 12 15:35:11 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan tr
sep 12 15:40:27 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan tr
sep 12 15:45:43 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan tr
sep 12 15:50:59 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan tr
sep 12 15:56:15 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan tr
sep 12 16:01:31 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan tr
sep 12 16:06:47 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan tr
sep 12 16:12:03 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan tr
sep 12 16:17:19 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan tr
lines 4-18/18 (END)
 Main PID: 3678 (wpa_supplicant)
    Tasks: 1 (limit: 4915)
   CGroup: /system.slice/wpa_supplicant.service
           └─3678 /sbin/wpa_supplicant -u -s -O /run/wpa_supplicant

sep 12 15:29:55 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan tr
sep 12 15:35:11 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan tr
sep 12 15:40:27 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan tr
sep 12 15:45:43 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan tr
sep 12 15:50:59 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan tr
sep 12 15:56:15 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan tr
sep 12 16:01:31 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan tr
sep 12 16:06:47 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan tr
sep 12 16:12:03 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan tr
sep 12 16:17:19 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan tr
~
lines 4-18/18 (END)
 Main PID: 3678 (wpa_supplicant)
    Tasks: 1 (limit: 4915)
   CGroup: /system.slice/wpa_supplicant.service
           └─3678 /sbin/wpa_supplicant -u -s -O /run/wpa_supplicant

sep 12 15:29:55 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan tri
sep 12 15:35:11 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan tri
sep 12 15:40:27 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan tri
sep 12 15:45:43 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan tri
sep 12 15:50:59 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan tri
sep 12 15:56:15 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan tri
sep 12 16:01:31 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan tri
sep 12 16:06:47 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan tri
sep 12 16:12:03 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan tri
sep 12 16:17:19 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan tri
~
~
lines 4-18/18 (END)
 Main PID: 3678 (wpa_supplicant)
    Tasks: 1 (limit: 4915)
   CGroup: /system.slice/wpa_supplicant.service
           └─3678 /sbin/wpa_supplicant -u -s -O /run/wpa_supplicant

sep 12 15:29:55 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigg
sep 12 15:35:11 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigg
sep 12 15:40:27 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigg
sep 12 15:45:43 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigg
sep 12 15:50:59 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigg
sep 12 15:56:15 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigg
sep 12 16:01:31 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigg
sep 12 16:06:47 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigg
sep 12 16:12:03 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigg
sep 12 16:17:19 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigg
~
~
lines 4-18/18 (END)
 Main PID: 3678 (wpa_supplicant)
    Tasks: 1 (limit: 4915)
   CGroup: /system.slice/wpa_supplicant.service
           └─3678 /sbin/wpa_supplicant -u -s -O /run/wpa_supplicant

sep 12 15:29:55 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigge
sep 12 15:35:11 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigge
sep 12 15:40:27 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigge
sep 12 15:45:43 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigge
sep 12 15:50:59 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigge
sep 12 15:56:15 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigge
sep 12 16:01:31 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigge
sep 12 16:06:47 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigge
sep 12 16:12:03 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigge
sep 12 16:17:19 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigge
~
~
~
lines 4-18/18 (END)

 Main PID: 3678 (wpa_supplicant)
    Tasks: 1 (limit: 4915)
   CGroup: /system.slice/wpa_supplicant.service
           └─3678 /sbin/wpa_supplicant -u -s -O /run/wpa_supplicant

sep 12 15:29:55 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigge
sep 12 15:35:11 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigge
sep 12 15:40:27 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigge
sep 12 15:45:43 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigge
sep 12 15:50:59 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigge
sep 12 15:56:15 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigge
sep 12 16:01:31 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigge
sep 12 16:06:47 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigge
sep 12 16:12:03 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigge
sep 12 16:17:19 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigge
~
~
~
~
lines 4-18/18 (END)
 Main PID: 3678 (wpa_supplicant)
    Tasks: 1 (limit: 4915)
   CGroup: /system.slice/wpa_supplicant.service
           └─3678 /sbin/wpa_supplicant -u -s -O /run/wpa_supplicant

sep 12 15:29:55 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger
sep 12 15:35:11 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger
sep 12 15:40:27 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger
sep 12 15:45:43 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger
sep 12 15:50:59 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger
sep 12 15:56:15 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger
sep 12 16:01:31 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger
sep 12 16:06:47 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger
sep 12 16:12:03 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger
sep 12 16:17:19 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger
~
~
~
~
lines 4-18/18 (END)

 Main PID: 3678 (wpa_supplicant)
    Tasks: 1 (limit: 4915)
   CGroup: /system.slice/wpa_supplicant.service
           └─3678 /sbin/wpa_supplicant -u -s -O /run/wpa_supplicant

sep 12 15:29:55 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger
sep 12 15:35:11 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger
sep 12 15:40:27 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger
sep 12 15:45:43 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger
sep 12 15:50:59 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger
sep 12 15:56:15 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger
sep 12 16:01:31 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger
sep 12 16:06:47 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger
sep 12 16:12:03 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger
sep 12 16:17:19 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger
~
~
~
~
~
lines 4-18/18 (END)
 Main PID: 3678 (wpa_supplicant)
    Tasks: 1 (limit: 4915)
   CGroup: /system.slice/wpa_supplicant.service
           └─3678 /sbin/wpa_supplicant -u -s -O /run/wpa_supplicant

sep 12 15:29:55 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger
sep 12 15:35:11 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger
sep 12 15:40:27 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger
sep 12 15:45:43 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger
sep 12 15:50:59 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger
sep 12 15:56:15 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger
sep 12 16:01:31 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger
sep 12 16:06:47 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger
sep 12 16:12:03 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger
sep 12 16:17:19 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger
~
~
~
~
~
~
lines 4-18/18 (END)
 Main PID: 3678 (wpa_supplicant)
    Tasks: 1 (limit: 4915)
   CGroup: /system.slice/wpa_supplicant.service
           └─3678 /sbin/wpa_supplicant -u -s -O /run/wpa_supplicant

sep 12 15:29:55 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger
sep 12 15:35:11 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger
sep 12 15:40:27 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger
sep 12 15:45:43 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger
sep 12 15:50:59 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger
sep 12 15:56:15 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger
sep 12 16:01:31 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger
sep 12 16:06:47 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger
sep 12 16:12:03 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger
sep 12 16:17:19 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger
~
~
~
~
~
~
~
lines 4-18/18 (END)
 Main PID: 3678 (wpa_supplicant)
    Tasks: 1 (limit: 4915)
   CGroup: /system.slice/wpa_supplicant.service
           └─3678 /sbin/wpa_supplicant -u -s -O /run/wpa_supplicant

sep 12 15:29:55 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger 
sep 12 15:35:11 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger 
sep 12 15:40:27 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger 
sep 12 15:45:43 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger 
sep 12 15:50:59 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger 
sep 12 15:56:15 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger 
sep 12 16:01:31 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger 
sep 12 16:06:47 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger 
sep 12 16:12:03 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger 
sep 12 16:17:19 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger 
~
~
~
~
~
~
~
lines 4-18/18 (END)
 Main PID: 3678 (wpa_supplicant)
    Tasks: 1 (limit: 4915)
   CGroup: /system.slice/wpa_supplicant.service
           └─3678 /sbin/wpa_supplicant -u -s -O /run/wpa_supplicant

sep 12 15:29:55 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger s
sep 12 15:35:11 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger s
sep 12 15:40:27 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger s
sep 12 15:45:43 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger s
sep 12 15:50:59 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger s
sep 12 15:56:15 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger s
sep 12 16:01:31 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger s
sep 12 16:06:47 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger s
sep 12 16:12:03 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger s
sep 12 16:17:19 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger s
~
~
~
~
~
~
~
lines 4-18/18 (END)
 Main PID: 3678 (wpa_supplicant)
    Tasks: 1 (limit: 4915)
   CGroup: /system.slice/wpa_supplicant.service
           └─3678 /sbin/wpa_supplicant -u -s -O /run/wpa_supplicant

sep 12 15:29:55 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger si
sep 12 15:35:11 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger si
sep 12 15:40:27 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger si
sep 12 15:45:43 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger si
sep 12 15:50:59 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger si
sep 12 15:56:15 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger si
sep 12 16:01:31 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger si
sep 12 16:06:47 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger si
sep 12 16:12:03 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger si
sep 12 16:17:19 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger si
~
~
~
~
~
~
~
~
lines 4-18/18 (END)
 Main PID: 3678 (wpa_supplicant)
    Tasks: 1 (limit: 4915)
   CGroup: /system.slice/wpa_supplicant.service
           └─3678 /sbin/wpa_supplicant -u -s -O /run/wpa_supplicant

sep 12 15:29:55 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger sin
sep 12 15:35:11 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger sin
sep 12 15:40:27 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger sin
sep 12 15:45:43 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger sin
sep 12 15:50:59 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger sin
sep 12 15:56:15 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger sin
sep 12 16:01:31 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger sin
sep 12 16:06:47 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger sin
sep 12 16:12:03 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger sin
sep 12 16:17:19 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger sin
~
~
~
~
~
~
~
~
lines 4-18/18 (END)
 Main PID: 3678 (wpa_supplicant)
    Tasks: 1 (limit: 4915)
   CGroup: /system.slice/wpa_supplicant.service
           └─3678 /sbin/wpa_supplicant -u -s -O /run/wpa_supplicant

sep 12 15:29:55 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger sinc
sep 12 15:35:11 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger sinc
sep 12 15:40:27 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger sinc
sep 12 15:45:43 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger sinc
sep 12 15:50:59 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger sinc
sep 12 15:56:15 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger sinc
sep 12 16:01:31 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger sinc
sep 12 16:06:47 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger sinc
sep 12 16:12:03 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger sinc
sep 12 16:17:19 vilde_dator wpa_supplicant[3678]: wlp3s0: Reject scan trigger sinc
~
~
~
~
~
~
~
~
root@vilde_dator:/home/vilde# cat /etc/network/interfaces
# /etc/network/interfaces - configuration file for ifup(8), ifdown(8)

# The loopback interface
auto lo
iface lo inet loopback

allow-hotplug enp0s25
iface enp0s25 inet dhcp

hendrikL · « **Reply #24 on:** 2016/09/12, 16:42:23 »

so, if you use NM, there is no need for a /e/n/interfaces
then, disable that networkmanager-wait-online.service with disable and than mask it!
Do you use wifi/wlan to connect or cable?
If you use cable, why do you try to start wifi? If you don't need it, disable it!
or set it up the right way!
Read the messages from journalctl and status wpa_.......

vilde · « **Reply #25 on:** 2016/09/12, 16:59:49 »

@ hendrikL Sorry but I don't understand what you want me to do, as I have wrote before here I'm a user not a developer.

Quote

so, if you use NM, there is no need for a /e/n/interfaces

I don't know what that is?

Quote

then, disable that networkmanager-wait-online.service with disable and than mask it!

Quote

Do you use wifi/wlan to connect or cable?

I use cable

Quote

If you use cable, why do you try to start wifi? If you don't need it, disable it!

I have not activly tried to start any wifi, and there is no wifi conected, don't a clean install of siduction always try to look for network? Besides, sometimes I do disconnect the computer and use it somewhere else, then I need the wifi to work.

Quote

or set it up the right way!

How?

Quote

Read the messages from journalctl and status wpa_.......

I have tried to read messages and logs many times but I have to say that I don't understand what they say, I know to little about this, to many words and computer related special expressions I don't understand.

agaida · « **Reply #26 on:** 2016/09/12, 17:19:15 »

apt purge wpasupplicant - and be done with it

hendrikL · « **Reply #27 on:** 2016/09/12, 17:22:18 »

as $user like the most off us, you should read some documentations and search the internet, and i am an $user too!

so,
1 /e/n/i == /etc/network/interfaces (ceni ?= configure /etc/network/interfaces)
1.1 as root

Code: [Select]

~# mv /etc/network/interfaces /etc/network/interfaces~
2

Code: [Select]

systemctl status NetworkManager-wait-online.service
3 to stop the wifi hardware use rfkill if you have one.
if not than this is just for the interested ones.

rfkill list shows you the device,
with rfkill block N, you disable it (N=number)

here an example how it looks, when you have blocked bluetooth

Code: [Select]

 rfkill list
0: tpacpi_bluetooth_sw: Bluetooth
        Soft blocked: yes
        Hard blocked: no
1: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no

3.1

Code: [Select]

systemctl disable wpa_suppliucant.service && systemctl mask wpa_supplicant.service
4 Try to learn a little bit to interpret the messages and to use a web search engine, you are using debian sid/unstable
so if you get a bunch of error messages from on service/app or what ever, start to dig for that error.
That is all i can say.

vilde · « **Reply #28 on:** 2016/09/12, 18:17:36 »

Than you agaida, apt purge wpasupplicant worked, but now I probably can't use wifi or?

Also, thank you for your effort hendrikL but I don't understand very much more now and no I don't want to learn about systemd or understand network vocabulary and how it works, I do other things.

I'm not using debian-unstable, I use siduction I know it's nearly pure debian unstable, but fixed so I can use it, i'ts been like that since all were on Kanotix, so I have been here for many many years without knowing this things. The day I have to fix the unstable problem myself I will start to use something else.

And also again, thank you everybody who make me be able to use siducion and debian-unstable, thank you everybody who try to help on the forum. I really appreciate it and have always done.

When I write something about a problem I have, it's not only to say that I want help, it's also a way to show the developers that there may be a problem that can and/or need to be fixed.

Enough OT, have a nice day everybody.

agaida · « **Reply #29 on:** 2016/09/12, 18:44:29 »

@vilde - if you want to use wifi - ok, you have to re-install wpasupplicant. but for now it was the most simple solution (KISS) - disable the wpa-supplicant service would be sufficient.

Author Topic: [EN] on every boot a n annoying start job for network manager (Read 6337 times)

dieres

[EN] Re: on every boot a n annoying start job for network manager

vilde

Re: on every boot a n annoying start job for network manager

ayla

Re: on every boot a n annoying start job for network manager

vilde

Re: on every boot a n annoying start job for network manager

ayla

Re: on every boot a n annoying start job for network manager

vilde

Re: on every boot a n annoying start job for network manager

hendrikL

Re: on every boot a n annoying start job for network manager

ayla

Re: on every boot a n annoying start job for network manager

vilde

Re: on every boot a n annoying start job for network manager

hendrikL

Re: on every boot a n annoying start job for network manager

vilde

Re: on every boot a n annoying start job for network manager

agaida

Re: on every boot a n annoying start job for network manager

hendrikL

Re: on every boot a n annoying start job for network manager

vilde

Re: on every boot a n annoying start job for network manager

agaida

Re: on every boot a n annoying start job for network manager