[Touch-packages] [Bug 1645257] [NEW] bluetoothd does not notice udev-induced device name change
Public bug reported: Cheers, using Ubuntu 16.10 and bluez 5.41-0ubuntu3 from yakkety, using Bluetooth NAP functionality to connect a device via the system's network connect fails because udev renames the device when it is registered and bluetoothd fails to realize that: Nov 28 10:26:21 fenrir kernel: bluetooth hci0:256 enx340286443693: renamed from bnep0 Nov 28 10:26:21 fenrir bluetoothd[2224]: bnep: Can't add bnep0 to the bridge pan1: No such device(19) Nov 28 10:26:21 fenrir bluetoothd[2224]: BNEP server cannot be added Expected results would, of course, be "added enx340286443693 to the bridge pan1". ** Affects: bluez (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1645257 Title: bluetoothd does not notice udev-induced device name change Status in bluez package in Ubuntu: New Bug description: Cheers, using Ubuntu 16.10 and bluez 5.41-0ubuntu3 from yakkety, using Bluetooth NAP functionality to connect a device via the system's network connect fails because udev renames the device when it is registered and bluetoothd fails to realize that: Nov 28 10:26:21 fenrir kernel: bluetooth hci0:256 enx340286443693: renamed from bnep0 Nov 28 10:26:21 fenrir bluetoothd[2224]: bnep: Can't add bnep0 to the bridge pan1: No such device(19) Nov 28 10:26:21 fenrir bluetoothd[2224]: BNEP server cannot be added Expected results would, of course, be "added enx340286443693 to the bridge pan1". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1645257/+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 1467481] [NEW] Fails silently when no network present
Public bug reported: If no network connection is present and on the additional driver tab one selects a driver that needs to download packages, 'apply changes' fails, reverting to previous setting, without further comment. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: software-properties-common 0.96.4 ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8 Uname: Linux 3.19.0-21-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jun 22 13:33:24 2015 InstallationDate: Installed on 2013-05-06 (776 days ago) InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Release amd64 (20130424) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: Upgraded to vivid on 2014-10-23 (241 days ago) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug gnome3-ppa third-party-packages vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1467481 Title: Fails silently when no network present Status in software-properties package in Ubuntu: New Bug description: If no network connection is present and on the additional driver tab one selects a driver that needs to download packages, 'apply changes' fails, reverting to previous setting, without further comment. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: software-properties-common 0.96.4 ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8 Uname: Linux 3.19.0-21-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jun 22 13:33:24 2015 InstallationDate: Installed on 2013-05-06 (776 days ago) InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Release amd64 (20130424) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: Upgraded to vivid on 2014-10-23 (241 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1467481/+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 1426358] [NEW] upgrade of whoopsie fails due to report_crashes=false
Public bug reported: Cheers, I'm using systemd and have set report_crashes=false in /etc/default/whoopsie. The systemctl service $ systemctl status whoopsie.service whoopsie.service - crash report submission daemon Loaded: loaded (/lib/systemd/system/whoopsie.service; enabled) Active: failed (Result: start-limit) since Fr 2015-02-27 13:52:53 CET; 7s ago Process: 22882 ExecStartPre=/bin/grep -sqi report_crashes=true /etc/default/whoopsie (code=exited, status=1/FAILURE) fails as one would expect; but having these kind of startup requirements in the systemd service is probably a bad idea, especially as it leaves the package unconfigured: $ sudo dpkg --configure --pending Setting up whoopsie (0.2.39ubuntu0.2) ... Job for whoopsie.service failed. See 'systemctl status whoopsie.service' and 'journalctl -xn' for details. invoke-rc.d: initscript whoopsie, action start failed. dpkg: error processing package whoopsie (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: whoopsie ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: whoopsie 0.2.39ubuntu0.2 ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 CrashReports: 640:0:111:272248:2015-02-27 13:37:38.737388070 +0100:2015-02-27 13:37:38.685387839 +0100:/var/crash/whoopsie.0.crash CurrentDesktop: GNOME Date: Fri Feb 27 13:54:04 2015 InstallationDate: Installed on 2013-05-06 (661 days ago) InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Release amd64 (20130424) RelatedPackageVersions: apport-noui N/A SourcePackage: whoopsie UpgradeStatus: Upgraded to utopic on 2014-10-23 (126 days ago) modified.conffile..etc.default.whoopsie: [General] report_crashes=false mtime.conffile..etc.default.whoopsie: 2013-12-15T20:44:50.138659 ** Affects: whoopsie (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug autoreport-false utopic -- 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/1426358 Title: upgrade of whoopsie fails due to report_crashes=false Status in whoopsie package in Ubuntu: New Bug description: Cheers, I'm using systemd and have set report_crashes=false in /etc/default/whoopsie. The systemctl service $ systemctl status whoopsie.service whoopsie.service - crash report submission daemon Loaded: loaded (/lib/systemd/system/whoopsie.service; enabled) Active: failed (Result: start-limit) since Fr 2015-02-27 13:52:53 CET; 7s ago Process: 22882 ExecStartPre=/bin/grep -sqi report_crashes=true /etc/default/whoopsie (code=exited, status=1/FAILURE) fails as one would expect; but having these kind of startup requirements in the systemd service is probably a bad idea, especially as it leaves the package unconfigured: $ sudo dpkg --configure --pending Setting up whoopsie (0.2.39ubuntu0.2) ... Job for whoopsie.service failed. See 'systemctl status whoopsie.service' and 'journalctl -xn' for details. invoke-rc.d: initscript whoopsie, action start failed. dpkg: error processing package whoopsie (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: whoopsie ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: whoopsie 0.2.39ubuntu0.2 ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 CrashReports: 640:0:111:272248:2015-02-27 13:37:38.737388070 +0100:2015-02-27 13:37:38.685387839 +0100:/var/crash/whoopsie.0.crash CurrentDesktop: GNOME Date: Fri Feb 27 13:54:04 2015 InstallationDate: Installed on 2013-05-06 (661 days ago) InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Release amd64 (20130424) RelatedPackageVersions: apport-noui N/A SourcePackage: whoopsie UpgradeStatus: Upgraded to utopic on 2014-10-23 (126 days ago) modified.conffile..etc.default.whoopsie: [General] report_crashes=false mtime.conffile..etc.default.whoopsie: 2013-12-15T20:44:50.138659 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1426358/+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
