[Touch-packages] [Bug 1644572] Re: package init 1.29ubuntu3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
[Expired for init-system-helpers (Ubuntu) because there has been no activity for 60 days.] ** Changed in: init-system-helpers (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1644572 Title: package init 1.29ubuntu3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in init-system-helpers package in Ubuntu: Expired Bug description: Cannot install any new packages, broke init ProblemType: Package DistroRelease: Ubuntu 16.04 Package: init 1.29ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Thu Nov 24 19:57:35 2016 DpkgTerminalLog: dpkg: error processing package init (--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-11-24 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.10ubuntu1 SourcePackage: init-system-helpers Title: package init 1.29ubuntu3 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/init-system-helpers/+bug/1644572/+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 1661912] [NEW] package util-linux 2.27.1-6ubuntu3.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: I installed drivers for my Space Pilot and after installation I cant update Ubuntu, I cant install anything from software center as well. Please check the issue. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: util-linux 2.27.1-6ubuntu3.2 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 Date: Sun Feb 5 07:15:22 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-09-12 (145 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15ubuntu0.2 SourcePackage: util-linux Title: package util-linux 2.27.1-6ubuntu3.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package third-party-packages xenial -- 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/1661912 Title: package util-linux 2.27.1-6ubuntu3.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in util-linux package in Ubuntu: New Bug description: I installed drivers for my Space Pilot and after installation I cant update Ubuntu, I cant install anything from software center as well. Please check the issue. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: util-linux 2.27.1-6ubuntu3.2 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 Date: Sun Feb 5 07:15:22 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-09-12 (145 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15ubuntu0.2 SourcePackage: util-linux Title: package util-linux 2.27.1-6ubuntu3.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1661912/+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 1655290] Re: RM: Qt 5.7.1 transition related package removals
No, as of today there are no debug symbol packages available under zesty-proposed. -- 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/1655290 Title: RM: Qt 5.7.1 transition related package removals Status in qtbase-opensource-src package in Ubuntu: Confirmed Bug description: Qt 5.7.1 and associated modules and rebuilds are now in zesty- proposed. Please delete the following dropped binary packages: qtbase5-dbg qtbase5-dev-tools-dbg qtbase5-examples-dbg libqt5libqgtk2 qtdeclarative5-dbg qttools5-dbg qttools5-examples-dbg libqt5qml-graphicaleffects qt3d-assimpsceneparser-plugin qt3d-gltfsceneparser-plugin qtmultimedia5-dbg qtlocation5-dbg qtpositioning5-dbg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1655290/+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 1661912] Re: package util-linux 2.27.1-6ubuntu3.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Tags removed: need-duplicate-check -- 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/1661912 Title: package util-linux 2.27.1-6ubuntu3.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in util-linux package in Ubuntu: New Bug description: I installed drivers for my Space Pilot and after installation I cant update Ubuntu, I cant install anything from software center as well. Please check the issue. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: util-linux 2.27.1-6ubuntu3.2 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 Date: Sun Feb 5 07:15:22 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-09-12 (145 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15ubuntu0.2 SourcePackage: util-linux Title: package util-linux 2.27.1-6ubuntu3.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1661912/+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 1655290] Re: RM: Qt 5.7.1 transition related package removals
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: qtbase-opensource-src (Ubuntu) Status: New => Confirmed -- 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/1655290 Title: RM: Qt 5.7.1 transition related package removals Status in qtbase-opensource-src package in Ubuntu: Confirmed Bug description: Qt 5.7.1 and associated modules and rebuilds are now in zesty- proposed. Please delete the following dropped binary packages: qtbase5-dbg qtbase5-dev-tools-dbg qtbase5-examples-dbg libqt5libqgtk2 qtdeclarative5-dbg qttools5-dbg qttools5-examples-dbg libqt5qml-graphicaleffects qt3d-assimpsceneparser-plugin qt3d-gltfsceneparser-plugin qtmultimedia5-dbg qtlocation5-dbg qtpositioning5-dbg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1655290/+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 1661869] Re: maas install fails inside of a 16.04 lxd container due to avahi problems
Oh right, I see now.. too early to comment as usual :( The problem is that you are setting up a "privileged" container for MAAS which does not use UID mapping, hence the issue shows up in the MAAS workflow but not with a normal container deployment. The rlimit-nproc is simply set in /etc/avahi/avahi-daemon.conf, so can easily be tweaked in the package. I believe the idea behind it originally is basically to ensure that avahi cannot be used to execute something else, despite all the chrooting, etc - even if there was a way. Essentially blocking further forking. For that reason, probably makes most sense to simply remove the limit rather than increase it by any given number. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1661869 Title: maas install fails inside of a 16.04 lxd container due to avahi problems Status in MAAS: New Status in avahi package in Ubuntu: New Status in lxd package in Ubuntu: Invalid Bug description: The bug, and workaround, are clearly described in this mailing list thread: https://lists.linuxcontainers.org/pipermail/lxc- users/2016-January/010791.html I'm trying to install MAAS in a LXD container, but that's failing due to avahi package install problems. I'm tagging all packages here. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1661869/+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 1661869] Re: maas install fails inside of a 16.04 lxd container due to avahi problems
Avahi starts fine in a 16.04 container for me. Can you share what errors you are actually seeing Dustin? lxc launch ubuntu:16.04 xenial ssh ubuntu@ sudo apt install avahi-daemon sudo systemctl status avahi-daemon The post you linked is from January 2016 and on 15.10 (wily).. it does in fact not launch correctly on wily but it does fine on xenial. On wily, setting rlimit-nproc=4 seems to fix it, for some reason rlimit- nproc=3 fails on wily though the same setting is working on xenial. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1661869 Title: maas install fails inside of a 16.04 lxd container due to avahi problems Status in MAAS: New Status in avahi package in Ubuntu: New Status in lxd package in Ubuntu: Invalid Bug description: The bug, and workaround, are clearly described in this mailing list thread: https://lists.linuxcontainers.org/pipermail/lxc- users/2016-January/010791.html I'm trying to install MAAS in a LXD container, but that's failing due to avahi package install problems. I'm tagging all packages here. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1661869/+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 1580308] Re: update-initramfs cryptsetup must correctly take into account PARTLABEL inside /etc/fstab
I am NOT using 'btrfs'. I am using 'PARTLABEL' in '/etc/fstab'. -- 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/1580308 Title: update-initramfs cryptsetup must correctly take into account PARTLABEL inside /etc/fstab Status in initramfs-tools package in Ubuntu: New Bug description: Systematically, - With a /etc/fstab using UUID or LABEL, update-initramfs works correctly - With a /etc/fstab using PARTLABEL, update-initramfs displays following error messages : cryptsetup: WARNING: failed to detect canonical device of PARTLABEL=Ubuntu-Gnome cryptsetup: WARNING: could not determine root device from /etc/fstab cryptsetup: WARNING: failed to detect canonical device of PARTLABEL=USR-Ubuntu The cryptsetup part of update-initramfs must correctly take into account PARTLABEL inside /etc/fstab Thank you in advance ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: initramfs-tools 0.122ubuntu8 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Tue May 10 21:14:24 2016 InstallationDate: Installed on 2014-11-03 (553 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: Upgraded to xenial on 2016-05-09 (1 days ago) mtime.conffile..etc.initramfs-tools.initramfs.conf: 2016-02-21T22:22:01 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1580308/+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 1661899] Re: [20ENCTO1WW, Realtek ALC298, Speaker, Internal] No sound at all
After rebooting the sound now works. No idea why exactly, I had done several previous reboots without effect, but the one after the 'sudo alsa force-reload seems to have worked. -- 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/1661899 Title: [20ENCTO1WW, Realtek ALC298, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: This is a fresh install of Ubuntu 16-04 on a Thinkpad P50. Sound works when booting into Windows, but not in Ubuntu. No sound from internal speakers or headphones. Sound controls all seem to work, volume controls and mute buttons work in settings as well as the keyboard sound controls (they show changing volume level etc on the screen, but there is never any sound). I have unsuccessfully used these commands in an attempt to fix the problem: sudo apt-get remove --purge alsa-base pulseaudio sudo apt-get install alsa-base pulseaudio sudo alsa force-reload ( As recommended on this site: https://www.unixmen.com/2012003-howto-resolve-nosound-problem-on-ubuntu/ ) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base (not installed) ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 5 09:43:25 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-02-06 (-1 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: p 2075 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [20ENCTO1WW, Realtek ALC298, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1661899/+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 1661899] [NEW] [20ENCTO1WW, Realtek ALC298, Speaker, Internal] No sound at all
Public bug reported: This is a fresh install of Ubuntu 16-04 on a Thinkpad P50. Sound works when booting into Windows, but not in Ubuntu. No sound from internal speakers or headphones. Sound controls all seem to work, volume controls and mute buttons work in settings as well as the keyboard sound controls (they show changing volume level etc on the screen, but there is never any sound). I have unsuccessfully used these commands in an attempt to fix the problem: sudo apt-get remove --purge alsa-base pulseaudio sudo apt-get install alsa-base pulseaudio sudo alsa force-reload ( As recommended on this site: https://www.unixmen.com/2012003-howto-resolve-nosound-problem-on-ubuntu/ ) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base (not installed) ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 5 09:43:25 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-02-06 (-1 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: p 2075 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [20ENCTO1WW, Realtek ALC298, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1661899 Title: [20ENCTO1WW, Realtek ALC298, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: This is a fresh install of Ubuntu 16-04 on a Thinkpad P50. Sound works when booting into Windows, but not in Ubuntu. No sound from internal speakers or headphones. Sound controls all seem to work, volume controls and mute buttons work in settings as well as the keyboard sound controls (they show changing volume level etc on the screen, but there is never any sound). I have unsuccessfully used these commands in an attempt to fix the problem: sudo apt-get remove --purge alsa-base pulseaudio sudo apt-get install alsa-base pulseaudio sudo alsa force-reload ( As recommended on this site: https://www.unixmen.com/2012003-howto-resolve-nosound-problem-on-ubuntu/ ) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base (not installed) ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 5 09:43:25 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-02-06 (-1 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: p 2075 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [20ENCTO1WW, Realtek ALC298, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1661899/+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 1490349] Re: 15:10 and 16.04: bluetoothd reports "Not enough handles to register service" at start
@aromo Similar issue, couldn't connect UE Boom speaker was just getting
'Unable to register GATT service with handle 0x0001'. Found it strange
that even when the speaker was powered down bluetoothd kept trying to
connect (and disconnect seconds later)
What I found was, UE Boom speakers can be powered on remotely using the
mobile application - which is done through Bluetooth LE. This is why the
speaker was connected even when powered-down because of it was connected
via LE. I could be wrong but I believe the GATT service manages the
messages from LE devices - So I tried disabling Bluetooth Low Energy on
the laptop bluetooth adaptor through this command:
sudo btmgmt le off
Unpaired the speaker, restarted the laptop and afterwards I had no more
"Unable to Register GATT" or "Device is already marked connected
messages" and I was able to connect the speaker through Audio Sink.
Haven't had any issues with it since (except for having to run a2dp.py -
but that is a separate issue)
Perhaps you could try disabling le and see if it works for you too?
--
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/1490349
Title:
15:10 and 16.04: bluetoothd reports "Not enough handles to register
service" at start
Status in bluez package in Ubuntu:
Confirmed
Bug description:
On 15:10 after the bluetooth service has been stopped and restarted it
is not possible to scan or connect to devices:
$ sudo systemctl start bluetooth
$ journalctl --unit=bluetooth | tail -n 19 | awk '{$1="";$2="";$4="";print
$0}'
23:31:53 systemd[1]: Starting Bluetooth service...
23:31:53 bluetoothd[16647]: Bluetooth daemon 5.33
23:31:53 systemd[1]: Started Bluetooth service.
23:31:53 bluetoothd[16647]: Starting SDP server
23:31:53 bluetoothd[16647]: Bluetooth management interface 1.9 initialized
23:31:53 bluetoothd[16647]: Failed to obtain handles for "Service Changed"
characteristic
23:31:53 bluetoothd[16647]: Not enough free handles to register service
23:31:53 bluetoothd[16647]: Error adding Link Loss service
23:31:53 bluetoothd[16647]: Not enough free handles to register service
23:31:53 bluetoothd[16647]: Not enough free handles to register service
23:31:53 bluetoothd[16647]: Not enough free handles to register service
23:31:53 bluetoothd[16647]: Current Time Service could not be registered
23:31:53 bluetoothd[16647]: gatt-time-server: Input/output error (5)
23:31:53 bluetoothd[16647]: Not enough free handles to register service
23:31:53 bluetoothd[16647]: Not enough free handles to register service
23:31:53 bluetoothd[16647]: Sap driver initialization failed.
23:31:53 bluetoothd[16647]: sap-server: Operation not permitted (1)
23:31:53 bluetoothd[16647]: Endpoint registered: sender=:1.440
path=/MediaEndpoint/A2DPSource
23:31:53 bluetoothd[16647]: Endpoint registered: sender=:1.440
path=/MediaEndpoint/A2DPSink
And
$ bluetoothctl
[NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]
[NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard
[NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse
[bluetooth]# scan on
Failed to start discovery: org.bluez.Error.NotReady
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1490349/+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 1659590] Re: containers won't start after lxc and apparmor upgrades in trusty
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lxc (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1659590 Title: containers won't start after lxc and apparmor upgrades in trusty Status in lxc package in Ubuntu: Confirmed Bug description: On January 19 lxc and apparmor were upgraded on our VPN servers: 2017-01-19 06:30:36 upgrade libdbus-1-3:amd64 1.6.18-0ubuntu4.4 1.6.18-0ubuntu4.5 2017-01-19 06:30:37 upgrade python3-lxc:amd64 1.0.8-0ubuntu0.4 1.0.9-0ubuntu2 2017-01-19 06:30:38 upgrade libapparmor1:amd64 2.8.95~2430-0ubuntu5.3 2.10.95-0ubuntu2.5~14.04.1 2017-01-19 06:30:38 upgrade libapparmor-perl:amd64 2.8.95~2430-0ubuntu5.3 2.10.95-0ubuntu2.5~14.04.1 2017-01-19 06:30:38 upgrade apparmor:amd64 2.8.95~2430-0ubuntu5.3 2.10.95-0ubuntu2.5~14.04.1 2017-01-19 06:30:39 upgrade lxc-templates:amd64 1.0.8-0ubuntu0.4 1.0.9-0ubuntu2 2017-01-19 06:30:40 upgrade liblxc1:amd64 1.0.8-0ubuntu0.4 1.0.9-0ubuntu2 2017-01-19 06:30:40 upgrade lxc:amd64 1.0.8-0ubuntu0.4 1.0.9-0ubuntu2 2017-01-19 06:30:41 upgrade libseccomp2:amd64 2.1.0+dfsg-1 2.1.1-1ubuntu1~trusty3 2017-01-19 06:30:42 upgrade dbus:amd64 1.6.18-0ubuntu4.4 1.6.18-0ubuntu4.5 The day after, the servers were rebooted and the application containers running the OpenVPN instances failed to start: + lxc-execute -n network-vpn -f /server/network.vpn/lxc/lxc.conf -- /server/network.vpn/lxc/lxc-start.sh lxc-execute: utils.c: safe_mount: 1391 No such file or directory - Failed to mount proc onto /proc lxc-execute: conf.c: tmp_proc_mount: 4132 No such file or directory - failed to mount /proc in the container. lxc-execute: lsm/apparmor.c: apparmor_process_label_get: 80 No such file or directory - opening /proc/1/attr/current lxc-execute: lsm/apparmor.c: apparmor_process_label_set: 191 No such file or directory - failed to change apparmor profile to lxc-container-default lxc-execute: sync.c: __sync_wait: 57 An error occurred in another process (expected sequence number 5) lxc-execute: start.c: __lxc_start: 1149 failed to spawn 'network-vpn' lxc-execute: cgmanager.c: cgm_remove_cgroup: 523 call to cgmanager_remove_sync failed: invalid request lxc-execute: cgmanager.c: cgm_remove_cgroup: 525 Error removing hugetlb:lxc/network-vpn lxc-execute: cgmanager.c: cgm_remove_cgroup: 523 call to cgmanager_remove_sync failed: invalid request lxc-execute: cgmanager.c: cgm_remove_cgroup: 525 Error removing perf_event:lxc/network-vpn lxc-execute: cgmanager.c: cgm_remove_cgroup: 523 call to cgmanager_remove_sync failed: invalid request lxc-execute: cgmanager.c: cgm_remove_cgroup: 525 Error removing blkio:lxc/network-vpn lxc-execute: cgmanager.c: cgm_remove_cgroup: 523 call to cgmanager_remove_sync failed: invalid request lxc-execute: cgmanager.c: cgm_remove_cgroup: 525 Error removing freezer:lxc/network-vpn lxc-execute: cgmanager.c: cgm_remove_cgroup: 523 call to cgmanager_remove_sync failed: invalid request lxc-execute: cgmanager.c: cgm_remove_cgroup: 525 Error removing devices:lxc/network-vpn lxc-execute: cgmanager.c: cgm_remove_cgroup: 523 call to cgmanager_remove_sync failed: invalid request lxc-execute: cgmanager.c: cgm_remove_cgroup: 525 Error removing memory:lxc/network-vpn lxc-execute: cgmanager.c: cgm_remove_cgroup: 523 call to cgmanager_remove_sync failed: invalid request lxc-execute: cgmanager.c: cgm_remove_cgroup: 525 Error removing name=systemd:lxc/network-vpn lxc-execute: cgmanager.c: cgm_remove_cgroup: 523 call to cgmanager_remove_sync failed: invalid request lxc-execute: cgmanager.c: cgm_remove_cgroup: 525 Error removing cpuacct:lxc/network-vpn lxc-execute: cgmanager.c: cgm_remove_cgroup: 523 call to cgmanager_remove_sync failed: invalid request lxc-execute: cgmanager.c: cgm_remove_cgroup: 525 Error removing cpu:lxc/network-vpn lxc-execute: cgmanager.c: cgm_remove_cgroup: 523 call to cgmanager_remove_sync failed: invalid request lxc-execute: cgmanager.c: cgm_remove_cgroup: 525 Error removing cpuset:lxc/network-vpn We had to downgrade lxc, apparmor and related packages to the latest version from trusty-security instead of trusty-updates to get the VPN up and running again. Details: No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 14.04.5 LTS Release: 14.04 Codename: trusty 3.13.0-107-generic #154-Ubuntu SMP Tue Dec 20 09:57:27 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux Any clue about what's going on? Thanks, Alex To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1659590/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages
[Touch-packages] [Bug 1661869] Re: maas install fails inside of a 16.04 lxd container due to avahi problems
Avahi is setting some rather strict rlimits which affect everything which uses that kernel uid, crossing container boundaries and so breaking containers. Unfortunately MAAS requires a privileged container right now, so you can't resort to uid mapping to avoid this problem. At the LXD level, all we can do to avoid this problem is to allow you to have one distinct id map per container, which we already support. But that's only going to work for unprivileged containers. One fix could be to tweak our avahi to relax or if not that useful, entirely remove those rlimits as it's a rather frequent pain point and I'm not sure of the benefit of those rlimits in the first place. Another fix would be to not have MAAS depend on avahi and let you install and run it without avahi, which is effectively what Brian's instructions do (as they disable avahi-daemon in the container). Marking the LXD task Invalid, as we're already doing all we can in this regard by supporting non-overlapping id maps for unprivileged containers. ** Changed in: lxd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1661869 Title: maas install fails inside of a 16.04 lxd container due to avahi problems Status in MAAS: New Status in avahi package in Ubuntu: New Status in lxd package in Ubuntu: Invalid Bug description: The bug, and workaround, are clearly described in this mailing list thread: https://lists.linuxcontainers.org/pipermail/lxc- users/2016-January/010791.html I'm trying to install MAAS in a LXD container, but that's failing due to avahi package install problems. I'm tagging all packages here. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1661869/+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 1659590] Re: containers won't start after lxc and apparmor upgrades in trusty
fwiw: me too - I'm hitting a related bug; same timeframe I assume similar reasons. Debugging now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1659590 Title: containers won't start after lxc and apparmor upgrades in trusty Status in lxc package in Ubuntu: Confirmed Bug description: On January 19 lxc and apparmor were upgraded on our VPN servers: 2017-01-19 06:30:36 upgrade libdbus-1-3:amd64 1.6.18-0ubuntu4.4 1.6.18-0ubuntu4.5 2017-01-19 06:30:37 upgrade python3-lxc:amd64 1.0.8-0ubuntu0.4 1.0.9-0ubuntu2 2017-01-19 06:30:38 upgrade libapparmor1:amd64 2.8.95~2430-0ubuntu5.3 2.10.95-0ubuntu2.5~14.04.1 2017-01-19 06:30:38 upgrade libapparmor-perl:amd64 2.8.95~2430-0ubuntu5.3 2.10.95-0ubuntu2.5~14.04.1 2017-01-19 06:30:38 upgrade apparmor:amd64 2.8.95~2430-0ubuntu5.3 2.10.95-0ubuntu2.5~14.04.1 2017-01-19 06:30:39 upgrade lxc-templates:amd64 1.0.8-0ubuntu0.4 1.0.9-0ubuntu2 2017-01-19 06:30:40 upgrade liblxc1:amd64 1.0.8-0ubuntu0.4 1.0.9-0ubuntu2 2017-01-19 06:30:40 upgrade lxc:amd64 1.0.8-0ubuntu0.4 1.0.9-0ubuntu2 2017-01-19 06:30:41 upgrade libseccomp2:amd64 2.1.0+dfsg-1 2.1.1-1ubuntu1~trusty3 2017-01-19 06:30:42 upgrade dbus:amd64 1.6.18-0ubuntu4.4 1.6.18-0ubuntu4.5 The day after, the servers were rebooted and the application containers running the OpenVPN instances failed to start: + lxc-execute -n network-vpn -f /server/network.vpn/lxc/lxc.conf -- /server/network.vpn/lxc/lxc-start.sh lxc-execute: utils.c: safe_mount: 1391 No such file or directory - Failed to mount proc onto /proc lxc-execute: conf.c: tmp_proc_mount: 4132 No such file or directory - failed to mount /proc in the container. lxc-execute: lsm/apparmor.c: apparmor_process_label_get: 80 No such file or directory - opening /proc/1/attr/current lxc-execute: lsm/apparmor.c: apparmor_process_label_set: 191 No such file or directory - failed to change apparmor profile to lxc-container-default lxc-execute: sync.c: __sync_wait: 57 An error occurred in another process (expected sequence number 5) lxc-execute: start.c: __lxc_start: 1149 failed to spawn 'network-vpn' lxc-execute: cgmanager.c: cgm_remove_cgroup: 523 call to cgmanager_remove_sync failed: invalid request lxc-execute: cgmanager.c: cgm_remove_cgroup: 525 Error removing hugetlb:lxc/network-vpn lxc-execute: cgmanager.c: cgm_remove_cgroup: 523 call to cgmanager_remove_sync failed: invalid request lxc-execute: cgmanager.c: cgm_remove_cgroup: 525 Error removing perf_event:lxc/network-vpn lxc-execute: cgmanager.c: cgm_remove_cgroup: 523 call to cgmanager_remove_sync failed: invalid request lxc-execute: cgmanager.c: cgm_remove_cgroup: 525 Error removing blkio:lxc/network-vpn lxc-execute: cgmanager.c: cgm_remove_cgroup: 523 call to cgmanager_remove_sync failed: invalid request lxc-execute: cgmanager.c: cgm_remove_cgroup: 525 Error removing freezer:lxc/network-vpn lxc-execute: cgmanager.c: cgm_remove_cgroup: 523 call to cgmanager_remove_sync failed: invalid request lxc-execute: cgmanager.c: cgm_remove_cgroup: 525 Error removing devices:lxc/network-vpn lxc-execute: cgmanager.c: cgm_remove_cgroup: 523 call to cgmanager_remove_sync failed: invalid request lxc-execute: cgmanager.c: cgm_remove_cgroup: 525 Error removing memory:lxc/network-vpn lxc-execute: cgmanager.c: cgm_remove_cgroup: 523 call to cgmanager_remove_sync failed: invalid request lxc-execute: cgmanager.c: cgm_remove_cgroup: 525 Error removing name=systemd:lxc/network-vpn lxc-execute: cgmanager.c: cgm_remove_cgroup: 523 call to cgmanager_remove_sync failed: invalid request lxc-execute: cgmanager.c: cgm_remove_cgroup: 525 Error removing cpuacct:lxc/network-vpn lxc-execute: cgmanager.c: cgm_remove_cgroup: 523 call to cgmanager_remove_sync failed: invalid request lxc-execute: cgmanager.c: cgm_remove_cgroup: 525 Error removing cpu:lxc/network-vpn lxc-execute: cgmanager.c: cgm_remove_cgroup: 523 call to cgmanager_remove_sync failed: invalid request lxc-execute: cgmanager.c: cgm_remove_cgroup: 525 Error removing cpuset:lxc/network-vpn We had to downgrade lxc, apparmor and related packages to the latest version from trusty-security instead of trusty-updates to get the VPN up and running again. Details: No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 14.04.5 LTS Release: 14.04 Codename: trusty 3.13.0-107-generic #154-Ubuntu SMP Tue Dec 20 09:57:27 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux Any clue about what's going on? Thanks, Alex To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1659590/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1591515] Re: Network manager can't disconnect from wifi or connect to another wifi
i just installed xubuntu-16.04.1-desktop-amd64.iso and have seen the same (or slight variation of the same) behavior a few times over the last several days. machine is a thinkpad x220. lshw identifies the networking h/w as: - ethernet: 82579LM Gigabit Network Connection - wireless: Centrino Advanced-N 6205 [Taylor Peak] first failure case: - connect to wireless network, become active network participant. - attach ethernet cable, become active network participant. - disconnect ethernet cable. - both wired and wireless networks were now in disconnected state, wireless did not reconnect automatically, and there was no list of networks from which to select a connection. another failure case: - use laptop on wireless - put to sleep - wake laptop - same symptoms: both wired and wireless networks were now in disconnected state, wireless did not reconnect automatically, and there was no list of networks from which to select a connection. this has happened several times, but note that it doesn't happen _every_ time. when it does occur, there are two workarounds which will cause the laptop to resume normal operation: - sudo service NetworkManager restart or - sudo iwlist scan -- 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/1591515 Title: Network manager can't disconnect from wifi or connect to another wifi Status in network-manager package in Ubuntu: Incomplete Bug description: After fresh install 16.04 I can't connect to different wifi network and if netbook lost wifi connection I need reboot it because NM can't do anything to reconnect. NM don't show connected wifi name. I attached image that show this bug. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.0-0ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 CRDA: country BY: DFS-ETSI (2402 - 2482 @ 40), (N/A, 20), (N/A) (5170 - 5250 @ 80), (N/A, 20), (N/A) (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS (5490 - 5710 @ 160), (N/A, 27), (0 ms), DFS CurrentDesktop: Unity Date: Sat Jun 11 16:37:25 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-05-14 (27 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) IpRoute: default via 192.168.100.1 dev wlp2s0 proto static metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.100.0/24 dev wlp2s0 proto kernel scope link src 192.168.100.8 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH HUAWEI-KpW2 3a8b63e2-b64e-4e64-b374-4fd453ccf5ec 802-11-wireless 1465652043 Sat 11 Jun 2016 16:34:03 MSK yes 0 no /org/freedesktop/NetworkManager/Settings/1 yes wlp2s0 activated /org/freedesktop/NetworkManager/ActiveConnection/2 Wired connection 1 32e99c74-fafd-483a-aa6f-745655ff5e9f 802-3-ethernet 1465650077 Sat 11 Jun 2016 16:01:17 MSK yes 4294966297no /org/freedesktop/NetworkManager/Settings/2 no -- -- -- nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connected/org/freedesktop/NetworkManager/Devices/2 HUAWEI-KpW2 3a8b63e2-b64e-4e64-b374-4fd453ccf5ec /org/freedesktop/NetworkManager/ActiveConnection/2 enp1s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1591515/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1661869] Re: maas install fails inside of a 16.04 lxd container due to avahi problems
(but keeping ~ubuntu-lxc subscribed to this bug) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1661869 Title: maas install fails inside of a 16.04 lxd container due to avahi problems Status in MAAS: New Status in avahi package in Ubuntu: New Status in lxd package in Ubuntu: Invalid Bug description: The bug, and workaround, are clearly described in this mailing list thread: https://lists.linuxcontainers.org/pipermail/lxc- users/2016-January/010791.html I'm trying to install MAAS in a LXD container, but that's failing due to avahi package install problems. I'm tagging all packages here. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1661869/+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 1530096] Re: Missing command "search" for apt in bash-completion
*** This bug is a duplicate of bug 1573547 ***
https://bugs.launchpad.net/bugs/1573547
Completions for apt are provided by the apt package.
** Package changed: bash-completion (Ubuntu) => apt (Ubuntu)
** This bug has been marked a duplicate of bug 1573547
Apt's bash completion is 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/1530096
Title:
Missing command "search" for apt in bash-completion
Status in apt package in Ubuntu:
Confirmed
Bug description:
1) Ubuntu release
$ lsb_release -rd
Description: Ubuntu 15.10
Release: 15.10
2) Package version
$ apt-cache policy bash-completion
bash-completion:
Installiert: 1:2.1-4.1ubuntu2
Installationskandidat: 1:2.1-4.1ubuntu2
Versionstabelle:
*** 1:2.1-4.1ubuntu2 0
500 http://de.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
100 /var/lib/dpkg/status
3) Expected
I've expected, if I type
$ apt se
that I would get
$ apt search
Or if I type
$ apt s
that I would get
$ apt
search show
4) What happend instead
I get only
$ apt show
But apt has also the command "search".
(5) Suggested Solution
So I looked into the apt file for bash-completion. In line 10 to 12,
there is no command for searching.
Add "search" somewhere in the command list in line 10 to 12.
I've added it behind the command "show".
local COMMANDS=("install" "remove" "purge" "show" "search" "list"
"update" "upgrade" "full-upgrade" "dist-upgrade"
"edit-sources" "help")
File: /usr/share/bash-completion/completions/apt
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1530096/+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 1530096] [NEW] Missing command "search" for apt in bash-completion
You have been subscribed to a public bug:
1) Ubuntu release
$ lsb_release -rd
Description:Ubuntu 15.10
Release:15.10
2) Package version
$ apt-cache policy bash-completion
bash-completion:
Installiert: 1:2.1-4.1ubuntu2
Installationskandidat: 1:2.1-4.1ubuntu2
Versionstabelle:
*** 1:2.1-4.1ubuntu2 0
500 http://de.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
100 /var/lib/dpkg/status
3) Expected
I've expected, if I type
$ apt se
that I would get
$ apt search
Or if I type
$ apt s
that I would get
$ apt
search show
4) What happend instead
I get only
$ apt show
But apt has also the command "search".
(5) Suggested Solution
So I looked into the apt file for bash-completion. In line 10 to 12,
there is no command for searching.
Add "search" somewhere in the command list in line 10 to 12.
I've added it behind the command "show".
local COMMANDS=("install" "remove" "purge" "show" "search" "list"
"update" "upgrade" "full-upgrade" "dist-upgrade"
"edit-sources" "help")
File: /usr/share/bash-completion/completions/apt
** Affects: apt (Ubuntu)
Importance: Low
Status: Confirmed
** Tags: apt trusty wily
--
Missing command "search" for apt in bash-completion
https://bugs.launchpad.net/bugs/1530096
You received this bug notification because you are a member of Ubuntu Touch
seeded packages, which is subscribed to apt 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 1091228] Re: No record of which repository a package was installed from
** Changed in: apt (Ubuntu) Importance: Wishlist => Medium -- 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/1091228 Title: No record of which repository a package was installed from Status in apt package in Ubuntu: New Bug description: Currently, for any given package you have installed, there is no record of which source/repository it was installed from. This is important if, for example, you want to remove an experimental repository (such as a PPA). The repository may no longer contain those packages, and may no longer even exist, but you may still want to remove all software that was installed from that repository (bug 625628). It may also be helpful, when diagnosing problems, to tell whether any installed packages are from unusual sources. apt could record the source used whenever installing or upgrading/downgrading a package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1091228/+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 1091228] Re: No record of which repository a package was installed from
** Changed in: apt (Ubuntu) Importance: Medium => Wishlist -- 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/1091228 Title: No record of which repository a package was installed from Status in apt package in Ubuntu: New Bug description: Currently, for any given package you have installed, there is no record of which source/repository it was installed from. This is important if, for example, you want to remove an experimental repository (such as a PPA). The repository may no longer contain those packages, and may no longer even exist, but you may still want to remove all software that was installed from that repository (bug 625628). It may also be helpful, when diagnosing problems, to tell whether any installed packages are from unusual sources. apt could record the source used whenever installing or upgrading/downgrading a package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1091228/+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 1661799] Re: [16.04] latest gstreamer1.0 update broke WMA support for some audio & video players
*** This bug is a duplicate of bug 1661842 *** https://bugs.launchpad.net/bugs/1661842 ** This bug has been marked a duplicate of bug 1661842 0001-Only-use-AV_CODEC_ID_WRAPPED_AVFRAME-on-new-enough-l.patch breaks wma decoding -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1661799 Title: [16.04] latest gstreamer1.0 update broke WMA support for some audio & video players Status in gstreamer1.0 package in Ubuntu: Confirmed Bug description: Noise won't play any .wma files after Elementary OS update. It displays a message saying it needs the .wma plugin to work (even though it has always worked on .wma files). Asks if I want to download the plugin but then can't find the plugin. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1661799/+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 1013681] Re: make apt-key net-update secure
Did this change ever make it in? ** Changed in: apt (Ubuntu) Assignee: (unassigned) => Michael Vogt (mvo) -- 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/1013681 Title: make apt-key net-update secure Status in apt package in Ubuntu: Triaged Status in apt package in Debian: New Bug description: Attacks are being performed against the 'apt-key net-update' command and it is not considered secure. While it is in the process of being disabled in Ubuntu, it should be improved to be secure. References: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/857472 https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1013128 https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1013639 http://seclists.org/fulldisclosure/2011/Sep/222 http://seclists.org/fulldisclosure/2012/Jun/267 http://seclists.org/fulldisclosure/2012/Jun/271 http://seclists.org/fulldisclosure/2012/Jun/289 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1013681/+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 1013681] Re: make apt-key net-update secure
** No longer affects: apt (Ubuntu Quantal) ** Changed in: apt (Ubuntu) Milestone: quantal-updates => None -- 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/1013681 Title: make apt-key net-update secure Status in apt package in Ubuntu: Triaged Status in apt package in Debian: New Bug description: Attacks are being performed against the 'apt-key net-update' command and it is not considered secure. While it is in the process of being disabled in Ubuntu, it should be improved to be secure. References: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/857472 https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1013128 https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1013639 http://seclists.org/fulldisclosure/2011/Sep/222 http://seclists.org/fulldisclosure/2012/Jun/267 http://seclists.org/fulldisclosure/2012/Jun/271 http://seclists.org/fulldisclosure/2012/Jun/289 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1013681/+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 857472] Re: net-update verifcation checking insecure
** Changed in: apt (Ubuntu) Milestone: ubuntu-11.10 => None -- 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/857472 Title: net-update verifcation checking insecure Status in apt package in Ubuntu: Fix Released Status in apt source package in Oneiric: Fix Released Bug description: From: http://seclists.org/fulldisclosure/2011/Sep/222 its easy to bypass the verification checking in apt-key net-update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/857472/+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 1016643] Re: add-apt-repository downloads gpg key in an insecure fashion
The code for add-apt-repository is in ppa.py from the software- properties package not the apt package. ** No longer affects: software-properties (Ubuntu Hardy) ** No longer affects: apt (Ubuntu) ** No longer affects: apt (Ubuntu Hardy) ** No longer affects: apt (Ubuntu Precise) ** No longer affects: apt (Ubuntu Lucid) ** No longer affects: apt (Ubuntu Natty) ** No longer affects: apt (Ubuntu Oneiric) ** No longer affects: apt (Ubuntu Quantal) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnupg in Ubuntu. https://bugs.launchpad.net/bugs/1016643 Title: add-apt-repository downloads gpg key in an insecure fashion Status in GnuPG: Fix Released Status in gnupg package in Ubuntu: Fix Released Status in gnupg2 package in Ubuntu: Fix Released Status in software-properties package in Ubuntu: Fix Released Status in gnupg source package in Lucid: Fix Released Status in gnupg2 source package in Lucid: Fix Released Status in software-properties source package in Lucid: Fix Released Status in gnupg source package in Natty: Fix Released Status in gnupg2 source package in Natty: Fix Released Status in software-properties source package in Natty: Fix Released Status in gnupg source package in Oneiric: Fix Released Status in gnupg2 source package in Oneiric: Fix Released Status in software-properties source package in Oneiric: Fix Released Status in gnupg source package in Precise: Fix Released Status in gnupg2 source package in Precise: Fix Released Status in software-properties source package in Precise: Fix Released Status in gnupg source package in Quantal: Fix Released Status in gnupg2 source package in Quantal: Fix Released Status in software-properties source package in Quantal: Fix Released Status in gnupg source package in Hardy: Fix Released Status in gnupg2 source package in Hardy: Fix Released Bug description: add-apt-repository can add PPAs and automatically import the PPA gpg key. Unfortunately, it uses apt-key, which in turn uses gpg to download the key from a keyserver. gpg downloads keys from keyservers using the short key id, which is trivial to collide. It is therefore possible to either MITM the point where gpg downloads the key from the keyserver, or to simply upload a second colliding key to the keyserver. This can result in being able to MITM packages installed from PPAs. To manage notifications about this bug go to: https://bugs.launchpad.net/gnupg/+bug/1016643/+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 1661199] Re: Apt-cacher-ng fails on https repo
Think about that: Your proxy returns 403 and you have 20 repositories, and now get 20 messages, each 100 lines long because your proxy decided to go fancy. And of course: If reported as an actual error message, these things also become python exceptions. Or did you really just mean the message after the status code (RFC calls it reason-phrase) and not the entire response body? That's usually reasonable short. That said, apt-cacher-ng gets very creative with these messages, other proxies stick to the standard messages. And the HTTP standard says a client should ignore the messages completely, as they are legacy (compare RFC 7230, 3.1.2). So I'm not sure it's worthwhile to display the reason-phrase either: It's only used by apt-cacher-ng and the standard says we should ignore its contents. -- 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/1661199 Title: Apt-cacher-ng fails on https repo Status in apt package in Ubuntu: Triaged Status in apt-cacher-ng package in Ubuntu: Invalid Bug description: Following the instructions to add the docker repo here: https://docs.docker.com/engine/installation/linux/ubuntu/ /etc/apt/sources.list contains the repo: deb https://apt.dockerproject.org/repo/ ubuntu-xenial main When running through apt-cacher-ng, apt-get update returns: $ sudo apt-get update Ign:1 https://apt.dockerproject.org/repo ubuntu-xenial InRelease Ign:2 https://apt.dockerproject.org/repo ubuntu-xenial Release Ign:3 https://apt.dockerproject.org/repo ubuntu-xenial/main amd64 Packages.diff/Index Ign:4 https://apt.dockerproject.org/repo ubuntu-xenial/main i386 Packages Ign:5 https://apt.dockerproject.org/repo ubuntu-xenial/main all Packages Ign:6 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en_US Ign:7 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en Ign:8 https://apt.dockerproject.org/repo ubuntu-xenial/main amd64 Packages Ign:4 https://apt.dockerproject.org/repo ubuntu-xenial/main i386 Packages Ign:5 https://apt.dockerproject.org/repo ubuntu-xenial/main all Packages Ign:6 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en_US Ign:7 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en Ign:8 https://apt.dockerproject.org/repo ubuntu-xenial/main amd64 Packages Ign:4 https://apt.dockerproject.org/repo ubuntu-xenial/main i386 Packages Ign:5 https://apt.dockerproject.org/repo ubuntu-xenial/main all Packages Ign:6 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en_US Ign:7 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en Ign:8 https://apt.dockerproject.org/repo ubuntu-xenial/main amd64 Packages Ign:4 https://apt.dockerproject.org/repo ubuntu-xenial/main i386 Packages Ign:5 https://apt.dockerproject.org/repo ubuntu-xenial/main all Packages Ign:6 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en_US Ign:7 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en Ign:8 https://apt.dockerproject.org/repo ubuntu-xenial/main amd64 Packages Ign:4 https://apt.dockerproject.org/repo ubuntu-xenial/main i386 Packages Ign:5 https://apt.dockerproject.org/repo ubuntu-xenial/main all Packages Ign:6 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en_US Ign:7 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en Ign:8 https://apt.dockerproject.org/repo ubuntu-xenial/main amd64 Packages Err:4 https://apt.dockerproject.org/repo ubuntu-xenial/main i386 Packages Received HTTP code 403 from proxy after CONNECT Ign:5 https://apt.dockerproject.org/repo ubuntu-xenial/main all Packages Ign:6 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en_US Ign:7 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en Ign:8 https://apt.dockerproject.org/repo ubuntu-xenial/main amd64 Packages Ign:9 http://dl.google.com/linux/chrome/deb stable InRelease Hit:10 http://archive.ubuntu.com/ubuntu xenial InRelease Hit:11 http://dl.google.com/linux/chrome/deb stable Release Hit:13 http://archive.ubuntu.com/ubuntu xenial-updates InRelease Hit:14 http://archive.ubuntu.com/ubuntu xenial-security InRelease Reading package lists... Done W: The repository 'https://apt.dockerproject.org/repo ubuntu-xenial Release' does not have a Release file. N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use. N: See apt-secure(8) manpage for repository creation and user configuration details. E: Failed to fetch https://apt.dockerproject.org/repo/dists/ubuntu-xenial/main/binary-i386/Packages Received HTTP code 403 from proxy after CONNECT E: Some index files failed to download. They have been ignored, or old ones used instead. When apt is set to disable the proxy, using the
[Touch-packages] [Bug 1651801] Re: ethernet does not autostart when associated with openvpn
/etc/openvpn/ I had my certs and keys in my encrypted /home. For some reason, the system can't see the certs and keys at boot time. Moving all those files to /etc/openvpn solved my problem. -- 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/1651801 Title: ethernet does not autostart when associated with openvpn Status in network-manager package in Ubuntu: Confirmed Bug description: I'm having this problem with an ethernet connection configured with openvpn on Ubuntu 16.04.01 LTS. When booting or rebooting, the network won't come up at all. But, if I select "Disconnect VPN" with network- manager the network comes up automatically. After the network comes up, I can enable the VPN and the client connects to the server. No error messages in syslog regarding the ethernet interface or openvpn. Also, the network interface will autoconnect if I unassociate openvpn with the ethernet interface. network-manager 1.2.2-0ubuntu0.16.04.3 network-manager-openvpn 1.1.93-1ubuntu1 openvpn 2.3.10-1ubuntu2 user@server1:~$ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1651801/+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 1661199] Re: Apt-cacher-ng fails on https repo
It would be nice to have some more details, but I think it's a bit unrealistic to display a web page in apt's error handling system. ** Changed in: apt (Ubuntu) Importance: Undecided => Wishlist ** Changed in: apt (Ubuntu) Status: New => Triaged -- 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/1661199 Title: Apt-cacher-ng fails on https repo Status in apt package in Ubuntu: Triaged Status in apt-cacher-ng package in Ubuntu: Invalid Bug description: Following the instructions to add the docker repo here: https://docs.docker.com/engine/installation/linux/ubuntu/ /etc/apt/sources.list contains the repo: deb https://apt.dockerproject.org/repo/ ubuntu-xenial main When running through apt-cacher-ng, apt-get update returns: $ sudo apt-get update Ign:1 https://apt.dockerproject.org/repo ubuntu-xenial InRelease Ign:2 https://apt.dockerproject.org/repo ubuntu-xenial Release Ign:3 https://apt.dockerproject.org/repo ubuntu-xenial/main amd64 Packages.diff/Index Ign:4 https://apt.dockerproject.org/repo ubuntu-xenial/main i386 Packages Ign:5 https://apt.dockerproject.org/repo ubuntu-xenial/main all Packages Ign:6 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en_US Ign:7 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en Ign:8 https://apt.dockerproject.org/repo ubuntu-xenial/main amd64 Packages Ign:4 https://apt.dockerproject.org/repo ubuntu-xenial/main i386 Packages Ign:5 https://apt.dockerproject.org/repo ubuntu-xenial/main all Packages Ign:6 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en_US Ign:7 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en Ign:8 https://apt.dockerproject.org/repo ubuntu-xenial/main amd64 Packages Ign:4 https://apt.dockerproject.org/repo ubuntu-xenial/main i386 Packages Ign:5 https://apt.dockerproject.org/repo ubuntu-xenial/main all Packages Ign:6 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en_US Ign:7 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en Ign:8 https://apt.dockerproject.org/repo ubuntu-xenial/main amd64 Packages Ign:4 https://apt.dockerproject.org/repo ubuntu-xenial/main i386 Packages Ign:5 https://apt.dockerproject.org/repo ubuntu-xenial/main all Packages Ign:6 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en_US Ign:7 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en Ign:8 https://apt.dockerproject.org/repo ubuntu-xenial/main amd64 Packages Ign:4 https://apt.dockerproject.org/repo ubuntu-xenial/main i386 Packages Ign:5 https://apt.dockerproject.org/repo ubuntu-xenial/main all Packages Ign:6 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en_US Ign:7 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en Ign:8 https://apt.dockerproject.org/repo ubuntu-xenial/main amd64 Packages Err:4 https://apt.dockerproject.org/repo ubuntu-xenial/main i386 Packages Received HTTP code 403 from proxy after CONNECT Ign:5 https://apt.dockerproject.org/repo ubuntu-xenial/main all Packages Ign:6 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en_US Ign:7 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en Ign:8 https://apt.dockerproject.org/repo ubuntu-xenial/main amd64 Packages Ign:9 http://dl.google.com/linux/chrome/deb stable InRelease Hit:10 http://archive.ubuntu.com/ubuntu xenial InRelease Hit:11 http://dl.google.com/linux/chrome/deb stable Release Hit:13 http://archive.ubuntu.com/ubuntu xenial-updates InRelease Hit:14 http://archive.ubuntu.com/ubuntu xenial-security InRelease Reading package lists... Done W: The repository 'https://apt.dockerproject.org/repo ubuntu-xenial Release' does not have a Release file. N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use. N: See apt-secure(8) manpage for repository creation and user configuration details. E: Failed to fetch https://apt.dockerproject.org/repo/dists/ubuntu-xenial/main/binary-i386/Packages Received HTTP code 403 from proxy after CONNECT E: Some index files failed to download. They have been ignored, or old ones used instead. When apt is set to disable the proxy, using the following /etc/apt/apt.conf: Acquire::http::Proxy "http://127.0.0.1:/;; Acquire::https::Proxy "DIRECT"; (note that the port has been changed from the default) The response is: $ sudo apt-get update Hit:1 https://apt.dockerproject.org/repo ubuntu-xenial InRelease Ign:2 http://dl.google.com/linux/chrome/deb stable InRelease Hit:3 http://archive.ubuntu.com/ubuntu xenial InRelease Hit:4 http://dl.google.com/linux/chrome/deb stable Release Hit:6 http://archive.ubuntu.com/ubuntu
[Touch-packages] [Bug 1661199] Re: Apt-cacher-ng fails on https repo
Added a task against apt as requested. Eduard, if I understan Simon correctly wouldn't it be possible to deal with this problem by changing the the defaults in acng for PassThroughPattern? ** Also affects: apt (Ubuntu) Importance: Undecided Status: New -- 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/1661199 Title: Apt-cacher-ng fails on https repo Status in apt package in Ubuntu: New Status in apt-cacher-ng package in Ubuntu: Invalid Bug description: Following the instructions to add the docker repo here: https://docs.docker.com/engine/installation/linux/ubuntu/ /etc/apt/sources.list contains the repo: deb https://apt.dockerproject.org/repo/ ubuntu-xenial main When running through apt-cacher-ng, apt-get update returns: $ sudo apt-get update Ign:1 https://apt.dockerproject.org/repo ubuntu-xenial InRelease Ign:2 https://apt.dockerproject.org/repo ubuntu-xenial Release Ign:3 https://apt.dockerproject.org/repo ubuntu-xenial/main amd64 Packages.diff/Index Ign:4 https://apt.dockerproject.org/repo ubuntu-xenial/main i386 Packages Ign:5 https://apt.dockerproject.org/repo ubuntu-xenial/main all Packages Ign:6 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en_US Ign:7 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en Ign:8 https://apt.dockerproject.org/repo ubuntu-xenial/main amd64 Packages Ign:4 https://apt.dockerproject.org/repo ubuntu-xenial/main i386 Packages Ign:5 https://apt.dockerproject.org/repo ubuntu-xenial/main all Packages Ign:6 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en_US Ign:7 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en Ign:8 https://apt.dockerproject.org/repo ubuntu-xenial/main amd64 Packages Ign:4 https://apt.dockerproject.org/repo ubuntu-xenial/main i386 Packages Ign:5 https://apt.dockerproject.org/repo ubuntu-xenial/main all Packages Ign:6 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en_US Ign:7 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en Ign:8 https://apt.dockerproject.org/repo ubuntu-xenial/main amd64 Packages Ign:4 https://apt.dockerproject.org/repo ubuntu-xenial/main i386 Packages Ign:5 https://apt.dockerproject.org/repo ubuntu-xenial/main all Packages Ign:6 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en_US Ign:7 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en Ign:8 https://apt.dockerproject.org/repo ubuntu-xenial/main amd64 Packages Ign:4 https://apt.dockerproject.org/repo ubuntu-xenial/main i386 Packages Ign:5 https://apt.dockerproject.org/repo ubuntu-xenial/main all Packages Ign:6 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en_US Ign:7 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en Ign:8 https://apt.dockerproject.org/repo ubuntu-xenial/main amd64 Packages Err:4 https://apt.dockerproject.org/repo ubuntu-xenial/main i386 Packages Received HTTP code 403 from proxy after CONNECT Ign:5 https://apt.dockerproject.org/repo ubuntu-xenial/main all Packages Ign:6 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en_US Ign:7 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en Ign:8 https://apt.dockerproject.org/repo ubuntu-xenial/main amd64 Packages Ign:9 http://dl.google.com/linux/chrome/deb stable InRelease Hit:10 http://archive.ubuntu.com/ubuntu xenial InRelease Hit:11 http://dl.google.com/linux/chrome/deb stable Release Hit:13 http://archive.ubuntu.com/ubuntu xenial-updates InRelease Hit:14 http://archive.ubuntu.com/ubuntu xenial-security InRelease Reading package lists... Done W: The repository 'https://apt.dockerproject.org/repo ubuntu-xenial Release' does not have a Release file. N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use. N: See apt-secure(8) manpage for repository creation and user configuration details. E: Failed to fetch https://apt.dockerproject.org/repo/dists/ubuntu-xenial/main/binary-i386/Packages Received HTTP code 403 from proxy after CONNECT E: Some index files failed to download. They have been ignored, or old ones used instead. When apt is set to disable the proxy, using the following /etc/apt/apt.conf: Acquire::http::Proxy "http://127.0.0.1:/;; Acquire::https::Proxy "DIRECT"; (note that the port has been changed from the default) The response is: $ sudo apt-get update Hit:1 https://apt.dockerproject.org/repo ubuntu-xenial InRelease Ign:2 http://dl.google.com/linux/chrome/deb stable InRelease Hit:3 http://archive.ubuntu.com/ubuntu xenial InRelease Hit:4 http://dl.google.com/linux/chrome/deb stable Release Hit:6 http://archive.ubuntu.com/ubuntu
[Touch-packages] [Bug 1511875] Re: Can't upgrade from 15.10 Wily to 16.04 Xenial in LXC container
As an update to my comment above, while the release upgrader hung and did not finish the upgrade, it *did* disable all my ppa's and switch over to the Xenial repositories, which ended up leaving my system broken next time I tried pulling in updates (thinking the upgrade had failed completely and the system was still using Trusty repositories). I'm not sure what packages are at Xenial versions and what packages are at still at Trusty versions, there seems to be a mix. So it seems I can't expect Ubuntu to upgrade between LTS versions without barfing all over itself. Gee, what fun. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1511875 Title: Can't upgrade from 15.10 Wily to 16.04 Xenial in LXC container Status in lxc package in Ubuntu: Invalid Status in ubuntu-release-upgrader package in Ubuntu: Triaged Bug description: When I try to upgrade from 15.10 Wily to 16.04 Xenial (actual development version) within an LXC container, the upgrade script hangs at the message „Calculating the changes”. Steps to reproduce: 1. Make an LXC container with Wily (quickest option is to use lxc-create -t download, choose ubuntu, wily, amd64/i386). 2. Boot up the container, log in, „apt-get -y install ubuntu-release-upgrader-core”. 3. Start the upgrade with „do-release-upgrade -d”. You will see that the upgrade process will hang at the message „Calculating the changes”. The process which hangs: „/usr/bin/python3 /tmp/ubuntu-release- upgrader-1mpotr5d/xenial --mode=server --frontend=DistUpgradeViewText --devel-release” With strace, it is revealed that the process hangs at a „futex” system call: futex(0x7f419c10, FUTEX_WAIT_PRIVATE, 0, NULL This system call never returns, the process must be interrupted with CTRL-C or kill. Upgrading to any previous release within an LXC container works without problems, therefore I consider it as a regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1511875/+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 1520893] Re: Emoji should not be a separate keyboard
Don't you think swiping from the bottom (space bar) to the top in order to display the emoji keyboard would make sense? −instead of a button, "difficult" to reach− -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1520893 Title: Emoji should not be a separate keyboard Status in Canonical System Image: Confirmed Status in Ubuntu UX: Triaged Status in ubuntu-keyboard package in Ubuntu: Confirmed Bug description: The primary use of the keyboard switcher is switching languages. But Emoji are used in every language. They are like symbols, and you don't type symbols by switching to a different keyboard. Rather there is a separate button on the keyboard for switching to symbol entering mode. Having emoji on a separate keyboard means a) monolingual people still need to figure out how to use the keyboard switcher and b) bilingual people have to deal with three keyboards rather than a simple toggle switch (see Bug #1520889). To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1520893/+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 1484801] Re: Feature request: gesture keyboard
For my part, I would also like to swipe on the keyboard in order to move the cursor to the left or to the right when the "swipe to type" feature is de-activated. See here for a demo: http://www.idownloadblog.com/2014/01/14 /swipeselection-pro-one-of-the-best-jailbreak-tweaks-of-all-time-just- got-better/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1484801 Title: Feature request: gesture keyboard Status in ubuntu-keyboard package in Ubuntu: Confirmed Bug description: Feature request: keyboard option to allow typing through swiping gestures for words rather than typing letters one by one. Currently available on android keyboard: settings: language and input: Google keyboard: gesture typing. Thanks again for everyone's work on Ubuntu touch. Everytime I use my Meizu Ubuntu phone, the first thing I miss is being able to swipe on the keyboard to type. I've looked around and found: https://bugs.launchpad.net/onboard/+bug/1094395 http://ubuntuforums.org/showthread.php?t=2080510 http://forum.swype.com/showthread.php?11368-SWYPE-for-Ubuntu-Touch-! Have I missed something? Thanks for everyone who is working on the Ubuntu phone! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1484801/+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 1437229] Re: There should be an option in the language settings to switch of Auto corrections (without going to the System Settings)
Maybe a toggle switch on the right side of the auto-correction bar can achieve this behaviour… Or a toggle in the keyboard section of the notification area -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1437229 Title: There should be an option in the language settings to switch of Auto corrections (without going to the System Settings) Status in ubuntu-keyboard: New Status in ubuntu-keyboard package in Ubuntu: Confirmed Bug description: The autocorretion ist very helfull if you write things properly in a language but if you want to use a dialect or abbreveations like "Can u go 2 the superM?" (There are better examples in Austrian dialects) it would be better to have the auto correction switched off. The way through the System Settings is a very long one to achieve the wished behaviour. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-keyboard/+bug/1437229/+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 1651801] Re: ethernet does not autostart when associated with openvpn
@engage1: Could you elaborate? I keep certificates in ~/Documents, which isn't encrypted. Where do you advise moving the PEM files to so it will auto connect correctly? -- 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/1651801 Title: ethernet does not autostart when associated with openvpn Status in network-manager package in Ubuntu: Confirmed Bug description: I'm having this problem with an ethernet connection configured with openvpn on Ubuntu 16.04.01 LTS. When booting or rebooting, the network won't come up at all. But, if I select "Disconnect VPN" with network- manager the network comes up automatically. After the network comes up, I can enable the VPN and the client connects to the server. No error messages in syslog regarding the ethernet interface or openvpn. Also, the network interface will autoconnect if I unassociate openvpn with the ethernet interface. network-manager 1.2.2-0ubuntu0.16.04.3 network-manager-openvpn 1.1.93-1ubuntu1 openvpn 2.3.10-1ubuntu2 user@server1:~$ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1651801/+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 1437229] Re: There should be an option in the language settings to switch of Auto corrections (without going to the System Settings)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-keyboard (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1437229 Title: There should be an option in the language settings to switch of Auto corrections (without going to the System Settings) Status in ubuntu-keyboard: New Status in ubuntu-keyboard package in Ubuntu: Confirmed Bug description: The autocorretion ist very helfull if you write things properly in a language but if you want to use a dialect or abbreveations like "Can u go 2 the superM?" (There are better examples in Austrian dialects) it would be better to have the auto correction switched off. The way through the System Settings is a very long one to achieve the wished behaviour. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-keyboard/+bug/1437229/+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 1651801] Re: ethernet does not autostart when associated with openvpn
Problem resolved. Moved certificates and key to an unencrypted directory. -- 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/1651801 Title: ethernet does not autostart when associated with openvpn Status in network-manager package in Ubuntu: Confirmed Bug description: I'm having this problem with an ethernet connection configured with openvpn on Ubuntu 16.04.01 LTS. When booting or rebooting, the network won't come up at all. But, if I select "Disconnect VPN" with network- manager the network comes up automatically. After the network comes up, I can enable the VPN and the client connects to the server. No error messages in syslog regarding the ethernet interface or openvpn. Also, the network interface will autoconnect if I unassociate openvpn with the ethernet interface. network-manager 1.2.2-0ubuntu0.16.04.3 network-manager-openvpn 1.1.93-1ubuntu1 openvpn 2.3.10-1ubuntu2 user@server1:~$ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1651801/+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 1651801] Re: ethernet does not autostart when associated with openvpn
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1651801 Title: ethernet does not autostart when associated with openvpn Status in network-manager package in Ubuntu: Confirmed Bug description: I'm having this problem with an ethernet connection configured with openvpn on Ubuntu 16.04.01 LTS. When booting or rebooting, the network won't come up at all. But, if I select "Disconnect VPN" with network- manager the network comes up automatically. After the network comes up, I can enable the VPN and the client connects to the server. No error messages in syslog regarding the ethernet interface or openvpn. Also, the network interface will autoconnect if I unassociate openvpn with the ethernet interface. network-manager 1.2.2-0ubuntu0.16.04.3 network-manager-openvpn 1.1.93-1ubuntu1 openvpn 2.3.10-1ubuntu2 user@server1:~$ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1651801/+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 1661869] [NEW] maas install fails inside of a 16.04 lxd container due to avahi problems
Public bug reported: The bug, and workaround, are clearly described in this mailing list thread: https://lists.linuxcontainers.org/pipermail/lxc- users/2016-January/010791.html I'm trying to install MAAS in a LXD container, but that's failing due to avahi package install problems. I'm tagging all packages here. ** Affects: maas Importance: Undecided Status: New ** Affects: avahi (Ubuntu) Importance: Undecided Status: New ** Affects: lxd (Ubuntu) Importance: Undecided Status: New ** Tags: maas-at-home ** Also affects: lxd (Ubuntu) Importance: Undecided Status: New ** Also affects: avahi (Ubuntu) Importance: Undecided Status: New ** Tags added: maas-at-home -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1661869 Title: maas install fails inside of a 16.04 lxd container due to avahi problems Status in MAAS: New Status in avahi package in Ubuntu: New Status in lxd package in Ubuntu: New Bug description: The bug, and workaround, are clearly described in this mailing list thread: https://lists.linuxcontainers.org/pipermail/lxc- users/2016-January/010791.html I'm trying to install MAAS in a LXD container, but that's failing due to avahi package install problems. I'm tagging all packages here. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1661869/+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 1659002] Re: package python-apt 1.1.0~beta1build1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Package changed: python-apt (Ubuntu) => python2.7 (Ubuntu) ** Changed in: python2.7 (Ubuntu) Status: Confirmed => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1659002 Title: package python-apt 1.1.0~beta1build1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in python2.7 package in Ubuntu: New Bug description: 1 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-apt 1.1.0~beta1build1 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 AptOrdering: python-apt: Install python-sip: Configure python-qt4: Configure python-apt: Configure NULL: ConfigurePending Architecture: amd64 Date: Tue Jan 24 16:45:23 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-11-23 (61 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.18 SourcePackage: python-apt Title: package python-apt 1.1.0~beta1build1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1659002/+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 1551274] Re: creating SRP file crashes openssl
** Changed in: openssl (Ubuntu) Importance: Undecided => High -- 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/1551274 Title: creating SRP file crashes openssl Status in openssl package in Ubuntu: Confirmed Bug description: the following, with "test", "test" as passwords, make openssl crash: touch passwd.srpv ; openssl srp -srpvfile passwd.srpv -add user ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: openssl 1.0.2f-2ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1 Uname: Linux 4.4.0-4-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Feb 29 16:15:20 2016 InstallationDate: Installed on 2015-12-02 (89 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151027) SourcePackage: openssl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1551274/+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 1661611] Re: apt/unattended-upgrades stalls shutdown
I'am effected by the same bug and here is a analysis made by someone else: http://askubuntu.com/questions/878630/apt-unattended-upgrades-stalls-shutdown The suggested patch works well. I hope it won't take too long to merge it. ** Tags added: xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1661611 Title: apt/unattended-upgrades stalls shutdown Status in unattended-upgrades package in Ubuntu: Confirmed Bug description: When unattended-upgrades is installed, 9 out of 10 shutdowns/reboots hang while "starting unattended upgrades shutdown". This hang stalls the shutdown process for 5-10 mins. If I disable unnattended-upgrades via the /etc/apt/apt.conf.d/20auto- upgrades and/or 50unattended-upgrades, the problems occurs. If I terminate the service before shutdown/reboot (sudo service unattended-upgrades stop) the problem still occurs. If I remove the package (sudo apt remove unattended-upgrades) the problem no longer occurs. This occurs on a freshly installed version of Ubuntu Server 16.04.1 (both unattended-upgrades installed via install GUI or manual install of unattended-upgrades) Both Kern.log & syslog do not show the shutdown process (I believe because the filesystems have already unmounted) Original report: http://askubuntu.com/questions/878630/apt-unattended- upgrades-stalls-shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1661611/+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 1186707] Re: Typo in android-tools-fsutils
Still present in zesty ** Description changed: Package: android-tools-fsutils - Version: 5.1.1r36+git20160322-0ubuntu4 + Version: 5.1.1r36+git20160322-0ubuntu5 The long package description contains a small typo: Android images (.img) are typically ext4 filesystems in a special sparse file format come in a special format. Should be: Android images (.img) are typically ext4 filesystems that come in a special sparse file format. https://translations.launchpad.net/ddtp-ubuntu/raring/+pots/ddtp-ubuntu- main/fr/73/+translate -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to android-tools in Ubuntu. https://bugs.launchpad.net/bugs/1186707 Title: Typo in android-tools-fsutils Status in Package Descriptions for Ubuntu: Triaged Status in android-tools package in Ubuntu: Confirmed Status in Debian: Fix Released Bug description: Package: android-tools-fsutils Version: 5.1.1r36+git20160322-0ubuntu5 The long package description contains a small typo: Android images (.img) are typically ext4 filesystems in a special sparse file format come in a special format. Should be: Android images (.img) are typically ext4 filesystems that come in a special sparse file format. https://translations.launchpad.net/ddtp-ubuntu/raring/+pots/ddtp- ubuntu-main/fr/73/+translate To manage notifications about this bug go to: https://bugs.launchpad.net/ddtp-ubuntu/+bug/1186707/+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 1659002] Re: package python-apt 1.1.0~beta1build1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Changed in: python-apt (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1659002 Title: package python-apt 1.1.0~beta1build1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in python-apt package in Ubuntu: Confirmed Bug description: 1 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-apt 1.1.0~beta1build1 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 AptOrdering: python-apt: Install python-sip: Configure python-qt4: Configure python-apt: Configure NULL: ConfigurePending Architecture: amd64 Date: Tue Jan 24 16:45:23 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-11-23 (61 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.18 SourcePackage: python-apt Title: package python-apt 1.1.0~beta1build1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1659002/+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 1661799] Re: [16.04] latest gstreamer1.0 update broke WMA support for some audio & video players
** Changed in: gstreamer1.0 (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1661799 Title: [16.04] latest gstreamer1.0 update broke WMA support for some audio & video players Status in gstreamer1.0 package in Ubuntu: Confirmed Bug description: Noise won't play any .wma files after Elementary OS update. It displays a message saying it needs the .wma plugin to work (even though it has always worked on .wma files). Asks if I want to download the plugin but then can't find the plugin. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1661799/+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 1648959] Re: package udev 229-4ubuntu12 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Changed in: systemd (Ubuntu) Importance: Undecided => High -- 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/1648959 Title: package udev 229-4ubuntu12 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in systemd package in Ubuntu: Confirmed Bug description: after installing updates via Software Updater Ubuntu version:16.04.1 LTS ProblemType: Package DistroRelease: Ubuntu 16.04 Package: udev 229-4ubuntu12 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.2 Architecture: amd64 Date: Sat Dec 10 10:52:01 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 1 MachineType: TOSHIBA Satellite L650 ProcKernelCmdLine: file=/cdrom/multiboot/hostname-16.04.1-desktop-amd64/preseed/hostname.seed boot=casper cdrom-detect/try-usb=true persistent persistent-path=/multiboot/hostname-16.04.1-desktop-amd64 noprompt floppy.allowed_drive_mask=0 ignore_uuid live-media-path=/multiboot/hostname-16.04.1-desktop-amd64/casper/ initrd=/multiboot/hostname-16.04.1-desktop-amd64/casper/initrd.lz quiet splash --- debian-installer/language=cs keyboard-configuration/layoutcode?=cz RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: systemd Title: package udev 229-4ubuntu12 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/09/2011 dmi.bios.vendor: INSYDE dmi.bios.version: 2.40 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr2.40:bd11/09/2011:svnTOSHIBA:pnSatelliteL650:pvrPSK1JE-0CR008CZ:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Satellite L650 dmi.product.version: PSK1JE-0CR008CZ dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1648959/+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 769314] Re: System bell completely silent because PulseAudio sample file undefined by default
** Changed in: pulseaudio (Ubuntu) Importance: High => Medium ** Changed in: gnome-media (Ubuntu) Importance: Undecided => Medium ** Changed in: unity (Ubuntu) Importance: Undecided => Medium ** Changed in: pulseaudio (Ubuntu) Status: In Progress => Confirmed -- 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/769314 Title: System bell completely silent because PulseAudio sample file undefined by default Status in Unity: Invalid Status in gnome-media package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Status in unity package in Ubuntu: Invalid Bug description: Binary package hint: unity This bug is about problems using the system bell in Unity or another Compiz-based environment. For problems using the system bell in Ubuntu Classic/Metacity or another Metacity-based environment, please see bug #486154. The system bell (that beep when you backspace on an empty line on a terminal, i.e.) is badly broken using the Unity environment in the Natty beta 2. By default, no sound is produced, and several misconfigurations make it difficult to produce sound either from the PC speaker or Pulse Audio's module-x11-bell. Not knowing what the desired behavior is, I can't say exactly what needs to be fixed. But the combination of the following issues makes the system quite obviously broken. 1) pcskpr is blacklisted. The pcspkr module is necessary for the PC speaker to produce sound. It is blacklisted, so regular users cannot turn the bell on. It would be nice for this to be fixed, but the attitudes displayed in #77010 suggest that it won't be. Nonetheless, I note it here because it interacts with some of the following. 2) The X bell volume is set to 0. (no more true in xenial) As reported by `xset q`, the bell volume is 0 when Unity is started. Both the PC speaker and module-x11-bell respect this setting, so the volume must be turned up (with `xset b on` or `xset b 100`) for either to work. Since both the PC speaker and module-x11-bell are disabled by default, this setting only serves to frustrate attempts to turn them on; it never prevents unwanted sound. 3) module-x11-bell is loaded by /usr/bin/start-pulseaudio-x11 This is a system file, not a user file, so users cannot decide whether they want this module loaded or not. They could write a script to unload the module at login (and hope the module number doesn't vary between boots), but it would be much cleaner to have the modules loaded from a user file, possibly with defaults if the user file doesn't exist. 4) Sample bell.ogg is not loaded. When module-x11-bell is loaded, it is told to use the sample bell.ogg. But no sample is loaded into Pulse Audio. Thus, module-x11-bell traps system bell events (keeping them from going to the PC speaker) without producing any sound. If module-x11-bell is loaded, the sample it calls on should be loaded as well. (To fix this, run `pactl upload-sample /usr/share/sounds/ubuntu/stereo/bell.ogg bell.ogg`.) 5) gnome-volume-control doesn't. The "Sound Effects" tab of gnome-volume-control offers to set the volume and sound for system bell events, but these have no effect. This is because gnome-volume-control is trying to control system bells through metacity. Ideally, it should be rewritten to control module-x11-bell instead, but a temporary fix could be to simply disable this tab. 6) System bell settings don't transfer to the Ubuntu Classic environment. Because that is using metacity, which has it's own set of problems. See bug #486154. This has been from testing in a VM (virtualbox), but all of these behaviors have also been seen in Compiz in various previous versions of Ubuntu running on various hardware. I have reported this bug against several components, as it is really an integration issue. The eventual fix may not involve your component, but please do not mark this bug as invalid until we have at least a roadmap for fixing it. Otherwise, I fear responsibility will be passed from component to component without anything being fixed. Rationales: Unity - As the overarching environment, Unity should be responsible for getting everything integrated. Additionally, some of the problems relate to session startup settings. Pulse Audio - module-x11-bell is not loaded intelligently or correctly. Gnome Media - Own gnome-volume-control. Versions (but note the same behavior has been seen in many earlier versions): unity: 3.8.10-0ubuntu2 pulseaudio: 1:0.9.22+stable-queue-24-g67d18-0ubuntu3 gnome-media: 2.32.0-0ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/769314/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1589147] Re: [MS-7817, Realtek ALC887-VD, Green Headphone Out, Front] Playback problem
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- 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/1589147 Title: [MS-7817, Realtek ALC887-VD, Green Headphone Out, Front] Playback problem Status in alsa-driver package in Ubuntu: Confirmed Bug description: Haven't sound at front output and have sound only rear side In mixer stand mute at headphones for default and no save, after changes and reboot ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kirill 1684 F pulseaudio /dev/snd/controlC0: kirill 1684 F pulseaudio CurrentDesktop: Unity Date: Sat Jun 4 23:51:09 2016 InstallationDate: Installed on 2016-06-04 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all ProcEnviron: LANGUAGE=ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Встроенное аудио - HDA Intel PCH Symptom_Jack: Green Headphone Out, Front Symptom_Type: Only some of outputs are working Title: [MS-7817, Realtek ALC887-VD, Green Headphone Out, Front] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V6.7 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-E33 (MS-7817) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV6.7:bd04/21/2015:svnMSI:pnMS-7817:pvr1.0:rvnMSI:rnH81M-E33(MS-7817):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7817 dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1589147/+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 1661859] Re: crash occurs when i try to install ubuntu with using ubuntu without installation options. package initramfs-tools 0.122ubuntu8 failed to install/upgrade: subprocess
** Tags removed: need-duplicate-check -- 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/1661859 Title: crash occurs when i try to install ubuntu with using ubuntu without installation options. package initramfs-tools 0.122ubuntu8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: crash occurs when i try to install ubuntu with using ubuntu without installation ProblemType: Package DistroRelease: Ubuntu 16.04 Package: initramfs-tools 0.122ubuntu8 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sat Feb 4 16:28:03 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.122ubuntu8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1661859/+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 1661859] [NEW] crash occurs when i try to install ubuntu with using ubuntu without installation options. package initramfs-tools 0.122ubuntu8 failed to install/upgrade: subproces
Public bug reported: crash occurs when i try to install ubuntu with using ubuntu without installation ProblemType: Package DistroRelease: Ubuntu 16.04 Package: initramfs-tools 0.122ubuntu8 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sat Feb 4 16:28:03 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.122ubuntu8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (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 initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1661859 Title: crash occurs when i try to install ubuntu with using ubuntu without installation options. package initramfs-tools 0.122ubuntu8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: crash occurs when i try to install ubuntu with using ubuntu without installation ProblemType: Package DistroRelease: Ubuntu 16.04 Package: initramfs-tools 0.122ubuntu8 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sat Feb 4 16:28:03 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.122ubuntu8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1661859/+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 1661611] Re: apt/unattended-upgrades stalls shutdown
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unattended-upgrades (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1661611 Title: apt/unattended-upgrades stalls shutdown Status in unattended-upgrades package in Ubuntu: Confirmed Bug description: When unattended-upgrades is installed, 9 out of 10 shutdowns/reboots hang while "starting unattended upgrades shutdown". This hang stalls the shutdown process for 5-10 mins. If I disable unnattended-upgrades via the /etc/apt/apt.conf.d/20auto- upgrades and/or 50unattended-upgrades, the problems occurs. If I terminate the service before shutdown/reboot (sudo service unattended-upgrades stop) the problem still occurs. If I remove the package (sudo apt remove unattended-upgrades) the problem no longer occurs. This occurs on a freshly installed version of Ubuntu Server 16.04.1 (both unattended-upgrades installed via install GUI or manual install of unattended-upgrades) Both Kern.log & syslog do not show the shutdown process (I believe because the filesystems have already unmounted) Original report: http://askubuntu.com/questions/878630/apt-unattended- upgrades-stalls-shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1661611/+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 1661851] Re: cannot enter rescue or emergency state from running system
One more info - after making the journal persistent, this is the end of the journal for the session ending with the hang: Feb 04 16:22:00 harry systemd[1]: Stopped ACPI Events Check. Feb 04 16:22:00 harry systemd[1]: Stopped target Sockets. Feb 04 16:22:00 harry systemd[1]: Closed UUID daemon activation socket. Feb 04 16:22:00 harry systemd[1]: Closed RPCbind Server Activation Socket. Feb 04 16:22:00 harry systemd[1]: Closed Syslog Socket. Feb 04 16:22:00 harry systemd[1]: Closed CUPS Scheduler. Feb 04 16:22:00 harry systemd[1]: Closed Socket activation for snappy daemon. Feb 04 16:22:00 harry systemd[1]: Closed D-Bus System Message Bus Socket. Feb 04 16:22:00 harry systemd[1]: Closed Avahi mDNS/DNS-SD Stack Activation Socket. Feb 04 16:22:00 harry systemd[1]: Closed ACPID Listen Socket. Feb 04 16:22:00 harry systemd[1]: Closed /dev/initctl Compatibility Named Pipe. Feb 04 16:22:00 harry systemd[1]: Stopped target Slices. Feb 04 16:22:00 harry systemd[1]: Received SIGRTMIN+21 from PID 4068 (plymouthd). -- 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/1661851 Title: cannot enter rescue or emergency state from running system Status in systemd package in Ubuntu: New Bug description: Typing "systemctl rescue" in a running system brings down the system and prompts Welcome to rescue mode! After logging in, type "journalctl -xb" to view system logs, "systemctl reboot" to reboot, "systemctl default" or ^D to boot into default mode. Press Enter for maintenance (or press Control-D to continue): Unfortunately the system is then completely dead. No keyboard entry works, not even 7 times Ctrl-Alt-Del reboot the system. I have this behaviour on a real 16.04 system and on a VirtualBox VM. On the VM I currently have problems entering rescue mode by GRUB selection (different problem to be files separately), so these two bugs combined make it impossible for me to enter rescue mode there. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu16 ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Feb 4 16:01:01 2017 InstallationDate: Installed on 2015-03-27 (680 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: Hewlett-Packard HP EliteBook 8460p ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-62-generic root=UUID=310be2be-96ea-4fe9-b929-75605e718fdc ro resume=/dev/sda6 loop.max_part=63 quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /etc/systemd/system/display-manager.service → /lib/systemd/system/display-manager.service.d/xdiagnose.conf 3 overridden configuration files found. UpgradeStatus: Upgraded to xenial on 2016-12-01 (64 days ago) dmi.bios.date: 12/22/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SCF Ver. F.22 dmi.board.name: 161C dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 97.4A dmi.chassis.asset.tag: 617H dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SCFVer.F.22:bd12/22/2011:svnHewlett-Packard:pnHPEliteBook8460p:pvrA0001D02:rvnHewlett-Packard:rn161C:rvrKBCVersion97.4A:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8460p dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1661851/+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 1661851] [NEW] cannot enter rescue or emergency state from running system
Public bug reported: Typing "systemctl rescue" in a running system brings down the system and prompts Welcome to rescue mode! After logging in, type "journalctl -xb" to view system logs, "systemctl reboot" to reboot, "systemctl default" or ^D to boot into default mode. Press Enter for maintenance (or press Control-D to continue): Unfortunately the system is then completely dead. No keyboard entry works, not even 7 times Ctrl-Alt-Del reboot the system. I have this behaviour on a real 16.04 system and on a VirtualBox VM. On the VM I currently have problems entering rescue mode by GRUB selection (different problem to be files separately), so these two bugs combined make it impossible for me to enter rescue mode there. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu16 ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Feb 4 16:01:01 2017 InstallationDate: Installed on 2015-03-27 (680 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: Hewlett-Packard HP EliteBook 8460p ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-62-generic root=UUID=310be2be-96ea-4fe9-b929-75605e718fdc ro resume=/dev/sda6 loop.max_part=63 quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /etc/systemd/system/display-manager.service → /lib/systemd/system/display-manager.service.d/xdiagnose.conf 3 overridden configuration files found. UpgradeStatus: Upgraded to xenial on 2016-12-01 (64 days ago) dmi.bios.date: 12/22/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SCF Ver. F.22 dmi.board.name: 161C dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 97.4A dmi.chassis.asset.tag: 617H dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SCFVer.F.22:bd12/22/2011:svnHewlett-Packard:pnHPEliteBook8460p:pvrA0001D02:rvnHewlett-Packard:rn161C:rvrKBCVersion97.4A:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8460p dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard ** Affects: systemd (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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/1661851 Title: cannot enter rescue or emergency state from running system Status in systemd package in Ubuntu: New Bug description: Typing "systemctl rescue" in a running system brings down the system and prompts Welcome to rescue mode! After logging in, type "journalctl -xb" to view system logs, "systemctl reboot" to reboot, "systemctl default" or ^D to boot into default mode. Press Enter for maintenance (or press Control-D to continue): Unfortunately the system is then completely dead. No keyboard entry works, not even 7 times Ctrl-Alt-Del reboot the system. I have this behaviour on a real 16.04 system and on a VirtualBox VM. On the VM I currently have problems entering rescue mode by GRUB selection (different problem to be files separately), so these two bugs combined make it impossible for me to enter rescue mode there. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu16 ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Feb 4 16:01:01 2017 InstallationDate: Installed on 2015-03-27 (680 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: Hewlett-Packard HP EliteBook 8460p ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-62-generic root=UUID=310be2be-96ea-4fe9-b929-75605e718fdc ro resume=/dev/sda6 loop.max_part=63 quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /etc/systemd/system/display-manager.service → /lib/systemd/system/display-manager.service.d/xdiagnose.conf 3 overridden configuration files found. UpgradeStatus: Upgraded to xenial on 2016-12-01 (64 days ago) dmi.bios.date: 12/22/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SCF Ver. F.22 dmi.board.name: 161C dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 97.4A dmi.chassis.asset.tag:
[Touch-packages] [Bug 1475945] Re: blacklisting i2c_i801 breaks trackpad detection on Acer C710, plus other hardware
I have found that iTCO_wdt doesn't work without previously loading i2c-i801 (you can see a pair of references in http://linux-kernel.2935.n7.nabble.com/PATCH-0-5-iTCO-wdt-Add-support-for-Intel-Sunrisepoint-td1160031.html and in https://lkml.org/lkml/2016/9/10/157) As it's blacklisted, it doesn't load even when putting it on /etc/modules. As stated by OP on launchpad discussion, it seems that the original decission to blacklist i2-i801, as correct as it was in its moment, seems to be creating more problems now for modern systems. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1475945 Title: blacklisting i2c_i801 breaks trackpad detection on Acer C710, plus other hardware Status in kmod package in Ubuntu: New Bug description: file: /etc/modprobe.d/blacklist.conf contains the text: # causes failure to suspend on HP compaq nc6000 (Ubuntu: #10306) blacklist i2c_i801 note: actually the correct LP id appears to be https://bugs.launchpad.net/bugs/16602 after short discussion at https://answers.launchpad.net/ubuntu/+source/kmod/+question/269329 I'm raising this as a bug as well as preventing trackpad detection in the case of Acer C710, there is an older bug open at https://bugs.launchpad.net/bugs/857175. Here this same blacklist entry breaks some functionality for a Thinkpad T41. In turn, that bug includes a reference to another source (http://permalink.gmane.org/gmane.linux.drivers.i2c/9120) where the blacklist entry has required support effort. lsb_release -rd Description: Ubuntu 15.04 Release: 15.04 apt-cache policy kmod kmod: Installed: 18-3ubuntu1 Candidate: 18-3ubuntu1 Version table: *** 18-3ubuntu1 0 500 http://au.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1475945/+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 1619600] Re: [SRU] New stable release 1.8.3
New bug, this only affects 16.04 as 17.04 has newer ffmpeg libs Bug 1661842 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1619600 Title: [SRU] New stable release 1.8.3 Status in gst-libav1.0 package in Ubuntu: Fix Released Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in gst-plugins-good1.0 package in Ubuntu: Fix Released Status in gst-plugins-ugly1.0 package in Ubuntu: Fix Released Status in gstreamer-vaapi package in Ubuntu: Fix Released Status in gstreamer1.0 package in Ubuntu: Fix Released Status in gst-libav1.0 source package in Xenial: Fix Released Status in gst-plugins-bad1.0 source package in Xenial: Fix Released Status in gst-plugins-base1.0 source package in Xenial: Fix Released Status in gst-plugins-good1.0 source package in Xenial: Fix Released Status in gst-plugins-ugly1.0 source package in Xenial: Fix Released Status in gstreamer-vaapi source package in Xenial: Fix Released Status in gstreamer1.0 source package in Xenial: Fix Released Bug description: [ Description ] We should keep up with GStreamer's bugfix releases in the 1.8 series that 16.04 shipped with. [ QA and testing ] Play a range of videos in Totem. Play a range of audio tracks in Rhythmbox. Try to stream audio and/or video. Try to install a missing codec. In all cases, make sure that everything which worked before still works. [ Regression potential ] One of the fixes could be bad. Watch out for it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1619600/+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 1661799] Re: Noise won't play any WMA files after recent Elementary OS upgrade
Forgot to mention that it's in 16.04. Got it from xenial-updates repo, and the changelog hints that it was a backport from 16.10. ** Tags added: regression-update xenial ** Summary changed: - Noise won't play any WMA files after recent Elementary OS upgrade + [16.04] latest gstreamer1.0 update broke WMA support for some audio & video players -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1661799 Title: [16.04] latest gstreamer1.0 update broke WMA support for some audio & video players Status in gstreamer1.0 package in Ubuntu: Confirmed Bug description: Noise won't play any .wma files after Elementary OS update. It displays a message saying it needs the .wma plugin to work (even though it has always worked on .wma files). Asks if I want to download the plugin but then can't find the plugin. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1661799/+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 1661799] Re: Noise won't play any WMA files after recent Elementary OS upgrade
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gstreamer1.0 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1661799 Title: [16.04] latest gstreamer1.0 update broke WMA support for some audio & video players Status in gstreamer1.0 package in Ubuntu: Confirmed Bug description: Noise won't play any .wma files after Elementary OS update. It displays a message saying it needs the .wma plugin to work (even though it has always worked on .wma files). Asks if I want to download the plugin but then can't find the plugin. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1661799/+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 1661799] Re: Noise won't play any WMA files after recent Elementary OS upgrade
Same happens in xplayer (a fork of Totem). When trying to play a .wmv file, it shows an error dialog about no support for Windows Media Audio. In the terminal it shows this message: ** Message: Missing plugin: gstreamer|1.0|xplayer|Windows Media Audio 9 decoder|decoder-audio/x-wma, wmaversion=(int)3, bitrate=(int)128040 (Windows Media Audio 9 decoder) This regression started yesterday with the simultaneous upgrade of the following source packages: - gstreamer1.0: 1.8.2-1~ubuntu1 -> 1.8.3-1~ubuntu0.1 - gst-plugins-base1.0: 1.8.2-1ubuntu0.2 -> 1.8.3-1ubuntu0.1 - gst-plugins-good1.0: 1.8.2-1ubuntu0.3 -> 1.8.3-1ubuntu0.3 - gst-plugins-bad1.0: 1.8.2-1ubuntu0.2 -> 1.8.3-1ubuntu0.2 - gst-plugins-ugly1.0: 1.8.2-1ubuntu0.1 -> 1.8.3-1ubuntu0.1 - gst-libav1.0: 1.8.2-1~ubuntu1 -> 1.8.3-1ubuntu0.1 I have no idea which of them broke things, but the bug needs to be reassigned, so let it be gstreamer1.0. ** Project changed: noise => gstreamer1.0 ** Project changed: gstreamer1.0 => gstreamer1.0 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1661799 Title: Noise won't play any WMA files after recent Elementary OS upgrade Status in gstreamer1.0 package in Ubuntu: Confirmed Bug description: Noise won't play any .wma files after Elementary OS update. It displays a message saying it needs the .wma plugin to work (even though it has always worked on .wma files). Asks if I want to download the plugin but then can't find the plugin. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1661799/+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 1661799] [NEW] Noise won't play any WMA files after recent Elementary OS upgrade
You have been subscribed to a public bug: Noise won't play any .wma files after Elementary OS update. It displays a message saying it needs the .wma plugin to work (even though it has always worked on .wma files). Asks if I want to download the plugin but then can't find the plugin. ** Affects: gstreamer1.0 (Ubuntu) Importance: Undecided Status: New -- Noise won't play any WMA files after recent Elementary OS upgrade https://bugs.launchpad.net/bugs/1661799 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 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 1661838] Re: package libdrm-amdgpu1:amd64 2.4.70-1 failed to install/upgrade: package libdrm-amdgpu1:amd64 2.4.70-1 cannot be configured because libdrm-amdgpu1:i386 is at a diffe
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1661838 Title: package libdrm-amdgpu1:amd64 2.4.70-1 failed to install/upgrade: package libdrm-amdgpu1:amd64 2.4.70-1 cannot be configured because libdrm-amdgpu1:i386 is at a different version (2.4.75+git1701280630.d4b834~gd~y) Status in libdrm package in Ubuntu: New Bug description: at start up ProblemType: Package DistroRelease: Ubuntu 16.10 Package: libdrm-amdgpu1:amd64 2.4.70-1 Uname: Linux 4.9.6-040906-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8.2 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: Sat Jan 28 22:44:55 2017 Dependencies: gcc-6-base 6.2.0-5ubuntu12 libc6 2.24-3ubuntu2 libdrm2 2.4.70-1 libgcc1 1:6.2.0-5ubuntu12 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu DuplicateSignature: package:libdrm-amdgpu1:amd64:2.4.70-1 Processing triggers for mime-support (3.60ubuntu1) ... dpkg: error processing package libdrm-amdgpu1:amd64 (--configure): package libdrm-amdgpu1:amd64 2.4.70-1 cannot be configured because libdrm-amdgpu1:i386 is at a different version (2.4.75+git1701280630.d4b834~gd~y) ErrorMessage: package libdrm-amdgpu1:amd64 2.4.70-1 cannot be configured because libdrm-amdgpu1:i386 is at a different version (2.4.75+git1701280630.d4b834~gd~y) GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller [103c:167d] Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M Series] [1002:6760] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Radeon HD 6490M [103c:167d] InstallationDate: Installed on 2016-10-20 (106 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Hewlett-Packard HP ProBook 4530s ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.6-040906-generic root=UUID=97c4a4e9-926d-46af-8e20-628413261f38 ro quiet splash modeset=1 vt.handoff=7 RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.4 SourcePackage: libdrm Title: package libdrm-amdgpu1:amd64 2.4.70-1 failed to install/upgrade: package libdrm-amdgpu1:amd64 2.4.70-1 cannot be configured because libdrm-amdgpu1:i386 is at a different version (2.4.75+git1701280630.d4b834~gd~y) UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/13/2015 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SRR Ver. F.60 dmi.board.name: 167C dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 22.26 dmi.chassis.asset.tag: CNU2082FCF dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SRRVer.F.60:bd03/13/2015:svnHewlett-Packard:pnHPProBook4530s:pvrAC02:rvnHewlett-Packard:rn167C:rvrKBCVersion22.26:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 4530s dmi.product.version: AC02 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Sat Feb 4 15:30:35 2017 xserver.configfile: default xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1661838/+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 1661838] [NEW] package libdrm-amdgpu1:amd64 2.4.70-1 failed to install/upgrade: package libdrm-amdgpu1:amd64 2.4.70-1 cannot be configured because libdrm-amdgpu1:i386 is at a dif
Public bug reported: at start up ProblemType: Package DistroRelease: Ubuntu 16.10 Package: libdrm-amdgpu1:amd64 2.4.70-1 Uname: Linux 4.9.6-040906-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8.2 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: Sat Jan 28 22:44:55 2017 Dependencies: gcc-6-base 6.2.0-5ubuntu12 libc6 2.24-3ubuntu2 libdrm2 2.4.70-1 libgcc1 1:6.2.0-5ubuntu12 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu DuplicateSignature: package:libdrm-amdgpu1:amd64:2.4.70-1 Processing triggers for mime-support (3.60ubuntu1) ... dpkg: error processing package libdrm-amdgpu1:amd64 (--configure): package libdrm-amdgpu1:amd64 2.4.70-1 cannot be configured because libdrm-amdgpu1:i386 is at a different version (2.4.75+git1701280630.d4b834~gd~y) ErrorMessage: package libdrm-amdgpu1:amd64 2.4.70-1 cannot be configured because libdrm-amdgpu1:i386 is at a different version (2.4.75+git1701280630.d4b834~gd~y) GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller [103c:167d] Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M Series] [1002:6760] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Radeon HD 6490M [103c:167d] InstallationDate: Installed on 2016-10-20 (106 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Hewlett-Packard HP ProBook 4530s ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.6-040906-generic root=UUID=97c4a4e9-926d-46af-8e20-628413261f38 ro quiet splash modeset=1 vt.handoff=7 RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.4 SourcePackage: libdrm Title: package libdrm-amdgpu1:amd64 2.4.70-1 failed to install/upgrade: package libdrm-amdgpu1:amd64 2.4.70-1 cannot be configured because libdrm-amdgpu1:i386 is at a different version (2.4.75+git1701280630.d4b834~gd~y) UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/13/2015 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SRR Ver. F.60 dmi.board.name: 167C dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 22.26 dmi.chassis.asset.tag: CNU2082FCF dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SRRVer.F.60:bd03/13/2015:svnHewlett-Packard:pnHPProBook4530s:pvrAC02:rvnHewlett-Packard:rn167C:rvrKBCVersion22.26:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 4530s dmi.product.version: AC02 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Sat Feb 4 15:30:35 2017 xserver.configfile: default xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6.1 xserver.video_driver: modeset ** Affects: libdrm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package compiz-0.9 ubuntu yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1661838 Title: package libdrm-amdgpu1:amd64 2.4.70-1 failed to install/upgrade: package libdrm-amdgpu1:amd64 2.4.70-1 cannot be configured because libdrm-amdgpu1:i386 is at a different version (2.4.75+git1701280630.d4b834~gd~y) Status in libdrm package in Ubuntu: New Bug description: at start up ProblemType: Package DistroRelease: Ubuntu 16.10 Package: libdrm-amdgpu1:amd64 2.4.70-1 Uname: Linux 4.9.6-040906-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8.2 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: Sat Jan 28 22:44:55 2017 Dependencies: gcc-6-base 6.2.0-5ubuntu12 libc6 2.24-3ubuntu2 libdrm2 2.4.70-1
[Touch-packages] [Bug 1661675] Re: too hard to tell which window will be selected in alt-tab window switcher
** Changed in: unity8 (Ubuntu) Assignee: (unassigned) => Michael Zanetti (mzanetti) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1661675 Title: too hard to tell which window will be selected in alt-tab window switcher Status in Ubuntu UX: New Status in unity8 package in Ubuntu: Confirmed Bug description: I find it really difficult to tell which window will be selected when alt-tabbing through my window list on Unity8. The highlighting of the selection is very subtle and there is not change to the window preview or the icon. I thought it would get easier after using unity8 a lot but it really hasn't. I think the following tweaks would make it much more clear which window is selected: 1) The app icon at the bottom should get bigger or some effect applied to it when the app window is selected. My eyes tend to look there as it's less cluttered than the window preview list 2) Make the border around the selected window preview thicker/darker to make it stand out more as currently the border highlighting is very subtle And/Or 3) Make the actual window preview larger (or some other effect to make it move forward) for the selected window so that it's super clear which window is selected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1661675/+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 1636282] Re: network-manager after suspend showing arrow icon instead of wifi icon and showing no wifi networks
After one week, I have not seen this issue anymore. Looks like solved for me. -- 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/1636282 Title: network-manager after suspend showing arrow icon instead of wifi icon and showing no wifi networks Status in network-manager package in Ubuntu: Confirmed Bug description: As requested by Mathieu Trudel-Lapierre (cyphermox) in bug #1589401 I'm creating my own bug report. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu $ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center $ apt-cache policy network-manager network-manager: Installiert: 1.2.2-0ubuntu0.16.04.3 Installationskandidat: 1.2.2-0ubuntu0.16.04.3 Versionstabelle: *** 1.2.2-0ubuntu0.16.04.3 500 500 http://ch.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.1.93-0ubuntu4 500 500 http://ch.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 3) What you expected to happen I'm connected by WiFi only, not by a wired connection. I expect to see the WiFi icon anytime while being connected to my WiFi network. Also, I expect to see all the WiFi networks around me (at least one other network with good reception and about 3 with bad reception). 4) What happened instead After waking up the laptop from suspend, there appears the ethernet icon (arrow symbols) instead of the WiFi icon. Also, in this state there are no other WiFi networks visible in the network-manager. However, the laptop is still connected with my WiFi and the connection works as usual. Using "service network-manager restart" in the console I can get the wireless icon back and all the other networks around me are visible again. This can be reproduced anytime and with 100% "success rate". The problem appeared with Ubuntu 16.10 and was persistent since. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.2-0ubuntu0.16.04.3 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Oct 24 20:06:09 2016 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-05-15 (161 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.1.1 dev wlo1 proto static metric 600 169.254.0.0/16 dev wlo1 scope link metric 1000 192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.244 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlo1wifi connected/org/freedesktop/NetworkManager/Devices/2 WiNet 2 162de978-4466-46b0-957b-5f9c141d702a /org/freedesktop/NetworkManager/ActiveConnection/1 eno1ethernet unavailable /org/freedesktop/NetworkManager/Devices/0 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.2connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1636282/+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 1636573] Re: xinit flooding syslog
Same here, Feb 4 08:06:56 755OTP compiz[2604]: extern "Python": function Cryptography_rand_status() called, but @ffi.def_extern() was not called in the current subinterpreter. Returning 0. Kodi and Ubuntu 16.10 $ lsb_release -a; uname -a; grep -r ppa /etc/apt/* No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.10 Release:16.10 Codename: yakkety Linux 755OTP 4.8.0-37-generic #39-Ubuntu SMP Thu Jan 26 02:27:07 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux /etc/apt/sources.list.d/stebbins-ubuntu-handbrake-releases-wily.list.distUpgrade:# deb http://ppa.launchpad.net/stebbins/handbrake-releases/ubuntu xenial main # забранен при надграждане до xenial /etc/apt/sources.list.d/stebbins-ubuntu-handbrake-releases-wily.list.distUpgrade:# deb-src http://ppa.launchpad.net/stebbins/handbrake-releases/ubuntu wily main /etc/apt/sources.list.d/stebbins-ubuntu-handbrake-releases-wily.list:# deb http://ppa.launchpad.net/stebbins/handbrake-releases/ubuntu xenial main # забранен при надграждане до xenial /etc/apt/sources.list.d/stebbins-ubuntu-handbrake-releases-wily.list:# deb-src http://ppa.launchpad.net/stebbins/handbrake-releases/ubuntu wily main /etc/apt/sources.list.d/graphics-drivers-ubuntu-ppa-yakkety.list:deb http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu yakkety main /etc/apt/sources.list.d/graphics-drivers-ubuntu-ppa-yakkety.list:# deb-src http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu yakkety main /etc/apt/sources.list.d/team-xbmc-ubuntu-ppa-xenial.list.distUpgrade:# deb-src http://ppa.launchpad.net/team-xbmc/ppa/ubuntu xenial main /etc/apt/sources.list.d/team-xbmc-ubuntu-ppa-wily.list:# deb-src http://ppa.launchpad.net/team-xbmc/ppa/ubuntu wily main /etc/apt/sources.list.d/stebbins-ubuntu-handbrake-releases-wily.list.save:# deb http://ppa.launchpad.net/stebbins/handbrake-releases/ubuntu xenial main # забранен при надграждане до xenial /etc/apt/sources.list.d/stebbins-ubuntu-handbrake-releases-wily.list.save:# deb-src http://ppa.launchpad.net/stebbins/handbrake-releases/ubuntu wily main /etc/apt/sources.list.d/team-xbmc-ubuntu-ppa-wily.list.distUpgrade:# deb-src http://ppa.launchpad.net/team-xbmc/ppa/ubuntu wily main /etc/apt/sources.list.d/graphics-drivers-ubuntu-ppa-yakkety.list.save:deb http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu yakkety main /etc/apt/sources.list.d/graphics-drivers-ubuntu-ppa-yakkety.list.save:# deb-src http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu yakkety main /etc/apt/sources.list.d/team-xbmc-ubuntu-ppa-vivid.list.distUpgrade:# deb http://ppa.launchpad.net/team-xbmc/ppa/ubuntu yakkety main # забранен при надграждане до wily забранен при надграждане до xenial забранен при надграждане до yakkety /etc/apt/sources.list.d/team-xbmc-ubuntu-ppa-vivid.list.distUpgrade:# deb-src http://ppa.launchpad.net/team-xbmc/ppa/ubuntu vivid main /etc/apt/sources.list.d/team-xbmc-ubuntu-ppa-wily.list.save:# deb-src http://ppa.launchpad.net/team-xbmc/ppa/ubuntu wily main /etc/apt/sources.list.d/team-xbmc-ubuntu-ppa-vivid.list:deb http://ppa.launchpad.net/team-xbmc/ppa/ubuntu yakkety main # забранен при надграждане до wily забранен при надграждане до xenial забранен при надграждане до yakkety /etc/apt/sources.list.d/team-xbmc-ubuntu-ppa-vivid.list:# deb-src http://ppa.launchpad.net/team-xbmc/ppa/ubuntu vivid main /etc/apt/sources.list.d/team-xbmc-ubuntu-ppa-yakkety.list:# deb-src http://ppa.launchpad.net/team-xbmc/ppa/ubuntu yakkety main /etc/apt/sources.list.d/team-xbmc-ubuntu-ppa-xenial.list:# deb-src http://ppa.launchpad.net/team-xbmc/ppa/ubuntu xenial main /etc/apt/sources.list.d/team-xbmc-ubuntu-ppa-xenial.list.save:# deb-src http://ppa.launchpad.net/team-xbmc/ppa/ubuntu xenial main /etc/apt/sources.list.d/team-xbmc-ubuntu-ppa-vivid.list.save:# deb http://ppa.launchpad.net/team-xbmc/ppa/ubuntu yakkety main # забранен при надграждане до wily забранен при надграждане до xenial забранен при надграждане до yakkety /etc/apt/sources.list.d/team-xbmc-ubuntu-ppa-vivid.list.save:# deb-src http://ppa.launchpad.net/team-xbmc/ppa/ubuntu vivid main Kodi is from ppa, I run Kodi in fulscreen, if I log into Kodi session - no problem, with Unity session problem exist. I will try with gnome shell 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/1636573 Title: xinit flooding syslog Status in pyopenssl package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Invalid Bug description: I am using xinit (1.3.4-3ubuntu1) to start an X11 session as follows (kodi is a media center): /usr/bin/xinit /usr/bin/dbus-launch --exit-with-session /usr/bin/kodi- standalone -- :1 -nolisten tcp vt8 This used to work fine with Ubuntu 16.04, but since the upgrade to 16.10 lots of log messages are sent to syslog. They are all repetitions of the following two lines: Oct 24 22:54:50 tiger
[Touch-packages] [Bug 1661825] Re: interfaces always dhcp in ubuntu template
It's not realistic to do this: - lxc-create is only called when the container is created whereas lxc.network.* can be changed at any point in time - The Ubuntu template maintains a cache of the generated system, so we'd need to do these as an extra step when re-using the cache as we sure wouldn't want to cache the generated file - The expanded configuration (with all includes) isn't provided to the template script or even computed by LXC at that point - A bunch of Linux distributions (and Ubuntu is/was one of those) will freak out when the ip and routing table is pre-filled, causing a boot failure. - There is indeed no way to configure DNS, nor will there be one as it's not something that's tied to a network namespace in the kernel, but is a pure userspace thing which can differ based on distros and therefore is out of scope for LXC itself. The way we allow people to do such things with LXD is by feeding cloud-init with yaml network configuration which will then be applied to the distro's configuration on first boot. This could be made to work with the ubuntu-cloud template which supports passing cloud-init configuration already (but doesn't support network- config right now) but that wouldn't be tied to the lxc.network.* config, instead just passing static configuration to cloud-init and have it record it all in /etc/network/interfaces on first boot. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1661825 Title: interfaces always dhcp in ubuntu template Status in lxc package in Ubuntu: Won't Fix Bug description: The ubuntu template always set the containers interfaces to dhcp for eth0, even if you have lxc.network.ipv4 specified. It should be either set to static and the same settings, or more preferred manual. The missing bit is dns server for the guest. Not sure how we would like to get that set in the guest. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1661825/+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 1661825] Re: interfaces always dhcp in ubuntu template
** Changed in: lxc (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1661825 Title: interfaces always dhcp in ubuntu template Status in lxc package in Ubuntu: Won't Fix Bug description: The ubuntu template always set the containers interfaces to dhcp for eth0, even if you have lxc.network.ipv4 specified. It should be either set to static and the same settings, or more preferred manual. The missing bit is dns server for the guest. Not sure how we would like to get that set in the guest. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1661825/+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 1659316] Re: compiz
Thank you for reporting this bug to Ubuntu. Wily Werewolf or 15.10 reached EOL on July 28, 2016 and is therefore now unsupported. Please refer to https://wiki.ubuntu.com/Releases for the currently supported Ubuntu releases. Please update your system to a currently supported release and let us know if you are still seeing the same issue, thanks. ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- 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/1659316 Title: compiz Status in xorg package in Ubuntu: Incomplete Bug description: i want start compiz but i have vesa driver installed Gathering information about your system... Distribution: Ubuntu 15.10 Desktop environment: GNOME Graphics chip: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) Driver in use: vesa Rendering method: AIGLX Checking if it's possible to run Compiz on your system... [SKIP] At least one check had to be skipped: Error: vesa driver in use ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-42.49-generic 4.2.8-ckt12 Uname: Linux 4.2.0-42-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Wed Jan 25 15:49:04 2017 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.14, 4.2.0-42-generic, x86_64: installed GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:013c] Subsystem: Acer Incorporated [ALI] Device [1025:013c] MachineType: Acer TravelMate 5730 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-42-generic root=UUID=dbf84782-3125-4254-83ec-9f0a4e9f125b ro quiet splash vt.handoff=7 SourcePackage: xorg UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/05/2008 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: V1.19 dmi.board.name: Homa dmi.board.vendor: Acer dmi.board.version: Rev dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.19:bd08/05/2008:svnAcer:pnTravelMate5730:pvr0100:rvnAcer:rnHoma:rvrRev:cvnAcer:ct10:cvrN/A: dmi.product.name: TravelMate 5730 dmi.product.version: 0100 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Wed Jan 25 15:07:31 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 32884 vendor AUO xserver.version: 2:1.17.2-1ubuntu9.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1659316/+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 1661825] [NEW] interfaces always dhcp in ubuntu template
Public bug reported: The ubuntu template always set the containers interfaces to dhcp for eth0, even if you have lxc.network.ipv4 specified. It should be either set to static and the same settings, or more preferred manual. The missing bit is dns server for the guest. Not sure how we would like to get that set in the guest. ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1661825 Title: interfaces always dhcp in ubuntu template Status in lxc package in Ubuntu: New Bug description: The ubuntu template always set the containers interfaces to dhcp for eth0, even if you have lxc.network.ipv4 specified. It should be either set to static and the same settings, or more preferred manual. The missing bit is dns server for the guest. Not sure how we would like to get that set in the guest. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1661825/+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 1661675] Re: too hard to tell which window will be selected in alt-tab window switcher
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity8 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1661675 Title: too hard to tell which window will be selected in alt-tab window switcher Status in Ubuntu UX: New Status in unity8 package in Ubuntu: Confirmed Bug description: I find it really difficult to tell which window will be selected when alt-tabbing through my window list on Unity8. The highlighting of the selection is very subtle and there is not change to the window preview or the icon. I thought it would get easier after using unity8 a lot but it really hasn't. I think the following tweaks would make it much more clear which window is selected: 1) The app icon at the bottom should get bigger or some effect applied to it when the app window is selected. My eyes tend to look there as it's less cluttered than the window preview list 2) Make the border around the selected window preview thicker/darker to make it stand out more as currently the border highlighting is very subtle And/Or 3) Make the actual window preview larger (or some other effect to make it move forward) for the selected window so that it's super clear which window is selected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1661675/+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 1659532] Re: TextInputPopover is not launched from search bar on unity8-dash
** Tags added: unity8 -- 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/1659532 Title: TextInputPopover is not launched from search bar on unity8-dash Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: Using lp:ubuntu-ui-toolkit/staging with unity8 (8.15+16.04.20170124-0ubuntu1) when I right-click the search bar from unity8-dash no context menu is displayed. Checking unity8-dash logs there is this entry: [2017-01-25:20:38:22.862] file:///usr/lib/x86_64-linux- gnu/qt5/qml/Ubuntu/Components/Popups/1.3/popupUtils.js:75: TypeError: Cannot read property 'activeFocusItem' of null Code validates if typeof window is defined but does not check if window is null which seems to be the case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1659532/+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 1334916] Re: sshd-ConsoleKit integration patch causes abrupt termination of multichannel sessions
Is this bug fix ever going to be released for 14.04 LTS? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1334916 Title: sshd-ConsoleKit integration patch causes abrupt termination of multichannel sessions Status in openssh package in Ubuntu: Fix Released Bug description: Attached to this report is a small app the reproduces the issue by creating multiple channels within one sessions. (I fist hit this issue using JSCH library) Following information is printed to stdout if sshd is launched with -d flags (I've modified the sshd code to print PIDs next to debug level): debug3(7526): monitor_read: checking request 156 debug3(7526): mm_answer_consolekit_register entering debug1(7526): session_by_tty: session 0 tty /dev/pts/1 debug1(7573): server_input_channel_req: channel 2 request pty-req reply 1 debug1(7573): session_by_channel: session 2 channel 2 debug1(7573): session_input_channel_req: session 2 req pty-req debug1(7573): Allocating pty. debug3(7573): mm_request_send entering: type 28 debug3(7573): mm_pty_allocate: waiting for MONITOR_ANS_PTY debug3(7573): mm_request_receive_expect entering: type 29 debug3(7573): mm_request_receive entering debug1(7526): Unable to open session: The name org.freedesktop.ConsoleKit was not provided by any .service files debug3(7526): mm_request_send entering: type 157 debug3(7526): mm_request_receive entering debug3(7526): monitor_read: checking request 28 debug3(7526): mm_answer_pty entering debug2(7526): session_new: allocate (allocated 2 max 10) debug3(7526): session_unused: session id 2 unused debug1(7526): session_new: session 2 mm_request_receive_expect: read: rtype 157 != type 29 From the log, it looks as if two processes use the same set of pipes to communicate to the monitor, one of them is sending MONITOR_REQ_CONSOLEKIT_REGISTER, while another MONITOR_REQ_PTY, and because they use same set of pipes, and because both processes use same pipe FDs, monitor reply is sometimes delivered to the wrong process. I can reproduce the failure 90% of time using attached app, which expects first argument to be host name, second - login and the third - password, that are defaulted to ubuntu:ubuntu@localhost: $ ./ssh-multisession Connecting to localhost...Done! Authenticating as ubuntu...Done. Starting channel 0 Starting channel 1 ssh_channel_request_pty()=-1: Socket error: disconnected Starting channel 2 ssh_channel_open_session()=-1: Writing packet: error on socket (or connection closed): Operation now in progress Starting channel 3 The same script works fine if sshd is compiled without consolekit.patch: ./ssh-multisession debian-host debian debian Connecting to 172.17.162.237...Done! Authenticating as debian...Done. Starting channel 0 Starting channel 1 Starting channel 2 Starting channel 3 Starting channel 4 Starting channel 5 Starting channel 6 Starting channel 7 Starting channel 8 Starting channel 9 P.S. To compile a test app one needs to have libssh-dev package installed on your system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1334916/+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
