[Desktop-packages] [Bug 1981952] [NEW] gnome-shell-extension-manager update feature doesn't work unless gnome-shell-extension-prefs is installed
Public bug reported: Impact -- There are 2 apps available in Ubuntu 22.04 LTS to manage extensions: the older Extensions app built as part of GNOME Shell but included in a separate binary package (gnome-shell-extension-prefs) and the newer third party Extension Manager from Matt Jakeman (packaged as gnome-shell-extension-manager). Extension Manager has a feature that automatically updates GNOME Shell extensions (like the Extensions app). However, the feature wasn't working unless the Extensions app was also installed because GNOME Shell didn't recognize the Extension Manager app as permitted to update GNOME Shell extensions. Test Case - 0. Make sure you don't have the gnome-shell-extension-prefs app installed. Open a terminal and run sudo apt remove gnome-shell-extension-prefs 1. Extract the bluetooth-quick-connect-27 archive to ~/.local/share/gnome-shell/extensions/ This should create a folder: ~/.local/share/gnome-shell/extensions/bluetooth-quick-conn...@bjarosze.gmail.com 2. Install the updated gnome-shell packages 3. Open a terminal and run sudo apt install gnome-shell-extension-manager gnome-shell-extension-manager 4. Log out 5. Log in 6. You should see a notification letting you know that there is an extension update available. 7. Click the notification. The Extension Manager app will open. 8. At the bottom of the app is a message like: "Updates are available. One extension will be updated on next login." Click the Log Out button. 9. Log in. 10. Open the Extension Manager app. Click the Bluetooth Quick Connect row. It should show the version number as greater than 27 (in my testing, the new version was 29 but new versions can be released at any time). You can also click the button to remove the extension if you want. Or you can turn the extension on if you want. What Could Go Wrong --- This is a minimal patch cherry-picked from the gnome-shell master branch. ** Affects: gnome-shell (Ubuntu) Importance: Low Status: Fix Committed ** Affects: gnome-shell (Ubuntu Jammy) Importance: Low Status: In Progress ** Tags: jammy ** Attachment added: "bluetooth-quick-connect-27.tar.xz" https://bugs.launchpad.net/bugs/1981952/+attachment/5603679/+files/bluetooth-quick-connect-27.tar.xz ** Also affects: gnome-shell (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu Jammy) Status: New => In Progress ** Changed in: gnome-shell (Ubuntu Jammy) Importance: Undecided => Low -- 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/1981952 Title: gnome-shell-extension-manager update feature doesn't work unless gnome-shell-extension-prefs is installed Status in gnome-shell package in Ubuntu: Fix Committed Status in gnome-shell source package in Jammy: In Progress Bug description: Impact -- There are 2 apps available in Ubuntu 22.04 LTS to manage extensions: the older Extensions app built as part of GNOME Shell but included in a separate binary package (gnome-shell-extension-prefs) and the newer third party Extension Manager from Matt Jakeman (packaged as gnome-shell-extension-manager). Extension Manager has a feature that automatically updates GNOME Shell extensions (like the Extensions app). However, the feature wasn't working unless the Extensions app was also installed because GNOME Shell didn't recognize the Extension Manager app as permitted to update GNOME Shell extensions. Test Case - 0. Make sure you don't have the gnome-shell-extension-prefs app installed. Open a terminal and run sudo apt remove gnome-shell-extension-prefs 1. Extract the bluetooth-quick-connect-27 archive to ~/.local/share/gnome-shell/extensions/ This should create a folder: ~/.local/share/gnome-shell/extensions/bluetooth-quick-conn...@bjarosze.gmail.com 2. Install the updated gnome-shell packages 3. Open a terminal and run sudo apt install gnome-shell-extension-manager gnome-shell-extension-manager 4. Log out 5. Log in 6. You should see a notification letting you know that there is an extension update available. 7. Click the notification. The Extension Manager app will open. 8. At the bottom of the app is a message like: "Updates are available. One extension will be updated on next login." Click the Log Out button. 9. Log in. 10. Open the Extension Manager app. Click the Bluetooth Quick Connect row. It should show the version number as greater than 27 (in my testing, the new version was 29 but new versions can be released at any time). You can also click the button to remove the extension if you want. Or you can turn the extension on if you want. What Could Go Wrong --- This is a minimal patch cherry-picked from the gnome-shell master branch. To manage notifications about this bug go to:
[Desktop-packages] [Bug 1698351] Re: Search in Nautilus Files does not allow sorting of results
Has this been fixed in the latest ubuntu 22.04 lts? If it has been fixed I cant find confirmation of it, the search for answers has been frustrating. Thanks to rickywales who mentioned "nemo" in his post on 2018-06-24, which I've installed and seem to have the search sort function I deserve, NAY, we all deserve! I try to resist posting anything on these sort of sites, so apologies for any issues I cause by doing so. I mainly wanted to thank rickywales. -- 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/1698351 Title: Search in Nautilus Files does not allow sorting of results Status in Nautilus: New Status in nautilus package in Ubuntu: Triaged Bug description: The version of nautilus/Files included with Ubuntu 17.04 no longer allows sorting of search results. Previously, sort was achieved by clicking on the column header titles. This no longer works. It represents a significant regression in the search feature. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1698351/+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 1965536] Re: Network icon disappeared in Unity
[Expired for network-manager-applet (Ubuntu) because there has been no activity for 60 days.] ** Changed in: network-manager-applet (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1965536 Title: Network icon disappeared in Unity Status in network-manager-applet package in Ubuntu: Expired Bug description: After upgrading to Ubuntu 22.04, the network icon at the top right of the screen in Unity has disappeared. The only way to change wireless network is now gear icon -> System Settings -> Network. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: network-manager-gnome 1.24.0-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Unity:Unity7:ubuntu Date: Fri Mar 18 14:07:50 2022 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d InstallationDate: Installed on 2020-07-14 (611 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 10.0.0.1 dev wlp0s20f3 proto dhcp metric 600 10.0.0.0/24 dev wg0 proto kernel scope link src 10.0.0.2 10.0.0.0/19 dev wlp0s20f3 proto kernel scope link src 10.0.7.124 metric 600 169.254.0.0/16 dev wlp0s20f3 scope link metric 1000 SourcePackage: network-manager-applet UpgradeStatus: Upgraded to jammy on 2022-03-18 (0 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.2 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1965536/+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 1973827] Re: Laptop freezes when recovering from suspend / sleep mode
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- 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/1973827 Title: Laptop freezes when recovering from suspend / sleep mode Status in gnome-shell package in Ubuntu: Expired Bug description: When I lock the laptop and unlock it - I have no issues. If I allow it to lock and then sleep, or close the lid and suspend - when I open it again, I get the login prompt but cannot use mouse / keyboard. The only solution I have is to press and hold the power button and force shutdown and then boot back up Description: Ubuntu 22.04 LTS Release: 22.04 No particular package being used. I would expect the system to recover from suspend / sleep and allow me to enter password. The laptop froze completely. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.10 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue May 17 21:45:17 2022 InstallationDate: Installed on 2022-04-22 (25 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade 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/1973827/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963767] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1963767 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1963767 Title: Microphone not working after suspend Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: I have Logitech BRIO 4k Pro webcam connected via its USB cable to Asus Vivobook Pro 16X OLED M7600QE-L2014X (90NB0V71-M02190) laptop. On Ubuntu 21.10 after suspend (`systemctl suspend`) webcam's microphone stops working (device is still there, but audio level is at zero all the time). To make it work again I need to do 2 things (just one is not sufficient): 1) Disconnect and connect webcam again to the laptop 2) Restart pulseaudio with `pulseaudio --kill; pulseaudio --start` Not sure whose fault it is, likely kernel driver, but the fact that pulseaudio needs to be restarted is concerning as well. Reproducible 100% for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Custom DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2 PackageArchitecture: amd64 Tags: impish Uname: Linux 5.16.11-xanmod1 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1963767/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963767] Re: Microphone not working after suspend
** Tags removed: impish ** Tags added: jammy ** Changed in: linux (Ubuntu) Status: Won't Fix => New ** Changed in: pulseaudio (Ubuntu) Status: Won't Fix => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1963767 Title: Microphone not working after suspend Status in linux package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: I have Logitech BRIO 4k Pro webcam connected via its USB cable to Asus Vivobook Pro 16X OLED M7600QE-L2014X (90NB0V71-M02190) laptop. On Ubuntu 21.10 after suspend (`systemctl suspend`) webcam's microphone stops working (device is still there, but audio level is at zero all the time). To make it work again I need to do 2 things (just one is not sufficient): 1) Disconnect and connect webcam again to the laptop 2) Restart pulseaudio with `pulseaudio --kill; pulseaudio --start` Not sure whose fault it is, likely kernel driver, but the fact that pulseaudio needs to be restarted is concerning as well. Reproducible 100% for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Custom DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2 PackageArchitecture: amd64 Tags: impish Uname: Linux 5.16.11-xanmod1 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1963767/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1981937] Re: Update gnome-shell to 42.3.1
This bug was fixed in the package gnome-shell - 42.3.1-1ubuntu1 --- gnome-shell (42.3.1-1ubuntu1) kinetic; urgency=medium * Merge with Debian (LP: #1981937) Remaining changes with Debian: - Replace gnome-backgrounds dep with ubuntu-wallpapers and Suggests gnome-themes-standard-data, gnome-backgrounds - Add some Recommends: + ubuntu-session (| gnome-session) to have the ubuntu session available + xserver-xorg-legacy + yaru-theme-gnome-shell for the default ubuntu theming + gnome-remote-desktop to provide remote desktop support by default - Moved some Recommends to Suggests: + chrome-gnome-shell - Break gnome-shell-extension-desktop-icons (<< 68ubuntu20.10.1) - gnome-shell-common.prerm: Remove deprecated ubuntu theme alternative - Update debian/gbp.conf with Ubuntu settings - debian/ubuntu-session-mods/ubuntu.json: Use Yaru's gnome-shell icons - debian/patches: Do not hang & crash if fingerprint service fails to start (LP: #1962566) - ubuntu/desktop_detect.patch: + add caching for desktop detection to avoid querying the current desktop env variable as iterate through the list each time. For the time of the Shell process, we can expect this env variable to stay stable. - ubuntu/lightdm-user-switching.patch: + Allow user switching when using LightDM. - ubuntu/lock_on_suspend.patch + Respect Ubuntu's lock-on-suspend setting. - ubuntu/background_login.patch + Change default background color as we modified the default GDM color for our ubuntu session. - ubuntu/gdm_alternatives.patch + Add support for GDM3 theme alternatives - main-show-an-error-message-on-gnome-shell-crash.patch, global-make-possible-to-set-debug-flags-dynamically.patch, main-increase-the-granularity-of-backtraces-in-SHELL_DEBU.patch, main-add-backtrace-crashes-all-and-backtrace-all.patch, sessionMode-add-support-for-debugFlags-parameter.patch: + Improve debug JS tracing for crash reports - ubuntu/smarter_alt_tab.patch: + quick alt-tab (without showing up the switcher) switch only between the last window of the last 2 applications to be focused instead of raising all windows of those apps. - magnifier-Show-cursor-when-magnifier-is-enabled-and-scale.patch: + Show monitor scaled cursor when magnifier is enabled - ubuntu/search-call-XUbuntuCancel-method-on-providers-when-no-dat.patch: + stop searches when requested from UI - magnifier-Show-cursor-when-magnifier-is-enabled-and-scale.patch - u/search-call-XUbuntuCancel-method-on-providers-when-no-dat.patch - ubuntu/resolve_alternate_theme_path.patch - ubuntu/secure_mode_extension.patch - ubuntu/keep-ubuntu-logo-bright-lp1867133-v1.patch - ubuntu/configure_login_screen.patch - ubuntu/layout-Make-starting-in-the-overview-optional.patch: + Makes dock replace overview easier - ubuntu/layout-Try-to-allocate-before-getting-size-of-tracke.patch: + Ensure windows don't get maximized under the panels / dock - debian/patches: Compute system background color from theme (LP: #1965727) - ubuntu/configure-login-screen.patch: Use bg color for initial system bg (LP: #1965727) - debian/patches: Ensure St.Entry's `selected-color` CSS property is honored (LP: #1878998) - ubuntu/support-loading-Yaru-variants: Handle dark/light variants better - d/p/use-favorites-strings: Only apply this to ubuntu session - debian/patches: Support configuring icons resource to use for mode - Revert-st-Apply-css-foreground-color-to-text-as-a-PangoAt.patch: + Ensure selected-text foreground color is preserved - u/main-Avoid-meta-finalize: Leak gjs context only on ubiquity sessions (LP: #1964458) - ubuntu/sessionMode-Add-support-for-configuring-an-icons-resource.patch: + Support loading iconsResourceName from session file - ubuntu/main-Support-loading-multiple-Yaru-theme-variants.patch: + Support loading Yaru theme variants (for accent color) - ubuntu/Revert-dash-Use-pin-instead-of-favorites gnome-shell (42.3.1-1) unstable; urgency=medium * New upstream release -- Jeremy Bicha Sun, 17 Jul 2022 22:54:29 +0200 ** Changed in: gnome-shell (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1981937 Title: Update gnome-shell to 42.3.1 Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: Triaged Bug description: Impact -- There is a new bugfix release in the stable 42 series (42.3 and 42.3.1) https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/42.3.1/NEWS It is hoped that this update will be included in Ubuntu 22.04.1 Test Case 1
[Desktop-packages] [Bug 1969315] Re: text in torrent info tabs change after opening it to gibberish
With two or three clicks on the properties tabs it is not noticeable or not happening let say, but if we click frequently one by one the tabs from left to righ or vice versa, confuses the text data through tabs also other parts of properties dialog, also if the clicking is not stopped transmission-gtk GUI crashes. I haven't passed this matter on upstream or forums yet. I have lived with it without going to propeties dialog. P.S. no other applications have this concern on my system. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1969315 Title: text in torrent info tabs change after opening it to gibberish Status in transmission package in Ubuntu: Confirmed Bug description: on transmission-gtk after opening the torrent's properties panel, the text at first it's showing ok, buy on mouse hover it changes to random text worked fine on 21.10 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: transmission-gtk 3.00-2ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 17 19:28:03 2022 SourcePackage: transmission UpgradeStatus: Upgraded to jammy on 2022-03-26 (22 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1969315/+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 1981937] [NEW] Update gnome-shell to 42.3.1
Public bug reported: Impact -- There is a new bugfix release in the stable 42 series (42.3 and 42.3.1) https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/42.3.1/NEWS It is hoped that this update will be included in Ubuntu 22.04.1 Test Case 1 - sudo apt install gnome-session gnome-shell-extensions Install the update. Log out. Select your name on the login screen. Click the gear button to choose a session to log in to. Finish logging in. Verify that things continue to work well for all these sessions: GNOME GNOME Classic Ubuntu Ubuntu on Xorg Test Case 2 --- Because a GNOME Shell update years ago broke some GNOME Shell extensions, it's also requested that we do a basic test of all the extensions included in the Ubuntu repositories. https://discourse.ubuntu.com/t/removal-of-gnome-shell-extension-from- universe-and-stop-auto-syncs/18437/9 Install all the extensions. Log out and then log back in. Use one of the Extensions apps to enable all the extensions. Verify that they can all be enabled without showing an error. What Could Go Wrong --- GNOME Shell is the heart of the Ubuntu desktop experience. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. GNOME Shell is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME ** Affects: gnome-shell (Ubuntu) Importance: Medium Status: Fix Committed ** Affects: gnome-shell (Ubuntu Jammy) Importance: Medium Status: Triaged ** Tags: jammy upgrade-software-version ** Also affects: gnome-shell (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: gnome-shell (Ubuntu Jammy) Status: New => Triaged -- 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/1981937 Title: Update gnome-shell to 42.3.1 Status in gnome-shell package in Ubuntu: Fix Committed Status in gnome-shell source package in Jammy: Triaged Bug description: Impact -- There is a new bugfix release in the stable 42 series (42.3 and 42.3.1) https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/42.3.1/NEWS It is hoped that this update will be included in Ubuntu 22.04.1 Test Case 1 - sudo apt install gnome-session gnome-shell-extensions Install the update. Log out. Select your name on the login screen. Click the gear button to choose a session to log in to. Finish logging in. Verify that things continue to work well for all these sessions: GNOME GNOME Classic Ubuntu Ubuntu on Xorg Test Case 2 --- Because a GNOME Shell update years ago broke some GNOME Shell extensions, it's also requested that we do a basic test of all the extensions included in the Ubuntu repositories. https://discourse.ubuntu.com/t/removal-of-gnome-shell-extension-from- universe-and-stop-auto-syncs/18437/9 Install all the extensions. Log out and then log back in. Use one of the Extensions apps to enable all the extensions. Verify that they can all be enabled without showing an error. What Could Go Wrong --- GNOME Shell is the heart of the Ubuntu desktop experience. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. GNOME Shell is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1981937/+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 1966911] Re: Cannot enroll finger on Jammy
This bug was fixed in the package libfprint - 1:1.94.3+tod1-0ubuntu2 --- libfprint (1:1.94.3+tod1-0ubuntu2) kinetic; urgency=medium * debian/patches: Ensure that identify works with old goodix driver (LP: #1966911) -- Marco Trevisan (Treviño) Sun, 17 Jul 2022 17:37:33 +0200 ** Changed in: libfprint (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fprintd in Ubuntu. https://bugs.launchpad.net/bugs/1966911 Title: Cannot enroll finger on Jammy Status in libfprint-2-tod1-goodix: Fix Committed Status in OEM Priority Project: Confirmed Status in fprintd package in Ubuntu: Won't Fix Status in libfprint package in Ubuntu: Fix Released Bug description: [Summary] Cannot enroll finger on Jammy. [Steps] 1. Install Jammy on XPS-9310 2. Open Gnome-control-center and select `User` 3. Enroll fingerprint [Expected] Enroll fingerprint without issue. [Actual] Cannot enroll fingerprint To manage notifications about this bug go to: https://bugs.launchpad.net/libfprint-2-tod1-goodix/+bug/1966911/+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 1981932] [NEW] Loud squeaking noise which disappears when audio is played
Public bug reported: When I connect my headset, theres a loud radio like noise which disappears when I play some audio but comes back as soon as i stop. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: costa 1294 F pulseaudio costa 6980 F alsamixer /dev/snd/controlC1: costa 1294 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jul 17 22:35:58 2022 InstallationDate: Installed on 2022-07-17 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Right Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [Nitro AN515-55, Realtek ALC295, Black Headphone Out, Right] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/19/2020 dmi.bios.release: 1.0 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.00 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Stonic_CMS dmi.board.vendor: CML dmi.board.version: V1.00 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.00 dmi.ec.firmware.release: 1.0 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.00:bd03/19/2020:br1.0:efr1.0:svnAcer:pnNitroAN515-55:pvrV1.00:rvnCML:rnStonic_CMS:rvrV1.00:cvnAcer:ct10:cvrV1.00:sku: dmi.product.family: Nitro 5 dmi.product.name: Nitro AN515-55 dmi.product.sku: dmi.product.version: V1.00 dmi.sys.vendor: Acer ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- 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/1981932 Title: Loud squeaking noise which disappears when audio is played Status in alsa-driver package in Ubuntu: New Bug description: When I connect my headset, theres a loud radio like noise which disappears when I play some audio but comes back as soon as i stop. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: costa 1294 F pulseaudio costa 6980 F alsamixer /dev/snd/controlC1: costa 1294 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jul 17 22:35:58 2022 InstallationDate: Installed on 2022-07-17 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Right Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [Nitro AN515-55, Realtek ALC295, Black Headphone Out, Right] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/19/2020 dmi.bios.release: 1.0 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.00 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Stonic_CMS dmi.board.vendor: CML dmi.board.version: V1.00 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.00 dmi.ec.firmware.release: 1.0 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.00:bd03/19/2020:br1.0:efr1.0:svnAcer:pnNitroAN515-55:pvrV1.00:rvnCML:rnStonic_CMS:rvrV1.00:cvnAcer:ct10:cvrV1.00:sku: dmi.product.family: Nitro 5 dmi.product.name: Nitro AN515-55 dmi.product.sku: dmi.product.version: V1.00 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1981932/+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 1927337] Re: [USB-Audio - RODECaster Pro, playback] Sound is distorted (21.04)
I have the same issue. -- 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/1927337 Title: [USB-Audio - RODECaster Pro, playback] Sound is distorted (21.04) Status in alsa-driver package in Ubuntu: Confirmed Bug description: I got a Rodecaster Pro USB device that has been causing trouble before and already lead to quirk handling in the kernel for the sample rate, see https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/sound/usb/format.c?h=v5.8#n412 The Rodecaster is running fine on my laptop, but on my desktop, only audio input is working. The audio output is distorted. It's played kind of very slowly. Interestingly, if the source is a video file, the video plays slower, e.g. YouTube in a browser. I have never seen anything like that before. I have tried to figure out what the cause might be and I think I have reached the end of where I can get to on my own. I have documented most things at https://ubuntuforums.org/showthread.php?t=2461568 Putting my last step it in a nutshell: I have booted both my computers with a plain Ubuntu 21.04 from a pen drive (it uses kernel version 5.11.0-16-generic) to make sure it's not some different configuration that I have set up over the years on my systems (both Ubuntu 20.04 with kernel 5.8.18). I attached the Rodecaster. It runs fine on my laptop, but not on my desktop (used the output test from). I then detected the card number with aplay -l I killed pulseaudio with pulseaudio -k I then played the same sample (encoded in 48000 Hz in PCM signed 32 bit little endian format) using aplay -f S32_LE -c 2 -r 48000 -D hw:x ~/sample.wav where x is the appropriate card number and the rest of the arguments meet the Rodecaster's narrow specification. It's playing fine on the laptop, but distorted on the desktop. As far as I understand using aplay this way without a plugin should send the file directly to the device, so I assume there's something on the way from aplay to the Rodecaster that's interfering (kernel or even some piece of hardware) - and that definitely is where my expertise ends (rather a little before :-)). I'll gladly contribute any information that could be useful and I will willingly help to debug this problem if it may be related to the kernel. If there's anything I can do, please let me know. Cheers, Oliver ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.461 CurrentDesktop: ubuntu:GNOME Date: Thu May 6 09:33:40 2021 LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Pro failed Symptom_Card: RODECaster Pro - RODECaster Pro Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [USB-Audio - RODECaster Pro, playback] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.40 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B550-A PRO (MS-7C56) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.40:bd10/30/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C56:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB550-APRO(MS-7C56):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C56 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1927337/+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 1973084] Re: transmission-daemon high RAM usage
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: transmission (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1973084 Title: transmission-daemon high RAM usage Status in transmission package in Ubuntu: Confirmed Bug description: Transmission uses a lot of RAM in ubuntu 22.04 server (arm64) runnign on a Raspberry Pi 4. It "eats" RAM and the RAM usage grows each hour until it crashes the system. I sideloaded transmission-daemon and its dependancies from debian 11 (arm64) locked the packages so apt won't update them and, ever since, this issue hasn't happened. Description:Ubuntu 22.04 LTS Release:22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1973084/+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 1971984] Re: pcscd 1.9.5-3 do not start automatically, only manual
@apinunt, pcscd is not started at boot but when an application is calling the WinSCard API. See https://ludovicrousseau.blogspot.com/2011/11/pcscd-auto-start-using-systemd.html Where do you find that pcscd manpage indicates it is started at boot? Interesting to know that this bug was already present in Ubuntu 21.10. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1971984 Title: pcscd 1.9.5-3 do not start automatically, only manual Status in pcsc-lite package in Ubuntu: Confirmed Bug description: Ubuntu Mate 22.04 with the latest updates. Problem is present with internal smart-card reader and also external usb smart-card reader. eid-viewer sees no card reader,but When i do: sudo pcscd -f it is working, also following the tips of Ludovic: https://ludovicrousseau.blogspot.com/2011/11/pcscd-auto-start-using-systemd.html sudo systemctl stop pcscd.socket sudo systemctl start pcscd.socket It is working until next restart. libacsccid1 version: 1.1.8-1 libccid version: 1.5.0-2 pcscd version: 1.9.5-3 eid-archive version: 2022.3 eid-mw version: 5.0.28v5.0.28-0u2204-1 eid-viewer version: 5.0.28v5.0.28-0u2204-1 In Firefox, my eid card is then also recognized, but only in the ESR version, but this is a know Mozilla bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+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 1966911] Re: Cannot enroll finger on Jammy
** Changed in: libfprint-2-tod1-goodix Status: Invalid => Fix Committed ** Changed in: libfprint (Ubuntu) Status: Won't Fix => Fix Committed ** Changed in: fprintd (Ubuntu) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fprintd in Ubuntu. https://bugs.launchpad.net/bugs/1966911 Title: Cannot enroll finger on Jammy Status in libfprint-2-tod1-goodix: Fix Committed Status in OEM Priority Project: Confirmed Status in fprintd package in Ubuntu: Won't Fix Status in libfprint package in Ubuntu: Fix Committed Bug description: [Summary] Cannot enroll finger on Jammy. [Steps] 1. Install Jammy on XPS-9310 2. Open Gnome-control-center and select `User` 3. Enroll fingerprint [Expected] Enroll fingerprint without issue. [Actual] Cannot enroll fingerprint To manage notifications about this bug go to: https://bugs.launchpad.net/libfprint-2-tod1-goodix/+bug/1966911/+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 1981717] Re: Ubuntu MATE & Budgie metapackages need to be updated for pipewire 0.3.54-2
Debian is reintroducing the previous named package as a transitional package but it needs to make it through the Debian new queue first. So updating the metapackages is less urgent but still nice to do. ** Bug watch added: Debian Bug tracker #1014639 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014639 ** Also affects: pipewire (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014639 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pipewire in Ubuntu. https://bugs.launchpad.net/bugs/1981717 Title: Ubuntu MATE & Budgie metapackages need to be updated for pipewire 0.3.54-2 Status in pipewire package in Ubuntu: Incomplete Status in ubuntu-budgie-meta package in Ubuntu: Fix Committed Status in ubuntu-mate-meta package in Ubuntu: Confirmed Status in pipewire package in Debian: Unknown Bug description: On Kinetic the latest pipewire 0.3.54-2 upgrade wants to remove: ubuntu-mate-core 1.284 ubuntu-mate-desktop 1.284 Please remove the conflict To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1981717/+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 1981863] Re: gnome calendar does not sync with google calendar
The same issue appears in gnome-todo... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1981863 Title: gnome calendar does not sync with google calendar Status in gnome-calendar package in Ubuntu: New Bug description: In the newest Ubuntu stable release (22.04), gnome 42.2, gnome calendar 41.2 does not sync calendar events from google calendar through GOA. But when an event is created in gnome calendar, it is synchronized with google calendar. So the synchronization works only in one direction. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1981863/+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 1971984] Re: pcscd 1.9.5-3 do not start automatically, only manual
Forgot to say, but the same problem exists on both a Dell G5, running Ubuntu Mate 21.10 and a Dell Latitude 3190 running Ubuntu Mate 22.04. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1971984 Title: pcscd 1.9.5-3 do not start automatically, only manual Status in pcsc-lite package in Ubuntu: Confirmed Bug description: Ubuntu Mate 22.04 with the latest updates. Problem is present with internal smart-card reader and also external usb smart-card reader. eid-viewer sees no card reader,but When i do: sudo pcscd -f it is working, also following the tips of Ludovic: https://ludovicrousseau.blogspot.com/2011/11/pcscd-auto-start-using-systemd.html sudo systemctl stop pcscd.socket sudo systemctl start pcscd.socket It is working until next restart. libacsccid1 version: 1.1.8-1 libccid version: 1.5.0-2 pcscd version: 1.9.5-3 eid-archive version: 2022.3 eid-mw version: 5.0.28v5.0.28-0u2204-1 eid-viewer version: 5.0.28v5.0.28-0u2204-1 In Firefox, my eid card is then also recognized, but only in the ESR version, but this is a know Mozilla bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+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 1971984] Re: pcscd 1.9.5-3 do not start automatically, only manual
We've been having to run "service pcscd start" manually to use the ACS ACR39U card reader each time. Man pcscd seems to say the service is started at boot, which it is not, though ideally we would like it to start when the reader is plugged into the computer and stop when it is unplugged. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1971984 Title: pcscd 1.9.5-3 do not start automatically, only manual Status in pcsc-lite package in Ubuntu: Confirmed Bug description: Ubuntu Mate 22.04 with the latest updates. Problem is present with internal smart-card reader and also external usb smart-card reader. eid-viewer sees no card reader,but When i do: sudo pcscd -f it is working, also following the tips of Ludovic: https://ludovicrousseau.blogspot.com/2011/11/pcscd-auto-start-using-systemd.html sudo systemctl stop pcscd.socket sudo systemctl start pcscd.socket It is working until next restart. libacsccid1 version: 1.1.8-1 libccid version: 1.5.0-2 pcscd version: 1.9.5-3 eid-archive version: 2022.3 eid-mw version: 5.0.28v5.0.28-0u2204-1 eid-viewer version: 5.0.28v5.0.28-0u2204-1 In Firefox, my eid card is then also recognized, but only in the ESR version, but this is a know Mozilla bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+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
