[Desktop-packages] [Bug 2009354] Re: [SRU] libreoffice 7.4.6 for kinetic
** Description changed: [Impact] * LibreOffice 7.4.6 is in its sixth bugfix release of the 7.4 line: https://wiki.documentfoundation.org/ReleasePlan/7.4#7.4.6_release - * Version 7.4.4/7.4.5 is currently released in kinetic. For a list of fixed bugs compared to 7.4.5 see the list of bugs fixed in the release candidates of 7.4.6 (that's a total of 74 bugs): + * Version 7.4.4 is currently released in kinetic. For a list of fixed bugs compared to 7.4.5 see the list of bugs fixed in the release candidates of 7.4.6 (that's a total of 74 bugs): https://wiki.documentfoundation.org/Releases/7.4.6/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.4.6/RC2#List_of_fixed_bugs + * 7.4.5 was an intermediate hotfix release with one bug fix which got cherry-picked as 1:7.4.4-0ubuntu0.22.10.2 * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_74/1717/ * 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-kinetic-ricotz-ppa/kinetic/amd64/libr/libreoffice/20230308_174140_556be@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic-ricotz-ppa/kinetic/arm64/libr/libreoffice/20230308_194429_0c8b8@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic-ricotz-ppa/kinetic/armhf/libr/libreoffice/20230308_202215_690b5@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic-ricotz-ppa/kinetic/ppc64el/libr/libreoffice/20230308_174403_74fe7@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic-ricotz-ppa/kinetic/s390x/libr/libreoffice/20230308_200234_9c534@/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 74 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/2009354 Title: [SRU] libreoffice 7.4.6 for kinetic Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Kinetic: Incomplete Bug description: [Impact] * LibreOffice 7.4.6 is in its sixth bugfix release of the 7.4 line: https://wiki.documentfoundation.org/ReleasePlan/7.4#7.4.6_release * Version 7.4.4 is currently released in kinetic. For a list of fixed bugs compared to 7.4.5 see the list of bugs fixed in the release candidates of 7.4.6 (that's a total of 74 bugs): https://wiki.documentfoundation.org/Releases/7.4.6/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.4.6/RC2#List_of_fixed_bugs * 7.4.5 was an intermediate hotfix release with one bug fix which got cherry-picked as 1:7.4.4-0ubuntu0.22.10.2 * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_74/1717/ * More information about the upstream QA testing can be found here: * Automated tests
[Desktop-packages] [Bug 2009944] Re: [BPO] libreoffice 7.4.6 for bionic, focal and jammy
** Description changed: [Impact] * LibreOffice 7.4.6 is in its sixth bugfix release of the 7.4 line: https://wiki.documentfoundation.org/ReleasePlan/7.4#7.4.6_release * This source packages matches the proposed SRU for kinetic handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2009354 and its backport is currently provided by the LibreOffice Still PPA at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+packages * LibreOffice 7.3.7 (EOL since November 30, 2022) is currently released in bionic-/focal-backports [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/1:7.4.6-0ubuntu0.22.10.1 * Backport targets are the Bionic/18.04, Focal/20.04 and Jammy/22.04 LTS releases 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_74/1717/ * 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. -Bionic/18.04 build at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+sourcepub/14541804/+listing-archive-extra - * [amd64] ... - * [arm64] ... - * [armhf] ... - * [ppc64el] ... - * [s390x] ... + Bionic/18.04 build at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+sourcepub/14541804/+listing-archive-extra + * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/amd64/libr/libreoffice/20230311_021721_5528d@/log.gz + * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/arm64/libr/libreoffice/20230311_022133_e8482@/log.gz + * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/armhf/libr/libreoffice/20230311_034543_5547f@/log.gz + * [i386l] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/i386/libr/libreoffice/20230311_024716_6fc50@/log.gz + * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/ppc64el/libr/libreoffice/20230311_013201_6dbb2@/log.gz + * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/s390x/libr/libreoffice/20230311_013952_49140@/log.gz -Focal/20.04 build at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+sourcepub/14541807/+listing-archive-extra - * [amd64] ... - * [arm64] ... - * [armhf] ... - * [ppc64el] ... - * [s390x] ... + Focal/20.04 build at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+sourcepub/14541807/+listing-archive-extra + * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/amd64/libr/libreoffice/20230311_001616_c1e3a@/log.gz + * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/arm64/libr/libreoffice/20230310_164346_4ac1d@/log.gz + * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/armhf/libr/libreoffice/20230311_052748_8b7c3@/log.gz + * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/ppc64el/libr/libreoffice/20230310_151809_05c21@/log.gz + * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/s390x/libr/libreoffice/20230310_190707_a5b67@/log.gz -Jammy/22.04 build at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+sourcepub/14541810/+listing-archive-extra - * [amd64] ... - * [arm64] ... - * [armhf] ... - * [ppc64el] ... - * [s390x] ... + Jammy/22.04 build at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+sourcepub/14541810/+listing-archive-extra + * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-still/jammy/amd64/libr/libreoffice/20230310_160612_6f011@/log.gz + * [arm64]
[Desktop-packages] [Bug 2009354] Re: [SRU] libreoffice 7.4.6 for kinetic
@vorlon Thanks for your review. tdf153059-after-ChangeHeaderOrFooter-the-c.patch was the only change in the unscheduled 7.4.5 hotfix release, and was cherry picked to avoid a full-source upload. https://wiki.documentfoundation.org/Releases/7.4.5/RC1 For the debian/*.symbols, I trust Rene that this is a proper way of dealing with those special library packages. Dropping "make check for s390x" is rather frustrating while the launchpad s390x builders are silently stopping without providing any log for investigation (Retried multiple times with 7.4.4 to no avail). Having the autopkgtest running afterwards covers the test-suite as well. https://git.launchpad.net/~libreoffice/ubuntu/+source/libreoffice/log/?h=wip/kinetic-7.4 -- 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/2009354 Title: [SRU] libreoffice 7.4.6 for kinetic Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Kinetic: Incomplete Bug description: [Impact] * LibreOffice 7.4.6 is in its sixth bugfix release of the 7.4 line: https://wiki.documentfoundation.org/ReleasePlan/7.4#7.4.6_release * Version 7.4.4/7.4.5 is currently released in kinetic. For a list of fixed bugs compared to 7.4.5 see the list of bugs fixed in the release candidates of 7.4.6 (that's a total of 74 bugs): https://wiki.documentfoundation.org/Releases/7.4.6/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.4.6/RC2#List_of_fixed_bugs * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_74/1717/ * 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-kinetic-ricotz-ppa/kinetic/amd64/libr/libreoffice/20230308_174140_556be@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic-ricotz-ppa/kinetic/arm64/libr/libreoffice/20230308_194429_0c8b8@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic-ricotz-ppa/kinetic/armhf/libr/libreoffice/20230308_202215_690b5@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic-ricotz-ppa/kinetic/ppc64el/libr/libreoffice/20230308_174403_74fe7@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic-ricotz-ppa/kinetic/s390x/libr/libreoffice/20230308_200234_9c534@/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 74 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/2009354/+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 2011283] [NEW] package libayatana-ido3-0.4-0:amd64 0.9.2-1 failed to install/upgrade: 写入 <标准输出> 出错: 没有那个文件或目录
Public bug reported: i don't know. ProblemType: Package DistroRelease: Ubuntu 22.10 Package: libayatana-ido3-0.4-0:amd64 0.9.2-1 ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Mar 11 12:22:01 2023 ErrorMessage: 写入 <标准输出> 出错: 没有那个文件或目录 InstallationDate: Installed on 2023-03-10 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.9ubuntu1 apt 2.5.3 SourcePackage: ayatana-ido Title: package libayatana-ido3-0.4-0:amd64 0.9.2-1 failed to install/upgrade: 写入 <标准输出> 出错: 没有那个文件或目录 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ayatana-ido (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package kinetic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ayatana-ido in Ubuntu. https://bugs.launchpad.net/bugs/2011283 Title: package libayatana-ido3-0.4-0:amd64 0.9.2-1 failed to install/upgrade: 写入 <标准输出> 出错: 没有那个文件或目录 Status in ayatana-ido package in Ubuntu: New Bug description: i don't know. ProblemType: Package DistroRelease: Ubuntu 22.10 Package: libayatana-ido3-0.4-0:amd64 0.9.2-1 ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Mar 11 12:22:01 2023 ErrorMessage: 写入 <标准输出> 出错: 没有那个文件或目录 InstallationDate: Installed on 2023-03-10 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.9ubuntu1 apt 2.5.3 SourcePackage: ayatana-ido Title: package libayatana-ido3-0.4-0:amd64 0.9.2-1 failed to install/upgrade: 写入 <标准输出> 出错: 没有那个文件或目录 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ayatana-ido/+bug/2011283/+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 1990861] Re: can no longer click on speaker icon in system tray menu to mute/unmute
** Changed in: gnome-shell (Ubuntu) Status: Triaged => Fix Released -- 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/1990861 Title: can no longer click on speaker icon in system tray menu to mute/unmute Status in gnome-shell package in Ubuntu: Fix Released Bug description: In Jammy, if I opened the system menu (click on system tray in top right corner of screen) and clicked the little speaker icon it would mute my audio, and then if I clicked again it would unmute. That icon is no longer clickable in Kinetic. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 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: ubuntu:GNOME Date: Mon Sep 26 11:39:09 2022 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-16 (1136 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 43.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2022-09-24 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1990861/+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 2011281] [NEW] chromium snap upgrade "lost" my passwords
Public bug reported: On upgrade to chromium snap revision 2333 (now since upgraded to 2367), I received a window with a notice about password migration: "Password storage via the Gnome keyring has been fixed, but for it to work, you have to rename your old ~/snap/chromium/common/chromium/Default/Login Data file so that a new, working one can replace it." I don't remember if I did this or not. However, when I went to use my saved passwords in chromium today, I found that they were absent. Tracking down the data in the chromium profile, I found that there was a ~/snap/chromium/common/chromium/Default/Login Data.old containing all of my passwords, and a ~/snap/chromium/common/chromium/Default/Login Data containing a single password entry for a site that I happened to have created a new login for in the past few days. That's not a very user-friendly experience on upgrade. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: snap ** Tags added: snap -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2011281 Title: chromium snap upgrade "lost" my passwords Status in chromium-browser package in Ubuntu: New Bug description: On upgrade to chromium snap revision 2333 (now since upgraded to 2367), I received a window with a notice about password migration: "Password storage via the Gnome keyring has been fixed, but for it to work, you have to rename your old ~/snap/chromium/common/chromium/Default/Login Data file so that a new, working one can replace it." I don't remember if I did this or not. However, when I went to use my saved passwords in chromium today, I found that they were absent. Tracking down the data in the chromium profile, I found that there was a ~/snap/chromium/common/chromium/Default/Login Data.old containing all of my passwords, and a ~/snap/chromium/common/chromium/Default/Login Data containing a single password entry for a site that I happened to have created a new login for in the past few days. That's not a very user-friendly experience on upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2011281/+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 2010924] Re: MT7921K --> BLE funktion don't working
It's the kernel driver itself: mt7921 It's missing BLE support for this device. On Windows BLE is working. I really don't know witch one is the driver for bluetooth function for this device, because it's Wi-fi + BT 5.2 combo. Found in AMD Wi-Fi 6E RZ608 (MediaTek MT7921K) In this MB: X570S AORUS ELITE AX (rev. 1.1) And this wi-fi + BT combo are found in all new MB with integrated wi-fi + BT combos. ** Package changed: ubuntu => bluez (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2010924 Title: MT7921K --> BLE funktion don't working Status in bluez package in Ubuntu: New Bug description: Hi, i have MT7921K BT chip that BLE function is not working with linux, but normal BT is working. I try several distros and some live-iso and get same effect. BLE just not working with this device. I have other BT adapters and BLE is working for them. This is a probe for my PC: https://linux-hardware.org/?probe=969ab4279f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2010924/+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 2009354] Re: [SRU] libreoffice 7.4.6 for kinetic
- Dropping of debian/patches/tdf153059-after-ChangeHeaderOrFooter-the-c.patch is not documented in the changelog and needs to be. If this is dropped because it's now applied upstream, the changelog should say this. - The changing of debian/*.symbols in an SRU is weird. I see no reason to have these libraries emit a versioned dependency on libstdc++ themselves, this looks to me like it should have been a change to the lintian overrides only; and I'm not happy to sign off on this in an SRU without further rationale/explanation. - There is no rationale given for disabling 'make check' on s390x and reducing test coverage in an SRU is almost always a no-go. ** Changed in: libreoffice (Ubuntu Kinetic) Status: In Progress => Incomplete -- 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/2009354 Title: [SRU] libreoffice 7.4.6 for kinetic Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Kinetic: Incomplete Bug description: [Impact] * LibreOffice 7.4.6 is in its sixth bugfix release of the 7.4 line: https://wiki.documentfoundation.org/ReleasePlan/7.4#7.4.6_release * Version 7.4.4/7.4.5 is currently released in kinetic. For a list of fixed bugs compared to 7.4.5 see the list of bugs fixed in the release candidates of 7.4.6 (that's a total of 74 bugs): https://wiki.documentfoundation.org/Releases/7.4.6/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.4.6/RC2#List_of_fixed_bugs * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_74/1717/ * 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-kinetic-ricotz-ppa/kinetic/amd64/libr/libreoffice/20230308_174140_556be@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic-ricotz-ppa/kinetic/arm64/libr/libreoffice/20230308_194429_0c8b8@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic-ricotz-ppa/kinetic/armhf/libr/libreoffice/20230308_202215_690b5@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic-ricotz-ppa/kinetic/ppc64el/libr/libreoffice/20230308_174403_74fe7@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic-ricotz-ppa/kinetic/s390x/libr/libreoffice/20230308_200234_9c534@/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 74 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/2009354/+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 2010924] [NEW] MT7921K --> BLE funktion don't working
You have been subscribed to a public bug: Hi, i have MT7921K BT chip that BLE function is not working with linux, but normal BT is working. I try several distros and some live-iso and get same effect. BLE just not working with this device. I have other BT adapters and BLE is working for them. This is a probe for my PC: https://linux-hardware.org/?probe=969ab4279f ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- MT7921K --> BLE funktion don't working https://bugs.launchpad.net/bugs/2010924 You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2011270] Re: Printing intermittenly fails -- autodetected network printer
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2011270 Title: Printing intermittenly fails -- autodetected network printer Status in xorg package in Ubuntu: New Bug description: It appears that print jobs passed to the auto-detected printer "adding" wizard do not always succeed. See in these error messages how hpcups is passed a null object to print. It's unclear what the interactions is between the auto-discovery gnome(?) applet, the hpcups system, and dbus. The net effect is that a print job is sent to the printer defined here, and it just gets stuck in "stopped". With no error message or way for the user to resolve the issue. I'm not sure where to begin debugging ... Error messages in question : Mar 10 16:44:17 semiauto dbus-daemon[680]: [system] Activating service name='org.opensuse.CupsPkHelper.Mechanism' requested by ':1.1929' (uid=1000 pid=485631 comm="gnome-control-center printers" label="unconfined") (using servicehelper) Mar 10 16:44:17 semiauto dbus-daemon[680]: [system] Successfully activated service 'org.opensuse.CupsPkHelper.Mechanism' Mar 10 16:44:25 semiauto google-chrome.desktop[496973]: Warning: disabling flag --expose_wasm due to conflicting flags Mar 10 16:44:34 semiauto hpcups[515382]: common/utils.c 79: unable to open /var/lib/hp/hplip.state: No such file or directory Mar 10 16:44:34 semiauto hpcups[515382]: common/utils.c 129: validate_plugin_version() Failed to get Plugin version from [/var/lib/hp/hplip.state] Mar 10 16:44:34 semiauto hpcups[515382]: common/utils.c 173: Plugin version is not matching Mar 10 16:44:34 semiauto hpcups[515382]: prnt/hpcups/HPCupsFilter.cpp 505: m_Job initialization failed with error = 48 Mar 10 16:44:34 semiauto hpcups[515382]: common/utils.c 244: Invalid Library handler pLibHandler = NULL. Mar 10 16:45:01 semiauto CRON[515541]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Mar 10 16:45:09 semiauto gnome-shell[333439]: Window manager warning: Ping serial 447743079 was reused for window W713, previous use was for window 0xc00014. Mar 10 16:45:20 semiauto systemd[4596]: vte-spawn-4d0c2df5-8c91-461c-ac5d-b95a2bc252a9.scope: Consumed 33.860s CPU time. Mar 10 16:45:20 semiauto gnome-shell[333439]: JS ERROR: TypeError: this.actor is null#012_syncEnabled@resource:///org/gnome/shell/ui/windowManager.js:138:25#012onStopped@resource:///org/gnome/shell/ui/windowManager.js:150:35#012_makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:150:22#012_easeActorProperty/<@resource:///org/gnome/shell/ui/environment.js:316:60#012_destroyWindowDone@resource:///org/gnome/shell/ui/windowManager.js:1596:21#012onStopped@resource:///org/gnome/shell/ui/windowManager.js:1564:39#012_makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:150:22#012_easeActor/<@resource:///org/gnome/shell/ui/environment.js:239:64 Mar 10 16:45:23 semiauto dbus-daemon[680]: [system] Activating service name='org.opensuse.CupsPkHelper.Mechanism' requested by ':1.1929' (uid=1000 pid=485631 comm="gnome-control-center printers" label="unconfined") (using servicehelper) Mar 10 16:45:23 semiauto systemd[4596]: app-gnome-virtualbox-495654.scope: Consumed 11min 33.878s CPU time. Mar 10 16:45:23 semiauto dbus-daemon[680]: [system] Successfully activated service 'org.opensuse.CupsPkHelper.Mechanism' Mar 10 16:45:57 semiauto dbus-daemon[332938]: [session uid=1000 pid=332938] Activating service name='org.gnome.Settings.SearchProvider' requested by ':1.23' (uid=1000 pid=333439 comm="/usr/bin/gnome-shell" label="unconfined") Mar 10 16:45:57 semiauto dbus-daemon[332938]: [session uid=1000 pid=332938] Activating service name='org.gnome.Calculator.SearchProvider' requested by ':1.23' (uid=1000 pid=333439 comm="/usr/bin/gnome-shell" label="unconfined") Mar 10 16:45:57 semiauto dbus-daemon[332938]: [session uid=1000 pid=332938] Activating service name='org.gnome.Characters' requested by ':1.23' (uid=1000 pid=333439 comm="/usr/bin/gnome-shell" label="unconfined") Mar 10 16:45:57 semiauto dbus-daemon[332938]: [session uid=1000 pid=332938] Activating service name='org.gnome.Notes.SearchProvider' requested by ':1.23' (uid=1000 pid=333439 comm="/usr/bin/gnome-shell" label="unconfined") Mar 10 16:45:57 semiauto dbus-daemon[332938]: [session uid=1000 pid=332938] Successfully activated service 'org.gnome.Settings.SearchProvider' Make and model auto-reported is: "HP LaserJet Professional m1217nfw MFP, hpcups 3.22.6, requires proprietary plugin" yes, it has commas. URI is reported as: dnssd://HP%20LaserJet%20Professional%20M1217nfw%20MFP._pdl-datastream._tcp.local/ and "location" is aparrently blank. I can troubleshoot further. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg
[Desktop-packages] [Bug 2011279] [NEW] xorg
Public bug reported: 桌面标不显示，右键菜单加载不完整 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Mar 11 07:57:08 2023 DistUpgraded: 2022-11-12 11:37:26,280 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu DkmsStatus: nvidia/525.85.05, 6.1.0-16-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22ca] Subsystem: Lenovo TU117M [GeForce MX450] [17aa:22ca] InstallationDate: Installed on 2022-01-02 (432 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211105) MachineType: LENOVO 20W0005VCD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-16-generic root=UUID=b4c00f4f-589b-42e2-b402-7ea8b75191a7 ro quiet splash systemd.unified_cgroup_hierarchy=0 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2022-11-12 (118 days ago) dmi.bios.date: 11/21/2022 dmi.bios.release: 1.54 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET54W (1.54 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W0005VCD dmi.board.vendor: LENOVO dmi.board.version: SDK0L77769 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.42 dmi.modalias: dmi:bvnLENOVO:bvrN34ET54W(1.54):bd11/21/2022:br1.54:efr1.42:svnLENOVO:pn20W0005VCD:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W0005VCD:rvrSDK0L77769WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20W0_BU_Think_FM_ThinkPadT14Gen2i: dmi.product.family: ThinkPad T14 Gen 2i dmi.product.name: 20W0005VCD dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i dmi.product.version: ThinkPad T14 Gen 2i dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.3.6-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar possible-manual-nvidia-install reproducible single-occurrence ubuntu wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2011279 Title: xorg Status in xorg package in Ubuntu: New Bug description: 桌面标不显示，右键菜单加载不完整 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Mar 11 07:57:08 2023 DistUpgraded: 2022-11-12 11:37:26,280 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu DkmsStatus: nvidia/525.85.05, 6.1.0-16-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22ca] Subsystem: Lenovo TU117M [GeForce MX450] [17aa:22ca] InstallationDate: Installed on 2022-01-02 (432 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211105) MachineType: LENOVO 20W0005VCD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-16-generic root=UUID=b4c00f4f-589b-42e2-b402-7ea8b75191a7 ro quiet splash systemd.unified_cgroup_hierarchy=0 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2022-11-12 (118 days ago) dmi.bios.date: 11/21/2022 dmi.bios.release: 1.54 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET54W (1.54 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W0005VCD dmi.board.vendor: LENOVO dmi.board.version: SDK0L77769 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO
[Desktop-packages] [Bug 2009279] Re: Sometimes it just don't open anymore
Thank you for your report! However, processing it in order to get sufficient information for the developers failed as the report has a core dump which is invalid. The corruption may have happened on the system which the crash occurred or during transit. Thank you for your understanding, and sorry for the inconvenience! ** Changed in: gnome-disk-utility (Ubuntu) Status: New => Invalid ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/2009279/+attachment/5651682/+files/CoreDump.gz -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/2009279 Title: Sometimes it just don't open anymore Status in gnome-disk-utility package in Ubuntu: Invalid Bug description: I need help to maker this problem reproducible. ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-disk-utility 44~beta-0ubuntu1 Uname: Linux 6.1.0-16-generic x86_64 Architecture: amd64 CrashCounter: 1 CurrentDesktop: X-Cinnamon Date: Sat Mar 4 18:21:11 2023 ExecutablePath: /usr/bin/gnome-disks ExecutableTimestamp: 1676054210 ProcCmdline: /usr/bin/gnome-disks --gapplication-service ProcCwd: /home/daniella Signal: 5 SourcePackage: gnome-disk-utility UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/2009279/+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 2011270] [NEW] Printing intermittenly fails -- autodetected network printer
You have been subscribed to a public bug: It appears that print jobs passed to the auto-detected printer "adding" wizard do not always succeed. See in these error messages how hpcups is passed a null object to print. It's unclear what the interactions is between the auto-discovery gnome(?) applet, the hpcups system, and dbus. The net effect is that a print job is sent to the printer defined here, and it just gets stuck in "stopped". With no error message or way for the user to resolve the issue. I'm not sure where to begin debugging ... Error messages in question : Mar 10 16:44:17 semiauto dbus-daemon[680]: [system] Activating service name='org.opensuse.CupsPkHelper.Mechanism' requested by ':1.1929' (uid=1000 pid=485631 comm="gnome-control-center printers" label="unconfined") (using servicehelper) Mar 10 16:44:17 semiauto dbus-daemon[680]: [system] Successfully activated service 'org.opensuse.CupsPkHelper.Mechanism' Mar 10 16:44:25 semiauto google-chrome.desktop[496973]: Warning: disabling flag --expose_wasm due to conflicting flags Mar 10 16:44:34 semiauto hpcups[515382]: common/utils.c 79: unable to open /var/lib/hp/hplip.state: No such file or directory Mar 10 16:44:34 semiauto hpcups[515382]: common/utils.c 129: validate_plugin_version() Failed to get Plugin version from [/var/lib/hp/hplip.state] Mar 10 16:44:34 semiauto hpcups[515382]: common/utils.c 173: Plugin version is not matching Mar 10 16:44:34 semiauto hpcups[515382]: prnt/hpcups/HPCupsFilter.cpp 505: m_Job initialization failed with error = 48 Mar 10 16:44:34 semiauto hpcups[515382]: common/utils.c 244: Invalid Library handler pLibHandler = NULL. Mar 10 16:45:01 semiauto CRON[515541]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Mar 10 16:45:09 semiauto gnome-shell[333439]: Window manager warning: Ping serial 447743079 was reused for window W713, previous use was for window 0xc00014. Mar 10 16:45:20 semiauto systemd[4596]: vte-spawn-4d0c2df5-8c91-461c-ac5d-b95a2bc252a9.scope: Consumed 33.860s CPU time. Mar 10 16:45:20 semiauto gnome-shell[333439]: JS ERROR: TypeError: this.actor is null#012_syncEnabled@resource:///org/gnome/shell/ui/windowManager.js:138:25#012onStopped@resource:///org/gnome/shell/ui/windowManager.js:150:35#012_makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:150:22#012_easeActorProperty/<@resource:///org/gnome/shell/ui/environment.js:316:60#012_destroyWindowDone@resource:///org/gnome/shell/ui/windowManager.js:1596:21#012onStopped@resource:///org/gnome/shell/ui/windowManager.js:1564:39#012_makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:150:22#012_easeActor/<@resource:///org/gnome/shell/ui/environment.js:239:64 Mar 10 16:45:23 semiauto dbus-daemon[680]: [system] Activating service name='org.opensuse.CupsPkHelper.Mechanism' requested by ':1.1929' (uid=1000 pid=485631 comm="gnome-control-center printers" label="unconfined") (using servicehelper) Mar 10 16:45:23 semiauto systemd[4596]: app-gnome-virtualbox-495654.scope: Consumed 11min 33.878s CPU time. Mar 10 16:45:23 semiauto dbus-daemon[680]: [system] Successfully activated service 'org.opensuse.CupsPkHelper.Mechanism' Mar 10 16:45:57 semiauto dbus-daemon[332938]: [session uid=1000 pid=332938] Activating service name='org.gnome.Settings.SearchProvider' requested by ':1.23' (uid=1000 pid=333439 comm="/usr/bin/gnome-shell" label="unconfined") Mar 10 16:45:57 semiauto dbus-daemon[332938]: [session uid=1000 pid=332938] Activating service name='org.gnome.Calculator.SearchProvider' requested by ':1.23' (uid=1000 pid=333439 comm="/usr/bin/gnome-shell" label="unconfined") Mar 10 16:45:57 semiauto dbus-daemon[332938]: [session uid=1000 pid=332938] Activating service name='org.gnome.Characters' requested by ':1.23' (uid=1000 pid=333439 comm="/usr/bin/gnome-shell" label="unconfined") Mar 10 16:45:57 semiauto dbus-daemon[332938]: [session uid=1000 pid=332938] Activating service name='org.gnome.Notes.SearchProvider' requested by ':1.23' (uid=1000 pid=333439 comm="/usr/bin/gnome-shell" label="unconfined") Mar 10 16:45:57 semiauto dbus-daemon[332938]: [session uid=1000 pid=332938] Successfully activated service 'org.gnome.Settings.SearchProvider' Make and model auto-reported is: "HP LaserJet Professional m1217nfw MFP, hpcups 3.22.6, requires proprietary plugin" yes, it has commas. URI is reported as: dnssd://HP%20LaserJet%20Professional%20M1217nfw%20MFP._pdl-datastream._tcp.local/ and "location" is aparrently blank. I can troubleshoot further. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop:
[Desktop-packages] [Bug 1935070] Please test proposed package
Hello Jeff, or anyone else affected, Accepted ubuntu-drivers-common into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-drivers- common/1:0.9.6.2~0.22.04.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1935070 Title: Traceback during 'ubuntu-drivers list' Status in Ubuntu Drivers Common: New Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Status in ubuntu-drivers-common source package in Kinetic: Fix Committed Bug description: [ Impact ] * Calling the ubuntu-drivers tool where the alsa-utils package is not installed (mainly on servers), ubuntu-drivers (through the sl-modem plugin) complains, unnecessarily about the missing aplay binary. [ Test Plan ] * Install the new ubuntu-drivers-common from -proposed, and make sure that alsa-utils is not installed. * Run the ubuntu-drivers list command. * Check that ubuntu-drivers does not complain about the missing aplay tool. [ Where problems could occur ] * A problem in the ubuntu-drivers tool can cause it to install a driver which is not recommended for the detected hardware, or even cause the package installation to fail, and prevent users from logging in through the graphics interface. [ Other Info ] - ___ ubuntu@doubletusk:~$ sudo ubuntu-drivers list ERROR:root:could not open aplay -l Traceback (most recent call last): File "/usr/share/ubuntu-drivers-common/detect/sl-modem.py", line 35, in detect aplay = subprocess.Popen( File "/usr/lib/python3.8/subprocess.py", line 858, in __init__ self._execute_child(args, executable, preexec_fn, close_fds, File "/usr/lib/python3.8/subprocess.py", line 1704, in _execute_child raise child_exception_type(errno_num, err_msg, err_filename) FileNotFoundError: [Errno 2] No such file or directory: 'aplay' nvidia-driver-418-server, (kernel modules provided by nvidia-dkms-418-server) nvidia-driver-470, (kernel modules provided by nvidia-dkms-470) nvidia-driver-460-server, (kernel modules provided by nvidia-dkms-460-server) nvidia-driver-465, (kernel modules provided by nvidia-dkms-465) nvidia-driver-450-server, (kernel modules provided by nvidia-dkms-450-server) nvidia-driver-460, (kernel modules provided by nvidia-dkms-460) ubuntu@doubletusk:~$ apt-cache policy ubuntu-drivers-common ubuntu-drivers-common: Installed: 1:0.9.0~0.20.04.1 Candidate: 1:0.9.0~0.20.04.1 Version table: *** 1:0.9.0~0.20.04.1 500 500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1:0.8.6.5~0.20.04.1 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 1:0.8.1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages ubuntu@doubletusk:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS Release:20.04 Codename: focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-drivers-common/+bug/1935070/+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 1935070] Please test proposed package
Hello Jeff, or anyone else affected, Accepted ubuntu-drivers-common into kinetic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-drivers-common/1:0.9.6.3.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- kinetic to verification-done-kinetic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-kinetic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1935070 Title: Traceback during 'ubuntu-drivers list' Status in Ubuntu Drivers Common: New Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Status in ubuntu-drivers-common source package in Kinetic: Fix Committed Bug description: [ Impact ] * Calling the ubuntu-drivers tool where the alsa-utils package is not installed (mainly on servers), ubuntu-drivers (through the sl-modem plugin) complains, unnecessarily about the missing aplay binary. [ Test Plan ] * Install the new ubuntu-drivers-common from -proposed, and make sure that alsa-utils is not installed. * Run the ubuntu-drivers list command. * Check that ubuntu-drivers does not complain about the missing aplay tool. [ Where problems could occur ] * A problem in the ubuntu-drivers tool can cause it to install a driver which is not recommended for the detected hardware, or even cause the package installation to fail, and prevent users from logging in through the graphics interface. [ Other Info ] - ___ ubuntu@doubletusk:~$ sudo ubuntu-drivers list ERROR:root:could not open aplay -l Traceback (most recent call last): File "/usr/share/ubuntu-drivers-common/detect/sl-modem.py", line 35, in detect aplay = subprocess.Popen( File "/usr/lib/python3.8/subprocess.py", line 858, in __init__ self._execute_child(args, executable, preexec_fn, close_fds, File "/usr/lib/python3.8/subprocess.py", line 1704, in _execute_child raise child_exception_type(errno_num, err_msg, err_filename) FileNotFoundError: [Errno 2] No such file or directory: 'aplay' nvidia-driver-418-server, (kernel modules provided by nvidia-dkms-418-server) nvidia-driver-470, (kernel modules provided by nvidia-dkms-470) nvidia-driver-460-server, (kernel modules provided by nvidia-dkms-460-server) nvidia-driver-465, (kernel modules provided by nvidia-dkms-465) nvidia-driver-450-server, (kernel modules provided by nvidia-dkms-450-server) nvidia-driver-460, (kernel modules provided by nvidia-dkms-460) ubuntu@doubletusk:~$ apt-cache policy ubuntu-drivers-common ubuntu-drivers-common: Installed: 1:0.9.0~0.20.04.1 Candidate: 1:0.9.0~0.20.04.1 Version table: *** 1:0.9.0~0.20.04.1 500 500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1:0.8.6.5~0.20.04.1 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 1:0.8.1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages ubuntu@doubletusk:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS Release:20.04 Codename: focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-drivers-common/+bug/1935070/+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 1993019] Please test proposed package
Hello Seth, or anyone else affected, Accepted ubuntu-drivers-common into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-drivers- common/1:0.9.6.2~0.22.04.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1993019 Title: UnboundLocalError: local variable 'version' referenced before assignment Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Bionic: Triaged Status in ubuntu-drivers-common source package in Focal: Triaged Status in ubuntu-drivers-common source package in Jammy: Fix Committed Status in ubuntu-drivers-common source package in Kinetic: Fix Committed Bug description: [ Impact ] * The introduction of the -open NVIDIA drivers requires a change in the way we detect driver series and flavours. Failing to do so, causes the ubuntu-drivers tool to crash (LP: #1993019), or to prefer the -open drivers over the non-open ones (LP: #1988836). * Furthermore, calling the ubuntu-drivers tool where the alsa-utils package is not installed (mainly on servers), ubuntu-drivers (through the sl-modem plugin) complains, unnecessarily about the missing aplay binary. [ Test Plan ] * Install the new ubuntu-drivers-common from -proposed on a system where the GPU is compatible with the 515 series (or higher). * Run the ubuntu-drivers list command, and make sure that the 515 driver series (or higher) is listed. * Try installing the driver using the following command: sudo ubuntu-drivers install * Check which driver series was installed (you can use the "sudo ubuntu-drivers debug" command), and make sure that the installation does not cause ubuntu-drivers to crash. [ Where problems could occur ] * A problem in the ubuntu-drivers tool can cause it to install a driver which is not recommended for the detected hardware, or even cause the package installation to fail, and prevent users from logging in through the graphics interface. [ Other Info ] * To prevent failures of the test-suite on architectures such as armhf (as seen in Lunar), we are skipping the tests for any architectures other than amd64 and arm64 (which are the only ones actually using ubuntu-drivers). This was already the case with riscv, and we now have an easier way to do so in the debian/rules file. == Changelogs == === Kinetic and Jammy === [ Alberto Milone ] * New upstream release: * UbuntuDrivers/detect.py: - Make sure all -open drivers have a lower priority, regardless of whether the --server parameter is passed in or not. - Update regex in nvidia_desktop_pre_installation_hook. This prevents ubuntu-drivers from crashing when dealing with the -open NVIDIA drivers (LP: #1993019). * tests/test_ubuntu_drivers.py: - Add tests so we make sure to keep preferring non-open NVIDIA modules over the -open ones, at least until the open modules catch up feature wise and performance wise. [ gongzhengyang ] * UbuntuDrivers/detect.py: - Fix local variable 'version' being referenced before assignment when catching ValueError (LP: #1993019). [ Jeff Lane ] * detect-plugins/sl-modem.py: - Add some error trapping when aplay is not installed (on servers). === Jammy only (left over from 1:0.9.6.2~0.22.04.1) === * UbuntuDrivers/detect.py: - Make sure -open drivers have a lower priority (LP: #1988836). == Changelogs == === Kinetic and Jammy === [ Alberto Milone ] * debian/rules: - Limit the tests to the selected architectures (amd64, arm64). This prevents armhf builds from failing. *
[Desktop-packages] [Bug 1993019] Please test proposed package
Hello Seth, or anyone else affected, Accepted ubuntu-drivers-common into kinetic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-drivers-common/1:0.9.6.3.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- kinetic to verification-done-kinetic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-kinetic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1993019 Title: UnboundLocalError: local variable 'version' referenced before assignment Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Bionic: Triaged Status in ubuntu-drivers-common source package in Focal: Triaged Status in ubuntu-drivers-common source package in Jammy: Fix Committed Status in ubuntu-drivers-common source package in Kinetic: Fix Committed Bug description: [ Impact ] * The introduction of the -open NVIDIA drivers requires a change in the way we detect driver series and flavours. Failing to do so, causes the ubuntu-drivers tool to crash (LP: #1993019), or to prefer the -open drivers over the non-open ones (LP: #1988836). * Furthermore, calling the ubuntu-drivers tool where the alsa-utils package is not installed (mainly on servers), ubuntu-drivers (through the sl-modem plugin) complains, unnecessarily about the missing aplay binary. [ Test Plan ] * Install the new ubuntu-drivers-common from -proposed on a system where the GPU is compatible with the 515 series (or higher). * Run the ubuntu-drivers list command, and make sure that the 515 driver series (or higher) is listed. * Try installing the driver using the following command: sudo ubuntu-drivers install * Check which driver series was installed (you can use the "sudo ubuntu-drivers debug" command), and make sure that the installation does not cause ubuntu-drivers to crash. [ Where problems could occur ] * A problem in the ubuntu-drivers tool can cause it to install a driver which is not recommended for the detected hardware, or even cause the package installation to fail, and prevent users from logging in through the graphics interface. [ Other Info ] * To prevent failures of the test-suite on architectures such as armhf (as seen in Lunar), we are skipping the tests for any architectures other than amd64 and arm64 (which are the only ones actually using ubuntu-drivers). This was already the case with riscv, and we now have an easier way to do so in the debian/rules file. == Changelogs == === Kinetic and Jammy === [ Alberto Milone ] * New upstream release: * UbuntuDrivers/detect.py: - Make sure all -open drivers have a lower priority, regardless of whether the --server parameter is passed in or not. - Update regex in nvidia_desktop_pre_installation_hook. This prevents ubuntu-drivers from crashing when dealing with the -open NVIDIA drivers (LP: #1993019). * tests/test_ubuntu_drivers.py: - Add tests so we make sure to keep preferring non-open NVIDIA modules over the -open ones, at least until the open modules catch up feature wise and performance wise. [ gongzhengyang ] * UbuntuDrivers/detect.py: - Fix local variable 'version' being referenced before assignment when catching ValueError (LP: #1993019). [ Jeff Lane ] * detect-plugins/sl-modem.py: - Add some error trapping when aplay is not installed (on servers). === Jammy only (left over from 1:0.9.6.2~0.22.04.1) === * UbuntuDrivers/detect.py: - Make sure -open drivers have a lower priority (LP: #1988836). == Changelogs == === Kinetic and Jammy === [ Alberto Milone ] * debian/rules: - Limit the tests to the selected architectures (amd64, arm64). This prevents armhf builds from failing. *
[Desktop-packages] [Bug 2008433] Re: Request to enable WidevineCDM checking on ARM64
I can confirm the be build from the ppa works on arm64. Thank you! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2008433 Title: Request to enable WidevineCDM checking on ARM64 Status in chromium-browser package in Ubuntu: Fix Committed Status in chromium-browser source package in Bionic: Fix Committed Bug description: If possible, could you please include a patch to enable widevinecdm checking on ARM64 linux? currently BUNDLE_WIDEVINE_CDM does not get set for arm64 linux (but does on amd64 linux) so chromium does not even check for widevine even if we have it available and placed in the directory manually. I am currently using the attached patch of my making when testing locally to correct this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2008433/+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 861493] Re: evince doesn't print duplex on duplex-able printers
Still an issue on the current LTS (jammy, 22.04), and the current devel series (lunar, 23.04) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/861493 Title: evince doesn't print duplex on duplex-able printers Status in evince package in Ubuntu: Confirmed Bug description: I have a postscript-printer, which can print on both sides of the paper (duplex). When I print a file with "lpr -Pduplex file.pdf", everything is o.k., when I do that in evince (selecting printer duplex), it prints every page on a single sheet, so it acts not the same as lpr does. This happens with Ubuntu 10.04.3. evince is in 2.30.3-0ubuntu1.2. Greetings, Leander Jedamus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/861493/+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 2011271] Re: gdm3: "Oh no! Something has gone wrong."
When trying to start via sddm the logon screen is shown but when
entering Gnome the same crash occurs and the "Oh no! Something has gone
wrong." message appears.
** Package changed: gdm3 (Ubuntu) => gnome-shell (Ubuntu)
--
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/2011271
Title:
gdm3: "Oh no! Something has gone wrong."
Status in gnome-shell package in Ubuntu:
New
Bug description:
I have installed ubuntu-desktop on Ubuntu Lunar using a RISCV system
with Nvidia GT 710 as well as on a system with a Radeon 8450. In both
cases gdm3 does not show a dialog but a message "Oh no! Something has
gone wrong." Kinetic and Jammy work fine.
ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: gdm3 43.0-3ubuntu2
ProcVersionSignature: Ubuntu 5.19.0-1013.14-generic 5.19.17
Uname: Linux 5.19.0-1013-generic riscv64
ApportVersion: 2.26.0-0ubuntu2
Architecture: riscv64
CasperMD5json:
{
"result": "skip"
}
Date: Fri Mar 10 21:53:33 2023
InstallationDate: Installed on 2023-02-22 (16 days ago)
InstallationMedia: Ubuntu-Server 22.04.2 LTS "Jammy Jellyfish" - Release
riscv64 (20230221)
ProcCpuinfoMinimal:
processor: 3
hart : 3
isa : rv64imafdc
mmu : sv39
uarch: sifive,u74-mc
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=vt220
SourcePackage: gdm3
UpgradeStatus: Upgraded to lunar on 2023-03-10 (0 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2011271/+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 2011272] Re: Crash lors du branchement d'un périphérique Bluetooth
*** This bug is a duplicate of bug 2006500 *** https://bugs.launchpad.net/bugs/2006500 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #2006500, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/2011272/+attachment/5653665/+files/CoreDump.gz ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/2011272/+attachment/5653667/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/2011272/+attachment/5653668/+files/ProcStatus.txt ** This bug has been marked a duplicate of private bug 2006500 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2011272 Title: Crash lors du branchement d'un périphérique Bluetooth Status in gnome-control-center package in Ubuntu: New Bug description: Périphérique bluetooth non reconnu ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-control-center 1:44~alpha-0ubuntu1 Uname: Linux 6.1.0-16-generic x86_64 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 10 16:56:53 2023 ExecutablePath: /usr/bin/gnome-control-center ExecutableTimestamp: 1673628537 ProcCmdline: /usr/bin/gnome-control-center ProcCwd: /home/emmanuel ProcEnviron: LANG=fr_CA.UTF-8 LANGUAGE=fr_CA:fr PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 11 SourcePackage: gnome-control-center UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2011272/+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 2011271] [NEW] gdm3: "Oh no! Something has gone wrong."
Public bug reported:
I have installed ubuntu-desktop on Ubuntu Lunar using a RISCV system
with Nvidia GT 710 as well as on a system with a Radeon 8450. In both
cases gdm3 does not show a dialog but a message "Oh no! Something has
gone wrong." Kinetic and Jammy work fine.
ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: gdm3 43.0-3ubuntu2
ProcVersionSignature: Ubuntu 5.19.0-1013.14-generic 5.19.17
Uname: Linux 5.19.0-1013-generic riscv64
ApportVersion: 2.26.0-0ubuntu2
Architecture: riscv64
CasperMD5json:
{
"result": "skip"
}
Date: Fri Mar 10 21:53:33 2023
InstallationDate: Installed on 2023-02-22 (16 days ago)
InstallationMedia: Ubuntu-Server 22.04.2 LTS "Jammy Jellyfish" - Release
riscv64 (20230221)
ProcCpuinfoMinimal:
processor : 3
hart : 3
isa: rv64imafdc
mmu: sv39
uarch : sifive,u74-mc
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=vt220
SourcePackage: gdm3
UpgradeStatus: Upgraded to lunar on 2023-03-10 (0 days ago)
** Affects: gdm3 (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug lunar riscv64
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/2011271
Title:
gdm3: "Oh no! Something has gone wrong."
Status in gdm3 package in Ubuntu:
New
Bug description:
I have installed ubuntu-desktop on Ubuntu Lunar using a RISCV system
with Nvidia GT 710 as well as on a system with a Radeon 8450. In both
cases gdm3 does not show a dialog but a message "Oh no! Something has
gone wrong." Kinetic and Jammy work fine.
ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: gdm3 43.0-3ubuntu2
ProcVersionSignature: Ubuntu 5.19.0-1013.14-generic 5.19.17
Uname: Linux 5.19.0-1013-generic riscv64
ApportVersion: 2.26.0-0ubuntu2
Architecture: riscv64
CasperMD5json:
{
"result": "skip"
}
Date: Fri Mar 10 21:53:33 2023
InstallationDate: Installed on 2023-02-22 (16 days ago)
InstallationMedia: Ubuntu-Server 22.04.2 LTS "Jammy Jellyfish" - Release
riscv64 (20230221)
ProcCpuinfoMinimal:
processor: 3
hart : 3
isa : rv64imafdc
mmu : sv39
uarch: sifive,u74-mc
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=vt220
SourcePackage: gdm3
UpgradeStatus: Upgraded to lunar on 2023-03-10 (0 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2011271/+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 2011257] [NEW] Latest gnome-shell hanging regularly
Public bug reported: In the short time I've had the newest GNOME updates for Lunar, my gnome- shell has hung twice. The first time I had just logged into a Google account in Chrome, and it popped up the window asking me if I wanted to switch to a new Chrome profile rather than logging into that account in the same profile, and I clicked the yes button to do that, and then my screen simply hang and refused to do anything for about 30-45 seconds, after which it unhung. The mouse pointer moved during the hang but nothing else. The second time I attempted to open an external drive that was mounted by clicking on its icon in the dock, and the open animation appeared but the folder didn't open. I clicked again and the open animation appeared again but again the folder did not open. At this point everything hung-- once again, mouse cursor moved but nothing else would happen no matter what I typed or clicked. Waiting this one out didn't work; I had to SSH into the machine from another bo and kill -9 the gnome-shell process to escape. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44~beta-1ubuntu1 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Mar 10 16:20:01 2023 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-16 (1302 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 44~beta-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2022-11-24 (106 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar wayland-session -- 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/2011257 Title: Latest gnome-shell hanging regularly Status in gnome-shell package in Ubuntu: New Bug description: In the short time I've had the newest GNOME updates for Lunar, my gnome-shell has hung twice. The first time I had just logged into a Google account in Chrome, and it popped up the window asking me if I wanted to switch to a new Chrome profile rather than logging into that account in the same profile, and I clicked the yes button to do that, and then my screen simply hang and refused to do anything for about 30-45 seconds, after which it unhung. The mouse pointer moved during the hang but nothing else. The second time I attempted to open an external drive that was mounted by clicking on its icon in the dock, and the open animation appeared but the folder didn't open. I clicked again and the open animation appeared again but again the folder did not open. At this point everything hung--once again, mouse cursor moved but nothing else would happen no matter what I typed or clicked. Waiting this one out didn't work; I had to SSH into the machine from another bo and kill -9 the gnome-shell process to escape. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44~beta-1ubuntu1 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Mar 10 16:20:01 2023 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-16 (1302 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 44~beta-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2022-11-24 (106 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2011257/+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 2011251] [NEW] gnome-shell gets into state where clicking on window title bars doesn't raise them
Public bug reported: After the most recent Lunar updates (i.e., with the newest GNOME) my gnome-shell got into a state where clicking on the title bar of a window wouldn't raise the window (or do anything else), while clicking inside the window raised it as expected. The problem went away after I rebooted. I think this may have occurred after some other aberrant behavior, specifically the shell hanging for about 30 seconds (I will file a separate bug about that), so it's possible that things were in some sort of broken state because of that and this bug isn't actually specifically about the title bar, but I thought I should file a bug report about it just in case it's something other people start seeing so we can see how frequently it's happening. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44~beta-1ubuntu1 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Mar 10 16:16:22 2023 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-16 (1302 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 44~beta-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2022-11-24 (106 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar wayland-session -- 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/2011251 Title: gnome-shell gets into state where clicking on window title bars doesn't raise them Status in gnome-shell package in Ubuntu: New Bug description: After the most recent Lunar updates (i.e., with the newest GNOME) my gnome-shell got into a state where clicking on the title bar of a window wouldn't raise the window (or do anything else), while clicking inside the window raised it as expected. The problem went away after I rebooted. I think this may have occurred after some other aberrant behavior, specifically the shell hanging for about 30 seconds (I will file a separate bug about that), so it's possible that things were in some sort of broken state because of that and this bug isn't actually specifically about the title bar, but I thought I should file a bug report about it just in case it's something other people start seeing so we can see how frequently it's happening. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44~beta-1ubuntu1 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Mar 10 16:16:22 2023 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-16 (1302 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 44~beta-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2022-11-24 (106 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2011251/+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 1988836] Autopkgtest regression report (linux-restricted-modules-aws/5.15.0-1032.36)
All autopkgtests for the newly accepted linux-restricted-modules-aws (5.15.0-1032.36) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-restricted-modules-aws [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: Fix Released Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+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 1990861] Re: can no longer click on speaker icon in system tray menu to mute/unmute
This appears to be fixed in current Lunar. -- 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/1990861 Title: can no longer click on speaker icon in system tray menu to mute/unmute Status in gnome-shell package in Ubuntu: Triaged Bug description: In Jammy, if I opened the system menu (click on system tray in top right corner of screen) and clicked the little speaker icon it would mute my audio, and then if I clicked again it would unmute. That icon is no longer clickable in Kinetic. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 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: ubuntu:GNOME Date: Mon Sep 26 11:39:09 2022 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-16 (1136 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 43.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2022-09-24 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1990861/+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 2009918] Re: package libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1 failed to install/upgrade: impossible de créer un lien symbolique de secours de « ./usr/lib/x86_64-linux-gnu/dri/
** Changed in: mesa (Ubuntu)
Status: Incomplete => New
--
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/2009918
Title:
package libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1 failed to
install/upgrade: impossible de créer un lien symbolique de secours de
« ./usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so » avant d'installer une
nouvelle version: Aucun espace disponible sur le périphérique
Status in mesa package in Ubuntu:
New
Bug description:
Running inside a VM (KVM) from a remastered ISO
The screen also show some artifacts horizontal dotted lines which disappear
after a second or two.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1
ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-30-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5json: {
CasperVersion: 1.445.1
CompositorRunning: None
Date: Fri Mar 10 08:21:08 2023
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ErrorMessage: impossible de créer un lien symbolique de secours de «
./usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so » avant d'installer une nouvelle
version: Aucun espace disponible sur le périphérique
ExtraDebuggingInterest: No
GraphicsCard:
Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 04) (prog-if 00
[VGA controller])
Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
InstallationDate: Installed on 2022-02-22 (380 days ago)
InstallationMedia:
LiveMediaBuild: Systemback Live (MobiOffice) - Release amd64
Lsusb:
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t:
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid,
480M
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz boot=casper
initrd=/casper/initrd.gz quiet splash
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal,
3.8.2-0ubuntu2
PythonDetails: N/A
SourcePackage: mesa
Title: package libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1 failed to
install/upgrade: impossible de créer un lien symbolique de secours de «
./usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so » avant d'installer une nouvelle
version: Aucun espace disponible sur le périphérique
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.release: 0.0
dmi.bios.vendor: SeaBIOS
dmi.bios.version: 1.13.0-1ubuntu1.1
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-focal
dmi.modalias:
dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-focal:cvnQEMU:ct1:cvrpc-i440fx-focal:sku:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-focal
dmi.sys.vendor: QEMU
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2009918/+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 2009918] Re: package libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1 failed to install/upgrade: impossible de créer un lien symbolique de secours de « ./usr/lib/x86_64-linux-gnu/dri/
Indeed that's the French translation of "No space left on the device".
As I explained in the comments, I have remastered an ISO (of 20.04) to
connect to my professional workspace (VPN Cisco AnyConnect and Citrix),
because I don't want those 2 closed source things to mess up with my
environment.
I am using that ISO inside a VM, via KVM/QEMU.
So the "bug" would be that mesa would try to install anything. That
obviously could fail considering the ISO runs in AUFS mode, and the
operation on system file is somehow restricted even more due to the
read-only part of the mount.
It does not happen all the times. Sometimes, it works just fine, does
not complain or spit out any error and does not display any artifacts.
Other times, I get the error.
This is anyway very low priority, it is not really a big deal, I just ignore
the errors and artifacts when they happen!
--
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/2009918
Title:
package libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1 failed to
install/upgrade: impossible de créer un lien symbolique de secours de
« ./usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so » avant d'installer une
nouvelle version: Aucun espace disponible sur le périphérique
Status in mesa package in Ubuntu:
Incomplete
Bug description:
Running inside a VM (KVM) from a remastered ISO
The screen also show some artifacts horizontal dotted lines which disappear
after a second or two.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1
ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-30-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5json: {
CasperVersion: 1.445.1
CompositorRunning: None
Date: Fri Mar 10 08:21:08 2023
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ErrorMessage: impossible de créer un lien symbolique de secours de «
./usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so » avant d'installer une nouvelle
version: Aucun espace disponible sur le périphérique
ExtraDebuggingInterest: No
GraphicsCard:
Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 04) (prog-if 00
[VGA controller])
Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
InstallationDate: Installed on 2022-02-22 (380 days ago)
InstallationMedia:
LiveMediaBuild: Systemback Live (MobiOffice) - Release amd64
Lsusb:
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t:
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid,
480M
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz boot=casper
initrd=/casper/initrd.gz quiet splash
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal,
3.8.2-0ubuntu2
PythonDetails: N/A
SourcePackage: mesa
Title: package libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1 failed to
install/upgrade: impossible de créer un lien symbolique de secours de «
./usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so » avant d'installer une nouvelle
version: Aucun espace disponible sur le périphérique
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.release: 0.0
dmi.bios.vendor: SeaBIOS
dmi.bios.version: 1.13.0-1ubuntu1.1
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-focal
dmi.modalias:
dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-focal:cvnQEMU:ct1:cvrpc-i440fx-focal:sku:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-focal
dmi.sys.vendor: QEMU
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
To manage notifications about this bug go to:
[Desktop-packages] [Bug 2006641] Re: hwacc branches fail to build
For 113, guide-0.9.1:a49acb3:one-copy.diff fails to apply. ** Tags removed: dev-ok ** Tags added: dev-failed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2006641 Title: hwacc branches fail to build Status in chromium-browser package in Ubuntu: Triaged Bug description: Currently the hwacc branches of snap_from_source fail to build. This is caused by the fact that the guide-0.9.1 patches are against 107 chromium, and no longer apply cleanly. build logs here: Candidate: https://launchpad.net/~chromium-team/+snap/chromium-snap-from-source-hwacc-candidate Beta: https://launchpad.net/~chromium-team/+snap/chromium-snap-from-source-hwacc-beta Dev: https://launchpad.net/~chromium-team/+snap/chromium-snap-from-source-hwacc-dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2006641/+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 2008433] Re: Request to enable WidevineCDM checking on ARM64
** Also affects: chromium-browser (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: chromium-browser (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2008433 Title: Request to enable WidevineCDM checking on ARM64 Status in chromium-browser package in Ubuntu: Fix Committed Status in chromium-browser source package in Bionic: Fix Committed Bug description: If possible, could you please include a patch to enable widevinecdm checking on ARM64 linux? currently BUNDLE_WIDEVINE_CDM does not get set for arm64 linux (but does on amd64 linux) so chromium does not even check for widevine even if we have it available and placed in the directory manually. I am currently using the attached patch of my making when testing locally to correct this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2008433/+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 2009918] Re: package libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1 failed to install/upgrade: impossible de créer un lien symbolique de secours de « ./usr/lib/x86_64-linux-gnu/dri/
Aucun espace disponible sur le périphérique
->
No space left on the device
So it looks you are low in free space on disk, is that correct?
** Changed in: mesa (Ubuntu)
Status: New => Incomplete
--
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/2009918
Title:
package libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1 failed to
install/upgrade: impossible de créer un lien symbolique de secours de
« ./usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so » avant d'installer une
nouvelle version: Aucun espace disponible sur le périphérique
Status in mesa package in Ubuntu:
Incomplete
Bug description:
Running inside a VM (KVM) from a remastered ISO
The screen also show some artifacts horizontal dotted lines which disappear
after a second or two.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1
ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-30-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5json: {
CasperVersion: 1.445.1
CompositorRunning: None
Date: Fri Mar 10 08:21:08 2023
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ErrorMessage: impossible de créer un lien symbolique de secours de «
./usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so » avant d'installer une nouvelle
version: Aucun espace disponible sur le périphérique
ExtraDebuggingInterest: No
GraphicsCard:
Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 04) (prog-if 00
[VGA controller])
Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
InstallationDate: Installed on 2022-02-22 (380 days ago)
InstallationMedia:
LiveMediaBuild: Systemback Live (MobiOffice) - Release amd64
Lsusb:
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t:
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid,
480M
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz boot=casper
initrd=/casper/initrd.gz quiet splash
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal,
3.8.2-0ubuntu2
PythonDetails: N/A
SourcePackage: mesa
Title: package libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1 failed to
install/upgrade: impossible de créer un lien symbolique de secours de «
./usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so » avant d'installer une nouvelle
version: Aucun espace disponible sur le périphérique
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.release: 0.0
dmi.bios.vendor: SeaBIOS
dmi.bios.version: 1.13.0-1ubuntu1.1
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-focal
dmi.modalias:
dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-focal:cvnQEMU:ct1:cvrpc-i440fx-focal:sku:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-focal
dmi.sys.vendor: QEMU
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2009918/+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 2004241] Re: Update to glib >= 2.75.1
** Changed in: glib2.0 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2004241 Title: Update to glib >= 2.75.1 Status in glib2.0 package in Ubuntu: Fix Released Bug description: Update to glib >= 2.75.1 because that's what mutter 44 now requires. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2004241/+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 2009944] [NEW] [BPO] libreoffice 7.4.6 for bionic, focal and jammy
Public bug reported: [Impact] * LibreOffice 7.4.6 is in its sixth bugfix release of the 7.4 line: https://wiki.documentfoundation.org/ReleasePlan/7.4#7.4.6_release * This source packages matches the proposed SRU for kinetic handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2009354 and its backport is currently provided by the LibreOffice Still PPA at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+packages * LibreOffice 7.3.7 (EOL since November 30, 2022) is currently released in bionic-/focal-backports [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/1:7.4.6-0ubuntu0.22.10.1 * Backport targets are the Bionic/18.04, Focal/20.04 and Jammy/22.04 LTS releases 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_74/1717/ * 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. Bionic/18.04 build at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+sourcepub/14541804/+listing-archive-extra * [amd64] ... * [arm64] ... * [armhf] ... * [ppc64el] ... * [s390x] ... Focal/20.04 build at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+sourcepub/14541807/+listing-archive-extra * [amd64] ... * [arm64] ... * [armhf] ... * [ppc64el] ... * [s390x] ... Jammy/22.04 build at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+sourcepub/14541810/+listing-archive-extra * [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 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 ** Affects: libreoffice (Ubuntu Focal) Importance: High Assignee: Rico Tzschichholz (ricotz) Status: In Progress ** Affects: libreoffice (Ubuntu Jammy) Importance: High Assignee: Rico Tzschichholz (ricotz) Status: In Progress ** Also affects: libreoffice (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: libreoffice (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: libreoffice (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: libreoffice (Ubuntu Bionic) Importance: Undecided => High ** Changed in: libreoffice (Ubuntu Focal) Importance: Undecided => High ** Changed in: libreoffice (Ubuntu Jammy) Importance: Undecided => High ** Changed in: libreoffice (Ubuntu Bionic) Assignee: (unassigned) => Rico Tzschichholz (ricotz) ** Changed in: libreoffice (Ubuntu Focal) Assignee: (unassigned) => Rico Tzschichholz (ricotz) ** Changed in: libreoffice (Ubuntu Jammy) Assignee: (unassigned) => Rico Tzschichholz (ricotz) ** Changed in: libreoffice (Ubuntu Bionic) Status: New => In Progress ** Changed in: libreoffice (Ubuntu Focal) Status: New => Incomplete ** Changed in: libreoffice (Ubuntu Focal) Status: Incomplete => In Progress ** Changed in: libreoffice (Ubuntu Jammy) Status: New => In Progress ** 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/2009944 Title: [BPO] libreoffice 7.4.6 for bionic, focal and jammy Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Bionic: In Progress Status in libreoffice source package in Focal: In Progress Status in libreoffice source package in Jammy: In Progress Bug description: [Impact] * LibreOffice 7.4.6 is in its sixth bugfix release of
[Desktop-packages] [Bug 1994011] Re: gnome-shell crashed with SIGSEGV in __strlen_avx2() from g_strjoinv() from init_secondary_gpu_data_gpu() from init_secondary_gpu_data() from create_renderer_gpu_da
This bug was fixed in the package mutter - 44~beta-3ubuntu2 --- mutter (44~beta-3ubuntu2) lunar; urgency=medium * debian/patches: Update code to get backend on X11-fractional scaling * debian/control: Do not depend on legacy EGL package name -- Marco Trevisan (Treviño) Thu, 23 Feb 2023 20:03:24 +0100 ** Changed in: mutter (Ubuntu) Status: Fix Committed => Fix Released -- 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/1994011 Title: gnome-shell crashed with SIGSEGV in __strlen_avx2() from g_strjoinv() from init_secondary_gpu_data_gpu() from init_secondary_gpu_data() from create_renderer_gpu_data_gbm() Status in mutter package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 43.0-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/572031ecb97102a47da85c728ab7b98e918bb1bd contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1994011/+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 1998529] Re: Uninstalling extensions dereferences symlinks, risking data loss
This bug was fixed in the package gnome-shell - 44~beta-1ubuntu1 --- gnome-shell (44~beta-1ubuntu1) lunar; urgency=medium [ Jeremy Bicha ] * Merge with Debian, containing new upstream release: - Do not deference symlinks when uninstalling an extension (LP: #1998529) * Remaining changes with debian: - Add some Recommends: + ubuntu-session (| gnome-session) to have the ubuntu session available + ubuntu-wallpapers + xserver-xorg-legacy + yaru-theme-gnome-shell for the default ubuntu theming - Move some Recommends to Suggests: + chrome-gnome-shell + gnome-backgrounds - Update debian/gbp.conf with Ubuntu settings - debian/ubuntu-session-mods/ubuntu.json: Use Yaru's gnome-shell icons - debian/patches: Do not hang & crash if fingerprint service fails to start (LP: #1962566) - ubuntu/desktop_detect.patch: + add caching for desktop detection to avoid querying the current desktop env variable as iterate through the list each time. For the time of the Shell process, we can expect this env variable to stay stable. - ubuntu/lightdm-user-switching.patch: + Allow user switching when using LightDM. - ubuntu/lock_on_suspend.patch + Respect Ubuntu's lock-on-suspend setting. - ubuntu/background_login.patch + Change default background color as we modified the default GDM color for our ubuntu session. - ubuntu/gdm_alternatives.patch + Add support for GDM3 theme alternatives - main-show-an-error-message-on-gnome-shell-crash.patch, global-make-possible-to-set-debug-flags-dynamically.patch, main-increase-the-granularity-of-backtraces-in-SHELL_DEBU.patch, main-add-backtrace-crashes-all-and-backtrace-all.patch, sessionMode-add-support-for-debugFlags-parameter.patch: + Improve debug JS tracing for crash reports - ubuntu/smarter_alt_tab.patch: + quick alt-tab (without showing up the switcher) switch only between the last window of the last 2 applications to be focused instead of raising all windows of those apps. - magnifier-Show-cursor-when-magnifier-is-enabled-and-scale.patch: + Show monitor scaled cursor when magnifier is enabled - ubuntu/search-call-XUbuntuCancel-method-on-providers-when-no-dat.patch: + stop searches when requested from UI - magnifier-Show-cursor-when-magnifier-is-enabled-and-scale.patch - u/search-call-XUbuntuCancel-method-on-providers-when-no-dat.patch - ubuntu/resolve_alternate_theme_path.patch - ubuntu/secure_mode_extension.patch - ubuntu/keep-ubuntu-logo-bright-lp1867133-v1.patch - ubuntu/configure_login_screen.patch - ubuntu/layout-Make-starting-in-the-overview-optional.patch: + Makes dock replace overview easier - ubuntu/layout-Try-to-allocate-before-getting-size-of-tracke.patch: + Ensure windows don't get maximized under the panels / dock - debian/patches: Compute system background color from theme (LP: #1965727) - ubuntu/configure-login-screen.patch: Use bg color for initial system bg (LP: #1965727) - debian/patches: Ensure St.Entry's `selected-color` CSS property is honored (LP: #1878998) - ubuntu/support-loading-Yaru-variants: Handle dark/light variants better - d/p/use-favorites-strings: Only apply this to ubuntu session - debian/patches: Support configuring icons resource to use for mode - Revert-st-Apply-css-foreground-color-to-text-as-a-PangoAt.patch: + Ensure selected-text foreground color is preserved - ubuntu/sessionMode-Add-support-for-configuring-an-icons-resource.patch: + Support loading iconsResourceName from session file - ubuntu/main-Support-loading-multiple-Yaru-theme-variants.patch, - ubuntu/darkMode-Add-support-to-Yaru-theme-color-variants.patch: + Support loading Yaru theme variants (for accent color) - ubuntu/Revert-dash-Use-pin-instead-of-favorites * Rebase patches * Drop main-Avoid-meta-finalize.patch: maybe not needed any more * Fix typo in patch [ Marco Trevisan (Treviño) ] * debian/patches: Ensure GSETTINGS_SCHEMA_DIR is honored in tests * debian/patches/ubuntu: Fix description typos to mute lintian gnome-shell (44~beta-1) experimental; urgency=medium * New upstream release * Drop translation patches: applied in new release * Bump mutter dependency to 44~beta * Update install files * Build-Depend on mutter-12-tests instead of libmutter-test-12 * Build-Depend on gir1.2-nma-1.0 for build tests * Temporarily disable change to make test warnings fail the build gnome-shell (43.3-1) unstable; urgency=medium * Team upload * New upstream release - Don't dereference symlinks when deleting extensions (GNOME/gnome-shell#6182, which can be a data loss bug) - Fix windows disappearing from Alt+Tab if their title changes at just the wrong time (GNOME/gnome-shell#6385) -
[Desktop-packages] [Bug 2007623] Re: Merge grilo-plugins 0.3.15-2 (universe) from Debian unstable (main)
This bug was fixed in the package grilo-plugins - 0.3.15-2ubuntu1 --- grilo-plugins (0.3.15-2ubuntu1) lunar; urgency=medium * Merge from Debian unstable (LP: #2007623). Remaining change: - Split package into -base and -extra (Closes: #805609) grilo-plugins (0.3.15-2) unstable; urgency=medium * debian/control: - Stop recommending dleyna-server (Closes: #1030125). - Update Standards-Version to 4.6.2 (no changes). * debian/copyright: - Update copyright years. -- Amin Bandali Thu, 16 Feb 2023 19:20:02 -0500 ** Changed in: grilo-plugins (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to grilo-plugins in Ubuntu. https://bugs.launchpad.net/bugs/2007623 Title: Merge grilo-plugins 0.3.15-2 (universe) from Debian unstable (main) Status in grilo-plugins package in Ubuntu: Fix Released Bug description: Please merge grilo-plugins 0.3.15-2 (universe) from Debian unstable (main) Changelog entries since current lunar version 0.3.15-1ubuntu1: grilo-plugins (0.3.15-2) unstable; urgency=medium * debian/control: - Stop recommending dleyna-server (Closes: #1030125). - Update Standards-Version to 4.6.2 (no changes). * debian/copyright: - Update copyright years. -- Alberto Garcia Tue, 31 Jan 2023 16:45:49 +0100 Remaining differences with grilo-plugins from Debian unstable: - Split package into -base and -extra (Closes: #805609) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grilo-plugins/+bug/2007623/+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 1900167] Re: gnome-software Unable to install updates
https://gitlab.gnome.org/GNOME/gnome-software/-/issues/1114#note_1693917 It will need to backport the merge requests from this issue to the version of gnome-software Xubuntu are shipping. ** Changed in: gnome-software (Ubuntu) Status: Opinion => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1900167 Title: gnome-software Unable to install updates Status in gnome-software package in Ubuntu: Confirmed Bug description: Click on 'Updates' and then on 'Restart & Update' I have a message: Unable to install updates: GDBus.error... Prepared update not found:/var/lib/PackageKit/prepared-update corrado@corrado-x2-gg-1009:~$ apt policy gnome-software gnome-software: Installed: 3.38.0-2build1 Candidate: 3.38.0-2build1 Version table: *** 3.38.0-2build1 500 500 http://archive.ubuntu.com/ubuntu groovy/universe amd64 Packages 100 /var/lib/dpkg/status corrado@corrado-x2-gg-1009:~$ inxi -Fx System: Host: corrado-x2-gg-1009 Kernel: 5.8.0-23-generic x86_64 bits: 64 compiler: gcc v: 10.2.0 Desktop: N/A Distro: Ubuntu 20.10 (Groovy Gorilla) Machine: Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial: UEFI: American Megatrends v: P1.10 date: 05/11/2017 CPU: Info: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP arch: Kaby Lake rev: 9 L2 cache: 3072 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31199 Speed: 800 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 Graphics: Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel bus ID: 00:02.0 Display: x11 server: X.Org 1.20.8 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 20.2.0 direct render: Yes Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASRock driver: snd_hda_intel v: kernel bus ID: 00:1f.3 Device-2: Logitech QuickCam Pro 9000 type: USB driver: snd-usb-audio,uvcvideo bus ID: 1-8:4 Sound Server: ALSA v: k5.8.0-23-generic Network: Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: 3.2.6-k port: f040 bus ID: 00:1f.6 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 70:85:c2:44:7b:86 Drives: Local Storage: total: 2.05 TiB used: 9.42 GiB (0.4%) ID-1: /dev/nvme0n1 vendor: Kingston model: SKC2000M8250G size: 232.89 GiB ID-2: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB ID-3: /dev/sdb vendor: Hitachi model: HDS721010CLA332 size: 931.51 GiB Partition: ID-1: / size: 31.25 GiB used: 9.41 GiB (30.1%) fs: ext4 dev: /dev/nvme0n1p2 Swap: ID-1: swap-1 type: partition size: 8.00 GiB used: 0 KiB (0.0%) dev: /dev/sda2 Sensors: System Temperatures: cpu: 43.5 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 224 Uptime: 3h 13m Memory: 7.48 GiB used: 1.66 GiB (22.2%) Init: systemd runlevel: 5 Compilers: gcc: N/A Packages: 1874 Shell: Bash v: 5.0.17 inxi: 3.1.07 corrado@corrado-x2-gg-1009:~$ ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-software 3.38.0-2build1 ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14 Uname: Linux 5.8.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Oct 16 18:20:00 2020 InstallationDate: Installed on 2020-10-10 (6 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201009.1) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.38.0-2build1 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1900167/+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 1900167] Re: gnome-software Unable to install updates
https://gitlab.gnome.org/GNOME/gnome-software/-/issues/1114#note_1693917 -> It will need to backport the merge requests from this issue to the version of gnome-software Xubuntu are shipping. ** Changed in: gnome-software (Ubuntu) Status: Expired => Opinion -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1900167 Title: gnome-software Unable to install updates Status in gnome-software package in Ubuntu: Confirmed Bug description: Click on 'Updates' and then on 'Restart & Update' I have a message: Unable to install updates: GDBus.error... Prepared update not found:/var/lib/PackageKit/prepared-update corrado@corrado-x2-gg-1009:~$ apt policy gnome-software gnome-software: Installed: 3.38.0-2build1 Candidate: 3.38.0-2build1 Version table: *** 3.38.0-2build1 500 500 http://archive.ubuntu.com/ubuntu groovy/universe amd64 Packages 100 /var/lib/dpkg/status corrado@corrado-x2-gg-1009:~$ inxi -Fx System: Host: corrado-x2-gg-1009 Kernel: 5.8.0-23-generic x86_64 bits: 64 compiler: gcc v: 10.2.0 Desktop: N/A Distro: Ubuntu 20.10 (Groovy Gorilla) Machine: Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial: UEFI: American Megatrends v: P1.10 date: 05/11/2017 CPU: Info: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP arch: Kaby Lake rev: 9 L2 cache: 3072 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31199 Speed: 800 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 Graphics: Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel bus ID: 00:02.0 Display: x11 server: X.Org 1.20.8 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 20.2.0 direct render: Yes Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASRock driver: snd_hda_intel v: kernel bus ID: 00:1f.3 Device-2: Logitech QuickCam Pro 9000 type: USB driver: snd-usb-audio,uvcvideo bus ID: 1-8:4 Sound Server: ALSA v: k5.8.0-23-generic Network: Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: 3.2.6-k port: f040 bus ID: 00:1f.6 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 70:85:c2:44:7b:86 Drives: Local Storage: total: 2.05 TiB used: 9.42 GiB (0.4%) ID-1: /dev/nvme0n1 vendor: Kingston model: SKC2000M8250G size: 232.89 GiB ID-2: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB ID-3: /dev/sdb vendor: Hitachi model: HDS721010CLA332 size: 931.51 GiB Partition: ID-1: / size: 31.25 GiB used: 9.41 GiB (30.1%) fs: ext4 dev: /dev/nvme0n1p2 Swap: ID-1: swap-1 type: partition size: 8.00 GiB used: 0 KiB (0.0%) dev: /dev/sda2 Sensors: System Temperatures: cpu: 43.5 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 224 Uptime: 3h 13m Memory: 7.48 GiB used: 1.66 GiB (22.2%) Init: systemd runlevel: 5 Compilers: gcc: N/A Packages: 1874 Shell: Bash v: 5.0.17 inxi: 3.1.07 corrado@corrado-x2-gg-1009:~$ ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-software 3.38.0-2build1 ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14 Uname: Linux 5.8.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Oct 16 18:20:00 2020 InstallationDate: Installed on 2020-10-10 (6 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201009.1) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.38.0-2build1 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1900167/+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 1900167] Re: gnome-software Unable to install updates
It will need to backport the merge requests from this issue to the version of gnome-software Xubuntu are shipping. - see https://gitlab.gnome.org/GNOME/gnome- software/-/issues/1114#note_1693917 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-software/-/issues #1114 https://gitlab.gnome.org/GNOME/gnome-software/-/issues/1114 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1900167 Title: gnome-software Unable to install updates Status in gnome-software package in Ubuntu: Confirmed Bug description: Click on 'Updates' and then on 'Restart & Update' I have a message: Unable to install updates: GDBus.error... Prepared update not found:/var/lib/PackageKit/prepared-update corrado@corrado-x2-gg-1009:~$ apt policy gnome-software gnome-software: Installed: 3.38.0-2build1 Candidate: 3.38.0-2build1 Version table: *** 3.38.0-2build1 500 500 http://archive.ubuntu.com/ubuntu groovy/universe amd64 Packages 100 /var/lib/dpkg/status corrado@corrado-x2-gg-1009:~$ inxi -Fx System: Host: corrado-x2-gg-1009 Kernel: 5.8.0-23-generic x86_64 bits: 64 compiler: gcc v: 10.2.0 Desktop: N/A Distro: Ubuntu 20.10 (Groovy Gorilla) Machine: Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial: UEFI: American Megatrends v: P1.10 date: 05/11/2017 CPU: Info: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP arch: Kaby Lake rev: 9 L2 cache: 3072 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31199 Speed: 800 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 Graphics: Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel bus ID: 00:02.0 Display: x11 server: X.Org 1.20.8 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 20.2.0 direct render: Yes Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASRock driver: snd_hda_intel v: kernel bus ID: 00:1f.3 Device-2: Logitech QuickCam Pro 9000 type: USB driver: snd-usb-audio,uvcvideo bus ID: 1-8:4 Sound Server: ALSA v: k5.8.0-23-generic Network: Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: 3.2.6-k port: f040 bus ID: 00:1f.6 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 70:85:c2:44:7b:86 Drives: Local Storage: total: 2.05 TiB used: 9.42 GiB (0.4%) ID-1: /dev/nvme0n1 vendor: Kingston model: SKC2000M8250G size: 232.89 GiB ID-2: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB ID-3: /dev/sdb vendor: Hitachi model: HDS721010CLA332 size: 931.51 GiB Partition: ID-1: / size: 31.25 GiB used: 9.41 GiB (30.1%) fs: ext4 dev: /dev/nvme0n1p2 Swap: ID-1: swap-1 type: partition size: 8.00 GiB used: 0 KiB (0.0%) dev: /dev/sda2 Sensors: System Temperatures: cpu: 43.5 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 224 Uptime: 3h 13m Memory: 7.48 GiB used: 1.66 GiB (22.2%) Init: systemd runlevel: 5 Compilers: gcc: N/A Packages: 1874 Shell: Bash v: 5.0.17 inxi: 3.1.07 corrado@corrado-x2-gg-1009:~$ ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-software 3.38.0-2build1 ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14 Uname: Linux 5.8.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Oct 16 18:20:00 2020 InstallationDate: Installed on 2020-10-10 (6 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201009.1) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.38.0-2build1 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1900167/+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 2009918] [NEW] package libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1 failed to install/upgrade: impossible de créer un lien symbolique de secours de « ./usr/lib/x86_64-linux-gnu/dr
Public bug reported:
Running inside a VM (KVM) from a remastered ISO
The screen also show some artifacts horizontal dotted lines which disappear
after a second or two.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1
ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-30-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5json: {
CasperVersion: 1.445.1
CompositorRunning: None
Date: Fri Mar 10 08:21:08 2023
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ErrorMessage: impossible de créer un lien symbolique de secours de «
./usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so » avant d'installer une nouvelle
version: Aucun espace disponible sur le périphérique
ExtraDebuggingInterest: No
GraphicsCard:
Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 04) (prog-if 00
[VGA controller])
Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
InstallationDate: Installed on 2022-02-22 (380 days ago)
InstallationMedia:
LiveMediaBuild: Systemback Live (MobiOffice) - Release amd64
Lsusb:
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t:
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz boot=casper
initrd=/casper/initrd.gz quiet splash
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal,
3.8.2-0ubuntu2
PythonDetails: N/A
SourcePackage: mesa
Title: package libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1 failed to
install/upgrade: impossible de créer un lien symbolique de secours de «
./usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so » avant d'installer une nouvelle
version: Aucun espace disponible sur le périphérique
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.release: 0.0
dmi.bios.vendor: SeaBIOS
dmi.bios.version: 1.13.0-1ubuntu1.1
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-focal
dmi.modalias:
dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-focal:cvnQEMU:ct1:cvrpc-i440fx-focal:sku:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-focal
dmi.sys.vendor: QEMU
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
** Affects: mesa (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-package focal ubuntu
--
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/2009918
Title:
package libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1 failed to
install/upgrade: impossible de créer un lien symbolique de secours de
« ./usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so » avant d'installer une
nouvelle version: Aucun espace disponible sur le périphérique
Status in mesa package in Ubuntu:
New
Bug description:
Running inside a VM (KVM) from a remastered ISO
The screen also show some artifacts horizontal dotted lines which disappear
after a second or two.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1
ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-30-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5json: {
CasperVersion: 1.445.1
CompositorRunning: None
Date: Fri Mar 10 08:21:08 2023
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ErrorMessage: impossible de créer un lien symbolique de secours de «
./usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so » avant d'installer une nouvelle
version: Aucun espace disponible sur le périphérique
ExtraDebuggingInterest: No
GraphicsCard:
Red Hat, Inc. QXL paravirtual graphic card [1b36:0100]
