[Touch-packages] [Bug 1734423] [NEW] package libdb5.3:amd64 5.3.28-11ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting config
Public bug reported: just started my laptop and this notification popped up, not sure if anything is broken. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libdb5.3:amd64 5.3.28-11ubuntu0.1 ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-40-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 Date: Fri Nov 24 23:07:55 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu9 libgcc1 1:6.0.1-0ubuntu1 DpkgTerminalLog: dpkg: error processing package libdb5.3:amd64 (--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 2017-10-18 (38 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: db5.3 Title: package libdb5.3:amd64 5.3.28-11ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: db5.3 (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 db5.3 in Ubuntu. https://bugs.launchpad.net/bugs/1734423 Title: package libdb5.3:amd64 5.3.28-11ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in db5.3 package in Ubuntu: New Bug description: just started my laptop and this notification popped up, not sure if anything is broken. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libdb5.3:amd64 5.3.28-11ubuntu0.1 ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-40-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 Date: Fri Nov 24 23:07:55 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu9 libgcc1 1:6.0.1-0ubuntu1 DpkgTerminalLog: dpkg: error processing package libdb5.3:amd64 (--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 2017-10-18 (38 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: db5.3 Title: package libdb5.3:amd64 5.3.28-11ubuntu0.1 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/db5.3/+bug/1734423/+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 1535840] Re: systemd ignoring /etc/modules due to blacklist
** Changed in: systemd (Ubuntu) Status: Confirmed => Opinion -- 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/1535840 Title: systemd ignoring /etc/modules due to blacklist Status in systemd package in Ubuntu: Opinion Bug description: I tried the daily build of 16.04 32-bit to test out the watchdog daemon code. Usually (Ubuntu 10.04-14.04) I add the watchdog module in /etc/modules so it is loaded at boot-time, as watchdog timer modules are not normally auto-loaded due to the risk of an unexpected reboot. However I now find that systemd is choosing to ignore my command to load the module in /etc/modules since it appears in the watchdog blacklist. Typical syslog entries look like this: Jan 19 16:46:14 ubuntu systemd-modules-load[337]: Module 'softdog' is blacklisted Jan 19 17:53:23 ubuntu systemd-modules-load[342]: Module 'softdog' is blacklisted This is just dumb! I have explicitly told the system to load the module, an action that works perfectly well using modprobe or by adding it to the start script for the watchdog, and yet systemd chooses to override that because of the blacklist for auto-loaded modules (in this case in /etc/modprobe.d/blacklist-watchdog.conf). $ lsb_release -rd Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 $ apt-cache policy systemd systemd: Installed: 228-4ubuntu1 Candidate: 228-4ubuntu1 Version table: *** 228-4ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages 100 /var/lib/dpkg/status What I expect to happen is modules added to /etc/modules are loaded at boot time, and not subject to the blacklist for hardware detect / automatic loading. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1535840/+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 1512068] Re: Python ctypes.util , Shell Injection in find_library()
** Changed in: python2.7 (Ubuntu Xenial) Assignee: (unassigned) => Brian Morton (rokclimb15) ** Changed in: python2.7 (Ubuntu) Assignee: Brian Morton (rokclimb15) => (unassigned) -- 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/1512068 Title: Python ctypes.util , Shell Injection in find_library() Status in Python: Fix Released Status in python2.7 package in Ubuntu: Fix Released Status in python2.7 source package in Xenial: New Bug description: https://github.com/Legrandin/ctypes/issues/1 The find_library() function can execute code when special chars like ;|`<>$ are in the name. The "os.popen()" calls in the util.py script should be replaced with "subprocess.Popen()". Demo Exploits for Linux : >>> from ctypes.util import find_library >>> find_library(";xeyes")# runs xeyes >>> find_library("|xterm")# runs terminal >>> find_library("&gimp")# runs gimp >>> find_library("$(nautilus)") # runs filemanager >>> find_library(">test") # creates, and if exists, erases a file "test" Traceback >>> find_library("`xmessage hello`")# shows a message, press ctrl+c for Traceback ^CTraceback (most recent call last): File "", line 1, in File "/usr/lib/python3.4/ctypes/util.py", line 244, in find_library return _findSoname_ldconfig(name) or _get_soname(_findLib_gcc(name)) File "/usr/lib/python3.4/ctypes/util.py", line 99, in _findLib_gcc trace = f.read() KeyboardInterrupt ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: libpython2.7-stdlib 2.7.10-4ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Nov 1 10:34:38 2015 InstallationDate: Installed on 2015-10-09 (22 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151009) SourcePackage: python2.7 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/python/+bug/1512068/+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 1734410] [NEW] systemd: handle undelegated cgroup2 hierarchy
Public bug reported: Hey everyone, Current systemd versions all fail when the unified cgroup hierarchy is not-writable. This is especially problematic in containers where the systemd administrator might decide to not delegate the unified hierarchy or when running with a liblxc driver that doesn't yet know how to handle the unified cgroup hierarchy. I've pushed patches to systemd upstream that let systemd ingnore the non-delegated unified hierarchy. The relevant commits are: e07aefbd675b651f8d45b5fb458f2747b04d6e04 2d56b80a1855836abf1d7458394c345ad9d55382 1ff654e28b7b8e7d0a0be33522a84069ac6b07c0 These patches will be in 235 but should be backported from xenial upwards. Christian ** Affects: systemd (Ubuntu) Importance: Undecided Assignee: Dimitri John Ledkov (xnox) Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1734410 Title: systemd: handle undelegated cgroup2 hierarchy Status in systemd package in Ubuntu: New Bug description: Hey everyone, Current systemd versions all fail when the unified cgroup hierarchy is not-writable. This is especially problematic in containers where the systemd administrator might decide to not delegate the unified hierarchy or when running with a liblxc driver that doesn't yet know how to handle the unified cgroup hierarchy. I've pushed patches to systemd upstream that let systemd ingnore the non-delegated unified hierarchy. The relevant commits are: e07aefbd675b651f8d45b5fb458f2747b04d6e04 2d56b80a1855836abf1d7458394c345ad9d55382 1ff654e28b7b8e7d0a0be33522a84069ac6b07c0 These patches will be in 235 but should be backported from xenial upwards. Christian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1734410/+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 1734409] [NEW] systemd-sysctl: exit gracefully on EPERM/EACCESS
Public bug reported: Hi everyone, systemd-sysctl in systemd versions prior to 232 will exit with FAILED when not being able to apply kernel variables. In containers it should simply move on and exit with SUCCESS. Upstream systemd carries appropriate patches for this already. The relevant commits are: 411e869f497c7c7bd0688f1e3500f9043bc56e48 39540de8abe24886693ca29a9caeea85c88089aa these should be backported to xenial's systemd. Christian ** Affects: systemd (Ubuntu) Importance: Undecided Assignee: Dimitri John Ledkov (xnox) Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1734409 Title: systemd-sysctl: exit gracefully on EPERM/EACCESS Status in systemd package in Ubuntu: New Bug description: Hi everyone, systemd-sysctl in systemd versions prior to 232 will exit with FAILED when not being able to apply kernel variables. In containers it should simply move on and exit with SUCCESS. Upstream systemd carries appropriate patches for this already. The relevant commits are: 411e869f497c7c7bd0688f1e3500f9043bc56e48 39540de8abe24886693ca29a9caeea85c88089aa these should be backported to xenial's systemd. Christian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1734409/+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 1731796] Re: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [gdbus:2878]
Happened again. Auto-bug reporting didn't recognize this report as similar, so created bug 1734405 Note - compiz was in Z state (per top), consuming 100% of a cpu (per top) throughout the incident. I was able to login via ssh and look at things. I don't believe that a stuck compiz process could be caused by soft lockups. So the compiz process *may* be closer to the root cause? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1731796 Title: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [gdbus:2878] Status in glib2.0 package in Ubuntu: New Bug description: This is a bug report about errors during the upgrade process. I don't know whether or not my samba installation was working immediately before the upgrade; the windows box that was intended to be a client died and has not been replaced. Don't believe my answers to the forced questions. *** My ubuntu system locks up regularly. Bugs I've reported about this get closed for inattention, after being ignored, and queries about how to do basic debugging get the same treatment, so I just power cycle whenever it happens again. This time the lock up happened while the GUI upgrade-everything-to- latest tool was running. When I power cycled the box to recover, the system was unusable - flashing "system problem detected" popups, none staying stable long enough to respond. ssh + "sudo apt-get update" + "sudo apt-get upgrade" pointed me to "sudo dpkg --configure -a" That command reported numerous errors - I don't know which of them are "normal" for this system, but hidden by the GUI, and which are new. But it got the system semi-usable from the GUI, so now I'm clicking on "yes, report it" for the many pop-ups, of which this is one. FWIW, samba is one of the ones "dpkg --reconfigure -a" complained about. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: samba 2:4.3.11+dfsg-0ubuntu0.16.04.10 ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 Uname: Linux 4.4.0-93-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Sun Nov 12 11:07:42 2017 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2012-04-26 (2026 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) NmbdLog: OtherFailedConnect: Yes RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SambaServerRegression: Yes SmbConfIncluded: Yes SmbLog: SourcePackage: samba Title: package samba 2:4.3.11+dfsg-0ubuntu0.16.04.10 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2017-03-31 (226 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1731796/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1606078] Re: No sound with Ubuntu 16.04
No audio only if I use Kernel 3.2, audio works. Also re-login audio problem fixes. No audio in normal log-in just after reboot. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1606078 Title: No sound with Ubuntu 16.04 Status in alsa-driver package in Ubuntu: Expired Bug description: After a fresh install of Ubuntu 16.04.1 on an LG S1 Express Dual laptop there was no sound from the speakers unless external speakers where hooked to the headphones socket. This applies to the Ubuntu Mate, Xubuntu and Lubuntu variants. This laptop was working fine for all previous releases up to 14.04. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bashar 3263 F pulseaudio CurrentDesktop: Unity Date: Mon Jul 25 01:51:19 2016 InstallationDate: Installed on 2016-07-24 (0 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bashar 3263 F pulseaudio Symptom_Jack: Line Out, Internal Symptom_Type: No sound at all Title: [S1-M401E1, Realtek ALC880, Line Out, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/16/2006 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: RKYWSF0B dmi.board.name: ROCKY dmi.board.vendor: LG Electronics dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LG Electronics dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrRKYWSF0B:bd02/16/2006:svnLGElectronics:pnS1-M401E1:pvrNotApplicable:rvnLGElectronics:rnROCKY:rvrNotApplicable:cvnLGElectronics:ct10:cvrN/A: dmi.product.name: S1-M401E1 dmi.product.version: Not Applicable dmi.sys.vendor: LG Electronics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1606078/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1734395] [NEW] mkfs.ext4dev unrecognised file system
Public bug reported: This is probably a bit of a daft one, and it's not blocking me on anything, but I see this more as a UX bug. mkfs.ext4dev creates a file system that mount then can't mount, unless it is told explicitly that it is ext4. (on a side note, what is ext4dev? Can't seem to find a solid answer) $ sudo mkfs.ext4dev /dev/sdb mke2fs 1.42.13 (17-May-2015) /dev/sdb contains a ext4 file system last mounted on Fri Nov 24 22:40:41 2017 Proceed anyway? (y,n) y Creating filesystem with 268435456 4k blocks and 67108864 inodes Filesystem UUID: d5dcc961-f34e-4f59-b0f5-f58ea75dc817 Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000, 7962624, 11239424, 2048, 23887872, 71663616, 78675968, 10240, 214990848 Allocating group tables: done Writing inode tables: done Creating journal (32768 blocks): done Writing superblocks and filesystem accounting information: done $ sudo mount /dev/sdb mount mount: unknown filesystem type 'ext4dev' $ sudo mount -t ext4 mount $ /dev/sdb on /home/ubuntu/mount type ext4 (rw,relatime,data=ordered) doing a normal mkfs.ext4 works perfectly fine, as you'd expect. Version: Ubuntu 16.04 Package: e2fsprogs 1.42.13-1ubuntu1 ** Affects: e2fsprogs (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1734395 Title: mkfs.ext4dev unrecognised file system Status in e2fsprogs package in Ubuntu: New Bug description: This is probably a bit of a daft one, and it's not blocking me on anything, but I see this more as a UX bug. mkfs.ext4dev creates a file system that mount then can't mount, unless it is told explicitly that it is ext4. (on a side note, what is ext4dev? Can't seem to find a solid answer) $ sudo mkfs.ext4dev /dev/sdb mke2fs 1.42.13 (17-May-2015) /dev/sdb contains a ext4 file system last mounted on Fri Nov 24 22:40:41 2017 Proceed anyway? (y,n) y Creating filesystem with 268435456 4k blocks and 67108864 inodes Filesystem UUID: d5dcc961-f34e-4f59-b0f5-f58ea75dc817 Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000, 7962624, 11239424, 2048, 23887872, 71663616, 78675968, 10240, 214990848 Allocating group tables: done Writing inode tables: done Creating journal (32768 blocks): done Writing superblocks and filesystem accounting information: done $ sudo mount /dev/sdb mount mount: unknown filesystem type 'ext4dev' $ sudo mount -t ext4 mount $ /dev/sdb on /home/ubuntu/mount type ext4 (rw,relatime,data=ordered) doing a normal mkfs.ext4 works perfectly fine, as you'd expect. Version: Ubuntu 16.04 Package: e2fsprogs 1.42.13-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1734395/+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 1733683] Please test proposed package
Hello Michael, or anyone else affected, Accepted ust into artful-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ust/2.9.1-1ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-artful to verification-done-artful. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-artful. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ust in Ubuntu. https://bugs.launchpad.net/bugs/1733683 Title: python3-lttngust tries to load unversionned agent library Status in ust package in Ubuntu: New Status in ust source package in Xenial: Fix Committed Status in ust source package in Zesty: Fix Committed Status in ust source package in Artful: Fix Committed Bug description: The python3-lttngust package contains bindings that use ctypes to interact with a dedicated library provided by the liblttng-ust-python- agent0. The python code loads the library by name but it targets the un-versioned ".so" which is part of the dev package. This means that when installed without the dev package the bindings won't work. The fix is to load the library by name and use the SONAME version ".so.0". I'll provide a debdiff for the affected versions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ust/+bug/1733683/+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 1733683] Please test proposed package
Hello Michael, or anyone else affected, Accepted ust into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ust/2.9.0-1ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-zesty to verification-done-zesty. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-zesty. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: ust (Ubuntu Artful) Status: New => Fix Committed ** Tags added: verification-needed-artful -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ust in Ubuntu. https://bugs.launchpad.net/bugs/1733683 Title: python3-lttngust tries to load unversionned agent library Status in ust package in Ubuntu: New Status in ust source package in Xenial: Fix Committed Status in ust source package in Zesty: Fix Committed Status in ust source package in Artful: Fix Committed Bug description: The python3-lttngust package contains bindings that use ctypes to interact with a dedicated library provided by the liblttng-ust-python- agent0. The python code loads the library by name but it targets the un-versioned ".so" which is part of the dev package. This means that when installed without the dev package the bindings won't work. The fix is to load the library by name and use the SONAME version ".so.0". I'll provide a debdiff for the affected versions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ust/+bug/1733683/+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 1733683] Re: python3-lttngust tries to load unversionned agent library
Hello Michael, or anyone else affected, Accepted ust into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ust/2.7.1-1ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: ust (Ubuntu Xenial) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-xenial ** Changed in: ust (Ubuntu Zesty) Status: New => Fix Committed ** Tags added: verification-needed-zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ust in Ubuntu. https://bugs.launchpad.net/bugs/1733683 Title: python3-lttngust tries to load unversionned agent library Status in ust package in Ubuntu: New Status in ust source package in Xenial: Fix Committed Status in ust source package in Zesty: Fix Committed Status in ust source package in Artful: Fix Committed Bug description: The python3-lttngust package contains bindings that use ctypes to interact with a dedicated library provided by the liblttng-ust-python- agent0. The python code loads the library by name but it targets the un-versioned ".so" which is part of the dev package. This means that when installed without the dev package the bindings won't work. The fix is to load the library by name and use the SONAME version ".so.0". I'll provide a debdiff for the affected versions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ust/+bug/1733683/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1316873] Re: Left mouse button stops working
*** This bug is a duplicate of bug 402892 *** https://bugs.launchpad.net/bugs/402892 ** This bug has been marked a duplicate of bug 402892 Mouse cursor gets stuck in "drag and drop" mode -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1316873 Title: Left mouse button stops working Status in xorg package in Ubuntu: Confirmed Bug description: This problem has plagued me for a few years across different laptops and Ubuntu versions. Current I am experiencing this on a Dell Inspiron 15z running Ubuntu 14.04 LTS. It typically starts after I have used the chat or call feature in gmail, by clicking on the phone icon in the left chat margin. I am a Firefox user and have not tested this with chrome etc. It has not happened if i dont install google-talkplugin so it is quite possible that the plugin is to blame. Symptom === The left mouse button on all attached mice - USB , Trackpad and touch - will not do anything however the right mouse button continues to work. This happens to all applications and also to the desktop. The keyboard continues to function as normal. When this occurs , my solution is to Alt-F4 close all windows and log out of the X session. When I re-login the left mouse button works as normal. This is an irritant and work disruptor as I have to save all browser and desktop applications to safe state before I logout to reset the mouse. I will appreciate any soltion or workaround. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue May 6 21:41:29 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:058f] InstallationDate: Installed on 2014-04-17 (19 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Inspiron 5523 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=f5004b03-b37f-4733-88a8-51c6f3bd0a4d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0GKGJG dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA05:bd05/18/2013:svnDellInc.:pnInspiron5523:pvrNotSpecified:rvnDellInc.:rn0GKGJG:rvrA05:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 5523 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue May 6 21:20:40 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5558 vendor CMN xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1316873/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1734384] Re: no audio
** Changed in: pulseaudio (Ubuntu) Assignee: (unassigned) => Ubuntu Audio Team (ubuntu-audio) -- 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/1734384 Title: no audio Status in pulseaudio package in Ubuntu: New Bug description: my laptop volume is mute. and it didn't unmute whatever i do. in bug report it says- pulseaudio crashed. ubuntu 14.04 LTS ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11.1 ProcVersionSignature: Ubuntu 3.13.0-135.184-generic 3.13.11-ckt39 Uname: Linux 3.13.0-135-generic i686 ApportVersion: 2.14.1-0ubuntu3.27 Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Sat Nov 25 01:01:25 2017 InstallationDate: Installed on 2016-09-15 (435 days ago) InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release i386 (20140807.1) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to trusty on 2017-09-10 (74 days ago) dmi.bios.date: 09/05/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CPE Ver. F.21 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1950 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 91.0B dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CPEVer.F.21:bd09/05/2013:svnHewlett-Packard:pnHPProBook445G1:pvrA2018CD200:rvnHewlett-Packard:rn1950:rvrKBCVersion91.0B:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 445 G1 dmi.product.version: A2018CD200 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1734384/+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 1734385] [NEW] it-keytable mapping only every second button press
Public bug reported: When mapping Phillips (Zotac AD12 remote) RC-6 Remote, ir-keymaps only maps every second button press, although the scan codes are the same. More details posted here: https://ubuntuforums.org/showthread.php?t=2378535 Ubuntu 17.10 Kernel Mainline generic amd64 4.13.14 ** Affects: v4l-utils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to v4l-utils in Ubuntu. https://bugs.launchpad.net/bugs/1734385 Title: it-keytable mapping only every second button press Status in v4l-utils package in Ubuntu: New Bug description: When mapping Phillips (Zotac AD12 remote) RC-6 Remote, ir-keymaps only maps every second button press, although the scan codes are the same. More details posted here: https://ubuntuforums.org/showthread.php?t=2378535 Ubuntu 17.10 Kernel Mainline generic amd64 4.13.14 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/v4l-utils/+bug/1734385/+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 1734384] [NEW] no audio
Public bug reported: my laptop volume is mute. and it didn't unmute whatever i do. in bug report it says- pulseaudio crashed. ubuntu 14.04 LTS ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11.1 ProcVersionSignature: Ubuntu 3.13.0-135.184-generic 3.13.11-ckt39 Uname: Linux 3.13.0-135-generic i686 ApportVersion: 2.14.1-0ubuntu3.27 Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Sat Nov 25 01:01:25 2017 InstallationDate: Installed on 2016-09-15 (435 days ago) InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release i386 (20140807.1) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to trusty on 2017-09-10 (74 days ago) dmi.bios.date: 09/05/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CPE Ver. F.21 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1950 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 91.0B dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CPEVer.F.21:bd09/05/2013:svnHewlett-Packard:pnHPProBook445G1:pvrA2018CD200:rvnHewlett-Packard:rn1950:rvrKBCVersion91.0B:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 445 G1 dmi.product.version: A2018CD200 dmi.sys.vendor: Hewlett-Packard ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty -- 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/1734384 Title: no audio Status in pulseaudio package in Ubuntu: New Bug description: my laptop volume is mute. and it didn't unmute whatever i do. in bug report it says- pulseaudio crashed. ubuntu 14.04 LTS ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11.1 ProcVersionSignature: Ubuntu 3.13.0-135.184-generic 3.13.11-ckt39 Uname: Linux 3.13.0-135-generic i686 ApportVersion: 2.14.1-0ubuntu3.27 Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Sat Nov 25 01:01:25 2017 InstallationDate: Installed on 2016-09-15 (435 days ago) InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release i386 (20140807.1) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to trusty on 2017-09-10 (74 days ago) dmi.bios.date: 09/05/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CPE Ver. F.21 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1950 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 91.0B dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CPEVer.F.21:bd09/05/2013:svnHewlett-Packard:pnHPProBook445G1:pvrA2018CD200:rvnHewlett-Packard:rn1950:rvrKBCVersion91.0B:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 445 G1 dmi.product.version: A2018CD200 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1734384/+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 1734376] [NEW] package bsdutils 1:2.29-1ubuntu2.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Public bug reported: I couldn't install the lastest update ProblemType: Package DistroRelease: Ubuntu 17.04 Package: bsdutils 1:2.29-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 Date: Fri Nov 24 11:10:53 2017 DpkgTerminalLog: dpkg: error processing package bsdutils (--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 2015-06-08 (899 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: util-linux Title: package bsdutils 1:2.29-1ubuntu2.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to zesty on 2017-06-11 (166 days ago) ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1734376 Title: package bsdutils 1:2.29-1ubuntu2.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in util-linux package in Ubuntu: New Bug description: I couldn't install the lastest update ProblemType: Package DistroRelease: Ubuntu 17.04 Package: bsdutils 1:2.29-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 Date: Fri Nov 24 11:10:53 2017 DpkgTerminalLog: dpkg: error processing package bsdutils (--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 2015-06-08 (899 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: util-linux Title: package bsdutils 1:2.29-1ubuntu2.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to zesty on 2017-06-11 (166 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1734376/+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 1734038] Re: utils don't understand «include "/where/ever"» (was: Potential regression found with apparmor test on Xenial/Zesty)
Yes, the split parser has been a issue for a long time. There has been a plan to make the flex/yacc/C parser code available as a lib for the other tools but its one of those things that never gets resources allocated. The short term fix for this is probably a backport of a newer version of the python utils. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1734038 Title: utils don't understand «include "/where/ever"» (was: Potential regression found with apparmor test on Xenial/Zesty) Status in AppArmor: New Status in apparmor package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Invalid Bug description: Issue found with Xenial kernel 4.4.0-102 and Zesty kernel 4.10.0-41, across different architectures Multiple tests from ubuntu_qrt_apparmor test suite failed with the same error message: ERROR: Syntax Error: Unknown line found in file /etc/apparmor.d/usr.lib.snapd.snap-confine.real line 15: include "/var/lib/snapd/apparmor/snap-confine.d" /etc/ld.so.cache r, (BTW the include and this ld.so.cache are not in the same line, please refer to comment #3 for attachment) This issue will gone if you downgrade the snapd and ubuntu-core-launcher package: sudo apt-get install snapd=2.28.5 ubuntu-core-launcher=2.28.5 Debug information: ubuntu@kernel01:~$ snap version snap2.29.3 snapd 2.29.3 series 16 ubuntu 16.04 kernel 4.4.0-102-generic ubuntu@kernel01:~$ apt list snapd Listing... Done snapd/xenial-proposed,now 2.29.3 s390x [installed] N: There are 2 additional versions. Please use the '-a' switch to see them. ubuntu@kernel01:~$ apt list apparmor -a Listing... Done apparmor/xenial-updates,now 2.10.95-0ubuntu2.7 s390x [installed] apparmor/xenial-security 2.10.95-0ubuntu2.6 s390x apparmor/xenial 2.10.95-0ubuntu2 s390x Steps to run the Apparmor test from QA Regression testing suite: 1. git clone --depth 1 https://git.launchpad.net/qa-regression-testing 2. sudo ./qa-regression-testing/scripts/test-apparmor.py ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-102-generic 4.4.0-102.125 ProcVersionSignature: Ubuntu 4.4.0-102.125-generic 4.4.98 Uname: Linux 4.4.0-102-generic s390x NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.13 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: Date: Thu Nov 23 01:36:31 2017 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=44b0b919-a1a4-4849-9425-e71d4ac87d85 crashkernel=196M BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.4.0-102-generic N/A linux-backports-modules-4.4.0-102-generic N/A linux-firmware 1.157.13 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1734038/+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 1734038] Re: Potential regression found with apparmor test on Xenial/Zesty
> There is also a python parser (in aa.py) which only seems to understand the > 'include ' > syntax and it is this which throws errors when running the utility commands. Exactly, that's the cause of this bug. I'll change the title to make it obvious. Interestingly, it has been this way for years (I checked 2.9, but it probably also affects even older versions) without someone noticing it. Therefore this bug doesn't qualify as regression IMHO ;-) ** Summary changed: - Potential regression found with apparmor test on Xenial/Zesty + utils don't understand «include "/where/ever"» (was: Potential regression found with apparmor test on Xenial/Zesty) ** Also affects: apparmor Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1734038 Title: utils don't understand «include "/where/ever"» (was: Potential regression found with apparmor test on Xenial/Zesty) Status in AppArmor: New Status in apparmor package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Invalid Bug description: Issue found with Xenial kernel 4.4.0-102 and Zesty kernel 4.10.0-41, across different architectures Multiple tests from ubuntu_qrt_apparmor test suite failed with the same error message: ERROR: Syntax Error: Unknown line found in file /etc/apparmor.d/usr.lib.snapd.snap-confine.real line 15: include "/var/lib/snapd/apparmor/snap-confine.d" /etc/ld.so.cache r, (BTW the include and this ld.so.cache are not in the same line, please refer to comment #3 for attachment) This issue will gone if you downgrade the snapd and ubuntu-core-launcher package: sudo apt-get install snapd=2.28.5 ubuntu-core-launcher=2.28.5 Debug information: ubuntu@kernel01:~$ snap version snap2.29.3 snapd 2.29.3 series 16 ubuntu 16.04 kernel 4.4.0-102-generic ubuntu@kernel01:~$ apt list snapd Listing... Done snapd/xenial-proposed,now 2.29.3 s390x [installed] N: There are 2 additional versions. Please use the '-a' switch to see them. ubuntu@kernel01:~$ apt list apparmor -a Listing... Done apparmor/xenial-updates,now 2.10.95-0ubuntu2.7 s390x [installed] apparmor/xenial-security 2.10.95-0ubuntu2.6 s390x apparmor/xenial 2.10.95-0ubuntu2 s390x Steps to run the Apparmor test from QA Regression testing suite: 1. git clone --depth 1 https://git.launchpad.net/qa-regression-testing 2. sudo ./qa-regression-testing/scripts/test-apparmor.py ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-102-generic 4.4.0-102.125 ProcVersionSignature: Ubuntu 4.4.0-102.125-generic 4.4.98 Uname: Linux 4.4.0-102-generic s390x NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.13 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: Date: Thu Nov 23 01:36:31 2017 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=44b0b919-a1a4-4849-9425-e71d4ac87d85 crashkernel=196M BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.4.0-102-generic N/A linux-backports-modules-4.4.0-102-generic N/A linux-firmware 1.157.13 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1734038/+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 1734167] Re: DNS doesn't work in no-cloud as launched by ubuntu
zesty does not show this problem. neither does xenial. I reflected that in the status. ** Changed in: cloud-init (Ubuntu Artful) Status: New => Confirmed ** Changed in: cloud-init (Ubuntu Artful) Importance: Undecided => Medium ** Changed in: cloud-init (Ubuntu Artful) Importance: Medium => High ** Changed in: systemd (Ubuntu Artful) Status: New => Confirmed ** Changed in: systemd (Ubuntu Artful) Importance: Undecided => High ** Changed in: systemd (Ubuntu Zesty) Status: New => Confirmed ** Changed in: systemd (Ubuntu Zesty) Status: Confirmed => Fix Released ** Changed in: cloud-init (Ubuntu Zesty) Status: New => Fix Released -- 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/1734167 Title: DNS doesn't work in no-cloud as launched by ubuntu Status in cloud-init: Confirmed Status in cloud-init package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in cloud-init source package in Zesty: Fix Released Status in systemd source package in Zesty: Fix Released Status in cloud-init source package in Artful: Confirmed Status in systemd source package in Artful: Confirmed Status in cloud-init source package in Bionic: Confirmed Status in systemd source package in Bionic: Confirmed Bug description: I use no-cloud to test the kernel in CI (I am maintainer of the bcache subsystem), and have been running it successfully under 16.04 cloud images from qemu, using a qemu command that includes: -smbios "type=1,serial=ds=nocloud- net;s=https://raw.githubusercontent.com/mlyle/mlyle/master/cloud- metadata/linuxtst/" As documented here: http://cloudinit.readthedocs.io/en/latest/topics/datasources/nocloud.html Under the new 17.10 cloud images, this doesn't work: the network comes up, but name resolution doesn't work-- /etc/resolv.conf is a symlink to a nonexistent file at this point of the boot and systemd-resolved is not running. When I manually hack /etc/resolv.conf in the cloud image to point to 4.2.2.1 it works fine. I don't know if nameservice not working is by design, but it seems like it should work. The documentation states: "With ds=nocloud-net, the seedfrom value must start with http://, https:// or ftp://"; And https is not going to work for a raw IP address. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1734167/+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 1734167] Re: DNS doesn't work in no-cloud as launched by ubuntu
zesty does not show this problem. neither does xenial. I reflected that in the status. $ sudo journalctl -b -o short-monotonic | pastebinit http://paste.ubuntu.com/26035779/ $ sudo journalctl -o short-precise | pastebinit http://paste.ubuntu.com/26035774/ Nov 24 17:49:25.193028 ubuntu systemd[1]: systemd-resolved.service: Found orderingcycle on basic.target/start Nov 24 17:49:25.193038 ubuntu systemd[1]: systemd-resolved.service: Found dependencyon paths.target/start Nov 24 17:49:25.193050 ubuntu systemd[1]: systemd-resolved.service: Found dependencyon acpid.path/start Nov 24 17:49:25.193060 ubuntu systemd[1]: systemd-resolved.service: Found dependency on sysinit.target/start -- 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/1734167 Title: DNS doesn't work in no-cloud as launched by ubuntu Status in cloud-init: Confirmed Status in cloud-init package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in cloud-init source package in Zesty: Fix Released Status in systemd source package in Zesty: Fix Released Status in cloud-init source package in Artful: Confirmed Status in systemd source package in Artful: Confirmed Status in cloud-init source package in Bionic: Confirmed Status in systemd source package in Bionic: Confirmed Bug description: I use no-cloud to test the kernel in CI (I am maintainer of the bcache subsystem), and have been running it successfully under 16.04 cloud images from qemu, using a qemu command that includes: -smbios "type=1,serial=ds=nocloud- net;s=https://raw.githubusercontent.com/mlyle/mlyle/master/cloud- metadata/linuxtst/" As documented here: http://cloudinit.readthedocs.io/en/latest/topics/datasources/nocloud.html Under the new 17.10 cloud images, this doesn't work: the network comes up, but name resolution doesn't work-- /etc/resolv.conf is a symlink to a nonexistent file at this point of the boot and systemd-resolved is not running. When I manually hack /etc/resolv.conf in the cloud image to point to 4.2.2.1 it works fine. I don't know if nameservice not working is by design, but it seems like it should work. The documentation states: "With ds=nocloud-net, the seedfrom value must start with http://, https:// or ftp://"; And https is not going to work for a raw IP address. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1734167/+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 1734167] Re: DNS doesn't work in no-cloud as launched by ubuntu
that ordering cycle is if we add 'After=systemd-resolved.service' to cloud-init.service. -- 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/1734167 Title: DNS doesn't work in no-cloud as launched by ubuntu Status in cloud-init: Confirmed Status in cloud-init package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in cloud-init source package in Zesty: Fix Released Status in systemd source package in Zesty: Fix Released Status in cloud-init source package in Artful: Confirmed Status in systemd source package in Artful: Confirmed Status in cloud-init source package in Bionic: Confirmed Status in systemd source package in Bionic: Confirmed Bug description: I use no-cloud to test the kernel in CI (I am maintainer of the bcache subsystem), and have been running it successfully under 16.04 cloud images from qemu, using a qemu command that includes: -smbios "type=1,serial=ds=nocloud- net;s=https://raw.githubusercontent.com/mlyle/mlyle/master/cloud- metadata/linuxtst/" As documented here: http://cloudinit.readthedocs.io/en/latest/topics/datasources/nocloud.html Under the new 17.10 cloud images, this doesn't work: the network comes up, but name resolution doesn't work-- /etc/resolv.conf is a symlink to a nonexistent file at this point of the boot and systemd-resolved is not running. When I manually hack /etc/resolv.conf in the cloud image to point to 4.2.2.1 it works fine. I don't know if nameservice not working is by design, but it seems like it should work. The documentation states: "With ds=nocloud-net, the seedfrom value must start with http://, https:// or ftp://"; And https is not going to work for a raw IP address. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1734167/+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 1734167] Re: DNS doesn't work in no-cloud as launched by ubuntu
smoser, yeah, so like cloud-init.service should want/after systemd-resolved.service; or e.g. systemd-resolved.service should declare itself before cloud-init.service smoser, i think changing it in systemd unit might be better. ** Also affects: cloud-init (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu Bionic) Importance: High Status: Confirmed ** Also affects: systemd (Ubuntu Bionic) Importance: High Status: Confirmed ** Also affects: cloud-init (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Zesty) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1734167 Title: DNS doesn't work in no-cloud as launched by ubuntu Status in cloud-init: Confirmed Status in cloud-init package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in cloud-init source package in Zesty: New Status in systemd source package in Zesty: New Status in cloud-init source package in Artful: New Status in systemd source package in Artful: New Status in cloud-init source package in Bionic: Confirmed Status in systemd source package in Bionic: Confirmed Bug description: I use no-cloud to test the kernel in CI (I am maintainer of the bcache subsystem), and have been running it successfully under 16.04 cloud images from qemu, using a qemu command that includes: -smbios "type=1,serial=ds=nocloud- net;s=https://raw.githubusercontent.com/mlyle/mlyle/master/cloud- metadata/linuxtst/" As documented here: http://cloudinit.readthedocs.io/en/latest/topics/datasources/nocloud.html Under the new 17.10 cloud images, this doesn't work: the network comes up, but name resolution doesn't work-- /etc/resolv.conf is a symlink to a nonexistent file at this point of the boot and systemd-resolved is not running. When I manually hack /etc/resolv.conf in the cloud image to point to 4.2.2.1 it works fine. I don't know if nameservice not working is by design, but it seems like it should work. The documentation states: "With ds=nocloud-net, the seedfrom value must start with http://, https:// or ftp://"; And https is not going to work for a raw IP address. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1734167/+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 1734167] Re: DNS doesn't work in no-cloud as launched by ubuntu
I think the primary issue is that cloud-init.service is depending on using the network fully. cloud-init.service runs: After=networking.service After=systemd-networkd-wait-online.service Before=network-online.target But systemd-resolved.service runs After=systemd-networkd.service network.target Before=network-online.target nss-lookup.target I tried adding to cloud-init.service. After=systemd-resolved.service but that did not help things. -- 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/1734167 Title: DNS doesn't work in no-cloud as launched by ubuntu Status in cloud-init: Confirmed Status in cloud-init package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in cloud-init source package in Zesty: New Status in systemd source package in Zesty: New Status in cloud-init source package in Artful: New Status in systemd source package in Artful: New Status in cloud-init source package in Bionic: Confirmed Status in systemd source package in Bionic: Confirmed Bug description: I use no-cloud to test the kernel in CI (I am maintainer of the bcache subsystem), and have been running it successfully under 16.04 cloud images from qemu, using a qemu command that includes: -smbios "type=1,serial=ds=nocloud- net;s=https://raw.githubusercontent.com/mlyle/mlyle/master/cloud- metadata/linuxtst/" As documented here: http://cloudinit.readthedocs.io/en/latest/topics/datasources/nocloud.html Under the new 17.10 cloud images, this doesn't work: the network comes up, but name resolution doesn't work-- /etc/resolv.conf is a symlink to a nonexistent file at this point of the boot and systemd-resolved is not running. When I manually hack /etc/resolv.conf in the cloud image to point to 4.2.2.1 it works fine. I don't know if nameservice not working is by design, but it seems like it should work. The documentation states: "With ds=nocloud-net, the seedfrom value must start with http://, https:// or ftp://"; And https is not going to work for a raw IP address. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1734167/+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 1734167] Re: DNS doesn't work in no-cloud as launched by ubuntu
Heres some more info that is from failed system using bionic. $ sudo journalctl -o short-monotonic --no-pager | pastebinit http://paste.ubuntu.com/26035621/ $ sudo base64 /run/log/journal/7ba07d79c32c4103aefee168e433d847/system@e9ae467d022046f0a034147c78254ae9-0001-00055ebdb4f0260b.journal | pastebinit http://paste.ubuntu.com/26035632/ ** Changed in: cloud-init Status: New => Confirmed ** Changed in: cloud-init Importance: Undecided => High ** Changed in: cloud-init (Ubuntu) Status: New => Confirmed ** Changed in: cloud-init (Ubuntu) Importance: Undecided => High ** Changed in: systemd (Ubuntu) Status: New => Confirmed ** 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/1734167 Title: DNS doesn't work in no-cloud as launched by ubuntu Status in cloud-init: Confirmed Status in cloud-init package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: I use no-cloud to test the kernel in CI (I am maintainer of the bcache subsystem), and have been running it successfully under 16.04 cloud images from qemu, using a qemu command that includes: -smbios "type=1,serial=ds=nocloud- net;s=https://raw.githubusercontent.com/mlyle/mlyle/master/cloud- metadata/linuxtst/" As documented here: http://cloudinit.readthedocs.io/en/latest/topics/datasources/nocloud.html Under the new 17.10 cloud images, this doesn't work: the network comes up, but name resolution doesn't work-- /etc/resolv.conf is a symlink to a nonexistent file at this point of the boot and systemd-resolved is not running. When I manually hack /etc/resolv.conf in the cloud image to point to 4.2.2.1 it works fine. I don't know if nameservice not working is by design, but it seems like it should work. The documentation states: "With ds=nocloud-net, the seedfrom value must start with http://, https:// or ftp://"; And https is not going to work for a raw IP address. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1734167/+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 1734167] Re: DNS doesn't work in no-cloud as launched by ubuntu
$ wget http://cloud-images.ubuntu.com/artful/20171122/artful-server- cloudimg-amd64.img ## set up dns locally for 'qemu-host' to the default ip for user networking. $ grep qemu-host /etc/hosts 10.0.2.2 qemu-host $ cat data/user-data #cloud-config password: passw0rd chpasswd: { expire: False } ssh_pwauth: True $ cat data/meta-data instance-id: i-test ## webserv is http://bazaar.launchpad.net/~curtin-dev/curtin/trunk/view/head:/tools/webserv $ webserve 44225 data :: 44225 ## backdoor the image so you can login with 'backdoor:passw0rd' # backdoor-image is http://bazaar.launchpad.net/~smoser/+junk/backdoor-image/view/head:/backdoor-image $ sudo backdoor-image -v --password=passw0rd $ url="http://qemu-host:44225/"; $ qemu-system-x86_64 -enable-kvm \ -device virtio-net-pci,netdev=net00 \ -netdev type=user,id=net00 \ -drive file=artful-server-cloudimg-amd64.img,id=disk00,if=none,format=qcow2,index=0 \ -device virtio-blk,drive=disk00,serial=artful-server-cloudimg-amd64.img \ -vga none -nographic -snapshot -echr 0x5 \ -smbios type=1,serial=ds=nocloud-net;s=$url" -m 768 ## console does show ## [ 20.388179] cloud-init[606]: 2017-11-24 17:03:13,786 - util.py[WARNING]: Gett ## ing data from failed ## login $ pastebinit /var/log/cloud-init.log http://paste.ubuntu.com/26035544/ ## interesting part of that is 2017-11-24 17:03:12,779 - url_helper.py[DEBUG]: [9/11] open 'http://qemu-host:44667/meta-data' with {'url': 'http://qemu-host:44667/meta-data', 'allow_redirects': True, 'method': 'GET', 'headers': {'User-Agent': 'Cloud-Init/17.1'}} configuration 2017-11-24 17:03:12,782 - url_helper.py[DEBUG]: Please wait 1 seconds while we wait to try again 2017-11-24 17:03:13,783 - url_helper.py[DEBUG]: [10/11] open 'http://qemu-host:44667/meta-data' with {'url': 'http://qemu-host:44667/meta-data', 'allow_redirects': True, 'method': 'GET', 'headers': {'User-Agent': 'Cloud-Init/17.1'}} configuration 2017-11-24 17:03:13,786 - handlers.py[DEBUG]: finish: init-network/search-NoCloudNet: FAIL: no network data found from DataSourceNoCloudNet 2017-11-24 17:03:13,786 - util.py[WARNING]: Getting data from failed 2017-11-24 17:03:13,794 - util.py[DEBUG]: Getting data from failed Traceback (most recent call last): File "/usr/lib/python3/dist-packages/cloudinit/sources/__init__.py", line 332, in find_source if s.get_data(): File "/usr/lib/python3/dist-packages/cloudinit/sources/DataSourceNoCloud.py", line 157, in get_data (md_seed, ud) = util.read_seeded(seedfrom, timeout=None) File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 932, in read_seeded md_resp = read_file_or_url(md_url, timeout, retries, file_retries) File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 892, in read_file_or_url exception_cb=exception_cb) File "/usr/lib/python3/dist-packages/cloudinit/url_helper.py", line 270, in readurl raise excps[-1] cloudinit.url_helper.UrlError: HTTPConnectionPool(host='qemu-host', port=44667): Max retries exceeded with url: /meta-data (Caused by NewConnectionError(': Failed to establish a new connection: [Errno -3] Temporary failure in name resolution',)) 2017-11-24 17:03:13,802 - handlers.py[DEBUG]: start: init-network/search-None: searching for network data from DataSourceNone ** Also affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1734167 Title: DNS doesn't work in no-cloud as launched by ubuntu Status in cloud-init: New Status in cloud-init package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: I use no-cloud to test the kernel in CI (I am maintainer of the bcache subsystem), and have been running it successfully under 16.04 cloud images from qemu, using a qemu command that includes: -smbios "type=1,serial=ds=nocloud- net;s=https://raw.githubusercontent.com/mlyle/mlyle/master/cloud- metadata/linuxtst/" As documented here: http://cloudinit.readthedocs.io/en/latest/topics/datasources/nocloud.html Under the new 17.10 cloud images, this doesn't work: the network comes up, but name resolution doesn't work-- /etc/resolv.conf is a symlink to a nonexistent file at this point of the boot and systemd-resolved is not running. When I manually hack /etc/resolv.conf in the cloud image to point to 4.2.2.1 it works fine. I don't know if nameservice not working is by design, but it seems like it should work. The documentation states: "With ds=nocloud-net, the seedfrom value must start with http://, https:// or ftp://"; And https is not going to work for a raw IP address. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1734167/+subscriptions -- Mailing list
[Touch-packages] [Bug 1730399] Re: Add krackattacks mitigation
** Changed in: wpa (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1730399 Title: Add krackattacks mitigation Status in wpa package in Ubuntu: Confirmed Bug description: See for reference: https://www.krackattacks.com/#ap-mitigations Yes this is not a bug. However, it has been noted on ubuntu-devel that adding some features even to stable releases could be justified in *some* cases. First of paramount importance is that the fix introduces no regression. In this case this code is *only* used if a new parameter is set: wpa_disable_eapol_key_retries=1 if this parameter is missing, behaviour will not change. So any regression introduced will be caused by a deliberate admin decision, from where all responsability could be denied (use at your own risk, yadda, yadda...) Then is this parameter useful: it could be for the hundred of millions of Android Phone that are not yet patched (6.0 et upper) and will never be patched (about 50% of existing Android Phones). Please note that at least one wifi provider has already decided to provide this feature to help its users: https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory /cisco-sa-20171016-wpa so this is something that leaders do :-) I have already patched my AP that runs Ubuntu 16 LTS (see attached patch against 2.4-0ubuntu6.2, I have used my AP for 3 days now with a Ubuntu and an Android client without problem) and I could try to provide a patch for Ubuntu 17. This kind of patch is really trivial anyway, since it's just a port of the upstream patch in hostapd: https://w1.fi/cgit/hostap/commit/?id=6f234c1e2ee1ede29f2412b7012b3345ed8e52d3 However I have a big problem. Any security patch (and this is a security enhancing patch at least) is only worth as much as it is *tested*. And I don't have the means to verify that mitigation is effective, as the vulnerability discoverer has not provided (for obvious reasons) public testing code for clients. I think that Ubuntu should have this code (or did you just distribute security patches without testing that they are effective ? that would not be very serious IMO). There is no chance that M. Vanhoef sends his code to any old dog on the internet, so Canonical is my only chance for a real test of this feature on an Ubuntu AP (short of rewriting the attack code myself, not an attractive proposition). If in fact you don't have the testing (well, attack) code feel free to dismiss my bug report as irrelevant. But if you have please consider the opportunity to add some goodwill to Ubuntu. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1730399/+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 1694916] Re: package apport 2.20.4-0ubuntu4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
affected by this too -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1694916 Title: package apport 2.20.4-0ubuntu4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in apport package in Ubuntu: Confirmed Bug description: Issues updating apport: sudo dpkg --configure -a dpkg: error processing package apport (--configure): package is in a very bad inconsistent state; you should reinstall it before attempting configuration Errors were encountered while processing: apport ssr@PC3248 ~/gdrive-local/mgmt/admin/info $ sudo apt-get install apport Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be upgraded: apport 1 upgraded, 0 newly installed, 0 to remove and 23 not upgraded. 1 not fully installed or removed. Need to get 0 B/121 kB of archives. After this operation, 0 B of additional disk space will be used. (Reading database ... 430429 files and directories currently installed.) Preparing to unpack .../apport_2.20.4-0ubuntu4.1_all.deb ... File "/usr/bin/pyclean", line 63 except (IOError, OSError), e: ^ SyntaxError: invalid syntax dpkg: warning: subprocess old pre-removal script returned error exit status 1 dpkg: trying script from the new package instead ... File "/usr/bin/pyclean", line 63 except (IOError, OSError), e: ^ SyntaxError: invalid syntax dpkg: error processing archive /var/cache/apt/archives/apport_2.20.4-0ubuntu4.1_all.deb (--unpack): subprocess new pre-removal script returned error exit status 1 Traceback (most recent call last): File "/usr/bin/pycompile", line 35, in from debpython.version import SUPPORTED, debsorted, vrepr, \ File "/usr/share/python/debpython/version.py", line 24, in from ConfigParser import SafeConfigParser ImportError: No module named 'ConfigParser' *** Error in `/usr/bin/dpkg': munmap_chunk(): invalid pointer: 0x56449feb52e8 *** === Backtrace: = /lib/x86_64-linux-gnu/libc.so.6(+0x7908b)[0x7ff8ca09608b] /lib/x86_64-linux-gnu/libc.so.6(cfree+0x1f8)[0x7ff8ca0a32d8] /usr/bin/dpkg(+0x20cd0)[0x56449dd54cd0] /usr/bin/dpkg(+0x21119)[0x56449dd55119] /usr/bin/dpkg(+0x283cd)[0x56449dd5c3cd] /usr/bin/dpkg(+0x17737)[0x56449dd4b737] /usr/bin/dpkg(+0x17915)[0x56449dd4b915] /usr/bin/dpkg(+0x17b5d)[0x56449dd4bb5d] /usr/bin/dpkg(+0xaed7)[0x56449dd3eed7] /usr/bin/dpkg(+0x20c0b)[0x56449dd54c0b] /usr/bin/dpkg(+0x20e01)[0x56449dd54e01] /usr/bin/dpkg(+0xa962)[0x56449dd3e962] /usr/bin/dpkg(+0x72fd)[0x56449dd3b2fd] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7ff8ca03d3f1] /usr/bin/dpkg(+0x743a)[0x56449dd3b43a] === Memory map: 56449dd34000-56449dd79000 r-xp fd:00 4718628 /usr/bin/dpkg 56449df79000-56449df7c000 r--p 00045000 fd:00 4718628 /usr/bin/dpkg 56449df7c000-56449df7d000 rw-p 00048000 fd:00 4718628 /usr/bin/dpkg 56449df7d000-56449e191000 rw-p 00:00 0 56449f79-5644a454c000 rw-p 00:00 0 [heap] 7ff8c8879000-7ff8c888f000 r-xp fd:00 6816526 /lib/x86_64-linux-gnu/libgcc_s.so.1 7ff8c888f000-7ff8c8a8e000 ---p 00016000 fd:00 6816526 /lib/x86_64-linux-gnu/libgcc_s.so.1 7ff8c8a8e000-7ff8c8a8f000 r--p 00015000 fd:00 6816526 /lib/x86_64-linux-gnu/libgcc_s.so.1 7ff8c8a8f000-7ff8c8a9 rw-p 00016000 fd:00 6816526 /lib/x86_64-linux-gnu/libgcc_s.so.1 7ff8c8a9-7ff8c8e1c000 rw-p 00:00 0 7ff8c8e1c000-7ff8c8e27000 r-xp fd:00 6817463 /lib/x86_64-linux-gnu/libnss_files-2.24.so 7ff8c8e27000-7ff8c9026000 ---p b000 fd:00 6817463 /lib/x86_64-linux-gnu/libnss_files-2.24.so 7ff8c9026000-7ff8c9027000 r--p a000 fd:00 6817463 /lib/x86_64-linux-gnu/libnss_files-2.24.so 7ff8c9027000-7ff8c9028000 rw-p b000 fd:00 6817463 /lib/x86_64-linux-gnu/libnss_files-2.24.so 7ff8c9028000-7ff8c902e000 rw-p 00:00 0 7ff8c902e000-7ff8c9039000 r-xp fd:00 6817465 /lib/x86_64-linux-gnu/libnss_nis-2.24.so 7ff8c9039000-7ff8c9238000 ---p b000 fd:00 6817465 /lib/x86_64-linux-gnu/libnss_nis-2.24.so 7ff8c9238000-7ff8c9239000 r--p a000 fd:00 6817465 /lib/x86_64-linux-gnu/libnss_nis-2.24.so 7ff8c9239000-7ff8c923a000 rw-p b000 fd:00 6817465 /lib/x86_64-linux-gnu/libnss_nis-2.24.so 7ff8c923a000-7ff8c925 r-xp fd:00 6817460 /lib/x86_64-linux-gnu/libnsl-2.24.so 7ff8c925000
[Touch-packages] [Bug 1720519] Re: KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once at most. Refusing to load.
I have this bug now too, seems to happen every time I restart. Everything was fine until upgrading to 17.10, which caused this and several other unrelated bugs. This kind of stuff makes me very wary to doing release upgrades anymore. E: [pulseaudio] module.c: Module "module-switch-on-connect" should be loaded once at most. Refusing to load. E: [pulseaudio] main.c: Module load failed. E: [pulseaudio] main.c: Failed to initialize daemon. -- 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/1720519 Title: KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once at most. Refusing to load. Status in PulseAudio: Confirmed Status in pulseaudio package in Ubuntu: Triaged Bug description: Pulseaudio daemon does not start after the update to Kubuntu 17.10 beta2, because the module fails to load although it is there. From 'pulseaudio -vv' E: [pulseaudio] module.c: Module "module-switch-on-connect" should be loaded once at most. Refusing to load. E: [pulseaudio] main.c: Module load failed. E: [pulseaudio] main.c: Failed to initialize daemon. PS sorry I am not a seasoned bug reporter. Let me know if I can provide more info. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: ben2809 F...m chrome /dev/snd/controlC0: ben2809 F chrome /dev/snd/timer: ben2809 f chrome CurrentDesktop: KDE Date: Sat Sep 30 11:20:55 2017 InstallationDate: Installed on 2017-04-07 (175 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to artful on 2017-09-30 (0 days ago) dmi.bios.date: 10/29/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: B150M-ITX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd10/29/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1720519/+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 1734038] Re: Potential regression found with apparmor test on Xenial/Zesty
This appears to be being triggered because there are actually two independent profile parsers in apparmor. There is a C version used by the apparmor_parse which correctly interprets the 'include "xxx"' syntax and then loads the profile. There is also a python parser (in aa.py) which only seems to understand the 'include ' syntax and it is this which throws errors when running the utility commands. ** Also affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Changed in: snapd (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1734038 Title: Potential regression found with apparmor test on Xenial/Zesty Status in apparmor package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Invalid Bug description: Issue found with Xenial kernel 4.4.0-102 and Zesty kernel 4.10.0-41, across different architectures Multiple tests from ubuntu_qrt_apparmor test suite failed with the same error message: ERROR: Syntax Error: Unknown line found in file /etc/apparmor.d/usr.lib.snapd.snap-confine.real line 15: include "/var/lib/snapd/apparmor/snap-confine.d" /etc/ld.so.cache r, (BTW the include and this ld.so.cache are not in the same line, please refer to comment #3 for attachment) This issue will gone if you downgrade the snapd and ubuntu-core-launcher package: sudo apt-get install snapd=2.28.5 ubuntu-core-launcher=2.28.5 Debug information: ubuntu@kernel01:~$ snap version snap2.29.3 snapd 2.29.3 series 16 ubuntu 16.04 kernel 4.4.0-102-generic ubuntu@kernel01:~$ apt list snapd Listing... Done snapd/xenial-proposed,now 2.29.3 s390x [installed] N: There are 2 additional versions. Please use the '-a' switch to see them. ubuntu@kernel01:~$ apt list apparmor -a Listing... Done apparmor/xenial-updates,now 2.10.95-0ubuntu2.7 s390x [installed] apparmor/xenial-security 2.10.95-0ubuntu2.6 s390x apparmor/xenial 2.10.95-0ubuntu2 s390x Steps to run the Apparmor test from QA Regression testing suite: 1. git clone --depth 1 https://git.launchpad.net/qa-regression-testing 2. sudo ./qa-regression-testing/scripts/test-apparmor.py ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-102-generic 4.4.0-102.125 ProcVersionSignature: Ubuntu 4.4.0-102.125-generic 4.4.98 Uname: Linux 4.4.0-102-generic s390x NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.13 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: Date: Thu Nov 23 01:36:31 2017 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=44b0b919-a1a4-4849-9425-e71d4ac87d85 crashkernel=196M BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.4.0-102-generic N/A linux-backports-modules-4.4.0-102-generic N/A linux-firmware 1.157.13 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1734038/+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 1734344] Re: systemd 234-2ubuntu12.1 ADT test failure with linux 4.13.0-18.21
The s390x failure is because tests now run in a VM and on s390x there is no grub (zipl is used as the boot loader). -- 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/1734344 Title: systemd 234-2ubuntu12.1 ADT test failure with linux 4.13.0-18.21 Status in systemd package in Ubuntu: New Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/amd64/s/systemd/20171123_190248_4f60f@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/s390x/s/systemd/20171123_123920_4f60f@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1734344/+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 1734344] [NEW] systemd 234-2ubuntu12.1 ADT test failure with linux 4.13.0-18.21
Public bug reported: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/amd64/s/systemd/20171123_190248_4f60f@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/s390x/s/systemd/20171123_123920_4f60f@/log.gz ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure -- 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/1734344 Title: systemd 234-2ubuntu12.1 ADT test failure with linux 4.13.0-18.21 Status in systemd package in Ubuntu: New Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/amd64/s/systemd/20171123_190248_4f60f@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/s390x/s/systemd/20171123_123920_4f60f@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1734344/+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 1523621] Re: [ FAILED ] NestedServer.*_cursor_* (usually NestedServer.named_cursor_image_changes_are_forwarded_to_host)
Logged upstream: https://github.com/MirServer/mir/issues/53 ** Bug watch added: Mir bugs on GitHub #53 https://github.com/MirServer/mir/issues/53 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1523621 Title: [ FAILED ] NestedServer.*_cursor_* (usually NestedServer.named_cursor_image_changes_are_forwarded_to_host) Status in Mir: Triaged Status in mir package in Ubuntu: Triaged Bug description: while bin/mir_acceptance_tests --gtest_filter=NestedServer.named_cursor_image_changes_are_forwarded_to_host; do :; done fails after a few hundred iterations. NB There two are other tests that are probably manifesting the same underlying issue: NestedServer.can_hide_the_host_cursor NestedServer.animated_cursor_image_changes_are_forwarded_to_host To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1523621/+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 1719720] Comment bridged from LTC Bugzilla
--- Comment From bssrika...@in.ibm.com 2017-11-24 07:23 EDT--- I tested again on 17.10 .. but this time I am not seeing mentioned errors in syslog.. uname -a Linux lep8b 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:03:08 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1719720 Title: [LTCTest][libvpd] Process '/bin/touch /run/run.vpdupdate' failed with exit code 127 Status in The Ubuntu-power-systems project: Incomplete Status in coreutils package in Ubuntu: Incomplete Bug description: ---Problem Description--- Currently syslog is getting flooded with below log messages .. Sep 25 03:16:41 ubuntu1710 systemd-udevd[2654]: Process '/bin/touch /run/run.vpdd update' failed with exit code 127. This is on UBuntu 17.10 latest build.. ---uname output--- Linux ubuntu1710 4.12.0-11-generic #12-Ubuntu SMP Fri Aug 11 12:23:06 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Machine Type = ZZ-L ---Steps to Reproduce--- I have seen these messages logged more often when we do any hotplug operations.. ex. cpu hotplug.. Ok. .this is the continuation of LTC #144627 / Launchpad #1682774. As suggested in that bug, we did change udev script to create temporary file under /run and that patch is available in ubuntu 17.10. Looks like this is udev script issue. If I modify systemd-udevd like below it works fine. I've limited udev knowledge. I don't know if you have any other better solution to this issue. root@ltc-boston123:/lib/systemd/system# diff -Naurp systemd-udevd.service.org systemd-udevd.service --- systemd-udevd.service.org 2017-09-26 04:37:47.090057318 -0500 +++ systemd-udevd.service 2017-09-26 04:37:55.381739372 -0500 @@ -25,7 +25,7 @@ KillMode=mixed WatchdogSec=3min TasksMax=infinity MountFlags=slave -MemoryDenyWriteExecute=yes +#MemoryDenyWriteExecute=yes RestrictRealtime=yes RestrictAddressFamilies=AF_UNIX AF_NETLINK AF_INET AF_INET6 SystemCallArchitectures=native -Vasant To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1719720/+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 1724233] Re: python2.7 crashed with SIGSEGV in ffi_closure_unix64_inner()
it possible that this happened after installing the Sensors extension in Gnome, the extension does not work. -- 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/1724233 Title: python2.7 crashed with SIGSEGV in ffi_closure_unix64_inner() Status in python2.7 package in Ubuntu: Incomplete Bug description: Booted into stock Ubuntu 17.10 release candidate from October 15, 2017 and this error message simply came up. apt-cache policy python python: Installed: 2.7.14-2ubuntu1 Candidate: 2.7.14-2ubuntu1 Version table: *** 2.7.14-2ubuntu1 500 500 http://ca.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: python2.7-minimal 2.7.14-2ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 17 06:15:41 2017 ExecutablePath: /usr/bin/python2.7 InstallationDate: Installed on 2017-10-17 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171015) ProcCmdline: python accountable2you.pyc --username ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 SegvAnalysis: Segfault happened at: 0x7f84d920daa9 : movzwl 0xa(%rdi),%r15d PC (0x7f84d920daa9) ok source "0xa(%rdi)" (0x64007d) not located in a known VMA region (needed readable region)! destination "%r15d" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: python2.7 StacktraceTop: ffi_closure_unix64_inner () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_closure_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 IceFlush () from /usr/lib/x86_64-linux-gnu/libICE.so.6 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 Title: python2.7 crashed with SIGSEGV in ffi_closure_unix64_inner() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1724233/+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 1711832] Re: package linux-firmware 1.164.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed -- 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/1711832 Title: package linux-firmware 1.164.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: I dont know ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-firmware 1.164.1 ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 Date: Fri Aug 18 20:00:53 2017 Dependencies: Df: ErrorMessage: subprocess installed post-installation script returned error exit status 139 InstallationDate: Installed on 2017-08-10 (9 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: initramfs-tools Title: package linux-firmware 1.164.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139 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/1711832/+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 1719579] Comment bridged from LTC Bugzilla
--- Comment From balamuruh...@in.ibm.com 2017-11-24 06:23 EDT--- (In reply to comment #43) > Please restest with 16.04.3 and also consider the setup proposed in the > comment #7 Tried giving permission to /etc/gss/mech.d and still issue got observed, # ls -l /etc/gss/ total 4 drwxrwxrwx 2 root root 4096 Jul 19 17:07 mech.d Tried giving permission to the save.file in /var/tmp/save.file and issue is observed # ls -l /var/tmp/save.file -rwxrwxrwx 1 root root 1595918108 Nov 23 10:46 /var/tmp/save.file Tried disabling apparmor and could see the issue, # service apparmor stop # service apparmor status ? apparmor.service - LSB: AppArmor initialization Loaded: loaded (/etc/init.d/apparmor; bad; vendor preset: enabled) Active: inactive (dead) since Fri 2017-11-24 16:50:14 IST; 4s ago Docs: man:systemd-sysv-generator(8) Process: 13213 ExecStop=/etc/init.d/apparmor stop (code=exited, status=0/SUCCESS) Process: 12081 ExecStart=/etc/init.d/apparmor start (code=exited, status=0/SUCCESS) Nov 24 16:50:14 pkvmhab006 systemd[1]: Stopping LSB: AppArmor initialization... Nov 24 16:50:14 pkvmhab006 apparmor[13213]: * Clearing AppArmor profiles cache Nov 24 16:50:14 pkvmhab006 apparmor[13213]:...done. Nov 24 16:50:14 pkvmhab006 apparmor[13213]: All profile caches have been cleared, but no profiles have been unloaded. Nov 24 16:50:14 pkvmhab006 apparmor[13213]: Unloading profiles will leave already running processes permanently Nov 24 16:50:14 pkvmhab006 apparmor[13213]: unconfined, which can lead to unexpected situations. Nov 24 16:50:14 pkvmhab006 apparmor[13213]: To set a process to complain mode, use the command line tool Nov 24 16:50:14 pkvmhab006 apparmor[13213]: 'aa-complain'. To really tear down all profiles, run the init script Nov 24 16:50:14 pkvmhab006 apparmor[13213]: with the 'teardown' option." Nov 24 16:50:14 pkvmhab006 systemd[1]: Stopped LSB: AppArmor initialization. # virsh restore /var/tmp/save.file error: Failed to restore domain from /var/tmp/save.file error: operation failed: job: unexpectedly failed Attached: Sosreport -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1719579 Title: [Ubuntu 16.04.2] [libvirt] virsh restore fails from state file saved in /var/tmp folder using virsh save Status in The Ubuntu-power-systems project: Incomplete Status in apparmor package in Ubuntu: Incomplete Bug description: == Comment: #1 - SEETEENA THOUFEEK - 2017-01-17 00:09:16 == Bala, Please mail me the machine information. == Comment: #3 - SEETEENA THOUFEEK - 2017-01-17 02:14:06 == 2017-01-16 12:09:37.707+: 7024: info : virSecurityDACRestoreFileLabelInternal:388 : Restoring DAC user and group on '/var/tmp/bala' 2017-01-16 12:09:37.707+: 7024: info : virSecurityDACSetOwnershipInternal:290 : Setting DAC user and group on '/var/tmp/bala' to '0:0' 2017-01-16 12:09:37.707+: 7024: warning : qemuDomainSaveImageStartVM:6750 : failed to restore save state label on /var/tmp/bala 2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: obj=0x3fff4ca62b00 2017-01-16 12:09:37.707+: 7024: debug : qemuDomainObjEndAsyncJob:1848 : Stopping async job: start (vm=0x3fff4ca535c0 name=virt-tests-vm1-bala) 2017-01-16 12:09:37.707+: 7024: info : virObjectRef:296 : OBJECT_REF: obj=0x3fff4ca62b00 2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: obj=0x3fff4ca62b00 2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: obj=0x3fff4ca535c0 2017-01-16 12:09:37.707+: 7024: debug : virThreadJobClear:121 : Thread 7024 (virNetServerHandleJob) finished job remoteDispatchDomainRestore with ret=-1 2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: obj=0x3fff7c002c10 2017-01-16 12:09:37.707+: 7024: debug : virNetServerProgramSendError:153 : prog=536903814 ver=1 proc=54 type=1 serial=4 msg=0x100133d2590 rerr=0x3fffa59be3c0 2017-01-16 12:09:37.707+: 7024: debug : virNetMessageEncodePayload:376 : Encode length as 172 2017-01-16 12:09:37.707+: 7024: debug : virNetServerClientSendMessageLocked:1399 : msg=0x100133d2590 proc=54 len=172 offset=0 2017-01-16 12:09:37.707+: 7024: info : virNetServerClientSendMessageLocked:1407 : RPC_SERVER_CLIENT_MSG_TX_QUEUE: client=0x100133d23c0 len=172 prog=536903814 vers=1 proc=54 type=1 status=1 serial=4 2017-01-16 12:09:37.707+: 7024: debug : virNetServerClientCalculateHandleMode:157 : tls=(nil) hs=-1, rx=0x100133d0670 tx=0x100133d2590 2017-01-16 12:09:37.707+: 7024: debug : virNetServerClientCalculateHandleMode:192 : mode=3 2017-01-16 12:09:37.707+: 7024: info : virEventPollUpdateHandle:152 : EVENT_POLL_UPDATE_HANDLE: watch=417 events=3 2017-01-16 12:09:37.707+: 7024: debug : virEventPollInterruptLocked:727 : Interrupting 2017-01-16 12:09:37.707
[Touch-packages] [Bug 1719579] sosreport
--- Comment (attachment only) From balamuruh...@in.ibm.com 2017-11-24 06:24 EDT--- ** Attachment added: "sosreport" https://bugs.launchpad.net/bugs/1719579/+attachment/5014048/+files/sosreport-virsh.restore-20171124165138.tar.xz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1719579 Title: [Ubuntu 16.04.2] [libvirt] virsh restore fails from state file saved in /var/tmp folder using virsh save Status in The Ubuntu-power-systems project: Incomplete Status in apparmor package in Ubuntu: Incomplete Bug description: == Comment: #1 - SEETEENA THOUFEEK - 2017-01-17 00:09:16 == Bala, Please mail me the machine information. == Comment: #3 - SEETEENA THOUFEEK - 2017-01-17 02:14:06 == 2017-01-16 12:09:37.707+: 7024: info : virSecurityDACRestoreFileLabelInternal:388 : Restoring DAC user and group on '/var/tmp/bala' 2017-01-16 12:09:37.707+: 7024: info : virSecurityDACSetOwnershipInternal:290 : Setting DAC user and group on '/var/tmp/bala' to '0:0' 2017-01-16 12:09:37.707+: 7024: warning : qemuDomainSaveImageStartVM:6750 : failed to restore save state label on /var/tmp/bala 2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: obj=0x3fff4ca62b00 2017-01-16 12:09:37.707+: 7024: debug : qemuDomainObjEndAsyncJob:1848 : Stopping async job: start (vm=0x3fff4ca535c0 name=virt-tests-vm1-bala) 2017-01-16 12:09:37.707+: 7024: info : virObjectRef:296 : OBJECT_REF: obj=0x3fff4ca62b00 2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: obj=0x3fff4ca62b00 2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: obj=0x3fff4ca535c0 2017-01-16 12:09:37.707+: 7024: debug : virThreadJobClear:121 : Thread 7024 (virNetServerHandleJob) finished job remoteDispatchDomainRestore with ret=-1 2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: obj=0x3fff7c002c10 2017-01-16 12:09:37.707+: 7024: debug : virNetServerProgramSendError:153 : prog=536903814 ver=1 proc=54 type=1 serial=4 msg=0x100133d2590 rerr=0x3fffa59be3c0 2017-01-16 12:09:37.707+: 7024: debug : virNetMessageEncodePayload:376 : Encode length as 172 2017-01-16 12:09:37.707+: 7024: debug : virNetServerClientSendMessageLocked:1399 : msg=0x100133d2590 proc=54 len=172 offset=0 2017-01-16 12:09:37.707+: 7024: info : virNetServerClientSendMessageLocked:1407 : RPC_SERVER_CLIENT_MSG_TX_QUEUE: client=0x100133d23c0 len=172 prog=536903814 vers=1 proc=54 type=1 status=1 serial=4 2017-01-16 12:09:37.707+: 7024: debug : virNetServerClientCalculateHandleMode:157 : tls=(nil) hs=-1, rx=0x100133d0670 tx=0x100133d2590 2017-01-16 12:09:37.707+: 7024: debug : virNetServerClientCalculateHandleMode:192 : mode=3 2017-01-16 12:09:37.707+: 7024: info : virEventPollUpdateHandle:152 : EVENT_POLL_UPDATE_HANDLE: watch=417 events=3 2017-01-16 12:09:37.707+: 7024: debug : virEventPollInterruptLocked:727 : Interrupting 2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: obj=0x3fff7c002c10 2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: obj=0x100133caea0 2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: obj=0x100133d23c0 . 2017-01-16 12:14:28.445+: 7019: info : qemuMonitorJSONIOProcessLine:201 : QEMU_MONITOR_RECV_EVENT: mon=0x3fff94004d90 event={"timestamp": {"seconds": 1484568868, "microseconds": 444620}, "event": "MIGRATION", "data": {"status": "failed"}} 2017-01-16 12:14:28.445+: 7019: debug : qemuMonitorJSONIOProcessEvent:147 : mon=0x3fff94004d90 obj=0x100133b5670 2017-01-16 12:14:28.445+: 7019: debug : virJSONValueToString:1762 : object=0x100133a8000 2017-01-16 12:14:28.445+: 7019: debug : virJSONValueToStringOne:1691 : object=0x100133a8000 type=0 gen=0x100133d1160 2017-01-16 12:14:28.445+: 7019: debug : virJSONValueToStringOne:1691 : object=0x100133d2a80 type=2 gen=0x100133d1160 2017-01-16 12:14:28.445+: 7019: debug : virJSONValueToString:1795 : result={"status":"failed"} 2017-01-16 12:14:28.445+: 7019: debug : qemuMonitorEmitEvent:1218 : mon=0x3fff94004d90 event=MIGRATION 2017-01-16 12:14:28.445+: 7019: info : virObjectRef:296 : OBJECT_REF: obj=0x3fff94004d90 2017-01-16 12:14:28.445+: 7019: debug : qemuProcessHandleEvent:629 : vm=0x3fff4ca535c0 2017-01-16 12:14:28.445+: 7019: info : virObjectNew:202 : OBJECT_NEW: obj=0x100133d2870 classname=virDomainQemuMonitorEvent 2017-01-16 12:14:28.445+: 7019: debug : virObjectEventNew:645 : obj=0x100133d2870 2017-01-16 12:14:28.445+: 7019: info : virObjectUnref:259 : OBJECT_UNREF: obj=0x100133d2870 2017-01-16 12:14:28.445+: 7019: info : virObjectUnref:261 : OBJECT_DISPOSE: obj=0x100133d2870 2017-01-16 12:14:28.445+0
[Touch-packages] [Bug 1734040] Re: openssh: The concurrency of settimeofday and ssh connect would lead to coredump
Thank you for taking the time to report this bug and helping to make Ubuntu better. I appreciate the quality of this bug report and I'm sure it'll be helpful to others experiencing the same issue. This sounds like an upstream bug to me. Please can you verify this by building directly from the latest upstream source? If this can be confirmed as an upstream bug, the best route to getting it fixed in Ubuntu in this case would be to file an upstream bug if you're able to do that. Otherwise, I'm not sure what we can do directly in Ubuntu to fix the problem. Slightly old, but still mostly applicable info about doing so can be found at [1] If you do end up filing an upstream bug, please link to it from here. Thanks! [1]: https://wiki.ubuntu.com/Bugs/Upstream/OpenSSH -- 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/1734040 Title: openssh: The concurrency of settimeofday and ssh connect would lead to coredump Status in openssh package in Ubuntu: New Bug description: Hi, pals: we found a coredump when we do ssh connection. the basic information as follow: the stack trace in coredump: (gdb) bt #0 0x20007510 in raise () from /lib/libc.so.6 #1 0x2000c718 in abort () from /lib/libc.so.6 #2 0x2053d42c in __mulvsi3 (a=, b=) at /home/l00194794/yocto/c08_sdk/sdk/build/script/cpu_hcc/ppc-linux/../../../toolchain_soft/ppc-linux/src/gcc-4.7.1/libgcc/libgcc2.c:159 #3 0x2050d030 in ms_subtract_diff (start=start@entry=0xbfa20a9c, ms=0x48027c40, ms@entry=0xbfa20a98) at misc.c:871 #4 0x204d2568 in ssh_exchange_identification (timeout_ms=timeout_ms@entry=5000) at sshconnect.c:580 #5 0x204d3e3c in ssh_login (sensitive=sensitive@entry=0x20586ea8, orighost=, hostaddr=hostaddr@entry=0x20586e28, port=, pw=pw@entry=0x20589ae8, timeout_ms=5000) at sshconnect.c:1346 #6 0x204c433c in main (ac=, av=) at ssh.c:1326 the direct cause of the coredump, is that the function __mulvsi3 in gcc checked the plus operation is overflow, then this gcc function abort(). the reason of the overflow is cause by the time-setting operation when do ssh connect. in function ms_subtract_diff . the timeoutp get a very big value because of the time-change. So could we add a limitation for the differ of the 2 values get from gettimeofday ? if it's too big, would lead to overflow, we set a default value and report a warning log. thanks for you attention and expect your reply. B.R. Le Wang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1734040/+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 1722708] Re: Crash when setting laptop display resolution
This problem still affects me: - I got a full HD monitor (1920x1080) connected via HDMI. - Laptop display with internal resolution 3200x1800. If I try to change the laptop display to 1600x900 (custom added resolution btw) to use 100% window scaling on both monitors, I'm instantly returned to the login screen (resolution changes are not applied). This happens every time I try to do this. However, I was able to change the laptop monitor resolution to 1920x1080! And, afterwards, I could even successfully change to 1600x900. -- 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/1722708 Title: Crash when setting laptop display resolution Status in xorg package in Ubuntu: Fix Released Bug description: This system has a 4k laptop screen with resolution 3840x2160, and an external HP monitor connected via HDMI, resolution 1920x1200. Windows, fonts etc are not scaled properly on the external monitor (too large, etc), and the only workaround I've found with earlier versions and other distros is to set the laptop display to 1920x1080 mode, so that's what I'm trying here as well. However, when doing that, the X (wayland, not sure if the package is correct here) session crashes and brings me back to login screen. So to summarize: connect the external monitor, go to Settings > Devices > Displays, click primary built in display, observe that it shows Resolution 3840x2160 (16:9) and Scale 200%, change resolution to 1920x1080 (16:9), click Apply --> crash. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 BootLog: CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Oct 11 07:49:08 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:2248] Subsystem: Lenovo GM108M [GeForce 940MX] [17aa:2248] InstallationDate: Installed on 2017-10-10 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171008) MachineType: LENOVO 20H9004MMX ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic.efi.signed root=UUID=182b5236-fa96-4fb5-bea9-f90769b65f3c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1VET35W (1.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 20H9004MMX dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1VET35W(1.25):bd09/06/2017:svnLENOVO:pn20H9004MMX:pvrThinkPadT570:rvnLENOVO:rn20H9004MMX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T570 dmi.product.name: 20H9004MMX dmi.product.version: ThinkPad T570 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1722708/+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 1716203] Re: Backport packages for 16.04.4 HWE stack
Hello Timo, or anyone else affected, Accepted xorg-server-hwe-16.04 into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xorg- server-hwe-16.04/2:1.19.5-0ubuntu2~16.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: xorg-server-hwe-16.04 (Ubuntu Xenial) Status: New => Fix Committed -- 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/1716203 Title: Backport packages for 16.04.4 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-5.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in wayland-protocols package in Ubuntu: Invalid Status in xorg-hwe-16.04 package in Ubuntu: Invalid Status in xorg-server-hwe-16.04 package in Ubuntu: Invalid Status in libclc source package in Xenial: Fix Committed Status in libdrm source package in Xenial: Fix Committed Status in llvm-toolchain-5.0 source package in Xenial: Fix Committed Status in mesa source package in Xenial: Fix Committed Status in wayland-protocols source package in Xenial: Fix Committed Status in xorg-hwe-16.04 source package in Xenial: New Status in xorg-server-hwe-16.04 source package in Xenial: Fix Committed Bug description: [Impact] *** hwe-16.04 refresh for 16.04.4 *** A minor update, only some driver updates plus a newer Mesa. Mesa needs llvm-toolchain-5.0 and libclc, libdrm, wayland-protocols updates. [Test case] upgrade from/to stock & old hwe stack, test desktop usage [Regression potential] libdrm: Slim to none, changes from 2.4.76 to 2.4.83 - amdgpu: pci-id handling moved here, new pci-ids, bugfixes, tests - intel: new pci-ids - drm: leak fixes, manpage updates - exynos, etnaviv, freedreno, android: fixes, new stuff wayland-protocols: None, just adds a few protocol definitions (xml files) llvm-toolchain-5.0: None, a new package libclc: I'd say none, very little has changed, added support for llvm-5 is the main reason for this slightly newer snapshot xorg-server: Slim, it's an upstream bugfix release, changes from 1.19.3 to 1.19.5 include: - security fixes - backported bugfixes to glamor, modesetting driver, xwayland etc mesa: New major release plus a few bugfix updates after that. Regressions at this point are less likely. Upstream is tested by Intel CI system for instance. And we're already testing it via a ppa on OEM systems for 16.04.4. Tracking bug for the bugfix release (xenial & artful) is bug 1727390 [Other information] build order: [libdrm, wayland-protocols, llvm-toolchain-5.0], [libclc, xorg-server], mesa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1716203/+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 1734212] Re: package openssh-server 1:7.5p1-10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Hi tenwit, thanks for your report! You did just right to clean up and complete the installation. On the error that occurred, what I can find related in your log is: frontend: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. I found various such issues across the past - not frequent but every now and then: - bug 951404 - bug 821630 None came to a perfect conclusion, but it matches the error in your log as well as the symptom "the graphical login having crashed". That took down everything else with it, so the upgrade which you completed later on. You might read through those bugs, there are some hints on lightdm.conf being responsible, but since you are "out of the bug" already that might not matter to you anymore. On the actual issue I don't see openssh related in any way - instead I'll re-file this against Given that this seems to be something like an X server dying checking and attaching those logs might help the Team around lightdm and such as well. ** Package changed: openssh (Ubuntu) => lightdm (Ubuntu) -- 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/1734212 Title: package openssh-server 1:7.5p1-10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in lightdm package in Ubuntu: New Bug description: Happened during upgrade of Ubuntu from 17.04 to 17.10. Stepped away from desk; when I came back I was locked out. I didn't recognize the lock screen. There was no way to log back into the session, no password prompt etc. I switched to a VT and monitored top for a while: "artful" was minimally active, but never about 2% CPU and memory never changed; I guessed it was waiting for a user prompt which I'd never be able to give, so I rebooted. I got this error on boot. The system is now usable. I've done `dpkg configure -a; apt upgrade` and it's all working as I'd expect. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: openssh-server 1:7.5p1-10 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 Date: Fri Nov 24 10:52:14 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-10-12 (42 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: openssh Title: package openssh-server 1:7.5p1-10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to artful on 2017-11-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1734212/+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 1734104] Re: 'upgrade' in bionic should by default autoremove as well
** Tags added: bionic -- 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/1734104 Title: 'upgrade' in bionic should by default autoremove as well Status in apt package in Ubuntu: New Bug description: In bionic, apt upgrade should also autoremove by default. I have a few bionic systems (upgrades from xenial mostly) which are not yet showing that behaviour, it may be we haven't implemented that yet so this is just a placeholder bug in that case :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1734104/+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 1734285] [NEW] unattended-upgrades.service ignores (changes in) /etc/apt/preferences.d/ files
Public bug reported: unattended-upgrades.service ignores (changes in) /etc/apt/preferences.d/ files that are done after the service has started. For example we 'pin' firefox on to a specific version and if a configuration file is placed after the service is started, the pinning is ignored. In our sitation that results in a newer firefox then we want at this moment. We run Ubuntu on 2000+ workstations and our users often start a workstation and let it run for days/weeks before rebooting and thus restarting the service unattended-upgrades again. I did not test if changes in other apt files are ignored also. ** Affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: New -- 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/1734285 Title: unattended-upgrades.service ignores (changes in) /etc/apt/preferences.d/ files Status in unattended-upgrades package in Ubuntu: New Bug description: unattended-upgrades.service ignores (changes in) /etc/apt/preferences.d/ files that are done after the service has started. For example we 'pin' firefox on to a specific version and if a configuration file is placed after the service is started, the pinning is ignored. In our sitation that results in a newer firefox then we want at this moment. We run Ubuntu on 2000+ workstations and our users often start a workstation and let it run for days/weeks before rebooting and thus restarting the service unattended-upgrades again. I did not test if changes in other apt files are ignored also. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1734285/+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