[Touch-packages] [Bug 1844132] Re: FFe: Mesa 19.2.0
Mmkay, based on the above, I say go for it. It'll miss beta (unless we have reason to respin, I guess), but such is life. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1844132 Title: FFe: Mesa 19.2.0 Status in mesa package in Ubuntu: Confirmed Status in mesa source package in Eoan: Confirmed Bug description: It would be great to get 19.2.0 in eoan, though it's release cycle has slipped. It's working fine on a typical desktop use here on i915 (Kaby Lake). It would also migrate to llvm-9. It is currently at rc3, and final version is expected to arrive next week (week 39). New features: Full support for Intel Ice Lake Support for AMD Navi GL_ARB_post_depth_coverage on radeonsi (Navi) GL_ARB_seamless_cubemap_per_texture on etnaviv (if GPU supports SEAMLESS_CUBE_MAP) GL_EXT_shader_image_load_store on radeonsi (with LLVM >= 10) GL_EXT_shader_samples_identical on iris and radeonsi (if using NIR) GL_EXT_texture_shadow_lod on i965, iris EGL_EXT_platform_device VK_AMD_buffer_marker on radv VK_EXT_index_type_uint8 on radv VK_EXT_post_depth_coverage on radv VK_EXT_queue_family_foreign on radv VK_EXT_sample_locations on radv VK_EXT_shader_demote_to_helper_invocation on Intel. VK_KHR_depth_stencil_resolve on radv VK_KHR_imageless_framebuffer on radv VK_KHR_shader_atomic_int64 on radv VK_KHR_uniform_buffer_standard_layout on radv (note: iris is the new DRI driver for newer Intel, not enabled by default yet) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1844132/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1222602]
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/727. -- 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/1222602 Title: [regression] [gen3] Mesa 9.2 makes Unity unusable on Atom class hardware and 943/945 graphics controllers Status in Mesa: Unknown Status in Nux: Fix Released Status in Release Notes for Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in nux package in Ubuntu: Fix Released Status in unity package in Ubuntu: Invalid Bug description: After the upgrade to Mesa 9.2.0 unity is barely usable. Dash, Alt+Tab switcher and Alt+F2 command line shows in more than 1 minute, using 100% cpu. A downgrade to mesa 9.1.6-2ubuntu2 restores full performance. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libgl1-mesa-glx 9.2-1ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0 Uname: Linux 3.11.0-5-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.12.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Sep 9 01:51:45 2013 DistUpgraded: 2013-09-08 20:36:47,811 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller [8086:27ae] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. Device [1462:0110] Subsystem: Micro-Star International Co., Ltd. Device [1462:0110] InstallationDate: Installed on 2013-09-07 (1 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MachineType: MICRO-STAR INTERNATIONAL CO., LTD U90/U100 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-5-generic root=UUID=674329c8-d0a6-4954-89c0-72821cfa0ba8 ro quiet splash vt.handoff=7 SourcePackage: mesa UpgradeStatus: Upgraded to saucy on 2013-09-08 (0 days ago) dmi.bios.date: 12/01/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: U90/U100 dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.board.version: Ver.001 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.chassis.version: Ver.001 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.3:bd12/01/2009:svnMICRO-STARINTERNATIONALCO.,LTD:pnU90/U100:pvrVer.001:rvnMICRO-STARINTERNATIONALCO.,LTD:rnU90/U100:rvrVer.001:cvnMICRO-STARINTERNATIONALCO.,LTD:ct10:cvrVer.001: dmi.product.name: U90/U100 dmi.product.version: Ver.001 dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD version.compiz: compiz 1:0.9.10+13.10.20130828.2-0ubuntu1 version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu6 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Mon Sep 9 01:46:55 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1001 vendor HSD xserver.version: 2:1.14.2.901-2ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1222602/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1222602] Re: [regression] [gen3] Mesa 9.2 makes Unity unusable on Atom class hardware and 943/945 graphics controllers
** Changed in: mesa Status: Confirmed => Unknown ** Bug watch added: gitlab.freedesktop.org/mesa/mesa/issues #727 https://gitlab.freedesktop.org/mesa/mesa/issues/727 -- 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/1222602 Title: [regression] [gen3] Mesa 9.2 makes Unity unusable on Atom class hardware and 943/945 graphics controllers Status in Mesa: Unknown Status in Nux: Fix Released Status in Release Notes for Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in nux package in Ubuntu: Fix Released Status in unity package in Ubuntu: Invalid Bug description: After the upgrade to Mesa 9.2.0 unity is barely usable. Dash, Alt+Tab switcher and Alt+F2 command line shows in more than 1 minute, using 100% cpu. A downgrade to mesa 9.1.6-2ubuntu2 restores full performance. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libgl1-mesa-glx 9.2-1ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0 Uname: Linux 3.11.0-5-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.12.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Sep 9 01:51:45 2013 DistUpgraded: 2013-09-08 20:36:47,811 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller [8086:27ae] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. Device [1462:0110] Subsystem: Micro-Star International Co., Ltd. Device [1462:0110] InstallationDate: Installed on 2013-09-07 (1 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MachineType: MICRO-STAR INTERNATIONAL CO., LTD U90/U100 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-5-generic root=UUID=674329c8-d0a6-4954-89c0-72821cfa0ba8 ro quiet splash vt.handoff=7 SourcePackage: mesa UpgradeStatus: Upgraded to saucy on 2013-09-08 (0 days ago) dmi.bios.date: 12/01/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: U90/U100 dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.board.version: Ver.001 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.chassis.version: Ver.001 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.3:bd12/01/2009:svnMICRO-STARINTERNATIONALCO.,LTD:pnU90/U100:pvrVer.001:rvnMICRO-STARINTERNATIONALCO.,LTD:rnU90/U100:rvrVer.001:cvnMICRO-STARINTERNATIONALCO.,LTD:ct10:cvrVer.001: dmi.product.name: U90/U100 dmi.product.version: Ver.001 dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD version.compiz: compiz 1:0.9.10+13.10.20130828.2-0ubuntu1 version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu6 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Mon Sep 9 01:46:55 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1001 vendor HSD xserver.version: 2:1.14.2.901-2ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1222602/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1275042] Re: Wrong colors with Mesa 11.1.2-1 on ubuntu MATE 16.04 PowerPC
** No longer affects: mesa (Ubuntu) ** Project changed: mesa => mesa (Ubuntu) ** Changed in: mesa (Ubuntu) Status: Unknown => New ** Changed in: mesa (Ubuntu) Remote watch: freedesktop.org Bugzilla #72877 => None ** Changed in: mesa (Ubuntu) Status: New => Triaged ** Description changed: - Hi all, + Upstream report: + https://gitlab.freedesktop.org/mesa/mesa/issues/477 I've tried Mesa 9.2.2-1 and 10.0.1 on Debian Sid, Lubuntu 13.10, and on Lubuntu 14.04. Unfortunately all have issued false colors in games. They appear to be ABGR instead of RGBA, thus blue becomes green, red becomes alpha etc. This issue affects sdl2 applications either. The Mesa version 11.1.2-1 doesn't work either on ubuntu MATE 16.04 PowerPC. Mesa 8.0.5-4 and Mesa 9.1.6 have no color problem. The transitional solution is to install the old Mesa 8.0.X with "Force Version" with the Synaptic package manager on new distributions. In my point of view, the problem is in the source file p_format.h in the directory src/gallium/include/pipe/. There is some code for translating colors for big-endian machines. The problem is, this code is only for the CPU. I mean for LLVMpipe for the CPU. The Radeon graphics cards don't need this translating code but IBM pSeries machines without graphics cards need this code. This code translates the colors in a wrong way for Radeon graphics cards. I removed this code and after compiling Mesa again, the colors are displayed correctly. I released some unofficial Mesa versions with this patch. Downloads: http://www.supertuxkart-amiga.de/amiga/mesalib- unofficial.html Hardware: AmigaOne X1000 (Nemo) PA Semi Dual-core PA6T-1682M, 1.8GHz PowerISA™ v2.04+ CPU "Xena" 500MHz XMOS XS1-L2 124 8GB DDR2 SDRAM XFX Radeon HD 6870, 1 GB RAM OCZ600MXSP 600 Switching power supply RTL 8139/8139C/8139C+ network card TSSTcorp CDDVDW SH-224BB dvd drive ATA ST2000DM001-9YN1 SEAGATE HD ATA ESA 3SF1240GB HD More information: http://en.wikipedia.org/wiki/AmigaOne_X1000 http://www.supertuxkart-amiga.de/amiga/x1000.html Rgds, Christian --- ApportVersion: 2.20-0ubuntu3 Architecture: powerpc CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: MATE DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Barts XT [Radeon HD 6870] [1002:6738] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Barts XT [Radeon HD 6870] [1682:3107] Package: libgl1-mesa-dri 11.1.2-1ubuntu1 PackageArchitecture: powerpc ProcKernelCmdLine: root=/dev/sdb1 quiet ro splash ProcModules: kvm_pr 91899 0 - Live 0x Tags: xenial ubuntu Uname: Linux 4.5.0-rc6_A-EON_AmigaONE_X1000_Nemo ppc64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1 -- 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/1275042 Title: Wrong colors with Mesa 11.1.2-1 on ubuntu MATE 16.04 PowerPC Status in mesa package in Ubuntu: Triaged Bug description: Upstream report: https://gitlab.freedesktop.org/mesa/mesa/issues/477 I've tried Mesa 9.2.2-1 and 10.0.1 on Debian Sid, Lubuntu 13.10, and on Lubuntu 14.04. Unfortunately all have issued false colors in games. They appear to be ABGR instead of RGBA, thus blue becomes green, red becomes alpha etc. This issue affects sdl2 applications either. The Mesa version 11.1.2-1 doesn't work either on ubuntu MATE 16.04 PowerPC. Mesa 8.0.5-4 and Mesa 9.1.6 have no color problem. The transitional solution is to install the old Mesa 8.0.X with "Force Version" with the Synaptic package manager on new distributions. In my point of view, the problem is in the source file p_format.h in the directory src/gallium/include/pipe/. There is some code for translating colors for big-endian machines. The problem is, this code is only for the CPU. I mean for LLVMpipe for the CPU. The Radeon graphics cards don't need this
[Touch-packages] [Bug 1275042] [NEW] Wrong colors with Mesa 11.1.2-1 on ubuntu MATE 16.04 PowerPC
You have been subscribed to a public bug: Hi all, I've tried Mesa 9.2.2-1 and 10.0.1 on Debian Sid, Lubuntu 13.10, and on Lubuntu 14.04. Unfortunately all have issued false colors in games. They appear to be ABGR instead of RGBA, thus blue becomes green, red becomes alpha etc. This issue affects sdl2 applications either. The Mesa version 11.1.2-1 doesn't work either on ubuntu MATE 16.04 PowerPC. Mesa 8.0.5-4 and Mesa 9.1.6 have no color problem. The transitional solution is to install the old Mesa 8.0.X with "Force Version" with the Synaptic package manager on new distributions. In my point of view, the problem is in the source file p_format.h in the directory src/gallium/include/pipe/. There is some code for translating colors for big-endian machines. The problem is, this code is only for the CPU. I mean for LLVMpipe for the CPU. The Radeon graphics cards don't need this translating code but IBM pSeries machines without graphics cards need this code. This code translates the colors in a wrong way for Radeon graphics cards. I removed this code and after compiling Mesa again, the colors are displayed correctly. I released some unofficial Mesa versions with this patch. Downloads: http://www.supertuxkart-amiga.de/amiga/mesalib- unofficial.html Hardware: AmigaOne X1000 (Nemo) PA Semi Dual-core PA6T-1682M, 1.8GHz PowerISA™ v2.04+ CPU "Xena" 500MHz XMOS XS1-L2 124 8GB DDR2 SDRAM XFX Radeon HD 6870, 1 GB RAM OCZ600MXSP 600 Switching power supply RTL 8139/8139C/8139C+ network card TSSTcorp CDDVDW SH-224BB dvd drive ATA ST2000DM001-9YN1 SEAGATE HD ATA ESA 3SF1240GB HD More information: http://en.wikipedia.org/wiki/AmigaOne_X1000 http://www.supertuxkart-amiga.de/amiga/x1000.html Rgds, Christian --- ApportVersion: 2.20-0ubuntu3 Architecture: powerpc CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: MATE DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Barts XT [Radeon HD 6870] [1002:6738] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Barts XT [Radeon HD 6870] [1682:3107] Package: libgl1-mesa-dri 11.1.2-1ubuntu1 PackageArchitecture: powerpc ProcKernelCmdLine: root=/dev/sdb1 quiet ro splash ProcModules: kvm_pr 91899 0 - Live 0x Tags: xenial ubuntu Uname: Linux 4.5.0-rc6_A-EON_AmigaONE_X1000_Nemo ppc64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1 ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected regression-release saucy trusty ubuntu xenial -- Wrong colors with Mesa 11.1.2-1 on ubuntu MATE 16.04 PowerPC https://bugs.launchpad.net/bugs/1275042 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa 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 1507247] Re: avahi-daemon dies after about a minute
I actually have a fix for this. The reason why the daemon is dying is because dbus is disabled in avahi and the configuration expects DBUS to be enabled for status checking. Make sure you have "enable-dbus=yes" in avahi-daemon.conf :) ** Changed in: avahi (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1507247 Title: avahi-daemon dies after about a minute Status in avahi package in Ubuntu: Fix Committed Bug description: So I thought I'd try running Vagrant inside of an Ubuntu VM to do some development work as detailed here: http://taoofmac.com/space/HOWTO/Vagrant When the box starts up, there is a short delay before broadcasting begins, and I'm able to ping the guest (in this case registered as "hobo-container.local"). Then, after a minute or two, it stops responding. The logs look like this: -- Logs begin at Thu 2015-10-15 14:36:55 EDT, end at Thu 2015-10-15 14:40:00 EDT. -- Oct 15 14:36:58 hobo-container systemd[1]: Starting Avahi mDNS/DNS-SD Stack... Oct 15 14:36:58 hobo-container avahi-daemon[507]: Found user 'avahi' (UID 110) and group 'avahi' (GID 119). Oct 15 14:36:58 hobo-container avahi-daemon[507]: Successfully dropped root privileges. Oct 15 14:36:58 hobo-container avahi-daemon[507]: avahi-daemon 0.6.31 starting up. Oct 15 14:36:58 hobo-container avahi-daemon[507]: Successfully called chroot(). Oct 15 14:36:58 hobo-container avahi-daemon[507]: Successfully dropped remaining capabilities. Oct 15 14:36:58 hobo-container avahi-daemon[507]: Loading service file /services/ssh.service. Oct 15 14:36:58 hobo-container avahi-daemon[507]: Joining mDNS multicast group on interface eth1.IPv6 with address fe80::a0 Oct 15 14:36:58 hobo-container avahi-daemon[507]: New relevant interface eth1.IPv6 for mDNS. Oct 15 14:36:58 hobo-container avahi-daemon[507]: Joining mDNS multicast group on interface eth1.IPv4 with address 203.0.11 Oct 15 14:36:58 hobo-container avahi-daemon[507]: New relevant interface eth1.IPv4 for mDNS. Oct 15 14:36:58 hobo-container avahi-daemon[507]: Network interface enumeration completed. Oct 15 14:36:58 hobo-container avahi-daemon[507]: Registering new address record for fe80::a00:27ff:fef9:e38c on eth1.*. Oct 15 14:36:58 hobo-container avahi-daemon[507]: Registering new address record for 203.0.113.2 on eth1.IPv4. Oct 15 14:36:58 hobo-container avahi-daemon[507]: Registering HINFO record with values 'X86_64'/'LINUX'. Oct 15 14:36:58 hobo-container avahi-daemon[507]: Joining mDNS multicast group on interface lxcbr0.IPv4 with address 10.0.3 Oct 15 14:36:58 hobo-container avahi-daemon[507]: New relevant interface lxcbr0.IPv4 for mDNS. Oct 15 14:36:58 hobo-container avahi-daemon[507]: Registering new address record for 10.0.3.1 on lxcbr0.IPv4. Oct 15 14:36:59 hobo-container avahi-daemon[507]: Server startup complete. Host name is hobo-container.local. Local service Oct 15 14:37:00 hobo-container avahi-daemon[507]: Joining mDNS multicast group on interface lxcbr0.IPv6 with address fe80:: Oct 15 14:37:00 hobo-container avahi-daemon[507]: New relevant interface lxcbr0.IPv6 for mDNS. Oct 15 14:37:00 hobo-container avahi-daemon[507]: Registering new address record for fe80::704a:9bff:fe76:a607 on lxcbr0.*. Oct 15 14:37:01 hobo-container avahi-daemon[507]: Service "hobo-container" (/services/ssh.service) successfully established Oct 15 14:38:28 hobo-container systemd[1]: avahi-daemon.service start operation timed out. Terminating. Oct 15 14:38:28 hobo-container avahi-daemon[507]: Got SIGTERM, quitting. Oct 15 14:38:28 hobo-container avahi-daemon[507]: Leaving mDNS multicast group on interface lxcbr0.IPv6 with address fe80:: Oct 15 14:38:28 hobo-container avahi-daemon[507]: Leaving mDNS multicast group on interface lxcbr0.IPv4 with address 10.0.3 Oct 15 14:38:28 hobo-container avahi-daemon[507]: Leaving mDNS multicast group on interface eth1.IPv6 with address fe80::a0 Oct 15 14:38:28 hobo-container avahi-daemon[507]: Leaving mDNS multicast group on interface eth1.IPv4 with address 203.0.11 Oct 15 14:38:28 hobo-container systemd[1]: Failed to start Avahi mDNS/DNS-SD Stack. Oct 15 14:38:28 hobo-container systemd[1]: Unit avahi-daemon.service entered failed state. Oct 15 14:38:28 hobo-container systemd[1]: avahi-daemon.service failed. Further attempts to restart the service fail: $ sudo service avahi-daemon start Job for avahi-daemon.service failed. See "systemctl status avahi-daemon.service" and "journalctl -xe" for details. With similar logs: Oct 15 14:41:16 hobo-container systemd[1]: Starting Avahi mDNS/DNS-SD Stack... Oct 15 14:41:16 hobo-container avahi-daemon[1099]: Found user 'avahi' (UID 110) and group 'avahi' (GID 119). Oct 15 14:41:16 hobo-container avahi-daemon[1099]:
[Touch-packages] [Bug 1844763] Re: file /etc/network/interfaces is missing in eoan-desktop-amd64.iso
Hi team, Please let us know if this is as-designed or not, Ubuntu desktop version was using /etc/network/interfaces to configure static IP address and etc... Best regards, Pengpeng -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1844763 Title: file /etc/network/interfaces is missing in eoan-desktop-amd64.iso Status in network-manager package in Ubuntu: Confirmed Bug description: The file /etc/network/interfaces is missing after install guestOS with eoan-desktop-amd64.iso(daily build Sep-17-2019) in ESXi. This issue cause a failure for VMware Guest OS Customization To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1844763/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1275042] Re: Wrong colors with Mesa 11.1.2-1 on ubuntu MATE 16.04 PowerPC
** Changed in: mesa Status: Confirmed => Unknown ** Bug watch added: gitlab.freedesktop.org/mesa/mesa/issues #477 https://gitlab.freedesktop.org/mesa/mesa/issues/477 -- 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/1275042 Title: Wrong colors with Mesa 11.1.2-1 on ubuntu MATE 16.04 PowerPC Status in Mesa: Unknown Status in mesa package in Ubuntu: Triaged Bug description: Hi all, I've tried Mesa 9.2.2-1 and 10.0.1 on Debian Sid, Lubuntu 13.10, and on Lubuntu 14.04. Unfortunately all have issued false colors in games. They appear to be ABGR instead of RGBA, thus blue becomes green, red becomes alpha etc. This issue affects sdl2 applications either. The Mesa version 11.1.2-1 doesn't work either on ubuntu MATE 16.04 PowerPC. Mesa 8.0.5-4 and Mesa 9.1.6 have no color problem. The transitional solution is to install the old Mesa 8.0.X with "Force Version" with the Synaptic package manager on new distributions. In my point of view, the problem is in the source file p_format.h in the directory src/gallium/include/pipe/. There is some code for translating colors for big-endian machines. The problem is, this code is only for the CPU. I mean for LLVMpipe for the CPU. The Radeon graphics cards don't need this translating code but IBM pSeries machines without graphics cards need this code. This code translates the colors in a wrong way for Radeon graphics cards. I removed this code and after compiling Mesa again, the colors are displayed correctly. I released some unofficial Mesa versions with this patch. Downloads: http://www.supertuxkart-amiga.de/amiga/mesalib- unofficial.html Hardware: AmigaOne X1000 (Nemo) PA Semi Dual-core PA6T-1682M, 1.8GHz PowerISA™ v2.04+ CPU "Xena" 500MHz XMOS XS1-L2 124 8GB DDR2 SDRAM XFX Radeon HD 6870, 1 GB RAM OCZ600MXSP 600 Switching power supply RTL 8139/8139C/8139C+ network card TSSTcorp CDDVDW SH-224BB dvd drive ATA ST2000DM001-9YN1 SEAGATE HD ATA ESA 3SF1240GB HD More information: http://en.wikipedia.org/wiki/AmigaOne_X1000 http://www.supertuxkart-amiga.de/amiga/x1000.html Rgds, Christian --- ApportVersion: 2.20-0ubuntu3 Architecture: powerpc CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: MATE DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Barts XT [Radeon HD 6870] [1002:6738] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Barts XT [Radeon HD 6870] [1682:3107] Package: libgl1-mesa-dri 11.1.2-1ubuntu1 PackageArchitecture: powerpc ProcKernelCmdLine: root=/dev/sdb1 quiet ro splash ProcModules: kvm_pr 91899 0 - Live 0x Tags: xenial ubuntu Uname: Linux 4.5.0-rc6_A-EON_AmigaONE_X1000_Nemo ppc64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1275042/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1275042]
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/477. -- 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/1275042 Title: Wrong colors with Mesa 11.1.2-1 on ubuntu MATE 16.04 PowerPC Status in Mesa: Unknown Status in mesa package in Ubuntu: Triaged Bug description: Hi all, I've tried Mesa 9.2.2-1 and 10.0.1 on Debian Sid, Lubuntu 13.10, and on Lubuntu 14.04. Unfortunately all have issued false colors in games. They appear to be ABGR instead of RGBA, thus blue becomes green, red becomes alpha etc. This issue affects sdl2 applications either. The Mesa version 11.1.2-1 doesn't work either on ubuntu MATE 16.04 PowerPC. Mesa 8.0.5-4 and Mesa 9.1.6 have no color problem. The transitional solution is to install the old Mesa 8.0.X with "Force Version" with the Synaptic package manager on new distributions. In my point of view, the problem is in the source file p_format.h in the directory src/gallium/include/pipe/. There is some code for translating colors for big-endian machines. The problem is, this code is only for the CPU. I mean for LLVMpipe for the CPU. The Radeon graphics cards don't need this translating code but IBM pSeries machines without graphics cards need this code. This code translates the colors in a wrong way for Radeon graphics cards. I removed this code and after compiling Mesa again, the colors are displayed correctly. I released some unofficial Mesa versions with this patch. Downloads: http://www.supertuxkart-amiga.de/amiga/mesalib- unofficial.html Hardware: AmigaOne X1000 (Nemo) PA Semi Dual-core PA6T-1682M, 1.8GHz PowerISA™ v2.04+ CPU "Xena" 500MHz XMOS XS1-L2 124 8GB DDR2 SDRAM XFX Radeon HD 6870, 1 GB RAM OCZ600MXSP 600 Switching power supply RTL 8139/8139C/8139C+ network card TSSTcorp CDDVDW SH-224BB dvd drive ATA ST2000DM001-9YN1 SEAGATE HD ATA ESA 3SF1240GB HD More information: http://en.wikipedia.org/wiki/AmigaOne_X1000 http://www.supertuxkart-amiga.de/amiga/x1000.html Rgds, Christian --- ApportVersion: 2.20-0ubuntu3 Architecture: powerpc CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: MATE DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Barts XT [Radeon HD 6870] [1002:6738] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Barts XT [Radeon HD 6870] [1682:3107] Package: libgl1-mesa-dri 11.1.2-1ubuntu1 PackageArchitecture: powerpc ProcKernelCmdLine: root=/dev/sdb1 quiet ro splash ProcModules: kvm_pr 91899 0 - Live 0x Tags: xenial ubuntu Uname: Linux 4.5.0-rc6_A-EON_AmigaONE_X1000_Nemo ppc64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1275042/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1845076] [NEW] Gnome shell/Xorg freeze after remote connection with monitor unplugged
Public bug reported: I was trying to have a remote connection on a Ubuntu 18.04 pc with nomachine (but the behavior with Anydesk is the same) AFTER I unplugged the monitor form that pc. Once connected the output on the client freeze by just opening the Activities panel. If I plug the monitor back in on the server, the gnome shell is glitched and the only way to gain back control is by doing ALT F2 and then r. If I keep the monitor plugged in but turned off everything will work as it should. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Sep 24 00:24:03 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GP107 [GeForce GTX 1050 Ti] [19da:2454] InstallationDate: Installed on 2019-07-16 (69 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 6.0 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic root=UUID=dfa66545-9ac3-41fa-817b-433d8a61bd78 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: GA-78LMT-USB3 6.0 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-78LMT-USB3 6.0 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic false-gpu-hang freeze ubuntu ** Summary changed: - Gnome shell freeze after remote connection with monitor unplugged + Gnome shell/Xorg freeze after remote connection with monitor unplugged -- 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/1845076 Title: Gnome shell/Xorg freeze after remote connection with monitor unplugged Status in xorg package in Ubuntu: New Bug description: I was trying to have a remote connection on a Ubuntu 18.04 pc with nomachine (but the behavior with Anydesk is the same) AFTER I unplugged the monitor form that pc. Once connected the output on the client freeze by just opening the Activities panel. If I plug the monitor back in on the server, the gnome shell is glitched and the only way to gain back control is by doing ALT F2 and then r. If I keep the monitor plugged in but turned off everything will work as it should. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Sep 24 00:24:03 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GP107 [GeForce GTX 1050 Ti] [19da:2454] InstallationDate: Installed on 2019-07-16 (69 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 6.0 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic root=UUID=dfa66545-9ac3-41fa-817b-433d8a61bd78 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display
[Touch-packages] [Bug 1844132] Re: FFe: Mesa 19.2.0
1) yes, the upstream schedule slip has meant that .0 (which should be released tomorrow/the day after) is better than the usual .0 release 2) there will be a point release every two weeks, so the first one should arrive roughly around Oct 9th -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1844132 Title: FFe: Mesa 19.2.0 Status in mesa package in Ubuntu: Confirmed Status in mesa source package in Eoan: Confirmed Bug description: It would be great to get 19.2.0 in eoan, though it's release cycle has slipped. It's working fine on a typical desktop use here on i915 (Kaby Lake). It would also migrate to llvm-9. It is currently at rc3, and final version is expected to arrive next week (week 39). New features: Full support for Intel Ice Lake Support for AMD Navi GL_ARB_post_depth_coverage on radeonsi (Navi) GL_ARB_seamless_cubemap_per_texture on etnaviv (if GPU supports SEAMLESS_CUBE_MAP) GL_EXT_shader_image_load_store on radeonsi (with LLVM >= 10) GL_EXT_shader_samples_identical on iris and radeonsi (if using NIR) GL_EXT_texture_shadow_lod on i965, iris EGL_EXT_platform_device VK_AMD_buffer_marker on radv VK_EXT_index_type_uint8 on radv VK_EXT_post_depth_coverage on radv VK_EXT_queue_family_foreign on radv VK_EXT_sample_locations on radv VK_EXT_shader_demote_to_helper_invocation on Intel. VK_KHR_depth_stencil_resolve on radv VK_KHR_imageless_framebuffer on radv VK_KHR_shader_atomic_int64 on radv VK_KHR_uniform_buffer_standard_layout on radv (note: iris is the new DRI driver for newer Intel, not enabled by default yet) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1844132/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1844132] Re: FFe: Mesa 19.2.0
Just tested 19.2 RC4 from the ppa on a Radeon RX 570. Everything works fine, desktop and games (I've tested Witcher 3, CS:GO, HoN). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1844132 Title: FFe: Mesa 19.2.0 Status in mesa package in Ubuntu: Confirmed Status in mesa source package in Eoan: Confirmed Bug description: It would be great to get 19.2.0 in eoan, though it's release cycle has slipped. It's working fine on a typical desktop use here on i915 (Kaby Lake). It would also migrate to llvm-9. It is currently at rc3, and final version is expected to arrive next week (week 39). New features: Full support for Intel Ice Lake Support for AMD Navi GL_ARB_post_depth_coverage on radeonsi (Navi) GL_ARB_seamless_cubemap_per_texture on etnaviv (if GPU supports SEAMLESS_CUBE_MAP) GL_EXT_shader_image_load_store on radeonsi (with LLVM >= 10) GL_EXT_shader_samples_identical on iris and radeonsi (if using NIR) GL_EXT_texture_shadow_lod on i965, iris EGL_EXT_platform_device VK_AMD_buffer_marker on radv VK_EXT_index_type_uint8 on radv VK_EXT_post_depth_coverage on radv VK_EXT_queue_family_foreign on radv VK_EXT_sample_locations on radv VK_EXT_shader_demote_to_helper_invocation on Intel. VK_KHR_depth_stencil_resolve on radv VK_KHR_imageless_framebuffer on radv VK_KHR_shader_atomic_int64 on radv VK_KHR_uniform_buffer_standard_layout on radv (note: iris is the new DRI driver for newer Intel, not enabled by default yet) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1844132/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843479] Re: gzip in Ubuntu Eoan results in Exec format error on WSL1
>From the WSL issues page: > Now, thing is, all of the new binaries (f.e. /bin/ls) have that .plt.sec section also, and they work just fine. Also compiling a hello.c with -fcf-protection works. Because of course it does. The only other new section in there (Disco gzip has 27 sections, Eoan has 29) is .note.gnu.property. No joy after stripping that either. Meh. It's not .note.ABI-tag; I stripped that as a WAG right after this issue was posted. Which is all a long description of things that don't work. Next thing to try would be to grab the apt-source, try to build a broken binary, and then try to guess what makes gzip so special (contrast say /bin/ls). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gzip in Ubuntu. https://bugs.launchpad.net/bugs/1843479 Title: gzip in Ubuntu Eoan results in Exec format error on WSL1 Status in gzip package in Ubuntu: Confirmed Bug description: Summary: Running gzip on WSL1 results in the following error: $ gzip -bash: /bin/gzip: cannot execute binary file: Exec format error What I expect to happen: gzip executes correctly on WSL1. What happens instead: gzip fails with an Exec format error. Notes: I suspect a change in how gzip is being built for Eoan is causing issues with ELF parsing on the WSL1 translation layer. For example: On Disco with gzip 1.9-3: $ file /bin/gzip /bin/gzip: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, BuildID[sha1]=efa859c26eaf8e035efe9a139361e2a60cd17b3e, stripped On Eoan with gzip 1.10-0ubuntu3: $ file /bin/gzip /bin/gzip: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=bc0f5994544c2a469d04c914bf4bf44b4ded6040, for GNU/Linux 3.2.0, stripped Eoan ships with gzip 1.10, while Disco ships with gzip 1.9, but I do not believe this is an issue in 1.10 because this error does not occur when building gzip from GNU project source on Ubuntu Eoan. Justifications: WSL1 will need to be patched in future Windows builds for this change in ELF. However that patch will likely not be backported to older builds of Windows, including Windows Enterprise/Server 2019. To ensure Eoan can run on current and older builds of Windows Ubuntu should consider looking at how it's building gzip and see if it can be made to 'play nice' until WSL1 can be updated. This was originally reported here: https://github.com/microsoft/WSL/issues/4461 Details: Description:Ubuntu Eoan Ermine (development branch) Release:19.10 gzip: Installed: 1.10-0ubuntu3 Candidate: 1.10-0ubuntu3 Version table: *** 1.10-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gzip/+bug/1843479/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1845046] [NEW] [WH-1000XM3, playback] Hearing input and output audio until disconnecting and reconnecting
Public bug reported: Whenever I turn on my headphones theyll connect to my computer but im able to hear the input audio from my microphone and low quality output audio. I have to disconnect the headphones in the bluetooth devices and reconnect for it to fix the problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: litleck1398 F pulseaudio /dev/snd/controlC0: litleck1398 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Sep 23 17:07:59 2019 InstallationDate: Installed on 2019-09-22 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: WH-1000XM3 Symptom_Type: High background noise, or volume is too low Title: [WH-1000XM3, playback] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2019 dmi.bios.vendor: Alienware dmi.bios.version: 1.0.19 dmi.board.name: 01NYPT dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.0.19:bd02/12/2019:svnAlienware:pnAlienwareAuroraR5:pvr1.0.19:rvnAlienware:rn01NYPT:rvrA00:cvnAlienware:ct3:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware Aurora R5 dmi.product.sku: 0729 dmi.product.version: 1.0.19 dmi.sys.vendor: Alienware ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1845046 Title: [WH-1000XM3, playback] Hearing input and output audio until disconnecting and reconnecting Status in pulseaudio package in Ubuntu: New Bug description: Whenever I turn on my headphones theyll connect to my computer but im able to hear the input audio from my microphone and low quality output audio. I have to disconnect the headphones in the bluetooth devices and reconnect for it to fix the problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: litleck1398 F pulseaudio /dev/snd/controlC0: litleck1398 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Sep 23 17:07:59 2019 InstallationDate: Installed on 2019-09-22 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: WH-1000XM3 Symptom_Type: High background noise, or volume is too low Title: [WH-1000XM3, playback] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2019 dmi.bios.vendor: Alienware dmi.bios.version: 1.0.19 dmi.board.name: 01NYPT dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.0.19:bd02/12/2019:svnAlienware:pnAlienwareAuroraR5:pvr1.0.19:rvnAlienware:rn01NYPT:rvrA00:cvnAlienware:ct3:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware Aurora R5 dmi.product.sku: 0729 dmi.product.version: 1.0.19 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1845046/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1707884] Re: GTK3 tooltips are corrupted after latest update
Launchpad has imported 23 comments from the remote bug at https://bugs.freedesktop.org/show_bug.cgi?id=102013. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2017-08-02T10:08:47+00:00 Amr Ibrahim wrote: Created attachment 133192 GTK3 tooltips are corrupted After updating to Radeon 7.9.0 in Ubuntu 16.04.3, I noticed that all GTK3 tooltips are corrupted. See the attached screencast. Other tooltips are not affected. Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1707884/comments/10 On 2017-08-02T10:14:58+00:00 Amr Ibrahim wrote: Created attachment 133193 Xorg log Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1707884/comments/11 On 2017-08-02T14:09:14+00:00 Michel Dänzer wrote: Does Option "AccelMethod" "EXA" in /etc/X11/xorg.conf avoid the problem? If not, please attach the corresponding Xorg log file. Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1707884/comments/12 On 2017-08-02T15:26:42+00:00 Amr Ibrahim wrote: I don't have this file /etc/X11/xorg.conf. Please tell me what the content of it would be so I can create a new one. Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1707884/comments/13 On 2017-08-02T22:13:50+00:00 Amr Ibrahim wrote: Michel, yes, adding that option fixes the tooltips problem. It also fixes another bug about artefacts when resizing windows. I attached a screencast. Downstream https://launchpad.net/bugs/1707893 Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1707884/comments/14 On 2017-08-02T22:16:44+00:00 Amr Ibrahim wrote: Created attachment 133215 Xorg log after Option "AccelMethod" "EXA" Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1707884/comments/15 On 2017-08-02T22:27:49+00:00 Amr Ibrahim wrote: Created attachment 133217 Resizing windows artefacts before Option "AccelMethod" "EXA" This screencast is before the Option "AccelMethod" "EXA". After applying the option, the artefacts are gone. Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1707884/comments/16 On 2017-08-03T01:07:03+00:00 Michel Dänzer wrote: Please try Driver "modesetting" in xorg.conf and attach the corresponding Xorg log file. Does either of these problems happen in that case as well? Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1707884/comments/17 On 2017-08-03T08:27:25+00:00 Amr Ibrahim wrote: Adding Driver "modesetting" made the two problems disappear by making compiz (unity7) go into low graphics mode. Effects and animations are gone. Compiz was using 50% CPU. Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1707884/comments/18 On 2017-08-03T08:28:44+00:00 Amr Ibrahim wrote: Created attachment 133224 Xorg log after Driver "modesetting" Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1707884/comments/19 On 2017-08-03T08:42:28+00:00 Amr Ibrahim wrote: The whole desktop is much slower after Driver "modesetting". Playing small videos in Totem is slow. Playing big videos crashes the session and brings me back to the login screen. Compiz and Totem together use 100% CPU for switching, moving windows and playing videos. Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1707884/comments/20 On 2017-08-03T09:24:31+00:00 Michel Dänzer wrote: Ah, you also need to comment out Option "AccelMethod" for testing the modesetting driver. Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1707884/comments/21 On 2017-08-03T09:41:55+00:00 Amr Ibrahim wrote: Created attachment 133225 Xorg log after Driver "modesetting" and without Option "AccelMethod" Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1707884/comments/22 On 2017-08-03T09:43:02+00:00 Amr Ibrahim wrote: OK, the driver modesetting brings back the two problems.
[Touch-packages] [Bug 1755447] Re: issue 32185: SSLContext.wrap_socket sends SNI Extension when server_hostname is IP
** Changed in: python3.4 (Ubuntu Trusty) Status: New => Won't Fix ** Changed in: python2.7 (Ubuntu Trusty) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1755447 Title: issue 32185: SSLContext.wrap_socket sends SNI Extension when server_hostname is IP Status in Python: Fix Released Status in python2.7 package in Ubuntu: New Status in python3.6 package in Ubuntu: Fix Released Status in python3.7 package in Ubuntu: Fix Released Status in python2.7 source package in Trusty: Won't Fix Status in python3.4 source package in Trusty: Won't Fix Status in python2.7 source package in Xenial: New Status in python3.5 source package in Xenial: New Status in python2.7 source package in Artful: Won't Fix Status in python3.6 source package in Artful: Won't Fix Status in python3.7 source package in Artful: Won't Fix Status in python2.7 source package in Bionic: New Status in python3.6 source package in Bionic: Fix Released Status in python3.7 source package in Bionic: Fix Released Status in python2.7 package in Debian: New Status in python3.4 package in Debian: New Status in python3.5 package in Debian: New Bug description: the fix for https://bugs.python.org/issue32185 needs backports for the stable releases. To manage notifications about this bug go to: https://bugs.launchpad.net/python/+bug/1755447/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1556302] Re: Ubuntu patch to add HOME to env_keep makes custom commands vulnerable by default
Follow up for anyone coming here because of Ubuntu's unique (pre-19.10) behavior of not changing $HOME when calling sudo; if this is causing you problems, you should change your calling of sudo to include the -H param which will force sudo on Ubuntu to change HOME to the target user's homedir, instead of leaving it as the calling user's homedir. -- 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/1556302 Title: Ubuntu patch to add HOME to env_keep makes custom commands vulnerable by default Status in Release Notes for Ubuntu: New Status in sudo package in Ubuntu: Fix Released Status in sudo source package in Xenial: In Progress Status in sudo source package in Bionic: In Progress Status in sudo source package in Cosmic: In Progress Status in sudo source package in Disco: In Progress Status in sudo source package in Eoan: Fix Released Bug description: [impact] sudo does not set HOME to the target user's HOME [test case] ddstreet@thorin:~$ sudo printenv | grep HOME HOME=/home/ddstreet [regression potential] this is a significant behavior change. As mentioned in comment 11 (and later, and other bugs duped to this, and the mailing list discussion, etc) users of Ubuntu so far have been used to running sudo with their own HOME set, not root's HOME. Therefore, it's inappropriate to change this behavior for existing releases; this should be changed starting in Eoan, and only the sudo and sudoers man pages changed in previous releases to indicate the actual behavior of sudo in those releases. [other info] Shortly after upstream changed the behavior, the patch to keep HOME as the calling (instead of target) user was added in bug 760140. For quick reference to anyone coming to this bug, the pre-19.10 behavior (of sudo keeping the calling user's $HOME) can be disabled by running 'sudo visudo' and adding this line: Defaultsalways_set_home or, run sudo with the -H param. -- original description: -- I wanted to allow certain users to execute a python script as another user, so I created the following sudoers config: Defaults env_reset source_user ALL=(target_user) NOPASSWD: /home/target_user/bin/script.py This results in a highly insecure Python environment because the source user can set HOME and override any Python package by putting files in $HOME/.local/lib/python*/site-packages/. This should be a safe configuration because the default behaviour (as specified in the man page) is that env_reset will replace HOME with the target user's home directory. The "env_reset" option even has special behaviour for bash which has its own potential environment vulnerabilities. However there is an Ubuntu-specific patch in the package (keep_home_by_default.patch) that makes sudo preserve HOME by default, which negates the correct behaviour of "env_reset". It should not be necessary to explicitly specify the "always_set_home" option in order to negate this patch. The patch should be removed and the default /etc/sudoers should explicitly add HOME to "env_keep" for the "allow admins to run any command as root" entries, to get the desired behaviour without creating security issues for other sudoers commands. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1556302/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1845028] [NEW] package qml-module-qtwebkit:amd64 (not installed) failed to install/upgrade: no package named 'qml-module-qtwebkit:amd64' is installed, cannot configure
Public bug reported: This error appeared during the upgrade from 16.04 to 18.04 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: qml-module-qtwebkit:amd64 (not installed) ProcVersionSignature: Ubuntu 4.15.0-64.73~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-64-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Mon Sep 23 14:39:47 2019 ErrorMessage: no package named 'qml-module-qtwebkit:amd64' is installed, cannot configure InstallationDate: Installed on 2017-12-07 (654 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.2 apt 1.6.12 SourcePackage: qtwebkit-opensource-src Title: package qml-module-qtwebkit:amd64 (not installed) failed to install/upgrade: no package named 'qml-module-qtwebkit:amd64' is installed, cannot configure UpgradeStatus: Upgraded to bionic on 2019-09-23 (0 days ago) ** Affects: qtwebkit-opensource-src (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtwebkit-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1845028 Title: package qml-module-qtwebkit:amd64 (not installed) failed to install/upgrade: no package named 'qml-module-qtwebkit:amd64' is installed, cannot configure Status in qtwebkit-opensource-src package in Ubuntu: New Bug description: This error appeared during the upgrade from 16.04 to 18.04 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: qml-module-qtwebkit:amd64 (not installed) ProcVersionSignature: Ubuntu 4.15.0-64.73~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-64-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Mon Sep 23 14:39:47 2019 ErrorMessage: no package named 'qml-module-qtwebkit:amd64' is installed, cannot configure InstallationDate: Installed on 2017-12-07 (654 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.2 apt 1.6.12 SourcePackage: qtwebkit-opensource-src Title: package qml-module-qtwebkit:amd64 (not installed) failed to install/upgrade: no package named 'qml-module-qtwebkit:amd64' is installed, cannot configure UpgradeStatus: Upgraded to bionic on 2019-09-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtwebkit-opensource-src/+bug/1845028/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452115] Re: Python interpreter binary is not compiled as PIE
** Changed in: python3.6 (Ubuntu) Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1452115 Title: Python interpreter binary is not compiled as PIE Status in python2.7 package in Ubuntu: Fix Released Status in python3.4 package in Ubuntu: Fix Released Status in python3.6 package in Ubuntu: New Bug description: The python2.7 binary (installed at /usr/bin/python2.7; package version 2.7.6-8) is not compiled as a position independent executable (PIE). It appears that the python compilation process is somewhat arcane and the hardening wrapper probably doesn't do the trick for it. This is incredibly dangerous as it means that any vulnerability within a native module (e.g. ctypes-based), or within python itself will expose an incredibly large amount of known memory contents at known addresses (including a large number of dangerous instruction groupings). This enables ROP-based (https://en.wikipedia.org/wiki /Return-oriented_programming) to abuse the interpreter itself to bypass non-executable page protections. I have put together an example vulnerable C shared object (with a buffer overflow) accessed via python through the ctypes interface as an example. This uses a single ROP "gadget" on top of using the known PLT location for system(3) (https://en.wikipedia.org/wiki/Return-to-libc_attack) to call "id". The example code is accessible at: - https://gist.github.com/ChaosData/ae6076cb1c3cc7b0a367 I'm not exactly familiar enough with the python build process to say where exactly an -fPIE needs to be injected into a script/makefile, but I feel that given the perceived general preference for ctypes- based modules over python written ones, as the native code implementations tend to be more performant, this feels like a large security hole within the system. Given the nature of this "issue," I'm not 100% sure of where it is best reported, but from what I can tell, this conflicts with the Ubuntu hardening features and is definitely exploitable should a native module contain a sufficiently exploitable vulnerability that allows for control of the instruction register. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1452115/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 330833] Re: NetworkManager always overwrites default route when connecting to OpenVPN network
it's 2019 and the same bug still exists. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/330833 Title: NetworkManager always overwrites default route when connecting to OpenVPN network Status in NetworkManager-OpenVPN: Invalid Status in network-manager package in Ubuntu: Invalid Status in network-manager-openvpn package in Ubuntu: Fix Released Status in network-manager package in Debian: New Status in network-manager package in Fedora: Invalid Bug description: Binary package hint: network-manager My office VPN has IMAP, (forwarding) DNS services and not much else. It doesn't forward client traffic to the Internet. This means I can't use the VPN server as a default gateway. Every time I connect to the VPN using NetworkManager/OpenVPN, my routing table gets a default route to the VPN. I've tried everything to avoid this in both the Intrepid package and the version from the network manager PPA with no success. Even telling NetworkManager to ignore routes from the server doesn't work. As it is right now, I have to connect to the VPN, delete the default route, and re-add my wireless router as the default gateway before I can have both email and web access. See attached routing table details. ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 8.10 NonfreeKernelModules: nvidia Package: network-manager 0.7-0ubuntu1~nm1~intrepid1 ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: network-manager Uname: Linux 2.6.27-11-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager-openvpn/+bug/330833/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1844132] Re: FFe: Mesa 19.2.0
1) Are you confident that you'll get enough testing to find any meaningful regressions, and have enough time to fix them before release? 2) Is there an upstream point release planned by October, or does their slip mean we'll see .1 as an SRU a month post-release? I'm a tentative +1 on this anyway just for the Ice Lake and Navi support, which we'll also want for the next bionic point release, but better answers to the above would help me be sure. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1844132 Title: FFe: Mesa 19.2.0 Status in mesa package in Ubuntu: Confirmed Status in mesa source package in Eoan: Confirmed Bug description: It would be great to get 19.2.0 in eoan, though it's release cycle has slipped. It's working fine on a typical desktop use here on i915 (Kaby Lake). It would also migrate to llvm-9. It is currently at rc3, and final version is expected to arrive next week (week 39). New features: Full support for Intel Ice Lake Support for AMD Navi GL_ARB_post_depth_coverage on radeonsi (Navi) GL_ARB_seamless_cubemap_per_texture on etnaviv (if GPU supports SEAMLESS_CUBE_MAP) GL_EXT_shader_image_load_store on radeonsi (with LLVM >= 10) GL_EXT_shader_samples_identical on iris and radeonsi (if using NIR) GL_EXT_texture_shadow_lod on i965, iris EGL_EXT_platform_device VK_AMD_buffer_marker on radv VK_EXT_index_type_uint8 on radv VK_EXT_post_depth_coverage on radv VK_EXT_queue_family_foreign on radv VK_EXT_sample_locations on radv VK_EXT_shader_demote_to_helper_invocation on Intel. VK_KHR_depth_stencil_resolve on radv VK_KHR_imageless_framebuffer on radv VK_KHR_shader_atomic_int64 on radv VK_KHR_uniform_buffer_standard_layout on radv (note: iris is the new DRI driver for newer Intel, not enabled by default yet) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1844132/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1714178] Re: Triple 4K monitor display failed (modesetting driver limited to 8192x8192)
This bug was fixed in the package linux-oem-osp1 - 5.0.0-1022.24 --- linux-oem-osp1 (5.0.0-1022.24) bionic; urgency=medium [ Ubuntu: 5.0.0-29.31 ] * powerpc/tm: Fix restoring FP/VMX facility incorrectly on interrupts (CVE-2019-15031) / powerpc/tm: Fix FP/VMX unavailable exceptions inside a transaction (CVE-2019-15030) (LP: #1843533) // CVE-2019-15031 - powerpc/tm: Fix FP/VMX unavailable exceptions inside a transaction - powerpc/tm: Fix restoring FP/VMX facility incorrectly on interrupts * CVE-2019-14835 - vhost: fix dirty log buffer overflow * Packaging resync (LP: #1786013) - [Packaging] resync getabis -- Stefan Bader Thu, 12 Sep 2019 20:27:12 +0200 ** Changed in: linux-oem-osp1 (Ubuntu) Status: New => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-14835 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-15030 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-15031 ** Changed in: linux-oem-osp1 (Ubuntu) Status: New => 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 DRI: Fix Released Status in HWE Next: New Status in X.Org X server: Unknown Status in linux package in Ubuntu: Triaged Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Status in linux-oem-osp1 source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Released Status in xorg-server source package in Bionic: Invalid 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
[Touch-packages] [Bug 1714178] Re: Triple 4K monitor display failed (modesetting driver limited to 8192x8192)
This bug was fixed in the package linux-oem-osp1 - 5.0.0-1022.24 --- linux-oem-osp1 (5.0.0-1022.24) bionic; urgency=medium [ Ubuntu: 5.0.0-29.31 ] * powerpc/tm: Fix restoring FP/VMX facility incorrectly on interrupts (CVE-2019-15031) / powerpc/tm: Fix FP/VMX unavailable exceptions inside a transaction (CVE-2019-15030) (LP: #1843533) // CVE-2019-15031 - powerpc/tm: Fix FP/VMX unavailable exceptions inside a transaction - powerpc/tm: Fix restoring FP/VMX facility incorrectly on interrupts * CVE-2019-14835 - vhost: fix dirty log buffer overflow * Packaging resync (LP: #1786013) - [Packaging] resync getabis -- Stefan Bader Thu, 12 Sep 2019 20:27:12 +0200 -- 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 DRI: Fix Released Status in HWE Next: New Status in X.Org X server: Unknown Status in linux package in Ubuntu: Triaged Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Status in linux-oem-osp1 source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Released Status in xorg-server source package in Bionic: Invalid 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
[Touch-packages] [Bug 1844879] Re: Behaviour change in systemd 243 breaks libvirt autopkgtest
** Changed in: systemd Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1844879 Title: Behaviour change in systemd 243 breaks libvirt autopkgtest Status in systemd: New Status in libvirt package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Confirmed Bug description: With systemd 243 libvirt autopkgtest starts failing: http://autopkgtest.ubuntu.com/packages/libv/libvirt/eoan/amd64 https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/amd64/libv/libvirt/20190921_104518_69667@/log.gz ... + virt-xml-validate debian/tests/smoke-lxc.xml debian/tests/smoke-lxc.xml validates + virsh define debian/tests/smoke-lxc.xml Domain sl defined from debian/tests/smoke-lxc.xml + rm -f /var/log/libvirt/lxc/sl.log + virsh start sl Domain sl started + grep -qs starting up /var/log/libvirt/lxc/sl.log + check_domain + grep/bin/ls Domain sl has been undefined -qs sl[[:space:]]\+running + virsh list + virsh lxc-enter-namespace --noseclabel sl /bin/ls /bin/ls + systemctl restart libvirtd + check_domain + grep -qs sl[[:space:]]\+running + virsh list + cleanup + [ -z ] + virsh destroy sl error: Failed to destroy domain sl error: Requested operation is not valid: domain is not running + true + virsh undefine sl + CLEANED_UP=1 autopkgtest [10:41:05]: test smoke-lxc: ---] autopkgtest [10:41:07]: test smoke-lxc: - - - - - - - - - - results - - - - - - - - - - smoke-lxcFAIL non-zero exit status 1 ... The behaviour change is still present in systemd master (v243-112-g984b96aa7a) I can revert the change in systemd, but it also fixes an issue reported at upstream. I will take another look later, but wanted to document my findings. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1844879/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1844853] Re: IBus no longer works in Qt applications after upgrade
** Bug watch added: Debian Bug tracker #941018 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941018 ** Also affects: ibus (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941018 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1844853 Title: IBus no longer works in Qt applications after upgrade Status in ibus: New Status in ibus package in Ubuntu: Fix Released Status in ibus package in Debian: Unknown Bug description: Kubuntu Release 18.04.3 LTS Expected behavior: ibus continues working as before after applying security update 1.5.17-ubuntu5.1 from version 1.5.17-ubuntu5. Observed behavior: ibus is not usable anymore in Qt applications. After updating ibus and the related packages ibus-gtk, ibus-gtk3, libibus-1.0-5 and gir1.2-ibus-1.0 all from version 1.5.17-ubuntu5 to 1.5.17-ubuntu5.1, I can no longer use ibus in Qt applications. Using shift-space no longer changes the selected input method and even when i switch to the mozc input method in a gtk application, i can not use it in any Qt applications. When starting qtconfig in a terminal, I also get the following message: Bus::open: Connect ibus failed! IBusInputContext::createInputContext: no connection to ibus-daemon This bug was not present in version 1.5.17-3ubuntu5 and I also confirmed that downgrading the packages to version 1.5.17-3ubuntu4 restores ibus functionality in Qt applications. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu5.1 ProcVersionSignature: Ubuntu 5.0.0-30.32~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: KDE Date: Sat Sep 21 07:58:56 2019 InstallationDate: Installed on 2019-06-28 (84 days ago) InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1844853/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1844879] Re: Behaviour change in systemd 243 breaks libvirt autopkgtest
Pinged upstream libvirt to be aware of the case as well. => https://www.redhat.com/archives/libvir-list/2019-September/msg00974.html -- 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/1844879 Title: Behaviour change in systemd 243 breaks libvirt autopkgtest Status in systemd: New Status in libvirt package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Confirmed Bug description: With systemd 243 libvirt autopkgtest starts failing: http://autopkgtest.ubuntu.com/packages/libv/libvirt/eoan/amd64 https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/amd64/libv/libvirt/20190921_104518_69667@/log.gz ... + virt-xml-validate debian/tests/smoke-lxc.xml debian/tests/smoke-lxc.xml validates + virsh define debian/tests/smoke-lxc.xml Domain sl defined from debian/tests/smoke-lxc.xml + rm -f /var/log/libvirt/lxc/sl.log + virsh start sl Domain sl started + grep -qs starting up /var/log/libvirt/lxc/sl.log + check_domain + grep/bin/ls Domain sl has been undefined -qs sl[[:space:]]\+running + virsh list + virsh lxc-enter-namespace --noseclabel sl /bin/ls /bin/ls + systemctl restart libvirtd + check_domain + grep -qs sl[[:space:]]\+running + virsh list + cleanup + [ -z ] + virsh destroy sl error: Failed to destroy domain sl error: Requested operation is not valid: domain is not running + true + virsh undefine sl + CLEANED_UP=1 autopkgtest [10:41:05]: test smoke-lxc: ---] autopkgtest [10:41:07]: test smoke-lxc: - - - - - - - - - - results - - - - - - - - - - smoke-lxcFAIL non-zero exit status 1 ... The behaviour change is still present in systemd master (v243-112-g984b96aa7a) I can revert the change in systemd, but it also fixes an issue reported at upstream. I will take another look later, but wanted to document my findings. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1844879/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1844853] Re: IBus no longer works in Qt applications after upgrade
This bug was fixed in the package ibus - 1.5.11-1ubuntu2.3 --- ibus (1.5.11-1ubuntu2.3) xenial-security; urgency=medium * SECURITY UPDATE: ibus regression in Qt applications (LP: #1844853) - debian/patches/CVE-2019-14822.patch: disabled pending further investigation. -- Marc Deslauriers Mon, 23 Sep 2019 13:31:22 +0200 ** Changed in: ibus (Ubuntu) Status: Confirmed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-14822 ** Changed in: ibus (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1844853 Title: IBus no longer works in Qt applications after upgrade Status in ibus: New Status in ibus package in Ubuntu: Fix Released Bug description: Kubuntu Release 18.04.3 LTS Expected behavior: ibus continues working as before after applying security update 1.5.17-ubuntu5.1 from version 1.5.17-ubuntu5. Observed behavior: ibus is not usable anymore in Qt applications. After updating ibus and the related packages ibus-gtk, ibus-gtk3, libibus-1.0-5 and gir1.2-ibus-1.0 all from version 1.5.17-ubuntu5 to 1.5.17-ubuntu5.1, I can no longer use ibus in Qt applications. Using shift-space no longer changes the selected input method and even when i switch to the mozc input method in a gtk application, i can not use it in any Qt applications. When starting qtconfig in a terminal, I also get the following message: Bus::open: Connect ibus failed! IBusInputContext::createInputContext: no connection to ibus-daemon This bug was not present in version 1.5.17-3ubuntu5 and I also confirmed that downgrading the packages to version 1.5.17-3ubuntu4 restores ibus functionality in Qt applications. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu5.1 ProcVersionSignature: Ubuntu 5.0.0-30.32~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: KDE Date: Sat Sep 21 07:58:56 2019 InstallationDate: Installed on 2019-06-28 (84 days ago) InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1844853/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1844853] Re: IBus no longer works in Qt applications after upgrade
This bug was fixed in the package ibus - 1.5.19-1ubuntu2.2 --- ibus (1.5.19-1ubuntu2.2) disco-security; urgency=medium * SECURITY UPDATE: ibus regression in Qt applications (LP: #1844853) - debian/patches/CVE-2019-14822.patch: disabled pending further investigation. -- Marc Deslauriers Mon, 23 Sep 2019 13:29:28 +0200 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1844853 Title: IBus no longer works in Qt applications after upgrade Status in ibus: New Status in ibus package in Ubuntu: Fix Released Bug description: Kubuntu Release 18.04.3 LTS Expected behavior: ibus continues working as before after applying security update 1.5.17-ubuntu5.1 from version 1.5.17-ubuntu5. Observed behavior: ibus is not usable anymore in Qt applications. After updating ibus and the related packages ibus-gtk, ibus-gtk3, libibus-1.0-5 and gir1.2-ibus-1.0 all from version 1.5.17-ubuntu5 to 1.5.17-ubuntu5.1, I can no longer use ibus in Qt applications. Using shift-space no longer changes the selected input method and even when i switch to the mozc input method in a gtk application, i can not use it in any Qt applications. When starting qtconfig in a terminal, I also get the following message: Bus::open: Connect ibus failed! IBusInputContext::createInputContext: no connection to ibus-daemon This bug was not present in version 1.5.17-3ubuntu5 and I also confirmed that downgrading the packages to version 1.5.17-3ubuntu4 restores ibus functionality in Qt applications. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu5.1 ProcVersionSignature: Ubuntu 5.0.0-30.32~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: KDE Date: Sat Sep 21 07:58:56 2019 InstallationDate: Installed on 2019-06-28 (84 days ago) InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1844853/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1844853] Re: IBus no longer works in Qt applications after upgrade
This bug was fixed in the package ibus - 1.5.17-3ubuntu5.2 --- ibus (1.5.17-3ubuntu5.2) bionic-security; urgency=medium * SECURITY UPDATE: ibus regression in Qt applications (LP: #1844853) - debian/patches/CVE-2019-14822.patch: disabled pending further investigation. -- Marc Deslauriers Mon, 23 Sep 2019 13:30:51 +0200 ** Changed in: ibus (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1844853 Title: IBus no longer works in Qt applications after upgrade Status in ibus: New Status in ibus package in Ubuntu: Fix Released Bug description: Kubuntu Release 18.04.3 LTS Expected behavior: ibus continues working as before after applying security update 1.5.17-ubuntu5.1 from version 1.5.17-ubuntu5. Observed behavior: ibus is not usable anymore in Qt applications. After updating ibus and the related packages ibus-gtk, ibus-gtk3, libibus-1.0-5 and gir1.2-ibus-1.0 all from version 1.5.17-ubuntu5 to 1.5.17-ubuntu5.1, I can no longer use ibus in Qt applications. Using shift-space no longer changes the selected input method and even when i switch to the mozc input method in a gtk application, i can not use it in any Qt applications. When starting qtconfig in a terminal, I also get the following message: Bus::open: Connect ibus failed! IBusInputContext::createInputContext: no connection to ibus-daemon This bug was not present in version 1.5.17-3ubuntu5 and I also confirmed that downgrading the packages to version 1.5.17-3ubuntu4 restores ibus functionality in Qt applications. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu5.1 ProcVersionSignature: Ubuntu 5.0.0-30.32~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: KDE Date: Sat Sep 21 07:58:56 2019 InstallationDate: Installed on 2019-06-28 (84 days ago) InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1844853/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1844879] Re: Behaviour change in systemd 243 breaks libvirt autopkgtest
@paelzer: OK, I will go with the revert. It still sounds that libvirt may need a change to keep the lxc guest even with the systemd change in, so if you don't mind I keep this bug open to track this. If it turns out that libvirt does everything right then I'll be happy to forward the issue to systemd upstream. -- 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/1844879 Title: Behaviour change in systemd 243 breaks libvirt autopkgtest Status in systemd: Unknown Status in libvirt package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Confirmed Bug description: With systemd 243 libvirt autopkgtest starts failing: http://autopkgtest.ubuntu.com/packages/libv/libvirt/eoan/amd64 https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/amd64/libv/libvirt/20190921_104518_69667@/log.gz ... + virt-xml-validate debian/tests/smoke-lxc.xml debian/tests/smoke-lxc.xml validates + virsh define debian/tests/smoke-lxc.xml Domain sl defined from debian/tests/smoke-lxc.xml + rm -f /var/log/libvirt/lxc/sl.log + virsh start sl Domain sl started + grep -qs starting up /var/log/libvirt/lxc/sl.log + check_domain + grep/bin/ls Domain sl has been undefined -qs sl[[:space:]]\+running + virsh list + virsh lxc-enter-namespace --noseclabel sl /bin/ls /bin/ls + systemctl restart libvirtd + check_domain + grep -qs sl[[:space:]]\+running + virsh list + cleanup + [ -z ] + virsh destroy sl error: Failed to destroy domain sl error: Requested operation is not valid: domain is not running + true + virsh undefine sl + CLEANED_UP=1 autopkgtest [10:41:05]: test smoke-lxc: ---] autopkgtest [10:41:07]: test smoke-lxc: - - - - - - - - - - results - - - - - - - - - - smoke-lxcFAIL non-zero exit status 1 ... The behaviour change is still present in systemd master (v243-112-g984b96aa7a) I can revert the change in systemd, but it also fixes an issue reported at upstream. I will take another look later, but wanted to document my findings. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1844879/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1844879] Re: Behaviour change in systemd 243 breaks libvirt autopkgtest
FYI reported upstream (Systemd) as https://github.com/systemd/systemd/issues/13629 ** Bug watch added: github.com/systemd/systemd/issues #13629 https://github.com/systemd/systemd/issues/13629 ** Also affects: systemd via https://github.com/systemd/systemd/issues/13629 Importance: Unknown Status: Unknown -- 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/1844879 Title: Behaviour change in systemd 243 breaks libvirt autopkgtest Status in systemd: Unknown Status in libvirt package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Confirmed Bug description: With systemd 243 libvirt autopkgtest starts failing: http://autopkgtest.ubuntu.com/packages/libv/libvirt/eoan/amd64 https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/amd64/libv/libvirt/20190921_104518_69667@/log.gz ... + virt-xml-validate debian/tests/smoke-lxc.xml debian/tests/smoke-lxc.xml validates + virsh define debian/tests/smoke-lxc.xml Domain sl defined from debian/tests/smoke-lxc.xml + rm -f /var/log/libvirt/lxc/sl.log + virsh start sl Domain sl started + grep -qs starting up /var/log/libvirt/lxc/sl.log + check_domain + grep/bin/ls Domain sl has been undefined -qs sl[[:space:]]\+running + virsh list + virsh lxc-enter-namespace --noseclabel sl /bin/ls /bin/ls + systemctl restart libvirtd + check_domain + grep -qs sl[[:space:]]\+running + virsh list + cleanup + [ -z ] + virsh destroy sl error: Failed to destroy domain sl error: Requested operation is not valid: domain is not running + true + virsh undefine sl + CLEANED_UP=1 autopkgtest [10:41:05]: test smoke-lxc: ---] autopkgtest [10:41:07]: test smoke-lxc: - - - - - - - - - - results - - - - - - - - - - smoke-lxcFAIL non-zero exit status 1 ... The behaviour change is still present in systemd master (v243-112-g984b96aa7a) I can revert the change in systemd, but it also fixes an issue reported at upstream. I will take another look later, but wanted to document my findings. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1844879/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1531184] Re: [SRU] dnsmasq doesn't start on boot because its interface isn't up yet
Thanks Christian. This bug was already on my list. More details here: https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/ It is not obvious to me that adding After/Wants=network-online.target to the packaging for _all_ users, or anything similar, is the correct fix here. Will this delay boot for laptop users who are offline, for example? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1531184 Title: [SRU] dnsmasq doesn't start on boot because its interface isn't up yet Status in One Hundred Papercuts: Confirmed Status in dnsmasq package in Ubuntu: Confirmed Status in dnsmasq package in Debian: New Bug description: [Impact] dnsmasq will fail to respond on network devices that weren't up when its service started, thus not binding as expected. [Test Case] TBD [Regression Potential] The fix is just configuring the order of service startup, so is unlikely to create any regressions. Things to watch would be service related misbehaviors and general availability of the dnsmasq functionality. [Fix] Straightforward packaging fix to the service to make it delay startup until after the network is online. https://bugs.debian.org/cgi- bin/bugreport.cgi?att=1;bug=774970;filename=774970-network- online.debdiff;msg=22 [Discussion] [Original Report] My dnsmasq instance uses "interface=br-vz0" and the interface br-vz0 is managed manually in /etc/network/interfaces. During boot, dnsmasq is started before br-vz0 is created and this causes dnsmasq to exit: Jan 5 08:56:16 simon-laptop dnsmasq[1008]: dnsmasq: unknown interface br-vz0 Jan 5 08:56:16 simon-laptop dnsmasq[1008]: unknown interface br-vz0 Jan 5 08:56:16 simon-laptop dnsmasq[1008]: FAILED to start up Jan 5 08:56:17 simon-laptop NetworkManager[937]: NetworkManager (version 1.0.4) is starting... ... Jan 5 08:56:18 simon-laptop NetworkManager[937]: interface-parser: parsing file /etc/network/interfaces ... Jan 5 08:56:18 simon-laptop NetworkManager[937]: found bridge ports none for br-vz0 Jan 5 08:56:18 simon-laptop NetworkManager[937]: adding bridge port none to eni_ifaces Jan 5 08:56:18 simon-laptop NetworkManager[937]: management mode: unmanaged ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: dnsmasq 2.75-1 ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3 Uname: Linux 4.3.0-5-generic x86_64 ApportVersion: 2.19.3-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jan 5 09:53:30 2016 PackageArchitecture: all SourcePackage: dnsmasq UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1531184/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1531184] Re: [SRU] dnsmasq doesn't start on boot because its interface isn't up yet
@Robie - I subscribed you as I wondered if this is another one for your list of bugs related to "binding to IPs available late". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1531184 Title: [SRU] dnsmasq doesn't start on boot because its interface isn't up yet Status in One Hundred Papercuts: Confirmed Status in dnsmasq package in Ubuntu: Confirmed Status in dnsmasq package in Debian: New Bug description: [Impact] dnsmasq will fail to respond on network devices that weren't up when its service started, thus not binding as expected. [Test Case] TBD [Regression Potential] The fix is just configuring the order of service startup, so is unlikely to create any regressions. Things to watch would be service related misbehaviors and general availability of the dnsmasq functionality. [Fix] Straightforward packaging fix to the service to make it delay startup until after the network is online. https://bugs.debian.org/cgi- bin/bugreport.cgi?att=1;bug=774970;filename=774970-network- online.debdiff;msg=22 [Discussion] [Original Report] My dnsmasq instance uses "interface=br-vz0" and the interface br-vz0 is managed manually in /etc/network/interfaces. During boot, dnsmasq is started before br-vz0 is created and this causes dnsmasq to exit: Jan 5 08:56:16 simon-laptop dnsmasq[1008]: dnsmasq: unknown interface br-vz0 Jan 5 08:56:16 simon-laptop dnsmasq[1008]: unknown interface br-vz0 Jan 5 08:56:16 simon-laptop dnsmasq[1008]: FAILED to start up Jan 5 08:56:17 simon-laptop NetworkManager[937]: NetworkManager (version 1.0.4) is starting... ... Jan 5 08:56:18 simon-laptop NetworkManager[937]: interface-parser: parsing file /etc/network/interfaces ... Jan 5 08:56:18 simon-laptop NetworkManager[937]: found bridge ports none for br-vz0 Jan 5 08:56:18 simon-laptop NetworkManager[937]: adding bridge port none to eni_ifaces Jan 5 08:56:18 simon-laptop NetworkManager[937]: management mode: unmanaged ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: dnsmasq 2.75-1 ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3 Uname: Linux 4.3.0-5-generic x86_64 ApportVersion: 2.19.3-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jan 5 09:53:30 2016 PackageArchitecture: all SourcePackage: dnsmasq UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1531184/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843755] Re: [FFe] Please accept systemd 243 to Eoan
Unfortunately Bileto reported a few tests as as always failing instead of new regressions. I have checked many, but not all of them before the upload and this is why a few regressions kept systemd in -proposed during the weekend. https://people.canonical.com/~ubuntu-archive/proposed-migration/eoan/update_excuses.html#systemd The original test result summary for the Bileto ticket is gone, but the test logs are still available: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-ci-train-ppa-service-3801/?format=plain The 243 package in proposed does have only a few regressions and should not break other autopkgtests thus I try to fix the newly observed regressions quickly and if that does not work then ask for the removal of the package from the proposed pocket. -- 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/1843755 Title: [FFe] Please accept systemd 243 to Eoan Status in systemd package in Ubuntu: Confirmed Bug description: Eoan currently has 241-7ubuntu1, Debian stable has 241 and Debian testing moved to 242 last week. While version 241 is the safer choice for Eoan (from v241 and v242) since it is widely tested updating to v242 will allow us to carry fewer patches in Eoan and makes moving to the next release easier. The proposed package is tested in Bileto and all tests are passing (except for a few unrelated failures): https://bileto.ubuntu.com/#/ticket/3797 The final version will be 242-6ubuntu1 and I'm tidying up the changelog, too. I plan merging 242-7, too, going forward but this will not need an FFe. CHANGES WITH 242: * In .link files, MACAddressPolicy=persistent (the default) is changed to cover more devices. For devices like bridges, tun, tap, bond, and similar interfaces that do not have other identifying information, the interface name is used as the basis for persistent seed for MAC and IPv4LL addresses. The way that devices that were handled previously is not changed, and this change is about covering more devices then previously by the "persistent" policy. MACAddressPolicy=random may be used to force randomized MACs and IPv4LL addresses for a device if desired. Hint: the log output from udev (at debug level) was enhanced to clarify what policy is followed and which attributes are used. `SYSTEMD_LOG_LEVEL=debug udevadm test-builtin net_setup_link /sys/class/net/` may be used to view this. Hint: if a bridge interface is created without any slaves, and gains a slave later, then now the bridge does not inherit slave's MAC. To inherit slave's MAC, for example, create the following file: ``` # /etc/systemd/network/98-bridge-inherit-mac.link [Match] Type=bridge [Link] MACAddressPolicy=none ``` * The .device units generated by systemd-fstab-generator and other generators do not automatically pull in the corresponding .mount unit as a Wants= dependency. This means that simply plugging in the device will not cause the mount unit to be started automatically. But please note that the mount unit may be started for other reasons, in particular if it is part of local-fs.target, and any unit which (transitively) depends on local-fs.target is started. * networkctl list/status/lldp now accept globbing wildcards for network interface names to match against all existing interfaces. * The $PIDFILE environment variable is set to point the absolute path configured with PIDFile= for processes of that service. * The fallback DNS server list was augmented with Cloudflare public DNS servers. Use `-Ddns-servers=` to set a different fallback. * A new special target usb-gadget.target will be started automatically when a USB Device Controller is detected (which means that the system is a USB peripheral). * A new unit setting CPUQuotaPeriodSec= assigns the time period relatively to which the CPU time quota specified by CPUQuota= is measured. * A new unit setting ProtectHostname= may be used to prevent services from modifying hostname information (even if they otherwise would have privileges to do so). * A new unit setting NetworkNamespacePath= may be used to specify a namespace for service or socket units through a path referring to a Linux network namespace pseudo-file. * The PrivateNetwork= setting and JoinsNamespaceOf=
[Touch-packages] [Bug 1845004] [NEW] Unable to set static route on eno1
Public bug reported: Install recent version of 19.10 daily build. All is well but can't set a static route for my wired ethernet. Going to Settings-Network-Wired tried to fill in IP Address/NetMask/Route and although all appears to be correct the Apply button is never activated to set the static environment. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.20.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 23 08:43:48 2019 InstallationDate: Installed on 2019-09-20 (2 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190917) IpRoute: default via 192.168.1.1 dev wlp5s0 proto static metric 600 169.254.0.0/16 dev wlp5s0 scope link metric 1000 192.168.1.0/24 dev wlp5s0 proto kernel scope link src 192.168.1.201 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.2 connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1845004 Title: Unable to set static route on eno1 Status in network-manager package in Ubuntu: New Bug description: Install recent version of 19.10 daily build. All is well but can't set a static route for my wired ethernet. Going to Settings-Network- Wired tried to fill in IP Address/NetMask/Route and although all appears to be correct the Apply button is never activated to set the static environment. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.20.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 23 08:43:48 2019 InstallationDate: Installed on 2019-09-20 (2 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190917) IpRoute: default via 192.168.1.1 dev wlp5s0 proto static metric 600 169.254.0.0/16 dev wlp5s0 scope link metric 1000 192.168.1.0/24 dev wlp5s0 proto kernel scope link src 192.168.1.201 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.2 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1845004/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1844879] Re: Behaviour change in systemd 243 breaks libvirt autopkgtest
Not sure yet what we could do on the libvirt side. For the time being reverting it on systems (as suggested by rbalint) might be the better fix. ** Changed in: systemd (Ubuntu) Status: New => Confirmed ** Changed in: libvirt (Ubuntu) Status: New => Incomplete ** Changed in: systemd (Ubuntu) Importance: Undecided => High ** Changed in: libvirt (Ubuntu) Importance: Undecided => Medium -- 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/1844879 Title: Behaviour change in systemd 243 breaks libvirt autopkgtest Status in libvirt package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Confirmed Bug description: With systemd 243 libvirt autopkgtest starts failing: http://autopkgtest.ubuntu.com/packages/libv/libvirt/eoan/amd64 https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/amd64/libv/libvirt/20190921_104518_69667@/log.gz ... + virt-xml-validate debian/tests/smoke-lxc.xml debian/tests/smoke-lxc.xml validates + virsh define debian/tests/smoke-lxc.xml Domain sl defined from debian/tests/smoke-lxc.xml + rm -f /var/log/libvirt/lxc/sl.log + virsh start sl Domain sl started + grep -qs starting up /var/log/libvirt/lxc/sl.log + check_domain + grep/bin/ls Domain sl has been undefined -qs sl[[:space:]]\+running + virsh list + virsh lxc-enter-namespace --noseclabel sl /bin/ls /bin/ls + systemctl restart libvirtd + check_domain + grep -qs sl[[:space:]]\+running + virsh list + cleanup + [ -z ] + virsh destroy sl error: Failed to destroy domain sl error: Requested operation is not valid: domain is not running + true + virsh undefine sl + CLEANED_UP=1 autopkgtest [10:41:05]: test smoke-lxc: ---] autopkgtest [10:41:07]: test smoke-lxc: - - - - - - - - - - results - - - - - - - - - - smoke-lxcFAIL non-zero exit status 1 ... The behaviour change is still present in systemd master (v243-112-g984b96aa7a) I can revert the change in systemd, but it also fixes an issue reported at upstream. I will take another look later, but wanted to document my findings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1844879/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1844158] Re: FTBFS using vala-0.46.1
The attachment "Fix for FTB" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libunity in Ubuntu. https://bugs.launchpad.net/bugs/1844158 Title: FTBFS using vala-0.46.1 Status in libunity package in Ubuntu: Confirmed Status in libunity package in Fedora: Confirmed Bug description: Trying to build on/for fedora 31+ fails with the following errors: make[2]: Entering directory '/builddir/build/BUILD/libunity-7.1.4/src' /usr/bin/valac -C -H unity.h -d . --gir=Unity-7.0.gir --library unity --internal-vapi=unity-internal.vapi --internal-header=unity-internal.h --target-glib=2.32 --thread --use-header --vapidir ../vapi --vapidir ../protocol --vapidir . --pkg unity-protocol --pkg config --pkg unity-trace --pkg glib-2.0 --pkg gmodule-2.0 --pkg gobject-2.0 --pkg gio-2.0 --pkg gio-unix-2.0 --pkg dee-1.0 --pkg Dbusmenu-0.4 unity-appinfo-manager.vala unity-icon.vala unity-inspector.vala unity-io.vala unity-launcher.vala unity-category.vala unity-filters.vala unity-preferences-manager.vala unity-merge-strategy.vala unity-models.vala unity-search.vala unity-synchronizer.vala unity-previews.vala unity-result-activation.vala unity-scope-interface.vala unity-scope-dbus-connector.vala unity-scope-dbus-impl.vala unity-scope-channel.vala unity-deprecated-scope.vala unity-deprecated-scope-impl.vala unity-aggregator-scope.vala unity-aggregator-scope-private.vala unity-master-scope.vala unity-simple-scope.vala unity-scope-loader.vala unity-scope-tracker.vala unity-sound-menu.vala unity-sound-menu-mpris.vala unity-utils.vala Command-line option `--thread` is deprecated and will be ignored Compilation failed: 2 error(s), 0 warning(s) BUILDSTDERR: unity-deprecated-scope.vala:64.3-64.28: error: Creation method of abstract class cannot be public. BUILDSTDERR: public DeprecatedScopeBase (string dbus_path_, string id_) BUILDSTDERR: ^^ BUILDSTDERR: unity-aggregator-scope.vala:54.3-54.24: error: Creation method of abstract class cannot be public. BUILDSTDERR: public AggregatorScope (string dbus_path_, string id_, MergeMode merge_mode = AggregatorScope.MergeMode.OWNER_SCOPE, bool proxy_filter_hints = false) BUILDSTDERR: ^^ BUILDSTDERR: make[2]: *** [Makefile:1389: libunity_la_vala.stamp] Error 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1844158/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1844119] Re: readelf crash on 32bit, leading to abi-monitor testsuite regression
** Changed in: binutils Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1844119 Title: readelf crash on 32bit, leading to abi-monitor testsuite regression Status in binutils: Fix Released Status in binutils package in Ubuntu: Confirmed Status in glibc package in Ubuntu: Invalid Bug description: readelf --debug-dump=info libjsoncpp.so.1.8.1 to reproduce dpkg -l |grep binut ii binutils2.32.51.20190905-0ubuntu1 i386 GNU assembler, linker and binary utilities ii binutils-common:i3862.32.51.20190905-0ubuntu1 i386 Common files for the GNU assembler, linker and binary utilities ii binutils-i686-linux-gnu 2.32.51.20190905-0ubuntu1 i386 GNU binary utilities, for i686-linux-gnu target ii libbinutils:i3862.32.51.20190905-0ubuntu1 i386 GNU binary utilities (private shared library) To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1844119/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1844119]
Fixed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1844119 Title: readelf crash on 32bit, leading to abi-monitor testsuite regression Status in binutils: Fix Released Status in binutils package in Ubuntu: Confirmed Status in glibc package in Ubuntu: Invalid Bug description: readelf --debug-dump=info libjsoncpp.so.1.8.1 to reproduce dpkg -l |grep binut ii binutils2.32.51.20190905-0ubuntu1 i386 GNU assembler, linker and binary utilities ii binutils-common:i3862.32.51.20190905-0ubuntu1 i386 Common files for the GNU assembler, linker and binary utilities ii binutils-i686-linux-gnu 2.32.51.20190905-0ubuntu1 i386 GNU binary utilities, for i686-linux-gnu target ii libbinutils:i3862.32.51.20190905-0ubuntu1 i386 GNU binary utilities (private shared library) To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1844119/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1844119]
The master branch has been updated by Alan Modra : https://sourceware.org/git/gitweb.cgi?p=binutils- gdb.git;h=b3fe587ed2c78d46132bd33e14f42449d410354b commit b3fe587ed2c78d46132bd33e14f42449d410354b Author: Alan Modra Date: Mon Sep 23 08:53:07 2019 +0930 PR25018, readelf crash on 32bits Pointer comparisons after adding an offset just don't work to catch overflow when the offset is a larger type than the pointer. PR 25018 * dwarf.c (get_type_signedness): Delete ineffective pointer comparison check. Properly range check uvalue offset on recursive call. (read_and_display_attr_value): Range check uvalue offset before calling get_type_signedness. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1844119 Title: readelf crash on 32bit, leading to abi-monitor testsuite regression Status in binutils: Fix Released Status in binutils package in Ubuntu: Confirmed Status in glibc package in Ubuntu: Invalid Bug description: readelf --debug-dump=info libjsoncpp.so.1.8.1 to reproduce dpkg -l |grep binut ii binutils2.32.51.20190905-0ubuntu1 i386 GNU assembler, linker and binary utilities ii binutils-common:i3862.32.51.20190905-0ubuntu1 i386 Common files for the GNU assembler, linker and binary utilities ii binutils-i686-linux-gnu 2.32.51.20190905-0ubuntu1 i386 GNU binary utilities, for i686-linux-gnu target ii libbinutils:i3862.32.51.20190905-0ubuntu1 i386 GNU binary utilities (private shared library) To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1844119/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1844158] Re: FTBFS using vala-0.46.1
Fix for FTB ** Patch added: "Fix for FTB" https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1844158/+attachment/5290648/+files/0001-Fix-FTB-with-recent-vala-requiring-non-public-abstra.patch ** Changed in: libunity (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libunity in Ubuntu. https://bugs.launchpad.net/bugs/1844158 Title: FTBFS using vala-0.46.1 Status in libunity package in Ubuntu: Confirmed Status in libunity package in Fedora: Confirmed Bug description: Trying to build on/for fedora 31+ fails with the following errors: make[2]: Entering directory '/builddir/build/BUILD/libunity-7.1.4/src' /usr/bin/valac -C -H unity.h -d . --gir=Unity-7.0.gir --library unity --internal-vapi=unity-internal.vapi --internal-header=unity-internal.h --target-glib=2.32 --thread --use-header --vapidir ../vapi --vapidir ../protocol --vapidir . --pkg unity-protocol --pkg config --pkg unity-trace --pkg glib-2.0 --pkg gmodule-2.0 --pkg gobject-2.0 --pkg gio-2.0 --pkg gio-unix-2.0 --pkg dee-1.0 --pkg Dbusmenu-0.4 unity-appinfo-manager.vala unity-icon.vala unity-inspector.vala unity-io.vala unity-launcher.vala unity-category.vala unity-filters.vala unity-preferences-manager.vala unity-merge-strategy.vala unity-models.vala unity-search.vala unity-synchronizer.vala unity-previews.vala unity-result-activation.vala unity-scope-interface.vala unity-scope-dbus-connector.vala unity-scope-dbus-impl.vala unity-scope-channel.vala unity-deprecated-scope.vala unity-deprecated-scope-impl.vala unity-aggregator-scope.vala unity-aggregator-scope-private.vala unity-master-scope.vala unity-simple-scope.vala unity-scope-loader.vala unity-scope-tracker.vala unity-sound-menu.vala unity-sound-menu-mpris.vala unity-utils.vala Command-line option `--thread` is deprecated and will be ignored Compilation failed: 2 error(s), 0 warning(s) BUILDSTDERR: unity-deprecated-scope.vala:64.3-64.28: error: Creation method of abstract class cannot be public. BUILDSTDERR: public DeprecatedScopeBase (string dbus_path_, string id_) BUILDSTDERR: ^^ BUILDSTDERR: unity-aggregator-scope.vala:54.3-54.24: error: Creation method of abstract class cannot be public. BUILDSTDERR: public AggregatorScope (string dbus_path_, string id_, MergeMode merge_mode = AggregatorScope.MergeMode.OWNER_SCOPE, bool proxy_filter_hints = false) BUILDSTDERR: ^^ BUILDSTDERR: make[2]: *** [Makefile:1389: libunity_la_vala.stamp] Error 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1844158/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1844879] Re: Behaviour change in systemd 243 breaks libvirt autopkgtest
Hmm, there isn't an obvious cgroup/lxd patch in upstream libvirt master branch atm that would suggest itself as fix to test to apply to libvirt. -- 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/1844879 Title: Behaviour change in systemd 243 breaks libvirt autopkgtest Status in libvirt package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: With systemd 243 libvirt autopkgtest starts failing: http://autopkgtest.ubuntu.com/packages/libv/libvirt/eoan/amd64 https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/amd64/libv/libvirt/20190921_104518_69667@/log.gz ... + virt-xml-validate debian/tests/smoke-lxc.xml debian/tests/smoke-lxc.xml validates + virsh define debian/tests/smoke-lxc.xml Domain sl defined from debian/tests/smoke-lxc.xml + rm -f /var/log/libvirt/lxc/sl.log + virsh start sl Domain sl started + grep -qs starting up /var/log/libvirt/lxc/sl.log + check_domain + grep/bin/ls Domain sl has been undefined -qs sl[[:space:]]\+running + virsh list + virsh lxc-enter-namespace --noseclabel sl /bin/ls /bin/ls + systemctl restart libvirtd + check_domain + grep -qs sl[[:space:]]\+running + virsh list + cleanup + [ -z ] + virsh destroy sl error: Failed to destroy domain sl error: Requested operation is not valid: domain is not running + true + virsh undefine sl + CLEANED_UP=1 autopkgtest [10:41:05]: test smoke-lxc: ---] autopkgtest [10:41:07]: test smoke-lxc: - - - - - - - - - - results - - - - - - - - - - smoke-lxcFAIL non-zero exit status 1 ... The behaviour change is still present in systemd master (v243-112-g984b96aa7a) I can revert the change in systemd, but it also fixes an issue reported at upstream. I will take another look later, but wanted to document my findings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1844879/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1844879] Re: Behaviour change in systemd 243 breaks libvirt autopkgtest
To summarize (out of the noisy test log). What happens with this patch applied is that libvirt looses its LXC-guest on the restart of the service. With the XML from the test this is what happens: $ virsh define debian/tests/smoke-lxc.xml $ virsh start sl $ virsh list Id Name State 2280 sl running $ virsh lxc-enter-namespace --noseclabel sl /bin/ls /bin/ls /bin/ls # At this point we know and have confirmed the guest works # Now restarting libvirtd breaks it. $ systemctl restart libvirtd # Now the guest container is gone Pre restart it looks like: 4 02426 1 20 0 138712 16132 poll_s Sl ? 0:00 /usr/lib/libvirt/libvirt_lxc --name sl --console 20 --security=apparmor --handshake 23 4 024282426 20 0 4084 3216 poll_s Ss+ pts/0 0:00 \_ /bin/bash The guest log in /var/log/libvirt/lxc/sl.log gets this entry in !BOTH! cases: 2019-09-23 10:51:46.004+: 2426: error : virNetSocketReadWire:1804 : End of file while reading data: Input/output error So this is a common red-herring, the system with systemd 241-7ubuntu1 has the same as well. Another red-herring is the libvirtd service on restart reporting the LXC processes as left-over. This also happens with old and new systemd: Sep 23 12:51:46 autopkgtest systemd[1]: libvirtd.service: Found left-over process 2428 (bash) in control group while starting unit. Ignoring. Sep 23 12:51:46 autopkgtest systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. Sep 23 12:51:46 autopkgtest systemd[1]: libvirtd.service: Found left-over process 2426 (libvirt_lxc) in control group while starting unit. Ignoring. Sep 23 12:51:46 autopkgtest systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. The error that is different between 241 and 243 is from the libvirtd daemon: Sep 23 12:51:46 autopkgtest libvirtd[2448]: internal error: No valid cgroup for machine sl Sep 23 12:51:46 autopkgtest libvirtd[2448]: End of file while reading data: Input/output error This is not just a visibility problem, the process that was the guest really is gone at this point. -- 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/1844879 Title: Behaviour change in systemd 243 breaks libvirt autopkgtest Status in libvirt package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: With systemd 243 libvirt autopkgtest starts failing: http://autopkgtest.ubuntu.com/packages/libv/libvirt/eoan/amd64 https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/amd64/libv/libvirt/20190921_104518_69667@/log.gz ... + virt-xml-validate debian/tests/smoke-lxc.xml debian/tests/smoke-lxc.xml validates + virsh define debian/tests/smoke-lxc.xml Domain sl defined from debian/tests/smoke-lxc.xml + rm -f /var/log/libvirt/lxc/sl.log + virsh start sl Domain sl started + grep -qs starting up /var/log/libvirt/lxc/sl.log + check_domain + grep/bin/ls Domain sl has been undefined -qs sl[[:space:]]\+running + virsh list + virsh lxc-enter-namespace --noseclabel sl /bin/ls /bin/ls + systemctl restart libvirtd + check_domain + grep -qs sl[[:space:]]\+running + virsh list + cleanup + [ -z ] + virsh destroy sl error: Failed to destroy domain sl error: Requested operation is not valid: domain is not running + true + virsh undefine sl + CLEANED_UP=1 autopkgtest [10:41:05]: test smoke-lxc: ---] autopkgtest [10:41:07]: test smoke-lxc: - - - - - - - - - - results - - - - - - - - - - smoke-lxcFAIL non-zero exit status 1 ... The behaviour change is still present in systemd master (v243-112-g984b96aa7a) I can revert the change in systemd, but it also fixes an issue reported at upstream. I will take another look later, but wanted to document my findings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1844879/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1844992] [NEW] Update to 1.18.0 not this cycle
Public bug reported: The new version has new features and it's late for this cycle ** Affects: v4l-utils (Ubuntu) Importance: Wishlist Status: New ** Tags: upgrade-software-version version-blocked-ff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to v4l-utils in Ubuntu. https://bugs.launchpad.net/bugs/1844992 Title: Update to 1.18.0 not this cycle Status in v4l-utils package in Ubuntu: New Bug description: The new version has new features and it's late for this cycle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/v4l-utils/+bug/1844992/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1842643] Re: [ffe] Update to 1.44.6
We failed to have consensus in Paris and I feel like it's getting late now and we have enough other work to do to wrap the cycle so would prefer to delay to next cycle now. Iain, what do you think? (you opened the FFe but so you should be the one deciding if we withdraw the request) ** Changed in: pango1.0 (Ubuntu) Importance: Undecided => Wishlist ** Changed in: pango1.0 (Ubuntu) Status: New => Triaged ** Tags added: version-blocked-ff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1842643 Title: [ffe] Update to 1.44.6 Status in pango1.0 package in Ubuntu: Triaged Bug description: There are a lot of changes in pango1.0 since the version we currently have in eoan. We held off updating because there was a test failure. This has been resolved in the latest release, so we'd like to go for the update now. Overview of changes in 1.44.6 = - docs: Fix symbol indices - Fix Thai line breaking - Re-add symbols needed by some bindings - Don't insert hyphens for some languages - Fix a crash with hyphenation Overview of changes in 1.44.5 = - Revert a broken change (causing crashes on OS X) Overview of changes in 1.44.4 = - Add an insert-hyphens attribute - Reinstate the return type of pango_fc_font_lock_face - Fix a problem with ellipses getting the wrong font - fc: Improve filtering by font format - Re-add PangoFcFont to public headers - Install PangoFc and PangoOT introspection files - Fix ink rectangles to have positive height - Fix mark positioning - Switch to using harfbuzz for metrics Overview of changes in 1.44.3 = - Install pango-ot headers - Make subpixel positioning optional - fc: Ignore fonts with unsupported formats Overview of changes in 1.44.2 = - Disable ligatures when letterspacing - Set design coords on hb_font_t - Expose more font options in pango-view - OS X: Make 'system-ui' font work - Keep deprecated pango-fc apis in headers - Make hex boxes work, always - introspection: Various build fixes - introspection: Add PangoPT, PangoFT2 namespaces - layout: Make the new line-spacing opt-in Overview of changes in 1.44.1 = - Fix a crash with allow_break attributes - Fix Emoji spacing - Fix up includes and pkg-config requires - Correct some cases for hyphen insertion Overview of changes in 1.44.0 = - Use harfbuzz for shaping on all platforms - Stop using freetype for font loading; this drops support for type1 and bitmap fonts - Add a getter for hb_font_t - Make PangoCoverage a GObject - Add a pango_tailor_break api - font metrics: Add line height - layout: Support line spacing - layout: Draw hyphens for line breaks - Add an attribute to suppress line breaking - cairo: Don't render hex boxes for space - Add an attribute to show invisible characters - Stop quantizing glyph positions - Add tests for itemization and line breaking - Remove language and shape engine remnants - Rename meson options: gtk_doc, introspection - Require GLib 2.59.2 - Require Harfbuzz 2.0 Overview of changes in 1.43.0 = - Drop autotools - Drop Visual Studio build - Build with meson everywhere - Update Emoji tables for Unicode 11 - Update test data for Unicode 11 - Fix a crash with Thai breaking - Fix a crash with font variations - Deprecate bidi apis in favor of fribidi - Add a variable font family api - Improve font fallback handling on win32 And see posts from upstream https://blogs.gnome.org/mclasen/2019/07/19/pango-updates/ https://blogs.gnome.org/mclasen/2019/07/27/more-text-rendering-updates/ https://blogs.gnome.org/mclasen/2019/08/07/pango-1-44-wrap-up/ for the new features. We'd like to update to it, if possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1842643/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1830796] Update Released
The verification of the Stable Release Update for gdb 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 gdb in Ubuntu. https://bugs.launchpad.net/bugs/1830796 Title: [Bionic][ARM64]Failure debugging linux kernel Status in gdb package in Ubuntu: Fix Released Status in gdb source package in Bionic: Fix Released Bug description: [Impact] GDB fails to debug ARM64 vmlinux debug image with proc/kcore information. For example it is unable to print values of variables like 'jiffies_64'. [Test] # gdb /usr/lib/debug/boot/vmlinux-4.18.0-20-generic /proc/kcore [New process 1] Core was generated by `BOOT_IMAGE=/boot/vmlinuz-4.18.0-20-generic root=UUID=edb5e5a7-8272-4e13-aa25-37'. #0 0x in ?? () (gdb) p jiffies_64 Cannot access memory at address 0x09616980 (gdb) [Fix] This issue was fixed upstream (git://sourceware.org/git/binutils-gdb.git) by the following patch: 8727de56b0 Fix tagged pointer support [Regression Potential] The risk of regression after applying this patch could be to architectures other than ARM64 due to changes to gdb/util.c. Please see comment #2 where I have tested the PPA package on a ppc64el system and found it does not introduce any regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1830796/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1830796] Re: [Bionic][ARM64]Failure debugging linux kernel
This bug was fixed in the package gdb - 8.1-0ubuntu3.1 --- gdb (8.1-0ubuntu3.1) bionic; urgency=medium * Fix tagged pointer support. LP: #1830796 -- Manoj Iyer Fri, 28 Jun 2019 08:26:38 -0700 ** Changed in: gdb (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 gdb in Ubuntu. https://bugs.launchpad.net/bugs/1830796 Title: [Bionic][ARM64]Failure debugging linux kernel Status in gdb package in Ubuntu: Fix Released Status in gdb source package in Bionic: Fix Released Bug description: [Impact] GDB fails to debug ARM64 vmlinux debug image with proc/kcore information. For example it is unable to print values of variables like 'jiffies_64'. [Test] # gdb /usr/lib/debug/boot/vmlinux-4.18.0-20-generic /proc/kcore [New process 1] Core was generated by `BOOT_IMAGE=/boot/vmlinuz-4.18.0-20-generic root=UUID=edb5e5a7-8272-4e13-aa25-37'. #0 0x in ?? () (gdb) p jiffies_64 Cannot access memory at address 0x09616980 (gdb) [Fix] This issue was fixed upstream (git://sourceware.org/git/binutils-gdb.git) by the following patch: 8727de56b0 Fix tagged pointer support [Regression Potential] The risk of regression after applying this patch could be to architectures other than ARM64 due to changes to gdb/util.c. Please see comment #2 where I have tested the PPA package on a ppc64el system and found it does not introduce any regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1830796/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815172] Re: [bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa
This bug was fixed in the package mesa - 19.0.8-0ubuntu0~18.04.2 --- mesa (19.0.8-0ubuntu0~18.04.2) bionic; urgency=medium * i965-revert-enabling-softpin.diff: Dropped, unnecessary by now and broke Ice Lake which needs softpin. (LP: #1815172) * rules: Force -DNDEBUG, meson < 0.47 is buggy and doesn't set it even if we have b_ndebug=true. (LP: #1841412) -- Timo Aaltonen Tue, 27 Aug 2019 09:42:44 +0300 ** 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/1815172 Title: [bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa Status in Mesa: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in mesa source package in Bionic: Fix Released Status in linux source package in Cosmic: Won't Fix Status in mesa source package in Cosmic: Fix Released Bug description: [Impact] Several schools reported black screens after normally updating their Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1. Downgrading mesa fixes the problem. lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:8694]Kernel modules: i915 Unfortunately I can't find a lot of useful information, here are some bits: * systemctl --failed says "gpu-manager" and "lightdm" have failed * Xorg.log is clean: https://termbin.com/6l2b * dmesg too: https://termbin.com/ip4e * It happens on lightdm/MATE, I don't know about Ubuntu GNOME. * If one runs `xinit` from ssh, it fails with: i965: Failed to submit batchbuffer: Invalid argument This is caused by mesa assuming that soft-pinning on GEN8+ is working since kernel 4.5, but in fact this issue wasn't fixed until 4.19.3. So a proper fix would be to backport commits from 4.19.3/4.20 to fix GTT sizes/pin flags, but that's left for future. [Test case] install fixed mesa or kernel, check that the regression is fixed [Regression potential] mesa: shouldn't be any, it just reverts the change to always soft-pin (TODO kernel: adds commits from upstream stable, which have been well tested upstream by now) To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815172/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813581] Re: gpgme1.0 ftbfs in 18.04 LTS
** Tags removed: block-proposed ** Tags added: block-proposed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gpgme1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1813581 Title: gpgme1.0 ftbfs in 18.04 LTS Status in gpgme1.0 package in Ubuntu: Won't Fix Status in gpgme1.0 source package in Bionic: Fix Committed Bug description: [Impact] according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html gpgme1.0 ftbfs. * Start testing of TofuInfoTest * Config: Using QtTest library 5.9.5, Qt 5.9.5 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 7.3.0) PASS : TofuInfoTest::initTestCase() PASS : TofuInfoTest::testTofuNull() PASS : TofuInfoTest::testTofuInfo() PASS : TofuInfoTest::testTofuSignCount() PASS : TofuInfoTest::testTofuKeyList() PASS : TofuInfoTest::testTofuPolicy() FAIL! : TofuInfoTest::testTofuConflict() 'sig.validity() == Signature::Marginal' returned FALSE. () Loc: [t-tofuinfo.cpp(458)] PASS : TofuInfoTest::cleanupTestCase() Totals: 7 passed, 1 failed, 0 skipped, 0 blacklisted, 2386ms * Finished testing of TofuInfoTest * FAIL: t-tofuinfo [Test case] build it [Regression potential] This only changes the test suite run during build, and that one currently fails, so it can't cause any regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1813581/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1808979] Re: package python-gtk2-dev 2.24.0-5.1ubuntu2 failed to install/upgrade: installed python-gtk2-dev package post-installation script subprocess returned error exit status
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: python-defaults (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1808979 Title: package python-gtk2-dev 2.24.0-5.1ubuntu2 failed to install/upgrade: installed python-gtk2-dev package post-installation script subprocess returned error exit status 1 Status in python-defaults package in Ubuntu: Confirmed Bug description: error by update ProblemType: Package DistroRelease: Ubuntu 18.04 Package: python-gtk2-dev 2.24.0-5.1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 AptOrdering: gnome-desktop3-data:amd64: Install libgnome-desktop-3-17:amd64: Install gir1.2-gnomedesktop-3.0:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Tue Dec 18 14:33:12 2018 ErrorMessage: installed python-gtk2-dev package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2015-08-09 (1226 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python3.6, Python 3.6.7, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: pygtk Title: package python-gtk2-dev 2.24.0-5.1ubuntu2 failed to install/upgrade: installed python-gtk2-dev package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2018-08-19 (121 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1808979/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1841412] Re: Build with NDEBUG again
This bug was fixed in the package mesa - 19.0.8-0ubuntu0~18.04.2 --- mesa (19.0.8-0ubuntu0~18.04.2) bionic; urgency=medium * i965-revert-enabling-softpin.diff: Dropped, unnecessary by now and broke Ice Lake which needs softpin. (LP: #1815172) * rules: Force -DNDEBUG, meson < 0.47 is buggy and doesn't set it even if we have b_ndebug=true. (LP: #1841412) -- Timo Aaltonen Tue, 27 Aug 2019 09:42:44 +0300 ** 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/1841412 Title: Build with NDEBUG again Status in mesa package in Ubuntu: Invalid Status in mesa source package in Bionic: Fix Released Bug description: [Impact] Mesa is now built with meson, and it turns out that meson < 0.47.0 (commit 7c4736d27f4c5d7 to be exact) doesn't handle command line options properly which means that -Db_ndebug=true didn't have any effect when mesa is built on bionic. This means that some asserts are enabled, and at least nouveau is affected. [Test case] chech the build log that -DNDEBUG is passed [Regression potential] none really, it just adds a build flag which should've been there To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1841412/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1841412] Update Released
The verification of the Stable Release Update for mesa has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1841412 Title: Build with NDEBUG again Status in mesa package in Ubuntu: Invalid Status in mesa source package in Bionic: Fix Released Bug description: [Impact] Mesa is now built with meson, and it turns out that meson < 0.47.0 (commit 7c4736d27f4c5d7 to be exact) doesn't handle command line options properly which means that -Db_ndebug=true didn't have any effect when mesa is built on bionic. This means that some asserts are enabled, and at least nouveau is affected. [Test case] chech the build log that -DNDEBUG is passed [Regression potential] none really, it just adds a build flag which should've been there To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1841412/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1844132] Re: FFe: Mesa 19.2.0
** Description changed: It would be great to get 19.2.0 in eoan, though it's release cycle has slipped. It's working fine on a typical desktop use here on i915 (Kaby Lake). It would also migrate to llvm-9. It is currently at rc3, and final version is expected to arrive next week (week 39). New features: + Full support for Intel Ice Lake Support for AMD Navi GL_ARB_post_depth_coverage on radeonsi (Navi) GL_ARB_seamless_cubemap_per_texture on etnaviv (if GPU supports SEAMLESS_CUBE_MAP) GL_EXT_shader_image_load_store on radeonsi (with LLVM >= 10) GL_EXT_shader_samples_identical on iris and radeonsi (if using NIR) GL_EXT_texture_shadow_lod on i965, iris EGL_EXT_platform_device VK_AMD_buffer_marker on radv VK_EXT_index_type_uint8 on radv VK_EXT_post_depth_coverage on radv VK_EXT_queue_family_foreign on radv VK_EXT_sample_locations on radv VK_EXT_shader_demote_to_helper_invocation on Intel. VK_KHR_depth_stencil_resolve on radv VK_KHR_imageless_framebuffer on radv VK_KHR_shader_atomic_int64 on radv VK_KHR_uniform_buffer_standard_layout on radv (note: iris is the new DRI driver for newer Intel, not enabled by default yet) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1844132 Title: FFe: Mesa 19.2.0 Status in mesa package in Ubuntu: Confirmed Status in mesa source package in Eoan: Confirmed Bug description: It would be great to get 19.2.0 in eoan, though it's release cycle has slipped. It's working fine on a typical desktop use here on i915 (Kaby Lake). It would also migrate to llvm-9. It is currently at rc3, and final version is expected to arrive next week (week 39). New features: Full support for Intel Ice Lake Support for AMD Navi GL_ARB_post_depth_coverage on radeonsi (Navi) GL_ARB_seamless_cubemap_per_texture on etnaviv (if GPU supports SEAMLESS_CUBE_MAP) GL_EXT_shader_image_load_store on radeonsi (with LLVM >= 10) GL_EXT_shader_samples_identical on iris and radeonsi (if using NIR) GL_EXT_texture_shadow_lod on i965, iris EGL_EXT_platform_device VK_AMD_buffer_marker on radv VK_EXT_index_type_uint8 on radv VK_EXT_post_depth_coverage on radv VK_EXT_queue_family_foreign on radv VK_EXT_sample_locations on radv VK_EXT_shader_demote_to_helper_invocation on Intel. VK_KHR_depth_stencil_resolve on radv VK_KHR_imageless_framebuffer on radv VK_KHR_shader_atomic_int64 on radv VK_KHR_uniform_buffer_standard_layout on radv (note: iris is the new DRI driver for newer Intel, not enabled by default yet) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1844132/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1844879] Re: Behaviour change in systemd 243 breaks libvirt autopkgtest
** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1844879 Title: Behaviour change in systemd 243 breaks libvirt autopkgtest Status in libvirt package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: With systemd 243 libvirt autopkgtest starts failing: http://autopkgtest.ubuntu.com/packages/libv/libvirt/eoan/amd64 https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/amd64/libv/libvirt/20190921_104518_69667@/log.gz ... + virt-xml-validate debian/tests/smoke-lxc.xml debian/tests/smoke-lxc.xml validates + virsh define debian/tests/smoke-lxc.xml Domain sl defined from debian/tests/smoke-lxc.xml + rm -f /var/log/libvirt/lxc/sl.log + virsh start sl Domain sl started + grep -qs starting up /var/log/libvirt/lxc/sl.log + check_domain + grep/bin/ls Domain sl has been undefined -qs sl[[:space:]]\+running + virsh list + virsh lxc-enter-namespace --noseclabel sl /bin/ls /bin/ls + systemctl restart libvirtd + check_domain + grep -qs sl[[:space:]]\+running + virsh list + cleanup + [ -z ] + virsh destroy sl error: Failed to destroy domain sl error: Requested operation is not valid: domain is not running + true + virsh undefine sl + CLEANED_UP=1 autopkgtest [10:41:05]: test smoke-lxc: ---] autopkgtest [10:41:07]: test smoke-lxc: - - - - - - - - - - results - - - - - - - - - - smoke-lxcFAIL non-zero exit status 1 ... The behaviour change is still present in systemd master (v243-112-g984b96aa7a) I can revert the change in systemd, but it also fixes an issue reported at upstream. I will take another look later, but wanted to document my findings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1844879/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1844763] Re: file /etc/network/interfaces is missing in eoan-desktop-amd64.iso
** Package changed: ubuntu => network-manager (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1844763 Title: file /etc/network/interfaces is missing in eoan-desktop-amd64.iso Status in network-manager package in Ubuntu: Confirmed Bug description: The file /etc/network/interfaces is missing after install guestOS with eoan-desktop-amd64.iso(daily build Sep-17-2019) in ESXi. This issue cause a failure for VMware Guest OS Customization To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1844763/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1844763] [NEW] file /etc/network/interfaces is missing in eoan-desktop-amd64.iso
You have been subscribed to a public bug: The file /etc/network/interfaces is missing after install guestOS with eoan-desktop-amd64.iso(daily build Sep-17-2019) in ESXi. This issue cause a failure for VMware Guest OS Customization ** Affects: network-manager (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: bot-comment -- file /etc/network/interfaces is missing in eoan-desktop-amd64.iso https://bugs.launchpad.net/bugs/1844763 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager 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 1840699] Re: Caps-lock doesn't work correctly in Old Hungarian layout
Thank you Gunnar Hjalmarsson! I tested this package on bionic, and it works. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1840699 Title: Caps-lock doesn't work correctly in Old Hungarian layout Status in xkeyboard-config: Fix Released Status in xkeyboard-config package in Ubuntu: Fix Released Bug description: Xkeyboard-config's version 2.27 resolves this problem To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/1840699/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
