[Touch-packages] [Bug 2060813] [NEW] Upgrade UPower to 1.90.4 to lower cpu and disk usage
Public bug reported: Reference: https://www.phoronix.com/news/UPower-1.90.4-Released Upower 1.90.4 has been released, which fixes an issue making some users (maybe having Logitech devices and others) use more cpu and disk than intended. For me (I have Logitech mouse receiver), when I look at htop without doing anything, I see upower appearing there as using CPU. If the upgrade cannot be done at this stage, maybe the patch can be added to 1.90.2 (the current version in the repository of 24.04): https://gitlab.freedesktop.org/upower/upower/-/merge_requests/212 ** Affects: upower (Ubuntu) Importance: Undecided Status: New ** Package changed: apport (Ubuntu) => upower (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/2060813 Title: Upgrade UPower to 1.90.4 to lower cpu and disk usage Status in upower package in Ubuntu: New Bug description: Reference: https://www.phoronix.com/news/UPower-1.90.4-Released Upower 1.90.4 has been released, which fixes an issue making some users (maybe having Logitech devices and others) use more cpu and disk than intended. For me (I have Logitech mouse receiver), when I look at htop without doing anything, I see upower appearing there as using CPU. If the upgrade cannot be done at this stage, maybe the patch can be added to 1.90.2 (the current version in the repository of 24.04): https://gitlab.freedesktop.org/upower/upower/-/merge_requests/212 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/2060813/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 604212] Re: infobox does not show
This is happening to me in Kubuntu 18.04. Anyone has any clue on what's happening? I cannot install virtualbox because it seems to be asking me about Secure Boot password in a whiptail dialog which I cannot see. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to newt in Ubuntu. https://bugs.launchpad.net/bugs/604212 Title: infobox does not show Status in newt package in Ubuntu: Confirmed Bug description: A command as simple as whiptail --infobox Hello 0 0 prints nothing in xterm-like terminal emulators while it shoud draw a box with Hello written inside. I was able to understand what whiptail is doing with this strace command : strace -e t=write -s 5000 -o trace whiptail --infobox Hello 0 0 When whiptail processes the --infobox option, it does this : switch terminal to alternate screen draw information box switch back to normal screen exit The effect is that it is not possible to see the information message. Infobox messages are supposed to be displayed for a long time... whiptail should not switch screen in this case. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: whiptail 0.52.10-5ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-23-generic x86_64 NonfreeKernelModules: nvidia wl Architecture: amd64 Date: Sun Jul 11 09:09:04 2010 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) ProcEnviron: PATH=(custom, user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: newt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/newt/+bug/604212/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1755030] Re: Dell XPS 13 (9350) problems with suspend to memory fixed after disabling AppArmor
I don't know how, but this got fixed. Maybe one of the latest package updates fixed it. Thanks, this bug can be closed. ** Changed in: xorg (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1755030 Title: Dell XPS 13 (9350) problems with suspend to memory fixed after disabling AppArmor Status in xorg package in Ubuntu: Invalid Bug description: After installing latest Kubuntu 18.04 daily ISO and upgrading to latest packages, I've had problems with suspend functionality: 0- Kubuntu installed correctly. 1- From Plasma, choose "Suspend to memory". Screen goes off. 2- When I power on the notebook, it starts with Grub and then a new Kubuntu session starts. 3- After reading in forums that the problem could be SELinux, I disable AppArmor by doing "/etc/init.d/apparmor stop". 4- From Plasma, choose "Suspend to memory". Screen goes off. 5- When I power on the notebook, it continues in the same place where I left it. It seems that AppArmor is screwing Suspend in any way. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: KDE Date: Sun Mar 11 21:25:04 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: kubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:0704] InstallationDate: Installed on 2018-03-11 (0 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 0a5c:6412 Broadcom Corp. Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=007be772-95a8-4b68-9f65-de19978e0979 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/14/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.1 dmi.board.name: 07TYC2 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.1:bd12/14/2017:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.family: NULL dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.90-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1755030/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1434986] Re: Not working network connection after boot
I've opened a new bug report where I point to the possible cause of my problem so maybe someone comes up with a solution: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1756830 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1434986 Title: Not working network connection after boot Status in NetworkManager: Expired Status in network-manager package in Ubuntu: Triaged Bug description: Directly after boot the network connections are not working. I am connected and have an IP address, but I cannot establish a connection with any Internet server. I have the impression it is related to thee DNS lookup, which waits forever for a result. Cycling the connection (disconnect->reconnect) seems to fix the problem for some time. I am reporting this against network-manager, but I am not sure if it is directly in network manager or if it is systemd related. With 14.10 everything worked perfectly. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu11 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Mar 22 12:38:26 2015 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-01-30 (50 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IpRoute: default via 192.168.1.1 dev eth0 proto static metric 1024 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.26 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.29 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-03-19 (3 days ago) modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2015-02-16T00:14:50.662693 nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth0ethernet connected /org/freedesktop/NetworkManager/Devices/2 Kabelnetzwerkverbindung 1 4a581685-6002-4401-a993-49aa649667eb /org/freedesktop/NetworkManager/ActiveConnection/4 wlan0 wifi connected /org/freedesktop/NetworkManager/Devices/1 4A616E7320574C414E f45aa3a7-fb44-41b7-a02a-ea9720d79414 /org/freedesktop/NetworkManager/ActiveConnection/3 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1434986/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1756830] Re: Wifi connection don't autoconnect at boot but it works afterwards
I've tried the solution to Archlinux forum post and it works right now. The solution (more like a hack) is proposed here in the bottom message: https://superuser.com/questions/1278234/have-to-restart-networkmanager- to-get-wifi-autoconnect So, is anyone interested on trying a definitive solution to this? I can do whatever test you need, now that we know where the problem is. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1756830 Title: Wifi connection don't autoconnect at boot but it works afterwards Status in network-manager package in Ubuntu: New Bug description: I'm using Kubuntu 18.04 installed from a daily and updated to current. When I restart my pc, NetworkManager cannot connect to wifi. According to logs (autoattached and here: https://paste.ubuntu.com/p/fmcF6B5T6x/) the problem is that NetworkManager cannot get the password. If I wait until it errors out or click "Disconnect" then "Connect", it works perfect. I've seen users in some forums (https://bbs.archlinux.org/viewtopic.php?id=233519) telling that the problem is that when NetworkManager boots, KWallet is not yet available and so it doesn't have the password to connect to the wifi network. But if you click the "Connect" button, then KWallet is available and then it works. Maybe NetworkManager should depend on KWallet at boot (just Kubuntu, of course). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Mon Mar 19 10:18:03 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-03-11 (8 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310) IpRoute: default via 192.168.1.1 dev wlp58s0 proto dhcp metric 600 169.254.0.0/16 dev wlp58s0 scope link metric 1000 192.168.1.0/24 dev wlp58s0 proto kernel scope link src 192.168.1.133 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE MIWIFI_2G_y36Y 602d6129-d306-4b63-9b96-aa042a710863 wifi 1521450896 lun 19 mar 2018 10:14:56 CET yes 0 no /org/freedesktop/NetworkManager/Settings/1 yes wlp58s0 activated /org/freedesktop/NetworkManager/ActiveConnection/2 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlp58s0 wifi connected /org/freedesktop/NetworkManager/Devices/2 MIWIFI_2G_y36Y 602d6129-d306-4b63-9b96-aa042a710863 /org/freedesktop/NetworkManager/ActiveConnection/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.10.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1756830/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1756830] [NEW] Wifi connection don't autoconnect at boot but it works afterwards
Public bug reported: I'm using Kubuntu 18.04 installed from a daily and updated to current. When I restart my pc, NetworkManager cannot connect to wifi. According to logs (autoattached and here: https://paste.ubuntu.com/p/fmcF6B5T6x/) the problem is that NetworkManager cannot get the password. If I wait until it errors out or click "Disconnect" then "Connect", it works perfect. I've seen users in some forums (https://bbs.archlinux.org/viewtopic.php?id=233519) telling that the problem is that when NetworkManager boots, KWallet is not yet available and so it doesn't have the password to connect to the wifi network. But if you click the "Connect" button, then KWallet is available and then it works. Maybe NetworkManager should depend on KWallet at boot (just Kubuntu, of course). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Mon Mar 19 10:18:03 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-03-11 (8 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310) IpRoute: default via 192.168.1.1 dev wlp58s0 proto dhcp metric 600 169.254.0.0/16 dev wlp58s0 scope link metric 1000 192.168.1.0/24 dev wlp58s0 proto kernel scope link src 192.168.1.133 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE MIWIFI_2G_y36Y 602d6129-d306-4b63-9b96-aa042a710863 wifi 1521450896 lun 19 mar 2018 10:14:56 CET yes 0 no /org/freedesktop/NetworkManager/Settings/1 yes wlp58s0 activated /org/freedesktop/NetworkManager/ActiveConnection/2 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlp58s0 wifi connected /org/freedesktop/NetworkManager/Devices/2 MIWIFI_2G_y36Y 602d6129-d306-4b63-9b96-aa042a710863 /org/freedesktop/NetworkManager/ActiveConnection/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.10.4 connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1756830 Title: Wifi connection don't autoconnect at boot but it works afterwards Status in network-manager package in Ubuntu: New Bug description: I'm using Kubuntu 18.04 installed from a daily and updated to current. When I restart my pc, NetworkManager cannot connect to wifi. According to logs (autoattached and here: https://paste.ubuntu.com/p/fmcF6B5T6x/) the problem is that NetworkManager cannot get the password. If I wait until it errors out or click "Disconnect" then "Connect", it works perfect. I've seen users in some forums (https://bbs.archlinux.org/viewtopic.php?id=233519) telling that the problem is that when NetworkManager boots, KWallet is not yet available and so it doesn't have the password to connect to the wifi network. But if you click the "Connect" button, then KWallet is available and then it works. Maybe NetworkManager should depend on KWallet at boot (just Kubuntu, of course). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Mon Mar 19 10:18:03 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-03-11 (8 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310) IpRoute: default via 192.168.1.1 dev wlp58s0 proto dhcp metric 600 169.254.0.0/16 dev wlp58s0 scope link metric 1000 192.168.1.0/24 dev wlp58s0 proto kernel scope link src 192.168.1.133 metric 600 NetworkManager.state: [main] Network
[Touch-packages] [Bug 1434986] Re: Not working network connection after boot
This is the relevant part of syslog: Mar 19 00:03:31 host-XPS-13-9350 NetworkManager[663]: [1521414211.4577] device (wlp58s0): Activation: starting connection 'MIWIFI_2G_y36Y' (602d6129-d306-4b63-9b96-aa042a710863) Mar 19 00:03:31 host-XPS-13-9350 NetworkManager[663]: [1521414211.4649] device (wlp58s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') Mar 19 00:03:31 host-XPS-13-9350 NetworkManager[663]: [1521414211.4655] manager: NetworkManager state is now CONNECTING Mar 19 00:03:31 host-XPS-13-9350 NetworkManager[663]: [1521414211.4667] device (wlp58s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Mar 19 00:03:31 host-XPS-13-9350 NetworkManager[663]: [1521414211.4675] device (wlp58s0): Activation: (wifi) access point 'MIWIFI_2G_y36Y' has security, but secrets are required. Mar 19 00:03:31 host-XPS-13-9350 NetworkManager[663]: [1521414211.4680] device (wlp58s0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed') Mar 19 00:03:31 host-XPS-13-9350 NetworkManager[663]: [1521414211.4686] sup-iface[0x56229b8baaf0,wlp58s0]: wps: type pbc start... Mar 19 00:03:31 host-XPS-13-9350 NetworkManager[663]: [1521414211.4707] device (wlp58s0): No agents were available for this request. * Mar 19 00:03:31 host-XPS-13-9350 NetworkManager[663]: [1521414211.4780] device (wlp58s0): supplicant interface state: ready -> scanning Mar 19 00:04:02 host-XPS-13-9350 NetworkManager[663]: [1521414242.0905] device (wlp58s0): state change: need-auth -> failed (reason 'no-secrets', sys-iface-state: 'managed') Mar 19 00:04:02 host-XPS-13-9350 NetworkManager[663]: [1521414242.0914] manager: NetworkManager state is now DISCONNECTED Mar 19 00:04:02 host-XPS-13-9350 NetworkManager[663]: [1521414242.0929] device (wlp58s0): Activation: failed for connection 'MIWIFI_2G_y36Y' Mar 19 00:04:02 host-XPS-13-9350 NetworkManager[663]: [1521414242.0961] device (wlp58s0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') Mar 19 00:04:41 host-XPS-13-9350 NetworkManager[663]: [1521414281.9133] device (wlp58s0): Activation: starting connection 'MIWIFI_2G_y36Y' (602d6129-d306-4b63-9b96-aa042a710863) Mar 19 00:04:41 host-XPS-13-9350 NetworkManager[663]: [1521414281.9140] audit: op="connection-activate" uuid="602d6129-d306-4b63-9b96-aa042a710863" name="MIWIFI_2G_y36Y" pid=1079 uid=1000 result="success" Mar 19 00:04:41 host-XPS-13-9350 NetworkManager[663]: [1521414281.9147] device (wlp58s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') Mar 19 00:04:41 host-XPS-13-9350 NetworkManager[663]: [1521414281.9153] manager: NetworkManager state is now CONNECTING Mar 19 00:04:41 host-XPS-13-9350 NetworkManager[663]: [1521414281.9169] device (wlp58s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Mar 19 00:04:41 host-XPS-13-9350 NetworkManager[663]: [1521414281.9178] device (wlp58s0): Activation: (wifi) access point 'MIWIFI_2G_y36Y' has security, but secrets are required. Mar 19 00:04:41 host-XPS-13-9350 NetworkManager[663]: [1521414281.9179] device (wlp58s0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed') Mar 19 00:04:41 host-XPS-13-9350 NetworkManager[663]: [1521414281.9193] sup-iface[0x56229b8baaf0,wlp58s0]: wps: type pbc start... Mar 19 00:04:41 host-XPS-13-9350 NetworkManager[663]: [1521414281.9467] device (wlp58s0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed') Mar 19 00:04:41 host-XPS-13-9350 NetworkManager[663]: [1521414281.9475] device (wlp58s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Mar 19 00:04:41 host-XPS-13-9350 NetworkManager[663]: [1521414281.9682] device (wlp58s0): Activation: (wifi) connection 'MIWIFI_2G_y36Y' has security, and secrets exist. No new secrets needed. As you can see in the line where I put , the message says "No agents were available for this request". If I click on Disconnect and Connect that message doesn't appear in the logs and it works ok. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1434986 Title: Not working network connection after boot Status in NetworkManager: Expired Status in network-manager package in Ubuntu: Triaged Bug description: Directly after boot the network connections are not working. I am connected and have an IP address, but I cannot establish a connection with any Internet server. I have the impression it is related to thee DNS lookup, which waits forever for a result. Cycling the connection (disconnect->reconnect) seems to fix the problem for some time. I am reporting this against network-manager, but I am not s
[Touch-packages] [Bug 1434986] Re: Not working network connection after boot
I have this problem in 18.04 daily with latest updates. It happens only at boot. If I suspend to memory and resume, it connects to wifi without any problem. - I don't have package dnsmasq to uninstall it - I disabled ipv6 - I don't have "dns=dnsmasq" in NetworkManager.conf Any clue on what's happening? Will try to get some logs later. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1434986 Title: Not working network connection after boot Status in NetworkManager: Expired Status in network-manager package in Ubuntu: Triaged Bug description: Directly after boot the network connections are not working. I am connected and have an IP address, but I cannot establish a connection with any Internet server. I have the impression it is related to thee DNS lookup, which waits forever for a result. Cycling the connection (disconnect->reconnect) seems to fix the problem for some time. I am reporting this against network-manager, but I am not sure if it is directly in network manager or if it is systemd related. With 14.10 everything worked perfectly. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu11 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Mar 22 12:38:26 2015 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-01-30 (50 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IpRoute: default via 192.168.1.1 dev eth0 proto static metric 1024 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.26 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.29 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-03-19 (3 days ago) modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2015-02-16T00:14:50.662693 nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth0ethernet connected /org/freedesktop/NetworkManager/Devices/2 Kabelnetzwerkverbindung 1 4a581685-6002-4401-a993-49aa649667eb /org/freedesktop/NetworkManager/ActiveConnection/4 wlan0 wifi connected /org/freedesktop/NetworkManager/Devices/1 4A616E7320574C414E f45aa3a7-fb44-41b7-a02a-ea9720d79414 /org/freedesktop/NetworkManager/ActiveConnection/3 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1434986/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1755030] [NEW] Dell XPS 13 (9350) problems with suspend to memory fixed after disabling AppArmor
Public bug reported: After installing latest Kubuntu 18.04 daily ISO and upgrading to latest packages, I've had problems with suspend functionality: 0- Kubuntu installed correctly. 1- From Plasma, choose "Suspend to memory". Screen goes off. 2- When I power on the notebook, it starts with Grub and then a new Kubuntu session starts. 3- After reading in forums that the problem could be SELinux, I disable AppArmor by doing "/etc/init.d/apparmor stop". 4- From Plasma, choose "Suspend to memory". Screen goes off. 5- When I power on the notebook, it continues in the same place where I left it. It seems that AppArmor is screwing Suspend in any way. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: KDE Date: Sun Mar 11 21:25:04 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: kubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:0704] InstallationDate: Installed on 2018-03-11 (0 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 0a5c:6412 Broadcom Corp. Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=007be772-95a8-4b68-9f65-de19978e0979 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/14/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.1 dmi.board.name: 07TYC2 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.1:bd12/14/2017:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.family: NULL dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.90-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic kubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1755030 Title: Dell XPS 13 (9350) problems with suspend to memory fixed after disabling AppArmor Status in xorg package in Ubuntu: New Bug description: After installing latest Kubuntu 18.04 daily ISO and upgrading to latest packages, I've had problems with suspend functionality: 0- Kubuntu installed correctly. 1- From Plasma, choose "Suspend to memory". Screen goes off. 2- When I power on the notebook, it starts with Grub and then a new Kubuntu session starts. 3- After reading in forums that the problem could be SELinux, I disable AppArmor by doing "/etc/init.d/apparmor stop". 4- From Plasma, choose "Suspend to memory". Screen goes off. 5- When I power on the notebook, it continues in the same place where I left it. It seems that AppArmor is screwing Suspend in any way. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: KDE Date: Sun Mar 11 21:25:04 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: kubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:0704] InstallationDate: Installed on 2018-03-11 (0 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 0a5c:6412 Br
