[Touch-packages] [Bug 1915903] Re: Up-to-date net-tools package tells me to recompile it
[Expired for net-tools (Ubuntu) because there has been no activity for 60 days.] ** Changed in: net-tools (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to net-tools in Ubuntu. https://bugs.launchpad.net/bugs/1915903 Title: Up-to-date net-tools package tells me to recompile it Status in net-tools package in Ubuntu: Expired Bug description: Attempting to run netstat -f inet results in netstat: feature `AF BLUETOOTH' not supported. Please recompile `net-tools' with newer kernel source or full configuration. Both my net-tools and kernel packages are fully up-to-date. (Version details are in the report collected by ubuntu-bug.) This looks to me like a package inconsistency. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: net-tools 1.60+git20161116.90da8a0-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-135.139-generic 4.15.18 Uname: Linux 4.15.0-135-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 Date: Wed Feb 17 09:02:39 2021 Dependencies: gcc-8-base 8.4.0-1ubuntu1~18.04 libc6 2.27-3ubuntu1.4 libgcc1 1:8.4.0-1ubuntu1~18.04 libpcre3 2:8.39-9 libselinux1 2.7-2build2 InstallationDate: Installed on 2017-12-02 (1172 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: net-tools UpgradeStatus: Upgraded to bionic on 2018-09-04 (896 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-tools/+bug/1915903/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925057] Re: [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or crackling sound
when problems happens, please run: $sudo sh -c 'echo 1 > /sys/module/snd_hda_codec/parameters/dump_coef' Then run alsa-info to collect an alsa-info.txt (bad) Then poweroff the machine and poweron it, make sure the audio works normally, run: $sudo sh -c 'echo 1 > /sys/module/snd_hda_codec/parameters/dump_coef' Then run alsa-info to collect an alsa-info.txt (good) and upload the alsa-info.txt-bad and alsa-info.txt-good, let us compare them. -- 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/1925057 Title: [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or crackling sound Status in alsa-driver package in Ubuntu: New Bug description: Hello, I'm using Ubuntu together with Windows on my laptop. If I boot in Ubuntu after Windows sound doesn't work well (instead of system sounds I can hear only shot noise). To fix the issue I need to completely shut down the system (call Power Off via Ubuntu GUI) and then boot again in Ubuntu. Please note, that reboot (called via Ubuntu GUI) doesn't help to fix the issue. Expected result: sound works well regardless of boot history. Actual result: every time I boot in Ubuntu after Windows sound doesn't work. Issue occurrence: 100%. Environment: $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ uname -a Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Thank you in advance! ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gluttton 1640 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Apr 19 19:37:56 2021 InstallationDate: Installed on 2021-03-06 (43 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: кві 19 19:37:21 tiptop pulseaudio[958]: After module unload, module 'module-null-sink' was still loaded! кві 19 19:37:21 tiptop systemd[944]: pulseaudio.service: Succeeded. кві 19 19:37:40 tiptop systemd[944]: pulseaudio.service: Succeeded. кві 19 19:37:50 tiptop systemd[944]: pulseaudio.socket: Succeeded. Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or crackling sound UpgradeStatus: Upgraded to hirsute on 2021-03-06 (43 days ago) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1925057/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1923150] Re: unexpected error pop-up after 'apt install nvidia-driver-455'
** Changed in: oem-priority Assignee: Yuan-Chen Cheng (ycheng-twn) => Alex Tu (alextu) -- 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/1923150 Title: unexpected error pop-up after 'apt install nvidia-driver-455' Status in OEM Priority Project: Confirmed Status in apt package in Ubuntu: Invalid Status in nvidia-graphics-drivers-455 package in Ubuntu: Invalid Bug description: Ubuntu info: $ lsb_release -rd Description:Ubuntu 20.04.1 LTS (fossa-spark-cml X52) Release 20.04 Full reproduce step 1. nvidia-driver-455 455.45.01-0ubuntu0.20.04.1 is installed in the first place, without all i386 pkg installed. 2. run update-manager to do upgrade. 3. it will show error after download deb and didn't upgrade anything. Per test with the command to do the upgrade, it will have an extra error message, but it will just upgrade and install recommended i386 debs. The error msgs are: E: Could not configure 'libc6:i386'. E: Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) Short way to get the error: # apt-get install libgcc-s1:i386 --dry-run Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: apt-clone archdetect-deb dctrl-tools dmraid gir1.2-timezonemap-1.0 gir1.2-xkl-1.0 kpartx kpartx-boot libdebian-installer4 libdmraid1.0.0.rc16 libtimezonemap-data libtimezonemap1 python3-icu python3-pam rdate Use 'apt autoremove' to remove them. The following additional packages will be installed: gcc-10-base:i386 libc6 libc6:i386 libcrypt1:i386 libidn2-0:i386 libunistring2:i386 Suggested packages: glibc-doc glibc-doc:i386 locales:i386 The following NEW packages will be installed: gcc-10-base:i386 libc6:i386 libcrypt1:i386 libgcc-s1:i386 libidn2-0:i386 libunistring2:i386 The following packages will be upgraded: libc6 1 upgraded, 6 newly installed, 0 to remove and 235 not upgraded. Inst libc6 [2.31-0ubuntu9.1] (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [amd64]) Inst libc6:i386 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [i386]) [] Conf libc6 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [amd64]) [] Inst libgcc-s1:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) [] Inst gcc-10-base:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) [] Conf gcc-10-base:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) [] Inst libcrypt1:i386 (1:4.4.10-10ubuntu4 Ubuntu:20.04/focal [i386]) Conf libgcc-s1:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) Conf libcrypt1:i386 (1:4.4.10-10ubuntu4 Ubuntu:20.04/focal [i386]) Conf libc6:i386 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [i386]) Inst libunistring2:i386 (0.9.10-2 Ubuntu:20.04/focal [i386]) Inst libidn2-0:i386 (2.2.0-2 Ubuntu:20.04/focal [i386]) Conf libunistring2:i386 (0.9.10-2 Ubuntu:20.04/focal [i386]) Conf libidn2-0:i386 (2.2.0-2 Ubuntu:20.04/focal [i386]) E: Could not configure 'libc6:i386'. E: Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) For now, we think the above Error is the root cause of update-manager failure. --- This happens as upgrade package nvidia-driver-455 from 455.45.01-0ubuntu0.20.04.1 to 460.39-0ubuntu0.20.04.1. for more detail, please check the attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1923150/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1916485] Re: test -x fails inside shell scripts in containers
Before I change the status of this bug, I would like to report my findings here. I am testing things on a Bionic s390x machine with everything up-to- date: # apt policy systemd systemd: Installed: 237-3ubuntu10.46 ... # apt policy containerd containerd: Installed: 1.4.4-0ubuntu1~18.04.2 ... # apt policy docker.io docker.io: Installed: 20.10.2-0ubuntu1~18.04.2 ... # apt policy runc runc: Installed: 1.0.0~rc93-0ubuntu1~18.04.1 ... Following the reproduction steps listed in the Description section still fail for me: # systemd-nspawn Spawning container h on /root/h. Press ^] three times within 1s to kill container. # bash -c 'test -x /usr/bin/gpg || echo Fail' Fail When I'm in a hirsute Docker container, it also fails: $ docker run -it --rm ubuntu:hirsute root@78506947b11f:/# bash -c 'test -x /usr/bin/gpg || echo Fail' Fail This is impacting the build of the 21.04 OCI images on s390x (amd64, arm64 and ppc64el succeed). I'm still not sure what's causing this, nor why this is happening only on s390x. I will post more details when I have them. -- 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/1916485 Title: test -x fails inside shell scripts in containers Status in docker.io package in Ubuntu: New Status in glibc package in Ubuntu: Opinion Status in libseccomp package in Ubuntu: Fix Committed Status in runc package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in docker.io source package in Xenial: New Status in libseccomp source package in Xenial: New Status in runc source package in Xenial: New Status in systemd source package in Xenial: Invalid Status in docker.io source package in Bionic: New Status in libseccomp source package in Bionic: New Status in runc source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Released Status in docker.io source package in Focal: New Status in libseccomp source package in Focal: New Status in runc source package in Focal: Fix Released Status in systemd source package in Focal: Fix Released Status in docker.io source package in Groovy: New Status in libseccomp source package in Groovy: New Status in runc source package in Groovy: Fix Released Status in systemd source package in Groovy: Fix Released Status in docker.io source package in Hirsute: New Status in libseccomp source package in Hirsute: Fix Committed Status in runc source package in Hirsute: Fix Released Status in systemd source package in Hirsute: Fix Released Status in systemd package in Debian: Fix Released Bug description: (SRU template for systemd) [impact] bash (and some other shells) builtin test command -x operation fails [test case] on any affected host system, start nspawn container, e.g.: $ sudo apt install systemd-container $ wget https://cloud-images.ubuntu.com/hirsute/current/hirsute-server-cloudimg-amd64-root.tar.xz $ mkdir h $ cd h $ tar xvf ../hirsute-server-cloudimg-amd64-root.tar.xz $ sudo systemd-nspawn Then from a bash shell, verify if test -x works: root@h:~# ls -l /usr/bin/gpg -rwxr-xr-x 1 1000 1000 1083472 Jan 16 09:53 /usr/bin/gpg root@h:~# test -x /usr/bin/gpg || echo "fail" fail [regression potential] any regression would likely occur during a syscall, most likely faccessat2(), or during other syscalls. [scope] this is needed for b/f this is fixed upstream by commit bcf08acbffdee0d6360d3c31d268e73d0623e5dc which is in 247 and later, so this is fixed in h this was pulled into Debian at version 246.2 in commit e80c5e5371ab77792bae94e0f8c5e85a4237e6eb, so this is fixed in g in x, the entire systemd seccomp code is completely different and the patch doesn't apply, nor does it appear to be needed, as the problem doesn't reproduce in a h container under x. [other info] this needs fixing in libseccomp as well [original description] glibc regression causes test -x to fail inside scripts inside docker/podman, dash and bash are broken, mksh and zsh are fine: root@0df2ce5d7a46:/# test -x /usr/bin/gpg || echo Fail root@0df2ce5d7a46:/# dash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# mksh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# zsh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# root@0df2ce5d7a46:/# zsh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# mksh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# dash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail The -f flag works, as does /usr/bin/test: # bash -c "test -f /usr/bin/gpg || echo Fail" # bash -c "/usr/bin/test -x /usr/bin/gpg || echo Fail" # [Original bug
[Touch-packages] [Bug 1924494] Re: Systemd shutdown order unmounts filesystem used by qemu/kvm guest before shutting down the guest
** Package changed: systemd (Ubuntu) => libvirt (Ubuntu) -- 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/1924494 Title: Systemd shutdown order unmounts filesystem used by qemu/kvm guest before shutting down the guest Status in libvirt package in Ubuntu: New Bug description: Last night I started a reboot without manually shutting down a qemu/kvm guest first. After X went down a bunch of I/O errors associated with a network block device that contains a NTFS filesystem showed up on the console. I noticed that the umount.target had been reached but the virt-guest-shutdown.target was still waiting for the guest to shut down, until it timed out. Wouldn't it be beneficial for all guests to be shutdown before unmounting all filesystems? ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: systemd 246.6-1ubuntu1.3 ProcVersionSignature: Ubuntu 5.8.0-49.55-generic 5.8.18 Uname: Linux 5.8.0-49-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Apr 15 08:35:48 2021 InstallationDate: Installed on 2021-01-17 (88 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: HP HP ZBook 15u G6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-49-generic root=UUID=25df7fed-1baf-421e-941e-7f7c280db6e8 ro iommu=pt intel_iommu=on default_hugepagesz=1G hugepagesz=1G hugepages=6 pcie_aspm.policy=performance SourcePackage: systemd UpgradeStatus: Upgraded to groovy on 2021-04-08 (6 days ago) dmi.bios.date: 01/08/2021 dmi.bios.release: 8.1 dmi.bios.vendor: HP dmi.bios.version: R70 Ver. 01.08.01 dmi.board.name: 8549 dmi.board.vendor: HP dmi.board.version: KBC Version 52.67.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 82.103 dmi.modalias: dmi:bvnHP:bvrR70Ver.01.08.01:bd01/08/2021:br8.1:efr82.103:svnHP:pnHPZBook15uG6:pvr:rvnHP:rn8549:rvrKBCVersion52.67.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook dmi.product.name: HP ZBook 15u G6 dmi.product.sku: 9AP56LP#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1924494/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925057] [NEW] [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or crackling sound
Public bug reported: Hello, I'm using Ubuntu together with Windows on my laptop. If I boot in Ubuntu after Windows sound doesn't work well (instead of system sounds I can hear only shot noise). To fix the issue I need to completely shut down the system (call Power Off via Ubuntu GUI) and then boot again in Ubuntu. Please note, that reboot (called via Ubuntu GUI) doesn't help to fix the issue. Expected result: sound works well regardless of boot history. Actual result: every time I boot in Ubuntu after Windows sound doesn't work. Issue occurrence: 100%. Environment: $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ uname -a Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Thank you in advance! ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gluttton 1640 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Apr 19 19:37:56 2021 InstallationDate: Installed on 2021-03-06 (43 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: кві 19 19:37:21 tiptop pulseaudio[958]: After module unload, module 'module-null-sink' was still loaded! кві 19 19:37:21 tiptop systemd[944]: pulseaudio.service: Succeeded. кві 19 19:37:40 tiptop systemd[944]: pulseaudio.service: Succeeded. кві 19 19:37:50 tiptop systemd[944]: pulseaudio.socket: Succeeded. Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or crackling sound UpgradeStatus: Upgraded to hirsute on 2021-03-06 (43 days ago) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- 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/1925057 Title: [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or crackling sound Status in alsa-driver package in Ubuntu: New Bug description: Hello, I'm using Ubuntu together with Windows on my laptop. If I boot in Ubuntu after Windows sound doesn't work well (instead of system sounds I can hear only shot noise). To fix the issue I need to completely shut down the system (call Power Off via Ubuntu GUI) and then boot again in Ubuntu. Please note, that reboot (called via Ubuntu GUI) doesn't help to fix the issue. Expected result: sound works well regardless of boot history. Actual result: every time I boot in Ubuntu after Windows sound doesn't work. Issue occurrence: 100%. Environment: $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ uname -a Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Thank you in advance! ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gluttton 1640 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Apr 19 19:37:56 2021 InstallationDate: Installed on 2021-03-06 (43 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test
[Touch-packages] [Bug 1891548] Re: autofs-ldap's /etc/ldap/schema/autofs.schema crashes slapd
Since this appears to have just required a fix to autofs, I'm closing the openldap task. If there actually is any followup work needed for openldap please reopen with additional detail of what needs done. ** Changed in: openldap (Ubuntu) Status: New => 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/1891548 Title: autofs-ldap's /etc/ldap/schema/autofs.schema crashes slapd Status in autofs package in Ubuntu: Fix Released Status in openldap package in Ubuntu: Fix Released Status in autofs package in Debian: Fix Released Bug description: Ubuntu Release: # lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 Version of packages in use: # dpkg -l autofs autofs-ldap slapd | grep '^ii' ii autofs 5.1.6-2ubuntu0.1 amd64kernel-based automounter for Linux ii autofs-ldap5.1.6-2ubuntu0.1 amd64LDAP map support for autofs ii slapd 2.4.49+dfsg-2ubuntu1.3 amd64OpenLDAP server (slapd) Expected: No errors from slaptest Actual Output: 5f359370 /etc/ldap/schema/autofs.schema: line 14 attributetype: AttributeType inappropriate matching rule: "caseExactMatch" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1891548/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1924852] Re: Selected output device in Sound settings is not persisted across restarts
it sounds similar to bug #1877194 could you try if commenting out switch-on-connect in /etc/pulse/default.pa fixes the issue for you? -- 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/1924852 Title: Selected output device in Sound settings is not persisted across restarts Status in gnome-control-center package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Incomplete Bug description: # Introduction My computer has multiple audio devices, so I had to select the correct one in the "Sound" section of "Settings". This worked fine, except that whenever I restart the computer this setting resets to the original one. Effectively I have to visit the sound settings on each system startup in order to hear anything. # How to reproduce 1. have system with multiple audio outputs 2. open sound settings 3. select non-default output device 4. restart computer 5. open sound settings # Expected result Selected audio device is the same as the one selected right before restart. # Actual result The active output device is the original default one (i.e. not the one that we selected). # System information $ lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 $ apt-cache policy gnome-control-center gnome-control-center: Installed: 1:3.36.5-0ubuntu1 Candidate: 1:3.36.5-0ubuntu1 Version table: *** 1:3.36.5-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.36.1-1ubuntu5 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1924852/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1857552] Re: [81NX, Realtek ALC285, Speaker, Internal] No sound at all
That's awesome ! I can confirm that your patch works on Ubuntu 20.04. I can finally enjoy fully functional Linux on my laptop (Lenovo S740 15"). Thank you so much ! -- 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/1857552 Title: [81NX, Realtek ALC285, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: In dual boot machine (lenove S740 laptop) sound is fine on windows side. Headphones work on linux side, but there is no sound at all from speakers on the ubuntu 19.10 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hu-mka 1574 F pulseaudio hu-mka 5552 F alsamixer CurrentDesktop: ubuntu:GNOME Date: Wed Dec 25 20:14:17 2019 InstallationDate: Installed on 2019-12-22 (3 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1126 F pulseaudio hu-mka 1574 F pulseaudio hu-mka 5552 F alsamixer Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [81NX, Realtek ALC285, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2019 dmi.bios.vendor: LENOVO dmi.bios.version: BKCN20WW(V1.02) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga S740-15IRH dmi.modalias: dmi:bvnLENOVO:bvrBKCN20WW(V1.02):bd07/15/2019:svnLENOVO:pn81NX:pvrLenovoYogaS740-15IRH:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYogaS740-15IRH: dmi.product.family: Yoga S740-15IRH dmi.product.name: 81NX dmi.product.sku: LENOVO_MT_81NX_BU_idea_FM_Yoga S740-15IRH dmi.product.version: Lenovo Yoga S740-15IRH dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1857552/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1916485] Re: test -x fails inside shell scripts in containers
This bug was fixed in the package runc - 1.0.0~rc93-0ubuntu1~18.04.1 --- runc (1.0.0~rc93-0ubuntu1~18.04.1) bionic; urgency=medium * Backport version 1.0.0~rc93-0ubuntu1 from Hirsute (LP: #1919322, LP: #1916485). - Use Go 1.13 to build it, with the default Go 1.10 it FTBFS. + d/control: b-d on golang-1.13-go instead of golang-any, + d/rules: add Go 1.13 to the $PATH. - d/rules: set GOCACHE to a temporary directory. dh-golang sets it to "off" which is not accepted by Go >= 1.12. - d/rules: set GO111MODULE to "off" to avoid getting modules info online. -- Lucas Kanashiro Tue, 16 Mar 2021 15:47:19 -0300 -- 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/1916485 Title: test -x fails inside shell scripts in containers Status in docker.io package in Ubuntu: New Status in glibc package in Ubuntu: Opinion Status in libseccomp package in Ubuntu: Fix Committed Status in runc package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in docker.io source package in Xenial: New Status in libseccomp source package in Xenial: New Status in runc source package in Xenial: New Status in systemd source package in Xenial: Invalid Status in docker.io source package in Bionic: New Status in libseccomp source package in Bionic: New Status in runc source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Released Status in docker.io source package in Focal: New Status in libseccomp source package in Focal: New Status in runc source package in Focal: Fix Released Status in systemd source package in Focal: Fix Released Status in docker.io source package in Groovy: New Status in libseccomp source package in Groovy: New Status in runc source package in Groovy: Fix Released Status in systemd source package in Groovy: Fix Released Status in docker.io source package in Hirsute: New Status in libseccomp source package in Hirsute: Fix Committed Status in runc source package in Hirsute: Fix Released Status in systemd source package in Hirsute: Fix Released Status in systemd package in Debian: Fix Released Bug description: (SRU template for systemd) [impact] bash (and some other shells) builtin test command -x operation fails [test case] on any affected host system, start nspawn container, e.g.: $ sudo apt install systemd-container $ wget https://cloud-images.ubuntu.com/hirsute/current/hirsute-server-cloudimg-amd64-root.tar.xz $ mkdir h $ cd h $ tar xvf ../hirsute-server-cloudimg-amd64-root.tar.xz $ sudo systemd-nspawn Then from a bash shell, verify if test -x works: root@h:~# ls -l /usr/bin/gpg -rwxr-xr-x 1 1000 1000 1083472 Jan 16 09:53 /usr/bin/gpg root@h:~# test -x /usr/bin/gpg || echo "fail" fail [regression potential] any regression would likely occur during a syscall, most likely faccessat2(), or during other syscalls. [scope] this is needed for b/f this is fixed upstream by commit bcf08acbffdee0d6360d3c31d268e73d0623e5dc which is in 247 and later, so this is fixed in h this was pulled into Debian at version 246.2 in commit e80c5e5371ab77792bae94e0f8c5e85a4237e6eb, so this is fixed in g in x, the entire systemd seccomp code is completely different and the patch doesn't apply, nor does it appear to be needed, as the problem doesn't reproduce in a h container under x. [other info] this needs fixing in libseccomp as well [original description] glibc regression causes test -x to fail inside scripts inside docker/podman, dash and bash are broken, mksh and zsh are fine: root@0df2ce5d7a46:/# test -x /usr/bin/gpg || echo Fail root@0df2ce5d7a46:/# dash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# mksh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# zsh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# root@0df2ce5d7a46:/# zsh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# mksh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# dash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail The -f flag works, as does /usr/bin/test: # bash -c "test -f /usr/bin/gpg || echo Fail" # bash -c "/usr/bin/test -x /usr/bin/gpg || echo Fail" # [Original bug report] root@84b750e443f8:/# lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 root@84b750e443f8:/# dpkg -l gnupg apt Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture
[Touch-packages] [Bug 1916485] Re: test -x fails inside shell scripts in containers
This bug was fixed in the package runc - 1.0.0~rc93-0ubuntu1~20.04.1 --- runc (1.0.0~rc93-0ubuntu1~20.04.1) focal; urgency=medium * Backport version 1.0.0~rc93-0ubuntu1 from Hirsute (LP: #1919322, LP: #1916485). -- Lucas Kanashiro Tue, 16 Mar 2021 15:34:35 -0300 ** Changed in: runc (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1916485 Title: test -x fails inside shell scripts in containers Status in docker.io package in Ubuntu: New Status in glibc package in Ubuntu: Opinion Status in libseccomp package in Ubuntu: Fix Committed Status in runc package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in docker.io source package in Xenial: New Status in libseccomp source package in Xenial: New Status in runc source package in Xenial: New Status in systemd source package in Xenial: Invalid Status in docker.io source package in Bionic: New Status in libseccomp source package in Bionic: New Status in runc source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Released Status in docker.io source package in Focal: New Status in libseccomp source package in Focal: New Status in runc source package in Focal: Fix Released Status in systemd source package in Focal: Fix Released Status in docker.io source package in Groovy: New Status in libseccomp source package in Groovy: New Status in runc source package in Groovy: Fix Released Status in systemd source package in Groovy: Fix Released Status in docker.io source package in Hirsute: New Status in libseccomp source package in Hirsute: Fix Committed Status in runc source package in Hirsute: Fix Released Status in systemd source package in Hirsute: Fix Released Status in systemd package in Debian: Fix Released Bug description: (SRU template for systemd) [impact] bash (and some other shells) builtin test command -x operation fails [test case] on any affected host system, start nspawn container, e.g.: $ sudo apt install systemd-container $ wget https://cloud-images.ubuntu.com/hirsute/current/hirsute-server-cloudimg-amd64-root.tar.xz $ mkdir h $ cd h $ tar xvf ../hirsute-server-cloudimg-amd64-root.tar.xz $ sudo systemd-nspawn Then from a bash shell, verify if test -x works: root@h:~# ls -l /usr/bin/gpg -rwxr-xr-x 1 1000 1000 1083472 Jan 16 09:53 /usr/bin/gpg root@h:~# test -x /usr/bin/gpg || echo "fail" fail [regression potential] any regression would likely occur during a syscall, most likely faccessat2(), or during other syscalls. [scope] this is needed for b/f this is fixed upstream by commit bcf08acbffdee0d6360d3c31d268e73d0623e5dc which is in 247 and later, so this is fixed in h this was pulled into Debian at version 246.2 in commit e80c5e5371ab77792bae94e0f8c5e85a4237e6eb, so this is fixed in g in x, the entire systemd seccomp code is completely different and the patch doesn't apply, nor does it appear to be needed, as the problem doesn't reproduce in a h container under x. [other info] this needs fixing in libseccomp as well [original description] glibc regression causes test -x to fail inside scripts inside docker/podman, dash and bash are broken, mksh and zsh are fine: root@0df2ce5d7a46:/# test -x /usr/bin/gpg || echo Fail root@0df2ce5d7a46:/# dash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# mksh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# zsh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# root@0df2ce5d7a46:/# zsh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# mksh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# dash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail The -f flag works, as does /usr/bin/test: # bash -c "test -f /usr/bin/gpg || echo Fail" # bash -c "/usr/bin/test -x /usr/bin/gpg || echo Fail" # [Original bug report] root@84b750e443f8:/# lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 root@84b750e443f8:/# dpkg -l gnupg apt Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-===--== ii apt2.1.20 amd64commandline package manager ii gnupg 2.2.20-1ubuntu2 all GNU privacy guard - a free PGP replacement Hi, for 3 days
[Touch-packages] [Bug 1916485] Re: test -x fails inside shell scripts in containers
This bug was fixed in the package runc - 1.0.0~rc93-0ubuntu1~20.10.1 --- runc (1.0.0~rc93-0ubuntu1~20.10.1) groovy; urgency=medium * Backport version 1.0.0~rc93-0ubuntu1 from Hirsute (LP: #1919322, LP: #1916485). -- Lucas Kanashiro Tue, 16 Mar 2021 15:23:05 -0300 ** Changed in: runc (Ubuntu Groovy) Status: Fix Committed => Fix Released ** Changed in: runc (Ubuntu Focal) Status: Fix Committed => 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/1916485 Title: test -x fails inside shell scripts in containers Status in docker.io package in Ubuntu: New Status in glibc package in Ubuntu: Opinion Status in libseccomp package in Ubuntu: Fix Committed Status in runc package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in docker.io source package in Xenial: New Status in libseccomp source package in Xenial: New Status in runc source package in Xenial: New Status in systemd source package in Xenial: Invalid Status in docker.io source package in Bionic: New Status in libseccomp source package in Bionic: New Status in runc source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Released Status in docker.io source package in Focal: New Status in libseccomp source package in Focal: New Status in runc source package in Focal: Fix Released Status in systemd source package in Focal: Fix Released Status in docker.io source package in Groovy: New Status in libseccomp source package in Groovy: New Status in runc source package in Groovy: Fix Released Status in systemd source package in Groovy: Fix Released Status in docker.io source package in Hirsute: New Status in libseccomp source package in Hirsute: Fix Committed Status in runc source package in Hirsute: Fix Released Status in systemd source package in Hirsute: Fix Released Status in systemd package in Debian: Fix Released Bug description: (SRU template for systemd) [impact] bash (and some other shells) builtin test command -x operation fails [test case] on any affected host system, start nspawn container, e.g.: $ sudo apt install systemd-container $ wget https://cloud-images.ubuntu.com/hirsute/current/hirsute-server-cloudimg-amd64-root.tar.xz $ mkdir h $ cd h $ tar xvf ../hirsute-server-cloudimg-amd64-root.tar.xz $ sudo systemd-nspawn Then from a bash shell, verify if test -x works: root@h:~# ls -l /usr/bin/gpg -rwxr-xr-x 1 1000 1000 1083472 Jan 16 09:53 /usr/bin/gpg root@h:~# test -x /usr/bin/gpg || echo "fail" fail [regression potential] any regression would likely occur during a syscall, most likely faccessat2(), or during other syscalls. [scope] this is needed for b/f this is fixed upstream by commit bcf08acbffdee0d6360d3c31d268e73d0623e5dc which is in 247 and later, so this is fixed in h this was pulled into Debian at version 246.2 in commit e80c5e5371ab77792bae94e0f8c5e85a4237e6eb, so this is fixed in g in x, the entire systemd seccomp code is completely different and the patch doesn't apply, nor does it appear to be needed, as the problem doesn't reproduce in a h container under x. [other info] this needs fixing in libseccomp as well [original description] glibc regression causes test -x to fail inside scripts inside docker/podman, dash and bash are broken, mksh and zsh are fine: root@0df2ce5d7a46:/# test -x /usr/bin/gpg || echo Fail root@0df2ce5d7a46:/# dash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# mksh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# zsh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# root@0df2ce5d7a46:/# zsh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# mksh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# dash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail The -f flag works, as does /usr/bin/test: # bash -c "test -f /usr/bin/gpg || echo Fail" # bash -c "/usr/bin/test -x /usr/bin/gpg || echo Fail" # [Original bug report] root@84b750e443f8:/# lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 root@84b750e443f8:/# dpkg -l gnupg apt Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-===--== ii apt2.1.20 amd64commandline package manager ii gnupg
[Touch-packages] [Bug 1925025] Re: package packagekit 1.1.13-2ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1925025 Title: package packagekit 1.1.13-2ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in packagekit package in Ubuntu: New Bug description: no further information ProblemType: Package DistroRelease: Ubuntu 20.04 Package: packagekit 1.1.13-2ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Apr 19 14:17:46 2021 DuplicateSignature: package:packagekit:1.1.13-2ubuntu1.1 Setting up libcurl4:amd64 (7.68.0-1ubuntu2.5) ... dpkg: error processing package packagekit (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2020-09-22 (209 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: packagekit Title: package packagekit 1.1.13-2ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1925025/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925025] [NEW] package packagekit 1.1.13-2ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configurati
Public bug reported: no further information ProblemType: Package DistroRelease: Ubuntu 20.04 Package: packagekit 1.1.13-2ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Apr 19 14:17:46 2021 DuplicateSignature: package:packagekit:1.1.13-2ubuntu1.1 Setting up libcurl4:amd64 (7.68.0-1ubuntu2.5) ... dpkg: error processing package packagekit (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2020-09-22 (209 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: packagekit Title: package packagekit 1.1.13-2ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: packagekit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1925025 Title: package packagekit 1.1.13-2ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in packagekit package in Ubuntu: New Bug description: no further information ProblemType: Package DistroRelease: Ubuntu 20.04 Package: packagekit 1.1.13-2ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Apr 19 14:17:46 2021 DuplicateSignature: package:packagekit:1.1.13-2ubuntu1.1 Setting up libcurl4:amd64 (7.68.0-1ubuntu2.5) ... dpkg: error processing package packagekit (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2020-09-22 (209 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: packagekit Title: package packagekit 1.1.13-2ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1925025/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1924251] Re: Embedded browser display corruption under Wayland on Pi desktop
** No longer affects: mesa (Ubuntu) -- 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/1924251 Title: Embedded browser display corruption under Wayland on Pi desktop Status in gtk+3.0 package in Ubuntu: New Status in webkit2gtk package in Ubuntu: New Status in yelp package in Ubuntu: New Bug description: On the hirsute Pi desktop, under a wayland session with the "full" KMS overlay enabled, and "kms-modifiers" present in the org.gnome.mutter /experimental-features, the body of a window containing an HTML renderer (e.g. help text or a login page) displays corruption. These reproduction cases may not be entirely reliable given that *some* pages appear to render correctly, but I'll include a couple in the hopes of making it reliably reproducible: 1. Open the Lights Off game 2. Select "Help" from the menu 3. In the help window that appears, select any link "Basics", "Rules", and "Strategy" all reliably reproduce the issue for me, but "Help Translate" doesn't so you may need to click around some links until the corruption appears -- however, once it does even navigating back to the prior page which rendered happily now displays the same corruption. Another reproduction case: 1. Open the Settings application 2. Select the Online Applications option from the left 3. Select the Google entry in the list 4. The login window that appears always displays corruption for me The Microsoft option always reliably corrupts for me, but the Facebook one doesn't so again I wonder how reproducible this may be for others (might be worth trying several options if the first doesn't display corruption). The corruption appears in the form of "shredded" content as if a horizontal stride is set incorrectly somewhere, but only appears in the body of the window; the window decorations are unaffected. I'll attach a screenshot of the corrupted help window to illustrate. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1924251/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1924852] Re: Selected output device in Sound settings is not persisted across restarts
In my specific case I have two output devices: 1. an audio card integrated in the motherboard 2. and an external microphone that has a monitoring output jack Each of them results in two selectable options (there's always a second "Digital Output (S/PDIF)" prefixed one) in the Ubuntu settings for a total of 4. After startup the usb microphone is selected as the output device so I have to switch it to the integrated sound card analog output. (you can see details about each device in the `pactl list sinks` output in my "workaround" comment) Also whenever I connect my guitar amp (also acts as sound output) it is automatically selected as the active device and disconnecting it results in the microphone being selected again no matter what I had selected before connecting the amp. There is no HDMI involved anywhere. -- 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/1924852 Title: Selected output device in Sound settings is not persisted across restarts Status in gnome-control-center package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Incomplete Bug description: # Introduction My computer has multiple audio devices, so I had to select the correct one in the "Sound" section of "Settings". This worked fine, except that whenever I restart the computer this setting resets to the original one. Effectively I have to visit the sound settings on each system startup in order to hear anything. # How to reproduce 1. have system with multiple audio outputs 2. open sound settings 3. select non-default output device 4. restart computer 5. open sound settings # Expected result Selected audio device is the same as the one selected right before restart. # Actual result The active output device is the original default one (i.e. not the one that we selected). # System information $ lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 $ apt-cache policy gnome-control-center gnome-control-center: Installed: 1:3.36.5-0ubuntu1 Candidate: 1:3.36.5-0ubuntu1 Version table: *** 1:3.36.5-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.36.1-1ubuntu5 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1924852/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1924965] Re: Since 5.8.0-49 Screen flickers and becomes unusable
*** This bug is a duplicate of bug 1924624 *** https://bugs.launchpad.net/bugs/1924624 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1924778, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** This bug has been marked a duplicate of bug 1924778 i915 gen7 (Haswell and Ivy Bridge): Screen flickers and flashes with kernel 5.8.0-50 -- 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/1924965 Title: Since 5.8.0-49 Screen flickers and becomes unusable Status in linux package in Ubuntu: Confirmed Bug description: On ubuntu 20.10, x-org. On upgrade kernel to 5.8.0-49, and then -50, after the desktop has been on for a while the screen starts to flicker. Blocks of text go missing. Letters in a string disappear. Windows start flickering. The panel starts flickering and icons disappear and reappear. The keyboard and mouse seem intermittently responsive. After a restart it is OK for a little then starts again. ubuntu wayland is no better. Reverting to 5.8.0-48 fixes the problem completely. I originally commented on #1923632 but that has gone private, and I was asked to raise my own report. This one. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 19 07:42:02 2021 DistUpgraded: 2020-10-26 15:35:51,446 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [19da:b220] InstallationDate: Installed on 2018-05-24 (1060 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ZOTAC ZBOX-ID92/ZBOX-IQ01 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic root=UUID=25b009b8-6f92-4bff-8f3f-8a9700abf672 ro quiet splash fsck.mode=force fsck.repair=yes vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to groovy on 2020-10-26 (174 days ago) dmi.bios.date: 05/21/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B220P007 dmi.board.asset.tag: NA dmi.board.name: ZBOX-ID92/ZBOX-IQ01 dmi.board.vendor: ZOTAC dmi.board.version: 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.:bvrB220P007:bd05/21/2014:br4.6:svnZOTAC:pnZBOX-ID92/ZBOX-IQ01:pvrXX:rvnZOTAC:rnZBOX-ID92/ZBOX-IQ01:rvrXX:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: NA dmi.product.name: ZBOX-ID92/ZBOX-IQ01 dmi.product.sku: NA dmi.product.version: XX dmi.sys.vendor: ZOTAC version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924965/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1924184] Re: drive not showing
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1924184 Title: drive not showing Status in xorg package in Ubuntu: New Bug description: i coudnt find graphic drive ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-49-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 15 03:35:34 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0844] Subsystem: Dell Jet PRO [Radeon R5 M230 / R7 M260DX / Radeon 520 Mobile] [1028:0844] InstallationDate: Installed on 2021-04-13 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Vostro 3578 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-49-generic root=UUID=7cf915de-bb29-49e2-a9cc-0079efc75ed1 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/09/2020 dmi.bios.release: 1.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.0 dmi.board.name: 01Y7V4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.0:bd01/09/2020:br1.10:svnDellInc.:pnVostro3578:pvr:rvnDellInc.:rn01Y7V4:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3578 dmi.product.sku: 0844 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1924184/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1924903] Re: PulseAudio automatically switches to HDMI sound output on every boot
Thank you for your bug report. Similar issues are being discussed on https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/950 and there are proposed fixes if you feel like trying how they work for you ** Bug watch added: gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues #950 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/950 ** Changed in: pulseaudio (Ubuntu) Importance: Undecided => High -- 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/1924903 Title: PulseAudio automatically switches to HDMI sound output on every boot Status in pulseaudio package in Ubuntu: New Bug description: After upgrading to an AMD laptop (Thinkpad T14) and Ubuntu 21.04, when I boot the laptop my audio device has changed to HDMI, instead of remembering my headphones from last session. Screen remains plugged in, but takes a few seconds to wake up while booting. Commenting out load-module module-switch-on-port-available in /etc/pulse/default.pa fixes the issue. Might be related to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570 Devices: Family 17h (Models 10h-1fh) HD Audio Controller Speaker + Headphones Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) HD Audio Controller Subsystem: Lenovo Family 17h (Models 10h-1fh) HD Audio Controller HD-Audio Generic HDMI1 Output Multimedia controller: Advanced Micro Devices, Inc. [AMD] Raven/Raven2/FireFlight/Renoir Audio Processor (rev 01) Subsystem: Lenovo Raven/Raven2/FireFlight/Renoir Audio Processor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1924903/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1924852] Re: Selected output device in Sound settings is not persisted across restarts
Could you give some details on what output you select and which one is on after restart? There a known problems around HDMI handling, unsure if that's what you are seeing though ** Changed in: pulseaudio (Ubuntu) Importance: Undecided => Low ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- 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/1924852 Title: Selected output device in Sound settings is not persisted across restarts Status in gnome-control-center package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Incomplete Bug description: # Introduction My computer has multiple audio devices, so I had to select the correct one in the "Sound" section of "Settings". This worked fine, except that whenever I restart the computer this setting resets to the original one. Effectively I have to visit the sound settings on each system startup in order to hear anything. # How to reproduce 1. have system with multiple audio outputs 2. open sound settings 3. select non-default output device 4. restart computer 5. open sound settings # Expected result Selected audio device is the same as the one selected right before restart. # Actual result The active output device is the original default one (i.e. not the one that we selected). # System information $ lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 $ apt-cache policy gnome-control-center gnome-control-center: Installed: 1:3.36.5-0ubuntu1 Candidate: 1:3.36.5-0ubuntu1 Version table: *** 1:3.36.5-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.36.1-1ubuntu5 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1924852/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1924852] Re: Selected output device in Sound settings is not persisted across restarts
The settings only apply the changes, they have no backend side aiming at enforcing the changes again after a restart, it's a pulseaudio problem rather ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-control-center (Ubuntu) Status: New => Invalid -- 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/1924852 Title: Selected output device in Sound settings is not persisted across restarts Status in gnome-control-center package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Incomplete Bug description: # Introduction My computer has multiple audio devices, so I had to select the correct one in the "Sound" section of "Settings". This worked fine, except that whenever I restart the computer this setting resets to the original one. Effectively I have to visit the sound settings on each system startup in order to hear anything. # How to reproduce 1. have system with multiple audio outputs 2. open sound settings 3. select non-default output device 4. restart computer 5. open sound settings # Expected result Selected audio device is the same as the one selected right before restart. # Actual result The active output device is the original default one (i.e. not the one that we selected). # System information $ lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 $ apt-cache policy gnome-control-center gnome-control-center: Installed: 1:3.36.5-0ubuntu1 Candidate: 1:3.36.5-0ubuntu1 Version table: *** 1:3.36.5-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.36.1-1ubuntu5 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1924852/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1924988] Re: /usr/bin/software-properties-gtk:AttributeError:on_combobox_server_changed:__init__:__init__
*** This bug is a duplicate of bug 1909918 *** https://bugs.launchpad.net/bugs/1909918 ** This bug has been marked a duplicate of bug 1909918 software-properties-gtk crashed with AttributeError in __init__(): 'ElementTree' object has no attribute 'getiterator' -- 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/1924988 Title: /usr/bin/software-properties- gtk:AttributeError:on_combobox_server_changed:__init__:__init__ Status in software-properties package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.99.10, the problem page at https://errors.ubuntu.com/problem/ffd73a45905c770182316a4fe1a04be6acdabff8 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1924988/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1924988] [NEW] /usr/bin/software-properties-gtk:AttributeError:on_combobox_server_changed:__init__:__init__
*** This bug is a duplicate of bug 1909918 *** https://bugs.launchpad.net/bugs/1909918 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.99.10, the problem page at https://errors.ubuntu.com/problem/ffd73a45905c770182316a4fe1a04be6acdabff8 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: focal groovy hirsute kylin-21.04 -- 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/1924988 Title: /usr/bin/software-properties- gtk:AttributeError:on_combobox_server_changed:__init__:__init__ Status in software-properties package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.99.10, the problem page at https://errors.ubuntu.com/problem/ffd73a45905c770182316a4fe1a04be6acdabff8 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1924988/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1924936] Re: package udev 247.3-3ubuntu3 failed to install/upgrade: o subprocesso instalado, do pacote udev, o script post-installation retornou erro do status de saída 1
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1924936 Title: package udev 247.3-3ubuntu3 failed to install/upgrade: o subprocesso instalado, do pacote udev, o script post-installation retornou erro do status de saída 1 Status in systemd package in Ubuntu: New Bug description: chrome9 hc igp no video ProblemType: Package DistroRelease: Ubuntu 21.04 Package: udev 247.3-3ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12 Uname: Linux 5.11.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 AptOrdering: udev:amd64: Install libudev1:amd64: Install libudev1:amd64: Configure NULL: ConfigurePending Architecture: amd64 CustomUdevRuleFiles: 70-snap.snap-store.rules 70-snap.snapd.rules Date: Sat Apr 17 08:54:48 2021 ErrorMessage: o subprocesso instalado, do pacote udev, o script post-installation retornou erro do status de saída 1 InstallationDate: Installed on 2021-04-16 (1 days ago) InstallationMedia: MachineType: Positivo Positivo Mobile ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-14-generic root=UUID=5fa45bbb-28e2-47c2-a1d2-6055f13d7284 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.9, Python 3.9.4, python3-minimal, 3.9.2-2 PythonDetails: N/A SourcePackage: systemd Title: package udev 247.3-3ubuntu3 failed to install/upgrade: o subprocesso instalado, do pacote udev, o script post-installation retornou erro do status de saída 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/24/2007 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.asset.tag: Tag 12345 dmi.board.name: M550SE/M660SE dmi.board.vendor: CLEVO Co. dmi.board.version: VT6363A dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: VIA dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/24/2007:svnPositivo:pnPositivoMobile:pvrVT6363A:rvnCLEVOCo.:rnM550SE/M660SE:rvrVT6363A:cvnVIA:ct1:cvrN/A: dmi.product.name: Positivo Mobile dmi.product.version: VT6363A dmi.sys.vendor: Positivo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1924936/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1924964] Re: screen glitches
*** This bug is a duplicate of bug 1924624 *** https://bugs.launchpad.net/bugs/1924624 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1924778, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Tags added: haswell regression-update ** Package changed: xorg (Ubuntu) => linux-hwe (Ubuntu) ** Package changed: linux-hwe (Ubuntu) => linux-hwe-5.8 (Ubuntu) ** This bug has been marked a duplicate of bug 1924778 i915 gen7: Screen flickers and flashes with kernel 5.8.0-50 -- 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/1924964 Title: screen glitches Status in linux-hwe-5.8 package in Ubuntu: New Bug description: The issue is screen glitches issue is intermittent and temporary I think it started after a recent update But it gives the impression of an unstable system things flickering like a highlighted file in nautilus or in filezilla shadows under dialog boxes flickering the icons in the activities bar flickering like its displayed twice but scrolled vertically there are flickers of the other apps behind each, and some appear highlighted as they do when you put your mouse over them by scrolling them manually and running mouse over them seemed to get it to stop it didn't stop immediately but it did sometimes unresponsive apps like zoom sometimes zoom showing empty dialog a symptom that has existed for a while in nautilus when deep in a directory structure the top bar containing directory names flickers like its scrolling horizontally. I click on a higher folder to get it to stop all the above happen regardless of where the mouse is in gedit with multiple tabs open one tab (the tab) appeared blank no file name, no flickering Ubuntu 20.04.2 LTS Laptop model Asus N550JV old 16GB RAM mouse is new but basic wired J.BURROWS had to replace small one becuase button got stuck and it kept double clicking when i only single clicked Additional relevant I recently updated twice normally I wait a while perhaps a month before I update I think it started after a recent update Additional I do have many app running at the same time many opera windows 5+ with many tabs each 30+ which drains my ram 16GB Has both NVIDIA and built in INTEL graphics at the time NVIDIA is turned off using INTEL could be related to RAM or maybe mouse Additional minor after latest update my desktop wallpaper which was just ubuntu 20.04 default now appears black in settings I can choose others and they display, but choose the one it was it stays black actually I would like an option for black. save power graphics CPU I really would like a ubuntu without screen glitches Thank you for your time ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 19 15:58:48 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:11cd] Subsystem: ASUSTeK Computer Inc. GK107M [GeForce GT 750M] [1043:11cd] InstallationDate: Installed on 2020-09-08 (222 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: ASUSTeK COMPUTER INC. N550JV ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic root=UUID=18f3ecb2-cebb-4134-aa73-7d85d52089a3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/14/2013 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N550JV.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N550JV 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:
[Touch-packages] [Bug 1924965] Re: Since 5.8.0-49 Screen flickers and becomes unusable
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New => Confirmed -- 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/1924965 Title: Since 5.8.0-49 Screen flickers and becomes unusable Status in xorg package in Ubuntu: Confirmed Bug description: On ubuntu 20.10, x-org. On upgrade kernel to 5.8.0-49, and then -50, after the desktop has been on for a while the screen starts to flicker. Blocks of text go missing. Letters in a string disappear. Windows start flickering. The panel starts flickering and icons disappear and reappear. The keyboard and mouse seem intermittently responsive. After a restart it is OK for a little then starts again. ubuntu wayland is no better. Reverting to 5.8.0-48 fixes the problem completely. I originally commented on #1923632 but that has gone private, and I was asked to raise my own report. This one. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 19 07:42:02 2021 DistUpgraded: 2020-10-26 15:35:51,446 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [19da:b220] InstallationDate: Installed on 2018-05-24 (1060 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ZOTAC ZBOX-ID92/ZBOX-IQ01 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic root=UUID=25b009b8-6f92-4bff-8f3f-8a9700abf672 ro quiet splash fsck.mode=force fsck.repair=yes vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to groovy on 2020-10-26 (174 days ago) dmi.bios.date: 05/21/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B220P007 dmi.board.asset.tag: NA dmi.board.name: ZBOX-ID92/ZBOX-IQ01 dmi.board.vendor: ZOTAC dmi.board.version: 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.:bvrB220P007:bd05/21/2014:br4.6:svnZOTAC:pnZBOX-ID92/ZBOX-IQ01:pvrXX:rvnZOTAC:rnZBOX-ID92/ZBOX-IQ01:rvrXX:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: NA dmi.product.name: ZBOX-ID92/ZBOX-IQ01 dmi.product.sku: NA dmi.product.version: XX dmi.sys.vendor: ZOTAC version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1924965/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1924964] Re: screen glitches
Thank you for taking the time to report this bug and helping to make Ubuntu better. Bug reporting is mostly about finding & fixing problems thus preventing future users from hitting the same bug. I suspect a Support site would be more appropriate, eg. https://answers.launchpad.net/ubuntu. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community-support/709 -- 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/1924964 Title: screen glitches Status in xorg package in Ubuntu: New Bug description: The issue is screen glitches issue is intermittent and temporary I think it started after a recent update But it gives the impression of an unstable system things flickering like a highlighted file in nautilus or in filezilla shadows under dialog boxes flickering the icons in the activities bar flickering like its displayed twice but scrolled vertically there are flickers of the other apps behind each, and some appear highlighted as they do when you put your mouse over them by scrolling them manually and running mouse over them seemed to get it to stop it didn't stop immediately but it did sometimes unresponsive apps like zoom sometimes zoom showing empty dialog a symptom that has existed for a while in nautilus when deep in a directory structure the top bar containing directory names flickers like its scrolling horizontally. I click on a higher folder to get it to stop all the above happen regardless of where the mouse is in gedit with multiple tabs open one tab (the tab) appeared blank no file name, no flickering Ubuntu 20.04.2 LTS Laptop model Asus N550JV old 16GB RAM mouse is new but basic wired J.BURROWS had to replace small one becuase button got stuck and it kept double clicking when i only single clicked Additional relevant I recently updated twice normally I wait a while perhaps a month before I update I think it started after a recent update Additional I do have many app running at the same time many opera windows 5+ with many tabs each 30+ which drains my ram 16GB Has both NVIDIA and built in INTEL graphics at the time NVIDIA is turned off using INTEL could be related to RAM or maybe mouse Additional minor after latest update my desktop wallpaper which was just ubuntu 20.04 default now appears black in settings I can choose others and they display, but choose the one it was it stays black actually I would like an option for black. save power graphics CPU I really would like a ubuntu without screen glitches Thank you for your time ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 19 15:58:48 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:11cd] Subsystem: ASUSTeK Computer Inc. GK107M [GeForce GT 750M] [1043:11cd] InstallationDate: Installed on 2020-09-08 (222 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: ASUSTeK COMPUTER INC. N550JV ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic root=UUID=18f3ecb2-cebb-4134-aa73-7d85d52089a3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/14/2013 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N550JV.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N550JV 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.:bvrN550JV.204:bd05/14/2013:br4.6:svnASUSTeKCOMPUTERINC.:pnN550JV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN550JV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: N dmi.product.name: N550JV dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2
[Touch-packages] [Bug 1924965] Re: Since 5.8.0-49 Screen flickers and becomes unusable
** 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/1924965 Title: Since 5.8.0-49 Screen flickers and becomes unusable Status in xorg package in Ubuntu: New Bug description: On ubuntu 20.10, x-org. On upgrade kernel to 5.8.0-49, and then -50, after the desktop has been on for a while the screen starts to flicker. Blocks of text go missing. Letters in a string disappear. Windows start flickering. The panel starts flickering and icons disappear and reappear. The keyboard and mouse seem intermittently responsive. After a restart it is OK for a little then starts again. ubuntu wayland is no better. Reverting to 5.8.0-48 fixes the problem completely. I originally commented on #1923632 but that has gone private, and I was asked to raise my own report. This one. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 19 07:42:02 2021 DistUpgraded: 2020-10-26 15:35:51,446 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [19da:b220] InstallationDate: Installed on 2018-05-24 (1060 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ZOTAC ZBOX-ID92/ZBOX-IQ01 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic root=UUID=25b009b8-6f92-4bff-8f3f-8a9700abf672 ro quiet splash fsck.mode=force fsck.repair=yes vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to groovy on 2020-10-26 (174 days ago) dmi.bios.date: 05/21/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B220P007 dmi.board.asset.tag: NA dmi.board.name: ZBOX-ID92/ZBOX-IQ01 dmi.board.vendor: ZOTAC dmi.board.version: 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.:bvrB220P007:bd05/21/2014:br4.6:svnZOTAC:pnZBOX-ID92/ZBOX-IQ01:pvrXX:rvnZOTAC:rnZBOX-ID92/ZBOX-IQ01:rvrXX:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: NA dmi.product.name: ZBOX-ID92/ZBOX-IQ01 dmi.product.sku: NA dmi.product.version: XX dmi.sys.vendor: ZOTAC version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1924965/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1924965] [NEW] Since 5.8.0-49 Screen flickers and becomes unusable
You have been subscribed to a public bug: On ubuntu 20.10, x-org. On upgrade kernel to 5.8.0-49, and then -50, after the desktop has been on for a while the screen starts to flicker. Blocks of text go missing. Letters in a string disappear. Windows start flickering. The panel starts flickering and icons disappear and reappear. The keyboard and mouse seem intermittently responsive. After a restart it is OK for a little then starts again. ubuntu wayland is no better. Reverting to 5.8.0-48 fixes the problem completely. I originally commented on #1923632 but that has gone private, and I was asked to raise my own report. This one. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 19 07:42:02 2021 DistUpgraded: 2020-10-26 15:35:51,446 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [19da:b220] InstallationDate: Installed on 2018-05-24 (1060 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ZOTAC ZBOX-ID92/ZBOX-IQ01 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic root=UUID=25b009b8-6f92-4bff-8f3f-8a9700abf672 ro quiet splash fsck.mode=force fsck.repair=yes vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to groovy on 2020-10-26 (174 days ago) dmi.bios.date: 05/21/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B220P007 dmi.board.asset.tag: NA dmi.board.name: ZBOX-ID92/ZBOX-IQ01 dmi.board.vendor: ZOTAC dmi.board.version: 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.:bvrB220P007:bd05/21/2014:br4.6:svnZOTAC:pnZBOX-ID92/ZBOX-IQ01:pvrXX:rvnZOTAC:rnZBOX-ID92/ZBOX-IQ01:rvrXX:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: NA dmi.product.name: ZBOX-ID92/ZBOX-IQ01 dmi.product.sku: NA dmi.product.version: XX dmi.sys.vendor: ZOTAC version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3 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 third-party-packages ubuntu -- Since 5.8.0-49 Screen flickers and becomes unusable https://bugs.launchpad.net/bugs/1924965 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 1924969] [NEW] No WPA3(SAE) Password Identifier field in the Wi-Fi manager
Public bug reported: Hey, The latest WPA3(SAE Dragonfly)[802.11-2016, section 12.4] standard defines Password Identifiers as a way to tell the access point (AP) which password is being used, this allows for a single SSID to support multiple passwords, but when I tried to connect to WPA3 AP I was asked only for the password. In the Wi-Fi supplicant there is an option for "Password Identifiers" [search for "sae_password_id" in https://w1.fi/cgit/hostap/plain/wpa_supplicant/wpa_supplicant.conf] Quote from the Link: " # sae_password_id: SAE password identifier # This parameter can be used to set an identifier for the SAE password. By # default, no such identifier is used. If set, the specified identifier value # is used by the other peer to select which password to use for authentication. " So the network-manager should have and additional field for entering the Password Identifier when connecting to WAP3 network, currently no such option exist in the Wi-Fi manager. Tested on the following system and the bug reported above exists: System Settings: No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04 LTS Release: 20.04 Codename: focal Linux wallet 5.8.0-48-generic #54~20.04.1-Ubuntu SMP Sat Mar 20 13:40:25 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Wi-Fi card: Intel 6 AX200 Image for the Wi-Fi manager in WPA3 settings: https://i.ibb.co/rM6GB7c/wpa3-pwd-id.png ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Attachment added: "wpa3-pwd-id.png" https://bugs.launchpad.net/bugs/1924969/+attachment/5489707/+files/wpa3-pwd-id.png -- 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/1924969 Title: No WPA3(SAE) Password Identifier field in the Wi-Fi manager Status in network-manager package in Ubuntu: New Bug description: Hey, The latest WPA3(SAE Dragonfly)[802.11-2016, section 12.4] standard defines Password Identifiers as a way to tell the access point (AP) which password is being used, this allows for a single SSID to support multiple passwords, but when I tried to connect to WPA3 AP I was asked only for the password. In the Wi-Fi supplicant there is an option for "Password Identifiers" [search for "sae_password_id" in https://w1.fi/cgit/hostap/plain/wpa_supplicant/wpa_supplicant.conf] Quote from the Link: " # sae_password_id: SAE password identifier # This parameter can be used to set an identifier for the SAE password. By # default, no such identifier is used. If set, the specified identifier value # is used by the other peer to select which password to use for authentication. " So the network-manager should have and additional field for entering the Password Identifier when connecting to WAP3 network, currently no such option exist in the Wi-Fi manager. Tested on the following system and the bug reported above exists: System Settings: No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04 LTS Release: 20.04 Codename: focal Linux wallet 5.8.0-48-generic #54~20.04.1-Ubuntu SMP Sat Mar 20 13:40:25 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Wi-Fi card: Intel 6 AX200 Image for the Wi-Fi manager in WPA3 settings: https://i.ibb.co/rM6GB7c/wpa3-pwd-id.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1924969/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1924964] [NEW] screen glitches
Public bug reported: The issue is screen glitches issue is intermittent and temporary I think it started after a recent update But it gives the impression of an unstable system things flickering like a highlighted file in nautilus or in filezilla shadows under dialog boxes flickering the icons in the activities bar flickering like its displayed twice but scrolled vertically there are flickers of the other apps behind each, and some appear highlighted as they do when you put your mouse over them by scrolling them manually and running mouse over them seemed to get it to stop it didn't stop immediately but it did sometimes unresponsive apps like zoom sometimes zoom showing empty dialog a symptom that has existed for a while in nautilus when deep in a directory structure the top bar containing directory names flickers like its scrolling horizontally. I click on a higher folder to get it to stop all the above happen regardless of where the mouse is in gedit with multiple tabs open one tab (the tab) appeared blank no file name, no flickering Ubuntu 20.04.2 LTS Laptop model Asus N550JV old 16GB RAM mouse is new but basic wired J.BURROWS had to replace small one becuase button got stuck and it kept double clicking when i only single clicked Additional relevant I recently updated twice normally I wait a while perhaps a month before I update I think it started after a recent update Additional I do have many app running at the same time many opera windows 5+ with many tabs each 30+ which drains my ram 16GB Has both NVIDIA and built in INTEL graphics at the time NVIDIA is turned off using INTEL could be related to RAM or maybe mouse Additional minor after latest update my desktop wallpaper which was just ubuntu 20.04 default now appears black in settings I can choose others and they display, but choose the one it was it stays black actually I would like an option for black. save power graphics CPU I really would like a ubuntu without screen glitches Thank you for your time ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 19 15:58:48 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:11cd] Subsystem: ASUSTeK Computer Inc. GK107M [GeForce GT 750M] [1043:11cd] InstallationDate: Installed on 2020-09-08 (222 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: ASUSTeK COMPUTER INC. N550JV ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic root=UUID=18f3ecb2-cebb-4134-aa73-7d85d52089a3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/14/2013 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N550JV.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N550JV 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.:bvrN550JV.204:bd05/14/2013:br4.6:svnASUSTeKCOMPUTERINC.:pnN550JV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN550JV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: N dmi.product.name: N550JV dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 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/1924964 Title: screen glitches Status in xorg package in Ubuntu: New Bug description: The issue is screen glitches issue is intermittent and temporary I think it started after a recent
[Touch-packages] [Bug 1833593] Re: fstrim.timer always triggers at 00:00, use RandomizedDelaySec
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: util-linux (Ubuntu) Status: New => Confirmed -- 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/1833593 Title: fstrim.timer always triggers at 00:00, use RandomizedDelaySec Status in util-linux package in Ubuntu: Confirmed Bug description: fstrim.timer always triggers at 00:00: $ systemctl list-timers fstrim.timer NEXT LEFTLAST PASSED UNIT ACTIVATES Mon 2019-06-24 00:00:00 CEST 3 days left Mon 2019-06-17 00:00:06 CEST 3 days ago fstrim.timer fstrim.service 1 timers listed. Pass --all to see loaded but inactive timers, too. This can be an issue if concurrent runs cause increased I/O load on multiple servers which are part of the same system architecture (I have no hard facts via monitoring on this, but assume this can be an issue). /lib/systemd/system/fstrim.timer does not try to randomize the start time. systemd.timer(5) suggests that RandomizedDelaySec can be used to introduce variable start times, allowing for balancing out the (suspected increased) I/O load across multiple systems. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: util-linux 2.31.1-0.4ubuntu3.3 ProcVersionSignature: Ubuntu 5.0.0-17.18~18.04.1-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jun 20 19:52:17 2019 SourcePackage: util-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1833593/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
