You are not logged in.

#1 2018-12-25 12:02:54

novare
Member
Registered: 2018-12-25
Posts: 3

[SOLVED] Network issues until opening Chromium, doesn't work with FF

Hi,
I've been running Arch on my laptop for a while now and for a few weeks I've been having issues with my WiFi connection. I'm running Gnome 3.30.2 on 64bit Arch, everything is up to date. When I boot up the system and log in, the network manager icon in the upper right corner shows a question mark. If I then try to load different websites using Firefox (64.0), most of them work (everything Google-related, Trello, GitHub etc.), but some can't be reached and I get "server not found" (Wikipedia, ProtonMail, StackOverflow, forums like this one).

I deleted my Firefox profile and reinstalled it, but that didn't help. I considered that my add-ons cause this, but the weird thing is that everything works once I open up an instance of Chrome or Chromium in the background - the question mark disappears and I can connect to every site using Firefox. Once I close the Chromium/Chrome instance, this effect lasts for a few minutes to an hour and then I get the same problem again. I know my WiFi card has pretty bad drivers, but I didn't have this issue for years.

To debug this, I checked journalctl NetworkManager before and after opening a Chrome/Chromium instance. First, I get the following output:

-- Reboot --
Dec 25 12:16:36 hawking NetworkManager[641]: <info>  [1545736596.3904] NetworkManager (version 1.14.5dev+17+gba83251bb-1) is starting... (for the first time)
Dec 25 12:16:36 hawking NetworkManager[641]: <info>  [1545736596.3908] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 20-connectivity.conf)
Dec 25 12:16:36 hawking NetworkManager[641]: <info>  [1545736596.5341] wifi-nl80211: (wlp8s0): using nl80211 for WiFi device control
Dec 25 12:16:36 hawking NetworkManager[641]: <info>  [1545736596.5458] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
Dec 25 12:16:36 hawking NetworkManager[641]: <info>  [1545736596.6631] manager[0x556c357cf010]: monitoring kernel firmware directory '/lib/firmware'.
Dec 25 12:16:36 hawking NetworkManager[641]: <info>  [1545736596.9659] hostname: hostname: using hostnamed
Dec 25 12:16:36 hawking NetworkManager[641]: <info>  [1545736596.9660] hostname: hostname changed from (none) to "hawking"
Dec 25 12:16:36 hawking NetworkManager[641]: <info>  [1545736596.9664] dns-mgr[0x556c357d8910]: init: dns=default, rc-manager=symlink
Dec 25 12:16:36 hawking NetworkManager[641]: <info>  [1545736596.9676] rfkill0: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.1/0000:08:00.0/ieee80211/phy0/rfkill0) (driver rtl8188ee)
Dec 25 12:16:36 hawking NetworkManager[641]: <info>  [1545736596.9680] manager[0x556c357cf010]: rfkill: WiFi hardware radio set enabled
Dec 25 12:16:36 hawking NetworkManager[641]: <info>  [1545736596.9680] manager[0x556c357cf010]: rfkill: WWAN hardware radio set enabled
Dec 25 12:16:37 hawking NetworkManager[641]: <info>  [1545736597.8275] settings: Loaded settings plugin: NMSKeyfilePlugin (internal)
Dec 25 12:16:37 hawking NetworkManager[641]: <info>  [1545736597.9665] settings: Loaded settings plugin: NMSIbftPlugin ("/usr/lib/NetworkManager/1.14.5dev+17+gba83251bb-1/libnm-settings-plugin-ibft.so")
Dec 25 12:16:38 hawking NetworkManager[641]: <info>  [1545736598.0805] keyfile: new connection /etc/NetworkManager/system-connections/EasyBox (8619ef61-598a-4856-84a2-d5d2902adcae,"EasyBox")
Dec 25 12:16:38 hawking NetworkManager[641]: <info>  [1545736598.4637] manager: rfkill: WiFi enabled by radio killswitch; enabled by state file
Dec 25 12:16:38 hawking NetworkManager[641]: <info>  [1545736598.4639] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
Dec 25 12:16:38 hawking NetworkManager[641]: <info>  [1545736598.4640] manager: Networking is enabled by state file
Dec 25 12:16:38 hawking NetworkManager[641]: <info>  [1545736598.4642] dhcp-init: Using DHCP client 'internal'
Dec 25 12:16:38 hawking NetworkManager[641]: <info>  [1545736598.6241] Loaded device plugin: NMOvsFactory (/usr/lib/NetworkManager/1.14.5dev+17+gba83251bb-1/libnm-device-plugin-ovs.so)
Dec 25 12:16:38 hawking NetworkManager[641]: <info>  [1545736598.6417] Loaded device plugin: NMWifiFactory (/usr/lib/NetworkManager/1.14.5dev+17+gba83251bb-1/libnm-device-plugin-wifi.so)
Dec 25 12:16:38 hawking NetworkManager[641]: <info>  [1545736598.6677] Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/1.14.5dev+17+gba83251bb-1/libnm-device-plugin-bluetooth.so)
Dec 25 12:16:39 hawking NetworkManager[641]: <info>  [1545736599.0528] Loaded device plugin: NMTeamFactory (/usr/lib/NetworkManager/1.14.5dev+17+gba83251bb-1/libnm-device-plugin-team.so)
Dec 25 12:16:39 hawking NetworkManager[641]: <info>  [1545736599.0884] Loaded device plugin: NMAtmManager (/usr/lib/NetworkManager/1.14.5dev+17+gba83251bb-1/libnm-device-plugin-adsl.so)
Dec 25 12:16:39 hawking NetworkManager[641]: <info>  [1545736599.0898] Loaded device plugin: NMWwanFactory (/usr/lib/NetworkManager/1.14.5dev+17+gba83251bb-1/libnm-device-plugin-wwan.so)
Dec 25 12:16:39 hawking NetworkManager[641]: <info>  [1545736599.1041] device (lo): carrier: link connected
Dec 25 12:16:39 hawking NetworkManager[641]: <info>  [1545736599.1052] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
Dec 25 12:16:39 hawking NetworkManager[641]: <info>  [1545736599.1073] manager: (enp9s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
Dec 25 12:16:39 hawking NetworkManager[641]: <info>  [1545736599.1117] keyfile: add connection /var/run/NetworkManager/system-connections/Wired connection 1.nmconnection (070248a1-f819-3fe3-9b1c-8def0522dcc8,"Wired connection 1")
Dec 25 12:16:39 hawking NetworkManager[641]: <info>  [1545736599.1132] settings: (enp9s0): created default wired connection 'Wired connection 1'
Dec 25 12:16:39 hawking NetworkManager[641]: <info>  [1545736599.1147] device (enp9s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Dec 25 12:16:39 hawking NetworkManager[641]: <info>  [1545736599.1176] device (wlp8s0): driver supports Access Point (AP) mode
Dec 25 12:16:39 hawking NetworkManager[641]: <info>  [1545736599.1182] manager: (wlp8s0): new 802.11 WiFi device (/org/freedesktop/NetworkManager/Devices/3)
Dec 25 12:16:39 hawking NetworkManager[641]: <info>  [1545736599.1195] device (wlp8s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Dec 25 12:16:39 hawking NetworkManager[641]: <info>  [1545736599.2132] ovsdb: Could not connect: No such file or directory
Dec 25 12:16:39 hawking NetworkManager[641]: <info>  [1545736599.7175] supplicant: wpa_supplicant running
Dec 25 12:16:39 hawking NetworkManager[641]: <info>  [1545736599.7176] device (wlp8s0): supplicant interface state: init -> starting
Dec 25 12:16:40 hawking NetworkManager[641]: <info>  [1545736600.0322] sup-iface[0x556c357d28c0,wlp8s0]: supports 4 scan SSIDs
Dec 25 12:16:40 hawking NetworkManager[641]: <info>  [1545736600.0332] device (wlp8s0): supplicant interface state: starting -> ready
Dec 25 12:16:40 hawking NetworkManager[641]: <info>  [1545736600.0333] device (wlp8s0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed')
Dec 25 12:16:40 hawking NetworkManager[641]: <info>  [1545736600.2136] modem-manager: ModemManager not available
Dec 25 12:16:40 hawking NetworkManager[641]: <info>  [1545736600.2552] modem-manager: ModemManager now available
Dec 25 12:16:41 hawking NetworkManager[641]: <info>  [1545736601.4884] policy: auto-activating connection 'EasyBox' (8619ef61-598a-4856-84a2-d5d2902adcae)
Dec 25 12:16:41 hawking NetworkManager[641]: <info>  [1545736601.4894] device (wlp8s0): Activation: starting connection 'EasyBox' (8619ef61-598a-4856-84a2-d5d2902adcae)
Dec 25 12:16:41 hawking NetworkManager[641]: <info>  [1545736601.4897] device (wlp8s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Dec 25 12:16:41 hawking NetworkManager[641]: <info>  [1545736601.4903] manager: NetworkManager state is now CONNECTING
Dec 25 12:16:41 hawking NetworkManager[641]: <info>  [1545736601.4910] device (wlp8s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Dec 25 12:16:41 hawking NetworkManager[641]: <info>  [1545736601.4917] device (wlp8s0): Activation: (wifi) access point 'EasyBox' has security, but secrets are required.
Dec 25 12:16:41 hawking NetworkManager[641]: <info>  [1545736601.4917] device (wlp8s0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Dec 25 12:16:41 hawking NetworkManager[641]: <info>  [1545736601.4943] device (wlp8s0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Dec 25 12:16:41 hawking NetworkManager[641]: <info>  [1545736601.4949] device (wlp8s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Dec 25 12:16:41 hawking NetworkManager[641]: <info>  [1545736601.4956] device (wlp8s0): Activation: (wifi) connection 'EasyBox' has security, and secrets exist.  No new secrets needed.
Dec 25 12:16:41 hawking NetworkManager[641]: <info>  [1545736601.4957] Config: added 'ssid' value 'EasyBox'
Dec 25 12:16:41 hawking NetworkManager[641]: <info>  [1545736601.4957] Config: added 'scan_ssid' value '1'
Dec 25 12:16:41 hawking NetworkManager[641]: <info>  [1545736601.4957] Config: added 'bgscan' value 'simple:30:-80:86400'
Dec 25 12:16:41 hawking NetworkManager[641]: <info>  [1545736601.4957] Config: added 'key_mgmt' value 'WPA-PSK'
Dec 25 12:16:41 hawking NetworkManager[641]: <info>  [1545736601.4958] Config: added 'psk' value '<hidden>'
Dec 25 12:16:41 hawking NetworkManager[641]: <info>  [1545736601.5140] device (wlp8s0): supplicant interface state: ready -> authenticating
Dec 25 12:16:41 hawking NetworkManager[641]: <info>  [1545736601.5210] device (wlp8s0): supplicant interface state: authenticating -> associating
Dec 25 12:16:41 hawking NetworkManager[641]: <info>  [1545736601.5296] device (wlp8s0): supplicant interface state: associating -> associated
Dec 25 12:16:41 hawking NetworkManager[641]: <info>  [1545736601.5371] device (wlp8s0): supplicant interface state: associated -> 4-way handshake
Dec 25 12:16:41 hawking NetworkManager[641]: <info>  [1545736601.6057] device (wlp8s0): supplicant interface state: 4-way handshake -> completed
Dec 25 12:16:41 hawking NetworkManager[641]: <info>  [1545736601.6058] device (wlp8s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "EasyBox"
Dec 25 12:16:41 hawking NetworkManager[641]: <info>  [1545736601.6061] device (wlp8s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Dec 25 12:16:41 hawking NetworkManager[641]: <info>  [1545736601.6069] dhcp4 (wlp8s0): activation: beginning transaction (timeout in 45 seconds)
Dec 25 12:16:45 hawking NetworkManager[641]: <info>  [1545736605.2282] dhcp4 (wlp8s0):   address 192.168.2.102
Dec 25 12:16:45 hawking NetworkManager[641]: <info>  [1545736605.2283] dhcp4 (wlp8s0):   plen 24
Dec 25 12:16:45 hawking NetworkManager[641]: <info>  [1545736605.2284] dhcp4 (wlp8s0):   expires in 31536000 seconds
Dec 25 12:16:45 hawking NetworkManager[641]: <info>  [1545736605.2285] dhcp4 (wlp8s0):   nameserver '192.168.2.1'
Dec 25 12:16:45 hawking NetworkManager[641]: <info>  [1545736605.2287] dhcp4 (wlp8s0):   domain name 'local'
Dec 25 12:16:45 hawking NetworkManager[641]: <info>  [1545736605.2288] dhcp4 (wlp8s0):   hostname 'hawking'
Dec 25 12:16:45 hawking NetworkManager[641]: <info>  [1545736605.2288] dhcp4 (wlp8s0):   gateway 192.168.2.1
Dec 25 12:16:45 hawking NetworkManager[641]: <info>  [1545736605.2502] dhcp4 (wlp8s0): state changed unknown -> bound
Dec 25 12:16:45 hawking NetworkManager[641]: <info>  [1545736605.2519] device (wlp8s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Dec 25 12:16:45 hawking NetworkManager[641]: <info>  [1545736605.2531] device (wlp8s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Dec 25 12:16:45 hawking NetworkManager[641]: <info>  [1545736605.2535] device (wlp8s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Dec 25 12:16:45 hawking NetworkManager[641]: <info>  [1545736605.2541] manager: NetworkManager state is now CONNECTED_LOCAL
Dec 25 12:16:45 hawking NetworkManager[641]: <info>  [1545736605.3504] manager: NetworkManager state is now CONNECTED_SITE
Dec 25 12:16:45 hawking NetworkManager[641]: <info>  [1545736605.3508] policy: set 'EasyBox' (wlp8s0) as default for IPv4 routing and DNS
Dec 25 12:16:45 hawking NetworkManager[641]: <info>  [1545736605.5120] device (wlp8s0): Activation: successful, device activated.
Dec 25 12:16:45 hawking NetworkManager[641]: <info>  [1545736605.5137] manager: startup complete
Dec 25 12:17:39 hawking NetworkManager[641]: <info>  [1545736659.9735] agent-manager: req[0x556c358bc890, :1.157/org.gnome.Shell.NetworkAgent/1000]: agent registered

And then, after opening Chromium, there's a new line:

Dec 25 12:20:59 hawking NetworkManager[641]: <info>  [1545736859.5824] manager: NetworkManager state is now CONNECTED_GLOBAL

Hope that someone has an idea on what is going on and how to fix this, I couldn't find any posts on this online or in the troubleshooting section of the Arch Wiki. Any help is greatly appreciated.

Last edited by novare (2018-12-26 19:24:16)

Offline

#2 2018-12-25 12:21:48

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 5,893

Re: [SOLVED] Network issues until opening Chromium, doesn't work with FF

NetworkManager's internal dhcp client tends to have issues, try to change that to something else: https://wiki.archlinux.org/index.php/Ne … HCP_client

Offline

#3 2018-12-26 12:02:17

novare
Member
Registered: 2018-12-25
Posts: 3

Re: [SOLVED] Network issues until opening Chromium, doesn't work with FF

Thanks for the tip, I tried both dhclient and dhcpcd, but neither of them fixed the issue. I still get the same behaviour (and journalctl entries) as before.

Offline

#4 2018-12-26 15:22:57

seth
Member
Registered: 2012-09-03
Posts: 9,440

Re: [SOLVED] Network issues until opening Chromium, doesn't work with FF

ps aux | grep systemd-resolved

In case it's running, drop it, ensure /etc/resolv.conf is no symlink. If resolved still buttfists itself in, see https://wiki.archlinux.org/index.php/Ne … onnections (ignore the header)

Offline

#5 2018-12-26 19:23:27

novare
Member
Registered: 2018-12-25
Posts: 3

Re: [SOLVED] Network issues until opening Chromium, doesn't work with FF

@seth disabling systemd-resolved fixed it for me; resolv.conf wasn't a symlink. I just rebooted after disabling resolved and the network manager connected without a question mark; all websites work properly. journalctl NetworkManager also immediately reports the "CONNECTED_GLOBAL" state after boot now.

I'll mark this as solved, thanks a lot!

Offline

Board footer

Powered by FluxBB