[Desktop-packages] [Bug 1928791] Re: gnome-shell runs on 60--100% CPU usage
Also, do you have any animated indicators in your panel like indicator- multiload? (I am thinking of bug 784055) How about apps that are rendering constantly? Web browsers? Which ones? What apps are close to gnome-shell in the 'top' list? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1928791 Title: gnome-shell runs on 60--100% CPU usage Status in gnome-shell package in Ubuntu: Incomplete Bug description: from top output: top - 14:18:02 up 5:45, 1 user, load average: 1,55, 1,54, 1,77 Tasks: 419 total, 1 running, 418 sleeping, 0 stopped, 0 zombie %Cpu(s): 13,2 us, 2,6 sy, 0,0 ni, 83,7 id, 0,1 wa, 0,0 hi, 0,4 si, 0,0 st MiB Mem : 7960,7 total,233,0 free, 5719,6 used, 2008,1 buff/cache MiB Swap: 26058,0 total, 23596,0 free, 2462,0 used.576,0 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 20866 tobias20 0 6652668 996,0m 83472 S 63,4 12,5 33:56.49 gnome-shell this is so wrong… how to fix it? best, Tobias ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.7-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 18 14:11:41 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-22 (300 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1928791/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1924888] Re: gnome-disks can't create exfat partitions on Hirsute with the Samsung provided tools.
Hey Chris, as written on bug #1925822 for Lukasz that's on our merge list, we will try to get to it today -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1924888 Title: gnome-disks can't create exfat partitions on Hirsute with the Samsung provided tools. Status in udisks2 package in Ubuntu: Fix Committed Status in udisks2 source package in Hirsute: Fix Committed Bug description: * Impact When on Hirsute with the new Samsung provided exfat support, gnome-disks can't create new exfat partitions due to being hardcoded to use the old mkexfatfs program from the exfat-utils package. The solution is to use mkfs.exfat which is provided by the old exfat-utils as well as the new exfatprogs. * Test Case - connect a device to format of your choice - $ apt install exfatprogs - start gnome-disks - select the device or partition to format - select other -> exfat as filesystem type - confirm the format -> the device should get formatted without error * Impact The change is in the section defining the commands to use for exfat so limited to this filesystem. Check that changing label or formatting is working with exfatprogs but also keeps working with exfat-utils To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1924888/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1924888] Re: gnome-disks can't create exfat partitions on Hirsute with the Samsung provided tools.
This looks like a candidate for release into hirsute-updates, but it's not clear whether or not this is fixed in impish yet. If it's fixed in impish could you please update the bug status, and if it's not fixed in impish yet could you please fix it there? :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1924888 Title: gnome-disks can't create exfat partitions on Hirsute with the Samsung provided tools. Status in udisks2 package in Ubuntu: Fix Committed Status in udisks2 source package in Hirsute: Fix Committed Bug description: * Impact When on Hirsute with the new Samsung provided exfat support, gnome-disks can't create new exfat partitions due to being hardcoded to use the old mkexfatfs program from the exfat-utils package. The solution is to use mkfs.exfat which is provided by the old exfat-utils as well as the new exfatprogs. * Test Case - connect a device to format of your choice - $ apt install exfatprogs - start gnome-disks - select the device or partition to format - select other -> exfat as filesystem type - confirm the format -> the device should get formatted without error * Impact The change is in the section defining the commands to use for exfat so limited to this filesystem. Check that changing label or formatting is working with exfatprogs but also keeps working with exfat-utils To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1924888/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1926165] Re: Bass speakers not enabled on Lenovo Yoga 9i
Please test with generic kernel, and set both DAC1 and DAC2 to maximum, download the attached set-verb.sh, chmod a+x set-verb.sh, sudo ./set- verb.sh. Check if the bass spk could output sound? thx. ** Attachment added: "set-verb.sh" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1926165/+attachment/5498623/+files/set-verb.sh -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1926165 Title: Bass speakers not enabled on Lenovo Yoga 9i Status in alsa-driver package in Ubuntu: Confirmed Bug description: The Lenovo Yoga 9i has two sets of speakers: regular ones and bass speakers. The former work but while latter are detected and show up in alsamixer, they play no sound. Plugging headphones in and out or toggling any of the volume options does not fix the issue. A possibly related issue for a different Yoga version: https://bugzilla.kernel.org/show_bug.cgi?id=205755 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: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4466 F pulseaudio ubuntu 6219 F alsamixer /dev/snd/pcmC0D0p: ubuntu 4466 F...m pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.461 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 26 15:10:05 2021 LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp successful Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [82BG, Realtek ALC287, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/28/2021 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: EHCN40WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 9 14ITL5 dmi.ec.firmware.release: 1.40 dmi.modalias: dmi:bvnLENOVO:bvrEHCN40WW:bd01/28/2021:br1.40:efr1.40:svnLENOVO:pn82BG:pvrYoga914ITL5:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrYoga914ITL5: dmi.product.family: Yoga 9 14ITL5 dmi.product.name: 82BG dmi.product.sku: LENOVO_MT_82BG_BU_idea_FM_Yoga 9 14ITL5 dmi.product.version: Yoga 9 14ITL5 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1926165/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914279] Update Released
The verification of the Stable Release Update for rtl8812au has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: Fix Released Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in bcmwl package in Ubuntu: Fix Released Status in dahdi-linux package in Ubuntu: Fix Released Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: Fix Released Status in evdi package in Ubuntu: Fix Released Status in gost-crypto package in Ubuntu: Fix Released Status in iptables-netflow package in Ubuntu: Fix Released Status in liblzf package in Ubuntu: Fix Released Status in lime-forensics package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: Fix Released Status in r8168 package in Ubuntu: Fix Released Status in rtl8812au package in Ubuntu: Fix Released Status in sysdig package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in acpi-call source package in Focal: Fix Released Status in backport-iwlwifi-dkms source package in Focal: Fix Released Status in bcmwl source package in Focal: Fix Released Status in dahdi-linux source package in Focal: Fix Released Status in dm-writeboost source package in Focal: Fix Released Status in evdi source package in Focal: Fix Released Status in gost-crypto source package in Focal: Fix Released Status in iptables-netflow source package in Focal: Fix Released Status in liblzf source package in Focal: Fix Released Status in lime-forensics source package in Focal: Fix Released Status in lttng-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-340 source package in Focal: Fix Released Status in oss4 source package in Focal: Fix Released Status in r8168 source package in Focal: Fix Released Status in rtl8812au source package in Focal: Fix Released Status in sysdig source package in Focal: Fix Released Status in v4l2loopback source package in Focal: Fix Released Status in virtualbox source package in Focal: Fix Released Status in virtualbox-hwe source package in Focal: Fix Released Status in zfs-linux source package in Focal: Fix Released Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them. Should dkms modules SRUs always getting published into -security pocket, as well as the -updates pocket? Should linux maintainer scripts prevent touching reboot required flag if any dkms modules fail to build? Should apt / unattanded-upgrades / update-manager always update dkms modules with kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1914279/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914279] Re: linux from security may force reboots without complete dkms modules
This bug was fixed in the package zfs-linux - 0.8.3-1ubuntu12.9 --- zfs-linux (0.8.3-1ubuntu12.9) focal; urgency=medium * No change rebuild in security pocket. LP: #1914279. -- Dimitri John Ledkov Thu, 29 Apr 2021 16:09:45 +0100 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: Fix Released Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in bcmwl package in Ubuntu: Fix Released Status in dahdi-linux package in Ubuntu: Fix Released Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: Fix Released Status in evdi package in Ubuntu: Fix Released Status in gost-crypto package in Ubuntu: Fix Released Status in iptables-netflow package in Ubuntu: Fix Released Status in liblzf package in Ubuntu: Fix Released Status in lime-forensics package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: Fix Released Status in r8168 package in Ubuntu: Fix Released Status in rtl8812au package in Ubuntu: Fix Released Status in sysdig package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in acpi-call source package in Focal: Fix Released Status in backport-iwlwifi-dkms source package in Focal: Fix Released Status in bcmwl source package in Focal: Fix Released Status in dahdi-linux source package in Focal: Fix Released Status in dm-writeboost source package in Focal: Fix Released Status in evdi source package in Focal: Fix Released Status in gost-crypto source package in Focal: Fix Released Status in iptables-netflow source package in Focal: Fix Released Status in liblzf source package in Focal: Fix Released Status in lime-forensics source package in Focal: Fix Released Status in lttng-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-340 source package in Focal: Fix Released Status in oss4 source package in Focal: Fix Released Status in r8168 source package in Focal: Fix Released Status in rtl8812au source package in Focal: Fix Released Status in sysdig source package in Focal: Fix Released Status in v4l2loopback source package in Focal: Fix Released Status in virtualbox source package in Focal: Fix Released Status in virtualbox-hwe source package in Focal: Fix Released Status in zfs-linux source package in Focal: Fix Released Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them. Should dkms modules SRUs always getting published into -security pocket, as well as the -updates pocket? Should linux maintainer scripts prevent touching reboot required flag if any dkms modules fail to build? Should apt / unattanded-upgrades / update-manager always update dkms modules with kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1914279/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914279] Re: linux from security may force reboots without complete dkms modules
This bug was fixed in the package v4l2loopback - 0.12.3-1ubuntu0.4 --- v4l2loopback (0.12.3-1ubuntu0.4) focal; urgency=medium * No change rebuild in security pocket. LP: #1914279. -- Dimitri John Ledkov Thu, 29 Apr 2021 16:09:12 +0100 ** Changed in: virtualbox (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: Fix Released Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in bcmwl package in Ubuntu: Fix Released Status in dahdi-linux package in Ubuntu: Fix Released Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: Fix Released Status in evdi package in Ubuntu: Fix Released Status in gost-crypto package in Ubuntu: Fix Released Status in iptables-netflow package in Ubuntu: Fix Released Status in liblzf package in Ubuntu: Fix Released Status in lime-forensics package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: Fix Released Status in r8168 package in Ubuntu: Fix Released Status in rtl8812au package in Ubuntu: Fix Released Status in sysdig package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in acpi-call source package in Focal: Fix Released Status in backport-iwlwifi-dkms source package in Focal: Fix Released Status in bcmwl source package in Focal: Fix Released Status in dahdi-linux source package in Focal: Fix Released Status in dm-writeboost source package in Focal: Fix Released Status in evdi source package in Focal: Fix Released Status in gost-crypto source package in Focal: Fix Released Status in iptables-netflow source package in Focal: Fix Released Status in liblzf source package in Focal: Fix Released Status in lime-forensics source package in Focal: Fix Released Status in lttng-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-340 source package in Focal: Fix Released Status in oss4 source package in Focal: Fix Released Status in r8168 source package in Focal: Fix Released Status in rtl8812au source package in Focal: Fix Released Status in sysdig source package in Focal: Fix Released Status in v4l2loopback source package in Focal: Fix Released Status in virtualbox source package in Focal: Fix Released Status in virtualbox-hwe source package in Focal: Fix Released Status in zfs-linux source package in Focal: Fix Released Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them. Should dkms modules SRUs always getting published into -security pocket, as well as the -updates pocket? Should linux maintainer scripts prevent touching reboot required flag if any dkms modules fail to build? Should apt / unattanded-upgrades / update-manager always update dkms modules with kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1914279/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914279] Re: linux from security may force reboots without complete dkms modules
This bug was fixed in the package virtualbox-hwe - 6.1.16-dfsg- 6ubuntu1.20.04.2 --- virtualbox-hwe (6.1.16-dfsg-6ubuntu1.20.04.2) focal; urgency=medium * No change rebuild in security pocket. LP: #1914279. -- Dimitri John Ledkov Thu, 29 Apr 2021 16:06:25 +0100 ** Changed in: zfs-linux (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: Fix Released Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in bcmwl package in Ubuntu: Fix Released Status in dahdi-linux package in Ubuntu: Fix Released Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: Fix Released Status in evdi package in Ubuntu: Fix Released Status in gost-crypto package in Ubuntu: Fix Released Status in iptables-netflow package in Ubuntu: Fix Released Status in liblzf package in Ubuntu: Fix Released Status in lime-forensics package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: Fix Released Status in r8168 package in Ubuntu: Fix Released Status in rtl8812au package in Ubuntu: Fix Released Status in sysdig package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in acpi-call source package in Focal: Fix Released Status in backport-iwlwifi-dkms source package in Focal: Fix Released Status in bcmwl source package in Focal: Fix Released Status in dahdi-linux source package in Focal: Fix Released Status in dm-writeboost source package in Focal: Fix Released Status in evdi source package in Focal: Fix Released Status in gost-crypto source package in Focal: Fix Released Status in iptables-netflow source package in Focal: Fix Released Status in liblzf source package in Focal: Fix Released Status in lime-forensics source package in Focal: Fix Released Status in lttng-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-340 source package in Focal: Fix Released Status in oss4 source package in Focal: Fix Released Status in r8168 source package in Focal: Fix Released Status in rtl8812au source package in Focal: Fix Released Status in sysdig source package in Focal: Fix Released Status in v4l2loopback source package in Focal: Fix Released Status in virtualbox source package in Focal: Fix Released Status in virtualbox-hwe source package in Focal: Fix Released Status in zfs-linux source package in Focal: Fix Released Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them. Should dkms modules SRUs always getting published into -security pocket, as well as the -updates pocket? Should linux maintainer scripts prevent touching reboot required flag if any dkms modules fail to build? Should apt / unattanded-upgrades / update-manager always update dkms modules with kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1914279/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914279] Re: linux from security may force reboots without complete dkms modules
This bug was fixed in the package virtualbox - 6.1.16-dfsg-6~ubuntu1.20.04.2 --- virtualbox (6.1.16-dfsg-6~ubuntu1.20.04.2) focal; urgency=medium * No change rebuild in security pocket. LP: #1914279. -- Dimitri John Ledkov Thu, 29 Apr 2021 16:42:15 +0100 ** Changed in: virtualbox-hwe (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: Fix Released Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in bcmwl package in Ubuntu: Fix Released Status in dahdi-linux package in Ubuntu: Fix Released Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: Fix Released Status in evdi package in Ubuntu: Fix Released Status in gost-crypto package in Ubuntu: Fix Released Status in iptables-netflow package in Ubuntu: Fix Released Status in liblzf package in Ubuntu: Fix Released Status in lime-forensics package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: Fix Released Status in r8168 package in Ubuntu: Fix Released Status in rtl8812au package in Ubuntu: Fix Released Status in sysdig package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in acpi-call source package in Focal: Fix Released Status in backport-iwlwifi-dkms source package in Focal: Fix Released Status in bcmwl source package in Focal: Fix Released Status in dahdi-linux source package in Focal: Fix Released Status in dm-writeboost source package in Focal: Fix Released Status in evdi source package in Focal: Fix Released Status in gost-crypto source package in Focal: Fix Released Status in iptables-netflow source package in Focal: Fix Released Status in liblzf source package in Focal: Fix Released Status in lime-forensics source package in Focal: Fix Released Status in lttng-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-340 source package in Focal: Fix Released Status in oss4 source package in Focal: Fix Released Status in r8168 source package in Focal: Fix Released Status in rtl8812au source package in Focal: Fix Released Status in sysdig source package in Focal: Fix Released Status in v4l2loopback source package in Focal: Fix Released Status in virtualbox source package in Focal: Fix Released Status in virtualbox-hwe source package in Focal: Fix Released Status in zfs-linux source package in Focal: Fix Released Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them. Should dkms modules SRUs always getting published into -security pocket, as well as the -updates pocket? Should linux maintainer scripts prevent touching reboot required flag if any dkms modules fail to build? Should apt / unattanded-upgrades / update-manager always update dkms modules with kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1914279/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914279] Re: linux from security may force reboots without complete dkms modules
This bug was fixed in the package r8168 - 8.048.00-1ubuntu0.20.04.2 --- r8168 (8.048.00-1ubuntu0.20.04.2) focal; urgency=medium * No change rebuild in security pocket. LP: #1914279. -- Dimitri John Ledkov Thu, 29 Apr 2021 16:08:42 +0100 ** Changed in: rtl8812au (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: Fix Released Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in bcmwl package in Ubuntu: Fix Released Status in dahdi-linux package in Ubuntu: Fix Released Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: Fix Released Status in evdi package in Ubuntu: Fix Released Status in gost-crypto package in Ubuntu: Fix Released Status in iptables-netflow package in Ubuntu: Fix Released Status in liblzf package in Ubuntu: Fix Released Status in lime-forensics package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: Fix Released Status in r8168 package in Ubuntu: Fix Released Status in rtl8812au package in Ubuntu: Fix Released Status in sysdig package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in acpi-call source package in Focal: Fix Released Status in backport-iwlwifi-dkms source package in Focal: Fix Released Status in bcmwl source package in Focal: Fix Released Status in dahdi-linux source package in Focal: Fix Released Status in dm-writeboost source package in Focal: Fix Released Status in evdi source package in Focal: Fix Released Status in gost-crypto source package in Focal: Fix Released Status in iptables-netflow source package in Focal: Fix Released Status in liblzf source package in Focal: Fix Released Status in lime-forensics source package in Focal: Fix Released Status in lttng-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-340 source package in Focal: Fix Released Status in oss4 source package in Focal: Fix Released Status in r8168 source package in Focal: Fix Released Status in rtl8812au source package in Focal: Fix Released Status in sysdig source package in Focal: Fix Released Status in v4l2loopback source package in Focal: Fix Released Status in virtualbox source package in Focal: Fix Released Status in virtualbox-hwe source package in Focal: Fix Released Status in zfs-linux source package in Focal: Fix Released Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them. Should dkms modules SRUs always getting published into -security pocket, as well as the -updates pocket? Should linux maintainer scripts prevent touching reboot required flag if any dkms modules fail to build? Should apt / unattanded-upgrades / update-manager always update dkms modules with kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1914279/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914279] Re: linux from security may force reboots without complete dkms modules
This bug was fixed in the package sysdig - 0.26.4-1ubuntu0.3 --- sysdig (0.26.4-1ubuntu0.3) focal; urgency=medium * No change rebuild in security pocket. LP: #1914279. -- Dimitri John Ledkov Thu, 29 Apr 2021 16:09:03 +0100 ** Changed in: v4l2loopback (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: Fix Released Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in bcmwl package in Ubuntu: Fix Released Status in dahdi-linux package in Ubuntu: Fix Released Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: Fix Released Status in evdi package in Ubuntu: Fix Released Status in gost-crypto package in Ubuntu: Fix Released Status in iptables-netflow package in Ubuntu: Fix Released Status in liblzf package in Ubuntu: Fix Released Status in lime-forensics package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: Fix Released Status in r8168 package in Ubuntu: Fix Released Status in rtl8812au package in Ubuntu: Fix Released Status in sysdig package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in acpi-call source package in Focal: Fix Released Status in backport-iwlwifi-dkms source package in Focal: Fix Released Status in bcmwl source package in Focal: Fix Released Status in dahdi-linux source package in Focal: Fix Released Status in dm-writeboost source package in Focal: Fix Released Status in evdi source package in Focal: Fix Released Status in gost-crypto source package in Focal: Fix Released Status in iptables-netflow source package in Focal: Fix Released Status in liblzf source package in Focal: Fix Released Status in lime-forensics source package in Focal: Fix Released Status in lttng-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-340 source package in Focal: Fix Released Status in oss4 source package in Focal: Fix Released Status in r8168 source package in Focal: Fix Released Status in rtl8812au source package in Focal: Fix Released Status in sysdig source package in Focal: Fix Released Status in v4l2loopback source package in Focal: Fix Released Status in virtualbox source package in Focal: Fix Released Status in virtualbox-hwe source package in Focal: Fix Released Status in zfs-linux source package in Focal: Fix Released Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them. Should dkms modules SRUs always getting published into -security pocket, as well as the -updates pocket? Should linux maintainer scripts prevent touching reboot required flag if any dkms modules fail to build? Should apt / unattanded-upgrades / update-manager always update dkms modules with kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1914279/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914279] Re: linux from security may force reboots without complete dkms modules
This bug was fixed in the package nvidia-graphics-drivers-340 - 340.108-0ubuntu5.20.04.2 --- nvidia-graphics-drivers-340 (340.108-0ubuntu5.20.04.2) focal; urgency=medium * No change rebuild in security pocket. LP: #1914279. -- Dimitri John Ledkov Thu, 29 Apr 2021 16:05:47 +0100 ** Changed in: oss4 (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: Fix Released Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in bcmwl package in Ubuntu: Fix Released Status in dahdi-linux package in Ubuntu: Fix Released Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: Fix Released Status in evdi package in Ubuntu: Fix Released Status in gost-crypto package in Ubuntu: Fix Released Status in iptables-netflow package in Ubuntu: Fix Released Status in liblzf package in Ubuntu: Fix Released Status in lime-forensics package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: Fix Released Status in r8168 package in Ubuntu: Fix Released Status in rtl8812au package in Ubuntu: Fix Released Status in sysdig package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in acpi-call source package in Focal: Fix Released Status in backport-iwlwifi-dkms source package in Focal: Fix Released Status in bcmwl source package in Focal: Fix Released Status in dahdi-linux source package in Focal: Fix Released Status in dm-writeboost source package in Focal: Fix Released Status in evdi source package in Focal: Fix Released Status in gost-crypto source package in Focal: Fix Released Status in iptables-netflow source package in Focal: Fix Released Status in liblzf source package in Focal: Fix Released Status in lime-forensics source package in Focal: Fix Released Status in lttng-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-340 source package in Focal: Fix Released Status in oss4 source package in Focal: Fix Released Status in r8168 source package in Focal: Fix Released Status in rtl8812au source package in Focal: Fix Released Status in sysdig source package in Focal: Fix Released Status in v4l2loopback source package in Focal: Fix Released Status in virtualbox source package in Focal: Fix Released Status in virtualbox-hwe source package in Focal: Fix Released Status in zfs-linux source package in Focal: Fix Released Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them. Should dkms modules SRUs always getting published into -security pocket, as well as the -updates pocket? Should linux maintainer scripts prevent touching reboot required flag if any dkms modules fail to build? Should apt / unattanded-upgrades / update-manager always update dkms modules with kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1914279/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914279] Re: linux from security may force reboots without complete dkms modules
This bug was fixed in the package oss4 - 4.2-build2010-5ubuntu6~20.04.2 --- oss4 (4.2-build2010-5ubuntu6~20.04.2) focal; urgency=medium * No change rebuild in security pocket. LP: #1914279. -- Dimitri John Ledkov Thu, 29 Apr 2021 16:08:32 +0100 ** Changed in: r8168 (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: Fix Released Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in bcmwl package in Ubuntu: Fix Released Status in dahdi-linux package in Ubuntu: Fix Released Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: Fix Released Status in evdi package in Ubuntu: Fix Released Status in gost-crypto package in Ubuntu: Fix Released Status in iptables-netflow package in Ubuntu: Fix Released Status in liblzf package in Ubuntu: Fix Released Status in lime-forensics package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: Fix Released Status in r8168 package in Ubuntu: Fix Released Status in rtl8812au package in Ubuntu: Fix Released Status in sysdig package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in acpi-call source package in Focal: Fix Released Status in backport-iwlwifi-dkms source package in Focal: Fix Released Status in bcmwl source package in Focal: Fix Released Status in dahdi-linux source package in Focal: Fix Released Status in dm-writeboost source package in Focal: Fix Released Status in evdi source package in Focal: Fix Released Status in gost-crypto source package in Focal: Fix Released Status in iptables-netflow source package in Focal: Fix Released Status in liblzf source package in Focal: Fix Released Status in lime-forensics source package in Focal: Fix Released Status in lttng-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-340 source package in Focal: Fix Released Status in oss4 source package in Focal: Fix Released Status in r8168 source package in Focal: Fix Released Status in rtl8812au source package in Focal: Fix Released Status in sysdig source package in Focal: Fix Released Status in v4l2loopback source package in Focal: Fix Released Status in virtualbox source package in Focal: Fix Released Status in virtualbox-hwe source package in Focal: Fix Released Status in zfs-linux source package in Focal: Fix Released Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them. Should dkms modules SRUs always getting published into -security pocket, as well as the -updates pocket? Should linux maintainer scripts prevent touching reboot required flag if any dkms modules fail to build? Should apt / unattanded-upgrades / update-manager always update dkms modules with kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1914279/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914279] Re: linux from security may force reboots without complete dkms modules
This bug was fixed in the package rtl8812au - 4.3.8.12175.20140902+dfsg- 0ubuntu13~20.04.2 --- rtl8812au (4.3.8.12175.20140902+dfsg-0ubuntu13~20.04.2) focal; urgency=medium * No change rebuild in security pocket. LP: #1914279. -- Dimitri John Ledkov Thu, 29 Apr 2021 16:08:52 +0100 ** Changed in: sysdig (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: Fix Released Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in bcmwl package in Ubuntu: Fix Released Status in dahdi-linux package in Ubuntu: Fix Released Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: Fix Released Status in evdi package in Ubuntu: Fix Released Status in gost-crypto package in Ubuntu: Fix Released Status in iptables-netflow package in Ubuntu: Fix Released Status in liblzf package in Ubuntu: Fix Released Status in lime-forensics package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: Fix Released Status in r8168 package in Ubuntu: Fix Released Status in rtl8812au package in Ubuntu: Fix Released Status in sysdig package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in acpi-call source package in Focal: Fix Released Status in backport-iwlwifi-dkms source package in Focal: Fix Released Status in bcmwl source package in Focal: Fix Released Status in dahdi-linux source package in Focal: Fix Released Status in dm-writeboost source package in Focal: Fix Released Status in evdi source package in Focal: Fix Released Status in gost-crypto source package in Focal: Fix Released Status in iptables-netflow source package in Focal: Fix Released Status in liblzf source package in Focal: Fix Released Status in lime-forensics source package in Focal: Fix Released Status in lttng-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-340 source package in Focal: Fix Released Status in oss4 source package in Focal: Fix Released Status in r8168 source package in Focal: Fix Released Status in rtl8812au source package in Focal: Fix Released Status in sysdig source package in Focal: Fix Released Status in v4l2loopback source package in Focal: Fix Released Status in virtualbox source package in Focal: Fix Released Status in virtualbox-hwe source package in Focal: Fix Released Status in zfs-linux source package in Focal: Fix Released Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them. Should dkms modules SRUs always getting published into -security pocket, as well as the -updates pocket? Should linux maintainer scripts prevent touching reboot required flag if any dkms modules fail to build? Should apt / unattanded-upgrades / update-manager always update dkms modules with kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1914279/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914279] Re: linux from security may force reboots without complete dkms modules
This bug was fixed in the package lttng-modules - 2.12.2-1ubuntu1~20.04.2 --- lttng-modules (2.12.2-1ubuntu1~20.04.2) focal; urgency=medium * No change rebuild in security pocket. LP: #1914279. -- Dimitri John Ledkov Thu, 29 Apr 2021 16:08:09 +0100 ** Changed in: nvidia-graphics-drivers-340 (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: Fix Released Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in bcmwl package in Ubuntu: Fix Released Status in dahdi-linux package in Ubuntu: Fix Released Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: Fix Released Status in evdi package in Ubuntu: Fix Released Status in gost-crypto package in Ubuntu: Fix Released Status in iptables-netflow package in Ubuntu: Fix Released Status in liblzf package in Ubuntu: Fix Released Status in lime-forensics package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: Fix Released Status in r8168 package in Ubuntu: Fix Released Status in rtl8812au package in Ubuntu: Fix Released Status in sysdig package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in acpi-call source package in Focal: Fix Released Status in backport-iwlwifi-dkms source package in Focal: Fix Released Status in bcmwl source package in Focal: Fix Released Status in dahdi-linux source package in Focal: Fix Released Status in dm-writeboost source package in Focal: Fix Released Status in evdi source package in Focal: Fix Released Status in gost-crypto source package in Focal: Fix Released Status in iptables-netflow source package in Focal: Fix Released Status in liblzf source package in Focal: Fix Released Status in lime-forensics source package in Focal: Fix Released Status in lttng-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-340 source package in Focal: Fix Released Status in oss4 source package in Focal: Fix Released Status in r8168 source package in Focal: Fix Released Status in rtl8812au source package in Focal: Fix Released Status in sysdig source package in Focal: Fix Released Status in v4l2loopback source package in Focal: Fix Released Status in virtualbox source package in Focal: Fix Released Status in virtualbox-hwe source package in Focal: Fix Released Status in zfs-linux source package in Focal: Fix Released Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them. Should dkms modules SRUs always getting published into -security pocket, as well as the -updates pocket? Should linux maintainer scripts prevent touching reboot required flag if any dkms modules fail to build? Should apt / unattanded-upgrades / update-manager always update dkms modules with kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1914279/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914279] Re: linux from security may force reboots without complete dkms modules
This bug was fixed in the package evdi - 1.7.0+dfsg-1ubuntu1~20.04.3 --- evdi (1.7.0+dfsg-1ubuntu1~20.04.3) focal; urgency=medium * No change rebuild in security pocket. LP: #1914279. -- Dimitri John Ledkov Thu, 29 Apr 2021 16:07:32 +0100 ** Changed in: gost-crypto (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: Fix Released Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in bcmwl package in Ubuntu: Fix Released Status in dahdi-linux package in Ubuntu: Fix Released Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: Fix Released Status in evdi package in Ubuntu: Fix Released Status in gost-crypto package in Ubuntu: Fix Released Status in iptables-netflow package in Ubuntu: Fix Released Status in liblzf package in Ubuntu: Fix Released Status in lime-forensics package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: Fix Released Status in r8168 package in Ubuntu: Fix Released Status in rtl8812au package in Ubuntu: Fix Released Status in sysdig package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in acpi-call source package in Focal: Fix Released Status in backport-iwlwifi-dkms source package in Focal: Fix Released Status in bcmwl source package in Focal: Fix Released Status in dahdi-linux source package in Focal: Fix Released Status in dm-writeboost source package in Focal: Fix Released Status in evdi source package in Focal: Fix Released Status in gost-crypto source package in Focal: Fix Released Status in iptables-netflow source package in Focal: Fix Released Status in liblzf source package in Focal: Fix Released Status in lime-forensics source package in Focal: Fix Released Status in lttng-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-340 source package in Focal: Fix Released Status in oss4 source package in Focal: Fix Released Status in r8168 source package in Focal: Fix Released Status in rtl8812au source package in Focal: Fix Released Status in sysdig source package in Focal: Fix Released Status in v4l2loopback source package in Focal: Fix Released Status in virtualbox source package in Focal: Fix Released Status in virtualbox-hwe source package in Focal: Fix Released Status in zfs-linux source package in Focal: Fix Released Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them. Should dkms modules SRUs always getting published into -security pocket, as well as the -updates pocket? Should linux maintainer scripts prevent touching reboot required flag if any dkms modules fail to build? Should apt / unattanded-upgrades / update-manager always update dkms modules with kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1914279/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914279] Re: linux from security may force reboots without complete dkms modules
This bug was fixed in the package dm-writeboost - 2.2.9-1ubuntu1.2 --- dm-writeboost (2.2.9-1ubuntu1.2) focal; urgency=medium * No change rebuild in security pocket. LP: #1914279. -- Dimitri John Ledkov Thu, 29 Apr 2021 16:07:23 +0100 ** Changed in: evdi (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: Fix Released Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in bcmwl package in Ubuntu: Fix Released Status in dahdi-linux package in Ubuntu: Fix Released Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: Fix Released Status in evdi package in Ubuntu: Fix Released Status in gost-crypto package in Ubuntu: Fix Released Status in iptables-netflow package in Ubuntu: Fix Released Status in liblzf package in Ubuntu: Fix Released Status in lime-forensics package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: Fix Released Status in r8168 package in Ubuntu: Fix Released Status in rtl8812au package in Ubuntu: Fix Released Status in sysdig package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in acpi-call source package in Focal: Fix Released Status in backport-iwlwifi-dkms source package in Focal: Fix Released Status in bcmwl source package in Focal: Fix Released Status in dahdi-linux source package in Focal: Fix Released Status in dm-writeboost source package in Focal: Fix Released Status in evdi source package in Focal: Fix Released Status in gost-crypto source package in Focal: Fix Released Status in iptables-netflow source package in Focal: Fix Released Status in liblzf source package in Focal: Fix Released Status in lime-forensics source package in Focal: Fix Released Status in lttng-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-340 source package in Focal: Fix Released Status in oss4 source package in Focal: Fix Released Status in r8168 source package in Focal: Fix Released Status in rtl8812au source package in Focal: Fix Released Status in sysdig source package in Focal: Fix Released Status in v4l2loopback source package in Focal: Fix Released Status in virtualbox source package in Focal: Fix Released Status in virtualbox-hwe source package in Focal: Fix Released Status in zfs-linux source package in Focal: Fix Released Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them. Should dkms modules SRUs always getting published into -security pocket, as well as the -updates pocket? Should linux maintainer scripts prevent touching reboot required flag if any dkms modules fail to build? Should apt / unattanded-upgrades / update-manager always update dkms modules with kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1914279/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914279] Re: linux from security may force reboots without complete dkms modules
This bug was fixed in the package lime-forensics - 1.9-1ubuntu0.2 --- lime-forensics (1.9-1ubuntu0.2) focal; urgency=medium * No change rebuild in security pocket. LP: #1914279. -- Dimitri John Ledkov Thu, 29 Apr 2021 16:08:00 +0100 ** Changed in: lttng-modules (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: Fix Released Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in bcmwl package in Ubuntu: Fix Released Status in dahdi-linux package in Ubuntu: Fix Released Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: Fix Released Status in evdi package in Ubuntu: Fix Released Status in gost-crypto package in Ubuntu: Fix Released Status in iptables-netflow package in Ubuntu: Fix Released Status in liblzf package in Ubuntu: Fix Released Status in lime-forensics package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: Fix Released Status in r8168 package in Ubuntu: Fix Released Status in rtl8812au package in Ubuntu: Fix Released Status in sysdig package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in acpi-call source package in Focal: Fix Released Status in backport-iwlwifi-dkms source package in Focal: Fix Released Status in bcmwl source package in Focal: Fix Released Status in dahdi-linux source package in Focal: Fix Released Status in dm-writeboost source package in Focal: Fix Released Status in evdi source package in Focal: Fix Released Status in gost-crypto source package in Focal: Fix Released Status in iptables-netflow source package in Focal: Fix Released Status in liblzf source package in Focal: Fix Released Status in lime-forensics source package in Focal: Fix Released Status in lttng-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-340 source package in Focal: Fix Released Status in oss4 source package in Focal: Fix Released Status in r8168 source package in Focal: Fix Released Status in rtl8812au source package in Focal: Fix Released Status in sysdig source package in Focal: Fix Released Status in v4l2loopback source package in Focal: Fix Released Status in virtualbox source package in Focal: Fix Released Status in virtualbox-hwe source package in Focal: Fix Released Status in zfs-linux source package in Focal: Fix Released Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them. Should dkms modules SRUs always getting published into -security pocket, as well as the -updates pocket? Should linux maintainer scripts prevent touching reboot required flag if any dkms modules fail to build? Should apt / unattanded-upgrades / update-manager always update dkms modules with kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1914279/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914279] Re: linux from security may force reboots without complete dkms modules
This bug was fixed in the package bcmwl - 6.30.223.271+bdcom- 0ubuntu7~20.04.2 --- bcmwl (6.30.223.271+bdcom-0ubuntu7~20.04.2) focal; urgency=medium * No change rebuild in security pocket. LP: #1914279. -- Dimitri John Ledkov Thu, 29 Apr 2021 16:05:27 +0100 ** Changed in: dahdi-linux (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: Fix Released Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in bcmwl package in Ubuntu: Fix Released Status in dahdi-linux package in Ubuntu: Fix Released Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: Fix Released Status in evdi package in Ubuntu: Fix Released Status in gost-crypto package in Ubuntu: Fix Released Status in iptables-netflow package in Ubuntu: Fix Released Status in liblzf package in Ubuntu: Fix Released Status in lime-forensics package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: Fix Released Status in r8168 package in Ubuntu: Fix Released Status in rtl8812au package in Ubuntu: Fix Released Status in sysdig package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in acpi-call source package in Focal: Fix Released Status in backport-iwlwifi-dkms source package in Focal: Fix Released Status in bcmwl source package in Focal: Fix Released Status in dahdi-linux source package in Focal: Fix Released Status in dm-writeboost source package in Focal: Fix Released Status in evdi source package in Focal: Fix Released Status in gost-crypto source package in Focal: Fix Released Status in iptables-netflow source package in Focal: Fix Released Status in liblzf source package in Focal: Fix Released Status in lime-forensics source package in Focal: Fix Released Status in lttng-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-340 source package in Focal: Fix Released Status in oss4 source package in Focal: Fix Released Status in r8168 source package in Focal: Fix Released Status in rtl8812au source package in Focal: Fix Released Status in sysdig source package in Focal: Fix Released Status in v4l2loopback source package in Focal: Fix Released Status in virtualbox source package in Focal: Fix Released Status in virtualbox-hwe source package in Focal: Fix Released Status in zfs-linux source package in Focal: Fix Released Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them. Should dkms modules SRUs always getting published into -security pocket, as well as the -updates pocket? Should linux maintainer scripts prevent touching reboot required flag if any dkms modules fail to build? Should apt / unattanded-upgrades / update-manager always update dkms modules with kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1914279/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914279] Re: linux from security may force reboots without complete dkms modules
This bug was fixed in the package liblzf - 3.6-2~ubuntu1.20.04.2 --- liblzf (3.6-2~ubuntu1.20.04.2) focal; urgency=medium * No change rebuild in security pocket. LP: #1914279. -- Dimitri John Ledkov Thu, 29 Apr 2021 17:11:50 +0100 ** Changed in: lime-forensics (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: Fix Released Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in bcmwl package in Ubuntu: Fix Released Status in dahdi-linux package in Ubuntu: Fix Released Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: Fix Released Status in evdi package in Ubuntu: Fix Released Status in gost-crypto package in Ubuntu: Fix Released Status in iptables-netflow package in Ubuntu: Fix Released Status in liblzf package in Ubuntu: Fix Released Status in lime-forensics package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: Fix Released Status in r8168 package in Ubuntu: Fix Released Status in rtl8812au package in Ubuntu: Fix Released Status in sysdig package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in acpi-call source package in Focal: Fix Released Status in backport-iwlwifi-dkms source package in Focal: Fix Released Status in bcmwl source package in Focal: Fix Released Status in dahdi-linux source package in Focal: Fix Released Status in dm-writeboost source package in Focal: Fix Released Status in evdi source package in Focal: Fix Released Status in gost-crypto source package in Focal: Fix Released Status in iptables-netflow source package in Focal: Fix Released Status in liblzf source package in Focal: Fix Released Status in lime-forensics source package in Focal: Fix Released Status in lttng-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-340 source package in Focal: Fix Released Status in oss4 source package in Focal: Fix Released Status in r8168 source package in Focal: Fix Released Status in rtl8812au source package in Focal: Fix Released Status in sysdig source package in Focal: Fix Released Status in v4l2loopback source package in Focal: Fix Released Status in virtualbox source package in Focal: Fix Released Status in virtualbox-hwe source package in Focal: Fix Released Status in zfs-linux source package in Focal: Fix Released Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them. Should dkms modules SRUs always getting published into -security pocket, as well as the -updates pocket? Should linux maintainer scripts prevent touching reboot required flag if any dkms modules fail to build? Should apt / unattanded-upgrades / update-manager always update dkms modules with kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1914279/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914279] Re: linux from security may force reboots without complete dkms modules
This bug was fixed in the package iptables-netflow - 2.4-2ubuntu0.4 --- iptables-netflow (2.4-2ubuntu0.4) focal; urgency=medium * No change rebuild in security pocket. LP: #1914279. -- Dimitri John Ledkov Thu, 29 Apr 2021 16:07:51 +0100 ** Changed in: liblzf (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: Fix Released Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in bcmwl package in Ubuntu: Fix Released Status in dahdi-linux package in Ubuntu: Fix Released Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: Fix Released Status in evdi package in Ubuntu: Fix Released Status in gost-crypto package in Ubuntu: Fix Released Status in iptables-netflow package in Ubuntu: Fix Released Status in liblzf package in Ubuntu: Fix Released Status in lime-forensics package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: Fix Released Status in r8168 package in Ubuntu: Fix Released Status in rtl8812au package in Ubuntu: Fix Released Status in sysdig package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in acpi-call source package in Focal: Fix Released Status in backport-iwlwifi-dkms source package in Focal: Fix Released Status in bcmwl source package in Focal: Fix Released Status in dahdi-linux source package in Focal: Fix Released Status in dm-writeboost source package in Focal: Fix Released Status in evdi source package in Focal: Fix Released Status in gost-crypto source package in Focal: Fix Released Status in iptables-netflow source package in Focal: Fix Released Status in liblzf source package in Focal: Fix Released Status in lime-forensics source package in Focal: Fix Released Status in lttng-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-340 source package in Focal: Fix Released Status in oss4 source package in Focal: Fix Released Status in r8168 source package in Focal: Fix Released Status in rtl8812au source package in Focal: Fix Released Status in sysdig source package in Focal: Fix Released Status in v4l2loopback source package in Focal: Fix Released Status in virtualbox source package in Focal: Fix Released Status in virtualbox-hwe source package in Focal: Fix Released Status in zfs-linux source package in Focal: Fix Released Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them. Should dkms modules SRUs always getting published into -security pocket, as well as the -updates pocket? Should linux maintainer scripts prevent touching reboot required flag if any dkms modules fail to build? Should apt / unattanded-upgrades / update-manager always update dkms modules with kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1914279/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914279] Re: linux from security may force reboots without complete dkms modules
This bug was fixed in the package dahdi-linux - 1:2.11.1~dfsg-1ubuntu6.2 --- dahdi-linux (1:2.11.1~dfsg-1ubuntu6.2) focal; urgency=medium * No change rebuild in security pocket. LP: #1914279. -- Dimitri John Ledkov Thu, 29 Apr 2021 16:07:14 +0100 ** Changed in: dm-writeboost (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: Fix Released Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in bcmwl package in Ubuntu: Fix Released Status in dahdi-linux package in Ubuntu: Fix Released Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: Fix Released Status in evdi package in Ubuntu: Fix Released Status in gost-crypto package in Ubuntu: Fix Released Status in iptables-netflow package in Ubuntu: Fix Released Status in liblzf package in Ubuntu: Fix Released Status in lime-forensics package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: Fix Released Status in r8168 package in Ubuntu: Fix Released Status in rtl8812au package in Ubuntu: Fix Released Status in sysdig package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in acpi-call source package in Focal: Fix Released Status in backport-iwlwifi-dkms source package in Focal: Fix Released Status in bcmwl source package in Focal: Fix Released Status in dahdi-linux source package in Focal: Fix Released Status in dm-writeboost source package in Focal: Fix Released Status in evdi source package in Focal: Fix Released Status in gost-crypto source package in Focal: Fix Released Status in iptables-netflow source package in Focal: Fix Released Status in liblzf source package in Focal: Fix Released Status in lime-forensics source package in Focal: Fix Released Status in lttng-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-340 source package in Focal: Fix Released Status in oss4 source package in Focal: Fix Released Status in r8168 source package in Focal: Fix Released Status in rtl8812au source package in Focal: Fix Released Status in sysdig source package in Focal: Fix Released Status in v4l2loopback source package in Focal: Fix Released Status in virtualbox source package in Focal: Fix Released Status in virtualbox-hwe source package in Focal: Fix Released Status in zfs-linux source package in Focal: Fix Released Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them. Should dkms modules SRUs always getting published into -security pocket, as well as the -updates pocket? Should linux maintainer scripts prevent touching reboot required flag if any dkms modules fail to build? Should apt / unattanded-upgrades / update-manager always update dkms modules with kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1914279/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914279] Re: linux from security may force reboots without complete dkms modules
This bug was fixed in the package acpi-call - 1.1.0-5ubuntu0.2 --- acpi-call (1.1.0-5ubuntu0.2) focal; urgency=medium * No change rebuild in security pocket. LP: #1914279. -- Dimitri John Ledkov Thu, 29 Apr 2021 16:06:55 +0100 ** Changed in: acpi-call (Ubuntu Focal) Status: Fix Committed => Fix Released ** Changed in: backport-iwlwifi-dkms (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: Fix Released Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in bcmwl package in Ubuntu: Fix Released Status in dahdi-linux package in Ubuntu: Fix Released Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: Fix Released Status in evdi package in Ubuntu: Fix Released Status in gost-crypto package in Ubuntu: Fix Released Status in iptables-netflow package in Ubuntu: Fix Released Status in liblzf package in Ubuntu: Fix Released Status in lime-forensics package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: Fix Released Status in r8168 package in Ubuntu: Fix Released Status in rtl8812au package in Ubuntu: Fix Released Status in sysdig package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in acpi-call source package in Focal: Fix Released Status in backport-iwlwifi-dkms source package in Focal: Fix Released Status in bcmwl source package in Focal: Fix Released Status in dahdi-linux source package in Focal: Fix Released Status in dm-writeboost source package in Focal: Fix Released Status in evdi source package in Focal: Fix Released Status in gost-crypto source package in Focal: Fix Released Status in iptables-netflow source package in Focal: Fix Released Status in liblzf source package in Focal: Fix Released Status in lime-forensics source package in Focal: Fix Released Status in lttng-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-340 source package in Focal: Fix Released Status in oss4 source package in Focal: Fix Released Status in r8168 source package in Focal: Fix Released Status in rtl8812au source package in Focal: Fix Released Status in sysdig source package in Focal: Fix Released Status in v4l2loopback source package in Focal: Fix Released Status in virtualbox source package in Focal: Fix Released Status in virtualbox-hwe source package in Focal: Fix Released Status in zfs-linux source package in Focal: Fix Released Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them. Should dkms modules SRUs always getting published into -security pocket, as well as the -updates pocket? Should linux maintainer scripts prevent touching reboot required flag if any dkms modules fail to build? Should apt / unattanded-upgrades / update-manager always update dkms modules with kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1914279/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1928791] Re: gnome-shell runs on 60--100% CPU usage
Thanks for the bug report. 1. It looks like you don't have any custom extensions installed, is that correct? You can check using the app called 'Extensions' where there should be only 3 default extensions listed. 2. Next time the problem is happening, please open a Terminal and run: journalctl -b0 > journal.txt 3. Attach the resulting text file here. ** Tags added: nvidia performance ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1928791 Title: gnome-shell runs on 60--100% CPU usage Status in gnome-shell package in Ubuntu: Incomplete Bug description: from top output: top - 14:18:02 up 5:45, 1 user, load average: 1,55, 1,54, 1,77 Tasks: 419 total, 1 running, 418 sleeping, 0 stopped, 0 zombie %Cpu(s): 13,2 us, 2,6 sy, 0,0 ni, 83,7 id, 0,1 wa, 0,0 hi, 0,4 si, 0,0 st MiB Mem : 7960,7 total,233,0 free, 5719,6 used, 2008,1 buff/cache MiB Swap: 26058,0 total, 23596,0 free, 2462,0 used.576,0 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 20866 tobias20 0 6652668 996,0m 83472 S 63,4 12,5 33:56.49 gnome-shell this is so wrong… how to fix it? best, Tobias ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.7-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 18 14:11:41 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-22 (300 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1928791/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914279] Re: linux from security may force reboots without complete dkms modules
This bug was fixed in the package backport-iwlwifi-dkms - 8324-0ubuntu3~20.04.3 --- backport-iwlwifi-dkms (8324-0ubuntu3~20.04.3) focal; urgency=medium * No change rebuild in security pocket. LP: #1914279. -- Dimitri John Ledkov Thu, 29 Apr 2021 16:07:04 +0100 ** Changed in: bcmwl (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: Fix Released Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in bcmwl package in Ubuntu: Fix Released Status in dahdi-linux package in Ubuntu: Fix Released Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: Fix Released Status in evdi package in Ubuntu: Fix Released Status in gost-crypto package in Ubuntu: Fix Released Status in iptables-netflow package in Ubuntu: Fix Released Status in liblzf package in Ubuntu: Fix Released Status in lime-forensics package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: Fix Released Status in r8168 package in Ubuntu: Fix Released Status in rtl8812au package in Ubuntu: Fix Released Status in sysdig package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in acpi-call source package in Focal: Fix Released Status in backport-iwlwifi-dkms source package in Focal: Fix Released Status in bcmwl source package in Focal: Fix Released Status in dahdi-linux source package in Focal: Fix Released Status in dm-writeboost source package in Focal: Fix Released Status in evdi source package in Focal: Fix Released Status in gost-crypto source package in Focal: Fix Released Status in iptables-netflow source package in Focal: Fix Released Status in liblzf source package in Focal: Fix Released Status in lime-forensics source package in Focal: Fix Released Status in lttng-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-340 source package in Focal: Fix Released Status in oss4 source package in Focal: Fix Released Status in r8168 source package in Focal: Fix Released Status in rtl8812au source package in Focal: Fix Released Status in sysdig source package in Focal: Fix Released Status in v4l2loopback source package in Focal: Fix Released Status in virtualbox source package in Focal: Fix Released Status in virtualbox-hwe source package in Focal: Fix Released Status in zfs-linux source package in Focal: Fix Released Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them. Should dkms modules SRUs always getting published into -security pocket, as well as the -updates pocket? Should linux maintainer scripts prevent touching reboot required flag if any dkms modules fail to build? Should apt / unattanded-upgrades / update-manager always update dkms modules with kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1914279/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914279] Re: linux from security may force reboots without complete dkms modules
This bug was fixed in the package gost-crypto - 0.3.2-2ubuntu0.2 --- gost-crypto (0.3.2-2ubuntu0.2) focal; urgency=medium * No change rebuild in security pocket. LP: #1914279. -- Dimitri John Ledkov Thu, 29 Apr 2021 16:07:41 +0100 ** Changed in: iptables-netflow (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: Fix Released Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in bcmwl package in Ubuntu: Fix Released Status in dahdi-linux package in Ubuntu: Fix Released Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: Fix Released Status in evdi package in Ubuntu: Fix Released Status in gost-crypto package in Ubuntu: Fix Released Status in iptables-netflow package in Ubuntu: Fix Released Status in liblzf package in Ubuntu: Fix Released Status in lime-forensics package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: Fix Released Status in r8168 package in Ubuntu: Fix Released Status in rtl8812au package in Ubuntu: Fix Released Status in sysdig package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in acpi-call source package in Focal: Fix Released Status in backport-iwlwifi-dkms source package in Focal: Fix Released Status in bcmwl source package in Focal: Fix Released Status in dahdi-linux source package in Focal: Fix Released Status in dm-writeboost source package in Focal: Fix Released Status in evdi source package in Focal: Fix Released Status in gost-crypto source package in Focal: Fix Released Status in iptables-netflow source package in Focal: Fix Released Status in liblzf source package in Focal: Fix Released Status in lime-forensics source package in Focal: Fix Released Status in lttng-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-340 source package in Focal: Fix Released Status in oss4 source package in Focal: Fix Released Status in r8168 source package in Focal: Fix Released Status in rtl8812au source package in Focal: Fix Released Status in sysdig source package in Focal: Fix Released Status in v4l2loopback source package in Focal: Fix Released Status in virtualbox source package in Focal: Fix Released Status in virtualbox-hwe source package in Focal: Fix Released Status in zfs-linux source package in Focal: Fix Released Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them. Should dkms modules SRUs always getting published into -security pocket, as well as the -updates pocket? Should linux maintainer scripts prevent touching reboot required flag if any dkms modules fail to build? Should apt / unattanded-upgrades / update-manager always update dkms modules with kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1914279/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1926165] Re: Bass speakers not enabled on Lenovo Yoga 9i
OK, wrote an email to realtek codec expert to ask for help. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1926165 Title: Bass speakers not enabled on Lenovo Yoga 9i Status in alsa-driver package in Ubuntu: Confirmed Bug description: The Lenovo Yoga 9i has two sets of speakers: regular ones and bass speakers. The former work but while latter are detected and show up in alsamixer, they play no sound. Plugging headphones in and out or toggling any of the volume options does not fix the issue. A possibly related issue for a different Yoga version: https://bugzilla.kernel.org/show_bug.cgi?id=205755 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: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4466 F pulseaudio ubuntu 6219 F alsamixer /dev/snd/pcmC0D0p: ubuntu 4466 F...m pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.461 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 26 15:10:05 2021 LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp successful Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [82BG, Realtek ALC287, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/28/2021 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: EHCN40WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 9 14ITL5 dmi.ec.firmware.release: 1.40 dmi.modalias: dmi:bvnLENOVO:bvrEHCN40WW:bd01/28/2021:br1.40:efr1.40:svnLENOVO:pn82BG:pvrYoga914ITL5:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrYoga914ITL5: dmi.product.family: Yoga 9 14ITL5 dmi.product.name: 82BG dmi.product.sku: LENOVO_MT_82BG_BU_idea_FM_Yoga 9 14ITL5 dmi.product.version: Yoga 9 14ITL5 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1926165/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1928586] Re: Desktop icons disappearing
** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1928586 Title: Desktop icons disappearing Status in gnome-shell-extension-desktop-icons package in Ubuntu: New Bug description: This is in Ubuntu 20.10 Groovy Gorilla. The bug: When connecting to USB tethering and allowing access to the phone's filesystem, Ubuntu's Desktop icons disappear. Steps to reproduce: Connect a phone to the computer via USB tethering (am a bit uneasy about mentioning which model phone it is). Switch on USB tethering and then switch off USB tethering in the phone's Mobile hotspot and tethering options. The phones screen will popup a dialog box asking "Allow access to phone data?" (which is a way to give the computer access to the phone's filesystem). You can click either "Allow" or "Deny". When either "Allow" or "Deny" is selected, the Desktop icons on Ubuntu disappear. When USB tethering is switched back on, the Desktop icons reappear. I've attached a video of the phenomenon. The video starts with USB tethering being switched on, which is why you can see the desktop icons. Then when USB tethering is switched off and "Allow" is clicked on the phone, the icons disappear and then they reappear when USB tethering is switched on again. This bug is probably related to bugs #1928206 and #1928213, which indicate that there are some inconsistencies with how the Nautilus Desktop works with respect to a Nautilus window. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1928586/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922353] Re: Overview sometimes fails to appear or disappear in 21.04
Thanks uriel, that is the same error in your log as comment #34. It seems we have at least some correlation if not causation. I'm not yet convinced it's a fix but can anyone test the patch and verify it fixes this bug? https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1794.patch Maybe we will need a PPA... ** Changed in: gnome-shell (Ubuntu Hirsute) Status: New => Incomplete ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Hirsute) Status: New => Incomplete ** Changed in: gnome-shell (Ubuntu Hirsute) Importance: Undecided => High ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Hirsute) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1922353 Title: Overview sometimes fails to appear or disappear in 21.04 Status in gnome-shell package in Ubuntu: Incomplete Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Incomplete Status in gnome-shell source package in Hirsute: Incomplete Status in gnome-shell-extension-ubuntu-dock source package in Hirsute: Incomplete Bug description: When I press the "windows" or "options" or "super" key a list of running applications (like alt-tab) and a text window appears. I can choose from the running applications or write a command into the text window. After I chose an application or press ESC all this disappear and I can do my thing. Since trying 21.04 sometimes this 1. does not appear properly - there is no visible text window 2. does not disappear - despite what I click on or what keys do I press this never disappear so I can not use my running applications or start anything new even from the menu. I have to log out and in to break this. Disabling my gnome-shell extensions or using xorg instead of wayland does not helps. Since upgrading this morning this happens every time I press Super, not just occasionally, thus making my desktop unusable. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 2 14:07:39 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-03-19 (378 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-03-06 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1922353/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1919255] Re: tracker-store crashed with signal 5
Mine still happens every day about 5 minutes after starting up On Tue, May 18, 2021, 15:10 Merlin <1919...@bugs.launchpad.net> wrote: > I saw this for a few days after a fresh install of Hirsute. It would > happen shortly after boot, but it seems to have stopped. It could be > because tracker has now scanned everything. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1919255 > > Title: > tracker-store crashed with signal 5 > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1919255/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1919255 Title: tracker-store crashed with signal 5 Status in tracker package in Ubuntu: Confirmed Bug description: This just happened... ProblemType: Crash DistroRelease: Ubuntu 21.04 Package: tracker 2.3.6-2 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 Date: Mon Mar 15 17:47:12 2021 ExecutablePath: /usr/libexec/tracker-store InstallationDate: Installed on 2021-02-28 (15 days ago) InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210227) ProcCmdline: /usr/libexec/tracker-store Signal: 5 SourcePackage: tracker StacktraceTop: () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so tracker_db_interface_sqlite_fts_delete_id () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so Title: tracker-store crashed with signal 5 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1919255/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1919255] Re: tracker-store crashed with signal 5
I saw this for a few days after a fresh install of Hirsute. It would happen shortly after boot, but it seems to have stopped. It could be because tracker has now scanned everything. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1919255 Title: tracker-store crashed with signal 5 Status in tracker package in Ubuntu: Confirmed Bug description: This just happened... ProblemType: Crash DistroRelease: Ubuntu 21.04 Package: tracker 2.3.6-2 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 Date: Mon Mar 15 17:47:12 2021 ExecutablePath: /usr/libexec/tracker-store InstallationDate: Installed on 2021-02-28 (15 days ago) InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210227) ProcCmdline: /usr/libexec/tracker-store Signal: 5 SourcePackage: tracker StacktraceTop: () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so tracker_db_interface_sqlite_fts_delete_id () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so Title: tracker-store crashed with signal 5 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1919255/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1928360] Re: Switch to Fcitx 5 for Chinese
Sure, Seth, attached please find the output from cat /var/log/audit/audit.log | grep DENIED ** Attachment added: "apparmor_denied-lines_chromium.txt" https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1928360/+attachment/5498578/+files/apparmor_denied-lines_chromium.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1928360 Title: Switch to Fcitx 5 for Chinese Status in Lubuntu default settings: New Status in Ubuntu Kylin: New Status in apparmor package in Ubuntu: New Status in language-selector package in Ubuntu: In Progress Bug description: In Debian 11 Fcitx 5 will be the default IM framework for Chinese on non-GNOME desktops. I can think it's time to make the equivalent changes in Ubuntu 21.10 as well. I'd appreciate input on the topic from the Ubuntu Kylin team as well as other Chinese speaking users. To manage notifications about this bug go to: https://bugs.launchpad.net/lubuntu-default-settings/+bug/1928360/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1928867] [NEW] System freeze on bulk rename
Public bug reported: Ubuntu 20.04 Nautilus 1:3.36.3-0ubuntu1 Bug: I have 8 files named as file-1.jpg, file-2.jpg, ... file-8.jpg When I select them all and rename using template as 'file-[1, 2, 3]' in descending order, the system freezes. Perhaps because the files already exist with same name? I was expecting the files to be renamed in descending series - file-1.jpg as file-8.jpg, file-2.jpg as file-7.jpg and so on.. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 19 00:44:49 2021 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'161' b'org.gnome.nautilus.window-state' b'initial-size' b'(891, 546)' InstallationDate: Installed on 2020-04-24 (389 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1928867 Title: System freeze on bulk rename Status in nautilus package in Ubuntu: New Bug description: Ubuntu 20.04 Nautilus 1:3.36.3-0ubuntu1 Bug: I have 8 files named as file-1.jpg, file-2.jpg, ... file-8.jpg When I select them all and rename using template as 'file-[1, 2, 3]' in descending order, the system freezes. Perhaps because the files already exist with same name? I was expecting the files to be renamed in descending series - file-1.jpg as file-8.jpg, file-2.jpg as file-7.jpg and so on.. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 19 00:44:49 2021 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'161' b'org.gnome.nautilus.window-state' b'initial-size' b'(891, 546)' InstallationDate: Installed on 2020-04-24 (389 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1928867/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [apparmor] [Bug 1928360] Re: Switch to Fcitx 5 for Chinese
On Tue, May 18, 2021 at 07:39:48PM -, Gunnar Hjalmarsson wrote: > On 2021-05-16 22:23, Gunnar Hjalmarsson wrote: > > As regards apparmor it's possible that no change is needed. > > Well, I simply tested with the Chromium snap. fcitx5 does not work in > Chromium, while fcitx4 does. So something needs to be done. Excellent, can you paste the DENIED lines from your test into the bug report? Thanks -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1928360 Title: Switch to Fcitx 5 for Chinese Status in Lubuntu default settings: New Status in Ubuntu Kylin: New Status in apparmor package in Ubuntu: New Status in language-selector package in Ubuntu: In Progress Bug description: In Debian 11 Fcitx 5 will be the default IM framework for Chinese on non-GNOME desktops. I can think it's time to make the equivalent changes in Ubuntu 21.10 as well. I'd appreciate input on the topic from the Ubuntu Kylin team as well as other Chinese speaking users. To manage notifications about this bug go to: https://bugs.launchpad.net/lubuntu-default-settings/+bug/1928360/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 923176] Re: [Upstream] Footnote Tooltip not honoring Footnote formatting
** Changed in: df-libreoffice Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/923176 Title: [Upstream] Footnote Tooltip not honoring Footnote formatting Status in LibreOffice: Won't Fix Status in libreoffice package in Ubuntu: Won't Fix Bug description: 1) lsb_release -rd Description: Ubuntu 11.10 Release: 11.10 2) apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:3.4.4-0ubuntu1 Candidate: 1:3.4.4-0ubuntu1 Version table: *** 1:3.4.4-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ oneiric-updates/main i386 Packages 100 /var/lib/dpkg/status 1:3.4.3-3ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages LibreOffice Writer 3.4.5 OOO340m1 (Build:502) 3) What is expected to happen in LibreOffice Writer via the Terminal: cd ~/Desktop && wget -c https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/923176/+attachment/2700678/+files/Untitled%201.odt -O example.odt && lowriter -nologo example.odt place the mouse cursor over the footnote link and the tooltip honors the footnote formatting. 4) What happens instead is the formatting is not honored. A screenshot of this may be found at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/923176/+attachment/2699118/+files/footnotebug.png . To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/923176/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915677] Re: [ snap ] libreoffice-style-* packages are missing ?
This fix is available in the 7.1.3 available in the --stable store channel. ** Changed in: libreoffice (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1915677 Title: [ snap ] libreoffice-style-* packages are missing ? Status in libreoffice package in Ubuntu: Fix Released Bug description: Hi, trying LibreOffice 7 as a snap on UbuntuBudgie 20.04. I generally use dark gtk theme style system wide - and some are available as snap ( Adapta ). I often use Papirus icons set - and those are also ( partly ) available as snap ( through Adpata gtk theme ). I can't see if the same choice exists while using LO as a snap : I can find some icons theme ( elementary, colibre, breeze, and so on ) but they all look designed for global light gtk themes. In other words icons in my LO are black on black. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1915677/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1928360] Re: Switch to Fcitx 5 for Chinese
On 2021-05-16 22:23, Gunnar Hjalmarsson wrote: > As regards apparmor it's possible that no change is needed. Well, I simply tested with the Chromium snap. fcitx5 does not work in Chromium, while fcitx4 does. So something needs to be done. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1928360 Title: Switch to Fcitx 5 for Chinese Status in Lubuntu default settings: New Status in Ubuntu Kylin: New Status in apparmor package in Ubuntu: New Status in language-selector package in Ubuntu: In Progress Bug description: In Debian 11 Fcitx 5 will be the default IM framework for Chinese on non-GNOME desktops. I can think it's time to make the equivalent changes in Ubuntu 21.10 as well. I'd appreciate input on the topic from the Ubuntu Kylin team as well as other Chinese speaking users. To manage notifications about this bug go to: https://bugs.launchpad.net/lubuntu-default-settings/+bug/1928360/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922353] Re: Overview sometimes fails to appear or disappear in 21.04
This bug happen to me a lot, but ramdomly. I followed instructions in comment #20 and looks like is the same bug Danien talked in comment #34, there were nothing in /var/crash ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1922353/+attachment/5498566/+files/prevboot.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1922353 Title: Overview sometimes fails to appear or disappear in 21.04 Status in gnome-shell package in Ubuntu: Incomplete Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Incomplete Status in gnome-shell source package in Hirsute: New Status in gnome-shell-extension-ubuntu-dock source package in Hirsute: New Bug description: When I press the "windows" or "options" or "super" key a list of running applications (like alt-tab) and a text window appears. I can choose from the running applications or write a command into the text window. After I chose an application or press ESC all this disappear and I can do my thing. Since trying 21.04 sometimes this 1. does not appear properly - there is no visible text window 2. does not disappear - despite what I click on or what keys do I press this never disappear so I can not use my running applications or start anything new even from the menu. I have to log out and in to break this. Disabling my gnome-shell extensions or using xorg instead of wayland does not helps. Since upgrading this morning this happens every time I press Super, not just occasionally, thus making my desktop unusable. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 2 14:07:39 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-03-19 (378 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-03-06 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1922353/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1928604] Re: ubuntu-advantage-tools should not be auto-installed on supported Ubuntu releases
Thanks for taking the time to file this bug and trying to make Ubuntu better. ubuntu-advantage-tools does not provide only a way to enable ESM, it also provides a bunch of other services (from the project README): "The Ubuntu Advantage client provides users with a simple mechanism to view, enable, and disable offerings from Canonical on their system. The following entitlements are supported: Common Criteria EAL2 certification artifacts provisioning Canonical CIS Benchmark Audit Tool Ubuntu Extended Security Maintenance FIPS 140-2 Certified Modules FIPS 140-2 Non-Certified Module Updates Livepatch Service " Those other services might be useful in non-EOL releases. Due to that, the package is installed by default in all supported releases. ** Changed in: ubuntu-advantage-tools (Ubuntu) Status: Confirmed => Invalid ** Changed in: ubuntu-meta (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1928604 Title: ubuntu-advantage-tools should not be auto-installed on supported Ubuntu releases Status in ubuntu-advantage-tools package in Ubuntu: Invalid Status in ubuntu-meta package in Ubuntu: Invalid Bug description: I understand that Canonical thinks about financial profit. It is business and it is good. But please do not install ubuntu-advantage-tools to supported releases like 18.04 LTS, 20.04 LTS and 21.04. It may confuse users. Users do not expect ESM existence on supported systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1928604/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1808716] Re: package libreoffice-common 1:5.1.6~rc2-0ubuntu1~xenial4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before att
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libreoffice (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1808716 Title: package libreoffice-common 1:5.1.6~rc2-0ubuntu1~xenial4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal Status in libreoffice package in Ubuntu: Confirmed Bug description: Not obviously a bug- Adding Libreoffice base to existing Libreoffice installation. Somehow got one copy installed, and another partially installed. Then unable to remove packages to start over. Unclear what happened. Ubuntu 16.04.5 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libreoffice-common 1:5.1.6~rc2-0ubuntu1~xenial4 ProcVersionSignature: Ubuntu 4.4.0-138.164-generic 4.4.155 Uname: Linux 4.4.0-138-generic i686 ApportVersion: 2.20.1-0ubuntu2.18 AptOrdering: libreoffice-style-galaxy: Remove libreoffice-common: Remove libreoffice-style-elementary: Remove NULL: ConfigurePending Architecture: i386 Date: Sun Dec 16 19:50:18 2018 DpkgTerminalLog: Removing libreoffice-style-elementary (1:5.1.6~rc2-0ubuntu1~xenial4) ... Removing libreoffice-style-galaxy (1:5.1.6~rc2-0ubuntu1~xenial4) ... dpkg: error processing package libreoffice-common (--remove): package is in a very bad inconsistent state; you should reinstall it before attempting a removal DuplicateSignature: package:libreoffice-common:1:5.1.6~rc2-0ubuntu1~xenial4 Removing libreoffice-style-galaxy (1:5.1.6~rc2-0ubuntu1~xenial4) ... dpkg: error processing package libreoffice-common (--remove): 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 a removal InstallationDate: Installed on 2017-09-11 (461 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release i386 (20160803) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29 SourcePackage: libreoffice Title: package libreoffice-common 1:5.1.6~rc2-0ubuntu1~xenial4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal UpgradeStatus: Upgraded to xenial on 2017-12-13 (368 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1808716/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1875015] Re: Ubuntu 20.04 and Displaylink is extremely slow
Since I've migrated to Linux Mint 20.1 MATE (from Xubuntu), no problem for me anymore. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1875015 Title: Ubuntu 20.04 and Displaylink is extremely slow Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Confirmed Bug description: Using ubuntu 20.04 on displaylink docking with external monitor is totally slow, unusable. The GUI responds very slow, if you click, the command of the click goes on after about 3 seconds... if you type, all the letters are with the same lag, so it is totally unusable. Was using displaylink without any problem on 19.10 until yesterday, when I upgraded to 20.04. It is terrific. If i plug out the usb for the displaylink docking station, than the speed is back, and the system is ok, if I connect it to the docking station again, everything extremely slow again. Please investigate this asap, as it is unusable on displaylink docking stations. To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1875015/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 273507] Re: No sound effects play when "play sound effects when buttons are clicked" is enabled
@Chris that linked comment seems like spam, I reported it now -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libcanberra in Ubuntu. https://bugs.launchpad.net/bugs/273507 Title: No sound effects play when "play sound effects when buttons are clicked" is enabled Status in libcanberra package in Ubuntu: Triaged Bug description: Binary package hint: libcanberra-gtk-module As initially detailed in some of the comments in #258703, selecting the "Play sound effects when buttons are clicked" has no effect. The instructions in this mailing list post (https://tango.0pointer.de/pipermail/libcanberra- discuss/2008-July/21.html) need to be followed to enable libcanberra gtk integration, which will properly enable gtk-sound effects. Quoted here: "...Packagers! If you package libcanberra, make sure to include a script like this one in your package: #!/bin/sh if [ -z "$GTK_MODULES" ] ; then GTK_MODULES="libcanberra-gtk-module" else GTK_MODULES="$GTK_MODULES:libcanberra-gtk-module" fi export GTK_MODULES This script should be sourced in each Gnome session and will enable the libcanberra gtk module for all gtk programs. In fedora we install it as "libcanberra-gtk-module.sh" in /etc/X11/xinit/xinitrc.d/. I assume other distributions have similar directories. ..." I think this is missing from the ubuntu libcanberra packages, which is preventing the gtk sound effects from working properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcanberra/+bug/273507/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1875015] Re: Ubuntu 20.04 and Displaylink is extremely slow
Seems some people here are using the DisplayLink driver offered by the company for USB3-based DL-devices. I ran into this bug using the udl driver, since I'm using a DL-device based on one of the older USB2 DisplayLink chipsets. Confirmed the problem in Mint 20.1 and Ubuntu 20.04.2. In Ubuntu, I also tried Wayland but couldn't get DL working there at all. Some people here have stated that it helped running one of the screens with VGA or HDMI. Didn't help me though. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1875015 Title: Ubuntu 20.04 and Displaylink is extremely slow Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Confirmed Bug description: Using ubuntu 20.04 on displaylink docking with external monitor is totally slow, unusable. The GUI responds very slow, if you click, the command of the click goes on after about 3 seconds... if you type, all the letters are with the same lag, so it is totally unusable. Was using displaylink without any problem on 19.10 until yesterday, when I upgraded to 20.04. It is terrific. If i plug out the usb for the displaylink docking station, than the speed is back, and the system is ok, if I connect it to the docking station again, everything extremely slow again. Please investigate this asap, as it is unusable on displaylink docking stations. To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1875015/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872522] Re: Ubuntu software will not install .deb files on focal fossa
*** This bug is a duplicate of bug 1867610 *** https://bugs.launchpad.net/bugs/1867610 make sure you have set "open with" to "software-install" in my case it was set to just "software". hope it helps -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1872522 Title: Ubuntu software will not install .deb files on focal fossa Status in gnome-software package in Ubuntu: Incomplete Bug description: On focal fossa Ubuntu software will not install .deb files (such as Google Chrome installer) however gdebi has no problem with the same files. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-software (not installed) ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Apr 13 19:36:10 2020 InstallationDate: Installed on 2020-04-12 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1872522/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1925238] Re: [nvidia-prime] switches between xorg and wayland session
** Tags removed: rls-hh-incoming ** Also affects: ubuntu-drivers-common (Ubuntu Impish) Importance: Undecided Assignee: Alberto Milone (albertomilone) Status: New ** Also affects: ubuntu-drivers-common (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: ubuntu-drivers-common (Ubuntu Hirsute) Assignee: (unassigned) => Alberto Milone (albertomilone) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1925238 Title: [nvidia-prime] switches between xorg and wayland session Status in ubuntu-drivers-common package in Ubuntu: New Status in ubuntu-drivers-common source package in Hirsute: New Status in ubuntu-drivers-common source package in Impish: New Bug description: I have noticed this on a hirsute install from today's RC media (20210420) with ubuntu-drivers-common 1:0.8.9.1. The first boot is always xorg, and nvidia mode is selected. After that reboots are *usually* wayland, but sometimes they are xorg too. Performance mode is selected in nvidia-settings, which is supposed to mean nvidia & therefore xorg but it's not working. Selecting it explicitly doesn't help either. What is the default meant to be - probably ondemand? Seems like it's somehow nondeterministic. Attaching some logs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1925238/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873895] Re: Regression: block staircase display with side-by-side monitors of different pixel widths
Sean, can you provide a debdiff for amdgpu please? I'm happy to sponsor it if you do that, ping me on IRC or something. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1873895 Title: Regression: block staircase display with side-by-side monitors of different pixel widths Status in xf86-video-amd: Unknown Status in Xfwm4: Unknown Status in xfwm4 package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: Triaged Status in xfwm4 source package in Focal: In Progress Status in xserver-xorg-video-amdgpu source package in Focal: Triaged Status in xfwm4 source package in Groovy: Fix Released Status in xserver-xorg-video-amdgpu source package in Groovy: Triaged Bug description: [Impact] * This issue affects AMD graphics on Xfwm4 4.14.1. * Windows are displayed staggered with a multi-window layout [Test Plan] * Use AMD graphics drivers * Connect a second display at a different resolution * Open multiple windows * While the issue is present, the windows and desktop will appeared staggered * Once fixed, they display normally. [Where problems could occur] * Regression potential should be relatively low, as the release between 4.14.1 and 4.14.5 are bug releases. * With window managers, some changes could lead to different behavior and other broken displays. Non-AMD graphics users should also test for regressions. [Other Info] * Please see the Xfwm4 release notes for changes between 4.14.1 and 4.14.5: https://gitlab.xfce.org/xfce/xfwm4/-/blob/xfce-4.14/NEWS#L7-44 [Original Report] Update based on further research. This only happens when the secondary external display is operating at a different pixel width to the internal. In this case eDP is 1920x1080 whereas the external HDMI-A-0 is natively 1680x1050. It is caused by xfwm4's recent switch from using glx to xpresent for AMD GPUs. The underlying bug is in the AMD driver. I was able to reproduce on an external 1920x1200 display only when it was set to a non-native 1680x1050 resolution. --- Two identical Lenovo E495 laptops with 20.04 installed. The problem occurred initially on the laptop that is having package upgrades applied regularly. With dual monitors and the external monitor placed left or right the display has a blocked staircase effect shown in the attached photograph, and seems related to https://gitlab.freedesktop.org/xorg/driver/xf86-video- amdgpu/-/issues/10 More detailed investigation suggests it only happens when the X coordinate of the two monitors is different. The symptom looks like an off-by-one error because it appears as if the display is divided into, say, 10 rows and 15 columns but the first row has 16 'columns' worth of blocks on it and so wraps to the beginning of the 2nd row, and so on. On the laptop without package upgrades being applied this didn't happen. So I upgraded it (314 packages) and restarted and it too sees the same problem. I suspected libxcomposite1 and downgraded it to 1:0.4.5-0ubuntu1 but that didn't solve it. I now suspect libxcb but so far haven't been able to prove it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad E595 [17aa:5124] InstallationDate: Installed on 2020-04-08 (11 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408) MachineType: LENOVO 20NECTO1WW Package: xserver-xorg-video-amdgpu 19.1.0-1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/ELLOE000-rootfs ro acpi_osi=! "acpi_osi=Windows 2016" quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal ubuntu ubuntu Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sudo users _MarkForUpload: True dmi.bios.date: 12/23/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R11ET32W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NECTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias:
[Desktop-packages] [Bug 1922353] Re: Overview sometimes fails to appear or disappear in 21.04
Accepting the rls nomination. Daniel, can you maybe get Marco to review the MR upstream and then prepare backports for ubuntu/debian? ** Also affects: gnome-shell (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu Hirsute) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Hirsute) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Tags removed: rls-hh-incoming rls-ii-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1922353 Title: Overview sometimes fails to appear or disappear in 21.04 Status in gnome-shell package in Ubuntu: Incomplete Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Incomplete Status in gnome-shell source package in Hirsute: New Status in gnome-shell-extension-ubuntu-dock source package in Hirsute: New Bug description: When I press the "windows" or "options" or "super" key a list of running applications (like alt-tab) and a text window appears. I can choose from the running applications or write a command into the text window. After I chose an application or press ESC all this disappear and I can do my thing. Since trying 21.04 sometimes this 1. does not appear properly - there is no visible text window 2. does not disappear - despite what I click on or what keys do I press this never disappear so I can not use my running applications or start anything new even from the menu. I have to log out and in to break this. Disabling my gnome-shell extensions or using xorg instead of wayland does not helps. Since upgrading this morning this happens every time I press Super, not just occasionally, thus making my desktop unusable. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 2 14:07:39 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-03-19 (378 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-03-06 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1922353/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918446] Re: [MIR] libmanette
Override component to main libmanette 0.2.6-2 in impish: universe/misc -> main gir1.2-manette-0.2 0.2.6-2 in impish amd64: universe/introspection/optional/100% -> main gir1.2-manette-0.2 0.2.6-2 in impish arm64: universe/introspection/optional/100% -> main gir1.2-manette-0.2 0.2.6-2 in impish armhf: universe/introspection/optional/100% -> main gir1.2-manette-0.2 0.2.6-2 in impish ppc64el: universe/introspection/optional/100% -> main gir1.2-manette-0.2 0.2.6-2 in impish riscv64: universe/introspection/optional/100% -> main gir1.2-manette-0.2 0.2.6-2 in impish s390x: universe/introspection/optional/100% -> main libmanette-0.2-0 0.2.6-2 in impish amd64: universe/libs/optional/100% -> main libmanette-0.2-0 0.2.6-2 in impish arm64: universe/libs/optional/100% -> main libmanette-0.2-0 0.2.6-2 in impish armhf: universe/libs/optional/100% -> main libmanette-0.2-0 0.2.6-2 in impish ppc64el: universe/libs/optional/100% -> main libmanette-0.2-0 0.2.6-2 in impish riscv64: universe/libs/optional/100% -> main libmanette-0.2-0 0.2.6-2 in impish s390x: universe/libs/optional/100% -> main libmanette-0.2-dev 0.2.6-2 in impish amd64: universe/libdevel/optional/100% -> main libmanette-0.2-dev 0.2.6-2 in impish arm64: universe/libdevel/optional/100% -> main libmanette-0.2-dev 0.2.6-2 in impish armhf: universe/libdevel/optional/100% -> main libmanette-0.2-dev 0.2.6-2 in impish ppc64el: universe/libdevel/optional/100% -> main libmanette-0.2-dev 0.2.6-2 in impish riscv64: universe/libdevel/optional/100% -> main libmanette-0.2-dev 0.2.6-2 in impish s390x: universe/libdevel/optional/100% -> main Override [y|N]? y 19 publications overridden. ** Changed in: libmanette (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmanette in Ubuntu. https://bugs.launchpad.net/bugs/1918446 Title: [MIR] libmanette Status in libmanette package in Ubuntu: Fix Released Bug description: * Availability Built for all supported architectures. In sync with Debian. https://launchpad.net/ubuntu/+source/libmanette/0.2.5-1 * Rationale It's a new optional build-depends from webkitgtk. It's enabled in Debian and an useful feature to have actived in Ubuntu. The binary needed in main is the library, libmanette-0.2-0. The dev and the gir binary are going to promoted in addition. * Security No known security issues https://security-tracker.debian.org/tracker/source-package/libmanette https://launchpad.net/ubuntu/+source/libmanette/+cve https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=libmanette * Quality assurance - The desktop-packages team is going to be subscribed - No open reports https://bugs.launchpad.net/ubuntu/+source/libmanette https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=libmanette https://gitlab.gnome.org/aplazas/libmanette/-/issues The tests are enabled during the build 1/3 ManetteEventMapping test OK 0.01s 2/3 ManetteMapping testOK 0.01s 3/3 ManetteMappingManager test OK 0.01s There is currently no autopkgtest * Dependencies The dependencies are in main Depends: libc6 (>= 2.4), libevdev2 (>= 1.4.5), libglib2.0-0 (>= 2.50.0), libgudev-1.0-0 (>= 146) * Standards compliance Use current Standards-Version and dh13 * Maintenance The Debian maintainer is active, the package is in sync, the Desktop Team is going to maintain it in Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmanette/+bug/1918446/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1926165] Re: Bass speakers not enabled on Lenovo Yoga 9i
DAC1 - no sound DAC2 - sound(only through the top speaker bar) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1926165 Title: Bass speakers not enabled on Lenovo Yoga 9i Status in alsa-driver package in Ubuntu: Confirmed Bug description: The Lenovo Yoga 9i has two sets of speakers: regular ones and bass speakers. The former work but while latter are detected and show up in alsamixer, they play no sound. Plugging headphones in and out or toggling any of the volume options does not fix the issue. A possibly related issue for a different Yoga version: https://bugzilla.kernel.org/show_bug.cgi?id=205755 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: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4466 F pulseaudio ubuntu 6219 F alsamixer /dev/snd/pcmC0D0p: ubuntu 4466 F...m pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.461 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 26 15:10:05 2021 LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp successful Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [82BG, Realtek ALC287, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/28/2021 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: EHCN40WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 9 14ITL5 dmi.ec.firmware.release: 1.40 dmi.modalias: dmi:bvnLENOVO:bvrEHCN40WW:bd01/28/2021:br1.40:efr1.40:svnLENOVO:pn82BG:pvrYoga914ITL5:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrYoga914ITL5: dmi.product.family: Yoga 9 14ITL5 dmi.product.name: 82BG dmi.product.sku: LENOVO_MT_82BG_BU_idea_FM_Yoga 9 14ITL5 dmi.product.version: Yoga 9 14ITL5 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1926165/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1926165] Re: Bass speakers not enabled on Lenovo Yoga 9i
> 1st test: set the DAC1 volume to minimum, and set the DAC2 volume to maximum, could you still hear the music? Does the sound comes from front speaker or rear speaker? Music works, bass speakers are not enabled. > 2nd test: set the DAC1 voluem to maximum, and set the DAC2 volume to minimum, could you still hear the music? Does the sound comes from front speaker or rear speaker? There is no sound at all. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1926165 Title: Bass speakers not enabled on Lenovo Yoga 9i Status in alsa-driver package in Ubuntu: Confirmed Bug description: The Lenovo Yoga 9i has two sets of speakers: regular ones and bass speakers. The former work but while latter are detected and show up in alsamixer, they play no sound. Plugging headphones in and out or toggling any of the volume options does not fix the issue. A possibly related issue for a different Yoga version: https://bugzilla.kernel.org/show_bug.cgi?id=205755 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: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4466 F pulseaudio ubuntu 6219 F alsamixer /dev/snd/pcmC0D0p: ubuntu 4466 F...m pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.461 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 26 15:10:05 2021 LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp successful Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [82BG, Realtek ALC287, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/28/2021 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: EHCN40WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 9 14ITL5 dmi.ec.firmware.release: 1.40 dmi.modalias: dmi:bvnLENOVO:bvrEHCN40WW:bd01/28/2021:br1.40:efr1.40:svnLENOVO:pn82BG:pvrYoga914ITL5:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrYoga914ITL5: dmi.product.family: Yoga 9 14ITL5 dmi.product.name: 82BG dmi.product.sku: LENOVO_MT_82BG_BU_idea_FM_Yoga 9 14ITL5 dmi.product.version: Yoga 9 14ITL5 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1926165/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1926165] Re: Bass speakers not enabled on Lenovo Yoga 9i
Not sure if it helps, but when i run speaker-test -c 5, all 5 channels get sent to the speaker bar up top. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1926165 Title: Bass speakers not enabled on Lenovo Yoga 9i Status in alsa-driver package in Ubuntu: Confirmed Bug description: The Lenovo Yoga 9i has two sets of speakers: regular ones and bass speakers. The former work but while latter are detected and show up in alsamixer, they play no sound. Plugging headphones in and out or toggling any of the volume options does not fix the issue. A possibly related issue for a different Yoga version: https://bugzilla.kernel.org/show_bug.cgi?id=205755 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: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4466 F pulseaudio ubuntu 6219 F alsamixer /dev/snd/pcmC0D0p: ubuntu 4466 F...m pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.461 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 26 15:10:05 2021 LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp successful Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [82BG, Realtek ALC287, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/28/2021 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: EHCN40WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 9 14ITL5 dmi.ec.firmware.release: 1.40 dmi.modalias: dmi:bvnLENOVO:bvrEHCN40WW:bd01/28/2021:br1.40:efr1.40:svnLENOVO:pn82BG:pvrYoga914ITL5:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrYoga914ITL5: dmi.product.family: Yoga 9 14ITL5 dmi.product.name: 82BG dmi.product.sku: LENOVO_MT_82BG_BU_idea_FM_Yoga 9 14ITL5 dmi.product.version: Yoga 9 14ITL5 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1926165/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1890716] Re: misidentifies .html file as Perl script when it contains JavaScript "use strict"
shared-mime-info 2.0-1 Published in groovy-release on 2020-10-14 ** Changed in: shared-mime-info (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1890716 Title: misidentifies .html file as Perl script when it contains JavaScript "use strict" Status in shared-mime-info: Unknown Status in qtbase-opensource-src package in Ubuntu: Invalid Status in shared-mime-info package in Ubuntu: Fix Released Status in shared-mime-info package in Debian: Confirmed Bug description: For .html files `xdg-mime` reports wrong type. The culprit is the `"use strict"` phrase which is used in JavaScript. It should not mistake .html files for anything else except of text/html ! STEPS TO REPRODUCE: Run the following step by step in any folder: 1. $ echo "\"use strict\"" > index.html 2. $ xdg-mime query filetype index.html # -> application/x-perl - this should be text/html! Platform: Ubuntu 20.04.1 LTS (Focal Fossa)" Linux version 5.4.0-42-generic (buildd@lgw01-amd64-038) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) xdg-utils: 1.1.3-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/shared-mime-info/+bug/1890716/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1890716] Re: misidentifies .html file as Perl script when it contains JavaScript "use strict"
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource- src/+bug/1857824/comments/12 ** Changed in: qtbase-opensource-src (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1890716 Title: misidentifies .html file as Perl script when it contains JavaScript "use strict" Status in shared-mime-info: Unknown Status in qtbase-opensource-src package in Ubuntu: Invalid Status in shared-mime-info package in Ubuntu: Fix Released Status in shared-mime-info package in Debian: Confirmed Bug description: For .html files `xdg-mime` reports wrong type. The culprit is the `"use strict"` phrase which is used in JavaScript. It should not mistake .html files for anything else except of text/html ! STEPS TO REPRODUCE: Run the following step by step in any folder: 1. $ echo "\"use strict\"" > index.html 2. $ xdg-mime query filetype index.html # -> application/x-perl - this should be text/html! Platform: Ubuntu 20.04.1 LTS (Focal Fossa)" Linux version 5.4.0-42-generic (buildd@lgw01-amd64-038) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) xdg-utils: 1.1.3-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/shared-mime-info/+bug/1890716/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1928536] Re: VNC Password cleared on reboot
Thank you for your bug report. Could you perhaps report it upstream as well on https://gitlab.gnome.org/jadahl/gnome-remote-desktop/issues ? ** Package changed: vino (Ubuntu) => gnome-remote-desktop (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1928536 Title: VNC Password cleared on reboot Status in gnome-remote-desktop package in Ubuntu: New Bug description: Password is set using the Screen Sharing settings... Screen sharing works till next machine reboot. After reboot the password entry is cleared in the settings and cannot connect anymore. The following line appears in syslog: May 15 09:53:37 alpha gnome-remote-de[1512]: Couldn't retrieve VNC password: Password not set Setting the password again in settings solves the problem... but this isn't very helpful on a machine which is meant to run headless. Thanks, J. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: vino 3.22.0-6ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat May 15 10:40:49 2021 InstallationDate: Installed on 2019-01-03 (862 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: vino UpgradeStatus: Upgraded to hirsute on 2021-05-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1928536/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1928642] Re: [SRU] libreoffice 7.0.6 for groovy
Hello Rico, or anyone else affected, Accepted libreoffice into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libreoffice/1:7.0.6-0ubuntu0.20.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Description changed: [Impact] * LibreOffice 7.0.6 is in its sixth bugfix release of the 7.0 line: https://wiki.documentfoundation.org/ReleasePlan/7.0#7.0.6_release * Version 7.0.5 is currently released in groovy. For a list of fixed bugs compared to 7.0.5 see the list of bugs fixed in the release candidates of 7.0.6 (that's a total of 50 bugs): https://wiki.documentfoundation.org/Releases/7.0.6/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.0.6/RC2#List_of_fixed_bugs * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_linux_gcc_release/82662/console * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-groovy-ricotz-ppa/groovy/amd64/libr/libreoffice/20210518_015036_da635@/log.gz * [arm64] ... * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-groovy-ricotz-ppa/groovy/armhf/libr/libreoffice/20210518_112400_10446@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-groovy-ricotz-ppa/groovy/ppc64el/libr/libreoffice/20210518_025204_037c5@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-groovy-ricotz-ppa/groovy/s390x/libr/libreoffice/20210518_014102_69cc4@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 50 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. + + [Additional Information] + + This upload carries two new patches without DEP-3 headers - their meaning can be seen through the commit messages here though: + * https://git.launchpad.net/~libreoffice/ubuntu/+source/libreoffice/commit/?h=wip/groovy-7.0=1105fa6e0e54e12a48c7a2115c61c8f8353f4ede + * https://git.launchpad.net/~libreoffice/ubuntu/+source/libreoffice/commit/?h=wip/groovy-7.0=4d38d4a68b6fe542d10712d38ff92fd9dc296014 ** Changed in: libreoffice (Ubuntu Groovy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-groovy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1928642 Title: [SRU] libreoffice 7.0.6 for groovy Status
[Desktop-packages] [Bug 1882143] Re: /usr/lib/libreoffice/program/soffice.bin:11:SvtBroadcaster::Add:SvtListener::StartListening:SwAccessibleNoTextFrame::SwAccessibleNoTextFrame:SwAccessibleGraphic::S
** Changed in: df-libreoffice Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1882143 Title: /usr/lib/libreoffice/program/soffice.bin:11:SvtBroadcaster::Add:SvtListener::StartListening:SwAccessibleNoTextFrame::SwAccessibleNoTextFrame:SwAccessibleGraphic::SwAccessibleGraphic:SwAccessibleMap::GetContext Status in LibreOffice: Fix Released Status in libreoffice package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding libreoffice. This problem was most recently seen with package version 1:6.4.3-0ubuntu0.20.04.1, the problem page at https://errors.ubuntu.com/problem/caec6eae4d3f44d6d42c65c3f1a882a3d15ce34e 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/df-libreoffice/+bug/1882143/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882143]
Thanks for testing! Setting to Verified then -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1882143 Title: /usr/lib/libreoffice/program/soffice.bin:11:SvtBroadcaster::Add:SvtListener::StartListening:SwAccessibleNoTextFrame::SwAccessibleNoTextFrame:SwAccessibleGraphic::SwAccessibleGraphic:SwAccessibleMap::GetContext Status in LibreOffice: Fix Released Status in libreoffice package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding libreoffice. This problem was most recently seen with package version 1:6.4.3-0ubuntu0.20.04.1, the problem page at https://errors.ubuntu.com/problem/caec6eae4d3f44d6d42c65c3f1a882a3d15ce34e 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/df-libreoffice/+bug/1882143/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1890716] Re: misidentifies .html file as Perl script when it contains JavaScript "use strict"
** Package changed: kde-cli-tools (Ubuntu) => qtbase-opensource-src (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1890716 Title: misidentifies .html file as Perl script when it contains JavaScript "use strict" Status in shared-mime-info: Unknown Status in qtbase-opensource-src package in Ubuntu: New Status in shared-mime-info package in Ubuntu: Fix Committed Status in shared-mime-info package in Debian: Confirmed Bug description: For .html files `xdg-mime` reports wrong type. The culprit is the `"use strict"` phrase which is used in JavaScript. It should not mistake .html files for anything else except of text/html ! STEPS TO REPRODUCE: Run the following step by step in any folder: 1. $ echo "\"use strict\"" > index.html 2. $ xdg-mime query filetype index.html # -> application/x-perl - this should be text/html! Platform: Ubuntu 20.04.1 LTS (Focal Fossa)" Linux version 5.4.0-42-generic (buildd@lgw01-amd64-038) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) xdg-utils: 1.1.3-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/shared-mime-info/+bug/1890716/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1928791] [NEW] gnome-shell runs on 60--100% CPU usage
Public bug reported: from top output: top - 14:18:02 up 5:45, 1 user, load average: 1,55, 1,54, 1,77 Tasks: 419 total, 1 running, 418 sleeping, 0 stopped, 0 zombie %Cpu(s): 13,2 us, 2,6 sy, 0,0 ni, 83,7 id, 0,1 wa, 0,0 hi, 0,4 si, 0,0 st MiB Mem : 7960,7 total,233,0 free, 5719,6 used, 2008,1 buff/cache MiB Swap: 26058,0 total, 23596,0 free, 2462,0 used.576,0 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 20866 tobias20 0 6652668 996,0m 83472 S 63,4 12,5 33:56.49 gnome-shell this is so wrong… how to fix it? best, Tobias ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.7-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 18 14:11:41 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-22 (300 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1928791 Title: gnome-shell runs on 60--100% CPU usage Status in gnome-shell package in Ubuntu: New Bug description: from top output: top - 14:18:02 up 5:45, 1 user, load average: 1,55, 1,54, 1,77 Tasks: 419 total, 1 running, 418 sleeping, 0 stopped, 0 zombie %Cpu(s): 13,2 us, 2,6 sy, 0,0 ni, 83,7 id, 0,1 wa, 0,0 hi, 0,4 si, 0,0 st MiB Mem : 7960,7 total,233,0 free, 5719,6 used, 2008,1 buff/cache MiB Swap: 26058,0 total, 23596,0 free, 2462,0 used.576,0 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 20866 tobias20 0 6652668 996,0m 83472 S 63,4 12,5 33:56.49 gnome-shell this is so wrong… how to fix it? best, Tobias ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.7-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 18 14:11:41 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-22 (300 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1928791/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1770271] Re: VegaM support
** Changed in: amd Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1770271 Title: VegaM support Status in amd: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in linux source package in Xenial: Won't Fix Status in mesa source package in Xenial: Won't Fix Status in linux source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Released Bug description: VegaM is a new GPU. Please include support for VegaM in the next LTS (16.04.x and 18.04.x) and non-LTS releases. Kernel support starts here (32 patches): https://patchwork.freedesktop.org/patch/218839/ Mesa support: https://cgit.freedesktop.org/mesa/mesa/commit/?id=d6a66bc8dbcdeed8e87f649bc281de0d60d2f123 https://cgit.freedesktop.org/mesa/mesa/commit/?id=c6f1d360198c52d208645c0ccb5e988cded408e8 https://cgit.freedesktop.org/mesa/mesa/commit/?id=90de03708fa269ad54de881b467f4811e4eef87e To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1770271/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1928787] Re: package libreoffice-common 1:6.4.6-0ubuntu0.20.04.1 failed to install/upgrade: unable to open '/usr/lib/libreoffice/share/template/common/presnt/Progress.otp.dpkg-
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1928787 Title: package libreoffice-common 1:6.4.6-0ubuntu0.20.04.1 failed to install/upgrade: unable to open '/usr/lib/libreoffice/share/template/common/presnt/Progress.otp.dpkg- new': Operation not permitted Status in libreoffice package in Ubuntu: New Bug description: Background update failed. This followed system boot. I am not skilled enough in Ubuntu to be able to troubleshoot to determine if truly a bug or something else. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libreoffice-common 1:6.4.6-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_52_57_generic_77 ApportVersion: 2.20.11-0ubuntu27.16 AptOrdering: libreoffice-common:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Tue May 11 21:15:03 2021 DpkgHistoryLog: Start-Date: 2021-05-11 21:14:48 Commandline: apt-get install -f Requested-By: ibgrizzly (1000) Upgrade: libreoffice-common:amd64 (1:6.4.6-0ubuntu0.20.04.1, 1:6.4.7-0ubuntu0.20.04.1) DpkgTerminalLog: Preparing to unpack .../libreoffice-common_1%3a6.4.7-0ubuntu0.20.04.1_all.deb ... Unpacking libreoffice-common (1:6.4.7-0ubuntu0.20.04.1) over (1:6.4.6-0ubuntu0.20.04.1) ... dpkg: error processing archive /var/cache/apt/archives/libreoffice-common_1%3a6.4.7-0ubuntu0.20.04.1_all.deb (--unpack): unable to open '/usr/lib/libreoffice/share/template/common/presnt/Progress.otp.dpkg-new': Operation not permitted DuplicateSignature: package:libreoffice-common:1:6.4.6-0ubuntu0.20.04.1 Unpacking libreoffice-common (1:6.4.7-0ubuntu0.20.04.1) over (1:6.4.6-0ubuntu0.20.04.1) ... dpkg: error processing archive /var/cache/apt/archives/libreoffice-common_1%3a6.4.7-0ubuntu0.20.04.1_all.deb (--unpack): unable to open '/usr/lib/libreoffice/share/template/common/presnt/Progress.otp.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/lib/libreoffice/share/template/common/presnt/Progress.otp.dpkg-new': Operation not permitted InstallationDate: Installed on 2020-10-18 (212 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: libreoffice Title: package libreoffice-common 1:6.4.6-0ubuntu0.20.04.1 failed to install/upgrade: unable to open '/usr/lib/libreoffice/share/template/common/presnt/Progress.otp.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1928787/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1928787] [NEW] package libreoffice-common 1:6.4.6-0ubuntu0.20.04.1 failed to install/upgrade: unable to open '/usr/lib/libreoffice/share/template/common/presnt/Progress.otp.dpk
Public bug reported: Background update failed. This followed system boot. I am not skilled enough in Ubuntu to be able to troubleshoot to determine if truly a bug or something else. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libreoffice-common 1:6.4.6-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_52_57_generic_77 ApportVersion: 2.20.11-0ubuntu27.16 AptOrdering: libreoffice-common:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Tue May 11 21:15:03 2021 DpkgHistoryLog: Start-Date: 2021-05-11 21:14:48 Commandline: apt-get install -f Requested-By: ibgrizzly (1000) Upgrade: libreoffice-common:amd64 (1:6.4.6-0ubuntu0.20.04.1, 1:6.4.7-0ubuntu0.20.04.1) DpkgTerminalLog: Preparing to unpack .../libreoffice-common_1%3a6.4.7-0ubuntu0.20.04.1_all.deb ... Unpacking libreoffice-common (1:6.4.7-0ubuntu0.20.04.1) over (1:6.4.6-0ubuntu0.20.04.1) ... dpkg: error processing archive /var/cache/apt/archives/libreoffice-common_1%3a6.4.7-0ubuntu0.20.04.1_all.deb (--unpack): unable to open '/usr/lib/libreoffice/share/template/common/presnt/Progress.otp.dpkg-new': Operation not permitted DuplicateSignature: package:libreoffice-common:1:6.4.6-0ubuntu0.20.04.1 Unpacking libreoffice-common (1:6.4.7-0ubuntu0.20.04.1) over (1:6.4.6-0ubuntu0.20.04.1) ... dpkg: error processing archive /var/cache/apt/archives/libreoffice-common_1%3a6.4.7-0ubuntu0.20.04.1_all.deb (--unpack): unable to open '/usr/lib/libreoffice/share/template/common/presnt/Progress.otp.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/lib/libreoffice/share/template/common/presnt/Progress.otp.dpkg-new': Operation not permitted InstallationDate: Installed on 2020-10-18 (212 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: libreoffice Title: package libreoffice-common 1:6.4.6-0ubuntu0.20.04.1 failed to install/upgrade: unable to open '/usr/lib/libreoffice/share/template/common/presnt/Progress.otp.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1928787 Title: package libreoffice-common 1:6.4.6-0ubuntu0.20.04.1 failed to install/upgrade: unable to open '/usr/lib/libreoffice/share/template/common/presnt/Progress.otp.dpkg- new': Operation not permitted Status in libreoffice package in Ubuntu: New Bug description: Background update failed. This followed system boot. I am not skilled enough in Ubuntu to be able to troubleshoot to determine if truly a bug or something else. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libreoffice-common 1:6.4.6-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_52_57_generic_77 ApportVersion: 2.20.11-0ubuntu27.16 AptOrdering: libreoffice-common:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Tue May 11 21:15:03 2021 DpkgHistoryLog: Start-Date: 2021-05-11 21:14:48 Commandline: apt-get install -f Requested-By: ibgrizzly (1000) Upgrade: libreoffice-common:amd64 (1:6.4.6-0ubuntu0.20.04.1, 1:6.4.7-0ubuntu0.20.04.1) DpkgTerminalLog: Preparing to unpack .../libreoffice-common_1%3a6.4.7-0ubuntu0.20.04.1_all.deb ... Unpacking libreoffice-common (1:6.4.7-0ubuntu0.20.04.1) over (1:6.4.6-0ubuntu0.20.04.1) ... dpkg: error processing archive /var/cache/apt/archives/libreoffice-common_1%3a6.4.7-0ubuntu0.20.04.1_all.deb (--unpack): unable to open '/usr/lib/libreoffice/share/template/common/presnt/Progress.otp.dpkg-new': Operation not permitted DuplicateSignature: package:libreoffice-common:1:6.4.6-0ubuntu0.20.04.1 Unpacking libreoffice-common (1:6.4.7-0ubuntu0.20.04.1) over (1:6.4.6-0ubuntu0.20.04.1) ... dpkg: error processing archive /var/cache/apt/archives/libreoffice-common_1%3a6.4.7-0ubuntu0.20.04.1_all.deb (--unpack): unable to open '/usr/lib/libreoffice/share/template/common/presnt/Progress.otp.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/lib/libreoffice/share/template/common/presnt/Progress.otp.dpkg-new': Operation not permitted InstallationDate: Installed on 2020-10-18 (212 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
[Desktop-packages] [Bug 1843760] Re: Please add a PPA to track only the Still Branch across major versions of LibreOffice
Introduced as https://launchpad.net/~libreoffice/+archive/ubuntu /libreoffice-still ** Changed in: libreoffice (Ubuntu) Assignee: (unassigned) => Rico Tzschichholz (ricotz) ** Changed in: libreoffice (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1843760 Title: Please add a PPA to track only the Still Branch across major versions of LibreOffice Status in libreoffice package in Ubuntu: Fix Released Bug description: Upstream LibreOffice provides two branches of LibreOffice, the Fresh Branch (6.3.0) and the Still Branch (6.2.7). In Ubuntu there is a PPA that tracks the Fresh Branch (LibreOffice Fresh) and separate PPAs that track one major version of LO without crossing to a higher version in the same PPA. I suggest creating a new PPA that tracks only the Still Branch of LibreOffice. Meaning, today the latest version in the still branch is 6.2.6, the last release from the 6.2.x branch is 6.2.7 and its end of life is on November 30, 2019. Afterwards the still branch will track the 6.3.x branch from the 6.3.4 release and so on. So the PPA would have: 6.2.6 ⇒ 6.2.7 (EOL) ⇒ 6.3.4 ⇒ 6.3.5 ⇒ 6.3.6 (EOL) ⇒ 6.4.4 ⇒ 6.4.5 ⇒ 6.4.6 ⇒ ... and so on. The reason why I ask this is that almost always the first three releases of a new major version of LO are buggy and have regressions. The 6.3.0 version that I'm on now is buggy, but at the same time, newer versions of LO fix bugs and UI enhancements that probably will never be backported to older branches like the one in Bionic. So tracking only the Still Branch solves this issue especially for enterprise and school users. The Still Branch PPA would target only the Ubuntu LTS releases, Xenial and Bionic, because it doesn't make sense to target the short-lived releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1843760/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1928642] Re: [SRU] libreoffice 7.0.6 for groovy
** Description changed: [Impact] * LibreOffice 7.0.6 is in its sixth bugfix release of the 7.0 line: https://wiki.documentfoundation.org/ReleasePlan/7.0#7.0.6_release * Version 7.0.5 is currently released in groovy. For a list of fixed bugs compared to 7.0.5 see the list of bugs fixed in the release candidates of 7.0.6 (that's a total of 50 bugs): https://wiki.documentfoundation.org/Releases/7.0.6/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.0.6/RC2#List_of_fixed_bugs * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_linux_gcc_release/82662/console * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-groovy-ricotz-ppa/groovy/amd64/libr/libreoffice/20210518_015036_da635@/log.gz * [arm64] ... - * [armhf] ... + * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-groovy-ricotz-ppa/groovy/armhf/libr/libreoffice/20210518_112400_10446@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-groovy-ricotz-ppa/groovy/ppc64el/libr/libreoffice/20210518_025204_037c5@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-groovy-ricotz-ppa/groovy/s390x/libr/libreoffice/20210518_014102_69cc4@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 50 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1928642 Title: [SRU] libreoffice 7.0.6 for groovy Status in libreoffice package in Ubuntu: In Progress Status in libreoffice source package in Groovy: In Progress Bug description: [Impact] * LibreOffice 7.0.6 is in its sixth bugfix release of the 7.0 line: https://wiki.documentfoundation.org/ReleasePlan/7.0#7.0.6_release * Version 7.0.5 is currently released in groovy. For a list of fixed bugs compared to 7.0.5 see the list of bugs fixed in the release candidates of 7.0.6 (that's a total of 50 bugs): https://wiki.documentfoundation.org/Releases/7.0.6/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.0.6/RC2#List_of_fixed_bugs * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_linux_gcc_release/82662/console * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. * [amd64]
[Desktop-packages] [Bug 273507] Re: No sound effects play when "play sound effects when buttons are clicked" is enabled
Hi its a good weather with a good smoke from https://www.medicalmarijuanabudshop.com/ their service is amazing try them out -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libcanberra in Ubuntu. https://bugs.launchpad.net/bugs/273507 Title: No sound effects play when "play sound effects when buttons are clicked" is enabled Status in libcanberra package in Ubuntu: Triaged Bug description: Binary package hint: libcanberra-gtk-module As initially detailed in some of the comments in #258703, selecting the "Play sound effects when buttons are clicked" has no effect. The instructions in this mailing list post (https://tango.0pointer.de/pipermail/libcanberra- discuss/2008-July/21.html) need to be followed to enable libcanberra gtk integration, which will properly enable gtk-sound effects. Quoted here: "...Packagers! If you package libcanberra, make sure to include a script like this one in your package: #!/bin/sh if [ -z "$GTK_MODULES" ] ; then GTK_MODULES="libcanberra-gtk-module" else GTK_MODULES="$GTK_MODULES:libcanberra-gtk-module" fi export GTK_MODULES This script should be sourced in each Gnome session and will enable the libcanberra gtk module for all gtk programs. In fedora we install it as "libcanberra-gtk-module.sh" in /etc/X11/xinit/xinitrc.d/. I assume other distributions have similar directories. ..." I think this is missing from the ubuntu libcanberra packages, which is preventing the gtk sound effects from working properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcanberra/+bug/273507/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1928001] Re: [SRU] New stable release 2.68.1
automake-1.16> same started happening in impish too - you could cherry- pick 2b8b44ffc37047231757780952f6290398fb73e2 to the hints maybe? netplan.io> slyon told me this is known bad and is skipped in other releases already (upstream) and will be included in the next SRU to hirsute, if any. could be hinted too? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1928001 Title: [SRU] New stable release 2.68.1 Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Hirsute: Fix Committed Bug description: [ Description ] Take this new upstream stable release. * Fix a crash in `GKeyFile` when parsing a file which contains translations using a `GKeyFile` instance which has loaded another file previously (#2361) * Pin GIO DLL in memory on Windows (!2016) * Bugs fixed: - #2361 g_key_file_load_from_file segfaults on "Key[*]="like lines - !1997 Backport !1996 “Include glibconfig.h to get the G_OS_UNIX token” to glib-2-68 - !2016 GIO W32: Pin gio DLL - !2021 Backport MR !2016 (GIO W32: Pin gio DLL) into glib-2-68 - !2022 Few fixes and notes for building on Visual Studio 2012 and earlier - !2034 Backport MR !2032 (gkeyfile: Drop a redundant check) into glib-2-68 - !2035 Backport !2026 “Split g_test_log() messages that contain multiple lines” to glib-2-68 [ QA ] Upstream release, so QA already performed by maintainers https://wiki.ubuntu.com/StableReleaseUpdates/GNOME This upload will trigger many autopkgtests that we expect to not be regressed by this upload. [ What could go wrong ] This update contains fixes in multiple places so multiple apps could be affected. The consequences of a broken GLib can range from some functions returning bad results sometimes, which have minimal runtime implications, up to the system simply crashing all the time. Pretty much all parts of GNOME use GLib, so test anything in the desktop that you can. If you reboot the machine and can get to the desktop, that's already tested GLib extensively. But also run applications like GNOME terminal, Files and Epiphany. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1928001/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1928586] Re: Desktop icons disappearing
No. It's not bug 1812883. I've actually described in detail what happens. The desktop icons aren't flashing. They disappear and stay invisible until I reactivate USB tethering. Let me describe the steps again: Step 1. Desktop icons are visible. Step 2. I connect my phone to the PC. Desktop icons are still visible. At this point, there's a dialog box on the phone's screen, asking "Allow access to phones data?". Options for me are to click "Allow" or "Deny". Step 3. Whether I click Allow or Deny, the Desktop icons disappear. Step 4. I activate USB tethering, and the Desktop icons appear. Step 5. I deactivate USB tethering, and the Desktop icons are still visible. The phone is again asking the Allow/Deny question. Step 6. Goto Step 3. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1928586 Title: Desktop icons disappearing Status in gnome-shell-extension-desktop-icons package in Ubuntu: Incomplete Bug description: This is in Ubuntu 20.10 Groovy Gorilla. The bug: When connecting to USB tethering and allowing access to the phone's filesystem, Ubuntu's Desktop icons disappear. Steps to reproduce: Connect a phone to the computer via USB tethering (am a bit uneasy about mentioning which model phone it is). Switch on USB tethering and then switch off USB tethering in the phone's Mobile hotspot and tethering options. The phones screen will popup a dialog box asking "Allow access to phone data?" (which is a way to give the computer access to the phone's filesystem). You can click either "Allow" or "Deny". When either "Allow" or "Deny" is selected, the Desktop icons on Ubuntu disappear. When USB tethering is switched back on, the Desktop icons reappear. I've attached a video of the phenomenon. The video starts with USB tethering being switched on, which is why you can see the desktop icons. Then when USB tethering is switched off and "Allow" is clicked on the phone, the icons disappear and then they reappear when USB tethering is switched on again. This bug is probably related to bugs #1928206 and #1928213, which indicate that there are some inconsistencies with how the Nautilus Desktop works with respect to a Nautilus window. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1928586/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1928618] Re: Desktop Sharing password not being saved
The desktop sharing is using gnome-remote-desktop now. Why did you close the report? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vino in Ubuntu. https://bugs.launchpad.net/bugs/1928618 Title: Desktop Sharing password not being saved Status in vino package in Ubuntu: Invalid Bug description: Desktop Sharing (assuming it's still vino) password not being saved in Gnome Shell Ubuntu 21.04 after reboot. I can go to the Settings app and Desktop Sharing is active, I set a password, then close the box and Settings then reboot the machine. I can't then connect to that desktop as after the reboot the password field is blank again. This worked fine in 20.10. It's not a crash so no files/error reports known. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vino/+bug/1928618/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1928763] Re: Ubuntu does not recognize the touchpad
*** This bug is a duplicate of bug 1881319 *** https://bugs.launchpad.net/bugs/1881319 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 1881319, 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 1881319 Touchpad not recognized Lenovo IdeaPad 5 15ARE05 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1928763 Title: Ubuntu does not recognize the touchpad Status in linux package in Ubuntu: New Bug description: The device in question is a Lenovo IdeaPad 5 15ARE05. Using the touchpad does not work in Ubuntu. Input does not get recognized. Using an external USB mouse works fine. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 18 10:07:58 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c3) (prog-if 00 [VGA controller]) Subsystem: Lenovo Renoir [17aa:381b] InstallationDate: Installed on 2021-03-24 (54 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210322) MachineType: LENOVO 81YQ ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic root=UUID=216cd85a-60ae-4f84-b68c-ba90f8154877 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.39 dmi.bios.vendor: LENOVO dmi.bios.version: E7CN39WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 15ARE05 dmi.ec.firmware.release: 1.39 dmi.modalias: dmi:bvnLENOVO:bvrE7CN39WW:bd01/14/2021:br1.39:efr1.39:svnLENOVO:pn81YQ:pvrIdeaPad515ARE05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad515ARE05: dmi.product.family: IdeaPad 5 15ARE05 dmi.product.name: 81YQ dmi.product.sku: LENOVO_MT_81YQ_BU_idea_FM_IdeaPad 5 15ARE05 dmi.product.version: IdeaPad 5 15ARE05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928763/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1928586] Re: Desktop icons disappearing
Yeah it sounds like this should be grouped into bug 1812883. ** Tags added: groovy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1928586 Title: Desktop icons disappearing Status in gnome-shell-extension-desktop-icons package in Ubuntu: Incomplete Bug description: This is in Ubuntu 20.10 Groovy Gorilla. The bug: When connecting to USB tethering and allowing access to the phone's filesystem, Ubuntu's Desktop icons disappear. Steps to reproduce: Connect a phone to the computer via USB tethering (am a bit uneasy about mentioning which model phone it is). Switch on USB tethering and then switch off USB tethering in the phone's Mobile hotspot and tethering options. The phones screen will popup a dialog box asking "Allow access to phone data?" (which is a way to give the computer access to the phone's filesystem). You can click either "Allow" or "Deny". When either "Allow" or "Deny" is selected, the Desktop icons on Ubuntu disappear. When USB tethering is switched back on, the Desktop icons reappear. I've attached a video of the phenomenon. The video starts with USB tethering being switched on, which is why you can see the desktop icons. Then when USB tethering is switched off and "Allow" is clicked on the phone, the icons disappear and then they reappear when USB tethering is switched on again. This bug is probably related to bugs #1928206 and #1928213, which indicate that there are some inconsistencies with how the Nautilus Desktop works with respect to a Nautilus window. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1928586/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1928763] [NEW] Ubuntu does not recognize the touchpad
Public bug reported: The device in question is a Lenovo IdeaPad 5 15ARE05. Using the touchpad does not work in Ubuntu. Input does not get recognized. Using an external USB mouse works fine. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 18 10:07:58 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c3) (prog-if 00 [VGA controller]) Subsystem: Lenovo Renoir [17aa:381b] InstallationDate: Installed on 2021-03-24 (54 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210322) MachineType: LENOVO 81YQ ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic root=UUID=216cd85a-60ae-4f84-b68c-ba90f8154877 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.39 dmi.bios.vendor: LENOVO dmi.bios.version: E7CN39WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 15ARE05 dmi.ec.firmware.release: 1.39 dmi.modalias: dmi:bvnLENOVO:bvrE7CN39WW:bd01/14/2021:br1.39:efr1.39:svnLENOVO:pn81YQ:pvrIdeaPad515ARE05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad515ARE05: dmi.product.family: IdeaPad 5 15ARE05 dmi.product.name: 81YQ dmi.product.sku: LENOVO_MT_81YQ_BU_idea_FM_IdeaPad 5 15ARE05 dmi.product.version: IdeaPad 5 15ARE05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ubuntu wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1928763 Title: Ubuntu does not recognize the touchpad Status in xorg package in Ubuntu: New Bug description: The device in question is a Lenovo IdeaPad 5 15ARE05. Using the touchpad does not work in Ubuntu. Input does not get recognized. Using an external USB mouse works fine. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 18 10:07:58 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c3) (prog-if 00 [VGA controller]) Subsystem: Lenovo Renoir [17aa:381b] InstallationDate: Installed on 2021-03-24 (54 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210322) MachineType: LENOVO 81YQ ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic root=UUID=216cd85a-60ae-4f84-b68c-ba90f8154877 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.39 dmi.bios.vendor: LENOVO dmi.bios.version: E7CN39WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 15ARE05 dmi.ec.firmware.release: 1.39 dmi.modalias: dmi:bvnLENOVO:bvrE7CN39WW:bd01/14/2021:br1.39:efr1.39:svnLENOVO:pn81YQ:pvrIdeaPad515ARE05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad515ARE05:
[Desktop-packages] [Bug 1927827] Re: Error launching cheese: Native Windows taller than 65535 pixels are not supported
** Package changed: cheese (Ubuntu) => gtk+3.0 (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1927827 Title: Error launching cheese: Native Windows taller than 65535 pixels are not supported Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: Attempting to run cheese on a HDPI display in Wayland results in the following errors: (cheese:9303): Gdk-CRITICAL **: 10:29:11.221: gdk_wayland_window_set_dbus_properties_libgtk_only: assertion 'GDK_IS_WAYLAND_WINDOW (window)' failed (cheese:9303): Gdk-WARNING **: 10:29:11.265: Native Windows taller than 65535 pixels are not supported When this error happens, the cheese window does not open. Sometimes the "Native Windows ... not supported" does not occur, the cheese window does open. However, the photo area is black. I can work around this problem by changing the "Photo resolution" in preferences to a different value, and then changing it back. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: cheese 3.38.0-3 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 CasperMD5CheckResult: pass CurrentDesktop: Ubuntu-Blue:ubuntu:GNOME Date: Sat May 8 10:32:03 2021 InstallationDate: Installed on 2021-04-28 (10 days ago) InstallationMedia: Ubuntu 21.04.0 2021.04.27 amd64 "Custom Hirsute Hippo" (20210427) MachineType: HP HP Spectre x360 Convertible 15-bl1XX ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: cheese3.38.0-3 cheese-common 3.38.0-3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/15/2020 dmi.bios.release: 15.43 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.43 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 827F dmi.board.vendor: HP dmi.board.version: 95.11 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 95.11 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.43:bd12/15/2020:br15.43:efr95.11:svnHP:pnHPSpectrex360Convertible15-bl1XX:pvr:rvnHP:rn827F:rvr95.11:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 15-bl1XX dmi.product.sku: 1VW22AV dmi.sys.vendor: HP lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 064e:3401 Suyin Corp. HP TrueVision FHD RGB-IR Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Ubuntu-Blue:ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-28 (17 days ago) InstallationMedia: Ubuntu 21.04.0 2021.04.27 amd64 "Custom Hirsute Hippo" (20210427) MachineType: HP HP Spectre x360 Convertible 15-bl1XX NonfreeKernelModules: nvidia_modeset nvidia Package: cheese 3.38.0-3 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 RelatedPackageVersions: cheese3.38.0-3 cheese-common 3.38.0-3 Tags: hirsute gstreamer-error Uname: Linux 5.11.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 12/15/2020 dmi.bios.release: 15.43 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.43 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 827F dmi.board.vendor: HP dmi.board.version: 95.11 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 95.11 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.43:bd12/15/2020:br15.43:efr95.11:svnHP:pnHPSpectrex360Convertible15-bl1XX:pvr:rvnHP:rn827F:rvr95.11:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 15-bl1XX dmi.product.sku: 1VW22AV dmi.sys.vendor: HP lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 064e:3401 Suyin Corp. HP TrueVision FHD RGB-IR Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub To manage notifications about this bug go to:
[Desktop-packages] [Bug 1927305] Re: google acount login not working, get stuck at loading screen
nothing interesting there, and is gnome-control-center printing any warning or error? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1927305 Title: google acount login not working, get stuck at loading screen Status in gnome-control-center package in Ubuntu: Incomplete Bug description: Every time I try to log in to my Google account in settings, after entering the details and clicking allow button settings get stuck and it did not even get closed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 6 10:18:59 2021 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-lancel+X97 InstallationDate: Installed on 2020-11-16 (170 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2020-11-21 (166 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1927305/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1928586] Re: Desktop icons disappearing
Thank you for your bug report, that's a gnome-shell-extension-desktop- icons issue. Are the icons coming back directly or what do you do to get them? Could be bug #1812883 for example ** Package changed: nautilus (Ubuntu) => gnome-shell-extension-desktop- icons (Ubuntu) ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1928586 Title: Desktop icons disappearing Status in gnome-shell-extension-desktop-icons package in Ubuntu: Incomplete Bug description: This is in Ubuntu 20.10 Groovy Gorilla. The bug: When connecting to USB tethering and allowing access to the phone's filesystem, Ubuntu's Desktop icons disappear. Steps to reproduce: Connect a phone to the computer via USB tethering (am a bit uneasy about mentioning which model phone it is). Switch on USB tethering and then switch off USB tethering in the phone's Mobile hotspot and tethering options. The phones screen will popup a dialog box asking "Allow access to phone data?" (which is a way to give the computer access to the phone's filesystem). You can click either "Allow" or "Deny". When either "Allow" or "Deny" is selected, the Desktop icons on Ubuntu disappear. When USB tethering is switched back on, the Desktop icons reappear. I've attached a video of the phenomenon. The video starts with USB tethering being switched on, which is why you can see the desktop icons. Then when USB tethering is switched off and "Allow" is clicked on the phone, the icons disappear and then they reappear when USB tethering is switched on again. This bug is probably related to bugs #1928206 and #1928213, which indicate that there are some inconsistencies with how the Nautilus Desktop works with respect to a Nautilus window. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1928586/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1928213] Re: Open with other application not working for multi file select and not showing cascading menu for single file select
** Tags added: groovy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1928213 Title: Open with other application not working for multi file select and not showing cascading menu for single file select Status in gnome-shell-extension-desktop-icons package in Ubuntu: New Bug description: This is in Ubuntu 20.10 Groovy Gorilla. Problem 1: As shown in the attached image, on selecting multiple files and right clicking to "Open with other application", the option for opening the files is not enabled. Problem 2: When right clicking a single file, the "Open with other application" is visible, but does not show a cascading dropdown menu like it used to in Ubuntu 16.04. The cascading menu would help avoid some unnecessary extra clicks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1928213/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1928213] Re: Open with other application not working for multi file select and not showing cascading menu for single file select
Thank you for your bug report, bug #1887816 is also about inconsistency in this dialog ** Package changed: ubuntu => gnome-shell-extension-desktop-icons (Ubuntu) ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1928213 Title: Open with other application not working for multi file select and not showing cascading menu for single file select Status in gnome-shell-extension-desktop-icons package in Ubuntu: New Bug description: This is in Ubuntu 20.10 Groovy Gorilla. Problem 1: As shown in the attached image, on selecting multiple files and right clicking to "Open with other application", the option for opening the files is not enabled. Problem 2: When right clicking a single file, the "Open with other application" is visible, but does not show a cascading dropdown menu like it used to in Ubuntu 16.04. The cascading menu would help avoid some unnecessary extra clicks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1928213/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1928213] [NEW] Open with other application not working for multi file select and not showing cascading menu for single file select
You have been subscribed to a public bug: This is in Ubuntu 20.10 Groovy Gorilla. Problem 1: As shown in the attached image, on selecting multiple files and right clicking to "Open with other application", the option for opening the files is not enabled. Problem 2: When right clicking a single file, the "Open with other application" is visible, but does not show a cascading dropdown menu like it used to in Ubuntu 16.04. The cascading menu would help avoid some unnecessary extra clicks. ** Affects: gnome-shell-extension-desktop-icons (Ubuntu) Importance: Low Status: New ** Tags: bot-comment -- Open with other application not working for multi file select and not showing cascading menu for single file select https://bugs.launchpad.net/bugs/1928213 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1928602] Re: Cyberpunk 1.22 crashes with amdgpu ring gfx_0.0.0 timeout
GPU DRIVER: 4.6 Mesa 21.1.0 - kisak-mesa PPA we don't have that even in impish yet -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1928602 Title: Cyberpunk 1.22 crashes with amdgpu ring gfx_0.0.0 timeout Status in mesa package in Ubuntu: New Bug description: Please see details in this link: https://gitlab.freedesktop.org/drm/amd/-/issues/934#note_916755 This happens when I try to play Cyberpunk 2077 1.22 in Proton. I use Proton-6.8-GE-1. The game launches, it plays fine but when I open the Inventory, it crashes. All other Proton versions crash the game immediately or very frequently with this graphics driver timeout. (Note this happened very rarely on Cyberpunk 1.21, other games seem to work fine and my system is otherwise stable) I was told to file a bug against mesa. OS: Ubuntu 20.04.2 LTS KERNEL: 5.12.3-xanmod1 CPU: AMD Ryzen 7 3700X 8-Core GPU: AMD AMD Radeon RX 5700 XT (NAVI10, DRM 3.40.0, 5.12.3-xanmod1, LLVM 12.0.0) GPU DRIVER: 4.6 Mesa 21.1.0 - kisak-mesa PPA RAM: 32 GB Kernel Arguments GRUB_CMDLINE_LINUX_DEFAULT="usbcore.autosuspend=-1 quiet splash radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1 amdgpu.noretry=0" Summary May 13 12:17:26 hackintosh Cyberpunk 2077.desktop[8529]: It has either not been recorded, or it failed to be recorded earlier (which is expected if application uses an extension that is not recognized by Fossilize). May 13 12:17:36 hackintosh kernel: [ 257.280586] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out! May 13 12:17:36 hackintosh kernel: [ 262.282283] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=21, emitted seq=23 May 13 12:17:36 hackintosh kernel: [ 262.282477] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Cyberpunk2077.e pid Full Log May 13 12:17:26 hackintosh Cyberpunk 2077.desktop[8529]: It has either not been recorded, or it failed to be recorded earlier (which is expected if application uses an extension that is not recognized by Fossilize). May 13 12:17:26 hackintosh Cyberpunk 2077.desktop[8529]: Fossilize WARN: Render pass handle 0x7fb8b546e460 is not registered. May 13 12:17:26 hackintosh Cyberpunk 2077.desktop[8529]: It has either not been recorded, or it failed to be recorded earlier (which is expected if application uses an extension that is not recognized by Fossilize). May 13 12:17:26 hackintosh Cyberpunk 2077.desktop[8529]: Fossilize WARN: Render pass handle 0x7fb8c13ca0a0 is not registered. May 13 12:17:26 hackintosh Cyberpunk 2077.desktop[8529]: It has either not been recorded, or it failed to be recorded earlier (which is expected if application uses an extension that is not recognized by Fossilize). May 13 12:17:26 hackintosh Cyberpunk 2077.desktop[8529]: Fossilize WARN: Render pass handle 0x7fb8c13ca0a0 is not registered. May 13 12:17:26 hackintosh Cyberpunk 2077.desktop[8529]: It has either not been recorded, or it failed to be recorded earlier (which is expected if application uses an extension that is not recognized by Fossilize). May 13 12:17:36 hackintosh kernel: [ 257.280586] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out! May 13 12:17:36 hackintosh kernel: [ 262.282283] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=21, emitted seq=23 May 13 12:17:36 hackintosh kernel: [ 262.282477] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Cyberpunk2077.e pid 8529 thread Cyberpunk2077.e pid 8529 May 13 12:17:36 hackintosh kernel: [ 262.282652] amdgpu :0c:00.0: amdgpu: GPU reset begin! May 13 12:17:36 hackintosh kernel: [ 262.400268] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out! May 13 12:17:36 hackintosh kernel: [ 262.660931] amdgpu :0c:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring kiq_2.1.0 test failed (-110) May 13 12:17:36 hackintosh kernel: [ 262.661006] [drm:gfx_v10_0_hw_fini [amdgpu]] *ERROR* KGQ disable failed May 13 12:17:36 hackintosh kernel: [ 262.904580] amdgpu :0c:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring kiq_2.1.0 test failed (-110) May 13 12:17:36 hackintosh kernel: [ 262.904654] [drm:gfx_v10_0_hw_fini [amdgpu]] *ERROR* KCQ disable failed May 13 12:17:37 hackintosh kernel: [ 263.148241] [drm:gfx_v10_0_hw_fini [amdgpu]] *ERROR* failed to halt cp gfx May 13 12:17:37 hackintosh kernel: [ 263.158091] [drm] free PSP TMR buffer May 13 12:17:37 hackintosh kernel: [ 263.197727] amdgpu :0c:00.0: amdgpu: BACO reset May 13 12:17:40 hackintosh kernel: [ 266.340490] amdgpu :0c:00.0: amdgpu: GPU reset succeeded, trying to resume May 13 12:17:40 hackintosh kernel: [
[Desktop-packages] [Bug 1926165] Re: Bass speakers not enabled on Lenovo Yoga 9i
@Tim and Jussi, I tried to find the same machine as yours in our office, but there is no 9i, c930 or c940. Please do one more test, then I will ask for help from Realtek according to the test result. Boot with the standard kernel (not my testing kernel), play some music through the speaker, open a terminal, run alsamixer, 1st test: set the DAC1 volume to minimum, and set the DAC2 volume to maximum, could you still hear the music? Does the sound comes from front speaker or rear speaker? 2nd test: set the DAC1 voluem to maximum, and set the DAC2 volume to minimum, could you still hear the music? Does the sound comes from front speaker or rear speaker? thx. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1926165 Title: Bass speakers not enabled on Lenovo Yoga 9i Status in alsa-driver package in Ubuntu: Confirmed Bug description: The Lenovo Yoga 9i has two sets of speakers: regular ones and bass speakers. The former work but while latter are detected and show up in alsamixer, they play no sound. Plugging headphones in and out or toggling any of the volume options does not fix the issue. A possibly related issue for a different Yoga version: https://bugzilla.kernel.org/show_bug.cgi?id=205755 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: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4466 F pulseaudio ubuntu 6219 F alsamixer /dev/snd/pcmC0D0p: ubuntu 4466 F...m pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.461 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 26 15:10:05 2021 LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp successful Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [82BG, Realtek ALC287, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/28/2021 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: EHCN40WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 9 14ITL5 dmi.ec.firmware.release: 1.40 dmi.modalias: dmi:bvnLENOVO:bvrEHCN40WW:bd01/28/2021:br1.40:efr1.40:svnLENOVO:pn82BG:pvrYoga914ITL5:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrYoga914ITL5: dmi.product.family: Yoga 9 14ITL5 dmi.product.name: 82BG dmi.product.sku: LENOVO_MT_82BG_BU_idea_FM_Yoga 9 14ITL5 dmi.product.version: Yoga 9 14ITL5 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1926165/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
