[Touch-packages] [Bug 1801382] Re: printing complex documents does not reproduce screen image on paper
Hi to all, I switched to macOS after the ongoing issues that reoccured with 19.04 (including this one). I could not bear with it any longer (12 years are a long time). Sorry to be of no assistance to this and any other issues any longer. cheers -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1801382 Title: printing complex documents does not reproduce screen image on paper Status in evince package in Ubuntu: Incomplete Status in gtk+3.0 package in Ubuntu: Incomplete Bug description: Ubuntu 18.10 latest update (by 2.11.2018) printing PDF documents that contain embedded images, these images get printed nearly black and completely illegible. I have attached a sample file and a printout of my cups pdf writer (which produces the exact same results as the printer) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: cups 2.2.8-5ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CupsErrorLog: W [02/Nov/2018:16:18:30 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M477fdw_AF82F1_-Gray..\' already exists W [02/Nov/2018:16:18:30 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M477fdw_AF82F1_-DeviceN..\' already exists W [02/Nov/2018:16:20:30 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M477fdw_AF82F1_-Gray..\' already exists W [02/Nov/2018:16:20:30 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M477fdw_AF82F1_-DeviceN..\' already exists CurrentDesktop: ubuntu:GNOME Date: Fri Nov 2 16:21:51 2018 InstallationDate: Installed on 2018-04-30 (186 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: device for HP_Color_LaserJet_MFP_M477fdw: hp:/net/HP_Color_LaserJet_MFP_M477fdw?ip=10.1.0.21 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05ac:0273 Apple, Inc. Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to cosmic on 2018-10-20 (13 days ago) dmi.bios.date: 08/08/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0171.B00.1708080033 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1801382/+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 1812637] [NEW] systemd-resolved stops resolving
Public bug reported: Regularly (= after about 15 mins of use) the systemd-resolved service stops resolving DNS names (any). Configuration: Two domains defined - one internal, one for external services DNS server does not provide DNSSEC services Both domains are in the search path (served by DHCP) Effect: Clients refuse to resolve internal domain servers (short or FQDN) after about 15 mins. Workaround: from the client CLI sudo systemctl restart systemd-resolved.service Background: A Github error (https://github.com/systemd/systemd/issues/6490) describes the cause to be (missing) DNSSEC. I found discussions about "the correct way" DNS works (with only one domain). Happens exclusively on Ubuntu clients (Windows, Mac and Fedora worked fine). ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: systemd 239-7ubuntu10.6 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 21 11:57:32 2019 InstallationDate: Installed on 2018-04-30 (266 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05ac:0273 Apple, Inc. Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: Upgraded to cosmic on 2018-10-20 (92 days ago) dmi.bios.date: 08/08/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0171.B00.1708080033 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- 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/1812637 Title: systemd-resolved stops resolving Status in systemd package in Ubuntu: New Bug description: Regularly (= after about 15 mins of use) the systemd-resolved service stops resolving DNS names (any). Configuration: Two domains defined - one internal, one for external services DNS server does not provide DNSSEC services Both domains are in the search path (served by DHCP) Effect: Clients refuse to resolve internal domain servers (short or FQDN) after about 15 mins. Workaround: from the client CLI sudo systemctl restart systemd-resolved.service Background: A Github error (https://github.com/systemd/systemd/issues/6490) describes the cause to be (missing) DNSSEC. I found discussions about "the correct way" DNS works (with only one domain). Happens exclusively on Ubuntu clients (Windows, Mac and Fedora worked fine). ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: systemd 239-7ubuntu10.6 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 21 11:57:32 2019 InstallationDate: Installed on 2018-04-30 (266 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05ac:0273 Apple, Inc. Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: Upgraded to cosmic on 2018-10-20 (92 days ago) dmi.bios.date: 08/08/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0171.B00.1708080033 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.v
[Touch-packages] [Bug 1801382] Re: printing complex documents does not reproduce screen image on paper
Todays update of evince (3.30.1-1ubuntu1.2) did not change anything. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1801382 Title: printing complex documents does not reproduce screen image on paper Status in evince package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: Ubuntu 18.10 latest update (by 2.11.2018) printing PDF documents that contain embedded images, these images get printed nearly black and completely illegible. I have attached a sample file and a printout of my cups pdf writer (which produces the exact same results as the printer) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: cups 2.2.8-5ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CupsErrorLog: W [02/Nov/2018:16:18:30 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M477fdw_AF82F1_-Gray..\' already exists W [02/Nov/2018:16:18:30 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M477fdw_AF82F1_-DeviceN..\' already exists W [02/Nov/2018:16:20:30 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M477fdw_AF82F1_-Gray..\' already exists W [02/Nov/2018:16:20:30 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M477fdw_AF82F1_-DeviceN..\' already exists CurrentDesktop: ubuntu:GNOME Date: Fri Nov 2 16:21:51 2018 InstallationDate: Installed on 2018-04-30 (186 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: device for HP_Color_LaserJet_MFP_M477fdw: hp:/net/HP_Color_LaserJet_MFP_M477fdw?ip=10.1.0.21 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05ac:0273 Apple, Inc. Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to cosmic on 2018-10-20 (13 days ago) dmi.bios.date: 08/08/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0171.B00.1708080033 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1801382/+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 1801382] Re: printing complex documents does not reproduce screen image on paper
** Attachment added: "This is the printed document with blackened images (s. page 7)" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1801382/+attachment/5208359/+files/StepStone_Eyetracking_Whitepaper_after_printing_with_cups.pdf -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1801382 Title: printing complex documents does not reproduce screen image on paper Status in cups package in Ubuntu: New Bug description: Ubuntu 18.10 latest update (by 2.11.2018) printing PDF documents that contain embedded images, these images get printed nearly black and completely illegible. I have attached a sample file and a printout of my cups pdf writer (which produces the exact same results as the printer) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: cups 2.2.8-5ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CupsErrorLog: W [02/Nov/2018:16:18:30 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M477fdw_AF82F1_-Gray..\' already exists W [02/Nov/2018:16:18:30 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M477fdw_AF82F1_-DeviceN..\' already exists W [02/Nov/2018:16:20:30 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M477fdw_AF82F1_-Gray..\' already exists W [02/Nov/2018:16:20:30 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M477fdw_AF82F1_-DeviceN..\' already exists CurrentDesktop: ubuntu:GNOME Date: Fri Nov 2 16:21:51 2018 InstallationDate: Installed on 2018-04-30 (186 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: device for HP_Color_LaserJet_MFP_M477fdw: hp:/net/HP_Color_LaserJet_MFP_M477fdw?ip=10.1.0.21 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05ac:0273 Apple, Inc. Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to cosmic on 2018-10-20 (13 days ago) dmi.bios.date: 08/08/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0171.B00.1708080033 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1801382/+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 1801382] [NEW] printing complex documents does not reproduce screen image on paper
Public bug reported: Ubuntu 18.10 latest update (by 2.11.2018) printing PDF documents that contain embedded images, these images get printed nearly black and completely illegible. I have attached a sample file and a printout of my cups pdf writer (which produces the exact same results as the printer) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: cups 2.2.8-5ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CupsErrorLog: W [02/Nov/2018:16:18:30 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M477fdw_AF82F1_-Gray..\' already exists W [02/Nov/2018:16:18:30 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M477fdw_AF82F1_-DeviceN..\' already exists W [02/Nov/2018:16:20:30 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M477fdw_AF82F1_-Gray..\' already exists W [02/Nov/2018:16:20:30 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M477fdw_AF82F1_-DeviceN..\' already exists CurrentDesktop: ubuntu:GNOME Date: Fri Nov 2 16:21:51 2018 InstallationDate: Installed on 2018-04-30 (186 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: device for HP_Color_LaserJet_MFP_M477fdw: hp:/net/HP_Color_LaserJet_MFP_M477fdw?ip=10.1.0.21 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05ac:0273 Apple, Inc. Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to cosmic on 2018-10-20 (13 days ago) dmi.bios.date: 08/08/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0171.B00.1708080033 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic ** Attachment added: "Original PDF with embedded images" https://bugs.launchpad.net/bugs/1801382/+attachment/5208346/+files/StepStone_Eyetracking_Whitepaper.pdf -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1801382 Title: printing complex documents does not reproduce screen image on paper Status in cups package in Ubuntu: New Bug description: Ubuntu 18.10 latest update (by 2.11.2018) printing PDF documents that contain embedded images, these images get printed nearly black and completely illegible. I have attached a sample file and a printout of my cups pdf writer (which produces the exact same results as the printer) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: cups 2.2.8-5ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CupsErrorLog: W [02/Nov/2018:16:18:30 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M477fdw_AF82F1_-Gray..\' already exists W [02/Nov/2018:16:18:30 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M477fdw_AF82F1_-DeviceN..\' already exists W [02/Nov/2018:16:20:30 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M477fdw_AF82F1_-Gray..\' already exists W [02/Nov/2018:16:20:30 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M477fdw_AF82F1_-DeviceN..\' already exists CurrentDesktop: ubuntu:GNOME Date: Fri Nov 2 16:21:51 2018 InstallationDate: Installed on 2018-04-30 (186 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: device for HP_Color_LaserJet_MFP_M477fdw: hp:/net/HP_Color_LaserJet_MFP_M477fdw?
[Touch-packages] [Bug 1799038] Re: Ubuntu 18.10 does not suspend on lid close
@Kai-Heng Feng: How should I compare /sys/kernel/debug/wakeup_sources if this path does not exist on a plain Ubuntu installation? @Brian Murray: What else do you need to mark it confirmed again (This issue is well reported if you search Google). -- 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/1799038 Title: Ubuntu 18.10 does not suspend on lid close Status in systemd package in Ubuntu: Incomplete Bug description: After an upgrade to Ubuntu 18.10 suspend to RAM due to closing the lid on notebooks does not work any more. The machine goes to suspend mode but wakes up immediately due to some events (can be network, or others). In 18.04 this issue was fixed (we had the same situation with any version since 14.04). Seems a regression. Mitigation reports suggesting to change /etc/systemd/logind.conf are WRONG. The changes do NOTHING. One might spare the time to experiment. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: systemd 239-7ubuntu10 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 21 11:55:48 2018 InstallationDate: Installed on 2018-04-30 (174 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05ac:0273 Apple, Inc. Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: Upgraded to cosmic on 2018-10-20 (0 days ago) dmi.bios.date: 08/08/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0171.B00.1708080033 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. mtime.conffile..etc.systemd.logind.conf: 2018-10-20T22:01:57.469491 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1799038/+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 1799038] Re: Ubuntu 18.10 does not suspend on lid close
In journalctl I found that whenever the machine reached suspend target, ACPI kicked in to wake the machine again. kernel: ACPI: Low-level resume complete Today, I put the machine to sleep (using the alt option on the shutdown menu). The machine woke up every two seconds and went to sleep again (for over half an hour). Finally and for no obvious reason, the machine kept sleeping until I woke it up 3 hours later. Weired -- 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/1799038 Title: Ubuntu 18.10 does not suspend on lid close Status in systemd package in Ubuntu: New Bug description: After an upgrade to Ubuntu 18.10 suspend to RAM due to closing the lid on notebooks does not work any more. The machine goes to suspend mode but wakes up immediately due to some events (can be network, or others). In 18.04 this issue was fixed (we had the same situation with any version since 14.04). Seems a regression. Mitigation reports suggesting to change /etc/systemd/logind.conf are WRONG. The changes do NOTHING. One might spare the time to experiment. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: systemd 239-7ubuntu10 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 21 11:55:48 2018 InstallationDate: Installed on 2018-04-30 (174 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05ac:0273 Apple, Inc. Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: Upgraded to cosmic on 2018-10-20 (0 days ago) dmi.bios.date: 08/08/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0171.B00.1708080033 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. mtime.conffile..etc.systemd.logind.conf: 2018-10-20T22:01:57.469491 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1799038/+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 1799038] Re: Ubuntu 18.10 does not suspend on lid close
I have figured out how to make the machine go to sleep. press alt on the shutdown menu makes the machine go to sleep and immediately wake up again. Do it again and it goes to sleep. HOWEVER: This triggers another issue: Resume does not work every second time (requires reboot). I could not figure out why this behaviour is like it is. Since the syslog is not the destination of logs any more (journalctl is) the messages are somewhat arbitrary. -- 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/1799038 Title: Ubuntu 18.10 does not suspend on lid close Status in systemd package in Ubuntu: New Bug description: After an upgrade to Ubuntu 18.10 suspend to RAM due to closing the lid on notebooks does not work any more. The machine goes to suspend mode but wakes up immediately due to some events (can be network, or others). In 18.04 this issue was fixed (we had the same situation with any version since 14.04). Seems a regression. Mitigation reports suggesting to change /etc/systemd/logind.conf are WRONG. The changes do NOTHING. One might spare the time to experiment. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: systemd 239-7ubuntu10 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 21 11:55:48 2018 InstallationDate: Installed on 2018-04-30 (174 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05ac:0273 Apple, Inc. Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: Upgraded to cosmic on 2018-10-20 (0 days ago) dmi.bios.date: 08/08/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0171.B00.1708080033 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. mtime.conffile..etc.systemd.logind.conf: 2018-10-20T22:01:57.469491 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1799038/+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 1799038] [NEW] Ubuntu 18.10 does not suspend on lid close
Public bug reported: After an upgrade to Ubuntu 18.10 suspend to RAM due to closing the lid on notebooks does not work any more. The machine goes to suspend mode but wakes up immediately due to some events (can be network, or others). In 18.04 this issue was fixed (we had the same situation with any version since 14.04). Seems a regression. Mitigation reports suggesting to change /etc/systemd/logind.conf are WRONG. The changes do NOTHING. One might spare the time to experiment. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: systemd 239-7ubuntu10 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 21 11:55:48 2018 InstallationDate: Installed on 2018-04-30 (174 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05ac:0273 Apple, Inc. Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: Upgraded to cosmic on 2018-10-20 (0 days ago) dmi.bios.date: 08/08/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0171.B00.1708080033 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. mtime.conffile..etc.systemd.logind.conf: 2018-10-20T22:01:57.469491 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- 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/1799038 Title: Ubuntu 18.10 does not suspend on lid close Status in systemd package in Ubuntu: New Bug description: After an upgrade to Ubuntu 18.10 suspend to RAM due to closing the lid on notebooks does not work any more. The machine goes to suspend mode but wakes up immediately due to some events (can be network, or others). In 18.04 this issue was fixed (we had the same situation with any version since 14.04). Seems a regression. Mitigation reports suggesting to change /etc/systemd/logind.conf are WRONG. The changes do NOTHING. One might spare the time to experiment. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: systemd 239-7ubuntu10 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 21 11:55:48 2018 InstallationDate: Installed on 2018-04-30 (174 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05ac:0273 Apple, Inc. Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: Upgraded to cosmic on 2018-10-20 (0 days ago) dmi.bios.date: 08/08/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0171.B00.1708080033 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. mtime.conffile..etc.systemd.logind.conf: 2018-10-20T22:01:57.469491 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1799038/+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 663534] Re: Printing errors after upgrade
Bug fixed since several versions ** Changed in: cups (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/663534 Title: Printing errors after upgrade Status in cups package in Ubuntu: Fix Released Bug description: Binary package hint: cups Updated cups and pdf printing today (auto upgrade) Now printing double-sided does not work (even when set on the printer). Printing of PDFs stalls and does not print anything. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: cups 1.4.4-6ubuntu2.1 ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Tue Oct 19 23:07:49 2010 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release Candidate amd64 (20091020.3) Lpstat: device for HP-Color-LaserJet-CP2025dn: hp:/net/HP_Color_LaserJet_CP2025dn?zc=NPI33DED8 MachineType: Hewlett-Packard HP Compaq 8510w Papersize: letter PccardctlStatus: Socket 0: no card Socket 1: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver "pata_pcmcia" PpdFiles: HP-Color-LaserJet-CP2025dn: HP Color LaserJet cp2025dn pcl3, hpcups 3.10.6 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic root=UUID=b921775a-49a7-48e8-985e-1907bc29f71e ro quiet splash ProcEnviron: LANGUAGE=en_GB:en LANG=en_GB.utf8 SHELL=/bin/bash SourcePackage: cups dmi.bios.date: 07/25/2007 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.05 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.32 dmi.chassis.asset.tag: CNU7402CLM dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.05:bd07/25/2007:svnHewlett-Packard:pnHPCompaq8510w:pvrF.05:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.32:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP Compaq 8510w dmi.product.version: F.05 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/663534/+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 663534] Re: Printing errors after upgrade
can be closed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/663534 Title: Printing errors after upgrade Status in cups package in Ubuntu: Fix Released Bug description: Binary package hint: cups Updated cups and pdf printing today (auto upgrade) Now printing double-sided does not work (even when set on the printer). Printing of PDFs stalls and does not print anything. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: cups 1.4.4-6ubuntu2.1 ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Tue Oct 19 23:07:49 2010 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release Candidate amd64 (20091020.3) Lpstat: device for HP-Color-LaserJet-CP2025dn: hp:/net/HP_Color_LaserJet_CP2025dn?zc=NPI33DED8 MachineType: Hewlett-Packard HP Compaq 8510w Papersize: letter PccardctlStatus: Socket 0: no card Socket 1: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver "pata_pcmcia" PpdFiles: HP-Color-LaserJet-CP2025dn: HP Color LaserJet cp2025dn pcl3, hpcups 3.10.6 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic root=UUID=b921775a-49a7-48e8-985e-1907bc29f71e ro quiet splash ProcEnviron: LANGUAGE=en_GB:en LANG=en_GB.utf8 SHELL=/bin/bash SourcePackage: cups dmi.bios.date: 07/25/2007 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.05 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.32 dmi.chassis.asset.tag: CNU7402CLM dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.05:bd07/25/2007:svnHewlett-Packard:pnHPCompaq8510w:pvrF.05:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.32:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP Compaq 8510w dmi.product.version: F.05 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/663534/+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 1733667] [NEW] bluetooth service does not start on reboot
Public bug reported: $ uname -a Linux mbpr13b 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Just updated to latest repo kernel. After reboot, the bluetoothd gets started but not activated. Restarting does not work (error msg in bluetooth panel: adapter not found - it was there before the reboot). Required several reboots to fix the issue (i.e. after a reboot I have to reboot several times, click the mouse frantically during boot to get it recognized somewhere during the bootup). I remember this to have happened two kernels before so I think it is a regression. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: bluez 5.46-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 21 18:58:04 2017 InstallationDate: Installed on 2017-10-20 (32 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05ac:0273 Apple, Inc. Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-17-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0171.B00.1708080033 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. hciconfig: hci0: Type: Primary Bus: USB BD Address: 4C:32:75:9F:91:1E ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN RX bytes:28328 acl:854 sco:0 events:231 errors:0 TX bytes:6881 acl:65 sco:0 commands:121 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session -- 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/1733667 Title: bluetooth service does not start on reboot Status in bluez package in Ubuntu: New Bug description: $ uname -a Linux mbpr13b 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Just updated to latest repo kernel. After reboot, the bluetoothd gets started but not activated. Restarting does not work (error msg in bluetooth panel: adapter not found - it was there before the reboot). Required several reboots to fix the issue (i.e. after a reboot I have to reboot several times, click the mouse frantically during boot to get it recognized somewhere during the bootup). I remember this to have happened two kernels before so I think it is a regression. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: bluez 5.46-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 21 18:58:04 2017 InstallationDate: Installed on 2017-10-20 (32 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05ac:0273 Apple, Inc. Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-17-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0171.B00.1708080033 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D48
[Touch-packages] [Bug 1718890] Re: name resolution stops working
To make clear the bearing of this: systemd-resolved stops working on EVERY machine here after 5 minutes. the DNS server has not been down since April A Macintosh running macOS High Sierra installed for comparison can resolve and connect to internal resources in every case where Ubuntu looses connection. And a last one: internally, my domain uses .internal as domain name. I want to keep this separate from my official domains. -- 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/1718890 Title: name resolution stops working Status in systemd package in Ubuntu: New Bug description: System: Ubuntu 17.10 beta DNS server hosts an internal and an external domain (the internal is used for internal purposes). Name resolution works for a while. Every now and then, the name resolution stops working. This issue was reported in 17.04 but no suggestion for resolv has worked. In 17.10 the symptoms are the same, the duration till it happens are longer (about 1.5 days). restarting systemd-resolved solves the issue temporarily. However, this should not be required at all. Happens on a fresh install Setup: DNS serves rsb.at and rsb.intern Server www.rsb.at can be reached even when internal resolution fails. Seems that the internal DNS server (the first in the line) is not queried first. If so, an rsb.intern address will not be found. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu10 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 22 11:05:57 2017 InstallationDate: Installed on 2017-09-05 (16 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) Lsusb: Bus 002 Device 002: ID 05ac:8406 Apple, Inc. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05ac:0273 Apple, Inc. Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-11-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0167.B33.1706181928 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B33.1706181928:bd06/18/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. mtime.conffile..etc.systemd.resolved.conf: 2017-09-06T23:14:52.682864 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1718890/+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 1718890] Re: name resolution stops working
Just found this article https://github.com/systemd/systemd/issues/5755 Following the argument, systemd-resolved resolves DNS names on the assumption that all configured DNS servers are equal. diego-treitos and others argue that in small/medium sized companies, DNS configuration will have an external DNS server configured and conveyed via DHCP. This is the case here as well. This has not posed a problem before systemd-resolved was adopted. But when a resolver insists on treating the fallback equally and keeping the connection till the next fallback, internal DNS resolution is not possible any more. It breaks known and established configurations. I have to accept that RFCs actually lend to the interpretation of poettering. In this case (as he is reluctant to adapt his softwares behaviour to previously known standards) there need to be a quick way to eliminate systemd-resolver from the system. I for one need the old behaviour with a primary DNS (internal, it resolved private addresses as well) and a secondary DNS (external, which only resolved external / official addresses) as a fallback. ** Bug watch added: github.com/systemd/systemd/issues #5755 https://github.com/systemd/systemd/issues/5755 -- 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/1718890 Title: name resolution stops working Status in systemd package in Ubuntu: New Bug description: System: Ubuntu 17.10 beta DNS server hosts an internal and an external domain (the internal is used for internal purposes). Name resolution works for a while. Every now and then, the name resolution stops working. This issue was reported in 17.04 but no suggestion for resolv has worked. In 17.10 the symptoms are the same, the duration till it happens are longer (about 1.5 days). restarting systemd-resolved solves the issue temporarily. However, this should not be required at all. Happens on a fresh install Setup: DNS serves rsb.at and rsb.intern Server www.rsb.at can be reached even when internal resolution fails. Seems that the internal DNS server (the first in the line) is not queried first. If so, an rsb.intern address will not be found. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu10 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 22 11:05:57 2017 InstallationDate: Installed on 2017-09-05 (16 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) Lsusb: Bus 002 Device 002: ID 05ac:8406 Apple, Inc. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05ac:0273 Apple, Inc. Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-11-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0167.B33.1706181928 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B33.1706181928:bd06/18/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. mtime.conffile..etc.systemd.resolved.conf: 2017-09-06T23:14:52.682864 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1718890/+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 1620636] Re: Fails to pair with Bose QC35 headphones
The head phone pairs, the microphone does not. Further, the sound still is very low and jittery. Useless to listen to music over this device under these conditions. -- 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/1620636 Title: Fails to pair with Bose QC35 headphones Status in Canonical System Image: In Progress Status in bluez package in Ubuntu: In Progress Bug description: I am unable to pair the Bose QC35 BT headphones with Ubuntu, either Ubuntu desktop running 16.04 LTS with bluez 5.37 (also tried bluez 5.41 from installed from yakkety archive), nor using Ubuntu Touch rc- proposed build for Turbo #174. I'm trying to pair through the normal bluetooth control panel brought up through the bluetooth indicator. I've attached some logs that show it failing to pair. If I can provide anymore useful information about the headphones, please let me know. Syslog with bluetoothd debugging enabled: http://pastebin.ubuntu.com/23141394/ btmon output: http://pastebin.ubuntu.com/23141446/ bluetoothctl output: http://pastebin.ubuntu.com/23141510/ With Linux kernel 4.8.0 and bluez 4.52: --- bluetoothctl: http://pastebin.ubuntu.com/23256457/ btmon: http://pastebin.ubuntu.com/23256471/ To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1620636/+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 1718890] [NEW] name resolution stops working
Public bug reported: System: Ubuntu 17.10 beta DNS server hosts an internal and an external domain (the internal is used for internal purposes). Name resolution works for a while. Every now and then, the name resolution stops working. This issue was reported in 17.04 but no suggestion for resolv has worked. In 17.10 the symptoms are the same, the duration till it happens are longer (about 1.5 days). restarting systemd-resolved solves the issue temporarily. However, this should not be required at all. Happens on a fresh install Setup: DNS serves rsb.at and rsb.intern Server www.rsb.at can be reached even when internal resolution fails. Seems that the internal DNS server (the first in the line) is not queried first. If so, an rsb.intern address will not be found. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu10 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 22 11:05:57 2017 InstallationDate: Installed on 2017-09-05 (16 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) Lsusb: Bus 002 Device 002: ID 05ac:8406 Apple, Inc. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05ac:0273 Apple, Inc. Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-11-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0167.B33.1706181928 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B33.1706181928:bd06/18/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. mtime.conffile..etc.systemd.resolved.conf: 2017-09-06T23:14:52.682864 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session -- 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/1718890 Title: name resolution stops working Status in systemd package in Ubuntu: New Bug description: System: Ubuntu 17.10 beta DNS server hosts an internal and an external domain (the internal is used for internal purposes). Name resolution works for a while. Every now and then, the name resolution stops working. This issue was reported in 17.04 but no suggestion for resolv has worked. In 17.10 the symptoms are the same, the duration till it happens are longer (about 1.5 days). restarting systemd-resolved solves the issue temporarily. However, this should not be required at all. Happens on a fresh install Setup: DNS serves rsb.at and rsb.intern Server www.rsb.at can be reached even when internal resolution fails. Seems that the internal DNS server (the first in the line) is not queried first. If so, an rsb.intern address will not be found. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu10 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 22 11:05:57 2017 InstallationDate: Installed on 2017-09-05 (16 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) Lsusb: Bus 002 Device 002: ID 05ac:8406 Apple, Inc. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05ac:0273 Apple, Inc. Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-11-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0167.B33.1706181928 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B33.1706181928:bd06/18/2017:svnAppleInc.:pnMa
[Touch-packages] [Bug 1716601] Re: video decoders don't work correctly
Seems so. Sorry, didn't find it when filing the issue. Should be merged with 1716250 as the descriptions there are accurate. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1716601 Title: video decoders don't work correctly Status in gstreamer1.0 package in Ubuntu: New Bug description: Playing videos sometimes just displays black images (audio coming in clearly) or with one colour channel missing (magenta tint mostly). Tried with several videos, there seems to be no pattern (avi as well as mpeg, different encoders). A significant amount of first calls (after waiting a period of minutes) brings up black (no video). Ubuntu 17.10 plain installation (with additional media support though) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libgstreamer1.0-0 1.12.2-1 ProcVersionSignature: Ubuntu 4.13.0-10.11-generic 4.13.1 Uname: Linux 4.13.0-10-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 12 10:03:44 2017 InstallationDate: Installed on 2017-09-05 (6 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1716601/+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 1716601] Re: video decoders don't work correctly
This issue occurs as well if cheese is started. (the camera had to be installed first via https://github.com/patjak/bcwc_pcie/wiki/Get-Started - refer to bug #1715717). The image is tinted magenta (the green channel is not captured). However taking a still works fine (all channels are captured giving correct imaging). Thus I presume the issue has something to do with video en- and decoding. (I tried the camera under macOS and it works fine). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1716601 Title: video decoders don't work correctly Status in gstreamer1.0 package in Ubuntu: New Bug description: Playing videos sometimes just displays black images (audio coming in clearly) or with one colour channel missing (magenta tint mostly). Tried with several videos, there seems to be no pattern (avi as well as mpeg, different encoders). A significant amount of first calls (after waiting a period of minutes) brings up black (no video). Ubuntu 17.10 plain installation (with additional media support though) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libgstreamer1.0-0 1.12.2-1 ProcVersionSignature: Ubuntu 4.13.0-10.11-generic 4.13.1 Uname: Linux 4.13.0-10-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 12 10:03:44 2017 InstallationDate: Installed on 2017-09-05 (6 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1716601/+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 1716601] [NEW] video decoders don't work correctly
Public bug reported: Playing videos sometimes just displays black images (audio coming in clearly) or with one colour channel missing (magenta tint mostly). Tried with several videos, there seems to be no pattern (avi as well as mpeg, different encoders). A significant amount of first calls (after waiting a period of minutes) brings up black (no video). Ubuntu 17.10 plain installation (with additional media support though) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libgstreamer1.0-0 1.12.2-1 ProcVersionSignature: Ubuntu 4.13.0-10.11-generic 4.13.1 Uname: Linux 4.13.0-10-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 12 10:03:44 2017 InstallationDate: Installed on 2017-09-05 (6 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' ** Affects: gstreamer1.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1716601 Title: video decoders don't work correctly Status in gstreamer1.0 package in Ubuntu: New Bug description: Playing videos sometimes just displays black images (audio coming in clearly) or with one colour channel missing (magenta tint mostly). Tried with several videos, there seems to be no pattern (avi as well as mpeg, different encoders). A significant amount of first calls (after waiting a period of minutes) brings up black (no video). Ubuntu 17.10 plain installation (with additional media support though) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libgstreamer1.0-0 1.12.2-1 ProcVersionSignature: Ubuntu 4.13.0-10.11-generic 4.13.1 Uname: Linux 4.13.0-10-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 12 10:03:44 2017 InstallationDate: Installed on 2017-09-05 (6 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1716601/+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 1716127] [NEW] Audio streaming over bluetooth is not possible
Public bug reported: Streaming of audio files over bluetooth is not possible in Ubuntu 17.10. Connecting a headphone requires several attempts. Then the sound settings have to be selected manually Even then, the sound offered is mono I tested with a Bose QC35. There is a sound profile that requires manual selection and offers stereo speakers. However, while testing left speaker gives reasonable results, testing the right speaker only produces cracking noise. Playback of music is virtually impossible (the stream is repeatedly interupted by voice anouncements of incoming calls ??? and reconnection attemts) To eliminate hardware issues I tested under macOS and the sound quality is excellent (even during working in a spread sheet and a word processor in parallel). => issues caused by the software stack ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: bluez 5.46-0ubuntu2 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 9 15:12:02 2017 InstallationDate: Installed on 2017-09-05 (4 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 002: ID 05ac:8406 Apple, Inc. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05ac:0273 Apple, Inc. Bus 001 Device 003: ID 05ac:8290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.12.0-13-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0167.B33.1706181928 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B33.1706181928:bd06/18/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. hciconfig: hci0: Type: Primary Bus: USB BD Address: 4C:32:75:9F:91:1E ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN RX bytes:1558111 acl:54896 sco:0 events:1375 errors:0 TX bytes:1129512 acl:1895 sco:5 commands:247 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- 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/1716127 Title: Audio streaming over bluetooth is not possible Status in bluez package in Ubuntu: New Bug description: Streaming of audio files over bluetooth is not possible in Ubuntu 17.10. Connecting a headphone requires several attempts. Then the sound settings have to be selected manually Even then, the sound offered is mono I tested with a Bose QC35. There is a sound profile that requires manual selection and offers stereo speakers. However, while testing left speaker gives reasonable results, testing the right speaker only produces cracking noise. Playback of music is virtually impossible (the stream is repeatedly interupted by voice anouncements of incoming calls ??? and reconnection attemts) To eliminate hardware issues I tested under macOS and the sound quality is excellent (even during working in a spread sheet and a word processor in parallel). => issues caused by the software stack ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: bluez 5.46-0ubuntu2 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 9 15:12:02 2017 InstallationDate: Installed on 2017-09-05 (4 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 002: ID 05ac:8406 Apple, Inc. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05ac:0273 Apple, Inc. Bus 001 Device 003: ID 05ac:8290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.12.0-13-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2017 dmi.bios.
[Touch-packages] [Bug 1716022] Re: Mouse cursor jaggy movements
Played around with magnification. Pressing Super-Alt-8 somehow creates this situation. Increasing the magnification to 200%, pressing Super-Alt-8 and reverting to 100% remedies the effect. Thus: An issue that I cannot explain. ** Changed in: xorg (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1716022 Title: Mouse cursor jaggy movements Status in xorg package in Ubuntu: Invalid Bug description: Ever since the update of libmpfr4:amd64 (3.1.6~rc1-1, 3.1.6-1) on 2017-09-08 12:28:20 the mouse cursor demonstrates a jumpy / jaggy behaviour. Compared to a similar machine or the live cd the mouse seems to jump around. Testing with a handwritten text in Gimp demonstrated the difference. This might not be an Xorg error but rather a Wayland | Mutter | libmpfr issue (I really can't tell but had to make a start) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu2 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 8 19:05:34 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu DkmsStatus: virtualbox, 5.1.26, 4.12.0-12-generic, x86_64: installed virtualbox, 5.1.26, 4.12.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Graphics 6100 [8086:162b] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Iris Graphics 6100 [106b:013f] InstallationDate: Installed on 2017-09-05 (3 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) MachineType: Apple Inc. MacBookPro12,1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.12.0-13-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0167.B33.1706181928 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B33.1706181928:bd06/18/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.82-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.0-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1716022/+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 1716022] [NEW] Mouse cursor jaggy movements
Public bug reported: Ever since the update of libmpfr4:amd64 (3.1.6~rc1-1, 3.1.6-1) on 2017-09-08 12:28:20 the mouse cursor demonstrates a jumpy / jaggy behaviour. Compared to a similar machine or the live cd the mouse seems to jump around. Testing with a handwritten text in Gimp demonstrated the difference. This might not be an Xorg error but rather a Wayland | Mutter | libmpfr issue (I really can't tell but had to make a start) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu2 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 8 19:05:34 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu DkmsStatus: virtualbox, 5.1.26, 4.12.0-12-generic, x86_64: installed virtualbox, 5.1.26, 4.12.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Graphics 6100 [8086:162b] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Iris Graphics 6100 [106b:013f] InstallationDate: Installed on 2017-09-05 (3 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) MachineType: Apple Inc. MacBookPro12,1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.12.0-13-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0167.B33.1706181928 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B33.1706181928:bd06/18/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.82-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.0-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful performance regression single-occurrence ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1716022 Title: Mouse cursor jaggy movements Status in xorg package in Ubuntu: New Bug description: Ever since the update of libmpfr4:amd64 (3.1.6~rc1-1, 3.1.6-1) on 2017-09-08 12:28:20 the mouse cursor demonstrates a jumpy / jaggy behaviour. Compared to a similar machine or the live cd the mouse seems to jump around. Testing with a handwritten text in Gimp demonstrated the difference. This might not be an Xorg error but rather a Wayland | Mutter | libmpfr issue (I really can't tell but had to make a start) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu2 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 8 19:05:34 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu DkmsStatus: virtualbox, 5.1.26, 4.12.0-12-generic, x86_64: installed virtualbox, 5.1.26, 4.12.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Graphics 6100 [8086:162b] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Iris Graphics 6100 [106b:013f] InstallationDate: Installed on 2017-09-05 (3 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) MachineType: Apple Inc. MacBookPro12,1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.12.0-13-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2017 dmi.bios.vendor: Apple Inc. dmi.bio
[Touch-packages] [Bug 1710978] Re: bluetooth stack looses connection to bluetooth devices when tlp is installed
I think, this should be a tlp related issue (didn't know at the time of filing it). -- 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/1710978 Title: bluetooth stack looses connection to bluetooth devices when tlp is installed Status in bluez package in Ubuntu: New Status in tlp package in Ubuntu: New Bug description: In Ubuntu Budgie bluetooth connection is lost in regular intervals (5mins). Thus my mouse stops working, my headset stops playing music. Reconnecting my mouse takes ages requiring a restart of bluez and reconnecting the mouse. This issue became worse ever since installing budgie (17.04) in May. (during writing this, the mouse stopped working again) ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: bluez 5.43-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Tue Aug 15 23:02:08 2017 InstallationDate: Installed on 2017-05-25 (81 days ago) InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Apple Inc. MacBookPro10,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic.efi.signed root=UUID=873566f9-4c01-4dae-8ca9-99c95dfbe269 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP101.88Z.00EE.B03.1212211437 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-C3EC7CD22292981F dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro10,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-C3EC7CD22292981F dmi.modalias: dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B03.1212211437:bd12/21/2012:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F: dmi.product.name: MacBookPro10,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 14:10:9F:D2:25:F8 ACL MTU: 1021:6 SCO MTU: 64:1 UP RUNNING PSCAN RX bytes:21297526 acl:766364 sco:0 events:1617 errors:0 TX bytes:14741 acl:474 sco:0 commands:583 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1710978/+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 1710978] Re: bluetooth stack looses connection to bluetooth devices
Uninstalling tlp (+tlp-rdw, budgie-desktop-environment, ubuntu-budgie-desktop) eliminates the issue completely Also #1711382 does not occure any more (however, I see no relation between the two) -- 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/1710978 Title: bluetooth stack looses connection to bluetooth devices Status in bluez package in Ubuntu: New Bug description: In Ubuntu Budgie bluetooth connection is lost in regular intervals (5mins). Thus my mouse stops working, my headset stops playing music. Reconnecting my mouse takes ages requiring a restart of bluez and reconnecting the mouse. This issue became worse ever since installing budgie (17.04) in May. (during writing this, the mouse stopped working again) ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: bluez 5.43-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Tue Aug 15 23:02:08 2017 InstallationDate: Installed on 2017-05-25 (81 days ago) InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Apple Inc. MacBookPro10,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic.efi.signed root=UUID=873566f9-4c01-4dae-8ca9-99c95dfbe269 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP101.88Z.00EE.B03.1212211437 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-C3EC7CD22292981F dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro10,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-C3EC7CD22292981F dmi.modalias: dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B03.1212211437:bd12/21/2012:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F: dmi.product.name: MacBookPro10,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 14:10:9F:D2:25:F8 ACL MTU: 1021:6 SCO MTU: 64:1 UP RUNNING PSCAN RX bytes:21297526 acl:766364 sco:0 events:1617 errors:0 TX bytes:14741 acl:474 sco:0 commands:583 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1710978/+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 1710978] Re: bluetooth stack looses connection to bluetooth devices
extended measures demonstrate a loss of connection every two minutes on average. -- 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/1710978 Title: bluetooth stack looses connection to bluetooth devices Status in bluez package in Ubuntu: New Bug description: In Ubuntu Budgie bluetooth connection is lost in regular intervals (5mins). Thus my mouse stops working, my headset stops playing music. Reconnecting my mouse takes ages requiring a restart of bluez and reconnecting the mouse. This issue became worse ever since installing budgie (17.04) in May. (during writing this, the mouse stopped working again) ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: bluez 5.43-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Tue Aug 15 23:02:08 2017 InstallationDate: Installed on 2017-05-25 (81 days ago) InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Apple Inc. MacBookPro10,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic.efi.signed root=UUID=873566f9-4c01-4dae-8ca9-99c95dfbe269 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP101.88Z.00EE.B03.1212211437 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-C3EC7CD22292981F dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro10,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-C3EC7CD22292981F dmi.modalias: dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B03.1212211437:bd12/21/2012:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F: dmi.product.name: MacBookPro10,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 14:10:9F:D2:25:F8 ACL MTU: 1021:6 SCO MTU: 64:1 UP RUNNING PSCAN RX bytes:21297526 acl:766364 sco:0 events:1617 errors:0 TX bytes:14741 acl:474 sco:0 commands:583 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1710978/+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 1710978] Re: bluetooth stack looses connection to bluetooth devices
could be. I already had issues with TLP (related to suspend to RAM). Must have been introduced with the latest kernel update though (as the former issue has been resolved). -- 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/1710978 Title: bluetooth stack looses connection to bluetooth devices Status in bluez package in Ubuntu: New Bug description: In Ubuntu Budgie bluetooth connection is lost in regular intervals (5mins). Thus my mouse stops working, my headset stops playing music. Reconnecting my mouse takes ages requiring a restart of bluez and reconnecting the mouse. This issue became worse ever since installing budgie (17.04) in May. (during writing this, the mouse stopped working again) ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: bluez 5.43-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Tue Aug 15 23:02:08 2017 InstallationDate: Installed on 2017-05-25 (81 days ago) InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Apple Inc. MacBookPro10,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic.efi.signed root=UUID=873566f9-4c01-4dae-8ca9-99c95dfbe269 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP101.88Z.00EE.B03.1212211437 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-C3EC7CD22292981F dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro10,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-C3EC7CD22292981F dmi.modalias: dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B03.1212211437:bd12/21/2012:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F: dmi.product.name: MacBookPro10,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 14:10:9F:D2:25:F8 ACL MTU: 1021:6 SCO MTU: 64:1 UP RUNNING PSCAN RX bytes:21297526 acl:766364 sco:0 events:1617 errors:0 TX bytes:14741 acl:474 sco:0 commands:583 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1710978/+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 1710978] [NEW] bluetooth stack looses connection to bluetooth devices
Public bug reported: In Ubuntu Budgie bluetooth connection is lost in regular intervals (5mins). Thus my mouse stops working, my headset stops playing music. Reconnecting my mouse takes ages requiring a restart of bluez and reconnecting the mouse. This issue became worse ever since installing budgie (17.04) in May. (during writing this, the mouse stopped working again) ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: bluez 5.43-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Tue Aug 15 23:02:08 2017 InstallationDate: Installed on 2017-05-25 (81 days ago) InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Apple Inc. MacBookPro10,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic.efi.signed root=UUID=873566f9-4c01-4dae-8ca9-99c95dfbe269 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP101.88Z.00EE.B03.1212211437 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-C3EC7CD22292981F dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro10,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-C3EC7CD22292981F dmi.modalias: dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B03.1212211437:bd12/21/2012:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F: dmi.product.name: MacBookPro10,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. hciconfig: hci0: Type: Primary Bus: USB BD Address: 14:10:9F:D2:25:F8 ACL MTU: 1021:6 SCO MTU: 64:1 UP RUNNING PSCAN RX bytes:21297526 acl:766364 sco:0 events:1617 errors:0 TX bytes:14741 acl:474 sco:0 commands:583 errors:0 ** Affects: bluez (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 bluez in Ubuntu. https://bugs.launchpad.net/bugs/1710978 Title: bluetooth stack looses connection to bluetooth devices Status in bluez package in Ubuntu: New Bug description: In Ubuntu Budgie bluetooth connection is lost in regular intervals (5mins). Thus my mouse stops working, my headset stops playing music. Reconnecting my mouse takes ages requiring a restart of bluez and reconnecting the mouse. This issue became worse ever since installing budgie (17.04) in May. (during writing this, the mouse stopped working again) ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: bluez 5.43-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Tue Aug 15 23:02:08 2017 InstallationDate: Installed on 2017-05-25 (81 days ago) InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Apple Inc. MacBookPro10,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic.efi.signed root=UUID=873566f9-4c01-4dae-8ca9-99c95dfbe269 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP101.88Z.00EE.B03.1212211437 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-C3EC7CD22292981F dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro10,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-C3EC7CD22292981F dmi.modalias: dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B03.1212211437:bd12/21/2012:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F: dmi.product.name: MacBookPro10,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 14:10:9F:D2:25:F8 ACL MTU: 1021:6 SCO MTU: 64:1 UP RUNNING PSCAN RX bytes:21297526 acl:766364 sco:0 events:1617 errors:0 TX bytes:14741 acl:474 sco:0 commands:583 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1710978/+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 1707392] [NEW] nm-applet not shown
Public bug reported: after an upgrade of shim-signed the nm-applet does not show in the budgie indication bar. Network connections cannot be established from the GUI anymore ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: network-manager 1.4.4-1ubuntu3.1 ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Sat Jul 29 14:17:45 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-05-25 (64 days ago) InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 10.1.0.254 dev wlp4s0 proto static metric 600 10.0.0.0/8 dev wlp4s0 proto kernel scope link src 10.1.0.162 metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.73.0/24 dev vmnet1 proto kernel scope link src 192.168.73.1 192.168.197.0/24 dev vmnet8 proto kernel scope link src 192.168.197.1 NetworkManager.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlp4s0 wifi connected /org/freedesktop/NetworkManager/Devices/1 rsb 2e593024-0de5-4795-b3bf-6918a96a15a1 /org/freedesktop/NetworkManager/ActiveConnection/0 vmnet1 ethernet unmanaged /org/freedesktop/NetworkManager/Devices/2 -- ---- vmnet8 ethernet unmanaged /org/freedesktop/NetworkManager/Devices/3 -- ---- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.4.4connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (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 network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1707392 Title: nm-applet not shown Status in network-manager package in Ubuntu: New Bug description: after an upgrade of shim-signed the nm-applet does not show in the budgie indication bar. Network connections cannot be established from the GUI anymore ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: network-manager 1.4.4-1ubuntu3.1 ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Sat Jul 29 14:17:45 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-05-25 (64 days ago) InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 10.1.0.254 dev wlp4s0 proto static metric 600 10.0.0.0/8 dev wlp4s0 proto kernel scope link src 10.1.0.162 metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.73.0/24 dev vmnet1 proto kernel scope link src 192.168.73.1 192.168.197.0/24 dev vmnet8 proto kernel scope link src 192.168.197.1 NetworkManager.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlp4s0 wifi connected /org/freedesktop/NetworkManager/Devices/1 rsb 2e593024-0de5-4795-b3bf-6918a96a15a1 /org/freedesktop/NetworkManager/ActiveConnection/0 vmnet1 ethernet unmanaged /org/freedesktop/NetworkManager/Devices/2 -- ---- vmnet8 ethernet unmanaged /org/freedesktop/NetworkManager/Devices/3 -- ----
[Touch-packages] [Bug 1635907] Re: Can't connect to Wifi network after suspend and resume
It seems I have a similar issue. After resume a connection dialog appears where the (correct) password is given. Connecting is still not possible (the dialog reappears in a loop, no connection established). Cancelling and connecting from the menu works fine. This looks like a similar old issue where the reconnect logon dialog messed up the encryption. (just my impression). -- 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/1635907 Title: Can't connect to Wifi network after suspend and resume Status in network-manager package in Ubuntu: New Bug description: Beginning in Ubuntu 16.04 and getting worse after upgrading to 16.10, I can't connect to wifi networks after suspending and resuming my laptop. I have a Sony Vaio SVP112A1CL with wireless network controller Intel Corporation Wireless 7260 (rev 6b). Typically I have to restart NetworkManager to recover from the problem (sudo systemctl restart NetworkManager). This seemed to be a reliable way to recover in 16.04, but it doesn't always work in 16.10 and may require a reboot. In some related bug reports they requested we run `sudo iw dev wlan0 scan` which resulted initially in an error but after running it a few times returned successfully. I'll attach the output below. Even though it did return, the wifi network still was unable to reconnect. I'll try to grab the errors next time, but if I do it now, I'll lose connectivity. $ apt-cache policy network-manager network-manager: Installed: 1.2.4-0ubuntu1 Candidate: 1.2.4-0ubuntu1 Version table: *** 1.2.4-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status $ sudo iw dev wlan0 scan BSS d4:05:98:46:d9:40(on wlan0) -- associated TSF: 2690064842954 usec (31d, 03:14:24) freq: 2457 beacon interval: 100 TUs capability: ESS Privacy ShortPreamble ShortSlotTime APSD (0x0c31) signal: -68.00 dBm last seen: 3728 ms ago Information elements from Probe Response frame: SSID: stevens-2G Supported rates: 1.0* 2.0* 5.5* 11.0* 9.0 18.0 36.0 54.0 DS Parameter set: channel 10 ERP: Extended supported rates: 6.0 12.0 24.0 48.0 Country: US Environment: Indoor/Outdoor Channels [1 - 11] @ 36 dBm HT capabilities: Capabilities: 0x1ec HT20 SM Power Save disabled RX HT20 SGI RX HT40 SGI TX STBC RX STBC 1-stream Max AMSDU length: 3839 bytes No DSSS/CCK HT40 Maximum RX AMPDU length 65535 bytes (exponent: 0x003) Minimum RX AMPDU time spacing: 4 usec (0x05) HT RX MCS rate indexes supported: 0-23 HT TX MCS rate indexes are undefined HT operation: * primary channel: 10 * secondary channel offset: no secondary * STA channel width: 20 MHz * RIFS: 0 * HT protection: no * non-GF present: 1 * OBSS non-GF present: 0 * dual beacon: 0 * dual CTS protection: 0 * STBC beacon: 0 * L-SIG TXOP Prot: 0 * PCO active: 0 * PCO phase: 0 WPA: * Version: 1 * Group cipher: TKIP * Pairwise ciphers: TKIP CCMP * Authentication suites: PSK RSN: * Version: 1 * Group cipher: TKIP * Pairwise ciphers: TKIP CCMP * Authentication suites: PSK * Capabilities: 1-PTKSA-RC 1-GTKSA-RC (0x) WMM: * Parameter version 1 * u-APSD * BE: CW 15-1023, AIFSN 3 * BK: CW 15-1023, AIFSN 7 * VI: CW 7-15, AIFSN 2, TXOP 3008 usec * VO: CW 3-7, AIFSN 2, TXOP 1504 usec BSS Load: * station count: 5 * channel utilisation: 28/255 * available admission capacity: 31250 [*32us] Extended capabilities: HT Information Exchange Supported Country: US Environment: Indoor/Outdoor Channels [1 - 11] @ 16 dBm WPS: * Version: 1.0 * Wi-Fi Protected Setup State: 2 (Configured) * Response Type: 3 (AP) * UUID: bc329e00-1dd8-11b2-8601-d4059846d940 * Manufacturer: Celeno Communication, Inc. * Model: Celeno Wireless AP 2.4G * Model Number: CL1800 * Serial Number: 12345678
[Touch-packages] [Bug 1700756] [NEW] HDMI not working
Public bug reported: Ever since updating nvidia driver to nvidia-381 the external HDMI connectors stopped working. Neither the native HDMI port nor HDMI over Thunderbolt works. The driver recognizes the external monitor (existence and resolution) but does not provide a picture. Thunderbolt #1 never worked before but Thunderbolt #2 and the HDMI port worked in 16.10. The ports are fine (I can boot into MacOS and find all three combinations working). ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 381.22 Thu May 4 00:55:03 PDT 2017 GCC version: gcc version 6.3.0 20170406 (Ubuntu 6.3.0-12ubuntu2) ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: Budgie:GNOME Date: Tue Jun 27 14:18:06 2017 DistUpgraded: Fresh install DistroCodename: zesty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. 3rd Gen Core processor Graphics Controller [106b:00f7] NVIDIA Corporation GK107M [GeForce GT 650M Mac Edition] [10de:0fd5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. GK107M [GeForce GT 650M Mac Edition] [106b:00f2] InstallationDate: Installed on 2017-05-25 (32 days ago) InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412) LightdmLog: [+21747.08s] DEBUG: Seat seat0 changes active session to [+21750.55s] DEBUG: Seat seat0 changes active session to c2 [+21750.55s] DEBUG: Session c2 is already active MachineType: Apple Inc. MacBookPro10,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-24-generic.efi.signed root=UUID=873566f9-4c01-4dae-8ca9-99c95dfbe269 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP101.88Z.00EE.B03.1212211437 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-C3EC7CD22292981F dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro10,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-C3EC7CD22292981F dmi.modalias: dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B03.1212211437:bd12/21/2012:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F: dmi.product.name: MacBookPro10,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1 xserver.bootTime: Mon Jun 26 07:46:39 2017 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.3-1ubuntu1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubuntu zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1700756 Title: HDMI not working Status in xorg package in Ubuntu: New Bug description: Ever since updating nvidia driver to nvidia-381 the external HDMI connectors stopped working. Neither the native HDMI port nor HDMI over Thunderbolt works. The driver recognizes the external monitor (existence and resolution) but does not provide a picture. Thunderbolt #1 never worked before but Thunderbolt #2 and the HDMI port worked in 16.10. The ports are fine (I can boot into MacOS and find all three combinations working). ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver
[Touch-packages] [Bug 1693895] Re: ubuntu budgie suspend to ram fails on Macbook Pro Ret
With the latest kernel update Linux 4.10.0-24-generic the issue seems resolved. Installing tlp -> Suspend to RAM works (at least from what I see in the system log) -- 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/1693895 Title: ubuntu budgie suspend to ram fails on Macbook Pro Ret Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: A default installation of Ubuntu Budgie fails to suspend to RAM. Workaround: sudo apt-get install pm-utils => Suspend works ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: systemd 232-21ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Fri May 26 20:13:16 2017 InstallationDate: Installed on 2017-05-25 (0 days ago) InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Apple Inc. MacBookPro10,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic.efi.signed root=UUID=873566f9-4c01-4dae-8ca9-99c95dfbe269 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP101.88Z.00EE.B03.1212211437 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-C3EC7CD22292981F dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro10,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-C3EC7CD22292981F dmi.modalias: dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B03.1212211437:bd12/21/2012:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F: dmi.product.name: MacBookPro10,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1693895/+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 1693895] Re: ubuntu budgie suspend to ram fails on Macbook Pro Ret
Uninstalled tlp -> Sleep works fine Thanks for the hint. -- 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/1693895 Title: ubuntu budgie suspend to ram fails on Macbook Pro Ret Status in systemd package in Ubuntu: New Bug description: A default installation of Ubuntu Budgie fails to suspend to RAM. Workaround: sudo apt-get install pm-utils => Suspend works ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: systemd 232-21ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Fri May 26 20:13:16 2017 InstallationDate: Installed on 2017-05-25 (0 days ago) InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Apple Inc. MacBookPro10,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic.efi.signed root=UUID=873566f9-4c01-4dae-8ca9-99c95dfbe269 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP101.88Z.00EE.B03.1212211437 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-C3EC7CD22292981F dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro10,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-C3EC7CD22292981F dmi.modalias: dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B03.1212211437:bd12/21/2012:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F: dmi.product.name: MacBookPro10,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1693895/+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 1693895] Re: ubuntu budgie suspend to ram fails on Macbook Pro Ret
This seems the normal case --- May 28 12:37:49 mbpr15 systemd[1]: Started Suspend. May 28 12:37:49 mbpr15 systemd[1]: sleep.target: Unit not needed anymore. Stoppi ng. May 28 12:37:49 mbpr15 systemd[1]: Stopped target Sleep. May 28 12:37:49 mbpr15 systemd[1]: tlp-sleep.service: Unit not needed anymore. S topping. May 28 12:37:49 mbpr15 systemd[1]: Stopping TLP suspend/resume... May 28 12:37:49 mbpr15 systemd[1]: Reached target Suspend. May 28 12:37:49 mbpr15 systemd[1]: suspend.target: Unit is bound to inactive uni t systemd-suspend.service. Stopping, too. May 28 12:37:49 mbpr15 systemd[1]: Stopped target Suspend. May 28 12:37:49 mbpr15 systemd[1]: Started Run anacron jobs at resume. --- -- 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/1693895 Title: ubuntu budgie suspend to ram fails on Macbook Pro Ret Status in systemd package in Ubuntu: New Bug description: A default installation of Ubuntu Budgie fails to suspend to RAM. Workaround: sudo apt-get install pm-utils => Suspend works ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: systemd 232-21ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Fri May 26 20:13:16 2017 InstallationDate: Installed on 2017-05-25 (0 days ago) InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Apple Inc. MacBookPro10,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic.efi.signed root=UUID=873566f9-4c01-4dae-8ca9-99c95dfbe269 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP101.88Z.00EE.B03.1212211437 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-C3EC7CD22292981F dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro10,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-C3EC7CD22292981F dmi.modalias: dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B03.1212211437:bd12/21/2012:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F: dmi.product.name: MacBookPro10,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1693895/+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 1693895] Re: ubuntu budgie suspend to ram fails on Macbook Pro Ret
Was a bit euphoric about the workaround. Suspend does not work even with pm-utils installed. The machine blanks the display but other than that works continuously. With the lid closed, the laptop might overheat. So this issue is endangering the hardware. Current workaround: Don't suspend, turn off. -- 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/1693895 Title: ubuntu budgie suspend to ram fails on Macbook Pro Ret Status in systemd package in Ubuntu: New Bug description: A default installation of Ubuntu Budgie fails to suspend to RAM. Workaround: sudo apt-get install pm-utils => Suspend works ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: systemd 232-21ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Fri May 26 20:13:16 2017 InstallationDate: Installed on 2017-05-25 (0 days ago) InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Apple Inc. MacBookPro10,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic.efi.signed root=UUID=873566f9-4c01-4dae-8ca9-99c95dfbe269 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP101.88Z.00EE.B03.1212211437 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-C3EC7CD22292981F dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro10,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-C3EC7CD22292981F dmi.modalias: dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B03.1212211437:bd12/21/2012:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F: dmi.product.name: MacBookPro10,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1693895/+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 1694006] [NEW] Tracker error slows down system and breaks suspend to RAM
Public bug reported: By default Budgie installs tracker. $ tracker status (tracker status:11680): Tracker-WARNING **: tracker-backend.vala:211: Falling back to bus backend, the direct backend failed to initialize: unable to open database file Could not get basic status for Tracker, GDBus.Error:org.freedesktop.Tracker1.SparqlError.Internal: no such table: nfo:FileDataObject in syslog: May 27 13:02:32 mbpr15 tracker-extract[11366]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 27 13:02:32 mbpr15 tracker-extract[11366]: char* poppler_page_get_text(PopplerPage*): assertion 'POPPLER_IS_PAGE (page)' failed May 27 13:02:32 mbpr15 tracker-extract[11366]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 27 13:02:32 mbpr15 tracker-extract[11366]: char* poppler_page_get_text(PopplerPage*): assertion 'POPPLER_IS_PAGE (page)' failed May 27 13:02:32 mbpr15 tracker-extract[11366]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 27 13:02:32 mbpr15 tracker-extract[11366]: char* poppler_page_get_text(PopplerPage*): assertion 'POPPLER_IS_PAGE (page)' failed May 27 13:02:32 mbpr15 tracker-extract[11366]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 27 13:02:32 mbpr15 tracker-extract[11366]: char* poppler_page_get_text(PopplerPage*): assertion 'POPPLER_IS_PAGE (page)' failed May 27 13:02:32 mbpr15 tracker-extract[11366]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 27 13:02:32 mbpr15 tracker-extract[11366]: char* poppler_page_get_text(PopplerPage*): assertion 'POPPLER_IS_PAGE (page)' failed May 27 13:02:32 mbpr15 tracker-extract[11366]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 27 13:02:32 mbpr15 tracker-extract[11366]: char* poppler_page_get_text(PopplerPage*): assertion 'POPPLER_IS_PAGE (page)' failed May 27 13:02:32 mbpr15 tracker-extract[11366]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 27 13:02:32 mbpr15 tracker-extract[11366]: char* poppler_page_get_text(PopplerPage*): assertion 'POPPLER_IS_PAGE (page)' failed May 27 13:02:32 mbpr15 tracker-extract[11366]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 27 13:02:32 mbpr15 tracker-extract[11366]: char* poppler_page_get_text(PopplerPage*): assertion 'POPPLER_IS_PAGE (page)' failed May 27 13:02:32 mbpr15 tracker-extract[11366]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 27 13:02:32 mbpr15 tracker-extract[11366]: char* poppler_page_get_text(PopplerPage*): assertion 'POPPLER_IS_PAGE (page)' failed May 27 13:02:32 mbpr15 tracker-extract[11366]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 27 13:02:32 mbpr15 tracker-extract[11366]: char* poppler_page_get_text(PopplerPage*): assertion 'POPPLER_IS_PAGE (page)' failed May 27 13:06:23 mbpr15 tracker-extract[11638]: Could not insert metadata for item "file:///home/wolf/Documents/books/it-vertrage-kurz-und-praktisch.pdf": 42.33: invalid UTF-8 character May 27 13:06:23 mbpr15 tracker-extract[11638]: If the error above is recurrent for the same item/ID, consider running "tracker-extract" in the terminal with the TRACKER_VERBOSITY=3 environment variable, and filing a bug with the additional information This slows down the system tremendously. As a side effect, the system can't go into suspend to RAM mode (wakes up every second) ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: tracker 1.12.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Sat May 27 13:04:43 2017 InstallationDate: Installed on 2017-05-25 (1 days ago) InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: tracker UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: tracker (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 tracker in Ubuntu. https://bugs.launchpad.net/bugs/1694006 Title: Tracker error slows down system and breaks suspend to RAM Status in tracker package in Ubuntu: New Bug description: By default Budgie installs tracker. $ tracker status (tracker status:11680): Tracker-WARNING **: tracker-backend.vala:211: Falling back to bus backend, the direct backend failed to initialize: unable to open database file Could not get basic status for Tracker, GDBus.Error:org.freedesktop.Tracker1.SparqlError.Internal: no such table: nfo:FileDataObject in syslog: May 27 13:02:32 mbpr15 tracker-extract[11366]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 27 13:02:32 mbpr15 tracker-extract[11366]: char* poppler_page_get_text(PopplerPage*): assertion 'POPPLER_IS_PAGE (page)' failed May 27 13:02:32 mbpr15
[Touch-packages] [Bug 1694006] Re: Tracker error slows down system and breaks suspend to RAM
Some more detail: sudo tracker daemon --get-log-verbosity Components: Store: errors Extract : errors Writeback: errors Miners (Only those with config listed): Files: errors (tracker daemon:12598): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed (tracker daemon:12598): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed (tracker daemon:12598): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed (tracker daemon:12598): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed (tracker daemon:12598): Tracker-WARNING **: (tracker- daemon.c:1708):daemon_run: code should not be reached -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1694006 Title: Tracker error slows down system and breaks suspend to RAM Status in tracker package in Ubuntu: New Bug description: By default Budgie installs tracker. $ tracker status (tracker status:11680): Tracker-WARNING **: tracker-backend.vala:211: Falling back to bus backend, the direct backend failed to initialize: unable to open database file Could not get basic status for Tracker, GDBus.Error:org.freedesktop.Tracker1.SparqlError.Internal: no such table: nfo:FileDataObject in syslog: May 27 13:02:32 mbpr15 tracker-extract[11366]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 27 13:02:32 mbpr15 tracker-extract[11366]: char* poppler_page_get_text(PopplerPage*): assertion 'POPPLER_IS_PAGE (page)' failed May 27 13:02:32 mbpr15 tracker-extract[11366]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 27 13:02:32 mbpr15 tracker-extract[11366]: char* poppler_page_get_text(PopplerPage*): assertion 'POPPLER_IS_PAGE (page)' failed May 27 13:02:32 mbpr15 tracker-extract[11366]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 27 13:02:32 mbpr15 tracker-extract[11366]: char* poppler_page_get_text(PopplerPage*): assertion 'POPPLER_IS_PAGE (page)' failed May 27 13:02:32 mbpr15 tracker-extract[11366]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 27 13:02:32 mbpr15 tracker-extract[11366]: char* poppler_page_get_text(PopplerPage*): assertion 'POPPLER_IS_PAGE (page)' failed May 27 13:02:32 mbpr15 tracker-extract[11366]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 27 13:02:32 mbpr15 tracker-extract[11366]: char* poppler_page_get_text(PopplerPage*): assertion 'POPPLER_IS_PAGE (page)' failed May 27 13:02:32 mbpr15 tracker-extract[11366]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 27 13:02:32 mbpr15 tracker-extract[11366]: char* poppler_page_get_text(PopplerPage*): assertion 'POPPLER_IS_PAGE (page)' failed May 27 13:02:32 mbpr15 tracker-extract[11366]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 27 13:02:32 mbpr15 tracker-extract[11366]: char* poppler_page_get_text(PopplerPage*): assertion 'POPPLER_IS_PAGE (page)' failed May 27 13:02:32 mbpr15 tracker-extract[11366]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 27 13:02:32 mbpr15 tracker-extract[11366]: char* poppler_page_get_text(PopplerPage*): assertion 'POPPLER_IS_PAGE (page)' failed May 27 13:02:32 mbpr15 tracker-extract[11366]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 27 13:02:32 mbpr15 tracker-extract[11366]: char* poppler_page_get_text(PopplerPage*): assertion 'POPPLER_IS_PAGE (page)' failed May 27 13:02:32 mbpr15 tracker-extract[11366]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 27 13:02:32 mbpr15 tracker-extract[11366]: char* poppler_page_get_text(PopplerPage*): assertion 'POPPLER_IS_PAGE (page)' failed May 27 13:06:23 mbpr15 tracker-extract[11638]: Could not insert metadata for item "file:///home/wolf/Documents/books/it-vertrage-kurz-und-praktisch.pdf": 42.33: invalid UTF-8 character May 27 13:06:23 mbpr15 tracker-extract[11638]: If the error above is recurrent for the same item/ID, consider running "tracker-extract" in the terminal with the TRACKER_VERBOSITY=3 environment variable, and filing a bug with the additional information This slows down the system tremendously. As a side effect, the system can't go into suspend to RAM mode (wakes up every second) ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: tracker 1.12.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Sat May 27 13:04:43 2017 InstallationDate: Installed on 2017-05-25 (1 days ago) InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: tracker UpgradeStatus: No upgrad
[Touch-packages] [Bug 1693895] [NEW] ubuntu budgie suspend to ram fails on Macbook Pro Ret
Public bug reported: A default installation of Ubuntu Budgie fails to suspend to RAM. Workaround: sudo apt-get install pm-utils => Suspend works ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: systemd 232-21ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Fri May 26 20:13:16 2017 InstallationDate: Installed on 2017-05-25 (0 days ago) InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Apple Inc. MacBookPro10,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic.efi.signed root=UUID=873566f9-4c01-4dae-8ca9-99c95dfbe269 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP101.88Z.00EE.B03.1212211437 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-C3EC7CD22292981F dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro10,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-C3EC7CD22292981F dmi.modalias: dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B03.1212211437:bd12/21/2012:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F: dmi.product.name: MacBookPro10,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple 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/1693895 Title: ubuntu budgie suspend to ram fails on Macbook Pro Ret Status in systemd package in Ubuntu: New Bug description: A default installation of Ubuntu Budgie fails to suspend to RAM. Workaround: sudo apt-get install pm-utils => Suspend works ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: systemd 232-21ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Fri May 26 20:13:16 2017 InstallationDate: Installed on 2017-05-25 (0 days ago) InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Apple Inc. MacBookPro10,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic.efi.signed root=UUID=873566f9-4c01-4dae-8ca9-99c95dfbe269 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP101.88Z.00EE.B03.1212211437 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-C3EC7CD22292981F dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro10,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-C3EC7CD22292981F dmi.modalias: dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B03.1212211437:bd12/21/2012:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F: dmi.product.name: MacBookPro10,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1693895/+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 1675353] [NEW] Network manager does not resolve dns names
Public bug reported: NM seems completely broken in 16.10. I use NM, wifi and several VPN connections. Expected behaviour: 1. Connect NM to default wlan -> name resolution works without interuption and permanently 2. Connection to Cisco Anyconnect (via openconnect) -> DNS servers sent via DHCP should be added to the resolver list, name resolution should work in destination network, routes adjusted accordingly 3. Connect NM to foreign network (WPA2) -> DNS resolution sent via DHCP should be taken as default Current behaviour: NM starts dnsmasq by default (I commented the start line to fix issues). DNS resolution stops after some minutes. Removing dnsmasq fron NetworkManager.conf (as I did) allows for name resolution except for web browsers (neither Firefox nor Chromium use the systemd.resolver). 5 minutes of inactivity on the network suffice for the name resolution to stop working. Have to reestablish network connection (sudo resolveconf -u does not work). This violates expectation 1 NM connects via openconnect. In the settings I added additional DNS servers and domain searches. They are ignored by dnsmasq. Name resolution does not work. *Worksaround* -> enter IP-addresses in /etc/hosts. dig @server-ip returns the correct IP address for target services but Firefox and Chromium do not utilize these services. dnsmasq does not return the correct address. This violates expectation 2 Entering a foreign but known network, DNS resolution stops after a while (5 minutes inactivity suffice). Summarizing: a. DNS resolution using VPN connections does not work (I use openvpn, openconnect and pptp). b. dnsmasq does not resolve dns names correctly in wlan situations c. dnsmasq conflicts with systemd.resolver d. Firefox and Chromium ignore systemd.resolver e. removing dnsmasq from NetworkManager.conf releaves the issue a little (resolution drop-outs do not occur so frequently) Comparison to plain Debian demonstrated that Debian does not start dnsmasq. This led to the elimination of my dns=dnsmaq line in NetworkManager.conf Comparison to Raspian demonstrated that Raspian uses wpa_supplicant to control dns name resolution. I have not tried this setup in Ubuntu yet. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: network-manager 1.2.6-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17 Uname: Linux 4.8.0-41-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 Date: Thu Mar 23 11:28:21 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-01-27 (54 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) IpRoute: default via 10.1.0.254 dev wlp4s0 proto static metric 600 10.0.0.0/8 dev wlp4s0 proto kernel scope link src 10.1.0.168 metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 172.16.199.0/24 dev vmnet8 proto kernel scope link src 172.16.199.1 192.168.31.0/24 dev vmnet1 proto kernel scope link src 192.168.31.1 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2017-03-23T11:24:00.888213 nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlp4s0 wifi connected /org/freedesktop/NetworkManager/Devices/2 rsb_hs 7a8389dc-afd3-444b-a106-1974e9e74dff /org/freedesktop/NetworkManager/ActiveConnection/0 vmnet1 ethernet unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- vmnet8 ethernet unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/3 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- 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/1675353 Title: Network manager does not resolve dns names Status in network-manager package in Ubuntu: New Bug description: NM seems completely broken in 16.10. I use NM, wifi and several VPN connections. Expected behaviour: 1. C
[Touch-packages] [Bug 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers
On Yakkety there is no file /etc/NetworkManager/dnsmasq.d/strict-order. Should a touch do the trick? If so why so? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1003842 Title: dnsmasq sometimes fails to resolve private names in networks with non- equivalent nameservers Status in dnsmasq package in Ubuntu: Triaged Status in network-manager package in Ubuntu: Invalid Status in dnsmasq source package in Precise: Triaged Status in network-manager source package in Precise: Invalid Status in dnsmasq package in Debian: New Bug description: A number of reports already filed against network-manager seem to reflect this problem, but to make things very clear I am opening a new report. Where appropriate I will mark other reports as duplicates of this one. Consider a pre-Precise system with the following /etc/resolv.conf: nameserver 192.168.0.1 nameserver 8.8.8.8 The first address is the address of a nameserver on the LAN that can resolve both private and public domain names. The second address is the address of a nameserver on the Internet that can resolve only public names. This setup works fine because the GNU resolver always tries the first- listed address first. Now the administrator upgrades to Precise and instead of writing the above to resolv.conf, NetworkManager writes server=192.168.0.1 server=8.8.8.8 to /var/run/nm-dns-dnsmasq.conf and "nameserver 127.0.0.1" to resolv.conf. Resolution of private domain names is now broken because dnsmasq treats the two upstream nameservers as equals and uses the faster one, which could be 8.8.8.8. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1003842/+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 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers
Regarding #69: This does not work at all. In resolv.conf there is still nameserver 127.0.1.1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1003842 Title: dnsmasq sometimes fails to resolve private names in networks with non- equivalent nameservers Status in dnsmasq package in Ubuntu: Triaged Status in network-manager package in Ubuntu: Invalid Status in dnsmasq source package in Precise: Triaged Status in network-manager source package in Precise: Invalid Status in dnsmasq package in Debian: New Bug description: A number of reports already filed against network-manager seem to reflect this problem, but to make things very clear I am opening a new report. Where appropriate I will mark other reports as duplicates of this one. Consider a pre-Precise system with the following /etc/resolv.conf: nameserver 192.168.0.1 nameserver 8.8.8.8 The first address is the address of a nameserver on the LAN that can resolve both private and public domain names. The second address is the address of a nameserver on the Internet that can resolve only public names. This setup works fine because the GNU resolver always tries the first- listed address first. Now the administrator upgrades to Precise and instead of writing the above to resolv.conf, NetworkManager writes server=192.168.0.1 server=8.8.8.8 to /var/run/nm-dns-dnsmasq.conf and "nameserver 127.0.0.1" to resolv.conf. Resolution of private domain names is now broken because dnsmasq treats the two upstream nameservers as equals and uses the faster one, which could be 8.8.8.8. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1003842/+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 1620636] Re: Fails to pair with Bose QC35 headphones
In my case, the Bose QC35 pairs as a head phone only and this only in case, the head phone is not paired with any other device (in my case, it was first paired with a mobile phone). However, using a BT mouse makes sound output extremly jittery. Even though the head set has a microphone, it is not recognized as a combination device. Using Ubuntu 16.10, latest kernels and BT stacks available from repository. -- 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/1620636 Title: Fails to pair with Bose QC35 headphones Status in Canonical System Image: In Progress Status in bluez package in Ubuntu: In Progress Bug description: I am unable to pair the Bose QC35 BT headphones with Ubuntu, either Ubuntu desktop running 16.04 LTS with bluez 5.37 (also tried bluez 5.41 from installed from yakkety archive), nor using Ubuntu Touch rc- proposed build for Turbo #174. I'm trying to pair through the normal bluetooth control panel brought up through the bluetooth indicator. I've attached some logs that show it failing to pair. If I can provide anymore useful information about the headphones, please let me know. Syslog with bluetoothd debugging enabled: http://pastebin.ubuntu.com/23141394/ btmon output: http://pastebin.ubuntu.com/23141446/ bluetoothctl output: http://pastebin.ubuntu.com/23141510/ With Linux kernel 4.8.0 and bluez 4.52: --- bluetoothctl: http://pastebin.ubuntu.com/23256457/ btmon: http://pastebin.ubuntu.com/23256471/ To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1620636/+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 1650897] [NEW] nvidia proprietary driver does not output to HDMI screens
Public bug reported: When attaching an external screen to my Macbook Pro 15" Retina the external screen stays blank. nvidia-settings report the screen correctly. There are three options to attach a screen: - HDMI directly - via Thunderbold port 1 and 2 I use a Moshi adapter. Cable and adapter used to work properly, HDMI direct worked till 16.04. Using Nouveau driver the external screen works fine (except for overlapping screens) from TB port 2 and HDMI port. TB port 1 works fine with VGA. Thus I presume there is an error in the nvidia 367 driver (I haven't tried the latest update 375.20 from NVidias site yet) I have reported this error under #1650891 (nvidia-367 driver) ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 367.57 Mon Oct 3 20:37:01 PDT 2016 GCC version: gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12) .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Dec 18 15:09:07 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. 3rd Gen Core processor Graphics Controller [106b:00f7] NVIDIA Corporation GK107M [GeForce GT 650M Mac Edition] [10de:0fd5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. GK107M [GeForce GT 650M Mac Edition] [106b:00f2] InstallationDate: Installed on 2016-10-22 (57 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Apple Inc. MacBookPro10,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-30-generic.efi.signed root=UUID=9a60a19c-458f-4dca-8617-f7c6cacf9658 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP101.88Z.00EE.B03.1212211437 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-C3EC7CD22292981F dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro10,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-C3EC7CD22292981F dmi.modalias: dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B03.1212211437:bd12/21/2012:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F: dmi.product.name: MacBookPro10,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Sun Dec 18 14:22:56 2016 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-1ubuntu6.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1650897 Title: nvidia proprietary driver does not output to HDMI screens Status in xorg package in Ubuntu: New Bug description: When attaching an external screen to my Macbook Pro 15" Retina the external screen stays blank. nvidia-settings report the screen correctly. There are three options to attach a screen: - HDMI directly - via Thunderbold port 1 and 2 I use a Moshi adapter. Cable and adapter used to work properly, HDMI direct worked till 16.04. Using Nouveau driver the external screen works fine (except for overlapping screens) from TB port 2 and HDMI port. T
[Touch-packages] [Bug 1636381] Re: Details views in dialogs are too small
Upgrade deja-dup 34.2-0ubuntu3 -> 34.2-0ubuntu3.1 does not solve the issue -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1636381 Title: Details views in dialogs are too small Status in xorg package in Ubuntu: Confirmed Bug description: Details views in dialogs are too small, the viewing height is approx. 15px. My machine has a screen resolution of 2880x1800 on 15". I have to adjust the scaling to 1,62 to be able to read text. This leads to just half a line displayed in the viewing slot. Initially I reported this issue with deja-dup (https://bugs.launchpad.net/bugs/1635197) but this issue also shows up on several other dialog boxes (e.g. system updates - download of repos, ...). Thus I presume it either to be related with Unity or xorg. If you need additional information to identity the source, let me know. This behaviour is new to 16.10 and can be reproduced on any machine that I have access to. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 367.57 Mon Oct 3 20:37:01 PDT 2016 GCC version: gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12) .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Oct 25 07:59:44 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.8.0-26-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 4.8.0-26-generic, x86_64: installed nvidia-367, 367.57, 4.8.0-26-generic, x86_64: installed virtualbox, 5.1.6, 4.8.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. 3rd Gen Core processor Graphics Controller [106b:00f7] NVIDIA Corporation GK107M [GeForce GT 650M Mac Edition] [10de:0fd5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. GK107M [GeForce GT 650M Mac Edition] [106b:00f2] InstallationDate: Installed on 2016-10-22 (2 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Apple Inc. MacBookPro10,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-generic.efi.signed root=UUID=9a60a19c-458f-4dca-8617-f7c6cacf9658 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP101.88Z.00EE.B03.1212211437 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-C3EC7CD22292981F dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro10,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-C3EC7CD22292981F dmi.modalias: dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B03.1212211437:bd12/21/2012:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F: dmi.product.name: MacBookPro10,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Mon Oct 24 16:16:55 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-1ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1636381/+
[Touch-packages] [Bug 1636381] Re: Details views in dialogs are too small
This issue occurs in: - deja-dup - software updater In applications that provide grid views (PgAdminIII) the grid is illegible (fonts larger than row height). My screen scaling factor is 1,62 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1636381 Title: Details views in dialogs are too small Status in xorg package in Ubuntu: Confirmed Bug description: Details views in dialogs are too small, the viewing height is approx. 15px. My machine has a screen resolution of 2880x1800 on 15". I have to adjust the scaling to 1,62 to be able to read text. This leads to just half a line displayed in the viewing slot. Initially I reported this issue with deja-dup (https://bugs.launchpad.net/bugs/1635197) but this issue also shows up on several other dialog boxes (e.g. system updates - download of repos, ...). Thus I presume it either to be related with Unity or xorg. If you need additional information to identity the source, let me know. This behaviour is new to 16.10 and can be reproduced on any machine that I have access to. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 367.57 Mon Oct 3 20:37:01 PDT 2016 GCC version: gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12) .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Oct 25 07:59:44 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.8.0-26-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 4.8.0-26-generic, x86_64: installed nvidia-367, 367.57, 4.8.0-26-generic, x86_64: installed virtualbox, 5.1.6, 4.8.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. 3rd Gen Core processor Graphics Controller [106b:00f7] NVIDIA Corporation GK107M [GeForce GT 650M Mac Edition] [10de:0fd5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. GK107M [GeForce GT 650M Mac Edition] [106b:00f2] InstallationDate: Installed on 2016-10-22 (2 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Apple Inc. MacBookPro10,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-generic.efi.signed root=UUID=9a60a19c-458f-4dca-8617-f7c6cacf9658 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP101.88Z.00EE.B03.1212211437 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-C3EC7CD22292981F dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro10,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-C3EC7CD22292981F dmi.modalias: dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B03.1212211437:bd12/21/2012:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F: dmi.product.name: MacBookPro10,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Mon Oct 24 16:16:55 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.
[Touch-packages] [Bug 1636381] [NEW] Details views in dialogs are too small
Public bug reported: Details views in dialogs are too small, the viewing height is approx. 15px. My machine has a screen resolution of 2880x1800 on 15". I have to adjust the scaling to 1,62 to be able to read text. This leads to just half a line displayed in the viewing slot. Initially I reported this issue with deja-dup (https://bugs.launchpad.net/bugs/1635197) but this issue also shows up on several other dialog boxes (e.g. system updates - download of repos, ...). Thus I presume it either to be related with Unity or xorg. If you need additional information to identity the source, let me know. This behaviour is new to 16.10 and can be reproduced on any machine that I have access to. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 367.57 Mon Oct 3 20:37:01 PDT 2016 GCC version: gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12) .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Oct 25 07:59:44 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.8.0-26-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 4.8.0-26-generic, x86_64: installed nvidia-367, 367.57, 4.8.0-26-generic, x86_64: installed virtualbox, 5.1.6, 4.8.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. 3rd Gen Core processor Graphics Controller [106b:00f7] NVIDIA Corporation GK107M [GeForce GT 650M Mac Edition] [10de:0fd5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. GK107M [GeForce GT 650M Mac Edition] [106b:00f2] InstallationDate: Installed on 2016-10-22 (2 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Apple Inc. MacBookPro10,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-generic.efi.signed root=UUID=9a60a19c-458f-4dca-8617-f7c6cacf9658 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP101.88Z.00EE.B03.1212211437 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-C3EC7CD22292981F dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro10,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-C3EC7CD22292981F dmi.modalias: dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B03.1212211437:bd12/21/2012:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F: dmi.product.name: MacBookPro10,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Mon Oct 24 16:16:55 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-1ubuntu6 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu yakkety ** Attachment added: "Screenshot from 2016-10-25 08-09-38.png" https://bugs.launchpad.net/bugs/1636381/+attachment/4766783/+files/Screenshot%20from%202016-10-25%2008-09-38.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1636381 Title: Details views in dialogs are too small Status in xorg package in Ubuntu: New Bug description: Details views in dialogs are too s
[Touch-packages] [Bug 1633827] Re: Screen goes black on NVidia card
The workaround seems to produce side effects (in dconf the color spec is entered with double digits. See screenshot) Should that be the aspired behaviour? ** Attachment added: "Screenshot from 2016-10-16 12-32-30.png" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1633827/+attachment/4761864/+files/Screenshot%20from%202016-10-16%2012-32-30.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1633827 Title: Screen goes black on NVidia card Status in xorg package in Ubuntu: New Bug description: I've set my desktop to show a gradient blue (standard dark blue to middle blue from the selection box). After resume from suspend the screen was black. This happened before when running an application that covered 70% of the screen (a black banner on the bottom of the screen 50% of screen hight). Workaround: System Settings -> Appearance -> Colors & Gradients choose single color (will switch to blue) choose gradient again (will show two previously selected colors) Screen changes accordingly The graphics card works fine. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 367.57 Mon Oct 3 20:37:01 PDT 2016 GCC version: gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Oct 16 11:56:55 2016 DistUpgraded: 2016-10-15 12:59:20,764 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory) (8)) DistroCodename: yakkety DistroVariant: ubuntu GconfCompiz: /apps/compiz-1/general: /apps/compiz-1/general/screen0: /apps/compiz-1/general/screen0/options: active_plugins = [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] GraphicsCard: NVIDIA Corporation GK107M [GeForce GT 650M Mac Edition] [10de:0fd5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. GK107M [GeForce GT 650M Mac Edition] [106b:00f2] InstallationDate: Installed on 2013-05-17 (1247 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64+mac (20130424) MachineType: Apple Inc. MacBookPro10,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic root=UUID=3679e976-6405-4981-aa99-8c79d15e6aa3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to yakkety on 2016-10-15 (0 days ago) dmi.bios.date: 12/21/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP101.88Z.00EE.B03.1212211437 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-C3EC7CD22292981F dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro10,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-C3EC7CD22292981F dmi.modalias: dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B03.1212211437:bd12/21/2012:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F: dmi.product.name: MacBookPro10,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
[Touch-packages] [Bug 1633827] Re: Screen goes black on NVidia card
When screen blanks partially, the workaround described above does not work. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1633827 Title: Screen goes black on NVidia card Status in xorg package in Ubuntu: New Bug description: I've set my desktop to show a gradient blue (standard dark blue to middle blue from the selection box). After resume from suspend the screen was black. This happened before when running an application that covered 70% of the screen (a black banner on the bottom of the screen 50% of screen hight). Workaround: System Settings -> Appearance -> Colors & Gradients choose single color (will switch to blue) choose gradient again (will show two previously selected colors) Screen changes accordingly The graphics card works fine. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 367.57 Mon Oct 3 20:37:01 PDT 2016 GCC version: gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Oct 16 11:56:55 2016 DistUpgraded: 2016-10-15 12:59:20,764 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory) (8)) DistroCodename: yakkety DistroVariant: ubuntu GconfCompiz: /apps/compiz-1/general: /apps/compiz-1/general/screen0: /apps/compiz-1/general/screen0/options: active_plugins = [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] GraphicsCard: NVIDIA Corporation GK107M [GeForce GT 650M Mac Edition] [10de:0fd5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. GK107M [GeForce GT 650M Mac Edition] [106b:00f2] InstallationDate: Installed on 2013-05-17 (1247 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64+mac (20130424) MachineType: Apple Inc. MacBookPro10,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic root=UUID=3679e976-6405-4981-aa99-8c79d15e6aa3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to yakkety on 2016-10-15 (0 days ago) dmi.bios.date: 12/21/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP101.88Z.00EE.B03.1212211437 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-C3EC7CD22292981F dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro10,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-C3EC7CD22292981F dmi.modalias: dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B03.1212211437:bd12/21/2012:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F: dmi.product.name: MacBookPro10,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserv
[Touch-packages] [Bug 1633827] Re: Screen goes black on NVidia card
** Attachment added: "Blanked portion of screen" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1633827/+attachment/4761854/+files/Screenshot%20from%202016-10-16%2012-17-39.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1633827 Title: Screen goes black on NVidia card Status in xorg package in Ubuntu: New Bug description: I've set my desktop to show a gradient blue (standard dark blue to middle blue from the selection box). After resume from suspend the screen was black. This happened before when running an application that covered 70% of the screen (a black banner on the bottom of the screen 50% of screen hight). Workaround: System Settings -> Appearance -> Colors & Gradients choose single color (will switch to blue) choose gradient again (will show two previously selected colors) Screen changes accordingly The graphics card works fine. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 367.57 Mon Oct 3 20:37:01 PDT 2016 GCC version: gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Oct 16 11:56:55 2016 DistUpgraded: 2016-10-15 12:59:20,764 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory) (8)) DistroCodename: yakkety DistroVariant: ubuntu GconfCompiz: /apps/compiz-1/general: /apps/compiz-1/general/screen0: /apps/compiz-1/general/screen0/options: active_plugins = [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] GraphicsCard: NVIDIA Corporation GK107M [GeForce GT 650M Mac Edition] [10de:0fd5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. GK107M [GeForce GT 650M Mac Edition] [106b:00f2] InstallationDate: Installed on 2013-05-17 (1247 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64+mac (20130424) MachineType: Apple Inc. MacBookPro10,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic root=UUID=3679e976-6405-4981-aa99-8c79d15e6aa3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to yakkety on 2016-10-15 (0 days ago) dmi.bios.date: 12/21/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP101.88Z.00EE.B03.1212211437 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-C3EC7CD22292981F dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro10,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-C3EC7CD22292981F dmi.modalias: dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B03.1212211437:bd12/21/2012:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F: dmi.product.name: MacBookPro10,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-vide
[Touch-packages] [Bug 1633827] [NEW] Screen goes black on NVidia card
Public bug reported: I've set my desktop to show a gradient blue (standard dark blue to middle blue from the selection box). After resume from suspend the screen was black. This happened before when running an application that covered 70% of the screen (a black banner on the bottom of the screen 50% of screen hight). Workaround: System Settings -> Appearance -> Colors & Gradients choose single color (will switch to blue) choose gradient again (will show two previously selected colors) Screen changes accordingly The graphics card works fine. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 367.57 Mon Oct 3 20:37:01 PDT 2016 GCC version: gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Oct 16 11:56:55 2016 DistUpgraded: 2016-10-15 12:59:20,764 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory) (8)) DistroCodename: yakkety DistroVariant: ubuntu GconfCompiz: /apps/compiz-1/general: /apps/compiz-1/general/screen0: /apps/compiz-1/general/screen0/options: active_plugins = [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] GraphicsCard: NVIDIA Corporation GK107M [GeForce GT 650M Mac Edition] [10de:0fd5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. GK107M [GeForce GT 650M Mac Edition] [106b:00f2] InstallationDate: Installed on 2013-05-17 (1247 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64+mac (20130424) MachineType: Apple Inc. MacBookPro10,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic root=UUID=3679e976-6405-4981-aa99-8c79d15e6aa3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to yakkety on 2016-10-15 (0 days ago) dmi.bios.date: 12/21/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP101.88Z.00EE.B03.1212211437 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-C3EC7CD22292981F dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro10,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-C3EC7CD22292981F dmi.modalias: dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B03.1212211437:bd12/21/2012:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F: dmi.product.name: MacBookPro10,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Sun Oct 16 11:21:42 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-1ubuntu6 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 corruption ubuntu yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bu
[Touch-packages] [Bug 1572041] Re: Can't create click target for armhf
Same with an dis-upgraded version. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1572041 Title: Can't create click target for armhf Status in click package in Ubuntu: Confirmed Bug description: sudo click chroot -a armhf -f ubuntu-sdk-15.04 create The following packages have unmet dependencies: ubuntu-sdk-libs:armhf : Depends: ubuntu-html5-container:armhf E: Unable to correct problems, you have held broken packages. Command returned 100: schroot -u root -c source:click-ubuntu-sdk-15.04-armhf -- /finish.sh Traceback (most recent call last): File "/usr/bin/click", line 110, in sys.exit(main()) File "/usr/bin/click", line 106, in main return mod.run(args) File "/usr/lib/python3/dist-packages/click/commands/chroot.py", line 266, in run return args.func(parser, args) File "/usr/lib/python3/dist-packages/click/commands/chroot.py", line 68, in create return chroot.create(args.keep_broken_chroot) File "/usr/lib/python3/dist-packages/click/chroot.py", line 599, in create self.full_name, ret_code)) click.chroot.ClickChrootException: Failed to create chroot 'click-ubuntu-sdk-15.04-armhf' (exit status 100) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1572041/+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 1549480] Re: Xorg freeze
I'm stuck somewhere in the middle. a) I have installed Ubuntu natively on my Mac. No OS X installed. b) I can boot from an external drive. I have OS X 10.11.3. This OS fixes the BIOS on the fly. c) I cannot install the BIOS updates that both you or Apple supplies as they require OS X 10.9.5 (which I haven't). d) even if I restore a very old backup with 10.8.5, I cannot upgrade to 10.9.5 as it suggests 10.11. immediately. e) Apple support does not offer suggestions (other than sending it in or leaving it as it is as 10.11. fixes it implicitly) So, my BIOS is like it is, cannot be changed. Any suggestions? ** Changed in: xorg (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1549480 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: After suspend - resume, the screen stays black, mouse cursor moves. Other than that the machines seems to work fine. This behaviour appeared in Linux 4.2.0-30-generic #35-Ubuntu SMP ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-30.35-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 NonfreeKernelModules: nvidia wl .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 352.63 Sat Nov 7 21:25:42 PST 2015 GCC version: gcc version 5.2.1 20151010 (Ubuntu 5.2.1-22ubuntu2) ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Wed Feb 24 21:45:24 2016 DistUpgraded: 2015-10-23 08:17:33,368 DEBUG enabling apt cron job DistroCodename: wily DistroVariant: ubuntu GpuHangFrequency: This is the first time GraphicsCard: NVIDIA Corporation GK107M [GeForce GT 650M Mac Edition] [10de:0fd5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device [106b:00f2] InstallationDate: Installed on 2013-05-17 (1012 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64+mac (20130424) MachineType: Apple Inc. MacBookPro10,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-generic root=UUID=3679e976-6405-4981-aa99-8c79d15e6aa3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to wily on 2015-10-23 (124 days ago) dmi.bios.date: 12/21/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP101.88Z.00EE.B03.1212211437 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-C3EC7CD22292981F dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro10,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-C3EC7CD22292981F dmi.modalias: dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B03.1212211437:bd12/21/2012:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F: dmi.product.name: MacBookPro10,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Wed Feb 24 21:44:44 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.17.2-1ubuntu9.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1549480/+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 1549480] [NEW] Xorg freeze
Public bug reported: After suspend - resume, the screen stays black, mouse cursor moves. Other than that the machines seems to work fine. This behaviour appeared in Linux 4.2.0-30-generic #35-Ubuntu SMP ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-30.35-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 NonfreeKernelModules: nvidia wl .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 352.63 Sat Nov 7 21:25:42 PST 2015 GCC version: gcc version 5.2.1 20151010 (Ubuntu 5.2.1-22ubuntu2) ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Wed Feb 24 21:45:24 2016 DistUpgraded: 2015-10-23 08:17:33,368 DEBUG enabling apt cron job DistroCodename: wily DistroVariant: ubuntu GpuHangFrequency: This is the first time GraphicsCard: NVIDIA Corporation GK107M [GeForce GT 650M Mac Edition] [10de:0fd5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device [106b:00f2] InstallationDate: Installed on 2013-05-17 (1012 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64+mac (20130424) MachineType: Apple Inc. MacBookPro10,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-generic root=UUID=3679e976-6405-4981-aa99-8c79d15e6aa3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to wily on 2015-10-23 (124 days ago) dmi.bios.date: 12/21/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP101.88Z.00EE.B03.1212211437 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-C3EC7CD22292981F dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro10,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-C3EC7CD22292981F dmi.modalias: dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B03.1212211437:bd12/21/2012:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F: dmi.product.name: MacBookPro10,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Wed Feb 24 21:44:44 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.17.2-1ubuntu9.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug freeze third-party-packages ubuntu wily -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1549480 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: After suspend - resume, the screen stays black, mouse cursor moves. Other than that the machines seems to work fine. This behaviour appeared in Linux 4.2.0-30-generic #35-Ubuntu SMP ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-30.35-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 NonfreeKernelModules: nvidia wl .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 352.63 Sat Nov 7 21:25:42 PST 2015 GCC version: gcc version 5.2.1 20151010 (Ubuntu 5.2.1-22ubuntu2) ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Wed Feb 24 21:45:24 2016 DistUpgraded: 2015-10-23 08:17:33,368 DEBUG enabling apt cron job DistroCodename: wily DistroVariant: ubuntu GpuHangFrequency: This is the first time GraphicsCard: NVIDIA Corporation GK107M [GeForce GT 650M Mac Edition] [10de:0fd5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device [106b:00f2] InstallationDate: Installed on 2013-05-17 (1012 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64+mac (20130424) MachineType: Apple Inc. MacBookPro10,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-generic root=UUID=3679e976-6405-4981-aa99-8c79d15e6aa3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to wily on 2015-10-23 (124
[Touch-packages] [Bug 393094] Re: network manager ppp timeout
I could verify this situation with a Windows client. I doubt there is anything that can be done. If two networks share the same IP range with two different default gateways and different dns name spaces, not even static routes can solve this. Thanks for your efforts though. -- 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/393094 Title: network manager ppp timeout Status in network-manager package in Ubuntu: Incomplete Bug description: NetworkManager: pppd_timed_out(): Looks like pppd didn't initialize our dbus module I cannot connect via usb UMTS modem. Here's the log (Machine: MSI X320, Ubuntu 9.04, Linux 2.6.28.13-generic #44-Ubuntu SMP) --- Jun 28 11:29:53 xb NetworkManager: Activation (ttyUSB0) starting connection 'Yesss' Jun 28 11:29:53 xb NetworkManager: (ttyUSB0): device state change: 3 -> 4 Jun 28 11:29:53 xb NetworkManager: Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) scheduled... Jun 28 11:29:53 xb NetworkManager: Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) started... Jun 28 11:29:53 xb NetworkManager: [1246181393.723285] nm_serial_device_open(): (ttyUSB0) opening device... Jun 28 11:29:53 xb NetworkManager: Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) complete. Jun 28 11:29:53 xb NetworkManager: (ttyUSB0): GSM pin secret required Jun 28 11:29:53 xb NetworkManager: (ttyUSB0): device state change: 4 -> 6 Jun 28 11:29:53 xb NetworkManager: Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) scheduled... Jun 28 11:29:53 xb NetworkManager: Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) started... Jun 28 11:29:53 xb NetworkManager: (ttyUSB0): device state change: 6 -> 4 Jun 28 11:29:53 xb NetworkManager: [1246181393.929608] nm_serial_device_open(): (ttyUSB0) opening device... Jun 28 11:29:53 xb NetworkManager: Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) complete. Jun 28 11:29:54 xb NetworkManager: (ttyUSB0): powering up... Jun 28 11:29:56 xb NetworkManager: Searching for a network... Jun 28 11:30:01 xb last message repeated 5 times Jun 28 11:30:02 xb NetworkManager: Registered on Roaming network Jun 28 11:30:02 xb NetworkManager: Associated with network: +COPS: 0,2,"23205",2 Jun 28 11:30:02 xb NetworkManager: Connected, Woo! Jun 28 11:30:02 xb NetworkManager: Activation (ttyUSB0) Stage 2 of 5 (Device Configure) scheduled... Jun 28 11:30:02 xb NetworkManager: Activation (ttyUSB0) Stage 2 of 5 (Device Configure) starting... Jun 28 11:30:02 xb NetworkManager: (ttyUSB0): device state change: 4 -> 5 Jun 28 11:30:02 xb NetworkManager: Starting pppd connection Jun 28 11:30:02 xb NetworkManager: [1246181402.327197] nm_ppp_manager_start(): Command line: /usr/sbin/pppd nodetach lock nodefaultroute ttyUSB0 noipdefault noauth usepeerdns lcp-echo-failure 0 lcp-echo-interval 0 ipparam /org/freedesktop/NetworkManager/PPP/0 plugin /usr/lib/pppd/2.4.4/nm-pppd-plugin.so Jun 28 11:30:02 xb NetworkManager: [1246181402.347065] nm_ppp_manager_start(): ppp started with pid 3306 Jun 28 11:30:02 xb NetworkManager: Activation (ttyUSB0) Stage 2 of 5 (Device Configure) complete. Jun 28 11:30:02 xb pppd[3306]: Plugin /usr/lib/pppd/2.4.4/nm-pppd-plugin.so loaded. Jun 28 11:30:02 xb pppd[3306]: pppd 2.4.5 started by root, uid 0 Jun 28 11:30:02 xb pppd[3306]: Using interface ppp0 Jun 28 11:30:02 xb pppd[3306]: Connect: ppp0 <--> /dev/ttyUSB0 Jun 28 11:30:02 xb pppd[3306]: Unable to obtain CHAP password for xb on UMTS_CHAP_SRVR from plugin Jun 28 11:30:02 xb pppd[3306]: No CHAP secret found for authenticating us to UMTS_CHAP_SRVR Jun 28 11:30:02 xb pppd[3306]: CHAP authentication succeeded Jun 28 11:30:02 xb pppd[3306]: CHAP authentication succeeded Jun 28 11:30:02 xb kernel: [ 137.660149] PPP BSD Compression module registered Jun 28 11:30:02 xb kernel: [ 137.717957] PPP Deflate Compression module registered Jun 28 11:30:06 xb pppd[3306]: Could not determine remote IP address: defaulting to 10.64.64.64 Jun 28 11:30:06 xb pppd[3306]: Cannot determine ethernet address for proxy ARP Jun 28 11:30:06 xb pppd[3306]: local IP address 10.113.214.1 Jun 28 11:30:06 xb pppd[3306]: remote IP address 10.64.64.64 Jun 28 11:30:06 xb pppd[3306]: primary DNS address 81.3.216.100 Jun 28 11:30:06 xb pppd[3306]: secondary DNS address 194.24.128.100 Jun 28 11:30:18 xb NetworkManager: pppd_timed_out(): Looks like pppd didn't initialize our dbus module Jun 28 11:30:18 xb NetworkManager: (ttyUSB0): device state change: 5 -> 9 Jun 28 11:30:18 xb pppd[3306]: Terminating on signal 15 Jun 28 11:30:18 xb NetworkManager: [1246181418.011641] nm_serial_device_close(): Closing device 'ttyUSB0' Jun 28 11:30:18 xb pppd[3306]: Connect time 0.2 minutes. Jun 28
[Touch-packages] [Bug 393094] Re: network manager ppp timeout
I just read the syslog excerpt above. I recently had a similar issue in 15.10 and want to share my experience: The symptoms: Timeouts and connection termination after some minutes. I used openconnect vpn connector. After several experiments I figured the source of the problem being that my home network is a class A network (10.x.x.x) and the destination network is a class A network (10.x.x.x) as well. Keep alive packets follow the routing table and in my case, this included the default route pointing to my router. The router tunnels the vpn connection but does not route it which means that keep alives will not reach the remote endpoint and the connection runs into timeouts. I found no solution to this issue other than using an alternative network connection (using mobile modem which issues a different home IP address 172.16.x.x). Now the connection is stable and keep alives are forwarded correctly. Note: Even static routes do not help as the endpoint of the vpn tunnel has rolling IP addresses. Why do I believe there is a connection? see: Jun 28 11:30:06 xb pppd[3306]: Cannot determine ethernet address for proxy ARP Jun 28 11:30:06 xb pppd[3306]: local IP address 10.113.214.1 < Jun 28 11:30:06 xb pppd[3306]: remote IP address 10.64.64.64 < I hope this helps -- 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/393094 Title: network manager ppp timeout Status in network-manager package in Ubuntu: Incomplete Bug description: NetworkManager: pppd_timed_out(): Looks like pppd didn't initialize our dbus module I cannot connect via usb UMTS modem. Here's the log (Machine: MSI X320, Ubuntu 9.04, Linux 2.6.28.13-generic #44-Ubuntu SMP) --- Jun 28 11:29:53 xb NetworkManager: Activation (ttyUSB0) starting connection 'Yesss' Jun 28 11:29:53 xb NetworkManager: (ttyUSB0): device state change: 3 -> 4 Jun 28 11:29:53 xb NetworkManager: Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) scheduled... Jun 28 11:29:53 xb NetworkManager: Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) started... Jun 28 11:29:53 xb NetworkManager: [1246181393.723285] nm_serial_device_open(): (ttyUSB0) opening device... Jun 28 11:29:53 xb NetworkManager: Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) complete. Jun 28 11:29:53 xb NetworkManager: (ttyUSB0): GSM pin secret required Jun 28 11:29:53 xb NetworkManager: (ttyUSB0): device state change: 4 -> 6 Jun 28 11:29:53 xb NetworkManager: Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) scheduled... Jun 28 11:29:53 xb NetworkManager: Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) started... Jun 28 11:29:53 xb NetworkManager: (ttyUSB0): device state change: 6 -> 4 Jun 28 11:29:53 xb NetworkManager: [1246181393.929608] nm_serial_device_open(): (ttyUSB0) opening device... Jun 28 11:29:53 xb NetworkManager: Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) complete. Jun 28 11:29:54 xb NetworkManager: (ttyUSB0): powering up... Jun 28 11:29:56 xb NetworkManager: Searching for a network... Jun 28 11:30:01 xb last message repeated 5 times Jun 28 11:30:02 xb NetworkManager: Registered on Roaming network Jun 28 11:30:02 xb NetworkManager: Associated with network: +COPS: 0,2,"23205",2 Jun 28 11:30:02 xb NetworkManager: Connected, Woo! Jun 28 11:30:02 xb NetworkManager: Activation (ttyUSB0) Stage 2 of 5 (Device Configure) scheduled... Jun 28 11:30:02 xb NetworkManager: Activation (ttyUSB0) Stage 2 of 5 (Device Configure) starting... Jun 28 11:30:02 xb NetworkManager: (ttyUSB0): device state change: 4 -> 5 Jun 28 11:30:02 xb NetworkManager: Starting pppd connection Jun 28 11:30:02 xb NetworkManager: [1246181402.327197] nm_ppp_manager_start(): Command line: /usr/sbin/pppd nodetach lock nodefaultroute ttyUSB0 noipdefault noauth usepeerdns lcp-echo-failure 0 lcp-echo-interval 0 ipparam /org/freedesktop/NetworkManager/PPP/0 plugin /usr/lib/pppd/2.4.4/nm-pppd-plugin.so Jun 28 11:30:02 xb NetworkManager: [1246181402.347065] nm_ppp_manager_start(): ppp started with pid 3306 Jun 28 11:30:02 xb NetworkManager: Activation (ttyUSB0) Stage 2 of 5 (Device Configure) complete. Jun 28 11:30:02 xb pppd[3306]: Plugin /usr/lib/pppd/2.4.4/nm-pppd-plugin.so loaded. Jun 28 11:30:02 xb pppd[3306]: pppd 2.4.5 started by root, uid 0 Jun 28 11:30:02 xb pppd[3306]: Using interface ppp0 Jun 28 11:30:02 xb pppd[3306]: Connect: ppp0 <--> /dev/ttyUSB0 Jun 28 11:30:02 xb pppd[3306]: Unable to obtain CHAP password for xb on UMTS_CHAP_SRVR from plugin Jun 28 11:30:02 xb pppd[3306]: No CHAP secret found for authenticating us to UMTS_CHAP_SRVR Jun 28 11:30:02 xb pppd[3306]: CHAP authentication succeeded Jun 28 11:30:02 xb pppd[3306]: CHA
[Touch-packages] [Bug 1491844] Re: Network Manager fails to connect to VPN (AnyConnect) - [vpn-mana ger/nm-vpn-connection.c:1770] get_secrets_cb(): Failed to request VPN secrets #2 : (6) No agents wer
This issue still exists in Linux 4.2.0-22-generic #27-Ubuntu SMP Thu Dec 17 22:57:08 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux This is what happens in the log file: ... Dec 22 11:47:18 mbr wpa_supplicant[1000]: wlan0: WPA: Group rekeying completed with 60:e3:27:4f:bb:0e [GTK=TKIP] Dec 22 11:47:25 mbr openconnect[9546]: CSTP Dead Peer Detection detected dead peer! ... The average intervall is less than 1 minute. -- 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/1491844 Title: Network Manager fails to connect to VPN (AnyConnect) - [vpn-mana ger /nm-vpn-connection.c:1770] get_secrets_cb(): Failed to request VPN secrets #2 : (6) No agents were available for this request Status in network-manager package in Ubuntu: Confirmed Bug description: Installed vpnc established vpn connection successfully after restart, the vpn connection cannot be established any more mbr NetworkManager[17397]: [1441285066.578727] [vpn-mana ger/nm-vpn-connection.c:1770] get_secrets_cb(): Failed to request VPN secrets #2 : (6) No agents were available for this request. Workaround: rm .gconf/apps/nm-applet logout/login connect to VPN works This surely cannot be a normal procedure ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu15.2 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.17.2-0ubuntu1.4 Architecture: amd64 CurrentDesktop: Unity Date: Thu Sep 3 15:10:53 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-05-17 (838 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64+mac (20130424) IpRoute: default via 10.1.0.254 dev wlan0 proto static metric 400 10.0.0.0/8 dev wlan0 proto kernel scope link src 10.1.0.104 169.254.0.0/16 dev wlan0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-04-25 (131 days ago) nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1491844/+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 1448555] Re: network-manager does not autoconnect to wifi network after resume from suspend
I can confirm that this bug is eliminated in 15.10. Unfortunately another old bug reappeared (random disconnect). I will look into this in more detail. For me it is solved. Thanks -- 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/1448555 Title: network-manager does not autoconnect to wifi network after resume from suspend Status in network-manager package in Ubuntu: Confirmed Bug description: After upgrading to 15.04 network manager does not reconnect to the wifi network after resuming from a suspend to memory. Workaround: disable and re-enable wireless network -> connects immediately ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu15 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 25 23:53:54 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-05-17 (708 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64+mac (20130424) IpRoute: default via 10.1.0.254 dev wlan0 proto static metric 1024 10.0.0.0/8 dev wlan0 proto kernel scope link src 10.1.0.103 169.254.0.0/16 dev wlan0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-04-25 (0 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlan0 wifi connected /org/freedesktop/NetworkManager/Devices/1 rsb_hs d8793959-2da1-4dc6-85ad-2dcf9e36e64b /org/freedesktop/NetworkManager/ActiveConnection/1 EC:88:92:61:E9:5F btdisconnected /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- -- -- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1448555/+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 982283] Re: Modem is not detected (ever, or for several minutes); computer sometimes freezes; modem-manager sometimes crashes -- Huawei E160
With Ubuntu 15.04 it reappeared.
The stick is practically useless.
Reason I found is that the stick registers as USB storage as well and
then is not recognized as modem.
--
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/982283
Title:
Modem is not detected (ever, or for several minutes); computer
sometimes freezes; modem-manager sometimes crashes -- Huawei E160
Status in linux package in Ubuntu:
Incomplete
Status in network-manager package in Ubuntu:
Confirmed
Bug description:
Huawei e160 modem isn't consistently detected. It's a hit and miss affair.
Sometimes requires several attempts of plugging in and out.
This modem also has a MicroSD card slot and this is probably what is causing
the issue. However, no additional drive is reported or mounted automatically.
It just takes 2-5 minutes for the modem to be detected. Following which
running it is usually hassle free.
Using ubuntu 12.04
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: network-manager 0.9.4.0-0ubuntu3
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux 3.2.0-23-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu3
Architecture: amd64
Date: Sun Apr 15 17:48:06 2012
InstallationMedia: This
IpRoute:
default via 10.64.64.64 dev ppp0 proto static
10.64.64.64 dev ppp0 proto kernel scope link src 112.79.128.134
169.254.0.0/16 dev ppp0 scope link metric 1000
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
WimaxEnabled=true
SourcePackage: network-manager
UpgradeStatus: Upgraded to precise on 2012-03-18 (28 days ago)
nmcli-dev:
DEVICE TYPE STATE DBUS-PATH
ttyUSB1gsm connected
/org/freedesktop/NetworkManager/Devices/3
eth0 802-3-ethernetunavailable
/org/freedesktop/NetworkManager/Devices/1
wlan0 802-11-wireless disconnected
/org/freedesktop/NetworkManager/Devices/0
nmcli-nm:
RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE
WIFI WWAN-HARDWARE WWAN
running 0.9.4.0connected enabled enabled
enabledenabled enabled
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu5
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC665 Analog [ALC665 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: rishi 2189 F pulseaudio
/dev/snd/controlC0: rishi 2189 F pulseaudio
/dev/snd/pcmC0D0p: rishi 2189 F...m pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf0a0 irq 57'
Mixer name : 'Realtek ALC665'
Components : 'HDA:10ec0665,1028046e,0013'
Controls : 25
Simple ctrls : 12
Card1.Amixer.info:
Card hw:1 'NVidia'/'HDA NVidia at 0xcdefc000 irq 17'
Mixer name : 'Nvidia GPU 14 HDMI/DP'
Components : 'HDA:10de0014,10de0101,00100100'
Controls : 24
Simple ctrls : 4
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=cc0cdc76-9415-4970-9655-ebde53ae90cf
InstallationMedia: This
IpRoute:
default via 192.168.2.1 dev wlan0 proto static
169.254.0.0/16 dev wlan0 scope link metric 1000
192.168.2.0/24 dev wlan0 proto kernel scope link src 192.168.2.104
metric 2
KnownReport: https://bugs.launchpad.net/bugs/452814
MachineType: Dell Inc. XPS L501X
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
WimaxEnabled=true
NonfreeKernelModules: nvidia
Package: network-manager 0.9.4.0-0ubuntu3
PackageArchitecture: amd64
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic
root=UUID=c6230f54-6e0e-4a44-9ad2-f195df33ec06 ro
resume=UUID=cc0cdc76-9415-4970-9655-ebde53ae90cf quiet splash
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
RelatedPackageVersions:
linux-restricted-modules-3.2.0-23-generic N/A
linux-backports-modules-3.2.0-23-generic N/A
linux-firmware1.79
StagingDrivers: mei
Tags: precise staging precise
Uname: Linux 3.2.0-23-generic x86_64
UpgradeStatus: Upgraded to precise on 2012-03-18 (39 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 07/26/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A08
dmi.board.name: 0J1VR3
dmi.board.vendor: Dell Inc.
dmi.board.version: A08
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A08
dmi.modalias:
dmi:bvnDellInc.:bvrA08:bd07/26/2011:svnDellInc.:pnXPSL501X:pvrA08:
[Touch-packages] [Bug 1448555] Re: network-manager does not autoconnect to wifi network after resume from suspend
suggestion #15 does not work either. Linux mbr 3.19.0-31-generic #36-Ubuntu SMP Wed Oct 7 15:04:02 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux using systemd -- 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/1448555 Title: network-manager does not autoconnect to wifi network after resume from suspend Status in network-manager package in Ubuntu: Confirmed Bug description: After upgrading to 15.04 network manager does not reconnect to the wifi network after resuming from a suspend to memory. Workaround: disable and re-enable wireless network -> connects immediately ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu15 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 25 23:53:54 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-05-17 (708 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64+mac (20130424) IpRoute: default via 10.1.0.254 dev wlan0 proto static metric 1024 10.0.0.0/8 dev wlan0 proto kernel scope link src 10.1.0.103 169.254.0.0/16 dev wlan0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-04-25 (0 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlan0 wifi connected /org/freedesktop/NetworkManager/Devices/1 rsb_hs d8793959-2da1-4dc6-85ad-2dcf9e36e64b /org/freedesktop/NetworkManager/ActiveConnection/1 EC:88:92:61:E9:5F btdisconnected /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- -- -- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1448555/+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 1491844] Re: Network Manager fails to connect to VPN (AnyConnect) - [vpn-mana ger/nm-vpn-connection.c:1770] get_secrets_cb(): Failed to request VPN secrets #2 : (6) No agents wer
This bug still applies with kernel 3.19.0-31-generic #36-Ubuntu SMP -- 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/1491844 Title: Network Manager fails to connect to VPN (AnyConnect) - [vpn-mana ger /nm-vpn-connection.c:1770] get_secrets_cb(): Failed to request VPN secrets #2 : (6) No agents were available for this request Status in network-manager package in Ubuntu: Confirmed Bug description: Installed vpnc established vpn connection successfully after restart, the vpn connection cannot be established any more mbr NetworkManager[17397]: [1441285066.578727] [vpn-mana ger/nm-vpn-connection.c:1770] get_secrets_cb(): Failed to request VPN secrets #2 : (6) No agents were available for this request. Workaround: rm .gconf/apps/nm-applet logout/login connect to VPN works This surely cannot be a normal procedure ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu15.2 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.17.2-0ubuntu1.4 Architecture: amd64 CurrentDesktop: Unity Date: Thu Sep 3 15:10:53 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-05-17 (838 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64+mac (20130424) IpRoute: default via 10.1.0.254 dev wlan0 proto static metric 400 10.0.0.0/8 dev wlan0 proto kernel scope link src 10.1.0.104 169.254.0.0/16 dev wlan0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-04-25 (131 days ago) nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1491844/+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 1491844] Re: Network Manager fails to connect to VPN (AnyConnect) - [vpn-mana ger/nm-vpn-connection.c:1770] get_secrets_cb(): Failed to request VPN secrets #2 : (6) No agents wer
ii network-manage 0.9.10.0-4ub amd64network management framework (dae Linux mbr 3.19.0-30-generic #34-Ubuntu SMP Fri Oct 2 22:08:41 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Problem still exists. -- 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/1491844 Title: Network Manager fails to connect to VPN (AnyConnect) - [vpn-mana ger /nm-vpn-connection.c:1770] get_secrets_cb(): Failed to request VPN secrets #2 : (6) No agents were available for this request Status in network-manager package in Ubuntu: Confirmed Bug description: Installed vpnc established vpn connection successfully after restart, the vpn connection cannot be established any more mbr NetworkManager[17397]: [1441285066.578727] [vpn-mana ger/nm-vpn-connection.c:1770] get_secrets_cb(): Failed to request VPN secrets #2 : (6) No agents were available for this request. Workaround: rm .gconf/apps/nm-applet logout/login connect to VPN works This surely cannot be a normal procedure ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu15.2 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.17.2-0ubuntu1.4 Architecture: amd64 CurrentDesktop: Unity Date: Thu Sep 3 15:10:53 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-05-17 (838 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64+mac (20130424) IpRoute: default via 10.1.0.254 dev wlan0 proto static metric 400 10.0.0.0/8 dev wlan0 proto kernel scope link src 10.1.0.104 169.254.0.0/16 dev wlan0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-04-25 (131 days ago) nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1491844/+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 1448555] Re: network-manager does not autoconnect to wifi network after resume from suspend
back to suggestion #12: It does not fire (still don't know why) However, running iwlist scan (as sudo) DOES reconnect. Today I connected to another network (which I use regulary. The connection was established immediately after resume. After putting the machine to sleep again, no reconnect occured after resume. Thus my observation: If after wake-up the network environment is the same, network manager DOES NOT reconnect. If after wake-up the network is different (other SSIDs or SSID not found) a scan is launched automatically and a reconnect occurs. -- 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/1448555 Title: network-manager does not autoconnect to wifi network after resume from suspend Status in network-manager package in Ubuntu: Confirmed Bug description: After upgrading to 15.04 network manager does not reconnect to the wifi network after resuming from a suspend to memory. Workaround: disable and re-enable wireless network -> connects immediately ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu15 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 25 23:53:54 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-05-17 (708 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64+mac (20130424) IpRoute: default via 10.1.0.254 dev wlan0 proto static metric 1024 10.0.0.0/8 dev wlan0 proto kernel scope link src 10.1.0.103 169.254.0.0/16 dev wlan0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-04-25 (0 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlan0 wifi connected /org/freedesktop/NetworkManager/Devices/1 rsb_hs d8793959-2da1-4dc6-85ad-2dcf9e36e64b /org/freedesktop/NetworkManager/ActiveConnection/1 EC:88:92:61:E9:5F btdisconnected /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- -- -- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1448555/+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 1448555] Re: network-manager does not autoconnect to wifi network after resume from suspend
suggestion #12 does not change the situation on my machines network stays down and I have to reconnect to the WiFi manually or restart Network Manager -- 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/1448555 Title: network-manager does not autoconnect to wifi network after resume from suspend Status in network-manager package in Ubuntu: Confirmed Bug description: After upgrading to 15.04 network manager does not reconnect to the wifi network after resuming from a suspend to memory. Workaround: disable and re-enable wireless network -> connects immediately ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu15 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 25 23:53:54 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-05-17 (708 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64+mac (20130424) IpRoute: default via 10.1.0.254 dev wlan0 proto static metric 1024 10.0.0.0/8 dev wlan0 proto kernel scope link src 10.1.0.103 169.254.0.0/16 dev wlan0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-04-25 (0 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlan0 wifi connected /org/freedesktop/NetworkManager/Devices/1 rsb_hs d8793959-2da1-4dc6-85ad-2dcf9e36e64b /org/freedesktop/NetworkManager/ActiveConnection/1 EC:88:92:61:E9:5F btdisconnected /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- -- -- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1448555/+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 1491844] [NEW] Network Manager fails to connect to VPN (AnyConnect) - [vpn-mana ger/nm-vpn-connection.c:1770] get_secrets_cb(): Failed to request VPN secrets #2 : (6) No agents w
Public bug reported: Installed vpnc established vpn connection successfully after restart, the vpn connection cannot be established any more mbr NetworkManager[17397]: [1441285066.578727] [vpn-mana ger/nm-vpn-connection.c:1770] get_secrets_cb(): Failed to request VPN secrets #2 : (6) No agents were available for this request. Workaround: rm .gconf/apps/nm-applet logout/login connect to VPN works This surely cannot be a normal procedure ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu15.2 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.17.2-0ubuntu1.4 Architecture: amd64 CurrentDesktop: Unity Date: Thu Sep 3 15:10:53 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-05-17 (838 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64+mac (20130424) IpRoute: default via 10.1.0.254 dev wlan0 proto static metric 400 10.0.0.0/8 dev wlan0 proto kernel scope link src 10.1.0.104 169.254.0.0/16 dev wlan0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-04-25 (131 days ago) nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug package-from-proposed third-party-packages vivid ** Summary changed: - Network Manager fails to connect to VPN (AnyConnect) - mbr NetworkManager[17397]: [1441285066.578727] [vpn-mana ger/nm-vpn-connection.c:1770] get_secrets_cb(): Failed to request VPN secrets #2 : (6) No agents were available for this request + Network Manager fails to connect to VPN (AnyConnect) - [vpn-mana ger/nm-vpn-connection.c:1770] get_secrets_cb(): Failed to request VPN secrets #2 : (6) No agents were available for this request -- 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/1491844 Title: Network Manager fails to connect to VPN (AnyConnect) - [vpn-mana ger /nm-vpn-connection.c:1770] get_secrets_cb(): Failed to request VPN secrets #2 : (6) No agents were available for this request Status in network-manager package in Ubuntu: New Bug description: Installed vpnc established vpn connection successfully after restart, the vpn connection cannot be established any more mbr NetworkManager[17397]: [1441285066.578727] [vpn-mana ger/nm-vpn-connection.c:1770] get_secrets_cb(): Failed to request VPN secrets #2 : (6) No agents were available for this request. Workaround: rm .gconf/apps/nm-applet logout/login connect to VPN works This surely cannot be a normal procedure ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu15.2 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.17.2-0ubuntu1.4 Architecture: amd64 CurrentDesktop: Unity Date: Thu Sep 3 15:10:53 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-05-17 (838 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64+mac (20130424) IpRoute: default via 10.1.0.254 dev wlan0 proto static metric 400 10.0.0.0/8 dev wlan0 proto kernel scope link src 10.1.0.104 169.254.0.0/16 dev wlan0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-04-25 (131 days ago) nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1491844/+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 1489461] [NEW] Network Manager looses connection and refuses to reconnect
Public bug reported: Repetitively with new versions this issue arises: Network Manager looses the connection. The list of SSIDs and APs includes a subset of APs that were there before the disconnect. Reconnection results in a permanent connection establishing effort with no final success. Restarting the NetworkManager service does not bring up the missing SSIDs and APs nor does it allow to reconnect. Only a reboot remedies this situation. Why is it repetitively: I haven't found the errors I previously reported on this edition but I did. Thus to me this seems like regression again. ** 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/1489461 Title: Network Manager looses connection and refuses to reconnect Status in network-manager package in Ubuntu: New Bug description: Repetitively with new versions this issue arises: Network Manager looses the connection. The list of SSIDs and APs includes a subset of APs that were there before the disconnect. Reconnection results in a permanent connection establishing effort with no final success. Restarting the NetworkManager service does not bring up the missing SSIDs and APs nor does it allow to reconnect. Only a reboot remedies this situation. Why is it repetitively: I haven't found the errors I previously reported on this edition but I did. Thus to me this seems like regression again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1489461/+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 1448555] Re: network-manager does not autoconnect to wifi network after resume from suspend
In kernel 3.19.0-26 the connection was reestablished sometimes (could not reproduce a pattern) in kernel 3.19.0-27 (updated today) the situation is as initially described. The connection does not get reestablished after a resume, regardless of wheter a. I previously disconnect and reconnect in the NM-applet b. restart service NetworkManager The log files demonstrate complete different behaviour on resume, restart of the service or reconnect from the applet. I cannot see any similarities at all. Should I expect some reuse of code and behaviour or is this a complete misconception? -- 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/1448555 Title: network-manager does not autoconnect to wifi network after resume from suspend Status in network-manager package in Ubuntu: Confirmed Bug description: After upgrading to 15.04 network manager does not reconnect to the wifi network after resuming from a suspend to memory. Workaround: disable and re-enable wireless network -> connects immediately ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu15 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 25 23:53:54 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-05-17 (708 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64+mac (20130424) IpRoute: default via 10.1.0.254 dev wlan0 proto static metric 1024 10.0.0.0/8 dev wlan0 proto kernel scope link src 10.1.0.103 169.254.0.0/16 dev wlan0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-04-25 (0 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlan0 wifi connected /org/freedesktop/NetworkManager/Devices/1 rsb_hs d8793959-2da1-4dc6-85ad-2dcf9e36e64b /org/freedesktop/NetworkManager/ActiveConnection/1 EC:88:92:61:E9:5F btdisconnected /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- -- -- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1448555/+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 1448555] Re: network-manager does not autoconnect to wifi network after resume from suspend
Additional observation: Somehow upgrading the kernel did not happen. So the kernel stayed 3.19.0.15 for a while. Other upgrades went fine. So for the last few days, I did not observe the phenomenon on this particular machine. (Others, where the kernel war upgraded to 3.19.0.20 had the issue constantly) After upgrading to 3.19.0.20 on this machine, the behaviour / issue reappeared. here is the syslog. Mind 09:53:21 where NetworkManager deactivates for no reason. ... Jun 4 09:53:05 mbr kernel: [13615.956552] bridge-wlan0: down Jun 4 09:53:05 mbr kernel: [13615.956559] bridge-wlan0: detached Jun 4 09:53:05 mbr kernel: [13615.956633] done. Jun 4 09:53:05 mbr kernel: [13615.956642] video LNXVIDEO:00: Restoring backlight state Jun 4 09:53:05 mbr kernel: [13615.958066] cfg80211: World regulatory domain updated: Jun 4 09:53:05 mbr kernel: [13615.958069] cfg80211: DFS Master region: unset Jun 4 09:53:05 mbr kernel: [13615.958070] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) Jun 4 09:53:05 mbr kernel: [13615.958072] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm), (N/A) Jun 4 09:53:05 mbr kernel: [13615.958074] cfg80211: (2457000 KHz - 2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm), (N/A) Jun 4 09:53:05 mbr kernel: [13615.958075] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm), (N/A) Jun 4 09:53:05 mbr kernel: [13615.958077] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 2000 mBm), (N/A) Jun 4 09:53:05 mbr kernel: [13615.958078] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm), (N/A) Jun 4 09:53:05 mbr NetworkManager[922]: wake requested (sleeping: yes enabled: yes) Jun 4 09:53:05 mbr NetworkManager[922]: waking up... Jun 4 09:53:05 mbr NetworkManager[922]: (wlan0): device state change: activated -> unmanaged (reason 'sleeping') [100 10 37] Jun 4 09:53:05 mbr NetworkManager[922]: (wlan0): deactivating device (reason 'sleeping') [37] Jun 4 09:53:05 mbr systemd[1]: Started Run anacron jobs. Jun 4 09:53:05 mbr systemd[1]: Starting Run anacron jobs... Jun 4 09:53:05 mbr anacron[5425]: Anacron 2.3 started on 2015-06-04 Jun 4 09:53:05 mbr anacron[5425]: Will run job `cron.daily' in 5 min. Jun 4 09:53:05 mbr anacron[5425]: Jobs will be executed sequentially Jun 4 09:53:06 mbr wpa_supplicant[1134]: wlan0: CTRL-EVENT-SCAN-STARTED Jun 4 09:53:06 mbr NetworkManager[922]: (wlan0): canceled DHCP transaction, DHCP client pid 4639 Jun 4 09:53:06 mbr avahi-daemon[945]: Withdrawing address record for fe80::1610:9fff:fed2:25f7 on wlan0. Jun 4 09:53:06 mbr avahi-daemon[945]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::1610:9fff:fed2:25f7. Jun 4 09:53:06 mbr avahi-daemon[945]: Interface wlan0.IPv6 no longer relevant for mDNS. Jun 4 09:53:06 mbr vmnet-natd: RTM_DELADDR: index:2, addr:10.1.0.103 Jun 4 09:53:06 mbr avahi-daemon[945]: Withdrawing address record for 10.1.0.103 on wlan0. Jun 4 09:53:06 mbr avahi-daemon[945]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 10.1.0.103. Jun 4 09:53:06 mbr avahi-daemon[945]: Interface wlan0.IPv4 no longer relevant for mDNS. Jun 4 09:53:06 mbr NetworkManager[922]: Writing DNS information to /sbin/resolvconf Jun 4 09:53:06 mbr dnsmasq[1359]: setting upstream servers from DBus Jun 4 09:53:06 mbr gnome-session[2464]: (deja-dup-monitor:3120): GLib-CRITICAL **: Source ID 198 was not found when attempting to remove it Jun 4 09:53:06 mbr whoopsie[909]: [09:53:06] Cannot reach: https://daisy.ubuntu.com Jun 4 09:53:06 mbr NetworkManager[922]: NetworkManager state is now CONNECTED_LOCAL Jun 4 09:53:06 mbr vmnet-natd: RTM_NEWLINK: name:wlan0 index:2 flags:0x1002 Jun 4 09:53:06 mbr vmnetBridge: RTM_NEWLINK: name:wlan0 index:2 flags:0x1002 Jun 4 09:53:06 mbr NetworkManager[922]: NetworkManager state is now DISCONNECTED Jun 4 09:53:06 mbr kernel: [13616.082194] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready Jun 4 09:53:06 mbr kernel: [13616.156323] userif-3: sent link down event. Jun 4 09:53:06 mbr kernel: [13616.156325] userif-3: sent link up event. Jun 4 09:53:06 mbr NetworkManager[922]: (wlan0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] Jun 4 09:53:06 mbr vmnet-natd: RTM_NEWLINK: name:wlan0 index:2 flags:0x00011003 Jun 4 09:53:06 mbr vmnetBridge: RTM_NEWLINK: name:wlan0 index:2 flags:0x00011003 Jun 4 09:53:06 mbr NetworkManager[922]: (wlan0): preparing device Jun 4 09:53:06 mbr NetworkManager[922]: (EC:88:92:61:E9:5F): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] Jun 4 09:53:06 mbr dbus[991]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' Jun 4 09:53:06 mbr systemd[1]: Starting Network Manager Script Dispatcher Service... Jun 4 09:53:06 mbr NetworkManager[922]: (EC:88:92:6
[Touch-packages] [Bug 1448555] Re: network-manager does not autoconnect to wifi network after resume from suspend
Just found this in /var/log/pm-suspend.log: Running hook /usr/lib/pm-utils/sleep.d/60_wpa_supplicant suspend suspend: Failed to connect to non-global ctrl_ifname: (null) error: No such file or directory /usr/lib/pm-utils/sleep.d/60_wpa_supplicant suspend suspend: success. full log attached. ** Attachment added: "pm-suspend.log" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1448555/+attachment/4384934/+files/pm-suspend.log -- 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/1448555 Title: network-manager does not autoconnect to wifi network after resume from suspend Status in network-manager package in Ubuntu: Confirmed Bug description: After upgrading to 15.04 network manager does not reconnect to the wifi network after resuming from a suspend to memory. Workaround: disable and re-enable wireless network -> connects immediately ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu15 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 25 23:53:54 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-05-17 (708 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64+mac (20130424) IpRoute: default via 10.1.0.254 dev wlan0 proto static metric 1024 10.0.0.0/8 dev wlan0 proto kernel scope link src 10.1.0.103 169.254.0.0/16 dev wlan0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-04-25 (0 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlan0 wifi connected /org/freedesktop/NetworkManager/Devices/1 rsb_hs d8793959-2da1-4dc6-85ad-2dcf9e36e64b /org/freedesktop/NetworkManager/ActiveConnection/1 EC:88:92:61:E9:5F btdisconnected /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- -- -- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1448555/+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 1448555] [NEW] network-manager does not autoconnect to wifi network after resume from suspend
Public bug reported: After upgrading to 15.04 network manager does not reconnect to the wifi network after resuming from a suspend to memory. Workaround: disable and re-enable wireless network -> connects immediately ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu15 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 25 23:53:54 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-05-17 (708 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64+mac (20130424) IpRoute: default via 10.1.0.254 dev wlan0 proto static metric 1024 10.0.0.0/8 dev wlan0 proto kernel scope link src 10.1.0.103 169.254.0.0/16 dev wlan0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-04-25 (0 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlan0 wifi connected /org/freedesktop/NetworkManager/Devices/1 rsb_hs d8793959-2da1-4dc6-85ad-2dcf9e36e64b /org/freedesktop/NetworkManager/ActiveConnection/1 EC:88:92:61:E9:5F btdisconnected /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- -- -- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- 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/1448555 Title: network-manager does not autoconnect to wifi network after resume from suspend Status in network-manager package in Ubuntu: New Bug description: After upgrading to 15.04 network manager does not reconnect to the wifi network after resuming from a suspend to memory. Workaround: disable and re-enable wireless network -> connects immediately ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu15 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 25 23:53:54 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-05-17 (708 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64+mac (20130424) IpRoute: default via 10.1.0.254 dev wlan0 proto static metric 1024 10.0.0.0/8 dev wlan0 proto kernel scope link src 10.1.0.103 169.254.0.0/16 dev wlan0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-04-25 (0 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlan0 wifi connected /org/freedesktop/NetworkManager/Devices/1 rsb_hs d8793959-2da1-4dc6-85ad-2dcf9e36e64b /org/freedesktop/NetworkManager/ActiveConnection/1 EC:88:92:61:E9:5F btdisconnected /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- -- -- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1448555/+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 1443985] [NEW] Apple macig mouse does not pair with Ubuntu
Public bug reported: Same phenomenon as previously: Connection to Apple magic mouse fails. In the pairing window, the device flickers. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: bluez 4.101-0ubuntu25 ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3 Uname: Linux 3.19.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17-0ubuntu2 Architecture: amd64 CasperVersion: 1.359 CurrentDesktop: Unity Date: Tue Apr 14 14:28:33 2015 InterestingModules: rfcomm bnep btusb bluetooth LiveMediaBuild: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150414) MachineType: Apple Inc. MacBookPro10,1 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=de SourcePackage: bluez UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP101.88Z.00EE.B03.1212211437 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-C3EC7CD22292981F dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro10,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-C3EC7CD22292981F dmi.modalias: dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B03.1212211437:bd12/21/2012:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F: dmi.product.name: MacBookPro10,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. hciconfig: hci0: Type: BR/EDR Bus: USB BD Address: 14:10:9F:D2:25:F8 ACL MTU: 1021:6 SCO MTU: 64:1 UP RUNNING PSCAN RX bytes:7000 acl:15 sco:0 events:318 errors:0 TX bytes:2665 acl:15 sco:0 commands:155 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- 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/1443985 Title: Apple macig mouse does not pair with Ubuntu Status in bluez package in Ubuntu: New Bug description: Same phenomenon as previously: Connection to Apple magic mouse fails. In the pairing window, the device flickers. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: bluez 4.101-0ubuntu25 ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3 Uname: Linux 3.19.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17-0ubuntu2 Architecture: amd64 CasperVersion: 1.359 CurrentDesktop: Unity Date: Tue Apr 14 14:28:33 2015 InterestingModules: rfcomm bnep btusb bluetooth LiveMediaBuild: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150414) MachineType: Apple Inc. MacBookPro10,1 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=de SourcePackage: bluez UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP101.88Z.00EE.B03.1212211437 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-C3EC7CD22292981F dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro10,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-C3EC7CD22292981F dmi.modalias: dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B03.1212211437:bd12/21/2012:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F: dmi.product.name: MacBookPro10,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 14:10:9F:D2:25:F8 ACL MTU: 1021:6 SCO MTU: 64:1 UP RUNNING PSCAN RX bytes:7000 acl:15 sco:0 events:318 errors:0 TX bytes:2665 acl:15 sco:0 commands:155 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1443985/+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 1438628] [NEW] vpn service fails
Public bug reported: Trying to connect via VPN (pptp) fails: Mar 31 12:25:39 mbr NetworkManager[1002]: Starting VPN service 'pptp'... Mar 31 12:25:39 mbr NetworkManager[1002]: VPN service 'pptp' started (org.freedesktop.NetworkManager.pptp), PID 4143 Mar 31 12:25:39 mbr NetworkManager[1002]: VPN service 'pptp' appeared; activating connections Mar 31 12:25:39 mbr NetworkManager[1002]: [1427797539.109043] [nm-vpn-connection.c:1374] get_secrets_cb(): Failed to request VPN secrets #2: (6) No agents were available for this request. Mar 31 12:25:39 mbr NetworkManager[1002]: Policy set 'rsb_hs' (wlan0) as default for IPv4 routing and DNS. Mar 31 12:25:43 mbr NetworkManager[1002]: VPN service 'pptp' disappeared Workaround (as previously suggested): remove ~/.gconf/apps/nm-applet/%gconf.xml logout / login connection works ... until the next reboot System: Ubuntu 14.10 (64bit) Linux mbr 3.16.0-34-generic #45-Ubuntu SMP Mon Mar 23 17:21:27 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Not quite similar to #1297849 but same effect. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: network-manager 0.9.8.8-0ubuntu28 ProcVersionSignature: Ubuntu 3.16.0-34.45-generic 3.16.7-ckt8 Uname: Linux 3.16.0-34-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 Date: Tue Mar 31 12:27:16 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-05-17 (682 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64+mac (20130424) IpRoute: default via 10.1.0.254 dev wlan0 proto static 10.0.0.0/8 dev wlan0 proto kernel scope link src 10.1.0.103 metric 9 192.168.97.0/24 dev vmnet8 proto kernel scope link src 192.168.97.1 192.168.204.0/24 dev vmnet1 proto kernel scope link src 192.168.204.1 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH EC:88:92:61:E9:5F bluetooth disconnected /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled disabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic -- 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/1438628 Title: vpn service fails Status in network-manager package in Ubuntu: New Bug description: Trying to connect via VPN (pptp) fails: Mar 31 12:25:39 mbr NetworkManager[1002]: Starting VPN service 'pptp'... Mar 31 12:25:39 mbr NetworkManager[1002]: VPN service 'pptp' started (org.freedesktop.NetworkManager.pptp), PID 4143 Mar 31 12:25:39 mbr NetworkManager[1002]: VPN service 'pptp' appeared; activating connections Mar 31 12:25:39 mbr NetworkManager[1002]: [1427797539.109043] [nm-vpn-connection.c:1374] get_secrets_cb(): Failed to request VPN secrets #2: (6) No agents were available for this request. Mar 31 12:25:39 mbr NetworkManager[1002]: Policy set 'rsb_hs' (wlan0) as default for IPv4 routing and DNS. Mar 31 12:25:43 mbr NetworkManager[1002]: VPN service 'pptp' disappeared Workaround (as previously suggested): remove ~/.gconf/apps/nm-applet/%gconf.xml logout / login connection works ... until the next reboot System: Ubuntu 14.10 (64bit) Linux mbr 3.16.0-34-generic #45-Ubuntu SMP Mon Mar 23 17:21:27 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Not quite similar to #1297849 but same effect. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: network-manager 0.9.8.8-0ubuntu28 ProcVersionSignature: Ubuntu 3.16.0-34.45-generic 3.16.7-ckt8 Uname: Linux 3.16.0-34-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 Date: Tue Mar 31 12:27:16 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-05-17 (682 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64+mac (20130424) IpRoute: default via 10.1.0.254 dev wlan0 proto static 10.0.0.0/8 dev wlan0 proto kernel scope link src 10.1.0.103 metric 9 192.168.97.0/24 dev vmnet8 proto kernel scope link src 192.168.97.1 192.168.204.0/24 dev vmnet1 proto kernel scope link src 192.168.204.1 NetworkManager.state: [main] NetworkingEnabled=true Wi
[Touch-packages] [Bug 1399888] [NEW] Wireless network connection terminates and won't reconnect
Public bug reported: On: Linux x 3.16.0-25-generic #33-Ubuntu SMP Tue Nov 4 12:06:54 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Wireless connections terminate without obvious reason. A reconnect is not possible. Every now and then (every second day) the network connection drops. The network indicator shows no signal strenght (empty icon) The correct connection is selected, a wealth of other SSIDs are in the list. A reconnect opens up the password dialog (which is an indication that the old error was reintroduced into the code). I reported this bug several times. The reason at the time was that reconnection would try to fetch the encrypted password and reencrypt it leading to a wrong password. There is a workaround: Disabling and Enabling the network connection reconnects correctly. In the code (as I analyzed then), this is due to the fact that the password from searing is taken as is and forwarded to the authentication code (not reencrypted). The connection gets established again. This issue did not occur in 12.04 and 12.10 (due to less connection problems or due to a fix is beyond me, I simple confirmed there were no connection aborts). It reappeared in 13.x and now is back as an annoyance. The error numbers then were around 460.000 - 490.000 as far is I remember (I have deleted bug reports I considered solved). I observed this issue on any Ubuntu machine. I also observed that the list of SSIDs is extremely long when this incident arises (approx. 15 - 20). Maybe a storm of SSID broadcasts is the basic cause but I have not done any research beyond what I described here. Hope this gets fixed for good now. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: wpasupplicant 2.1-0ubuntu4 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Sat Dec 6 10:27:42 2014 InstallationDate: Installed on 2013-05-17 (567 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64+mac (20130424) SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: wpa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1399888 Title: Wireless network connection terminates and won't reconnect Status in wpa package in Ubuntu: New Bug description: On: Linux x 3.16.0-25-generic #33-Ubuntu SMP Tue Nov 4 12:06:54 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Wireless connections terminate without obvious reason. A reconnect is not possible. Every now and then (every second day) the network connection drops. The network indicator shows no signal strenght (empty icon) The correct connection is selected, a wealth of other SSIDs are in the list. A reconnect opens up the password dialog (which is an indication that the old error was reintroduced into the code). I reported this bug several times. The reason at the time was that reconnection would try to fetch the encrypted password and reencrypt it leading to a wrong password. There is a workaround: Disabling and Enabling the network connection reconnects correctly. In the code (as I analyzed then), this is due to the fact that the password from searing is taken as is and forwarded to the authentication code (not reencrypted). The connection gets established again. This issue did not occur in 12.04 and 12.10 (due to less connection problems or due to a fix is beyond me, I simple confirmed there were no connection aborts). It reappeared in 13.x and now is back as an annoyance. The error numbers then were around 460.000 - 490.000 as far is I remember (I have deleted bug reports I considered solved). I observed this issue on any Ubuntu machine. I also observed that the list of SSIDs is extremely long when this incident arises (approx. 15 - 20). Maybe a storm of SSID broadcasts is the basic cause but I have not done any research beyond what I described here. Hope this gets fixed for good now. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: wpasupplicant 2.1-0ubuntu4 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Sat Dec 6 10:27:42 2014 InstallationDate: Installed on 2013-05-17 (567 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64+mac (20130424) SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1399888/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages
[Touch-packages] [Bug 1367636] [NEW] Network connection breaks down regularly
Public bug reported: Using WiFi on all my notebooks the network connection terminates at random (no signal, no connection). Reconnecting to the AP does not work (connection efforts take endlessly). Disabling and Re-enabling Wireless Network works immediately. This used to be an issue on a Macbook Pro Retina 15" at first, later the MBPR13" had the same issue and finally my old HP 8510w does the same. No regular events in the neighborhood (APs comming up or going down) or in PC workload. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager 0.9.8.8-0ubuntu7 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CurrentDesktop: Unity Date: Wed Sep 10 10:37:33 2014 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-05-17 (480 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64+mac (20130424) IpRoute: default via 10.1.0.254 dev wlan0 proto static 10.0.0.0/8 dev wlan0 proto kernel scope link src 10.1.0.103 metric 9 192.168.97.0/24 dev vmnet8 proto kernel scope link src 192.168.97.1 192.168.204.0/24 dev vmnet1 proto kernel scope link src 192.168.204.1 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to trusty on 2014-04-20 (143 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled enabled ** Affects: network-manager (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 network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1367636 Title: Network connection breaks down regularly Status in “network-manager” package in Ubuntu: New Bug description: Using WiFi on all my notebooks the network connection terminates at random (no signal, no connection). Reconnecting to the AP does not work (connection efforts take endlessly). Disabling and Re-enabling Wireless Network works immediately. This used to be an issue on a Macbook Pro Retina 15" at first, later the MBPR13" had the same issue and finally my old HP 8510w does the same. No regular events in the neighborhood (APs comming up or going down) or in PC workload. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager 0.9.8.8-0ubuntu7 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CurrentDesktop: Unity Date: Wed Sep 10 10:37:33 2014 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-05-17 (480 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64+mac (20130424) IpRoute: default via 10.1.0.254 dev wlan0 proto static 10.0.0.0/8 dev wlan0 proto kernel scope link src 10.1.0.103 metric 9 192.168.97.0/24 dev vmnet8 proto kernel scope link src 192.168.97.1 192.168.204.0/24 dev vmnet1 proto kernel scope link src 192.168.204.1 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to trusty on 2014-04-20 (143 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1367636/+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
