[Desktop-packages] [Bug 1777708] Re: Desktop briefly becomes unresponsive when receiving a keypress from a different device/mapping than the last keypress (in Xorg)
Are you using Compton? If so, please see https://askubuntu.com/a/1439993/682596 and https://gitlab.xfce.org/xfce/xfwm4/-/issues/676 Basically, Compton could be at fault for creating these key delays. As soon as I start Compton manually in a similar fashion as the OS startup, the problem appears. I am not using double keyboards. ** Bug watch added: gitlab.xfce.org/xfce/xfwm4/-/issues #676 https://gitlab.xfce.org/xfce/xfwm4/-/issues/676 -- 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/108 Title: Desktop briefly becomes unresponsive when receiving a keypress from a different device/mapping than the last keypress (in Xorg) Status in GNOME Shell: Fix Released Status in Mutter: New Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I'm running Ubuntu 18.04 and Gnome 3.28.1 with all the latest updates from the repos. If I connect 2 (or more) keyboards to my computer and type on both at the same time, the desktop briefly becomes unresponsive. More keypresses increase the time of unresponsiveness. E.g. when typing a full sentence in gedit or the terminal, only very few characters show up on the screen (I guess up until something is pressed on both keyboards at the same time), then everything freezes. Then after a while (some seconds), all the characters show up. And the desktop becomes responsive again. Symptoms: During the freeze, windows stop updating their content. If seconds are enabled on the clock at the top middle, these freeze too. But I'm still able to move the mouse pointer around during the freeze without any problems. The back story: I got an ergonomic keyboard (R-Go Split Keyboard) yesterday, and quickly noticed the issue. But initiallly I thought it was an issue with the keyboard, and the problem wasn't that bad. But as I've gotten more used to the keyboard since yesterday and started picking up a proper typing speed, things got worse. The keyboard is technically two separate cabled USB keyboards each with only about half of they keys of a normal keyboard (or at least that's very much my impression). After getting the suspicion that this was a software issue, not a hardware issue, I tried typing on my old Logitech keyboard (Unifying Receiver) along with one of the R-Go halves: Same issue. Then I tried each of the halves without the other (as in "single" keyboard typing): No issue. Then I connected another Logitech keyboard (separate UR), typed on both Logitechs: Same issue. Some further observations: 1) Nothing of significance in my syslog. 2) If I drop to a non-graphical shell, there's no problem. I suspect this issue is related to X.org or Gnome, but I'm in no position to say anything credible about that. 3) Also no problems when connecting the R-Go keyboard to a Windows or a MacOS machine. Let me know if there are any logs I can provide or things I can run to produce useful debug output. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/108/+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 1996082] Re: [BPO] libreoffice 7.3.7 for bionic
** Description changed: [Impact] * LibreOffice 7.3.7 is in its seventh bugfix release of the 7.3 line: https://wiki.documentfoundation.org/ReleasePlan/7.3#7.3.7_release * This source packages matches the proposed SRU for jammy handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1995054 and its backport is currently provided by the LibreOffice Still PPA at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+packages * Previous backport of 7.3.6 handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1990382 * LibreOffice 6.4.7 (EOL since November 30, 2020) is currently released in focal. * LibreOffice 7.3.6 is currently released in bionic-backports. * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/1:7.3.7-0ubuntu0.22.04.1 * Backport target is Bionic/18.04 LTS only to provide an official build of a more recent upstream version of LibreOffice [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_73/2020/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. - * [amd64] ... - * [arm64] ... - * [armhf] ... - * [ppc64el] ... - * [s390x] ... + * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/amd64/libr/libreoffice/20221109_194619_aafcb@/log.gz + * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/arm64/libr/libreoffice/20221109_182935_ad523@/log.gz + * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/armhf/libr/libreoffice/20221109_193157_bfaf9@/log.gz + * [i386] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/i386/libr/libreoffice/20221110_005928_4e278@/log.gz + * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/ppc64el/libr/libreoffice/20221109_191816_d9338@/log.gz + * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/s390x/libr/libreoffice/20221109_173606_13453@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 28 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1996082 Title: [BPO] libreoffice 7.3.7 for bionic Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Bionic: In Progress Bug description: [Impact] * LibreOffice 7.3.7 is in its seventh bugfix release of the 7.3 line: https://wiki.documentfoundation.org/ReleasePlan/7.3#7.3.7_release * This source packages matches the proposed SRU for jammy handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1995054 and its backport is currently provided by the LibreOffice Still PPA at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+packages * Previous backport of 7.3.6 handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1990382 * LibreOffice 6.4.7 (EOL since November 30, 2020) is currently released in focal. * LibreOffice 7.3.6 is currently released in bionic-backports. * Given the nature of the project, the complexity of the codebase and the high level of q
[Desktop-packages] [Bug 1950282] Re: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support
** Description changed: :55:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device [14c3:4d75] (rev 01) - Subsystem: Hewlett-Packard Company Device [103c:8914] + Subsystem: Hewlett-Packard Company Device [103c:8914] - https://lore.kernel.org/linux-wireless/20211101035635.26999-1-ricardo.marti...@linux.intel.com/ - --- + https://lore.kernel.org/linux- + wireless/20211101035635.26999-1-ricardo.marti...@linux.intel.com/ + + Modemmanager requires >= 1.19.1, the detail info is in + lp:1962525 + + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: - + DistributionChannelDescriptor: - # This is the distribution channel descriptor for the OEM CDs - # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor - canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X136 + # This is the distribution channel descriptor for the OEM CDs + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X136 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-07-13 (119 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Intel Corporation Alder Lake Client Platform Package: linux-firmware 1.187.20+staging.31 PackageArchitecture: all ProcFB: 0 i915 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9007-oem root=UUID=56278c18-b6d3-4b07-b758-32f574db7ae0 ro i915.force_probe=46c0 automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-9007.7+staging.29-oem 5.14.14 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: - linux-restricted-modules-5.14.0-9007-oem N/A - linux-backports-modules-5.14.0-9007-oem N/A - linux-firmware 1.187.20+staging.31 + linux-restricted-modules-5.14.0-9007-oem N/A + linux-backports-modules-5.14.0-9007-oem N/A + linux-firmware 1.187.20+staging.31 Tags: focal Uname: Linux 5.14.0-9007-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 08/23/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: ADLPFWI1.R00.2347.A00.2108230957 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: AlderLake-M LP5 RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.43 dmi.modalias: dmi:bvnIntelCorporation:bvrADLPFWI1.R00.2347.A00.2108230957:bd08/23/2021:efr1.43:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnAlderLake-MLP5RVP:rvr1:cvnIntelCorporation:ct9:cvr0.1:sku01010002: dmi.product.family: Alder Lake Client System dmi.product.name: Alder Lake Client Platform dmi.product.sku: 01010002 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1950282 Title: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Incomplete Status in modemmanager package in Ubuntu: New Bug description: :55:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device [14c3:4d75] (rev 01) Subsystem: Hewlett-Packard Company Device [103c:8914] https://lore.kernel.org/linux- wireless/20211101035635.26999-1-ricardo.marti...@linux.intel.com/ Modemmanager requires >= 1.19.1, the detail info is in lp:1962525 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X136 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-07-13 (119 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Intel Corporation Alder Lake Client Platform Package: linux-firmware 1.187.20+staging.31 PackageArchitecture: all ProcFB: 0 i915 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9007-oem root=UUID=56278c18-b6d3-4b07-b758
[Desktop-packages] [Bug 1950282] Re: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support
** Also affects: modemmanager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1950282 Title: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Incomplete Status in modemmanager package in Ubuntu: New Bug description: :55:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device [14c3:4d75] (rev 01) Subsystem: Hewlett-Packard Company Device [103c:8914] https://lore.kernel.org/linux-wireless/20211101035635.26999-1-ricardo.marti...@linux.intel.com/ --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X136 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-07-13 (119 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Intel Corporation Alder Lake Client Platform Package: linux-firmware 1.187.20+staging.31 PackageArchitecture: all ProcFB: 0 i915 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9007-oem root=UUID=56278c18-b6d3-4b07-b758-32f574db7ae0 ro i915.force_probe=46c0 automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-9007.7+staging.29-oem 5.14.14 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.14.0-9007-oem N/A linux-backports-modules-5.14.0-9007-oem N/A linux-firmware 1.187.20+staging.31 Tags: focal Uname: Linux 5.14.0-9007-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 08/23/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: ADLPFWI1.R00.2347.A00.2108230957 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: AlderLake-M LP5 RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.43 dmi.modalias: dmi:bvnIntelCorporation:bvrADLPFWI1.R00.2347.A00.2108230957:bd08/23/2021:efr1.43:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnAlderLake-MLP5RVP:rvr1:cvnIntelCorporation:ct9:cvr0.1:sku01010002: dmi.product.family: Alder Lake Client System dmi.product.name: Alder Lake Client Platform dmi.product.sku: 01010002 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1950282/+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 1943488] Re: when typeing too fast in the search line searching stops to work
If this is related to the bug I had filed upstream (linked above), then this should be fixed in Nautilus 43.1 or later. ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #1731 https://gitlab.gnome.org/GNOME/nautilus/-/issues/1731 ** Also affects: nautilus via https://gitlab.gnome.org/GNOME/nautilus/-/issues/1731 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1943488 Title: when typeing too fast in the search line searching stops to work Status in Nautilus: Unknown Status in nautilus package in Ubuntu: Confirmed Bug description: 1. $ lsb_release -rd Description: Ubuntu 20.04.3 LTS Release: 20.04 2. $ apt-cache policy nautilus nautilus: Installed: 1:3.36.3-0ubuntu1 Candidate: 1:3.36.3-0ubuntu1 Version table: *** 1:3.36.3-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.36.1.1-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 3. When I try to find a file/directory in nautilus I start to type some letters (or press CTRL-f befor typing). Normally nautilus tries to find the files and shows the result. 4. When I am typing too fast (or normal speed?) the searching hangs up, a small blue circle goes around in the left bottom corner and nothing happens for long time. If I cut (CTRL-a CTRL-x) the searched text and paste it back (CTRL-f CTRL-v) the searching is successful, and the result appears immidietly. The situation is same e.g. in gnome-software, so I think this problem is globally exists in gnome. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1943488/+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 1996118] [NEW] texit is not compatible with CJKutf8
Public bug reported:
The CJKutf8 package installed with the command `sudo apt install
texlive-full` disables the command `\textit`.
Tex 2021
Ubuntu 5.15.0-52.58-generic 5.15.60
Minimum working example:
```
\documentclass{article}
\usepackage{CJKutf8}
\begin{document}
\begin{CJK*}{UTF8}{min}
代数幾何
\end{CJK*}
\textit{This is not italic...}
\end{document}
```
** Affects: texlive-base (Ubuntu)
Importance: Undecided
Status: New
** Tags: tex texlive ubuntu-22.04
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to texlive-base in Ubuntu.
https://bugs.launchpad.net/bugs/1996118
Title:
texit is not compatible with CJKutf8
Status in texlive-base package in Ubuntu:
New
Bug description:
The CJKutf8 package installed with the command `sudo apt install
texlive-full` disables the command `\textit`.
Tex 2021
Ubuntu 5.15.0-52.58-generic 5.15.60
Minimum working example:
```
\documentclass{article}
\usepackage{CJKutf8}
\begin{document}
\begin{CJK*}{UTF8}{min}
代数幾何
\end{CJK*}
\textit{This is not italic...}
\end{document}
```
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/1996118/+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 1990563] Re: Some maximized/fullscreen windows appear on both monitors
43.1 seems to exist at https://gitlab.gnome.org/GNOME/mutter/-/tags Does anybody have a package to see if it actually fixes it? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1990563 Title: Some maximized/fullscreen windows appear on both monitors Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Committed Bug description: I have a dual monitor setup, with external monitor configured as primary. When I maximize certain windows on the secondary monitor, a copy of the same window appears on the primary monitor (see first attached video). It happens with some apps, not with all of them. For example, it happens with IntelliJ IDEA (Java app) and Spotify (presumably Electron app), not with Gnome Text Editor, Gnome Terminal, Chrome or Firefox, for instance. A very similar situation occurs when taking a screenshot with Flameshot, though in the opposite way: a copy of the primary monitor appears on the secondary (see second attached video). ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: mutter 43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Sep 22 14:37:37 2022 InstallationDate: Installed on 2018-12-14 (1378 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: mutter UpgradeStatus: Upgraded to kinetic on 2022-09-02 (20 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1990563/+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 1995137] Re: "sun4i-drm_dri.so" is missing from libg1-mesa-dri on riscv64
Using this library results in the following error: 'generic' is not a recognized processor for this target (ignoring processor) 'generic' is not a recognized processor for this target (ignoring processor) WARNING: This target JIT is not designed for the host you are running. If bad things happen, please choose a different -march switch. 'generic' is not a recognized processor for this target (ignoring processor) 'generic' is not a recognized processor for this target (ignoring processor) 'generic' is not a recognized processor for this target (ignoring processor) 'generic' is not a recognized processor for this target (ignoring processor) 'generic' is not a recognized processor for this target (ignoring processor) 'generic' is not a recognized processor for this target (ignoring processor) 'generic' is not a recognized processor for this target (ignoring processor) 'generic' is not a recognized processor for this target (ignoring processor) LLVM ERROR: Cannot select: 0x3fa81e7fa8: ch = store<(store 4 into %ir.mask_ptr1 + 12, basealign 16), trunc to i32> 0x3fa81eadd0, 0x3fa81eea00, 0x3fa81b3358, undef:i64 0x3fa81eea00: i64 = sub Constant:i64<0>, 0x3fa81e7c68 0x3fa81b59a8: i64 = Constant<0> 0x3fa81e7c68: i64 = and 0x3fa81e7ed8, Constant:i64<1> 0x3fa81e7ed8: i64 = srl 0x3fa81e9430, Constant:i64<7> 0x3fa81e9430: i64,ch = load<(load 2 from %fixed-stack.5, align 8), zext from i16> 0x3fa80c34b8, FrameIndex:i64<-2>, undef:i64 0x3fa81b2e78: i64 = FrameIndex<-2> 0x3fa81b2da8: i64 = undef 0x3fa81e7e70: i64 = Constant<7> 0x3fa81b5a78: i64 = Constant<1> 0x3fa81b3358: i64 = add FrameIndex:i64<6>, Constant:i64<28> 0x3fa81b34f8: i64 = FrameIndex<6> 0x3fa8217440: i64 = Constant<28> 0x3fa81b2da8: i64 = undef In function: fs_variant_partial !!! Fatal signal received. Attempting cleanup, but deadlock may occur pure virtual method called terminate called without an active exception !!! Fatal signal received. Attempting cleanup, but deadlock may occur Mir fatal error: Unsupported attempt to continue after a fatal signal: SIGABRT Seems similar to https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1993800 but probably unrelated -- 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/1995137 Title: "sun4i-drm_dri.so" is missing from libg1-mesa-dri on riscv64 Status in mesa package in Ubuntu: New Bug description: "sun4i-drm_dri.so" is needed for some RISC-V platforms such as the Allwinner D1. This file is missing from the riscv64 packages, but present on others. This affects (at least) 20.04 and 22.04. itrue@lxc-focal ~/tmp> dpkg -c libgl1-mesa-dri_21.2.6-0ubuntu0.1~20.04.2_arm64.deb | grep _dri.so *snip* hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/aarch64-linux-gnu/dri/sun4i-drm_dri.so link to ./usr/lib/aarch64-linux-gnu/dri/armada-drm_dri.so *snip* itrue@lxc-focal ~/tmp> dpkg -c libgl1-mesa-dri_21.2.6-0ubuntu0.1~20.04.2_riscv64.deb | grep _dri.so -rw-r--r-- root/root 16498024 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/nouveau_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so -rw-r--r-- root/root 4692400 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/nouveau_vieux_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/r200_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/nouveau_vieux_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/r300_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/r600_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/radeon_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/nouveau_vieux_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/radeonsi_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/swrast_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/virtio_gpu_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/zink_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1995137/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages
[Desktop-packages] [Bug 1915910] Re: evince does not print (apparmor, pxgsettings)
Same issue with evince 42.3-0ubuntu2, apparmor 3.0.4-2ubuntu2.1, cinnamon 5.2.7-4 on Ubuntu 22.04.1 (jammy). I believe the apparmor workaround below is better, since it works on any version: Inside '/etc/apparmor.d/usr.bin.evince', add following line after the line containing 'thunar': /usr/lib/x86_64-linux-gnu/libproxy/[0-9.]+/pxgsettings Cx -> sanitized_helper, # Print Dialog Alternatively, run the command below (one line): $ sudo sed -i 's|.*/usr/bin/thunar Cx -> sanitized_helper,.*|&\n /usr/lib/x86_64-linux-gnu/libproxy/[0-9.]+/pxgsettings Cx -> sanitized_helper, # Print Dialog|' /etc/apparmor.d/usr.bin.evince The workaround above solves the issue for me. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libproxy in Ubuntu. https://bugs.launchpad.net/bugs/1915910 Title: evince does not print (apparmor, pxgsettings) Status in evince package in Ubuntu: Confirmed Status in libproxy package in Ubuntu: Confirmed Status in evince package in Debian: New Bug description: audit: type=1400 audit(1613557537.646:81): apparmor="DENIED" operation="exec" profile="/usr/bin/evince" name="/usr/lib/x86_64-linux-gnu/libproxy/0.4.17/pxgsettings" pid=3500 comm="sh" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 It seems that evince has no rights to print if I understand this correctly Printing the same pdf-file from the same origin/folder works with OCULAR The error is reproduceable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1915910/+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 1995402] Re: cups keeps spool files forever and thus reveals confidential data
** Information type changed from Private Security to Public Security ** 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/1995402 Title: cups keeps spool files forever and thus reveals confidential data Status in cups package in Ubuntu: Confirmed Bug description: Hi, I found plenty of old spool files in /var/spool/cups on two machines, both 22.04 and formerly upgraded from 20.04, where files contained the original print files, some even two years old, containing confidential data that should have been delete long time ago. Thus, cups keeps confidential data forever at a location the user can neither see or delete. Severe security gap, since attackers, investigators, attorneys, whoever, will find data in /var/spool/cups, which the user believes to have deleted, encrypted, or whatever. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1995402/+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 1983794] Re: Evolution not deleting autosave files
To try to get rid of this problem with Evolution I uninstalled
libcanberra-gtk-3-0 as m...@papersolve.com suggested, and after that I
can only log in to my Ubuntu 22.04 in terminal mode! I have reinstalled
libcanberra-gtk-3-0 but it doesn't help. I am stuck in terminal at
start-up !!
(I realize now that I should never have uninstalled libcanberra-gtk-3-0)
How do I get the GUI back ??
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libcanberra in Ubuntu.
https://bugs.launchpad.net/bugs/1983794
Title:
Evolution not deleting autosave files
Status in Evolution:
Fix Released
Status in evolution package in Ubuntu:
Invalid
Status in libcanberra package in Ubuntu:
Triaged
Bug description:
Running Ubuntu MATE, Ubuntu 22.04.1 LTS. Evolution v3.44.1-0ubuntu1
was installed with the distribution on a new system and received
settings imported from an earlier version on another computer.
When composing an email, if the process takes long enough an autosave
file is created as ~/.local/share/evolution/.evolution-
composer.autosave-xx ("xx" is a random 6 character string).
When the email is successfully sent, the autosave file SHOULD be
deleted. It's not. When evolution is shut down and restarted I'm asked
if I want to recover an unfinished email. Answering No to this will
delete the autosave file, but otherwise it persists and the recovery
query recurs the next time I open evolution.
Other people are having the same issue, see
https://gitlab.gnome.org/GNOME/evolution/-/issues/1972. The Gnome
people aren't dealing with it, perhaps considering it a distro-
specific bug.
On a system used by many people this is a potential security issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution/+bug/1983794/+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 1987528] Re: Since upgrade from 20.04 → 22.04 ; unable to print in color, only black and white
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cups-filters (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1987528 Title: Since upgrade from 20.04 → 22.04 ; unable to print in color, only black and white Status in cups-filters package in Ubuntu: Confirmed Bug description: Hi, Printer ( in my context ) is Ricoh Aficio mpc 3002 and most Ricoh's drivers are open-source ( https://www.openprinting.org/printer/Ricoh/Ricoh-Aficio_MP_C3002 ) Since I « upgraded » my installation from 20.04 → 22.04, I'm unable to print in colors, only black and white, whatever I set in driver. I tried what's suggested in ⋅ https://askubuntu.com/questions/1410583/upgrading-to-22-04-printer-doesnt-works-in-color ⋅ https://discourse.ubuntubudgie.org/t/22-04-unable-to-add-printer-which-perfectly-worked-in-20-04/6209 I might go wrong somewhere cause I still can't manage to print in color. → the snap thing ( Gutenprint Printer Application ) does not detect my ( network ) printer, → I'm not sure of the name for PRINTER I should input in command « lpadmin -p PRINTER -o print-color-mode-default=color » ( and is this as normal user or sudo ? ) It seems related to ⋅ https://github.com/OpenPrinting/cups/issues/421 It's a regression ( as it used to work out of the box before 22.04 ). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1987528/+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 1995137] Re: "sun4i-drm_dri.so" is missing from libg1-mesa-dri on riscv64
The attachment "mesa-build-lima-on-riscv64.debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- 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/1995137 Title: "sun4i-drm_dri.so" is missing from libg1-mesa-dri on riscv64 Status in mesa package in Ubuntu: New Bug description: "sun4i-drm_dri.so" is needed for some RISC-V platforms such as the Allwinner D1. This file is missing from the riscv64 packages, but present on others. This affects (at least) 20.04 and 22.04. itrue@lxc-focal ~/tmp> dpkg -c libgl1-mesa-dri_21.2.6-0ubuntu0.1~20.04.2_arm64.deb | grep _dri.so *snip* hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/aarch64-linux-gnu/dri/sun4i-drm_dri.so link to ./usr/lib/aarch64-linux-gnu/dri/armada-drm_dri.so *snip* itrue@lxc-focal ~/tmp> dpkg -c libgl1-mesa-dri_21.2.6-0ubuntu0.1~20.04.2_riscv64.deb | grep _dri.so -rw-r--r-- root/root 16498024 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/nouveau_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so -rw-r--r-- root/root 4692400 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/nouveau_vieux_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/r200_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/nouveau_vieux_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/r300_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/r600_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/radeon_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/nouveau_vieux_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/radeonsi_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/swrast_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/virtio_gpu_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/zink_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1995137/+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 1996076] Re: [BPO] libreoffice 7.3.7 for focal
** Patch removed: "libreoffice_7.3.7-0ubuntu0.22.04.1_bpo20.04.1.patch" https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1996076/+attachment/5630088/+files/libreoffice_7.3.7-0ubuntu0.22.04.1_bpo20.04.1.patch ** Patch added: "libreoffice_7.3.7-0ubuntu0.22.04.1_bpo20.04.1.patch" https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1996076/+attachment/5630091/+files/libreoffice_7.3.7-0ubuntu0.22.04.1_bpo20.04.1.patch -- 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/1996076 Title: [BPO] libreoffice 7.3.7 for focal Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Focal: In Progress Bug description: [Impact] * LibreOffice 7.3.7 is in its seventh bugfix release of the 7.3 line: https://wiki.documentfoundation.org/ReleasePlan/7.3#7.3.7_release * This source packages matches the proposed SRU for jammy handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1995054 and its backport is currently provided by the LibreOffice Still PPA at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+packages * Previous backport of 7.3.6 handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1989418 * LibreOffice 6.4.7 (EOL since November 30, 2020) is currently released in focal. * LibreOffice 7.3.6 is currently released in focal-backports. * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/1:7.3.7-0ubuntu0.22.04.1 * Backport target is Focal/20.04 LTS only to provide an official build of a more recent upstream version of LibreOffice [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_73/2020/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/amd64/libr/libreoffice/20221109_131732_0f324@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/arm64/libr/libreoffice/20221109_134252_403d2@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/armhf/libr/libreoffice/20221109_152925_85c50@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/ppc64el/libr/libreoffice/20221109_134511_07b38@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/s390x/libr/libreoffice/20221109_125147_0715b@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 28 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1996076/+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 1996082] Re: [BPO] libreoffice 7.3.7 for bionic
** Patch removed: "libreoffice_7.3.7-0ubuntu0.22.04.1_bpo18.04.1.patch" https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1996082/+attachment/5630090/+files/libreoffice_7.3.7-0ubuntu0.22.04.1_bpo18.04.1.patch ** Patch added: "libreoffice_7.3.7-0ubuntu0.22.04.1_bpo18.04.1.patch" https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1996082/+attachment/5630092/+files/libreoffice_7.3.7-0ubuntu0.22.04.1_bpo18.04.1.patch -- 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/1996082 Title: [BPO] libreoffice 7.3.7 for bionic Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Bionic: In Progress Bug description: [Impact] * LibreOffice 7.3.7 is in its seventh bugfix release of the 7.3 line: https://wiki.documentfoundation.org/ReleasePlan/7.3#7.3.7_release * This source packages matches the proposed SRU for jammy handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1995054 and its backport is currently provided by the LibreOffice Still PPA at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+packages * Previous backport of 7.3.6 handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1990382 * LibreOffice 6.4.7 (EOL since November 30, 2020) is currently released in focal. * LibreOffice 7.3.6 is currently released in bionic-backports. * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/1:7.3.7-0ubuntu0.22.04.1 * Backport target is Bionic/18.04 LTS only to provide an official build of a more recent upstream version of LibreOffice [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_73/2020/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. * [amd64] ... * [arm64] ... * [armhf] ... * [ppc64el] ... * [s390x] ... * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 28 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1996082/+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 1996082] Re: [BPO] libreoffice 7.3.7 for bionic
** Patch added: "libreoffice_7.3.7-0ubuntu0.22.04.1_bpo18.04.1.patch" https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1996082/+attachment/5630090/+files/libreoffice_7.3.7-0ubuntu0.22.04.1_bpo18.04.1.patch -- 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/1996082 Title: [BPO] libreoffice 7.3.7 for bionic Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Bionic: In Progress Bug description: [Impact] * LibreOffice 7.3.7 is in its seventh bugfix release of the 7.3 line: https://wiki.documentfoundation.org/ReleasePlan/7.3#7.3.7_release * This source packages matches the proposed SRU for jammy handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1995054 and its backport is currently provided by the LibreOffice Still PPA at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+packages * Previous backport of 7.3.6 handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1990382 * LibreOffice 6.4.7 (EOL since November 30, 2020) is currently released in focal. * LibreOffice 7.3.6 is currently released in bionic-backports. * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/1:7.3.7-0ubuntu0.22.04.1 * Backport target is Bionic/18.04 LTS only to provide an official build of a more recent upstream version of LibreOffice [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_73/2020/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. * [amd64] ... * [arm64] ... * [armhf] ... * [ppc64el] ... * [s390x] ... * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 28 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1996082/+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 1996082] [NEW] [BPO] libreoffice 7.3.7 for bionic
Public bug reported: [Impact] * LibreOffice 7.3.7 is in its seventh bugfix release of the 7.3 line: https://wiki.documentfoundation.org/ReleasePlan/7.3#7.3.7_release * This source packages matches the proposed SRU for jammy handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1995054 and its backport is currently provided by the LibreOffice Still PPA at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+packages * Previous backport of 7.3.6 handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1990382 * LibreOffice 6.4.7 (EOL since November 30, 2020) is currently released in focal. * LibreOffice 7.3.6 is currently released in bionic-backports. * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/1:7.3.7-0ubuntu0.22.04.1 * Backport target is Bionic/18.04 LTS only to provide an official build of a more recent upstream version of LibreOffice [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_73/2020/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. * [amd64] ... * [arm64] ... * [armhf] ... * [ppc64el] ... * [s390x] ... * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 28 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: libreoffice (Ubuntu Bionic) Importance: High Assignee: Rico Tzschichholz (ricotz) Status: In Progress ** Also affects: libreoffice (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: libreoffice (Ubuntu) Status: New => Fix Released ** Changed in: libreoffice (Ubuntu Bionic) Status: New => In Progress ** Changed in: libreoffice (Ubuntu Bionic) Importance: Undecided => High ** Changed in: libreoffice (Ubuntu Bionic) Assignee: (unassigned) => Rico Tzschichholz (ricotz) -- 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/1996082 Title: [BPO] libreoffice 7.3.7 for bionic Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Bionic: In Progress Bug description: [Impact] * LibreOffice 7.3.7 is in its seventh bugfix release of the 7.3 line: https://wiki.documentfoundation.org/ReleasePlan/7.3#7.3.7_release * This source packages matches the proposed SRU for jammy handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1995054 and its backport is currently provided by the LibreOffice Still PPA at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+packages * Previous backport of 7.3.6 handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1990382 * LibreOffice 6.4.7 (EOL since November 30, 2020) is currently released in focal. * LibreOffice 7.3.6 is currently released in bionic-backports. * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/1:7.3.7-0ubuntu0.22.04.1 * Backport target is Bionic/18.04 LTS only to provide an official build of a more recent upstream version of LibreOffice [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the rele
[Desktop-packages] [Bug 1996076] [NEW] [BPO] libreoffice 7.3.7 for focal
Public bug reported: [Impact] * LibreOffice 7.3.7 is in its seventh bugfix release of the 7.3 line: https://wiki.documentfoundation.org/ReleasePlan/7.3#7.3.7_release * This source packages matches the proposed SRU for jammy handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1995054 and its backport is currently provided by the LibreOffice Still PPA at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+packages * Previous backport of 7.3.6 handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1989418 * LibreOffice 6.4.7 (EOL since November 30, 2020) is currently released in focal. * LibreOffice 7.3.6 is currently released in focal-backports. * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/1:7.3.7-0ubuntu0.22.04.1 * Backport target is Focal/20.04 LTS only to provide an official build of a more recent upstream version of LibreOffice [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_73/2020/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/amd64/libr/libreoffice/20221109_131732_0f324@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/arm64/libr/libreoffice/20221109_134252_403d2@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/armhf/libr/libreoffice/20221109_152925_85c50@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/ppc64el/libr/libreoffice/20221109_134511_07b38@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/s390x/libr/libreoffice/20221109_125147_0715b@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 28 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: libreoffice (Ubuntu Focal) Importance: High Assignee: Rico Tzschichholz (ricotz) Status: In Progress ** Also affects: libreoffice (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: libreoffice (Ubuntu Focal) Status: New => In Progress ** Changed in: libreoffice (Ubuntu Focal) Importance: Undecided => High ** Changed in: libreoffice (Ubuntu Focal) Assignee: (unassigned) => Rico Tzschichholz (ricotz) ** Changed in: libreoffice (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1996076 Title: [BPO] libreoffice 7.3.7 for focal Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Focal: In Progress Bug description: [Impact] * LibreOffice 7.3.7 is in its seventh bugfix release of the 7.3 line: https://wiki.documentfoundation.org/ReleasePlan/7.3#7.3.7_release * This source packages matches the proposed SRU for jammy handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1995054 and its backport is currently provided by the LibreOffice Still PPA at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+packages * Previous backport of 7.3.6 handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/19894
[Desktop-packages] [Bug 1996076] Re: [BPO] libreoffice 7.3.7 for focal
** Patch added: "libreoffice_7.3.7-0ubuntu0.22.04.1_bpo20.04.1.patch" https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1996076/+attachment/5630088/+files/libreoffice_7.3.7-0ubuntu0.22.04.1_bpo20.04.1.patch -- 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/1996076 Title: [BPO] libreoffice 7.3.7 for focal Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Focal: In Progress Bug description: [Impact] * LibreOffice 7.3.7 is in its seventh bugfix release of the 7.3 line: https://wiki.documentfoundation.org/ReleasePlan/7.3#7.3.7_release * This source packages matches the proposed SRU for jammy handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1995054 and its backport is currently provided by the LibreOffice Still PPA at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+packages * Previous backport of 7.3.6 handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1989418 * LibreOffice 6.4.7 (EOL since November 30, 2020) is currently released in focal. * LibreOffice 7.3.6 is currently released in focal-backports. * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/1:7.3.7-0ubuntu0.22.04.1 * Backport target is Focal/20.04 LTS only to provide an official build of a more recent upstream version of LibreOffice [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_73/2020/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/amd64/libr/libreoffice/20221109_131732_0f324@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/arm64/libr/libreoffice/20221109_134252_403d2@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/armhf/libr/libreoffice/20221109_152925_85c50@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/ppc64el/libr/libreoffice/20221109_134511_07b38@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/s390x/libr/libreoffice/20221109_125147_0715b@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 28 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1996076/+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 1995137] Re: "sun4i-drm_dri.so" is missing from libg1-mesa-dri on riscv64
The attached debdiff enables building the lima driver on riscv64. This drivers provides sun4i-drm_dri.so. I'm currently testing this locally and waiting on riscv64 to be enabled for my PPA to build a package on LP. ** Patch added: "mesa-build-lima-on-riscv64.debdiff" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1995137/+attachment/5630053/+files/mesa-build-lima-on-riscv64.debdiff -- 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/1995137 Title: "sun4i-drm_dri.so" is missing from libg1-mesa-dri on riscv64 Status in mesa package in Ubuntu: New Bug description: "sun4i-drm_dri.so" is needed for some RISC-V platforms such as the Allwinner D1. This file is missing from the riscv64 packages, but present on others. This affects (at least) 20.04 and 22.04. itrue@lxc-focal ~/tmp> dpkg -c libgl1-mesa-dri_21.2.6-0ubuntu0.1~20.04.2_arm64.deb | grep _dri.so *snip* hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/aarch64-linux-gnu/dri/sun4i-drm_dri.so link to ./usr/lib/aarch64-linux-gnu/dri/armada-drm_dri.so *snip* itrue@lxc-focal ~/tmp> dpkg -c libgl1-mesa-dri_21.2.6-0ubuntu0.1~20.04.2_riscv64.deb | grep _dri.so -rw-r--r-- root/root 16498024 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/nouveau_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so -rw-r--r-- root/root 4692400 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/nouveau_vieux_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/r200_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/nouveau_vieux_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/r300_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/r600_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/radeon_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/nouveau_vieux_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/radeonsi_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/swrast_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/virtio_gpu_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so hrw-r--r-- root/root 0 2022-03-08 16:37 ./usr/lib/riscv64-linux-gnu/dri/zink_dri.so link to ./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1995137/+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 1996068] Re: i915 crash at boot time (probably to activate vga console)
** Package changed: mutter (Ubuntu) => linux (Ubuntu) ** Attachment added: "Output of dmidecoe" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996068/+attachment/5630050/+files/dmi.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1996068 Title: i915 crash at boot time (probably to activate vga console) Status in linux package in Ubuntu: New Bug description: This is using kernel 5.19 on a Lenovo X1 Carbon 10th Gen. Nov 5 09:46:42 shusaku kernel: [2.209937] [ cut here ] Nov 5 09:46:42 shusaku kernel: [2.209938] i915 :00:02.0: Block 42 min_size is zero Nov 5 09:46:42 shusaku kernel: [2.209953] WARNING: CPU: 2 PID: 254 at drivers/gpu/drm/i915/display/intel_bios.c:476 init_bdb_block+0x29a/0x460 [i915] Nov 5 09:46:42 shusaku kernel: [2.210068] Modules linked in: fjes(+) i915(+) drm_buddy i2c_algo_bit ttm drm_display_helper hid_generic cec rc_core drm_kms_helper syscopyarea sysfillrect sysimgblt crct10dif_pclmul crc32_pclmul ghash_c lmulni_intel fb_sys_fops aesni_intel i2c_hid_acpi crypto_simd intel_lpss_pci nvme cryptd spi_intel_pci psmouse drm i2c_i801 i2c_hid xhci_pci intel_lpss thunderbolt(+) spi_intel i2c_smbus nvme_core idma64 xhci_pci_renesas wmi hid video pin ctrl_tigerlake Nov 5 09:46:42 shusaku kernel: [2.210087] CPU: 2 PID: 254 Comm: systemd-udevd Not tainted 5.19.0-23-generic #24-Ubuntu Nov 5 09:46:42 shusaku kernel: [2.210089] Hardware name: LENOVO 21CBCTO1WW/21CBCTO1WW, BIOS N3AET65W (1.30 ) 08/02/2022 Nov 5 09:46:42 shusaku kernel: [2.210091] RIP: 0010:init_bdb_block+0x29a/0x460 [i915] Nov 5 09:46:42 shusaku kernel: [2.210166] Code: 8b 7b 08 4c 8b 77 50 4d 85 f6 74 29 4c 89 4d c8 e8 bb cc 41 e3 44 89 e1 4c 89 f2 48 c7 c7 f0 42 8b c0 48 89 c6 e8 eb 96 8f e3 <0f> 0b 4c 8b 4d c8 e9 b7 fd ff ff 4c 8b 37 eb d2 4c 89 e6 48 c7 c7 Nov 5 09:46:42 shusaku kernel: [2.210168] RSP: 0018:abb9c0953888 EFLAGS: 00010246 Nov 5 09:46:42 shusaku kernel: [2.210170] RAX: RBX: 8ca1a1108000 RCX: Nov 5 09:46:42 shusaku kernel: [2.210171] RDX: RSI: RDI: Nov 5 09:46:42 shusaku kernel: [2.210172] RBP: abb9c09538d8 R08: R09: Nov 5 09:46:42 shusaku kernel: [2.210173] R10: R11: R12: 002a Nov 5 09:46:42 shusaku kernel: [2.210174] R13: R14: 8ca1826ad170 R15: 8ca1a1109328 Nov 5 09:46:42 shusaku kernel: [2.210175] FS: 7f21d34178c0() GS:8ca8bf48() knlGS: Nov 5 09:46:42 shusaku kernel: [2.210176] CS: 0010 DS: ES: CR0: 80050033 Nov 5 09:46:42 shusaku kernel: [2.210177] CR2: 55a99a0511d8 CR3: 00011d202003 CR4: 00770ee0 Nov 5 09:46:42 shusaku kernel: [2.210179] PKRU: 5554 Nov 5 09:46:42 shusaku kernel: [2.210179] Call Trace: Nov 5 09:46:42 shusaku kernel: [2.210181] Nov 5 09:46:42 shusaku kernel: [2.210183] intel_bios_init+0x171/0x7c0 [i915] Nov 5 09:46:42 shusaku kernel: [2.210312] ? drm_vblank_worker_init+0x68/0x80 [drm] Nov 5 09:46:42 shusaku kernel: [2.210391] intel_modeset_init_noirq+0x3b/0x250 [i915] Nov 5 09:46:42 shusaku kernel: [2.210594] i915_driver_probe+0x1ae/0x490 [i915] Nov 5 09:46:42 shusaku kernel: [2.210765] ? drm_privacy_screen_get+0x16d/0x190 [drm] Nov 5 09:46:42 shusaku kernel: [2.210833] ? acpi_dev_found+0x64/0x80 Nov 5 09:46:42 shusaku kernel: [2.210842] i915_pci_probe+0x56/0x150 [i915] Nov 5 09:46:42 shusaku kernel: [2.210935] local_pci_probe+0x44/0x90 Nov 5 09:46:42 shusaku kernel: [2.210939] pci_call_probe+0x55/0x190 Nov 5 09:46:42 shusaku kernel: [2.210940] pci_device_probe+0x84/0x120 Nov 5 09:46:42 shusaku kernel: [2.210941] really_probe+0x1dc/0x3b0 Nov 5 09:46:42 shusaku kernel: [2.210945] __driver_probe_device+0x12c/0x1b0 Nov 5 09:46:42 shusaku kernel: [2.210946] driver_probe_device+0x24/0xd0 Nov 5 09:46:42 shusaku kernel: [2.210948] __driver_attach+0xe0/0x210 Nov 5 09:46:42 shusaku kernel: [2.210949] ? __device_attach_driver+0x130/0x130 Nov 5 09:46:42 shusaku kernel: [2.210951] bus_for_each_dev+0x8d/0xe0 Nov 5 09:46:42 shusaku kernel: [2.210952] driver_attach+0x1e/0x30 Nov 5 09:46:42 shusaku kernel: [2.210953] bus_add_driver+0x187/0x230 Nov 5 09:46:42 shusaku kernel: [2.210955] driver_register+0x8f/0x100 Nov 5 09:46:42 shusaku kernel: [2.210956] __pci_register_driver+0x62/0x70 Nov 5 09:46:42 shusaku kernel: [2.210958] i915_pci_register_driver+0x23/0x30 [i915] Nov 5 09:46:42 shusaku kernel: [2.210993] i915_init+0x3b/0xf2
[Desktop-packages] [Bug 1996068] [NEW] i915 crash at boot time (probably to activate vga console)
Public bug reported: This is using kernel 5.19 on a Lenovo X1 Carbon 10th Gen. Nov 5 09:46:42 shusaku kernel: [2.209937] [ cut here ] Nov 5 09:46:42 shusaku kernel: [2.209938] i915 :00:02.0: Block 42 min_size is zero Nov 5 09:46:42 shusaku kernel: [2.209953] WARNING: CPU: 2 PID: 254 at drivers/gpu/drm/i915/display/intel_bios.c:476 init_bdb_block+0x29a/0x460 [i915] Nov 5 09:46:42 shusaku kernel: [2.210068] Modules linked in: fjes(+) i915(+) drm_buddy i2c_algo_bit ttm drm_display_helper hid_generic cec rc_core drm_kms_helper syscopyarea sysfillrect sysimgblt crct10dif_pclmul crc32_pclmul ghash_c lmulni_intel fb_sys_fops aesni_intel i2c_hid_acpi crypto_simd intel_lpss_pci nvme cryptd spi_intel_pci psmouse drm i2c_i801 i2c_hid xhci_pci intel_lpss thunderbolt(+) spi_intel i2c_smbus nvme_core idma64 xhci_pci_renesas wmi hid video pin ctrl_tigerlake Nov 5 09:46:42 shusaku kernel: [2.210087] CPU: 2 PID: 254 Comm: systemd-udevd Not tainted 5.19.0-23-generic #24-Ubuntu Nov 5 09:46:42 shusaku kernel: [2.210089] Hardware name: LENOVO 21CBCTO1WW/21CBCTO1WW, BIOS N3AET65W (1.30 ) 08/02/2022 Nov 5 09:46:42 shusaku kernel: [2.210091] RIP: 0010:init_bdb_block+0x29a/0x460 [i915] Nov 5 09:46:42 shusaku kernel: [2.210166] Code: 8b 7b 08 4c 8b 77 50 4d 85 f6 74 29 4c 89 4d c8 e8 bb cc 41 e3 44 89 e1 4c 89 f2 48 c7 c7 f0 42 8b c0 48 89 c6 e8 eb 96 8f e3 <0f> 0b 4c 8b 4d c8 e9 b7 fd ff ff 4c 8b 37 eb d2 4c 89 e6 48 c7 c7 Nov 5 09:46:42 shusaku kernel: [2.210168] RSP: 0018:abb9c0953888 EFLAGS: 00010246 Nov 5 09:46:42 shusaku kernel: [2.210170] RAX: RBX: 8ca1a1108000 RCX: Nov 5 09:46:42 shusaku kernel: [2.210171] RDX: RSI: RDI: Nov 5 09:46:42 shusaku kernel: [2.210172] RBP: abb9c09538d8 R08: R09: Nov 5 09:46:42 shusaku kernel: [2.210173] R10: R11: R12: 002a Nov 5 09:46:42 shusaku kernel: [2.210174] R13: R14: 8ca1826ad170 R15: 8ca1a1109328 Nov 5 09:46:42 shusaku kernel: [2.210175] FS: 7f21d34178c0() GS:8ca8bf48() knlGS: Nov 5 09:46:42 shusaku kernel: [2.210176] CS: 0010 DS: ES: CR0: 80050033 Nov 5 09:46:42 shusaku kernel: [2.210177] CR2: 55a99a0511d8 CR3: 00011d202003 CR4: 00770ee0 Nov 5 09:46:42 shusaku kernel: [2.210179] PKRU: 5554 Nov 5 09:46:42 shusaku kernel: [2.210179] Call Trace: Nov 5 09:46:42 shusaku kernel: [2.210181] Nov 5 09:46:42 shusaku kernel: [2.210183] intel_bios_init+0x171/0x7c0 [i915] Nov 5 09:46:42 shusaku kernel: [2.210312] ? drm_vblank_worker_init+0x68/0x80 [drm] Nov 5 09:46:42 shusaku kernel: [2.210391] intel_modeset_init_noirq+0x3b/0x250 [i915] Nov 5 09:46:42 shusaku kernel: [2.210594] i915_driver_probe+0x1ae/0x490 [i915] Nov 5 09:46:42 shusaku kernel: [2.210765] ? drm_privacy_screen_get+0x16d/0x190 [drm] Nov 5 09:46:42 shusaku kernel: [2.210833] ? acpi_dev_found+0x64/0x80 Nov 5 09:46:42 shusaku kernel: [2.210842] i915_pci_probe+0x56/0x150 [i915] Nov 5 09:46:42 shusaku kernel: [2.210935] local_pci_probe+0x44/0x90 Nov 5 09:46:42 shusaku kernel: [2.210939] pci_call_probe+0x55/0x190 Nov 5 09:46:42 shusaku kernel: [2.210940] pci_device_probe+0x84/0x120 Nov 5 09:46:42 shusaku kernel: [2.210941] really_probe+0x1dc/0x3b0 Nov 5 09:46:42 shusaku kernel: [2.210945] __driver_probe_device+0x12c/0x1b0 Nov 5 09:46:42 shusaku kernel: [2.210946] driver_probe_device+0x24/0xd0 Nov 5 09:46:42 shusaku kernel: [2.210948] __driver_attach+0xe0/0x210 Nov 5 09:46:42 shusaku kernel: [2.210949] ? __device_attach_driver+0x130/0x130 Nov 5 09:46:42 shusaku kernel: [2.210951] bus_for_each_dev+0x8d/0xe0 Nov 5 09:46:42 shusaku kernel: [2.210952] driver_attach+0x1e/0x30 Nov 5 09:46:42 shusaku kernel: [2.210953] bus_add_driver+0x187/0x230 Nov 5 09:46:42 shusaku kernel: [2.210955] driver_register+0x8f/0x100 Nov 5 09:46:42 shusaku kernel: [2.210956] __pci_register_driver+0x62/0x70 Nov 5 09:46:42 shusaku kernel: [2.210958] i915_pci_register_driver+0x23/0x30 [i915] Nov 5 09:46:42 shusaku kernel: [2.210993] i915_init+0x3b/0xf2 [i915] Nov 5 09:46:42 shusaku kernel: [2.211045] ? 0xc098b000 Nov 5 09:46:42 shusaku kernel: [2.211046] do_one_initcall+0x5b/0x240 Nov 5 09:46:42 shusaku kernel: [2.211049] do_init_module+0x50/0x210 Nov 5 09:46:42 shusaku kernel: [2.211051] load_module+0xb7d/0xcd0 Nov 5 09:46:42 shusaku kernel: [2.211053] __do_sys_finit_module+0xc4/0x140 Nov 5 09:46:42 shusaku kernel: [2.211054] ? __do_sys_finit_module+0xc4/0x140 Nov 5 09:46:42 shusaku kernel: [2.211056] __x64_sys_finit_module+0x18/0x30 Nov 5 09:46:42 shusaku
[Desktop-packages] [Bug 1996067] [NEW] [SRU] Enable support for Antelope Cloud Archive
Public bug reported: Please add support for: cloud-archive:antelope cloud-archive:antelope-proposed This will also need to be SRU'd back to jammy. [Impact] End users have to manually enable the antelope cloud archive pockets. [Test case] sudo add-apt-repository cloud-archive:antelope sudo add-apt-repository cloud-archive:antelope-proposed [Regression potential] Limited - just a data item addition ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1996067 Title: [SRU] Enable support for Antelope Cloud Archive Status in software-properties package in Ubuntu: New Bug description: Please add support for: cloud-archive:antelope cloud-archive:antelope-proposed This will also need to be SRU'd back to jammy. [Impact] End users have to manually enable the antelope cloud archive pockets. [Test case] sudo add-apt-repository cloud-archive:antelope sudo add-apt-repository cloud-archive:antelope-proposed [Regression potential] Limited - just a data item addition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1996067/+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 1983794] Re: Evolution not deleting autosave files
Thanks, uninstalling libcanberra-gtk-3-0 helped with this. (I'd only
installed it way back in the distant past to stop those stupid warnings
on the command line!)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libcanberra in Ubuntu.
https://bugs.launchpad.net/bugs/1983794
Title:
Evolution not deleting autosave files
Status in Evolution:
Fix Released
Status in evolution package in Ubuntu:
Invalid
Status in libcanberra package in Ubuntu:
Triaged
Bug description:
Running Ubuntu MATE, Ubuntu 22.04.1 LTS. Evolution v3.44.1-0ubuntu1
was installed with the distribution on a new system and received
settings imported from an earlier version on another computer.
When composing an email, if the process takes long enough an autosave
file is created as ~/.local/share/evolution/.evolution-
composer.autosave-xx ("xx" is a random 6 character string).
When the email is successfully sent, the autosave file SHOULD be
deleted. It's not. When evolution is shut down and restarted I'm asked
if I want to recover an unfinished email. Answering No to this will
delete the autosave file, but otherwise it persists and the recovery
query recurs the next time I open evolution.
Other people are having the same issue, see
https://gitlab.gnome.org/GNOME/evolution/-/issues/1972. The Gnome
people aren't dealing with it, perhaps considering it a distro-
specific bug.
On a system used by many people this is a potential security issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution/+bug/1983794/+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 1996053] [NEW] No GUI after upgrade from 22.04.1 to 22.10
Public bug reported: I am running Ubuntu 22.04.1 on a VM under TrueNas. After upgrade to 22.10 I just ends up with a black screen, however, everything else like mail, dns, dhcp and apache2 works well. I am using x11vnc and in the 'journalctl -b' it seems that a display cannot be achieved. In the boot menu I have *Ubuntu, with Linux version 5.19.0-23-generic Ubuntu, with Linux version 5.15.0-52-generic However, if I am booting 5.15.0-52 everything is OK. - lsb_release -rd Description:Ubuntu 22.10 Release:22.10 - cat /proc/version_signature Ubuntu 5.19.0-23.24-generic 5.19.7 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- 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/1996053 Title: No GUI after upgrade from 22.04.1 to 22.10 Status in gnome-shell package in Ubuntu: New Bug description: I am running Ubuntu 22.04.1 on a VM under TrueNas. After upgrade to 22.10 I just ends up with a black screen, however, everything else like mail, dns, dhcp and apache2 works well. I am using x11vnc and in the 'journalctl -b' it seems that a display cannot be achieved. In the boot menu I have *Ubuntu, with Linux version 5.19.0-23-generic Ubuntu, with Linux version 5.15.0-52-generic However, if I am booting 5.15.0-52 everything is OK. - lsb_release -rd Description: Ubuntu 22.10 Release: 22.10 - cat /proc/version_signature Ubuntu 5.19.0-23.24-generic 5.19.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1996053/+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 1963767] Re: [Purism Librem 13 v4] Microphone not working after suspend
If it happens on all or a large number or systems then people should share the same bug. Or if they have the same hardware (same laptop or same sound chips). Otherwise people should each log their own bug because in most cases problems like this are hardware-specific. So I'm thinking that's 3 separate bugs here. I only have access to Ubuntu 22.10 today so can only confirm that the bug does not happen on 22.10 here. It would be useful to ask more users of 22.04 to test this so Incomplete... ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => Incomplete ** Summary changed: - [Purism Librem 13 v4] Microphone not working after suspend + [jammy] Microphone not working after suspend -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1963767 Title: [jammy] Microphone not working after suspend Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: I have Logitech BRIO 4k Pro webcam connected via its USB cable to Asus Vivobook Pro 16X OLED M7600QE-L2014X (90NB0V71-M02190) laptop. On Ubuntu 21.10 after suspend (`systemctl suspend`) webcam's microphone stops working (device is still there, but audio level is at zero all the time). To make it work again I need to do 2 things (just one is not sufficient): 1) Disconnect and connect webcam again to the laptop 2) Restart pulseaudio with `pulseaudio --kill; pulseaudio --start` Not sure whose fault it is, likely kernel driver, but the fact that pulseaudio needs to be restarted is concerning as well. Reproducible 100% for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Custom DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2 PackageArchitecture: amd64 Tags: impish Uname: Linux 5.16.11-xanmod1 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nazar-pc 1488 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-15 (153 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04ca:300d Lite-On Technology Corp. Atheros AR3012 Bluetooth Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 3: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 3: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M MachineType: Purism Librem 13 v4 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=uk_UA.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-39-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 RelatedPackageVersions: linux-restricted-modules-5.15.0-39-generic N/A linux-backports-modules-5.15.0-39-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy wayland-session wayland-session Uname: Linux 5.15.0-39-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-06-21 (27 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/27/2022 dmi.bios.release: 4.15 dmi.bios.vendor: coreboot dmi.bios.version: 4.15-Purism-3 dmi.board.name: Librem 13 v4 dmi.board.vendor: Purism dmi.board.version: 1.0 dmi.chassis.type: 9 dmi.chassis.vendor: Purism dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvr4.15-Purism-3:bd01/27/2022:br4.15:efr0.0:svnPurism:pnLibrem13v4:pvr1.0:rvnPurism:rnLibrem13v4:rvr1.0:cvnPurism:ct9:cvr:sku: dmi.product.family: Librem 13 dmi.product.name: Librem 13 v4 dmi.product.version: 1.0 dmi.sys.vendor: Purism To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1963767/+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 1790608] Re: [snap] Libreoffice/Firefox do not open files from thunderbird (more general: from /tmp)
Same, if you click a link in evolution mail that should open in firefox. It breaks such an important use case that I don't understand, how snap moved forward to standard. Can't explain this to friends, whom I have recommended changing to Ubuntu. -- 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/1790608 Title: [snap] Libreoffice/Firefox do not open files from thunderbird (more general: from /tmp) Status in snapd: New Status in firefox package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: I received a document via e-mail in Thunderbird. I have the Libreoffice snap package installed. When I want to open the document from Thunderbird, I see the Libreoffice splash screen, and then a dialog stating "/tmp/mozilla_0/.docx does not exist." The same dialog appears when I navigate to the folder in Files and want to open it. When I copy the file to my desktop, however, I can open it without problems. I guess the source of the issue is confinement, that the Libreoffice snap can only access files from $HOME. But this breaks the case where thunderbird creates a temporary copy in /tmp. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1790608/+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 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
Same issue here. - HW:Lenovo ThinkPad X1 Carbon Gen 10 - HeadSet: Sennheiser 4.50BTNC - OS: Ubuntu 22.04.1 LTS (Jammy Jellyfish) - BT fw: intel/ibt-0040-0041.sfi - Kernel: 5.15.0-52-generic #58-Ubuntu SMP If high quality output is selected no input channel is available. To be able to use the headphones mic one has to use the mono channel output ... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Fix Released Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+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 1987631] Re: Screencast only records one second
On 22.10, our customer could not reproduce this issue. I picked the patch in pipewire, the screencast becomes stable, the fail rate is lower than before, although it would skip frames for seconds. I will let our customer do more test. https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/1ea1d525 https://people.canonical.com/~binli/pipewire/ -- 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/1987631 Title: Screencast only records one second Status in GNOME Shell: Fix Released Status in OEM Priority Project: In Progress Status in gnome-shell package in Ubuntu: Fix Released Status in pipewire package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: Fix Released Status in pipewire source package in Jammy: New Bug description: When recording a screencast with gnome on kinetic the resulting video will play for one second and then freeze. It looks like the same bug was discussed upstream at https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/5585 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1987631/+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 1987631] Re: Screencast only records one second
** Tags added: oem-priority originate-from-1994117 sutton ** Changed in: oem-priority Assignee: (unassigned) => Bin Li (binli) ** Changed in: oem-priority Importance: Undecided => High ** Changed in: oem-priority Status: New => In Progress -- 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/1987631 Title: Screencast only records one second Status in GNOME Shell: Fix Released Status in OEM Priority Project: In Progress Status in gnome-shell package in Ubuntu: Fix Released Status in pipewire package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: Fix Released Status in pipewire source package in Jammy: New Bug description: When recording a screencast with gnome on kinetic the resulting video will play for one second and then freeze. It looks like the same bug was discussed upstream at https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/5585 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1987631/+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
