[Desktop-packages] [Bug 2020049] Re: gnome-shell crashed with SIGSEGV in clutter_stage_view_get_onscreen() from meta_stage_impl_add_onscreen_frame_info() from add_onscreen_frame_info() from post_finis
I haven't been able to reproduce this crash yet, but it looks like it's related to monitors disconnecting during sleep mode (which is normal but doesn't happen on all machines). So I will have to try more types of monitors... -- 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/2020049 Title: gnome-shell crashed with SIGSEGV in clutter_stage_view_get_onscreen() from meta_stage_impl_add_onscreen_frame_info() from add_onscreen_frame_info() from post_finish_frame() from try_post_latest_swap() Status in mutter package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 44.0-2ubuntu3, the problem page at https://errors.ubuntu.com/problem/c675f1d61cef940571272d7e655162f1b1cddab1 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2020049/+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 1981837] Re: Using DiNG triggers ubuntu-dock opacity
Just added a reminder to fix this in jammy, some time. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1981837 Title: Using DiNG triggers ubuntu-dock opacity Status in Gnome Shell Extension Desktop Icons Ng: Fix Released Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Won't Fix Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-desktop-icons-ng source package in Jammy: New Status in gnome-shell-extension-ubuntu-dock source package in Jammy: Triaged Bug description: Hi, Ubuntu 22.04 LTS jammy Linux 5.15.0-40-generic x86_64 x86_64 ubuntu-xorg / x11 I prefer panel and dock to become fully opaque only when windows are maximized. So I use this extension for panel : Transparent Top Bar (Adjustable transparency) which JustWorks™ in both Xorg and Wayland. In ubuntu-dock, dynamic-transparency is set through dconf-editor ( transparency-mode, min-alpha, max-alpha. ) When using DiNG under Wayland, opacity is triggered as if « desktop » was considered as a maximized window. Under Xorg, DiNG does not trigger dock opacity, as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons-ng/+bug/1981837/+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 1981837] Re: Using DiNG triggers ubuntu-dock opacity
This bug was never fixed in 22.04. Only in 22.10 and later. ** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: gnome-shell-extension-desktop-icons-ng (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy) Status: New => Triaged ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy) Importance: Undecided => Low ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1981837 Title: Using DiNG triggers ubuntu-dock opacity Status in Gnome Shell Extension Desktop Icons Ng: Fix Released Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Won't Fix Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-desktop-icons-ng source package in Jammy: New Status in gnome-shell-extension-ubuntu-dock source package in Jammy: Triaged Bug description: Hi, Ubuntu 22.04 LTS jammy Linux 5.15.0-40-generic x86_64 x86_64 ubuntu-xorg / x11 I prefer panel and dock to become fully opaque only when windows are maximized. So I use this extension for panel : Transparent Top Bar (Adjustable transparency) which JustWorks™ in both Xorg and Wayland. In ubuntu-dock, dynamic-transparency is set through dconf-editor ( transparency-mode, min-alpha, max-alpha. ) When using DiNG under Wayland, opacity is triggered as if « desktop » was considered as a maximized window. Under Xorg, DiNG does not trigger dock opacity, as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons-ng/+bug/1981837/+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 2023916] Re: Dock opacity is triggered by DING extension in Wayland
*** This bug is a duplicate of bug 1981837 *** https://bugs.launchpad.net/bugs/1981837 Bug 1981837 was never fixed in 22.04 so it's still the same bug. ** This bug has been marked a duplicate of bug 1981837 Using DiNG triggers ubuntu-dock opacity -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/2023916 Title: Dock opacity is triggered by DING extension in Wayland Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: Hi, if dock transparency is set to DYNAMIC, dock opacity is triggered by DING extension in Wayland. Works as expected under Xorg, dock background stays transparent while DING is enabled. Not the first time this happens ( https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension- desktop-icons-ng/+bug/1981837 ) it has been fixed for a moment and now issue is back with latest version of gnome-shell-extension-ubuntu- dock. I can see that issue on many installations / machines running Ubuntu 22.04 LTS. If of any interest, other gnome shell extensions ( transparent top bar, dash to panel ) are not impacted by this issue. So far. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu5.22.04.2.1 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 14 21:09:46 2023 InstallationDate: Installed on 2022-06-01 (378 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2023916/+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 2023746] Re: [SRU] Add Quectel EM05-G/EM05-CN PID information to support WWAN LVFS
** Attachment added: "modemmanager-jammy-proposed-1.20.0-1~ubuntu22.04.2_verification.log" https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/2023746/+attachment/5680094/+files/modemmanager-jammy-proposed-1.20.0-1~ubuntu22.04.2_verification.log ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/2023746 Title: [SRU] Add Quectel EM05-G/EM05-CN PID information to support WWAN LVFS Status in OEM Priority Project: Fix Committed Status in modemmanager package in Ubuntu: Fix Released Status in modemmanager source package in Jammy: Fix Committed Bug description: [SRU] Add Quectel EM05-G/EM05-CN PID information to support WWAN LVFS [ Impact ] The modemmanager v1.20.0 doesn't have Quectel EM05-G/EM05-CN PID (0x311/0x312) information. Fwupd can't base on modemmanager to identify the modem for supporting WWAN LVFS on a x86-based platform with Intel EHL, which is working with Jammy. (lp: #2019555) [ Test Plan ] Under Jammy environment, check fwupd (snap version) can identify EM05-G/EM05-CN modems to support WWAN LVFS on the target platform $ fwupdmgr refresh --force $ sudo fwupdmgr install # Select EM05-G/EM05-CN [ Where problems could occur ] The EM05-G/EM05-CN PID information is upstreamed to modemmanager v1.20.4 1. https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/b43cae70b078ee1af5b454cfd2b452e8dc711453 2. https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/e30b3a07a8d0f2bf5676cdcaf74da76f4af98b63 The Lunar and Mantic already working with modemmanager v1.20.4. The target platform WWAN LVFS function works well on Lunar and Mantic. The change parts just only add VID/PIDs for Quectel's new modems under the Quectel plugin. [ Other Info ] N/A To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2023746/+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 2023746] Re: [SRU] Add Quectel EM05-G/EM05-CN PID information to support WWAN LVFS
Hi Lukasz, TEST CASE: 1. Enable -proposed 2. $ sudo apt install modemmanager 3. $ apt list --installed | grep modem 4. $ sudo apt purge fwupd; sudo reboot 5. $ sudo snap install fwupd --channel=latest/candidate --devmode 6. $ snap list | grep fwupd 7. $ fwupdmgr --version 8. Add remote channel configuration for WWAN 9. $ fwupdmgr refresh --force 10. $ fwupdmgr install 0. Cancel 1. 104f79ae6794ff3bbd28cb82ddb67b3d6946d6ab (EM05-G) 2. 2292ae5236790b47884e37cf162dcf23bfcd1c60 (Embedded Controller) 3. 04e17fcf7d3de91da49a163ffe4907855c3648be (MTFDHBK1T0TDP) 4. a45df35ac0e948ee180fe216a5f703f32dda163f (System Firmware) Choose device [0-4]: 1 0. Cancel 1. EM05GFAR07A07M1G_01.019.01.019 2. EM05GFAR07A07M1G_01.018.01.018 3. EM05GFAR07A07M1G_01.016.01.016 4. EM05GFAR07A07M1G_01.015.01.015 Choose release [0-4]: VERIFICATION DONE The new modem firmware can be detected correctly. For the detailed verification log, please reference the attached modemmanager-jammy-proposed-1.20.0-1~ubuntu22.04.2_verification.log The tag will be changed to "verification-done-jammy". Tks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/2023746 Title: [SRU] Add Quectel EM05-G/EM05-CN PID information to support WWAN LVFS Status in OEM Priority Project: Fix Committed Status in modemmanager package in Ubuntu: Fix Released Status in modemmanager source package in Jammy: Fix Committed Bug description: [SRU] Add Quectel EM05-G/EM05-CN PID information to support WWAN LVFS [ Impact ] The modemmanager v1.20.0 doesn't have Quectel EM05-G/EM05-CN PID (0x311/0x312) information. Fwupd can't base on modemmanager to identify the modem for supporting WWAN LVFS on a x86-based platform with Intel EHL, which is working with Jammy. (lp: #2019555) [ Test Plan ] Under Jammy environment, check fwupd (snap version) can identify EM05-G/EM05-CN modems to support WWAN LVFS on the target platform $ fwupdmgr refresh --force $ sudo fwupdmgr install # Select EM05-G/EM05-CN [ Where problems could occur ] The EM05-G/EM05-CN PID information is upstreamed to modemmanager v1.20.4 1. https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/b43cae70b078ee1af5b454cfd2b452e8dc711453 2. https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/e30b3a07a8d0f2bf5676cdcaf74da76f4af98b63 The Lunar and Mantic already working with modemmanager v1.20.4. The target platform WWAN LVFS function works well on Lunar and Mantic. The change parts just only add VID/PIDs for Quectel's new modems under the Quectel plugin. [ Other Info ] N/A To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2023746/+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 2023746] Re: [SRU] Add Quectel EM05-G/EM05-CN PID information to support WWAN LVFS
** Changed in: oem-priority Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/2023746 Title: [SRU] Add Quectel EM05-G/EM05-CN PID information to support WWAN LVFS Status in OEM Priority Project: Fix Committed Status in modemmanager package in Ubuntu: Fix Released Status in modemmanager source package in Jammy: Fix Committed Bug description: [SRU] Add Quectel EM05-G/EM05-CN PID information to support WWAN LVFS [ Impact ] The modemmanager v1.20.0 doesn't have Quectel EM05-G/EM05-CN PID (0x311/0x312) information. Fwupd can't base on modemmanager to identify the modem for supporting WWAN LVFS on a x86-based platform with Intel EHL, which is working with Jammy. (lp: #2019555) [ Test Plan ] Under Jammy environment, check fwupd (snap version) can identify EM05-G/EM05-CN modems to support WWAN LVFS on the target platform $ fwupdmgr refresh --force $ sudo fwupdmgr install # Select EM05-G/EM05-CN [ Where problems could occur ] The EM05-G/EM05-CN PID information is upstreamed to modemmanager v1.20.4 1. https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/b43cae70b078ee1af5b454cfd2b452e8dc711453 2. https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/e30b3a07a8d0f2bf5676cdcaf74da76f4af98b63 The Lunar and Mantic already working with modemmanager v1.20.4. The target platform WWAN LVFS function works well on Lunar and Mantic. The change parts just only add VID/PIDs for Quectel's new modems under the Quectel plugin. [ Other Info ] N/A To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2023746/+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 1779890] Re: gvfsd process does not have the KRB5CCNAME environment set
Attached is a v4 for Jammy that updates the version to ubuntu0.1 in both d/changelog and d/tracker-extract.postinst ** Patch added: "Debdiff for tracker-miners on Jammy V4" https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1779890/+attachment/5680090/+files/lp1779890_jammy_v4.debdiff ** Patch removed: "Debdiff for tracker-miners on Jammy V3" https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1779890/+attachment/5679385/+files/lp1779890_jammy_v3.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1779890 Title: gvfsd process does not have the KRB5CCNAME environment set Status in gvfs package in Ubuntu: New Status in tracker-miners package in Ubuntu: Fix Released Status in gvfs source package in Bionic: Invalid Status in tracker-miners source package in Bionic: Won't Fix Status in gvfs source package in Focal: Invalid Status in tracker-miners source package in Focal: In Progress Status in gvfs source package in Jammy: Invalid Status in tracker-miners source package in Jammy: In Progress Status in gvfs source package in Kinetic: Invalid Status in tracker-miners source package in Kinetic: In Progress Status in gvfs source package in Lunar: Invalid Status in tracker-miners source package in Lunar: Fix Released Bug description: [ Impact ] The KRB5CCNAME environment variable points to the Kerberos ticket of the current machine and this ticket is used for authentication in Active Directory servers. This variable is set by pam_sss when the user authenticates and can be used by other processes, such as gio, to skip the credentials input when accessing network shares, for example. Some services rely on gvfs-daemon in order to properly function, such as tracker-extract-3.service and tracker-miner-fs-3.service, which means they will ask for the gvfs-daemon to be initialized when they are executed by systemd. This creates problems if one service that relies on gvfsd is started too early, as it would result in gvfsd being started too early as well. As of version 3.1 of tracker-miners, the install target of tracker- miners-fs-3.service was set to gnome-session.target: https://gitlab.gnome.org/GNOME/tracker-miners/-/merge_requests/283 However, the tracker-extract-3.service was not updated and its target is still default.target, which is too early for the service to start. Starting tracker-extract too early is also starting gvfsd too early, before the session environment gets fully updated. Which means that gvfsd does not have the KRB5CCNAME variable and can not do any operations with it. Tracker-extract is supposed to be a helper service managed by tracker- miner-fs-3.service. By using a [Install] section, we are actually telling systemd that it should manage this service as well, when it shouldn't. So, by removing the [Install] section and having tracker-miner- fs-3.service being tied to gnome-session.target, we fix the issue of gvfsd starting too early without the updated session environment. [ Test Plan ] In order to test this issue, it's required to have an Active Directory server running. 1) Authenticate with an AD user (as this would set the KRB5CCNAME env); 2) Check gvfsd environment. This can be done by running: cat /proc/$(pidof gvfsd)/environ | xargs --null -n1 You will be able to see that it does not have the variable listed. 3) Check that the information mentioned above about tracker-miner-fs- 3.service is true. 4) Disable tracker-extract-3.service (This is a bit tricky, since its target was default.target. The easiest way is to remove the symlink that systemd created when enabling the unit, located under /etc/systemd/user/default.target.wants/tracker-extract-3.service 5) Reboot the machine; 6) Repeat steps 1 and 2. This will show that gvfsd is now started with the proper environment. Is not enough to look at ptree and the pids of the processes, instead it's better to look into the session logs with: journalctl --user -b And check the order in which the services were started and when they were triggered. Test packages are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf320070-test After installing test packages of tracker-miners, KRB5CCNAME should be set in gvfs environment upon login to gnome. [ Where problems could occur ] The tracker project is a search engine that speeds up search operations in Gnome. The tracker-miners is the indexing daemon that populates the database with information, so changing its start does not affect the system behavior. This changes fix the startup of gvfs-daemon.service, which could delay services that relied on it running to be executed. [ Other info ] This was fixed upstream by the following commit:
[Desktop-packages] [Bug 2014954] Re: Backport Intel Mutual Authentications - FCC Lock
Thanks Lucas and Seb, I re-uploaded the debdiff patch file for theses 3 series. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/2014954 Title: Backport Intel Mutual Authentications - FCC Lock Status in OEM Priority Project: Confirmed Status in libmbim package in Ubuntu: In Progress Status in libmbim source package in Jammy: New Status in libmbim source package in Lunar: New Bug description: [ Impact ] There exist no formal API to do the FCC unlock procedure[1] in the latest version of the modemmanger. But there is a merged commit[2] that provide this functionality for intel WWAN cards in the upstream project. Lenovo have several laptops using the Intel WWAN cards, and Lenovo are struggling to give a decent way to run the FCC unlock service without this. [ Test Plan ] OEM enablement engineers and Lenovo engineers will help to test if the FCC unlock would work on certain laptops with the help of a custom package[1] provided by Lenovo which contains the FCC unlock script. [ Where problems could occur ] This is a completely new feature to support Intel WWAN cards mutal authentication, which does not affect other existing features. But the feature itself might have bugs and glitches since it is a brand new one and is not widely tested by the laptop vendors, still it is better than nothing. [ Other Info ] [1] FCC unlock procedure: https://modemmanager.org/docs/modemmanager/fcc-unlock/ [2] intel-mutual-authentication: new service, fcc-lock: https://gitlab.freedesktop.org/mobile-broadband/libmbim/-/merge_requests/157 - when the device is first shipped or comes out of the factory, it should be protected with a lock till the device reaches the end user. This FCC lock feature will ensure the device is secured till its unlocked. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2014954/+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 2014954] Re: Backport Intel Mutual Authentications - FCC Lock
for jammy ** Patch added: "libmbim_1.28.0-1~ubuntu20.04.2.debdiff" https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/2014954/+attachment/5680079/+files/libmbim_1.28.0-1~ubuntu20.04.2.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/2014954 Title: Backport Intel Mutual Authentications - FCC Lock Status in OEM Priority Project: Confirmed Status in libmbim package in Ubuntu: In Progress Status in libmbim source package in Jammy: New Status in libmbim source package in Lunar: New Bug description: [ Impact ] There exist no formal API to do the FCC unlock procedure[1] in the latest version of the modemmanger. But there is a merged commit[2] that provide this functionality for intel WWAN cards in the upstream project. Lenovo have several laptops using the Intel WWAN cards, and Lenovo are struggling to give a decent way to run the FCC unlock service without this. [ Test Plan ] OEM enablement engineers and Lenovo engineers will help to test if the FCC unlock would work on certain laptops with the help of a custom package[1] provided by Lenovo which contains the FCC unlock script. [ Where problems could occur ] This is a completely new feature to support Intel WWAN cards mutal authentication, which does not affect other existing features. But the feature itself might have bugs and glitches since it is a brand new one and is not widely tested by the laptop vendors, still it is better than nothing. [ Other Info ] [1] FCC unlock procedure: https://modemmanager.org/docs/modemmanager/fcc-unlock/ [2] intel-mutual-authentication: new service, fcc-lock: https://gitlab.freedesktop.org/mobile-broadband/libmbim/-/merge_requests/157 - when the device is first shipped or comes out of the factory, it should be protected with a lock till the device reaches the end user. This FCC lock feature will ensure the device is secured till its unlocked. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2014954/+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 2014954] Re: Backport Intel Mutual Authentications - FCC Lock
for mantic ** Patch added: "libmbim_1.28.4-2ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/2014954/+attachment/5680078/+files/libmbim_1.28.4-2ubuntu1.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/2014954 Title: Backport Intel Mutual Authentications - FCC Lock Status in OEM Priority Project: Confirmed Status in libmbim package in Ubuntu: In Progress Status in libmbim source package in Jammy: New Status in libmbim source package in Lunar: New Bug description: [ Impact ] There exist no formal API to do the FCC unlock procedure[1] in the latest version of the modemmanger. But there is a merged commit[2] that provide this functionality for intel WWAN cards in the upstream project. Lenovo have several laptops using the Intel WWAN cards, and Lenovo are struggling to give a decent way to run the FCC unlock service without this. [ Test Plan ] OEM enablement engineers and Lenovo engineers will help to test if the FCC unlock would work on certain laptops with the help of a custom package[1] provided by Lenovo which contains the FCC unlock script. [ Where problems could occur ] This is a completely new feature to support Intel WWAN cards mutal authentication, which does not affect other existing features. But the feature itself might have bugs and glitches since it is a brand new one and is not widely tested by the laptop vendors, still it is better than nothing. [ Other Info ] [1] FCC unlock procedure: https://modemmanager.org/docs/modemmanager/fcc-unlock/ [2] intel-mutual-authentication: new service, fcc-lock: https://gitlab.freedesktop.org/mobile-broadband/libmbim/-/merge_requests/157 - when the device is first shipped or comes out of the factory, it should be protected with a lock till the device reaches the end user. This FCC lock feature will ensure the device is secured till its unlocked. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2014954/+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 2014954] Re: Backport Intel Mutual Authentications - FCC Lock
for lunar ** Patch added: "libmbim_1.28.2-1ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/2014954/+attachment/5680077/+files/libmbim_1.28.2-1ubuntu1.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/2014954 Title: Backport Intel Mutual Authentications - FCC Lock Status in OEM Priority Project: Confirmed Status in libmbim package in Ubuntu: In Progress Status in libmbim source package in Jammy: New Status in libmbim source package in Lunar: New Bug description: [ Impact ] There exist no formal API to do the FCC unlock procedure[1] in the latest version of the modemmanger. But there is a merged commit[2] that provide this functionality for intel WWAN cards in the upstream project. Lenovo have several laptops using the Intel WWAN cards, and Lenovo are struggling to give a decent way to run the FCC unlock service without this. [ Test Plan ] OEM enablement engineers and Lenovo engineers will help to test if the FCC unlock would work on certain laptops with the help of a custom package[1] provided by Lenovo which contains the FCC unlock script. [ Where problems could occur ] This is a completely new feature to support Intel WWAN cards mutal authentication, which does not affect other existing features. But the feature itself might have bugs and glitches since it is a brand new one and is not widely tested by the laptop vendors, still it is better than nothing. [ Other Info ] [1] FCC unlock procedure: https://modemmanager.org/docs/modemmanager/fcc-unlock/ [2] intel-mutual-authentication: new service, fcc-lock: https://gitlab.freedesktop.org/mobile-broadband/libmbim/-/merge_requests/157 - when the device is first shipped or comes out of the factory, it should be protected with a lock till the device reaches the end user. This FCC lock feature will ensure the device is secured till its unlocked. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2014954/+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 1968792] Re: After F10 menu Enter key opens file instead of menu action
** Changed in: nautilus Status: Unknown => Fix Released -- 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/1968792 Title: After F10 menu Enter key opens file instead of menu action Status in Nautilus: Fix Released Status in nautilus package in Ubuntu: Fix Released Bug description: When pressing F10 on Nautilus, the menu pops. Then the arrow keys navigate the menu, but when pressing Enter, does not execute the selected menu action. IE: if folder is selected, press F10, menu pops down arrow to choose "open in terminal", press enter, Nautilus navigates to the selected folder instead of opening terminal in the current location. Also with files: if text (or any) file is selected, press F10, menu pops, choose any action with arrows, press enter, gedit (or whatever) opens selected file. Tested all actions then selecting files or folders, same result. Expected behavior: After pressing F10, focus should be on the menu that just pops up, until ESC is pressed or mouse clicks somewhere else or focus is shifted by other means, so when pressing ENTER action gets performed. IE: file or folder is selected, press F10, down arrow to select PROPERTIES, press ENTER, PROPERTIES of selected item are shown. Also tried with SPACEBAR (just in case), but the result is the same. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1: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 CasperMD5CheckMismatches: ./preseed/ubuntu.seed ./pool/restricted/n/nvidia-graphics-drivers-470/nvidia-kernel-source-470_470.103.01-0ubuntu2_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/libnvidia-gl-510_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-compute-utils-510_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-driver-495_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-driver-510_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-kernel-common-510_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-kernel-source-510_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-utils-510_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/xserver-xorg-video-nvidia-510_510.60.02-0ubuntu1_amd64.deb CasperMD5CheckResult: fail CasperVersion: 1.468 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 12 23:08:24 2022 ExecutablePath: /usr/bin/nautilus GsettingsChanges: LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince42.1-2 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1968792/+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 2022885] Re: ubuntu-dock v82 unresponsive to mouse clicks on Xorg unless at least one window is open
This bug was fixed in the package gnome-shell-extension-ubuntu-dock - 84ubuntu1 --- gnome-shell-extension-ubuntu-dock (84ubuntu1) mantic; urgency=medium [ WhiredPlanck ] * Update Simplified Chinese translation * Update Traditional Chinese translation [ Marco Trevisan (Treviño) ] * New upstream release * Revert "dash: Compute number of icons easily and correctly to show the separator" * dash: Take in account the number of removed favorites to add the separator * docking: Always affect the input region when adding the dock (LP: #2022885) [ addieStarr ] * Fixed dash-js app issue -- Marco Trevisan (Treviño) Thu, 15 Jun 2023 22:51:34 +0200 ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/2022885 Title: ubuntu-dock v82 unresponsive to mouse clicks on Xorg unless at least one window is open Status in Dash to dock: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Bug description: After starting an application from dock and closing it dock becomes unresponsive if no apps are open. I start an app from dock and then close it. click on any icon in the dock has no effect. now I can start the dash with super+a and then start an app from the dash or start the terminal with ctrl+alt+t now the dock works until an app (any app) is active. when I close all apps dock becomes unresponsive again. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell-extension-ubuntu-dock 82ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-21.21-generic 6.2.6 Uname: Linux 6.2.0-21-generic x86_64 ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jun 5 08:12:29 2023 InstallationDate: Installed on 2023-05-21 (14 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230521) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/2022885/+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 2017076] Re: default Chinese font in snap apps is ugly
No worry, now things make sense, thanks for testing and confirming it's fixed! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/2017076 Title: default Chinese font in snap apps is ugly Status in Snappy: Fix Released Status in fontconfig package in Ubuntu: Invalid Status in language-selector package in Ubuntu: Invalid Bug description: After installs Ubuntu 23.04 with Chinese language selected, the default font is chosen to AR PL UMing CN, which is very ugly. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: fontconfig 2.14.1-3ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Thu Apr 20 14:18:45 2023 InstallationDate: Installed on 2023-04-20 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=zh_CN.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: fontconfig UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/2017076/+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 2024014] Re: Deleting files via nautilus windows causes the file list to refresh incorrectly.
*** This bug is a duplicate of bug 2022851 *** https://bugs.launchpad.net/bugs/2022851 ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** This bug has been marked a duplicate of bug 2022851 Nautilus displays invalid directory content after deleting -- 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/2024014 Title: Deleting files via nautilus windows causes the file list to refresh incorrectly. Status in nautilus package in Ubuntu: New Bug description: This problem started between kinetic (which worked) and lunar (which does not). If I delete a file the updated file listing in nautilus is incorrect, showing the deleted file and removing a random file/directory that is still technically present. Refreshing via ctrl+r restores the file view to the real state. This bug also happens when moving files to directories. To reproduce this bug: * create files/directories in a directory `touch file{1..9} ; mkdir -p dir{1..9}` * open the directory in nautilus and delete a file (in my case file6) This bug does happen when the file is permanently deleted using nautilus, however it doesn't happen when the file is deleted via a terminal with the nautilus window open in that directory. This bug is also reproduced on any other nautilus windows open and viewing the same directory. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: nautilus 1:44.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jun 15 11:36:28 2023 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'initial-size' b'(1092, 681)' InstallationDate: Installed on 2023-05-28 (18 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: nautilus-extension-gnome-terminal 3.48.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2024014/+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 2023417] Re: Update nautilus to 44.2.1
The Nautilus build tests passes and I successfully completed Test Cases 1, 2, and 3 with nautilus 44.2.1-0ubuntu1 on Ubuntu 23.04. -- 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/2023417 Title: Update nautilus to 44.2.1 Status in nautilus package in Ubuntu: Fix Released Status in nautilus source package in Lunar: Fix Committed Bug description: Impact -- This is a new stable release in the GNOME 44 series https://gitlab.gnome.org/GNOME/nautilus/-/blob/44.2.1/NEWS (The current version in Ubuntu 23.04 is 44.0) Test Case 0 --- Nautilus has a build test suite that will fail the build if the tests fail. Test Case 1 --- Install the update Make sure that Nautilus isn't running, either by logging out and logging back in or by running pkill nautilus Run Nautilus and ensure that it still works well Test Case 2 --- 1. Install the update 2. Run pkill nautilus to ensure all open nautilus windows are closed 3. Open Nautilus 4. Click Ctrl+N to open a second Nautilus window 5. In the first Nautilus window, open the Preferences dialog. This dialog is modal to this window (can't be moved away from centered in the window). Close Preferences. Close this window. 6. In the second Nautilus window, open the Preferences dialog. The preferences dialog should be modal to the window (and it should not crash). https://gitlab.gnome.org/GNOME/nautilus/-/issues/2986 Test Case 3 --- 1. Install the update 2. Open a terminal and run sudo apt install gnome-sushi 3. Open Nautilus 4. Open the preferences dialog and turn on Expandable Folders in List View. Close the preferences dialog. 5. Press Ctrl+l to focus the address bar and enter /usr/share 6. Use the space bar to open the Sushi previewer on one of the folders 7. With the Sushi preview window open, use the down arrow keys to navigate down to other folders. Keep going down until you go beyond the first page of results in Nautilus. The main nautilus window should scroll down to show these results focused. https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/1221 What Could Go Wrong --- nautilus is the default GUI file browser for Ubuntu Desktop. Other desktop flavors use other file browsers. As a component of GNOME Core, there is a micro-release exception for nautilus https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- This update requires gtk4 4.10.4 (LP: #2023031) This update drops 4 cherry-picked patches that have been applied in the new release It also cherry-picks 3 patches from the stable gnome-44 branch (future nautilus 44.3). It also includes a patch included in 44.2 but dropped from 44.2.1 because it was not clear how long it would take for gtk4 4.10.4 to be released. But gtk 4.10.4 was released only a few hours later. https://gitlab.gnome.org/GNOME/nautilus/-/commit/e193b2ce5d5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2023417/+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 2024064] [NEW] libssh dep8 fails on ppc64el/s390x
Public bug reported: Reporting this bug for documentation purposes. libssh's dep8 test is failing on ppc64el/s390x. I tried reproducing it in a ppc64el canonistack box, but the test always passes there. migration-reference/0 didn't help. It's interesting to notice that the test succeeds on debci, which leads me to believe that this is something really particular to our autopkgtest infra. ** Affects: libssh (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuse -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libssh in Ubuntu. https://bugs.launchpad.net/bugs/2024064 Title: libssh dep8 fails on ppc64el/s390x Status in libssh package in Ubuntu: New Bug description: Reporting this bug for documentation purposes. libssh's dep8 test is failing on ppc64el/s390x. I tried reproducing it in a ppc64el canonistack box, but the test always passes there. migration-reference/0 didn't help. It's interesting to notice that the test succeeds on debci, which leads me to believe that this is something really particular to our autopkgtest infra. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libssh/+bug/2024064/+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 2017076] Re: default Chinese font in snap apps is ugly
@Sebastien: Sorry for confusing the installer with the ISO (which is used for installing...). My point was that at first login after a Chinese install, you have the versions of firefox and core22 from April, and thus see the issue if you open FF before having refreshed the snaps. One concern of mine was that I feared that the FF default font would be stuck somehow at the value when FF was first opened. ( Yes, I'm a snap illiterate. :/ ) But I just tested, and saw that the FF default font changed to the expected one once I had run "snap refresh". So yes, the issue has been resolved. ** Changed in: snappy Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/2017076 Title: default Chinese font in snap apps is ugly Status in Snappy: Fix Released Status in fontconfig package in Ubuntu: Invalid Status in language-selector package in Ubuntu: Invalid Bug description: After installs Ubuntu 23.04 with Chinese language selected, the default font is chosen to AR PL UMing CN, which is very ugly. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: fontconfig 2.14.1-3ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Thu Apr 20 14:18:45 2023 InstallationDate: Installed on 2023-04-20 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=zh_CN.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: fontconfig UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/2017076/+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.socket is disabled after installation
Anyone willing to provide a debdiff (changes + changelog) to fix this issue in Jammy, Kinetic and Lunar? As Sebastien mentioned in comment #29, this bug has ~ubuntu-sponsors subscribed but there is no "ready-to- upload" debdiff attached. -- 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.socket is disabled after installation Status in pcsc-lite package in Ubuntu: Fix Released Status in pcsc-lite source package in Jammy: Triaged Status in pcsc-lite source package in Kinetic: Triaged Status in pcsc-lite source package in Lunar: Triaged Status in pcsc-lite package in Debian: Fix Released Bug description: [ Impact ] The pscc-lite package provides an open source implementation of PC/SC, the de-facto standard to interface Personal Computers with Smart Cards/Readers. This bug is in the upstream debian packaging, and results in the pcscd.socket being disabled after installation. This prevents automatic startup of the associated pcscd.service, thus preventing automatic handling of Smart Cards/Readers w/out manual intervention to enable the socket (which doesn't persist across reboots). This is especially painful for users that require Smart Authentication for login. [ Test Plan ] Steps to reproduce: 1. If installed, remove and do a fresh install of the package pcscd (the sole version released for jammy is 1.9.5-3). 2. Verify that the pcscd.socket is disabled: $ systemctl status pcscd.socket ○ pcscd.socket - PC/SC Smart Card Daemon Activation Socket Loaded: loaded (/lib/systemd/system/pcscd.socket; disabled; vendor preset: enabled) Active: inactive (dead) Triggers: ● pcscd.service Listen: /run/pcscd/pcscd.comm (Stream) 3. [Optional] insert a Smart Card or Crypto Token (e.g. a Yubikey or Nitrokey) that's known to work on Ubuntu and verify that it fails to work. Repeating the same steps with a package built with the patch attached to comment #27 should ensure that the socket is enabled, and that interaction with a Smart Card or Crypto Token should work w/out manual intervention. [ Where problems could occur ] This is a back-ported change from upstream and is a result of a bug in dh_installsystemd (see comment #26). As such the risk is minimal. The only potential risk of failure I can come up with is a snap that stages the old version of the client library, as it would be looking in the wrong place for the socket. [ Other Info ] This bug was originally reported against Ubuntu Mate 22.04, however it applies to all derivatives of Ubuntu Desktop 22.04 LTS. Note - while there's some disagreement as to whether this bug occurs 100% of the time across all 22.04 installations, it's pretty clear from the upstream Debian bug and subsequent packaging fix that we should land this. As the upstream fix landed in 1.9.9-2 (which is already released in mantic) only the following releases are impacted by this bug: - jammy - kinetic - lunar 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 2020604] Re: After Mesa upgrades, Chrome won't show graphics
What's up with the lunar task that is still open? Lunar didn't have a mesa update yet, so it can't have regressed. I understand if we want to avoid future regressions in lunar too, of course, but the fix ("set VERSION so that it also includes the packaging version") should be bundled together with that future update of lunar, no? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2020604 Title: After Mesa upgrades, Chrome won't show graphics Status in chromium-browser package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in chromium-browser source package in Jammy: Invalid Status in mesa source package in Jammy: Fix Committed Status in chromium-browser source package in Lunar: Invalid Status in mesa source package in Lunar: Confirmed Bug description: [Impact] After patching Mesa with some driver updates, Chromium/Brave started seeing corrupt graphics. This was due to GPU acceleration being enabled in the browser by default now, and the old GPU shader cache is invalid in some ways and the browser is not able to recognize that the driver has changed, since the upstream version string hasn't changed. This is shown for instance with 'glxinfo -B' or under 'chrome:gpu' from the browser. The fix is to make the upstream VERSION to have the full packaging version, this will then be used for the core profile version string as well. [Test case] - run stock jammy, install brave-browser from brave.com, launch brave- browser, check that 'brave://gpu' shows things are accelerated, then exit the browser - enable proposed, install libgl1-mesa-dri et al - launch brave-browser again, verify that gfx are not corrupted and brave://gpu is showing acceration being used with the pulled update, graphics would be severely corrupted [Where things could go wrong] There could be apps that expect the Mesa version string to only contain a.b.c, and break in some ways when that's no longer the case. -- After today's Ubuntu 22.04 Mesa upgrades many of our users reported problems viewing graphics when using Google Chrome (Stable). The Mesa upgrades we installed were: [UPGRADE] libegl-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libegl1-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libgl1-mesa-dri:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libgl1-mesa-glx:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libglapi-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libglx-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 We documented the problem in AskUbuntu before we realized it was probably related to Mesa, so wanted to link to that report here: https://askubuntu.com/questions/1469116/since-23-may-2023-ubuntu-22-04-mesa- updates-chrome-wont-display-website-graphi There are several useful pointers and bypasses listed in that AskUbuntu link (one being to remove affected users' GPUCache directories, which does not destroy their profiles and seems to work in many but not all cases). Not sure if this is an issue with Mesa or Chrome or specific machine graphics or an interaction between them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2020604/+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 2020641] Re: Installing or removing apps through snap-store launches another gdm session
This bug was fixed in the package gdm3 - 42.0-1ubuntu7.22.04.3 --- gdm3 (42.0-1ubuntu7.22.04.3) jammy; urgency=medium * debian/patches/ubuntu/gitlab_clearing_signal.patch: - clear signal handlers after udev settle to avoid unexpected session logouts, thanks Ghadi Rahme (lp: #2020641) -- Sebastien Bacher Thu, 01 Jun 2023 12:37:58 +0200 ** Changed in: gdm3 (Ubuntu Jammy) Status: Fix Committed => Fix Released -- 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/2020641 Title: Installing or removing apps through snap-store launches another gdm session Status in gdm3 package in Ubuntu: Fix Released Status in gdm3 source package in Jammy: Fix Released Status in gdm3 source package in Kinetic: Won't Fix Status in gdm3 source package in Lunar: Fix Released Status in gdm3 source package in Mantic: Fix Released Bug description: gdm3 version: 42.0-1ubuntu7.22.04.2 Ubuntu version: Ubuntu 22.04.2 LTS [Description] Installing or removing snap packages through NICE DCV on AWS will cause the user to be kicked out of their session. The issue happens on machines running nvidia GPUs (passed through to a VM) with the GRID driver installed as well as the normal nvidia driver. [Steps to reproduce] Simply install or remove any snap through the snap store will trigger the issue, for example: $ snap install skype also running any of the following commands will also trigger the issue: $ snap connect skype:opengl :opengl $ snap disconnect skype:opengl :opengl $ snap connect skype:camera :camera $ snap disconnect skype:camera :camera After further investigation I was able to pin down the issue to udev and could reproduce the issue by running the following command: $ sudo udevadm trigger --parent-match=/sys/devices/pci:00/:00:1e.0/drm/card0 where "/sys/devices/pci:00/:00:1e.0/drm/card0" corresponds to the nvidia GPU of my instance. A more generic way of triggering the issue would be running: $ sudo udevadm trigger [Solution] I have investigated the issue and discovered that it lies within GDM3 in the "udev_is_settled" function (daemon/gdm-local-display-factory.c). In the case where the udev is settled the line "g_clear_signal_handler (>uevent_handler_id, factory->gudev_client);" at the end of the function is triggered however this is not the case when the function returns early and will lead to the user being logged out. In its current implementation there are three different return points before "g_clear_signal_handler" is executed where the udev devices would already have settled. I have written a patch that fixes this issue by making sure the function "g_clear_signal_handler" is executed in all cases for which the udev is settled. [possible regressions] Excessive clearing of the signal handler might cause a case where it is not being re-initialized the next time it is needed. [Base test plan] This test plan is to make sure the issue listed in the description section is fixed. 1. Create a new nvidia accelerated VM instance on AWS with NICE DCV and the GRID driver (or normal driver) installed. Make sure the GPU is being fully passed through to the instance (do not slice the GPU). 2. Access the instance using the NICE DCV client and login. 3. Install any snap package (E.g $ snap install skype). 4. Verify there are no new sessions being launched with the user being gdm. $ sudo loginctl Also make sure that you don't get logged out of your own session. 5. Repeat step 4 while running the following command as well: $ sudo udevadm trigger 6. If the current session stays active and no new sessions spawn while performing step 3 or 5, the test succeeded. [Extra tests] This test plan is a sanity check to make sure no regressions have been created. 1. Login to the session 2. Run a few applications (E.g: Nautilus, gedit, terminal, firefox, skype, libreoffice, mpv, vlc...) and use some on the built in features (E.g: the launcher, search...) 3. Switch sessions without terminating the current one. 4. Login as a separate user and repeat step 2 5. Go back to the first session and make sure everything behaves as expected 6. Switch to init 3: $ init 3 and go back to init 5 afterwards: $ init 5 7. If no issues were found, the test succeeded. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2020641/+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 2020641] Re: Installing or removing apps through snap-store launches another gdm session
This bug was fixed in the package gdm3 - 44.0-1ubuntu2 --- gdm3 (44.0-1ubuntu2) lunar; urgency=medium * Add d/p/ubuntu/flush-signal-handler-on-udev-settle.patch: Clear signal handler after udev settle to avoid sudden logout (LP: #2020641) -- Ghadi Elie Rahme Thu, 01 Jun 2023 12:39:51 +0200 ** Changed in: gdm3 (Ubuntu Lunar) Status: Fix Committed => Fix Released -- 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/2020641 Title: Installing or removing apps through snap-store launches another gdm session Status in gdm3 package in Ubuntu: Fix Released Status in gdm3 source package in Jammy: Fix Released Status in gdm3 source package in Kinetic: Won't Fix Status in gdm3 source package in Lunar: Fix Released Status in gdm3 source package in Mantic: Fix Released Bug description: gdm3 version: 42.0-1ubuntu7.22.04.2 Ubuntu version: Ubuntu 22.04.2 LTS [Description] Installing or removing snap packages through NICE DCV on AWS will cause the user to be kicked out of their session. The issue happens on machines running nvidia GPUs (passed through to a VM) with the GRID driver installed as well as the normal nvidia driver. [Steps to reproduce] Simply install or remove any snap through the snap store will trigger the issue, for example: $ snap install skype also running any of the following commands will also trigger the issue: $ snap connect skype:opengl :opengl $ snap disconnect skype:opengl :opengl $ snap connect skype:camera :camera $ snap disconnect skype:camera :camera After further investigation I was able to pin down the issue to udev and could reproduce the issue by running the following command: $ sudo udevadm trigger --parent-match=/sys/devices/pci:00/:00:1e.0/drm/card0 where "/sys/devices/pci:00/:00:1e.0/drm/card0" corresponds to the nvidia GPU of my instance. A more generic way of triggering the issue would be running: $ sudo udevadm trigger [Solution] I have investigated the issue and discovered that it lies within GDM3 in the "udev_is_settled" function (daemon/gdm-local-display-factory.c). In the case where the udev is settled the line "g_clear_signal_handler (>uevent_handler_id, factory->gudev_client);" at the end of the function is triggered however this is not the case when the function returns early and will lead to the user being logged out. In its current implementation there are three different return points before "g_clear_signal_handler" is executed where the udev devices would already have settled. I have written a patch that fixes this issue by making sure the function "g_clear_signal_handler" is executed in all cases for which the udev is settled. [possible regressions] Excessive clearing of the signal handler might cause a case where it is not being re-initialized the next time it is needed. [Base test plan] This test plan is to make sure the issue listed in the description section is fixed. 1. Create a new nvidia accelerated VM instance on AWS with NICE DCV and the GRID driver (or normal driver) installed. Make sure the GPU is being fully passed through to the instance (do not slice the GPU). 2. Access the instance using the NICE DCV client and login. 3. Install any snap package (E.g $ snap install skype). 4. Verify there are no new sessions being launched with the user being gdm. $ sudo loginctl Also make sure that you don't get logged out of your own session. 5. Repeat step 4 while running the following command as well: $ sudo udevadm trigger 6. If the current session stays active and no new sessions spawn while performing step 3 or 5, the test succeeded. [Extra tests] This test plan is a sanity check to make sure no regressions have been created. 1. Login to the session 2. Run a few applications (E.g: Nautilus, gedit, terminal, firefox, skype, libreoffice, mpv, vlc...) and use some on the built in features (E.g: the launcher, search...) 3. Switch sessions without terminating the current one. 4. Login as a separate user and repeat step 2 5. Go back to the first session and make sure everything behaves as expected 6. Switch to init 3: $ init 3 and go back to init 5 afterwards: $ init 5 7. If no issues were found, the test succeeded. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2020641/+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 1970291] Re: [nvidia] Secondary monitor performance is slow on an Nvidia hybrid system in Wayland sessions
I just tested with 535 and I still have this issue :( -- 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/1970291 Title: [nvidia] Secondary monitor performance is slow on an Nvidia hybrid system in Wayland sessions Status in GNOME Shell: New Status in Mutter: Fix Released Status in mutter package in Ubuntu: Triaged Status in nvidia-graphics-drivers-525 package in Ubuntu: Triaged Bug description: In session with Wayland the Nvidia driver settings do not load. And there is a sluggishness when opening apps, show applications menu, maximize, changing workspace, resize, changing monitor windows etc. When in an Xorg session the Nvidia settings load correctly and the performance is satisfactory. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.60.02 Wed Mar 16 11:24:05 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 25 21:18:08 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:2086] NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation TU116M [GeForce GTX 1660 Ti Mobile] [8086:2086] InstallationDate: Installed on 2022-04-24 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) MachineType: Avell High Performance A60 MUV ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=894cb598-7172-481c-a449-3133b8f226e5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/11/2020 dmi.bios.release: 5.13 dmi.bios.vendor: Intel Corp. dmi.bios.version: QCCFL357.0122.2020.0911.1520 dmi.board.name: Avell High Performance dmi.board.vendor: Avell High Performance dmi.chassis.type: 10 dmi.chassis.vendor: Avell High Performance dmi.chassis.version: 1.0 dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnIntelCorp.:bvrQCCFL357.0122.2020.0911.1520:bd09/11/2020:br5.13:efr1.25:svnAvellHighPerformance:pnA60MUV:pvr:rvnAvellHighPerformance:rnAvellHighPerformance:rvr:cvnAvellHighPerformance:ct10:cvr1.0:skuA60MUV: dmi.product.family: A60 MUV dmi.product.name: A60 MUV dmi.product.sku: A60 MUV dmi.sys.vendor: Avell High Performance version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 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/gnome-shell/+bug/1970291/+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 2024045] Re: gnome-mahjongg 3.40.0-1 second game always locks up with high cpu usage
can kill the game with top or kill command from terminal.. as it happens on either the first or second tile selection .. wondering if a memory reset/free issue is involved -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-mahjongg in Ubuntu. https://bugs.launchpad.net/bugs/2024045 Title: gnome-mahjongg 3.40.0-1 second game always locks up with high cpu usage Status in gnome-mahjongg package in Ubuntu: New Bug description: second game played always causes high cpu usage and mahjongg is unresponsive .. can still exit desktop to reboot to stop high cpu usage.. will investigate further as time permits ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-mahjongg 1:3.40.0-1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Thu Jun 15 15:34:00 2023 InstallationDate: Installed on 2023-03-09 (97 days ago) InstallationMedia: Xubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230309) SourcePackage: gnome-mahjongg UpgradeStatus: Upgraded to mantic on 2023-05-09 (36 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-mahjongg/+bug/2024045/+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 2022851] Update Released
The verification of the Stable Release Update for gtk4 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 gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2022851 Title: Nautilus displays invalid directory content after deleting Status in GTK+: Fix Released Status in gtk4 package in Ubuntu: Fix Released Status in gtk4 source package in Lunar: Fix Released Bug description: Impact -- When files are deleted in Nautilus, they can still show up but in the wrong order. This can also happen if the files are rearranged. This bug is marked Critical because it happen with gtk4 4.10.3+ds-0ubuntu1 in lunar-updates but not with 4.10.1+ds-2ubuntu1 which was originally released with Lunar. Test Case - Install the gtk4 update 1. Close the file browser windows if they are open 2. From a terminal, run these commands: mkdir delete-test cd delete-test touch a b c d e f 3. Open the Nautilus file browser window 4. Navigate to the delete-test folder 5. Select the f file and press the Delete key to delete the file. The file should be deleted and you should see only the files a b c d e in the current folder view What Could Go Wrong --- This fix is included in gtk4 4.10.4 update so see the master bug LP: #2023031 Original Bug Report --- When I delete or reorganize files, they can be displayed wrong. After going to another directory and then back, everything displays properly. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: nautilus 1:44.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jun 4 18:25:47 2023 GsettingsChanges: b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'initial-size' b'(725, 456)' InstallationDate: Installed on 2022-07-22 (317 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) 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/gtk/+bug/2022851/+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 2022851] Re: Nautilus displays invalid directory content after deleting
This bug was fixed in the package gtk4 - 4.10.4+ds-0ubuntu1 --- gtk4 (4.10.4+ds-0ubuntu1) lunar; urgency=medium * New upstream release (LP: #2023031) - Fix Nautilus showing wrong content when files are deleted or rearranged (LP: #2022851) * Drop cherry-picked patch for Mutter 44.1: applied in new release * Add patch to revert an unnecessary buildsystem change that affected our installed-tests patch -- Jeremy Bícha Tue, 06 Jun 2023 08:40:17 -0400 ** Changed in: gtk4 (Ubuntu Lunar) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2022851 Title: Nautilus displays invalid directory content after deleting Status in GTK+: Fix Released Status in gtk4 package in Ubuntu: Fix Released Status in gtk4 source package in Lunar: Fix Released Bug description: Impact -- When files are deleted in Nautilus, they can still show up but in the wrong order. This can also happen if the files are rearranged. This bug is marked Critical because it happen with gtk4 4.10.3+ds-0ubuntu1 in lunar-updates but not with 4.10.1+ds-2ubuntu1 which was originally released with Lunar. Test Case - Install the gtk4 update 1. Close the file browser windows if they are open 2. From a terminal, run these commands: mkdir delete-test cd delete-test touch a b c d e f 3. Open the Nautilus file browser window 4. Navigate to the delete-test folder 5. Select the f file and press the Delete key to delete the file. The file should be deleted and you should see only the files a b c d e in the current folder view What Could Go Wrong --- This fix is included in gtk4 4.10.4 update so see the master bug LP: #2023031 Original Bug Report --- When I delete or reorganize files, they can be displayed wrong. After going to another directory and then back, everything displays properly. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: nautilus 1:44.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jun 4 18:25:47 2023 GsettingsChanges: b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'initial-size' b'(725, 456)' InstallationDate: Installed on 2022-07-22 (317 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) 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/gtk/+bug/2022851/+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 2022851] Re: Nautilus displays invalid directory content after deleting
> It does look like that issue was another regression triggered by GTK 4.10.3 > since it seems to work > correctly with GTK 4.10.1 but not with 4.10.3 (4.10.4 doesn't help it either). I confirmed that. Current lunar + updates shows the ctrl-click selection issue already, without updating to gtk 4.10.4 (udpates has 4.10.3). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2022851 Title: Nautilus displays invalid directory content after deleting Status in GTK+: Fix Released Status in gtk4 package in Ubuntu: Fix Released Status in gtk4 source package in Lunar: Fix Released Bug description: Impact -- When files are deleted in Nautilus, they can still show up but in the wrong order. This can also happen if the files are rearranged. This bug is marked Critical because it happen with gtk4 4.10.3+ds-0ubuntu1 in lunar-updates but not with 4.10.1+ds-2ubuntu1 which was originally released with Lunar. Test Case - Install the gtk4 update 1. Close the file browser windows if they are open 2. From a terminal, run these commands: mkdir delete-test cd delete-test touch a b c d e f 3. Open the Nautilus file browser window 4. Navigate to the delete-test folder 5. Select the f file and press the Delete key to delete the file. The file should be deleted and you should see only the files a b c d e in the current folder view What Could Go Wrong --- This fix is included in gtk4 4.10.4 update so see the master bug LP: #2023031 Original Bug Report --- When I delete or reorganize files, they can be displayed wrong. After going to another directory and then back, everything displays properly. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: nautilus 1:44.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jun 4 18:25:47 2023 GsettingsChanges: b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'initial-size' b'(725, 456)' InstallationDate: Installed on 2022-07-22 (317 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) 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/gtk/+bug/2022851/+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 2023031] Update Released
The verification of the Stable Release Update for gtk4 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 gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2023031 Title: Update gtk4 to 4.10.4 Status in gtk4 package in Ubuntu: Fix Released Status in gtk4 source package in Lunar: Fix Released Bug description: Impact - There is a new point release in the stable GTK 4.10 series. https://gitlab.gnome.org/GNOME/gtk/-/blob/4.10.4/NEWS The version currently in Ubuntu 23.04 is 4.10.3 Test Case 0 --- gtk4 has an extensive build test suite, and failures will fail the build. gtk4 also has thorough autopkgtests. Ensure that the build succeeds and that the autopgktests pass. Test Case 1 --- Make sure that opening and saving files from the Firefox and Chromium snaps still work Test Case 2 --- snap install portal-test snap run portal-test Verify that the app seems to still work ok What Could Go Wrong --- Ubuntu includes xdg-desktop-portal-gnome by default which is used for many snap actions like providing a file chooser. This is critical functionality for our snaps. The Ubuntu flavors use a different portal backend, most commonly xdg- desktop-portal-gtk which uses GTK3 so it's not affected by this SRU. Many of the default Ubuntu 23.04 desktop apps use GTK4. A serious enough regression could severely break the Ubuntu Desktop. gtk4 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/gtk4/+bug/2023031/+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 2023031] Re: Update gtk4 to 4.10.4
This bug was fixed in the package gtk4 - 4.10.4+ds-0ubuntu1 --- gtk4 (4.10.4+ds-0ubuntu1) lunar; urgency=medium * New upstream release (LP: #2023031) - Fix Nautilus showing wrong content when files are deleted or rearranged (LP: #2022851) * Drop cherry-picked patch for Mutter 44.1: applied in new release * Add patch to revert an unnecessary buildsystem change that affected our installed-tests patch -- Jeremy Bícha Tue, 06 Jun 2023 08:40:17 -0400 ** Changed in: gtk4 (Ubuntu Lunar) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2023031 Title: Update gtk4 to 4.10.4 Status in gtk4 package in Ubuntu: Fix Released Status in gtk4 source package in Lunar: Fix Released Bug description: Impact - There is a new point release in the stable GTK 4.10 series. https://gitlab.gnome.org/GNOME/gtk/-/blob/4.10.4/NEWS The version currently in Ubuntu 23.04 is 4.10.3 Test Case 0 --- gtk4 has an extensive build test suite, and failures will fail the build. gtk4 also has thorough autopkgtests. Ensure that the build succeeds and that the autopgktests pass. Test Case 1 --- Make sure that opening and saving files from the Firefox and Chromium snaps still work Test Case 2 --- snap install portal-test snap run portal-test Verify that the app seems to still work ok What Could Go Wrong --- Ubuntu includes xdg-desktop-portal-gnome by default which is used for many snap actions like providing a file chooser. This is critical functionality for our snaps. The Ubuntu flavors use a different portal backend, most commonly xdg- desktop-portal-gtk which uses GTK3 so it's not affected by this SRU. Many of the default Ubuntu 23.04 desktop apps use GTK4. A serious enough regression could severely break the Ubuntu Desktop. gtk4 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/gtk4/+bug/2023031/+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 2024045] [NEW] gnome-mahjongg 3.40.0-1 second game always locks up with high cpu usage
Public bug reported: second game played always causes high cpu usage and mahjongg is unresponsive .. can still exit desktop to reboot to stop high cpu usage.. will investigate further as time permits ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-mahjongg 1:3.40.0-1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Thu Jun 15 15:34:00 2023 InstallationDate: Installed on 2023-03-09 (97 days ago) InstallationMedia: Xubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230309) SourcePackage: gnome-mahjongg UpgradeStatus: Upgraded to mantic on 2023-05-09 (36 days ago) ** Affects: gnome-mahjongg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-mahjongg in Ubuntu. https://bugs.launchpad.net/bugs/2024045 Title: gnome-mahjongg 3.40.0-1 second game always locks up with high cpu usage Status in gnome-mahjongg package in Ubuntu: New Bug description: second game played always causes high cpu usage and mahjongg is unresponsive .. can still exit desktop to reboot to stop high cpu usage.. will investigate further as time permits ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-mahjongg 1:3.40.0-1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Thu Jun 15 15:34:00 2023 InstallationDate: Installed on 2023-03-09 (97 days ago) InstallationMedia: Xubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230309) SourcePackage: gnome-mahjongg UpgradeStatus: Upgraded to mantic on 2023-05-09 (36 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-mahjongg/+bug/2024045/+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 1779890] Re: gvfsd process does not have the KRB5CCNAME environment set
Hi Lucas, Thank you for taking a look at this! I was originally sponsoring this one for Matthew, but given it's now targeting a development release, I can't sponsor that one (as I'm currently an SRU developer). If a coredev could do the sponsoring for devel, I'd be happy to work with Matthew on the other series if necessary. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1779890 Title: gvfsd process does not have the KRB5CCNAME environment set Status in gvfs package in Ubuntu: New Status in tracker-miners package in Ubuntu: Fix Released Status in gvfs source package in Bionic: Invalid Status in tracker-miners source package in Bionic: Won't Fix Status in gvfs source package in Focal: Invalid Status in tracker-miners source package in Focal: In Progress Status in gvfs source package in Jammy: Invalid Status in tracker-miners source package in Jammy: In Progress Status in gvfs source package in Kinetic: Invalid Status in tracker-miners source package in Kinetic: In Progress Status in gvfs source package in Lunar: Invalid Status in tracker-miners source package in Lunar: Fix Released Bug description: [ Impact ] The KRB5CCNAME environment variable points to the Kerberos ticket of the current machine and this ticket is used for authentication in Active Directory servers. This variable is set by pam_sss when the user authenticates and can be used by other processes, such as gio, to skip the credentials input when accessing network shares, for example. Some services rely on gvfs-daemon in order to properly function, such as tracker-extract-3.service and tracker-miner-fs-3.service, which means they will ask for the gvfs-daemon to be initialized when they are executed by systemd. This creates problems if one service that relies on gvfsd is started too early, as it would result in gvfsd being started too early as well. As of version 3.1 of tracker-miners, the install target of tracker- miners-fs-3.service was set to gnome-session.target: https://gitlab.gnome.org/GNOME/tracker-miners/-/merge_requests/283 However, the tracker-extract-3.service was not updated and its target is still default.target, which is too early for the service to start. Starting tracker-extract too early is also starting gvfsd too early, before the session environment gets fully updated. Which means that gvfsd does not have the KRB5CCNAME variable and can not do any operations with it. Tracker-extract is supposed to be a helper service managed by tracker- miner-fs-3.service. By using a [Install] section, we are actually telling systemd that it should manage this service as well, when it shouldn't. So, by removing the [Install] section and having tracker-miner- fs-3.service being tied to gnome-session.target, we fix the issue of gvfsd starting too early without the updated session environment. [ Test Plan ] In order to test this issue, it's required to have an Active Directory server running. 1) Authenticate with an AD user (as this would set the KRB5CCNAME env); 2) Check gvfsd environment. This can be done by running: cat /proc/$(pidof gvfsd)/environ | xargs --null -n1 You will be able to see that it does not have the variable listed. 3) Check that the information mentioned above about tracker-miner-fs- 3.service is true. 4) Disable tracker-extract-3.service (This is a bit tricky, since its target was default.target. The easiest way is to remove the symlink that systemd created when enabling the unit, located under /etc/systemd/user/default.target.wants/tracker-extract-3.service 5) Reboot the machine; 6) Repeat steps 1 and 2. This will show that gvfsd is now started with the proper environment. Is not enough to look at ptree and the pids of the processes, instead it's better to look into the session logs with: journalctl --user -b And check the order in which the services were started and when they were triggered. Test packages are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf320070-test After installing test packages of tracker-miners, KRB5CCNAME should be set in gvfs environment upon login to gnome. [ Where problems could occur ] The tracker project is a search engine that speeds up search operations in Gnome. The tracker-miners is the indexing daemon that populates the database with information, so changing its start does not affect the system behavior. This changes fix the startup of gvfs-daemon.service, which could delay services that relied on it running to be executed. [ Other info ] This was fixed upstream by the following commit: commit 29a2320c1e4f0f7ced3c3e9d4d1c06c51518c1f3 From: Denison Barbosa Date: Tue, 21 Mar 2023 15:04:28 + Subject: Removing [Install] section from
[Desktop-packages] [Bug 2022929] Re: Bugs in resolution handling, especially garbage printed when invalid resolution value supplied
This bug was fixed in the package libppd - 2:2.0~rc1-0ubuntu1.1 --- libppd (2:2.0~rc1-0ubuntu1.1) lunar; urgency=medium * fix-mirrored-printout-when-ppd-has-mirrorprint-option.patch: When converting PPDs with “MirrorPrint” option into IPP attributes, setting of the option (“True”/“False”) was not considered, making printouts always come out mirrored (LP: #2018538). * fix-resolution-handling-on-ppd-to-ipp-attr-conversion.patch: For PPDs for driverless printers which take jobs in Apple/PWG Raster format always the lowest supported resolution got selected, regardless of the PPD default or job option settings (LP: #2022929). * ppdfilterpstops-fix-printers-with-reverse-output-order.patch: Printouts to PostScript printers (or printers with drivers which need PostScript input) which drop the pages face-up and therefore need to print in reverse order came out empty (Upstream issue #20, LP: #2022943). -- Till Kamppeter Tue, 6 Jun 2023 08:59:59 +0200 ** Changed in: libppd (Ubuntu Lunar) Status: Fix Committed => Fix Released ** Changed in: libcupsfilters (Ubuntu Lunar) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libcupsfilters in Ubuntu. https://bugs.launchpad.net/bugs/2022929 Title: Bugs in resolution handling, especially garbage printed when invalid resolution value supplied Status in libcupsfilters package in Ubuntu: Fix Released Status in libppd package in Ubuntu: Fix Released Status in libcupsfilters source package in Lunar: Fix Released Status in libppd source package in Lunar: Fix Released Status in libcupsfilters source package in Mantic: Fix Released Status in libppd source package in Mantic: Fix Released Bug description: This bug was originally reported upstream as https://github.com/OpenPrinting/libcupsfilters/issues/29 The reporter uses Fedora 38, besides Ubuntu 23.04 the second distro using cups-filters 2.x and libcupsfilters 2.x. As I am able to reproduce the bug on Ubuntu 23.04 and it is a problem many users could run into (it especially happens with driverless IPP printers) I post this bug report as base for an SRU in 23.04. What happens is that if a job is printed and along with it a resolution setting is supplied which is not supported by the printer, garbage is printed as the job gets actually rasterized with the wrong resolution. This was discovered by the Chromium Browser sending print jobs with `-o resolution=96dpi` regardless which resolutions the printer actually supports. Most driverless printers receive their jobs rasterrized into Apple Raster or PWG Raster and so for them this bug occurs. I have already fixed the bug upstream in libcupsfilters via https://github.com/OpenPrinting/libcupsfilters/commit/2892e9a63 The fix makes the function cfIPPAttrResolutionForPrinter() used more intensely, in which another bug showed, the list of supported resolutions searched for as a range data type which was wrong and so the list not being found. So I fixed this here, also in libcupsfilters: https://github.com/OpenPrinting/libcupsfilters/commit/9ff1341c2 Now unsupported resolutions supplied to jobs are ignored so that the default resolution gets used then. The bug masked another bug in resolution handling which got revealed once the above-mentioned fix was applied.Here the problem is that for driverless IPP printers, printing in Apple Raster or PWG Raster always the minimum resolution got used, even if I higher one was requested, as the default resolution or by a job attribute/option which sets a higher resolution. This I fixed in libppd via: https://github.com/OpenPrinting/libppd/commit/e2190988ff6c1 Now always the correct resolution gets used for the rasterization of the job and so the correct print quality obtained. The fixes get applied to the libcupsfilters and libppd source packages both in Mantic and in Lunar (SRU). [ Impact ] The bug impacts at least all users of driverless IPP printers which take print jobs in raster formats, and these are most common printers nowadays. Probably also other printers are affected. The principal bug, jobs with unsupported resolution settings being accepted leads to unusable printouts wasting paper and toner/ink. The secondary problem of always the lowest supported resolution being used leads to a lower print quality than expected. The fact that the Chromium Browser from version 112 on (we use the Snap and current version there is 113) sens "-o resolution=96dpi" along with jobs will trigger this bug for many people. [ Test Plan ] Download the attached sample PPD file, a file to use the HP OfficeJet Pro 8730 in driverless mode, sending the job data in Apple Raster. Also have a PDF file handy. No printer is required for the tests,
[Desktop-packages] [Bug 2014954] Re: Backport Intel Mutual Authentications - FCC Lock
I added tasks for Jammy, Lunar and Mantic (devel). I also took a look at the debdiff and you could also close this bug in the changelog via "LP: #2014954". Moreover, you could improve the patch DEP-3 headers and add the Bug-Ubuntu field with a link to this bug. ** Also affects: libmbim (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: libmbim (Ubuntu Lunar) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/2014954 Title: Backport Intel Mutual Authentications - FCC Lock Status in OEM Priority Project: Confirmed Status in libmbim package in Ubuntu: In Progress Status in libmbim source package in Jammy: New Status in libmbim source package in Lunar: New Bug description: [ Impact ] There exist no formal API to do the FCC unlock procedure[1] in the latest version of the modemmanger. But there is a merged commit[2] that provide this functionality for intel WWAN cards in the upstream project. Lenovo have several laptops using the Intel WWAN cards, and Lenovo are struggling to give a decent way to run the FCC unlock service without this. [ Test Plan ] OEM enablement engineers and Lenovo engineers will help to test if the FCC unlock would work on certain laptops with the help of a custom package[1] provided by Lenovo which contains the FCC unlock script. [ Where problems could occur ] This is a completely new feature to support Intel WWAN cards mutal authentication, which does not affect other existing features. But the feature itself might have bugs and glitches since it is a brand new one and is not widely tested by the laptop vendors, still it is better than nothing. [ Other Info ] [1] FCC unlock procedure: https://modemmanager.org/docs/modemmanager/fcc-unlock/ [2] intel-mutual-authentication: new service, fcc-lock: https://gitlab.freedesktop.org/mobile-broadband/libmbim/-/merge_requests/157 - when the device is first shipped or comes out of the factory, it should be protected with a lock till the device reaches the end user. This FCC lock feature will ensure the device is secured till its unlocked. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2014954/+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 1779890] Re: gvfsd process does not have the KRB5CCNAME environment set
This is in the general sponsorship queue, do you need help to get those uploads sponsored? Or is there someone with upload rights working with you on this? In case you already have someone to sponsor the uploads, please, unsubscribe ~ubuntu-sponsors. After a quick look at the latest debdiff proposed by Matthew, I would suggest to use version 3.3.0-1ubuntu0.1 in Jammy. Right now, we have version 3.3.0-1 in the release pocket, and using version 3.3.0-1ubuntu1 might make some users think that this delta was introduced during the development cycle, and using 3.3.0-1ubuntu0.1 makes more explicit the fact that this was introduced after the release via a SRU. This is just my 2 cents, what was proposed would work out well, it is more a semantic thing that I like to follow when adding a delta via SRU to a package that used to be a sync from Debian. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1779890 Title: gvfsd process does not have the KRB5CCNAME environment set Status in gvfs package in Ubuntu: New Status in tracker-miners package in Ubuntu: Fix Released Status in gvfs source package in Bionic: Invalid Status in tracker-miners source package in Bionic: Won't Fix Status in gvfs source package in Focal: Invalid Status in tracker-miners source package in Focal: In Progress Status in gvfs source package in Jammy: Invalid Status in tracker-miners source package in Jammy: In Progress Status in gvfs source package in Kinetic: Invalid Status in tracker-miners source package in Kinetic: In Progress Status in gvfs source package in Lunar: Invalid Status in tracker-miners source package in Lunar: Fix Released Bug description: [ Impact ] The KRB5CCNAME environment variable points to the Kerberos ticket of the current machine and this ticket is used for authentication in Active Directory servers. This variable is set by pam_sss when the user authenticates and can be used by other processes, such as gio, to skip the credentials input when accessing network shares, for example. Some services rely on gvfs-daemon in order to properly function, such as tracker-extract-3.service and tracker-miner-fs-3.service, which means they will ask for the gvfs-daemon to be initialized when they are executed by systemd. This creates problems if one service that relies on gvfsd is started too early, as it would result in gvfsd being started too early as well. As of version 3.1 of tracker-miners, the install target of tracker- miners-fs-3.service was set to gnome-session.target: https://gitlab.gnome.org/GNOME/tracker-miners/-/merge_requests/283 However, the tracker-extract-3.service was not updated and its target is still default.target, which is too early for the service to start. Starting tracker-extract too early is also starting gvfsd too early, before the session environment gets fully updated. Which means that gvfsd does not have the KRB5CCNAME variable and can not do any operations with it. Tracker-extract is supposed to be a helper service managed by tracker- miner-fs-3.service. By using a [Install] section, we are actually telling systemd that it should manage this service as well, when it shouldn't. So, by removing the [Install] section and having tracker-miner- fs-3.service being tied to gnome-session.target, we fix the issue of gvfsd starting too early without the updated session environment. [ Test Plan ] In order to test this issue, it's required to have an Active Directory server running. 1) Authenticate with an AD user (as this would set the KRB5CCNAME env); 2) Check gvfsd environment. This can be done by running: cat /proc/$(pidof gvfsd)/environ | xargs --null -n1 You will be able to see that it does not have the variable listed. 3) Check that the information mentioned above about tracker-miner-fs- 3.service is true. 4) Disable tracker-extract-3.service (This is a bit tricky, since its target was default.target. The easiest way is to remove the symlink that systemd created when enabling the unit, located under /etc/systemd/user/default.target.wants/tracker-extract-3.service 5) Reboot the machine; 6) Repeat steps 1 and 2. This will show that gvfsd is now started with the proper environment. Is not enough to look at ptree and the pids of the processes, instead it's better to look into the session logs with: journalctl --user -b And check the order in which the services were started and when they were triggered. Test packages are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf320070-test After installing test packages of tracker-miners, KRB5CCNAME should be set in gvfs environment upon login to gnome. [ Where problems could occur ] The tracker project is a search engine that speeds up search
[Desktop-packages] [Bug 2023623] Re: [SRU] Disable pressure for Precision5680 2nd source touchpad
Regarding the impact section: [ Impact ] * It will disable pressure event for i2c touchpad vid 0x06cb pid 0xcfa0 You are describing what the update will do, but not why. Why do we need to "disable pressure event" for this device? What's going on? What happens to users of this hardware without this patch? I also don't see a kinetic upload, can you please clarify that you are skipping kinetic on purpose, and why? ** Also affects: libinput (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: libinput (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: libinput (Ubuntu Jammy) Status: New => Incomplete ** Changed in: libinput (Ubuntu Lunar) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/2023623 Title: [SRU] Disable pressure for Precision5680 2nd source touchpad Status in OEM Priority Project: New Status in libinput package in Ubuntu: Fix Released Status in libinput source package in Jammy: Incomplete Status in libinput source package in Lunar: Incomplete Bug description: [ Impact ] * It will disable pressure event for i2c touchpad vid 0x06cb pid 0xcfa0 [ Test Plan ] * on Dell precision 5680 with touchpad vid:0x06cb pid:0xcfa0 * check left/right button * check 2 fingers scrolling * check 1 finger drag and drop * check 2 fingers drag and drop [ Where problems could occur ] * The quirk match the PID VID only, it won't impact other touchpad [ Other Info ] * https://gitlab.freedesktop.org/libinput/libinput/-/merge_requests/869 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2023623/+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 2024014] [NEW] Deleting files via nautilus windows causes the file list to refresh incorrectly.
Public bug reported: This problem started between kinetic (which worked) and lunar (which does not). If I delete a file the updated file listing in nautilus is incorrect, showing the deleted file and removing a random file/directory that is still technically present. Refreshing via ctrl+r restores the file view to the real state. This bug also happens when moving files to directories. To reproduce this bug: * create files/directories in a directory `touch file{1..9} ; mkdir -p dir{1..9}` * open the directory in nautilus and delete a file (in my case file6) This bug does happen when the file is permanently deleted using nautilus, however it doesn't happen when the file is deleted via a terminal with the nautilus window open in that directory. This bug is also reproduced on any other nautilus windows open and viewing the same directory. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: nautilus 1:44.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jun 15 11:36:28 2023 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'initial-size' b'(1092, 681)' InstallationDate: Installed on 2023-05-28 (18 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: nautilus-extension-gnome-terminal 3.48.0-1ubuntu1 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar ** Attachment added: "Screencast from 2023-06-15 11-31-02.webm" https://bugs.launchpad.net/bugs/2024014/+attachment/5680009/+files/Screencast%20from%202023-06-15%2011-31-02.webm -- 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/2024014 Title: Deleting files via nautilus windows causes the file list to refresh incorrectly. Status in nautilus package in Ubuntu: New Bug description: This problem started between kinetic (which worked) and lunar (which does not). If I delete a file the updated file listing in nautilus is incorrect, showing the deleted file and removing a random file/directory that is still technically present. Refreshing via ctrl+r restores the file view to the real state. This bug also happens when moving files to directories. To reproduce this bug: * create files/directories in a directory `touch file{1..9} ; mkdir -p dir{1..9}` * open the directory in nautilus and delete a file (in my case file6) This bug does happen when the file is permanently deleted using nautilus, however it doesn't happen when the file is deleted via a terminal with the nautilus window open in that directory. This bug is also reproduced on any other nautilus windows open and viewing the same directory. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: nautilus 1:44.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jun 15 11:36:28 2023 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'initial-size' b'(1092, 681)' InstallationDate: Installed on 2023-05-28 (18 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: nautilus-extension-gnome-terminal 3.48.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2024014/+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 2020604] Re: After Mesa upgrades, Chrome won't show graphics
marking verified according to #37, and also my testing shows it working ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2020604 Title: After Mesa upgrades, Chrome won't show graphics Status in chromium-browser package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in chromium-browser source package in Jammy: Invalid Status in mesa source package in Jammy: Fix Committed Status in chromium-browser source package in Lunar: Invalid Status in mesa source package in Lunar: Confirmed Bug description: [Impact] After patching Mesa with some driver updates, Chromium/Brave started seeing corrupt graphics. This was due to GPU acceleration being enabled in the browser by default now, and the old GPU shader cache is invalid in some ways and the browser is not able to recognize that the driver has changed, since the upstream version string hasn't changed. This is shown for instance with 'glxinfo -B' or under 'chrome:gpu' from the browser. The fix is to make the upstream VERSION to have the full packaging version, this will then be used for the core profile version string as well. [Test case] - run stock jammy, install brave-browser from brave.com, launch brave- browser, check that 'brave://gpu' shows things are accelerated, then exit the browser - enable proposed, install libgl1-mesa-dri et al - launch brave-browser again, verify that gfx are not corrupted and brave://gpu is showing acceration being used with the pulled update, graphics would be severely corrupted [Where things could go wrong] There could be apps that expect the Mesa version string to only contain a.b.c, and break in some ways when that's no longer the case. -- After today's Ubuntu 22.04 Mesa upgrades many of our users reported problems viewing graphics when using Google Chrome (Stable). The Mesa upgrades we installed were: [UPGRADE] libegl-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libegl1-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libgl1-mesa-dri:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libgl1-mesa-glx:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libglapi-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libglx-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 We documented the problem in AskUbuntu before we realized it was probably related to Mesa, so wanted to link to that report here: https://askubuntu.com/questions/1469116/since-23-may-2023-ubuntu-22-04-mesa- updates-chrome-wont-display-website-graphi There are several useful pointers and bypasses listed in that AskUbuntu link (one being to remove affected users' GPUCache directories, which does not destroy their profiles and seems to work in many but not all cases). Not sure if this is an issue with Mesa or Chrome or specific machine graphics or an interaction between them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2020604/+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 2024008] Re: Touchpad stops registering single touch movements after some time
** Package changed: ubuntu => xserver-xorg-input-libinput (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/2024008 Title: Touchpad stops registering single touch movements after some time Status in xserver-xorg-input-libinput package in Ubuntu: New Bug description: Hello, touchpad on my Dell XPS 17 (9720) with ubuntu 23 behaves weirdly. It usually works fine for a few hours and then it stops registering single touch movements, so it cannot be used to move cursor as expected. But clicks and multitouch stuff works (scrolling, ...). If one want to move cursor, two fingers must be used, one static, one moving, which is weird. Problem occurs randomly. If notebook is restarted after it occurs, problem is not solved. If notebook is turned off after the problem occurs, issue disappears. BIOS and all firmware is up to date, I use dual boot with windows. I followed touchpad debugging page on askubuntu and managed to get some logs before and after + from evtest. Thanks ! ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xserver-xorg-input-libinput 1.2.1-1 [modified: usr/share/X11/xorg.conf.d/40-libinput.conf] ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jun 15 17:14:01 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu InstallationDate: Installed on 2023-05-21 (24 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) MachineType: Dell Inc. XPS 17 9720 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=58d64f58-ccff-45f5-8a38-c6805fc27d2a ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-libinput UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/22/2023 dmi.bios.release: 1.16 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.16.1 dmi.board.name: 0KNF8J dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.16.1:bd03/22/2023:br1.16:svnDellInc.:pnXPS179720:pvr:rvnDellInc.:rn0KNF8J:rvrA00:cvnDellInc.:ct10:cvr:sku0AFF: dmi.product.family: XPS dmi.product.name: XPS 17 9720 dmi.product.sku: 0AFF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/2024008/+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 1968792] Re: After F10 menu Enter key opens file instead of menu action
I've removed the patch. It did not work. This bug must be reopened. ** Patch removed: "848.patch" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1968792/+attachment/5679802/+files/848.patch ** Tags removed: patch -- 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/1968792 Title: After F10 menu Enter key opens file instead of menu action Status in Nautilus: Unknown Status in nautilus package in Ubuntu: Fix Released Bug description: When pressing F10 on Nautilus, the menu pops. Then the arrow keys navigate the menu, but when pressing Enter, does not execute the selected menu action. IE: if folder is selected, press F10, menu pops down arrow to choose "open in terminal", press enter, Nautilus navigates to the selected folder instead of opening terminal in the current location. Also with files: if text (or any) file is selected, press F10, menu pops, choose any action with arrows, press enter, gedit (or whatever) opens selected file. Tested all actions then selecting files or folders, same result. Expected behavior: After pressing F10, focus should be on the menu that just pops up, until ESC is pressed or mouse clicks somewhere else or focus is shifted by other means, so when pressing ENTER action gets performed. IE: file or folder is selected, press F10, down arrow to select PROPERTIES, press ENTER, PROPERTIES of selected item are shown. Also tried with SPACEBAR (just in case), but the result is the same. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1: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 CasperMD5CheckMismatches: ./preseed/ubuntu.seed ./pool/restricted/n/nvidia-graphics-drivers-470/nvidia-kernel-source-470_470.103.01-0ubuntu2_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/libnvidia-gl-510_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-compute-utils-510_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-driver-495_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-driver-510_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-kernel-common-510_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-kernel-source-510_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-utils-510_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/xserver-xorg-video-nvidia-510_510.60.02-0ubuntu1_amd64.deb CasperMD5CheckResult: fail CasperVersion: 1.468 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 12 23:08:24 2022 ExecutablePath: /usr/bin/nautilus GsettingsChanges: LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince42.1-2 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1968792/+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 2023939] Re: Items in the sidebar are not activated by the keyboard when has selected files
I've removed the patch. It did not work. ** Patch removed: "848.patch" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2023939/+attachment/5679803/+files/848.patch ** Changed in: nautilus (Ubuntu) Status: Fix Released => New ** Tags removed: patch -- 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/2023939 Title: Items in the sidebar are not activated by the keyboard when has selected files Status in nautilus package in Ubuntu: New Bug description: The selected items in the sidebar are not activated by the keyboard when there are selected files. Steps to reproduce the bug: 1) Open a directory that contains files; 2) Select a file; 2) Press F6 to change the focus to the sidebar; 3) Use arrows up or down to select an item in the sidebar; 4) Press Enter to activate the item in the sidebar. Unexpected behavior: - The selected file is opened. Expected behavior: - The selected item in the sidebar should open. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.6-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 14 21:04:52 2023 GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" b'org.gnome.nautilus.window-state' b'initial-size' b'(989, 679)' b'org.gnome.nautilus.window-state' b'sidebar-width' b'255' InstallationDate: Installed on 2023-06-03 (11 days ago) InstallationMedia: Ubuntu 22.04.2 2023.06.03 LTS (20230603) SourcePackage: nautilus 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-06-03T14:17:19 usr_lib_nautilus: evince42.3-0ubuntu3 file-roller 3.42.0-1 nautilus-extension-brasero3.12.3-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2023939/+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
** Summary changed: - SRU gjs 1.72.3 to jammy + SRU gjs 1.72.4 to jammy ** Description changed: [ Impact ] That's the GNOME 42 stable update, including some fixes: - https://gitlab.gnome.org/GNOME/gjs/-/commits/1.72.3 + 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 Gjs applications (such as GNOME Maps, GNOME Characters, GNOME Weather...) and GNOME Shell and its components and extensions should continue working. [ 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). -- 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 Committed 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 Gjs applications (such as GNOME Maps, GNOME Characters, GNOME Weather...) and GNOME Shell and its components and extensions should continue working. [ 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 2023571] Re: Update to gjs 1.76.2 and SRU it
This bug was fixed in the package gjs - 1.76.2-1 gjs (1.76.2-1) experimental; urgency=medium * New upstream release (LP: #2023571) * Drop all patches: applied in new release -- Jeremy Bícha Wed, 14 Jun 2023 18:44:22 -0400 ** Summary changed: - Update to gjs 1.76.1 and SRU it + Update to gjs 1.76.2 and SRU it ** Description changed: [ Impact ] There is a new bugfix release in the stable series associated with GNOME 44 - https://gitlab.gnome.org/GNOME/gjs/-/blob/1.76.1/NEWS + https://gitlab.gnome.org/GNOME/gjs/-/blob/1.76.2/NEWS [ Test case ] Complete the test cases from https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Gjs applications (such as GNOME Maps, GNOME Characters, GNOME Weather...) and GNOME Shell and its components and extensions should continue working. [ Regression potential ] GNOME Shell is the heart of the Ubuntu desktop experience. gjs is a key component of GNOME Shell. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu (it is used by even GDM, the login screen). Smaller bugs could interrupt people's workflows. This update changed fundamentally the memory management of some objects and containers (especially GVariant's), but these changes were already part of gjs released in ubuntu lunar (1.76.0-3). -- 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/2023571 Title: Update to gjs 1.76.2 and SRU it Status in gjs package in Ubuntu: Fix Released Status in gjs source package in Lunar: In Progress Bug description: [ Impact ] There is a new bugfix release in the stable series associated with GNOME 44 https://gitlab.gnome.org/GNOME/gjs/-/blob/1.76.2/NEWS [ Test case ] Complete the test cases from https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Gjs applications (such as GNOME Maps, GNOME Characters, GNOME Weather...) and GNOME Shell and its components and extensions should continue working. [ Regression potential ] GNOME Shell is the heart of the Ubuntu desktop experience. gjs is a key component of GNOME Shell. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu (it is used by even GDM, the login screen). Smaller bugs could interrupt people's workflows. This update changed fundamentally the memory management of some objects and containers (especially GVariant's), but these changes were already part of gjs released in ubuntu lunar (1.76.0-3). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2023571/+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 2023746] Re: [SRU] Add Quectel EM05-G/EM05-CN PID information to support WWAN LVFS
Hello Laider, or anyone else affected, Accepted modemmanager into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/modemmanager/1.20.0-1~ubuntu22.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/2023746 Title: [SRU] Add Quectel EM05-G/EM05-CN PID information to support WWAN LVFS Status in OEM Priority Project: New Status in modemmanager package in Ubuntu: Fix Released Status in modemmanager source package in Jammy: Fix Committed Bug description: [SRU] Add Quectel EM05-G/EM05-CN PID information to support WWAN LVFS [ Impact ] The modemmanager v1.20.0 doesn't have Quectel EM05-G/EM05-CN PID (0x311/0x312) information. Fwupd can't base on modemmanager to identify the modem for supporting WWAN LVFS on a x86-based platform with Intel EHL, which is working with Jammy. (lp: #2019555) [ Test Plan ] Under Jammy environment, check fwupd (snap version) can identify EM05-G/EM05-CN modems to support WWAN LVFS on the target platform $ fwupdmgr refresh --force $ sudo fwupdmgr install # Select EM05-G/EM05-CN [ Where problems could occur ] The EM05-G/EM05-CN PID information is upstreamed to modemmanager v1.20.4 1. https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/b43cae70b078ee1af5b454cfd2b452e8dc711453 2. https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/e30b3a07a8d0f2bf5676cdcaf74da76f4af98b63 The Lunar and Mantic already working with modemmanager v1.20.4. The target platform WWAN LVFS function works well on Lunar and Mantic. The change parts just only add VID/PIDs for Quectel's new modems under the Quectel plugin. [ Other Info ] N/A To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2023746/+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 1954628] Re: [USB-Audio - ALC4080] Front panel: Headphone output not working
This is still affecting me @23.04 Lunar Lobster -- 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/1954628 Title: [USB-Audio - ALC4080] Front panel: Headphone output not working Status in alsa-driver package in Ubuntu: Confirmed Bug description: I have a MSI MAG X570s Torpedo MAX motherboard, which has an onboard 'Starship/Matisse HD Audio Controller' (-> ALC4080 USB based audio chip) controller that has a weird mapping via USB audio (see bug: https://bugzilla.kernel.org/show_bug.cgi?id=206873 for a similar configuration). Sound via line-out works fine without any interventions. Headphone output however does not, while Ubuntu correctly detects the headphones as being plugged in when selected sound is still output via line-out, instead of via the front panel headphone jack-out. After some debugging I figured the headphones are connected to a seperate Alsa device on the same card as the line-out. Running 'pacmd load-module module-alsa-sink device=hw:2,1' gives me a working audio output that plays just via the headphone out. I guess a quirk needs to be written for the configuration. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: gijs 2129 F pulseaudio /dev/snd/pcmC2D1p: gijs 2129 F...m pulseaudio /dev/snd/controlC0: gijs 2129 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Dec 13 09:28:19 2021 InstallationDate: Installed on 2020-12-06 (371 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Audio successful Symptom_Card: USB Audio - USB Audio Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Only some of outputs are working Title: [USB-Audio - USB Audio, playback] Playback problem UpgradeStatus: Upgraded to impish on 2021-09-28 (75 days ago) dmi.bios.date: 07/09/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: A.00 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MAG X570S TORPEDO MAX (MS-7D54) 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:bvnAmericanMegatrendsInternational,LLC.:bvrA.00:bd07/09/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D54:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMAGX570STORPEDOMAX(MS-7D54):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7D54 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/1954628/+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 2023979] [NEW] Ubuntu don't see second monitor after ssd replacing to another laptop.
Public bug reported: Ubuntu don't see second monitor after ssd replacing to another laptop. Also Ubuntu don't see that laptonp working from charger and not from battery. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Відмовлено у доступі: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jun 15 12:08:01 2023 DistUpgraded: 2023-01-10 10:20:22,046 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: rtbth/3.9.8, 5.15.0-73-generic, x86_64: installed rtbth/3.9.8, 5.19.0-42-generic, x86_64: installed rtbth/3.9.8, 5.19.0-43-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GA106M [GeForce RTX 3060 Mobile / Max-Q] [10de:2520] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GA106M [GeForce RTX 3060 Mobile / Max-Q] [1025:151f] Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c5) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Cezanne [1025:151f] InstallationDate: Installed on 2021-04-02 (803 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Acer Nitro AN517-41 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic root=UUID=9b25e014-685a-48c2-a845-93fba62dce47 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2023-01-10 (156 days ago) dmi.bios.date: 07/21/2021 dmi.bios.release: 1.8 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Kamiq_CAS dmi.board.vendor: CZ dmi.board.version: V1.08 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.08 dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd07/21/2021:br1.8:efr1.5:svnAcer:pnNitroAN517-41:pvrV1.08:rvnCZ:rnKamiq_CAS:rvrV1.08:cvnAcer:ct10:cvrV1.08:sku: dmi.product.family: Nitro 5 dmi.product.name: Nitro AN517-41 dmi.product.sku: dmi.product.version: V1.08 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.2 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages ubuntu wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2023979 Title: Ubuntu don't see second monitor after ssd replacing to another laptop. Status in xorg package in Ubuntu: New Bug description: Ubuntu don't see second monitor after ssd replacing to another laptop. Also Ubuntu don't see that laptonp working from charger and not from battery. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Відмовлено у доступі: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jun 15 12:08:01 2023 DistUpgraded: 2023-01-10 10:20:22,046 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: rtbth/3.9.8, 5.15.0-73-generic, x86_64: installed rtbth/3.9.8, 5.19.0-42-generic, x86_64: installed rtbth/3.9.8, 5.19.0-43-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GA106M [GeForce RTX 3060 Mobile / Max-Q] [10de:2520] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GA106M [GeForce RTX 3060 Mobile / Max-Q] [1025:151f] Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c5) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Cezanne [1025:151f] InstallationDate: Installed on 2021-04-02 (803 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" -
[Desktop-packages] [Bug 1959502] Re: U2F not connected in snap package
Is that still an issue? Could you give some details about the ubikey you are using? What key model are you using and could you share the corresponding line from $ lsusb ? It could be that a specific device is missing from https://github.com/snapcore/snapd/blob/master/interfaces/builtin/u2f_devices.go ** Changed in: thunderbird (Ubuntu) Status: In Progress => Incomplete -- 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/1959502 Title: U2F not connected in snap package Status in thunderbird package in Ubuntu: Incomplete Bug description: U2F is not working for me when adding my gmail account to Thunderbird. I noticed that u2f-devices is not connected to the thunderbird snap. Running `snap connections thunderbird | grep u2f` returns nothing. Running `snap connect thunderbird:u2f-devices` returns: `error: snap "thunderbird" has no plug named "u2f-devices"` Because the apt version of Thunderbird works fine for me, I think this is just a simple matter of adding the u2f-devices connection to the snap package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1959502/+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 2023086] Re: Gtk-4 update breaks nautilus
*** This bug is a duplicate of bug 2022851 *** https://bugs.launchpad.net/bugs/2022851 ** This bug has been marked a duplicate of bug 2022851 Nautilus displays invalid directory content after deleting -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2023086 Title: Gtk-4 update breaks nautilus Status in gtk4 package in Ubuntu: Confirmed Bug description: It took me 2 hours to find out what the problem is. I reset Gnome desktop because I thought doing the good old dconf reset helps. Folks at Ubuntu - this kind of quality is just very annoying and unacceptable! Now to the bug. This is Ubuntu 23.04. Updates up-to-date. The latest update of libgtk-4 from version 4.10.1 to 4.10.3 breaks nautilus' move-to-trash behavior and copying is broken too. If you move a file to trash with libgtk-4.10.3 installed, the wrong icon is removed from the icon view. Just watch the attached video to see the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2023086/+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 2023647] Re: Screens go into flicker cycle after going blank with external monitor(s)
I'll try to find some time during the weekend to reproduce it with Wayland. I am using this PC for work during the week and Wayland keeps crashing with entire session whenever I am in a videocall. :) -- 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/2023647 Title: Screens go into flicker cycle after going blank with external monitor(s) Status in Mutter: New Status in mutter package in Ubuntu: Incomplete Bug description: This happens whenever screen goes blank after inactivity with external monitors. When there is only one external monitor after few cycles the system recovers from the bug. When there are more than one monitors the system almost never recovers until unplugging extra monitor, as shown in video: https://photos.app.goo.gl/td6coEKFQd3DKe9C7 Happens on desktop and login screen. The same result with Wayland and X11. Does not depend on size of the monitor, cable (HDMI or USB-C) or is it connected via USB-C hub or directly. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.1-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jun 13 12:36:44 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-04-13 (60 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 44.1-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-04-21 (52 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2023647/+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 2023939] Re: Items in the sidebar are not activated by the keyboard when has selected files
Thanks for the upstream reference. I am closing it because the bug has been fixed in the latest development version of Ubuntu. If you need a fix for the bug in previous versions of Ubuntu, please perform as much as possible of the SRU Procedure [1] to bring the need to a developer's attention. [1]: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Fix Released -- 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/2023939 Title: Items in the sidebar are not activated by the keyboard when has selected files Status in nautilus package in Ubuntu: Fix Released Bug description: The selected items in the sidebar are not activated by the keyboard when there are selected files. Steps to reproduce the bug: 1) Open a directory that contains files; 2) Select a file; 2) Press F6 to change the focus to the sidebar; 3) Use arrows up or down to select an item in the sidebar; 4) Press Enter to activate the item in the sidebar. Unexpected behavior: - The selected file is opened. Expected behavior: - The selected item in the sidebar should open. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.6-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 14 21:04:52 2023 GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" b'org.gnome.nautilus.window-state' b'initial-size' b'(989, 679)' b'org.gnome.nautilus.window-state' b'sidebar-width' b'255' InstallationDate: Installed on 2023-06-03 (11 days ago) InstallationMedia: Ubuntu 22.04.2 2023.06.03 LTS (20230603) SourcePackage: nautilus 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-06-03T14:17:19 usr_lib_nautilus: evince42.3-0ubuntu3 file-roller 3.42.0-1 nautilus-extension-brasero3.12.3-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2023939/+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 1968792] Re: After F10 menu Enter key opens file instead of menu action
Thanks for the upstream reference. I am closing it because the bug has been fixed in the latest development version of Ubuntu. If you need a fix for the bug in previous versions of Ubuntu, please perform as much as possible of the SRU Procedure [1] to bring the need to a developer's attention. [1]: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure ** Changed in: nautilus (Ubuntu) Status: Triaged => Fix Released ** Also affects: nautilus via https://gitlab.gnome.org/GNOME/nautilus/-/issues/2225 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1968792 Title: After F10 menu Enter key opens file instead of menu action Status in Nautilus: Unknown Status in nautilus package in Ubuntu: Fix Released Bug description: When pressing F10 on Nautilus, the menu pops. Then the arrow keys navigate the menu, but when pressing Enter, does not execute the selected menu action. IE: if folder is selected, press F10, menu pops down arrow to choose "open in terminal", press enter, Nautilus navigates to the selected folder instead of opening terminal in the current location. Also with files: if text (or any) file is selected, press F10, menu pops, choose any action with arrows, press enter, gedit (or whatever) opens selected file. Tested all actions then selecting files or folders, same result. Expected behavior: After pressing F10, focus should be on the menu that just pops up, until ESC is pressed or mouse clicks somewhere else or focus is shifted by other means, so when pressing ENTER action gets performed. IE: file or folder is selected, press F10, down arrow to select PROPERTIES, press ENTER, PROPERTIES of selected item are shown. Also tried with SPACEBAR (just in case), but the result is the same. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1: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 CasperMD5CheckMismatches: ./preseed/ubuntu.seed ./pool/restricted/n/nvidia-graphics-drivers-470/nvidia-kernel-source-470_470.103.01-0ubuntu2_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/libnvidia-gl-510_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-compute-utils-510_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-driver-495_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-driver-510_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-kernel-common-510_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-kernel-source-510_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-utils-510_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/xserver-xorg-video-nvidia-510_510.60.02-0ubuntu1_amd64.deb CasperMD5CheckResult: fail CasperVersion: 1.468 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 12 23:08:24 2022 ExecutablePath: /usr/bin/nautilus GsettingsChanges: LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince42.1-2 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1968792/+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 2023623] Re: [SRU] Disable pressure for Precision5680 2nd source touchpad
The issue is fixed in the mantic libinput version. I've sponsored the fix for the L/J series now ** Changed in: libinput (Ubuntu) Importance: Undecided => High ** Changed in: libinput (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/2023623 Title: [SRU] Disable pressure for Precision5680 2nd source touchpad Status in OEM Priority Project: New Status in libinput package in Ubuntu: Fix Released Bug description: [ Impact ] * It will disable pressure event for i2c touchpad vid 0x06cb pid 0xcfa0 [ Test Plan ] * on Dell precision 5680 with touchpad vid:0x06cb pid:0xcfa0 * check left/right button * check 2 fingers scrolling * check 1 finger drag and drop * check 2 fingers drag and drop [ Where problems could occur ] * The quirk match the PID VID only, it won't impact other touchpad [ Other Info ] * https://gitlab.freedesktop.org/libinput/libinput/-/merge_requests/869 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2023623/+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