[Touch-packages] [Bug 1817799] Re: [FFe] apparmor 2.13
As discussed on IRC, if the upgrade is clean, and you're committing to keeping a close eye on bugs/regressions and fixing ASAP, go for it. ** Changed in: apparmor (Ubuntu) Status: New => Triaged -- 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/1817799 Title: [FFe] apparmor 2.13 Status in apparmor package in Ubuntu: Triaged Bug description: Feature Freeze exception for AppArmor 2.13.2 The security team is pushing to get AppArmor 2.13 into 19.04 since we want AppArmor 3 (or higher) in 20.04 and we'd like to update to 2.13.2 to have widespread use of its new features and make the overall experience to AppArmor 3 better tested and less disruptive. The 2.13.2 series over 2.12 is primarily incremental improvements in the parser, libapparmor, userspace tooling and policy; Debian started preparing 2.13 in experimental last June where the first upload to unstable was made in July. Since then, Debian has worked closely with upstream and Ubuntu devs to shake out bugs and improve the packaging. There are no new mediation rules so the chance of regression in terms of parser/kernel/policy updates is considered low. IME, the primary points of interest for the FFe surround the following: * apparmor_parser in 2.13 now creates subdirectories in the cache directory with the subdir name based on the kernel features. This improves the experience when booting between kernels with different feature sets * Debian moved /etc/apparmor.d/cache to /var/cache/apparmor (first upload with this change in August) * the init process now uses proper systemd unit instead of calling out to SysV init script. This and rc.apparmor.functions cleanups were done in coordination with Ubuntu devs (first upload in December) * due to bug #1820068, the 2.12 and earlier Ubuntu-distro patch to use -O no-expr-simplify (helps with policy compilation times on armhf) has been reverted. We'll get the bug fixed before disco release Debian has been very active in improving the packaging since the plan is to release with AppArmor by default in Buster (it has been on by default in Debian testing for a long time, before the 2.13 uploads). A version of 2.13.2 has been in Debian testing (Buster) since January with the 2.13.2-9 version that this FFe is based on migrating last week. Debian improved autopkgtests throughout Buster, worked with upstream and Ubuntu devs throughout. Because of the extensive baking in Debian, I think it is reasonable to consider granting the exception (indeed, part of why we missed Disco's freeze was because we were working with Debian on improving the package for Buster's freeze). While most software in Ubuntu doesn't care about the systemd or cache changes, it was known that snapd manages snap cache files on snap remove, and snapd needed to be changed to account for this[2]. This update is included in snapd 2.38 which is now in disco. Because of the change in the apparmor cache, I have introduced a Breaks: snapd (<< 2.38~) in the apparmor package since snaps cannot be removed (snapd aborts the removal when the cache file is not found; which is a little strict IMO, but I digress). In terms of testing, we exercised our test plan, like normal[1]. This includes upgrade testing, verifying profile load on boot, cache is used and software with apparmor integration continue to work (snapd, lxc, lxd, libvirt, docker, etc). Anecdotally I have been using 2.13.2 for some time without issue (and I have a lot of snap, distro and personal policy). The source tarball does not contain a changelog, instead the upstream release notes can be found here: * https://gitlab.com/apparmor/apparmor/wikis/Release_Notes_2.13 * https://gitlab.com/apparmor/apparmor/wikis/Release_Notes_2.13.1 * https://gitlab.com/apparmor/apparmor/wikis/Release_Notes_2.13.2 [1]https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor [2]https://github.com/snapcore/snapd/pull/6549 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1817799/+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 1795857] Re: enable CONFIG_DRM_BOCHS
The original bug report was on PowerKVM (ppc64el qemu). In testing that it was okay to revert this wholesale in both kmod and kernel, did anyone test POWER? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1795857 Title: enable CONFIG_DRM_BOCHS Status in kmod package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: CONFIG_DRM_BOCHS got disabled for https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1378648 but doing so regressed running qemu with the 'std' VGA driver, where it'd fail to start X after install, as mentioned on bug 1794280 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1795857/+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 1795857] Re: enable CONFIG_DRM_BOCHS
I'm rejecting the kmod upload in the disco queue until the above comment is addressed, so we don't get into a revert war. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1795857 Title: enable CONFIG_DRM_BOCHS Status in kmod package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: CONFIG_DRM_BOCHS got disabled for https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1378648 but doing so regressed running qemu with the 'std' VGA driver, where it'd fail to start X after install, as mentioned on bug 1794280 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1795857/+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 1795857] Re: enable CONFIG_DRM_BOCHS
What was the host system (ie: what version of qemu)? I want to be sure this works going back as far as we support (so, trusty hosts). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1795857 Title: enable CONFIG_DRM_BOCHS Status in kmod package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: CONFIG_DRM_BOCHS got disabled for https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1378648 but doing so regressed running qemu with the 'std' VGA driver, where it'd fail to start X after install, as mentioned on bug 1794280 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1795857/+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 1822341] Re: [FFE][SRU] Please add ubuntu-wsl binary package
This hand-crafted patch is wrong. The way the seeds are laid out, ubuntu-wsl should depend on exactly one package, not dozens. STRUCTURE is not an include hierarchy (if it was, all of minimal would be in desktop, for instance), it describes inheritance. "wsl: minimal" means "if it's in minimal, don't include it in wsl, so I don't have the same packages listed twice". wsl installs should install minimal (as *all* Ubuntu installations do) and ubuntu-wsl. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1822341 Title: [FFE][SRU] Please add ubuntu-wsl binary package Status in ubuntu-meta package in Ubuntu: New Bug description: [Impact] * The newly added wsl seed includes the packages to be installed by default on Ubuntu running in the Windows Subsystem for Linux. In addition to the packages in ubuntu-minimal the added ubuntu-wsl metapackage depends on on utilities useful only in the WSL environment. [Test Case] * The package is a new metapackage, just try installing it [Fix] * The change add the new package and also adds the wsl seed to watch. [Regression potential] * Nothing, it is a new meta package, with no breaks, etc. [Other Info] * Please consider accepting this new binary package to Disco, because it needs to be SRU-d to all supported releases. The ubuntu-wsl metapackage will allow adding new packages for WSL installations only when more integration utilities become available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1822341/+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 1816642] Re: SRU of LXC 2.0.11
Hello Stéphane, or anyone else affected, Accepted lxc into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/lxc/2.0.11-0ubuntu1~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, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: lxc (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1816642 Title: SRU of LXC 2.0.11 Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Trusty: Triaged Status in lxc source package in Xenial: Fix Committed Bug description: LXC upstream has released a new bugfix release for the LXC 2.0 LTS branch. This is version 2.0.10. Ubuntu never received 2.0.9 as an SRU, so the changelog for both of them can be found below: LXC 2.0.11: - autotools: handle getgrgid_r on bionic - autotools: add memory_utils.h to Makefile.am - change version to 2.0.11 in configure.ac LXC 2.0.10: - tools: allow lxc-attach to undefined containers - utils: move memfd_create() definition - utils: add lxc_cloexec() - utils: add lxc_make_tmpfile() - utils: add lxc_getpagesize() - utils: add lxc_safe_long_long() - utils: parse_byte_size_string() - utils: add lxc_find_next_power2() - namespace: use lxc_getpagesize() - lxc-debian: allow creating `testing` and `unstable` - Call lxc_config_define_load from lxc_execute again - Fix typo in lxc-net script - Add missing lxc_container_put - lxc-debian: don't write C.* locales to /etc/locale.gen - attach: correctly handle namespace inheritance - cgfsng: fix cgroup2 detection - cgroups: enable container without CAP_SYS_ADMIN - lxc-start: remove unnecessary checks - start: close non-needed file descriptors - handler: make name argument const - start: close data socket in parent - monitor: do not log useless warnings - network: reap child in all cases - conf: reap child in all cases - storage: switch to ext4 as default filesystem - tools: fix help output of lxc-create - attach: handle namespace inheritance - cgroups/cgfsng: keep mountpoint intact - cgroups/cgfsng: cgfsns_chown() -> cgfsng_chown() - cgroups/cgfsng: support MS_READONLY with cgroup ns - log: check for i/o error with vsnprintf() - cgroupfs/cgfsng: tweak logging - cgroups/cgfsng: remove is_lxcfs() - cgroups/cgfsng: fix get_controllers() for cgroup2 - cgroupfs/cgfsng: improve cgroup2 handling - config: remove SIGRTMIN+14 as lxc.signal.stop - commands: non-functional changes - console: non-functional changes - console: non-functional changes - lxc-test-unpriv: fix the overlayfs mount error - attach: allow attach with empty conf - tools/lxc_attach: removed api logging - console: fix console info message - Add missing dependency libunistring - cgroups/cgfsng: adapt to new cgroup2 delegation - console: report detach message on demand - lxccontainer: enable daemonized app containers - console: use correct escape sequence check - console: prepare for generic signal handler - console: exit mainloop on SIGTERM - commands: non-functional changes - lxccontainer: non-functional changes - commands: fix state socket implementation - lxc_init: set the control terminal in the child session - lxc-test-unpriv: check user existence before removing it - Fixed typo on lxc.spec.in - conf: move CAP_SYS_* definitions to utils.h - start.c: always switch uid and gid - Use AX_PTHREAD config script to detect pthread api - utils.h: Avoid duplicated sethostname implementation - tools/lxc_cgroup: remove internal logging - tools/lxc_autostart: remove internal logging - tools/lxc_clone: remove internal logging - tools/lxc_console: remove internal logging - tools/lxc_create: remove inter
[Touch-packages] [Bug 1818953] Re: mblen() failing in Perl / Perl core dumping core on UBUNTU 19.04 by executing perl script, multiple architectures
This is fixed in perl 5.28.1-6, now in the disco release pocket.
** Changed in: perl (Ubuntu Disco)
Status: Confirmed => Fix Released
** Changed in: ubuntu-power-systems
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to perl in Ubuntu.
https://bugs.launchpad.net/bugs/1818953
Title:
mblen() failing in Perl / Perl core dumping core on UBUNTU 19.04 by
executing perl script, multiple architectures
Status in The Ubuntu-power-systems project:
Fix Released
Status in perl package in Ubuntu:
Fix Released
Status in perl source package in Disco:
Fix Released
Status in perl package in Debian:
Unknown
Bug description:
== Comment: #0 - NAGENDRA P. DONTAMSETTY - 2019-02-28
00:14:49 ==
---Problem Description---
Perl core dumping core on UBUNTU 19.04 by executing perl script
---uname output---
root@p8ct1p13:/tmp# uname -a Linux p8ct1p13.in.ibm.com 4.19.0-13-generic
#14-Ubuntu SMP Thu Feb 7 21:50:00 UTC 2019 ppc64le ppc64le ppc64le GNU/Linux
Machine Type = ppc64le and power8
---Debugger Data---
root@p8ct1p13:/tmp# file core
core: ELF 64-bit LSB core file, 64-bit PowerPC or cisco 7500, version 1
(SYSV), SVR4-style, from '/usr/bin/perl /usr/bin/mkrsrc IBM.Ray Name=fvt1
NodeNameList={p8ct1p09.in.ibm.c', real uid: 0, effective uid: 0, real gid: 0,
effective gid: 0, execfn: '/usr/bin/mkrsrc', platform: 'power8'
---Steps to Reproduce---
Description: Perl core dumpinmg core on UBUNTU 19.04 by exec cmd "mkrsrc"
root@p8ct1p13:/tmp# uname -a
Linux p8ct1p13.in.ibm.com 4.19.0-13-generic #14-Ubuntu SMP Thu Feb 7 21:50:00
UTC 2019 ppc64le ppc64le ppc64le GNU/Linux
root@p8ct1p13:~# cat /etc/os-release
NAME="Ubuntu"
VERSION="19.04 (Disco Dingo)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu Disco Dingo (development branch)"
VERSION_ID="19.04"
HOME_URL="https://www.ubuntu.com/";
SUPPORT_URL="https://help.ubuntu.com/";
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy";
VERSION_CODENAME=disco
UBUNTU_CODENAME=disco
root@p8ct1p13:~# ctversion -bv
RSCT_Build_Name=rsholxs002a 3.2.4.2 RSCT_Build_Time=19043.16:11:49
RSCT_Build_Context=ppc64le_linux_2
root@p8ct1p13:/tmp# mkrsrc IBM.Ray Name="fvt1"
NodeNameList={"p8ct1p09.in.ibm.com"} ManualMode=0 Int32=00 String="Initial Test
String 2"
perl: mbrtowc.c:105: __mbrtowc: Assertion `__mbsinit (data.__statep)' failed.
Aborted (core dumped)
root@p8ct1p13:/tmp# file core
core: ELF 64-bit LSB core file, 64-bit PowerPC or cisco 7500, version 1
(SYSV), SVR4-style, from '/usr/bin/perl /usr/bin/mkrsrc IBM.Ray Name=fvt1
NodeNameList={p8ct1p09.in.ibm.c', real uid: 0, effective uid: 0, real gid: 0,
effective gid: 0, execfn: '/usr/bin/mkrsrc', platform: 'power8'
root@p8ct1p13:/tmp# which mkrsrc
/usr/bin/mkrsrc
root@p8ct1p13:/tmp# file /usr/bin/mkrsrc
/usr/bin/mkrsrc: symbolic link to /opt/rsct/bin/mkrsrc
root@p8ct1p13:/tmp# file /opt/rsct/bin/mkrsrc
/opt/rsct/bin/mkrsrc: Perl script text executable
Contact Information = Nagendra Dontamsetty/ndont...@in.ibm.com,
Anirban/anirb...@in.ibm.com
Userspace tool common name: perl 5
The userspace tool has the following bit modes: 64bit
Userspace rpm: ii perl 5.28.1-4
ppc64el
Userspace tool obtained from project website: na
*Additional Instructions for Nagendra Dontamsetty/ndont...@in.ibm.com,
Anirban/anirb...@in.ibm.com:
-Post a private note with access information to the machine that is currently
in the debugger.
-Attach ltrace and strace of userspace application.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1818953/+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 1789924] Re: Missing Intel GPU pci-id's
Hello Timo, or anyone else affected, Accepted libdrm into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libdrm/2.4.95-1~18.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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: libdrm (Ubuntu Bionic) Status: Confirmed => Fix Committed ** Tags removed: verification-done-bionic ** Tags added: verification-needed-bionic -- 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/1789924 Title: Missing Intel GPU pci-id's Status in libdrm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Fix Released Status in libdrm source package in Bionic: Fix Committed Status in linux source package in Bionic: Fix Released Status in mesa source package in Bionic: Confirmed Status in xorg-server source package in Bionic: Fix Released Bug description: [Impact] There are some new Intel GPU pci-id's that need to be added to several places: 0x3E98 0x87C0 and to make future additions easier, add platform definitions for Whiskey Lake and Amber Lake too. [Test case] Check that the user session uses the proper driver on these systems. [Regression potential] none, these just add pci-id's and platform definitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1789924/+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 1798597] Please test proposed package
Hello Timo, or anyone else affected, Accepted libdrm into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libdrm/2.4.95-1~18.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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/1798597 Title: Backport packages for 18.04.2 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-7 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in libclc source package in Bionic: New Status in libdrm source package in Bionic: Fix Committed Status in llvm-toolchain-7 source package in Bionic: Fix Committed Status in mesa source package in Bionic: New Status in xorg-server source package in Bionic: New Bug description: [Impact] [Test case] [Regression potential] libdrm: llvm-7: libclc: mesa: xserver: drivers: [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1798597/+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 1798597] Re: Backport packages for 18.04.2 HWE stack
Hello Timo, or anyone else affected, Accepted llvm-toolchain-7 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/llvm- toolchain-7/1:7-3~ubuntu0.18.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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: llvm-toolchain-7 (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-bionic ** Changed in: libdrm (Ubuntu Bionic) 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/1798597 Title: Backport packages for 18.04.2 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-7 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in libclc source package in Bionic: New Status in libdrm source package in Bionic: Fix Committed Status in llvm-toolchain-7 source package in Bionic: Fix Committed Status in mesa source package in Bionic: New Status in xorg-server source package in Bionic: New Bug description: [Impact] [Test case] [Regression potential] libdrm: llvm-7: libclc: mesa: xserver: drivers: [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1798597/+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 1770082] Please test proposed package
Hello Daniel, or anyone else affected,
Accepted netplan.io into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/netplan.io/0.40.1~18.04.3 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-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
--
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/1770082
Title:
systemd-networkd not renaming devices on boot
Status in netplan:
Fix Released
Status in cloud-init package in Ubuntu:
Confirmed
Status in netplan.io package in Ubuntu:
Fix Released
Status in nplan package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Confirmed
Status in nplan source package in Xenial:
Fix Released
Status in netplan.io source package in Bionic:
Fix Committed
Status in netplan.io source package in Cosmic:
Fix Committed
Bug description:
[Impact]
Systems relying on renaming network interfaces at boot and when 'netplan
apply' is run.
[Test case]
- Write a new netplan YAML (adjusting for current system as necessary):
network:
version: 2
ethernets:
ens3:
dhcp4: true
match:
macaddress: 52:54:00:de:bd:f6
set-name: myif0
- Bring down interface : 'ip link set dev ens3 down'
- Run 'netplan apply'
- Verify that the device is correctly renamed to 'myif0'.
- Reboot.
- Make sure the device is correctly renamed to 'myif0'.
[Regression potential]
Changes in rename logic to add udev rules may otherwise impact applying
different settings to the network interfaces. Changes in settings on network
interfaces, missing parameters (especially on bonds, bridges) should be
investigated as potential regressions. Other failures to apply network settings
might also happen if there's a race between applying renames via the udev
rules, and using the new names to apply configuration changes to the interfaces.
=== systemd issue ===
Renaming devices doesn't seem to work.
If I disable all other network configuration and create
/etc/systemd/network/10-network.link with:
[Match]
MACAddress=52:54:00:c1:c9:bb
[Link]
Name=myiface3
I expect this to cause the device with that MAC address to be renamed
to myiface3. However, when I reboot, I instead see:
$ ip l
1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode
DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: ens3: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff
The device is not renamed.
This link file is pretty much identical to Example 2 in
https://www.freedesktop.org/software/systemd/man/systemd.link.html.
The renaming does work if I boot with net.ifnames=0, and oddly, it
also works if I unbind the device and rebind it as netplan apply does.
No setting of NamePolicy seems to help.
=== Original Bug ==
'set-name:' doesn't change the name of a network interface on boot, it
only works when you do netplan apply.
Say I take this 50-cloud-init.yaml file:
# This file is generated from information provided by
# the datasource. Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
version: 2
ethernets:
ens3:
dhcp4: true
match:
macaddress: 52:54:00:de:bd:f6
set-name: ens3
Say I change set-name to 'myiface3' and reboot. I expect that the
device will be called myiface3 and brought up fine with dhcp. However,
instead I see:
$ ip a
1: lo: mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot
Hello Daniel, or anyone else affected,
Accepted netplan.io into cosmic-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/netplan.io/0.40.2.2
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-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Tags removed: verification-done-cosmic
** Tags added: verification-needed verification-needed-cosmic
** Tags removed: verification-done-bionic
** Tags added: verification-needed-bionic
--
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/1770082
Title:
systemd-networkd not renaming devices on boot
Status in netplan:
Fix Released
Status in cloud-init package in Ubuntu:
Confirmed
Status in netplan.io package in Ubuntu:
Fix Released
Status in nplan package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Confirmed
Status in nplan source package in Xenial:
Fix Released
Status in netplan.io source package in Bionic:
Fix Committed
Status in netplan.io source package in Cosmic:
Fix Committed
Bug description:
[Impact]
Systems relying on renaming network interfaces at boot and when 'netplan
apply' is run.
[Test case]
- Write a new netplan YAML (adjusting for current system as necessary):
network:
version: 2
ethernets:
ens3:
dhcp4: true
match:
macaddress: 52:54:00:de:bd:f6
set-name: myif0
- Bring down interface : 'ip link set dev ens3 down'
- Run 'netplan apply'
- Verify that the device is correctly renamed to 'myif0'.
- Reboot.
- Make sure the device is correctly renamed to 'myif0'.
[Regression potential]
Changes in rename logic to add udev rules may otherwise impact applying
different settings to the network interfaces. Changes in settings on network
interfaces, missing parameters (especially on bonds, bridges) should be
investigated as potential regressions. Other failures to apply network settings
might also happen if there's a race between applying renames via the udev
rules, and using the new names to apply configuration changes to the interfaces.
=== systemd issue ===
Renaming devices doesn't seem to work.
If I disable all other network configuration and create
/etc/systemd/network/10-network.link with:
[Match]
MACAddress=52:54:00:c1:c9:bb
[Link]
Name=myiface3
I expect this to cause the device with that MAC address to be renamed
to myiface3. However, when I reboot, I instead see:
$ ip l
1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode
DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: ens3: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff
The device is not renamed.
This link file is pretty much identical to Example 2 in
https://www.freedesktop.org/software/systemd/man/systemd.link.html.
The renaming does work if I boot with net.ifnames=0, and oddly, it
also works if I unbind the device and rebind it as netplan apply does.
No setting of NamePolicy seems to help.
=== Original Bug ==
'set-name:' doesn't change the name of a network interface on boot, it
only works when you do netplan apply.
Say I take this 50-cloud-init.yaml file:
# This file is generated from information provided by
# the datasource. Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
version: 2
ethernets:
ens3:
dhcp4: true
match:
macaddress: 52:54:00:de:bd:f6
set-name: ens3
Say I change set-name to 'myiface3' and reboot. I expect that the
device will be called myiface3 and brought up fine with dhcp. However,
instead I see:
[Touch-packages] [Bug 1798597] Re: Backport packages for 18.04.2 HWE stack
Hello Timo, or anyone else affected, Accepted libclc into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libclc/0.2.0+git20180917-2~ubuntu0.18.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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: libclc (Ubuntu Bionic) 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/1798597 Title: Backport packages for 18.04.2 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-7 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in xf86-input-wacom package in Ubuntu: Invalid Status in xorg package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in xserver-xorg-input-evdev package in Ubuntu: Invalid Status in xserver-xorg-input-joystick package in Ubuntu: Invalid Status in xserver-xorg-input-libinput package in Ubuntu: Invalid Status in xserver-xorg-input-synaptics package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu package in Ubuntu: Invalid Status in xserver-xorg-video-ati package in Ubuntu: Invalid Status in xserver-xorg-video-fbdev package in Ubuntu: Invalid Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Status in xserver-xorg-video-qxl package in Ubuntu: Invalid Status in xserver-xorg-video-vesa package in Ubuntu: Invalid Status in xserver-xorg-video-vmware package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Committed Status in libdrm source package in Bionic: Fix Committed Status in llvm-toolchain-7 source package in Bionic: Fix Committed Status in mesa source package in Bionic: New Status in wayland source package in Bionic: Fix Committed Status in xf86-input-wacom source package in Bionic: New Status in xorg source package in Bionic: New Status in xorg-server source package in Bionic: New Status in xserver-xorg-input-evdev source package in Bionic: New Status in xserver-xorg-input-joystick source package in Bionic: New Status in xserver-xorg-input-libinput source package in Bionic: New Status in xserver-xorg-input-synaptics source package in Bionic: New Status in xserver-xorg-video-amdgpu source package in Bionic: New Status in xserver-xorg-video-ati source package in Bionic: New Status in xserver-xorg-video-fbdev source package in Bionic: New Status in xserver-xorg-video-nouveau source package in Bionic: New Status in xserver-xorg-video-qxl source package in Bionic: New Status in xserver-xorg-video-vesa source package in Bionic: New Status in xserver-xorg-video-vmware source package in Bionic: New Bug description: [Impact] These are needed for 18.04.2 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-7: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 18.2.x series, so there shouldn't be any regressions left at that point xserver: a new major release, but since it's renamed there's no real chance of regression when it hits the archive xorg drivers: same as xserver [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1798597/+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 1798597] Re: Backport packages for 18.04.2 HWE stack
Hello Timo, or anyone else affected, Accepted wayland into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/wayland/1.16.0-1ubuntu1.1~18.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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: wayland (Ubuntu Bionic) 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/1798597 Title: Backport packages for 18.04.2 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-7 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in xf86-input-wacom package in Ubuntu: Invalid Status in xorg package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in xserver-xorg-input-evdev package in Ubuntu: Invalid Status in xserver-xorg-input-joystick package in Ubuntu: Invalid Status in xserver-xorg-input-libinput package in Ubuntu: Invalid Status in xserver-xorg-input-synaptics package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu package in Ubuntu: Invalid Status in xserver-xorg-video-ati package in Ubuntu: Invalid Status in xserver-xorg-video-fbdev package in Ubuntu: Invalid Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Status in xserver-xorg-video-qxl package in Ubuntu: Invalid Status in xserver-xorg-video-vesa package in Ubuntu: Invalid Status in xserver-xorg-video-vmware package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Committed Status in libdrm source package in Bionic: Fix Committed Status in llvm-toolchain-7 source package in Bionic: Fix Committed Status in mesa source package in Bionic: New Status in wayland source package in Bionic: Fix Committed Status in xf86-input-wacom source package in Bionic: New Status in xorg source package in Bionic: New Status in xorg-server source package in Bionic: New Status in xserver-xorg-input-evdev source package in Bionic: New Status in xserver-xorg-input-joystick source package in Bionic: New Status in xserver-xorg-input-libinput source package in Bionic: New Status in xserver-xorg-input-synaptics source package in Bionic: New Status in xserver-xorg-video-amdgpu source package in Bionic: New Status in xserver-xorg-video-ati source package in Bionic: New Status in xserver-xorg-video-fbdev source package in Bionic: New Status in xserver-xorg-video-nouveau source package in Bionic: New Status in xserver-xorg-video-qxl source package in Bionic: New Status in xserver-xorg-video-vesa source package in Bionic: New Status in xserver-xorg-video-vmware source package in Bionic: New Bug description: [Impact] These are needed for 18.04.2 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-7: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 18.2.x series, so there shouldn't be any regressions left at that point xserver: a new major release, but since it's renamed there's no real chance of regression when it hits the archive xorg drivers: same as xserver [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1798597/+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 1781440] Re: package libwayland-dev 1.15.0-2 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/pkgconfig/wayland-egl.pc', which is also in package libegl1
Hello Till, or anyone else affected, Accepted wayland into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/wayland/1.16.0-1ubuntu1.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-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: wayland (Ubuntu Cosmic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-cosmic ** Changed in: wayland (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1781440 Title: package libwayland-dev 1.15.0-2 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/pkgconfig/wayland-egl.pc', which is also in package libegl1-mesa-dev:amd64 18.0.5-0ubuntu0~18.04.1 Status in wayland package in Ubuntu: Fix Released Status in wayland source package in Bionic: Fix Committed Status in wayland source package in Cosmic: Fix Committed Bug description: [impact] upgrade from bionic fails if libwayland-dev & libegl1-mesa-dev was installed [test case] install libwayland-dev & libegl1-mesa-dev on bionic, upgrade to cosmic [regression potential] none, the fix only changes the version numbers in Breaks/Replaces -- Occured when upgrading from Bionic to Cosmic. ProblemType: Package DistroRelease: Ubuntu 18.10 Package: libwayland-dev 1.15.0-2 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 ApportVersion: 2.20.10-0ubuntu5 Architecture: amd64 CompositorRunning: None Date: Thu Jul 12 18:41:26 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/pkgconfig/wayland-egl.pc', which is also in package libegl1-mesa-dev:amd64 18.0.5-0ubuntu0~18.04.1 GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:224e] InstallationDate: Installed on 2018-02-07 (155 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180207) MachineType: LENOVO 20JDCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic root=UUID=150ad8bc-1d20-4de9-a767-b2b0679455f3 ro quiet splash acpi_osi= vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu3 apt 1.7.0~alpha2 SourcePackage: wayland Title: package libwayland-dev 1.15.0-2 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/pkgconfig/wayland-egl.pc', which is also in package libegl1-mesa-dev:amd64 18.0.5-0ubuntu0~18.04.1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/26/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1NET33W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20JDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1NET33W(1.20):bd10/26/2017:svnLENOVO:pn20JDCTO1WW:pvrThinkPadX1Yoga2nd:rvnLENOVO:rn20JDCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrNone: dmi.product.family: ThinkPad X1 Yoga 2nd dmi.product.name: 20JDCTO1WW dmi.product.version: ThinkPad X1 Yoga 2nd dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.92-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.3-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 versi
[Touch-packages] [Bug 1781440] Please test proposed package
Hello Till, or anyone else affected, Accepted wayland into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/wayland/1.16.0-1ubuntu1.1~18.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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1781440 Title: package libwayland-dev 1.15.0-2 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/pkgconfig/wayland-egl.pc', which is also in package libegl1-mesa-dev:amd64 18.0.5-0ubuntu0~18.04.1 Status in wayland package in Ubuntu: Fix Released Status in wayland source package in Bionic: Fix Committed Status in wayland source package in Cosmic: Fix Committed Bug description: [impact] upgrade from bionic fails if libwayland-dev & libegl1-mesa-dev was installed [test case] install libwayland-dev & libegl1-mesa-dev on bionic, upgrade to cosmic [regression potential] none, the fix only changes the version numbers in Breaks/Replaces -- Occured when upgrading from Bionic to Cosmic. ProblemType: Package DistroRelease: Ubuntu 18.10 Package: libwayland-dev 1.15.0-2 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 ApportVersion: 2.20.10-0ubuntu5 Architecture: amd64 CompositorRunning: None Date: Thu Jul 12 18:41:26 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/pkgconfig/wayland-egl.pc', which is also in package libegl1-mesa-dev:amd64 18.0.5-0ubuntu0~18.04.1 GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:224e] InstallationDate: Installed on 2018-02-07 (155 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180207) MachineType: LENOVO 20JDCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic root=UUID=150ad8bc-1d20-4de9-a767-b2b0679455f3 ro quiet splash acpi_osi= vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu3 apt 1.7.0~alpha2 SourcePackage: wayland Title: package libwayland-dev 1.15.0-2 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/pkgconfig/wayland-egl.pc', which is also in package libegl1-mesa-dev:amd64 18.0.5-0ubuntu0~18.04.1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/26/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1NET33W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20JDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1NET33W(1.20):bd10/26/2017:svnLENOVO:pn20JDCTO1WW:pvrThinkPadX1Yoga2nd:rvnLENOVO:rn20JDCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrNone: dmi.product.family: ThinkPad X1 Yoga 2nd dmi.product.name: 20JDCTO1WW dmi.product.version: ThinkPad X1 Yoga 2nd dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.92-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.3-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 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/wayla
[Touch-packages] [Bug 1757951] Re: backport from cosmic, move libwayland-egl to src:wayland
*** This bug is a duplicate of bug 1798597 *** https://bugs.launchpad.net/bugs/1798597 ** This bug has been marked a duplicate of bug 1798597 Backport packages for 18.04.2 HWE stack -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1757951 Title: backport from cosmic, move libwayland-egl to src:wayland Status in wayland package in Ubuntu: Invalid Status in wayland source package in Bionic: New Bug description: [Impact] libwayland-egl was moved from mesa to wayland in 1.15rc and got dropped from Mesa after 18.0.0. This update was planned as a FFE but it didn't quite make it before bionic release, so here we are. [Test case] [Regression potential] [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1757951/+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 1789924] Re: Missing Intel GPU pci-id's
Hello Timo, or anyone else affected, Accepted mesa into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mesa/18.2.2-0ubuntu1~18.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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: mesa (Ubuntu Bionic) Status: Confirmed => 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/1789924 Title: Missing Intel GPU pci-id's Status in libdrm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Fix Released Status in libdrm source package in Bionic: Fix Committed Status in linux source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Committed Status in xorg-server source package in Bionic: Fix Released Status in libdrm source package in Cosmic: Fix Released Status in linux source package in Cosmic: Fix Released Status in mesa source package in Cosmic: New Status in xorg-server source package in Cosmic: Fix Released Bug description: [Impact] There are some new Intel GPU pci-id's that need to be added to several places: 0x3E98 0x87C0 and to make future additions easier, add platform definitions for Whiskey Lake and Amber Lake too. [Test case] Check that the user session uses the proper driver on these systems. [Regression potential] none, these just add pci-id's and platform definitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1789924/+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 1798597] Re: Backport packages for 18.04.2 HWE stack
Hello Timo, or anyone else affected, Accepted mesa into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mesa/18.2.2-0ubuntu1~18.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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: mesa (Ubuntu Bionic) 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/1798597 Title: Backport packages for 18.04.2 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-7 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in xf86-input-wacom package in Ubuntu: Invalid Status in xorg package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in xserver-xorg-input-evdev package in Ubuntu: Invalid Status in xserver-xorg-input-joystick package in Ubuntu: Invalid Status in xserver-xorg-input-libinput package in Ubuntu: Invalid Status in xserver-xorg-input-synaptics package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu package in Ubuntu: Invalid Status in xserver-xorg-video-ati package in Ubuntu: Invalid Status in xserver-xorg-video-fbdev package in Ubuntu: Invalid Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Status in xserver-xorg-video-qxl package in Ubuntu: Invalid Status in xserver-xorg-video-vesa package in Ubuntu: Invalid Status in xserver-xorg-video-vmware package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Committed Status in libdrm source package in Bionic: Fix Committed Status in llvm-toolchain-7 source package in Bionic: Fix Committed Status in mesa source package in Bionic: Fix Committed Status in wayland source package in Bionic: Fix Committed Status in xf86-input-wacom source package in Bionic: New Status in xorg source package in Bionic: New Status in xorg-server source package in Bionic: New Status in xserver-xorg-input-evdev source package in Bionic: New Status in xserver-xorg-input-joystick source package in Bionic: New Status in xserver-xorg-input-libinput source package in Bionic: New Status in xserver-xorg-input-synaptics source package in Bionic: New Status in xserver-xorg-video-amdgpu source package in Bionic: New Status in xserver-xorg-video-ati source package in Bionic: New Status in xserver-xorg-video-fbdev source package in Bionic: New Status in xserver-xorg-video-nouveau source package in Bionic: New Status in xserver-xorg-video-qxl source package in Bionic: New Status in xserver-xorg-video-vesa source package in Bionic: New Status in xserver-xorg-video-vmware source package in Bionic: New Bug description: [Impact] These are needed for 18.04.2 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-7: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 18.2.x series, so there shouldn't be any regressions left at that point xserver: a new major release, but since it's renamed there's no real chance of regression when it hits the archive xorg drivers: same as xserver [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1798597/+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 1807023] Re: installer stock images fail to validate any HTTPS certificates (ca-certificates missing)
Hello Mauricio, or anyone else affected, Accepted debian-installer into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/debian- installer/20101020ubuntu557.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-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: debian-installer (Ubuntu Cosmic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1807023 Title: installer stock images fail to validate any HTTPS certificates (ca- certificates missing) Status in debian-installer: Unknown Status in ca-certificates package in Ubuntu: Invalid Status in debian-installer package in Ubuntu: Fix Committed Status in ca-certificates source package in Trusty: In Progress Status in debian-installer source package in Trusty: In Progress Status in ca-certificates source package in Xenial: In Progress Status in debian-installer source package in Xenial: In Progress Status in ca-certificates source package in Bionic: Invalid Status in debian-installer source package in Bionic: Fix Committed Status in ca-certificates source package in Cosmic: Invalid Status in debian-installer source package in Cosmic: Fix Committed Status in ca-certificates source package in Disco: Invalid Status in debian-installer source package in Disco: Fix Committed Status in debian-installer package in Debian: Fix Released Bug description: [Impact] * The installer stock images fail to validate any HTTPS certificates because ca-certificates is not available in the installer environment. * This causes wget/download errors for preseed files on HTTPS servers (or HTTP servers that redirect to HTTPS, which are increasingly common nowadays - e.g., GitHub) and theoretically any other files that are downloaded with d-i-utils/fetch-url/wget. * The fix is to ship ca-certificates-udeb in installer stock images. * Debian already ships ca-certificate-udeb in the stock installer images; the fix is applied since Jan 2017. (reference: Debian Bug #842040 / d-i commit 2f00c51a [1]) [Test Case] * In the installer shell: ~ # wget http://github.com # or https://github.com - FAIL if ca-certificates-udeb is missing: "ERROR: cannot verify github.com's certificate, <...>' - PASS if ca-certificates-udeb is available "Saving to: 'index.html'" * Test steps with virt-install and netboot images are provided in the comments, for each release. [Regression Potential] * Low. This just adds the ca-certificates files in /etc/ssl/certs and symlink in /usr/lib/ssl/certs, so only tools looking for that would be affected. * Apparently only wget checks for/uses those files, and the difference in behavior is download errors no longer occur. [Notes] * The ca-certificates-udeb is not currently present in the Ubuntu 'main' component, but in 'universe', despite the normal deb being in 'main'. However, when rebuilding in a PPA it goes into 'main' accordingly, and can be used by default by debian-installer (otherwise, UDEB_COMPONENTS has to be modified to include universe/d-i). * So this fix includes a no-change-rebuild for the ca-certificates package, in order to publish the udeb in the archive (at least in PPA for testing). Hopefully that can be sorted out for this fix to work out. * The ca-certificates and debian-installer builds have been done in a PPA using all architectures, and testing has been done with the amd64 images. * This fix is requested for Bionic, Cosmic, Disco at least. * The fix for Trusty and Xenial needed a little bit more work to build/ship the (new) udeb. (reference: Debian Bug #845456 / ca-certificates
[Touch-packages] [Bug 1807023] Re: installer stock images fail to validate any HTTPS certificates (ca-certificates missing)
Hello Mauricio, or anyone else affected, Accepted debian-installer into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/debian- installer/20101020ubuntu543.4 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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: debian-installer (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic ** Changed in: debian-installer (Ubuntu Disco) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1807023 Title: installer stock images fail to validate any HTTPS certificates (ca- certificates missing) Status in debian-installer: Unknown Status in ca-certificates package in Ubuntu: Invalid Status in debian-installer package in Ubuntu: Fix Committed Status in ca-certificates source package in Trusty: In Progress Status in debian-installer source package in Trusty: In Progress Status in ca-certificates source package in Xenial: In Progress Status in debian-installer source package in Xenial: In Progress Status in ca-certificates source package in Bionic: Invalid Status in debian-installer source package in Bionic: Fix Committed Status in ca-certificates source package in Cosmic: Invalid Status in debian-installer source package in Cosmic: Fix Committed Status in ca-certificates source package in Disco: Invalid Status in debian-installer source package in Disco: Fix Committed Status in debian-installer package in Debian: Fix Released Bug description: [Impact] * The installer stock images fail to validate any HTTPS certificates because ca-certificates is not available in the installer environment. * This causes wget/download errors for preseed files on HTTPS servers (or HTTP servers that redirect to HTTPS, which are increasingly common nowadays - e.g., GitHub) and theoretically any other files that are downloaded with d-i-utils/fetch-url/wget. * The fix is to ship ca-certificates-udeb in installer stock images. * Debian already ships ca-certificate-udeb in the stock installer images; the fix is applied since Jan 2017. (reference: Debian Bug #842040 / d-i commit 2f00c51a [1]) [Test Case] * In the installer shell: ~ # wget http://github.com # or https://github.com - FAIL if ca-certificates-udeb is missing: "ERROR: cannot verify github.com's certificate, <...>' - PASS if ca-certificates-udeb is available "Saving to: 'index.html'" * Test steps with virt-install and netboot images are provided in the comments, for each release. [Regression Potential] * Low. This just adds the ca-certificates files in /etc/ssl/certs and symlink in /usr/lib/ssl/certs, so only tools looking for that would be affected. * Apparently only wget checks for/uses those files, and the difference in behavior is download errors no longer occur. [Notes] * The ca-certificates-udeb is not currently present in the Ubuntu 'main' component, but in 'universe', despite the normal deb being in 'main'. However, when rebuilding in a PPA it goes into 'main' accordingly, and can be used by default by debian-installer (otherwise, UDEB_COMPONENTS has to be modified to include universe/d-i). * So this fix includes a no-change-rebuild for the ca-certificates package, in order to publish the udeb in the archive (at least in PPA for testing). Hopefully that can be sorted out for this fix to work out. * The ca-certificates and debian-installer builds have been done in a PPA using all architectures, and testing has been done with the amd64 images. * This fix is requested for Bionic, Cosmic, Disco at least. * The fix for Trusty and Xenial needed a little bit more work to build/shi
[Touch-packages] [Bug 1807448] [NEW] [SRU] Patch power9-001.diff breaks IFUNC on ELFv1
Public bug reported: [ SRU Justification ] As per comment #4 in https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1655181 the undefined weak fix should not have been backported because it breaks IFUNC on ELFv1, and can't be fixed without a much larger backport from 2.27. This patch breaks glibc builds on PPC64 ELFv1. See also https://sourceware.org/bugzilla/show_bug.cgi?id=20472 I will be pushing this upload via the ubuntu-security-proposed PPA, as this regression also exists in security and if we ever want to do a glibc security update, we need the fix there as well. [ Test Case ] See that glibc now builds on powerpc in xenial, when it didn't with the previous version. [ Regression Potential ] We lived fine without this patch before, and will do again in the future. Removing it fixes ELFv1 glibc builds (and presumably anything else that uses IFUNC), but should have no other obvious impact. ** Affects: binutils (Ubuntu) Importance: Undecided Status: Invalid ** Affects: binutils (Ubuntu Xenial) Importance: Undecided Assignee: Adam Conrad (adconrad) Status: In Progress ** Also affects: binutils (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: binutils (Ubuntu) Status: New => Invalid ** Changed in: binutils (Ubuntu Xenial) Assignee: (unassigned) => Adam Conrad (adconrad) ** Changed in: binutils (Ubuntu Xenial) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1807448 Title: [SRU] Patch power9-001.diff breaks IFUNC on ELFv1 Status in binutils package in Ubuntu: Invalid Status in binutils source package in Xenial: In Progress Bug description: [ SRU Justification ] As per comment #4 in https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1655181 the undefined weak fix should not have been backported because it breaks IFUNC on ELFv1, and can't be fixed without a much larger backport from 2.27. This patch breaks glibc builds on PPC64 ELFv1. See also https://sourceware.org/bugzilla/show_bug.cgi?id=20472 I will be pushing this upload via the ubuntu-security-proposed PPA, as this regression also exists in security and if we ever want to do a glibc security update, we need the fix there as well. [ Test Case ] See that glibc now builds on powerpc in xenial, when it didn't with the previous version. [ Regression Potential ] We lived fine without this patch before, and will do again in the future. Removing it fixes ELFv1 glibc builds (and presumably anything else that uses IFUNC), but should have no other obvious impact. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1807448/+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 1774857] Re: sort doesn't sort and uniq loses data for many non-Latin scripts on UTF-8 locales
Using the first test case, this does appear to be fixed in cosmic (glibc
2.28) and beyond, and only affect bionic (glibc 2.27), which certainly
implies either an upstream or Debian fix slipped in between the two.
I'm not sure I'll have the bandwidth to dig into it this SRU cycle, but
I'll try to look again when I can and.
--
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/1774857
Title:
sort doesn't sort and uniq loses data for many non-Latin scripts on
UTF-8 locales
Status in coreutils package in Ubuntu:
New
Status in glibc package in Ubuntu:
New
Bug description:
I’ve found out that sort doesn’t sort strings for many non-Latin
scripts at all if the locale you’re using is one of en_US.UTF-8,
fr_FR.UTF-8 or fi_FI.UTF-8 (probably others, too, but these are the
ones I have tested). For locales ”C” and ko_KR.UTF-8, things work as
expected. Here’s a test case:
Open xterm, launch sort and input some lines of Syriac, Ethiopic,
Korean, Japanese (Hiragana or Katakana, not Han) or Thai text
repeating one of the lines twice. Here’s an example in Syriac:
ܡܠܬܐ
ܒܝܬܐ
ܒܪܢܫܐ
ܡܠܬܐ
Sort produces the following:
ܡܠܬܐ
ܒܝܬܐ
ܡܠܬܐ
ܒܪܢܫܐ
Here strings are ordered only according to their length but not
characters. Even the two instances of the word ܡܠܬܐ are found on non-
adjacent lines (1 and 3). The expected sort order based on Unicode
points would be:
ܒܝܬܐ
ܒܪܢܫܐ
ܡܠܬܐ
ܡܠܬܐ
If you further pass sort’s output to uniq, it produces the following:
ܡܠܬܐ
ܒܪܢܫܐ
Here the word on line 2 ܒܝܬܐ is completely lost since, like sort, uniq
seems to consider all Syriac strings of equal length as the same.
Although this issue affects locale, I think it is not a locale issue
per se, since perl seems to handle similar cases expectedly. For
instance, the following command produces the expected result:
perl -CDS -e 'use locale; use utf8; @str = ("ܡܠܬܐ", "ܒܝܬܐ", "ܒܪܢܫܐ",
"ܡܠܬܐ"); foreach $i (sort @str) { print "$i\n"; }'
Curiously enough, codepoints in Plane 1 seem to count as two
codepoints of the basic plane, so that if you sort | uniq the
following (six codepoints of Syriac and three codepoints of
Phoenician):
ܥܠܝܟܘܢ
𐤁𐤉𐤕
you get ”ܥܠܝܟܘܢ" as the result whereas ”𐤁𐤉𐤕” is lost. This is of
course due to the UTF-8 representation of Plane 1 characters as two
surrogate characters on the basic plane.
Also curiously, LTR scripts seem to conflate with each other and RTL
scripts among themselves but not across the directionality line, so
that if you sort | uniq the following (three codepoints each in
Ethiopic, Hangul, Syriac, Hiragana and Thai):
ዘመን
스물셋
ܐܢܐ
わたし
ฟ้า
you are left with:
ܐܢܐ
ዘመን
That’s one line of Syriac and one line of Ethiopic; everything else
was lost. This issue does not seem to affect most Indic scripts
(Devanagari, Bengali, Telugu etc.) or Arabic. For CJK, things work as
expected for the main Unicode block (4E00..9FFF) but not for Extension
A (3400..4DBF, such as 㗖 or 㡘 or 㰋). For Greek, monotonic accents work
fine but all polytonic letters are conflated (αὐλὸς and αὐλῆς conflate
to αὐλῆς). For Hebrew, letters and vowel marks work fine but
cantillation marks are conflated.
Description: Ubuntu 18.04 LTS
Release: 18.04
coreutils:
Installed: 8.28-1ubuntu1
Candidate: 8.28-1ubuntu1
Version table:
*** 8.28-1ubuntu1 500
500 http://mr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: coreutils 8.28-1ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Jun 3 10:13:06 2018
InstallationDate: Installed on 2017-02-13 (474 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=fi_FI.UTF-8
SHELL=/bin/bash
SourcePackage: coreutils
UpgradeStatus: Upgraded to bionic on 2018-05-31 (2 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1774857/+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 1746995] Re: regression in 2.23-0ubuntu10: rsync in glusterfs's georeplication fails
** Bug watch added: Samba Bugzilla #6422
https://bugzilla.samba.org/show_bug.cgi?id=6422
** Also affects: glibc via
https://bugzilla.samba.org/show_bug.cgi?id=6422
Importance: Unknown
Status: Unknown
** Project changed: glibc => rsync
** Package changed: glibc (Ubuntu) => rsync (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/1746995
Title:
regression in 2.23-0ubuntu10: rsync in glusterfs's georeplication
fails
Status in rsync:
Unknown
Status in rsync package in Ubuntu:
Confirmed
Bug description:
Since somewhere in the Jan 14-18 range my glusterfs georeplication
reports Faulty. Georeplication uses rsync internally, and tracking
this this down leads to an exit code 3 out of rsync.
I have no stacktraces myself, but I found this report about the same
problem:
https://www.spinics.net/lists/gluster-users/msg33568.html
with traces:
strace rsync :
30743 23:34:47 newfstatat(3, "6737", {st_mode=S_IFDIR|0755, st_size=4096,
...}, AT_SYMLINK_NOFOLLOW) = 0
30743 23:34:47 newfstatat(3, "6741", {st_mode=S_IFDIR|0755, st_size=4096,
...}, AT_SYMLINK_NOFOLLOW) = 0
30743 23:34:47 getdents(3, /* 0 entries */, 131072) = 0
30743 23:34:47 munmap(0x7fa4feae7000, 135168) = 0
30743 23:34:47 close(3) = 0
30743 23:34:47 write(2, "rsync: getcwd(): No such file or directory (2)", 46)
= 46
30743 23:34:47 write(2, "\n", 1)= 1
30743 23:34:47 rt_sigaction(SIGUSR1, {SIG_IGN, [], SA_RESTORER,
0x7fa4fdf404b0}, NULL, 8) = 0
30743 23:34:47 rt_sigaction(SIGUSR2, {SIG_IGN, [], SA_RESTORER,
0x7fa4fdf404b0}, NULL, 8) = 0
30743 23:34:47 write(2, "rsync error: errors selecting input/output files,
dirs (code 3) at util.c(1056) [Receiver=3.1.1]", 96) = 96
30743 23:34:47 write(2, "\n", 1)= 1
30743 23:34:47 exit_group(3)= ?
30743 23:34:47 +++ exited with 3 +++
The Changelog of glibc mentions that getcwd has been changed:
* SECURITY UPDATE: Buffer underflow in realpath()
- debian/patches/any/cvs-make-getcwd-fail-if-path-is-no-absolute.diff:
Make getcwd(3) fail if it cannot obtain an absolute path
- CVE-2018-101
and downgrading glibc to (2.23-0ubuntu3) indeed fixes my
georeplication problem. 0ubuntu3 is the latest version that is
available in the repositories, other than 0ubuntu10.
To manage notifications about this bug go to:
https://bugs.launchpad.net/rsync/+bug/1746995/+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 1725333] Re: do-release-upgrade broke WSL
17.04 and 17.10 are both EOL and no further updates can or will be made there. For people still attempting to upgrade WSL, the best option is probably just to start fresh with an 18.04 WSL install. ** Changed in: bash (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: glibc (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1725333 Title: do-release-upgrade broke WSL Status in GLibC: Fix Released Status in Gnu Bash: Fix Released Status in bash package in Ubuntu: Won't Fix Status in glibc package in Ubuntu: Won't Fix Bug description: I had Ubuntu 17.04 installed in WSL and decided to upgrade it to 17.10, so I had run do-release-upgrade, as I did before to upgrade to 17.04. Everything was fine before script started upgrading packages. It's started from bash updating, and somehow there is a problem revealed that locale files is missing, and locale-gen can't be run (because of bug in WSL). I've tried to install language-pack-en as was suggested, but problem haven't resolved, any attempt to update leads to this error. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: bash 4.4-2ubuntu1.1 ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35 Uname: Linux 4.4.0-43-Microsoft x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 Date: Fri Oct 20 18:03:30 2017 Dmesg: DpkgTerminalLog: Preparing to unpack .../bash_4.4-5ubuntu1_amd64.deb ... preinst: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec >= 0' failed. dpkg: error processing archive /var/cache/apt/archives/bash_4.4-5ubuntu1_amd64.deb (--unpack): subprocess new pre-installation script was killed by signal (Aborted), core dumped DuplicateSignature: package:bash:4.4-2ubuntu1.1 Preparing to unpack .../bash_4.4-5ubuntu1_amd64.deb ... preinst: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec >= 0' failed. dpkg: error processing archive /var/cache/apt/archives/bash_4.4-5ubuntu1_amd64.deb (--unpack): subprocess new pre-installation script was killed by signal (Aborted), core dumped ErrorMessage: subprocess new pre-installation script was killed by signal (Aborted), core dumped RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4.6~17.04.1 SourcePackage: bash Title: package bash 4.4-2ubuntu1.1 failed to install/upgrade: subprocess new pre-installation script was killed by signal (Aborted), core dumped UpgradeStatus: Upgraded to artful on 2017-10-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/glibc/+bug/1725333/+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 1719004] Re: cupsd assert failure: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec >= 0' failed.
17.10 is EOL and this is fixed in 18.04 and up. ** Changed in: glibc (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1719004 Title: cupsd assert failure: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec >= 0' failed. Status in CUPS: Fix Released Status in cups package in Ubuntu: Invalid Status in glibc package in Ubuntu: Fix Released Bug description: 1. Error: Package/cups-daemon2.2.4-7 (mutilated) 2. compiz-core/tmp/apport_core_q_vnqis (corrupted) ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: cups-daemon 2.2.4-7 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AssertionMessage: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec >= 0' failed. Date: Fri Sep 22 22:16:18 2017 ExecutablePath: /usr/sbin/cupsd InstallationDate: Installed on 2017-05-27 (118 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161008) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name Papersize: a4 ProcAttrCurrent: /usr/sbin/cupsd (enforce) ProcCmdline: BOOT_IMAGE=/vmlinuz-4.13.0-11-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcEnviron: LANG=el_GR.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-11-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: cups Title: cupsd assert failure: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec >= 0' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 10/23/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0503 dmi.board.asset.tag: Default string dmi.board.name: H110M-K D3 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0503:bd10/23/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-KD3:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1719004/+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 1807023] Update Released
The verification of the Stable Release Update for debian-installer has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ca-certificates in Ubuntu.
https://bugs.launchpad.net/bugs/1807023
Title:
installer stock images fail to validate any HTTPS certificates (ca-
certificates missing)
Status in debian-installer:
Fix Released
Status in ca-certificates package in Ubuntu:
Invalid
Status in debian-installer package in Ubuntu:
Fix Released
Status in ca-certificates source package in Trusty:
Fix Committed
Status in debian-installer source package in Trusty:
Fix Committed
Status in ca-certificates source package in Xenial:
Fix Committed
Status in debian-installer source package in Xenial:
Fix Committed
Status in ca-certificates source package in Bionic:
Invalid
Status in debian-installer source package in Bionic:
Fix Released
Status in ca-certificates source package in Cosmic:
Invalid
Status in debian-installer source package in Cosmic:
Fix Committed
Status in ca-certificates source package in Disco:
Invalid
Status in debian-installer source package in Disco:
Fix Released
Status in debian-installer package in Debian:
Fix Released
Bug description:
[Impact]
* The installer stock images fail to validate any HTTPS
certificates because ca-certificates is not available
in the installer environment.
* This causes wget/download errors for preseed files on
HTTPS servers (or HTTP servers that redirect to HTTPS,
which are increasingly common nowadays - e.g., GitHub)
and theoretically any other files that are downloaded
with d-i-utils/fetch-url/wget.
* The fix is to ship ca-certificates-udeb in installer
stock images.
* Debian already ships ca-certificate-udeb in the stock
installer images; the fix is applied since Jan 2017.
(reference: Debian Bug #842040 / d-i commit 2f00c51a [1])
[Test Case]
* In the installer shell:
~ # wget http://github.com # or https://github.com
- FAIL if ca-certificates-udeb is missing:
"ERROR: cannot verify github.com's certificate, <...>'
- PASS if ca-certificates-udeb is available
"Saving to: 'index.html'"
* Test steps with virt-install and netboot images
are provided in the comments, for each release.
[Regression Potential]
* Low. This just adds the ca-certificates files in
/etc/ssl/certs and symlink in /usr/lib/ssl/certs,
so only tools looking for that would be affected.
* Apparently only wget checks for/uses those files,
and the difference in behavior is download errors
no longer occur.
[Notes]
* The ca-certificates-udeb is not currently present
in the Ubuntu 'main' component, but in 'universe',
despite the normal deb being in 'main'.
However, when rebuilding in a PPA it goes into
'main' accordingly, and can be used by default
by debian-installer (otherwise, UDEB_COMPONENTS
has to be modified to include universe/d-i).
* So this fix includes a no-change-rebuild for the
ca-certificates package, in order to publish the
udeb in the archive (at least in PPA for testing).
Hopefully that can be sorted out for this fix
to work out.
* The ca-certificates and debian-installer builds
have been done in a PPA using all architectures,
and testing has been done with the amd64 images.
* This fix is requested for Bionic, Cosmic, Disco
at least.
* The fix for Trusty and Xenial needed a little
bit more work to build/ship the (new) udeb.
(reference: Debian Bug #845456 / ca-certificates commit 3acb3a90 [2])
It would be good to have them too if at all possible.
[1]
https://salsa.debian.org/installer-team/debian-installer/commit/2f00c51a7ead982ae1cd71bee06c8416890196b6
[2]
https://salsa.debian.org/debian/ca-certificates/commit/3acb3a9042a00307ba35d10052d81cdc206c34a4
[Debugging]
For debugging purposes, one can install strace-udeb in the installer
to verify wget's stat() calls to /usr/lib/ssl/certs.
~ # anna-install strace-udeb
~ # strace -e stat wget -O- https://github.com >/dev/null
...
Resolving github.com... stat("/etc/resolv.conf", {st_mode=S_IFREG|0644,
st_size=20, ...}) = 0
140.82.118.3, 140.82.118.4
Connecting to github.com|140.82.118.3|:443... connected.
stat("/usr/lib/ssl/certs/45bfefc3.0", 0x7ffdba51b570) = -1 ENOENT (No such
file or directory)
stat("/usr/lib/ssl/certs/244b5494.0", 0x7ffdba51b570) = -1 ENOENT (No such
file or dire
[Touch-packages] [Bug 1798597] Please test proposed package
Hello Timo, or anyone else affected, Accepted xf86-input-wacom-hwe-18.04 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xf86-input-wacom- hwe-18.04/1:0.36.1-0ubuntu1~18.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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/1798597 Title: Backport packages for 18.04.2 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-7 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in xf86-input-wacom package in Ubuntu: Invalid Status in xorg package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in xserver-xorg-input-evdev package in Ubuntu: Invalid Status in xserver-xorg-input-joystick package in Ubuntu: Invalid Status in xserver-xorg-input-libinput package in Ubuntu: Invalid Status in xserver-xorg-input-synaptics package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu package in Ubuntu: Invalid Status in xserver-xorg-video-ati package in Ubuntu: Invalid Status in xserver-xorg-video-fbdev package in Ubuntu: Invalid Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Status in xserver-xorg-video-qxl package in Ubuntu: Invalid Status in xserver-xorg-video-vesa package in Ubuntu: Invalid Status in xserver-xorg-video-vmware package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Committed Status in libdrm source package in Bionic: Fix Committed Status in llvm-toolchain-7 source package in Bionic: Fix Committed Status in mesa source package in Bionic: Fix Committed Status in wayland source package in Bionic: Fix Committed Status in xf86-input-wacom source package in Bionic: New Status in xorg source package in Bionic: New Status in xorg-server source package in Bionic: New Status in xserver-xorg-input-evdev source package in Bionic: New Status in xserver-xorg-input-joystick source package in Bionic: New Status in xserver-xorg-input-libinput source package in Bionic: New Status in xserver-xorg-input-synaptics source package in Bionic: New Status in xserver-xorg-video-amdgpu source package in Bionic: New Status in xserver-xorg-video-ati source package in Bionic: New Status in xserver-xorg-video-fbdev source package in Bionic: New Status in xserver-xorg-video-nouveau source package in Bionic: New Status in xserver-xorg-video-qxl source package in Bionic: New Status in xserver-xorg-video-vesa source package in Bionic: New Status in xserver-xorg-video-vmware source package in Bionic: New Bug description: [Impact] These are needed for 18.04.2 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-7: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 18.2.x series, so there shouldn't be any regressions left at that point xserver: a new major release, but since it's renamed there's no real chance of regression when it hits the archive xorg drivers: same as xserver [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1798597/+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 1798597] Please test proposed package
Hello Timo, or anyone else affected, Accepted xserver-xorg-input-joystick-hwe-18.04 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xserver-xorg-input-joystick- hwe-18.04/1:1.6.3-1build1~18.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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/1798597 Title: Backport packages for 18.04.2 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-7 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in xf86-input-wacom package in Ubuntu: Invalid Status in xorg package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in xserver-xorg-input-evdev package in Ubuntu: Invalid Status in xserver-xorg-input-joystick package in Ubuntu: Invalid Status in xserver-xorg-input-libinput package in Ubuntu: Invalid Status in xserver-xorg-input-synaptics package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu package in Ubuntu: Invalid Status in xserver-xorg-video-ati package in Ubuntu: Invalid Status in xserver-xorg-video-fbdev package in Ubuntu: Invalid Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Status in xserver-xorg-video-qxl package in Ubuntu: Invalid Status in xserver-xorg-video-vesa package in Ubuntu: Invalid Status in xserver-xorg-video-vmware package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Committed Status in libdrm source package in Bionic: Fix Committed Status in llvm-toolchain-7 source package in Bionic: Fix Committed Status in mesa source package in Bionic: Fix Committed Status in wayland source package in Bionic: Fix Committed Status in xf86-input-wacom source package in Bionic: New Status in xorg source package in Bionic: New Status in xorg-server source package in Bionic: New Status in xserver-xorg-input-evdev source package in Bionic: New Status in xserver-xorg-input-joystick source package in Bionic: New Status in xserver-xorg-input-libinput source package in Bionic: New Status in xserver-xorg-input-synaptics source package in Bionic: New Status in xserver-xorg-video-amdgpu source package in Bionic: New Status in xserver-xorg-video-ati source package in Bionic: New Status in xserver-xorg-video-fbdev source package in Bionic: New Status in xserver-xorg-video-nouveau source package in Bionic: New Status in xserver-xorg-video-qxl source package in Bionic: New Status in xserver-xorg-video-vesa source package in Bionic: New Status in xserver-xorg-video-vmware source package in Bionic: New Bug description: [Impact] These are needed for 18.04.2 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-7: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 18.2.x series, so there shouldn't be any regressions left at that point xserver: a new major release, but since it's renamed there's no real chance of regression when it hits the archive xorg drivers: same as xserver [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1798597/+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 1798597] Please test proposed package
Hello Timo, or anyone else affected, Accepted xserver-xorg-input-evdev-hwe-18.04 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xserver-xorg-input-evdev- hwe-18.04/1:2.10.6-1~18.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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/1798597 Title: Backport packages for 18.04.2 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-7 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in xf86-input-wacom package in Ubuntu: Invalid Status in xorg package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in xserver-xorg-input-evdev package in Ubuntu: Invalid Status in xserver-xorg-input-joystick package in Ubuntu: Invalid Status in xserver-xorg-input-libinput package in Ubuntu: Invalid Status in xserver-xorg-input-synaptics package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu package in Ubuntu: Invalid Status in xserver-xorg-video-ati package in Ubuntu: Invalid Status in xserver-xorg-video-fbdev package in Ubuntu: Invalid Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Status in xserver-xorg-video-qxl package in Ubuntu: Invalid Status in xserver-xorg-video-vesa package in Ubuntu: Invalid Status in xserver-xorg-video-vmware package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Committed Status in libdrm source package in Bionic: Fix Committed Status in llvm-toolchain-7 source package in Bionic: Fix Committed Status in mesa source package in Bionic: Fix Committed Status in wayland source package in Bionic: Fix Committed Status in xf86-input-wacom source package in Bionic: New Status in xorg source package in Bionic: New Status in xorg-server source package in Bionic: New Status in xserver-xorg-input-evdev source package in Bionic: New Status in xserver-xorg-input-joystick source package in Bionic: New Status in xserver-xorg-input-libinput source package in Bionic: New Status in xserver-xorg-input-synaptics source package in Bionic: New Status in xserver-xorg-video-amdgpu source package in Bionic: New Status in xserver-xorg-video-ati source package in Bionic: New Status in xserver-xorg-video-fbdev source package in Bionic: New Status in xserver-xorg-video-nouveau source package in Bionic: New Status in xserver-xorg-video-qxl source package in Bionic: New Status in xserver-xorg-video-vesa source package in Bionic: New Status in xserver-xorg-video-vmware source package in Bionic: New Bug description: [Impact] These are needed for 18.04.2 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-7: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 18.2.x series, so there shouldn't be any regressions left at that point xserver: a new major release, but since it's renamed there's no real chance of regression when it hits the archive xorg drivers: same as xserver [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1798597/+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 1798597] Please test proposed package
Hello Timo, or anyone else affected, Accepted xserver-xorg-input-libinput-hwe-18.04 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xserver-xorg-input-libinput- hwe-18.04/0.28.1-1~18.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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/1798597 Title: Backport packages for 18.04.2 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-7 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in xf86-input-wacom-hwe-18.04 package in Ubuntu: Invalid Status in xorg package in Ubuntu: Invalid Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-evdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-joystick-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-libinput-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-synaptics-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-fbdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-nouveau-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-qxl package in Ubuntu: Invalid Status in xserver-xorg-video-vesa package in Ubuntu: Invalid Status in xserver-xorg-video-vmware package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Committed Status in libdrm source package in Bionic: Fix Committed Status in llvm-toolchain-7 source package in Bionic: Fix Committed Status in mesa source package in Bionic: Fix Committed Status in wayland source package in Bionic: Fix Committed Status in xf86-input-wacom-hwe-18.04 source package in Bionic: Fix Committed Status in xorg source package in Bionic: New Status in xorg-server-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-input-evdev-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-input-joystick-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-input-libinput-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-input-synaptics-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-fbdev-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-qxl source package in Bionic: New Status in xserver-xorg-video-vesa source package in Bionic: New Status in xserver-xorg-video-vmware source package in Bionic: New Bug description: [Impact] These are needed for 18.04.2 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-7: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 18.2.x series, so there shouldn't be any regressions left at that point xserver: a new major release, but since it's renamed there's no real chance of regression when it hits the archive xorg drivers: same as xserver [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1798597/+subscriptions -- Mailing list: https://launch
[Touch-packages] [Bug 1798597] Please test proposed package
Hello Timo, or anyone else affected, Accepted xserver-xorg-video-amdgpu-hwe-18.04 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu- hwe-18.04/18.1.0-1~18.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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Package changed: xf86-input-wacom (Ubuntu Bionic) => xf86-input- wacom-hwe-18.04 (Ubuntu Bionic) ** Changed in: xf86-input-wacom-hwe-18.04 (Ubuntu Bionic) Status: New => Fix Committed ** Package changed: xserver-xorg-input-evdev (Ubuntu Bionic) => xserver- xorg-input-evdev-hwe-18.04 (Ubuntu Bionic) ** Changed in: xserver-xorg-input-evdev-hwe-18.04 (Ubuntu Bionic) Status: New => Fix Committed ** Package changed: xserver-xorg-input-joystick (Ubuntu Bionic) => xserver-xorg-input-joystick-hwe-18.04 (Ubuntu Bionic) ** Changed in: xserver-xorg-input-joystick-hwe-18.04 (Ubuntu Bionic) Status: New => Fix Committed ** Package changed: xserver-xorg-input-libinput (Ubuntu Bionic) => xserver-xorg-input-libinput-hwe-18.04 (Ubuntu Bionic) ** Changed in: xserver-xorg-input-libinput-hwe-18.04 (Ubuntu Bionic) Status: New => Fix Committed ** Package changed: xserver-xorg-input-synaptics (Ubuntu Bionic) => xserver-xorg-input-synaptics-hwe-18.04 (Ubuntu Bionic) ** Changed in: xserver-xorg-input-synaptics-hwe-18.04 (Ubuntu Bionic) Status: New => Fix Committed ** Package changed: xorg-server (Ubuntu Bionic) => xorg-server-hwe-18.04 (Ubuntu Bionic) ** Changed in: xorg-server-hwe-18.04 (Ubuntu Bionic) Status: New => Fix Committed ** Package changed: xserver-xorg-video-amdgpu (Ubuntu Bionic) => xserver-xorg-video-amdgpu-hwe-18.04 (Ubuntu Bionic) ** Changed in: xserver-xorg-video-amdgpu-hwe-18.04 (Ubuntu Bionic) 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/1798597 Title: Backport packages for 18.04.2 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-7 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in xf86-input-wacom-hwe-18.04 package in Ubuntu: Invalid Status in xorg package in Ubuntu: Invalid Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-evdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-joystick-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-libinput-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-synaptics-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-fbdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-nouveau-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-qxl package in Ubuntu: Invalid Status in xserver-xorg-video-vesa package in Ubuntu: Invalid Status in xserver-xorg-video-vmware package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Committed Status in libdrm source package in Bionic: Fix Committed Status in llvm-toolchain-7 source package in Bionic: Fix Committed Status in mesa source package in Bionic: Fix Committed Status in wayland source package in Bionic: Fix Committed Status in xf86-input-wacom-hwe-18.04 source package in Bionic: Fix Committed Status in xorg source package in Bionic: New Status in xorg-server-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-input-evdev-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-input-joystick-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-input-libinput-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg
[Touch-packages] [Bug 1798597] Please test proposed package
Hello Timo, or anyone else affected, Accepted xserver-xorg-input-synaptics-hwe-18.04 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics- hwe-18.04/1.9.1-1ubuntu1~18.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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/1798597 Title: Backport packages for 18.04.2 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-7 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in xf86-input-wacom-hwe-18.04 package in Ubuntu: Invalid Status in xorg package in Ubuntu: Invalid Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-evdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-joystick-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-libinput-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-synaptics-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-fbdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-nouveau-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-qxl package in Ubuntu: Invalid Status in xserver-xorg-video-vesa package in Ubuntu: Invalid Status in xserver-xorg-video-vmware package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Committed Status in libdrm source package in Bionic: Fix Committed Status in llvm-toolchain-7 source package in Bionic: Fix Committed Status in mesa source package in Bionic: Fix Committed Status in wayland source package in Bionic: Fix Committed Status in xf86-input-wacom-hwe-18.04 source package in Bionic: Fix Committed Status in xorg source package in Bionic: New Status in xorg-server-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-input-evdev-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-input-joystick-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-input-libinput-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-input-synaptics-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-fbdev-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-qxl source package in Bionic: New Status in xserver-xorg-video-vesa source package in Bionic: New Status in xserver-xorg-video-vmware source package in Bionic: New Bug description: [Impact] These are needed for 18.04.2 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-7: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 18.2.x series, so there shouldn't be any regressions left at that point xserver: a new major release, but since it's renamed there's no real chance of regression when it hits the archive xorg drivers: same as xserver [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1798597/+subscriptions -- Mailing list: https:
[Touch-packages] [Bug 1798597] Please test proposed package
Hello Timo, or anyone else affected, Accepted xserver-xorg-video-ati-hwe-18.04 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xserver-xorg-video-ati- hwe-18.04/1:18.1.0-1~18.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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Package changed: xserver-xorg-video-ati (Ubuntu Bionic) => xserver- xorg-video-ati-hwe-18.04 (Ubuntu Bionic) ** Changed in: xserver-xorg-video-ati-hwe-18.04 (Ubuntu Bionic) 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/1798597 Title: Backport packages for 18.04.2 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-7 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in xf86-input-wacom-hwe-18.04 package in Ubuntu: Invalid Status in xorg package in Ubuntu: Invalid Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-evdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-joystick-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-libinput-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-synaptics-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-fbdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-nouveau-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-qxl-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vesa-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vmware-hwe-18.04 package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Committed Status in libdrm source package in Bionic: Fix Committed Status in llvm-toolchain-7 source package in Bionic: Fix Committed Status in mesa source package in Bionic: Fix Committed Status in wayland source package in Bionic: Fix Committed Status in xf86-input-wacom-hwe-18.04 source package in Bionic: Fix Committed Status in xorg source package in Bionic: New Status in xorg-server-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-input-evdev-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-input-joystick-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-input-libinput-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-input-synaptics-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-fbdev-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-qxl-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-vesa-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-vmware-hwe-18.04 source package in Bionic: Fix Committed Bug description: [Impact] These are needed for 18.04.2 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-7: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 18.2.x series, so there shouldn't be any regressions left at that point xserver: a new major release,
[Touch-packages] [Bug 1798597] Please test proposed package
Hello Timo, or anyone else affected, Accepted xserver-xorg-video-vesa-hwe-18.04 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xserver-xorg-video-vesa- hwe-18.04/1:2.4.0-1~18.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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Package changed: xserver-xorg-video-vesa (Ubuntu Bionic) => xserver- xorg-video-vesa-hwe-18.04 (Ubuntu Bionic) ** Changed in: xserver-xorg-video-vesa-hwe-18.04 (Ubuntu Bionic) 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/1798597 Title: Backport packages for 18.04.2 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-7 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in xf86-input-wacom-hwe-18.04 package in Ubuntu: Invalid Status in xorg package in Ubuntu: Invalid Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-evdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-joystick-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-libinput-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-synaptics-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-fbdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-nouveau-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-qxl-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vesa-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vmware-hwe-18.04 package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Committed Status in libdrm source package in Bionic: Fix Committed Status in llvm-toolchain-7 source package in Bionic: Fix Committed Status in mesa source package in Bionic: Fix Committed Status in wayland source package in Bionic: Fix Committed Status in xf86-input-wacom-hwe-18.04 source package in Bionic: Fix Committed Status in xorg source package in Bionic: New Status in xorg-server-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-input-evdev-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-input-joystick-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-input-libinput-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-input-synaptics-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-fbdev-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-qxl-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-vesa-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-vmware-hwe-18.04 source package in Bionic: Fix Committed Bug description: [Impact] These are needed for 18.04.2 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-7: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 18.2.x series, so there shouldn't be any regressions left at that point xserver: a new major relea
[Touch-packages] [Bug 1798597] Please test proposed package
Hello Timo, or anyone else affected, Accepted xserver-xorg-video-nouveau-hwe-18.04 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau- hwe-18.04/1:1.0.15-3~18.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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Package changed: xserver-xorg-video-nouveau (Ubuntu Bionic) => xserver-xorg-video-nouveau-hwe-18.04 (Ubuntu Bionic) ** Changed in: xserver-xorg-video-nouveau-hwe-18.04 (Ubuntu Bionic) 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/1798597 Title: Backport packages for 18.04.2 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-7 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in xf86-input-wacom-hwe-18.04 package in Ubuntu: Invalid Status in xorg package in Ubuntu: Invalid Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-evdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-joystick-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-libinput-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-synaptics-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-fbdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-nouveau-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-qxl-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vesa-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vmware-hwe-18.04 package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Committed Status in libdrm source package in Bionic: Fix Committed Status in llvm-toolchain-7 source package in Bionic: Fix Committed Status in mesa source package in Bionic: Fix Committed Status in wayland source package in Bionic: Fix Committed Status in xf86-input-wacom-hwe-18.04 source package in Bionic: Fix Committed Status in xorg source package in Bionic: New Status in xorg-server-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-input-evdev-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-input-joystick-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-input-libinput-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-input-synaptics-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-fbdev-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-qxl-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-vesa-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-vmware-hwe-18.04 source package in Bionic: Fix Committed Bug description: [Impact] These are needed for 18.04.2 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-7: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 18.2.x series, so there shouldn't be any regressions left at that point xserver: a
[Touch-packages] [Bug 1798597] Please test proposed package
Hello Timo, or anyone else affected, Accepted xserver-xorg-video-fbdev-hwe-18.04 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xserver-xorg-video-fbdev- hwe-18.04/1:0.5.0-1ubuntu1~18.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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Package changed: xserver-xorg-video-fbdev (Ubuntu Bionic) => xserver- xorg-video-fbdev-hwe-18.04 (Ubuntu Bionic) ** Changed in: xserver-xorg-video-fbdev-hwe-18.04 (Ubuntu Bionic) 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/1798597 Title: Backport packages for 18.04.2 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-7 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in xf86-input-wacom-hwe-18.04 package in Ubuntu: Invalid Status in xorg package in Ubuntu: Invalid Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-evdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-joystick-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-libinput-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-synaptics-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-fbdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-nouveau-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-qxl-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vesa-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vmware-hwe-18.04 package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Committed Status in libdrm source package in Bionic: Fix Committed Status in llvm-toolchain-7 source package in Bionic: Fix Committed Status in mesa source package in Bionic: Fix Committed Status in wayland source package in Bionic: Fix Committed Status in xf86-input-wacom-hwe-18.04 source package in Bionic: Fix Committed Status in xorg source package in Bionic: New Status in xorg-server-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-input-evdev-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-input-joystick-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-input-libinput-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-input-synaptics-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-fbdev-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-qxl-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-vesa-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-vmware-hwe-18.04 source package in Bionic: Fix Committed Bug description: [Impact] These are needed for 18.04.2 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-7: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 18.2.x series, so there shouldn't be any regressions left at that point xserver: a new
[Touch-packages] [Bug 1798597] Please test proposed package
Hello Timo, or anyone else affected, Accepted xserver-xorg-video-qxl-hwe-18.04 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xserver-xorg-video-qxl- hwe-18.04/0.1.5-2build2~18.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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Package changed: xserver-xorg-video-qxl (Ubuntu Bionic) => xserver- xorg-video-qxl-hwe-18.04 (Ubuntu Bionic) ** Changed in: xserver-xorg-video-qxl-hwe-18.04 (Ubuntu Bionic) 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/1798597 Title: Backport packages for 18.04.2 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-7 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in xf86-input-wacom-hwe-18.04 package in Ubuntu: Invalid Status in xorg package in Ubuntu: Invalid Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-evdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-joystick-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-libinput-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-synaptics-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-fbdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-nouveau-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-qxl-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vesa-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vmware-hwe-18.04 package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Committed Status in libdrm source package in Bionic: Fix Committed Status in llvm-toolchain-7 source package in Bionic: Fix Committed Status in mesa source package in Bionic: Fix Committed Status in wayland source package in Bionic: Fix Committed Status in xf86-input-wacom-hwe-18.04 source package in Bionic: Fix Committed Status in xorg source package in Bionic: New Status in xorg-server-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-input-evdev-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-input-joystick-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-input-libinput-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-input-synaptics-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-fbdev-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-qxl-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-vesa-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-vmware-hwe-18.04 source package in Bionic: Fix Committed Bug description: [Impact] These are needed for 18.04.2 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-7: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 18.2.x series, so there shouldn't be any regressions left at that point xserver: a new major releas
[Touch-packages] [Bug 1798597] Please test proposed package
Hello Timo, or anyone else affected, Accepted xserver-xorg-video-vmware-hwe-18.04 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xserver-xorg-video-vmware- hwe-18.04/1:13.3.0-2build1~18.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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Package changed: xserver-xorg-video-vmware (Ubuntu Bionic) => xserver-xorg-video-vmware-hwe-18.04 (Ubuntu Bionic) ** Changed in: xserver-xorg-video-vmware-hwe-18.04 (Ubuntu Bionic) Status: New => Fix Committed -- 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/1798597 Title: Backport packages for 18.04.2 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-7 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in xf86-input-wacom-hwe-18.04 package in Ubuntu: Invalid Status in xorg package in Ubuntu: Invalid Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-evdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-joystick-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-libinput-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-synaptics-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-fbdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-nouveau-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-qxl-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vesa-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vmware-hwe-18.04 package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Committed Status in libdrm source package in Bionic: Fix Committed Status in llvm-toolchain-7 source package in Bionic: Fix Committed Status in mesa source package in Bionic: Fix Committed Status in wayland source package in Bionic: Fix Committed Status in xf86-input-wacom-hwe-18.04 source package in Bionic: Fix Committed Status in xorg source package in Bionic: New Status in xorg-server-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-input-evdev-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-input-joystick-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-input-libinput-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-input-synaptics-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-fbdev-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-qxl-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-vesa-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-vmware-hwe-18.04 source package in Bionic: Fix Committed Bug description: [Impact] These are needed for 18.04.2 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-7: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 18.2.x series, so there shouldn't be any regressions left at that point xserver: a n
[Touch-packages] [Bug 1798597] Please test proposed package
Hello Timo, or anyone else affected, Accepted xserver-xorg-video-dummy-hwe-18.04 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xserver-xorg-video-dummy- hwe-18.04/1:0.3.8-1build3~18.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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Also affects: xserver-xorg-video-dummy-hwe-18.04 (Ubuntu) Importance: Undecided Status: New ** Changed in: xserver-xorg-video-dummy-hwe-18.04 (Ubuntu) Status: New => Invalid ** Changed in: xserver-xorg-video-dummy-hwe-18.04 (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: xserver-xorg-video-dummy-hwe-18.04 (Ubuntu Bionic) Assignee: (unassigned) => Timo Aaltonen (tjaalton) -- 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/1798597 Title: Backport packages for 18.04.2 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-7 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in xf86-input-wacom-hwe-18.04 package in Ubuntu: Invalid Status in xorg package in Ubuntu: Invalid Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-evdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-joystick-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-libinput-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-synaptics-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-dummy-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-fbdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-nouveau-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-qxl-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vesa-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vmware-hwe-18.04 package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Committed Status in libdrm source package in Bionic: Fix Committed Status in llvm-toolchain-7 source package in Bionic: Fix Committed Status in mesa source package in Bionic: Fix Committed Status in wayland source package in Bionic: Fix Committed Status in xf86-input-wacom-hwe-18.04 source package in Bionic: Fix Committed Status in xorg source package in Bionic: New Status in xorg-server-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-input-evdev-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-input-joystick-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-input-libinput-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-input-synaptics-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-dummy-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-fbdev-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-qxl-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-vesa-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-vmware-hwe-18.04 source package in Bionic: Fix Committed Bug description: [Impact] These are needed for 18.04.2 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic.
[Touch-packages] [Bug 1798597] Please test proposed package
Hello Timo, or anyone else affected, Accepted xorg-hwe-18.04 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xorg- hwe-18.04/1:7.7+19ubuntu8~18.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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Package changed: xorg (Ubuntu Bionic) => xorg-hwe-18.04 (Ubuntu Bionic) ** Changed in: xorg-hwe-18.04 (Ubuntu Bionic) Status: New => Fix Committed -- 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/1798597 Title: Backport packages for 18.04.2 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-7 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in xf86-input-wacom-hwe-18.04 package in Ubuntu: Invalid Status in xorg-hwe-18.04 package in Ubuntu: Invalid Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-evdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-joystick-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-libinput-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-synaptics-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-dummy-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-fbdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-nouveau-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-qxl-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vesa-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vmware-hwe-18.04 package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Committed Status in libdrm source package in Bionic: Fix Committed Status in llvm-toolchain-7 source package in Bionic: Fix Committed Status in mesa source package in Bionic: Fix Committed Status in wayland source package in Bionic: Fix Committed Status in xf86-input-wacom-hwe-18.04 source package in Bionic: Fix Committed Status in xorg-hwe-18.04 source package in Bionic: Fix Committed Status in xorg-server-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-input-evdev-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-input-joystick-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-input-libinput-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-input-synaptics-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-dummy-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-fbdev-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-qxl-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-vesa-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-vmware-hwe-18.04 source package in Bionic: Fix Committed Bug description: [Impact] These are needed for 18.04.2 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-7: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 18.2
[Touch-packages] [Bug 1754671] Re: Full-tunnel VPN DNS leakage regression
The original bug report was about a regression in 16.04 with the dnsmasq integration. While I'm glad this got the ball rolling on the bionic networkd integration, let's not forget that we broke xenial? Added a xenial task for network-manager accordingly. ** Also affects: network-manager (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Xenial) Status: New => Invalid -- 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/1754671 Title: Full-tunnel VPN DNS leakage regression Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in network-manager source package in Xenial: New Status in systemd source package in Xenial: Invalid Status in network-manager source package in Bionic: Fix Released Status in systemd source package in Bionic: Triaged Bug description: [Impact] When using a VPN the DNS requests might still be sent to a DNS server outside the VPN when they should not [Test case] 1) Set up a VPN with split tunneling: a) Configure VPN normally (set up remote host, any ports and options needed for the VPN to work) b) Under the IPv4 tab: enable "Use this connection only for the resources on its network". c) Under the IPv6 tab: enable "Use this connection only for the resources on its network". 2) Connect to the VPN. 3) Run 'systemd-resolve --status'; note the DNS servers configured: a) For the VPN; under a separate link (probably tun0), note down the IP of the DNS server(s). Also note the name of the interface (link). b) For the "main" connection; under the link for your ethernet or wireless devices (wl*, en*, whatever it may be), note down the IP of the DNS server(s). Also note the name of the interface (link). 4) In a separate terminal, run 'sudo tcpdump -ni port 53'; let it run. 5) In a separate terminal, run 'sudo tcpdump -ni port 53'; let it run. 6) In yet another terminal, issue name resolution requests using dig: a) For a name known to be reachable via the public network: 'dig www.yahoo.com' b) For a name known to be reachable only via the VPN: 'dig ' 7) Check the output of each terminal running tcpdump. When requesting the public name, traffic can go through either. When requesting the "private" name (behind the VPN), traffic should only be going through the interface for the VPN. Additionally, ensure the IP receiving the requests for the VPN name is indeed the IP address noted above for the VPN's DNS server. If you see no traffic showing in tcpdump output when requesting a name, it may be because it is cached by systemd-resolved. Use a different name you have not tried before. [Regression potential] The code change the handling of DNS servers when using a VPN, we should check that name resolution still work whne using a VPN in different configurations - In 16.04 the NetworkManager package used to carry this patch: http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch It fixed the DNS setup so that when I'm on the VPN, I am not sending unencrypted DNS queries to the (potentially hostile) local nameservers. This patch disappeared in an update. I think it was present in 1.2.2-0ubuntu0.16.04.4 but was dropped some time later. This security bug exists upstream too: https://bugzilla.gnome.org/show_bug.cgi?id=746422 It's not a *regression* there though, as they didn't fix it yet (unfortunately!) To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1754671/+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 1824111] Re: Backport packages for 18.04.3 HWE stack
Hello Timo, or anyone else affected, Accepted xorg-server-hwe-18.04 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xorg- server-hwe-18.04/2:1.20.4-1ubuntu3~18.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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: xorg-server-hwe-18.04 (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1824111 Title: Backport packages for 18.04.3 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-8 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-nouveau-hwe-18.04 package in Ubuntu: New Status in libclc source package in Bionic: Fix Committed Status in libdrm source package in Bionic: Fix Committed Status in llvm-toolchain-8 source package in Bionic: Fix Committed Status in mesa source package in Bionic: Fix Committed Status in xorg-server-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: New Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: New Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic: New Bug description: [Impact] These are needed for 18.04.3 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-8: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 19.0.x series, so there shouldn't be any regressions left at that point xserver: a new minor release xorg drivers: modest updates, mainly just new ati/amdgpu [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1824111/+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 1824111] Re: Backport packages for 18.04.3 HWE stack
Hello Timo, or anyone else affected, Accepted xserver-xorg-video-amdgpu-hwe-18.04 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu- hwe-18.04/19.0.1-1~18.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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: xserver-xorg-video-amdgpu-hwe-18.04 (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: xserver-xorg-video-ati-hwe-18.04 (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1824111 Title: Backport packages for 18.04.3 HWE stack Status in OEM Priority Project: Confirmed Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-8 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Committed Status in libdrm source package in Bionic: Fix Committed Status in llvm-toolchain-8 source package in Bionic: Fix Committed Status in mesa source package in Bionic: Fix Committed Status in xorg-server-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic: Fix Committed Bug description: [Impact] These are needed for 18.04.3 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-8: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 19.0.x series, so there shouldn't be any regressions left at that point xserver: a new minor release xorg drivers: modest updates, mainly just new ati/amdgpu [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1824111/+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 1824111] Please test proposed package
Hello Timo, or anyone else affected, Accepted xserver-xorg-video-nouveau-hwe-18.04 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau- hwe-18.04/1:1.0.16-1~18.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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1824111 Title: Backport packages for 18.04.3 HWE stack Status in OEM Priority Project: Confirmed Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-8 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Committed Status in libdrm source package in Bionic: Fix Committed Status in llvm-toolchain-8 source package in Bionic: Fix Committed Status in mesa source package in Bionic: Fix Committed Status in xorg-server-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic: Fix Committed Bug description: [Impact] These are needed for 18.04.3 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-8: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 19.0.x series, so there shouldn't be any regressions left at that point xserver: a new minor release xorg drivers: modest updates, mainly just new ati/amdgpu [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1824111/+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 1824111] Please test proposed package
Hello Timo, or anyone else affected, Accepted xserver-xorg-video-ati-hwe-18.04 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xserver-xorg-video-ati- hwe-18.04/1:19.0.1-0ubuntu1~18.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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: xserver-xorg-video-nouveau-hwe-18.04 (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1824111 Title: Backport packages for 18.04.3 HWE stack Status in OEM Priority Project: Confirmed Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-8 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Committed Status in libdrm source package in Bionic: Fix Committed Status in llvm-toolchain-8 source package in Bionic: Fix Committed Status in mesa source package in Bionic: Fix Committed Status in xorg-server-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic: Fix Committed Bug description: [Impact] These are needed for 18.04.3 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-8: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 19.0.x series, so there shouldn't be any regressions left at that point xserver: a new minor release xorg drivers: modest updates, mainly just new ati/amdgpu [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1824111/+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 1831498] Re: radeonsi: GTK elements become invisible in some applications (GIMP, LibreOffice)
Hello Timo, or anyone else affected, Accepted mesa into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mesa/19.0.2-1ubuntu1.1~18.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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: mesa (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1831498 Title: radeonsi: GTK elements become invisible in some applications (GIMP, LibreOffice) Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Bionic: Fix Committed Status in mesa source package in Disco: Fix Committed Bug description: [impact] imported from https://bugs.freedesktop.org/show_bug.cgi?id=110355 : "I am currently experiencing some issues with GTK elements (GtkMenuItem, GtkMenu) becoming invisible with GIMP and LibreOffice. I am currently using radeonsi+glamor and I'm on Arch Linux (x86_64). My hardware is a Ryzen 5 2400G APU with vega graphics." [test case] test that GIMP/Libreoffice work fine on AMD Vega/Raven [regression potential] the fix/workaround is already in mesa 19.0.4, shouldn't regress anything To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1831498/+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 1824111] Please test proposed package
Hello Timo, or anyone else affected, Accepted mesa into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mesa/19.0.2-1ubuntu1.1~18.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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1824111 Title: Backport packages for 18.04.3 HWE stack Status in OEM Priority Project: Confirmed Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-8 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Committed Status in libdrm source package in Bionic: Fix Committed Status in llvm-toolchain-8 source package in Bionic: Fix Committed Status in mesa source package in Bionic: Fix Committed Status in xorg-server-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic: Fix Committed Bug description: [Impact] These are needed for 18.04.3 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-8: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 19.0.x series, so there shouldn't be any regressions left at that point xserver: a new minor release xorg drivers: modest updates, mainly just new ati/amdgpu [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1824111/+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 1842284] Re: initramfs does not copy ehci-platform
What kernel is it that includes an ehci-platform driver? I'm not seeing it in linux or linux-hwe in xenial. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1842284 Title: initramfs does not copy ehci-platform Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Xenial: In Progress Status in initramfs-tools source package in Bionic: Fix Released Status in initramfs-tools source package in Disco: Fix Released Status in initramfs-tools source package in Eoan: Fix Released Bug description: [Impact] If you install Ubuntu onto USB storage behind a Platform USB host controller, it will not be able to boot because the generated initramfs will not include the host controller driver. [Test Case] Install to a USB stick attached to platform USB controller and reboot. Booting will fail because it will be unable to find the root file system. [Regression Risk] Driver is only loaded when system requires ehci-platform, minimizing the impact to all other systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1842284/+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 1842284] Re: initramfs does not copy ehci-platform
Hello Ike, or anyone else affected, Accepted initramfs-tools into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/initramfs- tools/0.122ubuntu8.15 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, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: initramfs-tools (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1842284 Title: initramfs does not copy ehci-platform Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Xenial: Fix Committed Status in initramfs-tools source package in Bionic: Fix Released Status in initramfs-tools source package in Disco: Fix Released Status in initramfs-tools source package in Eoan: Fix Released Bug description: [Impact] If you install Ubuntu onto USB storage behind a Platform USB host controller, it will not be able to boot because the generated initramfs will not include the host controller driver. [Test Case] Install to a USB stick attached to platform USB controller and reboot. Booting will fail because it will be unable to find the root file system. [Regression Risk] Driver is only loaded when system requires ehci-platform, minimizing the impact to all other systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1842284/+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 1844524] Re: text relocation of grep prevents its use under udevd
Hello Thadeu, or anyone else affected, Accepted grep into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/grep/3.1-2build1 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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: grep (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1844524 Title: text relocation of grep prevents its use under udevd Status in grep package in Ubuntu: Invalid Status in grep source package in Bionic: Fix Committed Bug description: [Impact] grep can't be used under udev, preventing kdump-tools to be used after a memory hotplug. [Test case] Run grep with systemd-run -t --property MemoryDenyWriteExecute=yes /bin/grep crashkernel /proc/cmdline [Regression potential] The fix is a simple rebuild, so should have minimal potential for regression. - # systemd-run -t --property MemoryDenyWriteExecute=yes /bin/grep crashkernel /proc/cmdline Running as unit: run-u54.service Press ^] three times within 1s to disconnect TTY. /bin/grep: error while loading shared libraries: cannot restore segment prot after reloc: Operation not permitted # Under ppc64el, grep can't be used under udev, because it restricts mapping to be Write+Execute, with MemoryDenyWriteExecute=yes. A rebuild of grep under bionic fixes the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1844524/+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 1830495] Re: tzdata noninteractive mode is being ignored
I can't reproduce this locally. See below. Is there anything extra special about this environment? (bionic-amd64)root@nosferatu:~# debconf-show debconf * debconf/frontend: Readline debconf-apt-progress/title: debconf-apt-progress/media-change: debconf-apt-progress/info: debconf-apt-progress/preparing: * debconf/priority: high (bionic-amd64)root@nosferatu:~# apt-get purge tzdata && rm /etc/timezone [...] Purging configuration files for tzdata (2019b-0ubuntu0.18.04) ... (bionic-amd64)root@nosferatu:~# apt-get install tzdata Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: tzdata 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/190 kB of archives. After this operation, 3106 kB of additional disk space will be used. Preconfiguring packages ... Configuring tzdata -- Please select the geographic area in which you live. Subsequent configuration questions will narrow this down by presenting a list of cities, representing the time zones in which they are located. 1. Africa 3. Antarctica 5. Arctic 7. Atlantic 9. Indian11. SystemV 13. Etc 2. America 4. Australia 6. Asia8. Europe10. Pacific 12. US Geographic area: [...] (bionic-amd64)root@nosferatu:~# apt-get purge tzdata && rm /etc/timezone [...] Purging configuration files for tzdata (2019b-0ubuntu0.18.04) ... (bionic-amd64)root@nosferatu:~# DEBIAN_FRONTEND=noninteractive apt-get install tzdata Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: tzdata 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/190 kB of archives. After this operation, 3106 kB of additional disk space will be used. Preconfiguring packages ... Selecting previously unselected package tzdata. (Reading database ... 10885 files and directories currently installed.) Preparing to unpack .../tzdata_2019b-0ubuntu0.18.04_all.deb ... Unpacking tzdata (2019b-0ubuntu0.18.04) ... Setting up tzdata (2019b-0ubuntu0.18.04) ... Current default time zone: 'Etc/UTC' Local time is now: Fri Sep 20 09:20:00 UTC 2019. Universal Time is now: Fri Sep 20 09:20:00 UTC 2019. Run 'dpkg-reconfigure tzdata' if you wish to change it. (bionic-amd64)root@nosferatu:~# ** Changed in: tzdata (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1830495 Title: tzdata noninteractive mode is being ignored Status in tzdata package in Ubuntu: Incomplete Bug description: This bug is related to Bug #1773687 I am trying to automate the build of an AMI with a package that requires tzdata. I am blocked from automation because tzdata will not install non-interactively. This is despite setting DEBIAN_FRONTEND=noninteractive. Here is an interactive session that shows the same problem. ``` ubuntu@ip-172-31-95-248:~$ env LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=00:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arc=01;31:*.arj=01;31:*.taz=01;31:*.lha=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.tzo=01;31:*.t7z=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.dz=01;31:*.gz=01;31:*.lrz=01;31:*.lz=01;31:*.lzo=01;31:*.xz=01;31:*.zst=01;31:*.tzst=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.alz=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.cab=01;31:*.wim=01;31:*.swm=01;31:*.dwm=01;31:*.esd=01;31:*.jpg=01;35:*.jpeg=01;35:*.mjpg=01;35:*.mjpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.m4a=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.oga=00;36:*.opus=00;36:*.spx=00;36:*.xspf=00;36: SSH_CONNECTION=172.58.185.180 50092 172.31.95.248 22 LANG=C.UTF-8 XDG_SESSION_ID=3 USER=ubuntu PWD=/home/ubuntu HOME=/home/ubuntu SSH_CLIENT=172.58.185.180 50092 22 XDG_DATA_DIRS=/usr/local/share:/usr/share:/var/lib/snapd/desktop DEBIAN_FRONTEND=noninteractive SSH_TTY=/dev/pts/0 MAIL=/var/mail/ubuntu TERM=xterm-256col
[Touch-packages] [Bug 964438] Re: The hour did not go forward today when it should have (UK)
Looks like this bug got lost long ago, as did the system it was reported from. That said, the original bug claimed it was "GMT", which is a timezone that doesn't do daylight savings time, so likely the fix was "use Europe/London" or similar. ** Changed in: tzdata (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/964438 Title: The hour did not go forward today when it should have (UK) Status in tzdata package in Ubuntu: Invalid Bug description: I'm in the GMT timezone and the time should be 10:45 but it's 9:45 on my Ubuntu system. This means all OCSP responses are invalid: The OCSP response is not yet valid (contains a date in the future). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: tzdata 2012b-1 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Sun Mar 25 09:41:46 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120201.1) PackageArchitecture: all SourcePackage: tzdata UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/964438/+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 1042547] Re: Debconf/Log.pm
This bug reported against precise (and almost certainly the wrong package) isn't obviously reproducible in current supported releases. ** Changed in: tzdata (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1042547 Title: Debconf/Log.pm Status in tzdata package in Ubuntu: Won't Fix Bug description: Good day. I can't update my system(ubuntu 12.04) becouse i recieve that message "Can't locate Debconf/Log.pm in @INC"... but my @INC contain that package. What can I do? Thanks. ___ With best regards Tigran Hovhannisyan. ProblemType: Package DistroRelease: Ubuntu 12.04 Package: tzdata 2012e-0ubuntu0.12.04 ProcVersionSignature: Ubuntu 3.2.0-29.46-generic-pae 3.2.24 Uname: Linux 3.2.0-29-generic-pae i686 ApportVersion: 2.0.1-0ubuntu12 Architecture: i386 Date: Tue Aug 28 09:56:57 2012 DpkgTerminalLog: Setting up tzdata (2012e-0ubuntu0.12.04) ... Can't locate Debconf/Db.pm in @INC (@INC contains: /usr/local/lib/perl5/site_perl/5.16.0/i686-linux /usr/local/lib/perl5/site_perl/5.16.0 /usr/local/lib/perl5/5.16.0/i686-linux /usr/local/lib/perl5/5.16.0 .) at /usr/share/debconf/frontend line 6. BEGIN failed--compilation aborted at /usr/share/debconf/frontend line 6. dpkg: error processing tzdata (--configure): subprocess installed post-installation script returned error exit status 2 DuplicateSignature: Setting up tzdata (2012e-0ubuntu0.12.04) ... Can't locate Debconf/Db.pm in @INC (@INC contains: /usr/local/lib/perl5/site_perl/5.16.0/i686-linux /usr/local/lib/perl5/site_perl/5.16.0 /usr/local/lib/perl5/5.16.0/i686-linux /usr/local/lib/perl5/5.16.0 .) at /usr/share/debconf/frontend line 6. BEGIN failed--compilation aborted at /usr/share/debconf/frontend line 6. dpkg: error processing tzdata (--configure): subprocess installed post-installation script returned error exit status 2 ErrorMessage: subprocess installed post-installation script returned error exit status 2 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) PackageArchitecture: all SourcePackage: tzdata Title: package tzdata 2012e-0ubuntu0.12.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1042547/+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 828538] Re: Europe/Moscow not updated
** Changed in: tzdata (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/828538 Title: Europe/Moscow not updated Status in tzdata package in Ubuntu: Fix Released Bug description: Please, update zone Russia (Europe/Moscow, etc) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/828538/+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 1844132] Re: FFe: Mesa 19.2.0
1) Are you confident that you'll get enough testing to find any meaningful regressions, and have enough time to fix them before release? 2) Is there an upstream point release planned by October, or does their slip mean we'll see .1 as an SRU a month post-release? I'm a tentative +1 on this anyway just for the Ice Lake and Navi support, which we'll also want for the next bionic point release, but better answers to the above would help me be sure. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1844132 Title: FFe: Mesa 19.2.0 Status in mesa package in Ubuntu: Confirmed Status in mesa source package in Eoan: Confirmed Bug description: It would be great to get 19.2.0 in eoan, though it's release cycle has slipped. It's working fine on a typical desktop use here on i915 (Kaby Lake). It would also migrate to llvm-9. It is currently at rc3, and final version is expected to arrive next week (week 39). New features: Full support for Intel Ice Lake Support for AMD Navi GL_ARB_post_depth_coverage on radeonsi (Navi) GL_ARB_seamless_cubemap_per_texture on etnaviv (if GPU supports SEAMLESS_CUBE_MAP) GL_EXT_shader_image_load_store on radeonsi (with LLVM >= 10) GL_EXT_shader_samples_identical on iris and radeonsi (if using NIR) GL_EXT_texture_shadow_lod on i965, iris EGL_EXT_platform_device VK_AMD_buffer_marker on radv VK_EXT_index_type_uint8 on radv VK_EXT_post_depth_coverage on radv VK_EXT_queue_family_foreign on radv VK_EXT_sample_locations on radv VK_EXT_shader_demote_to_helper_invocation on Intel. VK_KHR_depth_stencil_resolve on radv VK_KHR_imageless_framebuffer on radv VK_KHR_shader_atomic_int64 on radv VK_KHR_uniform_buffer_standard_layout on radv (note: iris is the new DRI driver for newer Intel, not enabled by default yet) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1844132/+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 1844132] Re: FFe: Mesa 19.2.0
Mmkay, based on the above, I say go for it. It'll miss beta (unless we have reason to respin, I guess), but such is life. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1844132 Title: FFe: Mesa 19.2.0 Status in mesa package in Ubuntu: Confirmed Status in mesa source package in Eoan: Confirmed Bug description: It would be great to get 19.2.0 in eoan, though it's release cycle has slipped. It's working fine on a typical desktop use here on i915 (Kaby Lake). It would also migrate to llvm-9. It is currently at rc3, and final version is expected to arrive next week (week 39). New features: Full support for Intel Ice Lake Support for AMD Navi GL_ARB_post_depth_coverage on radeonsi (Navi) GL_ARB_seamless_cubemap_per_texture on etnaviv (if GPU supports SEAMLESS_CUBE_MAP) GL_EXT_shader_image_load_store on radeonsi (with LLVM >= 10) GL_EXT_shader_samples_identical on iris and radeonsi (if using NIR) GL_EXT_texture_shadow_lod on i965, iris EGL_EXT_platform_device VK_AMD_buffer_marker on radv VK_EXT_index_type_uint8 on radv VK_EXT_post_depth_coverage on radv VK_EXT_queue_family_foreign on radv VK_EXT_sample_locations on radv VK_EXT_shader_demote_to_helper_invocation on Intel. VK_KHR_depth_stencil_resolve on radv VK_KHR_imageless_framebuffer on radv VK_KHR_shader_atomic_int64 on radv VK_KHR_uniform_buffer_standard_layout on radv (note: iris is the new DRI driver for newer Intel, not enabled by default yet) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1844132/+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 1847739] Re: Make zfs-initramfs and zfsutils-linux install optional
I went ahead and added ZFS to mate-live, since Martin forgot that step when he fixed his meta. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1847739 Title: Make zfs-initramfs and zfsutils-linux install optional Status in ubiquity package in Ubuntu: Fix Released Status in ubuntu-budgie-meta package in Ubuntu: Fix Released Status in ubuntu-mate-meta package in Ubuntu: Fix Committed Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntustudio-meta package in Ubuntu: Fix Released Status in xubuntu-meta package in Ubuntu: New Bug description: Move those 2 to the live seed to have them available in the installer. Mark them then manually installed in the installer if needed. Then, ubiquity will purge them if not used. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1847739/+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 1843743] Re: klibc ftbfs in eoan
2.0.7-1 fails to build in the same way on Ubuntu 19.10. I'm assuming it's either glibc 2.30 (Debian is at 2.29) or linux 5.3 (Debian is at 5.2), with the latter being more likely. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1843743 Title: klibc ftbfs in eoan Status in klibc package in Ubuntu: Confirmed Status in klibc source package in Eoan: Confirmed Bug description: https://launchpadlibrarian.net/441262209/buildlog_ubuntu-eoan- amd64.klibc_2.0.6-1ubuntu1_BUILDING.txt.gz gcc -Wp,-MD,usr/klibc/.sigsuspend.o.d -nostdinc -iwithprefix include -I/<>/usr/include/arch/x86_64 -Iusr/include/arch/x86_64 -I/<>/usr/include/bits64 -Iusr/include/bits64 -I/<>/usr/klibc/../include -Iusr/klibc/../include -I/<>/usr/include -Iusr/include -I/<>/linux/include -Ilinux/include -D__KLIBC__=2 -D__KLIBC_MINOR__=0 -D_BITSIZE=64 -fno-stack-protector -fwrapv -fno-PIE -ggdb -m64 -Os -fomit-frame-pointer -mno-sse -falign-functions=1 -falign-jumps=1 -falign-loops=1 -fno-asynchronous-unwind-tables -W -Wall -Wno-sign-compare -Wno-unused-parameter -c -o usr/klibc/sigsuspend.o usr/klibc/sigsuspend.c usr/klibc/sigsuspend.c:8:10: fatal error: klibc/havesyscall.h: No such file or directory 8 | #include | ^ compilation terminated. make[4]: *** [/<>/scripts/Kbuild.klibc:252: usr/klibc/sigsuspend.o] Error 1 make[3]: *** [/<>/./Kbuild:9: all] Error 2 make[2]: *** [Makefile:118: klibc] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1843743/+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 1843743] Re: klibc ftbfs in eoan
> The best guess I can come up with is that there's something different > about the compiler defaults you're using Derp, this was the hint I needed. The attached patch fixes the build on Ubuntu, though I can't think of a good way to upstream this, as the compiler option in question isn't available throughout history. Probably needs a test of some sort. ** Patch added: "cf-protection.patch" https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1843743/+attachment/5299063/+files/cf-protection.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1843743 Title: klibc ftbfs in eoan Status in klibc package in Ubuntu: Confirmed Status in klibc source package in Eoan: Confirmed Bug description: https://launchpadlibrarian.net/441262209/buildlog_ubuntu-eoan- amd64.klibc_2.0.6-1ubuntu1_BUILDING.txt.gz gcc -Wp,-MD,usr/klibc/.sigsuspend.o.d -nostdinc -iwithprefix include -I/<>/usr/include/arch/x86_64 -Iusr/include/arch/x86_64 -I/<>/usr/include/bits64 -Iusr/include/bits64 -I/<>/usr/klibc/../include -Iusr/klibc/../include -I/<>/usr/include -Iusr/include -I/<>/linux/include -Ilinux/include -D__KLIBC__=2 -D__KLIBC_MINOR__=0 -D_BITSIZE=64 -fno-stack-protector -fwrapv -fno-PIE -ggdb -m64 -Os -fomit-frame-pointer -mno-sse -falign-functions=1 -falign-jumps=1 -falign-loops=1 -fno-asynchronous-unwind-tables -W -Wall -Wno-sign-compare -Wno-unused-parameter -c -o usr/klibc/sigsuspend.o usr/klibc/sigsuspend.c usr/klibc/sigsuspend.c:8:10: fatal error: klibc/havesyscall.h: No such file or directory 8 | #include | ^ compilation terminated. make[4]: *** [/<>/scripts/Kbuild.klibc:252: usr/klibc/sigsuspend.o] Error 1 make[3]: *** [/<>/./Kbuild:9: all] Error 2 make[2]: *** [Makefile:118: klibc] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1843743/+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 1843743] Re: klibc ftbfs in eoan
** Description changed: - https://launchpadlibrarian.net/441262209/buildlog_ubuntu-eoan- - amd64.klibc_2.0.6-1ubuntu1_BUILDING.txt.gz + [ SRU Justification / Impact ] + klibc is FTBFS in eoan. As we have a history of SRUing klibc to add new features, we should probably make sure it's buildable. + + [ Test Case ] + If it builds, we win. Should also test that a machine with the new klibc installed still boots. + + [ Regression Potential ] + One patch is just adding a missing include, and the other is altering the build of a stub only used to determine which syscalls are availble, a part of the build that will cause the rest of the build to fail if it's generated incorrectly. Regression potential should be very low. + + [ Original Bug Report ] + https://launchpadlibrarian.net/441262209/buildlog_ubuntu-eoan-amd64.klibc_2.0.6-1ubuntu1_BUILDING.txt.gz gcc -Wp,-MD,usr/klibc/.sigsuspend.o.d -nostdinc -iwithprefix include -I/<>/usr/include/arch/x86_64 -Iusr/include/arch/x86_64 -I/<>/usr/include/bits64 -Iusr/include/bits64 -I/<>/usr/klibc/../include -Iusr/klibc/../include -I/<>/usr/include -Iusr/include -I/<>/linux/include -Ilinux/include -D__KLIBC__=2 -D__KLIBC_MINOR__=0 -D_BITSIZE=64 -fno-stack-protector -fwrapv -fno-PIE -ggdb -m64 -Os -fomit-frame-pointer -mno-sse -falign-functions=1 -falign-jumps=1 -falign-loops=1 -fno-asynchronous-unwind-tables -W -Wall -Wno-sign-compare -Wno-unused-parameter -c -o usr/klibc/sigsuspend.o usr/klibc/sigsuspend.c usr/klibc/sigsuspend.c:8:10: fatal error: klibc/havesyscall.h: No such file or directory - 8 | #include - | ^ + 8 | #include + | ^ compilation terminated. make[4]: *** [/<>/scripts/Kbuild.klibc:252: usr/klibc/sigsuspend.o] Error 1 make[3]: *** [/<>/./Kbuild:9: all] Error 2 make[2]: *** [Makefile:118: klibc] Error 2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1843743 Title: klibc ftbfs in eoan Status in klibc package in Ubuntu: Confirmed Status in klibc source package in Eoan: Confirmed Bug description: [ SRU Justification / Impact ] klibc is FTBFS in eoan. As we have a history of SRUing klibc to add new features, we should probably make sure it's buildable. [ Test Case ] If it builds, we win. Should also test that a machine with the new klibc installed still boots. [ Regression Potential ] One patch is just adding a missing include, and the other is altering the build of a stub only used to determine which syscalls are availble, a part of the build that will cause the rest of the build to fail if it's generated incorrectly. Regression potential should be very low. [ Original Bug Report ] https://launchpadlibrarian.net/441262209/buildlog_ubuntu-eoan-amd64.klibc_2.0.6-1ubuntu1_BUILDING.txt.gz gcc -Wp,-MD,usr/klibc/.sigsuspend.o.d -nostdinc -iwithprefix include -I/<>/usr/include/arch/x86_64 -Iusr/include/arch/x86_64 -I/<>/usr/include/bits64 -Iusr/include/bits64 -I/<>/usr/klibc/../include -Iusr/klibc/../include -I/<>/usr/include -Iusr/include -I/<>/linux/include -Ilinux/include -D__KLIBC__=2 -D__KLIBC_MINOR__=0 -D_BITSIZE=64 -fno-stack-protector -fwrapv -fno-PIE -ggdb -m64 -Os -fomit-frame-pointer -mno-sse -falign-functions=1 -falign-jumps=1 -falign-loops=1 -fno-asynchronous-unwind-tables -W -Wall -Wno-sign-compare -Wno-unused-parameter -c -o usr/klibc/sigsuspend.o usr/klibc/sigsuspend.c usr/klibc/sigsuspend.c:8:10: fatal error: klibc/havesyscall.h: No such file or directory 8 | #include | ^ compilation terminated. make[4]: *** [/<>/scripts/Kbuild.klibc:252: usr/klibc/sigsuspend.o] Error 1 make[3]: *** [/<>/./Kbuild:9: all] Error 2 make[2]: *** [Makefile:118: klibc] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1843743/+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 1843743] Re: klibc ftbfs in eoan
Oh, klibc has the same cc-option magic as the kernel's Kbuild does, so that's the correct upstream answer. I'll update my patch to use that when I merge 2.0.7. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1843743 Title: klibc ftbfs in eoan Status in klibc package in Ubuntu: Confirmed Status in klibc source package in Eoan: Confirmed Bug description: [ SRU Justification / Impact ] klibc is FTBFS in eoan. As we have a history of SRUing klibc to add new features, we should probably make sure it's buildable. [ Test Case ] If it builds, we win. Should also test that a machine with the new klibc installed still boots. [ Regression Potential ] One patch is just adding a missing include, and the other is altering the build of a stub only used to determine which syscalls are availble, a part of the build that will cause the rest of the build to fail if it's generated incorrectly. Regression potential should be very low. [ Original Bug Report ] https://launchpadlibrarian.net/441262209/buildlog_ubuntu-eoan-amd64.klibc_2.0.6-1ubuntu1_BUILDING.txt.gz gcc -Wp,-MD,usr/klibc/.sigsuspend.o.d -nostdinc -iwithprefix include -I/<>/usr/include/arch/x86_64 -Iusr/include/arch/x86_64 -I/<>/usr/include/bits64 -Iusr/include/bits64 -I/<>/usr/klibc/../include -Iusr/klibc/../include -I/<>/usr/include -Iusr/include -I/<>/linux/include -Ilinux/include -D__KLIBC__=2 -D__KLIBC_MINOR__=0 -D_BITSIZE=64 -fno-stack-protector -fwrapv -fno-PIE -ggdb -m64 -Os -fomit-frame-pointer -mno-sse -falign-functions=1 -falign-jumps=1 -falign-loops=1 -fno-asynchronous-unwind-tables -W -Wall -Wno-sign-compare -Wno-unused-parameter -c -o usr/klibc/sigsuspend.o usr/klibc/sigsuspend.c usr/klibc/sigsuspend.c:8:10: fatal error: klibc/havesyscall.h: No such file or directory 8 | #include | ^ compilation terminated. make[4]: *** [/<>/scripts/Kbuild.klibc:252: usr/klibc/sigsuspend.o] Error 1 make[3]: *** [/<>/./Kbuild:9: all] Error 2 make[2]: *** [Makefile:118: klibc] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1843743/+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 1843743] Re: klibc ftbfs in eoan
The builds all succeeded, and tested booting on amd64 (the only arch likely to be affected, due to cf-protection changes in the toolchain), and it booted fine. Marking v-done. ** Tags removed: verification-needed verification-needed-eoan ** Tags added: verification-done verification-done-eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1843743 Title: klibc ftbfs in eoan Status in klibc package in Ubuntu: Confirmed Status in klibc source package in Eoan: Fix Committed Bug description: [ SRU Justification / Impact ] klibc is FTBFS in eoan. As we have a history of SRUing klibc to add new features, we should probably make sure it's buildable. [ Test Case ] If it builds, we win. Should also test that a machine with the new klibc installed still boots. [ Regression Potential ] One patch is just adding a missing include, and the other is altering the build of a stub only used to determine which syscalls are availble, a part of the build that will cause the rest of the build to fail if it's generated incorrectly. Regression potential should be very low. [ Original Bug Report ] https://launchpadlibrarian.net/441262209/buildlog_ubuntu-eoan-amd64.klibc_2.0.6-1ubuntu1_BUILDING.txt.gz gcc -Wp,-MD,usr/klibc/.sigsuspend.o.d -nostdinc -iwithprefix include -I/<>/usr/include/arch/x86_64 -Iusr/include/arch/x86_64 -I/<>/usr/include/bits64 -Iusr/include/bits64 -I/<>/usr/klibc/../include -Iusr/klibc/../include -I/<>/usr/include -Iusr/include -I/<>/linux/include -Ilinux/include -D__KLIBC__=2 -D__KLIBC_MINOR__=0 -D_BITSIZE=64 -fno-stack-protector -fwrapv -fno-PIE -ggdb -m64 -Os -fomit-frame-pointer -mno-sse -falign-functions=1 -falign-jumps=1 -falign-loops=1 -fno-asynchronous-unwind-tables -W -Wall -Wno-sign-compare -Wno-unused-parameter -c -o usr/klibc/sigsuspend.o usr/klibc/sigsuspend.c usr/klibc/sigsuspend.c:8:10: fatal error: klibc/havesyscall.h: No such file or directory 8 | #include | ^ compilation terminated. make[4]: *** [/<>/scripts/Kbuild.klibc:252: usr/klibc/sigsuspend.o] Error 1 make[3]: *** [/<>/./Kbuild:9: all] Error 2 make[2]: *** [Makefile:118: klibc] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1843743/+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 1850184] Re: losetup -f broken in 2.0.6-1ubuntu2
The testcase here doesn't seem to be working (or, rather, failing) for me, which makes it harder to investigate this. It passes on both sid and eoan for me: (sid-amd64)root@nosferatu:~# dpkg -l \*klibc\* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---=== ii klibc-utils2.0.7-1 amd64small utilities built with klibc for early boot ii libklibc:amd64 2.0.7-1 amd64minimal libc subset for use with initramfs (sid-amd64)root@nosferatu:~# /usr/lib/klibc/bin/losetup -vf Loop device is /dev/loop0 /dev/loop0 (sid-amd64)root@nosferatu:~# (eoan-amd64)root@nosferatu:~# dpkg -l \*klibc\* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name VersionArchitecture Description +++-==-==--=== ii klibc-utils2.0.6-1ubuntu2 amd64small utilities built with klibc for early boot ii libklibc:amd64 2.0.6-1ubuntu2 amd64minimal libc subset for use with initramfs (eoan-amd64)root@nosferatu:~# /usr/lib/klibc/bin/losetup -vf Loop device is /dev/loop0 /dev/loop0 (eoan-amd64)root@nosferatu:~# -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1850184 Title: losetup -f broken in 2.0.6-1ubuntu2 Status in gcc-9 package in Ubuntu: New Status in klibc package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in gcc-9 source package in Eoan: New Status in klibc source package in Eoan: New Status in linux source package in Eoan: Incomplete Status in gcc-9 source package in Focal: New Status in klibc source package in Focal: New Status in linux source package in Focal: Incomplete Bug description: [Impact] * sudo /usr/lib/klibc/bin/losetup -vf, which appears to be missbuilt, as main(argc) is reset to zero, after ioctl() operations in a function call, quite unexpectadly. [Test Case] * $ sudo /usr/lib/klibc/bin/losetup -vf Loop device is /dev/loop20 loop: can't get info on device /dev/loop20: No such device or address is bad. Note that ioctl() must succeed, thus loop0 device must be configured to trigger the bug. [Regression Potential] * klibc is quite special, as it uses linux kernel headers/assembly. It seems like there is incompatibility between klibc sources, and gcc-9 with linux-5.3 when used to build userspace programmes. * disabling cf-protection and stack-clash-protection did not help. * building with gcc-8 does not exhibit the problem. * the workaround is quite simple in the code, keep a copy of argc to compare to it later in the code. [Other Info] * Original bug report http://autopkgtest.ubuntu.com/packages/c/casper/focal/amd64 https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal/focal/amd64/c/casper/20191025_214555_df8b8@/log.gz ... [ 11.751912] EXT4-fs (sda1): mounting ext2 file system using the ext4 subsystem [ 11.761441] EXT4-fs (sda1): mounted filesystem without journal. Opts: (null) loop: can't get info on device /dev/loop1: No such device or address BusyBox v1.30.1 (Ubuntu 1:1.30.1-4ubuntu4) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) [6n+ mkdir result + set -x + read LINE + grep -e '^--OUT .* BEGIN-- .* --END--$' qemu-output.txt ++ grep -q /rofs result/lsblk.txt grep: result/lsblk.txt: No such file or directory autopkgtest [21:45:45]: test boot: ---] autopkgtest [21:45:45]: test boot: - - - - - - - - - - results - - - - - - - - - - boot FAIL non-zero exit status 2 autopkgtest [21:45:45]: summary boot FAIL non-zero exit status 2 ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-9/+bug/1850184/+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 1850184] Re: losetup -f broken in 2.0.6-1ubuntu2
Ah-ha. If loop0 is in use, then the test-case appropriately fails in both unstable and eoan, which is comforting, as I didn't look forward to figuring out why this works in Debian (it doesn't). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1850184 Title: losetup -f broken in 2.0.6-1ubuntu2 Status in gcc-9 package in Ubuntu: New Status in klibc package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in gcc-9 source package in Eoan: New Status in klibc source package in Eoan: New Status in linux source package in Eoan: Incomplete Status in gcc-9 source package in Focal: New Status in klibc source package in Focal: New Status in linux source package in Focal: Incomplete Bug description: [Impact] * sudo /usr/lib/klibc/bin/losetup -vf, which appears to be missbuilt, as main(argc) is reset to zero, after ioctl() operations in a function call, quite unexpectadly. [Test Case] * $ sudo /usr/lib/klibc/bin/losetup -vf Loop device is /dev/loop20 loop: can't get info on device /dev/loop20: No such device or address is bad. Note that ioctl() must succeed, thus loop0 device must be configured to trigger the bug. [Regression Potential] * klibc is quite special, as it uses linux kernel headers/assembly. It seems like there is incompatibility between klibc sources, and gcc-9 with linux-5.3 when used to build userspace programmes. * disabling cf-protection and stack-clash-protection did not help. * building with gcc-8 does not exhibit the problem. * the workaround is quite simple in the code, keep a copy of argc to compare to it later in the code. [Other Info] * Original bug report http://autopkgtest.ubuntu.com/packages/c/casper/focal/amd64 https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal/focal/amd64/c/casper/20191025_214555_df8b8@/log.gz ... [ 11.751912] EXT4-fs (sda1): mounting ext2 file system using the ext4 subsystem [ 11.761441] EXT4-fs (sda1): mounted filesystem without journal. Opts: (null) loop: can't get info on device /dev/loop1: No such device or address BusyBox v1.30.1 (Ubuntu 1:1.30.1-4ubuntu4) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) [6n+ mkdir result + set -x + read LINE + grep -e '^--OUT .* BEGIN-- .* --END--$' qemu-output.txt ++ grep -q /rofs result/lsblk.txt grep: result/lsblk.txt: No such file or directory autopkgtest [21:45:45]: test boot: ---] autopkgtest [21:45:45]: test boot: - - - - - - - - - - results - - - - - - - - - - boot FAIL non-zero exit status 2 autopkgtest [21:45:45]: summary boot FAIL non-zero exit status 2 ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-9/+bug/1850184/+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 1850184] Re: losetup -f broken in 2.0.6-1ubuntu2
** Changed in: klibc (Ubuntu Focal) Status: Fix Released => Confirmed ** Changed in: klibc (Ubuntu Eoan) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1850184 Title: losetup -f broken in 2.0.6-1ubuntu2 Status in klibc package in Ubuntu: Confirmed Status in klibc source package in Eoan: Confirmed Status in klibc source package in Focal: Confirmed Bug description: [Impact] * sudo /usr/lib/klibc/bin/losetup -vf, which appears to be missbuilt, as main(argc) is reset to zero, after ioctl() operations in a function call, quite unexpectadly. [Test Case] * $ sudo /usr/lib/klibc/bin/losetup -vf Loop device is /dev/loop20 loop: can't get info on device /dev/loop20: No such device or address is bad. Note that ioctl() must succeed, thus loop0 device must be configured to trigger the bug. [Regression Potential] * klibc is quite special, as it uses linux kernel headers/assembly. It seems like there is incompatibility between klibc sources, and gcc-9 with linux-5.3 when used to build userspace programmes. * disabling cf-protection and stack-clash-protection did not help. * building with gcc-8 does not exhibit the problem. * the workaround is quite simple in the code, keep a copy of argc to compare to it later in the code. [Other Info] * Original bug report http://autopkgtest.ubuntu.com/packages/c/casper/focal/amd64 https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal/focal/amd64/c/casper/20191025_214555_df8b8@/log.gz ... [ 11.751912] EXT4-fs (sda1): mounting ext2 file system using the ext4 subsystem [ 11.761441] EXT4-fs (sda1): mounted filesystem without journal. Opts: (null) loop: can't get info on device /dev/loop1: No such device or address BusyBox v1.30.1 (Ubuntu 1:1.30.1-4ubuntu4) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) [6n+ mkdir result + set -x + read LINE + grep -e '^--OUT .* BEGIN-- .* --END--$' qemu-output.txt ++ grep -q /rofs result/lsblk.txt grep: result/lsblk.txt: No such file or directory autopkgtest [21:45:45]: test boot: ---] autopkgtest [21:45:45]: test boot: - - - - - - - - - - results - - - - - - - - - - boot FAIL non-zero exit status 2 autopkgtest [21:45:45]: summary boot FAIL non-zero exit status 2 ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1850184/+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 1847638] Re: initramfs-tools tests depend on linux-image-generic, not available on i386
** Summary changed: - initramfs-tools-core fails to install on i386 + initramfs-tools tests depend on linux-image-generic, not available on i386 -- 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/1847638 Title: initramfs-tools tests depend on linux-image-generic, not available on i386 Status in initramfs-tools package in Ubuntu: New Bug description: Autopkgtest fails on i386 due to kmod pulling in linux-image- generic:i386 , but it does not exist anymore in Eoan. http://autopkgtest.ubuntu.com/packages/i/initramfs-tools/eoan/i386 https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/i386/i/initramfs-tools/20191009_203931_515d7@/log.gz : ... Broken autopkgtest-satdep:i386 Depends on linux-image-generic:i386 < none @un H > Removing autopkgtest-satdep:i386 because I can't find linux-image-generic:i386 Done ... Manual testing: ubuntu@autopkgtest:/initramfs-tools-0.133ubuntu10$ sudo apt install initramfs-tools-core Reading package lists... Done Building dependency tree Reading state information... Done initramfs-tools-core is already the newest version (0.133ubuntu10). initramfs-tools-core set to manually installed. You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: autopkgtest-satdep : Depends: linux-image-generic but it is not installable Depends: qemu-system E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). ubuntu@autopkgtest:/initramfs-tools-0.133ubuntu10$ sudo apt install kmod Reading package lists... Done Building dependency tree Reading state information... Done kmod is already the newest version (26-1ubuntu1). kmod set to manually installed. You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: autopkgtest-satdep : Depends: linux-image-generic but it is not installable Depends: qemu-system E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1847638/+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 1845337] Re: Disco autopkgtest @ armhf fails root-unittests -> test-execute -> exec-dynamicuser-statedir.service
I bumped the systemd/ppc64el hint and retried the rest, and autopkgtests look clear now. -- 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/1845337 Title: Disco autopkgtest @ armhf fails root-unittests -> test-execute -> exec-dynamicuser-statedir.service Status in qemu package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in qemu source package in Disco: Invalid Status in systemd source package in Disco: Fix Committed Bug description: [impact] due to a recent change to allow armhf tests to run lxd containers, autopkgtest for systemd on disco fails consistently. [test case] see test results, linked in original description below. [regression potential] very low, autopkgtest fix only. [other info] original description: --- Since the recent few weeks systemd autopkgtest @ armhf @ disco fail [1]. The log is very (very) long and partially interwoven due to concurrent execution. Somewhere in between we see this subcase is the one failing: root-unittests Of this test (which again has many subtests) it is: test-execute And of this again it is (always): I'll attach bad and good case full and stripped logs. The diff of those comes down to just: 1. execute a find in a shell 2. shell exits 3. exec-dynamicuser-statedir.service: Main process exited, code=exited, status=0/SUCCESS vs 3. exec-dynamicuser-statedir.service: Main process exited, code=exited, status=1/FAILURE 4. in the bad case that triggers an assertion The find that fails is: find / -path /var/tmp -o -path /tmp -o -path /proc -o -path /dev/mqueue -o -path /dev/shm -o -path /sys/fs/bpf Good and bad case are the same most recent version systemd/240-6ubuntu5.7. Maybe something is bad in the containers we have for armhf in regard to these paths? Was there any change we'd know of? If there is nothing known, could we force-badtest it to get it out of the way of ongoing migrations? [1]: http://autopkgtest.ubuntu.com/packages/s/systemd/disco/armhf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1845337/+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 1831498] Update Released
The verification of the Stable Release Update for mesa has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1831498 Title: radeonsi: GTK elements become invisible in some applications (GIMP, LibreOffice) Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Bionic: Fix Committed Status in mesa source package in Disco: Fix Committed Bug description: [impact] imported from https://bugs.freedesktop.org/show_bug.cgi?id=110355 : "I am currently experiencing some issues with GTK elements (GtkMenuItem, GtkMenu) becoming invisible with GIMP and LibreOffice. I am currently using radeonsi+glamor and I'm on Arch Linux (x86_64). My hardware is a Ryzen 5 2400G APU with vega graphics." [test case] test that GIMP/Libreoffice work fine on AMD Vega/Raven [regression potential] the fix/workaround is already in mesa 19.0.4, shouldn't regress anything To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1831498/+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 1824111] Update Released
The verification of the Stable Release Update for llvm-toolchain-8 has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1824111 Title: Backport packages for 18.04.3 HWE stack Status in OEM Priority Project: Confirmed Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-8 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Released Status in libdrm source package in Bionic: Fix Released Status in llvm-toolchain-8 source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Committed Status in xorg-server-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic: Fix Released Bug description: [Impact] These are needed for 18.04.3 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-8: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 19.0.x series, so there shouldn't be any regressions left at that point xserver: a new minor release xorg drivers: modest updates, mainly just new ati/amdgpu [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1824111/+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 1835257] Re: update tzdata package to 2019b
Didn't notice this bug until I'd already done the work, so it's not linked in changelogs, but tzdata has been updated for eoan, disco, cosmic, bionic, xenial, and trusty-esm and precise-esm. ** Changed in: tzdata (Ubuntu) Assignee: (unassigned) => Adam Conrad (adconrad) ** Changed in: tzdata (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1835257 Title: update tzdata package to 2019b Status in tzdata package in Ubuntu: Fix Released Bug description: Update tzdata package to 2019b. https://mm.icann.org/pipermail/tz-announce/2019-July/56.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1835257/+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 1835809] Re: AMD Ryzen 3000 series fails to boot
FWIW, I think not booting a 19.04 ISO is probably fine, and it's not worth spinning a point release for this. "I can't install a 9mo release on this hardware" is unforunate, but not world-ending. However, we should definitely SRU this for people who are likely to take their EXISTING 19.04 system with a Ryzen 1xxx/2xxx and drop in a 3xxx and find it doesn't boot anymore. Also, obviously, we should make sure it's fixed for 19.10. -- 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/1835809 Title: AMD Ryzen 3000 series fails to boot Status in systemd package in Ubuntu: New Bug description: On the new AMD Ryzen 3000 series CPUs, there is an issue with systemd preventing the boot process from completing. This issue does not affect the older systemd version in 18.04, but affects the 19.04 version. Here is a screenshot showing what happens: https://www.phoronix.net/image.php?id=ryzen-3700x-3900x-linux&image=amd_zen2_14_show I am currently testing a patch to systemd, derived from this pull request: https://github.com/systemd/systemd/pull/12536 This is a high severity issue, as I do not believe there is no potential workaround without either a firmware update or an ISO respin. I have attached a rebase of the potential patch on the current 19.04 version of systemd for reference. I will provide more details after testing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1835809/+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 1835809] Re: AMD Ryzen 3000 series fails to boot
Hello Jeremy, or anyone else affected, Accepted systemd into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/240-6ubuntu5.2 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-disco to verification-done-disco. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-disco. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Disco) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-disco ** Changed in: systemd (Ubuntu Disco) Assignee: (unassigned) => Balint Reczey (rbalint) -- 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/1835809 Title: AMD Ryzen 3000 series fails to boot Status in systemd package in Ubuntu: In Progress Status in systemd source package in Disco: Fix Committed Bug description: [Impact] * Systems with AMD Ryzen 3000 series CPUs don't boot. [Test Case] * Boot with fixed systemd on an AMD Ryzen 3000 series system. [Regression Potential] * The fix itself is very small, it ignores known to be faulty random values returned by the rdrand instruction and use a different random source. Those values can still be returned by a properly working rdrand implementation in 2 in 2^32 cases on 32 bit arches and in 2 in 2^64 cases on 64 bit arches, but the fallback to the other random source ensures that in those rare occasions a random number can be generated. [Original Bug Text] On the new AMD Ryzen 3000 series CPUs, there is an issue with systemd preventing the boot process from completing. This issue does not affect the older systemd version in 18.04, but affects the 19.04 version. Here is a screenshot showing what happens: https://www.phoronix.net/image.php?id=ryzen-3700x-3900x-linux&image=amd_zen2_14_show I am currently testing a patch to systemd, derived from this pull request: https://github.com/systemd/systemd/pull/12536 This is a high severity issue, as I do not believe there is no potential workaround without either a firmware update or an ISO respin. I have attached a rebase of the potential patch on the current 19.04 version of systemd for reference. I will provide more details after testing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1835809/+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 1835809] Re: AMD Ryzen 3000 series fails to boot
Note that the fix is committed to git for eoan, but not uploaded as systemd currently fails its testsuite on eoan. This needs investigation. -- 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/1835809 Title: AMD Ryzen 3000 series fails to boot Status in systemd package in Ubuntu: In Progress Status in systemd source package in Disco: Fix Committed Bug description: [Impact] * Systems with AMD Ryzen 3000 series CPUs don't boot. [Test Case] * Boot with fixed systemd on an AMD Ryzen 3000 series system. [Regression Potential] * The fix itself is very small, it ignores known to be faulty random values returned by the rdrand instruction and use a different random source. Those values can still be returned by a properly working rdrand implementation in 2 in 2^32 cases on 32 bit arches and in 2 in 2^64 cases on 64 bit arches, but the fallback to the other random source ensures that in those rare occasions a random number can be generated. [Original Bug Text] On the new AMD Ryzen 3000 series CPUs, there is an issue with systemd preventing the boot process from completing. This issue does not affect the older systemd version in 18.04, but affects the 19.04 version. Here is a screenshot showing what happens: https://www.phoronix.net/image.php?id=ryzen-3700x-3900x-linux&image=amd_zen2_14_show I am currently testing a patch to systemd, derived from this pull request: https://github.com/systemd/systemd/pull/12536 This is a high severity issue, as I do not believe there is no potential workaround without either a firmware update or an ISO respin. I have attached a rebase of the potential patch on the current 19.04 version of systemd for reference. I will provide more details after testing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1835809/+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 1837466] Re: [SRU] Please make ubuntu-wsl recommend dbus-x11
Hello Balint, or anyone else affected, Accepted ubuntu-meta into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-meta/1.431.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-disco to verification-done-disco. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-disco. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: ubuntu-meta (Ubuntu Disco) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1837466 Title: [SRU] Please make ubuntu-wsl recommend dbus-x11 Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-meta source package in Disco: Fix Committed Bug description: [Impact] * Some graphical apps such as gedit complain about not being able to start dbus using dbus-launch when they are started from the WSL Ubuntu terminal because dbus-x11 is not installed. [Test Case] * Test if ubuntu-wsl recommends dbus-x11 (check the version to be verified): $ apt-cache show ubuntu-wsl=1.435 | grep dbus Recommends: dbus-x11 [Regression Potential] * Recommending the new dbus-x11 package comes with an increased installation size, but this is accepted to make the WSL experience more pleasant. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1837466/+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 1795959] Update Released
The verification of the Stable Release Update for ubuntu-meta has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1795959 Title: [FFe] Seed xdg-desktop-portal-gtk Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-meta source package in Xenial: New Status in ubuntu-meta source package in Bionic: Fix Released Bug description: [Impact] * These packages can improve desktop integration of snap packages. The risk is low as nothing in the default desktop install actually exercises the portals at this time. We need to seed the portals so they are available when snaps are installed that can utilize them. Flatpak packages will also benefit. [Test Case] * This can be tested by using the portal-test snap [Regression potential] * Nothing in the default install utilizes it, so there should be no risk. [Other Info] * Security and MIR reviews have been completed for xdg-desktop-portal-gtk[1] and xdg-desktop-portal[2]. 1. https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1750069 2. https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1749672 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1795959/+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 1798597] Update Released
The verification of the Stable Release Update for llvm-toolchain-7 has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1798597 Title: Backport packages for 18.04.2 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-7 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in xf86-input-wacom-hwe-18.04 package in Ubuntu: Invalid Status in xorg-hwe-18.04 package in Ubuntu: Invalid Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-evdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-joystick-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-libinput-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-synaptics-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-dummy-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-fbdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-nouveau-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-qxl-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vesa-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vmware-hwe-18.04 package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Committed Status in libdrm source package in Bionic: Fix Released Status in llvm-toolchain-7 source package in Bionic: Fix Committed Status in mesa source package in Bionic: Fix Released Status in wayland source package in Bionic: Fix Released Status in xf86-input-wacom-hwe-18.04 source package in Bionic: Fix Released Status in xorg-hwe-18.04 source package in Bionic: Fix Committed Status in xorg-server-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-evdev-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-input-joystick-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-libinput-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-synaptics-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-dummy-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-fbdev-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-qxl-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-vesa-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-vmware-hwe-18.04 source package in Bionic: Fix Released Bug description: [Impact] These are needed for 18.04.2 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-7: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 18.2.x series, so there shouldn't be any regressions left at that point xserver: a new major release, but since it's renamed there's no real chance of regression when it hits the archive xorg drivers: same as xserver [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1798597/+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 1560286] Update Released
The verification of the Stable Release Update for cairo has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/1560286 Title: Evince displays pdf file fine, but prints colors inverted Status in cairo package in Ubuntu: Fix Released Status in cairo source package in Bionic: Fix Released Status in cairo source package in Cosmic: Fix Committed Bug description: * Impact In some files images are printed with inverted colors * Test case open https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1560286/+attachment/5226857/+files/978-1-57896-287-7%20LL4%20SW%20Sem%201%20Reduced%20p.17.pdf in evince, click on the print preview, the colors should be right * Regression potential it's a change in the code dealing with specific adobe file, test opening the example in different document viewer and try with some other files (the bug has several example), they should display the correct image/colors I have several pdf files that when opened by evince, they appear to be fine until I try to print them. When I do, they print with the colors inverted (the printout looks like a photograph negative). This color inversion also occurs when viewed in the print preview screen. If I click on File > Properties, I get some information... Producer : Adobe Acrobat 15.10 Image Conversion Plug-in Creator : Adobe Acrobat 15.10 ... Format : PDF-1.6 ... I am running ubuntu 14.04 LTS ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: evince 3.10.3-0ubuntu10.2 ProcVersionSignature: Ubuntu 3.13.0-83.127-generic 3.13.11-ckt35 Uname: Linux 3.13.0-83-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 21 21:01:45 2016 ExecutablePath: /usr/bin/evince InstallationDate: Installed on 2012-07-24 (1336 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: LANGUAGE=en_US PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: Upgraded to trusty on 2014-09-29 (539 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1560286/+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 1802135] Update Released
The verification of the Stable Release Update for kmod has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1802135 Title: broken touchpad after i2c-i801 blacklist change Status in kmod package in Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Status in kmod source package in Xenial: Fix Committed Status in linux source package in Xenial: Invalid Status in kmod source package in Bionic: Fix Released Status in linux source package in Bionic: Fix Released Status in kmod source package in Cosmic: Fix Committed Status in linux source package in Cosmic: Fix Committed Bug description: SRU: [Impact] ThinkPad 11e 2nd/3rd touchpad not working when load i2c-i801. PNP LEN0049 will use smbus by default in kernel, but i2c bus is in runtime suspend mode in old touchpad fw. Then touchpad will not work. LEN2040 on 11e 3rd can reproduce this issue by passing psmouse.synaptics_intertouch=1 These 2 pnp device should be the same one Synaptics s3203_ver5. [Fix] i2c-i801 should auto suspend when not used, no need runtime pm. [Test Case] Tested on Thinkpad 11e 3rd. Touchpad works fine. [Regression Potential] Low, upstream fix cherry-picked. 4.18 kernel patch, no need for cosmic. Original bug report: = After upgrading to kmod (24-1ubuntu3.1) the trackpads stop working on Lenovo 11e 2nd gen machines. We have a fleet of approximetly 1000 of them in production running ubuntu 18.04. Prior to this update the trackpads worked out of box in 18.04. We are currently working around the issue by deploying our own blacklist files. Here is a link to the SRU justification: https://bugs.launchpad.net /hwe-next/+bug/1786574 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1802135/+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 1798597] Re: Backport packages for 18.04.2 HWE stack
Hello Timo, or anyone else affected, Accepted xserver-xorg-video-intel-hwe-18.04 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xserver-xorg-video-intel- hwe-18.04/2:2.99.917+git20171229-1ubuntu1~18.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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-done verification-done-bionic ** Tags added: verification-needed verification-needed-bionic -- 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/1798597 Title: Backport packages for 18.04.2 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-7 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in xf86-input-wacom-hwe-18.04 package in Ubuntu: Invalid Status in xorg-hwe-18.04 package in Ubuntu: Invalid Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-evdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-joystick-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-libinput-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-synaptics-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-dummy-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-fbdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-nouveau-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-qxl-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vesa-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vmware-hwe-18.04 package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Released Status in libdrm source package in Bionic: Fix Released Status in llvm-toolchain-7 source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Released Status in wayland source package in Bionic: Fix Released Status in xf86-input-wacom-hwe-18.04 source package in Bionic: Fix Released Status in xorg-hwe-18.04 source package in Bionic: Fix Released Status in xorg-server-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-evdev-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-joystick-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-libinput-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-synaptics-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-dummy-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-fbdev-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-qxl-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-vesa-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-vmware-hwe-18.04 source package in Bionic: Fix Released Bug description: [Impact] These are needed for 18.04.2 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-7: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 18
[Touch-packages] [Bug 1807448] Re: [SRU] Patch power9-001.diff breaks IFUNC on ELFv1
glibc has built successfully on powerpc with this new binutils ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1807448 Title: [SRU] Patch power9-001.diff breaks IFUNC on ELFv1 Status in binutils package in Ubuntu: Invalid Status in binutils source package in Xenial: Fix Committed Bug description: [ SRU Justification ] As per comment #4 in https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1655181 the undefined weak fix should not have been backported because it breaks IFUNC on ELFv1, and can't be fixed without a much larger backport from 2.27. This patch breaks glibc builds on PPC64 ELFv1. See also https://sourceware.org/bugzilla/show_bug.cgi?id=20472 I will be pushing this upload via the ubuntu-security-proposed PPA, as this regression also exists in security and if we ever want to do a glibc security update, we need the fix there as well. [ Test Case ] See that glibc now builds on powerpc in xenial, when it didn't with the previous version. [ Regression Potential ] We lived fine without this patch before, and will do again in the future. Removing it fixes ELFv1 glibc builds (and presumably anything else that uses IFUNC), but should have no other obvious impact. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1807448/+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 1811471] Update Released
The verification of the Stable Release Update for systemd has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1811471 Title: local resolver stub fails to handle multiple TCP dns queries Status in systemd: New Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Trusty: Invalid Status in systemd source package in Xenial: Invalid Status in systemd source package in Bionic: Fix Released Status in systemd source package in Cosmic: Fix Released Status in systemd source package in Disco: Fix Released Bug description: [Impact] The systemd local 'stub' resolver handles all local DNS queries (by default configuration used in Ubuntu), and essentially proxies all requests to its configured upstream DNS resolvers. Most local DNS resolution by applications uses glibc's getaddrinfo() function. This function is configured in various ways by the /etc/resolv.conf file, which tells glibc what nameserver/resolver to contact as well as how to talk to the name server. By default, glibc performs UDP DNS queries, with a single DNS query per UDP packet. The UDP packet size is limited per DNS spec to 512 bytes. For some DNS lookups, a 512 byte UDP packet is not large enough to contain the entire response - for example, an A record lookup with a large number (e.g. 30) of A record addresses. This number of A record entries is possible in some cases of load balancing. When the DNS UDP response size is larger than 512 bytes, the server puts as much response as it can into the DNS UDP response, and marks the "trunacted" flag. This lets glibc know that the DNS UDP packet did not contain the entire response for all the A records. When glibc sees a UDP response that is "trunacted", by default it ignores the contents of that response and issues a new DNS query, using TCP instead of UDP. The TCP packet size has a higher size limit (though see bug 1804487 which is a bug in systemd's max-sizing of TCP DNS packets), and so *should* allow glibc to receive the entire DNS response. However, glibc issues DNS queries for both A and records. When it uses UDP, those DNS queries are separate (i.e. one UDP DNS packet with a single A query, and one UDP DNS packet with a single query). When glibc uses TCP, it puts both DNS queries into a single TCP DNS packet - the RFC refers to this as "pipelining" (https://tools.ietf.org/html/rfc7766#section-6.2.1.1) and states that clients SHOULD do this, and that servers MUST expect to receive pipelined queries and SHOULD respond to all of them. (Technically pipelining can be separate DNS queries, one per TCP packet, but both using the same TCP connection - but the clear intention of pipelining is to improve TCP performance, and putting both DNS queries into a single TCP packet is clearly more performant than using separate TCP packets). Unfortunately, systemd's local stub resolver has only very basic support for TCP DNS, and it handles TCP DNS queries almost identically to UDP DNS queries - it reads the DNS query 2-byte header (containing the length of the query data), reads in the single DNS query data, performs lookup and sends a response to that DNS query, and closes the TCP connection. It does not check for "pipelined" queries in the TCP connection. That would be bad enough, as glibc is (rightly) expecting a response to both its A and queries; however what glibc gets is a TCP connection-reset error. That is because the local systemd stub resolver has closed its TCP socket while input data was still pending (i.e. it never even read the second pipelined DNS query). When the kernel sees unread input bytes in a TCP connection that is closed, it sends a TCP RST to the peer (i.e. glibc) and when the kernel sees the RST, it dumps all data in its socket buffer and passes the ECONNRESET error up to the application. So glibc gets nothing besides a connection reset error. Note also that even if the systemd local stub resolver's socket flushes its input buffer before closing the TCP connection (which will avoid the TCP RST), glibc still expects responses to both its A and queries before systemd closes the TCP connection, and so a simple change to systemd to flush the input buffer is not enough to fix the bug (and would also not actually fix the bug since glibc would never get the response).
[Touch-packages] [Bug 1804487] Update Released
The verification of the Stable Release Update for systemd has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1804487 Title: systemd-resolved has issues when the answer is over 512 bytes with EDNS disabled Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Xenial: Invalid Status in systemd source package in Bionic: Fix Released Status in systemd source package in Cosmic: Fix Released Status in systemd source package in Disco: Fix Committed Status in systemd package in Debian: Fix Released Bug description: [Impact] TCP stub is cutting down the payload to 512 bytes when EDNS is disabled. This makes non-EDNS clients (nslookup) receive a "shortened" answer even when UDP returns a truncated reply for a new TCP query. For instance, - If the client supports EDNS: $ dig +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l 30 - If the client does not support EDNS: $ dig +noedns +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l 29 In the second case, no-EDNS, TCP should provide the complete answer, but it's capped at UDP's size. [Test Case] Query systemd-resolved with a domain name that resolves to multiple (lots.. 30+) A records. A client with EDNS support (dig) will receive all of them, a client without support (nslookup or dig +noedns) will have a truncated list. Using the example above: EDNS: dig +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l non-EDNS: dig +noedns +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l [Regression potential] Minimal. This change only affects TCP requests, and the new size is already used in the code for other requests. [Other Info] Upstream bug: https://github.com/systemd/systemd/issues/10816 Fixed upstream with commit: https://github.com/systemd/systemd/commit/e6eed9445956cfa496e1db933bfd3530db23bfce [Original Description] Querying a domain name that has >512 bytes in records (e.g. 30+ A records), the number of results depends on the DNS client used: - If the client supports EDNS: $ dig +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l 30 - If the client does not support EDNS: $ dig +noedns +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l 29 Normally a client that doesn't support EDNS would receive a truncated reply from the initial UDP connection (limited by the spec to 512 bytes) and a second query would be established via TCP to receive the complete results. In this case, the number of results is the same regardless of the protocol used (29). Upstream bug: https://github.com/systemd/systemd/issues/10816 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1804487/+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 1815172] Re: Black screen on skylake after 18.0 => 18.2 update
Hello Alkis, or anyone else affected, Accepted mesa into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mesa/18.2.2-0ubuntu1~18.04.2 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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: mesa (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-bionic ** Changed in: mesa (Ubuntu Cosmic) Status: New => Fix Committed ** Tags added: verification-needed-cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1815172 Title: Black screen on skylake after 18.0 => 18.2 update Status in Mesa: Confirmed Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Status in linux source package in Bionic: New Status in mesa source package in Bionic: Fix Committed Status in linux source package in Cosmic: New Status in mesa source package in Cosmic: Fix Committed Bug description: Several schools reported black screens after normally updating their Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1. Downgrading mesa fixes the problem. lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:8694]Kernel modules: i915 Unfortunately I can't find a lot of useful information, here are some bits: * systemctl --failed says "gpu-manager" and "lightdm" have failed * Xorg.log is clean: https://termbin.com/6l2b * dmesg too: https://termbin.com/ip4e * It happens on lightdm/MATE, I don't know about Ubuntu GNOME. * If one runs `xinit` from ssh, it fails with: i965: Failed to submit batchbuffer: Invalid argument To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815172/+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 1815172] Please test proposed package
Hello Alkis, or anyone else affected, Accepted mesa into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mesa/18.2.8-0ubuntu0~18.10.2 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-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1815172 Title: Black screen on skylake after 18.0 => 18.2 update Status in Mesa: Confirmed Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Status in linux source package in Bionic: New Status in mesa source package in Bionic: Fix Committed Status in linux source package in Cosmic: New Status in mesa source package in Cosmic: Fix Committed Bug description: Several schools reported black screens after normally updating their Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1. Downgrading mesa fixes the problem. lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:8694]Kernel modules: i915 Unfortunately I can't find a lot of useful information, here are some bits: * systemctl --failed says "gpu-manager" and "lightdm" have failed * Xorg.log is clean: https://termbin.com/6l2b * dmesg too: https://termbin.com/ip4e * It happens on lightdm/MATE, I don't know about Ubuntu GNOME. * If one runs `xinit` from ssh, it fails with: i965: Failed to submit batchbuffer: Invalid argument To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815172/+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 1811225] Please test proposed package
Hello Timo, or anyone else affected, Accepted mesa into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mesa/18.2.8-0ubuntu0~18.10.2 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-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1811225 Title: Mesa 18.2.8 stable release Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Bionic: Fix Committed Status in mesa source package in Cosmic: Fix Committed Bug description: [Impact] Ubuntu 18.10 shipped with mesa 18.2.2, and deserves to get the last point release of the series. This will also be backported to 18.04 as part of the HWE stack update. Upstream changes: 18.2.3 - Different patches for the DirectX9 and DRI state trackers. - Several fixes and workarounds for different games, inlcuding RAGE, Yakuza and The Evil Within, Wolfenstein The Old Blood ARMA 3, or No Mans Sky. - A bunch of fixes for different drivers, including r600, nouveau, radeonsi, anv, radv, virgl, i965, nvc0 or nv50. Worth to mention a fix for GPU hangs in Radeonsi. - State Trackers also get different fixes and corrections. - Finally, fixes for GLSL and NIR are also in this queue. 18.2.4 - Different fixes for different drivers: freedreno, radeonsi, swr, anv and radv. - Also there are fixes for ac, gallium, spirv and blorp. 18.2.5 - A patch for nine state tracker that fixes several crashes using nine's thread_submit feature. There are other patches to other state trackers. - A couple of patches for Meson build system, as well as for autotools. - In the drivers side, there are a couple of fixes for RADV, one regarding subgroups and another regarding conditional rendering. There are also fixes for virgl, r600, and i965. - Finally, the queue contains a couple of fixes for NIR, Wayland, and other components. 18.2.6 - Several patches fixing leaks in glsl, winsys and r600. - Improvements in the scripts that helps in preparing releases. - Added PCI IDs for Amber Lake and Whiskey Lake. - Fixes for radv, anv, i965 and vc4 drivers. - A couple of fixes in NIR backend. - Finally, several fixes in meson build system. 18.2.7 - Several patches fixing leaks in glsl, winsys and r600. - Improvements in the scripts that helps in preparing releases. - Added PCI IDs for Amber Lake and Whiskey Lake. - Fixes for radv, anv, i965 and vc4 drivers. - A couple of fixes in NIR backend. - Finally, several fixes in meson build system. 18.2.8 - Several fixes in Meson build system. - Also several fixes for st/nine subcomponent. - Patch for RADV driver that fixes a hang in Yakuza using DXVK. - There are also fixes for Virgl driver. - Added PCI IDs for VegaM, Vega20 and Vega10. [Test Case] Check on intel/radeon hw that things still work fine. [Regression potential] Mesa stable releases are tested by vendor CI systems, this is the last of the series so should be safe to update to. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1811225/+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 1789924] Re: Missing Intel GPU pci-id's
Hello Timo, or anyone else affected, Accepted mesa into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mesa/18.2.8-0ubuntu0~18.10.2 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-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-done-cosmic ** Tags added: verification-needed-cosmic -- 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/1789924 Title: Missing Intel GPU pci-id's Status in libdrm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in libdrm source package in Bionic: Fix Released Status in linux source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Committed Status in xorg-server source package in Bionic: Fix Released Status in libdrm source package in Cosmic: Fix Released Status in linux source package in Cosmic: Fix Released Status in mesa source package in Cosmic: Fix Committed Status in xorg-server source package in Cosmic: Fix Released Bug description: [Impact] There are some new Intel GPU pci-id's that need to be added to several places: 0x3E98 0x87C0 and to make future additions easier, add platform definitions for Whiskey Lake and Amber Lake too. [Test case] Check that the user session uses the proper driver on these systems. [Regression potential] none, these just add pci-id's and platform definitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1789924/+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 1814818] Re: Skip enslaved devices during boot
Hello Marcelo, or anyone else affected, Accepted initramfs-tools into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/initramfs- tools/0.131ubuntu15.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-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: initramfs-tools (Ubuntu Cosmic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-cosmic -- 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/1814818 Title: Skip enslaved devices during boot Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Cosmic: Fix Committed Bug description: [Impact] In some scenarios, we need to skip enslaved network devices from being brought up in initrd. In order to avoid regressions for other users, the new behaviour is being conditioned to the configuration variable NETWORK_SKIP_ENSLAVED. This mechanism enable us to use it only for the required kernels. The target kernel should be responsible to include the configuration via an initramfs-tools hook. [Test Case] Enslaved network devices shouldn't be brought up when the configuration is set by certain kernels. For any other scenario, such as the generic Ubuntu kernel, the behaviour should not be changed. [Regression Potential] The potential for regressions was vastly reduced by conditioning the new behaviour. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1814818/+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 1815172] Update Released
The verification of the Stable Release Update for mesa has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1815172 Title: Black screen on skylake after 18.0 => 18.2 update Status in Mesa: Confirmed Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Status in linux source package in Bionic: New Status in mesa source package in Bionic: Fix Released Status in linux source package in Cosmic: New Status in mesa source package in Cosmic: Fix Committed Bug description: Several schools reported black screens after normally updating their Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1. Downgrading mesa fixes the problem. lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:8694]Kernel modules: i915 Unfortunately I can't find a lot of useful information, here are some bits: * systemctl --failed says "gpu-manager" and "lightdm" have failed * Xorg.log is clean: https://termbin.com/6l2b * dmesg too: https://termbin.com/ip4e * It happens on lightdm/MATE, I don't know about Ubuntu GNOME. * If one runs `xinit` from ssh, it fails with: i965: Failed to submit batchbuffer: Invalid argument To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815172/+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 1815172] Re: Black screen on skylake after 18.0 => 18.2 update
Hello Alkis, or anyone else affected, Accepted mesa into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mesa/18.2.8-0ubuntu0~18.04.2 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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: mesa (Ubuntu Bionic) Status: Fix Released => Fix Committed ** Tags removed: verification-done-bionic ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1815172 Title: Black screen on skylake after 18.0 => 18.2 update Status in Mesa: Fix Released Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Status in linux source package in Bionic: New Status in mesa source package in Bionic: Fix Committed Status in linux source package in Cosmic: New Status in mesa source package in Cosmic: Fix Committed Bug description: Several schools reported black screens after normally updating their Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1. Downgrading mesa fixes the problem. lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:8694]Kernel modules: i915 Unfortunately I can't find a lot of useful information, here are some bits: * systemctl --failed says "gpu-manager" and "lightdm" have failed * Xorg.log is clean: https://termbin.com/6l2b * dmesg too: https://termbin.com/ip4e * It happens on lightdm/MATE, I don't know about Ubuntu GNOME. * If one runs `xinit` from ssh, it fails with: i965: Failed to submit batchbuffer: Invalid argument To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815172/+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 1789924] Please test proposed package
Hello Timo, or anyone else affected, Accepted mesa into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mesa/18.2.8-0ubuntu0~18.04.2 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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/1789924 Title: Missing Intel GPU pci-id's Status in libdrm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in libdrm source package in Bionic: Fix Released Status in linux source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Committed Status in xorg-server source package in Bionic: Fix Released Status in libdrm source package in Cosmic: Fix Released Status in linux source package in Cosmic: Fix Released Status in mesa source package in Cosmic: Fix Committed Status in xorg-server source package in Cosmic: Fix Released Bug description: [Impact] There are some new Intel GPU pci-id's that need to be added to several places: 0x3E98 0x87C0 and to make future additions easier, add platform definitions for Whiskey Lake and Amber Lake too. [Test case] Check that the user session uses the proper driver on these systems. [Regression potential] none, these just add pci-id's and platform definitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1789924/+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 1811225] Please test proposed package
Hello Timo, or anyone else affected, Accepted mesa into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mesa/18.2.8-0ubuntu0~18.04.2 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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1811225 Title: Mesa 18.2.8 stable release Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Bionic: Fix Committed Status in mesa source package in Cosmic: Fix Committed Bug description: [Impact] Ubuntu 18.10 shipped with mesa 18.2.2, and deserves to get the last point release of the series. This will also be backported to 18.04 as part of the HWE stack update. Upstream changes: 18.2.3 - Different patches for the DirectX9 and DRI state trackers. - Several fixes and workarounds for different games, inlcuding RAGE, Yakuza and The Evil Within, Wolfenstein The Old Blood ARMA 3, or No Mans Sky. - A bunch of fixes for different drivers, including r600, nouveau, radeonsi, anv, radv, virgl, i965, nvc0 or nv50. Worth to mention a fix for GPU hangs in Radeonsi. - State Trackers also get different fixes and corrections. - Finally, fixes for GLSL and NIR are also in this queue. 18.2.4 - Different fixes for different drivers: freedreno, radeonsi, swr, anv and radv. - Also there are fixes for ac, gallium, spirv and blorp. 18.2.5 - A patch for nine state tracker that fixes several crashes using nine's thread_submit feature. There are other patches to other state trackers. - A couple of patches for Meson build system, as well as for autotools. - In the drivers side, there are a couple of fixes for RADV, one regarding subgroups and another regarding conditional rendering. There are also fixes for virgl, r600, and i965. - Finally, the queue contains a couple of fixes for NIR, Wayland, and other components. 18.2.6 - Several patches fixing leaks in glsl, winsys and r600. - Improvements in the scripts that helps in preparing releases. - Added PCI IDs for Amber Lake and Whiskey Lake. - Fixes for radv, anv, i965 and vc4 drivers. - A couple of fixes in NIR backend. - Finally, several fixes in meson build system. 18.2.7 - Several patches fixing leaks in glsl, winsys and r600. - Improvements in the scripts that helps in preparing releases. - Added PCI IDs for Amber Lake and Whiskey Lake. - Fixes for radv, anv, i965 and vc4 drivers. - A couple of fixes in NIR backend. - Finally, several fixes in meson build system. 18.2.8 - Several fixes in Meson build system. - Also several fixes for st/nine subcomponent. - Patch for RADV driver that fixes a hang in Yakuza using DXVK. - There are also fixes for Virgl driver. - Added PCI IDs for VegaM, Vega20 and Vega10. [Test Case] Check on intel/radeon hw that things still work fine. [Regression potential] Mesa stable releases are tested by vendor CI systems, this is the last of the series so should be safe to update to. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1811225/+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 1815125] Re: constant video freezes in firefox with x-x-v-amdgpu 18.1.0
Hello Timo, or anyone else affected, Accepted libx11 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libx11/2:1.6.4-3ubuntu0.2 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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: libx11 (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1815125 Title: constant video freezes in firefox with x-x-v-amdgpu 18.1.0 Status in libx11 package in Ubuntu: Fix Released Status in libx11 source package in Bionic: Fix Committed Bug description: [Impact] There are constant video freezes in firefox (e.g. on youtube) with xf86-video-amdgpu-18.1.0, which is included in the HWE stack in 18.04.2 https://bugs.freedesktop.org/show_bug.cgi?id=107992 [Test case] test firefox with youtube on radeon [Regression potential] it's a single commit from upstream 1.6.7, shouldn't regress anything To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1815125/+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 1777994] Proposed package upload rejected
An upload of libxcb to bionic-proposed has been rejected from the upload queue for the following reason: "Should not use a non-existent Debian version, but instead reflect reality with 1.13-2~ubuntu18.04". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxcb in Ubuntu. https://bugs.launchpad.net/bugs/1777994 Title: the header xcb/xinput.h is missing Status in libxcb package in Ubuntu: Fix Released Status in libxcb source package in Bionic: Fix Committed Bug description: [Impact] Allow Qt 5.12 to be compiled with full input support. This allows applications to be built using complex input devices such as drawing pads. This is used in e.g Krita which KDE builds into a Snap package for distribution. Currently Krita does not work with pen input devices with pressure sensitivity. [Test Case] Install Krita with Qt 5.12 from current Snap and note how pressure sensitivity does not work. [Regression Potential] None that I can see, it's just packaging a few new header files. I suspect this means there should be another package, libxcb-xinput-dev perhaps? I already did sudo apt install "libxcb*dev" to get all related dev packages, but none of them provide xcb/xinput.h. The result is that when building Qt from source, it's necessary to use a copy of this file which Qt provides (qtbase/src/3rdparty/xcb/include/xcb/xinput.h), because it's missing from the system. So if you don't give the option -qt-xcb to configure, then Qt will be built without multi-touch support. https://bugreports.qt.io/browse/QTBUG-69045 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libxcb1-dev 1.13-1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jun 21 08:32:12 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:3802] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 002: ID 04f2:b5da Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80Y7 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic root=ZFS=rpool/ROOT/ubuntu ro SourcePackage: libxcb UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/22/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 5NCN38WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 920-13IKB dmi.modalias: dmi:bvnLENOVO:bvr5NCN38WW:bd02/22/2018:svnLENOVO:pn80Y7:pvrLenovoYOGA920-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA920-13IKB: dmi.product.family: YOGA 920-13IKB dmi.product.name: 80Y7 dmi.product.version: Lenovo YOGA 920-13IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 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/libxcb/+bug/1777994/+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 1802689] Update Released
The verification of the Stable Release Update for kmod has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1802689 Title: Upgrade to kmod (25-1ubuntu1.1) causes Lenovo x240 laptop to hang on boot Status in kmod package in Ubuntu: Fix Released Status in linux package in Ubuntu: Incomplete Status in kmod source package in Xenial: Fix Released Status in linux source package in Xenial: Incomplete Status in kmod source package in Bionic: Fix Released Status in linux source package in Bionic: Incomplete Status in kmod source package in Cosmic: Fix Released Status in linux source package in Cosmic: Incomplete Bug description: After upgrading my Lenovo x240 laptop to kmod (25-1ubuntu1.1), it hangs on boot. After blacklisting i2c_i801 everything works great again. I realize that this was a fix for bug 1786574, and that helps some other folks out. I'm not sure what the right fix is but there's got to be something that works for everyone. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1802689/+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 1850184] Re: losetup -f broken in 2.0.6-1ubuntu2
(eoan-amd64)root@nosferatu:~# apt-get install klibc-utils=2.0.6-1ubuntu2 libklibc=2.0.6-1ubuntu2 (eoan-amd64)root@nosferatu:~# /sbin/losetup -vf /dev/loop6 (eoan-amd64)root@nosferatu:~# /usr/lib/klibc/bin/losetup -vf Loop device is /dev/loop6 loop: can't get info on device /dev/loop6: No such device or address (eoan-amd64)root@nosferatu:~# apt-get install klibc-utils=2.0.6-1ubuntu3 libklibc=2.0.6-1ubuntu3 (eoan-amd64)root@nosferatu:~# /sbin/losetup -vf /dev/loop6 (eoan-amd64)root@nosferatu:~# /usr/lib/klibc/bin/losetup -vf Loop device is /dev/loop6 /dev/loop6 ** Tags removed: verification-needed verification-needed-eoan ** Tags added: verification-done verification-done-eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1850184 Title: losetup -f broken in 2.0.6-1ubuntu2 Status in klibc package in Ubuntu: Fix Released Status in klibc source package in Eoan: Fix Committed Status in klibc source package in Focal: Fix Released Bug description: [Impact] * sudo /usr/lib/klibc/bin/losetup -vf, which appears to be missbuilt, as main(argc) is reset to zero, after ioctl() operations in a function call, quite unexpectadly. [Test Case] * $ sudo /usr/lib/klibc/bin/losetup -vf Loop device is /dev/loop20 loop: can't get info on device /dev/loop20: No such device or address is bad. Note that ioctl() must succeed, thus loop0 device must be configured to trigger the bug. [Regression Potential] * klibc is quite special, as it uses linux kernel headers/assembly. It seems like there is incompatibility between klibc sources, and gcc-9 with linux-5.3 when used to build userspace programmes. * disabling cf-protection and stack-clash-protection did not help. * building with gcc-8 does not exhibit the problem. * the workaround is quite simple in the code, keep a copy of argc to compare to it later in the code. [Other Info] * Original bug report http://autopkgtest.ubuntu.com/packages/c/casper/focal/amd64 https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal/focal/amd64/c/casper/20191025_214555_df8b8@/log.gz ... [ 11.751912] EXT4-fs (sda1): mounting ext2 file system using the ext4 subsystem [ 11.761441] EXT4-fs (sda1): mounted filesystem without journal. Opts: (null) loop: can't get info on device /dev/loop1: No such device or address BusyBox v1.30.1 (Ubuntu 1:1.30.1-4ubuntu4) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) [6n+ mkdir result + set -x + read LINE + grep -e '^--OUT .* BEGIN-- .* --END--$' qemu-output.txt ++ grep -q /rofs result/lsblk.txt grep: result/lsblk.txt: No such file or directory autopkgtest [21:45:45]: test boot: ---] autopkgtest [21:45:45]: test boot: - - - - - - - - - - results - - - - - - - - - - boot FAIL non-zero exit status 2 autopkgtest [21:45:45]: summary boot FAIL non-zero exit status 2 ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1850184/+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 1848522] Re: Backport packages for 18.04.4 HWE stack
Hello Timo, or anyone else affected, Accepted llvm-toolchain-9 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/llvm- toolchain-9/1:9-2~ubuntu18.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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: llvm-toolchain-9 (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- 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/1848522 Title: Backport packages for 18.04.4 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-9 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in libclc source package in Bionic: New Status in libdrm source package in Bionic: In Progress Status in llvm-toolchain-9 source package in Bionic: Fix Committed Status in mesa source package in Bionic: New Status in xorg-server-hwe-18.04 source package in Bionic: New Bug description: [Impact] These are needed for 18.04.4 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-9: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 19.2.x series, so there shouldn't be any regressions left at that point xserver: a new git snapshot (or maybe a point-release) xorg drivers: modest updates, mainly just new ati/amdgpu [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1848522/+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 1848522] Re: Backport packages for 18.04.4 HWE stack
Hello Timo, or anyone else affected, Accepted libdrm into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libdrm/2.4.99-1ubuntu1~18.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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: libdrm (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1848522 Title: Backport packages for 18.04.4 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-9 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in libclc source package in Bionic: New Status in libdrm source package in Bionic: Fix Committed Status in llvm-toolchain-9 source package in Bionic: Fix Committed Status in mesa source package in Bionic: New Status in xorg-server-hwe-18.04 source package in Bionic: New Bug description: [Impact] These are needed for 18.04.4 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-9: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 19.2.x series, so there shouldn't be any regressions left at that point xserver: a new git snapshot (or maybe a point-release) xorg drivers: modest updates, mainly just new ati/amdgpu [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1848522/+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 1845317] Re: Add new pci-id's for CML-S, ICL
Hello Timo, or anyone else affected, Accepted libdrm into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libdrm/2.4.99-1ubuntu1~18.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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: libdrm (Ubuntu Bionic) Status: New => Fix Committed ** Tags removed: verification-done verification-done-bionic ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1845317 Title: Add new pci-id's for CML-S, ICL Status in libdrm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in libdrm source package in Bionic: Fix Committed Status in linux source package in Bionic: Won't Fix Status in linux-oem-osp1 source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Released Bug description: [Impact] Comet Lake (CML) is basically same gen9 GPU as Sky Lake (SKL) (as is KBL, CFL, WHL). There are new CML-S desktop cpu's on the way, and they add three new pci-id's that need to be added across the stack in order to use the GPU properly. There's also one ICL pci-id which was added recently (not in 5.3). [Test case] The proper way to test is to have an actual machine and boot it up with the updated stack, but since these are just pci-id's with no regression potential on older hw, it should be fine to just accept them. [Regression potential] None, just adds new pci-id's to allow the new GPUs to load the proper drivers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1845317/+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 1848522] Re: Backport packages for 18.04.4 HWE stack
Hello Timo, or anyone else affected, Accepted libclc into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libclc/0.2.0+git20190827-1~ubuntu18.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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: libclc (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1848522 Title: Backport packages for 18.04.4 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-9 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Committed Status in libdrm source package in Bionic: Fix Committed Status in llvm-toolchain-9 source package in Bionic: Fix Committed Status in mesa source package in Bionic: New Status in xorg-server-hwe-18.04 source package in Bionic: New Bug description: [Impact] These are needed for 18.04.4 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-9: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 19.2.x series, so there shouldn't be any regressions left at that point xserver: a new git snapshot (or maybe a point-release) xorg drivers: modest updates, mainly just new ati/amdgpu [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1848522/+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
