[Touch-packages] [Bug 1869629] Re: please add /etc/mdns.allow to /etc/apparmor.d/abstractions/mdns
Hi Rich, thanks for your continued help - yes I agree that we need to fix this in the apparmor abstraction and not each individual other affected package. FYI: I pinged jjohansen yesterday and he said he will make an upload ready and will ask jdstrand to sponsor it. I subscribed them both here now to make that clear. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1869629 Title: please add /etc/mdns.allow to /etc/apparmor.d/abstractions/mdns Status in apparmor package in Ubuntu: New Status in chrony package in Ubuntu: Invalid Bug description: In focal users of mdns get denials in apparmor confined applications. An exampel can be found in the original bug below. It seems it is a common pattern, see https://github.com/lathiat/nss-mdns#etcmdnsallow Therefore I'm asking to add /etc/mdns.allow r, to the file /etc/apparmor.d/abstractions/mdns" by default. --- original bug --- Many repetitions of audit: type=1400 audit(1585517168.705:63): apparmor="DENIED" operation="open" profile="/usr/sbin/chronyd" name="/etc/mdns.allow" pid=1983815 comm="chronyd" requested_mask="r" denied_mask="r" fsuid=123 ouid=0 in log. I use libnss-mdns for .local name resolution, so /etc/nsswitch.conf contains hosts: files mdns [NOTFOUND=return] myhostname dns and /etc/mnds.allow contains the domains to resolve with mDNS (in may case, "local." and "local"; see /usr/share/doc/libnss- mdns/README.html.) Presumably cronyd calls a gethostbyX() somewhere, thus eventually trickling down through the name service switch and opening /etc/mdns.allow, which the AppArmor profile in the chrony package does not allow. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: chrony 3.5-6ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 Date: Sun Mar 29 15:02:39 2020 InstallationDate: Installed on 2020-03-26 (3 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200326) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: chrony UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1869629/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869116] Re: smartctl-validate is borked in a recent release
Rereading my comment above I had a huge typo, I meant to say that the script output for 18/16 LTS said "the drivers do not support SMART", rather than use the word RAID, sorry about that confusion! -cees -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1869116 Title: smartctl-validate is borked in a recent release Status in lxd: Unknown Status in MAAS: Triaged Status in util-linux package in Ubuntu: New Bug description: Bug (maybe?) details first, diatribe second. Bug Summary: multi-hdd / raid with multiple drives / multiple devices or something along those lines cannot be commissioned anymore: 2.4.x worked fine, 2.7.0 does not. Here is the script output of smartctl-validate: - # /dev/sda (Model: PERC 6/i, Serial: 6842b2b0740e9900260e66c9220df4ac) Unable to run 'smartctl-validate': Storage device 'PERC 6/i' with serial '6842b2b0740e9900260e66c9220df4ac' not found! This indicates the storage device has been removed or the OS is unable to find it due to a hardware failure. Please re-commission this node to re-discover the storage devices, or delete this device manually. Given parameters: {'storage': {'argument_format': '{path }', 'type': 'storage', 'value': {'id_path': '/dev/disk/by-id/wwn-0x6842b2b0740e9900260e66c9220df4ac', 'model': 'PERC 6/i', 'name': 'sda', 'physical_blockdevice_id': 33, 'serial': '6842b2b0740e9900260e66c9220df4ac' } } } Discovered storage devices: [ {'NAME': 'sda', 'MODEL': 'PERC_6/i', 'SERIAL': '6842b2b0740e9900260e66c9220df4ac' }, {'NAME': 'sdb', 'MODEL': 'PERC_6/i', 'SERIAL': '6842b2b0740e9900260e66f924ecece0' }, {'NAME': 'sr0', 'MODEL': 'TEAC_DVD-ROM_DV-28SW', 'SERIAL': '10092013112645' } ] Discovered interfaces: {'xx: xx: xx: xx: xx: xx': 'eno1' } - - # /dev/sdb (Model: PERC 6/i, Serial: 6842b2b0740e9900260e66f924ecece0) Unable to run 'smartctl-validate': Storage device 'PERC 6/i' with serial '6842b2b0740e9900260e66f924ecece0' not found! This indicates the storage device has been removed or the OS is unable to find it due to a hardware failure. Please re-commission this node to re-discover the storage devices, or delete this device manually. Given parameters: {'storage': {'argument_format': '{path }', 'type': 'storage', 'value': {'id_path': '/dev/disk/by-id/wwn-0x6842b2b0740e9900260e66f924ecece0', 'model': 'PERC 6/i', 'name': 'sdb', 'physical_blockdevice_id': 34, 'serial': '6842b2b0740e9900260e66f924ecece0' } } } Discovered storage devices: [ {'NAME': 'sda', 'MODEL': 'PERC_6/i', 'SERIAL': '6842b2b0740e9900260e66c9220df4ac' }, {'NAME': 'sdb', 'MODEL': 'PERC_6/i', 'SERIAL': '6842b2b0740e9900260e66f924ecece0' }, {'NAME': 'sr0', 'MODEL': 'TEAC_DVD-ROM_DV-28SW', 'SERIAL': '10092013112645' } ] Discovered interfaces: {'xx: xx: xx: xx: xx: xx': 'eno1' } - You can see that it says the storage cannot be found and immediately lists it as a discovered device. It does it for both tests (one for each drive), and for both servers Bug Details: I had maas 2.4.x for the longest time over my journey (see below journey) and have never had any problems re-commissioning (or deleting and re-discovering over boot PXE) 2 of my servers (r610, r710). r610 has an iPERC 6, four 10K X00GB drives configured in a RAID10, 1 virtual disk. r710 has an iPERC 6, 6x 2TB drives, configured in a RAID10, 2 virtual disks So commission after commission trying to get through my journey, 0 problems. After I finally get everything figured out on the juju, network/vlan, quad-nic end, I go to re-commission and I cannot. smartctl-validate fails on both, over and over again. I even destroyed and re-created the raid/VDs, still not. After spending so much time on it I remembered that it was the first time I had tried to re-commission these two servers since doing an upgrade from 2.4.x->2.7 in an effort to use the updated KVM integration to add a couple more guests. Once I got all everything figured out I went to re-commission everything and boom. [Upgrade path notes] In full disclosure, in case this matters. I was on apt install of 2.4.x and using snap for 2.7, except it didn't work. So I read on how to do apt 2.7 and did that and did not uninstall snap 2.7 yet. I wanted to migrate from apt to snap but do not know how to without losing all maas data and could not find docs on it, so a problem for another day. But in case that is part of the problem for some odd reason, I wanted to share. [Diatribe] My journey to get maas+juju+openstack+kubernets has been less then stellar. I have ran into problem after problem; albeit some of which were my own. I am so close, after spending the last 6 months on/off when I had time, and
[Touch-packages] [Bug 1867535] Re: [FFe] LXC 4.0.0 LTS
FFe granted. ** Changed in: lxc (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1867535 Title: [FFe] LXC 4.0.0 LTS Status in lxc package in Ubuntu: Confirmed Bug description: LXC 4.0 LTS will be tagged in the next week or so. LXC in Ubuntu is currently in universe as its main user is a snap nowadays (LXD) and builds directly from the upstream versions. We haven't written the changelog yet, but one thing worth noting is that it is 100% backward compatible, we do not break API and don't need to rebuild any of the rdepend for it. The main reason to want it in 20.04 LTS is because LXC 4.0 is itself an LTS with a matching 5 years of support. It also adds support for cgroupv2 which we expect to become more and more needed in the coming months/years. It'd be great if the release team could make a decision based on this already, if not, I will update the bug with the changelog and diff once we do have the release out. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1867535/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1866923] Re: Wifi connection says it's connected but this is not true after the computer goes into a sleep status
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1866923 Title: Wifi connection says it's connected but this is not true after the computer goes into a sleep status Status in network-manager package in Ubuntu: Confirmed Bug description: The wifi is connected and working correctly when powered on, however when I close the laptop lid, which I think puts it to sleep, and then reopen it, it says it's connected according to the icon but this is not true. A workaround is turning on Airplane mode and then switching it back on again. It then reconnects and is then fine again. Unless I close the lid and then the process repeats again. I guess this is to do with the wifi driver but I don't know what package it is so I just picked network-manager, sorry - I'm trying :) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.20.4-2ubuntu2.2 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 10 19:29:03 2020 InstallationDate: Installed on 2020-03-09 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IpRoute: default via 192.168.68.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.68.0/24 dev wlp1s0 proto kernel scope link src 192.168.68.18 metric 600 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.4 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/1866923/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869789] Re: Crossover fails to install due to missing lib32nss-mdns
The last currently-supported Ubuntu release to contain a lib32nss-mdns package is Ubuntu 14.04. nss-mdns (0.10-7) unstable; urgency=medium * Add Vcs-Git, Vcs-Browser fields * Move the git repo to collab-maint; it is still a pkg-utopia package, but there seems little reason to make it more awkward for other developers to commit changes. * Remove transitional lib32nss-mdns and libnss-mdns-i386 packages. The transition took place in Debian 8 (jessie) and we do not support direct upgrades from pre-jessie to stretch. * This upload includes automatic debug symbols (Closes: #642026) * Standards-Version: 3.9.7 (no changes needed) * Normalize packaging via wrap-and-sort -abst -- Simon McVittie Fri, 05 Feb 2016 11:21:05 + I'm sorry, but we can't support third-party .deb packages that have not updated their packaging in over 6 years. ** Package changed: apt (Ubuntu) => nss-mdns (Ubuntu) ** Changed in: nss-mdns (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1869789 Title: Crossover fails to install due to missing lib32nss-mdns Status in nss-mdns package in Ubuntu: Won't Fix Bug description: Crossover depends on lib32nss-mdns which does not appear to be available in 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nss-mdns/+bug/1869789/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1866923] Re: Wifi connection says it's connected but this is not true after the computer goes into a sleep status
I'm having the same error no ubuntu 20.04 -- 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/1866923 Title: Wifi connection says it's connected but this is not true after the computer goes into a sleep status Status in network-manager package in Ubuntu: Confirmed Bug description: The wifi is connected and working correctly when powered on, however when I close the laptop lid, which I think puts it to sleep, and then reopen it, it says it's connected according to the icon but this is not true. A workaround is turning on Airplane mode and then switching it back on again. It then reconnects and is then fine again. Unless I close the lid and then the process repeats again. I guess this is to do with the wifi driver but I don't know what package it is so I just picked network-manager, sorry - I'm trying :) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.20.4-2ubuntu2.2 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 10 19:29:03 2020 InstallationDate: Installed on 2020-03-09 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IpRoute: default via 192.168.68.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.68.0/24 dev wlp1s0 proto kernel scope link src 192.168.68.18 metric 600 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.4 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/1866923/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869831] [NEW] lvm2: VG swaps to most recent disk if underlying PV has duplicate UUID and VG name
Public bug reported: [Impact] On xenial with lvm2 2.02.133-1ubuntu10, if you say take a snapshot of a disk with an active VG, and attach that disk to the host, the VG will swap from the existing disk to the newly attached disk. This breaks mountpoints and directs writes to the wrong storage device. Note this only happens in the edge case where the PV and VGs are absolute duplicates. [Test] Steps to reproduce: 1) Create a xenial instance. 2) Create a secondary disk and attach it. 3) Create a PV, VG and LV on the disk. 4) Run lsblk: ubuntu@ubuntu:~$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT vdb 253:16 02G 0 disk └─test1-database 252:00 1.6G 0 lvm /mnt/database 5) Create a "snapshot" of this disk (cp -rp disk.qcow2 disk2.qcow2) 6) Attach disk2.qcow2. Check lsblk ubuntu@ubuntu:~$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT vdb 253:16 02G 0 disk vdc 253:32 02G 0 disk └─test1-database 252:00 1.6G 0 lvm We can see the VG jumps from /dev/vdb to /dev/vdc, even though the system was running at the time, and the VG was mounted. [Regression Potential] The risk of regression if we fix this issue is extreme. The commits themselves are large and modify core LVM code, and change the behaviour of how disks are scanned and processed. The commits introduce new configuration options. The commits do not apply cleanly, and all of them require significant backporting, and quite a few dependencies. Because of this, it would be far too risky to fix this for xenial, so I will mark this as wontfix. [Other Info] This was fixed in 2.02.153 by the following commits: commit 49d9582bed338dc555b616bcc9de20fafd00ce2d Author: David Teigland Date: Tue Mar 29 13:29:39 2016 -0500 Subject: lvmcache: use active LVs and device sizes to choose between duplicates Link: https://github.com/lvmteam/lvm2/commit/49d9582bed338dc555b616bcc9de20fafd00ce2d commit d4e434d1e6082ff4d448f4fbc03962c6f0926da4 Author: David Teigland Date: Fri Apr 29 14:42:14 2016 -0500 Subject: pvs: new attr and field for unchosen duplicate device Link: https://github.com/lvmteam/lvm2/commit/d4e434d1e6082ff4d448f4fbc03962c6f0926da4 commit d3d13e134af15611c3f12107aa1627b12110a974 Author: David Teigland Date: Thu Feb 11 12:37:36 2016 -0600 Subject: lvmcache: process duplicate PVs directly Link: https://github.com/lvmteam/lvm2/commit/d3d13e134af15611c3f12107aa1627b12110a974 commit 8b7a78c728be3b9af698dae9344d01752c4cf615 Author: David Teigland Date: Tue Feb 9 13:06:27 2016 -0600 Subject: lvmcache: improve duplicate PV handling Link: https://github.com/lvmteam/lvm2/commit/8b7a78c728be3b9af698dae9344d01752c4cf615 commit 3d2fbfe243550b7801165f393d27e35044c1a56d Author: David Teigland Date: Fri Jan 29 13:31:54 2016 -0600 Subject: lvmetad: set disabled flag when duplicate PVs are seen Link: https://github.com/lvmteam/lvm2/commit/3d2fbfe243550b7801165f393d27e35044c1a56d commit 9539ee809827a870c88d02cfb2d0dc1e3eaac0d0 Author: David Teigland Date: Fri Jan 29 12:25:20 2016 -0600 Subject: lvmetad: set disabled flag in lvmetad if duplicate PVs are found Link: https://github.com/lvmteam/lvm2/commit/9539ee809827a870c88d02cfb2d0dc1e3eaac0d0 The fixes are present in Ubuntu 16.10 and later, meaning xenial is the only impacted supported release. ** Affects: lvm2 (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: lvm2 (Ubuntu Xenial) Importance: Medium Assignee: Matthew Ruffell (mruffell) Status: Won't Fix ** Affects: lvm2 (Ubuntu Bionic) Importance: Undecided Status: Fix Released ** Affects: lvm2 (Ubuntu Disco) Importance: Undecided Status: Fix Released ** Affects: lvm2 (Ubuntu Eoan) Importance: Undecided Status: Fix Released ** Affects: lvm2 (Ubuntu Focal) Importance: Undecided Status: Fix Released ** Tags: sts ** Also affects: lvm2 (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: lvm2 (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: lvm2 (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: lvm2 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: lvm2 (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: lvm2 (Ubuntu Bionic) Status: New => Fix Released ** Changed in: lvm2 (Ubuntu Disco) Status: New => Fix Released ** Changed in: lvm2 (Ubuntu Eoan) Status: New => Fix Released ** Changed in: lvm2 (Ubuntu Focal) Status: New => Fix Released ** Changed in: lvm2 (Ubuntu Xenial) Status: New => Won't Fix ** Changed in: lvm2 (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: lvm2 (Ubuntu Xenial) Assignee: (unassigned) => Matthew Ruffell (mruffell) ** Tags added: sts -- You received this bug notification because you are a member of Ubuntu Touch seeded packages,
[Touch-packages] [Bug 1866303] Re: slapd crash with pwdAccountLockedTime and stacked overlays
** Changed in: openldap (Debian) Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1866303 Title: slapd crash with pwdAccountLockedTime and stacked overlays Status in openldap package in Ubuntu: Fix Released Status in openldap source package in Xenial: New Status in openldap source package in Bionic: New Status in openldap source package in Disco: Won't Fix Status in openldap source package in Eoan: New Status in openldap package in Debian: Fix Released Bug description: Hello, Please merge openldap 2.4.49+dfsg-2 from Debian unstable to fix an issue in the ppolicy overlay that can crash slapd. Please also consider SRUing the patch after it has had some testing time. Upstream: https://openldap.org/its/?findid=9171 Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953150 The ingredients for the crash are: 1: ppolicy overlay configured with pwdLockout: TRUE 2. smbk5pwd overlay stacked after ppolicy 3. an account locked out via pwdAccountLockedTime 4. a client binding to the locked-out account and also requesting the ppolicy control The buggy code is not as specific as the above steps, so I suspect there are probably other configurations or steps that can trigger the same crash. I will attach my test script and data for reproducing the crash. Expected output (last lines): [ ok ] Starting OpenLDAP: slapd. slapd running ldap_bind: Invalid credentials (49) slapd running Actual output (last lines): [ ok ] Starting OpenLDAP: slapd. slapd running ldap_bind: Invalid credentials (49) slapd dead To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1866303/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869814] Re: ubuntu-docs build failure - possible solution
@Shaun: Have you possibly stumbled into anything similar when building e.g. gnome-user-docs? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxml2 in Ubuntu. https://bugs.launchpad.net/bugs/1869814 Title: ubuntu-docs build failure - possible solution Status in itstool package in Ubuntu: New Status in libxml2 package in Ubuntu: New Status in ubuntu-docs package in Ubuntu: New Bug description: ubuntu-docs failed to build during the second Focal Fossa test rebuild: https://launchpad.net/ubuntu/+archive/test- rebuild-20200327-focal/+build/18982738 It was itstool which failed to generate the localized zh_CN pages. If dropping zh_CN from ubuntu-help/Makefile.am, ubuntu-docs builds. But excluding the Chinese pages is apparently not an acceptable solution. The itstool package in focal {build-,}depends on python3. I built itstool in a PPA with python2 instead, and in that PPA ubuntu-docs built fine without modifications: https://launchpad.net/~gunnarhj/+archive/ubuntu/ubuntu-docs/+packages So the root cause seems to lie neither in ubuntu-docs nor itstool. I would suspect that python3-libxml2 is buggy, but since itstool was built against python2 in eoan, it's hard to tell if it's a regression. Would building itstool against python2 be an acceptable workaround in focal? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/itstool/+bug/1869814/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833116] Re: chtmax98090 not working out of the box
Having the same issue on a Lenovo N20 "Clapper" Chromebook. Applying the Git patch crashes PulseAudio for me as well. Can't get any sound to play at all from the built-in speakers. dylan@dylan-Clapper:~$ aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 3: Generic Digital [Generic Digital] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: chtmax98090 [chtmax98090], device 0: 3 [] Subdevices: 0/1 Subdevice #0: subdevice #0 card 1: chtmax98090 [chtmax98090], device 1: Deep-Buffer Audio (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 dylan@dylan-Clapper:~$ lspci | grep Audio 00:1b.0 Audio device: Intel Corporation Atom Processor Z36xxx/Z37xxx Series High Definition Audio Controller (rev 0e) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1833116 Title: chtmax98090 not working out of the box Status in alsa-driver package in Ubuntu: Confirmed Bug description: chtmax98090 intel HD audio device doesn't work out of the box after installing ubuntu (from 14.04 to 18.04). It shows "Dummy Output" on audio devices. Audio options shows device and it works if I do this: git clone https://github.com/plbossart/UCM.git cd UCM cp -r chtmax98090/ /usr/share/alsa/ucm/ alsactl store It would be great if there were a solution to make it works out of the box. The device (Chromebook Acer CB3-111 has it's end of life for chromeOS in July-August, so I suppose more people with this device will change OS perhaps to Ubuntu). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-21-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jaime 1293 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jun 17 20:32:35 2019 InstallationDate: Installed on 2019-06-17 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2014 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvr:bd08/18/2014:svnGOOGLE:pnGnawty:pvr1.0:cvnGOOGLE:ct3:cvr: dmi.product.name: Gnawty dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1833116/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869578] Re: PCI/internal sound card not detected
Ubuntu 14.04 reached end of standard support in April 2019: https://wiki.ubuntu.com/Releases If you would like to continue with free support then please update to a newer Ubuntu version and tell us if the problem still occurs. If you would like to continue with Ubuntu 14.04 then there is a paid support option detailed at https://www.ubuntu.com/esm ** Tags added: regression-update ** Changed in: alsa-driver (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1869578 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: Won't Fix Bug description: i updated ubuntu 14.04 and now no sound i used aplay -l and i've got this message : internal sound card not detected ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39 Uname: Linux 3.13.0-170-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Sun Mar 29 13:56:20 2020 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2017-10-01 (910 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.product.name: Inspiron 15-3552 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1869578/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833116] Re: chtmax98090 not working out of the box
** Attachment added: "clapper-lspci-vvnn.txt" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1833116/+attachment/5343583/+files/clapper-lspci-vvnn.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1833116 Title: chtmax98090 not working out of the box Status in alsa-driver package in Ubuntu: Confirmed Bug description: chtmax98090 intel HD audio device doesn't work out of the box after installing ubuntu (from 14.04 to 18.04). It shows "Dummy Output" on audio devices. Audio options shows device and it works if I do this: git clone https://github.com/plbossart/UCM.git cd UCM cp -r chtmax98090/ /usr/share/alsa/ucm/ alsactl store It would be great if there were a solution to make it works out of the box. The device (Chromebook Acer CB3-111 has it's end of life for chromeOS in July-August, so I suppose more people with this device will change OS perhaps to Ubuntu). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-21-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jaime 1293 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jun 17 20:32:35 2019 InstallationDate: Installed on 2019-06-17 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2014 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvr:bd08/18/2014:svnGOOGLE:pnGnawty:pvr1.0:cvnGOOGLE:ct3:cvr: dmi.product.name: Gnawty dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1833116/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869759] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- 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/1869759 Title: [amdgpu] Opengl or vulkan or mesa bug that causes textures to glitch when mipmapping or trilinear/bilinear filtering is enabled Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: Textures are glitched (almost like they are cut up and repeated) when mipmapping or trilinear/bilinear filtering is enabled. Workaround is to disable both. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Mar 30 12:03:39 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c4) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Picasso [1025:134f] InstallationDate: Installed on 2019-11-04 (147 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Acer Aspire A515-43 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=a44eb2b0-d036-44b7-9c90-d0a427ecd008 ro quiet splash resume=/dev/nvme0n1p5 resume_offset=15261696 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Grumpy_PK dmi.board.vendor: PK dmi.board.version: V1.06 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.06 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.06:bd09/26/2019:svnAcer:pnAspireA515-43:pvrV1.06:rvnPK:rnGrumpy_PK:rvrV1.06:cvnAcer:ct10:cvrV1.06: dmi.product.family: Aspire 5 dmi.product.name: Aspire A515-43 dmi.product.sku: dmi.product.version: V1.06 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869759/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869116] Re: smartctl-validate is borked in a recent release
That makes sense based on the other information in this bug. MAAS sends the test runner a list of storage devices to run hardware tests on. The test runner uses the model and serial to map to a block device name. This block device name is passed to the smartctl-validate script. smartctl-validate uses smartctl to determine if SMART data is available for the device. Because the model name differs between lsblk and lxc it can't be looked up and the test is marked as a failure. The mapping needs to work so MAAS can pass the block device to to smartctl-validate which knows the test can be skipped. ** Tags added: champagne -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1869116 Title: smartctl-validate is borked in a recent release Status in lxd: Unknown Status in MAAS: Triaged Status in util-linux package in Ubuntu: New Bug description: Bug (maybe?) details first, diatribe second. Bug Summary: multi-hdd / raid with multiple drives / multiple devices or something along those lines cannot be commissioned anymore: 2.4.x worked fine, 2.7.0 does not. Here is the script output of smartctl-validate: - # /dev/sda (Model: PERC 6/i, Serial: 6842b2b0740e9900260e66c9220df4ac) Unable to run 'smartctl-validate': Storage device 'PERC 6/i' with serial '6842b2b0740e9900260e66c9220df4ac' not found! This indicates the storage device has been removed or the OS is unable to find it due to a hardware failure. Please re-commission this node to re-discover the storage devices, or delete this device manually. Given parameters: {'storage': {'argument_format': '{path }', 'type': 'storage', 'value': {'id_path': '/dev/disk/by-id/wwn-0x6842b2b0740e9900260e66c9220df4ac', 'model': 'PERC 6/i', 'name': 'sda', 'physical_blockdevice_id': 33, 'serial': '6842b2b0740e9900260e66c9220df4ac' } } } Discovered storage devices: [ {'NAME': 'sda', 'MODEL': 'PERC_6/i', 'SERIAL': '6842b2b0740e9900260e66c9220df4ac' }, {'NAME': 'sdb', 'MODEL': 'PERC_6/i', 'SERIAL': '6842b2b0740e9900260e66f924ecece0' }, {'NAME': 'sr0', 'MODEL': 'TEAC_DVD-ROM_DV-28SW', 'SERIAL': '10092013112645' } ] Discovered interfaces: {'xx: xx: xx: xx: xx: xx': 'eno1' } - - # /dev/sdb (Model: PERC 6/i, Serial: 6842b2b0740e9900260e66f924ecece0) Unable to run 'smartctl-validate': Storage device 'PERC 6/i' with serial '6842b2b0740e9900260e66f924ecece0' not found! This indicates the storage device has been removed or the OS is unable to find it due to a hardware failure. Please re-commission this node to re-discover the storage devices, or delete this device manually. Given parameters: {'storage': {'argument_format': '{path }', 'type': 'storage', 'value': {'id_path': '/dev/disk/by-id/wwn-0x6842b2b0740e9900260e66f924ecece0', 'model': 'PERC 6/i', 'name': 'sdb', 'physical_blockdevice_id': 34, 'serial': '6842b2b0740e9900260e66f924ecece0' } } } Discovered storage devices: [ {'NAME': 'sda', 'MODEL': 'PERC_6/i', 'SERIAL': '6842b2b0740e9900260e66c9220df4ac' }, {'NAME': 'sdb', 'MODEL': 'PERC_6/i', 'SERIAL': '6842b2b0740e9900260e66f924ecece0' }, {'NAME': 'sr0', 'MODEL': 'TEAC_DVD-ROM_DV-28SW', 'SERIAL': '10092013112645' } ] Discovered interfaces: {'xx: xx: xx: xx: xx: xx': 'eno1' } - You can see that it says the storage cannot be found and immediately lists it as a discovered device. It does it for both tests (one for each drive), and for both servers Bug Details: I had maas 2.4.x for the longest time over my journey (see below journey) and have never had any problems re-commissioning (or deleting and re-discovering over boot PXE) 2 of my servers (r610, r710). r610 has an iPERC 6, four 10K X00GB drives configured in a RAID10, 1 virtual disk. r710 has an iPERC 6, 6x 2TB drives, configured in a RAID10, 2 virtual disks So commission after commission trying to get through my journey, 0 problems. After I finally get everything figured out on the juju, network/vlan, quad-nic end, I go to re-commission and I cannot. smartctl-validate fails on both, over and over again. I even destroyed and re-created the raid/VDs, still not. After spending so much time on it I remembered that it was the first time I had tried to re-commission these two servers since doing an upgrade from 2.4.x->2.7 in an effort to use the updated KVM integration to add a couple more guests. Once I got all everything figured out I went to re-commission everything and boom. [Upgrade path notes] In full disclosure, in case this matters. I was on apt install of 2.4.x and using snap for 2.7, except it didn't work. So I read on how to do apt 2.7 and did that and did not uninstall snap 2.7 yet. I wanted to migrate from apt to snap but do not know how
[Touch-packages] [Bug 1869747] Re: Recent changes have caused Xorg to fail to start. Possibly nvidia driver related.
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete ** Also affects: nvidia-graphics-drivers-440 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-440 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1869747 Title: Recent changes have caused Xorg to fail to start. Possibly nvidia driver related. Status in nvidia-graphics-drivers-440 package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: I am unsure where the problem stems, but changes since the 25th have caused my system to fail to initialise the Xorg display. The console remains operational for debugging. I am currently using ZFS snapshots to use the system as it was on the 25th of March 2020 because that is the last snapshot before this issue. This bug was captured using ubuntu-bug when booted into the broken (i.e. not working) latest snapshot of my filesystem. The versions of packages from the not broken (i.e. correctly working) earlier snapshot of my filesystem are: libnvidia-cfg1-440:amd64 440.64-0ubuntu2 libnvidia-common-440 440.64-0ubuntu2 libnvidia-compute-440:amd64 440.64-0ubuntu2 libnvidia-compute-440:i386 440.64-0ubuntu2 libnvidia-decode-440:amd64 440.64-0ubuntu2 libnvidia-decode-440:i386440.64-0ubuntu2 libnvidia-encode-440:amd64 440.64-0ubuntu2 libnvidia-encode-440:i386440.64-0ubuntu2 libnvidia-fbc1-440:amd64 440.64-0ubuntu2 libnvidia-fbc1-440:i386 440.64-0ubuntu2 libnvidia-gl-440:amd64 440.64-0ubuntu2 libnvidia-gl-440:i386440.64-0ubuntu2 libnvidia-ifr1-440:amd64 440.64-0ubuntu2 libnvidia-ifr1-440:i386 440.64-0ubuntu2 nvidia-compute-utils-440 440.64-0ubuntu2 nvidia-dkms-440 440.64-0ubuntu2 nvidia-driver-440440.64-0ubuntu2 nvidia-kernel-common-440 440.64-0ubuntu2 nvidia-kernel-source-440 440.64-0ubuntu2 nvidia-prime 0.8.14 nvidia-settings 440.64-0ubuntu1 nvidia-utils-440 440.64-0ubuntu2 xserver-xorg-video-nvidia-440440.64-0ubuntu2 $ lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-3ubuntu1) ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 Date: Mon Mar 30 15:49:12 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes InstallationDate: Installed on 2020-03-03 (26 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) MachineType: Gigabyte Technology Co., Ltd. Z170X-UD5 TH ProcEnviron: LANGUAGE=en_GB:en TERM=linux PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_7176ku@/vmlinuz-5.4.0-18-generic root=ZFS=rpool/ROOT/ubuntu_7176ku ro quiet splash intel_iommu=on vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2018 dmi.bios.vendor: American
[Touch-packages] [Bug 1869747] Re: Recent changes have caused Xorg to fail to start. Possibly nvidia driver related.
Yes it's a crash but the stack trace in the log is confused: [ 411.772] (EE) Backtrace: [ 411.772] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x55cd86b5fd2c] [ 411.772] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7f3b483c341f] [ 411.773] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7f3b4820018b] [ 411.773] (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7f3b481df859] [ 411.773] (EE) unw_get_proc_name failed: no unwind info found [-10] [ 411.773] (EE) 4: /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so (?+0x0) [0x7f3b42d54375] [ 411.774] (EE) 5: /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so (nouveau_drm_screen_create+0x203457) [0x7f3b439462f7] [ 411.774] (EE) 6: /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so (__driDriverGetExtensions_zink+0x24ee8) [0x7f3b42da45c8] -- 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/1869747 Title: Recent changes have caused Xorg to fail to start. Possibly nvidia driver related. Status in nvidia-graphics-drivers-440 package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: I am unsure where the problem stems, but changes since the 25th have caused my system to fail to initialise the Xorg display. The console remains operational for debugging. I am currently using ZFS snapshots to use the system as it was on the 25th of March 2020 because that is the last snapshot before this issue. This bug was captured using ubuntu-bug when booted into the broken (i.e. not working) latest snapshot of my filesystem. The versions of packages from the not broken (i.e. correctly working) earlier snapshot of my filesystem are: libnvidia-cfg1-440:amd64 440.64-0ubuntu2 libnvidia-common-440 440.64-0ubuntu2 libnvidia-compute-440:amd64 440.64-0ubuntu2 libnvidia-compute-440:i386 440.64-0ubuntu2 libnvidia-decode-440:amd64 440.64-0ubuntu2 libnvidia-decode-440:i386440.64-0ubuntu2 libnvidia-encode-440:amd64 440.64-0ubuntu2 libnvidia-encode-440:i386440.64-0ubuntu2 libnvidia-fbc1-440:amd64 440.64-0ubuntu2 libnvidia-fbc1-440:i386 440.64-0ubuntu2 libnvidia-gl-440:amd64 440.64-0ubuntu2 libnvidia-gl-440:i386440.64-0ubuntu2 libnvidia-ifr1-440:amd64 440.64-0ubuntu2 libnvidia-ifr1-440:i386 440.64-0ubuntu2 nvidia-compute-utils-440 440.64-0ubuntu2 nvidia-dkms-440 440.64-0ubuntu2 nvidia-driver-440440.64-0ubuntu2 nvidia-kernel-common-440 440.64-0ubuntu2 nvidia-kernel-source-440 440.64-0ubuntu2 nvidia-prime 0.8.14 nvidia-settings 440.64-0ubuntu1 nvidia-utils-440 440.64-0ubuntu2 xserver-xorg-video-nvidia-440440.64-0ubuntu2 $ lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-3ubuntu1) ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 Date: Mon Mar 30 15:49:12 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes InstallationDate: Installed on 2020-03-03 (26 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) MachineType: Gigabyte Technology Co., Ltd. Z170X-UD5 TH ProcEnviron: LANGUAGE=en_GB:en TERM=linux PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_7176ku@/vmlinuz-5.4.0-18-generic root=ZFS=rpool/ROOT/ubuntu_7176ku ro quiet splash intel_iommu=on vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F22g dmi.board.asset.tag: Default string dmi.board.name: Z170X-UD5 TH-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version:
[Touch-packages] [Bug 1869759] Re: Opengl or vulkan or mesa bug that causes textures to glitch when mipmapping or trilinear/bilinear filtering is enabled
** Tags added: amdgpu ** Summary changed: - Opengl or vulkan or mesa bug that causes textures to glitch when mipmapping or trilinear/bilinear filtering is enabled + [amdgpu] Opengl or vulkan or mesa bug that causes textures to glitch when mipmapping or trilinear/bilinear filtering is enabled ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Also affects: xserver-xorg-video-amdgpu (Ubuntu) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1869759 Title: [amdgpu] Opengl or vulkan or mesa bug that causes textures to glitch when mipmapping or trilinear/bilinear filtering is enabled Status in linux package in Ubuntu: New Status in mesa package in Ubuntu: New Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: Textures are glitched (almost like they are cut up and repeated) when mipmapping or trilinear/bilinear filtering is enabled. Workaround is to disable both. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Mar 30 12:03:39 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c4) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Picasso [1025:134f] InstallationDate: Installed on 2019-11-04 (147 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Acer Aspire A515-43 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=a44eb2b0-d036-44b7-9c90-d0a427ecd008 ro quiet splash resume=/dev/nvme0n1p5 resume_offset=15261696 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Grumpy_PK dmi.board.vendor: PK dmi.board.version: V1.06 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.06 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.06:bd09/26/2019:svnAcer:pnAspireA515-43:pvrV1.06:rvnPK:rnGrumpy_PK:rvrV1.06:cvnAcer:ct10:cvrV1.06: dmi.product.family: Aspire 5 dmi.product.name: Aspire A515-43 dmi.product.sku: dmi.product.version: V1.06 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869759/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869758] Re: Repetative problem, Random connectivity
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1869758 Title: Repetative problem, Random connectivity Status in Ubuntu: Incomplete Bug description: This is a reoccurring problem. I run debug and then go to report with attached files and afterwards the problem temporarily clears out. It reoccurs upon subsequent log in and restart of computer. It also clears sometimes upon restart of system. It is a bug true to it's nature and nagging reoccurrence. Please provide a solution or debug program to cure this ill bug. Thank You J. Chosta Current OS Linux 4.4.0 141 generic, build date 10 august 2018, x protocol version 11 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18 Uname: Linux 4.15.0-91-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Mar 30 11:41:14 2020 DistUpgraded: 2018-12-25 11:16:26,692 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV610 [Radeon HD 2400 PRO] [1002:94c3] (prog-if 00 [VGA controller]) Subsystem: Dell Radeon HD 2400 Pro [1028:0302] InstallationDate: Installed on 2016-08-03 (1335 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Dell Inc. Dell XPS420 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-91-generic root=UUID=e737e1ac-8869-44b7-a03f-477223f8 ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-12-25 (460 days ago) dmi.bios.date: 03/27/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0TP406 dmi.board.vendor: Dell Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd03/27/2008:svnDellInc.:pnDellXPS420:pvr:rvnDellInc.:rn0TP406:rvr:cvnDellInc.:ct7:cvr: dmi.product.name: Dell XPS420 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Tue Dec 25 08:33:58 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech Logitech USB Speaker KEYBOARD, id 8 inputLogitech USB-PS/2 Optical Mouse MOUSE, id 9 inputDell Dell USB Keyboard KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1869758/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869814] Re: ubuntu-docs build failure - possible solution
Hmm.. I saw in the buildlog from the successful build that it skipped the Chinese translation of a particular string. The reason proved to be a missing '<' character, i.e. the translated string contains an instance of '/em>' instead of ''. And that's the correct behavior; it should check the Mallard syntax and skip translations with invalid syntax. Anyway, I added the missing '<', and then ubuntu-docs built with the itstool version in focal. So the direct reason for the build failure is a syntactically incorrect translation. OTOH, translators make mistakes, and a bad translation *should not* make the whole package build to fail. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxml2 in Ubuntu. https://bugs.launchpad.net/bugs/1869814 Title: ubuntu-docs build failure - possible solution Status in itstool package in Ubuntu: New Status in libxml2 package in Ubuntu: New Status in ubuntu-docs package in Ubuntu: New Bug description: ubuntu-docs failed to build during the second Focal Fossa test rebuild: https://launchpad.net/ubuntu/+archive/test- rebuild-20200327-focal/+build/18982738 It was itstool which failed to generate the localized zh_CN pages. If dropping zh_CN from ubuntu-help/Makefile.am, ubuntu-docs builds. But excluding the Chinese pages is apparently not an acceptable solution. The itstool package in focal {build-,}depends on python3. I built itstool in a PPA with python2 instead, and in that PPA ubuntu-docs built fine without modifications: https://launchpad.net/~gunnarhj/+archive/ubuntu/ubuntu-docs/+packages So the root cause seems to lie neither in ubuntu-docs nor itstool. I would suspect that python3-libxml2 is buggy, but since itstool was built against python2 in eoan, it's hard to tell if it's a regression. Would building itstool against python2 be an acceptable workaround in focal? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/itstool/+bug/1869814/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869819] [NEW] System can't detect external headset in the codec of Conexant
Public bug reported: [Impact] In some hp's devices, there are two audio jacks(one headset and one headphone) in the audio interface which is using the codec of Conexant, and apparently it's not working, the system can't detect the headset in current codec. [Test Case] 1. Insert 3-ring headset into front audio port (headset icon) 2. Check System Setting->Sound->Output [Expected result] Can detect external headset [Actual result] Only shows internal speaker. External headset microphone was detected. Another front audio port (earphone icon) works fine. [Regression Potential] [Failure rate] 100% [Additional information] system-product-name: HP EliteDesk 800 G5 SFF CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e98] (rev 02) OS-version: 18.04 kernel-version: 4.15.0-1065-oem pulseaudio-version: 1:11.1-1ubuntu7.2 Upstream Bug: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272 ** Affects: oem-priority Importance: Critical Assignee: hugh chao (hugh712) Status: Confirmed ** Affects: oem-priority/bionic Importance: Undecided Status: New ** Package changed: pulseaudio (Ubuntu) => oem-priority ** Changed in: oem-priority Assignee: (unassigned) => hugh chao (hugh712) ** Also affects: oem-priority/bionic Importance: Undecided Status: New ** Changed in: oem-priority Status: New => Confirmed ** Changed in: oem-priority Importance: Undecided => Critical -- 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/1869819 Title: System can't detect external headset in the codec of Conexant Status in OEM Priority Project: Confirmed Status in OEM Priority Project bionic series: New Bug description: [Impact] In some hp's devices, there are two audio jacks(one headset and one headphone) in the audio interface which is using the codec of Conexant, and apparently it's not working, the system can't detect the headset in current codec. [Test Case] 1. Insert 3-ring headset into front audio port (headset icon) 2. Check System Setting->Sound->Output [Expected result] Can detect external headset [Actual result] Only shows internal speaker. External headset microphone was detected. Another front audio port (earphone icon) works fine. [Regression Potential] [Failure rate] 100% [Additional information] system-product-name: HP EliteDesk 800 G5 SFF CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e98] (rev 02) OS-version: 18.04 kernel-version: 4.15.0-1065-oem pulseaudio-version: 1:11.1-1ubuntu7.2 Upstream Bug: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1869819/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869814] Re: ubuntu-docs build failure - possible solution
@Boyuan: Do you have any thoughts on the above? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxml2 in Ubuntu. https://bugs.launchpad.net/bugs/1869814 Title: ubuntu-docs build failure - possible solution Status in itstool package in Ubuntu: New Status in libxml2 package in Ubuntu: New Status in ubuntu-docs package in Ubuntu: New Bug description: ubuntu-docs failed to build during the second Focal Fossa test rebuild: https://launchpad.net/ubuntu/+archive/test- rebuild-20200327-focal/+build/18982738 It was itstool which failed to generate the localized zh_CN pages. If dropping zh_CN from ubuntu-help/Makefile.am, ubuntu-docs builds. But excluding the Chinese pages is apparently not an acceptable solution. The itstool package in focal {build-,}depends on python3. I built itstool in a PPA with python2 instead, and in that PPA ubuntu-docs built fine without modifications: https://launchpad.net/~gunnarhj/+archive/ubuntu/ubuntu-docs/+packages So the root cause seems to lie neither in ubuntu-docs nor itstool. I would suspect that python3-libxml2 is buggy, but since itstool was built against python2 in eoan, it's hard to tell if it's a regression. Would building itstool against python2 be an acceptable workaround in focal? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/itstool/+bug/1869814/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869814] [NEW] ubuntu-docs build failure - possible solution
Public bug reported: ubuntu-docs failed to build during the second Focal Fossa test rebuild: https://launchpad.net/ubuntu/+archive/test- rebuild-20200327-focal/+build/18982738 It was itstool which failed to generate the localized zh_CN pages. If dropping zh_CN from ubuntu-help/Makefile.am, ubuntu-docs builds. But excluding the Chinese pages is apparently not an acceptable solution. The itstool package in focal {build-,}depends on python3. I built itstool in a PPA with python2 instead, and in that PPA ubuntu-docs built fine without modifications: https://launchpad.net/~gunnarhj/+archive/ubuntu/ubuntu-docs/+packages So the root cause seems to lie neither in ubuntu-docs nor itstool. I would suspect that python3-libxml2 is buggy, but since itstool was built against python2 in eoan, it's hard to tell if it's a regression. Would building itstool against python2 be an acceptable workaround in focal? ** Affects: itstool (Ubuntu) Importance: Undecided Status: New ** Affects: libxml2 (Ubuntu) Importance: Undecided Status: New ** Affects: ubuntu-docs (Ubuntu) Importance: Undecided Status: New ** Also affects: itstool (Ubuntu) Importance: Undecided Status: New ** Also affects: libxml2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxml2 in Ubuntu. https://bugs.launchpad.net/bugs/1869814 Title: ubuntu-docs build failure - possible solution Status in itstool package in Ubuntu: New Status in libxml2 package in Ubuntu: New Status in ubuntu-docs package in Ubuntu: New Bug description: ubuntu-docs failed to build during the second Focal Fossa test rebuild: https://launchpad.net/ubuntu/+archive/test- rebuild-20200327-focal/+build/18982738 It was itstool which failed to generate the localized zh_CN pages. If dropping zh_CN from ubuntu-help/Makefile.am, ubuntu-docs builds. But excluding the Chinese pages is apparently not an acceptable solution. The itstool package in focal {build-,}depends on python3. I built itstool in a PPA with python2 instead, and in that PPA ubuntu-docs built fine without modifications: https://launchpad.net/~gunnarhj/+archive/ubuntu/ubuntu-docs/+packages So the root cause seems to lie neither in ubuntu-docs nor itstool. I would suspect that python3-libxml2 is buggy, but since itstool was built against python2 in eoan, it's hard to tell if it's a regression. Would building itstool against python2 be an acceptable workaround in focal? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/itstool/+bug/1869814/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1864253] Re: Pulseaudio sink/source selection, weird behaviour.
** No longer affects: pulseaudio -- 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/1864253 Title: Pulseaudio sink/source selection, weird behaviour. Status in pulseaudio package in Ubuntu: Invalid Bug description: I have a Laptop connected to an USB-C dock. By default the docks analog audio output is chosen as the default pulse audio sink. I want that the analog output of the Laptop is the default, hence I configured this in /etc/pulse/default.py This does not work and journalctl informs me that the device chosen by me (alsa_output.pci-_00_1f.3.analog-stereo) does not exist, see attached output from journalctl. I have followed Workaround 1 here https://wiki.debian.org/BluetoothUser/a2dp to prevent pulseaudio getting started in gdm to prevent device capture. This does not work, the device does still not exist. Restarting pulseaudio sometimes, but not always sets the configured default sink. Furthermore plugging in the headphones in the Laptops analog input switches audio to the dock. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.4 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: findus 3055 F pulseaudio /dev/snd/controlC1: findus 3055 F pulseaudio /dev/snd/controlC0: findus 3055 F pulseaudio /dev/snd/pcmC0D0p: findus 3055 F...m pulseaudio CurrentDesktop: i3 Date: Fri Feb 21 22:19:04 2020 InstallationDate: Installed on 2019-06-13 (253 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2IET80W (1.58 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N3S0UB00 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2IET80W(1.58):bd11/26/2019:svnLENOVO:pn20N3S0UB00:pvrThinkPadT490:rvnLENOVO:rn20N3S0UB00:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T490 dmi.product.name: 20N3S0UB00 dmi.product.sku: LENOVO_MT_20N3_BU_Think_FM_ThinkPad T490 dmi.product.version: ThinkPad T490 dmi.sys.vendor: LENOVO modified.conffile..etc.pulse.daemon.conf: [modified] modified.conffile..etc.pulse.default.pa: [modified] modified.conffile..etc.pulse.system.pa: [modified] mtime.conffile..etc.pulse.daemon.conf: 2020-02-21T20:38:20.081439 mtime.conffile..etc.pulse.default.pa: 2020-02-21T19:27:57.386938 mtime.conffile..etc.pulse.system.pa: 2020-02-21T15:23:09.470494 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1864253/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1867390] Re: Update libarchive to 3.4.2
** Changed in: libarchive (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libarchive in Ubuntu. https://bugs.launchpad.net/bugs/1867390 Title: Update libarchive to 3.4.2 Status in libarchive package in Ubuntu: Triaged Status in libarchive package in Debian: New Bug description: Please update libarchive to 3.4.2, also fixes LP: #1814109. The bug and security fixes outweighs the new features added in 3.4.1 and 3.4.2. https://github.com/libarchive/libarchive/releases Libarchive 3.4.2 is a feature and security release. New features: support for atomic file extraction (bsdtar -x --safe-writes) (#1289) support for mbed TLS (PolarSSL) (#1301) Important bugfixes: security fixes in RAR5 reader (#1280 #1326) compression buffer fix in XAR writer (#1317) fix uname and gname longer than 32 characters in PAX writer (#1319) fix segfault when archiving hard links in ISO9660 and XAR writers (#1325) fix support for extracting 7z archive entries with Delta filter (fixes LP: #1814109) (#987) Libarchive 3.4.1 is a feature and security release. New features: Unicode filename support for reading lha/lzh archives New pax write option "xattrhdr" Important bugfixes: security fixes in wide string processing (#1276 #1298) security fixes in RAR5 reader (#1212 #1217 #1296) security fixes and optimizations to write filter logic (#351) security fix related to use of readlink(2) (1dae5a5) sparse file handling fixes (#1218 #1260) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libarchive/+bug/1867390/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1865504] Re: hwclock reports incorrect status in audit message
** Changed in: util-linux (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1865504 Title: hwclock reports incorrect status in audit message Status in util-linux package in Ubuntu: Fix Released Status in util-linux source package in Bionic: Fix Released Status in util-linux source package in Eoan: Fix Released Status in util-linux package in Debian: New Bug description: [Impact] hwclock reports incorrect status in audit message: - hwclock calls audit_log_user_message(3) to create an audit entry. - audit_log_user_message(3) result 1 is "success" and 0 is "failed". - hwclock use standard EXIT_{SUCCESS,FAILURE} macros with reverse status. - Thus reports its status incorrectly in audit message. It is a requirement for Common Criteria Certification that hwclock reports correct status in audit message. This has been fixed upstream in https://github.com/karelzak/util- linux/commit/189edf1fe501ea39b35911337eab1740888fae7a [Test Steps] Steps to test: 1. Install auditd 2. Run following testcase, # hwclock 2020-03-02 15:03:03.280351+ # hwclock --set --date "1/1/2000 00:00:00" # echo $? 0 # hwclock 2000-01-01 00:00:05.413924+ # hwclock --utc --systohc # echo $? 0 # hwclock 2020-03-02 15:07:00.264331+ Following audit messages from /var/log/audit/audit.log, Note that last field in each audit record produced when hardware clock was modified has, "res=failed". Although, testcase shows no* failure occurred. type=USYS_CONFIG msg=audit(1583161562.884:105): pid=2084 uid=0 auid=1000 ses=1 msg='op=change-system-time exe="/sbin/hwclock" hostname=bionic-fips addr=? terminal=pts/0 res=failed' type=USYS_CONFIG msg=audit(1583161614.497:106): pid=2103 uid=0 auid=1000 ses=1 msg='op=change-system-time exe="/sbin/hwclock" hostname=bionic-fips addr=? terminal=pts/0 res=failed' [Regression Potential] Changes limited to the result value passed to audit_log_user_message(3), so the audit messages will change the 'res=' field (to correct result.) There should not be any regression to fix the status given to auditd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1865504/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869716] Re: Removing libpango1.0-0 broke Minecraft Launcher
Tested with libpango-1.0-0_1.44.7-2ubuntu2_amd64.deb and libpango-1.0-0_1.44.7-2ubuntu2_i386.deb from #8 above. Worked for Minecraft.deb on Xubuntu -- 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/1869716 Title: Removing libpango1.0-0 broke Minecraft Launcher Status in pango1.0 package in Ubuntu: Fix Committed Bug description: I just updated my machine, and when I did libpango1.0-0 was removed. This removed minecraft-launcher - the (very) popular launcher for Minecraft Java edition. I have reported this upstream, in case they can update their package https://bugs.mojang.com/browse/MCL-13512 I am filing this bug so we can track it internally. I personally think this shouldn't have been done this late in the cycle, but there may well have been good reasons for it. As a result of the change though, it's now not possible to install Minecraft on Ubuntu 20.04. $ sudo apt install ./Minecraft\(1\).deb Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting 'minecraft-launcher' instead of './Minecraft(1).deb' Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. minecraft-launcher : Depends: libpango1.0-0 (>= 1.14.0) but it is not installable E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1869716/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1867535] Re: [FFe] LXC 4.0.0 LTS
The release announcement finally got pushed out here: https://discuss.linuxcontainers.org/t/lxc-4-0-lts-has-been-released/7182 The main new features are: - cgroups: Full cgroup2 support - cgroups: Freezer support in CGroup2 - cgroups: eBPF device controller support in CGroup2 - config: Add lxc.autodev.tmpfs.size configuration key - config: Add lxc.selinux.context.keyring key - config: Add lxc.keyring.session - file utils: Add fopen_cached() and fdopen_cached - api: Add new init_pidfd() member - memory utils: Add new cleanup api - lxc-usernsexec: Make it easy to map own uid - seccomp: Add s390 support - syscalls: Improve manual syscall implementations - network: Improved network device creation and removal - network: Allow moving wireless devices Only one symbol was added compared to 3.2.1: - init_pidfd (to retrieve the pidfd of the init process) And a total of 5 since 3.0.0: - mount (to inject mounts into a running container) - umount (to remove mounts from a running container) - seccomp_notify_fd (to support syscall interception) - init_pidfd (to retrieve the pidfd of the init process) - lxc_has_api_extension (to check whether particular feature/options are present) No rebuilds are needed and all reverse dependencies of liblxc are know to work properly. LXC upstream has auto-generated PPAs that are used on all of our CI systems (running 18.04) so we have been testing those upgrades continuously and don't expect any issue. No configuration keys were removed in this release (unlike 3.0) and so no config updates are required for our users. Existing 3.0 users can upgrade to 4.0, running containers will keep working and the default configurations used by 4.0 are even backward compatible to 3.0, so a downgrade is even an option if needed. As mentioned above, the main benefit of getting 4.0 in Ubuntu is to get the 5 years of upstream security updates. Even though LXC is in universe, it's still quite widely used and actively maintained in Ubuntu by us. It's also worth noting that we've had all LXD users running the LXD snap run LXC 4.0 for the past week with only one regression found in the attach logic. This has since been fixed and will be cherry-picked in the package that's to be uploaded to Ubuntu. We realize we're getting late in the cycle, ideally we'd like this uploaded as soon as possible so it can get built, go through autopkgtest and land in the archive as soon as the freeze lifts (if it's covered by the freeze at all, not sure). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1867535 Title: [FFe] LXC 4.0.0 LTS Status in lxc package in Ubuntu: New Bug description: LXC 4.0 LTS will be tagged in the next week or so. LXC in Ubuntu is currently in universe as its main user is a snap nowadays (LXD) and builds directly from the upstream versions. We haven't written the changelog yet, but one thing worth noting is that it is 100% backward compatible, we do not break API and don't need to rebuild any of the rdepend for it. The main reason to want it in 20.04 LTS is because LXC 4.0 is itself an LTS with a matching 5 years of support. It also adds support for cgroupv2 which we expect to become more and more needed in the coming months/years. It'd be great if the release team could make a decision based on this already, if not, I will update the bug with the changelog and diff once we do have the release out. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1867535/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869716] Re: Removing libpango1.0-0 broke Minecraft Launcher
Tested with latest packages in proposed Ubuntu MATE and able to install and use balena-etcher-electron. -- 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/1869716 Title: Removing libpango1.0-0 broke Minecraft Launcher Status in pango1.0 package in Ubuntu: Fix Committed Bug description: I just updated my machine, and when I did libpango1.0-0 was removed. This removed minecraft-launcher - the (very) popular launcher for Minecraft Java edition. I have reported this upstream, in case they can update their package https://bugs.mojang.com/browse/MCL-13512 I am filing this bug so we can track it internally. I personally think this shouldn't have been done this late in the cycle, but there may well have been good reasons for it. As a result of the change though, it's now not possible to install Minecraft on Ubuntu 20.04. $ sudo apt install ./Minecraft\(1\).deb Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting 'minecraft-launcher' instead of './Minecraft(1).deb' Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. minecraft-launcher : Depends: libpango1.0-0 (>= 1.14.0) but it is not installable E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1869716/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1865278] Re: Update to tracker 2.3.2 in Focal
** Changed in: tracker (Debian) Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1865278 Title: Update to tracker 2.3.2 in Focal Status in tracker package in Ubuntu: Fix Released Status in tracker package in Debian: Fix Released Bug description: 2.3.2 is a small bug-fix release. https://gitlab.gnome.org/GNOME/tracker/-/blob/tracker-2.3/NEWS NEW in 2.3.2 - 2020-02-18 = * Location info for photos is now inserted into the DB. It didn't work before as we failed to process SPARQL "blank nodes" correctly. * Fix for oversensitive FTS5 index corruption detection Translations: ms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1865278/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 144270] Re: chrony, time-daemon and ntp-server
** Changed in: ntp (Debian) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/144270 Title: chrony, time-daemon and ntp-server Status in ntp package in Ubuntu: Invalid Status in ntp package in Debian: Fix Released Bug description: Binary package hint: ntp Package ntp provides "ntp-server" and package chrony provides "time- daemon". That seems inconsistent and it would be desirable that either chrony provide "ntp-server" or ntp provide "time-daemon" or both. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/144270/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869716] Re: Removing libpango1.0-0 broke Minecraft Launcher
Tested with the latest packages in proposed and it's fixed, I can now install and play Minecraft. Thank you! <3 -- 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/1869716 Title: Removing libpango1.0-0 broke Minecraft Launcher Status in pango1.0 package in Ubuntu: Fix Committed Bug description: I just updated my machine, and when I did libpango1.0-0 was removed. This removed minecraft-launcher - the (very) popular launcher for Minecraft Java edition. I have reported this upstream, in case they can update their package https://bugs.mojang.com/browse/MCL-13512 I am filing this bug so we can track it internally. I personally think this shouldn't have been done this late in the cycle, but there may well have been good reasons for it. As a result of the change though, it's now not possible to install Minecraft on Ubuntu 20.04. $ sudo apt install ./Minecraft\(1\).deb Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting 'minecraft-launcher' instead of './Minecraft(1).deb' Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. minecraft-launcher : Depends: libpango1.0-0 (>= 1.14.0) but it is not installable E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1869716/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 227744] Re: dapper upgrade to hardy: openldap silently refuses to start when unable to open SSL certificates - main: TLS init def ctx failed: -64 - openldap user not in ssl-cert
** Changed in: openldap2.3 (Debian) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/227744 Title: dapper upgrade to hardy: openldap silently refuses to start when unable to open SSL certificates - main: TLS init def ctx failed: -64 - openldap user not in ssl-cert group Status in openldap package in Ubuntu: Won't Fix Status in openldap2.3 package in Ubuntu: Invalid Status in openldap source package in Hardy: Invalid Status in openldap2.3 source package in Hardy: Won't Fix Status in openldap2.3 package in Debian: Fix Released Bug description: We ran a slapd on Dapper for a long time, and it relied on an SSL cert that we made root-owned 0400 for reasons of our own internal security. Apache happily opens these certs as root and passes the file descriptor along for after it drops privilege to the www-data user. The default install of slapd on Hardy silently refuses to start when we point it at these certificates. On Dapper, we ran slapd as root, and things worked reasonably well. The Hardy upgrade reconfigured slapd to run as the "openldap" user, which was unable to read the certificates we have. The problem with this is that there was no indication in the logs or the init script output that this was the reason it would not start. Forcing us to pore through the copious output of the debug mode is a little unreasonable for such a straightforward error condition. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/227744/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869789] Re: Crossover fails to install due to missing lib32nss-mdns
** Changed in: apt (Ubuntu) Assignee: (unassigned) => Steve Langasek (vorlon) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1869789 Title: Crossover fails to install due to missing lib32nss-mdns Status in apt package in Ubuntu: New Bug description: Crossover depends on lib32nss-mdns which does not appear to be available in 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1869789/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869803] Re: [HDA-Intel - HDA Intel PCH, recording] Recording problem, internal mic and headset mic not listed
Do not care about USB device, I bought a USB mic for lockdown and it works via USB. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1869803 Title: [HDA-Intel - HDA Intel PCH, recording] Recording problem, internal mic and headset mic not listed Status in alsa-driver package in Ubuntu: New Bug description: Hi, my dell laptop inspiron 15 5590 not working properly, internal mic is not listed in inputs and headset mic neither. I tested headset mic on other devices and it works fine. Also when I plug headset in in/out jack, ubuntu doesn't ask for connection type (headset, headset mic, mic) it use it only as simple headset. I tried some configuration in alsa and HDAJackRetask but none works. Same for kernels, 4.15.x, 5.0.x (oem), 5.3.x none works. I didn't test mics under windows because I can't for the moment. If you need details, I'll be glad to copy/paste your commands in terminal. Infos: Ubuntu 19.10 kernel: 5.3.0-29-generic alsa-base: 1.0.25+dfsg-0ubuntu5 Thanks! ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: nonot 2648 F pulseaudio /dev/snd/pcmC1D0c: nonot 2648 F...m pulseaudio /dev/snd/controlC0: nonot 2648 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Mar 30 23:34:18 2020 InstallationDate: Installed on 2020-01-07 (83 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_AlsaRecordingTestStderr: a r e c o r d : p c m _ r e a d : 2 1 4 9 : r e a d e r r o r : I n p u t / o u t p u t e r r o r Symptom_Card: USB PnP Audio Device(EEPROM) - USB PnP Audio Device(EEPROM) Symptom_Type: Only some of inputs are working Title: [HDA-Intel - HDA Intel PCH, recording] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 03P485 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd01/14/2020:svnDellInc.:pnInspiron5590:pvr:rvnDellInc.:rn03P485:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5590 dmi.product.sku: 0957 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-03-25T16:08:59.064986 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1869803/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869803] [NEW] [HDA-Intel - HDA Intel PCH, recording] Recording problem, internal mic and headset mic not listed
Public bug reported: Hi, my dell laptop inspiron 15 5590 not working properly, internal mic is not listed in inputs and headset mic neither. I tested headset mic on other devices and it works fine. Also when I plug headset in in/out jack, ubuntu doesn't ask for connection type (headset, headset mic, mic) it use it only as simple headset. I tried some configuration in alsa and HDAJackRetask but none works. Same for kernels, 4.15.x, 5.0.x (oem), 5.3.x none works. I didn't test mics under windows because I can't for the moment. If you need details, I'll be glad to copy/paste your commands in terminal. Infos: Ubuntu 19.10 kernel: 5.3.0-29-generic alsa-base: 1.0.25+dfsg-0ubuntu5 Thanks! ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: nonot 2648 F pulseaudio /dev/snd/pcmC1D0c: nonot 2648 F...m pulseaudio /dev/snd/controlC0: nonot 2648 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Mar 30 23:34:18 2020 InstallationDate: Installed on 2020-01-07 (83 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_AlsaRecordingTestStderr: a r e c o r d : p c m _ r e a d : 2 1 4 9 : r e a d e r r o r : I n p u t / o u t p u t e r r o r Symptom_Card: USB PnP Audio Device(EEPROM) - USB PnP Audio Device(EEPROM) Symptom_Type: Only some of inputs are working Title: [HDA-Intel - HDA Intel PCH, recording] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 03P485 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd01/14/2020:svnDellInc.:pnInspiron5590:pvr:rvnDellInc.:rn03P485:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5590 dmi.product.sku: 0957 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-03-25T16:08:59.064986 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug audio eoan mic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1869803 Title: [HDA-Intel - HDA Intel PCH, recording] Recording problem, internal mic and headset mic not listed Status in alsa-driver package in Ubuntu: New Bug description: Hi, my dell laptop inspiron 15 5590 not working properly, internal mic is not listed in inputs and headset mic neither. I tested headset mic on other devices and it works fine. Also when I plug headset in in/out jack, ubuntu doesn't ask for connection type (headset, headset mic, mic) it use it only as simple headset. I tried some configuration in alsa and HDAJackRetask but none works. Same for kernels, 4.15.x, 5.0.x (oem), 5.3.x none works. I didn't test mics under windows because I can't for the moment. If you need details, I'll be glad to copy/paste your commands in terminal. Infos: Ubuntu 19.10 kernel: 5.3.0-29-generic alsa-base: 1.0.25+dfsg-0ubuntu5 Thanks! ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: nonot 2648 F pulseaudio /dev/snd/pcmC1D0c: nonot 2648 F...m pulseaudio /dev/snd/controlC0: nonot 2648 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Mar 30 23:34:18 2020 InstallationDate: Installed on 2020-01-07 (83 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_AlsaRecordingTestStderr: a r e c o r d : p c m _ r e a d : 2 1 4 9 : r e a d e r r o r : I n p u t / o u t p u t e r r o r Symptom_Card: USB PnP Audio Device(EEPROM) - USB PnP Audio Device(EEPROM) Symptom_Type: Only some of inputs are working Title: [HDA-Intel - HDA Intel PCH, recording] Recording problem UpgradeStatus: No upgrade log present
[Touch-packages] [Bug 1863733] Re: Bubblewrap upstream-as-root test fails on libcap2 1:2.31-1 and later
** Changed in: bubblewrap (Debian) Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libcap2 in Ubuntu. https://bugs.launchpad.net/bugs/1863733 Title: Bubblewrap upstream-as-root test fails on libcap2 1:2.31-1 and later Status in bubblewrap package in Ubuntu: New Status in libcap2 package in Ubuntu: New Status in bubblewrap package in Debian: Fix Released Bug description: The bubblewrap upstream-as-root test started failing after libcap2 1:2.31-1 got synced from Debian. The same failure can be seen with 1:2.32-1. I have reproduced the issue locally on focal - when using the focal-proposed version, the aforementioned test fails, where with the release version (1:2.27-1) it passes. It seems to fail here already: bwrap --bind / / --tmpfs /tmp --as-pid-1 --cap-drop CAP_KILL --cap-drop CAP_FOWNER --unshare-pid capsh --print assert_not_file_has_content caps.test '^Current: =.*cap_kill' It looks like the requested caps did not get dropped, as the logs show that both cap_kill and cap_fowner are still there. This is only for the upstream-as-root test, i.e. executing tests/test-run.sh as root. This might be an issue with bubblewrap, but seeing that it all works fine with the release version, it all feels weird. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bubblewrap/+bug/1863733/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869716] Re: Removing libpango1.0-0 broke Minecraft Launcher
https://bugs.launchpad.net/ubuntu/+source/pango1.0/1.44.7-2ubuntu2 ** Changed in: pango1.0 (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1869716 Title: Removing libpango1.0-0 broke Minecraft Launcher Status in pango1.0 package in Ubuntu: Fix Committed Bug description: I just updated my machine, and when I did libpango1.0-0 was removed. This removed minecraft-launcher - the (very) popular launcher for Minecraft Java edition. I have reported this upstream, in case they can update their package https://bugs.mojang.com/browse/MCL-13512 I am filing this bug so we can track it internally. I personally think this shouldn't have been done this late in the cycle, but there may well have been good reasons for it. As a result of the change though, it's now not possible to install Minecraft on Ubuntu 20.04. $ sudo apt install ./Minecraft\(1\).deb Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting 'minecraft-launcher' instead of './Minecraft(1).deb' Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. minecraft-launcher : Depends: libpango1.0-0 (>= 1.14.0) but it is not installable E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1869716/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1862667] Re: systemd autopkgtest 'boot-and-services' fails with linux-kvm
marking as affecting linux-kvm, as I'm not sure the lack of CONFIG_DM_MULTIPATH was intentional or not. ** Also affects: linux-kvm (Ubuntu) Importance: Undecided Status: New ** Tags added: sts-sponsor-volunteer -- 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/1862667 Title: systemd autopkgtest 'boot-and-services' fails with linux-kvm Status in linux-kvm package in Ubuntu: New Status in systemd package in Ubuntu: In Progress Status in linux-kvm source package in Eoan: New Status in systemd source package in Eoan: In Progress Status in linux-kvm source package in Focal: New Status in systemd source package in Focal: In Progress Bug description: [impact] systemd autopkgtest 'boot-and-services' fails when running with linux- kvm kernel, because that kernel does not set CONFIG_DM_MULTIPATH, so the test detects failed services. [test case] check the autopkgtest results, e.g.: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/amd64/s/systemd/20200210_144351_da247@/log.gz test_no_failed (__main__.ServicesTest) No failed units ... journal for failed service multipathd.service --- -- Logs begin at Mon 2020-02-10 03:26:38 UTC, end at Mon 2020-02-10 13:56:23 UTC. -- Feb 10 13:56:07 autopkgtest systemd[1]: Starting Device-Mapper Multipath Device Controller... Feb 10 13:56:07 autopkgtest modprobe[194]: modprobe: WARNING: Module scsi_dh_alua not found in directory /lib/modules/5.3.0-1010-kvm Feb 10 13:56:07 autopkgtest modprobe[194]: modprobe: WARNING: Module scsi_dh_emc not found in directory /lib/modules/5.3.0-1010-kvm Feb 10 13:56:07 autopkgtest modprobe[194]: modprobe: WARNING: Module scsi_dh_rdac not found in directory /lib/modules/5.3.0-1010-kvm Feb 10 13:56:07 autopkgtest modprobe[194]: modprobe: WARNING: Module dm-multipath not found in directory /lib/modules/5.3.0-1010-kvm Feb 10 13:56:07 autopkgtest multipathd[195]: start up Feb 10 13:56:07 autopkgtest multipathd[195]: read /etc/multipath.conf Feb 10 13:56:07 autopkgtest multipathd[195]: DM multipath kernel driver not loaded Feb 10 13:56:07 autopkgtest systemd[1]: multipathd.service: Main process exited, code=exited, status=1/FAILURE Feb 10 13:56:07 autopkgtest systemd[1]: multipathd.service: Failed with result 'exit-code'. Feb 10 13:56:07 autopkgtest systemd[1]: Failed to start Device-Mapper Multipath Device Controller. FAIL == FAIL: test_no_failed (__main__.ServicesTest) No failed units -- Traceback (most recent call last): File "/tmp/autopkgtest.WQ5GyY/build.RUe/src/debian/tests/boot-and-services", line 68, in test_no_failed self.assertEqual(failed, []) AssertionError: Lists differ: ['multipathd.service loaded failed failed [38 chars]ler'] != [] First list contains 1 additional elements. First extra element 0: 'multipathd.service loaded failed failed Device-Mapper Multipath Device Controller' + [] - ['multipathd.service loaded failed failed Device-Mapper Multipath Device ' - 'Controller'] [regression potential] TBD [scope] This is needed at least in Eoan, and probably Focal. This doesn't fail on Bionic or Xenial, but that seems to be because the multipath-utils package (which provides multipathd.service) is not installed during the test for those releases. [other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1862667/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869765] Re: Problems dealing with Java Script promise in HTML
Thanks for pointing this out. I was able to get this working by building from the dev-wip branch and installing that locally. -- 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/1869765 Title: Problems dealing with Java Script promise in HTML Status in qtwebkit-opensource-src package in Ubuntu: New Bug description: We're using the GlobalProtect UI Client in Ubuntu. This uses libqt5webkit5 to provide allow login with an external SAML single sign on provider. This works with several identity providers (okta, jumpcloud). However, it does not work with Azure. Issue ID 9415 - https://docs.paloaltonetworks.com/globalprotect/5-1 /globalprotect-app-release-notes/gp-app-release-information/known- issues-related-to-gp-app The problem seems to be that the Azure AD HTML response has a java promise in it and this seems to be problematic in versions of libqt5webkit5 >= 5.212.0. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtwebkit-opensource-src/+bug/1869765/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1856871] Re: i/o error if next unused loop device is queried
marking invalid for systemd, as i think we all agree it's not an issue caused by systemd, but please feel free to re-mark it for systemd if i'm incorrect ** Changed in: systemd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1856871 Title: i/o error if next unused loop device is queried Status in linux package in Ubuntu: Incomplete Status in parted package in Ubuntu: New Status in snapd package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in udev package in Ubuntu: New Bug description: This is reproducible in Bionic and late. Here's an example running 'focal': $ lsb_release -cs focal $ uname -r 5.3.0-24-generic The error is: blk_update_request: I/O error, dev loop2, sector 0 and on more recent kernel: kernel: [18135.185709] blk_update_request: I/O error, dev loop18, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 How to trigger it: $ sosreport -o block or more precisely the cmd causing the situation inside the block plugin: $ parted -s $(losetup -f) unit s print https://github.com/sosreport/sos/blob/master/sos/plugins/block.py#L52 but if I run it on the next next unused loop device, in this case /dev/loop3 (which is also unused), no errors. While I agree that sosreport shouldn't query unused loop devices, there is definitely something going on with the next unused loop device. What is differentiate loop2 and loop3 and any other unused ones ? 3 things so far I have noticed: * loop2 is the next unused loop device (losetup -f) * A reboot is needed (if some loop modification (snap install, mount loop, ...) has been made at runtime * I have also noticed that loop2 (or whatever the next unused one is) have some stat as oppose to other unused loop devices. The stat exist already right after the system boot for the next unused loop device. /sys/block/loop2/stat :: 2 0 10 0 1 0 0 0 0 0 0 2 = number of read I/Os processed 10 = number of sectors read 1 = number of write I/Os processed Explanation of each column: https://www.kernel.org/doc/html/latest/block/stat.html while /dev/loop3 doesn't /sys/block/loop3/stat :: 0 0 0 0 0 0 0 0 0 0 0 Which tells me that something during the boot process most likely acquired (on purpose or not) the next unused loop and possibly didn't released it well enough. If loop2 is generating errors, and I install a snap, the snap squashfs will take loop2, making loop3 the next unused loop device. If I query loop3 with 'parted' right after, no errors. If I reboot, and query loop3 again, then no I'll have an error. To triggers the errors it need to be after a reboot and it only impact the first unused loop device available (losetup -f). This was tested with focal/systemd whic his very close to latest upstream code. This has been test with latest v5.5 mainline kernel as well. For now, I don't think it's a kernel problem, I'm more thinking of a userspace misbehaviour dealing with loop device (or block device) at boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856871/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869116] Re: smartctl-validate is borked in a recent release
When running previous (18.xx LTS and 16.xx LTS) options in MAAS for commissioning it skipped the scripts because it said the drives do not support RAID. Perhaps that ties in with Alberto's comment. I'm not too familiar with SMART but I'm not sure why the drives don't support it, I thought they did. Or is that it is because it is behind a hardware raid controller that SMART cannot be exposed/ran to test on? Maybe that answer is less relevant to this discussion, but I wanted to report back that running the other releases as requested passed, but due to SKIPPING the scripts. Thanks and hope that helps, -cees -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1869116 Title: smartctl-validate is borked in a recent release Status in lxd: Unknown Status in MAAS: Triaged Status in util-linux package in Ubuntu: New Bug description: Bug (maybe?) details first, diatribe second. Bug Summary: multi-hdd / raid with multiple drives / multiple devices or something along those lines cannot be commissioned anymore: 2.4.x worked fine, 2.7.0 does not. Here is the script output of smartctl-validate: - # /dev/sda (Model: PERC 6/i, Serial: 6842b2b0740e9900260e66c9220df4ac) Unable to run 'smartctl-validate': Storage device 'PERC 6/i' with serial '6842b2b0740e9900260e66c9220df4ac' not found! This indicates the storage device has been removed or the OS is unable to find it due to a hardware failure. Please re-commission this node to re-discover the storage devices, or delete this device manually. Given parameters: {'storage': {'argument_format': '{path }', 'type': 'storage', 'value': {'id_path': '/dev/disk/by-id/wwn-0x6842b2b0740e9900260e66c9220df4ac', 'model': 'PERC 6/i', 'name': 'sda', 'physical_blockdevice_id': 33, 'serial': '6842b2b0740e9900260e66c9220df4ac' } } } Discovered storage devices: [ {'NAME': 'sda', 'MODEL': 'PERC_6/i', 'SERIAL': '6842b2b0740e9900260e66c9220df4ac' }, {'NAME': 'sdb', 'MODEL': 'PERC_6/i', 'SERIAL': '6842b2b0740e9900260e66f924ecece0' }, {'NAME': 'sr0', 'MODEL': 'TEAC_DVD-ROM_DV-28SW', 'SERIAL': '10092013112645' } ] Discovered interfaces: {'xx: xx: xx: xx: xx: xx': 'eno1' } - - # /dev/sdb (Model: PERC 6/i, Serial: 6842b2b0740e9900260e66f924ecece0) Unable to run 'smartctl-validate': Storage device 'PERC 6/i' with serial '6842b2b0740e9900260e66f924ecece0' not found! This indicates the storage device has been removed or the OS is unable to find it due to a hardware failure. Please re-commission this node to re-discover the storage devices, or delete this device manually. Given parameters: {'storage': {'argument_format': '{path }', 'type': 'storage', 'value': {'id_path': '/dev/disk/by-id/wwn-0x6842b2b0740e9900260e66f924ecece0', 'model': 'PERC 6/i', 'name': 'sdb', 'physical_blockdevice_id': 34, 'serial': '6842b2b0740e9900260e66f924ecece0' } } } Discovered storage devices: [ {'NAME': 'sda', 'MODEL': 'PERC_6/i', 'SERIAL': '6842b2b0740e9900260e66c9220df4ac' }, {'NAME': 'sdb', 'MODEL': 'PERC_6/i', 'SERIAL': '6842b2b0740e9900260e66f924ecece0' }, {'NAME': 'sr0', 'MODEL': 'TEAC_DVD-ROM_DV-28SW', 'SERIAL': '10092013112645' } ] Discovered interfaces: {'xx: xx: xx: xx: xx: xx': 'eno1' } - You can see that it says the storage cannot be found and immediately lists it as a discovered device. It does it for both tests (one for each drive), and for both servers Bug Details: I had maas 2.4.x for the longest time over my journey (see below journey) and have never had any problems re-commissioning (or deleting and re-discovering over boot PXE) 2 of my servers (r610, r710). r610 has an iPERC 6, four 10K X00GB drives configured in a RAID10, 1 virtual disk. r710 has an iPERC 6, 6x 2TB drives, configured in a RAID10, 2 virtual disks So commission after commission trying to get through my journey, 0 problems. After I finally get everything figured out on the juju, network/vlan, quad-nic end, I go to re-commission and I cannot. smartctl-validate fails on both, over and over again. I even destroyed and re-created the raid/VDs, still not. After spending so much time on it I remembered that it was the first time I had tried to re-commission these two servers since doing an upgrade from 2.4.x->2.7 in an effort to use the updated KVM integration to add a couple more guests. Once I got all everything figured out I went to re-commission everything and boom. [Upgrade path notes] In full disclosure, in case this matters. I was on apt install of 2.4.x and using snap for 2.7, except it didn't work. So I read on how to do apt 2.7 and did that and did not uninstall snap 2.7 yet. I wanted to migrate from apt to snap but do not know how to without
[Touch-packages] [Bug 1869716] Re: Removing libpango1.0-0 broke Minecraft Launcher
** Changed in: pango1.0 (Ubuntu) Status: Fix Committed => In Progress -- 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/1869716 Title: Removing libpango1.0-0 broke Minecraft Launcher Status in pango1.0 package in Ubuntu: In Progress Bug description: I just updated my machine, and when I did libpango1.0-0 was removed. This removed minecraft-launcher - the (very) popular launcher for Minecraft Java edition. I have reported this upstream, in case they can update their package https://bugs.mojang.com/browse/MCL-13512 I am filing this bug so we can track it internally. I personally think this shouldn't have been done this late in the cycle, but there may well have been good reasons for it. As a result of the change though, it's now not possible to install Minecraft on Ubuntu 20.04. $ sudo apt install ./Minecraft\(1\).deb Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting 'minecraft-launcher' instead of './Minecraft(1).deb' Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. minecraft-launcher : Depends: libpango1.0-0 (>= 1.14.0) but it is not installable E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1869716/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869716] Re: Removing libpango1.0-0 broke Minecraft Launcher
THanks, I guess the provide needs to be version, new revision on his way... -- 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/1869716 Title: Removing libpango1.0-0 broke Minecraft Launcher Status in pango1.0 package in Ubuntu: Fix Committed Bug description: I just updated my machine, and when I did libpango1.0-0 was removed. This removed minecraft-launcher - the (very) popular launcher for Minecraft Java edition. I have reported this upstream, in case they can update their package https://bugs.mojang.com/browse/MCL-13512 I am filing this bug so we can track it internally. I personally think this shouldn't have been done this late in the cycle, but there may well have been good reasons for it. As a result of the change though, it's now not possible to install Minecraft on Ubuntu 20.04. $ sudo apt install ./Minecraft\(1\).deb Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting 'minecraft-launcher' instead of './Minecraft(1).deb' Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. minecraft-launcher : Depends: libpango1.0-0 (>= 1.14.0) but it is not installable E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1869716/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869759] Re: Opengl or vulkan or mesa bug that causes textures to glitch when mipmapping or trilinear/bilinear filtering is enabled
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1869759 Title: Opengl or vulkan or mesa bug that causes textures to glitch when mipmapping or trilinear/bilinear filtering is enabled Status in xorg package in Ubuntu: New Bug description: Textures are glitched (almost like they are cut up and repeated) when mipmapping or trilinear/bilinear filtering is enabled. Workaround is to disable both. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Mar 30 12:03:39 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c4) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Picasso [1025:134f] InstallationDate: Installed on 2019-11-04 (147 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Acer Aspire A515-43 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=a44eb2b0-d036-44b7-9c90-d0a427ecd008 ro quiet splash resume=/dev/nvme0n1p5 resume_offset=15261696 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Grumpy_PK dmi.board.vendor: PK dmi.board.version: V1.06 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.06 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.06:bd09/26/2019:svnAcer:pnAspireA515-43:pvrV1.06:rvnPK:rnGrumpy_PK:rvrV1.06:cvnAcer:ct10:cvrV1.06: dmi.product.family: Aspire 5 dmi.product.name: Aspire A515-43 dmi.product.sku: dmi.product.version: V1.06 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1869759/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869759] [NEW] Opengl or vulkan or mesa bug that causes textures to glitch when mipmapping or trilinear/bilinear filtering is enabled
You have been subscribed to a public bug: Textures are glitched (almost like they are cut up and repeated) when mipmapping or trilinear/bilinear filtering is enabled. Workaround is to disable both. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Mar 30 12:03:39 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c4) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Picasso [1025:134f] InstallationDate: Installed on 2019-11-04 (147 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Acer Aspire A515-43 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=a44eb2b0-d036-44b7-9c90-d0a427ecd008 ro quiet splash resume=/dev/nvme0n1p5 resume_offset=15261696 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Grumpy_PK dmi.board.vendor: PK dmi.board.version: V1.06 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.06 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.06:bd09/26/2019:svnAcer:pnAspireA515-43:pvrV1.06:rvnPK:rnGrumpy_PK:rvrV1.06:cvnAcer:ct10:cvrV1.06: dmi.product.family: Aspire 5 dmi.product.name: Aspire A515-43 dmi.product.sku: dmi.product.version: V1.06 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption focal reproducible single-occurrence ubuntu wayland-session -- Opengl or vulkan or mesa bug that causes textures to glitch when mipmapping or trilinear/bilinear filtering is enabled https://bugs.launchpad.net/bugs/1869759 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg 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 1869716] Re: Removing libpango1.0-0 broke Minecraft Launcher
I have proposed enabled. $ apt-cache policy libpango-1.0-0 libpango-1.0-0: Installed: 1.44.7-2ubuntu1 Candidate: 1.44.7-2ubuntu1 Version table: *** 1.44.7-2ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1.44.7-2 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages -- 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/1869716 Title: Removing libpango1.0-0 broke Minecraft Launcher Status in pango1.0 package in Ubuntu: Fix Committed Bug description: I just updated my machine, and when I did libpango1.0-0 was removed. This removed minecraft-launcher - the (very) popular launcher for Minecraft Java edition. I have reported this upstream, in case they can update their package https://bugs.mojang.com/browse/MCL-13512 I am filing this bug so we can track it internally. I personally think this shouldn't have been done this late in the cycle, but there may well have been good reasons for it. As a result of the change though, it's now not possible to install Minecraft on Ubuntu 20.04. $ sudo apt install ./Minecraft\(1\).deb Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting 'minecraft-launcher' instead of './Minecraft(1).deb' Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. minecraft-launcher : Depends: libpango1.0-0 (>= 1.14.0) but it is not installable E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1869716/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869716] Re: Removing libpango1.0-0 broke Minecraft Launcher
The fixed version is still in proposed, it didn't migrate yet... -- 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/1869716 Title: Removing libpango1.0-0 broke Minecraft Launcher Status in pango1.0 package in Ubuntu: Fix Committed Bug description: I just updated my machine, and when I did libpango1.0-0 was removed. This removed minecraft-launcher - the (very) popular launcher for Minecraft Java edition. I have reported this upstream, in case they can update their package https://bugs.mojang.com/browse/MCL-13512 I am filing this bug so we can track it internally. I personally think this shouldn't have been done this late in the cycle, but there may well have been good reasons for it. As a result of the change though, it's now not possible to install Minecraft on Ubuntu 20.04. $ sudo apt install ./Minecraft\(1\).deb Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting 'minecraft-launcher' instead of './Minecraft(1).deb' Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. minecraft-launcher : Depends: libpango1.0-0 (>= 1.14.0) but it is not installable E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1869716/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869716] Re: Removing libpango1.0-0 broke Minecraft Launcher
This doesn't seem properly fixed... dpkg: dependency problems prevent configuration of minecraft-launcher: minecraft-launcher depends on libpango1.0-0 (>= 1.14.0); however: Package libpango1.0-0 is not installed. Version of libpango1.0-0 on system, provided by libpango-1.0-0:amd64, is . -- 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/1869716 Title: Removing libpango1.0-0 broke Minecraft Launcher Status in pango1.0 package in Ubuntu: Fix Committed Bug description: I just updated my machine, and when I did libpango1.0-0 was removed. This removed minecraft-launcher - the (very) popular launcher for Minecraft Java edition. I have reported this upstream, in case they can update their package https://bugs.mojang.com/browse/MCL-13512 I am filing this bug so we can track it internally. I personally think this shouldn't have been done this late in the cycle, but there may well have been good reasons for it. As a result of the change though, it's now not possible to install Minecraft on Ubuntu 20.04. $ sudo apt install ./Minecraft\(1\).deb Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting 'minecraft-launcher' instead of './Minecraft(1).deb' Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. minecraft-launcher : Depends: libpango1.0-0 (>= 1.14.0) but it is not installable E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1869716/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863001] Re: Incorrect LAYOUT is set when choosing Lithuanian in dpkg-reconfigure keyboard-configuration and Ubiquity
** Changed in: console-setup (Debian) Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1863001 Title: Incorrect LAYOUT is set when choosing Lithuanian in dpkg-reconfigure keyboard-configuration and Ubiquity Status in console-setup package in Ubuntu: Fix Released Status in console-setup package in Debian: Fix Released Bug description: If user chooses Lithuanian keyboard layout during installation (Ubiquity) or dpkg-reconfigure keyboard-configuration then incorrect layout is set in /etc/default/keyboard : XKBLAYOUT="lt,lt" XKBVARIANT=",us" This configuration is not intuitive, because people think, that sometimes Lithuanian keyboard works (when lt1 is selected in GNOME shell panel) and sometimes doesn't work (when lt2 is selected). So, majority of Lithuanian users are force to removed second lt(us) layout and add English (US) altgr-intl layout. So, correct /etc/default/keyboard should be: XKBMODEL="pc105" XKBLAYOUT="lt,us" XKBVARIANT=",altgr-intl" XKBOPTIONS="grp_led:scroll" BACKSPACE="guess" I'm attaching a patch to debian/keyboard-configuration.config file which fixes this issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1863001/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869107] Re: Error when installing scanner deb on 20.04
Issue is resolved now and scanner works if you would like to close. Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1869107 Title: Error when installing scanner deb on 20.04 Status in apt package in Ubuntu: Fix Committed Bug description: Trying to install .deb for Brother ADS-2200 scanner. Worked previously in 18.04, 18.10, 19.04 and 19.10. If I double click on the .deb, Gnome Software attempts to install and fails with the following error: Failed to install file: not supported If I use apt to install the file manually I get the following error: sudo apt install ./brscanads2200ads2700w-0.1.15-1.amd64.deb Reading package lists... Error! E: Problem parsing Provides line of brscanads2200ads2700w:amd64=0.1.15-1 E: Error occurred while processing brscanads2200ads2700w (NewVersion2) E: Problem with MergeList /home/caleb/Downloads/brscanads2200ads2700w-0.1.15-1.amd64.deb E: The package lists or status file could not be parsed or opened. I installed using dpkg without any errors. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1869107/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869789] [NEW] Crossover fails to install due to missing lib32nss-mdns
Public bug reported: Crossover depends on lib32nss-mdns which does not appear to be available in 20.04. ** Affects: apt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1869789 Title: Crossover fails to install due to missing lib32nss-mdns Status in apt package in Ubuntu: New Bug description: Crossover depends on lib32nss-mdns which does not appear to be available in 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1869789/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869787] Re: libpango1.0-0 has been removed from 20.04 and is not installable
*** This bug is a duplicate of bug 1869716 *** https://bugs.launchpad.net/bugs/1869716 ** This bug has been marked a duplicate of bug 1869716 Removing libpango1.0-0 broke Minecraft Launcher -- 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/1869787 Title: libpango1.0-0 has been removed from 20.04 and is not installable Status in pango1.0 package in Ubuntu: New Bug description: Upon update on 30 March 2020 libpango1.0-0 was removed from the system. Package libpango1.0-0 is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source However the following packages replace it: libpangox-1.0-0 However applications such as balena-etcher require libpango1.0-0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1869787/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869787] Re: libpango1.0-0 has been removed from 20.04 and is not installable
*** This bug is a duplicate of bug 1869716 *** https://bugs.launchpad.net/bugs/1869716 https://packages.ubuntu.com/bionic/libpango1.0-0 ** Package changed: ubuntu => pango1.0 (Ubuntu) -- 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/1869787 Title: libpango1.0-0 has been removed from 20.04 and is not installable Status in pango1.0 package in Ubuntu: New Bug description: Upon update on 30 March 2020 libpango1.0-0 was removed from the system. Package libpango1.0-0 is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source However the following packages replace it: libpangox-1.0-0 However applications such as balena-etcher require libpango1.0-0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1869787/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869716] Re: Removing libpango1.0-0 broke Minecraft Launcher
** Changed in: pango1.0 (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1869716 Title: Removing libpango1.0-0 broke Minecraft Launcher Status in pango1.0 package in Ubuntu: Fix Committed Bug description: I just updated my machine, and when I did libpango1.0-0 was removed. This removed minecraft-launcher - the (very) popular launcher for Minecraft Java edition. I have reported this upstream, in case they can update their package https://bugs.mojang.com/browse/MCL-13512 I am filing this bug so we can track it internally. I personally think this shouldn't have been done this late in the cycle, but there may well have been good reasons for it. As a result of the change though, it's now not possible to install Minecraft on Ubuntu 20.04. $ sudo apt install ./Minecraft\(1\).deb Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting 'minecraft-launcher' instead of './Minecraft(1).deb' Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. minecraft-launcher : Depends: libpango1.0-0 (>= 1.14.0) but it is not installable E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1869716/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869716] Re: Removing libpango1.0-0 broke Minecraft Launcher
Note: In Bionic - I haven't checked exhaustively - libpango1.0-0 is a transitional package, and libpango-1.0-0 is the actual package. Perhaps Focal Fossa should continue to ship the transitional package to keep Minecraft folk from encountering this. Not sure what policy applies. -- 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/1869716 Title: Removing libpango1.0-0 broke Minecraft Launcher Status in pango1.0 package in Ubuntu: Fix Committed Bug description: I just updated my machine, and when I did libpango1.0-0 was removed. This removed minecraft-launcher - the (very) popular launcher for Minecraft Java edition. I have reported this upstream, in case they can update their package https://bugs.mojang.com/browse/MCL-13512 I am filing this bug so we can track it internally. I personally think this shouldn't have been done this late in the cycle, but there may well have been good reasons for it. As a result of the change though, it's now not possible to install Minecraft on Ubuntu 20.04. $ sudo apt install ./Minecraft\(1\).deb Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting 'minecraft-launcher' instead of './Minecraft(1).deb' Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. minecraft-launcher : Depends: libpango1.0-0 (>= 1.14.0) but it is not installable E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1869716/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869716] Re: Removing libpango1.0-0 broke Minecraft Launcher
And RikMills notes: https://launchpad.net/ubuntu/+source/pango1.0/1.44.7-2ubuntu1 -- 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/1869716 Title: Removing libpango1.0-0 broke Minecraft Launcher Status in pango1.0 package in Ubuntu: Fix Committed Bug description: I just updated my machine, and when I did libpango1.0-0 was removed. This removed minecraft-launcher - the (very) popular launcher for Minecraft Java edition. I have reported this upstream, in case they can update their package https://bugs.mojang.com/browse/MCL-13512 I am filing this bug so we can track it internally. I personally think this shouldn't have been done this late in the cycle, but there may well have been good reasons for it. As a result of the change though, it's now not possible to install Minecraft on Ubuntu 20.04. $ sudo apt install ./Minecraft\(1\).deb Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting 'minecraft-launcher' instead of './Minecraft(1).deb' Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. minecraft-launcher : Depends: libpango1.0-0 (>= 1.14.0) but it is not installable E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1869716/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1222527] Re: Rename 'Software & Updates' label
** Project changed: ayatana-design => ubuntu ** No longer affects: ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1222527 Title: Rename 'Software & Updates' label Status in software-properties package in Ubuntu: Confirmed Bug description: Ubuntu 13.10 Language: English US UX Problem: When searching in the Dash for the system software updater - a pretty common task - always two entries are presented to the user with nearly the same name. There is the update-manager labeled ' Software Updater' and there is software-properties labeled 'Software & Updates', result: 'Software Updater' and 'Software & Updates'. Both names start with a capital S and a capital U → they should be easier to distinguish. Suggested solution: Relabel the less common GenericName of the .desktop file to something else. As the software-properties are less important IMHO for the daily use of an average user, I purpose to relabel it to 'Software Settings'. Not my favorite name, but visual much better to distinguish then the current name and it would share the naming pattern of having 'Settings' at the end of a program that allows the user to configure something. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: software-properties-gtk 0.92.25 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Uname: Linux 3.11.0-4-generic x86_64 ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 Date: Sun Sep 8 20:50:21 2013 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2013-08-27 (11 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130827) InterpreterPath: /usr/bin/python3.3 MarkForUpload: True PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1222527/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869787] [NEW] libpango1.0-0 has been removed from 20.04 and is not installable
You have been subscribed to a public bug: Upon update on 30 March 2020 libpango1.0-0 was removed from the system. Package libpango1.0-0 is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source However the following packages replace it: libpangox-1.0-0 However applications such as balena-etcher require libpango1.0-0 ** Affects: pango1.0 (Ubuntu) Importance: Undecided Status: New -- libpango1.0-0 has been removed from 20.04 and is not installable https://bugs.launchpad.net/bugs/1869787 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pango1.0 in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1733321] Re: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18
** Changed in: network-manager (Ubuntu Eoan) Assignee: Dariusz Gadomski (dgadomski) => (unassigned) ** Changed in: network-manager (Ubuntu Focal) Assignee: Dariusz Gadomski (dgadomski) => (unassigned) -- 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/1733321 Title: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18 Status in network-manager package in Ubuntu: New Status in network-manager source package in Artful: Won't Fix Status in network-manager source package in Disco: Won't Fix Status in network-manager source package in Eoan: New Status in network-manager source package in Focal: New Bug description: [Impact] The killswitches-no-urfkill autopkgtest fails sometimes because nmcli reports the old state when it's called right after rfkill block/unblock. Adding a sleep before calling nmcli fixes the issue. ppc64el ADT log from failed testcase: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-artful/artful/ppc64el/n/network- manager/20171120_100719_28642@/log.gz Testcase output: - autopkgtest [10:04:48]: test killswitches-no-urfkill: [--- make -C /lib/modules/4.13.0-17-generic/build KBUILD_SRC=/lib/modules/4.13.0-17-generic/build M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic' AR /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o CC [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o Building modules, stage 2. MODPOST 1 modules CC /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o LD [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic' ERROR: NM could not track device state. autopkgtest [10:05:20]: test killswitches-no-urfkill: ---] autopkgtest [10:05:20]: test killswitches-no-urfkill: - - - - - - - - - - results - - - - - - - - - - killswitches-no-urfkill FAIL non-zero exit status 1 - Package versions [artful/ppc64el]: network-manager 1.8.4-1ubuntu3 linux-meta 4.13.0.17.18 [Test Case] 2.1. Download network-manager package source code $ apt-get source network-manager 2.2. Run killswitches-no-urfkill testcase $ cd network-manager-1.8.4 $ sudo ./debian/tests/killswitches-no-urfkill [Regression Potential] No regression potential. The fix touches only the testcase shipped with the source package and it doesn't change the binary package. The sleep time added is very small, so no possibility of causing testcase timeout. [Other Info] On ppc64el architecture, it was observed that a fix for systemd is also needed (see bug 1734908) for the testcase to be successful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1733321/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1733321] Re: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18
Sure Dan, I'm looking into it. -- 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/1733321 Title: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18 Status in network-manager package in Ubuntu: New Status in network-manager source package in Artful: Won't Fix Status in network-manager source package in Disco: Won't Fix Status in network-manager source package in Eoan: New Status in network-manager source package in Focal: New Bug description: [Impact] The killswitches-no-urfkill autopkgtest fails sometimes because nmcli reports the old state when it's called right after rfkill block/unblock. Adding a sleep before calling nmcli fixes the issue. ppc64el ADT log from failed testcase: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-artful/artful/ppc64el/n/network- manager/20171120_100719_28642@/log.gz Testcase output: - autopkgtest [10:04:48]: test killswitches-no-urfkill: [--- make -C /lib/modules/4.13.0-17-generic/build KBUILD_SRC=/lib/modules/4.13.0-17-generic/build M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic' AR /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o CC [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o Building modules, stage 2. MODPOST 1 modules CC /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o LD [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic' ERROR: NM could not track device state. autopkgtest [10:05:20]: test killswitches-no-urfkill: ---] autopkgtest [10:05:20]: test killswitches-no-urfkill: - - - - - - - - - - results - - - - - - - - - - killswitches-no-urfkill FAIL non-zero exit status 1 - Package versions [artful/ppc64el]: network-manager 1.8.4-1ubuntu3 linux-meta 4.13.0.17.18 [Test Case] 2.1. Download network-manager package source code $ apt-get source network-manager 2.2. Run killswitches-no-urfkill testcase $ cd network-manager-1.8.4 $ sudo ./debian/tests/killswitches-no-urfkill [Regression Potential] No regression potential. The fix touches only the testcase shipped with the source package and it doesn't change the binary package. The sleep time added is very small, so no possibility of causing testcase timeout. [Other Info] On ppc64el architecture, it was observed that a fix for systemd is also needed (see bug 1734908) for the testcase to be successful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1733321/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1850964] Re: Always explain why packages are held back in logs even without debugging enabled
** Changed in: unattended-upgrades (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1850964 Title: Always explain why packages are held back in logs even without debugging enabled Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades package in Debian: Fix Released Bug description: [Impact] * Unattended-upgrades' log does not contain information about why held packages are kept back unless debugging is enabled. Users should be explained why packages are kept back to let them easily resolve the issues keeping the packages from being upgraded. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1850964/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1868915] Re: [focal] nm-online -s --timeout=10 timeout every time
NetworkManager isn't installed in the base MAAS Focal image. Are you using the default image from images.maas.io? What cloud-init user-data are you sending to the install? Have you modified the preseed file at all? ** Changed in: maas Status: New => Incomplete -- 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/1868915 Title: [focal] nm-online -s --timeout=10 timeout every time Status in MAAS: Incomplete Status in OEM Priority Project: New Status in network-manager package in Ubuntu: New Bug description: Also created bug on upstream : https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/398 This issue will cause "NetworkManager-wait-online.service: Failed with result 'exit-code'." And cloud-init.service is counting on this service for network status. So this issue will finally cause MaaS deploying failed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu1 [modified: lib/systemd/system/NetworkManager-wait-online.service] ProcVersionSignature: Ubuntu 5.4.0-1002.4-oem 5.4.8 Uname: Linux 5.4.0-1002-oem x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 Date: Wed Mar 25 12:43:13 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200316-60+fossa-staging+X09 IfupdownConfig: source /etc/network/interfaces.d/*.cfg InstallationDate: Installed on 2020-03-25 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200316-08:40 IpRoute: default via 192.168.101.1 dev eno1 proto static metric 100 10.101.46.0/24 via 192.168.101.1 dev eno1 proto static metric 200 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.101.0/24 dev eno1 proto kernel scope link src 192.168.101.85 metric 100 NetDevice.bonding_masters: Error: command ['udevadm', 'info', '--query=all', '--path', '/sys/class/net/bonding_masters'] failed with exit code 1: Unknown device "/sys/class/net/bonding_masters": No such device X: INTERFACE_MAC=Error: command ['cat', '/sys/class/net/bonding_masters/address'] failed with exit code 1: cat: /sys/class/net/bonding_masters/address: Not a directory SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE FILENAME netplan-eno1 10838d80-caeb-349e-ba73-08ed16d4d666 ethernet 158577 廿廿年三月廿五日 (週三) 十二時39分37秒 yes 0 no /org/freedesktop/NetworkManager/Settings/1 yes eno1activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- /run/NetworkManager/system-connections/netplan-eno1.nmconnection nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected starting full enabled disabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1868915/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1866210] Re: FTBFS against Ruby 2.7 on arm64
It seems this test is flaky on arm systems, after a re-try it built fine against Ruby 2.7. ** Changed in: vim (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1866210 Title: FTBFS against Ruby 2.7 on arm64 Status in vim package in Ubuntu: Invalid Bug description: During the Ruby 2.7 transition we got a FTBFS on arm64 [1]. [1] https://launchpadlibrarian.net/467387248/buildlog_ubuntu-focal- arm64.vim_2%3A8.1.2269-1ubuntu4_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1866210/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869774] Re: libpango1.0-0 package missing in focal
*** This bug is a duplicate of bug 1869716 *** https://bugs.launchpad.net/bugs/1869716 Hi, the developers are fixing this, please follow https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1869716. ** Package changed: ubuntu => pango1.0 (Ubuntu) ** This bug has been marked a duplicate of bug 1869716 Removing libpango1.0-0 broke Minecraft Launcher -- 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/1869774 Title: libpango1.0-0 package missing in focal Status in pango1.0 package in Ubuntu: New Bug description: 18.04 has libpango1.0-0 (potentially as a transitional package) 20.04 doesn't appear to have it. Perhaps libpango1.0-0 could be added to 20.04 as a transitional package? This issue presented itself when installing Minecraft.deb on 20.04 minecraft-launcher does function on 20.04, but is removed during an "apt --fix-broken install" On 18.04: gamecage@steam:~$ lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 gamecage@steam:~$ sudo dpkg -i Minecraft.deb Selecting previously unselected package minecraft-launcher. (Reading database ... 187796 files and directories currently installed.) Preparing to unpack Minecraft.deb ... Unpacking minecraft-launcher (2.1.13086) ... dpkg: dependency problems prevent configuration of minecraft-launcher: minecraft-launcher depends on gconf-service; however: Package gconf-service is not installed. minecraft-launcher depends on libgconf-2-4 (>= 2.31.1); however: Package libgconf-2-4 is not installed. minecraft-launcher depends on libpango1.0-0 (>= 1.14.0); however: Package libpango1.0-0 is not installed. minecraft-launcher depends on libcurl3 | libcurl4; however: Package libcurl3 is not installed. Package libcurl4 is not installed. dpkg: error processing package minecraft-launcher (--install): dependency problems - leaving unconfigured Processing triggers for gnome-menus (3.13.3-11ubuntu1) ... Processing triggers for desktop-file-utils (0.23-1ubuntu3.18.04.1) ... Processing triggers for mime-support (3.60ubuntu1) ... Processing triggers for hicolor-icon-theme (0.17-2) ... Errors were encountered while processing: minecraft-launcher gamecage@steam:~$ sudo apt --fix-broken install Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following additional packages will be installed: gconf-service gconf-service-backend gconf2-common libcurl3 libgconf-2-4 libpango1.0-0 libpangox-1.0-0 The following NEW packages will be installed: gconf-service gconf-service-backend gconf2-common libcurl3 libgconf-2-4 libpango1.0-0 libpangox-1.0-0 0 upgraded, 7 newly installed, 0 to remove and 236 not upgraded. 1 not fully installed or removed. Need to get 1,104 kB of archives. After this operation, 8,897 kB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 gconf2-common all 3.2.6-4ubuntu1 [700 kB] Get:2 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 libgconf-2-4 amd64 3.2.6-4ubuntu1 [84.8 kB] Get:3 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 gconf-service-backend amd64 3.2.6-4ubuntu1 [58.1 kB] Get:4 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 gconf-service amd64 3.2.6-4ubuntu1 [2,036 B] Get:5 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 libpangox-1.0-0 amd64 0.0.2-5 [41.7 kB] Get:6 http://us.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 libpango1.0-0 amd64 1.40.14-1ubuntu0.1 [3,344 B] Get:7 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 libcurl3 amd64 7.58.0-2ubuntu2 [214 kB] Fetched 1,104 kB in 1s (1,406 kB/s) Selecting previously unselected package gconf2-common. (Reading database ... 187866 files and directories currently installed.) Preparing to unpack .../0-gconf2-common_3.2.6-4ubuntu1_all.deb ... Unpacking gconf2-common (3.2.6-4ubuntu1) ... Selecting previously unselected package libgconf-2-4:amd64. Preparing to unpack .../1-libgconf-2-4_3.2.6-4ubuntu1_amd64.deb ... Unpacking libgconf-2-4:amd64 (3.2.6-4ubuntu1) ... Selecting previously unselected package gconf-service-backend. Preparing to unpack .../2-gconf-service-backend_3.2.6-4ubuntu1_amd64.deb ... Unpacking gconf-service-backend (3.2.6-4ubuntu1) ... Selecting previously unselected package gconf-service. Preparing to unpack .../3-gconf-service_3.2.6-4ubuntu1_amd64.deb ... Unpacking gconf-service (3.2.6-4ubuntu1) ... Selecting previously unselected package libpangox-1.0-0:amd64. Preparing to unpack .../4-libpangox-1.0-0_0.0.2-5_amd64.deb ... Unpacking libpangox-1.0-0:amd64 (0.0.2-5) ... Selecting previously unselected package
[Touch-packages] [Bug 1869774] [NEW] libpango1.0-0 package missing in focal
You have been subscribed to a public bug: 18.04 has libpango1.0-0 (potentially as a transitional package) 20.04 doesn't appear to have it. Perhaps libpango1.0-0 could be added to 20.04 as a transitional package? This issue presented itself when installing Minecraft.deb on 20.04 minecraft-launcher does function on 20.04, but is removed during an "apt --fix-broken install" On 18.04: gamecage@steam:~$ lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 gamecage@steam:~$ sudo dpkg -i Minecraft.deb Selecting previously unselected package minecraft-launcher. (Reading database ... 187796 files and directories currently installed.) Preparing to unpack Minecraft.deb ... Unpacking minecraft-launcher (2.1.13086) ... dpkg: dependency problems prevent configuration of minecraft-launcher: minecraft-launcher depends on gconf-service; however: Package gconf-service is not installed. minecraft-launcher depends on libgconf-2-4 (>= 2.31.1); however: Package libgconf-2-4 is not installed. minecraft-launcher depends on libpango1.0-0 (>= 1.14.0); however: Package libpango1.0-0 is not installed. minecraft-launcher depends on libcurl3 | libcurl4; however: Package libcurl3 is not installed. Package libcurl4 is not installed. dpkg: error processing package minecraft-launcher (--install): dependency problems - leaving unconfigured Processing triggers for gnome-menus (3.13.3-11ubuntu1) ... Processing triggers for desktop-file-utils (0.23-1ubuntu3.18.04.1) ... Processing triggers for mime-support (3.60ubuntu1) ... Processing triggers for hicolor-icon-theme (0.17-2) ... Errors were encountered while processing: minecraft-launcher gamecage@steam:~$ sudo apt --fix-broken install Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following additional packages will be installed: gconf-service gconf-service-backend gconf2-common libcurl3 libgconf-2-4 libpango1.0-0 libpangox-1.0-0 The following NEW packages will be installed: gconf-service gconf-service-backend gconf2-common libcurl3 libgconf-2-4 libpango1.0-0 libpangox-1.0-0 0 upgraded, 7 newly installed, 0 to remove and 236 not upgraded. 1 not fully installed or removed. Need to get 1,104 kB of archives. After this operation, 8,897 kB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 gconf2-common all 3.2.6-4ubuntu1 [700 kB] Get:2 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 libgconf-2-4 amd64 3.2.6-4ubuntu1 [84.8 kB] Get:3 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 gconf-service-backend amd64 3.2.6-4ubuntu1 [58.1 kB] Get:4 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 gconf-service amd64 3.2.6-4ubuntu1 [2,036 B] Get:5 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 libpangox-1.0-0 amd64 0.0.2-5 [41.7 kB] Get:6 http://us.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 libpango1.0-0 amd64 1.40.14-1ubuntu0.1 [3,344 B] Get:7 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 libcurl3 amd64 7.58.0-2ubuntu2 [214 kB] Fetched 1,104 kB in 1s (1,406 kB/s) Selecting previously unselected package gconf2-common. (Reading database ... 187866 files and directories currently installed.) Preparing to unpack .../0-gconf2-common_3.2.6-4ubuntu1_all.deb ... Unpacking gconf2-common (3.2.6-4ubuntu1) ... Selecting previously unselected package libgconf-2-4:amd64. Preparing to unpack .../1-libgconf-2-4_3.2.6-4ubuntu1_amd64.deb ... Unpacking libgconf-2-4:amd64 (3.2.6-4ubuntu1) ... Selecting previously unselected package gconf-service-backend. Preparing to unpack .../2-gconf-service-backend_3.2.6-4ubuntu1_amd64.deb ... Unpacking gconf-service-backend (3.2.6-4ubuntu1) ... Selecting previously unselected package gconf-service. Preparing to unpack .../3-gconf-service_3.2.6-4ubuntu1_amd64.deb ... Unpacking gconf-service (3.2.6-4ubuntu1) ... Selecting previously unselected package libpangox-1.0-0:amd64. Preparing to unpack .../4-libpangox-1.0-0_0.0.2-5_amd64.deb ... Unpacking libpangox-1.0-0:amd64 (0.0.2-5) ... Selecting previously unselected package libpango1.0-0:amd64. Preparing to unpack .../5-libpango1.0-0_1.40.14-1ubuntu0.1_amd64.deb ... Unpacking libpango1.0-0:amd64 (1.40.14-1ubuntu0.1) ... Selecting previously unselected package libcurl3:amd64. Preparing to unpack .../6-libcurl3_7.58.0-2ubuntu2_amd64.deb ... Unpacking libcurl3:amd64 (7.58.0-2ubuntu2) ... Setting up gconf2-common (3.2.6-4ubuntu1) ... Setting up libcurl3:amd64 (7.58.0-2ubuntu2) ... Setting up libgconf-2-4:amd64 (3.2.6-4ubuntu1) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... Setting up libpangox-1.0-0:amd64 (0.0.2-5) ... Setting up libpango1.0-0:amd64 (1.40.14-1ubuntu0.1) ... Setting up gconf-service-backend (3.2.6-4ubuntu1) ... Setting up gconf-service (3.2.6-4ubuntu1) ... Setting up minecraft-launcher (2.1.13086) ... Processing
[Touch-packages] [Bug 1733321] Re: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18
** Changed in: network-manager (Ubuntu Eoan) Assignee: (unassigned) => Dariusz Gadomski (dgadomski) ** Changed in: network-manager (Ubuntu Focal) Assignee: (unassigned) => Dariusz Gadomski (dgadomski) -- 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/1733321 Title: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18 Status in network-manager package in Ubuntu: New Status in network-manager source package in Artful: Won't Fix Status in network-manager source package in Disco: Won't Fix Status in network-manager source package in Eoan: New Status in network-manager source package in Focal: New Bug description: [Impact] The killswitches-no-urfkill autopkgtest fails sometimes because nmcli reports the old state when it's called right after rfkill block/unblock. Adding a sleep before calling nmcli fixes the issue. ppc64el ADT log from failed testcase: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-artful/artful/ppc64el/n/network- manager/20171120_100719_28642@/log.gz Testcase output: - autopkgtest [10:04:48]: test killswitches-no-urfkill: [--- make -C /lib/modules/4.13.0-17-generic/build KBUILD_SRC=/lib/modules/4.13.0-17-generic/build M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic' AR /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o CC [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o Building modules, stage 2. MODPOST 1 modules CC /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o LD [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic' ERROR: NM could not track device state. autopkgtest [10:05:20]: test killswitches-no-urfkill: ---] autopkgtest [10:05:20]: test killswitches-no-urfkill: - - - - - - - - - - results - - - - - - - - - - killswitches-no-urfkill FAIL non-zero exit status 1 - Package versions [artful/ppc64el]: network-manager 1.8.4-1ubuntu3 linux-meta 4.13.0.17.18 [Test Case] 2.1. Download network-manager package source code $ apt-get source network-manager 2.2. Run killswitches-no-urfkill testcase $ cd network-manager-1.8.4 $ sudo ./debian/tests/killswitches-no-urfkill [Regression Potential] No regression potential. The fix touches only the testcase shipped with the source package and it doesn't change the binary package. The sleep time added is very small, so no possibility of causing testcase timeout. [Other Info] On ppc64el architecture, it was observed that a fix for systemd is also needed (see bug 1734908) for the testcase to be successful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1733321/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6
** Tags added: sts-sponsor-volunteer -- 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/1688018 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6 Status in network-manager package in Ubuntu: Triaged Status in network-manager source package in Xenial: In Progress Status in network-manager source package in Yakkety: Won't Fix Bug description: This was initially opened as #1671606 then later duped to #1639776. Discussion in #1639776 indicate that we need new bug for this so I am opening one ... Please don't mark this as duplicate to #1639776 or other similar bug report. We already lost several months and we are again at beginning ... TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from DHCP instead of one defined by VPN (wrong). DNS resolver should query only DNS servers defined by VPN while connection is active. = Test steps / result: - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 (dnsmasq-base-2.75-1ubuntu0.16.04.2) - restated my laptop to ensure clean start - connected to VPN using openconnect / network-manager-openconnect-gnome Observed results -> DNS queries are forwarded only to DNS servers defined by LAN connection (this is wrong / connection not working at all) - "killall dnsmasq" - dnsmasq get automatically restarted by system Observed results -> most of the the queries are forwarded to DNS servers defined by VPN, but lot of queries get forwarded to DNS servers defined by LAN connection (this is still wrong / DNS leaks, attacker can hijack connection even if VPN is enabled) - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base stay same) - restated my laptop to ensure clean test - connected to same VPN using openconnect Observed results -> DNS queries are forwarded only to DNS servers defined by VPN connection. There are no leaks to LAN DNS server (this is correct behavior). = Paul Smith requested additional details in #1639776. Here are: * If you're using IPv4 vs. IPv6 -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi /vpn) * If you have checked or unchecked the "Use this connection only for resources on its network" -> unchecked on all nw definition * If you have this checked, try unchecking it and see if that makes a difference -> no change if I toggle this option. Behavior is same. * When you say "DNS lookups" please be clear about whether the hostnames being looked up are public (e.g., www.google.com or whatever), on your local LAN, or in the network accessed via the VPN. Does it make a difference which one you choose? -> No difference. * Are you using fully-qualified hostnames, or relying on the DNS domain search path? Does it make a difference if you do it differently? -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see difference when I try same using hostname + domain search. = I am using openconnect (cisco) and openvpn. Test result are by using openconnect but I saw same behaviour also while using openvpn. = Thanks Lukas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1688018/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1733321] Re: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18
** Tags added: sts-sponsor-volunteer -- 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/1733321 Title: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18 Status in network-manager package in Ubuntu: New Status in network-manager source package in Artful: Won't Fix Status in network-manager source package in Disco: Won't Fix Status in network-manager source package in Eoan: New Status in network-manager source package in Focal: New Bug description: [Impact] The killswitches-no-urfkill autopkgtest fails sometimes because nmcli reports the old state when it's called right after rfkill block/unblock. Adding a sleep before calling nmcli fixes the issue. ppc64el ADT log from failed testcase: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-artful/artful/ppc64el/n/network- manager/20171120_100719_28642@/log.gz Testcase output: - autopkgtest [10:04:48]: test killswitches-no-urfkill: [--- make -C /lib/modules/4.13.0-17-generic/build KBUILD_SRC=/lib/modules/4.13.0-17-generic/build M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic' AR /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o CC [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o Building modules, stage 2. MODPOST 1 modules CC /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o LD [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic' ERROR: NM could not track device state. autopkgtest [10:05:20]: test killswitches-no-urfkill: ---] autopkgtest [10:05:20]: test killswitches-no-urfkill: - - - - - - - - - - results - - - - - - - - - - killswitches-no-urfkill FAIL non-zero exit status 1 - Package versions [artful/ppc64el]: network-manager 1.8.4-1ubuntu3 linux-meta 4.13.0.17.18 [Test Case] 2.1. Download network-manager package source code $ apt-get source network-manager 2.2. Run killswitches-no-urfkill testcase $ cd network-manager-1.8.4 $ sudo ./debian/tests/killswitches-no-urfkill [Regression Potential] No regression potential. The fix touches only the testcase shipped with the source package and it doesn't change the binary package. The sleep time added is very small, so no possibility of causing testcase timeout. [Other Info] On ppc64el architecture, it was observed that a fix for systemd is also needed (see bug 1734908) for the testcase to be successful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1733321/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869721] Re: Apt error message gives incorrect syntax
Actually, I highlighted the message on the terminal, and pasted it in. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1869721 Title: Apt error message gives incorrect syntax Status in apt package in Ubuntu: Invalid Bug description: in Apt, when trying to reinstall or remove problem packages, if the process is unable to run, it says there are unmet dependencies. It then suggest a command to run to fix the problems. This would be the proper procedure for this, however the suggested command it provides is wrong. $ lsb_release -rd Description: Linux Mint 19.3 Tricia Release: 19.3 apt: Installed: 1.6.12 Candidate: 1.6.12 Version table: *** 1.6.12 500 500 http://mirrors.tripadvisor.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.6.6ubuntu0.1 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1.6.1 500 500 http://mirrors.tripadvisor.com/ubuntu bionic/main amd64 Packages Expected behavior: failed reinstall/uninstall command should show correct syntax for recommended command. In this case it should be "apt install --fix- broken", or "sudo apt install --fix-broken" (verified myself by running that command). Actual behavior: output from failed command ended with "E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution)." Running the command as it is shown there results in apt giving a syntax summary, rather than running the intended command. It was only by guessing at alternative formats on the command that got it to work. The format as shown in the incorrect example would have seemed more logical, as the older apt-get equivalent was "apt-get -f install", with the option switch before the command. It is up to the devs to decide whether the switch before or after the command is correct, just as long as the correct and functional form is shown in the error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1869721/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869765] Re: Problems dealing with Java Script promise in HTML
Hi! WebKit is a complicated codebase, so I don’t think I can help you here. You may get some luck if you report this on https://github.com/qtwebkit/qtwebkit/issues. Though, 5.212 series is based on a very old WebKit version, not sure if the author wants to fix any bugs there (he usually recommends trying qtwebkit-dev-wip branch but it's too unstable for packaging into Ubuntu). -- 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/1869765 Title: Problems dealing with Java Script promise in HTML Status in qtwebkit-opensource-src package in Ubuntu: New Bug description: We're using the GlobalProtect UI Client in Ubuntu. This uses libqt5webkit5 to provide allow login with an external SAML single sign on provider. This works with several identity providers (okta, jumpcloud). However, it does not work with Azure. Issue ID 9415 - https://docs.paloaltonetworks.com/globalprotect/5-1 /globalprotect-app-release-notes/gp-app-release-information/known- issues-related-to-gp-app The problem seems to be that the Azure AD HTML response has a java promise in it and this seems to be problematic in versions of libqt5webkit5 >= 5.212.0. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtwebkit-opensource-src/+bug/1869765/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869629] Re: please add /etc/mdns.allow to /etc/apparmor.d/abstractions/mdns
This problem is indeed somewhat pervasive, I also filed bug 1869632 on cups-browsed doing the same thing, for the same reason. I suspect more will pop up. I don't think libnss_mdns is too widely used, most people would use libnss_mdns_minimal. I only have to use libnss_mdns because my ISP is insane. If this bug were fixed by adding /etc/mdns.allow to /etc/apparmor.d/abstractions/mdns bug 1869632 would be fixed as well (I've verified this by patching it on my system.) Not sure why /etc/apparmor.d/abstractions/mdns contains /etc/nss_mdns.conf, though: libnss_mdns.so.2 doesn't refer to that file (it appears to be used in the NetBSD implementation?) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1869629 Title: please add /etc/mdns.allow to /etc/apparmor.d/abstractions/mdns Status in apparmor package in Ubuntu: New Status in chrony package in Ubuntu: Invalid Bug description: In focal users of mdns get denials in apparmor confined applications. An exampel can be found in the original bug below. It seems it is a common pattern, see https://github.com/lathiat/nss-mdns#etcmdnsallow Therefore I'm asking to add /etc/mdns.allow r, to the file /etc/apparmor.d/abstractions/mdns" by default. --- original bug --- Many repetitions of audit: type=1400 audit(1585517168.705:63): apparmor="DENIED" operation="open" profile="/usr/sbin/chronyd" name="/etc/mdns.allow" pid=1983815 comm="chronyd" requested_mask="r" denied_mask="r" fsuid=123 ouid=0 in log. I use libnss-mdns for .local name resolution, so /etc/nsswitch.conf contains hosts: files mdns [NOTFOUND=return] myhostname dns and /etc/mnds.allow contains the domains to resolve with mDNS (in may case, "local." and "local"; see /usr/share/doc/libnss- mdns/README.html.) Presumably cronyd calls a gethostbyX() somewhere, thus eventually trickling down through the name service switch and opening /etc/mdns.allow, which the AppArmor profile in the chrony package does not allow. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: chrony 3.5-6ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 Date: Sun Mar 29 15:02:39 2020 InstallationDate: Installed on 2020-03-26 (3 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200326) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: chrony UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1869629/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624320] Re: systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing entries
This bug, as described, is about 127.0.0.53 being configured in /etc/resolv.conf /alongside/ other entries. In recent releases this is no longer the behavior; instead, /etc/resolv.conf is entirely managed by systemd and points exclusively to the 127.0.0.53 local resolver, which in turn will use the upstream resolvers that have been configured via dhcp or via static netplan or network-manager config. Concerns about the behavior of the local resolver should be filed as separate issues. ** Changed in: systemd (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1624320 Title: systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing entries Status in systemd package in Ubuntu: Fix Released Status in Ubuntu RTM: New Bug description: systemd-resolved, or more precisely the hook script /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf, causes resolvconf to add 127.0.0.53 to the set of nameservers in /etc/resolv.conf alongside the other nameservers. That makes no sense because systemd-resolved sets up 127.0.0.53 as a proxy for those other nameservers. The effect is similar to bug 1624071 but for applications doing their own DNS lookups. It breaks any DNSSEC validation that systemd-resolved tries to do; applications will failover to the other nameservers, bypassing validation failures. And it makes failing queries take twice as long. /etc/resolv.conf should have only 127.0.0.53 when systemd-resolved is active. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624320/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869765] [NEW] Problems dealing with Java Script promise in HTML
Public bug reported: We're using the GlobalProtect UI Client in Ubuntu. This uses libqt5webkit5 to provide allow login with an external SAML single sign on provider. This works with several identity providers (okta, jumpcloud). However, it does not work with Azure. Issue ID 9415 - https://docs.paloaltonetworks.com/globalprotect/5-1 /globalprotect-app-release-notes/gp-app-release-information/known- issues-related-to-gp-app The problem seems to be that the Azure AD HTML response has a java promise in it and this seems to be problematic in versions of libqt5webkit5 >= 5.212.0. ** Affects: qtwebkit-opensource-src (Ubuntu) Importance: Undecided Status: New -- 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/1869765 Title: Problems dealing with Java Script promise in HTML Status in qtwebkit-opensource-src package in Ubuntu: New Bug description: We're using the GlobalProtect UI Client in Ubuntu. This uses libqt5webkit5 to provide allow login with an external SAML single sign on provider. This works with several identity providers (okta, jumpcloud). However, it does not work with Azure. Issue ID 9415 - https://docs.paloaltonetworks.com/globalprotect/5-1 /globalprotect-app-release-notes/gp-app-release-information/known- issues-related-to-gp-app The problem seems to be that the Azure AD HTML response has a java promise in it and this seems to be problematic in versions of libqt5webkit5 >= 5.212.0. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtwebkit-opensource-src/+bug/1869765/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1824088] Re: unattended upgrade ran one day after schedule
It's hardly and issue given that the script runs twice per day, which compensates for that by running it after 36 hours instead of 24. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1824088 Title: unattended upgrade ran one day after schedule Status in apt package in Ubuntu: New Bug description: I have noticed a strange behaviour in unattended upgrades. The host in question is scheduled to run upgrades on Mondays every second week. However, this week it ran upgrades on Tuesday instead (2019-04-09). This is the first time I’ve noticed this behaviour. I checked the logs in /var/log/apt/history.log* and I saw that worked as intended up until this week. Upgrades ran as expected on 2019-03-11 and 2019-03-25, which where both Mondays. The schedule was set with the line 'APT::Periodic::Unattended-Upgrade "14";' in the file /etc/apt/apt.conf.d/20auto-upgrades. Could it be daylight savings time that has caused skewing of the schedule? The server is located in Sweden and on 2019-03-31 we switched from CET to CEST. If the time diff is calculated with hours instead of calendar days passed, perhaps the missing hour on 2019-03-31 caused the scheduler to believe that on Monday 2019-03-08, two weeks (336 hours) had not yet passed. ADDITIONAL INFO Description:Ubuntu 16.04.6 LTS Release:16.04 apt: Installed: 1.2.29ubuntu0.1 Candidate: 1.2.31 Version table: 1.2.31 500 500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages *** 1.2.29ubuntu0.1 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 1.2.10ubuntu1 500 500 http://se.archive.ubuntu.com/ubuntu xenial/main amd64 Packages unattended-upgrades: Installed: 0.90ubuntu0.10 Candidate: 0.90ubuntu0.10 Version table: *** 0.90ubuntu0.10 500 500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main i386 Packages 100 /var/lib/dpkg/status 0.90 500 500 http://se.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 500 http://se.archive.ubuntu.com/ubuntu xenial/main i386 Packages ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apt 1.2.29ubuntu0.1 ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 Uname: Linux 4.4.0-142-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Wed Apr 10 09:06:49 2019 InstallationDate: Installed on 2017-12-28 (467 days ago) InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1824088/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869641] Re: Failed to launch ibus daemon in Xwayland + gnome-shell 3.36.0
This bug was fixed in the package ibus - 1.5.22-2ubuntu2 --- ibus (1.5.22-2ubuntu2) focal; urgency=medium * d/p/git-Use-WAYLAND_DISPLAY-on-Wayland-sessions.patch: - Cherry-picked upstream commit to prevent failure to launch ibus-daemon in Xwayland (LP: #1869641). -- Gunnar Hjalmarsson Mon, 30 Mar 2020 11:50:00 +0200 ** Changed in: ibus (Ubuntu) Status: Fix Committed => 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/1869641 Title: Failed to launch ibus daemon in Xwayland + gnome-shell 3.36.0 Status in ibus package in Ubuntu: Fix Released Bug description: Description: Ubuntu Focal Fossa (development branch) Release: 20.04 ibus 1.5.22-2ubuntu1 Steps to reproduce 1. Upgrade to GNOME 3.36.0. 2. Restart Ubuntu 20.04 daily with Wayland What did you expect to happen The ibus daemon is launched. What happened The ibus daemon is not running. I can confirm I have an exact same issue in https://gitlab.gnome.org/GNOME/gnome-shell/issues/2341 when login with wayland selected. After applying this: https://github.com/ibus/ibus/commit/8ce25208c3f4adfd290a032c6aa739d2b7580eb1 patch locally I can confirm it fixed my issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1869641/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1824088] Re: unattended upgrade ran one day after schedule
Yes we know that the script does not necessarily run once a day, that's not a surprise. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1824088 Title: unattended upgrade ran one day after schedule Status in apt package in Ubuntu: New Bug description: I have noticed a strange behaviour in unattended upgrades. The host in question is scheduled to run upgrades on Mondays every second week. However, this week it ran upgrades on Tuesday instead (2019-04-09). This is the first time I’ve noticed this behaviour. I checked the logs in /var/log/apt/history.log* and I saw that worked as intended up until this week. Upgrades ran as expected on 2019-03-11 and 2019-03-25, which where both Mondays. The schedule was set with the line 'APT::Periodic::Unattended-Upgrade "14";' in the file /etc/apt/apt.conf.d/20auto-upgrades. Could it be daylight savings time that has caused skewing of the schedule? The server is located in Sweden and on 2019-03-31 we switched from CET to CEST. If the time diff is calculated with hours instead of calendar days passed, perhaps the missing hour on 2019-03-31 caused the scheduler to believe that on Monday 2019-03-08, two weeks (336 hours) had not yet passed. ADDITIONAL INFO Description:Ubuntu 16.04.6 LTS Release:16.04 apt: Installed: 1.2.29ubuntu0.1 Candidate: 1.2.31 Version table: 1.2.31 500 500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages *** 1.2.29ubuntu0.1 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 1.2.10ubuntu1 500 500 http://se.archive.ubuntu.com/ubuntu xenial/main amd64 Packages unattended-upgrades: Installed: 0.90ubuntu0.10 Candidate: 0.90ubuntu0.10 Version table: *** 0.90ubuntu0.10 500 500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main i386 Packages 100 /var/lib/dpkg/status 0.90 500 500 http://se.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 500 http://se.archive.ubuntu.com/ubuntu xenial/main i386 Packages ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apt 1.2.29ubuntu0.1 ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 Uname: Linux 4.4.0-142-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Wed Apr 10 09:06:49 2019 InstallationDate: Installed on 2017-12-28 (467 days ago) InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1824088/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869721] Re: Apt error message gives incorrect syntax
Thanks for your bug report, but it seems you made a typo somewhere, as both `--fix-broken install` and `install --fix-broken` work - apt does not care about argument order. ** Changed in: apt (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1869721 Title: Apt error message gives incorrect syntax Status in apt package in Ubuntu: Invalid Bug description: in Apt, when trying to reinstall or remove problem packages, if the process is unable to run, it says there are unmet dependencies. It then suggest a command to run to fix the problems. This would be the proper procedure for this, however the suggested command it provides is wrong. $ lsb_release -rd Description: Linux Mint 19.3 Tricia Release: 19.3 apt: Installed: 1.6.12 Candidate: 1.6.12 Version table: *** 1.6.12 500 500 http://mirrors.tripadvisor.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.6.6ubuntu0.1 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1.6.1 500 500 http://mirrors.tripadvisor.com/ubuntu bionic/main amd64 Packages Expected behavior: failed reinstall/uninstall command should show correct syntax for recommended command. In this case it should be "apt install --fix- broken", or "sudo apt install --fix-broken" (verified myself by running that command). Actual behavior: output from failed command ended with "E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution)." Running the command as it is shown there results in apt giving a syntax summary, rather than running the intended command. It was only by guessing at alternative formats on the command that got it to work. The format as shown in the incorrect example would have seemed more logical, as the older apt-get equivalent was "apt-get -f install", with the option switch before the command. It is up to the devs to decide whether the switch before or after the command is correct, just as long as the correct and functional form is shown in the error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1869721/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869631] Re: Dingbats font missing after install
** Package changed: whoopsie (Ubuntu) => ubuntu-meta (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1869631 Title: Dingbats font missing after install Status in ubuntu-meta package in Ubuntu: New Bug description: Focal Fossa Ubuntu 20.04. When I scan through the fonts using Gnome Fonts, It shows the name "Dingbats" in the alphabetized list, however the font icon (or example) is missing. When I try to use the Dingbats font, say in a spreadsheet, it does nothing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1869631/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869758] [NEW] Repetative problem, Random connectivity
Public bug reported: This is a reoccurring problem. I run debug and then go to report with attached files and afterwards the problem temporarily clears out. It reoccurs upon subsequent log in and restart of computer. It also clears sometimes upon restart of system. It is a bug true to it's nature and nagging reoccurrence. Please provide a solution or debug program to cure this ill bug. Thank You J. Chosta Current OS Linux 4.4.0 141 generic, build date 10 august 2018, x protocol version 11 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18 Uname: Linux 4.15.0-91-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Mar 30 11:41:14 2020 DistUpgraded: 2018-12-25 11:16:26,692 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV610 [Radeon HD 2400 PRO] [1002:94c3] (prog-if 00 [VGA controller]) Subsystem: Dell Radeon HD 2400 Pro [1028:0302] InstallationDate: Installed on 2016-08-03 (1335 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Dell Inc. Dell XPS420 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-91-generic root=UUID=e737e1ac-8869-44b7-a03f-477223f8 ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-12-25 (460 days ago) dmi.bios.date: 03/27/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0TP406 dmi.board.vendor: Dell Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd03/27/2008:svnDellInc.:pnDellXPS420:pvr:rvnDellInc.:rn0TP406:rvr:cvnDellInc.:ct7:cvr: dmi.product.name: Dell XPS420 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Tue Dec 25 08:33:58 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech Logitech USB Speaker KEYBOARD, id 8 inputLogitech USB-PS/2 Optical Mouse MOUSE, id 9 inputDell Dell USB Keyboard KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1869758 Title: Repetative problem, Random connectivity Status in xorg package in Ubuntu: New Bug description: This is a reoccurring problem. I run debug and then go to report with attached files and afterwards the problem temporarily clears out. It reoccurs upon subsequent log in and restart of computer. It also clears sometimes upon restart of system. It is a bug true to it's nature and nagging reoccurrence. Please provide a solution or debug program to cure this ill bug. Thank You J. Chosta Current OS Linux 4.4.0 141 generic, build date 10 august 2018, x protocol version 11 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18 Uname: Linux 4.15.0-91-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Mar 30 11:41:14 2020 DistUpgraded: 2018-12-25 11:16:26,692 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV610 [Radeon HD 2400 PRO] [1002:94c3] (prog-if 00 [VGA controller]) Subsystem: Dell Radeon HD 2400 Pro [1028:0302] InstallationDate: Installed on 2016-08-03 (1335 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64
[Touch-packages] [Bug 1809014] Re: mpeg-2 detected as tga (Targa image)
Problem present in upstream (Debian) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to file in Ubuntu. https://bugs.launchpad.net/bugs/1809014 Title: mpeg-2 detected as tga (Targa image) Status in file package in Ubuntu: Confirmed Bug description: It appears that currently using either the file command or through the File::LibMagic interface that 1:5.34-2 on Cosmic (18.10) makes a MPEG-2 file be detected as Targa at a higher priority, thus taking precedence over being what it actually is. See the below lines as examples using clips from http://hubblesource.stsci.edu/sources/video/clips/ as examples: $ file -k /home/piratefinn/Downloads/hst_2.mpg /home/piratefinn/Downloads/hst_2.mpg: Targa image data - Map 63635 x 65536 x 1 +268 +60928 - 11-bit alpha - top - right - four way interleave MPEG sequence, v2, program multiplex (Lepton 3.x), scale 0-0, spot sensor temperature 0.00, unit celsius, color scheme 0, calibration: offset 0.00, slope 0.00\012- data Note that this appears to only affect MPEG-2 (and possibly higher) as MPEG-1 is detected corretly. $ file -k /home/piratefinn/Downloads/hst_1.mpg /home/piratefinn/Downloads/hst_1.mpg: MPEG sequence, v1, progressive Y'CbCr 4:2:0 video, 320x240, 4:3, 29.97 fps (Lepton 2.x), scale 1-2, spot sensor temperature 0.00, unit celsius, color scheme 0, show spot sensor, show scale bar, maximum point enabled, calibration: offset 586.228088, slope -411899156202779801569722368.00\012- data file -k /home/piratefinn/Downloads/hst_1.mpg This appears to not be an issue in 1:5.25 used in 16.04, however looking through the github it appears since then in possible 5.26 (or above) changes as seen in https://github.com/file/file/commit/aee048a020badb5f36008f6d11e7d5b32834bcb2 affected this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file/+bug/1809014/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1809014] Re: mpeg-2 detected as tga (Targa image)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: file (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to file in Ubuntu. https://bugs.launchpad.net/bugs/1809014 Title: mpeg-2 detected as tga (Targa image) Status in file package in Ubuntu: Confirmed Bug description: It appears that currently using either the file command or through the File::LibMagic interface that 1:5.34-2 on Cosmic (18.10) makes a MPEG-2 file be detected as Targa at a higher priority, thus taking precedence over being what it actually is. See the below lines as examples using clips from http://hubblesource.stsci.edu/sources/video/clips/ as examples: $ file -k /home/piratefinn/Downloads/hst_2.mpg /home/piratefinn/Downloads/hst_2.mpg: Targa image data - Map 63635 x 65536 x 1 +268 +60928 - 11-bit alpha - top - right - four way interleave MPEG sequence, v2, program multiplex (Lepton 3.x), scale 0-0, spot sensor temperature 0.00, unit celsius, color scheme 0, calibration: offset 0.00, slope 0.00\012- data Note that this appears to only affect MPEG-2 (and possibly higher) as MPEG-1 is detected corretly. $ file -k /home/piratefinn/Downloads/hst_1.mpg /home/piratefinn/Downloads/hst_1.mpg: MPEG sequence, v1, progressive Y'CbCr 4:2:0 video, 320x240, 4:3, 29.97 fps (Lepton 2.x), scale 1-2, spot sensor temperature 0.00, unit celsius, color scheme 0, show spot sensor, show scale bar, maximum point enabled, calibration: offset 586.228088, slope -411899156202779801569722368.00\012- data file -k /home/piratefinn/Downloads/hst_1.mpg This appears to not be an issue in 1:5.25 used in 16.04, however looking through the github it appears since then in possible 5.26 (or above) changes as seen in https://github.com/file/file/commit/aee048a020badb5f36008f6d11e7d5b32834bcb2 affected this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file/+bug/1809014/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1671606] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1
*** This bug is a duplicate of bug 1688018 *** https://bugs.launchpad.net/bugs/1688018 I'm on 19.10 with a L2TP IPsec connection over wifi using packages: network-manager-l2tp network-manager-l2tp-gnome I set both the wifi and VPN IPv4 settings to "addresses only" When I configure the VPN DNS to the remote nameservers, queries go to those nameservers and I can access VPN resources. But when I ALSO add Cloudflare DNS to my wifi, and switch on VPN, only the Cloudflare DNS is queried. Not event a fallback to the VPN DNS. -- 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/1671606 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1 Status in network-manager package in Ubuntu: Confirmed Status in resolvconf package in Ubuntu: Invalid Bug description: I use my company's cisco vpn via network-manager in Ubuntu 16.04.2 LTS. After recent upgrade of network-manager:amd64 from version 1.2.2-0ubuntu0.16.04.4 to version 1.2.6-0ubuntu0.16.04.1 DNS resolution of VPN's server hostnames does not work. Roll back to version 1.2.2-0ubuntu0.16.04.4 solves the problem. Steps for reproducing: 1. upgrade network-manager:amd64 from version 1.2.2-0ubuntu0.16.04.4 to version 1.2.6-0ubuntu0.16.04.1 2. connect to VPN via network-manager applet 3. nslookop servername.internal --> ** server can't find servername.internal: NXDOMAIN 4. disconnect from VPN via network-manager applet 5. roll back network-manager via command: sudo apt-get install network-manager=1.2.2-0ubuntu0.16.04.4 6. restart network-manager via sudo service network-manager restart 7. connect to VPN via network-manager applet 8. nslookop servername.internal --> the server is resolved correctly ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 9 19:49:55 2017 InstallationDate: Installed on 2015-10-05 (520 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true 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.2.6connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1671606/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869747] [NEW] Recent changes have caused Xorg to fail to start. Possibly nvidia driver related.
Public bug reported: I am unsure where the problem stems, but changes since the 25th have caused my system to fail to initialise the Xorg display. The console remains operational for debugging. I am currently using ZFS snapshots to use the system as it was on the 25th of March 2020 because that is the last snapshot before this issue. This bug was captured using ubuntu-bug when booted into the broken (i.e. not working) latest snapshot of my filesystem. The versions of packages from the not broken (i.e. correctly working) earlier snapshot of my filesystem are: libnvidia-cfg1-440:amd64 440.64-0ubuntu2 libnvidia-common-440 440.64-0ubuntu2 libnvidia-compute-440:amd64 440.64-0ubuntu2 libnvidia-compute-440:i386 440.64-0ubuntu2 libnvidia-decode-440:amd64 440.64-0ubuntu2 libnvidia-decode-440:i386440.64-0ubuntu2 libnvidia-encode-440:amd64 440.64-0ubuntu2 libnvidia-encode-440:i386440.64-0ubuntu2 libnvidia-fbc1-440:amd64 440.64-0ubuntu2 libnvidia-fbc1-440:i386 440.64-0ubuntu2 libnvidia-gl-440:amd64 440.64-0ubuntu2 libnvidia-gl-440:i386440.64-0ubuntu2 libnvidia-ifr1-440:amd64 440.64-0ubuntu2 libnvidia-ifr1-440:i386 440.64-0ubuntu2 nvidia-compute-utils-440 440.64-0ubuntu2 nvidia-dkms-440 440.64-0ubuntu2 nvidia-driver-440440.64-0ubuntu2 nvidia-kernel-common-440 440.64-0ubuntu2 nvidia-kernel-source-440 440.64-0ubuntu2 nvidia-prime 0.8.14 nvidia-settings 440.64-0ubuntu1 nvidia-utils-440 440.64-0ubuntu2 xserver-xorg-video-nvidia-440440.64-0ubuntu2 $ lsb_release -rd Description:Ubuntu Focal Fossa (development branch) Release:20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-3ubuntu1) ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 Date: Mon Mar 30 15:49:12 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes InstallationDate: Installed on 2020-03-03 (26 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) MachineType: Gigabyte Technology Co., Ltd. Z170X-UD5 TH ProcEnviron: LANGUAGE=en_GB:en TERM=linux PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_7176ku@/vmlinuz-5.4.0-18-generic root=ZFS=rpool/ROOT/ubuntu_7176ku ro quiet splash intel_iommu=on vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F22g dmi.board.asset.tag: Default string dmi.board.name: Z170X-UD5 TH-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF22g:bd03/09/2018:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-UD5TH:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-UD5TH-CF:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z170X-UD5 TH dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.2-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug champagne focal nvidia regression reproducible ubuntu ** Tags added: champagne ** Tags added: nvidia -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu.
[Touch-packages] [Bug 1869716] Re: Removing libpango1.0-0 broke Minecraft Launcher
** Changed in: pango1.0 (Ubuntu) Importance: Undecided => High ** Changed in: pango1.0 (Ubuntu) Status: Confirmed => In Progress -- 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/1869716 Title: Removing libpango1.0-0 broke Minecraft Launcher Status in pango1.0 package in Ubuntu: In Progress Bug description: I just updated my machine, and when I did libpango1.0-0 was removed. This removed minecraft-launcher - the (very) popular launcher for Minecraft Java edition. I have reported this upstream, in case they can update their package https://bugs.mojang.com/browse/MCL-13512 I am filing this bug so we can track it internally. I personally think this shouldn't have been done this late in the cycle, but there may well have been good reasons for it. As a result of the change though, it's now not possible to install Minecraft on Ubuntu 20.04. $ sudo apt install ./Minecraft\(1\).deb Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting 'minecraft-launcher' instead of './Minecraft(1).deb' Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. minecraft-launcher : Depends: libpango1.0-0 (>= 1.14.0) but it is not installable E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1869716/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869723] Re: latest updates to libpango-1.0-0 seem to break dependencies from DropBox and BitDefender
*** This bug is a duplicate of bug 1869716 *** https://bugs.launchpad.net/bugs/1869716 ** This bug has been marked a duplicate of bug 1869716 Removing libpango1.0-0 broke Minecraft Launcher -- 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/1869723 Title: latest updates to libpango-1.0-0 seem to break dependencies from DropBox and BitDefender Status in pango1.0 package in Ubuntu: New Bug description: I'm using 20.04 beta. I think the latest updates to Pango have broken dependencies for DropBox-2020 and BitDefender, of less importance. Has libpango1.0-0 become libpango-1.0-0? I think DropBox depends on libpango-1.0-0, or maybe another package that's been superceded. doing a sudo apt upgrade gives: The following additional packages will be installed: libpango-1.0-0 libpango-1.0-0:i386 libpango1.0-dev libpangocairo-1.0-0 libpangocairo-1.0-0:i386 libpangoft2-1.0-0 libpangoft2-1.0-0:i386 libpangoxft-1.0-0 pango1.0-tools The following packages will be REMOVED bitdefender-scanner-gui dropbox libpango1.0-0 The following packages will be upgraded: gir1.2-pango-1.0 libpango-1.0-0 libpango-1.0-0:i386 libpango1.0-dev libpangocairo-1.0-0 libpangocairo-1.0-0:i386 libpangoft2-1.0-0 libpangoft2-1.0-0:i386 libpangoxft-1.0-0 pango1.0-tools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1869723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1847651] Re: NetworkManager isn't pushing DNS server for openvpn connection to systemd-resolved
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1847651 Title: NetworkManager isn't pushing DNS server for openvpn connection to systemd-resolved Status in network-manager package in Ubuntu: Confirmed Bug description: I imported an openvpn configuration with `nmcli c import type openvpn file config.ovpn`. After doing that, I edited the IPv4 and IPv6 settings for the VPN to turn off automatic DNS servers and specify an IPv4 DNS server IP address explicitly. I have /usr/lib/NetworkManager/conf.d/10-dns-resolved.conf which contains: [main] # We need to specify "dns=systemd-resolved" as for the time being our # /etc/resolv.conf points to resolvconf's generated file instead of # systemd-resolved's, so the auto-detection does not work. dns=systemd-resolved Given all this, what I believe _should_ happen is when I start the VPN, /run/NetworkManager/no-stub-resolv.conf should be updated to list the DNS server I've specified first, AND NetworkManager should tell systemd-resolved to associate that DNS server with the tun0 network interface created for the VPN. The former happens, i.e., no-stub-resolv.conf is updated, but the latter doesn't, i.e., systemd-reoslve --status and resolvectl status both do not show the DNS server I've specified in the VPN settings. As a result, my DNS server is not getting used. I've hacked this all over the place and I can't figure out _any_ way, when using systemd-resolved mode in NetworkManager, to get it to use my VPN's DNS server when I enable the VPN. Surely this behavior is not expected? ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.20.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-17.18-generic 5.3.1 Uname: Linux 5.3.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 10 14:19:17 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-09-12 (28 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) IpRoute: default via 10.204.0.1 dev wlp0s20f3 proto dhcp metric 600 10.204.0.0/21 dev wlp0s20f3 proto kernel scope link src 10.204.3.73 metric 600 169.254.0.0/16 dev wlp0s20f3 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to eoan on 2019-09-20 (20 days ago) 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/1847651/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1824088] Re: unattended upgrade ran one day after schedule
This IS related to daylight saving. The script: /usr/lib/apt/apt.systemd.daily check that the script is not run twice at the same period. The script checks the date of today and the date of the last timestamp to determine the the diff. The interval is calculated using the number of seconds per day multiplied by number of days. If a day in the interval has less then 24h this check fails. This also affects the apt-daily.service that updates. This is not only Xenial but all the way up to 20.04/Focal. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1824088 Title: unattended upgrade ran one day after schedule Status in apt package in Ubuntu: New Bug description: I have noticed a strange behaviour in unattended upgrades. The host in question is scheduled to run upgrades on Mondays every second week. However, this week it ran upgrades on Tuesday instead (2019-04-09). This is the first time I’ve noticed this behaviour. I checked the logs in /var/log/apt/history.log* and I saw that worked as intended up until this week. Upgrades ran as expected on 2019-03-11 and 2019-03-25, which where both Mondays. The schedule was set with the line 'APT::Periodic::Unattended-Upgrade "14";' in the file /etc/apt/apt.conf.d/20auto-upgrades. Could it be daylight savings time that has caused skewing of the schedule? The server is located in Sweden and on 2019-03-31 we switched from CET to CEST. If the time diff is calculated with hours instead of calendar days passed, perhaps the missing hour on 2019-03-31 caused the scheduler to believe that on Monday 2019-03-08, two weeks (336 hours) had not yet passed. ADDITIONAL INFO Description:Ubuntu 16.04.6 LTS Release:16.04 apt: Installed: 1.2.29ubuntu0.1 Candidate: 1.2.31 Version table: 1.2.31 500 500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages *** 1.2.29ubuntu0.1 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 1.2.10ubuntu1 500 500 http://se.archive.ubuntu.com/ubuntu xenial/main amd64 Packages unattended-upgrades: Installed: 0.90ubuntu0.10 Candidate: 0.90ubuntu0.10 Version table: *** 0.90ubuntu0.10 500 500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main i386 Packages 100 /var/lib/dpkg/status 0.90 500 500 http://se.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 500 http://se.archive.ubuntu.com/ubuntu xenial/main i386 Packages ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apt 1.2.29ubuntu0.1 ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 Uname: Linux 4.4.0-142-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Wed Apr 10 09:06:49 2019 InstallationDate: Installed on 2017-12-28 (467 days ago) InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1824088/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 571481] Re: when slapd upgrade fails, later upgrade attempts overwrite saved backups of pre-upgrade configuration files
** Changed in: openldap (Debian) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/571481 Title: when slapd upgrade fails, later upgrade attempts overwrite saved backups of pre-upgrade configuration files Status in openldap package in Ubuntu: Confirmed Status in openldap package in Debian: Confirmed Bug description: When called in "upgrade" mode, the slapd.postinst script starts out by making a backup of the $SLAPD_CONF directory into /var/backups/slapd -/ . However, if the upgrade fails (e.g. because of bug #571057), then later attempts to run the upgrade script will still be called with the same old-package-version, and the script will blindly re-run the backup of $SLAPD_CONF onto the same destination directory, overwriting the original pre-upgrade-attempt versions of those files with the copies that include edits made by the earlier runs of the upgrade script. I see there is some logic in the compute_backup_path function to check if the backup target already exists, and to abort the upgrade run if it does. Doing the same sort of check-and-abort in backup_config_once would be better than the current scenario, though it might be even nicer if the program could pick a new backup directory (e.g. /var/backups/slapd-_try or something) automatically, rather than aborting and forcing the user to clean up manually To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/571481/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869435] Re: Performance regression on ubuntu focal
Please see thiese results: Bionic results: https://paste.ubuntu.com/p/GDfnwMMTF2/ Focal results: https://paste.ubuntu.com/p/fFzDBrtNkW/ -- 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/1869435 Title: Performance regression on ubuntu focal Status in systemd package in Ubuntu: Opinion Bug description: Hello, I noticed that systmed is performin some tasks much faster in bionic than in focal, I created a script which iterates doing some operations and executed that on bionic and focal: https://paste.ubuntu.com/p/zWWQjndtXx/ I see for example how systemctl daemon reload takes more time in focal even where there are less units than in bionic results: bionic: https://paste.ubuntu.com/p/z32WScydNk/ eoan: https://paste.ubuntu.com/p/V98vd5CHwq/ focal: https://paste.ubuntu.com/p/brNjKvC2gF/ The tests was done in gce using clean instances type n1-standard-2. Please tell me if you need any extra info To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1869435/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869435] Re: Performance regression on ubuntu focal
@sergio-j-cazzolato I see the difference, but those operations are not particularly time-critical. Snapd restarting slowly can be investigated in snapd. Colord restarts quickly on my laptop for example: $ sudo time service colord restart 0.00user 0.02system 0:00.08elapsed 27%CPU (0avgtext+0avgdata 6948maxresident)k 3336inputs+0outputs (9major+1095minor)pagefaults 0swaps ** Changed in: systemd (Ubuntu) Status: Incomplete => Opinion ** Changed in: systemd (Ubuntu) Importance: Undecided => Low -- 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/1869435 Title: Performance regression on ubuntu focal Status in systemd package in Ubuntu: Opinion Bug description: Hello, I noticed that systmed is performin some tasks much faster in bionic than in focal, I created a script which iterates doing some operations and executed that on bionic and focal: https://paste.ubuntu.com/p/zWWQjndtXx/ I see for example how systemctl daemon reload takes more time in focal even where there are less units than in bionic results: bionic: https://paste.ubuntu.com/p/z32WScydNk/ eoan: https://paste.ubuntu.com/p/V98vd5CHwq/ focal: https://paste.ubuntu.com/p/brNjKvC2gF/ The tests was done in gce using clean instances type n1-standard-2. Please tell me if you need any extra info To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1869435/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869738] [NEW] [Aspire ES1-512, Realtek ALC283, Black Headphone Out, Left] Rear jack wrongly recognized
Public bug reported: My computer only has a 4-pin jack port for external audio devices. On Ubuntu, it only seems to recognize it as an input jack, therefore when I'm trying to use a combined jack with headphones + microphones it only give me sound, but does not capture it :-/ ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lolo 2156 F pulseaudio /dev/snd/pcmC0D0c: lolo 2156 F...m pulseaudio /dev/snd/pcmC0D0p: lolo 2156 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Mar 30 16:41:40 2020 InstallationDate: Installed on 2019-05-04 (330 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Audio interne - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [Aspire ES1-512, Realtek ALC283, Black Headphone Out, Left] Playback problem UpgradeStatus: Upgraded to eoan on 2019-10-18 (164 days ago) dmi.bios.date: 12/15/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Aspire ES1-512 dmi.board.vendor: Acer dmi.board.version: V1.10 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.10 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.10:bd12/15/2014:svnAcer:pnAspireES1-512:pvrV1.10:rvnAcer:rnAspireES1-512:rvrV1.10:cvnAcer:ct10:cvrV1.10: dmi.product.family: BayTrail dmi.product.name: Aspire ES1-512 dmi.product.sku: EA53_BM_083D_1.10 dmi.product.version: V1.10 dmi.sys.vendor: Acer mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-03-30T16:29:51.143751 ** Affects: alsa-driver (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 alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1869738 Title: [Aspire ES1-512, Realtek ALC283, Black Headphone Out, Left] Rear jack wrongly recognized Status in alsa-driver package in Ubuntu: New Bug description: My computer only has a 4-pin jack port for external audio devices. On Ubuntu, it only seems to recognize it as an input jack, therefore when I'm trying to use a combined jack with headphones + microphones it only give me sound, but does not capture it :-/ ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lolo 2156 F pulseaudio /dev/snd/pcmC0D0c: lolo 2156 F...m pulseaudio /dev/snd/pcmC0D0p: lolo 2156 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Mar 30 16:41:40 2020 InstallationDate: Installed on 2019-05-04 (330 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Audio interne - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [Aspire ES1-512, Realtek ALC283, Black Headphone Out, Left] Playback problem UpgradeStatus: Upgraded to eoan on 2019-10-18 (164 days ago) dmi.bios.date: 12/15/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Aspire ES1-512 dmi.board.vendor: Acer dmi.board.version: V1.10 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.10 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.10:bd12/15/2014:svnAcer:pnAspireES1-512:pvrV1.10:rvnAcer:rnAspireES1-512:rvrV1.10:cvnAcer:ct10:cvrV1.10: dmi.product.family: BayTrail dmi.product.name: Aspire ES1-512 dmi.product.sku: EA53_BM_083D_1.10 dmi.product.version: V1.10 dmi.sys.vendor: Acer mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-03-30T16:29:51.143751 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1869738/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1869661] Re: lxc 3.23 (?) breaks nested lxd with snaps
Hello, I still see: + lxd.lxc exec my-nesting-ubuntu -- lxd.lxc exec my-inner-ubuntu -- echo from-the-INSIDE-inside Error: EOF when using lxd from edge: google:ubuntu-18.04-64 .../tests/main/lxd# snap list lxd Name Version RevTracking Publisher Notes lxd git-350df50 14114 latest/edge canonical✓ - Is there any other thing to try? Thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1869661 Title: lxc 3.23 (?) breaks nested lxd with snaps Status in lxc package in Ubuntu: New Bug description: It looks like the latest release of lxd broke our snapd lxd test. The failure looks like it's lxd itself that can no longer run a nested lxd. The full log is available on e.g. https://api.travis-ci.org/v3/job/668138958/log.txt, search for """ Starting my-inner-ubuntu + MATCH from-the-INSIDE-inside + lxd.lxc exec my-nesting-ubuntu -- lxd.lxc exec my-inner-ubuntu -- echo from-the-INSIDE-inside Error: EOF grep error: pattern not found, got: """ The relevant part of the test is: https://github.com/snapcore/snapd/blob/master/tests/main/lxd/task.yaml#L153 I.e. this test creates an lxd container and sets up lxd inside this container. Happy to help with debugging (if needed), it really easy to reproduce with the above spread script. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1869661/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869435] Re: Performance regression on ubuntu focal
> results bionic: https://paste.ubuntu.com/p/GDfnwMMTF2/ > results focal: https://paste.ubuntu.com/p/GDfnwMMTF2/ these are the same pastebin. > Does it make sense? Do you need more info? Personally I don't see this as anything significant enough to investigate, but maybe I'm missing something. And I probably am not the person you need to convince to do something, so I'll back away from this bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1869435 Title: Performance regression on ubuntu focal Status in systemd package in Ubuntu: Incomplete Bug description: Hello, I noticed that systmed is performin some tasks much faster in bionic than in focal, I created a script which iterates doing some operations and executed that on bionic and focal: https://paste.ubuntu.com/p/zWWQjndtXx/ I see for example how systemctl daemon reload takes more time in focal even where there are less units than in bionic results: bionic: https://paste.ubuntu.com/p/z32WScydNk/ eoan: https://paste.ubuntu.com/p/V98vd5CHwq/ focal: https://paste.ubuntu.com/p/brNjKvC2gF/ The tests was done in gce using clean instances type n1-standard-2. Please tell me if you need any extra info To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1869435/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869723] [NEW] latest updates to libpango-1.0-0 seem to break dependencies from DropBox and BitDefender
Public bug reported: I'm using 20.04 beta. I think the latest updates to Pango have broken dependencies for DropBox-2020 and BitDefender, of less importance. Has libpango1.0-0 become libpango-1.0-0? I think DropBox depends on libpango-1.0-0, or maybe another package that's been superceded. doing a sudo apt upgrade gives: The following additional packages will be installed: libpango-1.0-0 libpango-1.0-0:i386 libpango1.0-dev libpangocairo-1.0-0 libpangocairo-1.0-0:i386 libpangoft2-1.0-0 libpangoft2-1.0-0:i386 libpangoxft-1.0-0 pango1.0-tools The following packages will be REMOVED bitdefender-scanner-gui dropbox libpango1.0-0 The following packages will be upgraded: gir1.2-pango-1.0 libpango-1.0-0 libpango-1.0-0:i386 libpango1.0-dev libpangocairo-1.0-0 libpangocairo-1.0-0:i386 libpangoft2-1.0-0 libpangoft2-1.0-0:i386 libpangoxft-1.0-0 pango1.0-tools ** Affects: pango1.0 (Ubuntu) Importance: Undecided Status: New -- 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/1869723 Title: latest updates to libpango-1.0-0 seem to break dependencies from DropBox and BitDefender Status in pango1.0 package in Ubuntu: New Bug description: I'm using 20.04 beta. I think the latest updates to Pango have broken dependencies for DropBox-2020 and BitDefender, of less importance. Has libpango1.0-0 become libpango-1.0-0? I think DropBox depends on libpango-1.0-0, or maybe another package that's been superceded. doing a sudo apt upgrade gives: The following additional packages will be installed: libpango-1.0-0 libpango-1.0-0:i386 libpango1.0-dev libpangocairo-1.0-0 libpangocairo-1.0-0:i386 libpangoft2-1.0-0 libpangoft2-1.0-0:i386 libpangoxft-1.0-0 pango1.0-tools The following packages will be REMOVED bitdefender-scanner-gui dropbox libpango1.0-0 The following packages will be upgraded: gir1.2-pango-1.0 libpango-1.0-0 libpango-1.0-0:i386 libpango1.0-dev libpangocairo-1.0-0 libpangocairo-1.0-0:i386 libpangoft2-1.0-0 libpangoft2-1.0-0:i386 libpangoxft-1.0-0 pango1.0-tools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1869723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869435] Re: Performance regression on ubuntu focal
Hi, In our tests logs we see that focal is slower than other systems like bionic. I printed all the commands we run with the times and noticed the main diff on times is when running different systemd commands. So I did a very small script to compare basic calls that we use in our snapd test suite. Now I did a new comparison between focal and bionic but changed the paramenters compared with the previous logs, now I am using the calls we see in our tests which are slower on focal compared with bionic. script used: https://paste.ubuntu.com/p/JG977dRXMy/ results bionic: https://paste.ubuntu.com/p/GDfnwMMTF2/ results focal: https://paste.ubuntu.com/p/GDfnwMMTF2/ All the results are in milliseconds. With these logs I think is more clear the performance difference between both, i.e. "systemctl list- unit-files --full" taks almost the double on bionic than focal. Does it make sense? Do you need more info? Thanks -- 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/1869435 Title: Performance regression on ubuntu focal Status in systemd package in Ubuntu: Incomplete Bug description: Hello, I noticed that systmed is performin some tasks much faster in bionic than in focal, I created a script which iterates doing some operations and executed that on bionic and focal: https://paste.ubuntu.com/p/zWWQjndtXx/ I see for example how systemctl daemon reload takes more time in focal even where there are less units than in bionic results: bionic: https://paste.ubuntu.com/p/z32WScydNk/ eoan: https://paste.ubuntu.com/p/V98vd5CHwq/ focal: https://paste.ubuntu.com/p/brNjKvC2gF/ The tests was done in gce using clean instances type n1-standard-2. Please tell me if you need any extra info To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1869435/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869641] Re: Failed to launch ibus daemon in Xwayland + gnome-shell 3.36.0
Thanks Gunnar, I've uploaded it to focal now ** Changed in: ibus (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1869641 Title: Failed to launch ibus daemon in Xwayland + gnome-shell 3.36.0 Status in ibus package in Ubuntu: Fix Committed Bug description: Description: Ubuntu Focal Fossa (development branch) Release: 20.04 ibus 1.5.22-2ubuntu1 Steps to reproduce 1. Upgrade to GNOME 3.36.0. 2. Restart Ubuntu 20.04 daily with Wayland What did you expect to happen The ibus daemon is launched. What happened The ibus daemon is not running. I can confirm I have an exact same issue in https://gitlab.gnome.org/GNOME/gnome-shell/issues/2341 when login with wayland selected. After applying this: https://github.com/ibus/ibus/commit/8ce25208c3f4adfd290a032c6aa739d2b7580eb1 patch locally I can confirm it fixed my issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1869641/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863414] Re: Have many "/usr/lib/python3.8/subprocess.py:838: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used" o
** Changed in: python3-defaults (Debian) Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1863414 Title: Have many "/usr/lib/python3.8/subprocess.py:838: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used" on simple APT usage Status in python3-defaults package in Ubuntu: In Progress Status in python3.8 package in Ubuntu: Invalid Status in python3-defaults source package in Focal: In Progress Status in python3.8 source package in Focal: Invalid Status in python3-defaults package in Debian: Fix Released Bug description: Steps to reproduce: 1. Have Ubuntu 20.04 LTS installed 2. Run regular APT task such as `sudo apt dist-upgrade` 3. Wait it to finish Expected results: * APT runs without any warnings and/or errors Actual results: * APT runs with many python-related warnings like >``` >/usr/lib/python3.8/subprocess.py:838: RuntimeWarning: line buffering (buffering=1) isn't supported >in binary mode, the default buffer size will be used > self.stdin = io.open(p2cwrite, 'wb', bufsize) > >``` Full output below: ``` $ sudo apt dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages were automatically installed and are no longer required: ruby-json ruby-pg ruby-sequel ruby-sequel-pg Use 'sudo apt autoremove' to remove them. The following NEW packages will be installed: kdevelop55-libs libxentoolcore1 ubuntu-mate-wallpapers-focal The following packages will be upgraded: atril atril-common debootstrap dmeventd dmsetup dnsmasq-base engrampa engrampa-common fwupd fwupd-signed gir1.2-atrildocument-1.5.0 gir1.2-atrilview-1.5.0 gir1.2-freedesktop gir1.2-glib-2.0 gir1.2-pluma-1.0 initramfs-tools initramfs-tools-bin initramfs-tools-core iproute2 isc-dhcp-client isc-dhcp-common jekyll k3b k3b-data k3b-i18n kdevelop kdevelop-data libatrildocument-dev libatrildocument3 libatrilview-dev libatrilview3 libdevmapper-event1.02.1 libdevmapper1.02.1 libdistro-info-perl libfwupd2 libfwupdplugin1 libgirepository-1.0-1 libk3b7 libk3b7-extracodecs liblvm2cmd2.03 libmate-sensors-applet-plugin-dev libmate-sensors-applet-plugin0 libmate-slab0 libmate-window-settings-dev libmate-window-settings1 libmatedict-dev libmatedict6 libmysqlclient21 libmysqlclient21:i386 libvirt-clients libvirt-daemon libvirt-daemon-driver-qemu libvirt-daemon-driver-storage-rbd libvirt-daemon-system libvirt-daemon-system-systemd libvirt0 libxenstore3.0 libxmlgraphics-commons-java lvm2 mate-applets mate-applets-common mate-common mate-control-center mate-control-center-common mate-core mate-desktop-environment mate-desktop-environment-core mate-desktop-environment-extra mate-desktop-environment-extras mate-dock-applet mate-media mate-media-common mate-netbook mate-netbook-common mate-notification-daemon mate-notification-daemon-common mate-power-manager mate-power-manager-common mate-screensaver mate-screensaver-common mate-sensors-applet mate-sensors-applet-common mate-sensors-applet-nvidia mate-system-monitor mate-system-monitor-common mate-terminal mate-terminal-common mate-user-share mate-user-share-common mate-utils mate-utils-common maxima maxima-doc maxima-share mozo nano pluma pluma-common pluma-dev pluma-doc plymouth-theme-ubuntu-mate-logo plymouth-theme-ubuntu-mate-text python-caja-common python3-caja python3-distro-info python3-macaroonbakery qemu-block-extra qemu-kvm qemu-system-common qemu-system-data qemu-system-gui qemu-system-x86 qemu-utils ubuntu-mate-artwork ubuntu-mate-default-settings ubuntu-mate-icon-themes ubuntu-mate-lightdm-theme ubuntu-mate-live-settings ubuntu-mate-themes ubuntu-mate-wallpapers ubuntu-mate-wallpapers-artful ubuntu-mate-wallpapers-bionic ubuntu-mate-wallpapers-common ubuntu-mate-wallpapers-complete ubuntu-mate-wallpapers-cosmic ubuntu-mate-wallpapers-disco ubuntu-mate-wallpapers-eoan ubuntu-mate-wallpapers-legacy ubuntu-mate-wallpapers-photos ubuntu-mate-wallpapers-utopic ubuntu-mate-wallpapers-vivid ubuntu-mate-wallpapers-wily ubuntu-mate-wallpapers-xenial ubuntu-mate-wallpapers-yakkety ubuntu-mate-wallpapers-zesty umbrello 136 upgraded, 3 newly installed, 0 to remove and 0 not upgraded. Need to get 215 MB of archives. After this operation, 12,8 MB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu focal/universe amd64 mate-common all 1.24.0-1ubuntu1 [17,0 kB] ... Get:139 http://archive.ubuntu.com/ubuntu focal/universe amd64 mate-dock-applet amd64 20.04.0-0ubuntu1 [91,8 kB] Fetched 215 MB in 4min 4s (882
[Touch-packages] [Bug 1757320] Re: Remove Qt 4 from the archive
** Changed in: qt4-x11 (Debian) Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/1757320 Title: Remove Qt 4 from the archive Status in qt4-x11 package in Ubuntu: Fix Released Status in qt4-x11 package in Debian: Fix Released Bug description: Currently Qt 4 has been dead upstream and we are starting to have problems maintaining it, like for example in the OpenSSL 1.1 support case. Following in the footsteps of Debian[1], all packages directly or indirectly depending on qt4-x11 must either get ported to Qt 5 and uploaded to the development release or get removed (by means of demotion to -proposed or the whole source package removal) before the 19.04 release. If it is possible to do this by the 18.10 release, please do so. No new packages entering the Ubuntu archive should depend on qt4-x11 or any package which directly or indirectly depends on it. [1] https://wiki.debian.org/Qt4Removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/1757320/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869721] [NEW] Apt error message gives incorrect syntax
Public bug reported: in Apt, when trying to reinstall or remove problem packages, if the process is unable to run, it says there are unmet dependencies. It then suggest a command to run to fix the problems. This would be the proper procedure for this, however the suggested command it provides is wrong. $ lsb_release -rd Description:Linux Mint 19.3 Tricia Release:19.3 apt: Installed: 1.6.12 Candidate: 1.6.12 Version table: *** 1.6.12 500 500 http://mirrors.tripadvisor.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.6.6ubuntu0.1 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1.6.1 500 500 http://mirrors.tripadvisor.com/ubuntu bionic/main amd64 Packages Expected behavior: failed reinstall/uninstall command should show correct syntax for recommended command. In this case it should be "apt install --fix- broken", or "sudo apt install --fix-broken" (verified myself by running that command). Actual behavior: output from failed command ended with "E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution)." Running the command as it is shown there results in apt giving a syntax summary, rather than running the intended command. It was only by guessing at alternative formats on the command that got it to work. The format as shown in the incorrect example would have seemed more logical, as the older apt-get equivalent was "apt-get -f install", with the option switch before the command. It is up to the devs to decide whether the switch before or after the command is correct, just as long as the correct and functional form is shown in the error. ** Affects: apt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1869721 Title: Apt error message gives incorrect syntax Status in apt package in Ubuntu: New Bug description: in Apt, when trying to reinstall or remove problem packages, if the process is unable to run, it says there are unmet dependencies. It then suggest a command to run to fix the problems. This would be the proper procedure for this, however the suggested command it provides is wrong. $ lsb_release -rd Description: Linux Mint 19.3 Tricia Release: 19.3 apt: Installed: 1.6.12 Candidate: 1.6.12 Version table: *** 1.6.12 500 500 http://mirrors.tripadvisor.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.6.6ubuntu0.1 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1.6.1 500 500 http://mirrors.tripadvisor.com/ubuntu bionic/main amd64 Packages Expected behavior: failed reinstall/uninstall command should show correct syntax for recommended command. In this case it should be "apt install --fix- broken", or "sudo apt install --fix-broken" (verified myself by running that command). Actual behavior: output from failed command ended with "E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution)." Running the command as it is shown there results in apt giving a syntax summary, rather than running the intended command. It was only by guessing at alternative formats on the command that got it to work. The format as shown in the incorrect example would have seemed more logical, as the older apt-get equivalent was "apt-get -f install", with the option switch before the command. It is up to the devs to decide whether the switch before or after the command is correct, just as long as the correct and functional form is shown in the error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1869721/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869716] Re: Removing libpango1.0-0 broke Minecraft Launcher
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pango1.0 (Ubuntu) Status: New => Confirmed -- 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/1869716 Title: Removing libpango1.0-0 broke Minecraft Launcher Status in pango1.0 package in Ubuntu: Confirmed Bug description: I just updated my machine, and when I did libpango1.0-0 was removed. This removed minecraft-launcher - the (very) popular launcher for Minecraft Java edition. I have reported this upstream, in case they can update their package https://bugs.mojang.com/browse/MCL-13512 I am filing this bug so we can track it internally. I personally think this shouldn't have been done this late in the cycle, but there may well have been good reasons for it. As a result of the change though, it's now not possible to install Minecraft on Ubuntu 20.04. $ sudo apt install ./Minecraft\(1\).deb Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting 'minecraft-launcher' instead of './Minecraft(1).deb' Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. minecraft-launcher : Depends: libpango1.0-0 (>= 1.14.0) but it is not installable E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1869716/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp