[Touch-packages] [Bug 1802591] Re: Skip enslaved devices during boot
This bug was fixed in the package initramfs-tools - 0.131ubuntu16 --- initramfs-tools (0.131ubuntu16) disco; urgency=medium * scripts/functions: include a new option to skip enslaved network devices. (LP: #1802591) Include the new variable NETWORK_SKIP_ENSLAVED. When set to a value different than "0", this variable will cause any enslaved network devices to be skipped from the list of netbootable devices. This variable can be set via the configuration files under /etc/initramfs-tools/ or via any configuration file under the initrd directory /conf/conf.d/ via a hook script. -- Marcelo Henrique Cerri Mon, 28 Jan 2019 10:02:53 -0200 ** Changed in: initramfs-tools (Ubuntu) Status: In Progress => Fix Released -- 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/1802591 Title: Skip enslaved devices during boot Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Xenial: Fix Released Status in initramfs-tools source package in Bionic: Fix Released Status in initramfs-tools source package in Cosmic: New Bug description: In order to support live migration in OCI, we need to filter enslaved devices during boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1802591/+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 1754693] Re: Xwayland/Xorg crashed with SIGSEGV in st_renderbuffer_delete() from _mesa_reference_renderbuffer_() [often when running Skype or Slack snaps]
this will be fixed via the hwe backport ** Also affects: xorg-server-hwe-18.04 (Ubuntu) Importance: Undecided Status: New ** Changed in: xorg-server-hwe-18.04 (Ubuntu Disco) Status: New => Invalid ** Changed in: xorg-server-hwe-18.04 (Ubuntu Cosmic) Status: New => Invalid ** Changed in: xorg-server-hwe-18.04 (Ubuntu Bionic) Status: New => Confirmed ** Changed in: xorg-server (Ubuntu Bionic) Status: Confirmed => Won't Fix ** Changed in: xorg-server-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 mesa in Ubuntu. https://bugs.launchpad.net/bugs/1754693 Title: Xwayland/Xorg crashed with SIGSEGV in st_renderbuffer_delete() from _mesa_reference_renderbuffer_() [often when running Skype or Slack snaps] Status in mesa package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in mesa source package in Bionic: Invalid Status in xorg-server source package in Bionic: Won't Fix Status in xorg-server-hwe-18.04 source package in Bionic: Confirmed Status in mesa source package in Cosmic: Invalid Status in xorg-server source package in Cosmic: Fix Committed Status in xorg-server-hwe-18.04 source package in Cosmic: Invalid Status in mesa source package in Disco: Invalid Status in xorg-server source package in Disco: Fix Released Status in xorg-server-hwe-18.04 source package in Disco: Invalid Bug description: https://errors.ubuntu.com/problem/01a80d2110a46f6b6d857ce814079646e695f4ca https://errors.ubuntu.com/problem/a1e7fe67e388164abd73462b322cb79ac2773fae --- Steps to reproduce: Install 'slack' snap: sudo snap install slack --classic Run slack: slack Instacrash. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xwayland 2:1.19.6-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,mousepoll,grid,vpswitch,compiztoolbox,imgpng,gnomecompat,regex,move,place,resize,snap,unitymtgrabhandles,wall,animation,session,expo,workarounds,fade,ezoom,scale,unityshell] CompositorRunning: None CurrentDesktop: GNOME Date: Fri Mar 9 10:31:06 2018 DistUpgraded: 2018-03-06 13:58:47,853 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu EcryptfsInUse: Yes ExecutablePath: /usr/bin/Xwayland ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] MachineType: ASUS All Series ProcCmdline: /usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 4 -listen 5 -displayfd 6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=cd444f9d-672e-4d7b-aea8-657fff0ea1f4 ro quiet splash crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=1 Signal: 6 SourcePackage: xorg-server StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so Title: Xwayland crashed with SIGABRT UpgradeStatus: Upgraded to bionic on 2018-03-06 (2 days ago) UserGroups: adm admin audio cdrom chroot-admin dialout dip egbuild fax floppy fuse libvirt libvirtd lpadmin lxd plugdev sambashare sudo tape video wireshark dmi.bios.date: 10/27/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2702 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M.
[Touch-packages] [Bug 420609] Re: wrong LC_TIME in Italian
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2016-10739 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-19591 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-6488 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to eglibc in Ubuntu. https://bugs.launchpad.net/bugs/420609 Title: wrong LC_TIME in Italian Status in GLibC: Fix Released Status in eglibc package in Ubuntu: Fix Released Status in glibc package in Ubuntu: Invalid Bug description: Accordingly to this file [1], this newspaper [2], and also because I'm Italian, there is an error in the way the date is displayed in linux. The correct format for Italian speakers is: day_name day_number month_name year, HH:MM:SS, time_zone in the LC_TIME date_fmt things are really mixed up and should be changed to: %a %e %b %Y, %H:%M:%S, %Z the file localedata/locales/it_IT needs to be changed, but I can't understand how, since there are only strange codes [1]: ftp://ftp.software.ibm.com/software/globalization/locales/Italy-Italian_Date.pdf [2]: http://www.corriere.it/ To manage notifications about this bug go to: https://bugs.launchpad.net/glibc/+bug/420609/+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 1770271] Re: VegaM support
bionic has 18.2.2 now ** Changed in: mesa (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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/1770271 Title: VegaM support Status in amd: New Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in linux source package in Xenial: Won't Fix Status in mesa source package in Xenial: Won't Fix Status in linux source package in Bionic: New Status in mesa source package in Bionic: Fix Released Bug description: VegaM is a new GPU. Please include support for VegaM in the next LTS (16.04.x and 18.04.x) and non-LTS releases. Kernel support starts here (32 patches): https://patchwork.freedesktop.org/patch/218839/ Mesa support: https://cgit.freedesktop.org/mesa/mesa/commit/?id=d6a66bc8dbcdeed8e87f649bc281de0d60d2f123 https://cgit.freedesktop.org/mesa/mesa/commit/?id=c6f1d360198c52d208645c0ccb5e988cded408e8 https://cgit.freedesktop.org/mesa/mesa/commit/?id=90de03708fa269ad54de881b467f4811e4eef87e To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1770271/+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 1752844] Re: Graphical artifacts with antialiased lines in OpenGL
I'm assuming this is fixed in mesa 18.2.2 in cosmic, which also landed bionic last night if not, feel free to reopen ** Changed in: mesa (Ubuntu) Status: Incomplete => Invalid -- 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/1752844 Title: Graphical artifacts with antialiased lines in OpenGL Status in mesa package in Ubuntu: Invalid Bug description: On Ubuntu 16.04.3, as from the update fixing https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594, antialiased line rendering in applications using Opengl is corrupt. Experienced using Intel GM45. Steps to reproduce: 1) Create an OpenGL application. 2) Enable GL_LINE_SMOOTH and set line width to any value below 1.5. 3) Draw a line (either by shaders or by glBegin). Blender and various games by Kenta Cho (tumiki-figthers, torus- trooper, parsec47, titanion) are affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752844/+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 420609]
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "GNU C Library master sources". The annotated tag, glibc-2.29 has been created at e7c9e41bb2407b0150997b382b49a5f3bb579bf9 (tag) tagging 56c86f5dd516284558e106d04b92875d5b623b7a (commit) replaces glibc-2.28.9000 tagged by Siddhesh Poyarekar on Thu Jan 31 22:24:07 2019 +0530 - Log - The GNU C Library = The GNU C Library version 2.29 is now available. The GNU C Library is used as *the* C library in the GNU system and in GNU/Linux systems, as well as many other systems that use Linux as the kernel. The GNU C Library is primarily designed to be a portable and high performance C library. It follows all relevant standards including ISO C11 and POSIX.1-2008. It is also internationalized and has one of the most complete internationalization interfaces known. The GNU C Library webpage is at http://www.gnu.org/software/libc/ Packages for the 2.29 release may be downloaded from: http://ftpmirror.gnu.org/libc/ http://ftp.gnu.org/gnu/libc/ The mirror list is at http://www.gnu.org/order/ftp.html NEWS for version 2.29 * The getcpu wrapper function has been added, which returns the currently used CPU and NUMA node. This function is Linux-specific. * A new convenience target has been added for distribution maintainers to build and install all locales as directories with files. The new target is run by issuing the following command in your build tree: 'make localedata/install-locale-files', with an optional DESTDIR to set the install root if you wish to install into a non-default configured location. * Optimized generic exp, exp2, log, log2, pow, sinf, cosf, sincosf and tanf. * The reallocarray function is now declared under _DEFAULT_SOURCE, not just for _GNU_SOURCE, to match BSD environments. * For powercp64le ABI, Transactional Lock Elision is now enabled iff kernel indicates that it will abort the transaction prior to entering the kernel (PPC_FEATURE2_HTM_NOSC on hwcap2). On older kernels the transaction is suspended, and this caused some undefined side-effects issues by aborting transactions manually. Glibc avoided it by abort transactions manually on each syscall, but it lead to performance issues on newer kernels where the HTM state is saved and restore lazily (the state being saved even when the process actually does not use HTM). * The functions posix_spawn_file_actions_addchdir_np and posix_spawn_file_actions_addfchdir_np have been added, enabling posix_spawn and posix_spawnp to run the new process in a different directory. These functions are GNU extensions. The function posix_spawn_file_actions_addchdir_np is similar to the Solaris function of the same name. * The popen and system do not run atfork handlers anymore (BZ#17490). Although it is a possible POSIX violation, the POSIX rationale in pthread_atfork documentation regarding atfork handlers is to handle inconsistent mutex state after a fork call in a multi-threaded process. In both popen and system there is no direct access to user-defined mutexes. * Support for the C-SKY ABIV2 running on Linux has been added. This port requires at least binutils-2.32, gcc-9.0, and linux-4.20. Two ABIs are supported: - C-SKY ABIV2 soft-float little-endian - C-SKY ABIV2 hard-float little-endian * strftime's default formatting of a locale's alternative year (%Ey) has been changed to zero-pad the year to a minimum of two digits, like "%y". This improves the display of Japanese era years during the first nine years of a new era, and is expected to be harmless for all other locales (only Japanese locales regularly have alternative year numbers less than 10). Zero-padding can be overridden with the '_' or '-' flags (which are GNU extensions). * As a GNU extension, the '_' and '-' flags can now be applied to "%EY" to control how the year number is formatted; they have the same effect that they would on "%Ey". Deprecated and removed features, and other changes affecting compatibility: * The glibc.tune tunable namespace has been renamed to glibc.cpu and the tunable glibc.tune.cpu has been renamed to glibc.cpu.name. * The type of the pr_uid and pr_gid members of struct elf_prpsinfo, defined in , has been corrected to match the type actually used by the Linux kernel. This affects the size and layout of that structure on MicroBlaze, MIPS (n64 ABI only), Nios II and RISC-V. * For the MIPS n32 ABI, the type of the pr_sigpend and pr_sighold members of struct elf_prstatus, and the pr_flag member of struct elf_prpsinfo, defined in , has been corrected to match the type actually used by the Linux kernel. This affects the size and layout of those structures. * An archaic
[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 1802689] Re: Upgrade to kmod (25-1ubuntu1.1) causes Lenovo x240 laptop to hang on boot
This bug was fixed in the package kmod - 24-1ubuntu3.2 --- kmod (24-1ubuntu3.2) bionic; urgency=medium * Add i2c_i801 back to d/modprobe.d/blacklist.conf again due to regressions. (LP: #1802689, #1802135) -- Michael Hudson-Doyle Tue, 13 Nov 2018 10:54:37 +1300 ** Changed in: kmod (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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 Committed 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 Committed 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 1802135] Re: broken touchpad after i2c-i801 blacklist change
This bug was fixed in the package kmod - 24-1ubuntu3.2 --- kmod (24-1ubuntu3.2) bionic; urgency=medium * Add i2c_i801 back to d/modprobe.d/blacklist.conf again due to regressions. (LP: #1802689, #1802135) -- Michael Hudson-Doyle Tue, 13 Nov 2018 10:54:37 +1300 ** Changed in: kmod (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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
This bug was fixed in the package xserver-xorg-input-evdev-hwe-18.04 - 1:2.10.6-1~18.04.1 --- xserver-xorg-input-evdev-hwe-18.04 (1:2.10.6-1~18.04.1) bionic; urgency=medium * Backport for 18.04.2 HWE stack update. (LP: #1798597) -- Timo Aaltonen Tue, 27 Nov 2018 19:27:15 +0200 -- 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.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
This bug was fixed in the package xserver-xorg-video-qxl-hwe-18.04 - 0.1.5-2build2~18.04.1 --- xserver-xorg-video-qxl-hwe-18.04 (0.1.5-2build2~18.04.1) bionic; urgency=medium * Backport for 18.04.2 HWE stack update. (LP: #1798597) -- Timo Aaltonen Tue, 27 Nov 2018 19:27:27 +0200 ** Changed in: xserver-xorg-video-dummy-hwe-18.04 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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.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
This bug was fixed in the package llvm-toolchain-7 - 1:7-3~ubuntu0.18.04.1 --- llvm-toolchain-7 (1:7-3~ubuntu0.18.04.1) bionic; urgency=medium * Backport to bionic for 18.04.2 HWE stack update. (LP: #1798597) -- Timo Aaltonen Thu, 22 Nov 2018 16:30:14 +0200 ** Changed in: libclc (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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.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
This bug was fixed in the package libclc - 0.2.0+git20180917-2~ubuntu0.18.04.1 --- libclc (0.2.0+git20180917-2~ubuntu0.18.04.1) bionic; urgency=medium * Backport for 18.04.2 HWE stack update. (LP: #1798597) -- Timo Aaltonen Thu, 11 Oct 2018 11:32:39 +0300 ** Changed in: xserver-xorg-input-evdev-hwe-18.04 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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.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
This bug was fixed in the package xorg-hwe-18.04 - 1:7.7+19ubuntu8~18.04.1 --- xorg-hwe-18.04 (1:7.7+19ubuntu8~18.04.1) bionic; urgency=medium * Backport for 18.04.2 HWE stack update. (LP: #1798597) -- Timo Aaltonen Tue, 27 Nov 2018 19:27:10 +0200 ** Changed in: llvm-toolchain-7 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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.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
This bug was fixed in the package xserver-xorg-video-vmware-hwe-18.04 - 1:13.3.0-2build1~18.04.1 --- xserver-xorg-video-vmware-hwe-18.04 (1:13.3.0-2build1~18.04.1) bionic; urgency=medium * Backport for 18.04.2 HWE stack update. (LP: #1798597) -- Timo Aaltonen Tue, 27 Nov 2018 19:27:30 +0200 ** Changed in: xserver-xorg-video-nouveau-hwe-18.04 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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.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
This bug was fixed in the package xserver-xorg-video-dummy-hwe-18.04 - 1:0.3.8-1build3~18.04.1 --- xserver-xorg-video-dummy-hwe-18.04 (1:0.3.8-1build3~18.04.1) bionic; urgency=medium * Backport for 18.04.2 HWE stack update. (LP: #1798597) -- Timo Aaltonen Fri, 14 Dec 2018 14:19:13 +0200 ** Changed in: xorg-hwe-18.04 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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.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
This bug was fixed in the package xserver-xorg-video-fbdev-hwe-18.04 - 1:0.5.0-1ubuntu1~18.04.1 --- xserver-xorg-video-fbdev-hwe-18.04 (1:0.5.0-1ubuntu1~18.04.1) bionic; urgency=medium * Backport for 18.04.2 HWE stack update. (LP: #1798597) -- Timo Aaltonen Tue, 27 Nov 2018 19:27:24 +0200 ** Changed in: xserver-xorg-video-qxl-hwe-18.04 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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.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
This bug was fixed in the package xserver-xorg-video-nouveau-hwe-18.04 - 1:1.0.15-3~18.04.1 --- xserver-xorg-video-nouveau-hwe-18.04 (1:1.0.15-3~18.04.1) bionic; urgency=medium * Backport for 18.04.2 HWE stack update. (LP: #1798597) -- Timo Aaltonen Tue, 27 Nov 2018 19:27:25 +0200 ** Changed in: xserver-xorg-video-fbdev-hwe-18.04 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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.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
This bug was fixed in the package xserver-xorg-video-vesa-hwe-18.04 - 1:2.4.0-1~18.04.1 --- xserver-xorg-video-vesa-hwe-18.04 (1:2.4.0-1~18.04.1) bionic; urgency=medium * Backport for 18.04.2 HWE stack update. (LP: #1798597) -- Timo Aaltonen Tue, 27 Nov 2018 19:27:28 +0200 ** Changed in: xserver-xorg-video-vmware-hwe-18.04 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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.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 1814205] Re: package sudo 1.8.16-0ubuntu1.5 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1
*** This bug is a duplicate of bug 1725628 *** https://bugs.launchpad.net/bugs/1725628 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1725628, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Tags removed: need-duplicate-check ** This bug has been marked a duplicate of bug 1725628 package sudo 1.8.16-0ubuntu1.5 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1814205 Title: package sudo 1.8.16-0ubuntu1.5 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 Status in sudo package in Ubuntu: New Bug description: new to Linux. can understand what the problem. please help me out. thank you ProblemType: Package DistroRelease: Ubuntu 16.04 Package: sudo 1.8.16-0ubuntu1.5 ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.18 AptOrdering: ubuntu-minimal: Remove sudo: Remove NULL: ConfigurePending Architecture: amd64 Date: Thu Jan 31 14:48:49 2019 ErrorMessage: subprocess installed pre-removal script returned error exit status 1 InstallationDate: Installed on 2018-11-20 (71 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SourcePackage: sudo Title: package sudo 1.8.16-0ubuntu1.5 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1814205/+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
This bug was fixed in the package xserver-xorg-video-ati-hwe-18.04 - 1:18.1.0-1~18.04.1 --- xserver-xorg-video-ati-hwe-18.04 (1:18.1.0-1~18.04.1) bionic; urgency=medium * Backport for 18.04.2 HWE stack update. (LP: #1798597) -- Timo Aaltonen Tue, 27 Nov 2018 19:27:23 +0200 ** Changed in: xserver-xorg-video-vesa-hwe-18.04 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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.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
This bug was fixed in the package xserver-xorg-video-amdgpu-hwe-18.04 - 18.1.0-1~18.04.1 --- xserver-xorg-video-amdgpu-hwe-18.04 (18.1.0-1~18.04.1) bionic; urgency=medium * Backport for 18.04.2 HWE stack update. (LP: #1798597) -- Timo Aaltonen Tue, 27 Nov 2018 19:27:21 +0200 ** Changed in: xserver-xorg-video-ati-hwe-18.04 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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.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
This bug was fixed in the package xserver-xorg-input-libinput-hwe-18.04 - 0.28.1-1~18.04.1 --- xserver-xorg-input-libinput-hwe-18.04 (0.28.1-1~18.04.1) bionic; urgency=medium * Backport for 18.04.2 HWE stack update. (LP: #1798597) -- Timo Aaltonen Tue, 27 Nov 2018 19:27:18 +0200 ** Changed in: xserver-xorg-input-synaptics-hwe-18.04 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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.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
This bug was fixed in the package xserver-xorg-input-synaptics-hwe-18.04 - 1.9.1-1ubuntu1~18.04.1 --- xserver-xorg-input-synaptics-hwe-18.04 (1.9.1-1ubuntu1~18.04.1) bionic; urgency=medium * Backport for 18.04.2 HWE stack update. (LP: #1798597) -- Timo Aaltonen Tue, 27 Nov 2018 19:27:19 +0200 ** Changed in: xserver-xorg-video-amdgpu-hwe-18.04 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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.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
This bug was fixed in the package mesa - 18.2.2-0ubuntu1~18.04.1 --- mesa (18.2.2-0ubuntu1~18.04.1) bionic; urgency=medium * Backport for 18.04.2 HWE stack update. (LP: #1798597) * intel-whl-aml-cfl-ids.diff: Add missing i965 pci-id's (LP: #1789924) -- Timo Aaltonen Thu, 29 Nov 2018 00:09:03 +0200 ** Changed in: xorg-server-hwe-18.04 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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.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
This bug was fixed in the package xserver-xorg-input-joystick-hwe-18.04 - 1:1.6.3-1build1~18.04.1 --- xserver-xorg-input-joystick-hwe-18.04 (1:1.6.3-1build1~18.04.1) bionic; urgency=medium * Backport for 18.04.2 HWE stack update. (LP: #1798597) -- Timo Aaltonen Tue, 27 Nov 2018 19:27:17 +0200 ** Changed in: xserver-xorg-input-libinput-hwe-18.04 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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.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
This bug was fixed in the package libdrm - 2.4.95-1~18.04.1 --- libdrm (2.4.95-1~18.04.1) bionic; urgency=medium * Backport to bionic for 18.04.2 HWE stack update. (LP: #1798597) libdrm (2.4.95-1) unstable; urgency=medium [ Timo Aaltonen ] * rules, control: Switch to meson. [ Andreas Boll ] * New upstream release. - Fixes WebGL on Firefox (Closes: #907698). * Update libdrm-amdgpu1.symbols and shlibs. * Drop static libdrm library from libdrm-dev. * Update extend-diff-ignore. libdrm (2.4.94-1) unstable; urgency=medium [ Guido Günther ] * Enable etnaviv on arm64 (Closes: #906915) [ Timo Aaltonen ] * New upstream release. (LP: #1789924) * Update libdrm-amdgpu1.symbols and shlibs. libdrm (2.4.93-1) unstable; urgency=medium * New upstream release. * Update libdrm-freedreno1.symbols and shlibs. libdrm (2.4.92-1) unstable; urgency=medium * New upstream release. * Update libdrm-freedreno1.symbols and shlibs. * control: Update to my Debian address. * Update Vcs-* URLs to point at salsa.debian.org. * Bump debhelper compat to 11. * Bump standards version to 4.1.4. -- Timo Aaltonen Thu, 22 Nov 2018 16:56:49 +0200 ** Changed in: libdrm (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: wayland (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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.2.x series, so there shouldn't be any regressions
[Touch-packages] [Bug 1798597] Re: Backport packages for 18.04.2 HWE stack
This bug was fixed in the package xf86-input-wacom-hwe-18.04 - 1:0.36.1-0ubuntu1~18.04.1 --- xf86-input-wacom-hwe-18.04 (1:0.36.1-0ubuntu1~18.04.1) bionic; urgency=medium * Backport for 18.04.2 HWE stack update. (LP: #1798597) -- Timo Aaltonen Tue, 27 Nov 2018 19:27:14 +0200 ** Changed in: mesa (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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.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
This bug was fixed in the package xorg-server-hwe-18.04 - 2:1.20.1-3ubuntu2.1~18.04.1 --- xorg-server-hwe-18.04 (2:1.20.1-3ubuntu2.1~18.04.1) bionic; urgency=medium * Backport for 18.04.2 HWE stack update. (LP: #1798597) -- Timo Aaltonen Tue, 27 Nov 2018 19:27:12 +0200 ** Changed in: xserver-xorg-input-joystick-hwe-18.04 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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.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
This bug was fixed in the package wayland - 1.16.0-1ubuntu1.1~18.04.1 --- wayland (1.16.0-1ubuntu1.1~18.04.1) bionic; urgency=medium * Backport for 18.04.2 HWE stack update. (LP: #1798597) wayland (1.16.0-1ubuntu1.1) cosmic; urgency=medium * control: Bump Breaks/Replaces again to match reality. (LP: #1781440) -- Timo Aaltonen Tue, 27 Nov 2018 21:43:07 +0200 ** Changed in: xf86-input-wacom-hwe-18.04 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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.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 1560286] Re: Evince displays pdf file fine, but prints colors inverted
This bug was fixed in the package cairo - 1.15.10-2ubuntu0.1 --- cairo (1.15.10-2ubuntu0.1) bionic; urgency=medium * debian/patches/git_adobe_cmykcolors.patch: - "Revert "Correctly decode Adobe CMYK JPEGs in PDF export" From further testing and investigation it appears that many PDF viewers already have a workaround to invert Adobe CMYK JPEGs, so our generated PDFs display incorrectly with those viewers due to double-inversion. (lp: #1560286) -- Sebastien Bacher Tue, 22 Jan 2019 15:17:42 +0100 ** Changed in: cairo (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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 1814205] [NEW] package sudo 1.8.16-0ubuntu1.5 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1
*** This bug is a duplicate of bug 1725628 *** https://bugs.launchpad.net/bugs/1725628 Public bug reported: new to Linux. can understand what the problem. please help me out. thank you ProblemType: Package DistroRelease: Ubuntu 16.04 Package: sudo 1.8.16-0ubuntu1.5 ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.18 AptOrdering: ubuntu-minimal: Remove sudo: Remove NULL: ConfigurePending Architecture: amd64 Date: Thu Jan 31 14:48:49 2019 ErrorMessage: subprocess installed pre-removal script returned error exit status 1 InstallationDate: Installed on 2018-11-20 (71 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SourcePackage: sudo Title: package sudo 1.8.16-0ubuntu1.5 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: sudo (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1814205 Title: package sudo 1.8.16-0ubuntu1.5 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 Status in sudo package in Ubuntu: New Bug description: new to Linux. can understand what the problem. please help me out. thank you ProblemType: Package DistroRelease: Ubuntu 16.04 Package: sudo 1.8.16-0ubuntu1.5 ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.18 AptOrdering: ubuntu-minimal: Remove sudo: Remove NULL: ConfigurePending Architecture: amd64 Date: Thu Jan 31 14:48:49 2019 ErrorMessage: subprocess installed pre-removal script returned error exit status 1 InstallationDate: Installed on 2018-11-20 (71 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SourcePackage: sudo Title: package sudo 1.8.16-0ubuntu1.5 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1814205/+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
This bug was fixed in the package wayland - 1.16.0-1ubuntu1.1~18.04.1 --- wayland (1.16.0-1ubuntu1.1~18.04.1) bionic; urgency=medium * Backport for 18.04.2 HWE stack update. (LP: #1798597) wayland (1.16.0-1ubuntu1.1) cosmic; urgency=medium * control: Bump Breaks/Replaces again to match reality. (LP: #1781440) -- Timo Aaltonen Tue, 27 Nov 2018 21:43:07 +0200 ** Changed in: wayland (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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 Released Status in wayland source package in Cosmic: Fix Released 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/wayland/+bug/1781440/+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
This bug was fixed in the package mesa - 18.2.2-0ubuntu1~18.04.1 --- mesa (18.2.2-0ubuntu1~18.04.1) bionic; urgency=medium * Backport for 18.04.2 HWE stack update. (LP: #1798597) * intel-whl-aml-cfl-ids.diff: Add missing i965 pci-id's (LP: #1789924) -- Timo Aaltonen Thu, 29 Nov 2018 00:09:03 +0200 -- 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 Released 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 1714178] Re: Triple 4K monitor display failed (modesetting driver limited to 8192x8192)
This bug was fixed in the package mesa - 18.2.2-0ubuntu1~18.04.1 --- mesa (18.2.2-0ubuntu1~18.04.1) bionic; urgency=medium * Backport for 18.04.2 HWE stack update. (LP: #1798597) * intel-whl-aml-cfl-ids.diff: Add missing i965 pci-id's (LP: #1789924) -- Timo Aaltonen Thu, 29 Nov 2018 00:09:03 +0200 ** Changed in: mesa (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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/1714178 Title: Triple 4K monitor display failed (modesetting driver limited to 8192x8192) Status in X.Org X server: Unknown Status in linux package in Ubuntu: Triaged Status in mesa package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Triaged Status in linux source package in Bionic: Confirmed Status in mesa source package in Bionic: Fix Released Status in xorg-server source package in Bionic: Confirmed Bug description: Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Summary: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Steps: 1. a laptop with Built-in 4K LCD 2. Cold boot system with Dell Dock connected 3. Connect a 4K monitor to Dock 4. Connect 2nd 4K monitor to Dock 5. Go to [All Settings]=>[Displays] to have the following configuration. Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors) Mirror displays: disable Expected results: Triple monitor display should works without issues Actual results: Triple monitor display failed with Dell Dock Additional information: 1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04 2. Laptop: Dell Precision 5520 3. Dell Business Thunderbolt Dock - TB16 https://goo.gl/vFDjpi WORKAROUND (UBUNTU 18.04+): Log in to "Ubuntu on Wayland" instead of "Ubuntu". --- .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07bf] Subsystem: Dell Device [1028:07bf] InstallationDate: Installed on 2017-08-29 (2 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision 5520 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1714178/+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 1776499] Re: Crash in libegl-mesa0 due to out of bound array access
This bug was fixed in the package mesa - 18.2.2-0ubuntu1~18.04.1 --- mesa (18.2.2-0ubuntu1~18.04.1) bionic; urgency=medium * Backport for 18.04.2 HWE stack update. (LP: #1798597) * intel-whl-aml-cfl-ids.diff: Add missing i965 pci-id's (LP: #1789924) -- Timo Aaltonen Thu, 29 Nov 2018 00:09:03 +0200 ** Changed in: mesa (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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/1776499 Title: Crash in libegl-mesa0 due to out of bound array access Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Bionic: Fix Released Bug description: Crash in libegl-mesa0 due to out of bound array access. Crash is fixed on Mesa master branch with change: https://cgit.freedesktop.org/mesa/mesa/commit/?id=41642bdbca007035772fbfdc311f14daa5510d5d .This bug is to request to include this change in Mesa upgrades in bionic. Please let me know if this change needs to be back ported to other branch so that libegl-mesa0 upgrade in Bionic could pick this change. lsb_release -a Distributor ID: Ubuntu Description:Ubuntu 18.04 LTS Release:18.04 Codename: bionic apt-cache policy libegl-mesa0 libegl-mesa0: Installed: 18.0.0~rc5-1ubuntu1 Candidate: 18.0.0~rc5-1ubuntu1 Version table: *** 18.0.0~rc5-1ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports bionic/main arm64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1776499/+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
This bug was fixed in the package libdrm - 2.4.95-1~18.04.1 --- libdrm (2.4.95-1~18.04.1) bionic; urgency=medium * Backport to bionic for 18.04.2 HWE stack update. (LP: #1798597) libdrm (2.4.95-1) unstable; urgency=medium [ Timo Aaltonen ] * rules, control: Switch to meson. [ Andreas Boll ] * New upstream release. - Fixes WebGL on Firefox (Closes: #907698). * Update libdrm-amdgpu1.symbols and shlibs. * Drop static libdrm library from libdrm-dev. * Update extend-diff-ignore. libdrm (2.4.94-1) unstable; urgency=medium [ Guido Günther ] * Enable etnaviv on arm64 (Closes: #906915) [ Timo Aaltonen ] * New upstream release. (LP: #1789924) * Update libdrm-amdgpu1.symbols and shlibs. libdrm (2.4.93-1) unstable; urgency=medium * New upstream release. * Update libdrm-freedreno1.symbols and shlibs. libdrm (2.4.92-1) unstable; urgency=medium * New upstream release. * Update libdrm-freedreno1.symbols and shlibs. * control: Update to my Debian address. * Update Vcs-* URLs to point at salsa.debian.org. * Bump debhelper compat to 11. * Bump standards version to 4.1.4. -- Timo Aaltonen Thu, 22 Nov 2018 16:56:49 +0200 ** Changed in: libdrm (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: mesa (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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 Released 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 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 1814197] Re: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is
Thanks. So the problem does seem to be with the Nvidia driver. You might want to start by trying to uninstall "i386" packages like: sudo dpkg -P libnvidia-gl-390:i386 libgl1-mesa-dri:i386 and if that doesn't clear it up then: sudo apt --fix-broken install -- 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/1814197 Title: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc /libwayland-server0/changelog.Debian.gz', which is different from other instances of package libwayland-server0:i386 Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in wayland package in Ubuntu: Incomplete Bug description: Trying to install nvidia-driver-390 on Dell XPS 15 6570 ProblemType: Package DistroRelease: Ubuntu 18.10 Package: libwayland-server0 1.16.0-1ubuntu1.1 ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20 Uname: Linux 4.18.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.87 Tue Aug 21 12:33:05 PDT 2018 GCC version: gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1) ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CompositorRunning: None Date: Thu Jan 31 18:32:20 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.18.0-14-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-13-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-14-generic, x86_64: installed DuplicateSignature: package:libwayland-server0:1.16.0-1ubuntu1.1 Unpacking libelf1:i386 (0.170-0.5.0ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-dAqKVk/12-libelf1_0.170-0.5.0ubuntu1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libelf1/changelog.Debian.gz', which is different from other instances of package libelf1:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is different from other instances of package libwayland-server0:i386 GraphicsCard: Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:087c] Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:087c] InstallationDate: Installed on 2019-01-31 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. XPS 15 9570 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-14-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.7rc1, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.2 SourcePackage: wayland Title: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is different from other instances of package libwayland-server0:i386 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 0HWTMH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd12/25/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0HWTMH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-0ubuntu0.18.10.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1814197/+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 1758721] Re: [nouveau] Screen corruption after suspend
[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Expired -- 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/1758721 Title: [nouveau] Screen corruption after suspend Status in mesa package in Ubuntu: Expired Status in xorg-server package in Ubuntu: Expired Bug description: I consistently get screen corruption after a suspend in the wake-up screen (the one with the arrows you drag) and login screen. Sometimes I have trouble dragging the wake-up screen to get the login screen. Sometimes I am able to get the login screen (although all text is corrupted) and login back into my session. After login screen corruption is inconsistent, at times the whole session is corrupted (see attachment), sometimes only text is corrupted (icons, desktop is okay) and sometimes there is no corruption. One workaround that seems to avoid the situation is to disable all automatic suspend options in the power settings. Note that I have recently upgraded from 16.04 LTS to 18.04 LTS Beta (1?). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Mar 25 19:18:25 2018 DistUpgraded: 2018-03-25 11:25:40,806 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT218M [NVS 3100M] [10de:0a6c] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GT218M [NVS 3100M] [103c:172b] InstallationDate: Installed on 2017-01-14 (435 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard HP EliteBook 8440p PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic root=UUID=a16d7c26-68e8-4cec-bcdc-c814a96b448d ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-03-25 (0 days ago) dmi.bios.date: 06/11/2012 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CCU Ver. F.22 dmi.board.name: 172B dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 30.33 dmi.chassis.asset.tag: CZC02417F8 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CCUVer.F.22:bd06/11/2012:svnHewlett-Packard:pnHPEliteBook8440p:pvr:rvnHewlett-Packard:rn172B:rvrKBCVersion30.33:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8440p dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 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-1ubuntu3 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 xserver.bootTime: Fri Mar 23 14:06:10 2018 xserver.configfile: default xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1758721/+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 1758721] Re: [nouveau] Screen corruption after suspend
[Expired for mesa (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mesa (Ubuntu) Status: Incomplete => Expired -- 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/1758721 Title: [nouveau] Screen corruption after suspend Status in mesa package in Ubuntu: Expired Status in xorg-server package in Ubuntu: Expired Bug description: I consistently get screen corruption after a suspend in the wake-up screen (the one with the arrows you drag) and login screen. Sometimes I have trouble dragging the wake-up screen to get the login screen. Sometimes I am able to get the login screen (although all text is corrupted) and login back into my session. After login screen corruption is inconsistent, at times the whole session is corrupted (see attachment), sometimes only text is corrupted (icons, desktop is okay) and sometimes there is no corruption. One workaround that seems to avoid the situation is to disable all automatic suspend options in the power settings. Note that I have recently upgraded from 16.04 LTS to 18.04 LTS Beta (1?). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Mar 25 19:18:25 2018 DistUpgraded: 2018-03-25 11:25:40,806 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT218M [NVS 3100M] [10de:0a6c] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GT218M [NVS 3100M] [103c:172b] InstallationDate: Installed on 2017-01-14 (435 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard HP EliteBook 8440p PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic root=UUID=a16d7c26-68e8-4cec-bcdc-c814a96b448d ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-03-25 (0 days ago) dmi.bios.date: 06/11/2012 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CCU Ver. F.22 dmi.board.name: 172B dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 30.33 dmi.chassis.asset.tag: CZC02417F8 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CCUVer.F.22:bd06/11/2012:svnHewlett-Packard:pnHPEliteBook8440p:pvr:rvnHewlett-Packard:rn172B:rvrKBCVersion30.33:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8440p dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 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-1ubuntu3 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 xserver.bootTime: Fri Mar 23 14:06:10 2018 xserver.configfile: default xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1758721/+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 1805040] Re: Apparently "Readline6" is not in Ubuntu 18.4.1 LTS but I need it
This can't be a good answer. For external software providers, if they want to ship a program linked against libreadline, and support it on multiple LTS versions of Ubuntu (from 14.04 to 18.04), this makes it impossible for them. There's no way they can force a link against libreadline5, unless you provide a libreadline5-dev (which you don't, on nay of those versions - the only libreadline-dev will link against libreadline6 on 14.04 and 16.04, and against libreadline7 on 18.04. So there's no way to link a single executable against libreadline-dev and have it run on all of 14.04, 16.04 and 18.04. You really _must_ ship a libreadline6 in addition to libreadline5. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to readline6 in Ubuntu. https://bugs.launchpad.net/bugs/1805040 Title: Apparently "Readline6" is not in Ubuntu 18.4.1 LTS but I need it Status in readline6 package in Ubuntu: New Bug description: I use applications that require Readline6. But Ubuntu 18.4.1 does not seem to have it - how can Iget it? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/readline6/+bug/1805040/+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 1812095] Re: console login loop after entering username followed by RETURN
Possible dup with https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813683 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1812095 Title: console login loop after entering username followed by RETURN Status in shadow package in Ubuntu: Confirmed Bug description: login: password: Just do nothing. About two seconds later ... login: password: login: password: login: password: After this being displayed three times: "Too many failure" or so and login is restarting. You cant login at all. Only solution: clear the password for the account you want to login with. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: login 1:4.5-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20 Uname: Linux 4.18.0-14-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Jan 16 19:34:30 2019 InstallationDate: Installed on 2011-10-19 (2645 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: shadow UpgradeStatus: Upgraded to cosmic on 2018-11-03 (74 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1812095/+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 1814197] Re: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is
frederick@graphMetrix-1:~$ sudo apt install --reinstall libwayland-server0 [sudo] password for frederick: Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: libgl1-mesa-dri:i386 : Depends: libelf1:i386 (>= 0.142) but it is not going to be installed libnvidia-gl-390:i386 : Depends: libwayland-client0:i386 (>= 1.3.92) but it is not going to be installed Depends: libwayland-server0:i386 (>= 1.2.0) but it is not going to be installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). -- 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/1814197 Title: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc /libwayland-server0/changelog.Debian.gz', which is different from other instances of package libwayland-server0:i386 Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in wayland package in Ubuntu: Incomplete Bug description: Trying to install nvidia-driver-390 on Dell XPS 15 6570 ProblemType: Package DistroRelease: Ubuntu 18.10 Package: libwayland-server0 1.16.0-1ubuntu1.1 ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20 Uname: Linux 4.18.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.87 Tue Aug 21 12:33:05 PDT 2018 GCC version: gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1) ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CompositorRunning: None Date: Thu Jan 31 18:32:20 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.18.0-14-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-13-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-14-generic, x86_64: installed DuplicateSignature: package:libwayland-server0:1.16.0-1ubuntu1.1 Unpacking libelf1:i386 (0.170-0.5.0ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-dAqKVk/12-libelf1_0.170-0.5.0ubuntu1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libelf1/changelog.Debian.gz', which is different from other instances of package libelf1:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is different from other instances of package libwayland-server0:i386 GraphicsCard: Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:087c] Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:087c] InstallationDate: Installed on 2019-01-31 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. XPS 15 9570 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-14-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.7rc1, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.2 SourcePackage: wayland Title: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is different from other instances of package libwayland-server0:i386 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 0HWTMH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd12/25/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0HWTMH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-0ubuntu0.18.10.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau:
[Touch-packages] [Bug 1814197] Re: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is
Hmm, thanks. That list shows the problematic package libwayland- server0:i386 is not installed (any more). But you do have the correct one libwayland-server0:amd64. Can you please run this command: sudo apt install --reinstall libwayland-server0 and send us the output you see? -- 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/1814197 Title: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc /libwayland-server0/changelog.Debian.gz', which is different from other instances of package libwayland-server0:i386 Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in wayland package in Ubuntu: Incomplete Bug description: Trying to install nvidia-driver-390 on Dell XPS 15 6570 ProblemType: Package DistroRelease: Ubuntu 18.10 Package: libwayland-server0 1.16.0-1ubuntu1.1 ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20 Uname: Linux 4.18.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.87 Tue Aug 21 12:33:05 PDT 2018 GCC version: gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1) ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CompositorRunning: None Date: Thu Jan 31 18:32:20 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.18.0-14-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-13-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-14-generic, x86_64: installed DuplicateSignature: package:libwayland-server0:1.16.0-1ubuntu1.1 Unpacking libelf1:i386 (0.170-0.5.0ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-dAqKVk/12-libelf1_0.170-0.5.0ubuntu1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libelf1/changelog.Debian.gz', which is different from other instances of package libelf1:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is different from other instances of package libwayland-server0:i386 GraphicsCard: Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:087c] Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:087c] InstallationDate: Installed on 2019-01-31 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. XPS 15 9570 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-14-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.7rc1, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.2 SourcePackage: wayland Title: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is different from other instances of package libwayland-server0:i386 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 0HWTMH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd12/25/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0HWTMH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-0ubuntu0.18.10.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1814197/+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 1814197] Re: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is
It looks like maybe the Nvidia driver has pulled in some i386 dependencies despite being amd64 itself. ** Also affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Incomplete -- 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/1814197 Title: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc /libwayland-server0/changelog.Debian.gz', which is different from other instances of package libwayland-server0:i386 Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in wayland package in Ubuntu: Incomplete Bug description: Trying to install nvidia-driver-390 on Dell XPS 15 6570 ProblemType: Package DistroRelease: Ubuntu 18.10 Package: libwayland-server0 1.16.0-1ubuntu1.1 ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20 Uname: Linux 4.18.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.87 Tue Aug 21 12:33:05 PDT 2018 GCC version: gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1) ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CompositorRunning: None Date: Thu Jan 31 18:32:20 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.18.0-14-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-13-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-14-generic, x86_64: installed DuplicateSignature: package:libwayland-server0:1.16.0-1ubuntu1.1 Unpacking libelf1:i386 (0.170-0.5.0ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-dAqKVk/12-libelf1_0.170-0.5.0ubuntu1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libelf1/changelog.Debian.gz', which is different from other instances of package libelf1:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is different from other instances of package libwayland-server0:i386 GraphicsCard: Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:087c] Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:087c] InstallationDate: Installed on 2019-01-31 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. XPS 15 9570 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-14-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.7rc1, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.2 SourcePackage: wayland Title: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is different from other instances of package libwayland-server0:i386 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 0HWTMH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd12/25/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0HWTMH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-0ubuntu0.18.10.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1814197/+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 1814197] Re: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is
** Attachment added: "Thanks Daniel!" https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1814197/+attachment/5234949/+files/allpackages.txt -- 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/1814197 Title: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc /libwayland-server0/changelog.Debian.gz', which is different from other instances of package libwayland-server0:i386 Status in wayland package in Ubuntu: Incomplete Bug description: Trying to install nvidia-driver-390 on Dell XPS 15 6570 ProblemType: Package DistroRelease: Ubuntu 18.10 Package: libwayland-server0 1.16.0-1ubuntu1.1 ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20 Uname: Linux 4.18.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.87 Tue Aug 21 12:33:05 PDT 2018 GCC version: gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1) ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CompositorRunning: None Date: Thu Jan 31 18:32:20 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.18.0-14-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-13-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-14-generic, x86_64: installed DuplicateSignature: package:libwayland-server0:1.16.0-1ubuntu1.1 Unpacking libelf1:i386 (0.170-0.5.0ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-dAqKVk/12-libelf1_0.170-0.5.0ubuntu1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libelf1/changelog.Debian.gz', which is different from other instances of package libelf1:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is different from other instances of package libwayland-server0:i386 GraphicsCard: Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:087c] Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:087c] InstallationDate: Installed on 2019-01-31 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. XPS 15 9570 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-14-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.7rc1, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.2 SourcePackage: wayland Title: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is different from other instances of package libwayland-server0:i386 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 0HWTMH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd12/25/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0HWTMH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-0ubuntu0.18.10.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1814197/+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 1814197] Re: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is
Can you please run this command: dpkg -l > allpackages.txt and then send us the resulting file 'allpackages.txt'? ** Changed in: wayland (Ubuntu) Status: New => Incomplete -- 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/1814197 Title: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc /libwayland-server0/changelog.Debian.gz', which is different from other instances of package libwayland-server0:i386 Status in wayland package in Ubuntu: Incomplete Bug description: Trying to install nvidia-driver-390 on Dell XPS 15 6570 ProblemType: Package DistroRelease: Ubuntu 18.10 Package: libwayland-server0 1.16.0-1ubuntu1.1 ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20 Uname: Linux 4.18.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.87 Tue Aug 21 12:33:05 PDT 2018 GCC version: gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1) ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CompositorRunning: None Date: Thu Jan 31 18:32:20 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.18.0-14-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-13-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-14-generic, x86_64: installed DuplicateSignature: package:libwayland-server0:1.16.0-1ubuntu1.1 Unpacking libelf1:i386 (0.170-0.5.0ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-dAqKVk/12-libelf1_0.170-0.5.0ubuntu1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libelf1/changelog.Debian.gz', which is different from other instances of package libelf1:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is different from other instances of package libwayland-server0:i386 GraphicsCard: Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:087c] Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:087c] InstallationDate: Installed on 2019-01-31 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. XPS 15 9570 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-14-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.7rc1, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.2 SourcePackage: wayland Title: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is different from other instances of package libwayland-server0:i386 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 0HWTMH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd12/25/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0HWTMH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-0ubuntu0.18.10.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1814197/+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 1814197] Re: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is
** Tags removed: need-duplicate-check -- 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/1814197 Title: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc /libwayland-server0/changelog.Debian.gz', which is different from other instances of package libwayland-server0:i386 Status in wayland package in Ubuntu: Incomplete Bug description: Trying to install nvidia-driver-390 on Dell XPS 15 6570 ProblemType: Package DistroRelease: Ubuntu 18.10 Package: libwayland-server0 1.16.0-1ubuntu1.1 ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20 Uname: Linux 4.18.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.87 Tue Aug 21 12:33:05 PDT 2018 GCC version: gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1) ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CompositorRunning: None Date: Thu Jan 31 18:32:20 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.18.0-14-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-13-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-14-generic, x86_64: installed DuplicateSignature: package:libwayland-server0:1.16.0-1ubuntu1.1 Unpacking libelf1:i386 (0.170-0.5.0ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-dAqKVk/12-libelf1_0.170-0.5.0ubuntu1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libelf1/changelog.Debian.gz', which is different from other instances of package libelf1:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is different from other instances of package libwayland-server0:i386 GraphicsCard: Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:087c] Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:087c] InstallationDate: Installed on 2019-01-31 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. XPS 15 9570 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-14-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.7rc1, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.2 SourcePackage: wayland Title: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is different from other instances of package libwayland-server0:i386 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 0HWTMH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd12/25/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0HWTMH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-0ubuntu0.18.10.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1814197/+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 1814197] [NEW] package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which i
Public bug reported: Trying to install nvidia-driver-390 on Dell XPS 15 6570 ProblemType: Package DistroRelease: Ubuntu 18.10 Package: libwayland-server0 1.16.0-1ubuntu1.1 ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20 Uname: Linux 4.18.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.87 Tue Aug 21 12:33:05 PDT 2018 GCC version: gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1) ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CompositorRunning: None Date: Thu Jan 31 18:32:20 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.18.0-14-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-13-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-14-generic, x86_64: installed DuplicateSignature: package:libwayland-server0:1.16.0-1ubuntu1.1 Unpacking libelf1:i386 (0.170-0.5.0ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-dAqKVk/12-libelf1_0.170-0.5.0ubuntu1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libelf1/changelog.Debian.gz', which is different from other instances of package libelf1:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is different from other instances of package libwayland-server0:i386 GraphicsCard: Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:087c] Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:087c] InstallationDate: Installed on 2019-01-31 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. XPS 15 9570 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-14-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.7rc1, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.2 SourcePackage: wayland Title: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is different from other instances of package libwayland-server0:i386 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 0HWTMH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd12/25/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0HWTMH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-0ubuntu0.18.10.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 ** Affects: wayland (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package cosmic package-conflict ubuntu -- 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/1814197 Title: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc /libwayland-server0/changelog.Debian.gz', which is different from other instances of package libwayland-server0:i386 Status in wayland package in Ubuntu: New Bug description: Trying to install nvidia-driver-390 on Dell XPS 15 6570 ProblemType: Package DistroRelease: Ubuntu 18.10 Package: libwayland-server0 1.16.0-1ubuntu1.1 ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20 Uname: Linux 4.18.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.87 Tue Aug 21 12:33:05 PDT 2018 GCC version: gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1) ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CompositorRunning: None Date: Thu Jan 31 18:32:20
[Touch-packages] [Bug 1813921] Re: The ubuntu doesn't work when there is a second monitor and the user locks the screen.
*** This bug is a duplicate of bug 1813663 *** https://bugs.launchpad.net/bugs/1813663 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1813663, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** This bug has been marked a duplicate of bug 1813663 External monitors does not work anymore 4.15.0-44 -- 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/1813921 Title: The ubuntu doesn't work when there is a second monitor and the user locks the screen. Status in linux package in Ubuntu: New Bug description: Initial Setup to reproduce the first issue: 1. Have the last Ubuntu (18.04) updated. 2. Have a second monitor. First bug Description: 1. Try to starts the Ubuntu. Actual Results: 1. The Ubuntu can't start. Initial Setup to reproduce the second issue: 1. Have the last Ubuntu (18.04) updated. 2. Have a second monitor ready (not connected) to connect. Second bug description: 1. With the Ubuntu started, connect the second monitor and then lock the screen. 2. Try to unlock Ubuntu. Actual Results: 2. The mouse and keyboard don't work and the screen can't be unlocked. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 Uname: Linux 4.15.0-44-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jan 30 07:16:30 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c] MachineType: LENOVO 20B7008BBR ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-44-generic root=UUID=e1c74834-7cc4-44fb-94a2-06206608a746 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/03/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GJET79WW (2.29 ) dmi.board.asset.tag: Not Available dmi.board.name: 20B7008BBR dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET79WW(2.29):bd09/03/2014:svnLENOVO:pn20B7008BBR:pvrThinkPadT440:rvnLENOVO:rn20B7008BBR:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440 dmi.product.name: 20B7008BBR dmi.product.version: ThinkPad T440 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 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 xserver.bootTime: Tue Jan 29 14:59:13 2019 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813921/+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 1814174] Re: Xorg crash report after resume
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Tags added: bionic ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1814174 Title: Xorg crash report after resume Status in xorg-server package in Ubuntu: Incomplete Bug description: Crash Report when resuming from sleep. Similar to https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1586223 This is a Sager NP8278 (Clevo P170SM-A) laptop with an Nvidia GeForce GTX 970M, driver 390.77 The crash log doesn't have much info in it IMO, but I uploaded here http://s000.tinyupload.com/?file_id=09497843963607449328 Output from sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date 4.6.5 11/14/2014 Output from uname -a Linux dksager2linux 4.15.0-44-generic #47-Ubuntu SMP Mon Jan 14 11:26:59 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Output from cat /etc/*ase DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" NAME="Ubuntu" VERSION="18.04.1 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.1 LTS" VERSION_ID="18.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=bionic UBUNTU_CODENAME=bionic Output from lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller (rev 06) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06) 00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06) 00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06) 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05) 00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05) 00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 05) 00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d5) 00:1c.1 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #2 (rev d5) 00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #3 (rev d5) 00:1c.3 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #4 (rev d5) 00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 05) 00:1f.0 ISA bridge: Intel Corporation HM87 Express LPC Controller (rev 05) 00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 05) 00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 05) 01:00.0 VGA compatible controller: NVIDIA Corporation GM204M [GeForce GTX 970M] (rev a1) 03:00.0 PCI bridge: Texas Instruments XIO2213A/B/XIO2221 PCI Express to PCI Bridge [Cheetah Express] (rev 01) 04:00.0 FireWire (IEEE 1394): Texas Instruments XIO2213A/B/XIO2221 IEEE-1394b OHCI Controller [Cheetah Express] (rev 01) 05:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411 PCI Express Card Reader (rev 01) 05:00.2 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0a) 06:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb) The nuisance inspired me to create a script on the desktop called ClearCrashLog.sh (info I got from a YouTube video) ls /var/crash sudo rm /var/crash/* It's
[Touch-packages] [Bug 1814125] Re: [nvidia] gnome-shell eats 100% cpu when seconds display is on and screen is locked
This might be a different issue, but your kernel log is also getting flooded with error messages about the touchpad(?) https://launchpadlibrarian.net/409195699/CurrentDmesg.txt ** Summary changed: - gnome-shell eats 100% cpu when seconds display is on and screen is locked + [nvidia] gnome-shell eats 100% cpu when seconds display is on and screen is locked ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Tags added: nvidia -- 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/1814125 Title: [nvidia] gnome-shell eats 100% cpu when seconds display is on and screen is locked Status in gnome-shell package in Ubuntu: Incomplete Bug description: on my laptop (xiaomi notebook pro), ubuntu 18.10 amd64, standart ubuntu desktop (gnome-shell), no application running just activate second display in gnome tweak, let it lock itself the fan is going fast, simply moving the mouse and the fan slow down. wrote a simple script to append a top every minut in a log file, show that gnome-shell consumes 100% when locked. workaround : disabling second displaying and no more CPU usage / fan noise when locked. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 415.27 Thu Dec 20 17:25:03 CST 2018 GCC version: gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1) ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 31 16:19:16 2019 DistUpgraded: 2018-12-30 21:42:17,971 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 415.27, 4.18.0-13-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Xiaomi UHD Graphics 620 [1d72:1701] Subsystem: Xiaomi Mi Notebook Pro [GeForce MX150] [1d72:1701] InstallationDate: Installed on 2018-06-08 (236 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Timi TM1701 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=174e8747-a737-411b-bfaf-4e6795426fea ro quiet splash nouveau.runpm=0 vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to cosmic on 2018-12-30 (31 days ago) dmi.bios.date: 10/13/2017 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: XMAKB5R0P0502 dmi.board.asset.tag: Any dmi.board.name: TM1701 dmi.board.vendor: Timi dmi.board.version: MP dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Timi dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrXMAKB5R0P0502:bd10/13/2017:svnTimi:pnTM1701:pvr:rvnTimi:rnTM1701:rvrMP:cvnTimi:ct10:cvrChassisVersion: dmi.product.family: Timibook dmi.product.name: TM1701 dmi.sys.vendor: Timi version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1814125/+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 1814162] Re: Xorg freeze
*** This bug is a duplicate of bug 1813663 *** https://bugs.launchpad.net/bugs/1813663 ** Package changed: xorg (Ubuntu) => linux (Ubuntu) -- 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/1814162 Title: Xorg freeze Status in linux package in Ubuntu: Confirmed Bug description: When I lock my machine on the latest ubuntu version 4.15.0-44-generic, it turns my display completely black and unresponsive. This is only when I have my dock (with external displays in). After it freezes however, removing the dock has no effect. Booting back into 4.15.0-43-generic has fixed the problem so this is a regression bug. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 31 14:25:01 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:081c] InstallationDate: Installed on 2018-10-17 (106 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Latitude 7490 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.2 dmi.board.name: 0KP0FT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.2:bd11/26/2018:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0KP0FT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7490 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 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/linux/+bug/1814162/+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 1814098] Re: Favorites cant be added or removed
If you have any gnome-shell extensions loaded, please uninstall (don't just disable) them and tell us if that fixes the problem. Please also run: apport-collect 1814098 because this bug is missing some information since it was reported to the wrong component. ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1814098 Title: Favorites cant be added or removed Status in gnome-shell package in Ubuntu: Incomplete Bug description: Apps randomly stay on the sidebar even tho they are not added to favorites, also favorites cant be removed. Video: https://www.youtube.com/watch?v=5LUx3ljV83I Recreation: i cant, but restarting the system allways fixes it. Also the sidebar appears on the lockscreen ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 31 11:43:49 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:39fa] InstallationDate: Installed on 2018-12-01 (60 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0cf3:e500 Atheros Communications, Inc. Bus 001 Device 002: ID 04f2:b5d9 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81BL ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/12/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 4QCN41WW(V2.05) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 520S-14IKB dmi.modalias: dmi:bvnLENOVO:bvr4QCN41WW(V2.05):bd12/12/2017:svnLENOVO:pn81BL:pvrLenovoideapad520S-14IKB:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad520S-14IKB: dmi.product.family: ideapad 520S-14IKB dmi.product.name: 81BL dmi.product.sku: LENOVO_MT_81BL_BU_idea_FM_ideapad 520S-14IKB dmi.product.version: Lenovo ideapad 520S-14IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1814098/+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 1813587] Re: libunistring ftbfs on 18.04 LTS
** Changed in: libunistring (Debian) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libunistring in Ubuntu. https://bugs.launchpad.net/bugs/1813587 Title: libunistring ftbfs on 18.04 LTS Status in libunistring package in Ubuntu: Fix Released Status in libunistring source package in Bionic: In Progress Status in libunistring package in Debian: Won't Fix Bug description: Impact -- libunistring doesn't build from source which means someone would need to fix that problem before fixing any bugs in the libunistring package for Ubuntu 18.04 LTS. Test Case - Does libunistring build successfully? Regression Potential We are simply backporting the workaround we applied in Ubuntu 18.10. Original Bug Report --- according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html libunistring ftbfs. FAIL: test-thread_create glthread_create failed FAIL test-thread_create (exit status: 1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunistring/+bug/1813587/+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 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK
** Changed in: gnome-control-center (Ubuntu Bionic) Status: Fix Committed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1745032 Title: AC adapter status not detected on Asus ZenBook UX410UAK Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in upower package in Ubuntu: Fix Released Status in gnome-control-center source package in Bionic: In Progress Status in gnome-shell source package in Bionic: Fix Committed Status in linux source package in Bionic: Fix Committed Status in upower source package in Bionic: Fix Committed Status in gnome-control-center source package in Cosmic: Fix Committed Status in gnome-shell source package in Cosmic: Fix Committed Status in linux source package in Cosmic: Triaged Status in upower source package in Cosmic: Fix Committed Bug description: === SRU Justification === [Impact] Some Asus laptops report "discharging" when the battery is full and AC is plugged [Test] Charge battery to full, the issue appears. Users report with the patch the behaviour is correct. [Fix] The discharge rate is 0 on those machines. Use that to detect the wrong status report. [Regression Potential] Low. The quirk uses strict DMI to match affected systems. === Original Bug Report === The AC adapter status is incorrectly reported when the battery is fully charged. It always shows as if the adapter is not plugged in. If the battery is drained for a while, the adapter status is shown correctly (both connects and disconnects are shown). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-31-generic 4.13.0-31.34 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abarto 1388 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 23 18:26:18 2018 InstallationDate: Installed on 2018-01-23 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-31-generic N/A linux-backports-modules-4.13.0-31-generic N/A linux-firmware 1.169.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1745032/+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 1812095] Re: console login loop after entering username followed by RETURN
Ubuntu server here on a box that serves as NAS. I would have been toast had I not already setup SSH. Confirmed issue with both: linux-image-4.15.0-44-generic linux-image-4.15.0-45-generic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1812095 Title: console login loop after entering username followed by RETURN Status in shadow package in Ubuntu: Confirmed Bug description: login: password: Just do nothing. About two seconds later ... login: password: login: password: login: password: After this being displayed three times: "Too many failure" or so and login is restarting. You cant login at all. Only solution: clear the password for the account you want to login with. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: login 1:4.5-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20 Uname: Linux 4.18.0-14-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Jan 16 19:34:30 2019 InstallationDate: Installed on 2011-10-19 (2645 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: shadow UpgradeStatus: Upgraded to cosmic on 2018-11-03 (74 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1812095/+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 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK
Augustin, What version of ubuntu have you tested? Can you please paste here the output of the command apt-cache policy linux-image-generic upower gnome-control-center gnome-shell Are you also using a fixed kernel? ** Changed in: upower (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: gnome-shell (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: gnome-control-center (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Cosmic) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1745032 Title: AC adapter status not detected on Asus ZenBook UX410UAK Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in upower package in Ubuntu: Fix Released Status in gnome-control-center source package in Bionic: Fix Committed Status in gnome-shell source package in Bionic: Fix Committed Status in linux source package in Bionic: Fix Committed Status in upower source package in Bionic: Fix Committed Status in gnome-control-center source package in Cosmic: Fix Committed Status in gnome-shell source package in Cosmic: Fix Committed Status in linux source package in Cosmic: Triaged Status in upower source package in Cosmic: Fix Committed Bug description: === SRU Justification === [Impact] Some Asus laptops report "discharging" when the battery is full and AC is plugged [Test] Charge battery to full, the issue appears. Users report with the patch the behaviour is correct. [Fix] The discharge rate is 0 on those machines. Use that to detect the wrong status report. [Regression Potential] Low. The quirk uses strict DMI to match affected systems. === Original Bug Report === The AC adapter status is incorrectly reported when the battery is fully charged. It always shows as if the adapter is not plugged in. If the battery is drained for a while, the adapter status is shown correctly (both connects and disconnects are shown). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-31-generic 4.13.0-31.34 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abarto 1388 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 23 18:26:18 2018 InstallationDate: Installed on 2018-01-23 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-31-generic N/A linux-backports-modules-4.13.0-31-generic N/A linux-firmware 1.169.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1745032/+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 1808233] Re: Update gtk to 3.24.4
Hi! Sorry to bother here but I wanted to attract your attention to the following bug, in case you could consider dropping the type ahead patch in future updates: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1592177 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1808233 Title: Update gtk to 3.24.4 Status in gtk+3.0 package in Ubuntu: Fix Committed Status in gtk+3.0 source package in Cosmic: In Progress Bug description: Impact == There is a new release in the stable 3.24 series. This also bundles the emoji fixes from LP: #1807719 and LP: #1807721 and the Xfce flickering fix from LP: #1798861. https://gitlab.gnome.org/GNOME/gtk/blob/gtk-3-24/NEWS https://gitlab.gnome.org/GNOME/gtk/compare/3.24.1...3.24.4 Test Case = Run several apps in the default Ubuntu install and make sure that there are no visible regressions. Make sure that GTK switches look OK. We will also be checking Xfce to validate the fix for LP: #1798861. Regression Potential There is a standing microrelease exception for GNOME point releases. I believe this is the second time in recent history that we've pushed a gtk point release as an SRU. The other example was 3.22.25 for Ubuntu 17.10 (LP: #1728421). We never ended up doing one for Ubuntu 18.04 LTS since it already included 3.22.30, the final 3.22 release. It hasn't been practical to update 18.04's gtk to the 3.24 series (bumped dependencies are one problem). https://wiki.ubuntu.com/StableReleaseUpdates#GNOME By the way, pre-release gtk3 is actually getting a bit more testing than a year ago since more developers and users are using development Flatpak releases of popular GNOME apps. (On the other hand, there were a few regressions in the 3.24.2 and 3.24.3 releases.) This update changes the ON/OFF switches for GNOME's default Adwaita theme to use ❙/○ for all languages (or ⏽/⭘ if they are supported in a font you have installed: currently, that's fonts-symbola which we no longer install by default). Previously, it was ❙/○ for most languages but ON/OFF for English (because English has short words that could fit on a switch). This doesn't affect default Ubuntu 18.10 which uses Yaru which doesn't use labels on its switches. This is technically a UI change, but it is useful for compatibility with Flatpak apps that are being built with the new GTK. This change is small enough that it could be reverted for Ubuntu 18.10 if necessary. Other Info == The commit history shows themeing changes to the GNOME default themes (Adwaita and Adwaita Dark which are bundled inside gtk3). But those changes were reverted for this release to make it easier for distros like us to push the update to our stable release. The next scheduled gtk3 release (3.24.5 ? in March?) will include those changes. See https://blog.gtk.org/2019/01/14/theme-changes-in- gtk-3/ for more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1808233/+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 1813591] Re: pygobject ftbfs in 18.04 LTS
Hello Matthias, or anyone else affected, Accepted pygobject into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/pygobject/3.26.1-2ubuntu1 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: pygobject (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 pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1813591 Title: pygobject ftbfs in 18.04 LTS Status in pygobject package in Ubuntu: Fix Released Status in pygobject source package in Bionic: Fix Committed Bug description: Impact -- pygobject doesn't build from source which means someone would need to fix that problem before fixing any bugs in the pygobject package for Ubuntu 18.04 LTS. Test Case - Does pygobject build successfully? Regression Potential pygobject 3.28 is the intended version to match glib 2.56 but it missed the deadline for Ubuntu 18.04 LTS. So this fix is cherry-picking a small commit to fix the build tests with 18.04's glib2.0 2.56. The only change that is made in this upload is to the tests. There should be no effect on anything else. https://gitlab.gnome.org/GNOME/pygobject/commit/550bd7c7 Original Bug Report --- according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html pygobject ftbfs. == FAIL: test_filenames (test_glib.TestGLib) -- Traceback (most recent call last): File "/<>/tests/test_glib.py", line 66, in test_filenames self.assertTrue(isinstance(res, bytes)) AssertionError: False is not true -- Ran 1211 tests in 4.072s FAILED (failures=1, skipped=4, expected failures=12) torture test 1 (1 iterations): 0.012186 secs torture test 2 (1 iterations): 0.068459 secs torture test 3 (1 iterations): 0.029216 secs torture test 4 (1 iterations): 0.065890 secs Total: 0.175751 sec Makefile:905: recipe for target 'check.real' failed make[5]: *** [check.real] Error 1 make[5]: Leaving directory '/<>/build-3.6/tests' Makefile:900: recipe for target 'check-local' failed make[4]: *** [check-local] Error 2 Makefile:738: recipe for target 'check-am' failed make[3]: *** [check-am] Error 2 Makefile:691: recipe for target 'check-recursive' failed make[2]: *** [check-recursive] Error 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1813591/+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 1164016] Re: restore type-ahead find
Today, as often, I installed Ubuntu to a new Linux user, coming from Windows. Everything is great and well designed, intuitive, and quick ... then ... this lady began to feel confortable and wanted to quickly jump to the photo named "IMG232.jpg"; so she started to type "IMG" on her folder, containing hundred of photos and sub-folder and ... yeah, I suddently remembered WHY I gave up using this software a bunch of years ago. How to explain this to this lady ? After a while she understood that those files that dissapeared and appeared under her eyes wasn't a deletion, but a search result. How to know WITCH IMG232.jpg was the one of the **current** folder ? The folder of the bro's weeding ? She logically asked me how to change this default strange behavior and I logically said to her "oh yeah, I remember this is a way old story; this MUST be an option to disable this". And ... WT-holly-F ? No, no option at all :/ I **CAN'T BELIEVE** that after more than 5 years there's still NO option to DECIDE what should be the default behavior of the default browser. And when I see the ridiculous patch [1] this implies, I can't believe it even less. What would be the cost of an option in program's preferences ?! 1. https://launchpadlibrarian.net/368070783/nautilus-restore-typeahead-patch.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1164016 Title: restore type-ahead find Status in Nautilus: Expired Status in nautilus package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: GNOME removed type-ahead find in Nautilus 3.6, not without controversy: https://mail.gnome.org/archives/nautilus- list/2012-August/msg2.html Now when you type in a Nautilus window, Nautilus immediately performs a search in the current directory and all its subdirectories. I personally find this annoying. If I want to search, I'll click the search icon. Often I'm looking at a long directory listing and simply want to jump to a certain point in it, and type-ahead find works great for that. Would Ubuntu consider patching type-ahead find back in? To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+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 1687478] Re: "properties" -> "open with" - defective statemachine
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Package changed: nautilus (Ubuntu) => gtk+3.0 (Ubuntu) ** Changed in: gtk+3.0 (Ubuntu) Importance: Undecided => Low ** Changed in: gtk+3.0 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1687478 Title: "properties" -> "open with" - defective statemachine Status in gtk+3.0 package in Ubuntu: Incomplete Bug description: On Ubuntu 16.04.2: The statemachine of the "Open With" dialogue in is defective. To open this dialogue reightclick a file, click "properties" and select "Open With" tab. The behaviour of the button "Set as default" is correct. After clicking that button, the behaviour of the "Add" button is also correct. But clicking only the button "Add" after opening the dialogue without click "Set as default", it shows the wrong behavior. Clicking "add" does always the same like clicking "Set as Default". Clicking "Set as default" one time repairs that behavior. Why that? There are two problems. Clicking "Add" does have the behaviour like clicking "Set as default" to have one "Default Application" set, if no "Default Application" is set. That is correct. 1st problem: This dialogue starts in state believing no default application is set. But the already set default application is listed as "Default Application". That means, clicking "Add" does the same like "Set as default", when it should not. 2nd related problem: Clicking "Add" to set the "Default Application" the first time, does not set the state that the "Default Application" is set like clicking "Set as default" does. So the 1st problem is repeated. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49 Uname: Linux 4.4.0-72-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Mon May 1 23:09:06 2017 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'253' b'org.gnome.nautilus.window-state' b'geometry' b"'890x522+1030+530'" SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1687478/+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 1687478] [NEW] "properties" -> "open with" - defective statemachine
You have been subscribed to a public bug: On Ubuntu 16.04.2: The statemachine of the "Open With" dialogue in is defective. To open this dialogue reightclick a file, click "properties" and select "Open With" tab. The behaviour of the button "Set as default" is correct. After clicking that button, the behaviour of the "Add" button is also correct. But clicking only the button "Add" after opening the dialogue without click "Set as default", it shows the wrong behavior. Clicking "add" does always the same like clicking "Set as Default". Clicking "Set as default" one time repairs that behavior. Why that? There are two problems. Clicking "Add" does have the behaviour like clicking "Set as default" to have one "Default Application" set, if no "Default Application" is set. That is correct. 1st problem: This dialogue starts in state believing no default application is set. But the already set default application is listed as "Default Application". That means, clicking "Add" does the same like "Set as default", when it should not. 2nd related problem: Clicking "Add" to set the "Default Application" the first time, does not set the state that the "Default Application" is set like clicking "Set as default" does. So the 1st problem is repeated. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49 Uname: Linux 4.4.0-72-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Mon May 1 23:09:06 2017 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'253' b'org.gnome.nautilus.window-state' b'geometry' b"'890x522+1030+530'" SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gtk+3.0 (Ubuntu) Importance: Low Status: Incomplete ** Tags: amd64 apport-bug xenial -- "properties" -> "open with" - defective statemachine https://bugs.launchpad.net/bugs/1687478 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811471] Re: local resolver stub fails to handle multiple TCP dns queries
autopkgtest regression failure analysis/justifications for bionic: systemd/s390x - failing since last november. gvfs/s390x - failing since 2017. snapd/s390x - flaky test that fails more than 1/2 the time since forever. snapd/ppc64el - same as s390x for cosmic: gvfs/s390x - almost always failed since forever. other bionic and cosmic autopkgtest regressions look like flaky tests, or autopkgtest system failures (e.g. can't reach apt repository). i have retried them all - will analyze again if the retest fails. -- 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 Committed Status in systemd source package in Trusty: Invalid Status in systemd source package in Xenial: Invalid Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Cosmic: Fix Committed Status in systemd source package in Disco: Fix Committed 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
[Touch-packages] [Bug 311029] Re: curl and pycurl is not compiled with sftp support
** Changed in: curl (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/311029 Title: curl and pycurl is not compiled with sftp support Status in curl package in Ubuntu: Fix Committed Status in curl package in Debian: Fix Released Bug description: Binary package hint: curl Running curl --version, I see: Protocols: tftp ftp telnet dict ldap ldaps http file https ftps SFTP is obviously missing, although it is supported by curl upstream The SFTP is also missing from python-pycurl, probably because libcurl doesn't have it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/311029/+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 1814167] Re: package poppler-utils 0.41.0-0ubuntu1.11 failed to install/upgrade: le paquet est dans un état vraiment incohérent; vous devriez le réinstaller avant de tenter de l
the issue is rather an hardware/corruption one than a package bug ** Changed in: poppler (Ubuntu) Importance: Undecided => Low ** Changed in: poppler (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1814167 Title: package poppler-utils 0.41.0-0ubuntu1.11 failed to install/upgrade: le paquet est dans un état vraiment incohérent; vous devriez le réinstaller avant de tenter de le configurer. Status in poppler package in Ubuntu: Invalid Bug description: problem with ubuntu 16.04 on an external disk, read only. Then i used grub-customizer. now i try to do again the updates. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: poppler-utils 0.41.0-0ubuntu1.11 ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 AptOrdering: poppler-utils: Configure cups: Configure NULL: ConfigurePending Architecture: amd64 Date: Thu Jan 31 21:55:37 2019 ErrorMessage: le paquet est dans un état vraiment incohérent; vous devriez le réinstaller avant de tenter de le configurer. InstallationDate: Installed on 2019-01-11 (20 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SourcePackage: poppler Title: package poppler-utils 0.41.0-0ubuntu1.11 failed to install/upgrade: le paquet est dans un état vraiment incohérent; vous devriez le réinstaller avant de tenter de le configurer. UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1814167/+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 1804487] Re: systemd-resolved has issues when the answer is over 512 bytes with EDNS disabled
For autopkgtest regression failure analysis/justification, please see bug 1811471 (since this sru contains patches for this and that bug) -- 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 Committed Status in systemd source package in Cosmic: Fix Committed 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 1808710] Re: !xcb_xlib_threads_sequence_lost error
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gtk+2.0 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1808710 Title: !xcb_xlib_threads_sequence_lost error Status in gtk+2.0 package in Ubuntu: Confirmed Bug description: Some gkt2 applications randomly crash with same error. See attached files. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1808710/+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 1814174] [NEW] Xorg crash report after resume
Public bug reported: Crash Report when resuming from sleep. Similar to https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1586223 This is a Sager NP8278 (Clevo P170SM-A) laptop with an Nvidia GeForce GTX 970M, driver 390.77 The crash log doesn't have much info in it IMO, but I uploaded here http://s000.tinyupload.com/?file_id=09497843963607449328 Output from sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date 4.6.5 11/14/2014 Output from uname -a Linux dksager2linux 4.15.0-44-generic #47-Ubuntu SMP Mon Jan 14 11:26:59 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Output from cat /etc/*ase DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" NAME="Ubuntu" VERSION="18.04.1 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.1 LTS" VERSION_ID="18.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=bionic UBUNTU_CODENAME=bionic Output from lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller (rev 06) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06) 00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06) 00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06) 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05) 00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05) 00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 05) 00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d5) 00:1c.1 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #2 (rev d5) 00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #3 (rev d5) 00:1c.3 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #4 (rev d5) 00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 05) 00:1f.0 ISA bridge: Intel Corporation HM87 Express LPC Controller (rev 05) 00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 05) 00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 05) 01:00.0 VGA compatible controller: NVIDIA Corporation GM204M [GeForce GTX 970M] (rev a1) 03:00.0 PCI bridge: Texas Instruments XIO2213A/B/XIO2221 PCI Express to PCI Bridge [Cheetah Express] (rev 01) 04:00.0 FireWire (IEEE 1394): Texas Instruments XIO2213A/B/XIO2221 IEEE-1394b OHCI Controller [Cheetah Express] (rev 01) 05:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411 PCI Express Card Reader (rev 01) 05:00.2 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0a) 06:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb) The nuisance inspired me to create a script on the desktop called ClearCrashLog.sh (info I got from a YouTube video) ls /var/crash sudo rm /var/crash/* It's annoying to have to type the password every time, but since root owns the crash log it's necessary. I've used Lubuntu for years. My prior laptop was a Sager with an AMD card. It had the same sort of issue versions ago. I got in the habit of just clicking it away. I think that the Report Crash fails because the log is owned by root and I don't have rights to it. Perhaps adding myself to the whoopsie group would resolve that (and needing sudo to delete too), so I think I'll try that. It's the only thing about Lubuntu that would be a turn off to new users. It's not a high priority thing, because the system works just fine. But it is a nuisance. ** Affects: xorg (Ubuntu) Importance: Undecided Status: New -- 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/1814174 Title: Xorg crash report after resume Status in xorg package in Ubuntu: New Bug description: Crash Report when resuming from sleep. Similar to https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1586223 This is a Sager NP8278 (Clevo P170SM-A) laptop with an Nvidia GeForce GTX 970M, driver 390.77 The crash log doesn't have much info in it IMO, but I uploaded here http://s000.tinyupload.com/?file_id=09497843963607449328 Output from sudo
[Touch-packages] [Bug 1813921] Re: The ubuntu doesn't work when there is a second monitor and the user locks the screen.
** Information type changed from Private Security to Public -- 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/1813921 Title: The ubuntu doesn't work when there is a second monitor and the user locks the screen. Status in xorg package in Ubuntu: New Bug description: Initial Setup to reproduce the first issue: 1. Have the last Ubuntu (18.04) updated. 2. Have a second monitor. First bug Description: 1. Try to starts the Ubuntu. Actual Results: 1. The Ubuntu can't start. Initial Setup to reproduce the second issue: 1. Have the last Ubuntu (18.04) updated. 2. Have a second monitor ready (not connected) to connect. Second bug description: 1. With the Ubuntu started, connect the second monitor and then lock the screen. 2. Try to unlock Ubuntu. Actual Results: 2. The mouse and keyboard don't work and the screen can't be unlocked. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 Uname: Linux 4.15.0-44-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jan 30 07:16:30 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c] MachineType: LENOVO 20B7008BBR ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-44-generic root=UUID=e1c74834-7cc4-44fb-94a2-06206608a746 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/03/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GJET79WW (2.29 ) dmi.board.asset.tag: Not Available dmi.board.name: 20B7008BBR dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET79WW(2.29):bd09/03/2014:svnLENOVO:pn20B7008BBR:pvrThinkPadT440:rvnLENOVO:rn20B7008BBR:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440 dmi.product.name: 20B7008BBR dmi.product.version: ThinkPad T440 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 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 xserver.bootTime: Tue Jan 29 14:59:13 2019 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1813921/+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 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK
I've tested the proposed updates and it seems to work with one minor caveat: If I unplug and plug the AC adapter, it takes a little while for the system to notice the change if it's near full charge (around 2 minutes). I think it's only a minor inconvenience. I've also tested that it properly detects the correct status coming of a cold boot or a resume and it worked just fine. I'd say this one's fixed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1745032 Title: AC adapter status not detected on Asus ZenBook UX410UAK Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in upower package in Ubuntu: Fix Released Status in gnome-control-center source package in Bionic: In Progress Status in gnome-shell source package in Bionic: In Progress Status in linux source package in Bionic: In Progress Status in upower source package in Bionic: In Progress Status in gnome-control-center source package in Cosmic: Fix Committed Status in gnome-shell source package in Cosmic: Fix Committed Status in linux source package in Cosmic: New Status in upower source package in Cosmic: Fix Committed Bug description: === SRU Justification === [Impact] Some Asus laptops report "discharging" when the battery is full and AC is plugged [Test] Charge battery to full, the issue appears. Users report with the patch the behaviour is correct. [Fix] The discharge rate is 0 on those machines. Use that to detect the wrong status report. [Regression Potential] Low. The quirk uses strict DMI to match affected systems. === Original Bug Report === The AC adapter status is incorrectly reported when the battery is fully charged. It always shows as if the adapter is not plugged in. If the battery is drained for a while, the adapter status is shown correctly (both connects and disconnects are shown). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-31-generic 4.13.0-31.34 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abarto 1388 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 23 18:26:18 2018 InstallationDate: Installed on 2018-01-23 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-31-generic N/A linux-backports-modules-4.13.0-31-generic N/A linux-firmware 1.169.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1745032/+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 1804487] Re: systemd-resolved has issues when the answer is over 512 bytes with EDNS disabled
Bionic verified too ii systemd 237-3ubuntu10.12 amd64system and service manager $ dig +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l 30 $ dig +noall +answer +noedns testing.irongiantdesign.com @127.0.0.53 | wc -l 30 ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic ** Tags removed: verification-needed ** Tags added: verification-done -- 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 Committed Status in systemd source package in Cosmic: Fix Committed 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 1811471] Re: local resolver stub fails to handle multiple TCP dns queries
Bionic verified ii systemd 237-3ubuntu10.12 amd64 system and service manager $ ping testing.irongiantdesign.com PING testing.irongiantdesign.com (253.0.0.6) 56(84) bytes of data. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-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/1811471 Title: local resolver stub fails to handle multiple TCP dns queries Status in systemd: New Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Trusty: Invalid Status in systemd source package in Xenial: Invalid Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Cosmic: Fix Committed Status in systemd source package in Disco: Fix Committed 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). [Test Case] This can be reproduced on any system using a local systemd stub resolver, when using an application that uses getaddrinfo() - such as
[Touch-packages] [Bug 1814167] [NEW] package poppler-utils 0.41.0-0ubuntu1.11 failed to install/upgrade: le paquet est dans un état vraiment incohérent; vous devriez le réinstaller avant de tenter de
Public bug reported: problem with ubuntu 16.04 on an external disk, read only. Then i used grub-customizer. now i try to do again the updates. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: poppler-utils 0.41.0-0ubuntu1.11 ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 AptOrdering: poppler-utils: Configure cups: Configure NULL: ConfigurePending Architecture: amd64 Date: Thu Jan 31 21:55:37 2019 ErrorMessage: le paquet est dans un état vraiment incohérent; vous devriez le réinstaller avant de tenter de le configurer. InstallationDate: Installed on 2019-01-11 (20 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SourcePackage: poppler Title: package poppler-utils 0.41.0-0ubuntu1.11 failed to install/upgrade: le paquet est dans un état vraiment incohérent; vous devriez le réinstaller avant de tenter de le configurer. UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: poppler (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1814167 Title: package poppler-utils 0.41.0-0ubuntu1.11 failed to install/upgrade: le paquet est dans un état vraiment incohérent; vous devriez le réinstaller avant de tenter de le configurer. Status in poppler package in Ubuntu: New Bug description: problem with ubuntu 16.04 on an external disk, read only. Then i used grub-customizer. now i try to do again the updates. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: poppler-utils 0.41.0-0ubuntu1.11 ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 AptOrdering: poppler-utils: Configure cups: Configure NULL: ConfigurePending Architecture: amd64 Date: Thu Jan 31 21:55:37 2019 ErrorMessage: le paquet est dans un état vraiment incohérent; vous devriez le réinstaller avant de tenter de le configurer. InstallationDate: Installed on 2019-01-11 (20 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SourcePackage: poppler Title: package poppler-utils 0.41.0-0ubuntu1.11 failed to install/upgrade: le paquet est dans un état vraiment incohérent; vous devriez le réinstaller avant de tenter de le configurer. UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1814167/+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] Re: local resolver stub fails to handle multiple TCP dns queries
Cosmic Verified ii systemd 239-7ubuntu10.7 amd64 system and service manager ping testing.irongiantdesign.com PING testing.irongiantdesign.com (253.0.0.15) 56(84) bytes of data. ** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic -- 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 Committed Status in systemd source package in Trusty: Invalid Status in systemd source package in Xenial: Invalid Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Cosmic: Fix Committed Status in systemd source package in Disco: Fix Committed 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). [Test Case] This can be reproduced on any system using a local systemd stub resolver, when using an application that uses getaddrinfo()
[Touch-packages] [Bug 1804487] Re: systemd-resolved has issues when the answer is over 512 bytes with EDNS disabled
Cosmic Verified ii systemd 239-7ubuntu10.7 amd64 system and service manager #EDNS query $ dig +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l 30 #No EDNS query falling back to TCP $ dig +noall +answer +noedns testing.irongiantdesign.com @127.0.0.53 | wc -l 30 #No EDNS query ignoring the truncate flag (stick to UDP only) $ dig +noall +answer +noedns +ignore testing.irongiantdesign.com @127.0.0.53 | wc -l 29 also fixes 1811471 but I'll put those results on the other bug. ** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic -- 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 Committed Status in systemd source package in Cosmic: Fix Committed 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 1787729] Re: apport-autoreport.service fails if whoopsie isn't running
Could somebody please test the version of apport from cosmic-proposed? I'd prefer somebody affected by the bug verified that the new version of the package works for them. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1787729 Title: apport-autoreport.service fails if whoopsie isn't running Status in apport package in Ubuntu: Fix Released Status in apport source package in Cosmic: Fix Committed Bug description: Impact -- If automatic crash reporting is enabled and apport-autoreport.service starts before whoopsie on boot then crash reports that happened during shutdown or start up will not be automatically uploaded to the error tracker. Test Case - 1) install apport-noui 2) sudo service apport stop 3) modify /usr/share/apport/whoopsie-upload-all to exit(1) thereby recreating the situation where whoopsie isn't running. I did this by copying lines 159,160 to 161,162 and unindenting them. N.B. this isn't necessary if you are on a system where whoopsie is starting after apport. 4) touch /var/crash/my.crash 5) reboot 5) run 'systemctl status apport-autoreport.service' and observe it failed because whoopsie isn't running When testing the proposed version of apport you'll want to revert the changes you made to whoopsie-upload-all. With the version of apport from -proposed you should no longer see the failure message for the apport-autoreport.service. The best test case is just having an affected system test the package from -proposed though. Regression Potential We are clearly fixing something that was a mistake in the original service so there is little chance for regression. ProblemType: BugDistroRelease: Ubuntu 18.10 Package: apport 2.20.10-0ubuntu7 Uname: Linux 4.18.3-041803-generic x86_64 ApportLog: ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 18 11:48:00 2018 InstallationDate: Installed on 2017-10-13 (308 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) PackageArchitecture: allSourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1787729/+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 1814133] Re: update to openjdk 11 in 18.04 LTS
** Also affects: jtreg (Ubuntu) Importance: Undecided Status: New ** Also affects: libcommons-lang3-java (Ubuntu) Importance: Undecided Status: New ** Also affects: testng (Ubuntu) Importance: Undecided Status: New ** Also affects: gradle (Ubuntu) Importance: Undecided Status: New ** Also affects: gradle-debian-helper (Ubuntu) Importance: Undecided Status: New ** Also affects: clojure1.8 (Ubuntu) Importance: Undecided Status: New ** Also affects: dd-plist (Ubuntu) Importance: Undecided Status: New ** Also affects: maven-compiler-plugin (Ubuntu) Importance: Undecided Status: New ** Also affects: maven-debian-helper (Ubuntu) Importance: Undecided Status: New ** Also affects: plexus-languages (Ubuntu) Importance: Undecided Status: New ** Also affects: saaj (Ubuntu) Importance: Undecided Status: New ** Also affects: surefire (Ubuntu) Importance: Undecided Status: New ** Also affects: ca-certificates-java (Ubuntu) Importance: Undecided Status: New ** Also affects: groovy (Ubuntu) Importance: Undecided Status: New ** Also affects: jaxws-api (Ubuntu) Importance: Undecided Status: New ** Also affects: jws-api (Ubuntu) Importance: Undecided Status: New ** Also affects: metro-policy (Ubuntu) Importance: Undecided Status: New ** Also affects: saaj-ri (Ubuntu) Importance: Undecided Status: New ** Also affects: junit4 (Ubuntu) Importance: Undecided Status: New ** Also affects: gettext (Ubuntu) Importance: Undecided Status: New ** Also affects: scala (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: New Status in clojure1.8 package in Ubuntu: New Status in dd-plist package in Ubuntu: New Status in gettext package in Ubuntu: New Status in gradle package in Ubuntu: New Status in gradle-debian-helper package in Ubuntu: New Status in groovy package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in jtreg package in Ubuntu: New Status in junit4 package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in libcommons-lang3-java package in Ubuntu: New Status in maven-compiler-plugin package in Ubuntu: New Status in maven-debian-helper package in Ubuntu: New Status in metro-policy package in Ubuntu: New Status in openjdk-lts package in Ubuntu: New Status in plexus-languages package in Ubuntu: New Status in saaj package in Ubuntu: New Status in saaj-ri package in Ubuntu: New Status in scala package in Ubuntu: New Status in surefire package in Ubuntu: New Status in testng package in Ubuntu: New Bug description: update to openjdk 11 in 18.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates-java/+bug/1814133/+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 1814162] [NEW] Xorg freeze
Public bug reported: When I lock my machine on the latest ubuntu version 4.15.0-44-generic, it turns my display completely black and unresponsive. This is only when I have my dock (with external displays in). After it freezes however, removing the dock has no effect. Booting back into 4.15.0-43-generic has fixed the problem so this is a regression bug. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 31 14:25:01 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:081c] InstallationDate: Installed on 2018-10-17 (106 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Latitude 7490 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.2 dmi.board.name: 0KP0FT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.2:bd11/26/2018:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0KP0FT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7490 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic freeze third-party-packages ubuntu -- 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/1814162 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: When I lock my machine on the latest ubuntu version 4.15.0-44-generic, it turns my display completely black and unresponsive. This is only when I have my dock (with external displays in). After it freezes however, removing the dock has no effect. Booting back into 4.15.0-43-generic has fixed the problem so this is a regression bug. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 31 14:25:01 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:081c] InstallationDate: Installed on 2018-10-17 (106 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Latitude 7490 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2018 dmi.bios.vendor: Dell Inc.
[Touch-packages] [Bug 1814162] Re: Xorg freeze
Sorry I realized this bug is misleading with the version listed, the bug is for version: 4.15.0-44-generic. I am booted into 43 to fix the problem. -- 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/1814162 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: When I lock my machine on the latest ubuntu version 4.15.0-44-generic, it turns my display completely black and unresponsive. This is only when I have my dock (with external displays in). After it freezes however, removing the dock has no effect. Booting back into 4.15.0-43-generic has fixed the problem so this is a regression bug. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 31 14:25:01 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:081c] InstallationDate: Installed on 2018-10-17 (106 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Latitude 7490 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.2 dmi.board.name: 0KP0FT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.2:bd11/26/2018:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0KP0FT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7490 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 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/xorg/+bug/1814162/+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
Re: [Touch-packages] [Bug 1644996] Re: logrotate config uses syslog group
On Thu, Jan 31, 2019 at 01:48:06PM -, Mantas Kriaučiūnas wrote: > Steve Langasek (vorlon), yes lots of Ubuntu users, including me have > lots of containers (based on ubuntu-minimal - Ubuntu developers created > "Minimal" LXC container image without rsyslog package by default), see > ubuntu-18.04-minimal-cloudimg-amd64.manifest: > https://cloud-images.ubuntu.com/minimal/releases/bionic/release/ubuntu-18.04-minimal-cloudimg- > amd64.manifest I know exactly what we are producing, I was personally involved in the development of the minimal images. Which is why I am disputing the idea that "lots of users" are consuming the minimal images in lxd today, because I know they are not currently published in a form that is consumed by the lxd client automatically. > https://github.com/sameersbn/docker-gitlab/issues/1544#issuecomment-373366621 > https://gitlab.timmertech.nl/docker/gitlab/commit/428e37a821f94af03e72201420ee2874be8834b4 These are about docker, not about lxd. docker and lxd are completely separate technologies that use completely separate images. If what you are running is docker containers, then running a syslog daemon (default or otherwise) and a log rotater inside the container is a corner case with a straightforward workaround (create the group when you create your docker image). This does not constitute a high priority issue for SRUing. If what you are running is lxd containers, you haven't answered my question of how you are doing this. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1644996 Title: logrotate config uses syslog group Status in logrotate package in Ubuntu: Fix Released Status in logrotate source package in Bionic: New Status in logrotate source package in Cosmic: New Bug description: The default logrotate config uses the "syslog" group. > # use the syslog group by default, since this is the owning group > # of /var/log/syslog. > su root syslog This is not correct anymore since 16.04, because: 1. "syslog" group doesn't exist on a stock Ubuntu 16.04 system, it only gets installed via rsyslog 2. The owning group is actually "adm". This results in logrotate terminating with the following error during cron.daily run: run-parts -v /etc/cron.daily run-parts: executing /etc/cron.daily/logrotate error: /etc/logrotate.conf:7 unknown group 'syslog' And can be fixed by changing syslog to adm group. This is not present when rsyslog is installed, but only because that package creates the syslog group. This is a common bug in lighter environments, like Docker, where syslog-ng is a common choice instead of rsyslog, like in this issue: https://github.com/phusion/baseimage-docker/issues/338 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1644996/+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 1644996] Re: logrotate config uses syslog group
Note that 'rls-bb-notfixing' is a statement that the Foundations Team does not intend to work on this SRU. It is not a statement that an SRU would be rejected. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1644996 Title: logrotate config uses syslog group Status in logrotate package in Ubuntu: Fix Released Status in logrotate source package in Bionic: New Status in logrotate source package in Cosmic: New Bug description: The default logrotate config uses the "syslog" group. > # use the syslog group by default, since this is the owning group > # of /var/log/syslog. > su root syslog This is not correct anymore since 16.04, because: 1. "syslog" group doesn't exist on a stock Ubuntu 16.04 system, it only gets installed via rsyslog 2. The owning group is actually "adm". This results in logrotate terminating with the following error during cron.daily run: run-parts -v /etc/cron.daily run-parts: executing /etc/cron.daily/logrotate error: /etc/logrotate.conf:7 unknown group 'syslog' And can be fixed by changing syslog to adm group. This is not present when rsyslog is installed, but only because that package creates the syslog group. This is a common bug in lighter environments, like Docker, where syslog-ng is a common choice instead of rsyslog, like in this issue: https://github.com/phusion/baseimage-docker/issues/338 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1644996/+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 1755863] Re: netbooting the bionic live CD over NFS goes straight to maintenance mode :
i just tried out the daily build of http://cdimage.ubuntu.com/daily-live/pending/disco-desktop-amd64.iso from 2019-01-31 07:45 to pxe boot wihout using the "systemd.mask=tmp.mount" workaround... but i still goes straight to maintenance mode. is the fix not included to the daily build yet? -- 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/1755863 Title: netbooting the bionic live CD over NFS goes straight to maintenance mode : Status in systemd: Unknown Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Xenial: In Progress Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: In Progress Status in systemd source package in Disco: Fix Committed Bug description: [Impact] Mounting manually a network share (NFS) and masking it breaks the state of other units (and their dependencies). Casper is masking a mounted NFS share, blocking the normal boot process as described in the original description, but the issue comes from systemd. [Test Case] - NFS mount point at /media root@iscsi-bionic:/home/ubuntu# mount | grep media 10.230.56.72:/tmp/mnt on /media type nfs4 (rw,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.122.127,local_lock=none,addr=10.230.56.72) - Test mount point (/test) defined in /etc/fstab: root@iscsi-bionic:/home/ubuntu# cat /etc/fstab |grep test tmpfs /test tmpfs nosuid,nodev 0 0 1. If media.mount is not masked, everything works fine: root@iscsi-bionic:/home/ubuntu# mount | grep test root@iscsi-bionic:/home/ubuntu# systemctl status media.mount | grep Active Active: active (mounted) since Thu 2018-11-15 16:03:59 UTC; 3 weeks 6 days ago root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active Active: inactive (dead) since Thu 2018-12-13 10:33:52 UTC; 4min 11s ago root@iscsi-bionic:/home/ubuntu# systemctl start test.mount root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active Active: active (mounted) since Thu 2018-12-13 10:38:13 UTC; 3s ago root@iscsi-bionic:/home/ubuntu# mount | grep test tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime) root@iscsi-bionic:/home/ubuntu# systemctl stop test.mount root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active Active: inactive (dead) since Thu 2018-12-13 10:38:32 UTC; 3s ago root@iscsi-bionic:/home/ubuntu# mount | grep test 2. If media.mount is masked, other mounts are failing: root@iscsi-bionic:/home/ubuntu# systemctl mask media.mount Created symlink /etc/systemd/system/media.mount → /dev/null. root@iscsi-bionic:/home/ubuntu# systemctl start test.mount Job for test.mount failed. See "systemctl status test.mount" and "journalctl -xe" for details. root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active Active: failed (Result: protocol) since Thu 2018-12-13 10:40:06 UTC; 10s ago root@iscsi-bionic:/home/ubuntu# mount | grep test tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime) root@iscsi-bionic:/home/ubuntu# systemctl stop test.mount root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active Active: failed (Result: protocol) since Thu 2018-12-13 10:40:06 UTC; 25s ago root@iscsi-bionic:/home/ubuntu# mount | grep test tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime) root@iscsi-bionic:/home/ubuntu# systemctl start test.mount Job for test.mount failed. See "systemctl status test.mount" and "journalctl -xe" for details. root@iscsi-bionic:/home/ubuntu# mount | grep test tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime) tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime) root@iscsi-bionic:/home/ubuntu# systemctl stop test.mount root@iscsi-bionic:/home/ubuntu# mount | grep test tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime) tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime) [Regression potential] Minimal. Originally, one failing mount point blocked the processing of the rest due to how the return codes were handled for every line in /proc/self/mountinfo. This patch removes this "dependency" and keeps the failure local to the affected mount point, allowing the rest to be processed normally. [Other Info] Upstream bug: https://github.com/systemd/systemd/issues/10874 Fixed upstream with commit: https://github.com/systemd/systemd/commit/c165888426ef99440418592a8cdbaff4b7c319b3 [Original Description] netbooting the bionic live CD[1] over NFS goes straight to maintenance mode : [1] http://cdimage.ubuntu.com/daily-live/current/ # casper.log Begin: Adding live session user... ... dbus-daemon[568]: [session uid=999 pid=568] Activating service name='org.gtk.vfs.Daemon' requested by ':1.0' (uid=999 pid=569
[Touch-packages] [Bug 1813432] Re: Specific PDF file fails to print to HP m551dn printer
mupdftoraster is part of cups-filters. If it is missing for you, run sudo apt install --reinstall cups-filters -- 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/1813432 Title: Specific PDF file fails to print to HP m551dn printer Status in cups package in Ubuntu: Incomplete Bug description: One particular PDF file is failing to print. I have no idea why. When I say failing to print I mean that my computer thinks the file printed but the printer shows no sign of ever having received it. The display of the printer never changes to show that it is receiving or printing a file, and the job log of the printer doesn't show that it was received either. I also checked the printer event log and it doesn't show any events at the time I attempted to print the file. Unfortunately I can't attach the PDF file itself because it contains private information, and I can't find another PDF that exhibits this problem. I even tried generating a new PDF exactly the same way the old one was generated -- with the scan to email PDF function on my scanner -- and the new PDF prints just fine. I tried uploading the PDF directly to the printer with FTP and it prints just fine that way. I enabled CUPS debug mode before attempting to print the file. Attached is the resulting contents of /var/log/cups/error_log. I wish I knew what was going on here but honestly I have no idea. Perhaps you can learn something from the error_log. I hope so. Other files, including other PDFs, do print. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: cups 2.2.10-3 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 26 17:47:49 2019 InstallationDate: Installed on 2019-01-02 (24 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lpstat: device for duplex: socket://m551dn.kamens.brookline.ma.us:9100 device for HP_LaserJet_500_color_M551_1637DA_: ipps://m551dn.local:443/ipp/print device for simplex: socket://m551dn.kamens.brookline.ma.us:9100 MachineType: Acer Predator G6-710 Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/simplex.ppd', '/etc/cups/ppd/HP_LaserJet_500_color_M551_1637DA_.ppd', '/etc/cups/ppd/duplex.ppd'] failed with exit code 2: grep: /etc/cups/ppd/simplex.ppd: Permission denied grep: /etc/cups/ppd/HP_LaserJet_500_color_M551_1637DA_.ppd: Permission denied grep: /etc/cups/ppd/duplex.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to disco on 2019-01-21 (5 days ago) dmi.bios.date: 05/18/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R01-A4 dmi.board.name: Predator G6-710 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr: dmi.product.family: Acer Desktop dmi.product.name: Predator G6-710 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1813432/+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 1770429] Re: Ubuntu 18.04 No audio from speakers. Headphones working. Surface Pro 3
more clues related to comment #9 if I run alsamixer I can toggle AUTO-MUTE from ENABLED to DISABLED and the SOUND SETTINGS Choose a device for sound output switches between headphones output and Analog Stereo Output. I did this 4-5 rapidly and now it seems that the SOUND SETTINGS Choose a device for sound output now appears to switch back/forth between headphones and Analog Stereo Out but when I plug in Headphones I hear audio from both speakers & headphones. But as a temp workaround this is ok for me since if I use headphones I can turn off my speakers but if not using headphones (re not plugged in) my speakers work. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1770429 Title: Ubuntu 18.04 No audio from speakers. Headphones working. Surface Pro 3 Status in alsa-driver package in Ubuntu: Confirmed Bug description: I updated my Surface Pro 3 From Ubuntu 17.10 to Ubuntu 18.04 (did a clean install) and the only audio working was from the headphone jack. I tried all these: [troubleshooting guide](https://help.ubuntu.com/community/SoundTroubleshootingProcedure) [this answer](https://askubuntu.com/questions/117842/no-sound-from-speakers-but-headphones-work) [another answer](https://askubuntu.com/questions/829520/ubuntu-16-04-no-sound-from-speakers-only-headphones-working) I went back and tested the live CD and even the live cd has no audio through the speakers. so this must be related to 18.04. I never had sound issues before and under windows audio still works correctly. here is my alsa iformation http://www.alsa- project.org/db/?f=8bf135db52610a603014779ef24041a491c8a32d and here is how I fixed it: renaming /etc/modprobe.d/alsa-base.conf to /etc/modprobe.d/alsa- base.bk , then rebooting the computer fixed the my speaker sound issue. I then restored line by line in to /etc/modprobe.d/alsa-base.conf, rebooting between restored lines, until all lines were back and ... it still worked! so I restored the original /etc/modprobe.d/alsa-base.conf and rebooted the computer and everything was still working so I am not sure what the problem was but is now fixed. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.16.7-041607-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: carlosr2267 F pulseaudio /dev/snd/controlC0: carlosr2267 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu May 10 10:15:29 2018 InstallationDate: Installed on 2018-04-27 (13 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.11.2350 dmi.board.asset.tag: 0 dmi.board.name: Surface Pro 3 dmi.board.vendor: Microsoft Corporation dmi.board.version: 1 dmi.chassis.asset.tag: 0 dmi.chassis.type: 9 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.11.2350:bd01/23/2018:svnMicrosoftCorporation:pnSurfacePro3:pvr1:rvnMicrosoftCorporation:rnSurfacePro3:rvr1:cvnMicrosoftCorporation:ct9:cvr1: dmi.product.family: Surface dmi.product.name: Surface Pro 3 dmi.product.version: 1 dmi.sys.vendor: Microsoft Corporation mtime.conffile..etc.modprobe.d.alsa-base.conf: 2018-05-09T14:04:13.313882 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1770429/+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 1770429] Re: Ubuntu 18.04 No audio from speakers. Headphones working. Surface Pro 3
Same problem ubuntu 18.04 ran pavucontrol and saw "line-out (unplugged)" plug in my headphones and "line-out unplugged" changed to: line-out (plugged in) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1770429 Title: Ubuntu 18.04 No audio from speakers. Headphones working. Surface Pro 3 Status in alsa-driver package in Ubuntu: Confirmed Bug description: I updated my Surface Pro 3 From Ubuntu 17.10 to Ubuntu 18.04 (did a clean install) and the only audio working was from the headphone jack. I tried all these: [troubleshooting guide](https://help.ubuntu.com/community/SoundTroubleshootingProcedure) [this answer](https://askubuntu.com/questions/117842/no-sound-from-speakers-but-headphones-work) [another answer](https://askubuntu.com/questions/829520/ubuntu-16-04-no-sound-from-speakers-only-headphones-working) I went back and tested the live CD and even the live cd has no audio through the speakers. so this must be related to 18.04. I never had sound issues before and under windows audio still works correctly. here is my alsa iformation http://www.alsa- project.org/db/?f=8bf135db52610a603014779ef24041a491c8a32d and here is how I fixed it: renaming /etc/modprobe.d/alsa-base.conf to /etc/modprobe.d/alsa- base.bk , then rebooting the computer fixed the my speaker sound issue. I then restored line by line in to /etc/modprobe.d/alsa-base.conf, rebooting between restored lines, until all lines were back and ... it still worked! so I restored the original /etc/modprobe.d/alsa-base.conf and rebooted the computer and everything was still working so I am not sure what the problem was but is now fixed. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.16.7-041607-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: carlosr2267 F pulseaudio /dev/snd/controlC0: carlosr2267 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu May 10 10:15:29 2018 InstallationDate: Installed on 2018-04-27 (13 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.11.2350 dmi.board.asset.tag: 0 dmi.board.name: Surface Pro 3 dmi.board.vendor: Microsoft Corporation dmi.board.version: 1 dmi.chassis.asset.tag: 0 dmi.chassis.type: 9 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.11.2350:bd01/23/2018:svnMicrosoftCorporation:pnSurfacePro3:pvr1:rvnMicrosoftCorporation:rnSurfacePro3:rvr1:cvnMicrosoftCorporation:ct9:cvr1: dmi.product.family: Surface dmi.product.name: Surface Pro 3 dmi.product.version: 1 dmi.sys.vendor: Microsoft Corporation mtime.conffile..etc.modprobe.d.alsa-base.conf: 2018-05-09T14:04:13.313882 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1770429/+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 1812095] Re: console login loop after entering username followed by RETURN
Ubuntu Mate 18.04.1, same problem with linux-image-4.15.0-44-generic and linux-image-4.15.0-45-generic If I switch back to linux-image-4.15.0-43-generic I can succesfully login to TTY. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1812095 Title: console login loop after entering username followed by RETURN Status in shadow package in Ubuntu: Confirmed Bug description: login: password: Just do nothing. About two seconds later ... login: password: login: password: login: password: After this being displayed three times: "Too many failure" or so and login is restarting. You cant login at all. Only solution: clear the password for the account you want to login with. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: login 1:4.5-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20 Uname: Linux 4.18.0-14-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Jan 16 19:34:30 2019 InstallationDate: Installed on 2011-10-19 (2645 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: shadow UpgradeStatus: Upgraded to cosmic on 2018-11-03 (74 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1812095/+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 1814109] Re: Nautilus corrupts 7z archive files when extracting via 'Extract here' context menu
The issue is with libarchive, installed libarchive-tools and trying to extract the archive with bsdtar gives that '# bsdtar -xf TestWavFile.7z TestWavFile/Sweep_1Hz_44000Hz_-3dBFS_30s.wav: 7-Zip bad CRC: 0x5f2fe0a4 should be 0x2a268c5a TestWavFile/Sweep_1Hz_48000Hz_-3dBFS_30s.wav: 7-Zip bad CRC: 0x48c4d6a2 should be 0xb05eb55d TestWavFile/Sweep_1Hz_88000Hz_-3dBFS_30s.wav: 7-Zip bad CRC: 0x3f9e0eb1 should be 0xc82c61f7 TestWavFile/Sweep_1Hz_96000Hz_-3dBFS_30s.wav: 7-Zip bad CRC: 0xef123101 should be 0x79650d07 TestWavFile/cuts_like_a_knife_44KHz_16bit_stereo_SMALL.wav: 7-Zip bad CRC: 0x9c17a479 should be 0x2aed26ef bsdtar: Error exit delayed from previous errors.' installing p7zip-full and extracting with it indeed gives different file content (which is what file-roller is doing) ** Package changed: nautilus (Ubuntu) => libarchive (Ubuntu) ** Bug watch added: github.com/libarchive/libarchive/issues #1129 https://github.com/libarchive/libarchive/issues/1129 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libarchive in Ubuntu. https://bugs.launchpad.net/bugs/1814109 Title: Nautilus corrupts 7z archive files when extracting via 'Extract here' context menu Status in libarchive package in Ubuntu: Triaged Bug description: Nautilus corrupts 7z archive files when extracting via 'Extract here' context menu. Extractions completes without errors, but the files are corrupted (mangled bytes, wrong size). This does happen only when extracting with 'Extract here' context menu action. Using 7z or p7zip via command line or opening the archive via file-roller and then drag single files or directory to a folder works well. This only happens with this particular archive, others 7z archives are extracted correctly. Original 7z archive: https://drive.google.com/open?id=1eZJm1ST3P-52tFSvHXbUn9-WSe_B3Ag9 Re-zipped corrupted archive here: https://drive.google.com/open?id=1N--99RuWdmg6oUGrAz7pLoRpuJOIBEE5 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: nautilus 1:3.26.4-0ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 31 15:03:45 2019 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'222' b'org.gnome.nautilus.window-state' b'geometry' b"'1133x703+51+273'" b'org.gnome.nautilus.desktop' b'trash-icon-visible' b'false' b'org.gnome.nautilus.desktop' b'volumes-visible' b'false' InstallationDate: Installed on 2018-05-31 (245 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: nautilus UpgradeStatus: Upgraded to cosmic on 2018-10-20 (103 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libarchive/+bug/1814109/+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 1814109] Re: Nautilus corrupts 7z archive files when extracting via 'Extract here' context menu
Reported upstream https://github.com/libarchive/libarchive/issues/1129 ** Changed in: libarchive (Ubuntu) Importance: Undecided => High ** Changed in: libarchive (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libarchive in Ubuntu. https://bugs.launchpad.net/bugs/1814109 Title: Nautilus corrupts 7z archive files when extracting via 'Extract here' context menu Status in libarchive package in Ubuntu: Triaged Bug description: Nautilus corrupts 7z archive files when extracting via 'Extract here' context menu. Extractions completes without errors, but the files are corrupted (mangled bytes, wrong size). This does happen only when extracting with 'Extract here' context menu action. Using 7z or p7zip via command line or opening the archive via file-roller and then drag single files or directory to a folder works well. This only happens with this particular archive, others 7z archives are extracted correctly. Original 7z archive: https://drive.google.com/open?id=1eZJm1ST3P-52tFSvHXbUn9-WSe_B3Ag9 Re-zipped corrupted archive here: https://drive.google.com/open?id=1N--99RuWdmg6oUGrAz7pLoRpuJOIBEE5 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: nautilus 1:3.26.4-0ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 31 15:03:45 2019 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'222' b'org.gnome.nautilus.window-state' b'geometry' b"'1133x703+51+273'" b'org.gnome.nautilus.desktop' b'trash-icon-visible' b'false' b'org.gnome.nautilus.desktop' b'volumes-visible' b'false' InstallationDate: Installed on 2018-05-31 (245 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: nautilus UpgradeStatus: Upgraded to cosmic on 2018-10-20 (103 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libarchive/+bug/1814109/+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 1814109] [NEW] Nautilus corrupts 7z archive files when extracting via 'Extract here' context menu
You have been subscribed to a public bug: Nautilus corrupts 7z archive files when extracting via 'Extract here' context menu. Extractions completes without errors, but the files are corrupted (mangled bytes, wrong size). This does happen only when extracting with 'Extract here' context menu action. Using 7z or p7zip via command line or opening the archive via file-roller and then drag single files or directory to a folder works well. This only happens with this particular archive, others 7z archives are extracted correctly. Original 7z archive: https://drive.google.com/open?id=1eZJm1ST3P-52tFSvHXbUn9-WSe_B3Ag9 Re-zipped corrupted archive here: https://drive.google.com/open?id=1N--99RuWdmg6oUGrAz7pLoRpuJOIBEE5 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: nautilus 1:3.26.4-0ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 31 15:03:45 2019 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'222' b'org.gnome.nautilus.window-state' b'geometry' b"'1133x703+51+273'" b'org.gnome.nautilus.desktop' b'trash-icon-visible' b'false' b'org.gnome.nautilus.desktop' b'volumes-visible' b'false' InstallationDate: Installed on 2018-05-31 (245 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: nautilus UpgradeStatus: Upgraded to cosmic on 2018-10-20 (103 days ago) usr_lib_nautilus: ** Affects: libarchive (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- Nautilus corrupts 7z archive files when extracting via 'Extract here' context menu https://bugs.launchpad.net/bugs/1814109 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libarchive in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 311029] Re: curl and pycurl is not compiled with sftp support
Could someone describe a test case using the backend which we could use to test that the feature is working if we enable it to bionic (the 'curl --version' output tells us that the backend is enabled but it would be good to also check that it's actually correctly working) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/311029 Title: curl and pycurl is not compiled with sftp support Status in curl package in Ubuntu: In Progress Status in curl package in Debian: Fix Released Bug description: Binary package hint: curl Running curl --version, I see: Protocols: tftp ftp telnet dict ldap ldaps http file https ftps SFTP is obviously missing, although it is supported by curl upstream The SFTP is also missing from python-pycurl, probably because libcurl doesn't have it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/311029/+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 1813432] Re: Specific PDF file fails to print to HP m551dn printer
Please try to print with lp -d duplex -o fit-to-page -o pdftops-renderer=XXX with XXX bring "hybrid", "gs", "pdftops", "pdftocairo", ... Does this work? -- 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/1813432 Title: Specific PDF file fails to print to HP m551dn printer Status in cups package in Ubuntu: Incomplete Bug description: One particular PDF file is failing to print. I have no idea why. When I say failing to print I mean that my computer thinks the file printed but the printer shows no sign of ever having received it. The display of the printer never changes to show that it is receiving or printing a file, and the job log of the printer doesn't show that it was received either. I also checked the printer event log and it doesn't show any events at the time I attempted to print the file. Unfortunately I can't attach the PDF file itself because it contains private information, and I can't find another PDF that exhibits this problem. I even tried generating a new PDF exactly the same way the old one was generated -- with the scan to email PDF function on my scanner -- and the new PDF prints just fine. I tried uploading the PDF directly to the printer with FTP and it prints just fine that way. I enabled CUPS debug mode before attempting to print the file. Attached is the resulting contents of /var/log/cups/error_log. I wish I knew what was going on here but honestly I have no idea. Perhaps you can learn something from the error_log. I hope so. Other files, including other PDFs, do print. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: cups 2.2.10-3 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 26 17:47:49 2019 InstallationDate: Installed on 2019-01-02 (24 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lpstat: device for duplex: socket://m551dn.kamens.brookline.ma.us:9100 device for HP_LaserJet_500_color_M551_1637DA_: ipps://m551dn.local:443/ipp/print device for simplex: socket://m551dn.kamens.brookline.ma.us:9100 MachineType: Acer Predator G6-710 Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/simplex.ppd', '/etc/cups/ppd/HP_LaserJet_500_color_M551_1637DA_.ppd', '/etc/cups/ppd/duplex.ppd'] failed with exit code 2: grep: /etc/cups/ppd/simplex.ppd: Permission denied grep: /etc/cups/ppd/HP_LaserJet_500_color_M551_1637DA_.ppd: Permission denied grep: /etc/cups/ppd/duplex.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to disco on 2019-01-21 (5 days ago) dmi.bios.date: 05/18/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R01-A4 dmi.board.name: Predator G6-710 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr: dmi.product.family: Acer Desktop dmi.product.name: Predator G6-710 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1813432/+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 1814125] [NEW] gnome-shell eats 100% cpu when seconds display is on and screen is locked
Public bug reported: on my laptop (xiaomi notebook pro), ubuntu 18.10 amd64, standart ubuntu desktop (gnome-shell), no application running just activate second display in gnome tweak, let it lock itself the fan is going fast, simply moving the mouse and the fan slow down. wrote a simple script to append a top every minut in a log file, show that gnome-shell consumes 100% when locked. workaround : disabling second displaying and no more CPU usage / fan noise when locked. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 415.27 Thu Dec 20 17:25:03 CST 2018 GCC version: gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1) ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 31 16:19:16 2019 DistUpgraded: 2018-12-30 21:42:17,971 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 415.27, 4.18.0-13-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Xiaomi UHD Graphics 620 [1d72:1701] Subsystem: Xiaomi Mi Notebook Pro [GeForce MX150] [1d72:1701] InstallationDate: Installed on 2018-06-08 (236 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Timi TM1701 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=174e8747-a737-411b-bfaf-4e6795426fea ro quiet splash nouveau.runpm=0 vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to cosmic on 2018-12-30 (31 days ago) dmi.bios.date: 10/13/2017 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: XMAKB5R0P0502 dmi.board.asset.tag: Any dmi.board.name: TM1701 dmi.board.vendor: Timi dmi.board.version: MP dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Timi dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrXMAKB5R0P0502:bd10/13/2017:svnTimi:pnTM1701:pvr:rvnTimi:rnTM1701:rvrMP:cvnTimi:ct10:cvrChassisVersion: dmi.product.family: Timibook dmi.product.name: TM1701 dmi.sys.vendor: Timi version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic performance ubuntu -- 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/1814125 Title: gnome-shell eats 100% cpu when seconds display is on and screen is locked Status in xorg package in Ubuntu: New Bug description: on my laptop (xiaomi notebook pro), ubuntu 18.10 amd64, standart ubuntu desktop (gnome-shell), no application running just activate second display in gnome tweak, let it lock itself the fan is going fast, simply moving the mouse and the fan slow down. wrote a simple script to append a top every minut in a log file, show that gnome-shell consumes 100% when locked. workaround : disabling second displaying and no more CPU usage / fan noise when locked. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 415.27 Thu Dec 20 17:25:03 CST 2018 GCC version: gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1) ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
[Touch-packages] [Bug 1804487] Re: systemd-resolved has issues when the answer is over 512 bytes with EDNS disabled
Hello Victor, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.12 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: systemd (Ubuntu Bionic) Status: In Progress => 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 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 Committed Status in systemd source package in Cosmic: Fix Committed 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 1811471] Re: local resolver stub fails to handle multiple TCP dns queries
Hello Dan, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.12 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: systemd (Ubuntu Bionic) Status: In Progress => 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 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 Committed Status in systemd source package in Trusty: Invalid Status in systemd source package in Xenial: Invalid Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Cosmic: Fix Committed Status in systemd source package in Disco: Fix Committed 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
[Touch-packages] [Bug 1814124] [NEW] sshd does not start after update
Public bug reported: After processing system update by: apt-get clean && apt-get autoclean && apt-get autoremove && apt-get update && apt-get upgrade && apt-get dist-upgrade && reboot ssh server stops starting at system boot. It starts after doing: mkdir /var/run/sshd chmod 0755 /var/run/sshd service ssh start It happens on fresh Ubuntu-16.04 installs on every VPS provide I have tested so far. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: openssh-server 1:7.2p2-4ubuntu2.6 Uname: Linux 2.6.32-042stab127.2 x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Thu Jan 31 10:18:56 2019 ProcEnviron: TERM=xterm PATH=(custom, no user) SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: Missing privilege separation directory: /var/run/sshd SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1814124 Title: sshd does not start after update Status in openssh package in Ubuntu: New Bug description: After processing system update by: apt-get clean && apt-get autoclean && apt-get autoremove && apt-get update && apt-get upgrade && apt-get dist-upgrade && reboot ssh server stops starting at system boot. It starts after doing: mkdir /var/run/sshd chmod 0755 /var/run/sshd service ssh start It happens on fresh Ubuntu-16.04 installs on every VPS provide I have tested so far. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: openssh-server 1:7.2p2-4ubuntu2.6 Uname: Linux 2.6.32-042stab127.2 x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Thu Jan 31 10:18:56 2019 ProcEnviron: TERM=xterm PATH=(custom, no user) SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: Missing privilege separation directory: /var/run/sshd SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1814124/+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 1804487] Re: systemd-resolved has issues when the answer is over 512 bytes with EDNS disabled
Hello Victor, or anyone else affected, Accepted systemd into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/239-7ubuntu10.7 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: systemd (Ubuntu Cosmic) Status: In Progress => Fix Committed ** Tags removed: verification-done verification-done-cosmic ** 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 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 Committed Status in systemd source package in Cosmic: Fix Committed 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 1811471] Re: local resolver stub fails to handle multiple TCP dns queries
Hello Dan, or anyone else affected, Accepted systemd into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/239-7ubuntu10.7 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: systemd (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 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 Committed Status in systemd source package in Trusty: Invalid Status in systemd source package in Xenial: Invalid Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Cosmic: Fix Committed Status in systemd source package in Disco: Fix Committed 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
