[Bug 1734750] Re: Fail to shutdown system properly
I decided to update system again after bug report and... it gone. Sorry for disturbing. Seems this issue can be closed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734750 Title: Fail to shutdown system properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1734750/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1734750] [NEW] Fail to shutdown system properly
Public bug reported: I use Ubuntu Mate 17.10 installed from scratch on Lenovo ideapad 700-15ISK (standard hardware - no modifications). When I try to reboot or shutdown I see messages like: [ *** ] A stop job is running for Network Manager (/) OR [ *** ] A stop job is running for WPA supplicant (/) (Messages appears periodically, replacing each other), and later this INFO task kworker/ blocked for more than 120 seconds is added to the line Where 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. I've tried: - Update BIOS to the latest version - Update Intel microcode - Uncheck "Use Intel Microcode" from Device Manager - Install all updates But the problem is persistent and I run into it each time I want to shutdown/reboot my laptop. It even can be reproduced from live usb stick (reboot after install). However, during regular work everything is fine. Before I used Ubuntu Mate 17.04 and such problem appears in some rare cases on shutdown/reboot (hard to say exactly, roughly 1 of 10 or even more shutdowns). Before I created bug https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/1733203 but it turned out to be two different bugs and there are attached photos of logs on shutdown. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: network-manager 1.8.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Mon Nov 27 13:40:10 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-11-27 (0 days ago) InstallationMedia: Ubuntu-MATE 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 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE MNANSHFF2df64dd7-961d-47cd-acce-5fc9aec6ce8d 802-11-wireless 1511807923 Mon 27 Nov 2017 01:38:43 PM EST yes 0 no/org/freedesktop/NetworkManager/Settings/1 yes wlp2s0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- Wired connection 1 9794efad-4922-3754-bb66-2a49594348d1 802-3-ethernet 1511807906 Mon 27 Nov 2017 01:38:26 PM EST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/2 no -- -- -- -- nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connected/org/freedesktop/NetworkManager/Devices/3 MNANSHFF2df64dd7-961d-47cd-acce-5fc9aec6ce8d /org/freedesktop/NetworkManager/ActiveConnection/1 enp3s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.8.4connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734750 Title: Fail to shutdown system properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1734750/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1733203] Re: ^@ about twice a second in active pure terminal (affects some UI). Fail to shutdown properly.
Yes, after $ sudo modprobe -r peaq-wmi the problems with ^@ and UI are gone. But live system failed to shutdown properly... Just blinking underscore into left-upper corner... Will it gone after persistent install? I can add the peaq-wmi module into blacklist, but what is the consequence after it? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1733203 Title: ^@ about twice a second in active pure terminal (affects some UI). Fail to shutdown properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1733203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1733203] Re: ^@ about twice a second in active pure terminal (affects some UI). Fail to shutdown properly.
And yes, thank you very much! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1733203 Title: ^@ about twice a second in active pure terminal (affects some UI). Fail to shutdown properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1733203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1733203] [NEW] ^@ about twice a second in active pure terminal (affects some UI). Fail to shutdown properly.
Public bug reported: 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 (/) OR [ *** ] A stop job is running for WPA supplicant (/) And later this INFO task kworker/ blocked for more than 120 seconds is added to the line Where 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 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 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-256color PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE MNANSHFF31d5cdf0-fc8c-49e9-8a3d-e3dcb0d6d609 802-11-wireless 1511108472 Sun 19 Nov 2017 11:21:12 AM EST yes 0 no/org/freedesktop/NetworkManager/Settings/1 yes wlp2s0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- Wired connection 1 3b76cb02-e9c2-3733-8cbd-8544a235b4f5 802-3-ethernet 1511105771 Sun 19 Nov 2017 10:36:11 AM EST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/2 no -- -- -- -- nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connected/org/freedesktop/NetworkManager/Devices/3 MNANSHFF31d5cdf0-fc8c-49e9-8a3d-e3dcb0d6d609 /org/freedesktop/NetworkManager/ActiveConnection/1 enp3s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged
[Bug 1733203] Re: ^@ about twice a second in active pure terminal (affects some UI). Fail to shutdown properly.
"A stop job is running..." photo-screenshot ** Attachment added: "20171119_173102.jpg" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1733203/+attachment/5011344/+files/20171119_173102.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1733203 Title: ^@ about twice a second in active pure terminal (affects some UI). Fail to shutdown properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1733203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1733203] Re: ^@ about twice a second in active pure terminal (affects some UI). Fail to shutdown properly.
A photo-screenshot after more then 5 min wait ** Attachment added: "20171119_173532.jpg" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1733203/+attachment/5011343/+files/20171119_173532.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1733203 Title: ^@ about twice a second in active pure terminal (affects some UI). Fail to shutdown properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1733203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1733203] Re: ^@ about twice a second in active pure terminal (affects some UI). Fail to shutdown properly.
** Attachment added: "20171119_173304.jpg" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1733203/+attachment/5011345/+files/20171119_173304.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1733203 Title: ^@ about twice a second in active pure terminal (affects some UI). Fail to shutdown properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1733203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 553200] Re: Mouse and keyboard stop working after selecting user
Installed from PPA, and issue is fixed. Thanks Aaron and Alberto :) -- Mouse and keyboard stop working after selecting user https://bugs.launchpad.net/bugs/553200 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 526379] Re: GDM login fails with regular gnome-session (lucid, i386)
I think I also have this bug, or similar, after an apt-get upgrade and apt-get dist-upgrade from Lucid B1 to B2. When I get to GDM, everything works perfectly, I can switch to a console, and login as normal. But if I click on a username in GDM to login, it freezes for a second or two, the screen turns black, and it appears as if GDM has restarted itself. Everything works as it should from a failsafe X session, which is where I attach these from. If I should attach anything else, let me know please. My graphics card is an Nvidia GeForce4 MX440 [AGP] using the Nvidia-96 driver. Attached /var/log/gdm/:0-greeter.log.1 /var/log/Xorg.0.log.old ** Attachment added: /var/log/:0-greeter.log.1 http://launchpadlibrarian.net/44192344/%3A0-greeter.log.txt -- GDM login fails with regular gnome-session (lucid, i386) https://bugs.launchpad.net/bugs/526379 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 526379] Re: GDM login fails with regular gnome-session (lucid, i386)
** Attachment added: /var/log/Xorg.0.log.old http://launchpadlibrarian.net/44192445/Xorg.0.log.old.txt -- GDM login fails with regular gnome-session (lucid, i386) https://bugs.launchpad.net/bugs/526379 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 526379] Re: GDM login fails with regular gnome-session (lucid, i386)
Also attaching .xsession-errors if that's any help. ** Attachment added: xsession-errors.txt http://launchpadlibrarian.net/44192525/xsession-errors.txt -- GDM login fails with regular gnome-session (lucid, i386) https://bugs.launchpad.net/bugs/526379 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 553200] Re: Mouse and keyboard stop working after selecting user
I have the same problem, and am using the Nvidia-96 driver, on a Geforce4 MX440 AGP. ** Attachment added: Xorg.0.log.old.txt http://launchpadlibrarian.net/44198486/Xorg.0.log.old.txt -- Mouse and keyboard stop working after selecting user https://bugs.launchpad.net/bugs/553200 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 526379] Re: GDM login fails with regular gnome-session (lucid, i386)
Apologies, it turns out that the bug I suffer from is #553200. My apologies for dumping my stuff here in error. :) -- GDM login fails with regular gnome-session (lucid, i386) https://bugs.launchpad.net/bugs/526379 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
