[Touch-packages] [Bug 1711048] [NEW] package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: le paquet bsdutils n'est pas prêt pour la configuration configuration impossible (état actuel « half-i
Public bug reported: ce bug est signalé au démarrage ProblemType: Package DistroRelease: Ubuntu 17.04 Package: bsdutils 1:2.29-1ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 AptOrdering: bsdutils:amd64: Configure libgd3:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Wed Aug 16 08:04:58 2017 DpkgTerminalLog: dpkg: erreur de traitement du paquet bsdutils (--configure) : le paquet bsdutils n'est pas prêt pour la configuration configuration impossible (état actuel « half-installed ») ErrorMessage: le paquet bsdutils n'est pas prêt pour la configuration configuration impossible (état actuel « half-installed ») InstallationDate: Installed on 2017-03-19 (149 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: util-linux Title: package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: le paquet bsdutils n'est pas prêt pour la configuration configuration impossible (état actuel « half-installed ») UpgradeStatus: Upgraded to zesty on 2017-05-03 (104 days ago) ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1711048 Title: package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: le paquet bsdutils n'est pas prêt pour la configuration configuration impossible (état actuel « half-installed ») Status in util-linux package in Ubuntu: New Bug description: ce bug est signalé au démarrage ProblemType: Package DistroRelease: Ubuntu 17.04 Package: bsdutils 1:2.29-1ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 AptOrdering: bsdutils:amd64: Configure libgd3:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Wed Aug 16 08:04:58 2017 DpkgTerminalLog: dpkg: erreur de traitement du paquet bsdutils (--configure) : le paquet bsdutils n'est pas prêt pour la configuration configuration impossible (état actuel « half-installed ») ErrorMessage: le paquet bsdutils n'est pas prêt pour la configuration configuration impossible (état actuel « half-installed ») InstallationDate: Installed on 2017-03-19 (149 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: util-linux Title: package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: le paquet bsdutils n'est pas prêt pour la configuration configuration impossible (état actuel « half-installed ») UpgradeStatus: Upgraded to zesty on 2017-05-03 (104 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1711048/+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 1711037] [NEW] Screen intermittently flickers
Public bug reported: Using both my nvidia and radeon cards my 2560x1600 display flickers. The screen is fine in Windows. This only seems to happen when I run the open source driver. Additionally, if I drop that screen to a lower 16:10 resolution like 1920x1200 it goes black. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CompositorRunning: None CurrentDesktop: GNOME Date: Tue Aug 15 22:32:41 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.11.0-10-generic, x86_64: installed bbswitch, 0.8, 4.11.0-13-generic, x86_64: installed nvidia-384, 384.59, 4.11.0-10-generic, x86_64: installed nvidia-384, 384.59, 4.11.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Polaris11] [1002:67ff] (rev cf) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Baffin [Polaris11] [1462:8a91] InstallationDate: Installed on 2017-08-07 (9 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170805) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-13-generic root=UUID=adb3a033-d515-4dfb-97d6-7c0ef12879cf ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1807 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P7P55D DELUXE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1807:bd07/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55DDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.82-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.1.4-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.1.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu2 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 xserver.bootTime: Mon Aug 14 07:40:51 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.3-1ubuntu2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful reproducible ubuntu wayland-session -- 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/1711037 Title: Screen intermittently flickers Status in xorg package in Ubuntu: New Bug description: Using both my nvidia and radeon cards my 2560x1600 display flickers. The screen is fine in Windows. This only seems to happen when I run the open source driver. Additionally, if I drop that screen to a lower 16:10 resolution like 1920x1200 it goes black. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CompositorRunning: None CurrentDesktop: GNOME Date: Tue Aug 15 22:32:41 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.11.0-10-generic, x86_64: installed bbswitch, 0.8, 4.11.0-13-generic, x86_64: installed nvidia-384, 384.59, 4.11.0-10-generic, x86_64: installed nvidia-384, 384.59, 4.11.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Polaris11] [1002:67ff] (rev cf) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Baffin [Polaris11] [1462:8a91] InstallationDate: Installed on 2017-08-07 (9 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170805) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-13-generic root=UUID=adb3a033-d515-4dfb-97d6-7c0ef12879cf ro quiet splash vt.handoff=7 SourcePackage: xorg S
[Touch-packages] [Bug 1711041] [NEW] package libasound2-plugins:i386 1.1.0-0ubuntu1 failed to install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert
Public bug reported: info ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libasound2-plugins:i386 1.1.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Wed Aug 16 06:58:58 2017 ErrorMessage: Abhängigkeitsprobleme - verbleibt unkonfiguriert InstallationDate: Installed on 2017-05-25 (82 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: alsa-plugins Title: package libasound2-plugins:i386 1.1.0-0ubuntu1 failed to install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: alsa-plugins (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1711041 Title: package libasound2-plugins:i386 1.1.0-0ubuntu1 failed to install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert Status in alsa-plugins package in Ubuntu: New Bug description: info ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libasound2-plugins:i386 1.1.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Wed Aug 16 06:58:58 2017 ErrorMessage: Abhängigkeitsprobleme - verbleibt unkonfiguriert InstallationDate: Installed on 2017-05-25 (82 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: alsa-plugins Title: package libasound2-plugins:i386 1.1.0-0ubuntu1 failed to install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-plugins/+bug/1711041/+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 1710941] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- 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/1710941 Title: Bluetooth stopped working after kernel update 4.4.0-91 Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: Bluetooth connection to Bose Soundlink II have been fine for years. Applied a few new updates in the last day or two --- system was generally up to date, I don't often wait more than a week or so --- and now I can no longer connect. Removed the device and re-paired just fine, although the speaker did not connect as it usually does after the pairing (i.e., it stayed in pairing mode). Messages in syslog: Aug 15 20:32:07 n1 bluetoothd[1075]: connect error: Connection refused (111) Aug 15 20:32:07 n1 bluetoothd[1075]: GLib: Source ID 276 was not found when attempting to remove it Aug 15 20:32:11 n1 bluetoothd[1075]: connect error: Connection refused (111) Aug 15 20:32:42 n1 bluetoothd[1075]: connect error: Connection refused (111) Aug 15 20:32:42 n1 bluetoothd[1075]: GLib: Source ID 287 was not found when attempting to remove it Aug 15 20:32:46 n1 bluetoothd[1075]: connect error: Connection refused (111) Aug 15 20:33:07 n1 bluetoothd[1075]: connect error: Host is down (112) Aug 15 20:33:07 n1 bluetoothd[1075]: GLib: Source ID 305 was not found when attempting to remove it ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-91.114-generic 4.4.76 Uname: Linux 4.4.0-91-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Tue Aug 15 20:34:34 2017 InstallationDate: Installed on 2015-12-26 (597 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) InterestingModules: rfcomm bnep btusb bluetooth ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-91-generic root=UUID=5950fbba-cde1-49ac-a918-04e517894c57 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to xenial on 2017-02-28 (168 days ago) dmi.bios.date: 01/18/2017 dmi.bios.vendor: Intel Corporation dmi.bios.version: RYBDWi35.86A.0362.2017.0118.0940 dmi.board.name: NUC5i5RYB dmi.board.vendor: Intel Corporation dmi.board.version: H40999-504 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorporation:bvrRYBDWi35.86A.0362.2017.0118.0940:bd01/18/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5i5RYB:rvrH40999-504:cvn:ct3:cvr: hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: DC:53:60:97:55:17 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:6896 acl:46 sco:0 events:294 errors:0 TX bytes:4254 acl:32 sco:0 commands:156 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2015-12-29T07:24:08.439240 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1710941/+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 1711031] [NEW] package libqt5widgets5:amd64 5.5.1+dfsg-16ubuntu7.5 failed to install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert
Public bug reported: Update / Upgrade not possible ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libqt5widgets5:amd64 5.5.1+dfsg-16ubuntu7.5 ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Tue Aug 15 06:04:47 2017 ErrorMessage: Abhängigkeitsprobleme - verbleibt unkonfiguriert InstallationDate: Installed on 2017-02-20 (176 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: qtbase-opensource-src Title: package libqt5widgets5:amd64 5.5.1+dfsg-16ubuntu7.5 failed to install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1711031 Title: package libqt5widgets5:amd64 5.5.1+dfsg-16ubuntu7.5 failed to install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert Status in qtbase-opensource-src package in Ubuntu: New Bug description: Update / Upgrade not possible ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libqt5widgets5:amd64 5.5.1+dfsg-16ubuntu7.5 ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Tue Aug 15 06:04:47 2017 ErrorMessage: Abhängigkeitsprobleme - verbleibt unkonfiguriert InstallationDate: Installed on 2017-02-20 (176 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: qtbase-opensource-src Title: package libqt5widgets5:amd64 5.5.1+dfsg-16ubuntu7.5 failed to install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1711031/+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 1710941] Re: Bluetooth stopped working after kernel update 4.4.0-91
** Summary changed: - Bluetooth stopped working after update + Bluetooth stopped working after kernel update 4.4.0-91 ** Changed in: linux (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1710941 Title: Bluetooth stopped working after kernel update 4.4.0-91 Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: New Bug description: Bluetooth connection to Bose Soundlink II have been fine for years. Applied a few new updates in the last day or two --- system was generally up to date, I don't often wait more than a week or so --- and now I can no longer connect. Removed the device and re-paired just fine, although the speaker did not connect as it usually does after the pairing (i.e., it stayed in pairing mode). Messages in syslog: Aug 15 20:32:07 n1 bluetoothd[1075]: connect error: Connection refused (111) Aug 15 20:32:07 n1 bluetoothd[1075]: GLib: Source ID 276 was not found when attempting to remove it Aug 15 20:32:11 n1 bluetoothd[1075]: connect error: Connection refused (111) Aug 15 20:32:42 n1 bluetoothd[1075]: connect error: Connection refused (111) Aug 15 20:32:42 n1 bluetoothd[1075]: GLib: Source ID 287 was not found when attempting to remove it Aug 15 20:32:46 n1 bluetoothd[1075]: connect error: Connection refused (111) Aug 15 20:33:07 n1 bluetoothd[1075]: connect error: Host is down (112) Aug 15 20:33:07 n1 bluetoothd[1075]: GLib: Source ID 305 was not found when attempting to remove it ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-91.114-generic 4.4.76 Uname: Linux 4.4.0-91-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Tue Aug 15 20:34:34 2017 InstallationDate: Installed on 2015-12-26 (597 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) InterestingModules: rfcomm bnep btusb bluetooth ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-91-generic root=UUID=5950fbba-cde1-49ac-a918-04e517894c57 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to xenial on 2017-02-28 (168 days ago) dmi.bios.date: 01/18/2017 dmi.bios.vendor: Intel Corporation dmi.bios.version: RYBDWi35.86A.0362.2017.0118.0940 dmi.board.name: NUC5i5RYB dmi.board.vendor: Intel Corporation dmi.board.version: H40999-504 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorporation:bvrRYBDWi35.86A.0362.2017.0118.0940:bd01/18/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5i5RYB:rvrH40999-504:cvn:ct3:cvr: hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: DC:53:60:97:55:17 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:6896 acl:46 sco:0 events:294 errors:0 TX bytes:4254 acl:32 sco:0 commands:156 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2015-12-29T07:24:08.439240 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1710941/+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 1697153] Re: package libnl-genl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal
[Expired for libnl3 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: libnl3 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1697153 Title: package libnl-genl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installieren, bevor Sie die Konfiguration versuchen. Status in libnl3 package in Ubuntu: Expired Bug description: linux-libc-dev:amd64 (4.4.0-79.100) wird eingerichtet ... Fehler traten auf beim Bearbeiten von: libnl-genl-3-200:amd64 E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libnl-genl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 AptOrdering: libnl-3-200: Install libnl-3-200: Configure libnl-genl-3-200: Configure libnl-route-3-200: Configure NULL: ConfigurePending Architecture: amd64 Date: Sat Jun 10 10:30:10 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu7 libgcc1 1:6.0.1-0ubuntu1 libnl-3-200 3.2.27-1ubuntu0.16.04.1 ErrorMessage: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installieren, bevor Sie die Konfiguration versuchen. InstallationDate: Installed on 2016-04-03 (432 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: libnl3 Title: package libnl-genl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installieren, bevor Sie die Konfiguration versuchen. UpgradeStatus: Upgraded to xenial on 2016-11-29 (192 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1697153/+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 1710941] Re: Bluetooth stopped working after update
Thanks Daniel. Rolling back to kernel 4.4.0-87-generic #110-Ubuntu SMP seemed to fix the problem. Upgrading to 4.4.0-91 also seemed to cause other problems: My system started overheating, eventually slowed to a crawl (i.e., over a matter of minutes after each reboot slowed to the point of being unresponsive), and I saw 4 instances (one for each core, I presume) of kidle_interrupt, which I had never seen before. I notice that 4.4.0-91 is no longer showing up as an update in the repos for 16.04. For what it's worth, I also downgraded libgd3 to version 2.1.1-4build2, as it also upgraded around the same time as my recent kernel updates (-87 and -89, but I don't think I ever rebooted into -89). -- 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/1710941 Title: Bluetooth stopped working after update Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Incomplete Bug description: Bluetooth connection to Bose Soundlink II have been fine for years. Applied a few new updates in the last day or two --- system was generally up to date, I don't often wait more than a week or so --- and now I can no longer connect. Removed the device and re-paired just fine, although the speaker did not connect as it usually does after the pairing (i.e., it stayed in pairing mode). Messages in syslog: Aug 15 20:32:07 n1 bluetoothd[1075]: connect error: Connection refused (111) Aug 15 20:32:07 n1 bluetoothd[1075]: GLib: Source ID 276 was not found when attempting to remove it Aug 15 20:32:11 n1 bluetoothd[1075]: connect error: Connection refused (111) Aug 15 20:32:42 n1 bluetoothd[1075]: connect error: Connection refused (111) Aug 15 20:32:42 n1 bluetoothd[1075]: GLib: Source ID 287 was not found when attempting to remove it Aug 15 20:32:46 n1 bluetoothd[1075]: connect error: Connection refused (111) Aug 15 20:33:07 n1 bluetoothd[1075]: connect error: Host is down (112) Aug 15 20:33:07 n1 bluetoothd[1075]: GLib: Source ID 305 was not found when attempting to remove it ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-91.114-generic 4.4.76 Uname: Linux 4.4.0-91-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Tue Aug 15 20:34:34 2017 InstallationDate: Installed on 2015-12-26 (597 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) InterestingModules: rfcomm bnep btusb bluetooth ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-91-generic root=UUID=5950fbba-cde1-49ac-a918-04e517894c57 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to xenial on 2017-02-28 (168 days ago) dmi.bios.date: 01/18/2017 dmi.bios.vendor: Intel Corporation dmi.bios.version: RYBDWi35.86A.0362.2017.0118.0940 dmi.board.name: NUC5i5RYB dmi.board.vendor: Intel Corporation dmi.board.version: H40999-504 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorporation:bvrRYBDWi35.86A.0362.2017.0118.0940:bd01/18/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5i5RYB:rvrH40999-504:cvn:ct3:cvr: hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: DC:53:60:97:55:17 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:6896 acl:46 sco:0 events:294 errors:0 TX bytes:4254 acl:32 sco:0 commands:156 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2015-12-29T07:24:08.439240 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1710941/+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 1705800] Re: Error message appears at startup
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New => Confirmed -- 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/1705800 Title: Error message appears at startup Status in xorg package in Ubuntu: Confirmed Bug description: [ 2.231153] nouveau :01:00.0: bus: MMIO read of FAULT at 3e6684 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-27-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 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: Sat Jul 22 00:58:12 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GM107 [GeForce GTX 750 Ti] [10de:1380] (rev a2) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GM107 [GeForce GTX 750 Ti] [3842:3753] InstallationDate: Installed on 2017-07-21 (0 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-27-generic root=UUID=73638941-2a1f-4419-940b-ee07b54dce2b ro locale=pt_BR quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2101:bd12/02/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-M/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sat Jul 22 00:55:55 2017 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputMOSART Semi. 2.4G RF Keyboard & Mouse KEYBOARD, id 8 inputMOSART Semi. 2.4G RF Keyboard & Mouse KEYBOARD, id 9 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1705800/+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 153883] Re: control tab does not cycle through tabs in gedit
** Changed in: gtk Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/153883 Title: control tab does not cycle through tabs in gedit Status in GTK+: Invalid Status in One Hundred Papercuts: Invalid Status in gtk+2.0 package in Ubuntu: Triaged Bug description: Binary package hint: gedit Control+Tab does not cycle between multiple documents open in tabs in a single instance of gedit. This is a fairly standard binding for this key combination (e.g. Firefox, Windows MDI). ProblemType: Bug Architecture: i386 Date: Thu Oct 18 13:26:23 2007 DistroRelease: Ubuntu 7.10 ExecutablePath: /usr/bin/gedit NonfreeKernelModules: vmnet vmblock vmmon Package: gedit 2.20.1-0ubuntu3 PackageArchitecture: i386 ProcCmdline: gedit file:///home/degs/absent%20before%20-%202.txt ProcCwd: /home/degs ProcEnviron: PATH=/home/degs/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gedit Uname: Linux ming 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/153883/+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 1606078] Re: No sound with Ubuntu 16.04
I've also found that whenever i change the hdmi resolution back to one of the resolutions that the tv originally reported, the audio over hdmi begins to work again. if i again change to the the tv native resolution (set with xrandr), the audio over hdmi stops again. while the audio is not working, in the 'PulseAudio volume control' the output bars are still moving as thought sound is actually playing. full troubleshooting to date is listed here: https://ubuntuforums.org/showthread.php?t=2367418 ** This bug is no longer a duplicate of bug 1533343 No sound from internal speakers after boot with connected headphones -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1606078 Title: No sound with Ubuntu 16.04 Status in alsa-driver package in Ubuntu: Incomplete Bug description: After a fresh install of Ubuntu 16.04.1 on an LG S1 Express Dual laptop there was no sound from the speakers unless external speakers where hooked to the headphones socket. This applies to the Ubuntu Mate, Xubuntu and Lubuntu variants. This laptop was working fine for all previous releases up to 14.04. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bashar 3263 F pulseaudio CurrentDesktop: Unity Date: Mon Jul 25 01:51:19 2016 InstallationDate: Installed on 2016-07-24 (0 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bashar 3263 F pulseaudio Symptom_Jack: Line Out, Internal Symptom_Type: No sound at all Title: [S1-M401E1, Realtek ALC880, Line Out, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/16/2006 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: RKYWSF0B dmi.board.name: ROCKY dmi.board.vendor: LG Electronics dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LG Electronics dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrRKYWSF0B:bd02/16/2006:svnLGElectronics:pnS1-M401E1:pvrNotApplicable:rvnLGElectronics:rnROCKY:rvrNotApplicable:cvnLGElectronics:ct10:cvrN/A: dmi.product.name: S1-M401E1 dmi.product.version: Not Applicable dmi.sys.vendor: LG Electronics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1606078/+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 1704171] Re: WiFi connections unstable
Ok, I ran 16.04 since reporting this bug, then today installed 17.04 again (fresh install). This is still a major issue with stability of wifi connections. -- 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/1704171 Title: WiFi connections unstable Status in network-manager package in Ubuntu: New Bug description: I have 3 WiFi signals here, and use them all without issue most of the time. Since upgrading to 17.04 I have issues where my wifi will not connect to one of the other 2 signals, then also won't re-connect to the signal that was just in use. When this happens, I can do a 'restart' and it will connect just fine to any of the 3 signals. While it was failing a bit ago, I captured the syslog of whats going on and will include it below. Distributor ID: Ubuntu Description: Ubuntu 17.04 Release: 17.04 Codename: zesty Linux lisa-Inspiron-7720 4.10.0-28-generic #32-Ubuntu SMP Fri Jun 30 05:32:18 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.2717] device (wlp2s0): Activation: starting connection 'LisaN' (58396782-9fe4-4ce3-b0e6-f72df56c72d5) Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.2720] audit: op="connection-activate" uuid="58396782-9fe4-4ce3-b0e6-f72df56c72d5" name="LisaN" pid=1962 uid=1000 result="success" Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.2723] device (wlp2s0): state change: disconnected -> prepare (reason 'none') [30 40 0] Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.2725] manager: NetworkManager state is now CONNECTING Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.2779] device (wlp2s0): set-hw-addr: set-cloned MAC address to C4:D9:87:6E:9B:0F (permanent) Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [ 312.891148] iwlwifi :02:00.0: L1 Enabled - LTR Disabled Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [ 312.898132] iwlwifi :02:00.0: L1 Enabled - LTR Disabled Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [ 312.898220] iwlwifi :02:00.0: Radio type=0x2-0x1-0x0 Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [ 313.183332] iwlwifi :02:00.0: L1 Enabled - LTR Disabled Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [ 313.190314] iwlwifi :02:00.0: L1 Enabled - LTR Disabled Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [ 313.190403] iwlwifi :02:00.0: Radio type=0x2-0x1-0x0 Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [ 313.274573] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.6644] device (wlp2s0): supplicant interface state: inactive -> disabled Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.6649] device (wlp2s0): state change: prepare -> config (reason 'none') [40 50 0] Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.6654] device (wlp2s0): Activation: (wifi) access point 'LisaN' has security, but secrets are required. Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.6654] device (wlp2s0): state change: config -> need-auth (reason 'none') [50 60 0] Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.6728] device (wlp2s0): state change: need-auth -> prepare (reason 'none') [60 40 0] Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.6735] device (wlp2s0): state change: prepare -> config (reason 'none') [40 50 0] Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.6738] device (wlp2s0): Activation: (wifi) connection 'LisaN' has security, and secrets exist. No new secrets needed. Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.6739] Config: added 'ssid' value 'LisaN' Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.6740] Config: added 'scan_ssid' value '1' Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.6740] Config: added 'key_mgmt' value 'WPA-PSK' Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.6740] Config: added 'psk' value '' Jul 13 09:52:39 lisa-Inspiron-7720 nm-applet[1962]: Can't set a parent on widget which has a parent Jul 13 09:52:39 lisa-Inspiron-7720 nm-applet[1962]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Jul 13 09:52:39 lisa-Inspiron-7720 nm-applet[1962]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Jul 13 09:52:39 lisa-Inspiron-7720 nm-applet[1962]: Can't set a parent on widget which has a parent Jul 13 09:52:39 lisa-Inspiron-7720 nm-applet[1962]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Jul 13 09:52:39 lisa-Inspiron-7720 nm-applet[1962]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET
[Touch-packages] [Bug 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec
How awkward ... I ask you to remove the new status. Randomness. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1563110 Title: No sound on Asus e200ha, intel sst with cx2072x codec Status in ALSA driver: Unknown Status in alsa-driver package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Released Bug description: I've recently bought an Asus e200ha. Sound in this laptop doesn't work. The sound card is an intel sst with codec conexant cx2072x aplay -l: aplay: device_list:268: no soundcard found... in the sound setting there is a "Dummy output" --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 RelatedPackageVersions: linux-restricted-modules-3.19.0-32-generic N/A linux-backports-modules-3.19.0-32-generic N/A linux-firmware 1.127.16 Tags: rosa Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: E200HA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1563110/+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 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec
** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1563110 Title: No sound on Asus e200ha, intel sst with cx2072x codec Status in ALSA driver: Unknown Status in alsa-driver package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Released Bug description: I've recently bought an Asus e200ha. Sound in this laptop doesn't work. The sound card is an intel sst with codec conexant cx2072x aplay -l: aplay: device_list:268: no soundcard found... in the sound setting there is a "Dummy output" --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 RelatedPackageVersions: linux-restricted-modules-3.19.0-32-generic N/A linux-backports-modules-3.19.0-32-generic N/A linux-firmware 1.127.16 Tags: rosa Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: E200HA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1563110/+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 1710941] Re: Bluetooth stopped working after update
You can try previous kernel versions your system had prior to the problem, using this technique: https://wiki.ubuntu.com/RecoveryMode No need to select "recovery mode" but other older kernel versions should still be listed for you to use. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1710941 Title: Bluetooth stopped working after update Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Incomplete Bug description: Bluetooth connection to Bose Soundlink II have been fine for years. Applied a few new updates in the last day or two --- system was generally up to date, I don't often wait more than a week or so --- and now I can no longer connect. Removed the device and re-paired just fine, although the speaker did not connect as it usually does after the pairing (i.e., it stayed in pairing mode). Messages in syslog: Aug 15 20:32:07 n1 bluetoothd[1075]: connect error: Connection refused (111) Aug 15 20:32:07 n1 bluetoothd[1075]: GLib: Source ID 276 was not found when attempting to remove it Aug 15 20:32:11 n1 bluetoothd[1075]: connect error: Connection refused (111) Aug 15 20:32:42 n1 bluetoothd[1075]: connect error: Connection refused (111) Aug 15 20:32:42 n1 bluetoothd[1075]: GLib: Source ID 287 was not found when attempting to remove it Aug 15 20:32:46 n1 bluetoothd[1075]: connect error: Connection refused (111) Aug 15 20:33:07 n1 bluetoothd[1075]: connect error: Host is down (112) Aug 15 20:33:07 n1 bluetoothd[1075]: GLib: Source ID 305 was not found when attempting to remove it ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-91.114-generic 4.4.76 Uname: Linux 4.4.0-91-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Tue Aug 15 20:34:34 2017 InstallationDate: Installed on 2015-12-26 (597 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) InterestingModules: rfcomm bnep btusb bluetooth ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-91-generic root=UUID=5950fbba-cde1-49ac-a918-04e517894c57 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to xenial on 2017-02-28 (168 days ago) dmi.bios.date: 01/18/2017 dmi.bios.vendor: Intel Corporation dmi.bios.version: RYBDWi35.86A.0362.2017.0118.0940 dmi.board.name: NUC5i5RYB dmi.board.vendor: Intel Corporation dmi.board.version: H40999-504 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorporation:bvrRYBDWi35.86A.0362.2017.0118.0940:bd01/18/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5i5RYB:rvrH40999-504:cvn:ct3:cvr: hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: DC:53:60:97:55:17 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:6896 acl:46 sco:0 events:294 errors:0 TX bytes:4254 acl:32 sco:0 commands:156 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2015-12-29T07:24:08.439240 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1710941/+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 1710941] Re: Bluetooth stopped working after update
If you're using 16.04 then there have been no high-level bluetooth- related updates at all recently: bluez 5.37-0ubuntu5 ... 2016-03-09 pulseaudio 1:8.0-0ubuntu3.3 ... 2017-06-30 So if your system was working for the previous month or more then the problem is not caused by bluez or pulseaudio at least. You might want to assign it to "linux (Ubuntu)" in case it was caused by a recent kernel update like: linux 4.4.0-91.114 ... 2017-08-07 which sounds more likely by the date. ** Changed in: bluez (Ubuntu) Status: New => Invalid -- 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/1710941 Title: Bluetooth stopped working after update Status in bluez package in Ubuntu: Invalid Bug description: Bluetooth connection to Bose Soundlink II have been fine for years. Applied a few new updates in the last day or two --- system was generally up to date, I don't often wait more than a week or so --- and now I can no longer connect. Removed the device and re-paired just fine, although the speaker did not connect as it usually does after the pairing (i.e., it stayed in pairing mode). Messages in syslog: Aug 15 20:32:07 n1 bluetoothd[1075]: connect error: Connection refused (111) Aug 15 20:32:07 n1 bluetoothd[1075]: GLib: Source ID 276 was not found when attempting to remove it Aug 15 20:32:11 n1 bluetoothd[1075]: connect error: Connection refused (111) Aug 15 20:32:42 n1 bluetoothd[1075]: connect error: Connection refused (111) Aug 15 20:32:42 n1 bluetoothd[1075]: GLib: Source ID 287 was not found when attempting to remove it Aug 15 20:32:46 n1 bluetoothd[1075]: connect error: Connection refused (111) Aug 15 20:33:07 n1 bluetoothd[1075]: connect error: Host is down (112) Aug 15 20:33:07 n1 bluetoothd[1075]: GLib: Source ID 305 was not found when attempting to remove it ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-91.114-generic 4.4.76 Uname: Linux 4.4.0-91-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Tue Aug 15 20:34:34 2017 InstallationDate: Installed on 2015-12-26 (597 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) InterestingModules: rfcomm bnep btusb bluetooth ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-91-generic root=UUID=5950fbba-cde1-49ac-a918-04e517894c57 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to xenial on 2017-02-28 (168 days ago) dmi.bios.date: 01/18/2017 dmi.bios.vendor: Intel Corporation dmi.bios.version: RYBDWi35.86A.0362.2017.0118.0940 dmi.board.name: NUC5i5RYB dmi.board.vendor: Intel Corporation dmi.board.version: H40999-504 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorporation:bvrRYBDWi35.86A.0362.2017.0118.0940:bd01/18/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5i5RYB:rvrH40999-504:cvn:ct3:cvr: hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: DC:53:60:97:55:17 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:6896 acl:46 sco:0 events:294 errors:0 TX bytes:4254 acl:32 sco:0 commands:156 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2015-12-29T07:24:08.439240 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1710941/+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 1711011] [NEW] fsck.jfs missing from initramfs
Public bug reported: Detected machine type: 0101 command line: BOOT_IMAGE=/boot/vmlinux-4.11.0-13-generic root=UUID=8c6162e8-9bb1-4171-a901-30e001222a14 ro splash quiet Max number of cores passed to firmware: 2048 (NR_CPUS = 2048) Calling ibm,client-architecture-support... done memory layout at init: memory_limit : (16 MB aligned) alloc_bottom : 0762 alloc_top: 3000 alloc_top_hi : 00078000 rmo_top : 3000 ram_top : 00078000 instantiating rtas at 0x2fff... done prom_hold_cpus: skipped copying OF device tree... Building dt strings... Building dt structure... Device tree strings 0x0763 -> 0x076309e6 Device tree struct 0x0764 -> 0x0765 Quiescing Open Firmware ... Booting Linux via __start() @ 0x0200 ... -> smp_release_cpus() spinning_secondaries = 7 <- smp_release_cpus() Linux ppc64le #19-Ubuntu SMP T[0.970009] Unable to open file: /etc/keys/x509_ima.der (-2) [0.970011] Unable to open file: /etc/keys/x509_evm.der (-2) fsck: error 2 (No such file or directory) while executing fsck.jfs for /dev/mapper/mpatha-part2 fsck exited with status code 8 I haven't investigated more than that, it looks like jfsutils does not include anything to copy fsck.jfs to the initramfs. Clearly hooks/fsck in initramfs-tools appears to not be doing its job in this case. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Affects: jfsutils (Ubuntu) Importance: Undecided Status: New ** Also affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1711011 Title: fsck.jfs missing from initramfs Status in initramfs-tools package in Ubuntu: New Status in jfsutils package in Ubuntu: New Bug description: Detected machine type: 0101 command line: BOOT_IMAGE=/boot/vmlinux-4.11.0-13-generic root=UUID=8c6162e8-9bb1-4171-a901-30e001222a14 ro splash quiet Max number of cores passed to firmware: 2048 (NR_CPUS = 2048) Calling ibm,client-architecture-support... done memory layout at init: memory_limit : (16 MB aligned) alloc_bottom : 0762 alloc_top: 3000 alloc_top_hi : 00078000 rmo_top : 3000 ram_top : 00078000 instantiating rtas at 0x2fff... done prom_hold_cpus: skipped copying OF device tree... Building dt strings... Building dt structure... Device tree strings 0x0763 -> 0x076309e6 Device tree struct 0x0764 -> 0x0765 Quiescing Open Firmware ... Booting Linux via __start() @ 0x0200 ... -> smp_release_cpus() spinning_secondaries = 7 <- smp_release_cpus() Linux ppc64le #19-Ubuntu SMP T[0.970009] Unable to open file: /etc/keys/x509_ima.der (-2) [0.970011] Unable to open file: /etc/keys/x509_evm.der (-2) fsck: error 2 (No such file or directory) while executing fsck.jfs for /dev/mapper/mpatha-part2 fsck exited with status code 8 I haven't investigated more than that, it looks like jfsutils does not include anything to copy fsck.jfs to the initramfs. Clearly hooks/fsck in initramfs-tools appears to not be doing its job in this case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1711011/+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 1711011] Re: fsck.jfs missing from initramfs
I'm unsure if this is a bug in jfsutils (which maybe should ship its own logic like btrfs does), or in initramfs-tools where its testing fails for jfs, hence the multiple tasks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1711011 Title: fsck.jfs missing from initramfs Status in initramfs-tools package in Ubuntu: New Status in jfsutils package in Ubuntu: New Bug description: Detected machine type: 0101 command line: BOOT_IMAGE=/boot/vmlinux-4.11.0-13-generic root=UUID=8c6162e8-9bb1-4171-a901-30e001222a14 ro splash quiet Max number of cores passed to firmware: 2048 (NR_CPUS = 2048) Calling ibm,client-architecture-support... done memory layout at init: memory_limit : (16 MB aligned) alloc_bottom : 0762 alloc_top: 3000 alloc_top_hi : 00078000 rmo_top : 3000 ram_top : 00078000 instantiating rtas at 0x2fff... done prom_hold_cpus: skipped copying OF device tree... Building dt strings... Building dt structure... Device tree strings 0x0763 -> 0x076309e6 Device tree struct 0x0764 -> 0x0765 Quiescing Open Firmware ... Booting Linux via __start() @ 0x0200 ... -> smp_release_cpus() spinning_secondaries = 7 <- smp_release_cpus() Linux ppc64le #19-Ubuntu SMP T[0.970009] Unable to open file: /etc/keys/x509_ima.der (-2) [0.970011] Unable to open file: /etc/keys/x509_evm.der (-2) fsck: error 2 (No such file or directory) while executing fsck.jfs for /dev/mapper/mpatha-part2 fsck exited with status code 8 I haven't investigated more than that, it looks like jfsutils does not include anything to copy fsck.jfs to the initramfs. Clearly hooks/fsck in initramfs-tools appears to not be doing its job in this case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1711011/+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 1710601] Re: bluetoothctl fails to connect [USB 0930:0506 Toshiba Corp. Integrated Bluetooth]
** Summary changed: - bluetoothctl fails to connect + bluetoothctl fails to connect [USB 0930:0506 Toshiba Corp. Integrated Bluetooth] ** Changed in: bluez (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1710601 Title: bluetoothctl fails to connect [USB 0930:0506 Toshiba Corp. Integrated Bluetooth] Status in bluez package in Ubuntu: New Bug description: bluetooth stopped working after some update, probably to bluez5 before it was working flawlessly following https://wiki.archlinux.org/index.php/Bluetooth#Configuration_via_the_CLI now $ bluetoothctl shows no typed characters, $ sudo bluetoothctl works well until I try to connect the device: [bluetooth]# connect A8:7E:33:FC:6D:15 Attempting to connect to A8:7E:33:FC:6D:15 [CHG] Device A8:7E:33:FC:6D:15 Connected: yes Failed to connect: org.bluez.Error.NotAvailable [CHG] Device A8:7E:33:FC:6D:15 Connected: no [CHG] Device A8:7E:33:FC:6D:15 RSSI: -81 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -73 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -65 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -79 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -61 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -75 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 I am using bluez 5.37-0ubuntu5 under Ubuntu 16.04.3 LTS, updated to the day. I found errors in logs: aug 13 17:34:25 george bluetoothd[752]: Starting SDP server aug 13 17:34:26 george ModemManager[738]: ModemManager (version 1.4.12) starting in system bus... aug 13 17:34:26 george kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3 aug 13 17:34:26 george kernel: Bluetooth: BNEP filters: protocol multicast aug 13 17:34:26 george kernel: Bluetooth: BNEP socket layer initialized aug 13 17:34:26 george bluetoothd[752]: Bluetooth management interface 1.10 initialized aug 13 17:34:26 george dbus[702]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.fre aug 13 17:34:26 george bluetoothd[752]: Failed to obtain handles for "Service Changed" characteristic aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Error adding Link Loss service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Current Time Service could not be registered aug 13 17:34:26 george bluetoothd[752]: gatt-time-server: Input/output error (5) aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Sap driver initialization failed. aug 13 17:34:26 george bluetoothd[752]: sap-server: Operation not permitted (1) aug 13 17:35:00 george dbus[702]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.22" (uid=100 aug 13 17:35:14 george sudo[1199]: user : TTY=pts/0 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:35:14 george sudo[1199]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:35:23 george systemd[1]: Starting Stop ureadahead data collection... aug 13 17:35:23 george systemd[1]: Started Stop ureadahead data collection. aug 13 17:35:23 george systemd[1]: Stopped Read required files in advance. aug 13 17:43:26 george sudo[1199]: pam_unix(sudo:session): session closed for user root aug 13 17:47:44 george sshd[1389]: Accepted publickey for user from 192.168.69.200 port 57812 ssh2: RSA SHA256:MQ3JEM2k/Yw2jzz aug 13 17:47:44 george sshd[1389]: pam_unix(sshd:session): session opened for user user by (uid=0) aug 13 17:47:44 george systemd-logind[742]: New session 2 of user user. aug 13 17:47:44 george systemd[1]: Started Session 2 of user user. aug 13 17:47:52 george sudo[1431]: user : TTY=pts/1 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:47:52 george sudo[1431]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:49:30 george /usr/lib/snapd/snapd[685]: snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd[1]: Starting Cleanup of Temporary Directories... aug 13 17:49:30 george snapd[685]: 2017/08/13 17:49:30.803962 snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd-tmpfiles[1459]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. aug 13 17:49:31 george systemd[1]: Started Cleanup of Temporary Directories. aug 13 17:53:16 george sudo[1520]: user :
[Touch-packages] [Bug 1711007] [NEW] Cannot print to HP printer
Public bug reported: Wireless connection was properly set up to enable wireless printing from my HP laptop to an HP Laser Jet Pro M12w. It worked for 2 weeks and stopped dead -- for no reason. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Aug 15 21:31:56 2017 DistUpgraded: Fresh install DistroCodename: zesty DistroVariant: ubuntu GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 35) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [103c:8205] InstallationDate: Installed on 2017-07-18 (28 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: HP HP Notebook ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic.efi.signed root=UUID=0c11b83b-a4fd-4737-b8c4-2969c5dd8ad7 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.26 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8205 dmi.board.vendor: HP dmi.board.version: 79.61 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.26:bd06/05/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn8205:rvr79.61:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.17.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.17.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1.1 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: Tue Aug 15 10:43:59 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1.1 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 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/1711007 Title: Cannot print to HP printer Status in xorg package in Ubuntu: New Bug description: Wireless connection was properly set up to enable wireless printing from my HP laptop to an HP Laser Jet Pro M12w. It worked for 2 weeks and stopped dead -- for no reason. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Aug 15 21:31:56 2017 DistUpgraded: Fresh install DistroCodename: zesty DistroVariant: ubuntu GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 35) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [103c:8205] InstallationDate: Installed on 2017-07-18 (28 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: HP HP Notebook ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic.efi.signed root=UUID=0c11b83b-a4fd-4737-b8c4-2969c5dd8ad7 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2017 dmi.bios.vendor: Insyde dmi.bios.version:
[Touch-packages] [Bug 1710853] Re: [Artful] Some appearance bugs in Ambiance
Thanks for the screenshots, but please open a separate bug for each separate issue. ** Changed in: ubuntu-themes (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1710853 Title: [Artful] Some appearance bugs in Ambiance Status in ubuntu-themes package in Ubuntu: Incomplete Bug description: See screenshots. Firefox : too small arrows (does not happen in Chromium, e.g., ok using Adwaita) Evolution : attachment bar, when displayed and expanded, is truncated (ok using Adwaita) ; it is needed to hover one of the icons to full display it Synaptic : error text field is too small (ok using Adwaita) Tweaks : misplaced menu bar separator (ok using Adwaita), the separator should be aligned with menu field below (Please note that the ubuntu-fr-artful tag is here due to Didier Roche's request.) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170703-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Aug 15 11:57:47 2017 InstallationDate: Installed on 2016-12-12 (245 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Alpha amd64 (20161211) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-themes UpgradeStatus: Upgraded to artful on 2017-05-04 (102 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1710853/+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 1711008] [NEW] Cannot print to HP printer
Public bug reported: Wireless connection was properly set up to enable wireless printing from my HP laptop to an HP Laser Jet Pro M12w. It worked for 2 weeks and stopped dead -- for no reason. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Aug 15 21:31:56 2017 DistUpgraded: Fresh install DistroCodename: zesty DistroVariant: ubuntu GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 35) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [103c:8205] InstallationDate: Installed on 2017-07-18 (28 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: HP HP Notebook ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic.efi.signed root=UUID=0c11b83b-a4fd-4737-b8c4-2969c5dd8ad7 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.26 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8205 dmi.board.vendor: HP dmi.board.version: 79.61 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.26:bd06/05/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn8205:rvr79.61:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.17.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.17.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1.1 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: Tue Aug 15 10:43:59 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1.1 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 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/1711008 Title: Cannot print to HP printer Status in xorg package in Ubuntu: New Bug description: Wireless connection was properly set up to enable wireless printing from my HP laptop to an HP Laser Jet Pro M12w. It worked for 2 weeks and stopped dead -- for no reason. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Aug 15 21:31:56 2017 DistUpgraded: Fresh install DistroCodename: zesty DistroVariant: ubuntu GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 35) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [103c:8205] InstallationDate: Installed on 2017-07-18 (28 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: HP HP Notebook ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic.efi.signed root=UUID=0c11b83b-a4fd-4737-b8c4-2969c5dd8ad7 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2017 dmi.bios.vendor: Insyde dmi.bios.version:
[Touch-packages] [Bug 1685668] Re: Firefox switched mouse clicks in scroll bar
** Also affects: firefox (Ubuntu) Importance: Undecided Status: New ** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-mate Status: New => Invalid ** Changed in: ubuntu-mate Status: Invalid => Opinion ** Changed in: ubuntu-mate Importance: Undecided => Wishlist -- 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/1685668 Title: Firefox switched mouse clicks in scroll bar Status in ubuntu-mate: Opinion Status in firefox package in Ubuntu: New Status in gtk+3.0 package in Ubuntu: New Bug description: This is a GTK3 behavior, but it's so weird: https://ubuntu-mate.community/t/how-to-restore-firefox-left-middle- clicking-on-scrollbar-behavior/12862 I fixed it creating this file (it didn't exists in xenial): costales@desktop:/$ cat /usr/share/themes/Ambiant-MATE/gtk-3.0/settings.ini [Settings] gtk-primary-button-warps-slider = false costales@desktop:/$ I was looking for creating a proposed branch, but I saw the last code: http://bazaar.launchpad.net/~ubuntu-mate-dev/ubuntu-mate/ubuntu-mate-artwork/view/head:/usr/share/themes/Ambiant-MATE/gtk-3.0/settings.ini And it has: gtk-primary-button-warps-slider = true Should it be "= false"? Thanks in advance! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1685668/+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 1710995] Re: whoopsie not online
Can you connect to https://daisy.ubuntu.com? ** Changed in: whoopsie (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1710995 Title: whoopsie not online Status in whoopsie package in Ubuntu: Incomplete Bug description: Reporting crashes from /var/crash/* is not possible any more. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: whoopsie 0.2.52.5 ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CrashReports: 640:1000:139:81264064:2017-08-12 10:41:39.397392016 +0200:2017-08-16 00:23:25.391175383 +0200:/var/crash/_usr_bin_mythwelcome.1000.crash 640:0:139:936170:2017-08-12 17:56:15.728615283 +0200:2017-08-16 00:34:15.013084038 +0200:/var/crash/_lib_systemd_systemd-udevd.0.crash 640:1000:139:1194610:2017-08-11 17:52:56.113431094 +0200:2017-08-11 17:55:44.737433966 +0200:/var/crash/_usr_bin_xfce4-power-manager.1000.crash 640:1000:139:60309601:2017-08-16 00:18:13.511184669 +0200:2017-08-16 00:18:13.515184669 +0200:/var/crash/_usr_lib_x86_64-linux-gnu_kodi_kodi.bin.1000.crash Date: Wed Aug 16 00:37:18 2017 RelatedPackageVersions: apport-noui 2.20.1-0ubuntu2.10 SourcePackage: whoopsie UpgradeStatus: Upgraded to xenial on 2016-08-06 (374 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1710995/+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 1695825] Re: No "Recently Used" in Caja 1.18.1
This is due to a change of behaviour in GTK+3. ** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-mate Status: New => Invalid -- 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/1695825 Title: No "Recently Used" in Caja 1.18.1 Status in ubuntu-mate: Invalid Status in gtk+3.0 package in Ubuntu: New Bug description: I updated to 17.04 about a week ago. Prior to that, when using 16.04, I'd been able to see, and use, the "Recently Used" function at the top of the "Places" Side pane in Caja. Now it seems to not be there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1695825/+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 1710996] [NEW] /sbin/wpa_supplicant:11:p2p_dbg:p2p_add_device:p2p_group_notif_assoc:check_assoc_ies:handle_assoc
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding wpa. This problem was most recently seen with package version 2.4-0ubuntu9, the problem page at https://errors.ubuntu.com/problem/e2e39c758119a0e8c1fcfb023026657f7cd3db55 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: wpa (Ubuntu) Importance: Undecided Status: New ** Tags: trusty utopic vivid wily xenial yakkety zesty -- 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/1710996 Title: /sbin/wpa_supplicant:11:p2p_dbg:p2p_add_device:p2p_group_notif_assoc:check_assoc_ies:handle_assoc Status in wpa package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding wpa. This problem was most recently seen with package version 2.4-0ubuntu9, the problem page at https://errors.ubuntu.com/problem/e2e39c758119a0e8c1fcfb023026657f7cd3db55 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1710996/+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 1708931] Re: Bluetooth service disconnects mouse after few minutes in Ubuntu Budgie 17.04
just wondering if this is a TLP / bluetooth interaction issue Can you have a look here - http://linrunner.de/en/tlp/docs/tlp- faq.html#btusb -- 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/1708931 Title: Bluetooth service disconnects mouse after few minutes in Ubuntu Budgie 17.04 Status in bluez package in Ubuntu: New Bug description: It happens at every reset, after using bluetooth mouse for a few minutes. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: bluez 5.43-0ubuntu1 [modified: lib/systemd/system/bluetooth.service] ProcVersionSignature: Ubuntu 4.10.0-30.34-generic 4.10.17 Uname: Linux 4.10.0-30-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Sun Aug 6 16:42:56 2017 InstallationDate: Installed on 2017-08-05 (1 days ago) InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80E5 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-30-generic root=UUID=0585caf9-68a0-4a81-ba3d-c030affa951e ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2016 dmi.bios.vendor: LENOVO dmi.bios.version: B0CN97WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo G50-80 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-80 dmi.modalias: dmi:bvnLENOVO:bvrB0CN97WW:bd01/08/2016:svnLENOVO:pn80E5:pvrLenovoG50-80:rvnLENOVO:rnLenovoG50-80:rvrNODPK:cvnLENOVO:ct10:cvrLenovoG50-80: dmi.product.name: 80E5 dmi.product.version: Lenovo G50-80 dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: B4:6D:83:B1:A7:87 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING RX bytes:301634 acl:15117 sco:0 events:1578 errors:0 TX bytes:2425 acl:31 sco:0 commands:169 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1708931/+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
just wondering if this is a TLP / bluetooth interaction issue Can you have a look here - http://linrunner.de/en/tlp/docs/tlp- faq.html#btusb -- 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 1710995] Re: whoopsie not online
sjuk@obelix:/var/crash$ sudo systemctl status whoopsie ● whoopsie.service - crash report submission daemon Loaded: loaded (/lib/systemd/system/whoopsie.service; enabled; vendor preset: enabled) Active: active (running) since Di 2017-08-15 23:58:15 CEST; 1h 9min ago Main PID: 1327 (whoopsie) CGroup: /system.slice/whoopsie.service └─1327 /usr/bin/whoopsie -f Aug 16 00:31:44 obelix whoopsie[1327]: [00:31:44] Not online; processing later (/var/crash/_lib_systemd_systemd-udevd.0.crash). Aug 16 00:34:18 obelix whoopsie[1327]: [00:34:18] Not online; processing later (/var/crash/_lib_systemd_systemd-udevd.0.crash). Aug 16 00:58:31 obelix whoopsie[1327]: [00:58:31] Not online; processing later (/var/crash/_usr_bin_mythwelcome.1000.crash). Aug 16 00:58:31 obelix whoopsie[1327]: [00:58:31] Not online; processing later (/var/crash/_usr_bin_mythwelcome.1000.crash). Aug 16 00:58:31 obelix whoopsie[1327]: [00:58:31] Not online; processing later (/var/crash/_lib_systemd_systemd-udevd.0.crash). Aug 16 00:58:31 obelix whoopsie[1327]: [00:58:31] Not online; processing later (/var/crash/_lib_systemd_systemd-udevd.0.crash). Aug 16 00:58:31 obelix whoopsie[1327]: [00:58:31] Not online; processing later (/var/crash/_usr_bin_xfce4-power-manager.1000.crash). Aug 16 00:58:31 obelix whoopsie[1327]: [00:58:31] Not online; processing later (/var/crash/_usr_bin_xfce4-power-manager.1000.crash) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1710995 Title: whoopsie not online Status in whoopsie package in Ubuntu: New Bug description: Reporting crashes from /var/crash/* is not possible any more. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: whoopsie 0.2.52.5 ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CrashReports: 640:1000:139:81264064:2017-08-12 10:41:39.397392016 +0200:2017-08-16 00:23:25.391175383 +0200:/var/crash/_usr_bin_mythwelcome.1000.crash 640:0:139:936170:2017-08-12 17:56:15.728615283 +0200:2017-08-16 00:34:15.013084038 +0200:/var/crash/_lib_systemd_systemd-udevd.0.crash 640:1000:139:1194610:2017-08-11 17:52:56.113431094 +0200:2017-08-11 17:55:44.737433966 +0200:/var/crash/_usr_bin_xfce4-power-manager.1000.crash 640:1000:139:60309601:2017-08-16 00:18:13.511184669 +0200:2017-08-16 00:18:13.515184669 +0200:/var/crash/_usr_lib_x86_64-linux-gnu_kodi_kodi.bin.1000.crash Date: Wed Aug 16 00:37:18 2017 RelatedPackageVersions: apport-noui 2.20.1-0ubuntu2.10 SourcePackage: whoopsie UpgradeStatus: Upgraded to xenial on 2016-08-06 (374 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1710995/+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 1710995] [NEW] whoopsie not online
Public bug reported: Reporting crashes from /var/crash/* is not possible any more. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: whoopsie 0.2.52.5 ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CrashReports: 640:1000:139:81264064:2017-08-12 10:41:39.397392016 +0200:2017-08-16 00:23:25.391175383 +0200:/var/crash/_usr_bin_mythwelcome.1000.crash 640:0:139:936170:2017-08-12 17:56:15.728615283 +0200:2017-08-16 00:34:15.013084038 +0200:/var/crash/_lib_systemd_systemd-udevd.0.crash 640:1000:139:1194610:2017-08-11 17:52:56.113431094 +0200:2017-08-11 17:55:44.737433966 +0200:/var/crash/_usr_bin_xfce4-power-manager.1000.crash 640:1000:139:60309601:2017-08-16 00:18:13.511184669 +0200:2017-08-16 00:18:13.515184669 +0200:/var/crash/_usr_lib_x86_64-linux-gnu_kodi_kodi.bin.1000.crash Date: Wed Aug 16 00:37:18 2017 RelatedPackageVersions: apport-noui 2.20.1-0ubuntu2.10 SourcePackage: whoopsie UpgradeStatus: Upgraded to xenial on 2016-08-06 (374 days ago) ** Affects: whoopsie (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug autoreport-true xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1710995 Title: whoopsie not online Status in whoopsie package in Ubuntu: New Bug description: Reporting crashes from /var/crash/* is not possible any more. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: whoopsie 0.2.52.5 ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CrashReports: 640:1000:139:81264064:2017-08-12 10:41:39.397392016 +0200:2017-08-16 00:23:25.391175383 +0200:/var/crash/_usr_bin_mythwelcome.1000.crash 640:0:139:936170:2017-08-12 17:56:15.728615283 +0200:2017-08-16 00:34:15.013084038 +0200:/var/crash/_lib_systemd_systemd-udevd.0.crash 640:1000:139:1194610:2017-08-11 17:52:56.113431094 +0200:2017-08-11 17:55:44.737433966 +0200:/var/crash/_usr_bin_xfce4-power-manager.1000.crash 640:1000:139:60309601:2017-08-16 00:18:13.511184669 +0200:2017-08-16 00:18:13.515184669 +0200:/var/crash/_usr_lib_x86_64-linux-gnu_kodi_kodi.bin.1000.crash Date: Wed Aug 16 00:37:18 2017 RelatedPackageVersions: apport-noui 2.20.1-0ubuntu2.10 SourcePackage: whoopsie UpgradeStatus: Upgraded to xenial on 2016-08-06 (374 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1710995/+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 59381] Re: Comboboxes do not facilitate keyboard navigation
** Changed in: gtk Status: New => Invalid -- 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/59381 Title: Comboboxes do not facilitate keyboard navigation Status in GTK+: Invalid Status in gtk+3.0 package in Ubuntu: Triaged Bug description: At present, I see no obvious way to quickly navigate this list via the keyboard. Although one can arrow through the selections, there are a lot of them, and the process of finding the right one can be extremely tedious, especially if using a screen reader. The implementation of first letter navigation would significantly improve the accessibility of this control. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/59381/+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 1710981] Re: printf count utf-8 chars like arrow wrong
** Changed in: coreutils (Debian) Status: Unknown => New ** Changed in: bash (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1710981 Title: printf count utf-8 chars like arrow wrong Status in bash package in Ubuntu: New Status in coreutils package in Ubuntu: New Status in bash package in Debian: New Status in coreutils package in Debian: New Bug description: The printf command in bash (builtin) and corutils /usb/bin/printf have an error in counting the length of a string, if a non-ascii character is involved. Example is the arrow - type Alt+I. Try the following commands: printf -v r "%-2s X\n" '→' ; echo ${#r} # prints 4 printf -v r "%-2s X\n" ' ' ; echo ${#r} # prints 5 The coreutils version of printf has the same misbehaviour. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: coreutils 8.25-2ubuntu3~16.04 ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Aug 15 23:05:40 2017 SourcePackage: coreutils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1710981/+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 1710634] Re: Incorrect directory for (lib)krb5 plugins
** Changed in: krb5 (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1710634 Title: Incorrect directory for (lib)krb5 plugins Status in krb5 package in Ubuntu: Triaged Status in krb5 package in Debian: Unknown Bug description: The libkrb5-3 package built from the krb5 source hints at a (lib)krb5 plugin directory like this: debian/libkrb5-3.dirs.in:usr/lib/${DEB_HOST_MULTIARCH}/krb5/plugins/krb5 debian/libkrb5-3.lintian-overrides:libkrb5-3: package-contains-empty-directory */plugins/krb5/ The correct (lib)krb5 plugins directory, however, is: /usr/lib/${DEB_HOST_MULTIARCH}/krb5/plugins/libkrb5 This can be verified in the krb5 source: $ grep plugins/libkrb5 -r src src/lib/krb5/os/locate_kdc.c: LIBDIR "/krb5/plugins/libkrb5", src/lib/krb5/os/locate_kdc.c:static const char *objdirs[] = { LIBDIR "/krb5/plugins/libkrb5", NULL }; As well as in the built library: $ strings /usr/lib/x86_64-linux-gnu/libkrb5.so.3|grep plugins /usr/lib/x86_64-linux-gnu/krb5/plugins/authdata /usr/lib/x86_64-linux-gnu/krb5/plugins plugins /usr/lib/x86_64-linux-gnu/krb5/plugins/libkrb5 This also briefly introduced a bug in the ubuntu and debian sssd packages, which assumed .../plugins/krb5 was the correct path: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1664566 In debian it was fixed in commit e6c4e91473e75f0ddc917a24f4d561fab9900939: commit e6c4e91473e75f0ddc917a24f4d561fab9900939 Author: Timo Aaltonen Date: Fri Feb 17 11:22:12 2017 +0200 rules, common.install: Fix sssd_krb5_locator_plugin install path. (LP: #1664566) There is no immediate impact to the libkrb5-3 package itself, since MIT kerberos does not ship any libkrb5 plugin at the moment and it is an empty directory. It should be fixed, though, to avoid inducing similar bugs in the future. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1710634/+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 1710981] Re: printf count utf-8 chars like arrow wrong
The bug leads to ugly output on the console if the data contains such characters. See the 3rd song in the following play queue listing: Pos. Artist TitleDur. 1. Bryan Adams I'm Ready4:26 2. TotoMrs. Johnson 3:48 3. The Doobie Brothers Long Train Runnin’ 3:39 4. Three Dog Night One 3:02 5. Norman GreenbaumSpirit in the Sky3:51 ** Bug watch added: Debian Bug tracker #872295 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872295 ** Also affects: bash (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872295 Importance: Unknown Status: Unknown ** Also affects: coreutils (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872295 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1710981 Title: printf count utf-8 chars like arrow wrong Status in bash package in Ubuntu: New Status in coreutils package in Ubuntu: New Status in bash package in Debian: Unknown Status in coreutils package in Debian: Unknown Bug description: The printf command in bash (builtin) and corutils /usb/bin/printf have an error in counting the length of a string, if a non-ascii character is involved. Example is the arrow - type Alt+I. Try the following commands: printf -v r "%-2s X\n" '→' ; echo ${#r} # prints 4 printf -v r "%-2s X\n" ' ' ; echo ${#r} # prints 5 The coreutils version of printf has the same misbehaviour. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: coreutils 8.25-2ubuntu3~16.04 ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Aug 15 23:05:40 2017 SourcePackage: coreutils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1710981/+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 1710981] [NEW] printf count utf-8 chars like arrow wrong
Public bug reported: The printf command in bash (builtin) and corutils /usb/bin/printf have an error in counting the length of a string, if a non-ascii character is involved. Example is the arrow - type Alt+I. Try the following commands: printf -v r "%-2s X\n" '→' ; echo ${#r} # prints 4 printf -v r "%-2s X\n" ' ' ; echo ${#r} # prints 5 The coreutils version of printf has the same misbehaviour. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: coreutils 8.25-2ubuntu3~16.04 ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Aug 15 23:05:40 2017 SourcePackage: coreutils UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: bash (Ubuntu) Importance: Undecided Status: New ** Affects: coreutils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages xenial ** Also affects: bash (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1710981 Title: printf count utf-8 chars like arrow wrong Status in bash package in Ubuntu: New Status in coreutils package in Ubuntu: New Bug description: The printf command in bash (builtin) and corutils /usb/bin/printf have an error in counting the length of a string, if a non-ascii character is involved. Example is the arrow - type Alt+I. Try the following commands: printf -v r "%-2s X\n" '→' ; echo ${#r} # prints 4 printf -v r "%-2s X\n" ' ' ; echo ${#r} # prints 5 The coreutils version of printf has the same misbehaviour. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: coreutils 8.25-2ubuntu3~16.04 ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Aug 15 23:05:40 2017 SourcePackage: coreutils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1710981/+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 1709670] Re: logrotate never recovers if the statefile is corrupted
### VERIFICATION XENIAL ### * Couldn't reproduce the above situation using the proposed package version "3.8.7-2ubuntu2.16.04.2" using Xenial/16.04 LTS. * Ran the testsuite against "3.8.7-2ubuntu2.16.04.2" and no errors were found, apart from a recurrent one which look to me like it did succeed but reported a failure. (false positive). (It has the exact same report result as previous version "3.8.7-2ubuntu2.16.04.1") == Testsuite Full Report -- # ./test setfacl failed on this system. ACL tests will not be executed. ./test: line 33: type: selinuxenabled: not found SELinux disabled. SELinux tests will not be executed. Running test 1 Running test 2 Running test 3 Running test 4 Running test 5 Running test 6 Skipping SELinux part of test 6 Running test 7 Running test 8 Running test 9 Running test 10 Skipping SELinux part of test 10 Running test 11 Running test 12 Running test 13 Running test 14 Running test 15 Running test 16 Running test 17 Running test 18 Running test 19 Running test 20 Running test 21 Running test 22 Running test 23 Running test 24 Running test 25 Running test 26 Running test 27 Running test 28 Running test 29 Running test 30 Running test 31 Skipping test 32: no ACL support Skipping test 33: no ACL support Running test 34 Skipping test 35: no ACL support Running test 36 Running test 37 Running test 38 Running test 39 Running test 40 Running test 41 Running test 42 Running test 43 Running test 44 Running test 45 Running test 46 Skipping SELinux part of test 6 Running test 47 Skipping SELinux test 47 Running test 48 Skipping test 48: no ACL support Running test 49 Running test 50 Running test 51 Running test 52 Running test 53 Running test 72 error: destination /tmp/logrotate-3.8.7/test/test.log.1.gz already exists, renaming to /tmp/logrotate-3.8.7/test/test.log.1.gz-2017081520.backup -- - Eric ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1709670 Title: logrotate never recovers if the statefile is corrupted Status in logrotate package in Ubuntu: Fix Released Status in logrotate source package in Trusty: Fix Committed Status in logrotate source package in Xenial: Fix Committed Status in logrotate source package in Zesty: Fix Committed Status in logrotate source package in Artful: Fix Released Status in logrotate package in Debian: New Bug description: [Impact] logrotate never recovers if the statefile is corrupted unless you remove it or fix the corruption by hand. Impact scenarios : - System could eventually run out of disk space on a separate partition if mounted in "/var" or specifically "/var/log" or even worst if "/var/log" is on the same partition as "/" it could create even more damage if by any chance the partition is running out of free space. - System keep updating the same files over and over, creating large size logfiles. - ... [Test Case] - Install logrotate - Run "/etc/cron.daily/logrotate" ## The first logrotate run will generate the statefile "var/lib/logrotate/status" - Modify "/var/lib/logrotate/status" by removing the first line in order to corrupt the file - Re-run "/etc/cron.daily/logrotate" and one will get the following error : "error: bad top line in state file /var/lib/logrotate/status" every time you run logrotate Unless you remove the statefile and start again or fix the corruption by hand. * Additionally, I will run the /path_to_source/test/test script as a dogfooding that does ~72 tests. [Regression Potential] * Risk of potential regression is low, and IMHO couldn't be worst than the actual situation where logrotate simply doesn't recover from a corrupt statefile. * The current patch does recover (after verification) and has been through some upstream CI validation, community feedbacks, et al. * Additionally, I will run the /path_to_source/test/test script as a dogfooding that does ~72 tests. [Other Info] * Upstream commit: https://github.com/logrotate/logrotate/commit/b9d82003002c98370e4131a7e43c76afcd23306a * Upstream bug: https://github.com/logrotate/logrotate/issues/45 * Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871592 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1709670/+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 1710961] Re: package libssl1.0.0:i386 1.0.2g-1ubuntu4.6 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configu
*** This bug is a duplicate of bug 1692981 *** https://bugs.launchpad.net/bugs/1692981 ** This bug has been marked a duplicate of bug 1692981 package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1710961 Title: package libssl1.0.0:i386 1.0.2g-1ubuntu4.6 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in openssl package in Ubuntu: New Bug description: i can't install system updates. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libssl1.0.0:i386 1.0.2g-1ubuntu4.6 ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73 Uname: Linux 4.4.0-87-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia wl ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Mon Aug 14 22:15:11 2017 DuplicateSignature: package:libssl1.0.0:i386:1.0.2g-1ubuntu4.6 Processing triggers for mime-support (3.59ubuntu1) ... dpkg: error processing package libssl1.0.0:i386 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2016-09-10 (339 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: openssl Title: package libssl1.0.0:i386 1.0.2g-1ubuntu4.6 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1710961/+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 1710961] Re: package libssl1.0.0:i386 1.0.2g-1ubuntu4.6 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configu
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1710961 Title: package libssl1.0.0:i386 1.0.2g-1ubuntu4.6 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in openssl package in Ubuntu: New Bug description: i can't install system updates. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libssl1.0.0:i386 1.0.2g-1ubuntu4.6 ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73 Uname: Linux 4.4.0-87-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia wl ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Mon Aug 14 22:15:11 2017 DuplicateSignature: package:libssl1.0.0:i386:1.0.2g-1ubuntu4.6 Processing triggers for mime-support (3.59ubuntu1) ... dpkg: error processing package libssl1.0.0:i386 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2016-09-10 (339 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: openssl Title: package libssl1.0.0:i386 1.0.2g-1ubuntu4.6 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1710961/+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 1710961] [NEW] package libssl1.0.0:i386 1.0.2g-1ubuntu4.6 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting confi
Public bug reported: i can't install system updates. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libssl1.0.0:i386 1.0.2g-1ubuntu4.6 ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73 Uname: Linux 4.4.0-87-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia wl ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Mon Aug 14 22:15:11 2017 DuplicateSignature: package:libssl1.0.0:i386:1.0.2g-1ubuntu4.6 Processing triggers for mime-support (3.59ubuntu1) ... dpkg: error processing package libssl1.0.0:i386 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2016-09-10 (339 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: openssl Title: package libssl1.0.0:i386 1.0.2g-1ubuntu4.6 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openssl (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1710961 Title: package libssl1.0.0:i386 1.0.2g-1ubuntu4.6 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in openssl package in Ubuntu: New Bug description: i can't install system updates. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libssl1.0.0:i386 1.0.2g-1ubuntu4.6 ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73 Uname: Linux 4.4.0-87-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia wl ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Mon Aug 14 22:15:11 2017 DuplicateSignature: package:libssl1.0.0:i386:1.0.2g-1ubuntu4.6 Processing triggers for mime-support (3.59ubuntu1) ... dpkg: error processing package libssl1.0.0:i386 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2016-09-10 (339 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: openssl Title: package libssl1.0.0:i386 1.0.2g-1ubuntu4.6 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1710961/+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 1710795] package python3-problem-report 2.20.1-0ubuntu2 [modified: usr/share/doc/python3-problem-report/changelog.Debian.gz] failed to install/upgrade: package python3-problem-re
DuplicateSignature: Processing triggers for man-db (2.7.5-1) ... Processing triggers for man-db (2.7.5-1) ... dpkg: error processing package python3-problem-report (--configure): package python3-problem-report is not ready for configuration -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1710795 Title: package python3-problem-report 2.20.1-0ubuntu2 [modified: usr/share/doc/python3-problem-report/changelog.Debian.gz] failed to install/upgrade: package python3-problem-report is not ready for configuration cannot configure (current status 'half-installed') Status in apport package in Ubuntu: New Bug description: fatal error on installing glfw ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python3-problem-report 2.20.1-0ubuntu2 [modified: usr/share/doc/python3-problem-report/changelog.Debian.gz] ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76 Uname: Linux 4.4.0-89-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Tue Aug 15 11:45:02 2017 Dependencies: DuplicateSignature: Processing triggers for man-db (2.7.5-1) ... dpkg: error processing package python3-problem-report (--configure): package python3-problem-report is not ready for configuration ErrorMessage: package python3-problem-report is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2017-08-04 (11 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: apport Title: package python3-problem-report 2.20.1-0ubuntu2 [modified: usr/share/doc/python3-problem-report/changelog.Debian.gz] failed to install/upgrade: package python3-problem-report is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1710795/+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 1710940] [NEW] No wlan connection
Public bug reported: Hi, I have here three Wlan Sticks (Fritz Wlan N v2 (RT5572 / RT2870), Ralink 7601U and Realtek RTL8188SU) which are under Ubuntu 17.04 and 17.10 although I recognized the WLan nets but when I enter the WLan key No connection can be established. Funny, I find the connection is made under Ubuntu 16.04 and under Solus without problems. ** 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/1710940 Title: No wlan connection Status in network-manager package in Ubuntu: New Bug description: Hi, I have here three Wlan Sticks (Fritz Wlan N v2 (RT5572 / RT2870), Ralink 7601U and Realtek RTL8188SU) which are under Ubuntu 17.04 and 17.10 although I recognized the WLan nets but when I enter the WLan key No connection can be established. Funny, I find the connection is made under Ubuntu 16.04 and under Solus without problems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1710940/+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 1710941] [NEW] Bluetooth stopped working after update
Public bug reported: Bluetooth connection to Bose Soundlink II have been fine for years. Applied a few new updates in the last day or two --- system was generally up to date, I don't often wait more than a week or so --- and now I can no longer connect. Removed the device and re-paired just fine, although the speaker did not connect as it usually does after the pairing (i.e., it stayed in pairing mode). Messages in syslog: Aug 15 20:32:07 n1 bluetoothd[1075]: connect error: Connection refused (111) Aug 15 20:32:07 n1 bluetoothd[1075]: GLib: Source ID 276 was not found when attempting to remove it Aug 15 20:32:11 n1 bluetoothd[1075]: connect error: Connection refused (111) Aug 15 20:32:42 n1 bluetoothd[1075]: connect error: Connection refused (111) Aug 15 20:32:42 n1 bluetoothd[1075]: GLib: Source ID 287 was not found when attempting to remove it Aug 15 20:32:46 n1 bluetoothd[1075]: connect error: Connection refused (111) Aug 15 20:33:07 n1 bluetoothd[1075]: connect error: Host is down (112) Aug 15 20:33:07 n1 bluetoothd[1075]: GLib: Source ID 305 was not found when attempting to remove it ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-91.114-generic 4.4.76 Uname: Linux 4.4.0-91-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Tue Aug 15 20:34:34 2017 InstallationDate: Installed on 2015-12-26 (597 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) InterestingModules: rfcomm bnep btusb bluetooth ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-91-generic root=UUID=5950fbba-cde1-49ac-a918-04e517894c57 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to xenial on 2017-02-28 (168 days ago) dmi.bios.date: 01/18/2017 dmi.bios.vendor: Intel Corporation dmi.bios.version: RYBDWi35.86A.0362.2017.0118.0940 dmi.board.name: NUC5i5RYB dmi.board.vendor: Intel Corporation dmi.board.version: H40999-504 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorporation:bvrRYBDWi35.86A.0362.2017.0118.0940:bd01/18/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5i5RYB:rvrH40999-504:cvn:ct3:cvr: hciconfig: hci0: Type: BR/EDR Bus: USB BD Address: DC:53:60:97:55:17 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:6896 acl:46 sco:0 events:294 errors:0 TX bytes:4254 acl:32 sco:0 commands:156 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2015-12-29T07:24:08.439240 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1710941 Title: Bluetooth stopped working after update Status in bluez package in Ubuntu: New Bug description: Bluetooth connection to Bose Soundlink II have been fine for years. Applied a few new updates in the last day or two --- system was generally up to date, I don't often wait more than a week or so --- and now I can no longer connect. Removed the device and re-paired just fine, although the speaker did not connect as it usually does after the pairing (i.e., it stayed in pairing mode). Messages in syslog: Aug 15 20:32:07 n1 bluetoothd[1075]: connect error: Connection refused (111) Aug 15 20:32:07 n1 bluetoothd[1075]: GLib: Source ID 276 was not found when attempting to remove it Aug 15 20:32:11 n1 bluetoothd[1075]: connect error: Connection refused (111) Aug 15 20:32:42 n1 bluetoothd[1075]: connect error: Connection refused (111) Aug 15 20:32:42 n1 bluetoothd[1075]: GLib: Source ID 287 was not found when attempting to remove it Aug 15 20:32:46 n1 bluetoothd[1075]: connect error: Connection refused (111) Aug 15 20:33:07 n1 bluetoothd[1075]: connect error: Host is down (112) Aug 15 20:33:07 n1 bluetoothd[1075]: GLib: Source ID 305 was not found when attempting to remove it ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-91.114-generic 4.4.76 Uname: Linux 4.4.0-91-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Tue Aug 15 20:34:34 2017 InstallationDate: Installed on 2015-12-26 (597 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) InterestingModules: rfcomm bnep btusb bluetooth ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-91-generic root=UUID=5950fbba-cde1-49ac-a918-04e517894c57 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to xenial on 2017-02-28 (168 days ago) dmi.bios.date: 01/18/2017 dmi.bios.vendor: Intel Corporation dmi.bios.version: RYBDWi35.86A.0362.2017.0118.0940 dmi.board.name: NUC5i5RYB dmi.board.vendor: Intel Corporation dmi.board.version: H40999-504 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorporation:bv
[Touch-packages] [Bug 1710925] Re: package apt 1.2.24 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
For some reason /var/log/apt/term.log was not attached, without it, we have no chance to see what happens. ** Changed in: apt (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1710925 Title: package apt 1.2.24 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in apt package in Ubuntu: Incomplete Bug description: don't know ProblemType: Package DistroRelease: Ubuntu 16.04 Package: apt 1.2.24 ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76 Uname: Linux 4.4.0-89-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 AptOrdering: apt: Configure apt-utils: Install apt-utils: Configure NULL: ConfigurePending Architecture: amd64 Date: Tue Aug 15 17:41:54 2017 DpkgTerminalLog: dpkg: error processing package apt (--configure): package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2016-08-10 (370 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: apt Title: package apt 1.2.24 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1710925/+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 1710926] Re: Build failing against qt 5.9 and python 3.6 on artful
** Tags added: ftbfs -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1710926 Title: Build failing against qt 5.9 and python 3.6 on artful Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: I am getting following error: ubuntu-ui- toolkit-1.3.2190+17.04.20170327ubuntu1/tests/autopilot/ubuntuuitoolkit/_custom_proxy_objects/_qquicklistview.py:179:9: E722 do not use bare except ubuntu-ui-toolkit-1.3.2190+17.04.20170327ubuntu1/tests/autopilot/ubuntuuitoolkit/_custom_proxy_objects/_uclistitem.py:52:9: E722 do not use bare except It seems to be related with latest pycodestyle version 2.3.0 (2017-01-30) which was added the new E722 check: Add E722 warning for bare except clauses To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1710926/+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 1710925] [NEW] package apt 1.2.24 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Public bug reported: don't know ProblemType: Package DistroRelease: Ubuntu 16.04 Package: apt 1.2.24 ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76 Uname: Linux 4.4.0-89-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 AptOrdering: apt: Configure apt-utils: Install apt-utils: Configure NULL: ConfigurePending Architecture: amd64 Date: Tue Aug 15 17:41:54 2017 DpkgTerminalLog: dpkg: error processing package apt (--configure): package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2016-08-10 (370 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: apt Title: package apt 1.2.24 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1710925 Title: package apt 1.2.24 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in apt package in Ubuntu: New Bug description: don't know ProblemType: Package DistroRelease: Ubuntu 16.04 Package: apt 1.2.24 ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76 Uname: Linux 4.4.0-89-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 AptOrdering: apt: Configure apt-utils: Install apt-utils: Configure NULL: ConfigurePending Architecture: amd64 Date: Tue Aug 15 17:41:54 2017 DpkgTerminalLog: dpkg: error processing package apt (--configure): package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2016-08-10 (370 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: apt Title: package apt 1.2.24 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1710925/+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 1710911] Re: apt-ftparchive does not correctly cache filesizes for packages > 4GB
juliank: From what I can see, cache files generated by apt-ftparchive do not contain versioned entries. They can also be located anywhere on a machine's filesystem, depending on how the sysadmin chose to apply the utility; there isn't one canonical file that can be automatically refreshed on package upgrade. At present, the ':st' part of a cache entry has the following structure: enum FlagList {FlControl = (1<<0),FlMD5=(1<<1),FlContents=(1<<2), FlSize=(1<<3), FlSHA1=(1<<4), FlSHA256=(1<<5), FlSHA512=(1<<6), FlSource=(1<<7) [...] // WARNING: this struct is read/written to the DB so do not change the // layout of the fields (see lp #1274466), only append to it struct StatStore { uint32_t Flags; uint32_t mtime; uint64_t FileSize; uint8_t MD5[16]; uint8_t SHA1[20]; uint8_t SHA256[32]; uint8_t SHA512[64]; } (From ftparchive/cachedb.h) One of my colleagues has pointed out that my original suggestion of checking the lower four bytes for null values will misbehave if the corrected code is asked to record information for a file that is an exact integer multiple of 4GB. You could stat the file on the filesystem in this case to resolve the ambiguity. Alternatively, you could modify the data-structure above to make it unambiguous what kind of record is being read: * A flag bit could be used in Flags; * An explicit version field could be added to the end of this struct. * The use of the cache to store package file sizes could be discontinued in favour of always statting the file-size directly; * The packed data-structure could be discarded completely, in favour of storing different pieces of metadata in independent DB keys. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1710911 Title: apt-ftparchive does not correctly cache filesizes for packages > 4GB Status in apt package in Ubuntu: New Bug description: Release: 16.04 Version: 1.2.19 apt-ftparchive is a utility for, among other things, generating a Packages file from a set of .deb packages. Because generating Packages files for a large directory tree of .deb packages is expensive, it can cache the properties of .deb packages it has already inspected in a Berkeley database file. Historically, apt-ftparchive stored the size of a .deb package as a 32-bit unsigned integer in network byte-order in this cache. This field was later enlarged to 64-bits - which caused other problems; see: LP #1274466. However, even after this integer field was enlarged, apt-ftparchive continued to use the htonl() and ntohl() libc functions to convert file-sizes to and from network byte-order when reading and writing to its cache. These functions unconditionally emit 32-bit unsigned integers, which means that apt-ftparchive remained unable to correctly record the file-sizes for packages > 32bits (i.e. > 4GB). Consequently, if apt-ftparchive is asked (with caching enabled) to generate a Packages file for a .deb package larger than 4GB, it will produce a Packages file with the correct Size: field the first time, but with incorrect Size: fields subsequently. I have developed a small patch which replaces the use of the ntohl() family of functions with suitable replacements from . This produces correct output on new installations. However, caution is necessary: the existing code is incorrectly storing the 32 least significant bits of a 64-bit number in the upper 32-bits of a 64-bit field, in big-endian byte order. The application of this patch will cause new values to be stored correctly, but in a binary-incompatible way with existing caches. For example, a package of size 7162161474 bytes will today have the following sequence of bytes stored in its cache entry: \xaa\xe5\xe9\x42\x00\x00\x00\x00 (When re-read, this will produce a file-size value of 7162161474 mod 32bits, i.e. 2867194178.) With this patch applied, apt-ftparchive will correctly store this entry: \x00\x00\x00\x01\xaa\xe5\xe9\x42 However, this correct cache entry, when interpreted by the current broken code, will return a file-size of 1 byte. Worse, the existing broken entry will be interpreted by my fixed code as containing the value 12314505225791602688. It would be good to have this patch, or some derivative of it, applied to the main APT code-base. Before this can happen, however, some mechanism to detect and correct broken cache entries will be needed if we are to avoid a repeat of LP #1274466. I would suggest this could be done by checking the trailing four bytes of the 64-bit filesize field: if they are all zero, then the cache entry is broken, and should be rewritten. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/171
[Touch-packages] [Bug 1710926] [NEW] Build failing against qt 5.9 and python 3.6 on artful
Public bug reported: I am getting following error: ubuntu-ui- toolkit-1.3.2190+17.04.20170327ubuntu1/tests/autopilot/ubuntuuitoolkit/_custom_proxy_objects/_qquicklistview.py:179:9: E722 do not use bare except ubuntu-ui-toolkit-1.3.2190+17.04.20170327ubuntu1/tests/autopilot/ubuntuuitoolkit/_custom_proxy_objects/_uclistitem.py:52:9: E722 do not use bare except It seems to be related with latest pycodestyle version 2.3.0 (2017-01-30) which was added the new E722 check: Add E722 warning for bare except clauses ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: New ** Tags: artful -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1710926 Title: Build failing against qt 5.9 and python 3.6 on artful Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: I am getting following error: ubuntu-ui- toolkit-1.3.2190+17.04.20170327ubuntu1/tests/autopilot/ubuntuuitoolkit/_custom_proxy_objects/_qquicklistview.py:179:9: E722 do not use bare except ubuntu-ui-toolkit-1.3.2190+17.04.20170327ubuntu1/tests/autopilot/ubuntuuitoolkit/_custom_proxy_objects/_uclistitem.py:52:9: E722 do not use bare except It seems to be related with latest pycodestyle version 2.3.0 (2017-01-30) which was added the new E722 check: Add E722 warning for bare except clauses To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1710926/+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 1710911] Re: apt-ftparchive does not correctly cache filesizes for packages > 4GB
The attachment "Fix truncation of 64-bit file-sizes caused by htonl()" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1710911 Title: apt-ftparchive does not correctly cache filesizes for packages > 4GB Status in apt package in Ubuntu: New Bug description: Release: 16.04 Version: 1.2.19 apt-ftparchive is a utility for, among other things, generating a Packages file from a set of .deb packages. Because generating Packages files for a large directory tree of .deb packages is expensive, it can cache the properties of .deb packages it has already inspected in a Berkeley database file. Historically, apt-ftparchive stored the size of a .deb package as a 32-bit unsigned integer in network byte-order in this cache. This field was later enlarged to 64-bits - which caused other problems; see: LP #1274466. However, even after this integer field was enlarged, apt-ftparchive continued to use the htonl() and ntohl() libc functions to convert file-sizes to and from network byte-order when reading and writing to its cache. These functions unconditionally emit 32-bit unsigned integers, which means that apt-ftparchive remained unable to correctly record the file-sizes for packages > 32bits (i.e. > 4GB). Consequently, if apt-ftparchive is asked (with caching enabled) to generate a Packages file for a .deb package larger than 4GB, it will produce a Packages file with the correct Size: field the first time, but with incorrect Size: fields subsequently. I have developed a small patch which replaces the use of the ntohl() family of functions with suitable replacements from . This produces correct output on new installations. However, caution is necessary: the existing code is incorrectly storing the 32 least significant bits of a 64-bit number in the upper 32-bits of a 64-bit field, in big-endian byte order. The application of this patch will cause new values to be stored correctly, but in a binary-incompatible way with existing caches. For example, a package of size 7162161474 bytes will today have the following sequence of bytes stored in its cache entry: \xaa\xe5\xe9\x42\x00\x00\x00\x00 (When re-read, this will produce a file-size value of 7162161474 mod 32bits, i.e. 2867194178.) With this patch applied, apt-ftparchive will correctly store this entry: \x00\x00\x00\x01\xaa\xe5\xe9\x42 However, this correct cache entry, when interpreted by the current broken code, will return a file-size of 1 byte. Worse, the existing broken entry will be interpreted by my fixed code as containing the value 12314505225791602688. It would be good to have this patch, or some derivative of it, applied to the main APT code-base. Before this can happen, however, some mechanism to detect and correct broken cache entries will be needed if we are to avoid a repeat of LP #1274466. I would suggest this could be done by checking the trailing four bytes of the 64-bit filesize field: if they are all zero, then the cache entry is broken, and should be rewritten. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1710911/+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 1710918] [NEW] pkexc nautilus error
Public bug reported: I have installed Nautilus-Admin to enable opening nautilus and gedit as administrator. But it does not work. On the terminal I get the following error: $ pkexec nautilus No protocol specified Unable to init server: Could not connect: Connection refused (nautilus:2524): Gtk-WARNING **: cannot open display: :0 Thanks ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: policykit-1 0.105-18 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 15 12:09:19 2017 InstallationDate: Installed on 2017-08-09 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170807) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: policykit-1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: policykit-1 (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 policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1710918 Title: pkexc nautilus error Status in policykit-1 package in Ubuntu: New Bug description: I have installed Nautilus-Admin to enable opening nautilus and gedit as administrator. But it does not work. On the terminal I get the following error: $ pkexec nautilus No protocol specified Unable to init server: Could not connect: Connection refused (nautilus:2524): Gtk-WARNING **: cannot open display: :0 Thanks ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: policykit-1 0.105-18 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 15 12:09:19 2017 InstallationDate: Installed on 2017-08-09 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170807) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: policykit-1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1710918/+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 1710911] Re: apt-ftparchive does not correctly cache filesizes for packages > 4GB
Just increment the cache version, thus forcing a regeneration. It's needed anyway so you don't destroy stuff on downgrades. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1710911 Title: apt-ftparchive does not correctly cache filesizes for packages > 4GB Status in apt package in Ubuntu: New Bug description: Release: 16.04 Version: 1.2.19 apt-ftparchive is a utility for, among other things, generating a Packages file from a set of .deb packages. Because generating Packages files for a large directory tree of .deb packages is expensive, it can cache the properties of .deb packages it has already inspected in a Berkeley database file. Historically, apt-ftparchive stored the size of a .deb package as a 32-bit unsigned integer in network byte-order in this cache. This field was later enlarged to 64-bits - which caused other problems; see: LP #1274466. However, even after this integer field was enlarged, apt-ftparchive continued to use the htonl() and ntohl() libc functions to convert file-sizes to and from network byte-order when reading and writing to its cache. These functions unconditionally emit 32-bit unsigned integers, which means that apt-ftparchive remained unable to correctly record the file-sizes for packages > 32bits (i.e. > 4GB). Consequently, if apt-ftparchive is asked (with caching enabled) to generate a Packages file for a .deb package larger than 4GB, it will produce a Packages file with the correct Size: field the first time, but with incorrect Size: fields subsequently. I have developed a small patch which replaces the use of the ntohl() family of functions with suitable replacements from . This produces correct output on new installations. However, caution is necessary: the existing code is incorrectly storing the 32 least significant bits of a 64-bit number in the upper 32-bits of a 64-bit field, in big-endian byte order. The application of this patch will cause new values to be stored correctly, but in a binary-incompatible way with existing caches. For example, a package of size 7162161474 bytes will today have the following sequence of bytes stored in its cache entry: \xaa\xe5\xe9\x42\x00\x00\x00\x00 (When re-read, this will produce a file-size value of 7162161474 mod 32bits, i.e. 2867194178.) With this patch applied, apt-ftparchive will correctly store this entry: \x00\x00\x00\x01\xaa\xe5\xe9\x42 However, this correct cache entry, when interpreted by the current broken code, will return a file-size of 1 byte. Worse, the existing broken entry will be interpreted by my fixed code as containing the value 12314505225791602688. It would be good to have this patch, or some derivative of it, applied to the main APT code-base. Before this can happen, however, some mechanism to detect and correct broken cache entries will be needed if we are to avoid a repeat of LP #1274466. I would suggest this could be done by checking the trailing four bytes of the 64-bit filesize field: if they are all zero, then the cache entry is broken, and should be rewritten. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1710911/+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 1710911] [NEW] apt-ftparchive does not correctly cache filesizes for packages > 4GB
Public bug reported: Release: 16.04 Version: 1.2.19 apt-ftparchive is a utility for, among other things, generating a Packages file from a set of .deb packages. Because generating Packages files for a large directory tree of .deb packages is expensive, it can cache the properties of .deb packages it has already inspected in a Berkeley database file. Historically, apt-ftparchive stored the size of a .deb package as a 32-bit unsigned integer in network byte-order in this cache. This field was later enlarged to 64-bits - which caused other problems; see: LP #1274466. However, even after this integer field was enlarged, apt-ftparchive continued to use the htonl() and ntohl() libc functions to convert file- sizes to and from network byte-order when reading and writing to its cache. These functions unconditionally emit 32-bit unsigned integers, which means that apt-ftparchive remained unable to correctly record the file-sizes for packages > 32bits (i.e. > 4GB). Consequently, if apt-ftparchive is asked (with caching enabled) to generate a Packages file for a .deb package larger than 4GB, it will produce a Packages file with the correct Size: field the first time, but with incorrect Size: fields subsequently. I have developed a small patch which replaces the use of the ntohl() family of functions with suitable replacements from . This produces correct output on new installations. However, caution is necessary: the existing code is incorrectly storing the 32 least significant bits of a 64-bit number in the upper 32-bits of a 64-bit field, in big-endian byte order. The application of this patch will cause new values to be stored correctly, but in a binary- incompatible way with existing caches. For example, a package of size 7162161474 bytes will today have the following sequence of bytes stored in its cache entry: \xaa\xe5\xe9\x42\x00\x00\x00\x00 (When re-read, this will produce a file-size value of 7162161474 mod 32bits, i.e. 2867194178.) With this patch applied, apt-ftparchive will correctly store this entry: \x00\x00\x00\x01\xaa\xe5\xe9\x42 However, this correct cache entry, when interpreted by the current broken code, will return a file-size of 1 byte. Worse, the existing broken entry will be interpreted by my fixed code as containing the value 12314505225791602688. It would be good to have this patch, or some derivative of it, applied to the main APT code-base. Before this can happen, however, some mechanism to detect and correct broken cache entries will be needed if we are to avoid a repeat of LP #1274466. I would suggest this could be done by checking the trailing four bytes of the 64-bit filesize field: if they are all zero, then the cache entry is broken, and should be rewritten. ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Patch added: "Fix truncation of 64-bit file-sizes caused by htonl()" https://bugs.launchpad.net/bugs/1710911/+attachment/4932874/+files/apt-ftparchive-64bit-fix.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1710911 Title: apt-ftparchive does not correctly cache filesizes for packages > 4GB Status in apt package in Ubuntu: New Bug description: Release: 16.04 Version: 1.2.19 apt-ftparchive is a utility for, among other things, generating a Packages file from a set of .deb packages. Because generating Packages files for a large directory tree of .deb packages is expensive, it can cache the properties of .deb packages it has already inspected in a Berkeley database file. Historically, apt-ftparchive stored the size of a .deb package as a 32-bit unsigned integer in network byte-order in this cache. This field was later enlarged to 64-bits - which caused other problems; see: LP #1274466. However, even after this integer field was enlarged, apt-ftparchive continued to use the htonl() and ntohl() libc functions to convert file-sizes to and from network byte-order when reading and writing to its cache. These functions unconditionally emit 32-bit unsigned integers, which means that apt-ftparchive remained unable to correctly record the file-sizes for packages > 32bits (i.e. > 4GB). Consequently, if apt-ftparchive is asked (with caching enabled) to generate a Packages file for a .deb package larger than 4GB, it will produce a Packages file with the correct Size: field the first time, but with incorrect Size: fields subsequently. I have developed a small patch which replaces the use of the ntohl() family of functions with suitable replacements from . This produces correct output on new installations. However, caution is necessary: the existing code is incorrectly storing the 32 least significant bits of a 64-bit number in the upper 32-bits of a 64-bit field, in big-endian byte order. The application of this patch will cause new values to be
[Touch-packages] [Bug 1710907] Re: ModemManager crashed with SIGSEGV in g_closure_invoke()
*** This bug is a duplicate of bug 1594799 *** https://bugs.launchpad.net/bugs/1594799 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1594799, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1710907/+attachment/4932849/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1710907/+attachment/4932851/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1710907/+attachment/4932854/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1710907/+attachment/4932855/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1710907/+attachment/4932856/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1710907/+attachment/4932857/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1710907/+attachment/4932858/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1594799 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1710907 Title: ModemManager crashed with SIGSEGV in g_closure_invoke() Status in modemmanager package in Ubuntu: New Bug description: ~ ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: modemmanager 1.6.8-1 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CrashCounter: 1 Date: Tue Aug 15 11:02:28 2017 ExecutablePath: /usr/sbin/ModemManager InstallationDate: Installed on 2017-08-03 (11 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170802) ProcCmdline: /usr/sbin/ModemManager ProcEnviron: LANG=en_CA.UTF-8 LANGUAGE=en_CA:en PATH=(custom, no user) SegvAnalysis: Segfault happened at: 0xfbae1f9c37: repz cmpsb %es:(%rdi),%ds:(%rsi) PC (0xfbae1f9c37) ok source "%es:(%rdi)" (0xfbae28d83f) ok destination "%ds:(%rsi)" (0x) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: modemmanager StacktraceTop: ?? () g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: ModemManager crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1710907/+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 1710720] Re: some libpcre3* packages have from support timeframe set for xenial LTS
** Tags added: xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcre3 in Ubuntu. https://bugs.launchpad.net/bugs/1710720 Title: some libpcre3* packages have from support timeframe set for xenial LTS Status in pcre3 package in Ubuntu: New Bug description: Some libpcre* packages from 16.04 have the wrong support timeframe set into the package info. Therefore they are falsely shown as unsupported on the "ubuntu-support-status" output: ~$ apt show libpcre3-dbg Package: libpcre3-dbg Version: 2:8.38-3.1 Priority: optional Section: libdevel Source: pcre3 Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Matthew Vernon Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 3.514 kB Depends: libpcre3 (= 2:8.38-3.1), libpcrecpp0v5 (= 2:8.38-3.1) Supported: 9m Download-Size: 692 kB APT-Sources: http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages Description: Perl 5 Compatible Regular Expression Library - debug symbols Dies ist eine Bibliothek von Funktionen zur Unterstützung von regulären Ausdrücken, deren Syntax und Semantik so ähnlich wie möglich zu denen der Sprache Perl 5 sind. . This package contains the debug symbols, This should be set to the 5years LTS timeframe (since its in main) and not to 9months. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcre3/+bug/1710720/+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 1710719] Re: python-dbg and other python packages in xenial got wrong timeframe set for support time
** Tags added: xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1710719 Title: python-dbg and other python packages in xenial got wrong timeframe set for support time Status in python-defaults package in Ubuntu: New Bug description: The python* packages from 16.04 have the wrong support timeframe set into the package info. Therefore they are falsely shown as unsupported on the "ubuntu-support-status" output: ~$ apt show python-dbg Package: python-dbg Version: 2.7.11-1 Priority: extra Section: python Source: python-defaults Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Matthias Klose Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 25,6 kB Depends: python (= 2.7.11-1), libpython-dbg (= 2.7.11-1), python2.7-dbg (>= 2.7.11-1~) Homepage: http://www.python.org/ Supported: 9m Download-Size: 1.252 B APT-Sources: http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages Description: Debugversion des Python-Interpreters (Version 2.7) Dieser Python-Interpreter wurde mit --pydebug konfiguriert. Dynamisch ladbare Module sucht er zuerst in /usr/lib/python2.7/lib-dynload/debug. This should be set to the 5years LTS timeframe (since its in main) and not to 9months. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1710719/+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 1710863] Re: Question dialog showing "text" as the question.
** Project changed: apport => apport (Ubuntu) ** Tags added: zesty ** Tags added: kubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1710863 Title: Question dialog showing "text" as the question. Status in apport package in Ubuntu: New Bug description: Screenshot that would not disappoint "thedailywtf.com" When running apport-collect 1706052, After authenticating, I got the following dialog on the screen. Just in order to report the bug to #1706052 , I selected "Yes", and you can see all the stuff it uploaded to that bug. Using Kubuntu 17.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1710863/+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 1710863] [NEW] Question dialog showing "text" as the question.
You have been subscribed to a public bug: Screenshot that would not disappoint "thedailywtf.com" When running apport-collect 1706052, After authenticating, I got the following dialog on the screen. Just in order to report the bug to #1706052 , I selected "Yes", and you can see all the stuff it uploaded to that bug. Using Kubuntu 17.04. ** Affects: apport (Ubuntu) Importance: Undecided Status: New -- Question dialog showing "text" as the question. https://bugs.launchpad.net/bugs/1710863 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. -- 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 1710715] Re: tracker 1.99.2 transition
** Also affects: tracker-miners (Ubuntu) Importance: Undecided Status: New ** Changed in: tracker-miners (Ubuntu) Status: New => Fix Committed ** Changed in: tracker-miners (Ubuntu) Importance: Undecided => Wishlist ** Changed in: tracker (Ubuntu) Status: In Progress => Fix Committed -- 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/1710715 Title: tracker 1.99.2 transition Status in tracker package in Ubuntu: Fix Committed Status in tracker-miners package in Ubuntu: Fix Committed Status in tracker package in Debian: New Bug description: Tracker bug for tracker! GNOME 3.26 includes tracker which bumps the libraries to tracker2. Also, tracker-miners is a new source package split from the old tracker source package. I have done test rebuilds for all packages that will need to be rebuilt for this transition in the GNOME3 Staging PPA. One nice benefit of the split source packages is that I believe we will be able to sync from Debian once Debian packages the new versions. Debian packaged 1.99.1 but the split happened in 1.99.2 and the Debian maintainers haven't had time yet to handle the 1.99.2 uploads. But Ubuntu needs this before Ubuntu Feature Freeze so I'm uploading to Ubuntu now. Debian ITP bug is attached. Setting block-proposed flags because I don't want src:tracker to migrate to artful this time without src:tracker-miners. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1710715/+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 1710684] Re: Debian merge 2.1.27~101-g0780600+dfsg-3
** Merge proposal linked: https://code.launchpad.net/~ahasenack/ubuntu/+source/cyrus-sasl2/+git/cyrus-sasl2/+merge/329039 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1710684 Title: Debian merge 2.1.27~101-g0780600+dfsg-3 Status in cyrus-sasl2 package in Ubuntu: In Progress Bug description: Please merge Debian's cyrus-sasl into ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1710684/+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 1539209] Re: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() from source_set_volume_cb() from pa_source_process_msg()
** Also affects: pulseaudio (Ubuntu Artful) Importance: High Assignee: Daniel van Vugt (vanvugt) Status: Fix Released ** Also affects: pulseaudio (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: pulseaudio (Ubuntu Zesty) Importance: Undecided Status: New ** Changed in: pulseaudio (Ubuntu Xenial) Importance: Undecided => High ** Changed in: pulseaudio (Ubuntu Zesty) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1539209 Title: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() from source_set_volume_cb() from pa_source_process_msg() Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Xenial: New Status in pulseaudio source package in Zesty: New Status in pulseaudio source package in Artful: Fix Released Bug description: https://errors.ubuntu.com/problem/49276ec9f717c5268dfc99940a28fb4a56fe1b4a --- [Impact] pulseaudio daemon crashes, interrupting sound output/input. [Test Case] Theoretical test case (crash does not happen for all users): 1. Find some headphones and/or microphone. Ensure you do not wear the headphones during the test as it may be loud. 2. Set audio output/input volumes to maximum. 3. Unplug and replug the headphones/microphone. 4. Check that that pulseaudio process is still running, with a start time older than when you began this test case. [Regression Potential] Low. This SRU affects the pulseaudio daemon only so the worst case would be loss of sound output/input. The same patches have been released to 17.10 for a month already and zero regressions of the crashes have occurred worldwide since then. [Original Description] Appears randomly. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:7.1-1ubuntu3 ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3 Uname: Linux 4.3.0-7-generic x86_64 ApportVersion: 2.19.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: potato12883 F...m pulseaudio /dev/snd/controlC0: potato12883 F pulseaudio /dev/snd/controlC1: potato12883 F pulseaudio CurrentDesktop: Unity Date: Thu Jan 28 22:16:03 2016 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2016-01-17 (11 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog ProcEnviron: PATH=(custom, no user) SHELL=/bin/bash LANG=ru_RU.UTF-8 LANGUAGE=ru XDG_RUNTIME_DIR= Signal: 6 SourcePackage: pulseaudio StacktraceTop: pa_alsa_path_set_volume () from /usr/lib/pulse-7.1/modules/libalsa-util.so ?? () from /usr/lib/pulse-7.1/modules/libalsa-util.so pa_source_process_msg () from /usr/lib/libpulsecore-7.1.so ?? () from /usr/lib/pulse-7.1/modules/libalsa-util.so ?? () from /usr/lib/libpulsecore-7.1.so Title: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() UpgradeStatus: Upgraded to xenial on 2016-01-28 (0 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 12/07/2009 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: V1.11 dmi.board.name: JV71TR dmi.board.vendor: Acer dmi.board.version: Rev dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: None dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.11:bd12/07/2009:svnAcer:pnAspire7540:pvr0100:rvnAcer:rnJV71TR:rvrRev:cvnAcer:ct10:cvrNone: dmi.product.name: Aspire 7540 dmi.product.version: 0100 dmi.sys.vendor: Acer modified.conffile..etc.pulse.daemon.conf: [modified] mtime.conffile..etc.pulse.daemon.conf: 2016-01-25T21:44:07.089113 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1539209/+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 1316873] Re: Left mouse button stops working
Wow. This just started happening to me today and I almost threw my mouse out of the window. I've been running 16.04 LTS for a long time and i've had some issues with ibus and PHPStorm but this is something completely new that started happening out of the blue today. Can confirm that switching to TTY and back helps (CTRL + ALT + F1 / CTRL+ ALT + F7) -- 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/1316873 Title: Left mouse button stops working Status in xorg package in Ubuntu: Confirmed Bug description: This problem has plagued me for a few years across different laptops and Ubuntu versions. Current I am experiencing this on a Dell Inspiron 15z running Ubuntu 14.04 LTS. It typically starts after I have used the chat or call feature in gmail, by clicking on the phone icon in the left chat margin. I am a Firefox user and have not tested this with chrome etc. It has not happened if i dont install google-talkplugin so it is quite possible that the plugin is to blame. Symptom === The left mouse button on all attached mice - USB , Trackpad and touch - will not do anything however the right mouse button continues to work. This happens to all applications and also to the desktop. The keyboard continues to function as normal. When this occurs , my solution is to Alt-F4 close all windows and log out of the X session. When I re-login the left mouse button works as normal. This is an irritant and work disruptor as I have to save all browser and desktop applications to safe state before I logout to reset the mouse. I will appreciate any soltion or workaround. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 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 May 6 21:41:29 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:058f] InstallationDate: Installed on 2014-04-17 (19 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Inspiron 5523 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=f5004b03-b37f-4733-88a8-51c6f3bd0a4d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0GKGJG dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA05:bd05/18/2013:svnDellInc.:pnInspiron5523:pvrNotSpecified:rvnDellInc.:rn0GKGJG:rvrA05:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 5523 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue May 6 21:20:40 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5558 vendor CMN xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1316873/+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 1710507] Re: Systemd persistent logs are not enabled
** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** No longer affects: ubuntu-mate -- 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/1710507 Title: Systemd persistent logs are not enabled Status in systemd package in Ubuntu: New Bug description: Currently, the installation is not creating the '/var/log/journal' directory, which means journald falls back to volatile storage of logs and does not provide persistent logging out of the box. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1710507/+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 1691096] Re: mysql in lxd fails to start with systemd 233: failed at step KEYRING
For good measure I also installed all of the above packages on a kvm artful instance and services came up fine. systemd version 233-8ubuntu3. -- 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/1691096 Title: mysql in lxd fails to start with systemd 233: failed at step KEYRING Status in systemd package in Ubuntu: Triaged Status in systemd source package in Artful: Triaged Bug description: artful unprivileged container on a xenial host xnox hinted that https://github.com/systemd/systemd/commit/b3415f5daef49642be3d5f417b8880c078420ff7 might be related With systemd 233, mysql-server-5.7 in an artful lxd unprivileged container fails to start: Process: 6460 ExecStartPre=/usr/share/mysql/mysql-systemd-start pre (code=exited, status=237/KEYRING) May 16 12:20:08 artful-mysql systemd[1]: mysql.service: Failed to set invocation ID on control group /system.slice/mysql.service, ignoring: Operation not permitted (...) May 16 12:20:08 artful-mysql systemd[6460]: mysql.service: Failed at step KEYRING spawning /usr/share/mysql/mysql-systemd-start: Permission denied Reproducing it on a fresh xenial kvm as host, fresh artful lxd image. We start with systemd-232 in the artful lxd: ubuntu@intense-sunbeam:~$ apt-cache policy systemd systemd: Installed: 232-21ubuntu3 Candidate: 233-6ubuntu1 Version table: 233-6ubuntu1 500 500 http://br.archive.ubuntu.com/ubuntu artful/main amd64 Packages *** 232-21ubuntu3 100 100 /var/lib/dpkg/status Then we install mysql-server-5.7: ubuntu@intense-sunbeam:~$ sudo apt install mysql-server-5.7 ... Setting up mysql-server-5.7 (5.7.17-0ubuntu1) ... update-alternatives: using /etc/mysql/mysql.cnf to provide /etc/mysql/my.cnf (my.cnf) in auto mode Renaming removed key_buffer and myisam-recover options (if present) Created symlink /etc/systemd/system/multi-user.target.wants/mysql.service → /lib/systemd/system/mysql.service. Processing triggers for libc-bin (2.24-9ubuntu2) ... Processing triggers for systemd (232-21ubuntu3) ... Which starts just fine: ubuntu@intense-sunbeam:~$ mysql -uroot -psecret mysql: [Warning] Using a password on the command line interface can be insecure. Welcome to the MySQL monitor. Commands end with ; or \g. ... We then upgrade systemd: ubuntu@intense-sunbeam:~$ sudo apt install systemd Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libpam-systemd libsystemd0 (...) Setting up libpam-systemd:amd64 (233-6ubuntu1) ... mysql is still running: ubuntu@intense-sunbeam:~$ mysql -uroot -psecret mysql: [Warning] Using a password on the command line interface can be insecure. Welcome to the MySQL monitor. Commands end with ; or \g. (...) But restarting mysql fails: ubuntu@intense-sunbeam:~$ sudo service mysql restart Job for mysql.service failed because the control process exited with error code. See "systemctl status mysql.service" and "journalctl -xe" for details. ubuntu@intense-sunbeam:~$ mysql -uroot -psecret mysql: [Warning] Using a password on the command line interface can be insecure. ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) More logs attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1691096/+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 1691096] Re: mysql in lxd fails to start with systemd 233: failed at step KEYRING
I tried systemd from proposed as well but still hit the failure: root@a1:~# apt policy systemd systemd: Installed: 234-2ubuntu3 Candidate: 234-2ubuntu3 Version table: *** 234-2ubuntu3 500 500 http://archive.ubuntu.com/ubuntu artful-proposed/main amd64 Packages 100 /var/lib/dpkg/status 233-8ubuntu3 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages I was able to reproduce this with several openstack services (cinder-scheduler, nova-scheduler, nova-conductor) and this is blocking autopkgtests so it appears to be fairly pervasive. -- 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/1691096 Title: mysql in lxd fails to start with systemd 233: failed at step KEYRING Status in systemd package in Ubuntu: Triaged Status in systemd source package in Artful: Triaged Bug description: artful unprivileged container on a xenial host xnox hinted that https://github.com/systemd/systemd/commit/b3415f5daef49642be3d5f417b8880c078420ff7 might be related With systemd 233, mysql-server-5.7 in an artful lxd unprivileged container fails to start: Process: 6460 ExecStartPre=/usr/share/mysql/mysql-systemd-start pre (code=exited, status=237/KEYRING) May 16 12:20:08 artful-mysql systemd[1]: mysql.service: Failed to set invocation ID on control group /system.slice/mysql.service, ignoring: Operation not permitted (...) May 16 12:20:08 artful-mysql systemd[6460]: mysql.service: Failed at step KEYRING spawning /usr/share/mysql/mysql-systemd-start: Permission denied Reproducing it on a fresh xenial kvm as host, fresh artful lxd image. We start with systemd-232 in the artful lxd: ubuntu@intense-sunbeam:~$ apt-cache policy systemd systemd: Installed: 232-21ubuntu3 Candidate: 233-6ubuntu1 Version table: 233-6ubuntu1 500 500 http://br.archive.ubuntu.com/ubuntu artful/main amd64 Packages *** 232-21ubuntu3 100 100 /var/lib/dpkg/status Then we install mysql-server-5.7: ubuntu@intense-sunbeam:~$ sudo apt install mysql-server-5.7 ... Setting up mysql-server-5.7 (5.7.17-0ubuntu1) ... update-alternatives: using /etc/mysql/mysql.cnf to provide /etc/mysql/my.cnf (my.cnf) in auto mode Renaming removed key_buffer and myisam-recover options (if present) Created symlink /etc/systemd/system/multi-user.target.wants/mysql.service → /lib/systemd/system/mysql.service. Processing triggers for libc-bin (2.24-9ubuntu2) ... Processing triggers for systemd (232-21ubuntu3) ... Which starts just fine: ubuntu@intense-sunbeam:~$ mysql -uroot -psecret mysql: [Warning] Using a password on the command line interface can be insecure. Welcome to the MySQL monitor. Commands end with ; or \g. ... We then upgrade systemd: ubuntu@intense-sunbeam:~$ sudo apt install systemd Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libpam-systemd libsystemd0 (...) Setting up libpam-systemd:amd64 (233-6ubuntu1) ... mysql is still running: ubuntu@intense-sunbeam:~$ mysql -uroot -psecret mysql: [Warning] Using a password on the command line interface can be insecure. Welcome to the MySQL monitor. Commands end with ; or \g. (...) But restarting mysql fails: ubuntu@intense-sunbeam:~$ sudo service mysql restart Job for mysql.service failed because the control process exited with error code. See "systemctl status mysql.service" and "journalctl -xe" for details. ubuntu@intense-sunbeam:~$ mysql -uroot -psecret mysql: [Warning] Using a password on the command line interface can be insecure. ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) More logs attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1691096/+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 1691096] Re: mysql in lxd fails to start with systemd 233: failed at step KEYRING
It looks like I'm hitting the same error with murano-cfapi in an artful unprivileged container: $ sudo apt install murano-cfapi $ sudo tail /var/log/syslog Aug 15 12:25:25 a1 systemd[1]: murano-cfapi.service: Failed to set invocation ID on control group /system.slice/murano-cfapi.service, ignoring: Operation not permitted Aug 15 12:25:25 a1 systemd[1]: Starting OpenStack Murano CF API... Aug 15 12:25:25 a1 systemd[19791]: murano-cfapi.service: Failed at step KEYRING spawning /bin/mkdir: Permission denied Aug 15 12:25:25 a1 systemd[1]: murano-cfapi.service: Control process exited, code=exited status=237 -- 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/1691096 Title: mysql in lxd fails to start with systemd 233: failed at step KEYRING Status in systemd package in Ubuntu: Triaged Status in systemd source package in Artful: Triaged Bug description: artful unprivileged container on a xenial host xnox hinted that https://github.com/systemd/systemd/commit/b3415f5daef49642be3d5f417b8880c078420ff7 might be related With systemd 233, mysql-server-5.7 in an artful lxd unprivileged container fails to start: Process: 6460 ExecStartPre=/usr/share/mysql/mysql-systemd-start pre (code=exited, status=237/KEYRING) May 16 12:20:08 artful-mysql systemd[1]: mysql.service: Failed to set invocation ID on control group /system.slice/mysql.service, ignoring: Operation not permitted (...) May 16 12:20:08 artful-mysql systemd[6460]: mysql.service: Failed at step KEYRING spawning /usr/share/mysql/mysql-systemd-start: Permission denied Reproducing it on a fresh xenial kvm as host, fresh artful lxd image. We start with systemd-232 in the artful lxd: ubuntu@intense-sunbeam:~$ apt-cache policy systemd systemd: Installed: 232-21ubuntu3 Candidate: 233-6ubuntu1 Version table: 233-6ubuntu1 500 500 http://br.archive.ubuntu.com/ubuntu artful/main amd64 Packages *** 232-21ubuntu3 100 100 /var/lib/dpkg/status Then we install mysql-server-5.7: ubuntu@intense-sunbeam:~$ sudo apt install mysql-server-5.7 ... Setting up mysql-server-5.7 (5.7.17-0ubuntu1) ... update-alternatives: using /etc/mysql/mysql.cnf to provide /etc/mysql/my.cnf (my.cnf) in auto mode Renaming removed key_buffer and myisam-recover options (if present) Created symlink /etc/systemd/system/multi-user.target.wants/mysql.service → /lib/systemd/system/mysql.service. Processing triggers for libc-bin (2.24-9ubuntu2) ... Processing triggers for systemd (232-21ubuntu3) ... Which starts just fine: ubuntu@intense-sunbeam:~$ mysql -uroot -psecret mysql: [Warning] Using a password on the command line interface can be insecure. Welcome to the MySQL monitor. Commands end with ; or \g. ... We then upgrade systemd: ubuntu@intense-sunbeam:~$ sudo apt install systemd Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libpam-systemd libsystemd0 (...) Setting up libpam-systemd:amd64 (233-6ubuntu1) ... mysql is still running: ubuntu@intense-sunbeam:~$ mysql -uroot -psecret mysql: [Warning] Using a password on the command line interface can be insecure. Welcome to the MySQL monitor. Commands end with ; or \g. (...) But restarting mysql fails: ubuntu@intense-sunbeam:~$ sudo service mysql restart Job for mysql.service failed because the control process exited with error code. See "systemctl status mysql.service" and "journalctl -xe" for details. ubuntu@intense-sunbeam:~$ mysql -uroot -psecret mysql: [Warning] Using a password on the command line interface can be insecure. ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) More logs attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1691096/+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 1709649] Re: 229 backport for race between explicit mount and handling automount
Hi Dimitri, We are affected by that,too. We have no advantage support. We have multiple server parks with 3000+ Ubuntu machines. We sees this this bug triggering especially, if some program/container/pod is using auto mount directly after startup. We worked around this issue by manually patching, but this is not a great solution, as you can guess. Is there any expectation when the MR above will be back ported or a new systemd release, which is including the fix will be issued ? Best Regards Lars ** Attachment added: "ubuntu-bug systemd" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1709649/+attachment/4932733/+files/apport.systemd.af72r96i.apport -- 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/1709649 Title: 229 backport for race between explicit mount and handling automount Status in systemd package in Ubuntu: Confirmed Bug description: Hi, We have a blocking issue in systemd for the following release ``` NAME="Ubuntu" VERSION="16.04.3 LTS (Xenial Xerus)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 16.04.3 LTS" VERSION_ID="16.04" HOME_URL="http://www.ubuntu.com/"; SUPPORT_URL="http://help.ubuntu.com/"; BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"; VERSION_CODENAME=xenial UBUNTU_CODENAME=xenial ``` This release runs systemd229, we are affected by the following auto- mouting race condition ``` https://github.com/systemd/systemd/pull/5916 ``` Is back porting the fix to the release 229 an option? Regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1709649/+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 1708051] Re: v234 seems to fail to reboot 5 times in a row on s390x, and crashes amd64/i386 instances
** Attachment added: "logs-amd64.tar.xz" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1708051/+attachment/4932720/+files/logs-amd64.tar.xz ** Description changed: ppc64el is fine. Given that everything is fixed to start containers and vms non-degraded, let's enforce that we boot not degraded. Also network online timeout is 30s, thus it makes no sense to only give the boot 10s. Especially since machines can be overcommitted with capacity. + + update: tests were improved somewhat, to be more deterministic and + always wait for the boot to fully finish before rebooting. On the + infrastructure - all but i386/amd64 pass. But locally it is not + reproducible. It almost feels like openstack-nova-autopkgtest-reboot- + marker integration is broken; or systemd fails to reboot in + scalingstack. -- 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/1708051 Title: v234 seems to fail to reboot 5 times in a row on s390x, and crashes amd64/i386 instances Status in systemd package in Ubuntu: New Bug description: ppc64el is fine. Given that everything is fixed to start containers and vms non- degraded, let's enforce that we boot not degraded. Also network online timeout is 30s, thus it makes no sense to only give the boot 10s. Especially since machines can be overcommitted with capacity. update: tests were improved somewhat, to be more deterministic and always wait for the boot to fully finish before rebooting. On the infrastructure - all but i386/amd64 pass. But locally it is not reproducible. It almost feels like openstack-nova-autopkgtest-reboot- marker integration is broken; or systemd fails to reboot in scalingstack. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1708051/+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 1708051] Re: v234 seems to fail to reboot 5 times in a row on s390x, and crashes amd64/i386 instances
** Attachment added: "logs-i386.tar.xz" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1708051/+attachment/4932719/+files/logs-i386.tar.xz -- 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/1708051 Title: v234 seems to fail to reboot 5 times in a row on s390x, and crashes amd64/i386 instances Status in systemd package in Ubuntu: New Bug description: ppc64el is fine. Given that everything is fixed to start containers and vms non- degraded, let's enforce that we boot not degraded. Also network online timeout is 30s, thus it makes no sense to only give the boot 10s. Especially since machines can be overcommitted with capacity. update: tests were improved somewhat, to be more deterministic and always wait for the boot to fully finish before rebooting. On the infrastructure - all but i386/amd64 pass. But locally it is not reproducible. It almost feels like openstack-nova-autopkgtest-reboot- marker integration is broken; or systemd fails to reboot in scalingstack. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1708051/+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 1708051] Re: v234 seems to fail to reboot 5 times in a row on s390x, and crashes amd64/i386 instances
$ cat logs-amd64/summary timedatedPASS hostnamedPASS localed-locale PASS localed-x11-keymap PASS logind PASS unit-config PASS storage PASS networkd-test.py PASS build-login PASS boot-and-servicesPASS udev PASS root-unittests PASS upstream PASS boot-smoke PASS systemd-fsckdPASS $ cat logs-i386/summary timedatedPASS hostnamedPASS localed-locale PASS localed-x11-keymap PASS logind PASS unit-config PASS storage PASS networkd-test.py PASS build-login PASS boot-and-servicesPASS udev PASS root-unittests PASS upstream PASS boot-smoke PASS systemd-fsckdPASS ** Tags added: adt-fail block-proposed -- 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/1708051 Title: v234 seems to fail to reboot 5 times in a row on s390x, and crashes amd64/i386 instances Status in systemd package in Ubuntu: New Bug description: ppc64el is fine. Given that everything is fixed to start containers and vms non- degraded, let's enforce that we boot not degraded. Also network online timeout is 30s, thus it makes no sense to only give the boot 10s. Especially since machines can be overcommitted with capacity. update: tests were improved somewhat, to be more deterministic and always wait for the boot to fully finish before rebooting. On the infrastructure - all but i386/amd64 pass. But locally it is not reproducible. It almost feels like openstack-nova-autopkgtest-reboot- marker integration is broken; or systemd fails to reboot in scalingstack. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1708051/+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 1710654] Re: systemd 233-8ubuntu3 ADT test failure with linux 4.12.0-11.12
1. lxd version in use 2. inotify watch settings https://github.com/lxc/lxd/blob/master/doc/production-setup.md -- 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/1710654 Title: systemd 233-8ubuntu3 ADT test failure with linux 4.12.0-11.12 Status in systemd package in Ubuntu: New Bug description: Testing failed on: armhf: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/armhf/s/systemd/20170814_062054_7f9b9@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1710654/+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 1710601] Re: bluetoothctl fails to connect
This is not a crash. Nothing crashes. It just disconnects immediately after connect and bluetoothctl is frozen without sudo. After running apport-collect bluetooth started working without sudo, but it still failed to connect. This is weird, since I did not use the GUI applet to connect. Thank you for your help. -- 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/1710601 Title: bluetoothctl fails to connect Status in bluez package in Ubuntu: Incomplete Bug description: bluetooth stopped working after some update, probably to bluez5 before it was working flawlessly following https://wiki.archlinux.org/index.php/Bluetooth#Configuration_via_the_CLI now $ bluetoothctl shows no typed characters, $ sudo bluetoothctl works well until I try to connect the device: [bluetooth]# connect A8:7E:33:FC:6D:15 Attempting to connect to A8:7E:33:FC:6D:15 [CHG] Device A8:7E:33:FC:6D:15 Connected: yes Failed to connect: org.bluez.Error.NotAvailable [CHG] Device A8:7E:33:FC:6D:15 Connected: no [CHG] Device A8:7E:33:FC:6D:15 RSSI: -81 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -73 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -65 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -79 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -61 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -75 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 I am using bluez 5.37-0ubuntu5 under Ubuntu 16.04.3 LTS, updated to the day. I found errors in logs: aug 13 17:34:25 george bluetoothd[752]: Starting SDP server aug 13 17:34:26 george ModemManager[738]: ModemManager (version 1.4.12) starting in system bus... aug 13 17:34:26 george kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3 aug 13 17:34:26 george kernel: Bluetooth: BNEP filters: protocol multicast aug 13 17:34:26 george kernel: Bluetooth: BNEP socket layer initialized aug 13 17:34:26 george bluetoothd[752]: Bluetooth management interface 1.10 initialized aug 13 17:34:26 george dbus[702]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.fre aug 13 17:34:26 george bluetoothd[752]: Failed to obtain handles for "Service Changed" characteristic aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Error adding Link Loss service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Current Time Service could not be registered aug 13 17:34:26 george bluetoothd[752]: gatt-time-server: Input/output error (5) aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Sap driver initialization failed. aug 13 17:34:26 george bluetoothd[752]: sap-server: Operation not permitted (1) aug 13 17:35:00 george dbus[702]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.22" (uid=100 aug 13 17:35:14 george sudo[1199]: user : TTY=pts/0 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:35:14 george sudo[1199]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:35:23 george systemd[1]: Starting Stop ureadahead data collection... aug 13 17:35:23 george systemd[1]: Started Stop ureadahead data collection. aug 13 17:35:23 george systemd[1]: Stopped Read required files in advance. aug 13 17:43:26 george sudo[1199]: pam_unix(sudo:session): session closed for user root aug 13 17:47:44 george sshd[1389]: Accepted publickey for user from 192.168.69.200 port 57812 ssh2: RSA SHA256:MQ3JEM2k/Yw2jzz aug 13 17:47:44 george sshd[1389]: pam_unix(sshd:session): session opened for user user by (uid=0) aug 13 17:47:44 george systemd-logind[742]: New session 2 of user user. aug 13 17:47:44 george systemd[1]: Started Session 2 of user user. aug 13 17:47:52 george sudo[1431]: user : TTY=pts/1 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:47:52 george sudo[1431]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:49:30 george /usr/lib/snapd/snapd[685]: snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd[1]: Starting Cleanup of Temporary Directories... aug 13 17:49:30 george snapd[685]: 2017/08/13 17:49:30.803962 snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd-tmpfiles[1459]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. aug 13 17:49:31 george systemd[1]: Started Cleanup of Tem
[Touch-packages] [Bug 1710601] getfacl.txt
apport information ** Attachment added: "getfacl.txt" https://bugs.launchpad.net/bugs/1710601/+attachment/4932689/+files/getfacl.txt -- 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/1710601 Title: bluetoothctl fails to connect Status in bluez package in Ubuntu: Incomplete Bug description: bluetooth stopped working after some update, probably to bluez5 before it was working flawlessly following https://wiki.archlinux.org/index.php/Bluetooth#Configuration_via_the_CLI now $ bluetoothctl shows no typed characters, $ sudo bluetoothctl works well until I try to connect the device: [bluetooth]# connect A8:7E:33:FC:6D:15 Attempting to connect to A8:7E:33:FC:6D:15 [CHG] Device A8:7E:33:FC:6D:15 Connected: yes Failed to connect: org.bluez.Error.NotAvailable [CHG] Device A8:7E:33:FC:6D:15 Connected: no [CHG] Device A8:7E:33:FC:6D:15 RSSI: -81 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -73 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -65 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -79 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -61 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -75 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 I am using bluez 5.37-0ubuntu5 under Ubuntu 16.04.3 LTS, updated to the day. I found errors in logs: aug 13 17:34:25 george bluetoothd[752]: Starting SDP server aug 13 17:34:26 george ModemManager[738]: ModemManager (version 1.4.12) starting in system bus... aug 13 17:34:26 george kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3 aug 13 17:34:26 george kernel: Bluetooth: BNEP filters: protocol multicast aug 13 17:34:26 george kernel: Bluetooth: BNEP socket layer initialized aug 13 17:34:26 george bluetoothd[752]: Bluetooth management interface 1.10 initialized aug 13 17:34:26 george dbus[702]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.fre aug 13 17:34:26 george bluetoothd[752]: Failed to obtain handles for "Service Changed" characteristic aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Error adding Link Loss service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Current Time Service could not be registered aug 13 17:34:26 george bluetoothd[752]: gatt-time-server: Input/output error (5) aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Sap driver initialization failed. aug 13 17:34:26 george bluetoothd[752]: sap-server: Operation not permitted (1) aug 13 17:35:00 george dbus[702]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.22" (uid=100 aug 13 17:35:14 george sudo[1199]: user : TTY=pts/0 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:35:14 george sudo[1199]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:35:23 george systemd[1]: Starting Stop ureadahead data collection... aug 13 17:35:23 george systemd[1]: Started Stop ureadahead data collection. aug 13 17:35:23 george systemd[1]: Stopped Read required files in advance. aug 13 17:43:26 george sudo[1199]: pam_unix(sudo:session): session closed for user root aug 13 17:47:44 george sshd[1389]: Accepted publickey for user from 192.168.69.200 port 57812 ssh2: RSA SHA256:MQ3JEM2k/Yw2jzz aug 13 17:47:44 george sshd[1389]: pam_unix(sshd:session): session opened for user user by (uid=0) aug 13 17:47:44 george systemd-logind[742]: New session 2 of user user. aug 13 17:47:44 george systemd[1]: Started Session 2 of user user. aug 13 17:47:52 george sudo[1431]: user : TTY=pts/1 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:47:52 george sudo[1431]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:49:30 george /usr/lib/snapd/snapd[685]: snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd[1]: Starting Cleanup of Temporary Directories... aug 13 17:49:30 george snapd[685]: 2017/08/13 17:49:30.803962 snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd-tmpfiles[1459]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. aug 13 17:49:31 george systemd[1]: Started Cleanup of Temporary Directories. aug 13 17:53:16 george sudo[1520]: user : TTY=pts/0 ; PWD=/var/log ; USER=root ; COMMAND=/usr/bin/vim -R dmesg aug 13 17:53:16 george sudo[1520]: pa
[Touch-packages] [Bug 1710601] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1710601/+attachment/4932688/+files/UdevDb.txt -- 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/1710601 Title: bluetoothctl fails to connect Status in bluez package in Ubuntu: Incomplete Bug description: bluetooth stopped working after some update, probably to bluez5 before it was working flawlessly following https://wiki.archlinux.org/index.php/Bluetooth#Configuration_via_the_CLI now $ bluetoothctl shows no typed characters, $ sudo bluetoothctl works well until I try to connect the device: [bluetooth]# connect A8:7E:33:FC:6D:15 Attempting to connect to A8:7E:33:FC:6D:15 [CHG] Device A8:7E:33:FC:6D:15 Connected: yes Failed to connect: org.bluez.Error.NotAvailable [CHG] Device A8:7E:33:FC:6D:15 Connected: no [CHG] Device A8:7E:33:FC:6D:15 RSSI: -81 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -73 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -65 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -79 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -61 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -75 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 I am using bluez 5.37-0ubuntu5 under Ubuntu 16.04.3 LTS, updated to the day. I found errors in logs: aug 13 17:34:25 george bluetoothd[752]: Starting SDP server aug 13 17:34:26 george ModemManager[738]: ModemManager (version 1.4.12) starting in system bus... aug 13 17:34:26 george kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3 aug 13 17:34:26 george kernel: Bluetooth: BNEP filters: protocol multicast aug 13 17:34:26 george kernel: Bluetooth: BNEP socket layer initialized aug 13 17:34:26 george bluetoothd[752]: Bluetooth management interface 1.10 initialized aug 13 17:34:26 george dbus[702]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.fre aug 13 17:34:26 george bluetoothd[752]: Failed to obtain handles for "Service Changed" characteristic aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Error adding Link Loss service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Current Time Service could not be registered aug 13 17:34:26 george bluetoothd[752]: gatt-time-server: Input/output error (5) aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Sap driver initialization failed. aug 13 17:34:26 george bluetoothd[752]: sap-server: Operation not permitted (1) aug 13 17:35:00 george dbus[702]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.22" (uid=100 aug 13 17:35:14 george sudo[1199]: user : TTY=pts/0 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:35:14 george sudo[1199]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:35:23 george systemd[1]: Starting Stop ureadahead data collection... aug 13 17:35:23 george systemd[1]: Started Stop ureadahead data collection. aug 13 17:35:23 george systemd[1]: Stopped Read required files in advance. aug 13 17:43:26 george sudo[1199]: pam_unix(sudo:session): session closed for user root aug 13 17:47:44 george sshd[1389]: Accepted publickey for user from 192.168.69.200 port 57812 ssh2: RSA SHA256:MQ3JEM2k/Yw2jzz aug 13 17:47:44 george sshd[1389]: pam_unix(sshd:session): session opened for user user by (uid=0) aug 13 17:47:44 george systemd-logind[742]: New session 2 of user user. aug 13 17:47:44 george systemd[1]: Started Session 2 of user user. aug 13 17:47:52 george sudo[1431]: user : TTY=pts/1 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:47:52 george sudo[1431]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:49:30 george /usr/lib/snapd/snapd[685]: snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd[1]: Starting Cleanup of Temporary Directories... aug 13 17:49:30 george snapd[685]: 2017/08/13 17:49:30.803962 snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd-tmpfiles[1459]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. aug 13 17:49:31 george systemd[1]: Started Cleanup of Temporary Directories. aug 13 17:53:16 george sudo[1520]: user : TTY=pts/0 ; PWD=/var/log ; USER=root ; COMMAND=/usr/bin/vim -R dmesg aug 13 17:53:16 george sudo[1520]: pam_u
[Touch-packages] [Bug 1710601] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1710601/+attachment/4932686/+files/ProcInterrupts.txt -- 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/1710601 Title: bluetoothctl fails to connect Status in bluez package in Ubuntu: Incomplete Bug description: bluetooth stopped working after some update, probably to bluez5 before it was working flawlessly following https://wiki.archlinux.org/index.php/Bluetooth#Configuration_via_the_CLI now $ bluetoothctl shows no typed characters, $ sudo bluetoothctl works well until I try to connect the device: [bluetooth]# connect A8:7E:33:FC:6D:15 Attempting to connect to A8:7E:33:FC:6D:15 [CHG] Device A8:7E:33:FC:6D:15 Connected: yes Failed to connect: org.bluez.Error.NotAvailable [CHG] Device A8:7E:33:FC:6D:15 Connected: no [CHG] Device A8:7E:33:FC:6D:15 RSSI: -81 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -73 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -65 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -79 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -61 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -75 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 I am using bluez 5.37-0ubuntu5 under Ubuntu 16.04.3 LTS, updated to the day. I found errors in logs: aug 13 17:34:25 george bluetoothd[752]: Starting SDP server aug 13 17:34:26 george ModemManager[738]: ModemManager (version 1.4.12) starting in system bus... aug 13 17:34:26 george kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3 aug 13 17:34:26 george kernel: Bluetooth: BNEP filters: protocol multicast aug 13 17:34:26 george kernel: Bluetooth: BNEP socket layer initialized aug 13 17:34:26 george bluetoothd[752]: Bluetooth management interface 1.10 initialized aug 13 17:34:26 george dbus[702]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.fre aug 13 17:34:26 george bluetoothd[752]: Failed to obtain handles for "Service Changed" characteristic aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Error adding Link Loss service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Current Time Service could not be registered aug 13 17:34:26 george bluetoothd[752]: gatt-time-server: Input/output error (5) aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Sap driver initialization failed. aug 13 17:34:26 george bluetoothd[752]: sap-server: Operation not permitted (1) aug 13 17:35:00 george dbus[702]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.22" (uid=100 aug 13 17:35:14 george sudo[1199]: user : TTY=pts/0 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:35:14 george sudo[1199]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:35:23 george systemd[1]: Starting Stop ureadahead data collection... aug 13 17:35:23 george systemd[1]: Started Stop ureadahead data collection. aug 13 17:35:23 george systemd[1]: Stopped Read required files in advance. aug 13 17:43:26 george sudo[1199]: pam_unix(sudo:session): session closed for user root aug 13 17:47:44 george sshd[1389]: Accepted publickey for user from 192.168.69.200 port 57812 ssh2: RSA SHA256:MQ3JEM2k/Yw2jzz aug 13 17:47:44 george sshd[1389]: pam_unix(sshd:session): session opened for user user by (uid=0) aug 13 17:47:44 george systemd-logind[742]: New session 2 of user user. aug 13 17:47:44 george systemd[1]: Started Session 2 of user user. aug 13 17:47:52 george sudo[1431]: user : TTY=pts/1 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:47:52 george sudo[1431]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:49:30 george /usr/lib/snapd/snapd[685]: snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd[1]: Starting Cleanup of Temporary Directories... aug 13 17:49:30 george snapd[685]: 2017/08/13 17:49:30.803962 snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd-tmpfiles[1459]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. aug 13 17:49:31 george systemd[1]: Started Cleanup of Temporary Directories. aug 13 17:53:16 george sudo[1520]: user : TTY=pts/0 ; PWD=/var/log ; USER=root ; COMMAND=/usr/bin/vim -R dmesg aug 13 17:53:16 george
[Touch-packages] [Bug 1710601] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1710601/+attachment/4932684/+files/ProcCpuinfoMinimal.txt -- 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/1710601 Title: bluetoothctl fails to connect Status in bluez package in Ubuntu: Incomplete Bug description: bluetooth stopped working after some update, probably to bluez5 before it was working flawlessly following https://wiki.archlinux.org/index.php/Bluetooth#Configuration_via_the_CLI now $ bluetoothctl shows no typed characters, $ sudo bluetoothctl works well until I try to connect the device: [bluetooth]# connect A8:7E:33:FC:6D:15 Attempting to connect to A8:7E:33:FC:6D:15 [CHG] Device A8:7E:33:FC:6D:15 Connected: yes Failed to connect: org.bluez.Error.NotAvailable [CHG] Device A8:7E:33:FC:6D:15 Connected: no [CHG] Device A8:7E:33:FC:6D:15 RSSI: -81 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -73 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -65 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -79 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -61 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -75 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 I am using bluez 5.37-0ubuntu5 under Ubuntu 16.04.3 LTS, updated to the day. I found errors in logs: aug 13 17:34:25 george bluetoothd[752]: Starting SDP server aug 13 17:34:26 george ModemManager[738]: ModemManager (version 1.4.12) starting in system bus... aug 13 17:34:26 george kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3 aug 13 17:34:26 george kernel: Bluetooth: BNEP filters: protocol multicast aug 13 17:34:26 george kernel: Bluetooth: BNEP socket layer initialized aug 13 17:34:26 george bluetoothd[752]: Bluetooth management interface 1.10 initialized aug 13 17:34:26 george dbus[702]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.fre aug 13 17:34:26 george bluetoothd[752]: Failed to obtain handles for "Service Changed" characteristic aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Error adding Link Loss service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Current Time Service could not be registered aug 13 17:34:26 george bluetoothd[752]: gatt-time-server: Input/output error (5) aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Sap driver initialization failed. aug 13 17:34:26 george bluetoothd[752]: sap-server: Operation not permitted (1) aug 13 17:35:00 george dbus[702]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.22" (uid=100 aug 13 17:35:14 george sudo[1199]: user : TTY=pts/0 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:35:14 george sudo[1199]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:35:23 george systemd[1]: Starting Stop ureadahead data collection... aug 13 17:35:23 george systemd[1]: Started Stop ureadahead data collection. aug 13 17:35:23 george systemd[1]: Stopped Read required files in advance. aug 13 17:43:26 george sudo[1199]: pam_unix(sudo:session): session closed for user root aug 13 17:47:44 george sshd[1389]: Accepted publickey for user from 192.168.69.200 port 57812 ssh2: RSA SHA256:MQ3JEM2k/Yw2jzz aug 13 17:47:44 george sshd[1389]: pam_unix(sshd:session): session opened for user user by (uid=0) aug 13 17:47:44 george systemd-logind[742]: New session 2 of user user. aug 13 17:47:44 george systemd[1]: Started Session 2 of user user. aug 13 17:47:52 george sudo[1431]: user : TTY=pts/1 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:47:52 george sudo[1431]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:49:30 george /usr/lib/snapd/snapd[685]: snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd[1]: Starting Cleanup of Temporary Directories... aug 13 17:49:30 george snapd[685]: 2017/08/13 17:49:30.803962 snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd-tmpfiles[1459]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. aug 13 17:49:31 george systemd[1]: Started Cleanup of Temporary Directories. aug 13 17:53:16 george sudo[1520]: user : TTY=pts/0 ; PWD=/var/log ; USER=root ; COMMAND=/usr/bin/vim -R dmesg aug 13 17:53:16
[Touch-packages] [Bug 1710601] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1710601/+attachment/4932687/+files/ProcModules.txt -- 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/1710601 Title: bluetoothctl fails to connect Status in bluez package in Ubuntu: Incomplete Bug description: bluetooth stopped working after some update, probably to bluez5 before it was working flawlessly following https://wiki.archlinux.org/index.php/Bluetooth#Configuration_via_the_CLI now $ bluetoothctl shows no typed characters, $ sudo bluetoothctl works well until I try to connect the device: [bluetooth]# connect A8:7E:33:FC:6D:15 Attempting to connect to A8:7E:33:FC:6D:15 [CHG] Device A8:7E:33:FC:6D:15 Connected: yes Failed to connect: org.bluez.Error.NotAvailable [CHG] Device A8:7E:33:FC:6D:15 Connected: no [CHG] Device A8:7E:33:FC:6D:15 RSSI: -81 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -73 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -65 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -79 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -61 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -75 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 I am using bluez 5.37-0ubuntu5 under Ubuntu 16.04.3 LTS, updated to the day. I found errors in logs: aug 13 17:34:25 george bluetoothd[752]: Starting SDP server aug 13 17:34:26 george ModemManager[738]: ModemManager (version 1.4.12) starting in system bus... aug 13 17:34:26 george kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3 aug 13 17:34:26 george kernel: Bluetooth: BNEP filters: protocol multicast aug 13 17:34:26 george kernel: Bluetooth: BNEP socket layer initialized aug 13 17:34:26 george bluetoothd[752]: Bluetooth management interface 1.10 initialized aug 13 17:34:26 george dbus[702]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.fre aug 13 17:34:26 george bluetoothd[752]: Failed to obtain handles for "Service Changed" characteristic aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Error adding Link Loss service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Current Time Service could not be registered aug 13 17:34:26 george bluetoothd[752]: gatt-time-server: Input/output error (5) aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Sap driver initialization failed. aug 13 17:34:26 george bluetoothd[752]: sap-server: Operation not permitted (1) aug 13 17:35:00 george dbus[702]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.22" (uid=100 aug 13 17:35:14 george sudo[1199]: user : TTY=pts/0 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:35:14 george sudo[1199]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:35:23 george systemd[1]: Starting Stop ureadahead data collection... aug 13 17:35:23 george systemd[1]: Started Stop ureadahead data collection. aug 13 17:35:23 george systemd[1]: Stopped Read required files in advance. aug 13 17:43:26 george sudo[1199]: pam_unix(sudo:session): session closed for user root aug 13 17:47:44 george sshd[1389]: Accepted publickey for user from 192.168.69.200 port 57812 ssh2: RSA SHA256:MQ3JEM2k/Yw2jzz aug 13 17:47:44 george sshd[1389]: pam_unix(sshd:session): session opened for user user by (uid=0) aug 13 17:47:44 george systemd-logind[742]: New session 2 of user user. aug 13 17:47:44 george systemd[1]: Started Session 2 of user user. aug 13 17:47:52 george sudo[1431]: user : TTY=pts/1 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:47:52 george sudo[1431]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:49:30 george /usr/lib/snapd/snapd[685]: snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd[1]: Starting Cleanup of Temporary Directories... aug 13 17:49:30 george snapd[685]: 2017/08/13 17:49:30.803962 snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd-tmpfiles[1459]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. aug 13 17:49:31 george systemd[1]: Started Cleanup of Temporary Directories. aug 13 17:53:16 george sudo[1520]: user : TTY=pts/0 ; PWD=/var/log ; USER=root ; COMMAND=/usr/bin/vim -R dmesg aug 13 17:53:16 george sudo[1
[Touch-packages] [Bug 1710601] syslog.txt
apport information ** Attachment added: "syslog.txt" https://bugs.launchpad.net/bugs/1710601/+attachment/4932691/+files/syslog.txt -- 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/1710601 Title: bluetoothctl fails to connect Status in bluez package in Ubuntu: Incomplete Bug description: bluetooth stopped working after some update, probably to bluez5 before it was working flawlessly following https://wiki.archlinux.org/index.php/Bluetooth#Configuration_via_the_CLI now $ bluetoothctl shows no typed characters, $ sudo bluetoothctl works well until I try to connect the device: [bluetooth]# connect A8:7E:33:FC:6D:15 Attempting to connect to A8:7E:33:FC:6D:15 [CHG] Device A8:7E:33:FC:6D:15 Connected: yes Failed to connect: org.bluez.Error.NotAvailable [CHG] Device A8:7E:33:FC:6D:15 Connected: no [CHG] Device A8:7E:33:FC:6D:15 RSSI: -81 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -73 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -65 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -79 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -61 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -75 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 I am using bluez 5.37-0ubuntu5 under Ubuntu 16.04.3 LTS, updated to the day. I found errors in logs: aug 13 17:34:25 george bluetoothd[752]: Starting SDP server aug 13 17:34:26 george ModemManager[738]: ModemManager (version 1.4.12) starting in system bus... aug 13 17:34:26 george kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3 aug 13 17:34:26 george kernel: Bluetooth: BNEP filters: protocol multicast aug 13 17:34:26 george kernel: Bluetooth: BNEP socket layer initialized aug 13 17:34:26 george bluetoothd[752]: Bluetooth management interface 1.10 initialized aug 13 17:34:26 george dbus[702]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.fre aug 13 17:34:26 george bluetoothd[752]: Failed to obtain handles for "Service Changed" characteristic aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Error adding Link Loss service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Current Time Service could not be registered aug 13 17:34:26 george bluetoothd[752]: gatt-time-server: Input/output error (5) aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Sap driver initialization failed. aug 13 17:34:26 george bluetoothd[752]: sap-server: Operation not permitted (1) aug 13 17:35:00 george dbus[702]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.22" (uid=100 aug 13 17:35:14 george sudo[1199]: user : TTY=pts/0 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:35:14 george sudo[1199]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:35:23 george systemd[1]: Starting Stop ureadahead data collection... aug 13 17:35:23 george systemd[1]: Started Stop ureadahead data collection. aug 13 17:35:23 george systemd[1]: Stopped Read required files in advance. aug 13 17:43:26 george sudo[1199]: pam_unix(sudo:session): session closed for user root aug 13 17:47:44 george sshd[1389]: Accepted publickey for user from 192.168.69.200 port 57812 ssh2: RSA SHA256:MQ3JEM2k/Yw2jzz aug 13 17:47:44 george sshd[1389]: pam_unix(sshd:session): session opened for user user by (uid=0) aug 13 17:47:44 george systemd-logind[742]: New session 2 of user user. aug 13 17:47:44 george systemd[1]: Started Session 2 of user user. aug 13 17:47:52 george sudo[1431]: user : TTY=pts/1 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:47:52 george sudo[1431]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:49:30 george /usr/lib/snapd/snapd[685]: snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd[1]: Starting Cleanup of Temporary Directories... aug 13 17:49:30 george snapd[685]: 2017/08/13 17:49:30.803962 snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd-tmpfiles[1459]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. aug 13 17:49:31 george systemd[1]: Started Cleanup of Temporary Directories. aug 13 17:53:16 george sudo[1520]: user : TTY=pts/0 ; PWD=/var/log ; USER=root ; COMMAND=/usr/bin/vim -R dmesg aug 13 17:53:16 george sudo[1520]: pam_u
[Touch-packages] [Bug 1710601] rfkill.txt
apport information ** Attachment added: "rfkill.txt" https://bugs.launchpad.net/bugs/1710601/+attachment/4932690/+files/rfkill.txt -- 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/1710601 Title: bluetoothctl fails to connect Status in bluez package in Ubuntu: Incomplete Bug description: bluetooth stopped working after some update, probably to bluez5 before it was working flawlessly following https://wiki.archlinux.org/index.php/Bluetooth#Configuration_via_the_CLI now $ bluetoothctl shows no typed characters, $ sudo bluetoothctl works well until I try to connect the device: [bluetooth]# connect A8:7E:33:FC:6D:15 Attempting to connect to A8:7E:33:FC:6D:15 [CHG] Device A8:7E:33:FC:6D:15 Connected: yes Failed to connect: org.bluez.Error.NotAvailable [CHG] Device A8:7E:33:FC:6D:15 Connected: no [CHG] Device A8:7E:33:FC:6D:15 RSSI: -81 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -73 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -65 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -79 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -61 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -75 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 I am using bluez 5.37-0ubuntu5 under Ubuntu 16.04.3 LTS, updated to the day. I found errors in logs: aug 13 17:34:25 george bluetoothd[752]: Starting SDP server aug 13 17:34:26 george ModemManager[738]: ModemManager (version 1.4.12) starting in system bus... aug 13 17:34:26 george kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3 aug 13 17:34:26 george kernel: Bluetooth: BNEP filters: protocol multicast aug 13 17:34:26 george kernel: Bluetooth: BNEP socket layer initialized aug 13 17:34:26 george bluetoothd[752]: Bluetooth management interface 1.10 initialized aug 13 17:34:26 george dbus[702]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.fre aug 13 17:34:26 george bluetoothd[752]: Failed to obtain handles for "Service Changed" characteristic aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Error adding Link Loss service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Current Time Service could not be registered aug 13 17:34:26 george bluetoothd[752]: gatt-time-server: Input/output error (5) aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Sap driver initialization failed. aug 13 17:34:26 george bluetoothd[752]: sap-server: Operation not permitted (1) aug 13 17:35:00 george dbus[702]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.22" (uid=100 aug 13 17:35:14 george sudo[1199]: user : TTY=pts/0 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:35:14 george sudo[1199]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:35:23 george systemd[1]: Starting Stop ureadahead data collection... aug 13 17:35:23 george systemd[1]: Started Stop ureadahead data collection. aug 13 17:35:23 george systemd[1]: Stopped Read required files in advance. aug 13 17:43:26 george sudo[1199]: pam_unix(sudo:session): session closed for user root aug 13 17:47:44 george sshd[1389]: Accepted publickey for user from 192.168.69.200 port 57812 ssh2: RSA SHA256:MQ3JEM2k/Yw2jzz aug 13 17:47:44 george sshd[1389]: pam_unix(sshd:session): session opened for user user by (uid=0) aug 13 17:47:44 george systemd-logind[742]: New session 2 of user user. aug 13 17:47:44 george systemd[1]: Started Session 2 of user user. aug 13 17:47:52 george sudo[1431]: user : TTY=pts/1 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:47:52 george sudo[1431]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:49:30 george /usr/lib/snapd/snapd[685]: snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd[1]: Starting Cleanup of Temporary Directories... aug 13 17:49:30 george snapd[685]: 2017/08/13 17:49:30.803962 snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd-tmpfiles[1459]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. aug 13 17:49:31 george systemd[1]: Started Cleanup of Temporary Directories. aug 13 17:53:16 george sudo[1520]: user : TTY=pts/0 ; PWD=/var/log ; USER=root ; COMMAND=/usr/bin/vim -R dmesg aug 13 17:53:16 george sudo[1520]: pam_u
[Touch-packages] [Bug 1710601] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1710601/+attachment/4932682/+files/Lsusb.txt -- 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/1710601 Title: bluetoothctl fails to connect Status in bluez package in Ubuntu: Incomplete Bug description: bluetooth stopped working after some update, probably to bluez5 before it was working flawlessly following https://wiki.archlinux.org/index.php/Bluetooth#Configuration_via_the_CLI now $ bluetoothctl shows no typed characters, $ sudo bluetoothctl works well until I try to connect the device: [bluetooth]# connect A8:7E:33:FC:6D:15 Attempting to connect to A8:7E:33:FC:6D:15 [CHG] Device A8:7E:33:FC:6D:15 Connected: yes Failed to connect: org.bluez.Error.NotAvailable [CHG] Device A8:7E:33:FC:6D:15 Connected: no [CHG] Device A8:7E:33:FC:6D:15 RSSI: -81 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -73 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -65 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -79 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -61 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -75 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 I am using bluez 5.37-0ubuntu5 under Ubuntu 16.04.3 LTS, updated to the day. I found errors in logs: aug 13 17:34:25 george bluetoothd[752]: Starting SDP server aug 13 17:34:26 george ModemManager[738]: ModemManager (version 1.4.12) starting in system bus... aug 13 17:34:26 george kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3 aug 13 17:34:26 george kernel: Bluetooth: BNEP filters: protocol multicast aug 13 17:34:26 george kernel: Bluetooth: BNEP socket layer initialized aug 13 17:34:26 george bluetoothd[752]: Bluetooth management interface 1.10 initialized aug 13 17:34:26 george dbus[702]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.fre aug 13 17:34:26 george bluetoothd[752]: Failed to obtain handles for "Service Changed" characteristic aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Error adding Link Loss service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Current Time Service could not be registered aug 13 17:34:26 george bluetoothd[752]: gatt-time-server: Input/output error (5) aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Sap driver initialization failed. aug 13 17:34:26 george bluetoothd[752]: sap-server: Operation not permitted (1) aug 13 17:35:00 george dbus[702]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.22" (uid=100 aug 13 17:35:14 george sudo[1199]: user : TTY=pts/0 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:35:14 george sudo[1199]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:35:23 george systemd[1]: Starting Stop ureadahead data collection... aug 13 17:35:23 george systemd[1]: Started Stop ureadahead data collection. aug 13 17:35:23 george systemd[1]: Stopped Read required files in advance. aug 13 17:43:26 george sudo[1199]: pam_unix(sudo:session): session closed for user root aug 13 17:47:44 george sshd[1389]: Accepted publickey for user from 192.168.69.200 port 57812 ssh2: RSA SHA256:MQ3JEM2k/Yw2jzz aug 13 17:47:44 george sshd[1389]: pam_unix(sshd:session): session opened for user user by (uid=0) aug 13 17:47:44 george systemd-logind[742]: New session 2 of user user. aug 13 17:47:44 george systemd[1]: Started Session 2 of user user. aug 13 17:47:52 george sudo[1431]: user : TTY=pts/1 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:47:52 george sudo[1431]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:49:30 george /usr/lib/snapd/snapd[685]: snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd[1]: Starting Cleanup of Temporary Directories... aug 13 17:49:30 george snapd[685]: 2017/08/13 17:49:30.803962 snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd-tmpfiles[1459]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. aug 13 17:49:31 george systemd[1]: Started Cleanup of Temporary Directories. aug 13 17:53:16 george sudo[1520]: user : TTY=pts/0 ; PWD=/var/log ; USER=root ; COMMAND=/usr/bin/vim -R dmesg aug 13 17:53:16 george sudo[1520]: pam_uni
[Touch-packages] [Bug 1710601] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1710601/+attachment/4932685/+files/ProcEnviron.txt -- 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/1710601 Title: bluetoothctl fails to connect Status in bluez package in Ubuntu: Incomplete Bug description: bluetooth stopped working after some update, probably to bluez5 before it was working flawlessly following https://wiki.archlinux.org/index.php/Bluetooth#Configuration_via_the_CLI now $ bluetoothctl shows no typed characters, $ sudo bluetoothctl works well until I try to connect the device: [bluetooth]# connect A8:7E:33:FC:6D:15 Attempting to connect to A8:7E:33:FC:6D:15 [CHG] Device A8:7E:33:FC:6D:15 Connected: yes Failed to connect: org.bluez.Error.NotAvailable [CHG] Device A8:7E:33:FC:6D:15 Connected: no [CHG] Device A8:7E:33:FC:6D:15 RSSI: -81 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -73 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -65 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -79 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -61 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -75 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 I am using bluez 5.37-0ubuntu5 under Ubuntu 16.04.3 LTS, updated to the day. I found errors in logs: aug 13 17:34:25 george bluetoothd[752]: Starting SDP server aug 13 17:34:26 george ModemManager[738]: ModemManager (version 1.4.12) starting in system bus... aug 13 17:34:26 george kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3 aug 13 17:34:26 george kernel: Bluetooth: BNEP filters: protocol multicast aug 13 17:34:26 george kernel: Bluetooth: BNEP socket layer initialized aug 13 17:34:26 george bluetoothd[752]: Bluetooth management interface 1.10 initialized aug 13 17:34:26 george dbus[702]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.fre aug 13 17:34:26 george bluetoothd[752]: Failed to obtain handles for "Service Changed" characteristic aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Error adding Link Loss service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Current Time Service could not be registered aug 13 17:34:26 george bluetoothd[752]: gatt-time-server: Input/output error (5) aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Sap driver initialization failed. aug 13 17:34:26 george bluetoothd[752]: sap-server: Operation not permitted (1) aug 13 17:35:00 george dbus[702]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.22" (uid=100 aug 13 17:35:14 george sudo[1199]: user : TTY=pts/0 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:35:14 george sudo[1199]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:35:23 george systemd[1]: Starting Stop ureadahead data collection... aug 13 17:35:23 george systemd[1]: Started Stop ureadahead data collection. aug 13 17:35:23 george systemd[1]: Stopped Read required files in advance. aug 13 17:43:26 george sudo[1199]: pam_unix(sudo:session): session closed for user root aug 13 17:47:44 george sshd[1389]: Accepted publickey for user from 192.168.69.200 port 57812 ssh2: RSA SHA256:MQ3JEM2k/Yw2jzz aug 13 17:47:44 george sshd[1389]: pam_unix(sshd:session): session opened for user user by (uid=0) aug 13 17:47:44 george systemd-logind[742]: New session 2 of user user. aug 13 17:47:44 george systemd[1]: Started Session 2 of user user. aug 13 17:47:52 george sudo[1431]: user : TTY=pts/1 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:47:52 george sudo[1431]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:49:30 george /usr/lib/snapd/snapd[685]: snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd[1]: Starting Cleanup of Temporary Directories... aug 13 17:49:30 george snapd[685]: 2017/08/13 17:49:30.803962 snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd-tmpfiles[1459]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. aug 13 17:49:31 george systemd[1]: Started Cleanup of Temporary Directories. aug 13 17:53:16 george sudo[1520]: user : TTY=pts/0 ; PWD=/var/log ; USER=root ; COMMAND=/usr/bin/vim -R dmesg aug 13 17:53:16 george sudo[1
[Touch-packages] [Bug 1710601] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1710601/+attachment/4932680/+files/JournalErrors.txt -- 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/1710601 Title: bluetoothctl fails to connect Status in bluez package in Ubuntu: Incomplete Bug description: bluetooth stopped working after some update, probably to bluez5 before it was working flawlessly following https://wiki.archlinux.org/index.php/Bluetooth#Configuration_via_the_CLI now $ bluetoothctl shows no typed characters, $ sudo bluetoothctl works well until I try to connect the device: [bluetooth]# connect A8:7E:33:FC:6D:15 Attempting to connect to A8:7E:33:FC:6D:15 [CHG] Device A8:7E:33:FC:6D:15 Connected: yes Failed to connect: org.bluez.Error.NotAvailable [CHG] Device A8:7E:33:FC:6D:15 Connected: no [CHG] Device A8:7E:33:FC:6D:15 RSSI: -81 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -73 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -65 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -79 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -61 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -75 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 I am using bluez 5.37-0ubuntu5 under Ubuntu 16.04.3 LTS, updated to the day. I found errors in logs: aug 13 17:34:25 george bluetoothd[752]: Starting SDP server aug 13 17:34:26 george ModemManager[738]: ModemManager (version 1.4.12) starting in system bus... aug 13 17:34:26 george kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3 aug 13 17:34:26 george kernel: Bluetooth: BNEP filters: protocol multicast aug 13 17:34:26 george kernel: Bluetooth: BNEP socket layer initialized aug 13 17:34:26 george bluetoothd[752]: Bluetooth management interface 1.10 initialized aug 13 17:34:26 george dbus[702]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.fre aug 13 17:34:26 george bluetoothd[752]: Failed to obtain handles for "Service Changed" characteristic aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Error adding Link Loss service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Current Time Service could not be registered aug 13 17:34:26 george bluetoothd[752]: gatt-time-server: Input/output error (5) aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Sap driver initialization failed. aug 13 17:34:26 george bluetoothd[752]: sap-server: Operation not permitted (1) aug 13 17:35:00 george dbus[702]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.22" (uid=100 aug 13 17:35:14 george sudo[1199]: user : TTY=pts/0 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:35:14 george sudo[1199]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:35:23 george systemd[1]: Starting Stop ureadahead data collection... aug 13 17:35:23 george systemd[1]: Started Stop ureadahead data collection. aug 13 17:35:23 george systemd[1]: Stopped Read required files in advance. aug 13 17:43:26 george sudo[1199]: pam_unix(sudo:session): session closed for user root aug 13 17:47:44 george sshd[1389]: Accepted publickey for user from 192.168.69.200 port 57812 ssh2: RSA SHA256:MQ3JEM2k/Yw2jzz aug 13 17:47:44 george sshd[1389]: pam_unix(sshd:session): session opened for user user by (uid=0) aug 13 17:47:44 george systemd-logind[742]: New session 2 of user user. aug 13 17:47:44 george systemd[1]: Started Session 2 of user user. aug 13 17:47:52 george sudo[1431]: user : TTY=pts/1 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:47:52 george sudo[1431]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:49:30 george /usr/lib/snapd/snapd[685]: snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd[1]: Starting Cleanup of Temporary Directories... aug 13 17:49:30 george snapd[685]: 2017/08/13 17:49:30.803962 snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd-tmpfiles[1459]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. aug 13 17:49:31 george systemd[1]: Started Cleanup of Temporary Directories. aug 13 17:53:16 george sudo[1520]: user : TTY=pts/0 ; PWD=/var/log ; USER=root ; COMMAND=/usr/bin/vim -R dmesg aug 13 17:53:16 george su
[Touch-packages] [Bug 1710601] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1710601/+attachment/4932681/+files/Lspci.txt -- 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/1710601 Title: bluetoothctl fails to connect Status in bluez package in Ubuntu: Incomplete Bug description: bluetooth stopped working after some update, probably to bluez5 before it was working flawlessly following https://wiki.archlinux.org/index.php/Bluetooth#Configuration_via_the_CLI now $ bluetoothctl shows no typed characters, $ sudo bluetoothctl works well until I try to connect the device: [bluetooth]# connect A8:7E:33:FC:6D:15 Attempting to connect to A8:7E:33:FC:6D:15 [CHG] Device A8:7E:33:FC:6D:15 Connected: yes Failed to connect: org.bluez.Error.NotAvailable [CHG] Device A8:7E:33:FC:6D:15 Connected: no [CHG] Device A8:7E:33:FC:6D:15 RSSI: -81 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -73 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -65 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -79 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -61 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -75 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 I am using bluez 5.37-0ubuntu5 under Ubuntu 16.04.3 LTS, updated to the day. I found errors in logs: aug 13 17:34:25 george bluetoothd[752]: Starting SDP server aug 13 17:34:26 george ModemManager[738]: ModemManager (version 1.4.12) starting in system bus... aug 13 17:34:26 george kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3 aug 13 17:34:26 george kernel: Bluetooth: BNEP filters: protocol multicast aug 13 17:34:26 george kernel: Bluetooth: BNEP socket layer initialized aug 13 17:34:26 george bluetoothd[752]: Bluetooth management interface 1.10 initialized aug 13 17:34:26 george dbus[702]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.fre aug 13 17:34:26 george bluetoothd[752]: Failed to obtain handles for "Service Changed" characteristic aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Error adding Link Loss service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Current Time Service could not be registered aug 13 17:34:26 george bluetoothd[752]: gatt-time-server: Input/output error (5) aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Sap driver initialization failed. aug 13 17:34:26 george bluetoothd[752]: sap-server: Operation not permitted (1) aug 13 17:35:00 george dbus[702]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.22" (uid=100 aug 13 17:35:14 george sudo[1199]: user : TTY=pts/0 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:35:14 george sudo[1199]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:35:23 george systemd[1]: Starting Stop ureadahead data collection... aug 13 17:35:23 george systemd[1]: Started Stop ureadahead data collection. aug 13 17:35:23 george systemd[1]: Stopped Read required files in advance. aug 13 17:43:26 george sudo[1199]: pam_unix(sudo:session): session closed for user root aug 13 17:47:44 george sshd[1389]: Accepted publickey for user from 192.168.69.200 port 57812 ssh2: RSA SHA256:MQ3JEM2k/Yw2jzz aug 13 17:47:44 george sshd[1389]: pam_unix(sshd:session): session opened for user user by (uid=0) aug 13 17:47:44 george systemd-logind[742]: New session 2 of user user. aug 13 17:47:44 george systemd[1]: Started Session 2 of user user. aug 13 17:47:52 george sudo[1431]: user : TTY=pts/1 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:47:52 george sudo[1431]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:49:30 george /usr/lib/snapd/snapd[685]: snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd[1]: Starting Cleanup of Temporary Directories... aug 13 17:49:30 george snapd[685]: 2017/08/13 17:49:30.803962 snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd-tmpfiles[1459]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. aug 13 17:49:31 george systemd[1]: Started Cleanup of Temporary Directories. aug 13 17:53:16 george sudo[1520]: user : TTY=pts/0 ; PWD=/var/log ; USER=root ; COMMAND=/usr/bin/vim -R dmesg aug 13 17:53:16 george sudo[1520]: pam_uni
[Touch-packages] [Bug 1710601] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1710601/+attachment/4932679/+files/Dependencies.txt -- 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/1710601 Title: bluetoothctl fails to connect Status in bluez package in Ubuntu: Incomplete Bug description: bluetooth stopped working after some update, probably to bluez5 before it was working flawlessly following https://wiki.archlinux.org/index.php/Bluetooth#Configuration_via_the_CLI now $ bluetoothctl shows no typed characters, $ sudo bluetoothctl works well until I try to connect the device: [bluetooth]# connect A8:7E:33:FC:6D:15 Attempting to connect to A8:7E:33:FC:6D:15 [CHG] Device A8:7E:33:FC:6D:15 Connected: yes Failed to connect: org.bluez.Error.NotAvailable [CHG] Device A8:7E:33:FC:6D:15 Connected: no [CHG] Device A8:7E:33:FC:6D:15 RSSI: -81 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -73 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -65 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -79 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -61 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -75 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 I am using bluez 5.37-0ubuntu5 under Ubuntu 16.04.3 LTS, updated to the day. I found errors in logs: aug 13 17:34:25 george bluetoothd[752]: Starting SDP server aug 13 17:34:26 george ModemManager[738]: ModemManager (version 1.4.12) starting in system bus... aug 13 17:34:26 george kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3 aug 13 17:34:26 george kernel: Bluetooth: BNEP filters: protocol multicast aug 13 17:34:26 george kernel: Bluetooth: BNEP socket layer initialized aug 13 17:34:26 george bluetoothd[752]: Bluetooth management interface 1.10 initialized aug 13 17:34:26 george dbus[702]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.fre aug 13 17:34:26 george bluetoothd[752]: Failed to obtain handles for "Service Changed" characteristic aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Error adding Link Loss service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Current Time Service could not be registered aug 13 17:34:26 george bluetoothd[752]: gatt-time-server: Input/output error (5) aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Sap driver initialization failed. aug 13 17:34:26 george bluetoothd[752]: sap-server: Operation not permitted (1) aug 13 17:35:00 george dbus[702]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.22" (uid=100 aug 13 17:35:14 george sudo[1199]: user : TTY=pts/0 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:35:14 george sudo[1199]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:35:23 george systemd[1]: Starting Stop ureadahead data collection... aug 13 17:35:23 george systemd[1]: Started Stop ureadahead data collection. aug 13 17:35:23 george systemd[1]: Stopped Read required files in advance. aug 13 17:43:26 george sudo[1199]: pam_unix(sudo:session): session closed for user root aug 13 17:47:44 george sshd[1389]: Accepted publickey for user from 192.168.69.200 port 57812 ssh2: RSA SHA256:MQ3JEM2k/Yw2jzz aug 13 17:47:44 george sshd[1389]: pam_unix(sshd:session): session opened for user user by (uid=0) aug 13 17:47:44 george systemd-logind[742]: New session 2 of user user. aug 13 17:47:44 george systemd[1]: Started Session 2 of user user. aug 13 17:47:52 george sudo[1431]: user : TTY=pts/1 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:47:52 george sudo[1431]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:49:30 george /usr/lib/snapd/snapd[685]: snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd[1]: Starting Cleanup of Temporary Directories... aug 13 17:49:30 george snapd[685]: 2017/08/13 17:49:30.803962 snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd-tmpfiles[1459]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. aug 13 17:49:31 george systemd[1]: Started Cleanup of Temporary Directories. aug 13 17:53:16 george sudo[1520]: user : TTY=pts/0 ; PWD=/var/log ; USER=root ; COMMAND=/usr/bin/vim -R dmesg aug 13 17:53:16 george sudo
[Touch-packages] [Bug 1710601] Re: bluetoothctl fails to connect
apport information ** Tags added: apport-collected xenial ** Description changed: bluetooth stopped working after some update, probably to bluez5 before it was working flawlessly following https://wiki.archlinux.org/index.php/Bluetooth#Configuration_via_the_CLI now $ bluetoothctl shows no typed characters, $ sudo bluetoothctl works well until I try to connect the device: [bluetooth]# connect A8:7E:33:FC:6D:15 Attempting to connect to A8:7E:33:FC:6D:15 [CHG] Device A8:7E:33:FC:6D:15 Connected: yes Failed to connect: org.bluez.Error.NotAvailable [CHG] Device A8:7E:33:FC:6D:15 Connected: no [CHG] Device A8:7E:33:FC:6D:15 RSSI: -81 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -73 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -65 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -79 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -61 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -75 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 I am using bluez 5.37-0ubuntu5 under Ubuntu 16.04.3 LTS, updated to the day. I found errors in logs: aug 13 17:34:25 george bluetoothd[752]: Starting SDP server aug 13 17:34:26 george ModemManager[738]: ModemManager (version 1.4.12) starting in system bus... aug 13 17:34:26 george kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3 aug 13 17:34:26 george kernel: Bluetooth: BNEP filters: protocol multicast aug 13 17:34:26 george kernel: Bluetooth: BNEP socket layer initialized aug 13 17:34:26 george bluetoothd[752]: Bluetooth management interface 1.10 initialized aug 13 17:34:26 george dbus[702]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.fre aug 13 17:34:26 george bluetoothd[752]: Failed to obtain handles for "Service Changed" characteristic aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Error adding Link Loss service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Current Time Service could not be registered aug 13 17:34:26 george bluetoothd[752]: gatt-time-server: Input/output error (5) aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Sap driver initialization failed. aug 13 17:34:26 george bluetoothd[752]: sap-server: Operation not permitted (1) aug 13 17:35:00 george dbus[702]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.22" (uid=100 aug 13 17:35:14 george sudo[1199]: user : TTY=pts/0 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:35:14 george sudo[1199]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:35:23 george systemd[1]: Starting Stop ureadahead data collection... aug 13 17:35:23 george systemd[1]: Started Stop ureadahead data collection. aug 13 17:35:23 george systemd[1]: Stopped Read required files in advance. aug 13 17:43:26 george sudo[1199]: pam_unix(sudo:session): session closed for user root aug 13 17:47:44 george sshd[1389]: Accepted publickey for user from 192.168.69.200 port 57812 ssh2: RSA SHA256:MQ3JEM2k/Yw2jzz aug 13 17:47:44 george sshd[1389]: pam_unix(sshd:session): session opened for user user by (uid=0) aug 13 17:47:44 george systemd-logind[742]: New session 2 of user user. aug 13 17:47:44 george systemd[1]: Started Session 2 of user user. aug 13 17:47:52 george sudo[1431]: user : TTY=pts/1 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:47:52 george sudo[1431]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:49:30 george /usr/lib/snapd/snapd[685]: snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd[1]: Starting Cleanup of Temporary Directories... aug 13 17:49:30 george snapd[685]: 2017/08/13 17:49:30.803962 snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd-tmpfiles[1459]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. aug 13 17:49:31 george systemd[1]: Started Cleanup of Temporary Directories. aug 13 17:53:16 george sudo[1520]: user : TTY=pts/0 ; PWD=/var/log ; USER=root ; COMMAND=/usr/bin/vim -R dmesg aug 13 17:53:16 george sudo[1520]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:53:18 george sudo[1520]: pam_unix(sudo:session): session closed for user root these errors are common, as you can see in comments to this bug report: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1490349 user@george:~$ lsmod | grep b
[Touch-packages] [Bug 1710601] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1710601/+attachment/4932683/+files/ProcCpuinfo.txt -- 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/1710601 Title: bluetoothctl fails to connect Status in bluez package in Ubuntu: Incomplete Bug description: bluetooth stopped working after some update, probably to bluez5 before it was working flawlessly following https://wiki.archlinux.org/index.php/Bluetooth#Configuration_via_the_CLI now $ bluetoothctl shows no typed characters, $ sudo bluetoothctl works well until I try to connect the device: [bluetooth]# connect A8:7E:33:FC:6D:15 Attempting to connect to A8:7E:33:FC:6D:15 [CHG] Device A8:7E:33:FC:6D:15 Connected: yes Failed to connect: org.bluez.Error.NotAvailable [CHG] Device A8:7E:33:FC:6D:15 Connected: no [CHG] Device A8:7E:33:FC:6D:15 RSSI: -81 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -73 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -65 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -79 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -61 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -75 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 I am using bluez 5.37-0ubuntu5 under Ubuntu 16.04.3 LTS, updated to the day. I found errors in logs: aug 13 17:34:25 george bluetoothd[752]: Starting SDP server aug 13 17:34:26 george ModemManager[738]: ModemManager (version 1.4.12) starting in system bus... aug 13 17:34:26 george kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3 aug 13 17:34:26 george kernel: Bluetooth: BNEP filters: protocol multicast aug 13 17:34:26 george kernel: Bluetooth: BNEP socket layer initialized aug 13 17:34:26 george bluetoothd[752]: Bluetooth management interface 1.10 initialized aug 13 17:34:26 george dbus[702]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.fre aug 13 17:34:26 george bluetoothd[752]: Failed to obtain handles for "Service Changed" characteristic aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Error adding Link Loss service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Current Time Service could not be registered aug 13 17:34:26 george bluetoothd[752]: gatt-time-server: Input/output error (5) aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Sap driver initialization failed. aug 13 17:34:26 george bluetoothd[752]: sap-server: Operation not permitted (1) aug 13 17:35:00 george dbus[702]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.22" (uid=100 aug 13 17:35:14 george sudo[1199]: user : TTY=pts/0 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:35:14 george sudo[1199]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:35:23 george systemd[1]: Starting Stop ureadahead data collection... aug 13 17:35:23 george systemd[1]: Started Stop ureadahead data collection. aug 13 17:35:23 george systemd[1]: Stopped Read required files in advance. aug 13 17:43:26 george sudo[1199]: pam_unix(sudo:session): session closed for user root aug 13 17:47:44 george sshd[1389]: Accepted publickey for user from 192.168.69.200 port 57812 ssh2: RSA SHA256:MQ3JEM2k/Yw2jzz aug 13 17:47:44 george sshd[1389]: pam_unix(sshd:session): session opened for user user by (uid=0) aug 13 17:47:44 george systemd-logind[742]: New session 2 of user user. aug 13 17:47:44 george systemd[1]: Started Session 2 of user user. aug 13 17:47:52 george sudo[1431]: user : TTY=pts/1 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:47:52 george sudo[1431]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:49:30 george /usr/lib/snapd/snapd[685]: snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd[1]: Starting Cleanup of Temporary Directories... aug 13 17:49:30 george snapd[685]: 2017/08/13 17:49:30.803962 snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd-tmpfiles[1459]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. aug 13 17:49:31 george systemd[1]: Started Cleanup of Temporary Directories. aug 13 17:53:16 george sudo[1520]: user : TTY=pts/0 ; PWD=/var/log ; USER=root ; COMMAND=/usr/bin/vim -R dmesg aug 13 17:53:16 george sudo[1
[Touch-packages] [Bug 1710601] Re: bluetoothctl fails to connect
bluetoothd is still running after the problem occurs. there is a /var/crash/_usr_lib_blueman_blueman-rfcomm-watcher.0.crash which in my opinion refers to an unrelated incident involving blueman. if you want I can upload the file. -- 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/1710601 Title: bluetoothctl fails to connect Status in bluez package in Ubuntu: Incomplete Bug description: bluetooth stopped working after some update, probably to bluez5 before it was working flawlessly following https://wiki.archlinux.org/index.php/Bluetooth#Configuration_via_the_CLI now $ bluetoothctl shows no typed characters, $ sudo bluetoothctl works well until I try to connect the device: [bluetooth]# connect A8:7E:33:FC:6D:15 Attempting to connect to A8:7E:33:FC:6D:15 [CHG] Device A8:7E:33:FC:6D:15 Connected: yes Failed to connect: org.bluez.Error.NotAvailable [CHG] Device A8:7E:33:FC:6D:15 Connected: no [CHG] Device A8:7E:33:FC:6D:15 RSSI: -81 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -73 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -65 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -79 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -61 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -75 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 I am using bluez 5.37-0ubuntu5 under Ubuntu 16.04.3 LTS, updated to the day. I found errors in logs: aug 13 17:34:25 george bluetoothd[752]: Starting SDP server aug 13 17:34:26 george ModemManager[738]: ModemManager (version 1.4.12) starting in system bus... aug 13 17:34:26 george kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3 aug 13 17:34:26 george kernel: Bluetooth: BNEP filters: protocol multicast aug 13 17:34:26 george kernel: Bluetooth: BNEP socket layer initialized aug 13 17:34:26 george bluetoothd[752]: Bluetooth management interface 1.10 initialized aug 13 17:34:26 george dbus[702]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.fre aug 13 17:34:26 george bluetoothd[752]: Failed to obtain handles for "Service Changed" characteristic aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Error adding Link Loss service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Current Time Service could not be registered aug 13 17:34:26 george bluetoothd[752]: gatt-time-server: Input/output error (5) aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Sap driver initialization failed. aug 13 17:34:26 george bluetoothd[752]: sap-server: Operation not permitted (1) aug 13 17:35:00 george dbus[702]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.22" (uid=100 aug 13 17:35:14 george sudo[1199]: user : TTY=pts/0 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:35:14 george sudo[1199]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:35:23 george systemd[1]: Starting Stop ureadahead data collection... aug 13 17:35:23 george systemd[1]: Started Stop ureadahead data collection. aug 13 17:35:23 george systemd[1]: Stopped Read required files in advance. aug 13 17:43:26 george sudo[1199]: pam_unix(sudo:session): session closed for user root aug 13 17:47:44 george sshd[1389]: Accepted publickey for user from 192.168.69.200 port 57812 ssh2: RSA SHA256:MQ3JEM2k/Yw2jzz aug 13 17:47:44 george sshd[1389]: pam_unix(sshd:session): session opened for user user by (uid=0) aug 13 17:47:44 george systemd-logind[742]: New session 2 of user user. aug 13 17:47:44 george systemd[1]: Started Session 2 of user user. aug 13 17:47:52 george sudo[1431]: user : TTY=pts/1 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:47:52 george sudo[1431]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:49:30 george /usr/lib/snapd/snapd[685]: snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd[1]: Starting Cleanup of Temporary Directories... aug 13 17:49:30 george snapd[685]: 2017/08/13 17:49:30.803962 snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd-tmpfiles[1459]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. aug 13 17:49:31 george systemd[1]: Started Cleanup of Temporary Directories. aug 13 17:53:16 george sudo[1520]: user : TTY=pts/0 ; PW
[Touch-packages] [Bug 1710853] Re: [Artful] Some appearance bugs in Ambiance
** Description changed: See screenshots. Firefox : too small arrows (does not happen in Chromium, e.g., ok using Adwaita) Evolution : attachment bar, when displayed and expanded, is truncated (ok using Adwaita) ; it is needed to hover one of the icons to full display it Synaptic : error text field is too small (ok using Adwaita) + Tweaks : misplaced menu bar separator (ok using Adwaita) (Please note that the ubuntu-fr-artful tag is here due to Didier Roche's request.) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170703-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Aug 15 11:57:47 2017 InstallationDate: Installed on 2016-12-12 (245 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Alpha amd64 (20161211) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-themes UpgradeStatus: Upgraded to artful on 2017-05-04 (102 days ago) ** Attachment added: "Tweaks" https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1710853/+attachment/4932674/+files/Capture%20d%27%C3%A9cran%20de%202017-08-15%2012-33-09.png ** Description changed: See screenshots. Firefox : too small arrows (does not happen in Chromium, e.g., ok using Adwaita) Evolution : attachment bar, when displayed and expanded, is truncated (ok using Adwaita) ; it is needed to hover one of the icons to full display it Synaptic : error text field is too small (ok using Adwaita) - Tweaks : misplaced menu bar separator (ok using Adwaita) + Tweaks : misplaced menu bar separator (ok using Adwaita), the separator should be aligned with menu field below (Please note that the ubuntu-fr-artful tag is here due to Didier Roche's request.) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170703-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Aug 15 11:57:47 2017 InstallationDate: Installed on 2016-12-12 (245 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Alpha amd64 (20161211) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-themes UpgradeStatus: Upgraded to artful on 2017-05-04 (102 days ago) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1710853 Title: [Artful] Some appearance bugs in Ambiance Status in ubuntu-themes package in Ubuntu: New Bug description: See screenshots. Firefox : too small arrows (does not happen in Chromium, e.g., ok using Adwaita) Evolution : attachment bar, when displayed and expanded, is truncated (ok using Adwaita) ; it is needed to hover one of the icons to full display it Synaptic : error text field is too small (ok using Adwaita) Tweaks : misplaced menu bar separator (ok using Adwaita), the separator should be aligned with menu field below (Please note that the ubuntu-fr-artful tag is here due to Didier Roche's request.) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170703-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Aug 15 11:57:47 2017 InstallationDate: Installed on 2016-12-12 (245 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Alpha amd64 (20161211) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-themes UpgradeStatus: Upgraded to artful on 2017-05-04 (102 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1710853/+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 1710853] Re: [Artful] Some appearance bugs in Ambiance
** Attachment added: "Evolution attachment bar, unexpanded" https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1710853/+attachment/4932658/+files/Capture%20d%27%C3%A9cran%20de%202017-08-10%2008-27-48.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1710853 Title: [Artful] Some appearance bugs in Ambiance Status in ubuntu-themes package in Ubuntu: New Bug description: See screenshots. Firefox : too small arrows (does not happen in Chromium, e.g., ok using Adwaita) Evolution : attachment bar, when displayed and expanded, is truncated (ok using Adwaita) ; it is needed to hover one of the icons to full display it Synaptic : error text field is too small (ok using Adwaita) (Please note that the ubuntu-fr-artful tag is here due to Didier Roche's request.) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170703-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Aug 15 11:57:47 2017 InstallationDate: Installed on 2016-12-12 (245 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Alpha amd64 (20161211) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-themes UpgradeStatus: Upgraded to artful on 2017-05-04 (102 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1710853/+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 1710853] Re: [Artful] Some appearance bugs in Ambiance
** Attachment added: "Synaptic usual error message" https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1710853/+attachment/4932660/+files/Capture%20d%27%C3%A9cran%20de%202017-08-14%2023-33-48.png ** Description changed: See screenshots. Firefox : too small arrows (does not happen in Chromium, e.g., ok using Adwaita) - Evolution : attachment bar, when displayed and expanded, is truncated (ok using Adwaita) + Evolution : attachment bar, when displayed and expanded, is truncated (ok using Adwaita) ; it is needed to hover one of the icons to full display it Synaptic : error text field is too small (ok using Adwaita) (Please note that the ubuntu-fr-artful tag is here due to Didier Roche's request.) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170703-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Aug 15 11:57:47 2017 InstallationDate: Installed on 2016-12-12 (245 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Alpha amd64 (20161211) PackageArchitecture: all ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=fr_FR.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=fr_FR.UTF-8 + SHELL=/bin/bash SourcePackage: ubuntu-themes UpgradeStatus: Upgraded to artful on 2017-05-04 (102 days ago) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1710853 Title: [Artful] Some appearance bugs in Ambiance Status in ubuntu-themes package in Ubuntu: New Bug description: See screenshots. Firefox : too small arrows (does not happen in Chromium, e.g., ok using Adwaita) Evolution : attachment bar, when displayed and expanded, is truncated (ok using Adwaita) ; it is needed to hover one of the icons to full display it Synaptic : error text field is too small (ok using Adwaita) (Please note that the ubuntu-fr-artful tag is here due to Didier Roche's request.) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170703-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Aug 15 11:57:47 2017 InstallationDate: Installed on 2016-12-12 (245 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Alpha amd64 (20161211) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-themes UpgradeStatus: Upgraded to artful on 2017-05-04 (102 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1710853/+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 1710853] Re: [Artful] Some appearance bugs in Ambiance
** Attachment added: "Firefox" https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1710853/+attachment/4932657/+files/Capture%20d%27%C3%A9cran%20de%202017-08-09%2015-20-32.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1710853 Title: [Artful] Some appearance bugs in Ambiance Status in ubuntu-themes package in Ubuntu: New Bug description: See screenshots. Firefox : too small arrows (does not happen in Chromium, e.g., ok using Adwaita) Evolution : attachment bar, when displayed and expanded, is truncated (ok using Adwaita) ; it is needed to hover one of the icons to full display it Synaptic : error text field is too small (ok using Adwaita) (Please note that the ubuntu-fr-artful tag is here due to Didier Roche's request.) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170703-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Aug 15 11:57:47 2017 InstallationDate: Installed on 2016-12-12 (245 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Alpha amd64 (20161211) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-themes UpgradeStatus: Upgraded to artful on 2017-05-04 (102 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1710853/+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 1710853] Re: [Artful] Some appearance bugs in Ambiance
** Attachment added: "Evolution attachment bar, using Adwaita" https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1710853/+attachment/4932659/+files/Capture%20d%27%C3%A9cran%20de%202017-08-10%2008-28-20.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1710853 Title: [Artful] Some appearance bugs in Ambiance Status in ubuntu-themes package in Ubuntu: New Bug description: See screenshots. Firefox : too small arrows (does not happen in Chromium, e.g., ok using Adwaita) Evolution : attachment bar, when displayed and expanded, is truncated (ok using Adwaita) ; it is needed to hover one of the icons to full display it Synaptic : error text field is too small (ok using Adwaita) (Please note that the ubuntu-fr-artful tag is here due to Didier Roche's request.) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170703-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Aug 15 11:57:47 2017 InstallationDate: Installed on 2016-12-12 (245 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Alpha amd64 (20161211) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-themes UpgradeStatus: Upgraded to artful on 2017-05-04 (102 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1710853/+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 1710853] [NEW] [Artful] Some appearance bugs in Ambiance
Public bug reported: See screenshots. Firefox : too small arrows (does not happen in Chromium, e.g., ok using Adwaita) Evolution : attachment bar, when displayed and expanded, is truncated (ok using Adwaita) ; it is needed to hover one of the icons to full display it Synaptic : error text field is too small (ok using Adwaita) (Please note that the ubuntu-fr-artful tag is here due to Didier Roche's request.) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170703-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Aug 15 11:57:47 2017 InstallationDate: Installed on 2016-12-12 (245 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Alpha amd64 (20161211) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-themes UpgradeStatus: Upgraded to artful on 2017-05-04 (102 days ago) ** Affects: ubuntu-themes (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ubuntu-fr-artful ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1710853/+attachment/4932656/+files/ProcCpuinfoMinimal.txt ** Attachment removed: "JournalErrors.txt" https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1710853/+attachment/4932655/+files/JournalErrors.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1710853 Title: [Artful] Some appearance bugs in Ambiance Status in ubuntu-themes package in Ubuntu: New Bug description: See screenshots. Firefox : too small arrows (does not happen in Chromium, e.g., ok using Adwaita) Evolution : attachment bar, when displayed and expanded, is truncated (ok using Adwaita) ; it is needed to hover one of the icons to full display it Synaptic : error text field is too small (ok using Adwaita) (Please note that the ubuntu-fr-artful tag is here due to Didier Roche's request.) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170703-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Aug 15 11:57:47 2017 InstallationDate: Installed on 2016-12-12 (245 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Alpha amd64 (20161211) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-themes UpgradeStatus: Upgraded to artful on 2017-05-04 (102 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1710853/+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 1207004] Re: certdata2pem.py doesn't handle CKT_NSS_MUST_VERIFY_TRUST
** Changed in: ca-certificates (Debian) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1207004 Title: certdata2pem.py doesn't handle CKT_NSS_MUST_VERIFY_TRUST Status in ca-certificates package in Ubuntu: Confirmed Status in ca-certificates package in Debian: Fix Released Bug description: Hello, I'm a Python core developer and hobbyist security researcher. While I was working on my own parser for Mozillas certdata.txt [1] I found an issue in curls mk-ca-bundle.pl script. Today I found the same issue in Debian's and Ubuntu's script. The Python script ./mozilla/certdata2pem.py of ca-certificates-20120623 doesn't handle the flag CKT_NSS_MUST_VERIFY_TRUST. The flag was introduced in revision 1.84 of certdata.txt, see [2] The PKCS#11 glue documentation [3] of the freedesktop.org project has some background information on the flag, too. Quote: --- The certificate is not a trusted anchor (even if a later trust record in another PKCS #11 module says this cert should be trusted). If the marked certificate is self-signed, then this is semantically equivalent to CKT_NSS_NOT_TRUSTED, except NSS will return a different error code (unknown CA for CKT_NSS_MUST_VERIFY_TRUST versus untrusted CA for CKT_NSS_NOT_TRUSTED). --- May I suggest that you reverse the check and distrust any certificate unless it was explicitly flagged as a trusted delegator and root CA cert? In the context of cryptography and TLS it more secure to omit a root CA cert than to wrongly ship a bogus cert. By the way Adam Langley [4] uses the same approach [5]. My Ubuntu box has files like Verisign_Class_1_Public_Primary_Certification_Authority.pem in the /etc/ssl/certs/ directory. According to my script "Verisign Class 1 Public Primary Certification Authority" is flagged as CKT_NSS_MUST_VERIFY_TRUST for CKA_TRUST_SERVER_AUTH [6]. $ LC_ALL=C apt-cache policy ca-certificates ca-certificates: Installed: 20120623 Candidate: 20120623 Version table: *** 20120623 0 500 http://de.archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages 100 /var/lib/dpkg/status $ LC_ALL=C lsb_release -a LSB Version: core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch Distributor ID: Ubuntu Description:Ubuntu 12.10 Release:12.10 Codename: quantal Regards, Christian [1] https://bitbucket.org/tiran/storeroom/ [2] http://lists.debian.org/debian-release/2012/11/msg00411.html [3] http://p11-glue.freedesktop.org/doc/storing-trust-policy/storing-trust-existing.html [4] https://www.imperialviolet.org/2012/01/30/mozillaroots.html [5] https://github.com/agl/extract-nss-root-certs/blob/master/convert_mozilla_certdata.go#L251 [6] https://bitbucket.org/tiran/storeroom/src/e24eef16ff64041ab7792a907f0d69f7b19cd624/certdata/certs.py?at=default#cl-4411 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1207004/+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 1710654] Re: systemd 233-8ubuntu3 ADT test failure with linux 4.12.0-11.12
What would you like me to check? -- 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/1710654 Title: systemd 233-8ubuntu3 ADT test failure with linux 4.12.0-11.12 Status in systemd package in Ubuntu: New Bug description: Testing failed on: armhf: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/armhf/s/systemd/20170814_062054_7f9b9@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1710654/+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 1706052] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1706052/+attachment/4932547/+files/JournalErrors.txt -- 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/1706052 Title: cupsd crashes with SIGSEGV on ubuntu 17.04 on start Status in cups package in Ubuntu: New Bug description: Hey, I upgraded to Ubuntu 17.04, but CUPS crashes on boot, and when I run cupsd it segfaults. Attaching strace ouput. --- ApportVersion: 2.20.4-0ubuntu4.4 Architecture: amd64 CupsErrorLog: CurrentDesktop: KDE DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2012-12-20 (1698 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad file descriptor MachineType: ASUSTeK COMPUTER INC. UX303LB NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: cups 2.2.2-1ubuntu1 PackageArchitecture: amd64 Papersize: letter ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic root=UUID=a8690ccc-4675-4e21-896f-eadcc45159f4 ro quiet splash vga=791 pcie_aspm=force drm.vblankoffdelay=1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic root=UUID=a8690ccc-4675-4e21-896f-eadcc45159f4 ro quiet splash vga=791 pcie_aspm=force drm.vblankoffdelay=1 ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17 Tags: zesty Uname: Linux 4.10.0-28-generic x86_64 UpgradeStatus: Upgraded to zesty on 2017-04-19 (117 days ago) UserGroups: adm bluetooth bumblebee cdrom dialout dip lp lpadmin netdev nvidia-persistenced plugdev sambashare sudo usrp _MarkForUpload: True dmi.bios.date: 03/17/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX303LB.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX303LB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX303LB.203:bd03/17/2015:svnASUSTeKCOMPUTERINC.:pnUX303LB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX303LB dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. mtime.conffile..etc.cups.cupsd.conf: 2015-10-21T13:38:49.740915 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1706052/+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 1706052] KernLog.txt
apport information ** Attachment added: "KernLog.txt" https://bugs.launchpad.net/bugs/1706052/+attachment/4932548/+files/KernLog.txt -- 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/1706052 Title: cupsd crashes with SIGSEGV on ubuntu 17.04 on start Status in cups package in Ubuntu: New Bug description: Hey, I upgraded to Ubuntu 17.04, but CUPS crashes on boot, and when I run cupsd it segfaults. Attaching strace ouput. --- ApportVersion: 2.20.4-0ubuntu4.4 Architecture: amd64 CupsErrorLog: CurrentDesktop: KDE DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2012-12-20 (1698 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad file descriptor MachineType: ASUSTeK COMPUTER INC. UX303LB NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: cups 2.2.2-1ubuntu1 PackageArchitecture: amd64 Papersize: letter ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic root=UUID=a8690ccc-4675-4e21-896f-eadcc45159f4 ro quiet splash vga=791 pcie_aspm=force drm.vblankoffdelay=1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic root=UUID=a8690ccc-4675-4e21-896f-eadcc45159f4 ro quiet splash vga=791 pcie_aspm=force drm.vblankoffdelay=1 ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17 Tags: zesty Uname: Linux 4.10.0-28-generic x86_64 UpgradeStatus: Upgraded to zesty on 2017-04-19 (117 days ago) UserGroups: adm bluetooth bumblebee cdrom dialout dip lp lpadmin netdev nvidia-persistenced plugdev sambashare sudo usrp _MarkForUpload: True dmi.bios.date: 03/17/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX303LB.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX303LB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX303LB.203:bd03/17/2015:svnASUSTeKCOMPUTERINC.:pnUX303LB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX303LB dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. mtime.conffile..etc.cups.cupsd.conf: 2015-10-21T13:38:49.740915 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1706052/+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 1706052] PpdFiles.txt
apport information ** Attachment added: "PpdFiles.txt" https://bugs.launchpad.net/bugs/1706052/+attachment/4932552/+files/PpdFiles.txt -- 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/1706052 Title: cupsd crashes with SIGSEGV on ubuntu 17.04 on start Status in cups package in Ubuntu: New Bug description: Hey, I upgraded to Ubuntu 17.04, but CUPS crashes on boot, and when I run cupsd it segfaults. Attaching strace ouput. --- ApportVersion: 2.20.4-0ubuntu4.4 Architecture: amd64 CupsErrorLog: CurrentDesktop: KDE DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2012-12-20 (1698 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad file descriptor MachineType: ASUSTeK COMPUTER INC. UX303LB NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: cups 2.2.2-1ubuntu1 PackageArchitecture: amd64 Papersize: letter ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic root=UUID=a8690ccc-4675-4e21-896f-eadcc45159f4 ro quiet splash vga=791 pcie_aspm=force drm.vblankoffdelay=1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic root=UUID=a8690ccc-4675-4e21-896f-eadcc45159f4 ro quiet splash vga=791 pcie_aspm=force drm.vblankoffdelay=1 ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17 Tags: zesty Uname: Linux 4.10.0-28-generic x86_64 UpgradeStatus: Upgraded to zesty on 2017-04-19 (117 days ago) UserGroups: adm bluetooth bumblebee cdrom dialout dip lp lpadmin netdev nvidia-persistenced plugdev sambashare sudo usrp _MarkForUpload: True dmi.bios.date: 03/17/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX303LB.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX303LB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX303LB.203:bd03/17/2015:svnASUSTeKCOMPUTERINC.:pnUX303LB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX303LB dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. mtime.conffile..etc.cups.cupsd.conf: 2015-10-21T13:38:49.740915 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1706052/+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 1706052] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1706052/+attachment/4932557/+files/ProcInterrupts.txt -- 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/1706052 Title: cupsd crashes with SIGSEGV on ubuntu 17.04 on start Status in cups package in Ubuntu: New Bug description: Hey, I upgraded to Ubuntu 17.04, but CUPS crashes on boot, and when I run cupsd it segfaults. Attaching strace ouput. --- ApportVersion: 2.20.4-0ubuntu4.4 Architecture: amd64 CupsErrorLog: CurrentDesktop: KDE DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2012-12-20 (1698 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad file descriptor MachineType: ASUSTeK COMPUTER INC. UX303LB NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: cups 2.2.2-1ubuntu1 PackageArchitecture: amd64 Papersize: letter ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic root=UUID=a8690ccc-4675-4e21-896f-eadcc45159f4 ro quiet splash vga=791 pcie_aspm=force drm.vblankoffdelay=1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic root=UUID=a8690ccc-4675-4e21-896f-eadcc45159f4 ro quiet splash vga=791 pcie_aspm=force drm.vblankoffdelay=1 ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17 Tags: zesty Uname: Linux 4.10.0-28-generic x86_64 UpgradeStatus: Upgraded to zesty on 2017-04-19 (117 days ago) UserGroups: adm bluetooth bumblebee cdrom dialout dip lp lpadmin netdev nvidia-persistenced plugdev sambashare sudo usrp _MarkForUpload: True dmi.bios.date: 03/17/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX303LB.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX303LB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX303LB.203:bd03/17/2015:svnASUSTeKCOMPUTERINC.:pnUX303LB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX303LB dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. mtime.conffile..etc.cups.cupsd.conf: 2015-10-21T13:38:49.740915 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1706052/+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 1706052] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1706052/+attachment/4932558/+files/ProcModules.txt -- 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/1706052 Title: cupsd crashes with SIGSEGV on ubuntu 17.04 on start Status in cups package in Ubuntu: New Bug description: Hey, I upgraded to Ubuntu 17.04, but CUPS crashes on boot, and when I run cupsd it segfaults. Attaching strace ouput. --- ApportVersion: 2.20.4-0ubuntu4.4 Architecture: amd64 CupsErrorLog: CurrentDesktop: KDE DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2012-12-20 (1698 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad file descriptor MachineType: ASUSTeK COMPUTER INC. UX303LB NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: cups 2.2.2-1ubuntu1 PackageArchitecture: amd64 Papersize: letter ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic root=UUID=a8690ccc-4675-4e21-896f-eadcc45159f4 ro quiet splash vga=791 pcie_aspm=force drm.vblankoffdelay=1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic root=UUID=a8690ccc-4675-4e21-896f-eadcc45159f4 ro quiet splash vga=791 pcie_aspm=force drm.vblankoffdelay=1 ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17 Tags: zesty Uname: Linux 4.10.0-28-generic x86_64 UpgradeStatus: Upgraded to zesty on 2017-04-19 (117 days ago) UserGroups: adm bluetooth bumblebee cdrom dialout dip lp lpadmin netdev nvidia-persistenced plugdev sambashare sudo usrp _MarkForUpload: True dmi.bios.date: 03/17/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX303LB.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX303LB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX303LB.203:bd03/17/2015:svnASUSTeKCOMPUTERINC.:pnUX303LB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX303LB dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. mtime.conffile..etc.cups.cupsd.conf: 2015-10-21T13:38:49.740915 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1706052/+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 1706052] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1706052/+attachment/4932556/+files/ProcEnviron.txt -- 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/1706052 Title: cupsd crashes with SIGSEGV on ubuntu 17.04 on start Status in cups package in Ubuntu: New Bug description: Hey, I upgraded to Ubuntu 17.04, but CUPS crashes on boot, and when I run cupsd it segfaults. Attaching strace ouput. --- ApportVersion: 2.20.4-0ubuntu4.4 Architecture: amd64 CupsErrorLog: CurrentDesktop: KDE DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2012-12-20 (1698 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad file descriptor MachineType: ASUSTeK COMPUTER INC. UX303LB NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: cups 2.2.2-1ubuntu1 PackageArchitecture: amd64 Papersize: letter ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic root=UUID=a8690ccc-4675-4e21-896f-eadcc45159f4 ro quiet splash vga=791 pcie_aspm=force drm.vblankoffdelay=1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic root=UUID=a8690ccc-4675-4e21-896f-eadcc45159f4 ro quiet splash vga=791 pcie_aspm=force drm.vblankoffdelay=1 ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17 Tags: zesty Uname: Linux 4.10.0-28-generic x86_64 UpgradeStatus: Upgraded to zesty on 2017-04-19 (117 days ago) UserGroups: adm bluetooth bumblebee cdrom dialout dip lp lpadmin netdev nvidia-persistenced plugdev sambashare sudo usrp _MarkForUpload: True dmi.bios.date: 03/17/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX303LB.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX303LB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX303LB.203:bd03/17/2015:svnASUSTeKCOMPUTERINC.:pnUX303LB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX303LB dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. mtime.conffile..etc.cups.cupsd.conf: 2015-10-21T13:38:49.740915 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1706052/+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