[Desktop-packages] [Bug 1997150] Re: system will not boot using kernel version 5.15.0-53-generic
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: evince (Ubuntu) Status: New => Confirmed -- 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/1997150 Title: system will not boot using kernel version 5.15.0-53-generic Status in evince package in Ubuntu: Confirmed Bug description: When updating packages using apt-get dist-upgrade I receive this message: ### New kernel available The currently running kernel version is 5.15.0-52-generic which is not the expected kernel version 5.15.0-53-generic. Restarting the system to load the new kernel will not be handled automatically, so you should consider rebooting. ### When I reboot using the version 53-generic, the system will not boot. I am using Ubuntu 22.04.1 LTS (jammy) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 42.3-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Nov 19 09:40:31 2022 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: Upgraded to jammy on 2022-09-04 (76 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1997150/+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 1535390] Re: Chromium's built-in PDF renderer crashes when rendering some files, takes unity down
[Expired for chromium-browser (Ubuntu) because there has been no activity for 60 days.] ** Changed in: chromium-browser (Ubuntu) Status: Incomplete => Expired -- 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/1535390 Title: Chromium's built-in PDF renderer crashes when rendering some files, takes unity down Status in chromium-browser package in Ubuntu: Expired Bug description: Chromium reliably crashes when opening some PDF files (not all of them). When it does, unity (compiz) is taken down with it and I'm taken back to the login screen. At that point logging in results in compiz seemingly crashing again, and a reboot is needed to allow logging in again. I'm attaching a PDF file that reliably triggers the crash. Note that the file renders fine in e.g. evince. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: chromium-browser 47.0.2526.106-0ubuntu0.14.04.1.1107 ProcVersionSignature: Ubuntu 3.16.0-57.77~14.04.1-generic 3.16.7-ckt20 Uname: Linux 3.16.0-57-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jan 18 18:15:10 2016 Desktop-Session: 'ubuntu' '/etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg' '/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/' DetectedPlugins: EcryptfsInUse: Yes Env: 'None' 'None' InstallationDate: Installed on 2015-03-25 (299 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64+mac (20150218.1) Load-Avg-1min: 1.15 Load-Processes-Running-Percent: 0.3% MachineType: TOSHIBA Satellite A200 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-57-generic root=UUID=f7263bc4-72bc-441d-9b44-570c4df94a18 ro quiet splash vt.handoff=7 SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/27/2007 dmi.bios.vendor: TOSHIBA dmi.bios.version: V1.70 dmi.board.name: ISKAA dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV1.70:bd09/27/2007:svnTOSHIBA:pnSatelliteA200:pvrPSAE3E-03K01CCE:rvnTOSHIBA:rnISKAA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A: dmi.product.name: Satellite A200 dmi.product.version: PSAE3E-03K01CCE dmi.sys.vendor: TOSHIBA gconf-keys: /desktop/gnome/applications/browser/exec = b''/desktop/gnome/url-handlers/https/command = b''/desktop/gnome/url-handlers/https/enabled = b''/desktop/gnome/url-handlers/http/command = b''/desktop/gnome/url-handlers/http/enabled = b''/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b''/desktop/gnome/interface/gtk_theme = b'' modified.conffile..etc.default.chromium.browser: [deleted] mtime.conffile..etc.chromium.browser.default: 2016-01-13T07:48:20.494539 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1535390/+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 1547483] Re: chromium-browser selects the first entry in srcset element
[Expired for chromium-browser (Ubuntu) because there has been no activity for 60 days.] ** Changed in: chromium-browser (Ubuntu) Status: Incomplete => Expired -- 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/1547483 Title: chromium-browser selects the first entry in srcset element Status in chromium-browser package in Ubuntu: Expired Bug description: The chormium browser (v37) if showing the first entry in a srcset attribute for IMG tags. Given: http://codepen.io/anon/pen/zxPZYM Expected: largest image to be shown (running on Full HD res) Actual: First entry in the srcset list is displayed. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: chromium-browser 37.0.2062.120-0ubuntu0.12.04.1~pkg917 ProcVersionSignature: Ubuntu 3.13.0-77.121~precise1-generic 3.13.11-ckt32 Uname: Linux 3.13.0-77-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.13 Architecture: amd64 Date: Fri Feb 19 13:00:34 2016 InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) MarkForUpload: True SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.chromium.browser: [deleted] mtime.conffile..etc.chromium.browser.default: 2016-01-22T23:46:52.310138 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1547483/+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 1552298] Re: chromium-browser should depend on kmod
[Expired for chromium-browser (Ubuntu) because there has been no activity for 60 days.] ** Changed in: chromium-browser (Ubuntu) Status: Incomplete => Expired -- 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/1552298 Title: chromium-browser should depend on kmod Status in chromium-browser package in Ubuntu: Expired Bug description: The chromium-browser package should depend on the kmod package due to the following workaround in /usr/bin/chromium-browser: lsmod |grep ^i915\ >/dev/null && export LIBGL_DRI3_DISABLE=1 There are situations in which chromium-browser can be installed without kmod already being installed such as in a container for Libertine (the convergence container for phones/tablets/future desktop). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1552298/+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 1997154] Re: package firefox 87.0+build3-0ubuntu0.20.10.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1
error when updating my OS, and had to update Firefox as well. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1997154 Title: package firefox 87.0+build3-0ubuntu0.20.10.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 Status in firefox package in Ubuntu: New Bug description: Was updating my os version and also had to update firefox. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: firefox 87.0+build3-0ubuntu0.20.10.1 ProcVersionSignature: Ubuntu 5.8.0-1019.22-raspi 5.8.18 Uname: Linux 5.8.0-1019-raspi aarch64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu82.1 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: merlinddg51 1377 F pulseaudio /dev/snd/controlC0: merlinddg51 1377 F pulseaudio BuildID: 20210318103112 CasperMD5CheckResult: unknown Channel: Unavailable Date: Sat Nov 19 08:46:02 2022 ErrorMessage: new firefox package pre-installation script subprocess returned error exit status 1 ForcedLayersAccel: False ImageMediaBuild: 20201022 IpRoute: default via 192.168.1.1 dev eth0 proto dhcp metric 100 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.75 metric 100 NoProfiles: True PciNetwork: PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 87.0+build3-0ubuntu0.20.10.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1997154/+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 1997154] [NEW] package firefox 87.0+build3-0ubuntu0.20.10.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1
Public bug reported: Was updating my os version and also had to update firefox. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: firefox 87.0+build3-0ubuntu0.20.10.1 ProcVersionSignature: Ubuntu 5.8.0-1019.22-raspi 5.8.18 Uname: Linux 5.8.0-1019-raspi aarch64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu82.1 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: merlinddg51 1377 F pulseaudio /dev/snd/controlC0: merlinddg51 1377 F pulseaudio BuildID: 20210318103112 CasperMD5CheckResult: unknown Channel: Unavailable Date: Sat Nov 19 08:46:02 2022 ErrorMessage: new firefox package pre-installation script subprocess returned error exit status 1 ForcedLayersAccel: False ImageMediaBuild: 20201022 IpRoute: default via 192.168.1.1 dev eth0 proto dhcp metric 100 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.75 metric 100 NoProfiles: True PciNetwork: PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 87.0+build3-0ubuntu0.20.10.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package arm64 arm64-image jammy need-duplicate-check raspi-image -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1997154 Title: package firefox 87.0+build3-0ubuntu0.20.10.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 Status in firefox package in Ubuntu: New Bug description: Was updating my os version and also had to update firefox. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: firefox 87.0+build3-0ubuntu0.20.10.1 ProcVersionSignature: Ubuntu 5.8.0-1019.22-raspi 5.8.18 Uname: Linux 5.8.0-1019-raspi aarch64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu82.1 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: merlinddg51 1377 F pulseaudio /dev/snd/controlC0: merlinddg51 1377 F pulseaudio BuildID: 20210318103112 CasperMD5CheckResult: unknown Channel: Unavailable Date: Sat Nov 19 08:46:02 2022 ErrorMessage: new firefox package pre-installation script subprocess returned error exit status 1 ForcedLayersAccel: False ImageMediaBuild: 20201022 IpRoute: default via 192.168.1.1 dev eth0 proto dhcp metric 100 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.75 metric 100 NoProfiles: True PciNetwork: PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 87.0+build3-0ubuntu0.20.10.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1997154/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1996076] Re: [BPO] libreoffice 7.3.7 for focal
** Changed in: libreoffice (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1996076 Title: [BPO] libreoffice 7.3.7 for focal Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Focal: Fix Committed Bug description: [Impact] * LibreOffice 7.3.7 is in its seventh bugfix release of the 7.3 line: https://wiki.documentfoundation.org/ReleasePlan/7.3#7.3.7_release * This source packages matches the proposed SRU for jammy handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1995054 and its backport is currently provided by the LibreOffice Still PPA at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+packages * Previous backport of 7.3.6 handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1989418 * LibreOffice 6.4.7 (EOL since November 30, 2020) is currently released in focal. * LibreOffice 7.3.6 is currently released in focal-backports. * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/1:7.3.7-0ubuntu0.22.04.1 * Backport target is Focal/20.04 LTS only to provide an official build of a more recent upstream version of LibreOffice [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_73/2020/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/amd64/libr/libreoffice/20221109_131732_0f324@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/arm64/libr/libreoffice/20221109_134252_403d2@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/armhf/libr/libreoffice/20221109_152925_85c50@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/ppc64el/libr/libreoffice/20221109_134511_07b38@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/s390x/libr/libreoffice/20221109_125147_0715b@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 28 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1996076/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1996082] Re: [BPO] libreoffice 7.3.7 for bionic
** Changed in: libreoffice (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1996082 Title: [BPO] libreoffice 7.3.7 for bionic Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Bionic: Fix Committed Bug description: [Impact] * LibreOffice 7.3.7 is in its seventh bugfix release of the 7.3 line: https://wiki.documentfoundation.org/ReleasePlan/7.3#7.3.7_release * This source packages matches the proposed SRU for jammy handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1995054 and its backport is currently provided by the LibreOffice Still PPA at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+packages * Previous backport of 7.3.6 handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1990382 * LibreOffice 6.4.7 (EOL since November 30, 2020) is currently released in focal. * LibreOffice 7.3.6 is currently released in bionic-backports. * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/1:7.3.7-0ubuntu0.22.04.1 * Backport target is Bionic/18.04 LTS only to provide an official build of a more recent upstream version of LibreOffice [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_73/2020/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/amd64/libr/libreoffice/20221109_194619_aafcb@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/arm64/libr/libreoffice/20221109_182935_ad523@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/armhf/libr/libreoffice/20221109_193157_bfaf9@/log.gz * [i386] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/i386/libr/libreoffice/20221110_005928_4e278@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/ppc64el/libr/libreoffice/20221109_191816_d9338@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/s390x/libr/libreoffice/20221109_173606_13453@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 28 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1996082/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969512] Re: Totem unable to play video: "The specified movie could not be found"
New report: The Videos app will not play .mp4 files comes up with error "The specified movie could not be found.", they play OK on VSCode & Kdenlive, using Ubuntu 22.04, worked OK on 20.04.5 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1969512 Title: Totem unable to play video: "The specified movie could not be found" Status in Totem: Fix Released Status in totem package in Ubuntu: Confirmed Bug description: As part of our ISO testing for the Pi desktop, we attempt to play https://archive.org/download/BigBuckBunny_124/Content/big_buck_bunny_720p_surround.mp4 with the shipped totem video player. Unfortunately, on the current Jammy image, totem simply reports "The specified movie could not be found" when attempting to play the file (the exit code is 0, no other errors are reported at the command line). I've attempted to install a few gstreamer codecs, in case that might've been the issue (this was necessary on some older versions), but neither gstreamer1.0-plugins-ugly, nor gstreamer1.0-libav made any difference. Just to ensure the video file was intact and playable, I then installed vlc from the archive, which played the video happily. To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1969512/+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 1997150] [NEW] system will not boot using kernel version 5.15.0-53-generic
Public bug reported: When updating packages using apt-get dist-upgrade I receive this message: ### New kernel available The currently running kernel version is 5.15.0-52-generic which is not the expected kernel version 5.15.0-53-generic. Restarting the system to load the new kernel will not be handled automatically, so you should consider rebooting. ### When I reboot using the version 53-generic, the system will not boot. I am using Ubuntu 22.04.1 LTS (jammy) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 42.3-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Nov 19 09:40:31 2022 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: Upgraded to jammy on 2022-09-04 (76 days ago) ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages uec-images wayland-session -- 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/1997150 Title: system will not boot using kernel version 5.15.0-53-generic Status in evince package in Ubuntu: New Bug description: When updating packages using apt-get dist-upgrade I receive this message: ### New kernel available The currently running kernel version is 5.15.0-52-generic which is not the expected kernel version 5.15.0-53-generic. Restarting the system to load the new kernel will not be handled automatically, so you should consider rebooting. ### When I reboot using the version 53-generic, the system will not boot. I am using Ubuntu 22.04.1 LTS (jammy) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 42.3-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Nov 19 09:40:31 2022 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: Upgraded to jammy on 2022-09-04 (76 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1997150/+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 1970808] Re: [nvidia] Lock screen is frozen
This hasn't happened to me in a while, so I think it is fixed, at least when using the latest 515 Nvidia drivers. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1970808 Title: [nvidia] Lock screen is frozen Status in nvidia-graphics-drivers-510 package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: After suspending my PC, sometimes when I resume, I get stuck on the lock screen which shows the current time and says "Click or press any key". No matter which mouse button or key I press, the screen is frozen. The mouse cursor is displayed but does not move. It seems to occur more frequently when my computer has been suspended for at least several hours. I would say this issue occurs about 50% of the time (very roughly speaking). Things I have tried which did not work: - Unplugging and re-plugging in my mouse - Turning my keyboard off and on again - Ctrl+Alt+F2 through F6, in an attempt to get access to a TTY This is on a fresh install of 22.04. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-27-generic 5.15.0-27.28 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: srmagura 1247 F pulseaudio /dev/snd/controlC2: srmagura 1247 F pulseaudio /dev/snd/controlC0: srmagura 1247 F pulseaudio /dev/snd/controlC1: srmagura 1247 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 28 17:53:11 2022 InstallationDate: Installed on 2022-04-23 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B450M DS3H ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=c4ac1391-7d4e-4282-94ba-fbae3c4c044c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: Default string dmi.board.name: B450M DS3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:br5.13:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: B450M DS3H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/1970808/+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 1971712] Re: Add support for Intel DG2
The new firmware package works fine with the 6.0 kernel, it loads the GuC and HuC Firmware, as seen below: [4.691687] i915 :03:00.0: [drm] Finished loading DMC firmware i915/dg2_dmc_ver2_06.bin (v2.6) [4.702309] i915 :03:00.0: [drm] GuC firmware i915/dg2_guc_70.1.2.bin version 70. I presume the firmware updates are a preparation for the i915/drm backports to the 6.0-oem kernel? -- 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/1971712 Title: Add support for Intel DG2 Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Status in linux-oem-5.17 source package in Jammy: Won't Fix Status in linux-oem-6.0 source package in Jammy: Confirmed Status in mesa source package in Jammy: Fix Released Status in linux-firmware source package in Kinetic: Fix Committed Bug description: [Impact] Ubuntu 22.04 does not support Intel DG2-based hw which is released later this year. [Fix] Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1 or 22.2 kernel: oem-6.0 plus a bunch of backports from 6.1/drm-tip firmare: updates to i915 DMC, GuC [Test case] Boot a system with a DG2-based GPU, check that native graphics drivers are used. Test mesa also on gen9-gen12 GPU's to verify that there are no regressions even though the backports are for DG2. [What could go wrong] The Mesa patches are only for DG2 support, should not affect other hardware at all. The kernel driver is in a separate package which isn't installed by default except preinstall machines with this hardware. So other users are not affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1971712/+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 1989602] Re: Delay in updating charge status in Ubuntu 22.04 LTS
This bug does not seem to be present in Ubuntu 22.10, on the same hardware. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1989602 Title: Delay in updating charge status in Ubuntu 22.04 LTS Status in upower package in Ubuntu: New Bug description: I am using a Lenovo ThinkPad Yoga 370, running Ubuntu 22.04 LTS. When plugging in the charger, the current charge status in the top bar and Settings shows 'Not Charging' for a few minutes and then shows that the system is charging normally. When unplugging the charger the same happens; the charge status shows 'Not Charging' for a few minutes, and then shows the correct charge status. Normally, the change in power status should be instantaneous. In short, there is a delay in the OS in showing the current charge status. Upon further research, it was found that the 'upower' service is to blame; it polls every two minutes(i.e., it refreshes the charge status every two minutes); causing a delay in charge status. This is further compounded by the fact that restarting upower service, or the system as a whole makes the system to show the correct charge status. However, I did not have this problem on another system, a HP Pavilion x360 14m-dw0023dx, running the same OS, Ubuntu 22.04 LTS. There, the power status behaves normally with no delays whatsoever. Please look into this issue and fix this bug as soon as possible. One suggestion would be to increase the polling frequency of upower from 2 mins. to something lesser, so that the charge status shows correctly. upower version: UPower client version 0.99.17 UPower daemon version 0.99.17 OS: Description: Ubuntu 22.04.1 LTS Release: 22.04 Kernel: Linux 5.15.0-47-generic ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: upower 0.99.17-1 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 14 20:41:16 2022 InstallationDate: Installed on 2022-09-12 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: upower UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1989602/+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 1997147] [NEW] App theme for legacy GTK3 apps inadvertently changes to light mode when Appearance pane in Settings is clicked/made active in Ubuntu 22.10
Public bug reported: This bug happens with dark mode enabled, whenever I open Settings with Appearance pane open, or I enter Appearance pane from other panes in Settings. Whenever I do so, the app theme for legacy GTK3 applications (those not supporting the new GTK dark mode API) inadvertently changes to light mode. To turn back dark mode on for legacy apps, I have to use the toggle in Quick Settings, or click on any of the theme circles. Normally, the dark mode theme for legacy apps should not change whenever Settings is opened with Appearance pane open, or Appearance pane is selected from other panes in Settings, just like GTK3 applications using the new dark mode API, and GTK4+libadwaita apps (which are not affected by this bug). A recording of the bug in action is attached along with this report. Ubuntu release details: Description:Ubuntu 22.10 Release:22.10 Package details: gnome-control-center: Installed: 1:43.0-1ubuntu2 Candidate: 1:43.0-1ubuntu2 Version table: *** 1:43.0-1ubuntu2 500 500 http://ae.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-control-center 1:43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Nov 19 17:32:30 2022 InstallationDate: Installed on 2022-09-24 (56 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic third-party-packages wayland-session ** Attachment added: "Screen capture showing the bug in action. It shows two apps: (Gufw (legacy GTK3), Software & Updates (GTK3 with new dark mode API support), and Settings (GTK4+libadwaita)" https://bugs.launchpad.net/bugs/1997147/+attachment/5631569/+files/Screencast%20from%202022-11-19%2017-42-54.webm -- 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/1997147 Title: App theme for legacy GTK3 apps inadvertently changes to light mode when Appearance pane in Settings is clicked/made active in Ubuntu 22.10 Status in gnome-control-center package in Ubuntu: New Bug description: This bug happens with dark mode enabled, whenever I open Settings with Appearance pane open, or I enter Appearance pane from other panes in Settings. Whenever I do so, the app theme for legacy GTK3 applications (those not supporting the new GTK dark mode API) inadvertently changes to light mode. To turn back dark mode on for legacy apps, I have to use the toggle in Quick Settings, or click on any of the theme circles. Normally, the dark mode theme for legacy apps should not change whenever Settings is opened with Appearance pane open, or Appearance pane is selected from other panes in Settings, just like GTK3 applications using the new dark mode API, and GTK4+libadwaita apps (which are not affected by this bug). A recording of the bug in action is attached along with this report. Ubuntu release details: Description: Ubuntu 22.10 Release: 22.10 Package details: gnome-control-center: Installed: 1:43.0-1ubuntu2 Candidate: 1:43.0-1ubuntu2 Version table: *** 1:43.0-1ubuntu2 500 500 http://ae.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-control-center 1:43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Nov 19 17:32:30 2022 InstallationDate: Installed on 2022-09-24 (56 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1997147/+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 1971712] Please test proposed package
Hello Timo, or anyone else affected, Accepted linux-firmware into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/20220329.git681281e4-0ubuntu3.7 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 mesa in Ubuntu. https://bugs.launchpad.net/bugs/1971712 Title: Add support for Intel DG2 Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Status in linux-oem-5.17 source package in Jammy: Won't Fix Status in linux-oem-6.0 source package in Jammy: Confirmed Status in mesa source package in Jammy: Fix Released Status in linux-firmware source package in Kinetic: Fix Committed Bug description: [Impact] Ubuntu 22.04 does not support Intel DG2-based hw which is released later this year. [Fix] Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1 or 22.2 kernel: oem-6.0 plus a bunch of backports from 6.1/drm-tip firmare: updates to i915 DMC, GuC [Test case] Boot a system with a DG2-based GPU, check that native graphics drivers are used. Test mesa also on gen9-gen12 GPU's to verify that there are no regressions even though the backports are for DG2. [What could go wrong] The Mesa patches are only for DG2 support, should not affect other hardware at all. The kernel driver is in a separate package which isn't installed by default except preinstall machines with this hardware. So other users are not affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1971712/+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 1971712] Re: Add support for Intel DG2
Hello Timo, or anyone else affected, Accepted linux-firmware into kinetic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/20220923.gitf09bebf3-0ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- 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. ** Changed in: linux-firmware (Ubuntu Kinetic) Status: New => Fix Committed ** Changed in: linux-firmware (Ubuntu Jammy) Status: In Progress => Fix Committed -- 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/1971712 Title: Add support for Intel DG2 Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Status in linux-oem-5.17 source package in Jammy: Won't Fix Status in linux-oem-6.0 source package in Jammy: Confirmed Status in mesa source package in Jammy: Fix Released Status in linux-firmware source package in Kinetic: Fix Committed Bug description: [Impact] Ubuntu 22.04 does not support Intel DG2-based hw which is released later this year. [Fix] Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1 or 22.2 kernel: oem-6.0 plus a bunch of backports from 6.1/drm-tip firmare: updates to i915 DMC, GuC [Test case] Boot a system with a DG2-based GPU, check that native graphics drivers are used. Test mesa also on gen9-gen12 GPU's to verify that there are no regressions even though the backports are for DG2. [What could go wrong] The Mesa patches are only for DG2 support, should not affect other hardware at all. The kernel driver is in a separate package which isn't installed by default except preinstall machines with this hardware. So other users are not affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1971712/+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 1997143] [NEW] ctrl + s opens up a lot of save menu in firefox
Public bug reported: cancel button does not work, had to press esc key multiple times to close that, is that ubuntu related? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 Uname: Linux 5.15.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 126: Error executing command as another user: Request dismissed Date: Sat Nov 19 17:19:22 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell WhiskeyLake-U GT2 [UHD Graphics 620] [1028:08c9] Subsystem: Dell Jet PRO [Radeon R5 M230 / R7 M260DX / Radeon 520 Mobile] [1028:08c9] InstallationDate: Installed on 2022-11-19 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 002: ID 09da:c10a A4Tech Co., Ltd. USB Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3580 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-53-generic root=UUID=977cd227-415b-4915-bc7a-3a9c60e11499 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 126: Error executing command as another user: Request dismissed dmi.bios.date: 04/12/2022 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.0 dmi.board.name: 0V9PNT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.0:bd04/12/2022:br1.19:svnDellInc.:pnInspiron3580:pvr:rvnDellInc.:rn0V9PNT:rvrA00:cvnDellInc.:ct10:cvr:sku08C9: dmi.product.family: Inspiron dmi.product.name: Inspiron 3580 dmi.product.sku: 08C9 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.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-2ubuntu1 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 jammy ubuntu wayland-session ** Description changed: cancel button does not work, had to press esc key multiple times to - close that + close that, is that ubuntu related? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 Uname: Linux 5.15.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 126: Error executing command as another user: Request dismissed Date: Sat Nov 19 17:19:22 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: - Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) -Subsystem: Dell WhiskeyLake-U GT2 [UHD Graphics 620] [1028:08c9] -Subsystem: Dell Jet PRO [Radeon R5 M230 / R7 M260DX / Radeon 520 Mobile] [1028:08c9] + Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) + Subsystem: Dell WhiskeyLake-U GT2 [UHD Graphics 620] [1028:08c9] + Subsystem: Dell Jet PRO [Radeon R5 M230 / R7 M260DX / Radeon 520 Mobile] [1028:08c9] InstallationDate: Installed on 2022-11-19 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD - Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications - Bus 001 Device 002: ID 09da:c10a A4Tech Co., Ltd. USB Mouse - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001:
[Desktop-packages] [Bug 1996927] Re: Nautilus send mail not working
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nautilus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1996927 Title: Nautilus send mail not working Status in nautilus package in Ubuntu: Confirmed Bug description: Hi, After upgrade from 22.04 to 22.10 Send an attached file to email from nautilus is not working anymore. Menu sendmail ( courriel in french) appears when i right click on file , then thunderbird appears but without the attachement . It was working very well with previous releases . regards Yanick ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Nov 17 18:42:19 2022 InstallationDate: Installed on 2021-10-16 (397 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 nautilus-image-converter 0.4.0-2 python3-nautilus 4.0-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1996927/+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 1997142] monitors.xml.txt
apport information ** Attachment added: "monitors.xml.txt" https://bugs.launchpad.net/bugs/1997142/+attachment/5631554/+files/monitors.xml.txt ** Description changed: When using a Wayland session with kernel 5.15.0-53-generic gnome-shell may sometimes crash and restart. This happened to me when using a chromium-based browser (Brave). ➜ ~ uname -r 5.15.0-53-generic - ➜ ~ printenv XDG_SESSION_TYPE + ➜ ~ printenv XDG_SESSION_TYPE wayland The issue does not happen on the previous version of the kernel which is - 5.15.0-52-generic. + 5.15.0-52-generic or on the 5.15.0-53-generic kernel when using an X11 + session. apt policy brave-browser brave-browser: - Installed: 1.45.127 - Candidate: 1.45.127 - --- + Installed: 1.45.127 + Candidate: 1.45.127 + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-01-08 (679 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-shell 42.5-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 RelatedPackageVersions: mutter-common 42.5-0ubuntu1 Tags: jammy wayland-session Uname: Linux 5.15.0-53-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-21 (211 days ago) UserGroups: adm cdrom cvdnetwork dialout dip kvm libvirt lpadmin lxd plugdev render sambashare sudo video _MarkForUpload: True -- 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/1997142 Title: gnome-shell (wayland session) crashes on kernel 5.15.0-53-generic when some applications are started Status in gnome-shell package in Ubuntu: New Bug description: When using a Wayland session with kernel 5.15.0-53-generic gnome-shell may sometimes crash and restart. This happened to me when using a chromium-based browser (Brave). ➜ ~ uname -r 5.15.0-53-generic ➜ ~ printenv XDG_SESSION_TYPE wayland The issue does not happen on the previous version of the kernel which is 5.15.0-52-generic or on the 5.15.0-53-generic kernel when using an X11 session. apt policy brave-browser brave-browser: Installed: 1.45.127 Candidate: 1.45.127 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-01-08 (679 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-shell 42.5-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 RelatedPackageVersions: mutter-common 42.5-0ubuntu1 Tags: jammy wayland-session Uname: Linux 5.15.0-53-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-21 (211 days ago) UserGroups: adm cdrom cvdnetwork dialout dip kvm libvirt lpadmin lxd plugdev render sambashare sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1997142/+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 1969602] Re: gnome-shell with focus-mode=mouse behaves wrongly when alt-tabbing
** Changed in: gnome-shell Status: New => 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/1969602 Title: gnome-shell with focus-mode=mouse behaves wrongly when alt-tabbing Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I have set gnome to "focus on hover", i.e. focus follows mouse. If I alt-tab to bring a window to the front but the mouse is over another window, then the hovered-over window will reclaim focus and the window I raised will typically get covered up again. In previous gnome versions, if I explicitly focussed a window via keyboard shortcuts, it remained focussed and I think this is the preferred behaviour. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 20 11:35:20 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-17 (33 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1969602/+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 1997142] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/1997142/+attachment/5631553/+files/ShellJournal.txt -- 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/1997142 Title: gnome-shell (wayland session) crashes on kernel 5.15.0-53-generic when some applications are started Status in gnome-shell package in Ubuntu: New Bug description: When using a Wayland session with kernel 5.15.0-53-generic gnome-shell may sometimes crash and restart. This happened to me when using a chromium-based browser (Brave). ➜ ~ uname -r 5.15.0-53-generic ➜ ~ printenv XDG_SESSION_TYPE wayland The issue does not happen on the previous version of the kernel which is 5.15.0-52-generic or on the 5.15.0-53-generic kernel when using an X11 session. apt policy brave-browser brave-browser: Installed: 1.45.127 Candidate: 1.45.127 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-01-08 (679 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-shell 42.5-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 RelatedPackageVersions: mutter-common 42.5-0ubuntu1 Tags: jammy wayland-session Uname: Linux 5.15.0-53-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-21 (211 days ago) UserGroups: adm cdrom cvdnetwork dialout dip kvm libvirt lpadmin lxd plugdev render sambashare sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1997142/+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 1997142] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1997142/+attachment/5631552/+files/ProcEnviron.txt -- 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/1997142 Title: gnome-shell (wayland session) crashes on kernel 5.15.0-53-generic when some applications are started Status in gnome-shell package in Ubuntu: New Bug description: When using a Wayland session with kernel 5.15.0-53-generic gnome-shell may sometimes crash and restart. This happened to me when using a chromium-based browser (Brave). ➜ ~ uname -r 5.15.0-53-generic ➜ ~ printenv XDG_SESSION_TYPE wayland The issue does not happen on the previous version of the kernel which is 5.15.0-52-generic or on the 5.15.0-53-generic kernel when using an X11 session. apt policy brave-browser brave-browser: Installed: 1.45.127 Candidate: 1.45.127 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-01-08 (679 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-shell 42.5-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 RelatedPackageVersions: mutter-common 42.5-0ubuntu1 Tags: jammy wayland-session Uname: Linux 5.15.0-53-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-21 (211 days ago) UserGroups: adm cdrom cvdnetwork dialout dip kvm libvirt lpadmin lxd plugdev render sambashare sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1997142/+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 1997142] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1997142/+attachment/5631549/+files/Dependencies.txt -- 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/1997142 Title: gnome-shell (wayland session) crashes on kernel 5.15.0-53-generic when some applications are started Status in gnome-shell package in Ubuntu: New Bug description: When using a Wayland session with kernel 5.15.0-53-generic gnome-shell may sometimes crash and restart. This happened to me when using a chromium-based browser (Brave). ➜ ~ uname -r 5.15.0-53-generic ➜ ~ printenv XDG_SESSION_TYPE wayland The issue does not happen on the previous version of the kernel which is 5.15.0-52-generic or on the 5.15.0-53-generic kernel when using an X11 session. apt policy brave-browser brave-browser: Installed: 1.45.127 Candidate: 1.45.127 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-01-08 (679 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-shell 42.5-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 RelatedPackageVersions: mutter-common 42.5-0ubuntu1 Tags: jammy wayland-session Uname: Linux 5.15.0-53-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-21 (211 days ago) UserGroups: adm cdrom cvdnetwork dialout dip kvm libvirt lpadmin lxd plugdev render sambashare sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1997142/+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 1997142] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1997142/+attachment/5631551/+files/ProcCpuinfoMinimal.txt -- 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/1997142 Title: gnome-shell (wayland session) crashes on kernel 5.15.0-53-generic when some applications are started Status in gnome-shell package in Ubuntu: New Bug description: When using a Wayland session with kernel 5.15.0-53-generic gnome-shell may sometimes crash and restart. This happened to me when using a chromium-based browser (Brave). ➜ ~ uname -r 5.15.0-53-generic ➜ ~ printenv XDG_SESSION_TYPE wayland The issue does not happen on the previous version of the kernel which is 5.15.0-52-generic or on the 5.15.0-53-generic kernel when using an X11 session. apt policy brave-browser brave-browser: Installed: 1.45.127 Candidate: 1.45.127 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-01-08 (679 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-shell 42.5-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 RelatedPackageVersions: mutter-common 42.5-0ubuntu1 Tags: jammy wayland-session Uname: Linux 5.15.0-53-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-21 (211 days ago) UserGroups: adm cdrom cvdnetwork dialout dip kvm libvirt lpadmin lxd plugdev render sambashare sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1997142/+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 1997142] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1997142/+attachment/5631550/+files/GsettingsChanges.txt -- 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/1997142 Title: gnome-shell (wayland session) crashes on kernel 5.15.0-53-generic when some applications are started Status in gnome-shell package in Ubuntu: New Bug description: When using a Wayland session with kernel 5.15.0-53-generic gnome-shell may sometimes crash and restart. This happened to me when using a chromium-based browser (Brave). ➜ ~ uname -r 5.15.0-53-generic ➜ ~ printenv XDG_SESSION_TYPE wayland The issue does not happen on the previous version of the kernel which is 5.15.0-52-generic or on the 5.15.0-53-generic kernel when using an X11 session. apt policy brave-browser brave-browser: Installed: 1.45.127 Candidate: 1.45.127 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-01-08 (679 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-shell 42.5-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 RelatedPackageVersions: mutter-common 42.5-0ubuntu1 Tags: jammy wayland-session Uname: Linux 5.15.0-53-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-21 (211 days ago) UserGroups: adm cdrom cvdnetwork dialout dip kvm libvirt lpadmin lxd plugdev render sambashare sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1997142/+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 1997142] [NEW] gnome-shell (wayland session) crashes on kernel 5.15.0-53-generic when some applications are started
Public bug reported: When using a Wayland session with kernel 5.15.0-53-generic gnome-shell may sometimes crash and restart. This happened to me when using a chromium-based browser (Brave). ➜ ~ uname -r 5.15.0-53-generic ➜ ~ printenv XDG_SESSION_TYPE wayland The issue does not happen on the previous version of the kernel which is 5.15.0-52-generic or on the 5.15.0-53-generic kernel when using an X11 session. apt policy brave-browser brave-browser: Installed: 1.45.127 Candidate: 1.45.127 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-01-08 (679 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-shell 42.5-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 RelatedPackageVersions: mutter-common 42.5-0ubuntu1 Tags: jammy wayland-session Uname: Linux 5.15.0-53-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-21 (211 days ago) UserGroups: adm cdrom cvdnetwork dialout dip kvm libvirt lpadmin lxd plugdev render sambashare sudo video _MarkForUpload: True ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected jammy wayland-session ** Tags added: apport-collected jammy wayland-session ** Description changed: When using a Wayland session with kernel 5.15.0-53-generic gnome-shell may sometimes crash and restart. This happened to me when using a chromium-based browser (Brave). ➜ ~ uname -r 5.15.0-53-generic ➜ ~ printenv XDG_SESSION_TYPE wayland The issue does not happen on the previous version of the kernel which is 5.15.0-52-generic. apt policy brave-browser brave-browser: Installed: 1.45.127 Candidate: 1.45.127 + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.1 + Architecture: amd64 + CasperMD5CheckResult: unknown + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2021-01-08 (679 days ago) + InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) + NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair + Package: gnome-shell 42.5-0ubuntu1 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 + RelatedPackageVersions: mutter-common 42.5-0ubuntu1 + Tags: jammy wayland-session + Uname: Linux 5.15.0-53-generic x86_64 + UpgradeStatus: Upgraded to jammy on 2022-04-21 (211 days ago) + UserGroups: adm cdrom cvdnetwork dialout dip kvm libvirt lpadmin lxd plugdev render sambashare sudo video + _MarkForUpload: True -- 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/1997142 Title: gnome-shell (wayland session) crashes on kernel 5.15.0-53-generic when some applications are started Status in gnome-shell package in Ubuntu: New Bug description: When using a Wayland session with kernel 5.15.0-53-generic gnome-shell may sometimes crash and restart. This happened to me when using a chromium-based browser (Brave). ➜ ~ uname -r 5.15.0-53-generic ➜ ~ printenv XDG_SESSION_TYPE wayland The issue does not happen on the previous version of the kernel which is 5.15.0-52-generic or on the 5.15.0-53-generic kernel when using an X11 session. apt policy brave-browser brave-browser: Installed: 1.45.127 Candidate: 1.45.127 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-01-08 (679 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-shell 42.5-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 RelatedPackageVersions: mutter-common 42.5-0ubuntu1 Tags: jammy wayland-session Uname: Linux 5.15.0-53-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-21 (211 days ago) UserGroups: adm cdrom cvdnetwork dialout dip kvm libvirt lpadmin lxd plugdev render sambashare sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1997142/+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
