[Touch-packages] [Bug 1988119] Re: systemd-udevd: Run net_setup_link on 'change' uevents to prevent DNS outages on Azure
I just created a new worker nodepool this morning, en redschedulded all pods to the new workers. Solved it for us. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1988119 Title: systemd-udevd: Run net_setup_link on 'change' uevents to prevent DNS outages on Azure Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Released Bug description: [Impact] A widespread outage was caused on Azure instances earlier today, when systemd 237-3ubuntu10.54 was published to the bionic-security pocket. Instances could no longer resolve DNS queries, breaking networking. For affected users, the following workarounds are available. Use whatever is most convenient. - Reboot your instances - or - - Issue "udevadm trigger -cadd -yeth0 && systemctl restart systemd-networkd" as root The trigger was found to be open-vm-tools issuing "udevadm trigger". Azure has a specific netplan setup that uses the `driver` match to set up networking. If a udevadm trigger is executed, the KV pair that contains this info is lost. Next time netplan is executed, the server loses it's DNS information. This is the same as bug 1902960 experienced on Focal two years ago. The root cause was found to be a bug in systemd, where if we receive a "Remove" action from a change uevent, we need to run net_setup_link(), we need to skip device rename and keep the old name. [Testcase] Start an instance up on Azure, any type. Simply issue udevadm trigger and reload systemd-networkd: $ ping google.com PING google.com (172.253.62.102) 56(84) bytes of data. 64 bytes from bc-in-f102.1e100.net (172.253.62.102): icmp_seq=1 ttl=56 time=1.85 ms $ sudo udevadm trigger && sudo systemctl restart systemd-networkd $ ping google.com ping: google.com: Temporary failure in name resolution To fix a broken instance, you can run: $ sudo udevadm trigger -cadd -yeth0 && sudo systemctl restart systemd- networkd and then install the test packages below: Test packages are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf343528-test If you install them, the issue should no longer occur. [Where problems could occur] If a regression were to occur, it would affect systemd-udevd processing 'change' events from network devices, which could lead to network outages. Since this would happen when systemd-networkd is restarted on postinstall, a regression would cause widespread outages due to this SRU being targeted to the security pocket, where unattended-upgrades will automatically install from. Side effects could include incorrect udevd device properties. It is very important that this SRU is well tested before release. [Other info] This was fixed in Systemd 247 with the following commit: commit e0e789c1e97e2cdf1cafe0c6b7d7e43fa054f151 Author: Yu Watanabe Date: Mon, 14 Sep 2020 15:21:04 +0900 Subject: udev: re-assign ID_NET_DRIVER=, ID_NET_LINK_FILE=, ID_NET_NAME= properties on non-'add' uevent Link: https://github.com/systemd/systemd/commit/e0e789c1e97e2cdf1cafe0c6b7d7e43fa054f151 This was backported to Focal's systemd 245.4-4ubuntu3.4 in bug 1902960 two years ago. Focal required a heavy backport, which was performed by Dan Streetman. Focals backport can be found in d/p/lp1902960-udev-re- assign-ID_NET_DRIVER-ID_NET_LINK_FILE-ID_NET.patch, or the below pastebin: https://paste.ubuntu.com/p/K5k7bGt3Wx/ The changes between the Focal backport and the Bionic backport are: - We use udev_device_get_action() instead of device_get_action() - device_action_from_string() is used to get to enum DeviceAction - We return 0 from the "if (a == DEVICE_ACTION_MOVE) " hunk instead of "goto no_rename" - log_device_* has been changed to log_*. See attached debdiff for Bionic backport. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988119/+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 1827879] Re: Killer Wireless 1525 firmware crashes on suspend
Yes, nothing changed as far as i know, so the issue remains -- 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/1827879 Title: Killer Wireless 1525 firmware crashes on suspend Status in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: Problem: Ubuntu running on Alienware 17 R2 system hangs on suspend. The Keyboard LED's stay on and FAN keeps running. Strangely this does not happen in Fedora 29 (Kernel 4.18 & same board firmware) System: Ubuntu 19.04 Kernel 5.0.0-13-generic Wireless chipset Killer Wireless 1525 (Atheros QCA6174, hw2.1) Wireless info: description: Wireless interface product: QCA6174 802.11ac Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:03:00.0 logical name: wlp3s0 version: 20 serial: 40:b8:9a:ca:2b:99 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=ath10k_pci driverversion=5.0.0-13-generic firmware=SW_RM.1.1.1-00157-QCARMSWPZ-1 ip=192.168.55.161 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:32 memory:f680-f69f My attempts: 1. Tried other kernels: 5.0.12, 4.20.17, 4.19.7, 4.18.16, 4.18.0, 4.16.0, 4.14.114 2. Tried several distro's based on ubuntu -> all have the same issue 3. Checked firmware from Fedora 29 (md5sum was equal) and updated firmware (not available, using latest) 4. Created systemd scripts for disabling & enabling the driver, this causes the same crashes in /var/log/syslog See: https://forum.manjaro.org/t/solved-qca6174-freez-after-suspend/66232/11 5. Physically replaced Killer 1525 with Intel 8260 --> problem is gone, standby works perfectly Of course i want to be able to use the 1525, so please help me solve the issue. Happy to perform additional debugging if required. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sander 1527 F pulseaudio /dev/snd/controlC0: sander 1527 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.55.1 dev wlp3s0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.55.0/24 dev wlp3s0 proto kernel scope link src 192.168.55.58 metric 600 MachineType: Alienware Alienware 17 R2 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.16.0-0ubuntu2 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=9f06fd28-fdb2-4ada-986f-1e7eb1b87882 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 Tags: disco Uname: Linux 5.0.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/31/2017 dmi.bios.vendor: Alienware dmi.bios.version: A08 dmi.board.name: Alienware 17 R2 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A08 dmi.modalias: dmi:bvnAlienware:bvrA08:bd03/31/2017:svnAlienware:pnAlienware17R2:pvrA08:rvnAlienware:rnAlienware17R2:rvrA00:cvnAlienware:ct8:cvrA08: dmi.product.family: Alienware 17 R2 dmi.product.name: Alienware 17 R2 dmi.product.sku: Alienware 15 dmi.product.version: A08 dmi.sys.vendor: Alienware nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.16.0 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1827879/+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 1827879] NetDevice.lo.txt
apport information ** Attachment added: "NetDevice.lo.txt" https://bugs.launchpad.net/bugs/1827879/+attachment/5264335/+files/NetDevice.lo.txt -- 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/1827879 Title: Killer Wireless 1525 firmware crashes on suspend Status in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: Problem: Ubuntu running on Alienware 17 R2 system hangs on suspend. The Keyboard LED's stay on and FAN keeps running. Strangely this does not happen in Fedora 29 (Kernel 4.18 & same board firmware) System: Ubuntu 19.04 Kernel 5.0.0-13-generic Wireless chipset Killer Wireless 1525 (Atheros QCA6174, hw2.1) Wireless info: description: Wireless interface product: QCA6174 802.11ac Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:03:00.0 logical name: wlp3s0 version: 20 serial: 40:b8:9a:ca:2b:99 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=ath10k_pci driverversion=5.0.0-13-generic firmware=SW_RM.1.1.1-00157-QCARMSWPZ-1 ip=192.168.55.161 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:32 memory:f680-f69f My attempts: 1. Tried other kernels: 5.0.12, 4.20.17, 4.19.7, 4.18.16, 4.18.0, 4.16.0, 4.14.114 2. Tried several distro's based on ubuntu -> all have the same issue 3. Checked firmware from Fedora 29 (md5sum was equal) and updated firmware (not available, using latest) 4. Created systemd scripts for disabling & enabling the driver, this causes the same crashes in /var/log/syslog See: https://forum.manjaro.org/t/solved-qca6174-freez-after-suspend/66232/11 5. Physically replaced Killer 1525 with Intel 8260 --> problem is gone, standby works perfectly Of course i want to be able to use the 1525, so please help me solve the issue. Happy to perform additional debugging if required. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sander 1527 F pulseaudio /dev/snd/controlC0: sander 1527 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.55.1 dev wlp3s0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.55.0/24 dev wlp3s0 proto kernel scope link src 192.168.55.58 metric 600 MachineType: Alienware Alienware 17 R2 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.16.0-0ubuntu2 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=9f06fd28-fdb2-4ada-986f-1e7eb1b87882 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 Tags: disco Uname: Linux 5.0.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/31/2017 dmi.bios.vendor: Alienware dmi.bios.version: A08 dmi.board.name: Alienware 17 R2 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A08 dmi.modalias: dmi:bvnAlienware:bvrA08:bd03/31/2017:svnAlienware:pnAlienware17R2:pvrA08:rvnAlienware:rnAlienware17R2:rvrA00:cvnAlienware:ct8:cvrA08: dmi.product.family: Alienware 17 R2 dmi.product.name: Alienware 17 R2 dmi.product.sku: Alienware 15 dmi.product.version: A08 dmi.sys.vendor: Alienware nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.16.0 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1827879/+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 1827879] NetDevice.enp2s0.txt
apport information ** Attachment added: "NetDevice.enp2s0.txt" https://bugs.launchpad.net/bugs/1827879/+attachment/5264334/+files/NetDevice.enp2s0.txt -- 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/1827879 Title: Killer Wireless 1525 firmware crashes on suspend Status in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: Problem: Ubuntu running on Alienware 17 R2 system hangs on suspend. The Keyboard LED's stay on and FAN keeps running. Strangely this does not happen in Fedora 29 (Kernel 4.18 & same board firmware) System: Ubuntu 19.04 Kernel 5.0.0-13-generic Wireless chipset Killer Wireless 1525 (Atheros QCA6174, hw2.1) Wireless info: description: Wireless interface product: QCA6174 802.11ac Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:03:00.0 logical name: wlp3s0 version: 20 serial: 40:b8:9a:ca:2b:99 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=ath10k_pci driverversion=5.0.0-13-generic firmware=SW_RM.1.1.1-00157-QCARMSWPZ-1 ip=192.168.55.161 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:32 memory:f680-f69f My attempts: 1. Tried other kernels: 5.0.12, 4.20.17, 4.19.7, 4.18.16, 4.18.0, 4.16.0, 4.14.114 2. Tried several distro's based on ubuntu -> all have the same issue 3. Checked firmware from Fedora 29 (md5sum was equal) and updated firmware (not available, using latest) 4. Created systemd scripts for disabling & enabling the driver, this causes the same crashes in /var/log/syslog See: https://forum.manjaro.org/t/solved-qca6174-freez-after-suspend/66232/11 5. Physically replaced Killer 1525 with Intel 8260 --> problem is gone, standby works perfectly Of course i want to be able to use the 1525, so please help me solve the issue. Happy to perform additional debugging if required. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sander 1527 F pulseaudio /dev/snd/controlC0: sander 1527 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.55.1 dev wlp3s0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.55.0/24 dev wlp3s0 proto kernel scope link src 192.168.55.58 metric 600 MachineType: Alienware Alienware 17 R2 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.16.0-0ubuntu2 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=9f06fd28-fdb2-4ada-986f-1e7eb1b87882 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 Tags: disco Uname: Linux 5.0.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/31/2017 dmi.bios.vendor: Alienware dmi.bios.version: A08 dmi.board.name: Alienware 17 R2 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A08 dmi.modalias: dmi:bvnAlienware:bvrA08:bd03/31/2017:svnAlienware:pnAlienware17R2:pvrA08:rvnAlienware:rnAlienware17R2:rvrA00:cvnAlienware:ct8:cvrA08: dmi.product.family: Alienware 17 R2 dmi.product.name: Alienware 17 R2 dmi.product.sku: Alienware 15 dmi.product.version: A08 dmi.sys.vendor: Alienware nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.16.0 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1827879/+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 1827879] nmcli-dev.txt
apport information ** Attachment added: "nmcli-dev.txt" https://bugs.launchpad.net/bugs/1827879/+attachment/5264348/+files/nmcli-dev.txt -- 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/1827879 Title: Killer Wireless 1525 firmware crashes on suspend Status in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: Problem: Ubuntu running on Alienware 17 R2 system hangs on suspend. The Keyboard LED's stay on and FAN keeps running. Strangely this does not happen in Fedora 29 (Kernel 4.18 & same board firmware) System: Ubuntu 19.04 Kernel 5.0.0-13-generic Wireless chipset Killer Wireless 1525 (Atheros QCA6174, hw2.1) Wireless info: description: Wireless interface product: QCA6174 802.11ac Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:03:00.0 logical name: wlp3s0 version: 20 serial: 40:b8:9a:ca:2b:99 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=ath10k_pci driverversion=5.0.0-13-generic firmware=SW_RM.1.1.1-00157-QCARMSWPZ-1 ip=192.168.55.161 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:32 memory:f680-f69f My attempts: 1. Tried other kernels: 5.0.12, 4.20.17, 4.19.7, 4.18.16, 4.18.0, 4.16.0, 4.14.114 2. Tried several distro's based on ubuntu -> all have the same issue 3. Checked firmware from Fedora 29 (md5sum was equal) and updated firmware (not available, using latest) 4. Created systemd scripts for disabling & enabling the driver, this causes the same crashes in /var/log/syslog See: https://forum.manjaro.org/t/solved-qca6174-freez-after-suspend/66232/11 5. Physically replaced Killer 1525 with Intel 8260 --> problem is gone, standby works perfectly Of course i want to be able to use the 1525, so please help me solve the issue. Happy to perform additional debugging if required. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sander 1527 F pulseaudio /dev/snd/controlC0: sander 1527 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.55.1 dev wlp3s0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.55.0/24 dev wlp3s0 proto kernel scope link src 192.168.55.58 metric 600 MachineType: Alienware Alienware 17 R2 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.16.0-0ubuntu2 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=9f06fd28-fdb2-4ada-986f-1e7eb1b87882 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 Tags: disco Uname: Linux 5.0.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/31/2017 dmi.bios.vendor: Alienware dmi.bios.version: A08 dmi.board.name: Alienware 17 R2 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A08 dmi.modalias: dmi:bvnAlienware:bvrA08:bd03/31/2017:svnAlienware:pnAlienware17R2:pvrA08:rvnAlienware:rnAlienware17R2:rvrA00:cvnAlienware:ct8:cvrA08: dmi.product.family: Alienware 17 R2 dmi.product.name: Alienware 17 R2 dmi.product.sku: Alienware 15 dmi.product.version: A08 dmi.sys.vendor: Alienware nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.16.0 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1827879/+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 1827879] Re: Killer Wireless 1525 firmware crashes on suspend
Please note that the killer wireless card is replaced by intel when running apport-collect. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- 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/1827879 Title: Killer Wireless 1525 firmware crashes on suspend Status in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: Problem: Ubuntu running on Alienware 17 R2 system hangs on suspend. The Keyboard LED's stay on and FAN keeps running. Strangely this does not happen in Fedora 29 (Kernel 4.18 & same board firmware) System: Ubuntu 19.04 Kernel 5.0.0-13-generic Wireless chipset Killer Wireless 1525 (Atheros QCA6174, hw2.1) Wireless info: description: Wireless interface product: QCA6174 802.11ac Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:03:00.0 logical name: wlp3s0 version: 20 serial: 40:b8:9a:ca:2b:99 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=ath10k_pci driverversion=5.0.0-13-generic firmware=SW_RM.1.1.1-00157-QCARMSWPZ-1 ip=192.168.55.161 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:32 memory:f680-f69f My attempts: 1. Tried other kernels: 5.0.12, 4.20.17, 4.19.7, 4.18.16, 4.18.0, 4.16.0, 4.14.114 2. Tried several distro's based on ubuntu -> all have the same issue 3. Checked firmware from Fedora 29 (md5sum was equal) and updated firmware (not available, using latest) 4. Created systemd scripts for disabling & enabling the driver, this causes the same crashes in /var/log/syslog See: https://forum.manjaro.org/t/solved-qca6174-freez-after-suspend/66232/11 5. Physically replaced Killer 1525 with Intel 8260 --> problem is gone, standby works perfectly Of course i want to be able to use the 1525, so please help me solve the issue. Happy to perform additional debugging if required. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sander 1527 F pulseaudio /dev/snd/controlC0: sander 1527 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.55.1 dev wlp3s0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.55.0/24 dev wlp3s0 proto kernel scope link src 192.168.55.58 metric 600 MachineType: Alienware Alienware 17 R2 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.16.0-0ubuntu2 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=9f06fd28-fdb2-4ada-986f-1e7eb1b87882 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 Tags: disco Uname: Linux 5.0.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/31/2017 dmi.bios.vendor: Alienware dmi.bios.version: A08 dmi.board.name: Alienware 17 R2 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A08 dmi.modalias: dmi:bvnAlienware:bvrA08:bd03/31/2017:svnAlienware:pnAlienware17R2:pvrA08:rvnAlienware:rnAlienware17R2:rvrA00:cvnAlienware:ct8:cvrA08: dmi.product.family: Alienware 17 R2 dmi.product.name: Alienware 17 R2 dmi.product.sku: Alienware 15 dmi.product.version: A08 dmi.sys.vendor: Alienware nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.16.0 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1827879/+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 1827879] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1827879/+attachment/5264346/+files/WifiSyslog.txt -- 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/1827879 Title: Killer Wireless 1525 firmware crashes on suspend Status in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: Problem: Ubuntu running on Alienware 17 R2 system hangs on suspend. The Keyboard LED's stay on and FAN keeps running. Strangely this does not happen in Fedora 29 (Kernel 4.18 & same board firmware) System: Ubuntu 19.04 Kernel 5.0.0-13-generic Wireless chipset Killer Wireless 1525 (Atheros QCA6174, hw2.1) Wireless info: description: Wireless interface product: QCA6174 802.11ac Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:03:00.0 logical name: wlp3s0 version: 20 serial: 40:b8:9a:ca:2b:99 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=ath10k_pci driverversion=5.0.0-13-generic firmware=SW_RM.1.1.1-00157-QCARMSWPZ-1 ip=192.168.55.161 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:32 memory:f680-f69f My attempts: 1. Tried other kernels: 5.0.12, 4.20.17, 4.19.7, 4.18.16, 4.18.0, 4.16.0, 4.14.114 2. Tried several distro's based on ubuntu -> all have the same issue 3. Checked firmware from Fedora 29 (md5sum was equal) and updated firmware (not available, using latest) 4. Created systemd scripts for disabling & enabling the driver, this causes the same crashes in /var/log/syslog See: https://forum.manjaro.org/t/solved-qca6174-freez-after-suspend/66232/11 5. Physically replaced Killer 1525 with Intel 8260 --> problem is gone, standby works perfectly Of course i want to be able to use the 1525, so please help me solve the issue. Happy to perform additional debugging if required. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sander 1527 F pulseaudio /dev/snd/controlC0: sander 1527 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.55.1 dev wlp3s0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.55.0/24 dev wlp3s0 proto kernel scope link src 192.168.55.58 metric 600 MachineType: Alienware Alienware 17 R2 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.16.0-0ubuntu2 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=9f06fd28-fdb2-4ada-986f-1e7eb1b87882 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 Tags: disco Uname: Linux 5.0.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/31/2017 dmi.bios.vendor: Alienware dmi.bios.version: A08 dmi.board.name: Alienware 17 R2 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A08 dmi.modalias: dmi:bvnAlienware:bvrA08:bd03/31/2017:svnAlienware:pnAlienware17R2:pvrA08:rvnAlienware:rnAlienware17R2:rvrA00:cvnAlienware:ct8:cvrA08: dmi.product.family: Alienware 17 R2 dmi.product.name: Alienware 17 R2 dmi.product.sku: Alienware 15 dmi.product.version: A08 dmi.sys.vendor: Alienware nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.16.0 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1827879/+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 1827879] nmcli-con.txt
apport information ** Attachment added: "nmcli-con.txt" https://bugs.launchpad.net/bugs/1827879/+attachment/5264347/+files/nmcli-con.txt -- 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/1827879 Title: Killer Wireless 1525 firmware crashes on suspend Status in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: Problem: Ubuntu running on Alienware 17 R2 system hangs on suspend. The Keyboard LED's stay on and FAN keeps running. Strangely this does not happen in Fedora 29 (Kernel 4.18 & same board firmware) System: Ubuntu 19.04 Kernel 5.0.0-13-generic Wireless chipset Killer Wireless 1525 (Atheros QCA6174, hw2.1) Wireless info: description: Wireless interface product: QCA6174 802.11ac Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:03:00.0 logical name: wlp3s0 version: 20 serial: 40:b8:9a:ca:2b:99 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=ath10k_pci driverversion=5.0.0-13-generic firmware=SW_RM.1.1.1-00157-QCARMSWPZ-1 ip=192.168.55.161 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:32 memory:f680-f69f My attempts: 1. Tried other kernels: 5.0.12, 4.20.17, 4.19.7, 4.18.16, 4.18.0, 4.16.0, 4.14.114 2. Tried several distro's based on ubuntu -> all have the same issue 3. Checked firmware from Fedora 29 (md5sum was equal) and updated firmware (not available, using latest) 4. Created systemd scripts for disabling & enabling the driver, this causes the same crashes in /var/log/syslog See: https://forum.manjaro.org/t/solved-qca6174-freez-after-suspend/66232/11 5. Physically replaced Killer 1525 with Intel 8260 --> problem is gone, standby works perfectly Of course i want to be able to use the 1525, so please help me solve the issue. Happy to perform additional debugging if required. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sander 1527 F pulseaudio /dev/snd/controlC0: sander 1527 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.55.1 dev wlp3s0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.55.0/24 dev wlp3s0 proto kernel scope link src 192.168.55.58 metric 600 MachineType: Alienware Alienware 17 R2 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.16.0-0ubuntu2 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=9f06fd28-fdb2-4ada-986f-1e7eb1b87882 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 Tags: disco Uname: Linux 5.0.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/31/2017 dmi.bios.vendor: Alienware dmi.bios.version: A08 dmi.board.name: Alienware 17 R2 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A08 dmi.modalias: dmi:bvnAlienware:bvrA08:bd03/31/2017:svnAlienware:pnAlienware17R2:pvrA08:rvnAlienware:rnAlienware17R2:rvrA00:cvnAlienware:ct8:cvrA08: dmi.product.family: Alienware 17 R2 dmi.product.name: Alienware 17 R2 dmi.product.sku: Alienware 15 dmi.product.version: A08 dmi.sys.vendor: Alienware nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.16.0 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1827879/+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 1827879] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1827879/+attachment/5264345/+files/UdevDb.txt -- 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/1827879 Title: Killer Wireless 1525 firmware crashes on suspend Status in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: Problem: Ubuntu running on Alienware 17 R2 system hangs on suspend. The Keyboard LED's stay on and FAN keeps running. Strangely this does not happen in Fedora 29 (Kernel 4.18 & same board firmware) System: Ubuntu 19.04 Kernel 5.0.0-13-generic Wireless chipset Killer Wireless 1525 (Atheros QCA6174, hw2.1) Wireless info: description: Wireless interface product: QCA6174 802.11ac Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:03:00.0 logical name: wlp3s0 version: 20 serial: 40:b8:9a:ca:2b:99 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=ath10k_pci driverversion=5.0.0-13-generic firmware=SW_RM.1.1.1-00157-QCARMSWPZ-1 ip=192.168.55.161 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:32 memory:f680-f69f My attempts: 1. Tried other kernels: 5.0.12, 4.20.17, 4.19.7, 4.18.16, 4.18.0, 4.16.0, 4.14.114 2. Tried several distro's based on ubuntu -> all have the same issue 3. Checked firmware from Fedora 29 (md5sum was equal) and updated firmware (not available, using latest) 4. Created systemd scripts for disabling & enabling the driver, this causes the same crashes in /var/log/syslog See: https://forum.manjaro.org/t/solved-qca6174-freez-after-suspend/66232/11 5. Physically replaced Killer 1525 with Intel 8260 --> problem is gone, standby works perfectly Of course i want to be able to use the 1525, so please help me solve the issue. Happy to perform additional debugging if required. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sander 1527 F pulseaudio /dev/snd/controlC0: sander 1527 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.55.1 dev wlp3s0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.55.0/24 dev wlp3s0 proto kernel scope link src 192.168.55.58 metric 600 MachineType: Alienware Alienware 17 R2 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.16.0-0ubuntu2 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=9f06fd28-fdb2-4ada-986f-1e7eb1b87882 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 Tags: disco Uname: Linux 5.0.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/31/2017 dmi.bios.vendor: Alienware dmi.bios.version: A08 dmi.board.name: Alienware 17 R2 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A08 dmi.modalias: dmi:bvnAlienware:bvrA08:bd03/31/2017:svnAlienware:pnAlienware17R2:pvrA08:rvnAlienware:rnAlienware17R2:rvrA00:cvnAlienware:ct8:cvrA08: dmi.product.family: Alienware 17 R2 dmi.product.name: Alienware 17 R2 dmi.product.sku: Alienware 15 dmi.product.version: A08 dmi.sys.vendor: Alienware nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.16.0 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1827879/+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 1827879] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1827879/+attachment/5264343/+files/PulseList.txt -- 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/1827879 Title: Killer Wireless 1525 firmware crashes on suspend Status in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: Problem: Ubuntu running on Alienware 17 R2 system hangs on suspend. The Keyboard LED's stay on and FAN keeps running. Strangely this does not happen in Fedora 29 (Kernel 4.18 & same board firmware) System: Ubuntu 19.04 Kernel 5.0.0-13-generic Wireless chipset Killer Wireless 1525 (Atheros QCA6174, hw2.1) Wireless info: description: Wireless interface product: QCA6174 802.11ac Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:03:00.0 logical name: wlp3s0 version: 20 serial: 40:b8:9a:ca:2b:99 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=ath10k_pci driverversion=5.0.0-13-generic firmware=SW_RM.1.1.1-00157-QCARMSWPZ-1 ip=192.168.55.161 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:32 memory:f680-f69f My attempts: 1. Tried other kernels: 5.0.12, 4.20.17, 4.19.7, 4.18.16, 4.18.0, 4.16.0, 4.14.114 2. Tried several distro's based on ubuntu -> all have the same issue 3. Checked firmware from Fedora 29 (md5sum was equal) and updated firmware (not available, using latest) 4. Created systemd scripts for disabling & enabling the driver, this causes the same crashes in /var/log/syslog See: https://forum.manjaro.org/t/solved-qca6174-freez-after-suspend/66232/11 5. Physically replaced Killer 1525 with Intel 8260 --> problem is gone, standby works perfectly Of course i want to be able to use the 1525, so please help me solve the issue. Happy to perform additional debugging if required. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sander 1527 F pulseaudio /dev/snd/controlC0: sander 1527 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.55.1 dev wlp3s0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.55.0/24 dev wlp3s0 proto kernel scope link src 192.168.55.58 metric 600 MachineType: Alienware Alienware 17 R2 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.16.0-0ubuntu2 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=9f06fd28-fdb2-4ada-986f-1e7eb1b87882 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 Tags: disco Uname: Linux 5.0.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/31/2017 dmi.bios.vendor: Alienware dmi.bios.version: A08 dmi.board.name: Alienware 17 R2 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A08 dmi.modalias: dmi:bvnAlienware:bvrA08:bd03/31/2017:svnAlienware:pnAlienware17R2:pvrA08:rvnAlienware:rnAlienware17R2:rvrA00:cvnAlienware:ct8:cvrA08: dmi.product.family: Alienware 17 R2 dmi.product.name: Alienware 17 R2 dmi.product.sku: Alienware 15 dmi.product.version: A08 dmi.sys.vendor: Alienware nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.16.0 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1827879/+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 1827879] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1827879/+attachment/5264344/+files/RfKill.txt -- 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/1827879 Title: Killer Wireless 1525 firmware crashes on suspend Status in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: Problem: Ubuntu running on Alienware 17 R2 system hangs on suspend. The Keyboard LED's stay on and FAN keeps running. Strangely this does not happen in Fedora 29 (Kernel 4.18 & same board firmware) System: Ubuntu 19.04 Kernel 5.0.0-13-generic Wireless chipset Killer Wireless 1525 (Atheros QCA6174, hw2.1) Wireless info: description: Wireless interface product: QCA6174 802.11ac Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:03:00.0 logical name: wlp3s0 version: 20 serial: 40:b8:9a:ca:2b:99 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=ath10k_pci driverversion=5.0.0-13-generic firmware=SW_RM.1.1.1-00157-QCARMSWPZ-1 ip=192.168.55.161 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:32 memory:f680-f69f My attempts: 1. Tried other kernels: 5.0.12, 4.20.17, 4.19.7, 4.18.16, 4.18.0, 4.16.0, 4.14.114 2. Tried several distro's based on ubuntu -> all have the same issue 3. Checked firmware from Fedora 29 (md5sum was equal) and updated firmware (not available, using latest) 4. Created systemd scripts for disabling & enabling the driver, this causes the same crashes in /var/log/syslog See: https://forum.manjaro.org/t/solved-qca6174-freez-after-suspend/66232/11 5. Physically replaced Killer 1525 with Intel 8260 --> problem is gone, standby works perfectly Of course i want to be able to use the 1525, so please help me solve the issue. Happy to perform additional debugging if required. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sander 1527 F pulseaudio /dev/snd/controlC0: sander 1527 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.55.1 dev wlp3s0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.55.0/24 dev wlp3s0 proto kernel scope link src 192.168.55.58 metric 600 MachineType: Alienware Alienware 17 R2 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.16.0-0ubuntu2 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=9f06fd28-fdb2-4ada-986f-1e7eb1b87882 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 Tags: disco Uname: Linux 5.0.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/31/2017 dmi.bios.vendor: Alienware dmi.bios.version: A08 dmi.board.name: Alienware 17 R2 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A08 dmi.modalias: dmi:bvnAlienware:bvrA08:bd03/31/2017:svnAlienware:pnAlienware17R2:pvrA08:rvnAlienware:rnAlienware17R2:rvrA00:cvnAlienware:ct8:cvrA08: dmi.product.family: Alienware 17 R2 dmi.product.name: Alienware 17 R2 dmi.product.sku: Alienware 15 dmi.product.version: A08 dmi.sys.vendor: Alienware nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.16.0 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1827879/+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 1827879] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1827879/+attachment/5264340/+files/ProcEnviron.txt -- 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/1827879 Title: Killer Wireless 1525 firmware crashes on suspend Status in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: Problem: Ubuntu running on Alienware 17 R2 system hangs on suspend. The Keyboard LED's stay on and FAN keeps running. Strangely this does not happen in Fedora 29 (Kernel 4.18 & same board firmware) System: Ubuntu 19.04 Kernel 5.0.0-13-generic Wireless chipset Killer Wireless 1525 (Atheros QCA6174, hw2.1) Wireless info: description: Wireless interface product: QCA6174 802.11ac Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:03:00.0 logical name: wlp3s0 version: 20 serial: 40:b8:9a:ca:2b:99 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=ath10k_pci driverversion=5.0.0-13-generic firmware=SW_RM.1.1.1-00157-QCARMSWPZ-1 ip=192.168.55.161 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:32 memory:f680-f69f My attempts: 1. Tried other kernels: 5.0.12, 4.20.17, 4.19.7, 4.18.16, 4.18.0, 4.16.0, 4.14.114 2. Tried several distro's based on ubuntu -> all have the same issue 3. Checked firmware from Fedora 29 (md5sum was equal) and updated firmware (not available, using latest) 4. Created systemd scripts for disabling & enabling the driver, this causes the same crashes in /var/log/syslog See: https://forum.manjaro.org/t/solved-qca6174-freez-after-suspend/66232/11 5. Physically replaced Killer 1525 with Intel 8260 --> problem is gone, standby works perfectly Of course i want to be able to use the 1525, so please help me solve the issue. Happy to perform additional debugging if required. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sander 1527 F pulseaudio /dev/snd/controlC0: sander 1527 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.55.1 dev wlp3s0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.55.0/24 dev wlp3s0 proto kernel scope link src 192.168.55.58 metric 600 MachineType: Alienware Alienware 17 R2 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.16.0-0ubuntu2 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=9f06fd28-fdb2-4ada-986f-1e7eb1b87882 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 Tags: disco Uname: Linux 5.0.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/31/2017 dmi.bios.vendor: Alienware dmi.bios.version: A08 dmi.board.name: Alienware 17 R2 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A08 dmi.modalias: dmi:bvnAlienware:bvrA08:bd03/31/2017:svnAlienware:pnAlienware17R2:pvrA08:rvnAlienware:rnAlienware17R2:rvrA00:cvnAlienware:ct8:cvrA08: dmi.product.family: Alienware 17 R2 dmi.product.name: Alienware 17 R2 dmi.product.sku: Alienware 15 dmi.product.version: A08 dmi.sys.vendor: Alienware nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.16.0 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1827879/+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 1827879] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1827879/+attachment/5264339/+files/ProcCpuinfoMinimal.txt -- 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/1827879 Title: Killer Wireless 1525 firmware crashes on suspend Status in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: Problem: Ubuntu running on Alienware 17 R2 system hangs on suspend. The Keyboard LED's stay on and FAN keeps running. Strangely this does not happen in Fedora 29 (Kernel 4.18 & same board firmware) System: Ubuntu 19.04 Kernel 5.0.0-13-generic Wireless chipset Killer Wireless 1525 (Atheros QCA6174, hw2.1) Wireless info: description: Wireless interface product: QCA6174 802.11ac Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:03:00.0 logical name: wlp3s0 version: 20 serial: 40:b8:9a:ca:2b:99 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=ath10k_pci driverversion=5.0.0-13-generic firmware=SW_RM.1.1.1-00157-QCARMSWPZ-1 ip=192.168.55.161 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:32 memory:f680-f69f My attempts: 1. Tried other kernels: 5.0.12, 4.20.17, 4.19.7, 4.18.16, 4.18.0, 4.16.0, 4.14.114 2. Tried several distro's based on ubuntu -> all have the same issue 3. Checked firmware from Fedora 29 (md5sum was equal) and updated firmware (not available, using latest) 4. Created systemd scripts for disabling & enabling the driver, this causes the same crashes in /var/log/syslog See: https://forum.manjaro.org/t/solved-qca6174-freez-after-suspend/66232/11 5. Physically replaced Killer 1525 with Intel 8260 --> problem is gone, standby works perfectly Of course i want to be able to use the 1525, so please help me solve the issue. Happy to perform additional debugging if required. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sander 1527 F pulseaudio /dev/snd/controlC0: sander 1527 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.55.1 dev wlp3s0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.55.0/24 dev wlp3s0 proto kernel scope link src 192.168.55.58 metric 600 MachineType: Alienware Alienware 17 R2 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.16.0-0ubuntu2 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=9f06fd28-fdb2-4ada-986f-1e7eb1b87882 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 Tags: disco Uname: Linux 5.0.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/31/2017 dmi.bios.vendor: Alienware dmi.bios.version: A08 dmi.board.name: Alienware 17 R2 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A08 dmi.modalias: dmi:bvnAlienware:bvrA08:bd03/31/2017:svnAlienware:pnAlienware17R2:pvrA08:rvnAlienware:rnAlienware17R2:rvrA00:cvnAlienware:ct8:cvrA08: dmi.product.family: Alienware 17 R2 dmi.product.name: Alienware 17 R2 dmi.product.sku: Alienware 15 dmi.product.version: A08 dmi.sys.vendor: Alienware nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.16.0 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1827879/+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 1827879] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1827879/+attachment/5264342/+files/ProcModules.txt -- 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/1827879 Title: Killer Wireless 1525 firmware crashes on suspend Status in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: Problem: Ubuntu running on Alienware 17 R2 system hangs on suspend. The Keyboard LED's stay on and FAN keeps running. Strangely this does not happen in Fedora 29 (Kernel 4.18 & same board firmware) System: Ubuntu 19.04 Kernel 5.0.0-13-generic Wireless chipset Killer Wireless 1525 (Atheros QCA6174, hw2.1) Wireless info: description: Wireless interface product: QCA6174 802.11ac Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:03:00.0 logical name: wlp3s0 version: 20 serial: 40:b8:9a:ca:2b:99 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=ath10k_pci driverversion=5.0.0-13-generic firmware=SW_RM.1.1.1-00157-QCARMSWPZ-1 ip=192.168.55.161 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:32 memory:f680-f69f My attempts: 1. Tried other kernels: 5.0.12, 4.20.17, 4.19.7, 4.18.16, 4.18.0, 4.16.0, 4.14.114 2. Tried several distro's based on ubuntu -> all have the same issue 3. Checked firmware from Fedora 29 (md5sum was equal) and updated firmware (not available, using latest) 4. Created systemd scripts for disabling & enabling the driver, this causes the same crashes in /var/log/syslog See: https://forum.manjaro.org/t/solved-qca6174-freez-after-suspend/66232/11 5. Physically replaced Killer 1525 with Intel 8260 --> problem is gone, standby works perfectly Of course i want to be able to use the 1525, so please help me solve the issue. Happy to perform additional debugging if required. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sander 1527 F pulseaudio /dev/snd/controlC0: sander 1527 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.55.1 dev wlp3s0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.55.0/24 dev wlp3s0 proto kernel scope link src 192.168.55.58 metric 600 MachineType: Alienware Alienware 17 R2 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.16.0-0ubuntu2 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=9f06fd28-fdb2-4ada-986f-1e7eb1b87882 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 Tags: disco Uname: Linux 5.0.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/31/2017 dmi.bios.vendor: Alienware dmi.bios.version: A08 dmi.board.name: Alienware 17 R2 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A08 dmi.modalias: dmi:bvnAlienware:bvrA08:bd03/31/2017:svnAlienware:pnAlienware17R2:pvrA08:rvnAlienware:rnAlienware17R2:rvrA00:cvnAlienware:ct8:cvrA08: dmi.product.family: Alienware 17 R2 dmi.product.name: Alienware 17 R2 dmi.product.sku: Alienware 15 dmi.product.version: A08 dmi.sys.vendor: Alienware nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.16.0 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1827879/+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 1827879] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1827879/+attachment/5264341/+files/ProcInterrupts.txt -- 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/1827879 Title: Killer Wireless 1525 firmware crashes on suspend Status in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: Problem: Ubuntu running on Alienware 17 R2 system hangs on suspend. The Keyboard LED's stay on and FAN keeps running. Strangely this does not happen in Fedora 29 (Kernel 4.18 & same board firmware) System: Ubuntu 19.04 Kernel 5.0.0-13-generic Wireless chipset Killer Wireless 1525 (Atheros QCA6174, hw2.1) Wireless info: description: Wireless interface product: QCA6174 802.11ac Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:03:00.0 logical name: wlp3s0 version: 20 serial: 40:b8:9a:ca:2b:99 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=ath10k_pci driverversion=5.0.0-13-generic firmware=SW_RM.1.1.1-00157-QCARMSWPZ-1 ip=192.168.55.161 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:32 memory:f680-f69f My attempts: 1. Tried other kernels: 5.0.12, 4.20.17, 4.19.7, 4.18.16, 4.18.0, 4.16.0, 4.14.114 2. Tried several distro's based on ubuntu -> all have the same issue 3. Checked firmware from Fedora 29 (md5sum was equal) and updated firmware (not available, using latest) 4. Created systemd scripts for disabling & enabling the driver, this causes the same crashes in /var/log/syslog See: https://forum.manjaro.org/t/solved-qca6174-freez-after-suspend/66232/11 5. Physically replaced Killer 1525 with Intel 8260 --> problem is gone, standby works perfectly Of course i want to be able to use the 1525, so please help me solve the issue. Happy to perform additional debugging if required. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sander 1527 F pulseaudio /dev/snd/controlC0: sander 1527 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.55.1 dev wlp3s0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.55.0/24 dev wlp3s0 proto kernel scope link src 192.168.55.58 metric 600 MachineType: Alienware Alienware 17 R2 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.16.0-0ubuntu2 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=9f06fd28-fdb2-4ada-986f-1e7eb1b87882 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 Tags: disco Uname: Linux 5.0.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/31/2017 dmi.bios.vendor: Alienware dmi.bios.version: A08 dmi.board.name: Alienware 17 R2 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A08 dmi.modalias: dmi:bvnAlienware:bvrA08:bd03/31/2017:svnAlienware:pnAlienware17R2:pvrA08:rvnAlienware:rnAlienware17R2:rvrA00:cvnAlienware:ct8:cvrA08: dmi.product.family: Alienware 17 R2 dmi.product.name: Alienware 17 R2 dmi.product.sku: Alienware 15 dmi.product.version: A08 dmi.sys.vendor: Alienware nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.16.0 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1827879/+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 1827879] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1827879/+attachment/5264332/+files/Lspci.txt -- 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/1827879 Title: Killer Wireless 1525 firmware crashes on suspend Status in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: Problem: Ubuntu running on Alienware 17 R2 system hangs on suspend. The Keyboard LED's stay on and FAN keeps running. Strangely this does not happen in Fedora 29 (Kernel 4.18 & same board firmware) System: Ubuntu 19.04 Kernel 5.0.0-13-generic Wireless chipset Killer Wireless 1525 (Atheros QCA6174, hw2.1) Wireless info: description: Wireless interface product: QCA6174 802.11ac Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:03:00.0 logical name: wlp3s0 version: 20 serial: 40:b8:9a:ca:2b:99 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=ath10k_pci driverversion=5.0.0-13-generic firmware=SW_RM.1.1.1-00157-QCARMSWPZ-1 ip=192.168.55.161 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:32 memory:f680-f69f My attempts: 1. Tried other kernels: 5.0.12, 4.20.17, 4.19.7, 4.18.16, 4.18.0, 4.16.0, 4.14.114 2. Tried several distro's based on ubuntu -> all have the same issue 3. Checked firmware from Fedora 29 (md5sum was equal) and updated firmware (not available, using latest) 4. Created systemd scripts for disabling & enabling the driver, this causes the same crashes in /var/log/syslog See: https://forum.manjaro.org/t/solved-qca6174-freez-after-suspend/66232/11 5. Physically replaced Killer 1525 with Intel 8260 --> problem is gone, standby works perfectly Of course i want to be able to use the 1525, so please help me solve the issue. Happy to perform additional debugging if required. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sander 1527 F pulseaudio /dev/snd/controlC0: sander 1527 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.55.1 dev wlp3s0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.55.0/24 dev wlp3s0 proto kernel scope link src 192.168.55.58 metric 600 MachineType: Alienware Alienware 17 R2 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.16.0-0ubuntu2 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=9f06fd28-fdb2-4ada-986f-1e7eb1b87882 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 Tags: disco Uname: Linux 5.0.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/31/2017 dmi.bios.vendor: Alienware dmi.bios.version: A08 dmi.board.name: Alienware 17 R2 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A08 dmi.modalias: dmi:bvnAlienware:bvrA08:bd03/31/2017:svnAlienware:pnAlienware17R2:pvrA08:rvnAlienware:rnAlienware17R2:rvrA00:cvnAlienware:ct8:cvrA08: dmi.product.family: Alienware 17 R2 dmi.product.name: Alienware 17 R2 dmi.product.sku: Alienware 15 dmi.product.version: A08 dmi.sys.vendor: Alienware nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.16.0 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1827879/+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 1827879] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1827879/+attachment/5264333/+files/Lsusb.txt -- 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/1827879 Title: Killer Wireless 1525 firmware crashes on suspend Status in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: Problem: Ubuntu running on Alienware 17 R2 system hangs on suspend. The Keyboard LED's stay on and FAN keeps running. Strangely this does not happen in Fedora 29 (Kernel 4.18 & same board firmware) System: Ubuntu 19.04 Kernel 5.0.0-13-generic Wireless chipset Killer Wireless 1525 (Atheros QCA6174, hw2.1) Wireless info: description: Wireless interface product: QCA6174 802.11ac Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:03:00.0 logical name: wlp3s0 version: 20 serial: 40:b8:9a:ca:2b:99 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=ath10k_pci driverversion=5.0.0-13-generic firmware=SW_RM.1.1.1-00157-QCARMSWPZ-1 ip=192.168.55.161 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:32 memory:f680-f69f My attempts: 1. Tried other kernels: 5.0.12, 4.20.17, 4.19.7, 4.18.16, 4.18.0, 4.16.0, 4.14.114 2. Tried several distro's based on ubuntu -> all have the same issue 3. Checked firmware from Fedora 29 (md5sum was equal) and updated firmware (not available, using latest) 4. Created systemd scripts for disabling & enabling the driver, this causes the same crashes in /var/log/syslog See: https://forum.manjaro.org/t/solved-qca6174-freez-after-suspend/66232/11 5. Physically replaced Killer 1525 with Intel 8260 --> problem is gone, standby works perfectly Of course i want to be able to use the 1525, so please help me solve the issue. Happy to perform additional debugging if required. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sander 1527 F pulseaudio /dev/snd/controlC0: sander 1527 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.55.1 dev wlp3s0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.55.0/24 dev wlp3s0 proto kernel scope link src 192.168.55.58 metric 600 MachineType: Alienware Alienware 17 R2 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.16.0-0ubuntu2 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=9f06fd28-fdb2-4ada-986f-1e7eb1b87882 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 Tags: disco Uname: Linux 5.0.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/31/2017 dmi.bios.vendor: Alienware dmi.bios.version: A08 dmi.board.name: Alienware 17 R2 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A08 dmi.modalias: dmi:bvnAlienware:bvrA08:bd03/31/2017:svnAlienware:pnAlienware17R2:pvrA08:rvnAlienware:rnAlienware17R2:rvrA00:cvnAlienware:ct8:cvrA08: dmi.product.family: Alienware 17 R2 dmi.product.name: Alienware 17 R2 dmi.product.sku: Alienware 15 dmi.product.version: A08 dmi.sys.vendor: Alienware nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.16.0 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1827879/+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 1827879] PciNetwork.txt
apport information ** Attachment added: "PciNetwork.txt" https://bugs.launchpad.net/bugs/1827879/+attachment/5264338/+files/PciNetwork.txt -- 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/1827879 Title: Killer Wireless 1525 firmware crashes on suspend Status in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: Problem: Ubuntu running on Alienware 17 R2 system hangs on suspend. The Keyboard LED's stay on and FAN keeps running. Strangely this does not happen in Fedora 29 (Kernel 4.18 & same board firmware) System: Ubuntu 19.04 Kernel 5.0.0-13-generic Wireless chipset Killer Wireless 1525 (Atheros QCA6174, hw2.1) Wireless info: description: Wireless interface product: QCA6174 802.11ac Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:03:00.0 logical name: wlp3s0 version: 20 serial: 40:b8:9a:ca:2b:99 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=ath10k_pci driverversion=5.0.0-13-generic firmware=SW_RM.1.1.1-00157-QCARMSWPZ-1 ip=192.168.55.161 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:32 memory:f680-f69f My attempts: 1. Tried other kernels: 5.0.12, 4.20.17, 4.19.7, 4.18.16, 4.18.0, 4.16.0, 4.14.114 2. Tried several distro's based on ubuntu -> all have the same issue 3. Checked firmware from Fedora 29 (md5sum was equal) and updated firmware (not available, using latest) 4. Created systemd scripts for disabling & enabling the driver, this causes the same crashes in /var/log/syslog See: https://forum.manjaro.org/t/solved-qca6174-freez-after-suspend/66232/11 5. Physically replaced Killer 1525 with Intel 8260 --> problem is gone, standby works perfectly Of course i want to be able to use the 1525, so please help me solve the issue. Happy to perform additional debugging if required. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sander 1527 F pulseaudio /dev/snd/controlC0: sander 1527 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.55.1 dev wlp3s0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.55.0/24 dev wlp3s0 proto kernel scope link src 192.168.55.58 metric 600 MachineType: Alienware Alienware 17 R2 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.16.0-0ubuntu2 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=9f06fd28-fdb2-4ada-986f-1e7eb1b87882 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 Tags: disco Uname: Linux 5.0.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/31/2017 dmi.bios.vendor: Alienware dmi.bios.version: A08 dmi.board.name: Alienware 17 R2 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A08 dmi.modalias: dmi:bvnAlienware:bvrA08:bd03/31/2017:svnAlienware:pnAlienware17R2:pvrA08:rvnAlienware:rnAlienware17R2:rvrA00:cvnAlienware:ct8:cvrA08: dmi.product.family: Alienware 17 R2 dmi.product.name: Alienware 17 R2 dmi.product.sku: Alienware 15 dmi.product.version: A08 dmi.sys.vendor: Alienware nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.16.0 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1827879/+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 1827879] IpAddr.txt
apport information ** Attachment added: "IpAddr.txt" https://bugs.launchpad.net/bugs/1827879/+attachment/5264330/+files/IpAddr.txt -- 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/1827879 Title: Killer Wireless 1525 firmware crashes on suspend Status in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: Problem: Ubuntu running on Alienware 17 R2 system hangs on suspend. The Keyboard LED's stay on and FAN keeps running. Strangely this does not happen in Fedora 29 (Kernel 4.18 & same board firmware) System: Ubuntu 19.04 Kernel 5.0.0-13-generic Wireless chipset Killer Wireless 1525 (Atheros QCA6174, hw2.1) Wireless info: description: Wireless interface product: QCA6174 802.11ac Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:03:00.0 logical name: wlp3s0 version: 20 serial: 40:b8:9a:ca:2b:99 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=ath10k_pci driverversion=5.0.0-13-generic firmware=SW_RM.1.1.1-00157-QCARMSWPZ-1 ip=192.168.55.161 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:32 memory:f680-f69f My attempts: 1. Tried other kernels: 5.0.12, 4.20.17, 4.19.7, 4.18.16, 4.18.0, 4.16.0, 4.14.114 2. Tried several distro's based on ubuntu -> all have the same issue 3. Checked firmware from Fedora 29 (md5sum was equal) and updated firmware (not available, using latest) 4. Created systemd scripts for disabling & enabling the driver, this causes the same crashes in /var/log/syslog See: https://forum.manjaro.org/t/solved-qca6174-freez-after-suspend/66232/11 5. Physically replaced Killer 1525 with Intel 8260 --> problem is gone, standby works perfectly Of course i want to be able to use the 1525, so please help me solve the issue. Happy to perform additional debugging if required. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sander 1527 F pulseaudio /dev/snd/controlC0: sander 1527 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.55.1 dev wlp3s0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.55.0/24 dev wlp3s0 proto kernel scope link src 192.168.55.58 metric 600 MachineType: Alienware Alienware 17 R2 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.16.0-0ubuntu2 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=9f06fd28-fdb2-4ada-986f-1e7eb1b87882 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 Tags: disco Uname: Linux 5.0.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/31/2017 dmi.bios.vendor: Alienware dmi.bios.version: A08 dmi.board.name: Alienware 17 R2 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A08 dmi.modalias: dmi:bvnAlienware:bvrA08:bd03/31/2017:svnAlienware:pnAlienware17R2:pvrA08:rvnAlienware:rnAlienware17R2:rvrA00:cvnAlienware:ct8:cvrA08: dmi.product.family: Alienware 17 R2 dmi.product.name: Alienware 17 R2 dmi.product.sku: Alienware 15 dmi.product.version: A08 dmi.sys.vendor: Alienware nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.16.0 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1827879/+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 1827879] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1827879/+attachment/5264331/+files/IwConfig.txt -- 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/1827879 Title: Killer Wireless 1525 firmware crashes on suspend Status in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: Problem: Ubuntu running on Alienware 17 R2 system hangs on suspend. The Keyboard LED's stay on and FAN keeps running. Strangely this does not happen in Fedora 29 (Kernel 4.18 & same board firmware) System: Ubuntu 19.04 Kernel 5.0.0-13-generic Wireless chipset Killer Wireless 1525 (Atheros QCA6174, hw2.1) Wireless info: description: Wireless interface product: QCA6174 802.11ac Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:03:00.0 logical name: wlp3s0 version: 20 serial: 40:b8:9a:ca:2b:99 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=ath10k_pci driverversion=5.0.0-13-generic firmware=SW_RM.1.1.1-00157-QCARMSWPZ-1 ip=192.168.55.161 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:32 memory:f680-f69f My attempts: 1. Tried other kernels: 5.0.12, 4.20.17, 4.19.7, 4.18.16, 4.18.0, 4.16.0, 4.14.114 2. Tried several distro's based on ubuntu -> all have the same issue 3. Checked firmware from Fedora 29 (md5sum was equal) and updated firmware (not available, using latest) 4. Created systemd scripts for disabling & enabling the driver, this causes the same crashes in /var/log/syslog See: https://forum.manjaro.org/t/solved-qca6174-freez-after-suspend/66232/11 5. Physically replaced Killer 1525 with Intel 8260 --> problem is gone, standby works perfectly Of course i want to be able to use the 1525, so please help me solve the issue. Happy to perform additional debugging if required. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sander 1527 F pulseaudio /dev/snd/controlC0: sander 1527 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.55.1 dev wlp3s0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.55.0/24 dev wlp3s0 proto kernel scope link src 192.168.55.58 metric 600 MachineType: Alienware Alienware 17 R2 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.16.0-0ubuntu2 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=9f06fd28-fdb2-4ada-986f-1e7eb1b87882 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 Tags: disco Uname: Linux 5.0.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/31/2017 dmi.bios.vendor: Alienware dmi.bios.version: A08 dmi.board.name: Alienware 17 R2 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A08 dmi.modalias: dmi:bvnAlienware:bvrA08:bd03/31/2017:svnAlienware:pnAlienware17R2:pvrA08:rvnAlienware:rnAlienware17R2:rvrA00:cvnAlienware:ct8:cvrA08: dmi.product.family: Alienware 17 R2 dmi.product.name: Alienware 17 R2 dmi.product.sku: Alienware 15 dmi.product.version: A08 dmi.sys.vendor: Alienware nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.16.0 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1827879/+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 1827879] NetworkManager.conf.txt
apport information ** Attachment added: "NetworkManager.conf.txt" https://bugs.launchpad.net/bugs/1827879/+attachment/5264337/+files/NetworkManager.conf.txt -- 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/1827879 Title: Killer Wireless 1525 firmware crashes on suspend Status in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: Problem: Ubuntu running on Alienware 17 R2 system hangs on suspend. The Keyboard LED's stay on and FAN keeps running. Strangely this does not happen in Fedora 29 (Kernel 4.18 & same board firmware) System: Ubuntu 19.04 Kernel 5.0.0-13-generic Wireless chipset Killer Wireless 1525 (Atheros QCA6174, hw2.1) Wireless info: description: Wireless interface product: QCA6174 802.11ac Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:03:00.0 logical name: wlp3s0 version: 20 serial: 40:b8:9a:ca:2b:99 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=ath10k_pci driverversion=5.0.0-13-generic firmware=SW_RM.1.1.1-00157-QCARMSWPZ-1 ip=192.168.55.161 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:32 memory:f680-f69f My attempts: 1. Tried other kernels: 5.0.12, 4.20.17, 4.19.7, 4.18.16, 4.18.0, 4.16.0, 4.14.114 2. Tried several distro's based on ubuntu -> all have the same issue 3. Checked firmware from Fedora 29 (md5sum was equal) and updated firmware (not available, using latest) 4. Created systemd scripts for disabling & enabling the driver, this causes the same crashes in /var/log/syslog See: https://forum.manjaro.org/t/solved-qca6174-freez-after-suspend/66232/11 5. Physically replaced Killer 1525 with Intel 8260 --> problem is gone, standby works perfectly Of course i want to be able to use the 1525, so please help me solve the issue. Happy to perform additional debugging if required. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sander 1527 F pulseaudio /dev/snd/controlC0: sander 1527 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.55.1 dev wlp3s0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.55.0/24 dev wlp3s0 proto kernel scope link src 192.168.55.58 metric 600 MachineType: Alienware Alienware 17 R2 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.16.0-0ubuntu2 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=9f06fd28-fdb2-4ada-986f-1e7eb1b87882 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 Tags: disco Uname: Linux 5.0.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/31/2017 dmi.bios.vendor: Alienware dmi.bios.version: A08 dmi.board.name: Alienware 17 R2 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A08 dmi.modalias: dmi:bvnAlienware:bvrA08:bd03/31/2017:svnAlienware:pnAlienware17R2:pvrA08:rvnAlienware:rnAlienware17R2:rvrA00:cvnAlienware:ct8:cvrA08: dmi.product.family: Alienware 17 R2 dmi.product.name: Alienware 17 R2 dmi.product.sku: Alienware 15 dmi.product.version: A08 dmi.sys.vendor: Alienware nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.16.0 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1827879/+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 1827879] NetDevice.wlp3s0.txt
apport information ** Attachment added: "NetDevice.wlp3s0.txt" https://bugs.launchpad.net/bugs/1827879/+attachment/5264336/+files/NetDevice.wlp3s0.txt -- 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/1827879 Title: Killer Wireless 1525 firmware crashes on suspend Status in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: Problem: Ubuntu running on Alienware 17 R2 system hangs on suspend. The Keyboard LED's stay on and FAN keeps running. Strangely this does not happen in Fedora 29 (Kernel 4.18 & same board firmware) System: Ubuntu 19.04 Kernel 5.0.0-13-generic Wireless chipset Killer Wireless 1525 (Atheros QCA6174, hw2.1) Wireless info: description: Wireless interface product: QCA6174 802.11ac Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:03:00.0 logical name: wlp3s0 version: 20 serial: 40:b8:9a:ca:2b:99 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=ath10k_pci driverversion=5.0.0-13-generic firmware=SW_RM.1.1.1-00157-QCARMSWPZ-1 ip=192.168.55.161 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:32 memory:f680-f69f My attempts: 1. Tried other kernels: 5.0.12, 4.20.17, 4.19.7, 4.18.16, 4.18.0, 4.16.0, 4.14.114 2. Tried several distro's based on ubuntu -> all have the same issue 3. Checked firmware from Fedora 29 (md5sum was equal) and updated firmware (not available, using latest) 4. Created systemd scripts for disabling & enabling the driver, this causes the same crashes in /var/log/syslog See: https://forum.manjaro.org/t/solved-qca6174-freez-after-suspend/66232/11 5. Physically replaced Killer 1525 with Intel 8260 --> problem is gone, standby works perfectly Of course i want to be able to use the 1525, so please help me solve the issue. Happy to perform additional debugging if required. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sander 1527 F pulseaudio /dev/snd/controlC0: sander 1527 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.55.1 dev wlp3s0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.55.0/24 dev wlp3s0 proto kernel scope link src 192.168.55.58 metric 600 MachineType: Alienware Alienware 17 R2 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.16.0-0ubuntu2 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=9f06fd28-fdb2-4ada-986f-1e7eb1b87882 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 Tags: disco Uname: Linux 5.0.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/31/2017 dmi.bios.vendor: Alienware dmi.bios.version: A08 dmi.board.name: Alienware 17 R2 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A08 dmi.modalias: dmi:bvnAlienware:bvrA08:bd03/31/2017:svnAlienware:pnAlienware17R2:pvrA08:rvnAlienware:rnAlienware17R2:rvrA00:cvnAlienware:ct8:cvrA08: dmi.product.family: Alienware 17 R2 dmi.product.name: Alienware 17 R2 dmi.product.sku: Alienware 15 dmi.product.version: A08 dmi.sys.vendor: Alienware nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.16.0 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1827879/+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 1827879] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1827879/+attachment/5264329/+files/Dependencies.txt -- 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/1827879 Title: Killer Wireless 1525 firmware crashes on suspend Status in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: Problem: Ubuntu running on Alienware 17 R2 system hangs on suspend. The Keyboard LED's stay on and FAN keeps running. Strangely this does not happen in Fedora 29 (Kernel 4.18 & same board firmware) System: Ubuntu 19.04 Kernel 5.0.0-13-generic Wireless chipset Killer Wireless 1525 (Atheros QCA6174, hw2.1) Wireless info: description: Wireless interface product: QCA6174 802.11ac Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:03:00.0 logical name: wlp3s0 version: 20 serial: 40:b8:9a:ca:2b:99 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=ath10k_pci driverversion=5.0.0-13-generic firmware=SW_RM.1.1.1-00157-QCARMSWPZ-1 ip=192.168.55.161 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:32 memory:f680-f69f My attempts: 1. Tried other kernels: 5.0.12, 4.20.17, 4.19.7, 4.18.16, 4.18.0, 4.16.0, 4.14.114 2. Tried several distro's based on ubuntu -> all have the same issue 3. Checked firmware from Fedora 29 (md5sum was equal) and updated firmware (not available, using latest) 4. Created systemd scripts for disabling & enabling the driver, this causes the same crashes in /var/log/syslog See: https://forum.manjaro.org/t/solved-qca6174-freez-after-suspend/66232/11 5. Physically replaced Killer 1525 with Intel 8260 --> problem is gone, standby works perfectly Of course i want to be able to use the 1525, so please help me solve the issue. Happy to perform additional debugging if required. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sander 1527 F pulseaudio /dev/snd/controlC0: sander 1527 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.55.1 dev wlp3s0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.55.0/24 dev wlp3s0 proto kernel scope link src 192.168.55.58 metric 600 MachineType: Alienware Alienware 17 R2 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.16.0-0ubuntu2 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=9f06fd28-fdb2-4ada-986f-1e7eb1b87882 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 Tags: disco Uname: Linux 5.0.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/31/2017 dmi.bios.vendor: Alienware dmi.bios.version: A08 dmi.board.name: Alienware 17 R2 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A08 dmi.modalias: dmi:bvnAlienware:bvrA08:bd03/31/2017:svnAlienware:pnAlienware17R2:pvrA08:rvnAlienware:rnAlienware17R2:rvrA00:cvnAlienware:ct8:cvrA08: dmi.product.family: Alienware 17 R2 dmi.product.name: Alienware 17 R2 dmi.product.sku: Alienware 15 dmi.product.version: A08 dmi.sys.vendor: Alienware nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.16.0 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1827879/+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 1827879] Re: Killer Wireless 1525 firmware crashes on suspend
apport information ** Tags added: apport-collected ** Description changed: Problem: Ubuntu running on Alienware 17 R2 system hangs on suspend. The Keyboard LED's stay on and FAN keeps running. Strangely this does not happen in Fedora 29 (Kernel 4.18 & same board firmware) System: Ubuntu 19.04 Kernel 5.0.0-13-generic Wireless chipset Killer Wireless 1525 (Atheros QCA6174, hw2.1) Wireless info: description: Wireless interface product: QCA6174 802.11ac Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:03:00.0 logical name: wlp3s0 version: 20 serial: 40:b8:9a:ca:2b:99 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=ath10k_pci driverversion=5.0.0-13-generic firmware=SW_RM.1.1.1-00157-QCARMSWPZ-1 ip=192.168.55.161 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:32 memory:f680-f69f My attempts: 1. Tried other kernels: 5.0.12, 4.20.17, 4.19.7, 4.18.16, 4.18.0, 4.16.0, 4.14.114 2. Tried several distro's based on ubuntu -> all have the same issue 3. Checked firmware from Fedora 29 (md5sum was equal) and updated firmware (not available, using latest) 4. Created systemd scripts for disabling & enabling the driver, this causes the same crashes in /var/log/syslog See: https://forum.manjaro.org/t/solved-qca6174-freez-after-suspend/66232/11 5. Physically replaced Killer 1525 with Intel 8260 --> problem is gone, standby works perfectly Of course i want to be able to use the 1525, so please help me solve the issue. Happy to perform additional debugging if required. + --- + ProblemType: Bug + ApportVersion: 2.20.10-0ubuntu27 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: sander 1527 F pulseaudio + /dev/snd/controlC0: sander 1527 F pulseaudio + CurrentDesktop: KDE + DistroRelease: Ubuntu 19.04 + IfupdownConfig: + # interfaces(5) file used by ifup(8) and ifdown(8) + auto lo + iface lo inet loopback + IpRoute: + default via 192.168.55.1 dev wlp3s0 proto dhcp metric 600 + 169.254.0.0/16 dev wlp3s0 scope link metric 1000 + 192.168.55.0/24 dev wlp3s0 proto kernel scope link src 192.168.55.58 metric 600 + MachineType: Alienware Alienware 17 R2 + NetworkManager.state: + [main] + NetworkingEnabled=true + WirelessEnabled=true + WWANEnabled=true + NonfreeKernelModules: nvidia_modeset nvidia + Package: network-manager 1.16.0-0ubuntu2 + PackageArchitecture: amd64 + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=9f06fd28-fdb2-4ada-986f-1e7eb1b87882 ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 + RelatedPackageVersions: + linux-restricted-modules-5.0.0-15-generic N/A + linux-backports-modules-5.0.0-15-generic N/A + linux-firmware1.178.1 + Tags: disco + Uname: Linux 5.0.0-15-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 03/31/2017 + dmi.bios.vendor: Alienware + dmi.bios.version: A08 + dmi.board.name: Alienware 17 R2 + dmi.board.vendor: Alienware + dmi.board.version: A00 + dmi.chassis.type: 8 + dmi.chassis.vendor: Alienware + dmi.chassis.version: A08 + dmi.modalias: dmi:bvnAlienware:bvrA08:bd03/31/2017:svnAlienware:pnAlienware17R2:pvrA08:rvnAlienware:rnAlienware17R2:rvrA00:cvnAlienware:ct8:cvrA08: + dmi.product.family: Alienware 17 R2 + dmi.product.name: Alienware 17 R2 + dmi.product.sku: Alienware 15 + dmi.product.version: A08 + dmi.sys.vendor: Alienware + nmcli-nm: + RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN + running 1.16.0 connected started full enabled enabled enabled enabled enabled ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1827879/+attachment/5264326/+files/AlsaInfo.txt -- 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/1827879 Title: Killer Wireless 1525 firmware crashes on suspend Status in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: Problem: Ubuntu running on Alienware 17 R2 system hangs on suspend. The Keyboard LED's stay on and FAN keeps running. Strangely this does not happen in Fedora 29 (Kernel 4.18 & same board firmware) System: Ubuntu 19.04 Kernel 5.0.0-13-generic Wireless chipset Killer Wireless 1525 (Atheros QCA6174, hw2.1) Wireless info: description: Wireles
[Touch-packages] [Bug 1827879] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1827879/+attachment/5264328/+files/CurrentDmesg.txt -- 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/1827879 Title: Killer Wireless 1525 firmware crashes on suspend Status in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: Problem: Ubuntu running on Alienware 17 R2 system hangs on suspend. The Keyboard LED's stay on and FAN keeps running. Strangely this does not happen in Fedora 29 (Kernel 4.18 & same board firmware) System: Ubuntu 19.04 Kernel 5.0.0-13-generic Wireless chipset Killer Wireless 1525 (Atheros QCA6174, hw2.1) Wireless info: description: Wireless interface product: QCA6174 802.11ac Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:03:00.0 logical name: wlp3s0 version: 20 serial: 40:b8:9a:ca:2b:99 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=ath10k_pci driverversion=5.0.0-13-generic firmware=SW_RM.1.1.1-00157-QCARMSWPZ-1 ip=192.168.55.161 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:32 memory:f680-f69f My attempts: 1. Tried other kernels: 5.0.12, 4.20.17, 4.19.7, 4.18.16, 4.18.0, 4.16.0, 4.14.114 2. Tried several distro's based on ubuntu -> all have the same issue 3. Checked firmware from Fedora 29 (md5sum was equal) and updated firmware (not available, using latest) 4. Created systemd scripts for disabling & enabling the driver, this causes the same crashes in /var/log/syslog See: https://forum.manjaro.org/t/solved-qca6174-freez-after-suspend/66232/11 5. Physically replaced Killer 1525 with Intel 8260 --> problem is gone, standby works perfectly Of course i want to be able to use the 1525, so please help me solve the issue. Happy to perform additional debugging if required. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sander 1527 F pulseaudio /dev/snd/controlC0: sander 1527 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.55.1 dev wlp3s0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.55.0/24 dev wlp3s0 proto kernel scope link src 192.168.55.58 metric 600 MachineType: Alienware Alienware 17 R2 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.16.0-0ubuntu2 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=9f06fd28-fdb2-4ada-986f-1e7eb1b87882 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 Tags: disco Uname: Linux 5.0.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/31/2017 dmi.bios.vendor: Alienware dmi.bios.version: A08 dmi.board.name: Alienware 17 R2 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A08 dmi.modalias: dmi:bvnAlienware:bvrA08:bd03/31/2017:svnAlienware:pnAlienware17R2:pvrA08:rvnAlienware:rnAlienware17R2:rvrA00:cvnAlienware:ct8:cvrA08: dmi.product.family: Alienware 17 R2 dmi.product.name: Alienware 17 R2 dmi.product.sku: Alienware 15 dmi.product.version: A08 dmi.sys.vendor: Alienware nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.16.0 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1827879/+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 1827879] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1827879/+attachment/5264327/+files/CRDA.txt -- 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/1827879 Title: Killer Wireless 1525 firmware crashes on suspend Status in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: Problem: Ubuntu running on Alienware 17 R2 system hangs on suspend. The Keyboard LED's stay on and FAN keeps running. Strangely this does not happen in Fedora 29 (Kernel 4.18 & same board firmware) System: Ubuntu 19.04 Kernel 5.0.0-13-generic Wireless chipset Killer Wireless 1525 (Atheros QCA6174, hw2.1) Wireless info: description: Wireless interface product: QCA6174 802.11ac Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:03:00.0 logical name: wlp3s0 version: 20 serial: 40:b8:9a:ca:2b:99 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=ath10k_pci driverversion=5.0.0-13-generic firmware=SW_RM.1.1.1-00157-QCARMSWPZ-1 ip=192.168.55.161 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:32 memory:f680-f69f My attempts: 1. Tried other kernels: 5.0.12, 4.20.17, 4.19.7, 4.18.16, 4.18.0, 4.16.0, 4.14.114 2. Tried several distro's based on ubuntu -> all have the same issue 3. Checked firmware from Fedora 29 (md5sum was equal) and updated firmware (not available, using latest) 4. Created systemd scripts for disabling & enabling the driver, this causes the same crashes in /var/log/syslog See: https://forum.manjaro.org/t/solved-qca6174-freez-after-suspend/66232/11 5. Physically replaced Killer 1525 with Intel 8260 --> problem is gone, standby works perfectly Of course i want to be able to use the 1525, so please help me solve the issue. Happy to perform additional debugging if required. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sander 1527 F pulseaudio /dev/snd/controlC0: sander 1527 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.55.1 dev wlp3s0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.55.0/24 dev wlp3s0 proto kernel scope link src 192.168.55.58 metric 600 MachineType: Alienware Alienware 17 R2 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.16.0-0ubuntu2 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=9f06fd28-fdb2-4ada-986f-1e7eb1b87882 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 Tags: disco Uname: Linux 5.0.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/31/2017 dmi.bios.vendor: Alienware dmi.bios.version: A08 dmi.board.name: Alienware 17 R2 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A08 dmi.modalias: dmi:bvnAlienware:bvrA08:bd03/31/2017:svnAlienware:pnAlienware17R2:pvrA08:rvnAlienware:rnAlienware17R2:rvrA00:cvnAlienware:ct8:cvrA08: dmi.product.family: Alienware 17 R2 dmi.product.name: Alienware 17 R2 dmi.product.sku: Alienware 15 dmi.product.version: A08 dmi.sys.vendor: Alienware nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.16.0 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1827879/+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 1827879] Re: Killer Wireless 1525 firmware crashes on suspend
Some additional information: It looks like NetworkManager is part of the problem / solution. --> Linked to networkmanager <-- If wifi is disabled (nmcli radio wifi off) the suspend works as expected. Unfortunately, when scripting this into a systemctl script hooking to suspend.target, networkmanager is killed before the script is executed, thus networkmanager cannot respond anymore to the command. Example of this systemctl script included here: [Unit] Description=Network suspend service Before=sleep.target StopWhenUnneeded=yes [Service] User=root Type=oneshot RemainAfterExit=yes ExecStart=/usr/bin/sudo -u $USER /bin/bash -lc 'nmcli radio wifi off' ExecStart=/usr/bin/sleep 5 [Install] WantedBy=sleep.target ** Also affects: network-manager (Ubuntu) Importance: Undecided Status: New -- 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/1827879 Title: Killer Wireless 1525 firmware crashes on suspend Status in Ubuntu: New Status in network-manager package in Ubuntu: New Bug description: Problem: Ubuntu running on Alienware 17 R2 system hangs on suspend. The Keyboard LED's stay on and FAN keeps running. Strangely this does not happen in Fedora 29 (Kernel 4.18 & same board firmware) System: Ubuntu 19.04 Kernel 5.0.0-13-generic Wireless chipset Killer Wireless 1525 (Atheros QCA6174, hw2.1) Wireless info: description: Wireless interface product: QCA6174 802.11ac Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:03:00.0 logical name: wlp3s0 version: 20 serial: 40:b8:9a:ca:2b:99 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=ath10k_pci driverversion=5.0.0-13-generic firmware=SW_RM.1.1.1-00157-QCARMSWPZ-1 ip=192.168.55.161 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:32 memory:f680-f69f My attempts: 1. Tried other kernels: 5.0.12, 4.20.17, 4.19.7, 4.18.16, 4.18.0, 4.16.0, 4.14.114 2. Tried several distro's based on ubuntu -> all have the same issue 3. Checked firmware from Fedora 29 (md5sum was equal) and updated firmware (not available, using latest) 4. Created systemd scripts for disabling & enabling the driver, this causes the same crashes in /var/log/syslog See: https://forum.manjaro.org/t/solved-qca6174-freez-after-suspend/66232/11 5. Physically replaced Killer 1525 with Intel 8260 --> problem is gone, standby works perfectly Of course i want to be able to use the 1525, so please help me solve the issue. Happy to perform additional debugging if required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1827879/+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 1820114] Re: iptables v1.6.1: can't initialize iptables table `filter': Memory allocation problem
** Changed in: iptables (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1820114 Title: iptables v1.6.1: can't initialize iptables table `filter': Memory allocation problem Status in iptables package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I hit this error on disco: ``` $ free -h totalusedfree shared buff/cache available Mem: 478Mi98Mi 311Mi 0.0Ki68Mi 366Mi Swap:0B 0B 0B $ sudo iptables -S iptables v1.6.1: can't initialize iptables table `filter': Memory allocation problem Perhaps iptables or your kernel needs to be upgraded. ``` ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: iptables 1.6.1-2ubuntu3 ProcVersionSignature: User Name 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 Date: Thu Mar 14 19:16:15 2019 SourcePackage: iptables UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 DistroRelease: Ubuntu 19.04 Package: linux PackageArchitecture: amd64 ProcVersionSignature: User Name 5.0.0-7.8-generic 5.0.0 Tags: disco uec-images Uname: Linux 5.0.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1820114/+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 1820114] Re: iptables v1.6.1: can't initialize iptables table `filter': Memory allocation problem
I get sometimes the memory allocation error and sometimes a "no chain by that name": root@ubu1904:/etc/ctdb# iptables -L iptables v1.6.1: can't initialize iptables table `filter': Memory allocation problem Perhaps iptables or your kernel needs to be upgraded. root@ubu1904:/etc/ctdb# iptables -L iptables: No chain/target/match by that name. root@ubu1904:/etc/ctdb# iptables -L iptables: No chain/target/match by that name. root@ubu1904:/etc/ctdb# iptables -L iptables v1.6.1: can't initialize iptables table `filter': Memory allocation problem Perhaps iptables or your kernel needs to be upgraded. root@ubu1904:/etc/ctdb# iptables -L INPUT iptables v1.6.1: can't initialize iptables table `filter': Memory allocation problem Perhaps iptables or your kernel needs to be upgraded. root@ubu1904:/etc/ctdb# iptables -L INPUT iptables v1.6.1: can't initialize iptables table `filter': Memory allocation problem Perhaps iptables or your kernel needs to be upgraded. root@ubu1904:/etc/ctdb# iptables -L INPUT iptables: No chain/target/match by that name. root@ubu1904:/etc/ctdb# iptables -L INPUT iptables: No chain/target/match by that name. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1820114 Title: iptables v1.6.1: can't initialize iptables table `filter': Memory allocation problem Status in iptables package in Ubuntu: Incomplete Status in linux package in Ubuntu: Confirmed Bug description: I hit this error on disco: ``` $ free -h totalusedfree shared buff/cache available Mem: 478Mi98Mi 311Mi 0.0Ki68Mi 366Mi Swap:0B 0B 0B $ sudo iptables -S iptables v1.6.1: can't initialize iptables table `filter': Memory allocation problem Perhaps iptables or your kernel needs to be upgraded. ``` ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: iptables 1.6.1-2ubuntu3 ProcVersionSignature: User Name 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 Date: Thu Mar 14 19:16:15 2019 SourcePackage: iptables UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 DistroRelease: Ubuntu 19.04 Package: linux PackageArchitecture: amd64 ProcVersionSignature: User Name 5.0.0-7.8-generic 5.0.0 Tags: disco uec-images Uname: Linux 5.0.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1820114/+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 1508146] Re: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable
Also having this issue on a fresh install of 18.04.01, `sudo kbd_mode -s` fixed it for now, haven't rebooted yet. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1508146 Title: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I'm used to using alt+left/right arrow to navigate back and forward in web browsers and elsewhere (nautilus)... But on this fresh install of Ubuntu Gnome 15.10 beta, it seems to try and switch me between tty consoles (the ctrl+alt+f1 ones). But it's not listed as one of the shortcuts in the "keyboard" menu, so I don't know how to disable it... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1508146/+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 1630946] Re: ubuntu-server depends on open-iscsi and runs iscsid
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-17840 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1630946 Title: ubuntu-server depends on open-iscsi and runs iscsid Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: ubuntu-server has a hard dependency on open-iscsi, which means there is a daemon running (iscsid), and the package cannot be removed. All unnecessary daemons are a cause of concern when auditing a system. Propose moving this to "Recommends" instead, which currently has: Recommends: lxd, snapd ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-server 1.361 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Thu Oct 6 10:43:04 2016 Ec2AMI: ami-c06b1eb3 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-west-1a Ec2InstanceType: t2.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable ProcEnviron: TERM=xterm-256color SHELL=/bin/bash PATH=(custom, user) LANG=en_US.UTF-8 XDG_RUNTIME_DIR= SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1630946/+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 1586528] Re: Avahi-daemon withdraws address record
Same problem with raspbian stretch and avahi. I used dhcp binding of my router to fix the address 192.168.2.4 to Mac address b8:27:eb:3f:11:5f. Few hours later, after the syslog gives the "Withdrawing address record for 192.168.2.4" the machine gets another ip-adres, 192.168.2.23 from the dhcp router. Checking in the router to see why it don't bind I see the router assigns 192.168.2.23 to Mac address 86:16:f9:3f:11:5f The first Mac address is right, b8:27:eb belongs to raspberry http://standards-oui.ieee.org/oui.txt The second Mac address starting 86:16:f9 is not known by http://standards-oui.ieee.org/oui.txt. Where does the second, incorrect, Mac address came from? -- 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/1586528 Title: Avahi-daemon withdraws address record Status in avahi package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: For some reason, if I leave my Ubuntu VM up for a prolonged period of time the machine will lose connection to the network. ip addr shows that the nic port no longer has an address and an examination of the syslog shows this: May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Withdrawing address record for 10.0.2.15 on enp0s3. May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Leaving mDNS multicast group on interface enp0s3.IPv4 with address 10.0.2.15. May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Interface enp0s3.IPv4 no longer relevant for mDNS. for no known reason. The only reliable way to get the network to come back (that I have found) is a full reboot. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri May 27 15:11:34 2016 InstallationDate: Installed on 2015-10-22 (218 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: avahi UpgradeStatus: Upgraded to xenial on 2016-03-30 (58 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1586528/+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 1737250] Re: systemd-resolved returns only short hostname when PTR record of local IP is requested
Yep, that setting fixes the issue. Please make LLMNR=no the default. BTW: systemd-resolved seems to have many other issues, too. I do not think that it is fit to be included in a stable release. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1737250 Title: systemd-resolved returns only short hostname when PTR record of local IP is requested Status in systemd package in Ubuntu: Incomplete Bug description: Ubuntu 17.10 comes with systemd-resolved as the default local resolver. When querying the PTR record of any local IP address it returns only the hostname (without domain) and does not forward the query to the available nameservers. This results in unwanted results. How do I change that behaviours without disabling and masking systemd- resolved and manually putting the nameservers in /etc/resolv.conf? Example: root@files05:~# host 192.168.48.115 115.48.168.192.in-addr.arpa domain name pointer files05. root@files05:~# host 192.168.48.116 116.48.168.192.in-addr.arpa domain name pointer files06.example.net. root@files05:~# host 192.168.48.120 120.48.168.192.in-addr.arpa domain name pointer files05. root@files05:~# host 192.168.48.120 192.168.48.2 Using domain server: Name: 192.168.48.2 Address: 192.168.48.2#53 Aliases: 120.48.168.192.in-addr.arpa domain name pointer fileserv.example.net. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1737250/+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 1737250] [NEW] systemd-resolved returns only short hostname when PTR record of local IP is requested
Public bug reported: Ubuntu 17.10 comes with systemd-resolved as the default local resolver. When querying the PTR record of any local IP address it returns only the hostname (without domain) and does not forward the query to the available nameservers. This results in unwanted results. How do I change that behaviours without disabling and masking systemd- resolved and manually putting the nameservers in /etc/resolv.conf? Example: root@files05:~# host 192.168.48.115 115.48.168.192.in-addr.arpa domain name pointer files05. root@files05:~# host 192.168.48.116 116.48.168.192.in-addr.arpa domain name pointer files06.example.net. root@files05:~# host 192.168.48.120 120.48.168.192.in-addr.arpa domain name pointer files05. root@files05:~# host 192.168.48.120 192.168.48.2 Using domain server: Name: 192.168.48.2 Address: 192.168.48.2#53 Aliases: 120.48.168.192.in-addr.arpa domain name pointer fileserv.example.net. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1737250 Title: systemd-resolved returns only short hostname when PTR record of local IP is requested Status in systemd package in Ubuntu: New Bug description: Ubuntu 17.10 comes with systemd-resolved as the default local resolver. When querying the PTR record of any local IP address it returns only the hostname (without domain) and does not forward the query to the available nameservers. This results in unwanted results. How do I change that behaviours without disabling and masking systemd- resolved and manually putting the nameservers in /etc/resolv.conf? Example: root@files05:~# host 192.168.48.115 115.48.168.192.in-addr.arpa domain name pointer files05. root@files05:~# host 192.168.48.116 116.48.168.192.in-addr.arpa domain name pointer files06.example.net. root@files05:~# host 192.168.48.120 120.48.168.192.in-addr.arpa domain name pointer files05. root@files05:~# host 192.168.48.120 192.168.48.2 Using domain server: Name: 192.168.48.2 Address: 192.168.48.2#53 Aliases: 120.48.168.192.in-addr.arpa domain name pointer fileserv.example.net. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1737250/+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 1729041] [NEW] package libgtk2.0-common 2.24.30-1ubuntu1.16.04.2 failed to install/upgrade: pakket verkeert in een heel slechte en inconsistente staat; u zou het opnieuw moeten
Public bug reported: at startup i get an system failure ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libgtk2.0-common 2.24.30-1ubuntu1.16.04.2 ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 AptOrdering: mdadm: Install libgtk2.0-common: Configure mdadm: Configure NULL: ConfigurePending Architecture: amd64 Date: Tue Oct 31 17:44:47 2017 ErrorMessage: pakket verkeert in een heel slechte en inconsistente staat; u zou het opnieuw moeten installeren alvorens het te configureren. InstallationDate: Installed on 2017-10-30 (0 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: gtk+2.0 Title: package libgtk2.0-common 2.24.30-1ubuntu1.16.04.2 failed to install/upgrade: pakket verkeert in een heel slechte en inconsistente staat; u zou het opnieuw moeten installeren alvorens het te configureren. UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gtk+2.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1729041 Title: package libgtk2.0-common 2.24.30-1ubuntu1.16.04.2 failed to install/upgrade: pakket verkeert in een heel slechte en inconsistente staat; u zou het opnieuw moeten installeren alvorens het te configureren. Status in gtk+2.0 package in Ubuntu: New Bug description: at startup i get an system failure ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libgtk2.0-common 2.24.30-1ubuntu1.16.04.2 ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 AptOrdering: mdadm: Install libgtk2.0-common: Configure mdadm: Configure NULL: ConfigurePending Architecture: amd64 Date: Tue Oct 31 17:44:47 2017 ErrorMessage: pakket verkeert in een heel slechte en inconsistente staat; u zou het opnieuw moeten installeren alvorens het te configureren. InstallationDate: Installed on 2017-10-30 (0 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: gtk+2.0 Title: package libgtk2.0-common 2.24.30-1ubuntu1.16.04.2 failed to install/upgrade: pakket verkeert in een heel slechte en inconsistente staat; u zou het opnieuw moeten installeren alvorens het te configureren. UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1729041/+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 1721948] Re: gvfs-open/xdg-open shows message about 'gio open' which confuses user
Yes, that solved it for me after activating "proposed" on artful, with xdg-utils (1.1.1-1ubuntu3) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1721948 Title: gvfs-open/xdg-open shows message about 'gio open' which confuses user Status in Apport: Fix Released Status in gvfs: Fix Released Status in apport package in Ubuntu: Invalid Status in gvfs package in Ubuntu: Invalid Status in python3.6 package in Ubuntu: Invalid Status in xdg-utils package in Ubuntu: Fix Committed Status in xdg-utils source package in Artful: Fix Committed Bug description: Steps to reproduce: 1. Install Ubuntu 17.10 2. Try to report bug with Apport by terminal command `apport-bug apport` Expected results: apport-bug reports bug silently Actual results: get output in the terminal $ apport-bug apport This tool has been deprecated, use 'gio open' instead. See 'gio help open' for more info. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: apport 2.20.7-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic i686 ApportVersion: 2.20.7-0ubuntu2 Architecture: i386 CurrentDesktop: MATE Date: Sat Oct 7 13:50:23 2017 InstallationDate: Installed on 2017-08-26 (41 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1721948/+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 1701068] Re: motd.ubuntu.com currently shows media item (HBO's Silicon Valley using Ubuntu)
Well, it's acombined issue: An ubuntu package shows content from motd.ubuntu.com. If we have control over what motd.ubuntu.com contains then we should fix that. If we don't have control over the quality of what motd.ubuntu.com contains then we shouldn't use it. User's won't know where the information comes from, only that Ubuntu shows it. Therefore we should only show information from sources we can rely on to show useful information to users. Either the source should be fixed, or it shouldn't be used... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1701068 Title: motd.ubuntu.com currently shows media item (HBO's Silicon Valley using Ubuntu) Status in base-files package in Ubuntu: Triaged Bug description: In Ubuntu 17.04 or newer, there is a script at /etc/update-motd.d/50 -motd-news that reads https://motd.ubuntu.com/ and displays that text with the rest of the MOTD. Currently, https://motd.ubuntu.com shows a news item about HBO's Silicon Valley which has a reference to Ubuntu. Instead, https://motd.ubuntu.com should show relevant items to those that use Ubuntu Server (relevant security issues, etc), instead of items for desktop users. = Welcome to Ubuntu 17.04 (GNU/Linux 4.10.0-21-generic x86_64) * Documentation: https://help.ubuntu.com * Management: https://landscape.canonical.com * Support:https://ubuntu.com/advantage * How HBO's Silicon Valley built "Not Hotdog" with mobile TensorFlow, Keras & React Native on Ubuntu - https://ubu.one/HBOubu == ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: base-files 9.6ubuntu13 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Wed Jun 28 12:31:24 2017 InstallationDate: Installed on 2017-05-02 (56 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: base-files UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1701068/+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 1691359] [NEW] Sound works after boot, but quickly stops working all together.
Public bug reported: $ aplay -l List of PLAYBACK Hardware Devices card 0: HDMI [HDA Intel HDMI], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: HDMI [HDA Intel HDMI], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: HDMI [HDA Intel HDMI], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: PCH [HDA Intel PCH], device 0: ALC3236 Analog [ALC3236 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: PCH [HDA Intel PCH], device 1: ALC3236 Digital [ALC3236 Digital] Subdevices: 1/1 Subdevice #0: subdevice #0 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59 Uname: Linux 4.4.0-77-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sander 1993 F pulseaudio /dev/snd/controlC0: sander 1993 F pulseaudio CurrentDesktop: GNOME Date: Wed May 17 08:17:38 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-01-31 (105 days ago) InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm1589 F pulseaudio sander 1993 F pulseaudio /dev/snd/controlC0: gdm1589 F pulseaudio sander 1993 F pulseaudio Symptom_Jack: Black Speaker, Internal Symptom_Type: No sound at all Title: [X555LAB, Realtek ALC3236, Black Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555LAB.601 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555LAB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555LAB.601:bd05/05/2016:svnASUSTeKCOMPUTERINC.:pnX555LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X555LAB dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-05-16T21:01:34.210179 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1691359 Title: Sound works after boot, but quickly stops working all together. Status in alsa-driver package in Ubuntu: New Bug description: $ aplay -l List of PLAYBACK Hardware Devices card 0: HDMI [HDA Intel HDMI], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: HDMI [HDA Intel HDMI], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: HDMI [HDA Intel HDMI], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: PCH [HDA Intel PCH], device 0: ALC3236 Analog [ALC3236 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: PCH [HDA Intel PCH], device 1: ALC3236 Digital [ALC3236 Digital] Subdevices: 1/1 Subdevice #0: subdevice #0 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59 Uname: Linux 4.4.0-77-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sander 1993 F pulseaudio /dev/snd/controlC0: sander 1993 F pulseaudio CurrentDesktop: GNOME Date: Wed May 17 08:17:38 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-01-31 (105 days ago) InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm1589 F pulseaudio sander 1993 F pulseaudio /dev/snd/controlC0: gdm1589 F pulseaudio sander 1993 F pulseaudio Symptom_Jack: Black Speaker, Internal Symptom_Type: No sound at all Title: [X555LAB, Realtek ALC3236, Black Speaker, Internal] No sound at all UpgradeStatus: No
[Touch-packages] [Bug 1690099] [NEW] systemd-resolved and Samba 4 INTERNAL_DNS
Public bug reported: Ubuntu 17.04 desktop in a network with Samba 4 AD DC and its internal DNS server and resolver. Messages like the following in the log: May 11 10:47:04 rabi systemd-resolved[1614]: Grace period over, resuming full feature set (UDP+EDNS0+DO+LARGE) for DNS server 192.168.48.2. May 11 10:54:33 rabi systemd-resolved[1614]: Using degraded feature set (UDP) for DNS server 192.168.48.2. It looks like this upstream issue: https://github.com/systemd/systemd/issues/5352 ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: systemd 232-21ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Thu May 11 10:54:09 2017 MachineType: Dell Inc. Precision Tower 7910 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic root=/dev/mapper/system-root ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to zesty on 2017-05-11 (0 days ago) dmi.bios.date: 02/28/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0NK5PH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd02/28/2017:svnDellInc.:pnPrecisionTower7910:pvr:rvnDellInc.:rn0NK5PH:rvrA00:cvnDellInc.:ct7:cvr: dmi.product.name: Precision Tower 7910 dmi.sys.vendor: Dell Inc. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1690099 Title: systemd-resolved and Samba 4 INTERNAL_DNS Status in systemd package in Ubuntu: New Bug description: Ubuntu 17.04 desktop in a network with Samba 4 AD DC and its internal DNS server and resolver. Messages like the following in the log: May 11 10:47:04 rabi systemd-resolved[1614]: Grace period over, resuming full feature set (UDP+EDNS0+DO+LARGE) for DNS server 192.168.48.2. May 11 10:54:33 rabi systemd-resolved[1614]: Using degraded feature set (UDP) for DNS server 192.168.48.2. It looks like this upstream issue: https://github.com/systemd/systemd/issues/5352 ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: systemd 232-21ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Thu May 11 10:54:09 2017 MachineType: Dell Inc. Precision Tower 7910 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic root=/dev/mapper/system-root ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to zesty on 2017-05-11 (0 days ago) dmi.bios.date: 02/28/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0NK5PH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd02/28/2017:svnDellInc.:pnPrecisionTower7910:pvr:rvnDellInc.:rn0NK5PH:rvrA00:cvnDellInc.:ct7:cvr: dmi.product.name: Precision Tower 7910 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1690099/+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 1573272] Re: default gateway route not installed for bond interfaces through reboot
The patch fixes the issue for me as well. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1573272 Title: default gateway route not installed for bond interfaces through reboot Status in ifupdown package in Ubuntu: Confirmed Bug description: Expectation: After reboot, route for default gateway specified on bonded interface is installed according to "gateway x.x.x.x" (where x.x.x.x is a valid IPv4 address) specified in /etc/network/interfaces or files sourced per /etc/network/interfaces Actual Result: After reboot, route is not installed. Interface does work otherwise (I can ping the gateway on that subnet, for instance). 'ifdown -a' followed by 'ifup -a' (run with proper permission... so sudo) brings the gateway back until next reboot. Package: I'm not familiar enough to be certain what is causing this, but I was seeing this in beta2 of 16.04 as well. *username snipped*@*hostname snipped*:~$ lsb_release -rd Description:Ubuntu 16.04 LTS Release:16.04 *username snipped*@*hostname snipped*:~$ apt-cache policy ifenslave ifenslave: Installed: 2.7ubuntu1 Candidate: 2.7ubuntu1 Version table: *** 2.7ubuntu1 100 100 /var/lib/dpkg/status *username snipped*@*hostname snipped*:~$ apt-cache policy ifupdown ifupdown: Installed: 0.8.10ubuntu1 Candidate: 0.8.10ubuntu1 Version table: *** 0.8.10ubuntu1 100 100 /var/lib/dpkg/status /etc/network/interfaces -- # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto enp2s0f1 iface enp2s0f1 inet manual bond-master bond0 auto enp2s0f0 iface enp2s0f0 inet manual bond-master bond0 auto bond0 iface bond0 inet static address 10.96.96.2 netmask 255.255.255.0 network 10.96.96.0 broadcast 10.96.96.255 # dns-* options are implemented by the resolvconf package, if installed dns-search *snip* bond-mode balance-alb bond-slaves none bond-miimon 100 auto bond0.3000 iface bond0.3000 inet static address 172.21.33.29 netmask 255.255.255.0 network 172.21.33.0 broadcast 172.21.33.255 gateway 172.21.33.1 dns-search *snip* vlan-raw-device bond0 dns-nameservers 172.31.10.84 8.8.8.8 4.2.2.2 - interfaces.d is empty: *username snipped*@*hostname snipped*:~$ ls -lisah /etc/network/interfaces.d total 8.0K 10748247 4.0K drwxr-xr-x 2 root root 4.0K Jan 24 14:08 . 10748237 4.0K drwxr-xr-x 7 root root 4.0K Apr 21 17:32 .. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1573272/+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 1627192] Re: owncloud login
Problem was relaxed to using self signet certificate. This prevented login thingy to display. Solved with a lets encrypt certificate. Should browser not also accept self signed certificates? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1627192 Title: owncloud login Status in webbrowser-app package in Ubuntu: New Bug description: I can't login to my owncloud on my raspberry pi. the button to login doesn't apear. (does in firefox) Owncloud 9.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1627192/+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 1589401] Re: cannot view wifi networks after re-enabling wifi
@Hansen ... I did that, did a reboot, did a suspend/resume (arrows appeared), and the logging is 1997 lines long. Can you advice what to do with that logging? -- 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/1589401 Title: cannot view wifi networks after re-enabling wifi Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Incomplete Bug description: after re enabling wifi, up-down arrows just like wired network. cannot see any wifi ssid. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1589401/+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 1589401] Re: cannot view wifi networks after re-enabling wifi
@Joakim: Ah, OK, I now understand. Thanks. However: I have the beam symbol, but it's now grey (like: no signal), and no Wifi networks visible. :-( After a "sudo systemctl restart network-manager.service" the beam signal shortly becomes an empty pizza slice, then the Up-Down-arrow, and greyed beam after a minute or so. Pity And I should have written: FWIW: I've NO Intel Wifi, but Realtek: 02:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8723BE PCIe Wireless Network Adapter Sorry about that. -- 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/1589401 Title: cannot view wifi networks after re-enabling wifi Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Incomplete Bug description: after re enabling wifi, up-down arrows just like wired network. cannot see any wifi ssid. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1589401/+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 1589401] Re: cannot view wifi networks after re-enabling wifi
FWIW2: I only have Wifi. No fixed ethernet. Maybe that is part of the problem? Maybe the indicator assumes the first ethernet is always fixed ethernet, and puts that symbol on it? -- 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/1589401 Title: cannot view wifi networks after re-enabling wifi Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Incomplete Bug description: after re enabling wifi, up-down arrows just like wired network. cannot see any wifi ssid. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1589401/+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 1589401] Re: cannot view wifi networks after re-enabling wifi
I have the same problem with a fresh install of Ubuntu 16.10 / yakkety on my HP Stream 13. The workaround "sudo systemctl restart network-manager.service" works for me: it removes the up-down-arrow, and gives back the beam symbol showing the available wifi networks. I have no file /etc/systemd/system/wifi-resume.service, so I can't use the workaround from http://askubuntu.com/questions/761180/wifi-doesnt- work-after-suspend-after-16-04-upgrade/761220#761220 FWIW: I've an Intel Wifi too: 02:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8723BE PCIe Wireless Network Adapter -- 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/1589401 Title: cannot view wifi networks after re-enabling wifi Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Incomplete Bug description: after re enabling wifi, up-down arrows just like wired network. cannot see any wifi ssid. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1589401/+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 1575078] Re: [XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a while
I'm seeing the same problem on my XPS 9550, running Yakkety under kernel 4.8.0-17. I've had this problem for a lot longer, though. Headset detection doesn't work at all. Upon bootup audio is OK. after plugging in a pair of headphone (with MIC in the wire) all audio is killed, permanently, until after a reboot. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1575078 Title: [XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a while Status in alsa-driver package in Ubuntu: Confirmed Bug description: I'm experiencing a strange behavior with a headphone jack on my laptop. I have an external audio speaker connected to it. When I disconnect the speaker and reconnect it again it stops working. Even more, laptop audio stops working too. And after the reboot, I don't even see any of the audio devices. I've googled a lot and tried different fixes from forums with no luck. After a while, I've accidentally discovered that putting the laptop to the sleep mode and rebooting system after brings audio back to live. Even more, if speakers were attached during this sleep-reboot procedure, they are starting to work as well. However, after the next reboot speakers are not working again. And if I will plug them out and in - problem with completely missing audio returns. P.S. I'm using laptop-mode-tools package on my laptop. Recovery after hibernation made me believe that it's somehow related. But after uninstalling this package nothing really changed. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: kop3224 F...m pulseaudio /dev/snd/controlC0: kop3224 F pulseaudio CurrentDesktop: Unity Date: Tue Apr 26 12:17:03 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-22 (3 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Встроенное аудио - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_Type: Sound works for a while, then breaks Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1575078/+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 1609107] Re: Ota13
can not reproduce anymore -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1609107 Title: Ota13 Status in bluez package in Ubuntu: New Bug description: Without ota13 bluetooth doesn't work anymore in my m10 tablet anymore. Keyboard and mouse donut connct and bluetooth switches itself off all the time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1609107/+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 1627195] [NEW] exchange
Public bug reported: I would like to sync my company contacts that ar on a MS exchange server ** Affects: address-book-app (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to address-book-app in Ubuntu. https://bugs.launchpad.net/bugs/1627195 Title: exchange Status in address-book-app package in Ubuntu: New Bug description: I would like to sync my company contacts that ar on a MS exchange server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/address-book-app/+bug/1627195/+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 1627192] [NEW] owncloud login
Public bug reported: I can't login to my owncloud on my raspberry pi. the button to login doesn't apear. (does in firefox) Owncloud 9.1 ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1627192 Title: owncloud login Status in webbrowser-app package in Ubuntu: New Bug description: I can't login to my owncloud on my raspberry pi. the button to login doesn't apear. (does in firefox) Owncloud 9.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1627192/+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 1609107] [NEW] Ota13
Public bug reported: Without ota13 bluetooth doesn't work anymore in my m10 tablet anymore. Keyboard and mouse donut connct and bluetooth switches itself off all the time. ** Affects: bluez (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1609107 Title: Ota13 Status in bluez package in Ubuntu: New Bug description: Without ota13 bluetooth doesn't work anymore in my m10 tablet anymore. Keyboard and mouse donut connct and bluetooth switches itself off all the time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1609107/+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 1605867] [NEW] Panorama Function
Public bug reported: It would be awesome to have a panorama function in the camera app. ** Affects: camera-app (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1605867 Title: Panorama Function Status in camera-app package in Ubuntu: New Bug description: It would be awesome to have a panorama function in the camera app. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1605867/+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 1602680] Re: ecryptfs not work with libnss3/libnss3-1d Version 2:3.23-0ubuntu0.12.04.1
Thanks for your help! FWIW, as it took me a bit to figure out how my libnspr4 version could be outdated: I have 0ad installed from the wfg ppa, which depends on libmozjs-31-0, which depends on libnspr4, and has this version in the ppa: libnspr4_4.10.10-0ubuntu0.14.04.1~12.04~wfg1_i386.deb - and that's apparently seen as an upgrade of libnspr4_4.12-0ubuntu0.12.04.1_i386.deb -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nss in Ubuntu. https://bugs.launchpad.net/bugs/1602680 Title: ecryptfs not work with libnss3/libnss3-1d Version 2:3.23-0ubuntu0.12.04.1 Status in nss package in Ubuntu: Invalid Bug description: After updating libnss3 and libnss3-1d from 2:3.21-0ubuntu0.12.04.3 to 2:3.23-0ubuntu0.12.04.1 last night it is not longer possible to mount my home directory encrypted with ecryptfs. Automatic by login or with ecryptfs-recover-private or else not work. After downgrade to Version 2:3.21-0ubuntu0.12.04.3 if works fine. syslog: Jul 13 01:29:36 Michael-Thinkpad-X121e-SSD ecryptfs-insert-wrapped-passphrase-into-keyring: do_hash: PK11_HashBuf() error; SECFailure = [-1]; PORT_GetError() = [-8128] Jul 13 01:29:36 Michael-Thinkpad-X121e-SSD ecryptfs-insert-wrapped-passphrase-into-keyring: Error generating passphrase signature; rc = [-22] Jul 13 01:29:36 Michael-Thinkpad-X121e-SSD ecryptfs-insert-wrapped-passphrase-into-keyring: Error attempting to unwrap passphrase from file [/home/michael/.ecryptfs/wrapped-passphrase]; rc = [-22] - lsb_release -rd Description: Ubuntu 12.04.5 LTS Release: 12.04 apt-cache policy libnss3 libnss3-1d after downgrade to previous version libnss3: Installiert: 2:3.21-0ubuntu0.12.04.3 Kandidat:2:3.23-0ubuntu0.12.04.1 Versionstabelle: 2:3.23-0ubuntu0.12.04.1 0 500 http://archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu/ precise-security/main amd64 Packages *** 2:3.21-0ubuntu0.12.04.3 0 100 /var/lib/dpkg/status 3.13.1.with.ckbi.1.88-1ubuntu6 0 500 http://archive.ubuntu.com/ubuntu/ precise/main amd64 Packages libnss3-1d: Installiert: 2:3.21-0ubuntu0.12.04.3 Kandidat:2:3.23-0ubuntu0.12.04.1 Versionstabelle: 2:3.23-0ubuntu0.12.04.1 0 500 http://archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu/ precise-security/main amd64 Packages *** 2:3.21-0ubuntu0.12.04.3 0 100 /var/lib/dpkg/status 3.13.1.with.ckbi.1.88-1ubuntu6 0 500 http://archive.ubuntu.com/ubuntu/ precise/main amd64 Packages I have marked the bug as security vulnerability because I must use older version they be more unsafe than the new one to work with my laptop. Unfortunately I go to holiday tomorrow. I'll be back at next monday 18. July 2016 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1602680/+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 1602680] Re: ecryptfs not work with libnss3/libnss3-1d Version 2:3.23-0ubuntu0.12.04.1
I'm also suffering from this exact bug, and setting the higher memory limit does not allow me to log in. auth.log shows: PAM unable to dlopen(pam_ecryptfs.so): /usr/lib/i386-linux-gnu/libnssutil3.so: undefined symbol: PR_GetEnvSecure PAM adding faulty module: pam_ecryptfs.so -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nss in Ubuntu. https://bugs.launchpad.net/bugs/1602680 Title: ecryptfs not work with libnss3/libnss3-1d Version 2:3.23-0ubuntu0.12.04.1 Status in nss package in Ubuntu: Incomplete Bug description: After updating libnss3 and libnss3-1d from 2:3.21-0ubuntu0.12.04.3 to 2:3.23-0ubuntu0.12.04.1 last night it is not longer possible to mount my home directory encrypted with ecryptfs. Automatic by login or with ecryptfs-recover-private or else not work. After downgrade to Version 2:3.21-0ubuntu0.12.04.3 if works fine. syslog: Jul 13 01:29:36 Michael-Thinkpad-X121e-SSD ecryptfs-insert-wrapped-passphrase-into-keyring: do_hash: PK11_HashBuf() error; SECFailure = [-1]; PORT_GetError() = [-8128] Jul 13 01:29:36 Michael-Thinkpad-X121e-SSD ecryptfs-insert-wrapped-passphrase-into-keyring: Error generating passphrase signature; rc = [-22] Jul 13 01:29:36 Michael-Thinkpad-X121e-SSD ecryptfs-insert-wrapped-passphrase-into-keyring: Error attempting to unwrap passphrase from file [/home/michael/.ecryptfs/wrapped-passphrase]; rc = [-22] - lsb_release -rd Description: Ubuntu 12.04.5 LTS Release: 12.04 apt-cache policy libnss3 libnss3-1d after downgrade to previous version libnss3: Installiert: 2:3.21-0ubuntu0.12.04.3 Kandidat:2:3.23-0ubuntu0.12.04.1 Versionstabelle: 2:3.23-0ubuntu0.12.04.1 0 500 http://archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu/ precise-security/main amd64 Packages *** 2:3.21-0ubuntu0.12.04.3 0 100 /var/lib/dpkg/status 3.13.1.with.ckbi.1.88-1ubuntu6 0 500 http://archive.ubuntu.com/ubuntu/ precise/main amd64 Packages libnss3-1d: Installiert: 2:3.21-0ubuntu0.12.04.3 Kandidat:2:3.23-0ubuntu0.12.04.1 Versionstabelle: 2:3.23-0ubuntu0.12.04.1 0 500 http://archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu/ precise-security/main amd64 Packages *** 2:3.21-0ubuntu0.12.04.3 0 100 /var/lib/dpkg/status 3.13.1.with.ckbi.1.88-1ubuntu6 0 500 http://archive.ubuntu.com/ubuntu/ precise/main amd64 Packages I have marked the bug as security vulnerability because I must use older version they be more unsafe than the new one to work with my laptop. Unfortunately I go to holiday tomorrow. I'll be back at next monday 18. July 2016 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1602680/+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 1594532] Re: Portrait mode is missing top
Since the last reboot of my tablet this bug seems gone. Strange because previous reboots did not help. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1594532 Title: Portrait mode is missing top Status in unity-scope-click package in Ubuntu: New Status in unity8 package in Ubuntu: Incomplete Bug description: When I open the apps scope in portrait mode on my m10 tablet. The top of the scope is missing. Contacts, camera etc + top 2 or 3 lines with apps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1594532/+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 1594532] Re: Portrait mode is missing top
Refresh does not help. Only go to ether scope, switch back to landscape ad go back to apps scope (sometimes needs a refresh) ** Attachment added: "screenshot20160622_220305439.png" https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1594532/+attachment/4688742/+files/screenshot20160622_220305439.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1594532 Title: Portrait mode is missing top Status in unity-scope-click package in Ubuntu: New Status in unity8 package in Ubuntu: Incomplete Bug description: When I open the apps scope in portrait mode on my m10 tablet. The top of the scope is missing. Contacts, camera etc + top 2 or 3 lines with apps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1594532/+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 1588727] Re: owncloud login
Installed 9.0.2 on an other computer. Indeed. Login works. Can't upgrade my production machine because not all owncloud paps work in version 9. Thanks anyway -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1588727 Title: owncloud login Status in webbrowser-app package in Ubuntu: Incomplete Bug description: In the webbrowser on my M10 tablet I am not able to login to my owncloud server. The login button (that is placed inside the password input) is not shown and accessable) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1588727/+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 1588727] Re: owncloud login
Owncloud 8.2 is the newest owncloud. I'm not sure if upgrading to 9 is possible. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1588727 Title: owncloud login Status in webbrowser-app package in Ubuntu: Incomplete Bug description: In the webbrowser on my M10 tablet I am not able to login to my owncloud server. The login button (that is placed inside the password input) is not shown and accessable) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1588727/+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 1588730] [NEW] lock screen doesn't rotate
Public bug reported: The Lock screen doesn't rotate so when you use the M10 tablet in a keyboard the lock screen is upside down making mousemovement impossibly difficult :-) ** Affects: libusermetrics (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libusermetrics in Ubuntu. https://bugs.launchpad.net/bugs/1588730 Title: lock screen doesn't rotate Status in libusermetrics package in Ubuntu: New Bug description: The Lock screen doesn't rotate so when you use the M10 tablet in a keyboard the lock screen is upside down making mousemovement impossibly difficult :-) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libusermetrics/+bug/1588730/+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 1588727] [NEW] owncloud login
Public bug reported: In the webbrowser on my M10 tablet I am not able to login to my owncloud server. The login button (that is placed inside the password input) is not shown and accessable) ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1588727 Title: owncloud login Status in webbrowser-app package in Ubuntu: New Bug description: In the webbrowser on my M10 tablet I am not able to login to my owncloud server. The login button (that is placed inside the password input) is not shown and accessable) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1588727/+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 1140716]
Tuesday, March 1, 2016, 9:43:23 PM, you wrote: > Chris Wilson changed bug 54226 > WhatRemovedAddedCC russ.pridem...@gmail.com > > Comment # 249 on bug 54226 from Chris Wilson > *** Bug 94057 has been marked as a duplicate of this bug. *** > > You are receiving this mail because: > You are on the CC list for the bug. > Sorry to say, but: Is there a way to get off the CC-list of this slightly depressing kind of "catch-all" bug ? It unfortunately doesn't seem to have be going anywhere for the last 3 to 4 years accept for an endless stream of duplicates being appended. -- Sander -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1140716 Title: [regression] 3.5.0-26-generic and 3.2.0-39-generic GPU hangs on Sandybridge Status in DRI: In Progress Status in Mesa: Unknown Status in linux package in Ubuntu: Invalid Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in mesa package in Ubuntu: Triaged Status in linux source package in Precise: Fix Committed Status in linux-lts-quantal source package in Precise: Fix Committed Status in linux-lts-raring source package in Precise: Invalid Status in mesa source package in Precise: Triaged Status in linux source package in Quantal: Invalid Status in linux-lts-quantal source package in Quantal: Invalid Status in linux source package in Raring: Invalid Status in linux-lts-quantal source package in Raring: Invalid Status in linux package in Debian: New Status in linux package in Fedora: Unknown Bug description: I'm getting errors about GPU hangs every minute or so (usually only when using FF and scrolling a webpage or something). I also get an annoying ubuntu dialog saying there is a "system error". This didn't happen with 3.5.0-24-generic. Here is the dmesg: [15169.033709] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [15169.034517] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [15628.480216] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [15628.480570] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [15844.231372] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [15844.231773] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [20173.232593] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [20173.233211] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [26285.650393] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [26285.650980] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [26285.658405] [ cut here ] [26285.658472] WARNING: at /build/buildd/linux-3.5.0/drivers/gpu/drm/i915/intel_pm.c:2505 gen6_enable_rps+0x706/0x710 [i915]() [26285.658474] Hardware name: SATELLITE Z830 [26285.658476] Modules linked in: sdhci_pci sdhci btrfs zlib_deflate libcrc32c ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs reiserfs ext2 snd_hda_codec_hdmi snd_hda_codec_realtek joydev btusb coretemp kvm_intel kvm arc4 ghash_clmulni_intel aesni_intel cryptd aes_x86_64 snd_hda_intel snd_hda_codec snd_hwdep uvcvideo snd_pcm videobuf2_core microcode videodev bnep iwlwifi videobuf2_vmalloc snd_seq_midi psmouse videobuf2_memops snd_rawmidi rfcomm pcspkr snd_seq_midi_event serio_raw snd_seq bluetooth mac80211 snd_timer snd_seq_device i915 drm_kms_helper cfg80211 drm toshiba_acpi snd sparse_keymap soundcore wmi i2c_algo_bit toshiba_bluetooth snd_page_alloc parport_pc mei video mac_hid lpc_ich ppdev nfsd nfs lockd fscache auth_rpcgss nfs_acl sunrpc lp parport e1000e ahci libahci [last unloaded: sdhci] [26285.658537] Pid: 23433, comm: kworker/u:0 Not tainted 3.5.0-26-generic #40-Ubuntu [26285.658539] Call Trace: [26285.658549] [] warn_slowpath_common+0x7f/0xc0 [26285.658553] [] warn_slowpath_null+0x1a/0x20 [26285.658569] [] gen6_enable_rps+0x706/0x710 [i915] [26285.658584] [] intel_modeset_init_hw+0x66/0xa0 [i915] [26285.658595] [] i915_reset+0x1a4/0x6e0 [i915] [26285.658601] [] ? __switch_to+0x12b/0x420 [26285.658612] [] i915_error_work_func+0xc3/0x110 [i915] [26285.658618] [] process_one_work+0x12a/0x420 [26285.658629] [] ? gen6_pm_rps_work+0xe0/0xe0 [i915] [26285.658632] [] worker_thread+0x12e/0x2f0 [26285.658636] [] ? manage_workers.isra.26+0x200/0x200 [26285.658640] [] kthread+0x93/0xa0 [26285.658644] [] kernel_thread_helper+0x4/0x10 [26285.658649] [] ? kthread_freezable_should_stop+0x70/0x70 [26285.658652] [] ? gs_change+0x13/0x13 [26285.658654] ---[ end trace 59c6162fdfcbffee ]--- [26756.021167] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [26756.021426] [drm] E
[Touch-packages] [Bug 1466581] [NEW] Unable to unmount 'hung NFS mount' (server gone) with FORCE and/or LAZY
Public bug reported: Ubuntu Trusty, util-linux 2.20.1-5.1ubuntu20.3 I can't 'umount -f /mnt/storage' an NFS-filesystem whose remote end has gone missing. The process just stalls in an uninterruptable state. Strace shows umount at some point tries to readlink() the mount point which stalls because that mount point is broken. Which is why i want to force umount it. ;) I then proceeded to remove 99% of umount.c's code so it would just call umount2() on the target with the FORCE flag, recompiled the binary and it 'neatly' unmounted the filesystem. I think umount.c tries too many sanity checks with -f enabled. It should perhaps ask if the user is really sure, and then just call umount on the target and fix mtab etc... ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1466581 Title: Unable to unmount 'hung NFS mount' (server gone) with FORCE and/or LAZY Status in util-linux package in Ubuntu: New Bug description: Ubuntu Trusty, util-linux 2.20.1-5.1ubuntu20.3 I can't 'umount -f /mnt/storage' an NFS-filesystem whose remote end has gone missing. The process just stalls in an uninterruptable state. Strace shows umount at some point tries to readlink() the mount point which stalls because that mount point is broken. Which is why i want to force umount it. ;) I then proceeded to remove 99% of umount.c's code so it would just call umount2() on the target with the FORCE flag, recompiled the binary and it 'neatly' unmounted the filesystem. I think umount.c tries too many sanity checks with -f enabled. It should perhaps ask if the user is really sure, and then just call umount on the target and fix mtab etc... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1466581/+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 1173915] Re: initctl continuously takes 100% of CPU
Same issue here, Ubuntu 14.04 64 bits on a Toshiba Portege Z30-A 18J, custom kernel 3.18.11 64 bits though. I suspect it has something to do with certain processes running on the system, such as perhaps Nautilus, but no hard evidence. The problem only occurs after a long uptime duration. Strace gives the same result as #5 mentioned. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1173915 Title: initctl continuously takes 100% of CPU Status in upstart package in Ubuntu: Confirmed Bug description: Many programs are fairly slow to start on my computer, despite it being relatively new (core i5). Suspecting a heavy CPU usage, I started gnome-system-monitor: all processes were displayed at 0% CPU, but the overall load was 1.33; 1.33; 1.34. Using the top command, however, revealed the real CPU use, with the initctl process taking 100%CPU, even 1 hour after startup. I upgraded to roaring ringtail before checking this but the symptoms were the same with quantal quetzal, so there is a fair chance the causes were identical. Regards ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: upstart 1.8-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CheckboxSubmission: 2deefc5fd2f1f0ae2fdd4bd781248a2a CheckboxSystem: daed2f3d6643b4a84b4520a2427f8c2b Date: Sun Apr 28 13:04:05 2013 ExecutablePath: /sbin/initctl InstallationDate: Installed on 2012-12-15 (133 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True ProcEnviron: ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=fa624f8f-d9d0-4b09-af8b-88b106aaaf5b ro quiet splash vt.handoff=7 SourcePackage: upstart UpgradeStatus: Upgraded to raring on 2013-04-28 (0 days ago) UpstartBugCategory: System To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1173915/+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 1426910] [NEW] kdb5_ldap_util creates principal with wrong DNS domain
Public bug reported: If there is more than one domain in the search line of /etc/resolv.conf when kdb5_ldap_util create is used to populate the LDAP directory, a wrong hostname is composed. kdb5_ldap_util seems to use the last domain name of the search list, which is obviously not always correct. Maybe kdb5_ldap_util should use an algorithm like hostname --fqdn to determine the fully qualified domain name of the host. ** Affects: krb5 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1426910 Title: kdb5_ldap_util creates principal with wrong DNS domain Status in krb5 package in Ubuntu: New Bug description: If there is more than one domain in the search line of /etc/resolv.conf when kdb5_ldap_util create is used to populate the LDAP directory, a wrong hostname is composed. kdb5_ldap_util seems to use the last domain name of the search list, which is obviously not always correct. Maybe kdb5_ldap_util should use an algorithm like hostname --fqdn to determine the fully qualified domain name of the host. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1426910/+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 1397319] Re: two sequential login windows after resuming from sleep
Update: After installing gdm (instead of lightdm) the problem did not occur anymore. So: the problem seems to be in lightdm. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1397319 Title: two sequential login windows after resuming from sleep Status in lightdm package in Ubuntu: New Bug description: After resuming from sleep, I sometimes (about 50%) get a first (unusual, ugly) login screen, then a short (1 sec) flash showing my desktop, then the 'normal' login screen First login window: http://oi59.tinypic.com/ws5uo9.jpg Second login window: http://oi57.tinypic.com/24xnx4w.jpg I tried the 4 sudo commands from http://ubuntuforums.org/showthread.php?t=1867733p=11626298#post11626298, but that did not update anything, so I expect that to change nothing. Then, based on http://ubuntuforums.org/showthread.php?t=1867733page=3p=12566826#post12566826, I installed and selected gdm instead of lightdm. I'll post back the results after a few days of usage. TBC ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Fri Nov 28 14:03:32 2014 InstallationDate: Installed on 2013-09-01 (452 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) LightdmConfig: [SeatDefaults] user-session=ubuntu greeter-session=unity-greeter SourcePackage: lightdm UpgradeStatus: Upgraded to trusty on 2014-03-17 (255 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1397319/+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 1397319] [NEW] two sequential login windows after resuming from sleep
Public bug reported: After resuming from sleep, I sometimes (about 50%) get a first (unusual, ugly) login screen, then a short (1 sec) flash showing my desktop, then the 'normal' login screen First login window: http://oi59.tinypic.com/ws5uo9.jpg Second login window: http://oi57.tinypic.com/24xnx4w.jpg I tried the 4 sudo commands from http://ubuntuforums.org/showthread.php?t=1867733p=11626298#post11626298, but that did not update anything, so I expect that to change nothing. Then, based on http://ubuntuforums.org/showthread.php?t=1867733page=3p=12566826#post12566826, I installed and selected gdm instead of lightdm. I'll post back the results after a few days of usage. TBC ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Fri Nov 28 14:03:32 2014 InstallationDate: Installed on 2013-09-01 (452 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) LightdmConfig: [SeatDefaults] user-session=ubuntu greeter-session=unity-greeter SourcePackage: lightdm UpgradeStatus: Upgraded to trusty on 2014-03-17 (255 days ago) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1397319 Title: two sequential login windows after resuming from sleep Status in lightdm package in Ubuntu: New Bug description: After resuming from sleep, I sometimes (about 50%) get a first (unusual, ugly) login screen, then a short (1 sec) flash showing my desktop, then the 'normal' login screen First login window: http://oi59.tinypic.com/ws5uo9.jpg Second login window: http://oi57.tinypic.com/24xnx4w.jpg I tried the 4 sudo commands from http://ubuntuforums.org/showthread.php?t=1867733p=11626298#post11626298, but that did not update anything, so I expect that to change nothing. Then, based on http://ubuntuforums.org/showthread.php?t=1867733page=3p=12566826#post12566826, I installed and selected gdm instead of lightdm. I'll post back the results after a few days of usage. TBC ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Fri Nov 28 14:03:32 2014 InstallationDate: Installed on 2013-09-01 (452 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) LightdmConfig: [SeatDefaults] user-session=ubuntu greeter-session=unity-greeter SourcePackage: lightdm UpgradeStatus: Upgraded to trusty on 2014-03-17 (255 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1397319/+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 1186662] Re: isc-dhcp-server fails to renew lease file
Workaround from http://ubuntuforums.org/showthread.php?t=2141740page=2 sudo setfacl -dm u:dhcpd:rwx /var/lib/dhcp sudo setfacl -m u:dhcpd:rwx /var/lib/dhcp -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1186662 Title: isc-dhcp-server fails to renew lease file Status in “isc-dhcp” package in Ubuntu: Triaged Bug description: After raring upgrade, the dhcp server fails to renew lease file when it tries to (about every hour). The syslog says: dhcpd: Can't create new lease file: Permission denied It looks like a permission problem, because # chown -R dhcpd:dhcpd /var/lib/dhcp the above command temporarily solves the issue, until dhcpd is restarted: at that time, the ownership of the directory and the lease file is set back to root:root. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1186662/+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 905660] Re: [ifupdown] ipv6 refuse vlan interfaces
It looks like ifupdown tries to configure the VLAN a second time when it comes across the inet6 definition in /etc/network/interfaces. This fails as the VLAN interface was already setup in the inet definition of the same interface. It looks like a conceptual error in the interfaces(5) syntax. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/905660 Title: [ifupdown] ipv6 refuse vlan interfaces Status in “ifupdown” package in Ubuntu: Fix Released Bug description: Package: ifupdown Version: ifupdown 0.7~alpha5.1ubuntu5 Severity: normal ifupdown (0.7~beta1) correct this bug : * Accept VLAN interface names (Closes: #632902). The interfaces file: (/etc/network/interfaces) auto eth0.77 iface eth0.77 inet static address 192.168.1.50 netmask 255.255.255.0 gateway 192.168.1.1 iface eth0.77 inet6 static address 2a01:6e00::::2 netmask 64 gateway 2a01:6e00::::1 = IPv4 is OK with VLAN77 = IPv6 not mont with VLAN77 (IPv6 ok without VLAN) Bug with IPv6 auto : http://bugs.debian.org/cgi- bin/bugreport.cgi?bug=632902 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/905660/+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 1354668] [NEW] Fix for suspend/hibernate with DVB-t USB stick
Public bug reported: I have a Terratec Cinergy T USB XXS DVB-t USB stick, but when you suspend the system while a radio or TV channel is actively playing in some application, the system does not correctly suspend the device. The system will not wake up again and you have to reset the computer. This bug exists for at least 3 year and likely people with similar DVB-t USB sticks will be affected as well. I have created a failure proof workaround solution for VLC by creating the script /etc/pm/sleep.d/50_dvb_usb_dib0700_quirk: #!/bin/sh PASS=enter password for LUA telnet access to VLC case $1 in hibernate|suspend) # check whether a stream with telx (Teletext) is active or not if [ `{ echo $PASS; echo info; } | netcat localhost 4212 -q 1 | grep -c telx` -eq 0 ] then continue else { echo $PASS; echo stop; } | netcat localhost 4212 -q 1 /dev/null fi modprobe -r dvb_usb_dib0700 sleep 1 ;; thaw|resume) modprobe dvb_usb_dib0700 # automatically start playing after wake up { echo $PASS; echo play; } | netcat localhost 4212 -q 1 /dev/null ;; *) exit $NA ;; esac This solution was inspired by: http://forum.xbmc.org/printthread.php?tid=71490 ** Affects: pm-utils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1354668 Title: Fix for suspend/hibernate with DVB-t USB stick Status in “pm-utils” package in Ubuntu: New Bug description: I have a Terratec Cinergy T USB XXS DVB-t USB stick, but when you suspend the system while a radio or TV channel is actively playing in some application, the system does not correctly suspend the device. The system will not wake up again and you have to reset the computer. This bug exists for at least 3 year and likely people with similar DVB-t USB sticks will be affected as well. I have created a failure proof workaround solution for VLC by creating the script /etc/pm/sleep.d/50_dvb_usb_dib0700_quirk: #!/bin/sh PASS=enter password for LUA telnet access to VLC case $1 in hibernate|suspend) # check whether a stream with telx (Teletext) is active or not if [ `{ echo $PASS; echo info; } | netcat localhost 4212 -q 1 | grep -c telx` -eq 0 ] then continue else { echo $PASS; echo stop; } | netcat localhost 4212 -q 1 /dev/null fi modprobe -r dvb_usb_dib0700 sleep 1 ;; thaw|resume) modprobe dvb_usb_dib0700 # automatically start playing after wake up { echo $PASS; echo play; } | netcat localhost 4212 -q 1 /dev/null ;; *) exit $NA ;; esac This solution was inspired by: http://forum.xbmc.org/printthread.php?tid=71490 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1354668/+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 1349128] Re: Ubuntu 14.04 login screen doesn't accept keyboard input (until using indicators)
When not accepting/showing input from the keyboard, there is the usual vertical blinking line in the password box (so: 'showing' it is accepting input there), with the word password in the background of that password box. Would it help if I post a picture of video of what goes (or: doesn't go) on? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1349128 Title: Ubuntu 14.04 login screen doesn't accept keyboard input (until using indicators) Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: Ubuntu 14.04 login screen doesn't accept keyboard input in the password box after my system has resumed from a sleep (=lid opening), so I can't relogin anymore Excpected behaviour: the login screen should accept keyboard input and show them as stars in the password box. Workaround: click on switch user in the upper right corner, after which keyboard input is accepted again. $ lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 System is fully updated. Problem started to happen one or two weeks ago, so around mid July 2014. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1349128/+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 1349128] Re: Ubuntu 14.04 login screen doesn't accept keyboard input
** Package changed: ubuntu = lightdm (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1349128 Title: Ubuntu 14.04 login screen doesn't accept keyboard input Status in “lightdm” package in Ubuntu: New Bug description: Ubuntu 14.04 login screen doesn't accept keyboard input in the password box after my system has resumed from a sleep (=lid opening), so I can't relogin anymore Excpected behaviour: the login screen should accept keyboard input and show them as stars in the password box. Workaround: click on switch user in the upper right corner, after which keyboard input is accepted again. $ lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 System is fully updated. Problem started to happen one or two weeks ago, so around mid July 2014. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1349128/+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 1349128] Re: Ubuntu 14.04 login screen doesn't accept keyboard input
Update: Another workaround: change the language in the upper right corner, in my case switch from En1 to En2. After that, the password box accepts keyboard input and shows corresponding dots. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1349128 Title: Ubuntu 14.04 login screen doesn't accept keyboard input Status in “lightdm” package in Ubuntu: New Bug description: Ubuntu 14.04 login screen doesn't accept keyboard input in the password box after my system has resumed from a sleep (=lid opening), so I can't relogin anymore Excpected behaviour: the login screen should accept keyboard input and show them as stars in the password box. Workaround: click on switch user in the upper right corner, after which keyboard input is accepted again. $ lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 System is fully updated. Problem started to happen one or two weeks ago, so around mid July 2014. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1349128/+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 1341103] [NEW] No Sound (Realtek ALC887)
Public bug reported: After updating to the 3.13.0-30-generic kernel sound has stopped working. DMESG gives numerous errors about unknow symbols and disagreeing about version of symbol while loading the snd_hda_codec. Reverting to a previous kernel (3.13.0-29-generic) restores sound. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: hostname 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: GNOME Date: Sat Jul 12 11:35:33 2014 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/24/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97P-D3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd04/24/2014:svnGigabyteTechnologyCo.,Ltd.:pnZ97P-D3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97P-D3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: Z97P-D3 dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1341103 Title: No Sound (Realtek ALC887) Status in “alsa-driver” package in Ubuntu: New Bug description: After updating to the 3.13.0-30-generic kernel sound has stopped working. DMESG gives numerous errors about unknow symbols and disagreeing about version of symbol while loading the snd_hda_codec. Reverting to a previous kernel (3.13.0-29-generic) restores sound. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: hostname 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: GNOME Date: Sat Jul 12 11:35:33 2014 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/24/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97P-D3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd04/24/2014:svnGigabyteTechnologyCo.,Ltd.:pnZ97P-D3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97P-D3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: Z97P-D3 dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1341103/+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 1341103] Re: No Sound (Realtek ALC887)
PulseAudio verbose log was requested, so hereby provided :D ** Attachment added: pulseverbose.log https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1341103/+attachment/4151078/+files/pulseverbose.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1341103 Title: No Sound (Realtek ALC887) Status in “alsa-driver” package in Ubuntu: New Bug description: After updating to the 3.13.0-30-generic kernel sound has stopped working. DMESG gives numerous errors about unknow symbols and disagreeing about version of symbol while loading the snd_hda_codec. Reverting to a previous kernel (3.13.0-29-generic) restores sound. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: hostname 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: GNOME Date: Sat Jul 12 11:35:33 2014 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/24/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97P-D3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd04/24/2014:svnGigabyteTechnologyCo.,Ltd.:pnZ97P-D3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97P-D3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: Z97P-D3 dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1341103/+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