^@ about twice a second in active pure terminal (affects some UI). Fail to shutdown properly.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I am not sure that this is a network-manager fault... just because it causes troubles on shutdown (see shutdown section below). Network manager is fine while system is running...
PROBLEMS
I used Ubuntu Mate 17.04 and was happy. After 17.10 release I upgraded system with Software Updater tool. Upgrade was successful. But after a day or so I noticed some problems with UI:
- When try to select a group of object on desktop or in the caja file manager the selection is gone in about a second.
- Some popups (my translator plugin in firefox) was closed after appearing.
- When press and hold a key (arrow key to navigate in text or just a symbol) the input was interrupted in about a second, like I release the button. (For different desktops UI troubles are different, but problem with pressing and holding key is common for KDE 5, Gnome 3 and Mate).
Then I noticed "^@" (without quotes) sequence appears in pure terminal (Ctrl + Alt + F[1-8]) a bit more frequently than a second. Probably it brakes UI.
I reinstalled Ubuntu Mate 17.10 from scratch, but the problem remains. I also tried Kubuntu 17.10 and now Ubuntu 17.10 (with Gnome 3) with persistent install but problem is still here. More the problem is present when I boot from usb stick. But I have no troubles on Ubuntu 17.04 Mate and Windows 10
WHAT I TRIED
- Update BIOS to the latest version
- Update Intel microcode
- Uncheck "Use Intel Microcode" from Device Manager
- Switch between proprietary and Xorg drivers for NVidia
- Unmount and spin off HDD
- Add wi-fi kernel modules (ath, ath10k_core, ath10k_pci) into blacklist (seems that it had no effect, they were loaded)
- Install all updates
SHUTDOWN PROBLEM
System cannot shutdown properly. It can hung (or maybe just waits and doesn't show any logs or shows only a few lines - once it happens) or, in most cases, I see:
[ *** ] A stop job is running for Network Manager (<waiting time>/<max time to wait>)
OR
[ *** ] A stop job is running for WPA supplicant (<waiting time>/<max time to wait>)
And later this
INFO task kworker/<info> blocked for more than 120 seconds
is added to the line
Where <info> could be different, for example: u8:2:169 or 0:1:33
If I wait about 6 or so minutes I finally can see:
Reached target Shutdown
But the laptop is still on and I have have to hold power button a few seconds to halt it.
(for more information see attached photo-screenshots
HARDWARE
I have used Lenovo ideapad 700-15ISK all the time without hardware modifications.
P.S.
Feel free to ping me if you need additional info. Also I always can experiment from live usb stick.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: network-manager 1.8.4-1ubuntu3
ProcVersionSign
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.4
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov 19 11:22:44 2017
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2017-11-19 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
IpRoute:
default via 192.168.1.1 dev wlp2s0 proto static metric 600
169.254.0.0/16 dev wlp2s0 scope link metric 1000
192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.10 metric 600
ProcEnviron:
TERM=xterm-
PATH=(custom, no username)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con:
NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-
MNANSHFF 31d5cdf0-
Wired connection 1 3b76cb02-
nmcli-dev:
DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH
wlp2s0 wifi connected /org/freedeskto
enp3s0 ethernet unavailable /org/freedeskto
lo loopback unmanaged /org/freedeskto
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN
running 1.8.4 connected started full enabled enabled enabled enabled enabled
A photo-screenshot after more then 5 min wait