[Desktop-packages] [Bug 1931701] Re: autopkgtests failures on armhf of 7.1.4
** Description changed: The autopkgtests for 7.1.4~rc2-0ubuntu1 on impish/armhf has started to fail reliably. https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/armhf/libr/libreoffice/20210610_121847_0ab56@/log.gz "/usr/lib/libreoffice/program/unopkg" add -f "/tmp/tmp.oOlP0i1pzN/out/sdk/LINUXexample.out/bin/SampleDialog.oxt" # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0xf47474b8, pid=35616, tid=35643 # # JRE version: OpenJDK Runtime Environment (11.0.12+4) (build 11.0.12-ea+4-Ubuntu-0ubuntu2) # Java VM: OpenJDK Server VM (11.0.12-ea+4-Ubuntu-0ubuntu2, mixed mode, g1 gc, linux-) # Problematic frame: - # C [libbootstraplo.so+0x1c4b8] + # C [libbootstraplo.so+0x1c4b8] stoc_impreg::mergeKeys(com::sun::star::uno::Reference const&, com::sun::star::uno::Reference const&, std::vector >&)+0xb # # Core dump will be written. Default location: Core dumps may be processed with "/usr/share/apport/apport %p %s %c %d %P %E" (or dumping to /usr/lib/libreoffice/sdk/examples/DevelopersGuide/BasicAndDialogs/CreatingDialogs/core.35616) # # An error report file with more information is saved as: # /tmp/hs_err_pid35616.log # # If you would like to submit a bug report, please visit: # https://bugs.launchpad.net/ubuntu/+source/openjdk-lts # ERROR: Exception occurred: Binary URP bridge disposed during call ./binaryurp/source/bridge.cxx:613 ERROR: unopkg failed. make[1]: Leaving directory '/usr/lib/libreoffice/sdk/examples/DevelopersGuide/BasicAndDialogs/CreatingDialogs' make[1]: *** [Makefile:112: /tmp/tmp.oOlP0i1pzN/out/sdk/LINUXexample.out/misc/devguide_basicanddialogs_creatingdialogs_register_component.flag] Error 1 make[1]: Target 'ALL' not remade because of errors. make: *** [/tmp/autopkgtest.U74TIg/build.myd/src/odk/CustomTarget_build-examples_java.mk:62: /tmp/autopkgtest.U74TIg/build.myd/src/workdir/CustomTarget/odk/build-examples_java.done] Error 2 make: Target 'CustomTarget_odk/build-examples_java' not remade because of errors. While a re-run of the test for 7.1.3-0ubuntu1 were successful it suggests it is binary problem. https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/armhf/libr/libreoffice/20210609_234830_1265b@/log.gz liberoffice is built with gcc-9/g++-9 on armhf to avoid https://bugs.launchpad.net/ubuntu/+source/gcc-10/+bug/1891623 A significant difference in the used toolchain points to the update of gcc-9 7.1.3-0ubuntu1 was built with gcc 9.3.0-24ubuntu1 https://launchpadlibrarian.net/537628130/buildlog_ubuntu-impish-armhf.libreoffice_1%3A7.1.3-0ubuntu1_BUILDING.txt.gz 7.1.4~rc2-0ubuntu1 was built with gcc 9.4.0-1ubuntu1 https://launchpadlibrarian.net/542492348/buildlog_ubuntu-impish-armhf.libreoffice_1%3A7.1.4~rc2-0ubuntu1_BUILDING.txt.gz Regarding 21.04/Hirsute 1:7.1.4~rc2-0ubuntu0.21.04.1~lo1 built and successfully ran autopkgtests, see https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1931272 If was using the gcc-9 9.3.0-23ubuntu2 available at the time. The no-change rebuild against 9.4.0-1ubuntu1~21.04 results in the same failure now. https://launchpadlibrarian.net/543392061/buildlog_ubuntu-hirsute-armhf.libreoffice_1%3A7.1.4~rc2-0ubuntu0.21.04.1~lo1_BUILDING.txt.gz https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute-libreoffice-experimental/hirsute/armhf/libr/libreoffice/20210612_113218_f7f69@/log.gz -- 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/1931701 Title: autopkgtests failures on armhf of 7.1.4 Status in gcc-9 package in Ubuntu: New Status in libreoffice package in Ubuntu: New Status in gcc-9 source package in Hirsute: New Status in libreoffice source package in Hirsute: New Status in gcc-9 source package in Impish: New Status in libreoffice source package in Impish: New Bug description: The autopkgtests for 7.1.4~rc2-0ubuntu1 on impish/armhf has started to fail reliably. https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/armhf/libr/libreoffice/20210610_121847_0ab56@/log.gz "/usr/lib/libreoffice/program/unopkg" add -f "/tmp/tmp.oOlP0i1pzN/out/sdk/LINUXexample.out/bin/SampleDialog.oxt" # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0xf47474b8, pid=35616, tid=35643 # # JRE version: OpenJDK Runtime Environment (11.0.12+4) (build 11.0.12-ea+4-Ubuntu-0ubuntu2) # Java VM: OpenJDK Server VM (11.0.12-ea+4-Ubuntu-0ubuntu2, mixed mode, g1 gc, linux-) # Problematic frame: # C [libbootstraplo.so+0x1c4b8] stoc_impreg::mergeKeys(com::sun::star::uno::Reference const&, com::sun::star::uno::Reference const&, std::vector >&)+0xb # # Core dump will be written. Default location: Core dumps may be
[Desktop-packages] [Bug 1930641] Re: memory leak in xorg-server 2:1.20.9-2ubuntu1.2~20.04.2
Well, it's not libreoffice nor evolution mail client. And I also tried Unity with X instead of fallback, no better, so it doesn't look like metacity. I'll try more experiments tomorrow -- 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/1930641 Title: memory leak in xorg-server 2:1.20.9-2ubuntu1.2~20.04.2 Status in libreoffice package in Ubuntu: New Status in xorg-server package in Ubuntu: Incomplete Bug description: Progressive memory leak in Xorg. With 16Gb RAM, memory use increases by about 1% each day according to top. Started at about 1%, now 24% after nearly 3 weeks. Video driver is i915, uname -m shows x86_64. Ubuntu 20.04, up to date as at 29 May 2021. HDMI connector. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME-Flashback:GNOME Date: Thu Jun 3 11:06:35 2021 DistUpgraded: 2021-04-26 20:35:01,095 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-73-generic, x86_64: installed virtualbox-guest, 6.1.16, 5.4.0-73-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd HD Graphics 5500 [1458:1000] InstallationDate: Installed on 2017-05-31 (1463 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: GIGABYTE GB-BXi7-5500 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic root=UUID=6999d6bd-6356-4df2-b056-032c25b2dd60 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2021-04-26 (37 days ago) dmi.bios.date: 12/05/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MQLP7AP-00 dmi.board.vendor: GIGABYTE dmi.board.version: 1.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd12/05/2014:svnGIGABYTE:pnGB-BXi7-5500:pvr1.x:rvnGIGABYTE:rnMQLP7AP-00:rvr1.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: GB-BXi7-5500 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.x dmi.sys.vendor: GIGABYTE version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1930641/+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 1916469] Re: Apps don't use Wayland by default
Also starting in troublesooting mode I see Xwayland instead Wayland attached: text from about:support in troublesooting mode ** Attachment added: "text from about:support in troublesooting mode" https://bugs.launchpad.net/ubuntu/+source/telegram-desktop/+bug/1916469/+attachment/5505171/+files/ff91-troubleshooting.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1916469 Title: Apps don't use Wayland by default Status in firefox package in Ubuntu: Fix Released Status in qdirstat package in Ubuntu: Confirmed Status in telegram-desktop package in Ubuntu: Confirmed Status in thunderbird package in Ubuntu: Fix Released Bug description: The Ubuntu universe has a big Wayland problem! What does that mean? So a lot of packages in the Universe repository are not compiled with Wayland support which is really bad and would lead to bad performance after 21.04 comes out. Here are the following packages that I detected with wrong compilation: telegram-desktop (Wayland support work with snap version) kiwix firefox (everything works fine with this env variable set:"MOZ_ENABLE_WAYLAND=1") To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1916469/+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 1742736] Re: ubuntu software not showing progress bar in dock
** Tags added: focal -- 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/1742736 Title: ubuntu software not showing progress bar in dock Status in gnome-software package in Ubuntu: Confirmed Bug description: When installing /removing software, or when updating the system, ubuntu-software dosen't show any progress bar in it's icon on the dock , like other programs do (such as nautilus or ubuntu native's system updater). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-software 3.26.3-2ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 11 14:22:46 2018 InstallationDate: Installed on 2017-12-19 (22 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171218) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.26.3-2ubuntu1 PackageArchitecture: all 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/1742736/+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 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"
I was finally able to spend a bit of time on this. Unfortunately, there’s not much to report back. Em terça-feira, 8 de junho de 2021, às 15:13:36 -03, Thiago Jung Bauermann escreveu: > Em terça-feira, 8 de junho de 2021, às 10:30:24 -03, Alex Deucher escreveu: > > Can you narrow down which specific firmware file causes the problem? > > Ok, I will try. I don’t think I can narrow down which firmware file causes the problem, because I don’t have a last known good version. All firmware files that I tested (Ubuntu versions 1.190.5, 1.197 and latest linux-firmware.git) immediately trigger the bug when I try the only reliable reproducer I know (i.e., running flatpak’s com.github.quaternion package). Since it can take several days for the bug to happen if I just use the machine normally, it would take weeks to narrow down which of the picasso_* files is more stable relative to the others. And even then, I wouldn’t be sure about it. > > I think it may be related to a change in mesa. Specifically mesa > > commit > > 820dec3f7c7. For more info see > > https://gitlab.freedesktop.org/mesa/mesa/-/issues/4866 > > I’ll run with Mario’s build of Mesa with that patch backported. > Thanks, Mario! I’m running with the Mesa build from Mario’s PPA now. If I don’t see any issue within two weeks, I think it will be possible to say that the bug is gone, or at least much harder to hit. I can’t use my reproducer in this case, because I can’t change the Mesa version inside the flatpak image. -- 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/1928393 Title: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault" Status in amd: New Status in linux-firmware package in Ubuntu: Incomplete Status in mesa package in Ubuntu: New Bug description: After upgrading linux-firmware from 1.190.5 to 1.197 (as part of the upgrade from Ubuntu 20.10 to 21.04), I started experiencing frequent and severe GPU instability. When this happens, I see this error in dmesg: [20061.061069] amdgpu :03:00.0: amdgpu: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:1 pasid:32769, for process Xorg pid 1141 thread Xorg:cs0 pid 1236) [20061.061103] amdgpu :03:00.0: amdgpu: in page starting at address 0x80401000 from client 27 [20061.061135] amdgpu :03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00101031 [20061.061147] amdgpu :03:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8) [20061.061157] amdgpu :03:00.0: amdgpu: MORE_FAULTS: 0x1 [20061.061167] amdgpu :03:00.0: amdgpu: WALKER_ERROR: 0x0 [20061.061174] amdgpu :03:00.0: amdgpu: PERMISSION_FAULTS: 0x3 [20061.061183] amdgpu :03:00.0: amdgpu: MAPPING_ERROR: 0x0 [20061.061189] amdgpu :03:00.0: amdgpu: RW: 0x0 I'll attach a couple of full dmesgs that I collected. Many of the times when this happens, the screen and keyboard freeze irreversibly (I tried waiting for more than 30 minutes, but it doesn't help). I can still log in via ssh though. When there's no freeze, I can continue using the computer normally, but the laptop fans keep running are always running and the battery depletes fast. There's probably something on a permanent loop either in the kernel or in the GPU. This bug happens several times a day, rendering the machine so unstable as to be almost unusable. It is a severe regression and I'm aghast that it passed AMD's Quality Assurance. After downgrading back to linux-firmware 1.190.5, the machine is back to the previous, mostly-reliable state. Which is to say, this bug is gone, I'm just left with the other amdgpu suspend bug I've learned to live with since I bought this computer. Please revert the amdgpu firmware in this package as soon as possible. This is unbearable. Relevant information: Ubuntu version: 21.04 Linux kernel: 5.11.0-17-generic x86_64 CPU model: AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx GPU: 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picasso (rev c1) Laptop model: Lenovo Ideapad S145 To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1928393/+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 1931756] Re: [XPS 17 9700, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem
Then please try this kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.13-rc6/amd64/ Download linux-image-unsigned-5.13.0-051300rc6-generic_5.13.0-051300rc6.202106132230_amd64.deb linux-modules-5.13.0-051300rc6-generic_5.13.0-051300rc6.202106132230_amd64.deb sudo dpkg -i *.deb reboot; turn off secure boot from BIOS -- 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/1931756 Title: [XPS 17 9700, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem Status in alsa-driver package in Ubuntu: New Bug description: I have tried modifications to DKMS, modprobe.d, pulseaudio and alsa but all were no sound. The modprobe,d modifications did result in the "dummy" message being replaced by a device. This was done 2 installs ago,sorry. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.10.0-051000-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pbea 1894 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Fri Jun 11 23:34:27 2021 InstallationDate: Installed on 2021-06-11 (0 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Digital Out, HDMI Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [XPS 17 9700, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/04/2021 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.2 dmi.board.name: 0P25F6 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.2:bd03/04/2021:br1.7:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn0P25F6:rvrA03:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9700 dmi.product.sku: 098F dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1931756/+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 1931756] Re: [XPS 17 9700, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem
Hello again. Thank You for your continuing help. As I did before, I tried to load 5.11.0-20 but absolutely no luck. I found the packages at ubuntu.paks(?).org but they locked me up totally. My system froze halfway through the boot process. Tried it 3 times. Same result. I found some more at the ubuntu kernel team site but after loading the kernel nothing showed in grub-customizer or the grub boot menu. Synaptic shows it is loaded and so does: dpkg -l | tail -n +6 | grep -E 'linux-image-[0-9]+' | grep -Fv $(uname -r) rc linux-image-5.11.0-20-generic 5.11.0-20.21~20.04.1 amd64Signed kernel image generic rc linux-image-5.8.0-43-generic 5.8.0-43.49~20.04.1 amd64Signed kernel image generic rc linux-image-5.8.0-55-generic 5.8.0-55.62~20.04.1 amd64Signed kernel image generic ii linux-image-5.8.0-56-generic 5.8.0-56.63~20.04.1 amd64Signed kernel image generic ii linux-image-5.8.0-57-generic 5.8.0-57.64~20.04.1 amd64Signed kernel image generic 5.11.0-20 does not show on any menu. My best guess is possibly dependency issues. Can I try a later kernel? I am using LTS 20.04 and not 21.04 which may be required. Another option is for me is to pop in another ssd and try another distro. Would that work? Thank You again . . . -- 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/1931756 Title: [XPS 17 9700, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem Status in alsa-driver package in Ubuntu: New Bug description: I have tried modifications to DKMS, modprobe.d, pulseaudio and alsa but all were no sound. The modprobe,d modifications did result in the "dummy" message being replaced by a device. This was done 2 installs ago,sorry. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.10.0-051000-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pbea 1894 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Fri Jun 11 23:34:27 2021 InstallationDate: Installed on 2021-06-11 (0 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Digital Out, HDMI Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [XPS 17 9700, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/04/2021 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.2 dmi.board.name: 0P25F6 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.2:bd03/04/2021:br1.7:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn0P25F6:rvrA03:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9700 dmi.product.sku: 098F dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1931756/+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 1931901] Re: Revert background key patch removal breaks dependent packages
So the function isn't really used anywhere we care about, so I think we can just drop it https://paste.ubuntu.com/p/tyN5Vp99Fj/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/1931901 Title: Revert background key patch removal breaks dependent packages Status in gnome-desktop3 package in Ubuntu: New Status in gsettings-desktop-schemas package in Ubuntu: Invalid Bug description: in the package gnome-desktop3 there is a custom ubuntu patch that tries to write to the draw-background key that has now been removed in gsettings-desktop-schemas 40.0-1ubuntu1 All packages that depend on the gnome-desktop3 library now crash such as budgie-desktop Suggestion - either re-add the patch again ... or revert the gnome- desktop3 custom patch. The latter option changes the symbols so probably I'm guessing a so- name version bump is needed and any dependent packages need a rebuild? I'll try to locally rebuild gnome-desktop3 without the custom ubuntu patch to see what happens with budgie-desktop ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gsettings-desktop-schemas 40.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21 Uname: Linux 5.11.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Budgie:GNOME Date: Mon Jun 14 20:52:16 2021 InstallationDate: Installed on 2021-06-14 (0 days ago) InstallationMedia: Ubuntu-Budgie 21.10 "Impish Indri" - Alpha amd64 (20210614) PackageArchitecture: all SourcePackage: gsettings-desktop-schemas UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1931901/+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 1931756] Re: [XPS 17 9700, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem
@pbea, It is expected that the audio doesn't work well with 5.10.0-051000-generic kernel on your machine, what I mean is please try 5.11.0-20-generic kernel, if the audio still doesn't work with that kernel, please upload the dmesg.txt generated under that kernel. 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/1931756 Title: [XPS 17 9700, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem Status in alsa-driver package in Ubuntu: New Bug description: I have tried modifications to DKMS, modprobe.d, pulseaudio and alsa but all were no sound. The modprobe,d modifications did result in the "dummy" message being replaced by a device. This was done 2 installs ago,sorry. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.10.0-051000-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pbea 1894 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Fri Jun 11 23:34:27 2021 InstallationDate: Installed on 2021-06-11 (0 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Digital Out, HDMI Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [XPS 17 9700, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/04/2021 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.2 dmi.board.name: 0P25F6 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.2:bd03/04/2021:br1.7:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn0P25F6:rvrA03:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9700 dmi.product.sku: 098F dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1931756/+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 1932205] Re: Canon iP90 Ptr outputs blank pgs in 20.04, works in Win10
** Package changed: ubuntu => cups (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1932205 Title: Canon iP90 Ptr outputs blank pgs in 20.04, works in Win10 Status in cups package in Ubuntu: New Bug description: Ver: Ubuntu 20.04.2 LTS Expected: CUPS to print to an iP90 inkjet printer. What happens: Whenever I try to print anything to the iP90, it outputs ~14 blank pages with a ghostly thin line across the top of the page. It hesitates after drawing the sheet of paper into the machine so that's where it's printing that single line (or multiple lines but very tiny), and then spits out the page without printing anything else. That squished line on top is so small, and with the rest of the page blank, I reuse that paper when I leave Ubuntu and boot to Win10. Then I can print to the iP90 all day and the pages come out fine. What I've tried: I've loaded and deleted the CUPS driver for the iP90 numerous times to no avail. CUPS recognizes the USB printer is attached and it's name & model number. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Wed Jun 16 14:13:05 2021 Lpstat: device for Canon-iP90: usb://Canon/iP90?serial=31A4B2 device for Canon-MG2900-series: usb://Canon/MG2900%20series?serial=473C59=1 MachineType: Gigabyte Technology Co., Ltd. A520M S2H Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Canon-MG2900-series.ppd', '/etc/cups/ppd/Canon-iP90.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Canon-MG2900-series.ppd: Permission denied grep: /etc/cups/ppd/Canon-iP90.ppd: Permission denied ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-55-generic root=UUID=c201ceca-9f5a-4845-b650-e68fc9d5230f ro quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/27/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: Default string dmi.board.name: A520M S2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd07/27/2020:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnA520MS2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA520MS2H:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: A520 MB dmi.product.name: A520M S2H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1932205/+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 1932205] [NEW] Canon iP90 Ptr outputs blank pgs in 20.04, works in Win10
You have been subscribed to a public bug: Ver: Ubuntu 20.04.2 LTS Expected: CUPS to print to an iP90 inkjet printer. What happens: Whenever I try to print anything to the iP90, it outputs ~14 blank pages with a ghostly thin line across the top of the page. It hesitates after drawing the sheet of paper into the machine so that's where it's printing that single line (or multiple lines but very tiny), and then spits out the page without printing anything else. That squished line on top is so small, and with the rest of the page blank, I reuse that paper when I leave Ubuntu and boot to Win10. Then I can print to the iP90 all day and the pages come out fine. What I've tried: I've loaded and deleted the CUPS driver for the iP90 numerous times to no avail. CUPS recognizes the USB printer is attached and it's name & model number. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Wed Jun 16 14:13:05 2021 Lpstat: device for Canon-iP90: usb://Canon/iP90?serial=31A4B2 device for Canon-MG2900-series: usb://Canon/MG2900%20series?serial=473C59=1 MachineType: Gigabyte Technology Co., Ltd. A520M S2H Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Canon-MG2900-series.ppd', '/etc/cups/ppd/Canon-iP90.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Canon-MG2900-series.ppd: Permission denied grep: /etc/cups/ppd/Canon-iP90.ppd: Permission denied ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-55-generic root=UUID=c201ceca-9f5a-4845-b650-e68fc9d5230f ro quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/27/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: Default string dmi.board.name: A520M S2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd07/27/2020:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnA520MS2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA520MS2H:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: A520 MB dmi.product.name: A520M S2H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- Canon iP90 Ptr outputs blank pgs in 20.04, works in Win10 https://bugs.launchpad.net/bugs/1932205 You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups 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 1931388] Re: Firefox disaplayerror after Update on last version 89
I saw this comment for a similar issue: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1931035/comments/2 Setting layers.acceleration.disabled = true before upgrading to FF89 makes the issue go away, but now I don't have acceleration for this "feature". Since it seems to be acceleration related, here is some info on my graphics: $ sudo lshw -c video *-display description: VGA compatible controller product: GP102 [GeForce GTX 1080 Ti] vendor: NVIDIA Corporation physical id: 0 bus info: pci@:0a:00.0 version: a1 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress vga_controller bus_master cap_list rom configuration: driver=nvidia latency=0 resources: iomemory:7f0-7ef iomemory:7f0-7ef irq:178 memory:f500-f5ff memory:7fe000-7fefff memory:7ff000-7ff1ff ioport:e000(size=128) memory:f600-f607 $ modinfo nvidia filename: /lib/modules/5.11.0-18-generic/updates/dkms/nvidia.ko alias: char-major-195-* version:460.84 supported: external license:NVIDIA srcversion: BE511DEA3662B4CF045EC5D alias: pci:v10DEd*sv*sd*bc03sc02i00* alias: pci:v10DEd*sv*sd*bc03sc00i00* -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1931388 Title: Firefox disaplayerror after Update on last version 89 Status in Ubuntu MATE: New Status in firefox package in Ubuntu: Incomplete Bug description: After the last Update from Firefox Browser to Version 89 Firefox is unsuable. The Program starts but the window is somehow transparent and white. I removed and reinstalled Firefox but the problem is the same. My computer is an Amd Mashine running Ubuntu Mate 20.10 Mate 1.24.1 I took a Screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1931388/+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 1923845] Re: Please compress packages with zstd by default
This bug was fixed in the package lintian - 2.104.0ubuntu3
---
lintian (2.104.0ubuntu3) impish; urgency=medium
* Add zst as allowed compression for .deb & .udeb. Although we don't
actually ship udeb package that supports zst. LP: #1923845
-- Dimitri John Ledkov Tue, 15 Jun 2021 10:42:12
+0100
** Changed in: lintian (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream-glib in Ubuntu.
https://bugs.launchpad.net/bugs/1923845
Title:
Please compress packages with zstd by default
Status in appstream-glib package in Ubuntu:
New
Status in apt package in Ubuntu:
Fix Released
Status in aptly package in Ubuntu:
New
Status in boinc package in Ubuntu:
New
Status in busybox package in Ubuntu:
New
Status in cdebootstrap package in Ubuntu:
New
Status in cdist package in Ubuntu:
New
Status in debdelta package in Ubuntu:
New
Status in debian-el package in Ubuntu:
New
Status in debootstrap package in Ubuntu:
Fix Released
Status in debsig-verify package in Ubuntu:
New
Status in debsigs package in Ubuntu:
New
Status in diffoscope package in Ubuntu:
New
Status in dpkg package in Ubuntu:
New
Status in dpkg-sig package in Ubuntu:
New
Status in file package in Ubuntu:
New
Status in libsolv package in Ubuntu:
New
Status in lintian package in Ubuntu:
Fix Released
Status in lutris package in Ubuntu:
New
Status in obs-build package in Ubuntu:
New
Status in osc package in Ubuntu:
New
Status in radare2 package in Ubuntu:
New
Status in reprepro package in Ubuntu:
New
Status in vim-scripts package in Ubuntu:
New
Status in zeroinstall-injector package in Ubuntu:
New
Bug description:
https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built
on Hirsute having both data and control members of the .deb being
compressed with zstd. It can be handy for testing various tools.
[dpkg]
Decompression support in dpkg landed first in Bionic and is being SRUd to
Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the
zstd-compressed binary packages.
From dpkg's perspective the upgrade path is cleared.
The original plan was compressing only the internal data.tar .deb
member, but dpkg uses uniform compression by default since dpkg 1.19.0
thus I'm collecting all the changes to support control.tar.zst, too,
in this bug.
Reviewed packages from:
https://codesearch.debian.net/search?q=data.tar.xz=1=1
https://codesearch.debian.net/search?q=control.tar.xz=1=1
appstream-glib - needs fix: libappstream-builder/asb-package-deb.c
aptly - needs fix: deb/deb.go
boinc - needs fix: debian/fetch_example_applications.sh
busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c
cdebootstrap- needs fix: src/package.c
cdist - may need fix, can use dpkg-deb:
cdist/preos/debootstrap/files/devuan-debootstrap/functions
debdelta- needs fix: debdelta debpatch.sh
debian-el - needs fix: deb-view.el
debian-handbook - needs fix, maybe later, for Debian
debootstrap - needs fix,
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54
debsigs - needs fix, debsigs
debsig-verify - needs fix, src/debsig-verify.c
diffoscope - needs fix, diffoscope/comparators/deb.py
dpkg- needs fix, change default
dpkg-sig- needs fix, dpkg-sig
dpmb- needs fix, maybe later, for Debian
elfutils- may need fix, uses dpkg-deb if it is available, does not
handle .gz either
file- needs fix, magic/Magdir/archive
libsolv - needs fix, ext/repo_deb.c
lintian - needs fix malformed-deb-archive
lutris - needs fix, lutris/util/extract.py
obs-build - needs fix Build/Deb.pm
osc - needs fix osc/util/debquery.py control.tar.zst only
python-apt - needs fix
apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall()
radare2 - needs fix
reprepro- needs fix, debfile.c
vim-scripts - needs fix debPlugin/autoload/deb.vim
winetricks - needs fix when Debian switches src/winetricks
zeroinstall-injector - needs fix src/zeroinstall/archive.ml
acr - skip, does not _have to_ be fixed, just creates packages,
see dist/deb_hand.mak
alien - skip, uses dpkg-deb to extract .deb
ansible - not affected, just test data in dbdata.tar.xz
anthy - not affected, just changelog entry
apt - seems fixed already
ceph- not affected in Ubuntu's version
circlator - not affected, just test data
cowdancer - not affected, just documentation
eccodes - skip, just orig-data.tar.xz
eckit - skip, just ...orig-data.tar.xz
firefox - skip, profdata.tar.xz
firefox-esr - skip, profdata.tar.xz
[Desktop-packages] [Bug 1930982]
Pushed by lsalz...@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/c77fc5fac5ae use vqmovun_s16 for packing pixels. r=sotaro -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1930982 Title: Firefox 89: webrender breaks videos on Raspberry Pi Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Released Bug description: Firefox 89 enabled the Webrender framework by default. Unfortunately, the GFX drivers on a Pi 4 seem to be non-compliant in a way that breaks videos - specifically, there will be a lot of primary coloured artefacts in videos. My guess is that other Raspberry Pi's will also be affected, but I don't have the hardware available to test. Setting gfx.webrender.force-disabled to True fixes the issue, so it's fairly clear where it lies. Mozilla doesn't seem to provide official builds for Raspberry Pi's (or Linux/Arm in general), so I think this is an issue to fix in these packages, rather than upstream. The quick solution would to just set gfx.webrender.force-disabled to True for the Pi-platforms and be done with it, but there may be better solutions I don't know about. Additioal info: Ubuntu release: 21.04 Firefox package: firefox/hirsute-security,hirsute-updates,now 89.0+build2-0ubuntu0.21.04.1 arm64 Steps to reproduce: Play a video on Youtube, watch the coloured blocks appear. Then set gfx.webrender.force-disabled to True and restart to verify the fix. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1930982/+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 1930982]
Sotaro, can you see if my vqmovun_s16 patch fixes this or not? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1930982 Title: Firefox 89: webrender breaks videos on Raspberry Pi Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Released Bug description: Firefox 89 enabled the Webrender framework by default. Unfortunately, the GFX drivers on a Pi 4 seem to be non-compliant in a way that breaks videos - specifically, there will be a lot of primary coloured artefacts in videos. My guess is that other Raspberry Pi's will also be affected, but I don't have the hardware available to test. Setting gfx.webrender.force-disabled to True fixes the issue, so it's fairly clear where it lies. Mozilla doesn't seem to provide official builds for Raspberry Pi's (or Linux/Arm in general), so I think this is an issue to fix in these packages, rather than upstream. The quick solution would to just set gfx.webrender.force-disabled to True for the Pi-platforms and be done with it, but there may be better solutions I don't know about. Additioal info: Ubuntu release: 21.04 Firefox package: firefox/hirsute-security,hirsute-updates,now 89.0+build2-0ubuntu0.21.04.1 arm64 Steps to reproduce: Play a video on Youtube, watch the coloured blocks appear. Then set gfx.webrender.force-disabled to True and restart to verify the fix. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1930982/+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 1930982]
https://hg.mozilla.org/mozilla-central/rev/c77fc5fac5ae -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1930982 Title: Firefox 89: webrender breaks videos on Raspberry Pi Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Released Bug description: Firefox 89 enabled the Webrender framework by default. Unfortunately, the GFX drivers on a Pi 4 seem to be non-compliant in a way that breaks videos - specifically, there will be a lot of primary coloured artefacts in videos. My guess is that other Raspberry Pi's will also be affected, but I don't have the hardware available to test. Setting gfx.webrender.force-disabled to True fixes the issue, so it's fairly clear where it lies. Mozilla doesn't seem to provide official builds for Raspberry Pi's (or Linux/Arm in general), so I think this is an issue to fix in these packages, rather than upstream. The quick solution would to just set gfx.webrender.force-disabled to True for the Pi-platforms and be done with it, but there may be better solutions I don't know about. Additioal info: Ubuntu release: 21.04 Firefox package: firefox/hirsute-security,hirsute-updates,now 89.0+build2-0ubuntu0.21.04.1 arm64 Steps to reproduce: Play a video on Youtube, watch the coloured blocks appear. Then set gfx.webrender.force-disabled to True and restart to verify the fix. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1930982/+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 1930982]
Tested that commit on top of the 89.0 release, on Ubuntu 21.04 on aarch64 (Raspberry Pi 4), and I can confirm the problem is fixed. Thanks a lot :lsalzman ! I'm going to cherry-pick that commit as a distro- patch for Ubuntu packages. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1930982 Title: Firefox 89: webrender breaks videos on Raspberry Pi Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Released Bug description: Firefox 89 enabled the Webrender framework by default. Unfortunately, the GFX drivers on a Pi 4 seem to be non-compliant in a way that breaks videos - specifically, there will be a lot of primary coloured artefacts in videos. My guess is that other Raspberry Pi's will also be affected, but I don't have the hardware available to test. Setting gfx.webrender.force-disabled to True fixes the issue, so it's fairly clear where it lies. Mozilla doesn't seem to provide official builds for Raspberry Pi's (or Linux/Arm in general), so I think this is an issue to fix in these packages, rather than upstream. The quick solution would to just set gfx.webrender.force-disabled to True for the Pi-platforms and be done with it, but there may be better solutions I don't know about. Additioal info: Ubuntu release: 21.04 Firefox package: firefox/hirsute-security,hirsute-updates,now 89.0+build2-0ubuntu0.21.04.1 arm64 Steps to reproduce: Play a video on Youtube, watch the coloured blocks appear. Then set gfx.webrender.force-disabled to True and restart to verify the fix. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1930982/+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 1930982]
(In reply to Lee Salzman [:lsalzman] from comment #27) > Sotaro, can you see if my vqmovun_s16 patch fixes this or not? The updated patch worked for me on arm64 Win10 :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1930982 Title: Firefox 89: webrender breaks videos on Raspberry Pi Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Released Bug description: Firefox 89 enabled the Webrender framework by default. Unfortunately, the GFX drivers on a Pi 4 seem to be non-compliant in a way that breaks videos - specifically, there will be a lot of primary coloured artefacts in videos. My guess is that other Raspberry Pi's will also be affected, but I don't have the hardware available to test. Setting gfx.webrender.force-disabled to True fixes the issue, so it's fairly clear where it lies. Mozilla doesn't seem to provide official builds for Raspberry Pi's (or Linux/Arm in general), so I think this is an issue to fix in these packages, rather than upstream. The quick solution would to just set gfx.webrender.force-disabled to True for the Pi-platforms and be done with it, but there may be better solutions I don't know about. Additioal info: Ubuntu release: 21.04 Firefox package: firefox/hirsute-security,hirsute-updates,now 89.0+build2-0ubuntu0.21.04.1 arm64 Steps to reproduce: Play a video on Youtube, watch the coloured blocks appear. Then set gfx.webrender.force-disabled to True and restart to verify the fix. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1930982/+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 1930982]
(In reply to Lee Salzman [:lsalzman] from comment #25) > The circumstantial evidence "seems like" something in the function here > (https://searchfox.org/mozilla-central/source/gfx/wr/swgl/src/composite.h#534) > is underflowing. But I would need someone who can reliably reproduce the > issue to find out where in those math equations are actually doing so. I > tried testing in my patch if the additions were the culprit, but that seems > unlikely. > > It's possible the multiplications "rbCoeffs * uv" or "gCoeffs * uv" are > underflowing based on whatever values the ARM video codecs seem to be > supplying. However, this is not happening on x86 at all, which is strange, > and it is also happening on ARM across platform, which is further strange, > since there isn't really much in the way of platform specific code here. > > Sotaro, might you be able to investigate this? Taking a step back. If a certain function is suspected what are the diff's with this code between the working 88.0 and non working 89.0 version? Since the issue affects all ARM regardless of platform the only culprit not eliminated is Firefox. If you have a downloaded executable for me to test I'm happy to do so. My platforms are : aarch64 Ubuntu 18.04 LTS aarch64 Ubuntu 20.10 I can only test on one of these platforms! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1930982 Title: Firefox 89: webrender breaks videos on Raspberry Pi Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Released Bug description: Firefox 89 enabled the Webrender framework by default. Unfortunately, the GFX drivers on a Pi 4 seem to be non-compliant in a way that breaks videos - specifically, there will be a lot of primary coloured artefacts in videos. My guess is that other Raspberry Pi's will also be affected, but I don't have the hardware available to test. Setting gfx.webrender.force-disabled to True fixes the issue, so it's fairly clear where it lies. Mozilla doesn't seem to provide official builds for Raspberry Pi's (or Linux/Arm in general), so I think this is an issue to fix in these packages, rather than upstream. The quick solution would to just set gfx.webrender.force-disabled to True for the Pi-platforms and be done with it, but there may be better solutions I don't know about. Additioal info: Ubuntu release: 21.04 Firefox package: firefox/hirsute-security,hirsute-updates,now 89.0+build2-0ubuntu0.21.04.1 arm64 Steps to reproduce: Play a video on Youtube, watch the coloured blocks appear. Then set gfx.webrender.force-disabled to True and restart to verify the fix. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1930982/+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 1930982]
Comment on attachment 9226932 Bug 1714511 - use vqmovun_s16 for packing pixels. r?sotaro ### Beta/Release Uplift Approval Request * **User impact if declined**: Enabling Software-WebRender on ARM platforms can lead to visual artifacts. Should not impact x86 platforms or non-SW-WR configurations. * **Is this code covered by automated tests?**: No * **Has the fix been verified in Nightly?**: Yes * **Needs manual test from QE?**: No * **If yes, steps to reproduce**: * **List of other uplifts needed**: None * **Risk to taking this patch**: Low * **Why is the change risky/not risky? (and alternatives if risky)**: Software-WebRender on ARM is not deployed by default to release. Must be pref'd on. However, many users on tier-2 platforms like ARM/Linux are pref'ing the feature on, and it would be nice if we just supplied the fix to them so they don't need to manually apply it to their build. * **String changes made/needed**: -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1930982 Title: Firefox 89: webrender breaks videos on Raspberry Pi Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Released Bug description: Firefox 89 enabled the Webrender framework by default. Unfortunately, the GFX drivers on a Pi 4 seem to be non-compliant in a way that breaks videos - specifically, there will be a lot of primary coloured artefacts in videos. My guess is that other Raspberry Pi's will also be affected, but I don't have the hardware available to test. Setting gfx.webrender.force-disabled to True fixes the issue, so it's fairly clear where it lies. Mozilla doesn't seem to provide official builds for Raspberry Pi's (or Linux/Arm in general), so I think this is an issue to fix in these packages, rather than upstream. The quick solution would to just set gfx.webrender.force-disabled to True for the Pi-platforms and be done with it, but there may be better solutions I don't know about. Additioal info: Ubuntu release: 21.04 Firefox package: firefox/hirsute-security,hirsute-updates,now 89.0+build2-0ubuntu0.21.04.1 arm64 Steps to reproduce: Play a video on Youtube, watch the coloured blocks appear. Then set gfx.webrender.force-disabled to True and restart to verify the fix. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1930982/+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 1930982]
Created attachment 9226932 Bug 1714511 - use vqmovun_s16 for packing pixels. r?sotaro -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1930982 Title: Firefox 89: webrender breaks videos on Raspberry Pi Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Released Bug description: Firefox 89 enabled the Webrender framework by default. Unfortunately, the GFX drivers on a Pi 4 seem to be non-compliant in a way that breaks videos - specifically, there will be a lot of primary coloured artefacts in videos. My guess is that other Raspberry Pi's will also be affected, but I don't have the hardware available to test. Setting gfx.webrender.force-disabled to True fixes the issue, so it's fairly clear where it lies. Mozilla doesn't seem to provide official builds for Raspberry Pi's (or Linux/Arm in general), so I think this is an issue to fix in these packages, rather than upstream. The quick solution would to just set gfx.webrender.force-disabled to True for the Pi-platforms and be done with it, but there may be better solutions I don't know about. Additioal info: Ubuntu release: 21.04 Firefox package: firefox/hirsute-security,hirsute-updates,now 89.0+build2-0ubuntu0.21.04.1 arm64 Steps to reproduce: Play a video on Youtube, watch the coloured blocks appear. Then set gfx.webrender.force-disabled to True and restart to verify the fix. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1930982/+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 1930982] Re: Firefox 89: webrender breaks videos on Raspberry Pi
** Changed in: firefox Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1930982 Title: Firefox 89: webrender breaks videos on Raspberry Pi Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Released Bug description: Firefox 89 enabled the Webrender framework by default. Unfortunately, the GFX drivers on a Pi 4 seem to be non-compliant in a way that breaks videos - specifically, there will be a lot of primary coloured artefacts in videos. My guess is that other Raspberry Pi's will also be affected, but I don't have the hardware available to test. Setting gfx.webrender.force-disabled to True fixes the issue, so it's fairly clear where it lies. Mozilla doesn't seem to provide official builds for Raspberry Pi's (or Linux/Arm in general), so I think this is an issue to fix in these packages, rather than upstream. The quick solution would to just set gfx.webrender.force-disabled to True for the Pi-platforms and be done with it, but there may be better solutions I don't know about. Additioal info: Ubuntu release: 21.04 Firefox package: firefox/hirsute-security,hirsute-updates,now 89.0+build2-0ubuntu0.21.04.1 arm64 Steps to reproduce: Play a video on Youtube, watch the coloured blocks appear. Then set gfx.webrender.force-disabled to True and restart to verify the fix. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1930982/+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 1930982]
The circumstantial evidence "seems like" something in the function here (https://searchfox.org/mozilla- central/source/gfx/wr/swgl/src/composite.h#534) is underflowing. But I would need someone who can reliably reproduce the issue to find out where in those math equations are actually doing so. I tried testing in my patch if the additions were the culprit, but that seems unlikely. It's possible the multiplications "rbCoeffs * uv" or "gCoeffs * uv" are underflowing based on whatever values the ARM video codecs seem to be supplying. However, this is not happening on x86 at all, which is strange, and it is also happening on ARM across platform, which is further strange, since there isn't really much in the way of platform specific code here. Sotaro, might you be able to investigate this? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1930982 Title: Firefox 89: webrender breaks videos on Raspberry Pi Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Released Bug description: Firefox 89 enabled the Webrender framework by default. Unfortunately, the GFX drivers on a Pi 4 seem to be non-compliant in a way that breaks videos - specifically, there will be a lot of primary coloured artefacts in videos. My guess is that other Raspberry Pi's will also be affected, but I don't have the hardware available to test. Setting gfx.webrender.force-disabled to True fixes the issue, so it's fairly clear where it lies. Mozilla doesn't seem to provide official builds for Raspberry Pi's (or Linux/Arm in general), so I think this is an issue to fix in these packages, rather than upstream. The quick solution would to just set gfx.webrender.force-disabled to True for the Pi-platforms and be done with it, but there may be better solutions I don't know about. Additioal info: Ubuntu release: 21.04 Firefox package: firefox/hirsute-security,hirsute-updates,now 89.0+build2-0ubuntu0.21.04.1 arm64 Steps to reproduce: Play a video on Youtube, watch the coloured blocks appear. Then set gfx.webrender.force-disabled to True and restart to verify the fix. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1930982/+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 1931901] Re: Revert background key patch removal breaks dependent packages
>From the above - I've attached the alternative solution to remove the read/write of the draw_background key without removing the patch library functions ** Patch added: "remove_draw_background_rw.debdiff" https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1931901/+attachment/5505066/+files/remove_draw_background_rw.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/1931901 Title: Revert background key patch removal breaks dependent packages Status in gnome-desktop3 package in Ubuntu: New Status in gsettings-desktop-schemas package in Ubuntu: Invalid Bug description: in the package gnome-desktop3 there is a custom ubuntu patch that tries to write to the draw-background key that has now been removed in gsettings-desktop-schemas 40.0-1ubuntu1 All packages that depend on the gnome-desktop3 library now crash such as budgie-desktop Suggestion - either re-add the patch again ... or revert the gnome- desktop3 custom patch. The latter option changes the symbols so probably I'm guessing a so- name version bump is needed and any dependent packages need a rebuild? I'll try to locally rebuild gnome-desktop3 without the custom ubuntu patch to see what happens with budgie-desktop ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gsettings-desktop-schemas 40.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21 Uname: Linux 5.11.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Budgie:GNOME Date: Mon Jun 14 20:52:16 2021 InstallationDate: Installed on 2021-06-14 (0 days ago) InstallationMedia: Ubuntu-Budgie 21.10 "Impish Indri" - Alpha amd64 (20210614) PackageArchitecture: all SourcePackage: gsettings-desktop-schemas UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1931901/+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 1931901] Re: Revert background key patch removal breaks dependent packages
** Patch removed: "remove-git-revert.debdiff" https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1931901/+attachment/5505056/+files/remove-git-revert.debdiff ** Patch added: "remove-git-revert.debdiff" https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1931901/+attachment/5505057/+files/remove-git-revert.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/1931901 Title: Revert background key patch removal breaks dependent packages Status in gnome-desktop3 package in Ubuntu: New Status in gsettings-desktop-schemas package in Ubuntu: Invalid Bug description: in the package gnome-desktop3 there is a custom ubuntu patch that tries to write to the draw-background key that has now been removed in gsettings-desktop-schemas 40.0-1ubuntu1 All packages that depend on the gnome-desktop3 library now crash such as budgie-desktop Suggestion - either re-add the patch again ... or revert the gnome- desktop3 custom patch. The latter option changes the symbols so probably I'm guessing a so- name version bump is needed and any dependent packages need a rebuild? I'll try to locally rebuild gnome-desktop3 without the custom ubuntu patch to see what happens with budgie-desktop ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gsettings-desktop-schemas 40.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21 Uname: Linux 5.11.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Budgie:GNOME Date: Mon Jun 14 20:52:16 2021 InstallationDate: Installed on 2021-06-14 (0 days ago) InstallationMedia: Ubuntu-Budgie 21.10 "Impish Indri" - Alpha amd64 (20210614) PackageArchitecture: all SourcePackage: gsettings-desktop-schemas UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1931901/+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 1931901] Re: Revert background key patch removal breaks dependent packages
As discussed with Marco Trevisan on IRC https://irclogs.ubuntu.com/2021/06/16/%23ubuntu-desktop.html#t14:06 Two potential solutions here. Attached is a simple debdiff to drop the git-revert patch without amending the so-name ** Also affects: gnome-desktop3 (Ubuntu) Importance: Undecided Status: New ** Changed in: gsettings-desktop-schemas (Ubuntu) Status: New => Invalid ** Tags removed: block-proposed ** Patch added: "remove-git-revert.debdiff" https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1931901/+attachment/5505056/+files/remove-git-revert.debdiff ** Changed in: gnome-desktop3 (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/1931901 Title: Revert background key patch removal breaks dependent packages Status in gnome-desktop3 package in Ubuntu: New Status in gsettings-desktop-schemas package in Ubuntu: Invalid Bug description: in the package gnome-desktop3 there is a custom ubuntu patch that tries to write to the draw-background key that has now been removed in gsettings-desktop-schemas 40.0-1ubuntu1 All packages that depend on the gnome-desktop3 library now crash such as budgie-desktop Suggestion - either re-add the patch again ... or revert the gnome- desktop3 custom patch. The latter option changes the symbols so probably I'm guessing a so- name version bump is needed and any dependent packages need a rebuild? I'll try to locally rebuild gnome-desktop3 without the custom ubuntu patch to see what happens with budgie-desktop ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gsettings-desktop-schemas 40.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21 Uname: Linux 5.11.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Budgie:GNOME Date: Mon Jun 14 20:52:16 2021 InstallationDate: Installed on 2021-06-14 (0 days ago) InstallationMedia: Ubuntu-Budgie 21.10 "Impish Indri" - Alpha amd64 (20210614) PackageArchitecture: all SourcePackage: gsettings-desktop-schemas UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1931901/+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 1932155] Re: Crashes on Ubuntu 20.04.2 involving amdgpu/radeonsi and various AMD GPUs (e.g. RX 5500 XT)
it's not fixed upstream until merged to master and preferably to at least one stable branch ** Summary changed: - *Fixed upstream* Crashes on Ubuntu 20.04.2 involving amdgpu/radeonsi and various AMD GPUs (e.g. RX 5500 XT), please merge/backport if possible! + Crashes on Ubuntu 20.04.2 involving amdgpu/radeonsi and various AMD GPUs (e.g. RX 5500 XT) -- 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/1932155 Title: Crashes on Ubuntu 20.04.2 involving amdgpu/radeonsi and various AMD GPUs (e.g. RX 5500 XT) Status in Mesa: Unknown Status in mesa package in Ubuntu: New Bug description: In Ubuntu focal, 20.04.2, amdgpu/Xorg kernel driver crashes/resets occur with various previous-generation AMD Radeon GPUs, for instance Radeon RX 5500 XT. There is a recent fix in the mesa library. Please see upstream mesa bug including available patch: https://gitlab.freedesktop.org/mesa/mesa/-/issues/4866 Patch is available for mesa-stable, 21.1.3 and 21.1.4. It looks like it could apply to 21.0 (which is in focal-proposed) too, with minor effort. Thanks if you can backport this! amdgpu kernel bug: https://bugzilla.kernel.org/show_bug.cgi?id=213145 I can confirm it with linux-generic-hwe-20.04=5.8.0-55.62~20.04.1 from focal-updates/focal-security To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1932155/+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 1931756] Re: [XPS 17 9700, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem
Thank You once more for the reply. This time success! sudo dmesg > dmesg.txt contains lots of text info. It is attached all 85kb of it. uname -r = 5.10.0-051000-generic Hope this helps. ** Attachment added: "sudo dmesg > dmesg.txt results" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1931756/+attachment/5505055/+files/dmesg.txt -- 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/1931756 Title: [XPS 17 9700, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem Status in alsa-driver package in Ubuntu: New Bug description: I have tried modifications to DKMS, modprobe.d, pulseaudio and alsa but all were no sound. The modprobe,d modifications did result in the "dummy" message being replaced by a device. This was done 2 installs ago,sorry. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.10.0-051000-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pbea 1894 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Fri Jun 11 23:34:27 2021 InstallationDate: Installed on 2021-06-11 (0 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Digital Out, HDMI Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [XPS 17 9700, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/04/2021 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.2 dmi.board.name: 0P25F6 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.2:bd03/04/2021:br1.7:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn0P25F6:rvrA03:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9700 dmi.product.sku: 098F dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1931756/+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 1925795] Update Released
The verification of the Stable Release Update for libsecret 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 libsecret in Ubuntu. https://bugs.launchpad.net/bugs/1925795 Title: SRU the current 0.20.4 stable update Status in libsecret package in Ubuntu: Fix Released Status in libsecret source package in Focal: Fix Released Bug description: * Impact That's the current GNOME stable update, including some bugfixes and translation updates https://gitlab.gnome.org/GNOME/libsecret/-/blob/master/NEWS There are non trivial changes to the meson build system included in the update but we still build using autotools so that's not impacting us * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Libsecret is providing an API to access gnome-keyring secrets, try a few applications using it and make sure credentials are correctly available. To list a few possible candidate softwares - evince (try to open a a password protected pdf, it should store and remember the password) - evolution - epiphany-browser - vinagre - balsa - deja-dup * Regression potential Nothing specific to try in those changes, just ensure the library still access the passwords as expected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsecret/+bug/1925795/+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 1925795] Re: SRU the current 0.20.4 stable update
This bug was fixed in the package libsecret - 0.20.4-0ubuntu1 --- libsecret (0.20.4-0ubuntu1) focal; urgency=medium * New stable version (lp: #1925795) -- Sebastien Bacher Fri, 23 Apr 2021 15:03:10 +0200 ** Changed in: libsecret (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libsecret in Ubuntu. https://bugs.launchpad.net/bugs/1925795 Title: SRU the current 0.20.4 stable update Status in libsecret package in Ubuntu: Fix Released Status in libsecret source package in Focal: Fix Released Bug description: * Impact That's the current GNOME stable update, including some bugfixes and translation updates https://gitlab.gnome.org/GNOME/libsecret/-/blob/master/NEWS There are non trivial changes to the meson build system included in the update but we still build using autotools so that's not impacting us * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Libsecret is providing an API to access gnome-keyring secrets, try a few applications using it and make sure credentials are correctly available. To list a few possible candidate softwares - evince (try to open a a password protected pdf, it should store and remember the password) - evolution - epiphany-browser - vinagre - balsa - deja-dup * Regression potential Nothing specific to try in those changes, just ensure the library still access the passwords as expected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsecret/+bug/1925795/+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 1925795] Re: SRU the current 0.20.4 stable update
Part of the argument for requiring the package being SRU'ed to be available in the release to which you'd upgrade is that we don't want to regress users when they upgrade to the next release or prevent their ability to upgrade by creating a scenario for which an upgrade cannot be calculated. Having said that I installed the libsecret binary packages from -proposed for Focal and then attempted an upgrade from Focal to Groovy, this was successfully calculated and the libsecret binary packages were kept at the same version. Subsequently, I think it is okay to release libsecret for Focal. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libsecret in Ubuntu. https://bugs.launchpad.net/bugs/1925795 Title: SRU the current 0.20.4 stable update Status in libsecret package in Ubuntu: Fix Released Status in libsecret source package in Focal: Fix Committed Bug description: * Impact That's the current GNOME stable update, including some bugfixes and translation updates https://gitlab.gnome.org/GNOME/libsecret/-/blob/master/NEWS There are non trivial changes to the meson build system included in the update but we still build using autotools so that's not impacting us * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Libsecret is providing an API to access gnome-keyring secrets, try a few applications using it and make sure credentials are correctly available. To list a few possible candidate softwares - evince (try to open a a password protected pdf, it should store and remember the password) - evolution - epiphany-browser - vinagre - balsa - deja-dup * Regression potential Nothing specific to try in those changes, just ensure the library still access the passwords as expected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsecret/+bug/1925795/+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 1931388] Re: Firefox disaplayerror after Update on last version 89
** Attachment added: "What I see on the monitor" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1931388/+attachment/5505051/+files/IMG_20210616_093217.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1931388 Title: Firefox disaplayerror after Update on last version 89 Status in Ubuntu MATE: New Status in firefox package in Ubuntu: Incomplete Bug description: After the last Update from Firefox Browser to Version 89 Firefox is unsuable. The Program starts but the window is somehow transparent and white. I removed and reinstalled Firefox but the problem is the same. My computer is an Amd Mashine running Ubuntu Mate 20.10 Mate 1.24.1 I took a Screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1931388/+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 1931388] Re: Firefox disaplayerror after Update on last version 89
** Attachment added: "Window previews in Gnome overview look fine" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1931388/+attachment/5505050/+files/Screenshot%20from%202021-06-16%2009-22-16.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1931388 Title: Firefox disaplayerror after Update on last version 89 Status in Ubuntu MATE: New Status in firefox package in Ubuntu: Incomplete Bug description: After the last Update from Firefox Browser to Version 89 Firefox is unsuable. The Program starts but the window is somehow transparent and white. I removed and reinstalled Firefox but the problem is the same. My computer is an Amd Mashine running Ubuntu Mate 20.10 Mate 1.24.1 I took a Screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1931388/+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 1931388] Re: Firefox disaplayerror after Update on last version 89
I also have this issue on Hirsute and 89.0+build2-0ubuntu0.21.04.1 Strangely, in the Gnome overview, all of the firefox windows have correctly rendered previews, however when you take a screenshot of an open firefox window, it comes out either blank, or with a transparent checkerboard pattern. The actual image seen on the monitor is a white screen. My workaround for the moment is to downgrade to an older version sudo apt install firefox=87.0+build3-0ubuntu4 Then launch Firefox once using the command: firefox -allow-downgrade And for now I have held the package in apt to prevent upgrades to the broken version: sudo apt-mark hold firefox ** Attachment added: "screenshot of 2 firefox windows" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1931388/+attachment/5505049/+files/Screenshot%20from%202021-06-16%2009-32-05.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1931388 Title: Firefox disaplayerror after Update on last version 89 Status in Ubuntu MATE: New Status in firefox package in Ubuntu: Incomplete Bug description: After the last Update from Firefox Browser to Version 89 Firefox is unsuable. The Program starts but the window is somehow transparent and white. I removed and reinstalled Firefox but the problem is the same. My computer is an Amd Mashine running Ubuntu Mate 20.10 Mate 1.24.1 I took a Screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1931388/+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 1932155] Re: *Fixed upstream* Crashes on Ubuntu 20.04.2 involving amdgpu/radeonsi and various AMD GPUs (e.g. RX 5500 XT), please merge/backport if possible!
I saw in another bug that it already got backported in a PPA by Mario Limonciello: https://launchpad.net/~superm1/+archive/ubuntu/lp1928393 However the bug manifestation looks different in that bug: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1928393 I attach a dmesg output from my PC, in which you see it differently. This might also be a related bug: https://gitlab.freedesktop.org/drm/amd/-/issues/934 ** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #934 https://gitlab.freedesktop.org/drm/amd/-/issues/934 ** Attachment added: "amdgpu-errors-rx5500-complete-dmesg.txt" https://bugs.launchpad.net/mesa/+bug/1932155/+attachment/5505043/+files/amdgpu-errors-rx5500-complete-dmesg.txt -- 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/1932155 Title: *Fixed upstream* Crashes on Ubuntu 20.04.2 involving amdgpu/radeonsi and various AMD GPUs (e.g. RX 5500 XT), please merge/backport if possible! Status in Mesa: Unknown Status in mesa package in Ubuntu: New Bug description: In Ubuntu focal, 20.04.2, amdgpu/Xorg kernel driver crashes/resets occur with various previous-generation AMD Radeon GPUs, for instance Radeon RX 5500 XT. There is a recent fix in the mesa library. Please see upstream mesa bug including available patch: https://gitlab.freedesktop.org/mesa/mesa/-/issues/4866 Patch is available for mesa-stable, 21.1.3 and 21.1.4. It looks like it could apply to 21.0 (which is in focal-proposed) too, with minor effort. Thanks if you can backport this! amdgpu kernel bug: https://bugzilla.kernel.org/show_bug.cgi?id=213145 I can confirm it with linux-generic-hwe-20.04=5.8.0-55.62~20.04.1 from focal-updates/focal-security To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1932155/+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 1923845] Re: Please compress packages with zstd by default
lintian should be good in impish-proposed, but we should migrate it
first.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream-glib in Ubuntu.
https://bugs.launchpad.net/bugs/1923845
Title:
Please compress packages with zstd by default
Status in appstream-glib package in Ubuntu:
New
Status in apt package in Ubuntu:
Fix Released
Status in aptly package in Ubuntu:
New
Status in boinc package in Ubuntu:
New
Status in busybox package in Ubuntu:
New
Status in cdebootstrap package in Ubuntu:
New
Status in cdist package in Ubuntu:
New
Status in debdelta package in Ubuntu:
New
Status in debian-el package in Ubuntu:
New
Status in debootstrap package in Ubuntu:
Fix Released
Status in debsig-verify package in Ubuntu:
New
Status in debsigs package in Ubuntu:
New
Status in diffoscope package in Ubuntu:
New
Status in dpkg package in Ubuntu:
New
Status in dpkg-sig package in Ubuntu:
New
Status in file package in Ubuntu:
New
Status in libsolv package in Ubuntu:
New
Status in lintian package in Ubuntu:
New
Status in lutris package in Ubuntu:
New
Status in obs-build package in Ubuntu:
New
Status in osc package in Ubuntu:
New
Status in radare2 package in Ubuntu:
New
Status in reprepro package in Ubuntu:
New
Status in vim-scripts package in Ubuntu:
New
Status in zeroinstall-injector package in Ubuntu:
New
Bug description:
https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built
on Hirsute having both data and control members of the .deb being
compressed with zstd. It can be handy for testing various tools.
[dpkg]
Decompression support in dpkg landed first in Bionic and is being SRUd to
Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the
zstd-compressed binary packages.
From dpkg's perspective the upgrade path is cleared.
The original plan was compressing only the internal data.tar .deb
member, but dpkg uses uniform compression by default since dpkg 1.19.0
thus I'm collecting all the changes to support control.tar.zst, too,
in this bug.
Reviewed packages from:
https://codesearch.debian.net/search?q=data.tar.xz=1=1
https://codesearch.debian.net/search?q=control.tar.xz=1=1
appstream-glib - needs fix: libappstream-builder/asb-package-deb.c
aptly - needs fix: deb/deb.go
boinc - needs fix: debian/fetch_example_applications.sh
busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c
cdebootstrap- needs fix: src/package.c
cdist - may need fix, can use dpkg-deb:
cdist/preos/debootstrap/files/devuan-debootstrap/functions
debdelta- needs fix: debdelta debpatch.sh
debian-el - needs fix: deb-view.el
debian-handbook - needs fix, maybe later, for Debian
debootstrap - needs fix,
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54
debsigs - needs fix, debsigs
debsig-verify - needs fix, src/debsig-verify.c
diffoscope - needs fix, diffoscope/comparators/deb.py
dpkg- needs fix, change default
dpkg-sig- needs fix, dpkg-sig
dpmb- needs fix, maybe later, for Debian
elfutils- may need fix, uses dpkg-deb if it is available, does not
handle .gz either
file- needs fix, magic/Magdir/archive
libsolv - needs fix, ext/repo_deb.c
lintian - needs fix malformed-deb-archive
lutris - needs fix, lutris/util/extract.py
obs-build - needs fix Build/Deb.pm
osc - needs fix osc/util/debquery.py control.tar.zst only
python-apt - needs fix
apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall()
radare2 - needs fix
reprepro- needs fix, debfile.c
vim-scripts - needs fix debPlugin/autoload/deb.vim
winetricks - needs fix when Debian switches src/winetricks
zeroinstall-injector - needs fix src/zeroinstall/archive.ml
acr - skip, does not _have to_ be fixed, just creates packages,
see dist/deb_hand.mak
alien - skip, uses dpkg-deb to extract .deb
ansible - not affected, just test data in dbdata.tar.xz
anthy - not affected, just changelog entry
apt - seems fixed already
ceph- not affected in Ubuntu's version
circlator - not affected, just test data
cowdancer - not affected, just documentation
eccodes - skip, just orig-data.tar.xz
eckit - skip, just ...orig-data.tar.xz
firefox - skip, profdata.tar.xz
firefox-esr - skip, profdata.tar.xz
galculator - skip, just changelog
grads - skip, ...orig-data.tar.xz
gvmd- skip, just creates xz compressed .deb
insighttoolkit4 - skip, ...orig-data.tar.xz
jdeb- skip, just creates compressed .deb packages
jmol- skip, just local data archive
jq -
[Desktop-packages] [Bug 1916469] Re: Apps don't use Wayland by default
On my PC I have 6 partitions with different Ubuntu releases (with or without proposed) and Firefox behaves differently Ubuntu 89.0.1 91.0a1 x2-impish-0615 5.11.0-18-generic wayland xwayland x3-groovy 5.8.0-55-genericxwaylandxwayland x4-focal5.8.0-55-genericxwaylandxwayland x5-hippo-x 5.11.0-18-generic wayland xwayland x6-impish-0501 5.11.0-18-generic wayland xwayland x7-hippo5.11.0-18-generic wayland xwayland My hardware: corrado@corrado-x2-ii-0615:~$ inxi -CG CPU: Info: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP L2 cache: 3 MiB Speed: 800 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 Graphics: Device-1: Intel HD Graphics 630 driver: i915 v: kernel Device-2: ARC USB 2.0 Camera type: USB driver: uvcvideo Display: wayland server: X.Org 1.21.1.1 driver: loaded: i915 note: n/a (using device driver) resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 21.1.0 corrado@corrado-x2-ii-0615:~$ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1916469 Title: Apps don't use Wayland by default Status in firefox package in Ubuntu: Fix Released Status in qdirstat package in Ubuntu: Confirmed Status in telegram-desktop package in Ubuntu: Confirmed Status in thunderbird package in Ubuntu: Fix Released Bug description: The Ubuntu universe has a big Wayland problem! What does that mean? So a lot of packages in the Universe repository are not compiled with Wayland support which is really bad and would lead to bad performance after 21.04 comes out. Here are the following packages that I detected with wrong compilation: telegram-desktop (Wayland support work with snap version) kiwix firefox (everything works fine with this env variable set:"MOZ_ENABLE_WAYLAND=1") To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1916469/+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 1932155] Re: *Fixed upstream* Crashes on Ubuntu 20.04.2 involving amdgpu/radeonsi and various AMD GPUs (e.g. RX 5500 XT), please merge/backport if possible!
** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #4866 https://gitlab.freedesktop.org/mesa/mesa/-/issues/4866 ** Also affects: mesa via https://gitlab.freedesktop.org/mesa/mesa/-/issues/4866 Importance: Unknown Status: Unknown -- 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/1932155 Title: *Fixed upstream* Crashes on Ubuntu 20.04.2 involving amdgpu/radeonsi and various AMD GPUs (e.g. RX 5500 XT), please merge/backport if possible! Status in Mesa: Unknown Status in mesa package in Ubuntu: New Bug description: In Ubuntu focal, 20.04.2, amdgpu/Xorg kernel driver crashes/resets occur with various previous-generation AMD Radeon GPUs, for instance Radeon RX 5500 XT. There is a recent fix in the mesa library. Please see upstream mesa bug including available patch: https://gitlab.freedesktop.org/mesa/mesa/-/issues/4866 Patch is available for mesa-stable, 21.1.3 and 21.1.4. It looks like it could apply to 21.0 (which is in focal-proposed) too, with minor effort. Thanks if you can backport this! amdgpu kernel bug: https://bugzilla.kernel.org/show_bug.cgi?id=213145 I can confirm it with linux-generic-hwe-20.04=5.8.0-55.62~20.04.1 from focal-updates/focal-security To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1932155/+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 1932155] [NEW] *Fixed upstream* Crashes on Ubuntu 20.04.2 involving amdgpu/radeonsi and various AMD GPUs (e.g. RX 5500 XT), please merge/backport if possible!
Public bug reported: In Ubuntu focal, 20.04.2, amdgpu/Xorg kernel driver crashes/resets occur with various previous-generation AMD Radeon GPUs, for instance Radeon RX 5500 XT. There is a recent fix in the mesa library. Please see upstream mesa bug including available patch: https://gitlab.freedesktop.org/mesa/mesa/-/issues/4866 Patch is available for mesa-stable, 21.1.3 and 21.1.4. It looks like it could apply to 21.0 (which is in focal-proposed) too, with minor effort. Thanks if you can backport this! amdgpu kernel bug: https://bugzilla.kernel.org/show_bug.cgi?id=213145 I can confirm it with linux-generic-hwe-20.04=5.8.0-55.62~20.04.1 from focal-updates/focal-security ** Affects: mesa Importance: Unknown Status: Unknown ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: focal patch-accepted-upstream -- 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/1932155 Title: *Fixed upstream* Crashes on Ubuntu 20.04.2 involving amdgpu/radeonsi and various AMD GPUs (e.g. RX 5500 XT), please merge/backport if possible! Status in Mesa: Unknown Status in mesa package in Ubuntu: New Bug description: In Ubuntu focal, 20.04.2, amdgpu/Xorg kernel driver crashes/resets occur with various previous-generation AMD Radeon GPUs, for instance Radeon RX 5500 XT. There is a recent fix in the mesa library. Please see upstream mesa bug including available patch: https://gitlab.freedesktop.org/mesa/mesa/-/issues/4866 Patch is available for mesa-stable, 21.1.3 and 21.1.4. It looks like it could apply to 21.0 (which is in focal-proposed) too, with minor effort. Thanks if you can backport this! amdgpu kernel bug: https://bugzilla.kernel.org/show_bug.cgi?id=213145 I can confirm it with linux-generic-hwe-20.04=5.8.0-55.62~20.04.1 from focal-updates/focal-security To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1932155/+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 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
Ok I will cook an other custom image and try to reproduce.
Concerning this log line:
Jun 16 08:55:45 alan-hirsute-base-aiamcicscciaelhaktpo dbus-daemon[711]:
[system] Connection has not authenticated soon enough, closing it
(auth_timeout=3ms, elapsed: 45129ms)
Please note that during our first investigation with @slyon, we added this
9
in /etc/dbus-1/system-local.conf and this particular error disappeared.
However the original issue ("Unexpected error response from
GetNameOwner()" and slow critical-chain) was still there.
--
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/1871538
Title:
dbus timeout-ed during an upgrade, taking services down including gdm
Status in systemd:
New
Status in accountsservice package in Ubuntu:
Invalid
Status in dbus package in Ubuntu:
Incomplete
Status in gnome-shell package in Ubuntu:
Invalid
Status in accountsservice source package in Focal:
Invalid
Status in dbus source package in Focal:
Incomplete
Status in gnome-shell source package in Focal:
Invalid
Status in accountsservice source package in Groovy:
New
Status in dbus source package in Groovy:
New
Status in gnome-shell source package in Groovy:
New
Status in accountsservice source package in Hirsute:
New
Status in dbus source package in Hirsute:
New
Status in gnome-shell source package in Hirsute:
New
Status in accountsservice source package in Impish:
Invalid
Status in dbus source package in Impish:
Incomplete
Status in gnome-shell source package in Impish:
Invalid
Bug description:
This morning I found my computer on the login screen.
But not the one of the screen log, no a new one - so something must have
crashed.
Logging in again confirmed that all apps were gone and the gnome shell
was brought down what seems like triggered by a background update o
accountsservice.
As always things are not perfectly clear :-/
The following goes *back* in time through my logs one by one.
Multiple apps crashed at 06:09, but we will find later that this is a follow
on issue of the underlying gnome/X/... recycling.
-rw-r- 1 paelzer whoopsie 52962868 Apr 8 06:09
_usr_bin_konversation.1000.crash
-rw-r- 1 paelzer whoopsie 986433 Apr 8 06:09
_usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash
rdkit was failing fast and giving up (that will be a different bug, it just
seems broken on my system):
Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling
Policy Service.
Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called
chroot.
Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped
privileges.
Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited
resources.
Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed:
Resource temporarily unavailable
Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running.
Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread.
Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time
threads.
Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoted 0 threads.
Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Main process
exited, code=exited, status=1/FAILURE
Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with
result 'exit-code'.
Apr 08 06:10:13 Keschdeichel dbus-daemon[1208]: [system] Activating via
systemd: service name='org.freedesktop.RealtimeKit1'
unit='rtkit-daemon.service' requested by ':1.1176' (uid=121 pid=>
Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Start request
repeated too quickly.
Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with
result 'exit-code'.
Apr 08 06:10:13 Keschdeichel systemd[1]: Failed to start RealtimeKit
Scheduling Policy Service.
Apr 08 06:10:13 Keschdeichel bluetoothd[1729331]: Bluetooth daemon 5.53
But that already was only triggered by a gnome restart that kicked of earlier:
Apr 08 06:09:27 Keschdeichel systemd[1726656]: Started GNOME Shell on Wayland.
Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Shell on
Wayland.
Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session
is initialized.
Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Wayland
Session.
Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session
(session: gnome-login).
X was recycleing before:
Apr 08 06:09:19 Keschdeichel systemd[10683]: Stopping GNOME Shell on X11...
...
Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (EE)
systemd-logind: ReleaseControl failed: Unknown object
'/org/freedesktop/login1/session/_32'.
Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (II) Server
terminated
[Desktop-packages] [Bug 1925795] Re: SRU the current 0.20.4 stable update
@Chris, would you need the SRU in proposed or to migrate to updates? If that's the later I don't think we want to waste verification resources on that at the moment, in which case we would rather delay copying until we stop doing SRUs for 20.10, sorry for the LTS users waiting for the update -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libsecret in Ubuntu. https://bugs.launchpad.net/bugs/1925795 Title: SRU the current 0.20.4 stable update Status in libsecret package in Ubuntu: Fix Released Status in libsecret source package in Focal: Fix Committed Bug description: * Impact That's the current GNOME stable update, including some bugfixes and translation updates https://gitlab.gnome.org/GNOME/libsecret/-/blob/master/NEWS There are non trivial changes to the meson build system included in the update but we still build using autotools so that's not impacting us * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Libsecret is providing an API to access gnome-keyring secrets, try a few applications using it and make sure credentials are correctly available. To list a few possible candidate softwares - evince (try to open a a password protected pdf, it should store and remember the password) - evolution - epiphany-browser - vinagre - balsa - deja-dup * Regression potential Nothing specific to try in those changes, just ensure the library still access the passwords as expected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsecret/+bug/1925795/+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 1909297] Re: cups missing write permission (for sendmessage operation) in apparmor
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cups (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1909297 Title: cups missing write permission (for sendmessage operation) in apparmor Status in cups package in Ubuntu: Confirmed Bug description: After updating recent version of cups (2.3.3op1-3ubuntu1) : I have started to get errors about its missing permissions on journal audit[29527]: AVC apparmor="DENIED" operation="sendmsg" profile="/usr/sbin/cupsd" name="/run/systemd/notify" pid=29527 comm="cupsd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 kernel: audit: type=1400 audit(1608880333.084:56): apparmor="DENIED" operation="sendmsg" profile="/usr/sbin/cupsd" name="/run/systemd/notify" pid=29527 comm="cupsd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu55 Architecture: amd64 CasperMD5CheckResult: skip CupsErrorLog: E [25/Dec/2020:10:11:15 +0300] [CGI] ippfind (PID 12144) stopped with status 1! CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2020-12-25 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201224) KernLog: Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: LENOVO INVALID NonfreeKernelModules: nvidia_modeset nvidia Package: cups 2.3.3op1-3ubuntu1 PackageArchitecture: amd64 Papersize: a4 ProcCmdline: BOOT_IMAGE=/@/boot/vmlinuz-5.8.0-34-generic root=UUID=b42aef37-b541-43bb-bef8-2dcb8f34df09 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.8.0-34-generic root=UUID=b42aef37-b541-43bb-bef8-2dcb8f34df09 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-34.37+21.04.1-generic 5.8.18 Tags: hirsute package-from-proposed Uname: Linux 5.8.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/11/2019 dmi.bios.release: 1.45 dmi.bios.vendor: LENOVO dmi.bios.version: 4KCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: VIUU4 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: INVALID dmi.ec.firmware.release: 1.45 dmi.modalias: dmi:bvnLENOVO:bvr4KCN45WW:bd01/11/2019:br1.45:efr1.45:svnLENOVO:pnINVALID:pvrINVALID:rvnLENOVO:rnVIUU4:rvrNODPK:cvnLENOVO:ct10:cvrINVALID: dmi.product.family: IDEAPAD dmi.product.name: INVALID dmi.product.sku: LENOVO_BI_IDEAPAD4K_BU_idea_FM_ dmi.product.version: INVALID dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1909297/+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 1909297] Re: cups missing write permission (for sendmessage operation) in apparmor
Soo any progress about this in 6 months? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1909297 Title: cups missing write permission (for sendmessage operation) in apparmor Status in cups package in Ubuntu: Confirmed Bug description: After updating recent version of cups (2.3.3op1-3ubuntu1) : I have started to get errors about its missing permissions on journal audit[29527]: AVC apparmor="DENIED" operation="sendmsg" profile="/usr/sbin/cupsd" name="/run/systemd/notify" pid=29527 comm="cupsd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 kernel: audit: type=1400 audit(1608880333.084:56): apparmor="DENIED" operation="sendmsg" profile="/usr/sbin/cupsd" name="/run/systemd/notify" pid=29527 comm="cupsd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu55 Architecture: amd64 CasperMD5CheckResult: skip CupsErrorLog: E [25/Dec/2020:10:11:15 +0300] [CGI] ippfind (PID 12144) stopped with status 1! CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2020-12-25 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201224) KernLog: Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: LENOVO INVALID NonfreeKernelModules: nvidia_modeset nvidia Package: cups 2.3.3op1-3ubuntu1 PackageArchitecture: amd64 Papersize: a4 ProcCmdline: BOOT_IMAGE=/@/boot/vmlinuz-5.8.0-34-generic root=UUID=b42aef37-b541-43bb-bef8-2dcb8f34df09 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.8.0-34-generic root=UUID=b42aef37-b541-43bb-bef8-2dcb8f34df09 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-34.37+21.04.1-generic 5.8.18 Tags: hirsute package-from-proposed Uname: Linux 5.8.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/11/2019 dmi.bios.release: 1.45 dmi.bios.vendor: LENOVO dmi.bios.version: 4KCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: VIUU4 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: INVALID dmi.ec.firmware.release: 1.45 dmi.modalias: dmi:bvnLENOVO:bvr4KCN45WW:bd01/11/2019:br1.45:efr1.45:svnLENOVO:pnINVALID:pvrINVALID:rvnLENOVO:rnVIUU4:rvrNODPK:cvnLENOVO:ct10:cvrINVALID: dmi.product.family: IDEAPAD dmi.product.name: INVALID dmi.product.sku: LENOVO_BI_IDEAPAD4K_BU_idea_FM_ dmi.product.version: INVALID dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1909297/+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 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
Thanks! Here's where I think the problem starts: Ok, let's authenticate to dbus: Jun 16 08:54:54 alan-hirsute-base-aiamcicscciaelhaktpo systemd[1]: Bus bus-api-system: changing state AUTHENTICATING → HELLO ... Jun 16 08:54:54 alan-hirsute-base-aiamcicscciaelhaktpo systemd[1]: Bus bus-api-system: changing state HELLO → RUNNING Right, systemd thinks it's done it at least. You can see a whole bunch of messages being returned, the connection is working. After a while (note this first timestamp jump; is that significant? looks to be waiting for udev to settle I think so maybe not; could be snapd related) we decide to do something with a Type=dbus unit: Jun 16 08:55:25 alan-hirsute-base-aiamcicscciaelhaktpo systemd[1]: Sent message type=method_call sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=AddMatch cookie=1511 reply_cookie=0 signature=s error-name=n/a error-message=n/a Jun 16 08:55:25 alan-hirsute-base-aiamcicscciaelhaktpo systemd[1]: Sent message type=method_call sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=GetNameOwner cookie=1512 reply_cookie=0 signature=s error-name=n/a error-message=n/a And another timestamp jump, waiting for this timeout: Jun 16 08:55:45 alan-hirsute-base-aiamcicscciaelhaktpo dbus-daemon[711]: [system] Connection has not authenticated soon enough, closing it (auth_timeout=3ms, elapsed: 45129ms) Jun 16 08:55:45 alan-hirsute-base-aiamcicscciaelhaktpo systemd[1]: Got message type=method_return sender=org.freedesktop.DBus destination=:1.4 path=n/a interface=n/a member=n/a cookie=42 reply_cookie=1512 signature=s error-name=n/a error-message=n/a The dbus-daemon didn't think that the connection was authenticated. The last message AFAICS received on the bus connection was: Jun 16 08:55:00 alan-hirsute-base-aiamcicscciaelhaktpo systemd[1]: Got message type=method_call sender=n/a destination=org.freedesktop.systemd1 path=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=Reload cookie=1 reply_cookie=0 signature=n/a error-name=n/a error-message=n/a Jun 16 08:55:00 alan-hirsute-base-aiamcicscciaelhaktpo systemd[1]: Reloading. No smoking gun yet, at least not to me. But interesting that the last thing which happened successfully was reloading. Can we have another go please, with these changes vs. an upstream clean image? - LogLevel=debug in /etc/systemd/system.conf - Using the dbus 1.12.20-2ubuntu1+ppa1 from ppa:ci-train-ppa-service/4587. This dbus is just the one from impish backported to hirsute with verbose debugging turned on. And then attach the full `journalctl -b ` which will probably be quite large. :-) Maybe we'll get some information out of the dbus side to say what it thinks goes wrong with the connection. ** Please note ** The "connection has not authenticated" string does not appear in the earlier logs from Christian or Steve. It could be that there are two bugs here, with similar symptoms that systemd loses its connection to the system bus. -- 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/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm Status in systemd: New Status in accountsservice package in Ubuntu: Invalid Status in dbus package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Invalid Status in accountsservice source package in Focal: Invalid Status in dbus source package in Focal: Incomplete Status in gnome-shell source package in Focal: Invalid Status in accountsservice source package in Groovy: New Status in dbus source package in Groovy: New Status in gnome-shell source package in Groovy: New Status in accountsservice source package in Hirsute: New Status in dbus source package in Hirsute: New Status in gnome-shell source package in Hirsute: New Status in accountsservice source package in Impish: Invalid Status in dbus source package in Impish: Incomplete Status in gnome-shell source package in Impish: Invalid Bug description: This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was brought down what seems like triggered by a background update o accountsservice. As always things are not perfectly clear :-/ The following goes *back* in time through my logs one by one. Multiple apps crashed at 06:09, but we will find later that this is a follow on issue of the underlying gnome/X/... recycling. -rw-r- 1 paelzer whoopsie 52962868 Apr 8 06:09 _usr_bin_konversation.1000.crash -rw-r- 1 paelzer whoopsie 986433 Apr 8 06:09 _usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash rdkit was
[Desktop-packages] [Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
Also, systemd is actually reloaded by cloud-init. In cloud-init logs, I can read: 2021-06-16 08:54:51,608 - subp.py[DEBUG]: Running command ['systemctl', 'daemon-reload'] with allowed return codes [0] (shell=False, capture=True) 2021-06-16 08:54:51,953 - cc_mounts.py[DEBUG]: Activate mounts: PASS:systemctl daemon-reload 2021-06-16 08:54:51,953 - handlers.py[DEBUG]: finish: init-network/config-mounts: SUCCESS: config-mounts ran successfully -- 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/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm Status in systemd: New Status in accountsservice package in Ubuntu: Invalid Status in dbus package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Invalid Status in accountsservice source package in Focal: Invalid Status in dbus source package in Focal: Incomplete Status in gnome-shell source package in Focal: Invalid Status in accountsservice source package in Groovy: New Status in dbus source package in Groovy: New Status in gnome-shell source package in Groovy: New Status in accountsservice source package in Hirsute: New Status in dbus source package in Hirsute: New Status in gnome-shell source package in Hirsute: New Status in accountsservice source package in Impish: Invalid Status in dbus source package in Impish: Incomplete Status in gnome-shell source package in Impish: Invalid Bug description: This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was brought down what seems like triggered by a background update o accountsservice. As always things are not perfectly clear :-/ The following goes *back* in time through my logs one by one. Multiple apps crashed at 06:09, but we will find later that this is a follow on issue of the underlying gnome/X/... recycling. -rw-r- 1 paelzer whoopsie 52962868 Apr 8 06:09 _usr_bin_konversation.1000.crash -rw-r- 1 paelzer whoopsie 986433 Apr 8 06:09 _usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash rdkit was failing fast and giving up (that will be a different bug, it just seems broken on my system): Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called chroot. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped privileges. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited resources. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: Resource temporarily unavailable Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time threads. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoted 0 threads. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Main process exited, code=exited, status=1/FAILURE Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel dbus-daemon[1208]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.1176' (uid=121 pid=> Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Start request repeated too quickly. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel systemd[1]: Failed to start RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel bluetoothd[1729331]: Bluetooth daemon 5.53 But that already was only triggered by a gnome restart that kicked of earlier: Apr 08 06:09:27 Keschdeichel systemd[1726656]: Started GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session is initialized. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Wayland Session. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session (session: gnome-login). X was recycleing before: Apr 08 06:09:19 Keschdeichel systemd[10683]: Stopping GNOME Shell on X11... ... Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (EE) systemd-logind: ReleaseControl failed: Unknown object '/org/freedesktop/login1/session/_32'. Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (II) Server terminated successfully (0). Closing log file. It seems like some internal service broke and everything that
[Desktop-packages] [Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
@laney I built a custom image with system logs level set to debug and I was able to reproduce the issue. You can find the logs attached. ** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1871538/+attachment/5505001/+files/syslog -- 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/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm Status in systemd: New Status in accountsservice package in Ubuntu: Invalid Status in dbus package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Invalid Status in accountsservice source package in Focal: Invalid Status in dbus source package in Focal: Incomplete Status in gnome-shell source package in Focal: Invalid Status in accountsservice source package in Groovy: New Status in dbus source package in Groovy: New Status in gnome-shell source package in Groovy: New Status in accountsservice source package in Hirsute: New Status in dbus source package in Hirsute: New Status in gnome-shell source package in Hirsute: New Status in accountsservice source package in Impish: Invalid Status in dbus source package in Impish: Incomplete Status in gnome-shell source package in Impish: Invalid Bug description: This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was brought down what seems like triggered by a background update o accountsservice. As always things are not perfectly clear :-/ The following goes *back* in time through my logs one by one. Multiple apps crashed at 06:09, but we will find later that this is a follow on issue of the underlying gnome/X/... recycling. -rw-r- 1 paelzer whoopsie 52962868 Apr 8 06:09 _usr_bin_konversation.1000.crash -rw-r- 1 paelzer whoopsie 986433 Apr 8 06:09 _usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash rdkit was failing fast and giving up (that will be a different bug, it just seems broken on my system): Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called chroot. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped privileges. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited resources. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: Resource temporarily unavailable Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time threads. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoted 0 threads. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Main process exited, code=exited, status=1/FAILURE Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel dbus-daemon[1208]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.1176' (uid=121 pid=> Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Start request repeated too quickly. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel systemd[1]: Failed to start RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel bluetoothd[1729331]: Bluetooth daemon 5.53 But that already was only triggered by a gnome restart that kicked of earlier: Apr 08 06:09:27 Keschdeichel systemd[1726656]: Started GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session is initialized. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Wayland Session. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session (session: gnome-login). X was recycleing before: Apr 08 06:09:19 Keschdeichel systemd[10683]: Stopping GNOME Shell on X11... ... Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (EE) systemd-logind: ReleaseControl failed: Unknown object '/org/freedesktop/login1/session/_32'. Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (II) Server terminated successfully (0). Closing log file. It seems like some internal service broke and everything that followed was a secondary issue to that: Apr 08 06:09:19 Keschdeichel systemd[1]: NetworkManager.service: Unexpected error response from GetNameOwner(): Connection terminated
[Desktop-packages] [Bug 1929326] Re: Bluetooth WH-1000XM3 headphones disconnects and reconnects
Can confirm this on Bose QuietComfort 35 II starting with similar "Rejected send message" entry in journalctl. -- 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/1929326 Title: Bluetooth WH-1000XM3 headphones disconnects and reconnects Status in alsa-driver package in Ubuntu: Confirmed Bug description: From time to time, my Sony WH-1000XM3 Bluetooth connected headphones automatically disconnect, and then a couple of seconds later reconnects. This started happening after updating Ubuntu from 20.10 to 21.04. This never happened even once when using Ubuntu 20.10, and the headphones are not used or paired to any other device. The only device that has had any changes to it is the computer which is now running Ubuntu 21.04. It is currently using a custom kernel from https://kernel.ubuntu.com /~kernel-ppa/mainline/ in an attempt to see if that would mitigate the problem. It did not. The issue started to happen when the Ubuntu 21.04 system was running its default kernel. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 Uname: Linux 5.12.4-051204-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: per2734 F pulseaudio /dev/snd/controlC2: per2734 F pulseaudio /dev/snd/controlC0: per2734 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun May 23 12:58:22 2021 InstallationDate: Installed on 2018-11-26 (908 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: WH-1000XM3 Symptom_PulseAudioLog: maj 23 11:33:04 perdator systemd[1473]: pulseaudio.service: Succeeded. maj 23 11:33:14 perdator systemd[1473]: pulseaudio.socket: Succeeded. maj 23 12:35:05 perdator dbus-daemon[1151]: [system] Rejected send message, 0 matched rules; type="method_return", sender=":1.79" (uid=1000 pid=2734 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.5" (uid=0 pid=1147 comm="/usr/lib/bluetooth/bluetoothd ") maj 23 12:54:15 perdator dbus-daemon[1151]: [system] Rejected send message, 0 matched rules; type="method_return", sender=":1.79" (uid=1000 pid=2734 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.5" (uid=0 pid=1147 comm="/usr/lib/bluetooth/bluetoothd ") Symptom_Type: Sound works for a while, then breaks Title: [WH-1000XM3, playback] fails after a while UpgradeStatus: Upgraded to hirsute on 2021-05-10 (13 days ago) dmi.bios.date: 03/11/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5843 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX X470-F GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5843:bd03/11/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX470-FGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1929326/+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 1906741] Re: Firefox sometimes causes garbled audio
Running Ubuntu 20.04 and I have the same issue with Firefox. Watching Netflix works fine, till I go to some sites that has a tendency to crash audio. Then all audio goes garbled. Even doing an audio test in settings gives a garbled echo result. When audio is crashed like this the pulseaudio service uses high CPU even when no audio is being played. Opening a terminal and running "pulseaudio -k" to restart pulseaudio seems to fix the issue without closing Firefox or all the media apps. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1906741 Title: Firefox sometimes causes garbled audio Status in firefox package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Opening certain applications/websites at the same time as Firefox causes the audio to become garbled. The audio sounds distorted with an echo. Certain actions are guaranteed to cause this, but it can also happening when only running instances of Firefox. I've been able to consistently cause this by launching Zoom from a link within Firefox. This does not occur when using Chrome. The only way to fix the issue is to shut down all audio-related programs. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 83.0+build2-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rdevans 55475 F pulseaudio /dev/snd/controlC0: rdevans 55475 F pulseaudio /dev/snd/controlC3: rdevans 55475 F pulseaudio /dev/snd/controlC1: rdevans 55475 F pulseaudio BuildID: 20201112153044 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Thu Dec 3 16:55:36 2020 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-10-20 (1140 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 10.0.0.1 dev enp7s0 proto dhcp metric 100 10.0.0.0/24 dev enp7s0 proto kernel scope link src 10.0.0.7 metric 100 169.254.0.0/16 dev enp7s0 scope link metric 1000 Locales: extensions.sqlite corrupt or missing PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:354 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=83.0/20201112153044 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to focal on 2020-11-12 (21 days ago) dmi.bios.date: 02/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.40 dmi.board.name: H67M dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd02/18/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH67M:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1906741/+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 1932108] Re: bluetooth not starting also airplane mode is not working. laptop hp pavillion g6
** Package changed: ubuntu => bluez (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1932108 Title: bluetooth not starting also airplane mode is not working. laptop hp pavillion g6 Status in bluez package in Ubuntu: New Bug description: native bluetooth is not working.Sometimes disabling the wifi and bluetooth hardware and then enabling it again enables bluetooth. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jun 16 11:28:58 2021 InstallationDate: Installed on 2021-01-27 (140 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: bnep btusb bluetooth MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=35e14111-9084-42ac-baef-472ae96d2665 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-06-08 (7 days ago) dmi.bios.date: 02/11/2011 dmi.bios.release: 15.4 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.04 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1668 dmi.board.vendor: Hewlett-Packard dmi.board.version: 08.10 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.ec.firmware.release: 8.16 dmi.modalias: dmi:bvnHewlett-Packard:bvrF.04:bd02/11/2011:br15.4:efr8.16:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr059F100046100:rvnHewlett-Packard:rn1668:rvr08.10:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion g6 Notebook PC dmi.product.sku: LN246EA#A2N dmi.product.version: 059F100046100 dmi.sys.vendor: Hewlett-Packard hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:34 acl:0 sco:0 events:3 errors:0 TX bytes:12 acl:0 sco:0 commands:4 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1932108/+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 1932108] [NEW] bluetooth not starting also airplane mode is not working. laptop hp pavillion g6
You have been subscribed to a public bug: native bluetooth is not working.Sometimes disabling the wifi and bluetooth hardware and then enabling it again enables bluetooth. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jun 16 11:28:58 2021 InstallationDate: Installed on 2021-01-27 (140 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: bnep btusb bluetooth MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=35e14111-9084-42ac-baef-472ae96d2665 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-06-08 (7 days ago) dmi.bios.date: 02/11/2011 dmi.bios.release: 15.4 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.04 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1668 dmi.board.vendor: Hewlett-Packard dmi.board.version: 08.10 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.ec.firmware.release: 8.16 dmi.modalias: dmi:bvnHewlett-Packard:bvrF.04:bd02/11/2011:br15.4:efr8.16:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr059F100046100:rvnHewlett-Packard:rn1668:rvr08.10:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion g6 Notebook PC dmi.product.sku: LN246EA#A2N dmi.product.version: 059F100046100 dmi.sys.vendor: Hewlett-Packard hciconfig: hci0: Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:34 acl:0 sco:0 events:3 errors:0 TX bytes:12 acl:0 sco:0 commands:4 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session -- bluetooth not starting also airplane mode is not working. laptop hp pavillion g6 https://bugs.launchpad.net/bugs/1932108 You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez 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 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
** Also affects: dbus (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: gnome-shell (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: accountsservice (Ubuntu Hirsute) Importance: Undecided Status: New ** Tags added: rls-ff-incoming rls-hh-incoming ** Also affects: dbus (Ubuntu Impish) Importance: High Status: Incomplete ** Also affects: gnome-shell (Ubuntu Impish) Importance: Undecided Status: Invalid ** Also affects: accountsservice (Ubuntu Impish) Importance: Undecided Status: Invalid ** Also affects: dbus (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: gnome-shell (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: accountsservice (Ubuntu Groovy) Importance: Undecided Status: New ** Tags added: rls-ii-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm Status in systemd: New Status in accountsservice package in Ubuntu: Invalid Status in dbus package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Invalid Status in accountsservice source package in Focal: Invalid Status in dbus source package in Focal: Incomplete Status in gnome-shell source package in Focal: Invalid Status in accountsservice source package in Groovy: New Status in dbus source package in Groovy: New Status in gnome-shell source package in Groovy: New Status in accountsservice source package in Hirsute: New Status in dbus source package in Hirsute: New Status in gnome-shell source package in Hirsute: New Status in accountsservice source package in Impish: Invalid Status in dbus source package in Impish: Incomplete Status in gnome-shell source package in Impish: Invalid Bug description: This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was brought down what seems like triggered by a background update o accountsservice. As always things are not perfectly clear :-/ The following goes *back* in time through my logs one by one. Multiple apps crashed at 06:09, but we will find later that this is a follow on issue of the underlying gnome/X/... recycling. -rw-r- 1 paelzer whoopsie 52962868 Apr 8 06:09 _usr_bin_konversation.1000.crash -rw-r- 1 paelzer whoopsie 986433 Apr 8 06:09 _usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash rdkit was failing fast and giving up (that will be a different bug, it just seems broken on my system): Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called chroot. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped privileges. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited resources. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: Resource temporarily unavailable Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time threads. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoted 0 threads. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Main process exited, code=exited, status=1/FAILURE Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel dbus-daemon[1208]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.1176' (uid=121 pid=> Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Start request repeated too quickly. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel systemd[1]: Failed to start RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel bluetoothd[1729331]: Bluetooth daemon 5.53 But that already was only triggered by a gnome restart that kicked of earlier: Apr 08 06:09:27 Keschdeichel systemd[1726656]: Started GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session is initialized. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Wayland Session. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session (session: gnome-login). X was recycleing
[Desktop-packages] [Bug 1932112] [NEW] package libreoffice-common 1:7.0.6-0ubuntu0.20.10.1 failed to install/upgrade: installed libreoffice-common package post-installation script subprocess returned
Public bug reported: crash ProblemType: Package DistroRelease: Ubuntu 20.10 Package: libreoffice-common 1:7.0.6-0ubuntu0.20.10.1 ProcVersionSignature: Ubuntu 5.8.0-49.55-generic 5.8.18 Uname: Linux 5.8.0-49-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.7 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Jun 15 20:14:27 2021 DuplicateSignature: package:libreoffice-common:1:7.0.6-0ubuntu0.20.10.1 Installing new version of config file /etc/apparmor.d/usr.lib.libreoffice.program.soffice.bin ... Replacing config file /etc/libreoffice/registry/main.xcd with new version dpkg: error processing package libreoffice-common (--configure): installed libreoffice-common package post-installation script subprocess returned error exit status 128 ErrorMessage: installed libreoffice-common package post-installation script subprocess returned error exit status 128 InstallationDate: Installed on 2021-01-31 (136 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: /usr/bin/python3.8, Python 3.8.6, unpackaged RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10ubuntu0.3 SourcePackage: libreoffice Title: package libreoffice-common 1:7.0.6-0ubuntu0.20.10.1 failed to install/upgrade: installed libreoffice-common package post-installation script subprocess returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package groovy 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/1932112 Title: package libreoffice-common 1:7.0.6-0ubuntu0.20.10.1 failed to install/upgrade: installed libreoffice-common package post- installation script subprocess returned error exit status 128 Status in libreoffice package in Ubuntu: New Bug description: crash ProblemType: Package DistroRelease: Ubuntu 20.10 Package: libreoffice-common 1:7.0.6-0ubuntu0.20.10.1 ProcVersionSignature: Ubuntu 5.8.0-49.55-generic 5.8.18 Uname: Linux 5.8.0-49-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.7 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Jun 15 20:14:27 2021 DuplicateSignature: package:libreoffice-common:1:7.0.6-0ubuntu0.20.10.1 Installing new version of config file /etc/apparmor.d/usr.lib.libreoffice.program.soffice.bin ... Replacing config file /etc/libreoffice/registry/main.xcd with new version dpkg: error processing package libreoffice-common (--configure): installed libreoffice-common package post-installation script subprocess returned error exit status 128 ErrorMessage: installed libreoffice-common package post-installation script subprocess returned error exit status 128 InstallationDate: Installed on 2021-01-31 (136 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: /usr/bin/python3.8, Python 3.8.6, unpackaged RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10ubuntu0.3 SourcePackage: libreoffice Title: package libreoffice-common 1:7.0.6-0ubuntu0.20.10.1 failed to install/upgrade: installed libreoffice-common package post-installation script subprocess returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1932112/+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
