[Desktop-packages] [Bug 1858165] Re: Could not load the program library libodbc.so or it is corrupted. The ODBC data source selection is not available.
Hi there! I'm having the same problem but it wasn't fixable this way. Reason being most likely that I was using the snap version of Base. I now installed the apt version and it works. Have a good one. -- 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/1858165 Title: Could not load the program library libodbc.so or it is corrupted. The ODBC data source selection is not available. Status in libreoffice package in Ubuntu: Won't Fix Bug description: I'm working on Ubuntu 18.04 LTS x86_64 fully patched. I have LibreOffice Base installed. I am trying to open a MS Access database. I open LibreOffice Base. At Step (1) I select "Connect to an existing database". At Step (2), which is the File Open dialog, I click browse: Could not load the program library libodbc.so or it is corrupted. The ODBC data source selection is not available. At this point I am browsing to the *.mdb file. No database is selected. This is a drag. I am working with a company that specializes in fresh water wells. I'm trying to get them to convert from Windows to Linux for all the right reasons. Obviously they cannot convert if Linux software cannot open the database. $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.3 LTS Release: 18.04 Codename: bionic $ libreoffice --version LibreOffice 6.0.7.3 00m0(Build:3) $ apt-cache show libreoffice Package: libreoffice Architecture: amd64 Version: 1:6.0.7-0ubuntu0.18.04.10 Priority: optional Section: universe/editors Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Debian LibreOffice Maintainers Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 103 ... $ apt-cache show libreoffice-base Package: libreoffice-base Architecture: amd64 Version: 1:6.0.7-0ubuntu0.18.04.10 Priority: optional Section: universe/database Source: libreoffice Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Debian LibreOffice Maintainers Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 8928 ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1858165/+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 2037599] Re: [D13.5 MFF Luxor Low] System didn't enter s0ix.
** Package changed: gnome-shell (Ubuntu) => 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/2037599 Title: [D13.5 MFF Luxor Low] System didn't enter s0ix. Status in Ubuntu: New Bug description: [Reproduce Steps] 1. Manually Install Ubuntu 22.04 OS 2. Input "cat /sys/kernel/debug/pmc_core/substate_residencies". 3. Check the output. (please refer attached picture. 4. Put the system into suspend mode. 5. Resume system. 6. Input "cat /sys/kernel/debug/pmc_core/substate_residencies". 7. System didn't enter s0ix. --> issue occurs. [Results] Expected Result System can enter s0ix. Actual Result System didn't enter s0ix. VNP on Alexandria Low SKU. VNP on Luxor High SKU. [Additional Information] Test Vault ID: N/A Checkbox test case ID: N/A SKU:MFF MLK Luxor Low X00 BIOS Version:0.4.19 Image/Manifest:dell-bto-jammy-jellyfish-abra-X100-20230919-7 CPU i3-13100t GPU N/A WLAN: N/A Failure rate:(FR:5/5) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2037599/+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 1968040] Re: [i915] Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
Please provide a system log showing the errors: journalctl -b0 > journal.txt and attach the resulting text file here. -- 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/1968040 Title: [i915] Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] Status in GNOME Shell: New Status in Mutter: New Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.19 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: [ Workaround ] Add to /etc/environment (in Ubuntu 22.04): MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 or in Ubuntu 22.10 and later: MUTTER_DEBUG_FORCE_KMS_MODE=simple and then reboot. [ Upstream bugs ] https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5098 https://gitlab.gnome.org/GNOME/mutter/-/issues/2268 https://gitlab.gnome.org/GNOME/mutter/-/issues/2749 [ Original report ] (initially reported as a comment on bug #1965085, and split into a separate bug report) After I lock my screen and let it blank, moving the mouse or pressing any key on the keyboard won't wake it up. The only reliable workaround I've found is to press Ctrl+Alt+F1. That's on a fully up-to-date jammy, my hardware is an Intel NUC with a single Samsung monitor connected with a standard HDMI cable. This is a regression that started happening yesterday (2022-04-05) if I can remember correctly (I do apply pending updates at least once daily). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 6 15:19:30 2022 InstallationDate: Installed on 2020-09-16 (566 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-03-19 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968040/+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 2037599] Re: [D13.5 MFF Luxor Low] System didn't enter s0ix.
** Description changed: [Reproduce Steps] 1. Manually Install Ubuntu 22.04 OS 2. Input "cat /sys/kernel/debug/pmc_core/substate_residencies". 3. Check the output. (please refer attached picture. 4. Put the system into suspend mode. 5. Resume system. 6. Input "cat /sys/kernel/debug/pmc_core/substate_residencies". 7. System didn't enter s0ix. --> issue occurs. [Results] Expected Result System can enter s0ix. Actual Result System didn't enter s0ix. + VNP on Alexandria Low SKU. + VNP on Luxor High SKU. + [Additional Information] Test Vault ID: N/A Checkbox test case ID: N/A SKU:MFF MLK Luxor Low X00 BIOS Version:0.4.19 Image/Manifest:dell-bto-jammy-jellyfish-abra-X100-20230919-7 CPU i3-13100t GPU N/A WLAN: N/A Failure rate:(FR:5/5) -- 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/2037599 Title: [D13.5 MFF Luxor Low] System didn't enter s0ix. Status in gnome-shell package in Ubuntu: New Bug description: [Reproduce Steps] 1. Manually Install Ubuntu 22.04 OS 2. Input "cat /sys/kernel/debug/pmc_core/substate_residencies". 3. Check the output. (please refer attached picture. 4. Put the system into suspend mode. 5. Resume system. 6. Input "cat /sys/kernel/debug/pmc_core/substate_residencies". 7. System didn't enter s0ix. --> issue occurs. [Results] Expected Result System can enter s0ix. Actual Result System didn't enter s0ix. VNP on Alexandria Low SKU. VNP on Luxor High SKU. [Additional Information] Test Vault ID: N/A Checkbox test case ID: N/A SKU:MFF MLK Luxor Low X00 BIOS Version:0.4.19 Image/Manifest:dell-bto-jammy-jellyfish-abra-X100-20230919-7 CPU i3-13100t GPU N/A WLAN: N/A Failure rate:(FR:5/5) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037599/+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 2037599] Re: [D13.5 MFF Luxor Low] System didn't enter s0ix.
Add s0ix picture. ** Attachment added: "s0ix.PNG" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037599/+attachment/5705030/+files/s0ix.PNG -- 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/2037599 Title: [D13.5 MFF Luxor Low] System didn't enter s0ix. Status in gnome-shell package in Ubuntu: New Bug description: [Reproduce Steps] 1. Manually Install Ubuntu 22.04 OS 2. Input "cat /sys/kernel/debug/pmc_core/substate_residencies". 3. Check the output. (please refer attached picture. 4. Put the system into suspend mode. 5. Resume system. 6. Input "cat /sys/kernel/debug/pmc_core/substate_residencies". 7. System didn't enter s0ix. --> issue occurs. [Results] Expected Result System can enter s0ix. Actual Result System didn't enter s0ix. VNP on Alexandria Low SKU. VNP on Luxor High SKU. [Additional Information] Test Vault ID: N/A Checkbox test case ID: N/A SKU:MFF MLK Luxor Low X00 BIOS Version:0.4.19 Image/Manifest:dell-bto-jammy-jellyfish-abra-X100-20230919-7 CPU i3-13100t GPU N/A WLAN: N/A Failure rate:(FR:5/5) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037599/+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 2037538] Re: GNOME Freezes, Alt+F2 not even responding. Mouse Cursor Tracks, but can't click.
Please also try deleting locally installed extensions: cd ~/.local/share/gnome-shell/ rm -rf extensions and then reboot. -- 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/2037538 Title: GNOME Freezes, Alt+F2 not even responding. Mouse Cursor Tracks, but can't click. Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 22.04.3 LTS gnome-shell[3218]: Can't update stage views actor [:0x555e5db5c350] is on because it needs an allocation. gnome-shell[3218]: Can't update stage views actor [:0x555e5fe0d310] is on because it needs an allocation. gnome-shell[3218]: Can't update stage views actor [:0x555e5fe106d0] is on because it needs an allocation. gnome-shell[3218]: Can't update stage views actor [:0x555e5db5c350] is on because it needs an allocation. gnome-shell[3218]: Can't update stage views actor [:0x555e5fe0d310] is on because it needs an allocation. gnome-shell[3218]: Can't update stage views actor [:0x555e5fe106d0] is on because it needs an allocation. gnome-shell[5794]: [5788:5825:0927/071652.214702:ERROR:nss_util.cc(357)] After loading Root Certs, loaded==false: NSS error code: -8018 Also, getting stack traces every time I open Activities by click or super button. I removed all User-Installed Extensions, and have also tried disabling the default System Extensions with no change. JS ERROR: TypeError: workspace is undefined#012_getSpacing@resource:///org/gnome/shell/ui/workspacesView.js:213:13#012vfunc_allocate@resource:///org/gnome/shell/ui/workspacesView.js:339:18#012vfunc_allocate@resource:///org/gnome/shell/ui/workspacesView.js:711:30#012removeWindow@resource:///org/gnome/shell/ui/workspace.js:855:29#012addWindow/<.destroyId<@resource:///org/gnome/shell/ui/workspace.js:806:22#012vfunc_hide@resource:///org/gnome/shell/ui/workspacesView.js:1016:38#012vfunc_unmap@resource:///org/gnome/shell/ui/overviewControls.js:715:33#012hideOverview@resource:///org/gnome/shell/ui/layout.js:347:28#012_hideDone@resource:///org/gnome/shell/ui/overview.js:641:32#012_animateNotVisible/<@resource:///org/gnome/shell/ui/overview.js:624:55#012onStopped@resource:///org/gnome/shell/ui/overviewControls.js:757:21#012_makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:151:22#012_easeActorProperty/<@resource:///org/gnome/shell/ui/environment.js:317:60 gnome-shell[3218]: Object St.Button (0x555e5dc62c60), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. gnome-shell[3218]: == Stack trace for context 0x555e5d657170 == gnome-shell[3218]: #0 555e5deb4708 i resource:///org/gnome/shell/ui/windowPreview.js:566 (20a2bc50b650 @ 10) gnome-shell[3218]: == Stack trace for context 0x555e5d657170 == gnome-shell[3218]: #0 555e5deb4708 i resource:///org/gnome/shell/ui/windowPreview.js:567 (20a2bc50b650 @ 36) gnome-shell[3218]: == Stack trace for context 0x555e5d657170 == gnome-shell[3218]: #0 555e5deb4708 i resource:///org/gnome/shell/ui/windowPreview.js:570 (20a2bc50b650 @ 77) gnome-shell[3218]: Object St.Label (0x555e5df247a0), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. gnome-shell[3218]: Object .Gjs_ui_windowPreview_WindowPreview (0x555e5ed83d30), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 27 07:19:09 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-08-15 (42 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.9-0ubuntu4 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037538/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 2037599] Re: [D13.5 MFF Luxor Low] System didn't enter s0ix.
add sosreport. ** Attachment added: "sosreport-u-OptiPlex-Micro-7020-2023-09-27-uuprzcb.tar.xz" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037599/+attachment/5705032/+files/sosreport-u-OptiPlex-Micro-7020-2023-09-27-uuprzcb.tar.xz -- 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/2037599 Title: [D13.5 MFF Luxor Low] System didn't enter s0ix. Status in gnome-shell package in Ubuntu: New Bug description: [Reproduce Steps] 1. Manually Install Ubuntu 22.04 OS 2. Input "cat /sys/kernel/debug/pmc_core/substate_residencies". 3. Check the output. (please refer attached picture. 4. Put the system into suspend mode. 5. Resume system. 6. Input "cat /sys/kernel/debug/pmc_core/substate_residencies". 7. System didn't enter s0ix. --> issue occurs. [Results] Expected Result System can enter s0ix. Actual Result System didn't enter s0ix. VNP on Alexandria Low SKU. VNP on Luxor High SKU. [Additional Information] Test Vault ID: N/A Checkbox test case ID: N/A SKU:MFF MLK Luxor Low X00 BIOS Version:0.4.19 Image/Manifest:dell-bto-jammy-jellyfish-abra-X100-20230919-7 CPU i3-13100t GPU N/A WLAN: N/A Failure rate:(FR:5/5) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037599/+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 2037599] [NEW] [D13.5 MFF Luxor Low] System didn't enter s0ix.
Public bug reported: [Reproduce Steps] 1. Manually Install Ubuntu 22.04 OS 2. Input "cat /sys/kernel/debug/pmc_core/substate_residencies". 3. Check the output. (please refer attached picture. 4. Put the system into suspend mode. 5. Resume system. 6. Input "cat /sys/kernel/debug/pmc_core/substate_residencies". 7. System didn't enter s0ix. --> issue occurs. [Results] Expected Result System can enter s0ix. Actual Result System didn't enter s0ix. VNP on Alexandria Low SKU. VNP on Luxor High SKU. [Additional Information] Test Vault ID: N/A Checkbox test case ID: N/A SKU:MFF MLK Luxor Low X00 BIOS Version:0.4.19 Image/Manifest:dell-bto-jammy-jellyfish-abra-X100-20230919-7 CPU i3-13100t GPU N/A WLAN: N/A Failure rate:(FR:5/5) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: jellyfish-abra odm-bug white-whale ** Tags added: jellyfish-abra odm-bug white-whale -- 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/2037599 Title: [D13.5 MFF Luxor Low] System didn't enter s0ix. Status in gnome-shell package in Ubuntu: New Bug description: [Reproduce Steps] 1. Manually Install Ubuntu 22.04 OS 2. Input "cat /sys/kernel/debug/pmc_core/substate_residencies". 3. Check the output. (please refer attached picture. 4. Put the system into suspend mode. 5. Resume system. 6. Input "cat /sys/kernel/debug/pmc_core/substate_residencies". 7. System didn't enter s0ix. --> issue occurs. [Results] Expected Result System can enter s0ix. Actual Result System didn't enter s0ix. VNP on Alexandria Low SKU. VNP on Luxor High SKU. [Additional Information] Test Vault ID: N/A Checkbox test case ID: N/A SKU:MFF MLK Luxor Low X00 BIOS Version:0.4.19 Image/Manifest:dell-bto-jammy-jellyfish-abra-X100-20230919-7 CPU i3-13100t GPU N/A WLAN: N/A Failure rate:(FR:5/5) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037599/+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 2037182] Re: Restarting GNOME doesn't work
Please also try deleting locally installed extensions: cd ~/.local/share/gnome-shell/ rm -rf extensions and then reboot. -- 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/2037182 Title: Restarting GNOME doesn't work Status in gnome-shell package in Ubuntu: Incomplete Bug description: Triggering a restart through Alt-F2 then "r" causes GNOME to hang for a few seconds before going to the "something went wrong" screen prompting the user to log out. But once you log out and back in, the system still has issues, with application now taking far longer to launch. This is ultimately resolved by a full system restart. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Sep 23 14:56:37 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-08-02 (53 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-09-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037182/+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 2037182] Re: Restarting GNOME doesn't work
Please follow steps 2 and 3 in comment #2. ** Tags added: hybrid i915 multigpu nvidia -- 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/2037182 Title: Restarting GNOME doesn't work Status in gnome-shell package in Ubuntu: Incomplete Bug description: Triggering a restart through Alt-F2 then "r" causes GNOME to hang for a few seconds before going to the "something went wrong" screen prompting the user to log out. But once you log out and back in, the system still has issues, with application now taking far longer to launch. This is ultimately resolved by a full system restart. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Sep 23 14:56:37 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-08-02 (53 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-09-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037182/+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 2037182] Re: Restarting GNOME doesn't work
Here's the system logs, the restart occurred at 22:34 on Sep 27. ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037182/+attachment/5705029/+files/journal.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/2037182 Title: Restarting GNOME doesn't work Status in gnome-shell package in Ubuntu: Incomplete Bug description: Triggering a restart through Alt-F2 then "r" causes GNOME to hang for a few seconds before going to the "something went wrong" screen prompting the user to log out. But once you log out and back in, the system still has issues, with application now taking far longer to launch. This is ultimately resolved by a full system restart. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Sep 23 14:56:37 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-08-02 (53 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-09-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037182/+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 2037307] Re: Dragging the top activities/time bar freezes GNOME completely (Xorg session)
** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2037307 Title: Dragging the top activities/time bar freezes GNOME completely (Xorg session) Status in gnome-shell package in Ubuntu: New Bug description: If you use a touchscreen and drag a finger down on the very top bar (with the time and the former activities button), GNOME will completely freeze. The mouse cursor will be locked in the "drag" state. All keyboard input (including Alt-F2) will be ignored. The only way to escape this state is to switch into a virtual console and kill the current program. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 25 12:33:44 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-08-02 (55 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-09-23 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037307/+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 2037307] Re: Dragging the top activities/time bar freezes GNOME completely (Xorg session)
The foreground app. -- 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/2037307 Title: Dragging the top activities/time bar freezes GNOME completely (Xorg session) Status in gnome-shell package in Ubuntu: Incomplete Bug description: If you use a touchscreen and drag a finger down on the very top bar (with the time and the former activities button), GNOME will completely freeze. The mouse cursor will be locked in the "drag" state. All keyboard input (including Alt-F2) will be ignored. The only way to escape this state is to switch into a virtual console and kill the current program. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 25 12:33:44 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-08-02 (55 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-09-23 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037307/+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 2037538] Re: GNOME Freezes, Alt+F2 not even responding. Mouse Cursor Tracks, but can't click.
Please also check to see if the freeze is related to switching workspaces (bug 2000644). ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2037538 Title: GNOME Freezes, Alt+F2 not even responding. Mouse Cursor Tracks, but can't click. Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 22.04.3 LTS gnome-shell[3218]: Can't update stage views actor [:0x555e5db5c350] is on because it needs an allocation. gnome-shell[3218]: Can't update stage views actor [:0x555e5fe0d310] is on because it needs an allocation. gnome-shell[3218]: Can't update stage views actor [:0x555e5fe106d0] is on because it needs an allocation. gnome-shell[3218]: Can't update stage views actor [:0x555e5db5c350] is on because it needs an allocation. gnome-shell[3218]: Can't update stage views actor [:0x555e5fe0d310] is on because it needs an allocation. gnome-shell[3218]: Can't update stage views actor [:0x555e5fe106d0] is on because it needs an allocation. gnome-shell[5794]: [5788:5825:0927/071652.214702:ERROR:nss_util.cc(357)] After loading Root Certs, loaded==false: NSS error code: -8018 Also, getting stack traces every time I open Activities by click or super button. I removed all User-Installed Extensions, and have also tried disabling the default System Extensions with no change. JS ERROR: TypeError: workspace is undefined#012_getSpacing@resource:///org/gnome/shell/ui/workspacesView.js:213:13#012vfunc_allocate@resource:///org/gnome/shell/ui/workspacesView.js:339:18#012vfunc_allocate@resource:///org/gnome/shell/ui/workspacesView.js:711:30#012removeWindow@resource:///org/gnome/shell/ui/workspace.js:855:29#012addWindow/<.destroyId<@resource:///org/gnome/shell/ui/workspace.js:806:22#012vfunc_hide@resource:///org/gnome/shell/ui/workspacesView.js:1016:38#012vfunc_unmap@resource:///org/gnome/shell/ui/overviewControls.js:715:33#012hideOverview@resource:///org/gnome/shell/ui/layout.js:347:28#012_hideDone@resource:///org/gnome/shell/ui/overview.js:641:32#012_animateNotVisible/<@resource:///org/gnome/shell/ui/overview.js:624:55#012onStopped@resource:///org/gnome/shell/ui/overviewControls.js:757:21#012_makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:151:22#012_easeActorProperty/<@resource:///org/gnome/shell/ui/environment.js:317:60 gnome-shell[3218]: Object St.Button (0x555e5dc62c60), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. gnome-shell[3218]: == Stack trace for context 0x555e5d657170 == gnome-shell[3218]: #0 555e5deb4708 i resource:///org/gnome/shell/ui/windowPreview.js:566 (20a2bc50b650 @ 10) gnome-shell[3218]: == Stack trace for context 0x555e5d657170 == gnome-shell[3218]: #0 555e5deb4708 i resource:///org/gnome/shell/ui/windowPreview.js:567 (20a2bc50b650 @ 36) gnome-shell[3218]: == Stack trace for context 0x555e5d657170 == gnome-shell[3218]: #0 555e5deb4708 i resource:///org/gnome/shell/ui/windowPreview.js:570 (20a2bc50b650 @ 77) gnome-shell[3218]: Object St.Label (0x555e5df247a0), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. gnome-shell[3218]: Object .Gjs_ui_windowPreview_WindowPreview (0x555e5ed83d30), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 27 07:19:09 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-08-15 (42 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.9-0ubuntu4 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037538/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help
[Desktop-packages] [Bug 2037538] Re: GNOME Freezes, Alt+F2 not even responding. Mouse Cursor Tracks, but can't click.
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Run these commands: journalctl -b0 > journal.txt journalctl -b-1 > prevjournal.txt and attach the resulting text files here. 2. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 3. If step 2 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. -- 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/2037538 Title: GNOME Freezes, Alt+F2 not even responding. Mouse Cursor Tracks, but can't click. Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 22.04.3 LTS gnome-shell[3218]: Can't update stage views actor [:0x555e5db5c350] is on because it needs an allocation. gnome-shell[3218]: Can't update stage views actor [:0x555e5fe0d310] is on because it needs an allocation. gnome-shell[3218]: Can't update stage views actor [:0x555e5fe106d0] is on because it needs an allocation. gnome-shell[3218]: Can't update stage views actor [:0x555e5db5c350] is on because it needs an allocation. gnome-shell[3218]: Can't update stage views actor [:0x555e5fe0d310] is on because it needs an allocation. gnome-shell[3218]: Can't update stage views actor [:0x555e5fe106d0] is on because it needs an allocation. gnome-shell[5794]: [5788:5825:0927/071652.214702:ERROR:nss_util.cc(357)] After loading Root Certs, loaded==false: NSS error code: -8018 Also, getting stack traces every time I open Activities by click or super button. I removed all User-Installed Extensions, and have also tried disabling the default System Extensions with no change. JS ERROR: TypeError: workspace is undefined#012_getSpacing@resource:///org/gnome/shell/ui/workspacesView.js:213:13#012vfunc_allocate@resource:///org/gnome/shell/ui/workspacesView.js:339:18#012vfunc_allocate@resource:///org/gnome/shell/ui/workspacesView.js:711:30#012removeWindow@resource:///org/gnome/shell/ui/workspace.js:855:29#012addWindow/<.destroyId<@resource:///org/gnome/shell/ui/workspace.js:806:22#012vfunc_hide@resource:///org/gnome/shell/ui/workspacesView.js:1016:38#012vfunc_unmap@resource:///org/gnome/shell/ui/overviewControls.js:715:33#012hideOverview@resource:///org/gnome/shell/ui/layout.js:347:28#012_hideDone@resource:///org/gnome/shell/ui/overview.js:641:32#012_animateNotVisible/<@resource:///org/gnome/shell/ui/overview.js:624:55#012onStopped@resource:///org/gnome/shell/ui/overviewControls.js:757:21#012_makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:151:22#012_easeActorProperty/<@resource:///org/gnome/shell/ui/environment.js:317:60 gnome-shell[3218]: Object St.Button (0x555e5dc62c60), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. gnome-shell[3218]: == Stack trace for context 0x555e5d657170 == gnome-shell[3218]: #0 555e5deb4708 i resource:///org/gnome/shell/ui/windowPreview.js:566 (20a2bc50b650 @ 10) gnome-shell[3218]: == Stack trace for context 0x555e5d657170 == gnome-shell[3218]: #0 555e5deb4708 i resource:///org/gnome/shell/ui/windowPreview.js:567 (20a2bc50b650 @ 36) gnome-shell[3218]: == Stack trace for context 0x555e5d657170 == gnome-shell[3218]: #0 555e5deb4708 i resource:///org/gnome/shell/ui/windowPreview.js:570 (20a2bc50b650 @ 77) gnome-shell[3218]: Object St.Label (0x555e5df247a0), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. gnome-shell[3218]: Object .Gjs_ui_windowPreview_WindowPreview (0x555e5ed83d30), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 27 07:19:09 2023 DisplayManager: gdm3
[Desktop-packages] [Bug 2037307] Re: Dragging the top activities/time bar freezes GNOME completely
When you say the workaround is to "kill the current program" do you mean the foreground app or the shell? ** Summary changed: - Dragging the top activities/time bar freezes GNOME completely + Dragging the top activities/time bar freezes GNOME completely (Xorg session] ** Summary changed: - Dragging the top activities/time bar freezes GNOME completely (Xorg session] + Dragging the top activities/time bar freezes GNOME completely (Xorg 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/2037307 Title: Dragging the top activities/time bar freezes GNOME completely (Xorg session) Status in gnome-shell package in Ubuntu: Incomplete Bug description: If you use a touchscreen and drag a finger down on the very top bar (with the time and the former activities button), GNOME will completely freeze. The mouse cursor will be locked in the "drag" state. All keyboard input (including Alt-F2) will be ignored. The only way to escape this state is to switch into a virtual console and kill the current program. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 25 12:33:44 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-08-02 (55 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-09-23 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037307/+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 1532508] Re: Screen contents revealed briefly on resume, before even unlocking
** Tags removed: mantic -- 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/1532508 Title: Screen contents revealed briefly on resume, before even unlocking Status in GNOME Shell: New Status in Mutter: New Status in gnome-shell package in Ubuntu: Confirmed Status in unity package in Ubuntu: Fix Released Status in unity source package in Xenial: Fix Released Status in gnome-shell package in Debian: Confirmed Bug description: [Impact] When lock is enabled, the screen doesn't get blank/covered by lockscreen before suspending, thus on early resume the content might be shown. Video showing the bug: https://youtu.be/dDOgtK1MldI Reproduced on Ubuntu 2015.10, Ubuntu 2014.04 [Test case] 1. Work on highly secret files 2. Close the lid of your laptop and go have a break 3. Anyone who opens the lid of the laptop can see the secret files for a half second before the lock screen appears [Possible Regression] Content on screen isn't painted anymore and screen stays black. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1532508/+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 2037191] Re: Lockscreen sometimes doesn't render
** This bug is no longer a duplicate of bug 1532508 Screen contents revealed briefly on resume, before even unlocking ** Summary changed: - Lockscreen sometimes doesn't render + Screen is sometimes not locked when opening the laptop lid ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New ** Summary changed: - Screen is sometimes not locked when opening the laptop lid + Lockscreen sometimes doesn't render (input is locked but desktop visible) ** Information type changed from Public to Public Security ** Summary changed: - Lockscreen sometimes doesn't render (input is locked but desktop visible) + Lock screen sometimes doesn't render (input is locked but desktop visible) -- 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/2037191 Title: Lock screen sometimes doesn't render (input is locked but desktop visible) Status in gnome-shell package in Ubuntu: New Bug description: Sometimes when I unlock my laptop by opening the lid, the touchscreen just doesn't render. This renders the system completely frozen until I go into a TTY and run "sudo loginctl unlock-sessions". But that's not the real problem. The real problem is that while the lock-screen doesn't render, *everything* else does. This means that while I wasn't logged in, Firefox and all other open applications were completely visible. This is obviously a big issue if one has sensitive information open. There does not seem to be a reliable way to reproduce this, it just happens sometimes. So far, I've experienced this twice, once on 23.04 and once on the 23.10 beta. There are however, some really suspicious error messages in the logs: Sep 23 17:31:26 user-83BV gnome-shell[2000]: == Stack trace for context 0x564e3e5286b0 == Sep 23 17:31:26 user-83BV gnome-shell[2000]: #0 564e3e6415e8 i resource:///org/gnome/shell/ui/keyboard.js:1809 (3e69d1677920 @ 73) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #1 564e3e641558 i resource:///org/gnome/shell/ui/keyboard.js:1941 (3e69d1677e20 @ 43) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #2 564e3e6414d8 i resource:///org/gnome/shell/ui/keyboard.js:1931 (3e69d1677dd0 @ 28) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #3 564e3e641448 i resource:///org/gnome/shell/ui/init.js:21 (2f81e37d060 @ 48) Sep 23 17:31:26 user-83BV gnome-shell[2000]: == Stack trace for context 0x564e3e5286b0 == Sep 23 17:31:26 user-83BV gnome-shell[2000]: #0 564e3e6415e8 i resource:///org/gnome/shell/ui/keyboard.js:1812 (3e69d1677920 @ 124) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #1 564e3e641558 i resource:///org/gnome/shell/ui/keyboard.js:1941 (3e69d1677e20 @ 43) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #2 564e3e6414d8 i resource:///org/gnome/shell/ui/keyboard.js:1931 (3e69d1677dd0 @ 28) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #3 564e3e641448 i resource:///org/gnome/shell/ui/init.js:21 (2f81e37d060 @ 48) Sep 23 17:31:26 user-83BV gnome-shell[2000]: == Stack trace for context 0x564e3e5286b0 == Sep 23 17:31:26 user-83BV gnome-shell[2000]: #0 564e3e6415e8 i resource:///org/gnome/shell/ui/keyboard.js:1988 (3e69d1677fb0 @ 112) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #1 564e3e641558 i resource:///org/gnome/shell/ui/keyboard.js:1942 (3e69d1677e20 @ 58) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #2 564e3e6414d8 i resource:///org/gnome/shell/ui/keyboard.js:1931 (3e69d1677dd0 @ 28) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #3 564e3e641448 i resource:///org/gnome/shell/ui/init.js:21 (2f81e37d060 @ 48) Sep 23 17:31:26 user-83BV gnome-shell[2000]: == Stack trace for context 0x564e3e5286b0 == Sep 23 17:31:26 user-83BV gnome-shell[2000]: #0 564e3e641710 i resource:///org/gnome/shell/ui/environment.js:112 (2f81e37d600 @ 43) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #1 564e3e641678 i resource:///org/gnome/shell/ui/environment.js:297 (2f81e37dce0 @ 19) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #2 564e3e6415e8 i resource:///org/gnome/shell/ui/keyboard.js:1987 (3e69d1677fb0 @ 176) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #3 564e3e641558 i resource:///org/gnome/shell/ui/keyboard.js:1942 (3e69d1677e20 @ 58) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #4 564e3e6414d8 i resource:///org/gnome/shell/ui/keyboard.js:1931 (3e69d1677dd0 @ 28) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #5 564e3e641448 i resource:///org/gnome/shell/ui/init.js:21 (2f81e37d060 @ 48) Sep 23 17:31:26 user-83BV gnome-shell[2000]: == Stack trace for context 0x564e3e5286b0 == Sep 23 17:31:26 user-83BV gnome-shell[2000]: #0 564e3e6417e0 i resource:///org/gnome/shell/ui/environment.js:289 (2f81e37dc40 @ 39) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #1 564e3e641710 i resource:///org/gnome/shell/ui/environment.js:115 (2f81e37d600 @ 91) Sep
[Desktop-packages] [Bug 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland
** Summary changed: - [amdgpu] gnome-shell gets SIGKILL'd when lock screen in Wayland + [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland -- 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/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland Status in Linux: New Status in Mutter: New Status in X.Org X server: Fix Released Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: In Progress Status in linux source package in Mantic: Confirmed Status in mutter source package in Mantic: In Progress Bug description: [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_KMS_THREAD_TYPE=user and then reboot. [ Original Description] I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. All works in xorg. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 22:32:22 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-03 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+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 2037460] Re: gnome-shell crash
*** This bug is a duplicate of bug 2034619 *** https://bugs.launchpad.net/bugs/2034619 I can see three bugs there: 1. "bijiben-shell-s... segfault" -> bug 2012985 2. "org.gnome.Shell@wayland.service: Main process exited, code=killed, status=9/KILL" -> bug 2034619 3. "Cursor update failed: drmModeAtomicCommit: Invalid argument" though the shell kept running for hours after that so it wasn't fatal. I think most likely #2 is the main problem here. ** This bug has been marked a duplicate of bug 2034619 [amdgpu] gnome-shell gets SIGKILL'd when lock screen in Wayland -- 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/2037460 Title: gnome-shell crash Status in gnome-shell package in Ubuntu: New Bug description: gnome shell crashed when switching workspaces to check out the new 'activities' workspace indicator functionality. it also crashed when starting ms teams, not sure if that's the same bug? ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Sep 26 11:28:15 2023 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-17 (1502 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) RelatedPackageVersions: mutter-common 45.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-09-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037460/+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 2029913] Re: [SRU request] Update Thunderbird to 115.x (as 102.x is EOL)
Now we have reached the point, from which security vulnerabilities rated as "high" will stay unfixed in Thunderbird 102! https://www.mozilla.org/en-US/security/advisories/mfsa2023-43/ The CVEs CVE-2023-5169, CVE-2023-5171 and CVE-2023-5176 got fixed in Thunderbird 115.3 but stay open in TB 102. So please don't wait any longer and push TB 115.3! ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-5169 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-5171 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-5176 ** CVE removed: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-4045 ** CVE removed: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-4046 ** CVE removed: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-4047 ** CVE removed: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-4048 ** CVE removed: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-4049 ** CVE removed: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-4050 ** CVE removed: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-4054 ** CVE removed: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-4055 ** CVE removed: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-4056 ** CVE removed: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-4573 ** CVE removed: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-4574 ** CVE removed: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-4575 ** CVE removed: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-4576 ** CVE removed: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-4581 ** CVE removed: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-4584 ** CVE removed: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-4863 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/2029913 Title: [SRU request] Update Thunderbird to 115.x (as 102.x is EOL) Status in thunderbird package in Ubuntu: Confirmed Bug description: [ Impact ] * The Thunderbird 102.x series has its final release (12.15.0) planned for release on August 30th. After that, the 102.x series will no longer receive critical security updates. Due to the size and complexity of the Mozilla/Thunderbird codebase, it is extremely unlikely that the Ubuntu team could take on the task of backporting patches to new security issues once official support for the 102.x series has ended. * Updating to Thunderbird 115.x in all currently-supported Ubuntu releases will make sure users stay secure. * It should be noted that 115.x does make changes to the interface. While all these changes are ostensibly for the better, normally this level of change would disqualify an application from getting SRUed. However, running an EOL email client is a security/privacy risk to users that can't be ignored. * Official post detailing the interface changes: https://www.thunderbird.net/en-US/thunderbird/115.0/whatsnew/ * Official changelog for 115.0 release: https://www.thunderbird.net/en-US/thunderbird/115.0/releasenotes/ * Official changelog for 115.1 bugfix release: https://www.thunderbird.net/en-US/thunderbird/115.1.0/releasenotes/ [ Test Plan ] Not sure, I'm just a user [ Where problems could occur ] * New major release, usual concerns apply [ Other Info ] * I'm guessing that this SRU was already planned to happen eventually, but since I couldn't find an official request, here we are To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2029913/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 2013236] Re: b43 driver conflicts with bcmwl driver for some Broadcom devices
On Thu, Sep 28, 2023 at 12:34:34AM -, Steve Langasek wrote: > On Wed, Sep 27, 2023 at 11:16:52PM -, Brian Murray wrote: > > However, using software-properties-gtk to install the proprietary driver > > (broadcom-sta-dkms) worked and the b43 driver was blacklisted and I was > > able to connect to a wireless network. > > Does this mean the driver was not offered to you automatically through > ubuntu-drivers-common? I'm not exactly sure what you mean by automatically. The b43 was driver was the in use after installing and rebooting. `ubuntu-drivers list` does show broadcom-sta-dkms as an option however, running `ubuntu-drivers install` indicates that "All the available drivers are already installed". -- Brian Murray -- 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/2013236 Title: b43 driver conflicts with bcmwl driver for some Broadcom devices Status in broadcom-sta package in Ubuntu: New Status in linux-firmware package in Ubuntu: Invalid Status in ubuntu-drivers-common package in Ubuntu: Incomplete Status in broadcom-sta source package in Lunar: New Status in linux-firmware source package in Lunar: Invalid Status in ubuntu-drivers-common source package in Lunar: Incomplete Status in broadcom-sta source package in Mantic: New Status in linux-firmware source package in Mantic: Invalid Status in ubuntu-drivers-common source package in Mantic: Incomplete Bug description: Specifically for Lunar - using a Macbook Air 2012, its wireless driver was not enabled even though I ticked the wireless tickbox on the installer. A quick look at the installer logs reveals various issues syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [ 43.063747] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [ 43.063802] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063862] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063908] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 I will attach the installer logs manually since this was captured after the installation Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was installed correctly during the install so this is a regression with the 6.2 kernel Workaround -- You'll first need to blacklist the b43 driver by adding a blacklist file to /etc/modprobe.d/b43.conf with the contents "blacklist b43". Then run "update-initramfs -u". Then install the bcmwl-kernel-source package. After a reboot your wireless device should be available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2013236/+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 2037540] Re: system extension light style is not working
** Package changed: gnome-shell (Ubuntu) => gnome-shell-extensions (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/2037540 Title: system extension light style is not working Status in gnome-shell-extensions package in Ubuntu: New Bug description: Trying to enable light style gnome shell system extension is not working. What should happen is that light style should be enabled: when pressing the super button, a light-not black background should be displayed. lsb_release -rd: Description: Ubuntu Mantic Minotaur (development branch) Release: 23.10 apt-cache policy gnome-shell: gnome-shell: Installed: 45.0-1ubuntu1 Candidate: 45.0-1ubuntu1 Version table: *** 45.0-1ubuntu1 500 500 http://gr.archive.ubuntu.com/ubuntu mantic/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extensions/+bug/2037540/+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 2037569] Re: udev issues with mantic beta
Spent some time analyzing this. Frank loaned me a test system. The test system in the "idle" state is enough to see the issue, with a persistent load of 3+ when nothing is happening except event loop spin. The test system is using a dasd as the disk that it is running from. With some udev tracing, one can see an apparent loop, with udisks2 opening /dev/dasda, which triggers an inotify, which triggers udev rules, which trigger udisks2 again, or something similar to this flow. Workarounds include: * adding a nowatch rule 'ACTION=="add|change", KERNEL=="dasd*", OPTIONS:="nowatch"' * systemctl stop udisks2 I've begun exploring udev changes for udisks2 to ignore dasd. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/2037569 Title: udev issues with mantic beta Status in Ubuntu on IBM z Systems: New Status in systemd package in Ubuntu: Confirmed Status in udisks2 package in Ubuntu: Confirmed Bug description: While installing mantic beta (on s390x, LPAR and z/VM - but this might not be architecture specific) I faced issues with udev. In my installation I've updated the installer to "edge/lp-2009141" (subiquity 22.02.2+git1762.1b1ee6f4 5164). During my installations I first noticed bad response times in case of dealing with devices (like enabling new devices with chzdev). chzdev is used during the installation, hence the installation procedure is also affected by this. (I mainly notice this issue in case of DASD ECKD disk enablements.) But even after after a successful (but due to this issue less snappier) installation, means after the post-install reboot, in the installed system I can find several udev related processes, like: 69448 root 20 0 31280 11944 2560 S 39.2 0.0 2:51.67 (udev-worker) 509 root 20 0 31276 13812 4600 S 20.6 0.0 2:07.76 systemd-udevd 893 root 20 0 469016 13544 10496 R 17.3 0.0 1:43.53 udisksd 1 root 20 0 168664 12748 8396 S 16.3 0.0 1:40.47 systemd which is not only unusual, but (as one can see) they consume quite some resources. Even the remote ssh into that system is impacted by this high load. So far I only see this in mantic. I tried 20.04.3 as well as lunar, but both do not seem to be affected by this udev problem. I neither face the bad response on device enablement, nor can see any udev related processes still running after post-install-reboot in the installed system. (Sometimes I could also see a growing log file 'syslog'). I cannot say yet what is causing this, but since I see 'systemd-udevd' as prominent process in top, I'll first of all mark this as affecting systemd-udevd (or systemd). I've attached the outcome of some more investigations I did ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2037569/+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 2037510] Re: MPV Player doesn't get paused on Teams Call
** Changed in: mpv (Ubuntu) Status: New => Opinion ** Changed in: chromium-browser (Ubuntu) Status: New => Opinion ** Changed in: chromium-browser (Ubuntu) Importance: Undecided => Wishlist ** Changed in: mpv (Ubuntu) Importance: Undecided => Wishlist -- 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/2037510 Title: MPV Player doesn't get paused on Teams Call Status in chromium-browser package in Ubuntu: Opinion Status in mpv package in Ubuntu: Opinion Bug description: Issue:- Audio/Video played on MPV Player or YouTube on chromium browser doesn't get paused on getting Microsoft Teams Call. Expected:- Audio/Video played on MPV player or YouTube on chromium browser should get paused on getting Microsoft Teams Call. Support:- Audio/Video played on VLC player/ Rhythem box player/Totem player get paused on getting Microsoft teams Call. Steps To Reproduce the Issue 1. Play any Audio/Video either on YouTube on Chromium/MPV player. 2. Get login to Microsoft teams Application/Web Application. 3. Get a call on Teams. Expected :- Audio/Video played on the Application should get paused. Actuall :- Audio/Video played on the Application is not getting paused. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2037510/+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 2037349] Re: package cups 2.4.1op1-1ubuntu4.7 failed to install/upgrade: installed cups package post-installation script subprocess returned error exit status 1
** Package changed: ubuntu => cups (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2037349 Title: package cups 2.4.1op1-1ubuntu4.7 failed to install/upgrade: installed cups package post-installation script subprocess returned error exit status 1 Status in cups package in Ubuntu: New Bug description: DOnt know, but crome always cras, i migt be infected ProblemType: Package DistroRelease: Ubuntu 22.04 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CupsErrorLog: Date: Thu Sep 21 06:28:18 2023 DuplicateSignature: package:cups:2.4.1op1-1ubuntu4.7 Setting up cups (2.4.1op1-1ubuntu4.7) ... debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable dpkg: error processing package cups (--configure): installed cups package post-installation script subprocess returned error exit status 1 ErrorMessage: installed cups package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-04-06 (172 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 003: ID 05c8:03ab Cheng Uei Precision Industry Co., Ltd (Foxlink) HP Wide Vision HD Camera Bus 001 Device 002: ID 145f:02d7 Trust Trust Wireless Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion Power Laptop 15-cb0xx Papersize: a4 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic root=UUID=23c97043-a6af-4600-a6fe-bae17d889351 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic root=UUID=23c97043-a6af-4600-a6fe-bae17d889351 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.10 Snap: cups 2.4.6-4 (stable) Snap.Changes: no changes found Title: package cups 2.4.1op1-1ubuntu4.7 failed to install/upgrade: installed cups package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2020 dmi.bios.release: 15.41 dmi.bios.vendor: Insyde dmi.bios.version: F.41 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 836B dmi.board.vendor: HP dmi.board.version: 46.24 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 46.24 dmi.modalias: dmi:bvnInsyde:bvrF.41:bd12/01/2020:br15.41:efr46.24:svnHP:pnHPPavilionPowerLaptop15-cb0xx:pvrType1ProductConfigId:rvnHP:rn836B:rvr46.24:cvnHP:ct10:cvrChassisVersion:sku2CK98EA#ABE: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Power Laptop 15-cb0xx dmi.product.sku: 2CK98EA#ABE dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2037349/+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 2037510] Re: MPV Player doesn't get paused on Teams Call
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 2037510 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. Please note that you omitted to tell us which release of Ubuntu you are using. ** Package changed: ubuntu => mpv (Ubuntu) ** Also affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- 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/2037510 Title: MPV Player doesn't get paused on Teams Call Status in chromium-browser package in Ubuntu: New Status in mpv package in Ubuntu: New Bug description: Issue:- Audio/Video played on MPV Player or YouTube on chromium browser doesn't get paused on getting Microsoft Teams Call. Expected:- Audio/Video played on MPV player or YouTube on chromium browser should get paused on getting Microsoft Teams Call. Support:- Audio/Video played on VLC player/ Rhythem box player/Totem player get paused on getting Microsoft teams Call. Steps To Reproduce the Issue 1. Play any Audio/Video either on YouTube on Chromium/MPV player. 2. Get login to Microsoft teams Application/Web Application. 3. Get a call on Teams. Expected :- Audio/Video played on the Application should get paused. Actuall :- Audio/Video played on the Application is not getting paused. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2037510/+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 2037349] [NEW] package cups 2.4.1op1-1ubuntu4.7 failed to install/upgrade: installed cups package post-installation script subprocess returned error exit status 1
You have been subscribed to a public bug: DOnt know, but crome always cras, i migt be infected ProblemType: Package DistroRelease: Ubuntu 22.04 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CupsErrorLog: Date: Thu Sep 21 06:28:18 2023 DuplicateSignature: package:cups:2.4.1op1-1ubuntu4.7 Setting up cups (2.4.1op1-1ubuntu4.7) ... debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable dpkg: error processing package cups (--configure): installed cups package post-installation script subprocess returned error exit status 1 ErrorMessage: installed cups package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-04-06 (172 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 003: ID 05c8:03ab Cheng Uei Precision Industry Co., Ltd (Foxlink) HP Wide Vision HD Camera Bus 001 Device 002: ID 145f:02d7 Trust Trust Wireless Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion Power Laptop 15-cb0xx Papersize: a4 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic root=UUID=23c97043-a6af-4600-a6fe-bae17d889351 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic root=UUID=23c97043-a6af-4600-a6fe-bae17d889351 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.10 Snap: cups 2.4.6-4 (stable) Snap.Changes: no changes found Title: package cups 2.4.1op1-1ubuntu4.7 failed to install/upgrade: installed cups package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2020 dmi.bios.release: 15.41 dmi.bios.vendor: Insyde dmi.bios.version: F.41 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 836B dmi.board.vendor: HP dmi.board.version: 46.24 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 46.24 dmi.modalias: dmi:bvnInsyde:bvrF.41:bd12/01/2020:br15.41:efr46.24:svnHP:pnHPPavilionPowerLaptop15-cb0xx:pvrType1ProductConfigId:rvnHP:rn836B:rvr46.24:cvnHP:ct10:cvrChassisVersion:sku2CK98EA#ABE: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Power Laptop 15-cb0xx dmi.product.sku: 2CK98EA#ABE dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- package cups 2.4.1op1-1ubuntu4.7 failed to install/upgrade: installed cups package post-installation script subprocess returned error exit status 1 https://bugs.launchpad.net/bugs/2037349 You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 2013236] Re: b43 driver conflicts with bcmwl driver for some Broadcom devices
On Wed, Sep 27, 2023 at 11:16:52PM -, Brian Murray wrote: > However, using software-properties-gtk to install the proprietary driver > (broadcom-sta-dkms) worked and the b43 driver was blacklisted and I was > able to connect to a wireless network. Does this mean the driver was not offered to you automatically through ubuntu-drivers-common? -- 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/2013236 Title: b43 driver conflicts with bcmwl driver for some Broadcom devices Status in broadcom-sta package in Ubuntu: New Status in linux-firmware package in Ubuntu: Invalid Status in ubuntu-drivers-common package in Ubuntu: Incomplete Status in broadcom-sta source package in Lunar: New Status in linux-firmware source package in Lunar: Invalid Status in ubuntu-drivers-common source package in Lunar: Incomplete Status in broadcom-sta source package in Mantic: New Status in linux-firmware source package in Mantic: Invalid Status in ubuntu-drivers-common source package in Mantic: Incomplete Bug description: Specifically for Lunar - using a Macbook Air 2012, its wireless driver was not enabled even though I ticked the wireless tickbox on the installer. A quick look at the installer logs reveals various issues syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [ 43.063747] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [ 43.063802] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063862] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063908] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 I will attach the installer logs manually since this was captured after the installation Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was installed correctly during the install so this is a regression with the 6.2 kernel Workaround -- You'll first need to blacklist the b43 driver by adding a blacklist file to /etc/modprobe.d/b43.conf with the contents "blacklist b43". Then run "update-initramfs -u". Then install the bcmwl-kernel-source package. After a reboot your wireless device should be available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2013236/+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 2037569] Re: udev issues with mantic beta
** Also affects: udisks2 (Ubuntu) Importance: Undecided Status: New ** Changed in: udisks2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/2037569 Title: udev issues with mantic beta Status in Ubuntu on IBM z Systems: New Status in systemd package in Ubuntu: Confirmed Status in udisks2 package in Ubuntu: Confirmed Bug description: While installing mantic beta (on s390x, LPAR and z/VM - but this might not be architecture specific) I faced issues with udev. In my installation I've updated the installer to "edge/lp-2009141" (subiquity 22.02.2+git1762.1b1ee6f4 5164). During my installations I first noticed bad response times in case of dealing with devices (like enabling new devices with chzdev). chzdev is used during the installation, hence the installation procedure is also affected by this. (I mainly notice this issue in case of DASD ECKD disk enablements.) But even after after a successful (but due to this issue less snappier) installation, means after the post-install reboot, in the installed system I can find several udev related processes, like: 69448 root 20 0 31280 11944 2560 S 39.2 0.0 2:51.67 (udev-worker) 509 root 20 0 31276 13812 4600 S 20.6 0.0 2:07.76 systemd-udevd 893 root 20 0 469016 13544 10496 R 17.3 0.0 1:43.53 udisksd 1 root 20 0 168664 12748 8396 S 16.3 0.0 1:40.47 systemd which is not only unusual, but (as one can see) they consume quite some resources. Even the remote ssh into that system is impacted by this high load. So far I only see this in mantic. I tried 20.04.3 as well as lunar, but both do not seem to be affected by this udev problem. I neither face the bad response on device enablement, nor can see any udev related processes still running after post-install-reboot in the installed system. (Sometimes I could also see a growing log file 'syslog'). I cannot say yet what is causing this, but since I see 'systemd-udevd' as prominent process in top, I'll first of all mark this as affecting systemd-udevd (or systemd). I've attached the outcome of some more investigations I did ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2037569/+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 2013236] Re: b43 driver conflicts with bcmwl driver for some Broadcom devices
I tested this today with "Ubuntu Legacy 23.10 "Mantic Minotaur" - Daily amd64 (20230927)" and discovered the b43 driver still does not work with my wireless adapter as I saw the following in dmesg: $ sudo dmesg | grep b43 [sudo] password for bdmurray: [ 18.921934] b43-phy0: Broadcom 4352 WLAN found (core revision 42) [ 18.922272] b43-phy0 ERROR: FOUND UNSUPPORTED PHY (Analog 12, Type 11 (AC), Revision 1) [ 18.922277] b43: probe of bcma0:1 failed with error -95 However, using software-properties-gtk to install the proprietary driver (broadcom-sta-dkms) worked and the b43 driver was blacklisted and I was able to connect to a wireless network. -- 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/2013236 Title: b43 driver conflicts with bcmwl driver for some Broadcom devices Status in broadcom-sta package in Ubuntu: New Status in linux-firmware package in Ubuntu: Invalid Status in ubuntu-drivers-common package in Ubuntu: Incomplete Status in broadcom-sta source package in Lunar: New Status in linux-firmware source package in Lunar: Invalid Status in ubuntu-drivers-common source package in Lunar: Incomplete Status in broadcom-sta source package in Mantic: New Status in linux-firmware source package in Mantic: Invalid Status in ubuntu-drivers-common source package in Mantic: Incomplete Bug description: Specifically for Lunar - using a Macbook Air 2012, its wireless driver was not enabled even though I ticked the wireless tickbox on the installer. A quick look at the installer logs reveals various issues syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [ 43.063747] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [ 43.063802] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063862] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063908] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 I will attach the installer logs manually since this was captured after the installation Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was installed correctly during the install so this is a regression with the 6.2 kernel Workaround -- You'll first need to blacklist the b43 driver by adding a blacklist file to /etc/modprobe.d/b43.conf with the contents "blacklist b43". Then run "update-initramfs -u". Then install the bcmwl-kernel-source package. After a reboot your wireless device should be available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2013236/+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 2037176] Re: not able to cold boot with ARC770M
I have same issue on Debian Sid, with kernel 6.5.0-1-amd64. It's not directly cold boot vs reboot. If I start my PC and reboot (ctrl+alt+del) on Grub stage, OS won't boot. To start my OS I need to: * Power on Intel NUC12SNKI72 * Boot Debian from Grub * Boot will hang at "Loading initial Ramdisk" * Press ctrl+alt+del to reboot * Now OS will boot properly Issue occurs on kernel 6.5 (unstable version) and 6.4 (stable backports). Something is loaded into GPU at first boot attempt which makes Debian (and Ubuntu) possible to boot properly after restart. hwinfo --display 08: PCI 300.0: 0300 VGA compatible controller (VGA) [Created at pci.386] Unique ID: svHJ.77hoq_qsqUD Parent ID: GA8e.mr2N3fBJq5F SysFS ID: /devices/pci:00/:00:01.0/:01:00.0/:02:01.0/:03:00.0 SysFS BusID: :03:00.0 Hardware Class: graphics card Device Name: "dGPU" Model: "Intel VGA compatible controller" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x5690 SubVendor: pci 0x8086 "Intel Corporation" SubDevice: pci 0x3026 Revision: 0x08 Driver: "i915" Driver Modules: "i915" Memory Range: 0x6b00-0x6bff (rw,non-prefetchable) Memory Range: 0x60-0x63 (ro,non-prefetchable) Memory Range: 0x6c00-0x6c1f (ro,non-prefetchable,disabled) IRQ: 251 (23243 events) Module Alias: "pci:v8086d5690sv8086sd3026bc03sc00i00" Driver Info #0: Driver Status: i915 is active Driver Activation Cmd: "modprobe i915" Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #33 (PCI bridge) 34: PCI 02.0: 0300 VGA compatible controller (VGA) [Created at pci.386] Unique ID: _Znp.HMLUX1zIkGC SysFS ID: /devices/pci:00/:00:02.0 SysFS BusID: :00:02.0 Hardware Class: graphics card Device Name: "GPU" Model: "Intel VGA compatible controller" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x46a6 SubVendor: pci 0x8086 "Intel Corporation" SubDevice: pci 0x3026 Revision: 0x0c Driver: "i915" Driver Modules: "i915" Memory Range: 0x644c00-0x644cff (rw,non-prefetchable) Memory Range: 0x40-0x400fff (ro,non-prefetchable) I/O Ports: 0x4000-0x403f (rw) Memory Range: 0x000c-0x000d (rw,non-prefetchable,disabled) IRQ: 250 (35 events) Module Alias: "pci:v8086d46A6sv8086sd3026bc03sc00i00" Driver Info #0: Driver Status: i915 is active Driver Activation Cmd: "modprobe i915" Config Status: cfg=new, avail=yes, need=no, active=unknown Primary display adapter: #8 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/2037176 Title: not able to cold boot with ARC770M Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: I am able to boot with kernel 6.5.x after install however after POWER OFF, Restart It hangs during boot and it does not start the graphical server. George Nistor ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xserver-xorg-video-intel 2:2.99.917+git20210115-1 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 23 19:07:47 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:3026] Intel Corporation Device [8086:5690] (rev 08) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:3026] InstallationDate: Installed on 2023-09-21 (2 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: Intel(R) Client Systems NUC12SNKi72 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.2.0-33-generic root=UUID=5663b3c3-49bb-4a93-b8fc-399746cb1397 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-intel UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/11/2023 dmi.bios.release: 0.58 dmi.bios.vendor: Intel Corp. dmi.bios.version: SNADL357.0058.2023.0711.1531 dmi.board.name: NUC12SNKi72 dmi.board.vendor: Intel Corporation dmi.board.version: M45201-502 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 1.17 dmi.modalias:
[Desktop-packages] [Bug 2037176] Re: not able to cold boot with ARC770M
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/2037176 Title: not able to cold boot with ARC770M Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: I am able to boot with kernel 6.5.x after install however after POWER OFF, Restart It hangs during boot and it does not start the graphical server. George Nistor ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xserver-xorg-video-intel 2:2.99.917+git20210115-1 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 23 19:07:47 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:3026] Intel Corporation Device [8086:5690] (rev 08) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:3026] InstallationDate: Installed on 2023-09-21 (2 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: Intel(R) Client Systems NUC12SNKi72 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.2.0-33-generic root=UUID=5663b3c3-49bb-4a93-b8fc-399746cb1397 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-intel UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/11/2023 dmi.bios.release: 0.58 dmi.bios.vendor: Intel Corp. dmi.bios.version: SNADL357.0058.2023.0711.1531 dmi.board.name: NUC12SNKi72 dmi.board.vendor: Intel Corporation dmi.board.version: M45201-502 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 1.17 dmi.modalias: dmi:bvnIntelCorp.:bvrSNADL357.0058.2023.0711.1531:bd07/11/2023:br0.58:efr1.17:svnIntel(R)ClientSystems:pnNUC12SNKi72:pvrM82271-502:rvnIntelCorporation:rnNUC12SNKi72:rvrM45201-502:cvnIntelCorporation:ct35:cvr2.0:skuRNUC12SNKi7200: dmi.product.family: SN dmi.product.name: NUC12SNKi72 dmi.product.sku: RNUC12SNKi7200 dmi.product.version: M82271-502 dmi.sys.vendor: Intel(R) Client Systems version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/2037176/+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 2034986] Re: some text became unreadable during a distribution upgrade
** Merge proposal linked: https://code.launchpad.net/~enr0n/ubuntu-release-upgrader/+git/ubuntu-release-upgrader/+merge/452304 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2034986 Title: some text became unreadable during a distribution upgrade Status in ubuntu-meta package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: In Progress Status in ubuntu-meta source package in Mantic: Confirmed Status in ubuntu-release-upgrader source package in Mantic: In Progress Bug description: I was upgrading from Lunar to Mantic the other day and left a couple of applications open during the upgrade process. During the upgrade the text in audacious became unreadable (I'll attach a screenshot) and I seem to recall the title bar of Firefox being unreadable but the contents of web pages still being readable. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-release-upgrader-core 1:23.10.5 ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0 Uname: Linux 6.5.0-4-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Sep 8 15:39:27 2023 InstallationDate: Installed on 2018-08-10 (1855 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 126: Error executing command as another user: Request dismissed VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2034986/+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 1968040] Re: [i915] Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
Hello. I seem to be hitting the same bug and I have attached the drm_info output while the screen is stuck in the off state. I see the the same Failed to post KMS update: drmModeAtomicCommit: Invalid argument and Page flip discarded: drmModeAtomicCommit: Invalid argument in my logs while the the monitor is stuck. It gets stuck when I turn my monitor off from inactivity or the monitor turns itself off after locking the computer. Putting MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 in /etc/environment fixed it for me. Rarely the screen also flickers at random moment, turns dark for a second, and then turns back on. When I checked the logs after it, I see the drmModeAtomicCommit: Invalid argument lines again. I have Ubuntu 22.04 with an external monitor Single display setup. Also Intel. ** Attachment added: "drm_info.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1968040/+attachment/5705009/+files/drm_info.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1968040 Title: [i915] Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] Status in GNOME Shell: New Status in Mutter: New Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.19 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: [ Workaround ] Add to /etc/environment (in Ubuntu 22.04): MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 or in Ubuntu 22.10 and later: MUTTER_DEBUG_FORCE_KMS_MODE=simple and then reboot. [ Upstream bugs ] https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5098 https://gitlab.gnome.org/GNOME/mutter/-/issues/2268 https://gitlab.gnome.org/GNOME/mutter/-/issues/2749 [ Original report ] (initially reported as a comment on bug #1965085, and split into a separate bug report) After I lock my screen and let it blank, moving the mouse or pressing any key on the keyboard won't wake it up. The only reliable workaround I've found is to press Ctrl+Alt+F1. That's on a fully up-to-date jammy, my hardware is an Intel NUC with a single Samsung monitor connected with a standard HDMI cable. This is a regression that started happening yesterday (2022-04-05) if I can remember correctly (I do apply pending updates at least once daily). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 6 15:19:30 2022 InstallationDate: Installed on 2020-09-16 (566 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-03-19 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968040/+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 2036735] Re: package firefox 117.0.1+build2-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1
** Tags removed: need-duplicate-check -- 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/2036735 Title: package firefox 117.0.1+build2-0ubuntu0.20.04.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: facing problem while upgrading ProblemType: Package DistroRelease: Ubuntu 22.04 Package: firefox 117.0.1+build2-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.15.0-84.93~20.04.1-generic 5.15.116 Uname: Linux 5.15.0-84-generic x86_64 NonfreeKernelModules: aufs AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aniket 1332 F pulseaudio BuildID: 20230912013654 CasperMD5CheckResult: unknown Channel: Unavailable Date: Wed Sep 20 17:22:12 2023 ErrorMessage: new firefox package pre-installation script subprocess returned error exit status 1 ForcedLayersAccel: False InstallationDate: Installed on 2022-01-18 (610 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) IpRoute: default via 192.168.1.1 dev wlp0s20f3 proto dhcp metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.1.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.1.57 metric 600 NoProfiles: True 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.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python3.10, Python 3.10.12, unpackaged RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.10 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 117.0.1+build2-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2023-09-20 (0 days ago) dmi.bios.date: 06/03/2021 dmi.bios.release: 2.33 dmi.bios.vendor: LENOVO dmi.bios.version: FKCN33WW(V2.01) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55724 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 14ITL05 dmi.ec.firmware.release: 2.33 dmi.modalias: dmi:bvnLENOVO:bvrFKCN33WW(V2.01):bd06/03/2021:br2.33:efr2.33:svnLENOVO:pn82FE:pvrIdeaPad514ITL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55724WIN:cvnLENOVO:ct10:cvrIdeaPad514ITL05:skuLENOVO_MT_82FE_BU_idea_FM_IdeaPad514ITL05: dmi.product.family: IdeaPad 5 14ITL05 dmi.product.name: 82FE dmi.product.sku: LENOVO_MT_82FE_BU_idea_FM_IdeaPad 5 14ITL05 dmi.product.version: IdeaPad 5 14ITL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2036735/+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 2036735] Re: package firefox 117.0.1+build2-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1
** Information type changed from Private Security to Public -- 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/2036735 Title: package firefox 117.0.1+build2-0ubuntu0.20.04.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: facing problem while upgrading ProblemType: Package DistroRelease: Ubuntu 22.04 Package: firefox 117.0.1+build2-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.15.0-84.93~20.04.1-generic 5.15.116 Uname: Linux 5.15.0-84-generic x86_64 NonfreeKernelModules: aufs AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aniket 1332 F pulseaudio BuildID: 20230912013654 CasperMD5CheckResult: unknown Channel: Unavailable Date: Wed Sep 20 17:22:12 2023 ErrorMessage: new firefox package pre-installation script subprocess returned error exit status 1 ForcedLayersAccel: False InstallationDate: Installed on 2022-01-18 (610 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) IpRoute: default via 192.168.1.1 dev wlp0s20f3 proto dhcp metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.1.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.1.57 metric 600 NoProfiles: True 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.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python3.10, Python 3.10.12, unpackaged RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.10 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 117.0.1+build2-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2023-09-20 (0 days ago) dmi.bios.date: 06/03/2021 dmi.bios.release: 2.33 dmi.bios.vendor: LENOVO dmi.bios.version: FKCN33WW(V2.01) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55724 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 14ITL05 dmi.ec.firmware.release: 2.33 dmi.modalias: dmi:bvnLENOVO:bvrFKCN33WW(V2.01):bd06/03/2021:br2.33:efr2.33:svnLENOVO:pn82FE:pvrIdeaPad514ITL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55724WIN:cvnLENOVO:ct10:cvrIdeaPad514ITL05:skuLENOVO_MT_82FE_BU_idea_FM_IdeaPad514ITL05: dmi.product.family: IdeaPad 5 14ITL05 dmi.product.name: 82FE dmi.product.sku: LENOVO_MT_82FE_BU_idea_FM_IdeaPad 5 14ITL05 dmi.product.version: IdeaPad 5 14ITL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2036735/+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 2037340] Re: Four Screens
** Information type changed from Private Security to Public -- 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/2037340 Title: Four Screens Status in xorg package in Ubuntu: New Bug description: I apologize for any grammar issues, but I can barely see what I am typing. Essentially, when I installed Ubuntu, I had to do so in safe graphics mode, as the screen would otherwise split itself into four different displays that had small amounts of resolution and are rather pale. I managed to install it, but once that happend, and it restarted, it went back to being four screens. I am not sure what to do, as I cannot really read any lines of code. Thank you for your help. I am using an iMac a1311, with an HDD and installed from a flashed usb. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Sep 25 20:33:11 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV730/M96-XT [Mobility Radeon HD 4670] [1002:9488] (prog-if 00 [VGA controller]) Subsystem: Apple Inc. RV730/M96-XT [Mobility Radeon HD 4670] [106b:00b6] InstallationDate: Installed on 2023-09-24 (1 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: Apple Inc. iMac10,1 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic root=UUID=be40ad74-149a-443c-99b3-2dbae10973a3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/14/2019 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 215.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F2268CC8 dmi.board.vendor: Apple Inc. dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 13 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F2268CC8 dmi.modalias: dmi:bvnAppleInc.:bvr215.0.0.0.0:bd06/14/2019:br0.1:svnAppleInc.:pniMac10,1:pvr1.0:rvnAppleInc.:rnMac-F2268CC8:rvr:cvnAppleInc.:ct13:cvrMac-F2268CC8:skuSystemSKU#: dmi.product.family: Mac dmi.product.name: iMac10,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2037340/+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 2037581] Re: Missing font when viewing some google docs
** Description changed: In chromium, some documents render with an incorrect font. It looks all "bold". I can provide a link in PVT if needed, but see attached screenshots for chrome, and chromium. The chromium console log also shows a lot of these 404 errors for *.woff2 fonts: GET filesystem:https://docs.google.com/persistent/docs/fonts/KFO8CneDtsqEr0keqCMhbCc_Mn33tY0.woff2 net::ERR_FILE_NOT_FOUND - The document is selecting the "Ubuntu" font, that seems to be the - culprit. + The document is using the "Ubuntu" font, that seems to be the culprit. ** Summary changed: - Missing font when viewing some google docs + Missing ubuntu font when viewing some google docs ** Description changed: - In chromium, some documents render with an incorrect font. It looks all - "bold". I can provide a link in PVT if needed, but see attached - screenshots for chrome, and chromium. + chromium snap + chromium 118.0.5993.11 2645 latest/edge canonical✓ - + + + In chromium, some documents render with an incorrect font. It looks all "bold". I can provide a link in PVT if needed, but see attached screenshots for chrome, and chromium. The chromium console log also shows a lot of these 404 errors for *.woff2 fonts: GET filesystem:https://docs.google.com/persistent/docs/fonts/KFO8CneDtsqEr0keqCMhbCc_Mn33tY0.woff2 net::ERR_FILE_NOT_FOUND The document is using the "Ubuntu" font, that seems to be the culprit. ** Description changed: chromium snap chromium 118.0.5993.11 2645 latest/edge canonical✓ - - - In chromium, some documents render with an incorrect font. It looks all "bold". I can provide a link in PVT if needed, but see attached screenshots for chrome, and chromium. + In chromium, some google doc documents render with an incorrect font. It + looks all "bold". I can provide a link in PVT if needed, but see + attached screenshots for chrome, and chromium. The chromium console log also shows a lot of these 404 errors for *.woff2 fonts: GET filesystem:https://docs.google.com/persistent/docs/fonts/KFO8CneDtsqEr0keqCMhbCc_Mn33tY0.woff2 net::ERR_FILE_NOT_FOUND The document is using the "Ubuntu" font, that seems to be the culprit. -- 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/2037581 Title: Missing ubuntu font when viewing some google docs Status in chromium-browser package in Ubuntu: New Bug description: chromium snap chromium 118.0.5993.11 2645 latest/edge canonical✓ - In chromium, some google doc documents render with an incorrect font. It looks all "bold". I can provide a link in PVT if needed, but see attached screenshots for chrome, and chromium. The chromium console log also shows a lot of these 404 errors for *.woff2 fonts: GET filesystem:https://docs.google.com/persistent/docs/fonts/KFO8CneDtsqEr0keqCMhbCc_Mn33tY0.woff2 net::ERR_FILE_NOT_FOUND The document is using the "Ubuntu" font, that seems to be the culprit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2037581/+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 2037581] Re: Missing font when viewing some google docs
** Attachment added: "chrome.png" https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2037581/+attachment/5704999/+files/chrome.png ** Tags added: snap ** Description changed: In chromium, some documents render with an incorrect font. It looks all "bold". I can provide a link in PVT if needed, but see attached screenshots for chrome, and chromium. The chromium console log also shows a lot of these 404 errors for *.woff2 fonts: GET filesystem:https://docs.google.com/persistent/docs/fonts/KFO8CneDtsqEr0keqCMhbCc_Mn33tY0.woff2 net::ERR_FILE_NOT_FOUND + + The document is selecting the "Ubuntu" font, that seems to be the + culprit. -- 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/2037581 Title: Missing ubuntu font when viewing some google docs Status in chromium-browser package in Ubuntu: New Bug description: chromium snap chromium 118.0.5993.11 2645 latest/edge canonical✓ - In chromium, some google doc documents render with an incorrect font. It looks all "bold". I can provide a link in PVT if needed, but see attached screenshots for chrome, and chromium. The chromium console log also shows a lot of these 404 errors for *.woff2 fonts: GET filesystem:https://docs.google.com/persistent/docs/fonts/KFO8CneDtsqEr0keqCMhbCc_Mn33tY0.woff2 net::ERR_FILE_NOT_FOUND The document is using the "Ubuntu" font, that seems to be the culprit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2037581/+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 2037581] [NEW] Missing ubuntu font when viewing some google docs
Public bug reported: chromium snap chromium 118.0.5993.11 2645 latest/edge canonical✓ - In chromium, some google doc documents render with an incorrect font. It looks all "bold". I can provide a link in PVT if needed, but see attached screenshots for chrome, and chromium. The chromium console log also shows a lot of these 404 errors for *.woff2 fonts: GET filesystem:https://docs.google.com/persistent/docs/fonts/KFO8CneDtsqEr0keqCMhbCc_Mn33tY0.woff2 net::ERR_FILE_NOT_FOUND The document is using the "Ubuntu" font, that seems to be the culprit. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: snap ** Attachment added: "chromium.png" https://bugs.launchpad.net/bugs/2037581/+attachment/5704998/+files/chromium.png -- 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/2037581 Title: Missing ubuntu font when viewing some google docs Status in chromium-browser package in Ubuntu: New Bug description: chromium snap chromium 118.0.5993.11 2645 latest/edge canonical✓ - In chromium, some google doc documents render with an incorrect font. It looks all "bold". I can provide a link in PVT if needed, but see attached screenshots for chrome, and chromium. The chromium console log also shows a lot of these 404 errors for *.woff2 fonts: GET filesystem:https://docs.google.com/persistent/docs/fonts/KFO8CneDtsqEr0keqCMhbCc_Mn33tY0.woff2 net::ERR_FILE_NOT_FOUND The document is using the "Ubuntu" font, that seems to be the culprit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2037581/+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 2037577] [NEW] [mantic] dconf parameter color-scheme in /org/gnome/shell/ubuntu/ has no effect
Public bug reported: When the dconf parameter color-scheme in /org/gnome/shell/ubuntu/ is modified, the GNOME Shell theme remains in the default state, i.e. it switches between light and dark together with the ‘Dark Style’ toggle. It is impossible to set the Shell theme to be unconditionally dark or light. To reproduce: 1. Run command gsettings set org.gnome.shell.ubuntu color-scheme 'prefer-dark' or modify the parameter color-scheme in /org/gnome/shell/ubuntu/ to be equal 'prefer-dark' via the Dconf Editor GUI. 2. Make sure that the ‘Dark Style’ toggle is deactivated in the quick settings. What should happen: The Shell dialogs like the quick settings menu and the calendar-and-notifications menu should be rendered in dark style. What happens instead: The Shell dialogs are still light. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 27 20:04:08 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-09-21 (371 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829) RelatedPackageVersions: mutter-common 45.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-09-26 (1 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic 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/2037577 Title: [mantic] dconf parameter color-scheme in /org/gnome/shell/ubuntu/ has no effect Status in gnome-shell package in Ubuntu: New Bug description: When the dconf parameter color-scheme in /org/gnome/shell/ubuntu/ is modified, the GNOME Shell theme remains in the default state, i.e. it switches between light and dark together with the ‘Dark Style’ toggle. It is impossible to set the Shell theme to be unconditionally dark or light. To reproduce: 1. Run command gsettings set org.gnome.shell.ubuntu color-scheme 'prefer-dark' or modify the parameter color-scheme in /org/gnome/shell/ubuntu/ to be equal 'prefer-dark' via the Dconf Editor GUI. 2. Make sure that the ‘Dark Style’ toggle is deactivated in the quick settings. What should happen: The Shell dialogs like the quick settings menu and the calendar-and-notifications menu should be rendered in dark style. What happens instead: The Shell dialogs are still light. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 27 20:04:08 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-09-21 (371 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829) RelatedPackageVersions: mutter-common 45.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-09-26 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037577/+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 2037460] Re: gnome-shell crash
there's nothing in /var/crash or in errors.ubuntu.com ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2037460 Title: gnome-shell crash Status in gnome-shell package in Ubuntu: New Bug description: gnome shell crashed when switching workspaces to check out the new 'activities' workspace indicator functionality. it also crashed when starting ms teams, not sure if that's the same bug? ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Sep 26 11:28:15 2023 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-17 (1502 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) RelatedPackageVersions: mutter-common 45.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-09-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037460/+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 2037460] Re: gnome-shell crash
-b -1 ** Attachment added: "prevjournal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037460/+attachment/5704967/+files/prevjournal.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/2037460 Title: gnome-shell crash Status in gnome-shell package in Ubuntu: New Bug description: gnome shell crashed when switching workspaces to check out the new 'activities' workspace indicator functionality. it also crashed when starting ms teams, not sure if that's the same bug? ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Sep 26 11:28:15 2023 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-17 (1502 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) RelatedPackageVersions: mutter-common 45.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-09-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037460/+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 2037460] Re: gnome-shell crash
-b 0 ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037460/+attachment/5704966/+files/journal.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/2037460 Title: gnome-shell crash Status in gnome-shell package in Ubuntu: New Bug description: gnome shell crashed when switching workspaces to check out the new 'activities' workspace indicator functionality. it also crashed when starting ms teams, not sure if that's the same bug? ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Sep 26 11:28:15 2023 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-17 (1502 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) RelatedPackageVersions: mutter-common 45.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-09-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037460/+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 2033645] Re: [BPO] libreoffice 7.5.6 for jammy
this has now been published. ** Changed in: libreoffice (Ubuntu Jammy) Status: Fix Committed => 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/2033645 Title: [BPO] libreoffice 7.5.6 for jammy Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Jammy: Fix Released Bug description: [Impact] * LibreOffice 7.5.6 is in its sixth bugfix release of the 7.5 line: https://wiki.documentfoundation.org/ReleasePlan/7.5#7.5.6_release * This source packages matches the proposed SRU for lunar handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2033643 [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/1:7.5.6-0ubuntu0.23.04.1 * Backport target is 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_75/1671/ * 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. Jammy/22.04 build at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-prereleases/+sourcepub/15135069/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/amd64/libr/libreoffice/20230902_144308_89e10@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/arm64/libr/libreoffice/20230902_165623_9d364@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/armhf/libr/libreoffice/20230904_200742_5f3fa@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/ppc64el/libr/libreoffice/20230902_160737_b0f46@/log.gz * [riscv64] not available * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/s390x/libr/libreoffice/20230902_232846_e9b82@/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 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/2033645/+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 1891165] Re: gsettings-desktop-schemas : Breaks: mutter (< 3.31.4) but 3.28.4-0ubuntu18.04.2 is to be installed
This was solved for me by doing `apt full-upgrade`. `man apt` describes: `upgrade is used to install available upgrades of all packages currently installed on the system from the, but existing packages will never be removed. If an upgrade for a package requires the remove of an installed package the upgrade for this package isn't performed.` -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1891165 Title: gsettings-desktop-schemas : Breaks: mutter (< 3.31.4) but 3.28.4-0ubuntu18.04.2 is to be installed Status in gsettings-desktop-schemas package in Ubuntu: Confirmed Bug description: I was about to upgrade ubuntu 18 to ubuntu 20, but it says “Your python3 install is corrupted. Please fix the '/usr/bin/python3'”, So i tried to run sudo ln -sf /usr/bin/python2.7 /usr/bin/python as suggested in https://askubuntu.com/questions/1185813/how-to-fix-ubuntu-19-04-cannot-upgrade-to-19-10-error-your-python3-install-is. But i got more errors The following packages have unmet dependencies: gsettings-desktop-schemas : Breaks: mutter (< 3.31.4) but 3.28.4-0ubuntu18.04.2 is to be installed libgirepository-1.0-1 : Breaks: python-gi (< 3.34.0-4~) but 3.26.1-2ubuntu1 is to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. sudo ln -sf /usr/bin/python2.7 /usr/bin/python ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.28.4-0ubuntu18.04.2 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 11 20:38:08 2020 InstallationDate: Installed on 2020-02-08 (184 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1891165/+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 2037307] Re: Dragging the top activities/time bar freezes GNOME completely
The issue's really consistent and easy to reproduce thankfully. ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037307/+attachment/5704945/+files/journal.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/2037307 Title: Dragging the top activities/time bar freezes GNOME completely Status in gnome-shell package in Ubuntu: Incomplete Bug description: If you use a touchscreen and drag a finger down on the very top bar (with the time and the former activities button), GNOME will completely freeze. The mouse cursor will be locked in the "drag" state. All keyboard input (including Alt-F2) will be ignored. The only way to escape this state is to switch into a virtual console and kill the current program. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 25 12:33:44 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-08-02 (55 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-09-23 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037307/+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 2011385] Re: [950XED, Realtek ALC298, Speaker, Internal] No sound at all
Confirming the same problem on Razer Blade 16 and Galaxy Book3 pro, both running Arch Linux -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2011385 Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: only bluetooth can work,im sungsang book2 pro ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 13 15:41:47 2023 InstallationDate: Installed on 2023-03-08 (4 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P08RGF.054.220817.ZQ dmi.board.asset.tag: No Asset Tag dmi.board.name: NT950XEW-A51AS dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGLFREEDOS-C00-R000-S+1.0. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP08RGF.054.220817.ZQ:bd08/17/2022:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn950XED:pvrP08RGF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNT950XEW-A51AS:rvrSGLFREEDOS-C00-R000-S+1.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-ICPS-A5A5-ADLP-PRGF: dmi.product.family: Galaxy Book2 Pro dmi.product.name: 950XED dmi.product.sku: SCAI-ICPS-A5A5-ADLP-PRGF dmi.product.version: P08RGF dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2011385/+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 2037540] Re: system extension light style is not working
The new light style extension is provided in the gnome-shell-extensions package. ** Tags added: mantic -- 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/2037540 Title: system extension light style is not working Status in gnome-shell package in Ubuntu: New Bug description: Trying to enable light style gnome shell system extension is not working. What should happen is that light style should be enabled: when pressing the super button, a light-not black background should be displayed. lsb_release -rd: Description: Ubuntu Mantic Minotaur (development branch) Release: 23.10 apt-cache policy gnome-shell: gnome-shell: Installed: 45.0-1ubuntu1 Candidate: 45.0-1ubuntu1 Version table: *** 45.0-1ubuntu1 500 500 http://gr.archive.ubuntu.com/ubuntu mantic/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037540/+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 2011385] Re: [950XED, Realtek ALC298, Speaker, Internal] No sound at all
razer blade 18 2023 is also affected. so is the asus strix 17 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2011385 Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: only bluetooth can work,im sungsang book2 pro ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 13 15:41:47 2023 InstallationDate: Installed on 2023-03-08 (4 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P08RGF.054.220817.ZQ dmi.board.asset.tag: No Asset Tag dmi.board.name: NT950XEW-A51AS dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGLFREEDOS-C00-R000-S+1.0. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP08RGF.054.220817.ZQ:bd08/17/2022:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn950XED:pvrP08RGF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNT950XEW-A51AS:rvrSGLFREEDOS-C00-R000-S+1.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-ICPS-A5A5-ADLP-PRGF: dmi.product.family: Galaxy Book2 Pro dmi.product.name: 950XED dmi.product.sku: SCAI-ICPS-A5A5-ADLP-PRGF dmi.product.version: P08RGF dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2011385/+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 2017498] Re: crashes trying to open the mouse screen
For me, the reason is the gstreamer playback plugin being blacklisted. To remove it from blacklist, you can run : sudo rm ~/.cache/gstreamer-1.0/registry* I have no idea why it was blacklisted in the first place. -- 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/2017498 Title: crashes trying to open the mouse screen Status in gnome-control-center package in Ubuntu: Incomplete Bug description: gnome-control-center crashes on ubuntu 23.04 when trying to open the mouse screen Steps to reproduce: 1. In GNOME Settings, navigate to the mouse screen. The control center crashes (i.e., the window closes instead of showing the mouse screen). 2. Start GNOME Settings again, e.g., using GNOME Shell or by running the following command from the terminal: `gnome-control-center`. The main window does not show. Instead, the commandline output prints an error message as follows: Commandline output: ``` gnome-control-center --verbose 21:10:51.6276 GStreamer-Play[32248]: ERROR: GtkGstPlay: 'playbin' element not found, please check your setup [1]32248 trace trap (core dumped) gnome-control-center --verbose ``` More observations: Note, this happens reproducably. I just recently upgraded to ubuntu 23.04, which means I am running GNOME 44. I am now unable to start the gnome-control-center. It happens in wayland and xorg sessions. I am using an intel x86 laptop, a lenovo thinkpad x1 carbon. Workaround: The following workaround allows to start gnome-control- center again, but does not allow to access the mouse panel. In dconf editor, reset `org/gnome/control-center/last-panel'. The control center will then open successfully. I think this indicates that the mouse panel causes gnome-control-center to crash. Upstream ticket over at GNOME's gitlab project: https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2459 Upstream analysis by Felipe Borges, maintainer of the upstream project: > The issue seems to be about Ubuntu packaging not including the needed dependencies for the GtkPicture videos we now show in the Mouse panel. > Could you please file this issue downstream in the Ubuntu bug tracker? --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 EcryptfsInUse: Yes InstallationDate: Installed on 2020-11-15 (892 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Package: gnome-control-center 1:44.0-1ubuntu5 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Tags: lunar wayland-session Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-23 (3 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2017498/+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 2037540] [NEW] system extension light style is not working
Public bug reported: Trying to enable light style gnome shell system extension is not working. What should happen is that light style should be enabled: when pressing the super button, a light-not black background should be displayed. lsb_release -rd: Description:Ubuntu Mantic Minotaur (development branch) Release:23.10 apt-cache policy gnome-shell: gnome-shell: Installed: 45.0-1ubuntu1 Candidate: 45.0-1ubuntu1 Version table: *** 45.0-1ubuntu1 500 500 http://gr.archive.ubuntu.com/ubuntu mantic/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2037540 Title: system extension light style is not working Status in gnome-shell package in Ubuntu: New Bug description: Trying to enable light style gnome shell system extension is not working. What should happen is that light style should be enabled: when pressing the super button, a light-not black background should be displayed. lsb_release -rd: Description: Ubuntu Mantic Minotaur (development branch) Release: 23.10 apt-cache policy gnome-shell: gnome-shell: Installed: 45.0-1ubuntu1 Candidate: 45.0-1ubuntu1 Version table: *** 45.0-1ubuntu1 500 500 http://gr.archive.ubuntu.com/ubuntu mantic/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037540/+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 2037186] Re: Update cairo to 1.18.0
This bug was fixed in the package cairo - 1.18.0-1 --- cairo (1.18.0-1) unstable; urgency=medium * New upstream release (LP: #2037186) * Drop all patches: applied in new release * debian/libcairo*.symbols: Add new symbols -- Jeremy Bícha Sat, 23 Sep 2023 18:39:51 -0400 ** Changed in: cairo (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/2037186 Title: Update cairo to 1.18.0 Status in cairo package in Ubuntu: Fix Released Bug description: Impact -- Ubuntu 23.10 includes cairo 1.17.8, the final pre-release snapshot of what eventually became the stable 1.18.0. It would be nicer to include the stable release than a beta release. Debian's autopkgtests completed successfully. News https://cairographics.org/news/cairo-1.18.0/ Detailed changelog -- https://gitlab.freedesktop.org/cairo/cairo/-/compare/1.17.8...1.18.0 Why This Didn't Land Sooner -- I was told by cairo upstream developers to expect cairo 1.18.0 in August 2023. It was released September 23 instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/2037186/+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 2037538] [NEW] GNOME Freezes, Alt+F2 not even responding. Mouse Cursor Tracks, but can't click.
Public bug reported: Ubuntu 22.04.3 LTS gnome-shell[3218]: Can't update stage views actor [:0x555e5db5c350] is on because it needs an allocation. gnome-shell[3218]: Can't update stage views actor [:0x555e5fe0d310] is on because it needs an allocation. gnome-shell[3218]: Can't update stage views actor [:0x555e5fe106d0] is on because it needs an allocation. gnome-shell[3218]: Can't update stage views actor [:0x555e5db5c350] is on because it needs an allocation. gnome-shell[3218]: Can't update stage views actor [:0x555e5fe0d310] is on because it needs an allocation. gnome-shell[3218]: Can't update stage views actor [:0x555e5fe106d0] is on because it needs an allocation. gnome-shell[5794]: [5788:5825:0927/071652.214702:ERROR:nss_util.cc(357)] After loading Root Certs, loaded==false: NSS error code: -8018 Also, getting stack traces every time I open Activities by click or super button. I removed all User-Installed Extensions, and have also tried disabling the default System Extensions with no change. JS ERROR: TypeError: workspace is undefined#012_getSpacing@resource:///org/gnome/shell/ui/workspacesView.js:213:13#012vfunc_allocate@resource:///org/gnome/shell/ui/workspacesView.js:339:18#012vfunc_allocate@resource:///org/gnome/shell/ui/workspacesView.js:711:30#012removeWindow@resource:///org/gnome/shell/ui/workspace.js:855:29#012addWindow/<.destroyId<@resource:///org/gnome/shell/ui/workspace.js:806:22#012vfunc_hide@resource:///org/gnome/shell/ui/workspacesView.js:1016:38#012vfunc_unmap@resource:///org/gnome/shell/ui/overviewControls.js:715:33#012hideOverview@resource:///org/gnome/shell/ui/layout.js:347:28#012_hideDone@resource:///org/gnome/shell/ui/overview.js:641:32#012_animateNotVisible/<@resource:///org/gnome/shell/ui/overview.js:624:55#012onStopped@resource:///org/gnome/shell/ui/overviewControls.js:757:21#012_makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:151:22#012_easeActorProperty/<@resource:///org/gnome/shell/ui/environment.js:317:60 gnome-shell[3218]: Object St.Button (0x555e5dc62c60), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. gnome-shell[3218]: == Stack trace for context 0x555e5d657170 == gnome-shell[3218]: #0 555e5deb4708 i resource:///org/gnome/shell/ui/windowPreview.js:566 (20a2bc50b650 @ 10) gnome-shell[3218]: == Stack trace for context 0x555e5d657170 == gnome-shell[3218]: #0 555e5deb4708 i resource:///org/gnome/shell/ui/windowPreview.js:567 (20a2bc50b650 @ 36) gnome-shell[3218]: == Stack trace for context 0x555e5d657170 == gnome-shell[3218]: #0 555e5deb4708 i resource:///org/gnome/shell/ui/windowPreview.js:570 (20a2bc50b650 @ 77) gnome-shell[3218]: Object St.Label (0x555e5df247a0), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. gnome-shell[3218]: Object .Gjs_ui_windowPreview_WindowPreview (0x555e5ed83d30), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 27 07:19:09 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-08-15 (42 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.9-0ubuntu4 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug gnome jammy -- 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/2037538 Title: GNOME Freezes, Alt+F2 not even responding. Mouse Cursor Tracks, but can't click. Status in gnome-shell package in Ubuntu: New Bug description: Ubuntu 22.04.3 LTS gnome-shell[3218]: Can't update stage views actor [:0x555e5db5c350] is on because it needs an allocation. gnome-shell[3218]: Can't update stage views actor [:0x555e5fe0d310] is on because it needs an allocation. gnome-shell[3218]: Can't update stage views actor [:0x555e5fe106d0] is on because it needs an allocation. gnome-shell[3218]: Can't update stage views actor
[Desktop-packages] [Bug 1978890] Re: FIPS/OEM installation compatibility is unclear to the end-user
** Changed in: ubuntu-advantage-tools (Ubuntu) Status: New => Triaged -- 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/1978890 Title: FIPS/OEM installation compatibility is unclear to the end-user Status in subiquity package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: New Status in ubuntu-advantage-tools package in Ubuntu: Triaged Status in ubuntu-drivers-common package in Ubuntu: New Status in update-manager package in Ubuntu: New Bug description: [Overall Summary] Converting to cover all oem/fips compatibility issues with ua/installers/update-manager. These projects are mostly silo'd, so when they all converge it creates a confusing and frustrating experience for the user. At it's core, the problem is that both fips and oem us GRUB_FLAVOUR_ORDER to select the preferred kernel to boot from, disregarding versioning. The main issues are: 1. ubuntu-drivers should not attempt to `oem-ify` a `fipsified` machine 2. ua tool should not attempt to `fipsify` an oem machine 3. subiquity should mention that drivers page is potentially making machine realtime & fips incompatible Below are some reproducible examples of issues: --- (Subiquity installer case) [Summary] A recent change to the subiquity snap adds support for installing oem drivers at time of instance install. If the user installs these packages, then attempts to install the fips packages post-install, fips will install as expected, but the system will always boot to the oem kernel. [Expected Behavior] Messaging should clearly indicate that installing the oem packages will make the environment incompatible with fips/RT kernel/ etc. [Observed Behavior] Subiquity just offers additional drivers, without clarifying the compatibility complications. [Replication Steps] (Using Dell Inc. Precision 7920 Tower/060K5C) 1. Install from current focal ISO 2. Confirm driver installation on the oem gui page 3. Install ua client/fips 4. Reboot 5. Observe kernel version (oem) --- (update-manager case) [Summary] A feature was added to allow for post-install enablement for oem-enabled devices via update manager: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1908050 While this works great for some situations, it can lead to users unexpectedly installing the oem meta package + associated kernel, overwriting an existing fips installation, as the "Improved hardware support" bundle may not be noticed when operating update-manager [Expected Behavior] For non linux-generic running installs, the post-install oem enablement functionality should not trigger, nor should it add the additional repositories to the client's sources.list.d. [Observed Behavior] sources.list.d is updated and "Improved hardware support" is allowed as an option in update-manager, which leads to clients unexpectedly losing compliance in fips environments. [Replication Steps] (Using Dell Inc. Precision 7920 Tower/060K5C) 1. Install from current focal ISO 2. Attach a ua subscription 3. Enable the fips-updates service 4. Reboot the system, login the desktop and wait for a while. The notification will pop up and it will show "Improved hardware support" on the certified machines that has the OEM metapackage support. 5. Click through the update-manager prompt and install the oem packages 6. Reboot check fips status oem's config in /etc/default/grub.d/* does not have a number prefix, and thus will always override 99-ubuntu-fips.cfg when calling update- grub. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1978890/+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 2037191] Re: Lockscreen sometimes doesn't render
*** This bug is a duplicate of bug 1532508 *** https://bugs.launchpad.net/bugs/1532508 https://bugs.launchpad.net/bugs/1532508 seems to be about the lockscreen only being invisible for a split second, but in this bug it stays invisible, activity preventing the user from logging in while revealing the desktop. -- 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/2037191 Title: Lockscreen sometimes doesn't render Status in gnome-shell package in Ubuntu: Incomplete Bug description: Sometimes when I unlock my laptop by opening the lid, the touchscreen just doesn't render. This renders the system completely frozen until I go into a TTY and run "sudo loginctl unlock-sessions". But that's not the real problem. The real problem is that while the lock-screen doesn't render, *everything* else does. This means that while I wasn't logged in, Firefox and all other open applications were completely visible. This is obviously a big issue if one has sensitive information open. There does not seem to be a reliable way to reproduce this, it just happens sometimes. So far, I've experienced this twice, once on 23.04 and once on the 23.10 beta. There are however, some really suspicious error messages in the logs: Sep 23 17:31:26 user-83BV gnome-shell[2000]: == Stack trace for context 0x564e3e5286b0 == Sep 23 17:31:26 user-83BV gnome-shell[2000]: #0 564e3e6415e8 i resource:///org/gnome/shell/ui/keyboard.js:1809 (3e69d1677920 @ 73) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #1 564e3e641558 i resource:///org/gnome/shell/ui/keyboard.js:1941 (3e69d1677e20 @ 43) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #2 564e3e6414d8 i resource:///org/gnome/shell/ui/keyboard.js:1931 (3e69d1677dd0 @ 28) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #3 564e3e641448 i resource:///org/gnome/shell/ui/init.js:21 (2f81e37d060 @ 48) Sep 23 17:31:26 user-83BV gnome-shell[2000]: == Stack trace for context 0x564e3e5286b0 == Sep 23 17:31:26 user-83BV gnome-shell[2000]: #0 564e3e6415e8 i resource:///org/gnome/shell/ui/keyboard.js:1812 (3e69d1677920 @ 124) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #1 564e3e641558 i resource:///org/gnome/shell/ui/keyboard.js:1941 (3e69d1677e20 @ 43) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #2 564e3e6414d8 i resource:///org/gnome/shell/ui/keyboard.js:1931 (3e69d1677dd0 @ 28) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #3 564e3e641448 i resource:///org/gnome/shell/ui/init.js:21 (2f81e37d060 @ 48) Sep 23 17:31:26 user-83BV gnome-shell[2000]: == Stack trace for context 0x564e3e5286b0 == Sep 23 17:31:26 user-83BV gnome-shell[2000]: #0 564e3e6415e8 i resource:///org/gnome/shell/ui/keyboard.js:1988 (3e69d1677fb0 @ 112) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #1 564e3e641558 i resource:///org/gnome/shell/ui/keyboard.js:1942 (3e69d1677e20 @ 58) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #2 564e3e6414d8 i resource:///org/gnome/shell/ui/keyboard.js:1931 (3e69d1677dd0 @ 28) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #3 564e3e641448 i resource:///org/gnome/shell/ui/init.js:21 (2f81e37d060 @ 48) Sep 23 17:31:26 user-83BV gnome-shell[2000]: == Stack trace for context 0x564e3e5286b0 == Sep 23 17:31:26 user-83BV gnome-shell[2000]: #0 564e3e641710 i resource:///org/gnome/shell/ui/environment.js:112 (2f81e37d600 @ 43) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #1 564e3e641678 i resource:///org/gnome/shell/ui/environment.js:297 (2f81e37dce0 @ 19) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #2 564e3e6415e8 i resource:///org/gnome/shell/ui/keyboard.js:1987 (3e69d1677fb0 @ 176) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #3 564e3e641558 i resource:///org/gnome/shell/ui/keyboard.js:1942 (3e69d1677e20 @ 58) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #4 564e3e6414d8 i resource:///org/gnome/shell/ui/keyboard.js:1931 (3e69d1677dd0 @ 28) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #5 564e3e641448 i resource:///org/gnome/shell/ui/init.js:21 (2f81e37d060 @ 48) Sep 23 17:31:26 user-83BV gnome-shell[2000]: == Stack trace for context 0x564e3e5286b0 == Sep 23 17:31:26 user-83BV gnome-shell[2000]: #0 564e3e6417e0 i resource:///org/gnome/shell/ui/environment.js:289 (2f81e37dc40 @ 39) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #1 564e3e641710 i resource:///org/gnome/shell/ui/environment.js:115 (2f81e37d600 @ 91) Sep 23 17:31:26 user-83BV gnome-shell[2000]: Object .Gjs_ui_keyboard_Keyboard (0x564e41dbc4f0), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Sep 23 17:31:26 user-83BV gnome-shell[2000]: #2 564e3e641678 i resource:///org/gnome/shell/ui/environment.js:297
[Desktop-packages] [Bug 1969140] Re: Window minimize animation flickers and appears in the wrong place in Xorg sessions
** Changed in: dash-to-dock Status: Unknown => New -- 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/1969140 Title: Window minimize animation flickers and appears in the wrong place in Xorg sessions Status in Dash to dock: New Status in Mutter: New Status in mutter package in Ubuntu: Confirmed Bug description: Graphical glitches appears while minimizing or maximizing apps in x11 session randomly, screencast below 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 Date: Thu Apr 14 17:07:49 2022 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2022-04-12 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.0-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1969140/+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 2036981] Re: UIFe: update for the new snap store naming and icon
This bug was fixed in the package ubuntu-docs - 23.10.3 --- ubuntu-docs (23.10.3) mantic; urgency=medium * For languages where existing strings were translated keeping the name "Ubuntu Software" verbatim, replace this with the new name "App Center" to avoid unnecessarily regressing translation coverage. Translation teams might choose to translate the name "App Center" where they left "Ubuntu Software" untranslated, but leave this to reviews after the fact so that doc translations aren't regressed for release in the meantime. Thanks, Zixing Liu . -- Steve Langasek Tue, 26 Sep 2023 22:26:05 -0700 ** Changed in: ubuntu-docs (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-initial-setup in Ubuntu. https://bugs.launchpad.net/bugs/2036981 Title: UIFe: update for the new snap store naming and icon Status in gnome-initial-setup package in Ubuntu: Fix Released Status in ubuntu-docs package in Ubuntu: Fix Released Bug description: The mantic Desktop image transitioned from the old snap-store to the new app-center (https://github.com/ubuntu/app-center) The gnome initial setup now incorrectly references 'ubuntu software' when it should refer to the 'App Center', the update is changing the name and also removing the quoting around the name which was flagged as something we don't want during UI review We also want to replace the snapcrafter icon with the icon of the App Center It's going to require revalidating the translations but it should be a trivial change for translators since only the appname is changing, we believe there is still time for that work before release and that doing this cycle will increase the coverage for the LTS Screenshots before - https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/2036981/+attachment/5703505/+files/image.png after - https://launchpadlibrarian.net/688536719/gis2.png email to the documentation team - https://lists.ubuntu.com/archives/ubuntu-doc/2023-September/020903.html email to the translations team - https://lists.ubuntu.com/archives/ubuntu-translators/2023-September/007900.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/2036981/+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 2037528] [NEW] every tab with touchscreen on a folder gives the context menu.
Public bug reported: Ubuntu installed on Chuwi u-book x pro (13 inch). CPU: Intel® Core™ i7-7Y75 × 4 GPU: Intel® HD Graphics 615 (KBL GT2) Tapping a folder in Nautilus always gives the context menu. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: nautilus 1:44.2.1-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-33.33-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 27 12:08:40 2023 GsettingsChanges: b'org.gnome.nautilus.preferences' b'click-policy' b"'single'" b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2023-09-19 (7 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.48.0-1ubuntu1 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar wayland-session ** Attachment added: "Schermafdruk van 2023-09-27 12-14-03.png" https://bugs.launchpad.net/bugs/2037528/+attachment/5704881/+files/Schermafdruk%20van%202023-09-27%2012-14-03.png -- 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/2037528 Title: every tab with touchscreen on a folder gives the context menu. Status in nautilus package in Ubuntu: New Bug description: Ubuntu installed on Chuwi u-book x pro (13 inch). CPU: Intel® Core™ i7-7Y75 × 4 GPU: Intel® HD Graphics 615 (KBL GT2) Tapping a folder in Nautilus always gives the context menu. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: nautilus 1:44.2.1-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-33.33-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 27 12:08:40 2023 GsettingsChanges: b'org.gnome.nautilus.preferences' b'click-policy' b"'single'" b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2023-09-19 (7 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.48.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2037528/+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 2013083] Re: libwebp-dev doesn't install CMake configs
This is fixed in Debian sid/testing, will be fixed for mantic if bug: 2037527 is accepted, or to 24.04 otherwise. Setting right now as fix released. ** Changed in: libwebp (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libwebp in Ubuntu. https://bugs.launchpad.net/bugs/2013083 Title: libwebp-dev doesn't install CMake configs Status in libwebp package in Ubuntu: Fix Released Bug description: Libwebp source archive ships Cmake configs. Unlike vcpkg, the Ubuntu package doesn't install them. This prevents client applications from using the recommended find_package(WebP) functionality. Please install the CMake configs along with the pkg-config files. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libwebp/+bug/2013083/+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 2037527] [NEW] [Ffe] libwebp
Public bug reported: - 9/13/2023: version 1.3.2 This is a binary compatible release. * security fix for lossless decoder (chromium: #1479274, CVE-2023-4863) - 6/23/2023: version 1.3.1 This is a binary compatible release. * security fixes for lossless encoder (#603, chromium: #1420107, #1455619, CVE-2023-1999) * improve error reporting through WebPPicture error codes * fix upsampling for RGB565 and RGBA in NEON builds * img2webp: add -sharp_yuv & -near_lossless * Windows builds: - fix compatibility with clang-cl (#607) - improve Arm64 performance with cl.exe - add Arm64EC support * fix webp_js with emcc >= 3.1.27 (stack size change, #614) * CMake fixes (#592, #610, #612) * further updates to the container and lossless bitstream docs (#581, #611) - 12/16/2022: version 1.3.0 This is a binary compatible release. * add libsharpyuv, which exposes -sharp_yuv/config.use_sharp_yuv functionality to other libraries; libwebp now depends on this library * major updates to the container and lossless bitstream docs (#448, #546, #551) * miscellaneous warning, bug & build fixes (#576, #583, #584) Moreover the LP: #2013083 can be closed in this release. The non-bugfix changes are related to a new library added, that is used probably by firefox and chromium (next releases? or maybe they are using the embedded library) ** Affects: libwebp (Ubuntu) Importance: Undecided Assignee: Ubuntu Release Team (ubuntu-release) Status: New ** Changed in: libwebp (Ubuntu) Assignee: (unassigned) => Ubuntu Release Team (ubuntu-release) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libwebp in Ubuntu. https://bugs.launchpad.net/bugs/2037527 Title: [Ffe] libwebp Status in libwebp package in Ubuntu: New Bug description: - 9/13/2023: version 1.3.2 This is a binary compatible release. * security fix for lossless decoder (chromium: #1479274, CVE-2023-4863) - 6/23/2023: version 1.3.1 This is a binary compatible release. * security fixes for lossless encoder (#603, chromium: #1420107, #1455619, CVE-2023-1999) * improve error reporting through WebPPicture error codes * fix upsampling for RGB565 and RGBA in NEON builds * img2webp: add -sharp_yuv & -near_lossless * Windows builds: - fix compatibility with clang-cl (#607) - improve Arm64 performance with cl.exe - add Arm64EC support * fix webp_js with emcc >= 3.1.27 (stack size change, #614) * CMake fixes (#592, #610, #612) * further updates to the container and lossless bitstream docs (#581, #611) - 12/16/2022: version 1.3.0 This is a binary compatible release. * add libsharpyuv, which exposes -sharp_yuv/config.use_sharp_yuv functionality to other libraries; libwebp now depends on this library * major updates to the container and lossless bitstream docs (#448, #546, #551) * miscellaneous warning, bug & build fixes (#576, #583, #584) Moreover the LP: #2013083 can be closed in this release. The non-bugfix changes are related to a new library added, that is used probably by firefox and chromium (next releases? or maybe they are using the embedded library) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libwebp/+bug/2037527/+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 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen in Wayland
** Description changed: + [ Workaround ] + + Add this to /etc/environment: + + MUTTER_DEBUG_KMS_THREAD_TYPE=user + + and then reboot. + + [ Original Description] + I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. All works in xorg. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 22:32:22 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-03 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: -- 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/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen in Wayland Status in Linux: New Status in Mutter: New Status in X.Org X server: Fix Released Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: In Progress Status in linux source package in Mantic: Confirmed Status in mutter source package in Mantic: In Progress Bug description: [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_KMS_THREAD_TYPE=user and then reboot. [ Original Description] I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. All works in xorg. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 22:32:22 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-03 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+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 2037520] [NEW] Locking screen causes logout in Wayland
Public bug reported: == Expected == When I lock the screen, the lock screen appears, and I can log in to return to my existing sessions. == Actual == When I lock the screen (Windows+L, Quick Settings or closing the laptop lid) it'll cause the session to logout and redirect me back to the login screen, which causes all running programs to close and starts a new session after login. == Additional details == This bug only happens on Wayland and is not present under xorg. I have confirmed (with top) that all the running programs are closed and the session itself is destroyed (Ctrl+Alt+F2 and other screens are all tty, except for the login screen at Ctrl+Alt+F1) == System details == ThinkPad E14 Gen 2 - AMD Ryzen 5500U Ubuntu 23.10 Mantic Minotaur (beta) ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gdm3 45~beta-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 27 11:06:43 2023 InstallationDate: Installed on 2022-04-23 (522 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: gdm3 UpgradeStatus: Upgraded to mantic on 2023-09-25 (2 days ago) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic -- 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/2037520 Title: Locking screen causes logout in Wayland Status in gdm3 package in Ubuntu: New Bug description: == Expected == When I lock the screen, the lock screen appears, and I can log in to return to my existing sessions. == Actual == When I lock the screen (Windows+L, Quick Settings or closing the laptop lid) it'll cause the session to logout and redirect me back to the login screen, which causes all running programs to close and starts a new session after login. == Additional details == This bug only happens on Wayland and is not present under xorg. I have confirmed (with top) that all the running programs are closed and the session itself is destroyed (Ctrl+Alt+F2 and other screens are all tty, except for the login screen at Ctrl+Alt+F1) == System details == ThinkPad E14 Gen 2 - AMD Ryzen 5500U Ubuntu 23.10 Mantic Minotaur (beta) ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gdm3 45~beta-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 27 11:06:43 2023 InstallationDate: Installed on 2022-04-23 (522 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: gdm3 UpgradeStatus: Upgraded to mantic on 2023-09-25 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2037520/+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 2023572] Re: SRU gjs 1.72.4 to jammy
You still get The following packages have been kept back: gjs (1.72.2-0ubuntu2 => 1.72.4-0ubuntu0.22.04.1) libgjs0g (1.72.2-0ubuntu2 => 1.72.4-0ubuntu0.22.04.1) all the time. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2023572 Title: SRU gjs 1.72.4 to jammy Status in gjs package in Ubuntu: Fix Released Status in gjs source package in Jammy: Fix Released Bug description: [ Impact ] That's the GNOME 42 stable update, including some fixes: https://gitlab.gnome.org/GNOME/gjs/-/commits/1.72.4 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME The test plan that will be used is documented at https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs [ Regression potential ] Gjs is fundamental part of the ubuntu desktop, so any failure of it may cause the desktop not even to boot (because it's being used by gdm too). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2023572/+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 2037345] Re: error saving a new vpn
Thank you for your bug report. The GNOME report is from an opensuse user which suggests it's not distro specific. ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => High ** Tags added: rls-mm-incoming -- 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/2037345 Title: error saving a new vpn Status in gnome-control-center package in Ubuntu: Confirmed Bug description: I tried adding a new openvpn. I filled in all the information, but after I click the save button, it returns me to the network settings list, but that vpn is not present. Release: 23.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2037345/+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 2037345] Re: error saving a new vpn
Same as https://bugs.launchpad.net/ubuntu/+source/network-manager- openvpn/+bug/2037011 and the gnome bug report is https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2668 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #2668 https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2668 -- 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/2037345 Title: error saving a new vpn Status in gnome-control-center package in Ubuntu: Confirmed Bug description: I tried adding a new openvpn. I filled in all the information, but after I click the save button, it returns me to the network settings list, but that vpn is not present. Release: 23.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2037345/+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 2030959] Update Released
The verification of the Stable Release Update for mutter has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2030959 Title: Cursor sometimes stutters after heavy shell animations in 42.9 Status in mutter package in Ubuntu: Invalid Status in mutter source package in Jammy: Fix Released Bug description: [ Impact ] Cursor sometimes stutters after heavy shell animations in 42.9 if there is no GUI animation in response to its movement. And it doesn't stop stuttering until GUI redraws occur (giving the frame clock an opportunity to measure lower GPU usage). This is different to the recent bug fix that probably caused it: Bug 2023766: * only occurs when moving over animated GUIs. * never recovers or corrects itself. * was spatial jittering at full frame rate. * reduced the frame rate of the GUI below it. This bug: * only occurs when moving over non-animated GUIs. * does recover and correct itself. * is stuttering at seemingly half frame rate, but perfect spatially. * does not reduce the frame rate of the the GUI below. I think the reason we only see this in 42 (jammy) is because that predates the change in the triple buffering algorithm to scale based on "dynamic max render time" alone. [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 and then reboot. [ Test Plan ] 1. Stress GNOME Shell maximally by repeatedly entering/leaving the overview and/or scrolling the app grid. 2. Stop suddenly and wiggle the mouse over some part of the desktop that DOES NOT respond to mouse movement. Such as the wallpaper or some blank grey space next to the app grid. Expect: The mouse cursor does not get stuck in half frame rate. [ Where problems could occur ] In desktop frame timing since the clutter frame clock is being changed. Although risk is minimal since we're just reverting to the pre-July state of that code. [ Other Info ] The patch being dropped was found to not really be required in GNOME 42: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023766/comments/13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2030959/+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 2030959] Re: Cursor sometimes stutters after heavy shell animations in 42.9
This bug was fixed in the package mutter - 42.9-0ubuntu5 --- mutter (42.9-0ubuntu5) jammy; urgency=medium [ Daniel van Vugt ] * Drop clutter-frame-clock-Avoid-rapidly-toggling-dynamic-max-re.patch. It was never really required in mutter 42 but has caused some new stutter elsewhere (LP: #2030959) -- Marco Trevisan (Treviño) Mon, 11 Sep 2023 15:39:50 +0200 ** Changed in: mutter (Ubuntu Jammy) 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/2030959 Title: Cursor sometimes stutters after heavy shell animations in 42.9 Status in mutter package in Ubuntu: Invalid Status in mutter source package in Jammy: Fix Released Bug description: [ Impact ] Cursor sometimes stutters after heavy shell animations in 42.9 if there is no GUI animation in response to its movement. And it doesn't stop stuttering until GUI redraws occur (giving the frame clock an opportunity to measure lower GPU usage). This is different to the recent bug fix that probably caused it: Bug 2023766: * only occurs when moving over animated GUIs. * never recovers or corrects itself. * was spatial jittering at full frame rate. * reduced the frame rate of the GUI below it. This bug: * only occurs when moving over non-animated GUIs. * does recover and correct itself. * is stuttering at seemingly half frame rate, but perfect spatially. * does not reduce the frame rate of the the GUI below. I think the reason we only see this in 42 (jammy) is because that predates the change in the triple buffering algorithm to scale based on "dynamic max render time" alone. [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 and then reboot. [ Test Plan ] 1. Stress GNOME Shell maximally by repeatedly entering/leaving the overview and/or scrolling the app grid. 2. Stop suddenly and wiggle the mouse over some part of the desktop that DOES NOT respond to mouse movement. Such as the wallpaper or some blank grey space next to the app grid. Expect: The mouse cursor does not get stuck in half frame rate. [ Where problems could occur ] In desktop frame timing since the clutter frame clock is being changed. Although risk is minimal since we're just reverting to the pre-July state of that code. [ Other Info ] The patch being dropped was found to not really be required in GNOME 42: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023766/comments/13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2030959/+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 2037509] [NEW] Gnome/Ubuntu desktop wayland
Public bug reported: Good day, I hasten to inform you about a problem that has not left your distribution for several releases in a row. When the Wayland secant is launched, some window elements for control are not active. In particular, the open new tab/settings expand/collapse buttons in browsers and ower applications do not work. Snap and Deb are equally susceptible to this problem. The solution is to login to X11 and immediately log out and log into Wayland again. In the current builds of the Minotaur, the problem appeared quite recently, with the release of the public beta; in the builds for developers, this problem did not occur. I will be very upset if this problem goes into release. Please correct it if possible. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-desktop (not installed) ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 27 11:14:33 2023 InstallationDate: Installed on 2023-06-21 (98 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230620) SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2037509 Title: Gnome/Ubuntu desktop wayland Status in ubuntu-meta package in Ubuntu: New Bug description: Good day, I hasten to inform you about a problem that has not left your distribution for several releases in a row. When the Wayland secant is launched, some window elements for control are not active. In particular, the open new tab/settings expand/collapse buttons in browsers and ower applications do not work. Snap and Deb are equally susceptible to this problem. The solution is to login to X11 and immediately log out and log into Wayland again. In the current builds of the Minotaur, the problem appeared quite recently, with the release of the public beta; in the builds for developers, this problem did not occur. I will be very upset if this problem goes into release. Please correct it if possible. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-desktop (not installed) ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 27 11:14:33 2023 InstallationDate: Installed on 2023-06-21 (98 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230620) SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2037509/+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 2033719] Re: Mouse pointer stutters in gnome-shell 45
Also proposed a Debian patch: https://salsa.debian.org/gnome-team/mutter/-/merge_requests/110 -- 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/2033719 Title: Mouse pointer stutters in gnome-shell 45 Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Committed Bug description: The mouse pointer stutters in gnome-shell 45~beta.1 on a lot of machines. Workaround: Put one of these in /etc/environment and reboot: MUTTER_DEBUG_KMS_THREAD_TYPE=user MUTTER_DEBUG_FORCE_KMS_MODE=simple To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2033719/+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 1865226] Re: gdm-smartcard pam config needs to be updated for Ubuntu and installed
gdm3 looks good to me, but I haven't accepted it yet as it depends on the gnome-settings-daemon patches and I think it's best to resolve those questions before accepting gdm3 into -proposed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1865226 Title: gdm-smartcard pam config needs to be updated for Ubuntu and installed Status in GNOME Settings Daemon: Fix Released Status in gdm3 package in Ubuntu: Fix Released Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in sssd package in Ubuntu: Fix Released Status in gdm3 source package in Focal: In Progress Status in gnome-settings-daemon source package in Focal: Incomplete Status in sssd source package in Focal: In Progress Status in gdm3 package in Debian: Fix Released Bug description: [ Impact ] the pam profile for gdm-smartcard is missing. gdm refuses to login with a smartcard. Looking at ubuntu/+source/gdm3, other pam files are pregenerated into debian/ and installed from there; gdm-smartcard is left out. [ Test case ] 1. When in GDM, insert a smartcard 2. The GDM interface should require for an user 3. The user should be set (or empty may be provided, depending on sssd configuration) 4. The smartcard PIN should be requested and once introduce the user must login. Note that this requires configuring sssd before, a simple local configuration could require having sssd.conf filled with: ```ini [sssd] enable_files_domain = True services = pam [certmap/implicit_files/$USER] matchrule = .*YOUR CARD IDENTIFIER* [pam] pam_cert_auth = True ``` The UI authentication can also be simulated via pamtester: # Must be ran as user sudo apt install pamtester pamtester -v gdm-smartcard $USER authenticate Expected output is + pamtester -v gdm-smartcard ubuntu authenticate pamtester: invoking pam_start(gdm-smartcard, ubuntu, ...) pamtester: performing operation - authenticate PIN for Test Organization Sub Int Token: pamtester: successfully authenticated --- Alternatively, if no smartcard or hardware is available, this can be tested and simulated using these scripts (they will reset the system setup at each run, but it's suggested to run them in a VM, lxd container or in a test installation): https://gist.github.com/3v1n0/287d02ca8e03936f1c7bba992173d47a - sudo apt install gdm3 pamtester softhsm2 openssl wget sssd gnutls-bin && \ sudo apt-mark auto gdm3 pamtester softhsm2 openssl wget sssd gnutls-bin - wget https://gist.github.com/3v1n0/287d02ca8e03936f1c7bba992173d47a/raw/sssd-gdm-smartcard-pam-auth-tester.sh - wget https://gist.github.com/3v1n0/287d02ca8e03936f1c7bba992173d47a/raw/sssd-softhism2-certificates-tests.sh - sudo bash ./sssd-gdm-smartcard-pam-auth-tester.sh The script will generate some fake CA authority, issue some certificates, will install them in some software-based smartcards (using softhsm2) and test that they work properly to login with gdm- smartcard. Using `WAIT` environment variable set (to any value) will make it to restart gdm at each iteration so that an user can try to access, using the username that launched the script and the pin of 123456. [ Regression potential ] Smartcard authentication using custom methods using via a custom configured system nss database may not work anymore. --- ProblemType: BugDistroRelease: Ubuntu 18.04 Package: gdm3 3.28.3-0ubuntu18.04.4 ProcVersionSignature: Ubuntu 5.3.0-24.26~18.04.2-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 14:30:30 2020 InstallationDate: Installed on 2016-05-23 (1376 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.Xsession: 2018-04-27T11:41:04.766901 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1865226/+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 2037497] Re: gnome-shell crashed with SIGSEGV in ?? (iris_dri.so) from end_query() from cogl_gl_create_timestamp_query() from cogl_onscreen_egl_swap_buffers_with_damage()
** Tags added: regression-release -- 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/2037497 Title: gnome-shell crashed with SIGSEGV in ?? (iris_dri.so) from end_query() from cogl_gl_create_timestamp_query() from cogl_onscreen_egl_swap_buffers_with_damage() Status in mesa package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: crash after update wayland session is not accessible anymore ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 27 05:52:26 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-26 (0 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230924) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.0-2ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: ?? () ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0 ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-13.so.0 Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2037497/+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 2033433] Re: Chromium leaks tens of gigabytes of pixmaps (in the Xorg process) after using hardware accelerated video
This is now released to beta and edge. And thank you, Jianhui, for contributing the fix! ** Changed in: chromium-browser (Ubuntu) Status: Fix Committed => Fix Released -- 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/2033433 Title: Chromium leaks tens of gigabytes of pixmaps (in the Xorg process) after using hardware accelerated video Status in chromium-browser package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Opinion Bug description: https://crbug.com/1467689 --- chromium 118.0.5966.0 2604 latest/edge Whenever I use chromium in a video session (meet, youtube) that used hardware acceleration, for a long time (like 20min or more), and then close it, the whole desktop freezes, and the laptop fan turns on. Logging in remotely I see that Xorg is at 100% CPU. The rest of the system is operational, but nothing graphical is. Just the mouse cursor moves around. SOMETIMES, if I wait a few minutes, Xorg resumes behaving normally, and I can use the desktop again, but most of the time I have to login remotely and kill -9 xorg (plain kill won't do it). With wayland, this does not happen. This could very well be an Xorg bug, but filing here first for visibility. $ lsgpu card0Intel Alderlake_p (Gen12) drm:/dev/dri/card0 └─renderD128 $ lscpu Architecture:x86_64 CPU op-mode(s):32-bit, 64-bit Address sizes: 46 bits physical, 48 bits virtual Byte Order:Little Endian CPU(s): 16 On-line CPU(s) list: 0-15 Vendor ID: GenuineIntel Model name:12th Gen Intel(R) Core(TM) i7-1270P CPU family: 6 Model: 154 Thread(s) per core: 2 Core(s) per socket: 12 Socket(s): 1 Stepping:3 CPU(s) scaling MHz: 41% CPU max MHz: 4800, CPU min MHz: 400, BogoMIPS:4992,00 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdp e1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqd q dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave a vx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept_ ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid rdseed adx smap clflushopt clwb intel_pt sha_ni xsaveopt xsavec xgetbv1 xsaves split_lock_detect avx_vnni dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp hwp_pkg_req hfi umip pku ospke waitpkg gfni vaes vpclmulqdq tme rdpid movdiri movdir64b fsrm md_clear serialize pconfig arch_lbr ibt flush_l1d arch_capabilities Virtualization features: Virtualization:VT-x Caches (sum of all): L1d: 448 KiB (12 instances) L1i: 640 KiB (12 instances) L2:9 MiB (6 instances) L3:18 MiB (1 instance) NUMA: NUMA node(s): 1 NUMA node0 CPU(s): 0-15 Vulnerabilities: Itlb multihit: Not affected L1tf: Not affected Mds: Not affected Meltdown: Not affected Mmio stale data: Not affected Retbleed: Not affected Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl Spectre v1:Mitigation; usercopy/swapgs barriers and __user pointer sanitization Spectre v2:Mitigation; Enhanced IBRS, IBPB conditional, RSB filling, PBRSB-eIBRS SW sequence Srbds: Not affected Tsx async abort: Not affected ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 6.2.0-27.28-generic 6.2.15 Uname: Linux 6.2.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Aug 29 16:47:30 2023 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2033433/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 2036749] Re: Sudo gnome-terminal fails
having the same issue. Both `gnome-terminal` or `sudo gnome-terminal` doesn't work. However, when I changed to Linux 6.2.0-32-generic, gnome-terminal works again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/2036749 Title: Sudo gnome-terminal fails Status in gnome-terminal package in Ubuntu: Confirmed Bug description: Can't launch a sudo version of gnome-terminal sudo gnome-terminal # Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: Failed to execute child process “dbus-launch” (No such file or directory) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-terminal 3.44.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Budgie:GNOME Date: Wed Sep 20 08:48:31 2023 InstallationDate: Installed on 2023-09-01 (19 days ago) InstallationMedia: Ubuntu-Budgie 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-09-02T06:36:32.926571 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2036749/+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 2037503] Re: [jammy]backport #1453 from upstream
** Description changed: In some cases, it was possible for a profile to be set (directly, or through a hold) even though it wasn't supported. Don't assert in those cases. The bug in question makes the gnome-control-center crash if an unsupported power profile is set using, say, powerprofilesctl. Should be trivial to cherry-pick without breaking other components. https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1453 + + I had to wait for this long because I expected a 42.x backport in the + backports repository of .1 release, but no one bothered to do such a + backport. -- 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/2037503 Title: [jammy]backport #1453 from upstream Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-control-center package in Debian: New Bug description: In some cases, it was possible for a profile to be set (directly, or through a hold) even though it wasn't supported. Don't assert in those cases. The bug in question makes the gnome-control-center crash if an unsupported power profile is set using, say, powerprofilesctl. Should be trivial to cherry-pick without breaking other components. https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1453 I had to wait for this long because I expected a 42.x backport in the backports repository of .1 release, but no one bothered to do such a backport. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2037503/+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 2036749] Re: Sudo gnome-terminal fails
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-terminal (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/2036749 Title: Sudo gnome-terminal fails Status in gnome-terminal package in Ubuntu: Confirmed Bug description: Can't launch a sudo version of gnome-terminal sudo gnome-terminal # Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: Failed to execute child process “dbus-launch” (No such file or directory) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-terminal 3.44.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Budgie:GNOME Date: Wed Sep 20 08:48:31 2023 InstallationDate: Installed on 2023-09-01 (19 days ago) InstallationMedia: Ubuntu-Budgie 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-09-02T06:36:32.926571 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2036749/+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 2037503] [NEW] [jammy]backport #1453 from upstream
Public bug reported: In some cases, it was possible for a profile to be set (directly, or through a hold) even though it wasn't supported. Don't assert in those cases. The bug in question makes the gnome-control-center crash if an unsupported power profile is set using, say, powerprofilesctl. Should be trivial to cherry-pick without breaking other components. https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1453 I had to wait for this long because I expected a 42.x backport in the backports repository of .1 release, but no one bothered to do such a backport. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: gnome-control-center (Debian) Importance: Undecided Status: New ** Tags: cherry-pick ** Changed in: gnome-control-center (Ubuntu) Status: New => Confirmed ** Description changed: In some cases, it was possible for a profile to be set (directly, or through a hold) even though it wasn't supported. Don't assert in those cases. + The bug in question makes the gnome-control-center crash if an unsupported + power profile is set using, say, powerprofilesctl. Should be trivial to cherry-pick without breaking other components. https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1453 ** Also affects: gnome-control-center Importance: Undecided Status: New ** No longer affects: gnome-control-center ** Also affects: gnome-control-center (Debian) Importance: Undecided Status: New -- 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/2037503 Title: [jammy]backport #1453 from upstream Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-control-center package in Debian: New Bug description: In some cases, it was possible for a profile to be set (directly, or through a hold) even though it wasn't supported. Don't assert in those cases. The bug in question makes the gnome-control-center crash if an unsupported power profile is set using, say, powerprofilesctl. Should be trivial to cherry-pick without breaking other components. https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1453 I had to wait for this long because I expected a 42.x backport in the backports repository of .1 release, but no one bothered to do such a backport. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2037503/+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
