[Touch-packages] [Bug 1896073] Re: SRU the current 2.3.6 stable update
** Tags added: upgrade-software-version -- 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/1896073 Title: SRU the current 2.3.6 stable update Status in tracker package in Ubuntu: Fix Released Status in tracker source package in Focal: Fix Committed Bug description: * Impact That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/tracker/-/blob/tracker-2.3/NEWS The update add a 'tracker export' command, that's new and not used into any integration so has no real regression potential. It's an optional new option that can be used to export the data to migrate them to the incoming tracker3. * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Check that file search works correctly from the command line, shell and nautilus * Regression potential There is no specific change or feature to test in that update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1896073/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1906364] Re: [SRU] unattended-upgrade still restarts blacklisted daemons
** No longer affects: unattended-upgrades (Ubuntu) ** No longer affects: unattended-upgrades (Ubuntu Xenial) ** No longer affects: unattended-upgrades (Ubuntu Bionic) ** No longer affects: unattended-upgrades (Ubuntu Focal) ** No longer affects: unattended-upgrades (Ubuntu Groovy) ** No longer affects: unattended-upgrades (Ubuntu Hirsute) -- 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/1906364 Title: [SRU] unattended-upgrade still restarts blacklisted daemons Status in docker.io package in Ubuntu: Fix Released Status in docker.io source package in Xenial: Fix Committed Status in docker.io source package in Bionic: Fix Committed Status in docker.io source package in Focal: Fix Committed Status in docker.io source package in Groovy: Fix Committed Status in docker.io source package in Hirsute: Fix Released Bug description: [Impact] Docker uses containerd under the hood. When containerd is upgraded it stops and restarts its service; docker stops when containerd stops but doesn’t restart. Particularly when doing unattended upgrades, an SRU fix rolled out for containerd can result in unexpected and widespread service outages for docker. [Test Case] $ sudo apt install docker.io $ sudo systemctl start docker $ systemctl status docker | grep Active Active: active (running) since[...] $ systemctl status containerd | grep Active Active: active (running) since[...] $ docker pull ubuntu/redis:latest $ docker run -e REDIS_PASSWORD=1234 --network host \ --name test-redis -d ubuntu/redis:latest $ telnet localhost 6379 $ docker container logs test-redis $ sudo apt install --reinstall containerd $ systemctl status containerd | grep Active Active: active (running) since $ systemctl status docker | grep Active Active: inactive (dead) since [...]; 8s ago $ docker container logs test-redis [Where Problems Could Occur] The challenge with this issue is addressing all important corner cases, and as such the biggest risk is that we miss a corner case and fail to keep the two services running when they should. Areas to watch will be failures during start/stop/restart/upgrade type operations. Issues during runtime are unlikely to relate to this change. [Original Report] Hello, Today plenty of our systems running ubuntu 20.04 were restarting the docker daemon, even if i blacklisted the docker package. Since docker has an dependency on containerd thats the reason why it was restarted. IMO the blacklist should also check the full tree of dependencies... This should NOT happen! From the log you find: 2020-12-01 06:40:13,881 INFO Starting unattended upgrades script 2020-12-01 06:40:13,882 INFO Allowed origins are: o=Ubuntu,a=focal, o=Ubuntu,a=focal-security, o=UbuntuESMApps,a=focal-apps-security, o=UbuntuESM,a=focal-infra-security 2020-12-01 06:40:13,882 INFO Initial blacklist: docker docker.io 2020-12-01 06:40:13,882 INFO Initial whitelist (not strict): 2020-12-01 06:40:19,139 INFO Packages that will be upgraded: containerd qemu-block-extra qemu-kvm qemu-system-common qemu-system-data qemu-system-gui qemu-system-x86 qemu-utils 2020-12-01 06:40:19,140 INFO Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log 2020-12-01 06:40:46,996 INFO All upgrades installed 2020-12-01 06:40:50,732 INFO Starting unattended upgrades script 2020-12-01 06:40:50,732 INFO Allowed origins are: o=Ubuntu,a=focal, o=Ubuntu,a=focal-security, o=UbuntuESMApps,a=focal-apps-security, o=UbuntuESM,a=focal-infra-security 2020-12-01 06:40:50,733 INFO Initial blacklist: docker docker.io 2020-12-01 06:40:50,733 INFO Initial whitelist (not strict): Also this happened for us on plenty of our servers almost at the same (why the unattended updates are not spread over time?), which destroyed the second time an production environment. This is not how unattended-upgraded should be, sadly this package lost our trust and we disable it and schedule the 'unattended updates' now on our own. PS: Not to say that on some servers the docker daemon did not even restart.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1906364/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1908733] Re: CVE-2020-1971 OpenSSL package upgrade issue
Hello, I know, it might look as i replaced Ubuntu OpenSSL packages with Ondrej's OpenSSL package. But i didnt. And here is a big problem for a lot of people. Please link: https://github.com/oerdnj/deb.sury.org/issues/1512 When regular user of Ubuntu 18.04 LTS want to install PHP7.4 pretty much only way is to add ppa:ondrej/php and after that install PHP7.4. But after ppa:ondrej/php added, for some reason it replaces Ubuntu OpenSSL packages with Ondrej's OpenSSL packages. A lot of guides in Internet describe how to install PHP7.4 via "ppa:ondrej/php", so i believe this issue affect a lot of people/companies, which run public facing webservers with PHP7.4 and Ubuntu 18.04. I would be really grateful if someone with expertise and knowledge could check Github link (https://github.com/oerdnj/deb.sury.org/issues/1512), and advice (or just post their thoughts) about this situation. Thank you. ** Bug watch added: github.com/oerdnj/deb.sury.org/issues #1512 https://github.com/oerdnj/deb.sury.org/issues/1512 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1908733 Title: CVE-2020-1971 OpenSSL package upgrade issue Status in openssl package in Ubuntu: Invalid Bug description: Hello, I have tested it on 4 vurtual machines (details below): # uname -a Linux web2 4.15.0-128-generic #131-Ubuntu SMP Wed Dec 9 06:57:35 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux # lsb_release -rd Description:Ubuntu 18.04.5 LTS Release:18.04 $ apt-cache policy openssl openssl: Installed: 1.1.1g-1+ubuntu18.04.1+deb.sury.org+1 Candidate: 1.1.1g-1+ubuntu18.04.1+deb.sury.org+1 Version table: *** 1.1.1g-1+ubuntu18.04.1+deb.sury.org+1 500 500 http://ppa.launchpad.net/ondrej/apache2/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 1.1.1g-1+ubuntu18.04.1+deb.sury.org+1 500 500 http://ppa.launchpad.net/ondrej/php/ubuntu bionic/main amd64 Packages 1.1.1-1ubuntu2.1~18.04.7 500 500 http://il.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1.1.0g-2ubuntu4 500 500 http://il.archive.ubuntu.com/ubuntu bionic/main amd64 Packages My OpenSSL version is: openssl 1.1.1g-1+ubuntu18.04.1+deb.sury.org+1 I wanted to install patch to fix "CVE-2020-1971" on my virtual machines. But found next issue: there is article ( https://ubuntu.com/security/CVE-2020-1971) with package name (version), where "CVE-2020-1971" issues is fixed --> "1.1.1-1ubuntu2.1~18.04.7". Normal (expected?) behaviour for me (in my case) is to do next: sudo apt update sudo apt upgrade After this all packages in my system should be upgraded to latest versions. But in fact - OpenSSL package remained same 1.1.1g-1+ubuntu18.04.1+deb.sury.org+1 When i check: $ apt list openssl Listing... Done openssl/bionic,now 1.1.1g-1+ubuntu18.04.1+deb.sury.org+1 amd64 [installed] N: There are 3 additional versions. Please use the '-a' switch to see them. $ apt list openssl -a Listing... Done openssl/bionic,now 1.1.1g-1+ubuntu18.04.1+deb.sury.org+1 amd64 [installed] openssl/bionic 1.1.1g-1+ubuntu18.04.1+deb.sury.org+1 amd64 openssl/bionic-updates,bionic-security 1.1.1-1ubuntu2.1~18.04.7 amd64 openssl/bionic 1.1.0g-2ubuntu4 amd64 Ok, lets install latest package --> 1.1.1-1ubuntu2.1~18.04.7: sudo apt install openssl=1.1.1-1ubuntu2.1~18.04.7 And here i receive next: Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be DOWNGRADED: openssl 0 upgraded, 0 newly installed, 1 downgraded, 0 to remove and 0 not upgraded. Need to get 614 kB of archives. After this operation, 132 kB disk space will be freed. Do you want to continue? [Y/n] yn Get:1 http://il.archive.ubuntu.com/ubuntu bionic-updates/main amd64 openssl amd6 4 1.1.1-1ubuntu2.1~18.04.7 [614 kB] Fetched 614 kB in 0s (1,367 kB/s) dpkg: warning: downgrading openssl from 1.1.1g-1+ubuntu18.04.1+deb.sury.org+1 to 1.1.1-1ubuntu2.1~18.04.7 Is this correct behavior? Why newest version (mentioned in https://ubuntu.com/security/CVE-2020-1971) considered as DOWNGRADE? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1908733/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-pack
[Touch-packages] [Bug 1888598] Re: Pulseaudio breaks HDMI audio on sleep/wake
I have the same issue. Linux nova 5.4.0-58-generic #64-Ubuntu SMP Wed Dec 9 08:16:25 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Ubuntu 20.04.1 LTS -- 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/1888598 Title: Pulseaudio breaks HDMI audio on sleep/wake Status in pulseaudio package in Ubuntu: Confirmed Bug description: on a fresh Ubuntu 20.04 x64 install, I've noticed some troubling bugs with pulseaudio after putting my system to sleep and then waking it up. these bugs aren't present on a fresh boot, only after resuming from sleep: - it forgets which sound output device it's set to, and always reverse to the motherboard's S/PDIF output. - I have two devices connected to my video card, one is a displayport monitor, and one is a home theater receiver via HDMI. it confuses the two, and randomly switches which device it thinks is capable of surround sound. - it sometimes refuses to switch to the correct audio device, and just resets any choice back to the internal S/PDIF, until the system is rebooted. as you can imagine, this a pretty frustrating state of affairs. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.4 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tessa 3387 F pulseaudio /dev/snd/pcmC1D7p: tessa 3387 F...m pulseaudio /dev/snd/controlC2: tessa 3387 F pulseaudio /dev/snd/controlC0: tessa 3387 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 22 18:38:42 2020 InstallationDate: Installed on 2020-07-15 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3503 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: GRYPHON Z97 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3503:bd04/18/2018:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnGRYPHONZ97:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1888598/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1909108] [NEW] Second static mouse pointer on two screen setup
Public bug reported: I have two screens and a Bluetooth mouse. When I wake PC up from the suspend the second frozen cursor is left on the screen. Screenshot tool does not see it. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Dec 23 11:06:00 2020 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon Pro WX 4100] [1002:67e3] (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon Pro WX 4100] [1002:0b0d] InstallationDate: Installed on 2020-12-15 (7 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Micro-Star International Co., Ltd. MS-7B89 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-33-generic root=UUID=2426cc97-af0d-4826-80aa-a05ec1ef1e8e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.70 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M MORTAR MAX (MS-7B89) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.70:bd04/21/2020:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B89 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-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 groovy ubuntu ** Attachment added: "IMG_20201223_111820-1.jpg" https://bugs.launchpad.net/bugs/1909108/+attachment/5446192/+files/IMG_20201223_111820-1.jpg -- 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/1909108 Title: Second static mouse pointer on two screen setup Status in xorg package in Ubuntu: New Bug description: I have two screens and a Bluetooth mouse. When I wake PC up from the suspend the second frozen cursor is left on the screen. Screenshot tool does not see it. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Dec 23 11:06:00 2020 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon Pro WX 4100] [1002:67e3] (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon Pro WX 4100] [1002:0b0d] InstallationDate: Installed on 2020-12-15 (7 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Micro-Star International Co., Ltd. MS-7B89 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-33-generic root=UUID=2426cc97-af0d-4826-80aa-a05ec1ef1e8e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.70 dmi.board.asset.tag
[Touch-packages] [Bug 1850966] Re: Stuck at "Refreshing software cache" after enabling repository not updated for Eoan
it affects me too... Ubuntu 20.10 -- 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/1850966 Title: Stuck at "Refreshing software cache" after enabling repository not updated for Eoan Status in software-properties package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Open Software and Updates 2. Go to "other software" and enable, for example, a repository disabled during upgrade to Eoan which is not updated for Eoan yet 3. Press close and then reload on the dialog that opens. 4. Refreshing software cache dialog is stuck After closing the dialogs by right clicking on the windows and the open apps bar, re opening Software and updates only shows a white square you can't interact with. Ubuntu 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1850966/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/440 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Triaged Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1908726] Re: Update the package for Focal Fossa to >= 0.27.3
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: exiv2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1908726 Title: Update the package for Focal Fossa to >= 0.27.3 Status in exiv2 package in Ubuntu: Confirmed Bug description: The current Darktable from the Focal Fossa repo can't be upgraded because it requires libexiv2-27 (>= 0.27.3) and the currently available one is libexiv2-27/0.27.2-8ubuntu2 Can you please update it to >= 0.27.3 ? $ sudo apt upgrade darktable Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 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: darktable : Depends: libexiv2-27 (>= 0.27.3) but 0.27.2-8ubuntu2 is to be installed Depends: libilmbase25 (>= 2.5.3) but it is not installable Depends: libjson-glib-1.0-0 (>= 1.5.2) but 1.4.4-2ubuntu2 is to be installed Depends: libopenexr25 (>= 2.5.3) but it is not installable E: Broken packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1908726/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1908725] Re: Update the package for Focal Fossa to >= 2.5.3
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: openexr (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openexr in Ubuntu. https://bugs.launchpad.net/bugs/1908725 Title: Update the package for Focal Fossa to >= 2.5.3 Status in openexr package in Ubuntu: Confirmed Bug description: The current Darktable from the Focal Fossa repo can't be upgraded because it requires libopenexr25 (>= 2.5.3) and the currently available one is libopenexr24/focal-updates,focal-security,now 2.3.0-6ubuntu0.2 Can you please update it to >=2.5.3 ? $ sudo apt upgrade darktable Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 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: darktable : Depends: libexiv2-27 (>= 0.27.3) but 0.27.2-8ubuntu2 is to be installed Depends: libilmbase25 (>= 2.5.3) but it is not installable Depends: libjson-glib-1.0-0 (>= 1.5.2) but 1.4.4-2ubuntu2 is to be installed Depends: libopenexr25 (>= 2.5.3) but it is not installable E: Broken packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openexr/+bug/1908725/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1909132] [NEW] wavy diagonal line when scrolling in firefox
Public bug reported: Scrolling in Firefox moves the web page up and down, but also causes a wavy line to appear, that extends horizontally and diagonally across the page, and disappears once you stop scrolling. i use ubuntu20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .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 450.80.02 Wed Sep 23 01:13:39 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Dec 23 21:32:24 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia-srv, 450.80.02, 5.4.0-58-generic, x86_64: installed GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:1b10] Subsystem: ASUSTeK Computer Inc. GM108M [GeForce 930MX] [1043:1b10] InstallationDate: Installed on 2020-12-19 (4 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 13d3:3496 IMC Networks Bus 001 Device 003: ID 13d3:5a01 IMC Networks USB2.0 VGA UVC WebCam Bus 001 Device 002: ID 062a:4101 MosArt Semiconductor Corp. Wireless Keyboard/Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X542URV ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-58-generic root=UUID=2b8aa80b-3a8c-4397-9c75-472b469e71ec ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X542URV.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X542URV dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX542URV.308:bd05/21/2019:svnASUSTeKCOMPUTERINC.:pnX542URV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX542URV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: X542URV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 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+git20200226-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 focal 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/1909132 Title: wavy diagonal line when scrolling in firefox Status in xorg package in Ubuntu: New Bug description: Scrolling in Firefox moves the web page up and down, but also causes a wavy line to appear, that extends horizontally and diagonally across the page, and disappears once you stop scrolling. i use ubuntu20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gp
[Touch-packages] [Bug 1909131] [NEW] wayland - cursor is not affected by night light mode
Public bug reported: Even with the night light mode activated, the cursor remains blue (the filter is not applied). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Dec 23 14:54:37 2020 DistUpgraded: 2020-10-23 13:38:17,737 DEBUG /openCache(), new cache size 66390 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS780L [Radeon 3000] [1002:9616] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd RS780L [Radeon 3000] [1458:d000] InstallationDate: Installed on 2020-07-24 (151 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 6.0 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=b12510e7-1702-4d36-80bc-11251ef87185 ro quiet splash radeon.audio=1 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-10-23 (61 days ago) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 126: Error executing command as another user: Request dismissed dmi.bios.date: 11/25/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: GA-78LMT-USB3 6.0 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: SEx dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrSEx:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-78LMT-USB3 6.0 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 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+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New ** Affects: wayland (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption focal ubuntu wayland-session ** Attachment added: "a.jpeg" https://bugs.launchpad.net/bugs/1909131/+attachment/5446268/+files/a.jpeg ** Package changed: xorg (Ubuntu) => wayland (Ubuntu) ** Also affects: gnome-session (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/1909131 Title: wayland - cursor is not affected by night light mode Status in gnome-session package in Ubuntu: New Status in wayland package in Ubuntu: New Bug description: Even with the night light mode activated, the cursor remains blue (the filter is not applied). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Dec 23 14:54:37 2020 DistUpgraded: 2020-10-23 13:38:17,737 DEBUG /openCache(), new cache size 66390 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS780L [Radeon 3000] [1002:9616] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd RS780L [Radeon 3000] [1458:d000] InstallationDate: Installed on 2020-07-24 (151 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 6.0 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=b12510e7-1702-4d36-80bc-11251ef87185 ro quiet splash radeon.audio=1 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-10-23 (61 days ago) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 126: Error executing command as another user: Request dismis
[Touch-packages] [Bug 1899288] Re: Python3 can't co-exist with Oracle's VirtualBox on 20.10
I ran into the same problem. During dist-upgrade it wanted to remove python2 and virtualbox, but upgrade dh-python. The upgraded dh-python doesn't work with virtualbox. I uninstalled dh-python, let dist-upgrade do what it wanted, then re- installed virtualbox, and that seemed to make everything happy. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/1899288 Title: Python3 can't co-exist with Oracle's VirtualBox on 20.10 Status in dh-python package in Ubuntu: Confirmed Status in what-is-python package in Ubuntu: Incomplete Bug description: Sorry I couldn't file this bug against the correct packages. The form told me there are no such packages as python-is-python3 and dh-python in Ubuntu... Release: Groovy Gorilla (Ubuntu 20.10). Package versions: python-is-python3 3.8.2-4 dh-python 4.20200925 The release of Ubuntu 20.10 is less than two weeks out, so I'd like to draw attention to a problem I've run into. It seems that 20.10 defaults to python3 and wants to install python-is-python3, which pulls in the latest version of dh-python, which in turn can't co-exist with Oracle's Virtualbox-6.1 and wants to uninstall it. I don't mind having _both_ python2 (apparently a requirement of VirtualBox) and python3 installed. But as of right now I can have either python-is-python3, and not be able to do a complete upgrade since virtualbox-6.1 will be uninstalled, or python-is-python2, in which case I cripple 20.10's python3 install, since I won't get dh- python and python-six. Ia there something the python packagers do about this? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/1899288/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1909143] [NEW] df & mount aliases to hide reports for snap mounts
Public bug reported: I would purpose the following aliases as defaults for Hirsute: alias df="df -x squashfs" alias mount="mount -t nosquashfs,nocgroup,nsfs,tmpfs,fuse" My rationale: The output of df and mount are currently cluttered because of snap mounts. df & mount information on snap packages are usually irrelevant for most end-users and rather create more confusion. ** Affects: bash (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1909143 Title: df & mount aliases to hide reports for snap mounts Status in bash package in Ubuntu: New Bug description: I would purpose the following aliases as defaults for Hirsute: alias df="df -x squashfs" alias mount="mount -t nosquashfs,nocgroup,nsfs,tmpfs,fuse" My rationale: The output of df and mount are currently cluttered because of snap mounts. df & mount information on snap packages are usually irrelevant for most end-users and rather create more confusion. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1909143/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1903048] Re: [SRU] Bluetooth won't activate on the pi 400
I installed version 5.55-0ubuntu2 did not make a difference. in journalctl is this : bluetoothd[40120]: src/main.c:parse_controller_config() Key file does not have group “Controller” -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1903048 Title: [SRU] Bluetooth won't activate on the pi 400 Status in bluez package in Ubuntu: Triaged Status in bluez source package in Groovy: Fix Released Status in bluez source package in Hirsute: Triaged Bug description: [Impact] Without these patches, Bluetooth is inoperable on the recently released Raspberry Pi 400. [Test Case] * Boot the Ubuntu Desktop for Pi image on a Pi 400. * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is not enabled and attempting to activate it fails * Enable the -proposed repository for the release (groovy) * sudo apt update * sudo apt install bluez * sudo reboot * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is active and that Bluetooth devices (e.g. mice, mobile phones, headphones, etc.) can connect and operate correctly [Regression Potential] Extremely low (on groovy in particular, this has the same version of bluez as hirsute). The only significant risk is to non-Pi platforms or dongles which also use the Broadcom 43xx (or Cypress 305) chips for Bluetooth which might be inadvertently affected by these patches. [Original Description] The new Pi 400 has a slightly different Wifi/BT chip to the Pi4. Whilst wifi works happily, Bluetooth fails to operate. This doesn't appear to be an issue with either the firmware (the latest versions from upstream Raspbian have been tried), or the kernel (a known-good raspi kernel has been tested under Ubuntu), but with Bluez itself. Specifically, tracing the initialization with btmon on Raspbian and Ubuntu, the stack consistently fails when attempting to "Set Default PHY" on the latter. Curiously, under Ubuntu the adapter also appears to lack a MAC address. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1909152] [NEW] color calibration fails when using gnome gui on 20.10
Public bug reported: in the past, I've used DisplayCalGUI to calibrate my displays. however, that software hasn't been updated to use Python3 properly, so it doesn't run on recent Ubuntu releases. I thought I'd try the builtin gnome calibration, but it seems completely broken on 20.10. I've tried two difference systems with fresh minimal installs, each has a different display and a different brand of colour calibration hardware. in both cases, they get to testing the coloured swatches, and fail, with an error saying: "Calibration failed! An internal error occurred that could not be recovered. You can remove the calibration device." however, looking in the output from `journalctl`, colord seems to claim that it succeeded in generating a profile. So I'm guessing there's something broken in the integration between colord and gnome-settings? all I know is it reports that it failed, and gnome doesn't show any new profile to use. here's the `journalctl` output: Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: No of test patches = 64 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Omitted 0 zero measurements Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Find white & black points Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Initial white point = 1.051779 0.999535 0.796168 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Creating matrix... Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: [46B blob data] Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Matrix = 0.615651 0.622859 0.645454 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: 0.647113 0.653246 0.680660 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: 0.531396 0.531212 0.553325 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Creating matrix and single gamma curve... Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: [26B blob data] Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Matrix = 0.009811 0.389211 0.558809 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: 0.144281 0.347751 0.505066 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: 0.198306 0.283542 0.312788 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Gamma = -1.574397 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Doing White point fine tune: Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Before fine tune, rel WP = XYZ 0.95783065 0.99709777 0.79463644, Lab 99.887672 -0.619729 2.283133 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: After fine tune, rel WP = XYZ 0.96420288 1. 0.82490540, Lab 100.00 0.00 0.00 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: abs WP = XYZ 1.04542265 0.99666916 0.76687003, Lab 99.871064 14.218222 4.582465 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Black point XYZ = 1.04542265 0.99666916 0.76687003, Lab = 99.871064 14.218222 4.582465 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Scaling White Point by 1.003342 to make Y = 1.0 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Display Luminance = 0.940928 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: White point XYZ = 1.048916 1.00 0.769433 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Black point XYZ = 1.048916 1.00 0.769433 Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Done gamma/shaper and matrix creation Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Profile done ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: colord 1.4.4-2build1 ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Wed Dec 23 13:51:43 2020 SourcePackage: colord UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: colord (Ubuntu) Importance: Undecided Status: New ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ** Also affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1909152 Title: color calibration fails when using gnome gui on 20.10 Status in colord package in Ubuntu: New Status in gnome-control-center package in Ubuntu: New Bug description: in the past, I've used DisplayCalGUI to calibrate my displays. however, that software hasn't been updated to use Python3 properly, so it doesn't run on recent Ubuntu releases. I thought I'd try the builtin gnome calibration, but it seems completely broken on 20.10. I've tried two difference systems with fresh minimal installs, each has a different display and a diffe
[Touch-packages] [Bug 1909173] [NEW] Python-apt for Python2.x is missing from repositories for Groovy
Public bug reported: I can't seem to find clear cut explanation why python-apt is missing from the repositories. AFAICT, there was a security release Dec 10th? If this was intentional or not, I'll leave this issue here, at least for those who run up against this issue and don't know why. Description:Ubuntu 20.10 Release:20.10 ** Affects: python-apt (Ubuntu) Importance: Undecided Status: New ** Tags: packaging -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1909173 Title: Python-apt for Python2.x is missing from repositories for Groovy Status in python-apt package in Ubuntu: New Bug description: I can't seem to find clear cut explanation why python-apt is missing from the repositories. AFAICT, there was a security release Dec 10th? If this was intentional or not, I'll leave this issue here, at least for those who run up against this issue and don't know why. Description:Ubuntu 20.10 Release:20.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1909173/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1909173] Re: Python-apt for Python2.x is missing from repositories for Groovy
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1909173 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. --- python-apt | 2.1.3ubuntu1| groovy | source python-apt | 2.1.3ubuntu1.2 | groovy-security | source python-apt | 2.1.3ubuntu1.2 | groovy-updates | source https://launchpad.net/ubuntu/+source/python-apt/+changelog -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1909173 Title: Python-apt for Python2.x is missing from repositories for Groovy Status in python-apt package in Ubuntu: New Bug description: I can't seem to find clear cut explanation why python-apt is missing from the repositories. AFAICT, there was a security release Dec 10th? If this was intentional or not, I'll leave this issue here, at least for those who run up against this issue and don't know why. Description:Ubuntu 20.10 Release:20.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1909173/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp