[Desktop-packages] [Bug 2007262] Re: Ubuntu's GNOME desktop rendering latency is higher than necessary
** Summary changed: - Ubuntu's GNOME desktop is higher latency than necessary + Ubuntu's GNOME desktop rendering latency is higher than necessary ** Changed in: mutter (Ubuntu Kinetic) Status: Triaged => Won't Fix -- 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/2007262 Title: Ubuntu's GNOME desktop rendering latency is higher than necessary Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: Triaged Status in mutter source package in Kinetic: Won't Fix Status in mutter source package in Lunar: Fix Released Bug description: [ Impact ] Ubuntu's GNOME desktop is higher latency than necessary. It's stuck in triple buffering when it should be dropping to double buffering during light rendering. [ Test Plan ] 1. Add this to /etc/environment: MUTTER_DEBUG=kms 2. Reboot and log into a Wayland session. 3. Open a Terminal and run: journalctl -f /usr/bin/gnome-shell | grep 'Swap buffers' 4. Drag the Terminal window rapidly with the mouse (a high sample rate mouse will also help). Observed bug: "KMS: Swap buffers: 2 frames pending (triple-buffering)" Expected fix: "KMS: Swap buffers: 1 frames pending (double-buffering)" If you don't at first confirm the bug prior to the fix then try dragging the window to the top bar before wiggling it or opening the overview to make the render load higher. The fix will make the log messages return to double buffering much sooner and stay there more reliably. [ Where problems could occur ] Any part of the smoothness of the desktop experience could be impacted since the fix involves changing the frame clock for frame scheduling. [ Other Info ] Upstream fix: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1441/diffs?commit_id=17ea73d0570318926899c4e3e4821a8b7b21edae To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2007262/+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 V3 debdiff for Mantic that fixes this issue ** Patch added: "Debdiff for tracker-miners on Mantic V3" https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1779890/+attachment/5679388/+files/lp1779890_mantic_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: commit 29a2320c1e4f0f7ced3c3e9d4d1c06c51518c1f3 From: Denison Barbosa Date: Tue, 21 Mar 2023 15:04:28 + Subject: Removing [Install] section from tracker-extract-3.service Link:
[Desktop-packages] [Bug 1779890] Re: gvfsd process does not have the KRB5CCNAME environment set
Attached is a V3 debdiff for Lunar that fixes this issue ** Patch added: "Debdiff for tracker-miners on Lunar V3" https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1779890/+attachment/5679387/+files/lp1779890_lunar_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: commit 29a2320c1e4f0f7ced3c3e9d4d1c06c51518c1f3 From: Denison Barbosa Date: Tue, 21 Mar 2023 15:04:28 + Subject: Removing [Install] section from tracker-extract-3.service Link:
[Desktop-packages] [Bug 1779890] Re: gvfsd process does not have the KRB5CCNAME environment set
Attached is a V3 debdiff for Kinetic that fixes this issue ** Patch added: "Debdiff for tracker-miners on Kinetic V3" https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1779890/+attachment/5679386/+files/lp1779890_kinetic_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: commit 29a2320c1e4f0f7ced3c3e9d4d1c06c51518c1f3 From: Denison Barbosa Date: Tue, 21 Mar 2023 15:04:28 + Subject: Removing [Install] section from tracker-extract-3.service Link:
[Desktop-packages] [Bug 1779890] Re: gvfsd process does not have the KRB5CCNAME environment set
Attached is a V3 debdiff for Jammy that fixes this issue ** Patch added: "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: commit 29a2320c1e4f0f7ced3c3e9d4d1c06c51518c1f3 From: Denison Barbosa Date: Tue, 21 Mar 2023 15:04:28 + Subject: Removing [Install] section from tracker-extract-3.service Link:
[Desktop-packages] [Bug 1779890] Re: gvfsd process does not have the KRB5CCNAME environment set
Attached is a V3 debdiff for Focal that fixes this issue ** Patch removed: "debdiff for tracker-miners on jammy" https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1779890/+attachment/5663488/+files/lp1779890_jammy_v2.debdiff ** Patch removed: "debdiff for tracker-miners on kinetic" https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1779890/+attachment/5663489/+files/lp1779890_kinetic_v2.debdiff ** Patch removed: "debdiff for tracker-miners on Focal V2" https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1779890/+attachment/5665098/+files/lp1779890_focal_v2.debdiff ** Patch added: "Debdiff for tracker-miners on Focal V3" https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1779890/+attachment/5679384/+files/lp1779890_focal_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
[Desktop-packages] [Bug 2023610] Re: Update to 114.0.1
https://ubuntu.com/security/notices/USN-6143-2 Package Information: https://launchpad.net/ubuntu/+source/firefox/114.0.1+build1-0ubuntu0.20.04.1 ** Changed in: firefox (Ubuntu) Status: New => Fix Released ** Changed in: firefox (Ubuntu Focal) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2023610 Title: Update to 114.0.1 Status in firefox package in Ubuntu: Fix Released Status in firefox source package in Focal: Fix Released Bug description: https://www.mozilla.org/en-US/firefox/114.0.1/releasenotes/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2023610/+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 2016182] Re: terminal opened started from nautilus does not get focus
[Expired for nautilus (Ubuntu) because there has been no activity for 60
days.]
** Changed in: nautilus (Ubuntu)
Status: Incomplete => Expired
--
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/2016182
Title:
terminal opened started from nautilus does not get focus
Status in nautilus package in Ubuntu:
Expired
Bug description:
Terminals launched from the nautilus context menu ("Open in Terminal") do not
automatically receive focus.If one starts typing, the input goes to nautilus
instead of the terminal and the terminal needs to be selected manually to get
focus.
Steps:
1. right-click in nautilus
2. select "Open in Terminal"
3. A terminal pops up but the prompt is inactive
I gave up on 22.10 because it had the same issue. I thought the issue
would be solved by now but clearly it still exists. Maybe the
behaviour is intended but that feels go against basic UX...
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.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: GNOME
Date: Thu Apr 13 21:34:46 2023
InstallationDate: Installed on 2022-10-29 (166 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
SourcePackage: nautilus
UpgradeStatus: Upgraded to lunar on 2023-04-12 (1 days ago)
usr_lib_nautilus:
eiciel0.10.0-1
file-roller 43.0-1
nautilus-extension-gnome-terminal 3.48.0-1ubuntu1
python3-nautilus 4.0-1build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2016182/+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 1990341] Re: [SRU] Support to install nvidia driver by allowing list
** Changed in: ubuntu-drivers-common (Ubuntu Lunar)
Status: New => Fix Released
** Changed in: ubuntu-drivers-common (Ubuntu Jammy)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1990341
Title:
[SRU] Support to install nvidia driver by allowing list
Status in OEM Priority Project:
Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
Fix Released
Status in ubuntu-drivers-common source package in Jammy:
Fix Committed
Status in ubuntu-drivers-common source package in Lunar:
Fix Released
Bug description:
[ Impact ]
* In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to
OEM/ODM for production.
In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA)
to use a specific nvidia version to development/production.
NVIDIA and OEN/ODM will announce the next generation combination at
the same time usually when the factory ready to ship the product.
We made Ubuntu as a leading distribution supports many cutting edge
devices, it's time to have an official way to make the nvidia
installation consistent in unannounced (yet) nvidia devices to support
OEM/ODM factory shipment for our growing counterparts.
[ Test Plan ]
* Steps to make sure it works:
1. pick a cutting edge nvidia graphic.
2. remove nv-525 from the pool.
3. check the nv support status:
```
$ ubuntu-drivers list
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
```
4. modify custom file
```
$ cat /etc/custom_supported_gpus.json
{
"chips": [
{
"devid": "0x24BA",
"name": "TEST 24BA",
"branch": "580.1234",
"features": [
"runtimepm"
]
},
{
"devid": "0x25BC",
"name": "TEST 25BC",
"branch": "510",
"features": [
"runtimepm"
]
}
]
}
```
5. make sure the hook works
```
$ ubuntu-drivers list
nvidia-driver-510, (kernel modules provided by nvidia-dkms-510)
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
[ Where problems could occur ]
* This feature only impact target system has a custom file
"/etc/custom_supported_gpus.json". And it won't generate automatically
which should not impact normal users
[ Other Info ]
* the patches are picked from
-
https://github.com/tseliot/ubuntu-drivers-common/commit/ec675fba22c68932da9fae95e0f4f2fd10732bf3
-
https://github.com/tseliot/ubuntu-drivers-common/commit/4776c6b9f78411ef3b269a28e9546e4ffd2b7115
-
https://github.com/tseliot/ubuntu-drivers-common/commit/83528313da84b55c04daa62b5edcbf823e5c067b.
* Discussion is in https://github.com/tseliot/ubuntu-drivers-common/pull/71
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1990341/+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 2023610] Re: Update to 114.0.1
upstream bug for regression: https://bugzilla.mozilla.org/show_bug.cgi?id=1837201 ** Bug watch added: Mozilla Bugzilla #1837201 https://bugzilla.mozilla.org/show_bug.cgi?id=1837201 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2023610 Title: Update to 114.0.1 Status in firefox package in Ubuntu: New Status in firefox source package in Focal: New Bug description: https://www.mozilla.org/en-US/firefox/114.0.1/releasenotes/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2023610/+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 1990341] Re: [SRU] Support to install nvidia driver by allowing list
** Also affects: ubuntu-drivers-common (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: ubuntu-drivers-common (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1990341
Title:
[SRU] Support to install nvidia driver by allowing list
Status in OEM Priority Project:
Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
Fix Released
Status in ubuntu-drivers-common source package in Jammy:
New
Status in ubuntu-drivers-common source package in Lunar:
New
Bug description:
[ Impact ]
* In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to
OEM/ODM for production.
In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA)
to use a specific nvidia version to development/production.
NVIDIA and OEN/ODM will announce the next generation combination at
the same time usually when the factory ready to ship the product.
We made Ubuntu as a leading distribution supports many cutting edge
devices, it's time to have an official way to make the nvidia
installation consistent in unannounced (yet) nvidia devices to support
OEM/ODM factory shipment for our growing counterparts.
[ Test Plan ]
* Steps to make sure it works:
1. pick a cutting edge nvidia graphic.
2. remove nv-525 from the pool.
3. check the nv support status:
```
$ ubuntu-drivers list
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
```
4. modify custom file
```
$ cat /etc/custom_supported_gpus.json
{
"chips": [
{
"devid": "0x24BA",
"name": "TEST 24BA",
"branch": "580.1234",
"features": [
"runtimepm"
]
},
{
"devid": "0x25BC",
"name": "TEST 25BC",
"branch": "510",
"features": [
"runtimepm"
]
}
]
}
```
5. make sure the hook works
```
$ ubuntu-drivers list
nvidia-driver-510, (kernel modules provided by nvidia-dkms-510)
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
[ Where problems could occur ]
* This feature only impact target system has a custom file
"/etc/custom_supported_gpus.json". And it won't generate automatically
which should not impact normal users
[ Other Info ]
* the patches are picked from
-
https://github.com/tseliot/ubuntu-drivers-common/commit/ec675fba22c68932da9fae95e0f4f2fd10732bf3
-
https://github.com/tseliot/ubuntu-drivers-common/commit/4776c6b9f78411ef3b269a28e9546e4ffd2b7115
-
https://github.com/tseliot/ubuntu-drivers-common/commit/83528313da84b55c04daa62b5edcbf823e5c067b.
* Discussion is in https://github.com/tseliot/ubuntu-drivers-common/pull/71
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1990341/+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 2023610] [NEW] Update to 114.0.1
Public bug reported: https://www.mozilla.org/en-US/firefox/114.0.1/releasenotes/ ** Affects: firefox (Ubuntu) Importance: Undecided Assignee: Nishit Majithia (0xnishit) Status: New ** Affects: firefox (Ubuntu Focal) Importance: Undecided Assignee: Nishit Majithia (0xnishit) Status: New ** Changed in: firefox (Ubuntu) Assignee: (unassigned) => Nishit Majithia (0xnishit) ** Also affects: firefox (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: firefox (Ubuntu Focal) Assignee: (unassigned) => Nishit Majithia (0xnishit) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2023610 Title: Update to 114.0.1 Status in firefox package in Ubuntu: New Status in firefox source package in Focal: New Bug description: https://www.mozilla.org/en-US/firefox/114.0.1/releasenotes/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2023610/+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
My system is fully updated but I am still seeing the bug described in the opening post. If I move a file to different directory: * the moved files keeps showing in the original directory * trying to move that file to the trash folder pops up an error message stating that the file is unknown * refreshing the view (F5) makes the file vanish from the original directory -- 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 Committed 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 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
This bug was fixed in the package evince - 44.1-1ubuntu1 --- evince (44.1-1ubuntu1) mantic; urgency=medium * Allow evince to spawn browsers distributed as snaps (LP: #1794064) - debian/apparmor-profile: include snap-browsers abstracted profile and allow transitions to them in evince -- Georgia Garcia Mon, 05 Jun 2023 16:35:51 -0300 ** Changed in: evince (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Fix Committed Status in evince package in Ubuntu: Fix Released Status in apparmor source package in Jammy: In Progress Status in evince source package in Jammy: In Progress Status in apparmor source package in Lunar: In Progress Status in evince source package in Lunar: In Progress Status in evince package in Debian: Confirmed Bug description: [Impact] * Users cannot open a hyperlink in a PDF opened with evince when the default browser is a snap. * The fix creates a snap_browsers abstraction on AppArmor which can be used in a transition for when the browser is executed. The snap_browsers abstraction provides the minimal amount of permissions required to execute a browser provided through snaps. This is a workaround since AppArmor currently does not provide mediation/filtering on enhanced environment variables. [Test Plan] * Make sure the default browser is provided through the snap store. * Open a PDF that contains a hyperlink using evince and click on the URL. * The browser should open the requested URL. [Where problems could occur] * If the browser or snap core update to have new requirements for opening a browser, then the current policy could become obsolete and will need to be updated again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+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 2018731] Re: Graphics memory (VRAM) leak in mutter-x11-frames
** Changed in: mutter Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2018731 Title: Graphics memory (VRAM) leak in mutter-x11-frames Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Bug description: I'm seeing degraded performance with NVIDIA Geforce 3008 Mobile and two screens. After launching nvidia-smi, I can clearly see that there's a memory leak in mutter-x11-frames, which uses around 10-12 GB of VRAM. nvidia-drivers-525 Ubuntu 23.04 X11 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-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 525.105.17 Tue Mar 28 18:02:59 UTC 2023 GCC version: gcc version 12.2.0 (Ubuntu 12.2.0-17ubuntu1) ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 8 14:28:13 2023 DistUpgraded: 2023-04-20 10:00:59,509 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu DkmsStatus: nvidia/525.105.17, 6.2.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] [10de:24dc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] [17aa:3a58] InstallationDate: Installed on 2023-02-09 (87 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: LENOVO 82N6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=2a43fd27-b65c-4d7a-bc19-b001521b0771 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-04-20 (18 days ago) dmi.bios.date: 03/07/2023 dmi.bios.release: 1.60 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN60WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76461 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.60 dmi.modalias: dmi:bvnLENOVO:bvrGKCN60WW:bd03/07/2023:br1.60:efr1.60:svnLENOVO:pn82N6:pvrLegion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO 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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2018731/+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.3 to jammy
** Changed in: gjs (Ubuntu Jammy) Status: In Progress => Fix Committed -- 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.3 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.3 [ 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 2012978] Re: Memory leak
** Description changed:
[ Impact ]
High Memory Usage 3.1gb in 2h after reboot
[ Test case ]
Run:
- env G_SLICE=always-malloc valgrind --leak-check=full \
- --suppressions=/usr/share/glib-2.0/valgrind/glib.supp \
- gjs -c "const GLib=imports.gi['GLib'];function leak(){const
l=GLib.Variant['new']('i',1)};leak();imports.system.gc();"
+ env G_SLICE=always-malloc valgrind --leak-check=full \
+ --suppressions=/usr/share/glib-2.0/valgrind/glib.supp \
+ gjs -c "const GLib=imports.gi['GLib'];function leak(){const
l=GLib.Variant['new']('i',1)};leak();imports.system.gc();"
No leak should be detected
+
+ Running more installed tests under valgrind should output no leaks
+ (unless those caused by gobject-introspection):
+
+ sudo apt install gjs-tests
+ env GJS_DEBUG_TOPICS= valgrind --leak-check=full \
+ --suppressions=/usr/share/glib-2.0/valgrind/glib.supp \
+ /usr/libexec/installed-tests/gjs/minijasmine \
+ /usr/libexec/installed-tests/gjs/js/testGIMarshalling.js
+
+ There may be only two leaks caused by
+ gi_marshalling_tests_garray_boxed_struct_full_return and a gbytes one
+ after a ObjectInstance::prop_setter_impl call (these are leaks in the
+ test library that are expected with gobject-introspection 42, but fixed
+ in later versions).
+
+ env GJS_DEBUG_TOPICS= valgrind --leak-check=full \
+ --suppressions=/usr/share/glib-2.0/valgrind/glib.supp \
+ /usr/libexec/installed-tests/gjs/minijasmine \
+ /usr/libexec/installed-tests/gjs/js/testRegress.js
+
+ No leak expected
[ Regression potential ]
Gjs applications (including gnome Shell) using GVariant may misbehave
+ ---
ProblemType: BugDistroRelease: Ubuntu 22.04
Package: gnome-shell 42.5-0ubuntu1
Uname: Linux 6.2.8-060208-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 27 22:46:07 2023
DisplayManager: gdm3
InstallationDate: Installed on 2022-03-25 (366 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
RelatedPackageVersions: mutter-common 42.5-0ubuntu1SourcePackage: gnome-shell
UpgradeStatus: Upgraded to jammy on 2022-09-03 (205 days ago)
** Changed in: gjs (Ubuntu Kinetic)
Status: Triaged => Won't Fix
--
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/2012978
Title:
Memory leak
Status in gjs package in Ubuntu:
Fix Released
Status in gjs source package in Jammy:
Triaged
Status in gjs source package in Kinetic:
Won't Fix
Bug description:
[ Impact ]
High Memory Usage 3.1gb in 2h after reboot
[ Test case ]
Run:
env G_SLICE=always-malloc valgrind --leak-check=full \
--suppressions=/usr/share/glib-2.0/valgrind/glib.supp \
gjs -c "const GLib=imports.gi['GLib'];function leak(){const
l=GLib.Variant['new']('i',1)};leak();imports.system.gc();"
No leak should be detected
Running more installed tests under valgrind should output no leaks
(unless those caused by gobject-introspection):
sudo apt install gjs-tests
env GJS_DEBUG_TOPICS= valgrind --leak-check=full \
--suppressions=/usr/share/glib-2.0/valgrind/glib.supp \
/usr/libexec/installed-tests/gjs/minijasmine \
/usr/libexec/installed-tests/gjs/js/testGIMarshalling.js
There may be only two leaks caused by
gi_marshalling_tests_garray_boxed_struct_full_return and a gbytes one
after a ObjectInstance::prop_setter_impl call (these are leaks in the
test library that are expected with gobject-introspection 42, but
fixed in later versions).
env GJS_DEBUG_TOPICS= valgrind --leak-check=full \
--suppressions=/usr/share/glib-2.0/valgrind/glib.supp \
/usr/libexec/installed-tests/gjs/minijasmine \
/usr/libexec/installed-tests/gjs/js/testRegress.js
No leak expected
[ Regression potential ]
Gjs applications (including gnome Shell) using GVariant may misbehave
---
ProblemType: BugDistroRelease: Ubuntu 22.04
Package: gnome-shell 42.5-0ubuntu1
Uname: Linux 6.2.8-060208-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 27 22:46:07 2023
DisplayManager: gdm3
InstallationDate: Installed on 2022-03-25 (366 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
RelatedPackageVersions: mutter-common 42.5-0ubuntu1SourcePackage: gnome-shell
UpgradeStatus: Upgraded to jammy on 2022-09-03 (205 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2012978/+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 1986522] Re: Using a Gio.DesktopAppinfo().launch with context freezes GJS
It seems the problem is quite old, let's move at
https://gitlab.gnome.org/GNOME/gjs/-/issues/553
** Bug watch added: gitlab.gnome.org/GNOME/gjs/-/issues #553
https://gitlab.gnome.org/GNOME/gjs/-/issues/553
--
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/1986522
Title:
Using a Gio.DesktopAppinfo().launch with context freezes GJS
Status in gjs package in Ubuntu:
New
Bug description:
Creating a Gio.DesktopAppInfo for a desktopfile, then launching with
an app_launch context freezes GJS. Launching with context set to null
works. There is no debug information on the console.
Using Gtk4
Here is the relevant code-
let desktopFile = Gio.DesktopAppInfo.new('gnome-background-panel.desktop');
const context = Gdk.Display.get_default().get_app_launch_context();
context.set_timestamp(Gdk.CURRENT_TIME);
// Fix me, context in the following causes a crash;
desktopFile.launch([], context)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1986522/+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.1 and SRU it
This bug was fixed in the package gjs - 1.76.1-1 --- gjs (1.76.1-1) experimental; urgency=medium * New upstream release (LP: #2023571) -- Marco Trevisan (Treviño) Mon, 12 Jun 2023 18:53:58 +0200 ** Changed in: gjs (Ubuntu) Status: Fix Committed => Fix Released -- 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.1 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.1/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 2016906] Re: Inactive zombie ghost icons left behind on desktop when copying files
** Package changed: gjs (Ubuntu) => gnome-shell-extension-desktop-icons- ng (Ubuntu) -- 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/2016906 Title: Inactive zombie ghost icons left behind on desktop when copying files Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: New Bug description: When copying files between directory windows, occasionally zombie ghost icons are left on the desktop. These are like holes in the screen with an icon that appears on top of everything in its covered location, is not selectable and is not moveable. Ubuntu 22.10 Release: 22.10 gjs: Installed: 1.74.0-1 Candidate: 1.74.0-1 Version table: *** 1.74.0-1 500 500 http://us.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gjs 1.74.0-1 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3.2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 18 11:24:52 2023 ExecutablePath: /usr/bin/gjs-console InstallationDate: Installed on 2023-02-21 (56 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gjs 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-desktop-icons-ng/+bug/2016906/+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 1987445] Re: After upgrade to 22.04 from 20.x execution of the shell fails to start the application
** Changed in: gjs (Ubuntu) Status: New => Incomplete -- 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/1987445 Title: After upgrade to 22.04 from 20.x execution of the shell fails to start the application Status in gjs package in Ubuntu: Incomplete Bug description: file: cd maple2020/bin ./xmaple the file has permission to run as a program. Double-click results in nothing. I expected maple to start up. Right click plus "Run as a Program" works. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gjs 1.72.0-3~ubuntu22.04.2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Aug 23 23:10:01 2022 ExecutablePath: /usr/bin/gjs-console InstallationDate: Installed on 2021-01-10 (590 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: LANG=en_US.UTF-8 LANGUAGE=en_US:en PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gjs UpgradeStatus: Upgraded to jammy on 2022-08-17 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1987445/+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 2007739] Re: gjs-console crashed with SIGABRT
*** This bug is a duplicate of bug 2012287 ***
https://bugs.launchpad.net/bugs/2012287
** This bug has been marked a duplicate of bug 2012287
gjs-console crashed with signal 6 in g_assertion_message("assertion failed:
(!priv->is_realized)") from g_assertion_message_expr() from
gsk_renderer_dispose() from gsk_renderer_dispose() from g_object_unref()
--
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/2007739
Title:
gjs-console crashed with SIGABRT
Status in gjs package in Ubuntu:
Confirmed
Bug description:
This is happening after wake from suspend.
ProblemType: Crash
DistroRelease: Ubuntu 23.04
Package: gjs 1.74.1-1
ProcVersionSignature: Ubuntu 5.19.0-1012.13-lowlatency 5.19.7
Uname: Linux 5.19.0-1012-lowlatency x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.24.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 17 18:41:41 2023
ExecutablePath: /usr/bin/gjs-console
InstallationDate: Installed on 2021-08-19 (547 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210818)
ProcCmdline: /usr/bin/gjs-console /usr/bin/gnome-characters
--gapplication-service
ProcEnviron:
SHELL=/bin/bash
XDG_RUNTIME_DIR=
PATH=(custom, user)
LANG=en_US.UTF-8
Signal: 6
SourcePackage: gjs
StacktraceTop:
() at /lib/x86_64-linux-gnu/libglib-2.0.so.0
g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
() at /lib/x86_64-linux-gnu/libgtk-4.so.1
g_object_unref () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
() at /lib/x86_64-linux-gnu/libgjs.so.0
Title: gjs-console crashed with SIGABRT
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2007739/+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 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
** Changed in: evince (Ubuntu Jammy) Status: Confirmed => In Progress ** Changed in: apparmor (Ubuntu Jammy) Status: Confirmed => In Progress ** Changed in: apparmor (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: apparmor (Ubuntu Lunar) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Fix Committed Status in evince package in Ubuntu: Fix Committed Status in apparmor source package in Jammy: In Progress Status in evince source package in Jammy: In Progress Status in apparmor source package in Lunar: In Progress Status in evince source package in Lunar: In Progress Status in evince package in Debian: Confirmed Bug description: [Impact] * Users cannot open a hyperlink in a PDF opened with evince when the default browser is a snap. * The fix creates a snap_browsers abstraction on AppArmor which can be used in a transition for when the browser is executed. The snap_browsers abstraction provides the minimal amount of permissions required to execute a browser provided through snaps. This is a workaround since AppArmor currently does not provide mediation/filtering on enhanced environment variables. [Test Plan] * Make sure the default browser is provided through the snap store. * Open a PDF that contains a hyperlink using evince and click on the URL. * The browser should open the requested URL. [Where problems could occur] * If the browser or snap core update to have new requirements for opening a browser, then the current policy could become obsolete and will need to be updated again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+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 2023436] Re: Icons are showing as no entry signs
thanks for the update, closing since it seems like a local issue rather than a gtk bug ** Changed in: gtk+3.0 (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/2023436 Title: Icons are showing as no entry signs Status in gtk+3.0 package in Ubuntu: Invalid Bug description: I have tried looking in various places to see why icons aren't showing properly. Checked loads of log messages. Located the icons on the filesystem but for some reason the icons aren't loading. It is intermittent, for example sometimes the battery symbol shows and sometimes it doesn't. A bigger problem is that sometimes the screen goes black but the laptop is still on, the keyboard is still responding but it's impossible to use. Sometimes this happens a few times in an hour. Sometimes it can be days between using it. This is making my laptop pretty unusable. If there is anything I can do to investigate this further then please shout, happy to run all the commands and provide all the logs. I've attached a screenshot showing the issue in the settings panel but that isn't the only place this is happening. 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] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jun 10 10:17:48 2023 DistUpgraded: 2022-10-02 12:38:39,285 DEBUG icon theme changed, re-reading DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell CometLake-H GT2 [UHD Graphics] [1028:097d] Subsystem: Dell TU117M [GeForce GTX 1650 Ti Mobile] [1028:097d] InstallationDate: Installed on 2020-07-31 (1043 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. XPS 15 9500 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic root=UUID=7a62b7f7-b519-470b-bcb8-48e870873cc4 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-10-02 (250 days ago) dmi.bios.date: 03/16/2023 dmi.bios.release: 1.22 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.22.0 dmi.board.name: 05XYW7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.22.0:bd03/16/2023:br1.22:svnDellInc.:pnXPS159500:pvr:rvnDellInc.:rn05XYW7:rvrA00:cvnDellInc.:ct10:cvr:sku097D: dmi.product.family: XPS dmi.product.name: XPS 15 9500 dmi.product.sku: 097D dmi.sys.vendor: Dell Inc. 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.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2023436/+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 2023588] [NEW] PDF fonts messed up in evince, mupdf, are fine in chrome
Public bug reported: Just downloaded my credit card statement PDF and opened it with evince. Fonts are all messed up. Tried mupdf; also messed up. Opened it in Chrome, everything is fine. See attached screenshots of how a particular paragraph in the PDF looks in Chrome, evince, and mupdf. Also tried loading the PDF gimp, it's rendered wrong there like in evince. Same with xournalpp. Mupdf is close to correct but I think I think Chrome is doing a better job. Made sure all packages were up-to-date and rebooted, didn't help. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: evince 44.1-1 ProcVersionSignature: Ubuntu 6.2.0-21.21-generic 6.2.6 Uname: Linux 6.2.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jun 12 15:04:13 2023 InstallationDate: Installed on 2019-01-02 (1622 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: evince UpgradeStatus: Upgraded to mantic on 2023-05-20 (23 days ago) ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic ** Attachment added: "samples.png" https://bugs.launchpad.net/bugs/2023588/+attachment/5679357/+files/samples.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/2023588 Title: PDF fonts messed up in evince, mupdf, are fine in chrome Status in evince package in Ubuntu: New Bug description: Just downloaded my credit card statement PDF and opened it with evince. Fonts are all messed up. Tried mupdf; also messed up. Opened it in Chrome, everything is fine. See attached screenshots of how a particular paragraph in the PDF looks in Chrome, evince, and mupdf. Also tried loading the PDF gimp, it's rendered wrong there like in evince. Same with xournalpp. Mupdf is close to correct but I think I think Chrome is doing a better job. Made sure all packages were up-to-date and rebooted, didn't help. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: evince 44.1-1 ProcVersionSignature: Ubuntu 6.2.0-21.21-generic 6.2.6 Uname: Linux 6.2.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jun 12 15:04:13 2023 InstallationDate: Installed on 2019-01-02 (1622 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: evince UpgradeStatus: Upgraded to mantic on 2023-05-20 (23 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/2023588/+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 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
** Changed in: evince (Ubuntu Lunar) Status: Confirmed => In Progress ** Changed in: evince (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: evince (Ubuntu) Assignee: James Henstridge (jamesh) => (unassigned) ** Changed in: evince (Ubuntu Lunar) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Confirmed Status in evince package in Ubuntu: Fix Committed Status in apparmor source package in Jammy: Confirmed Status in evince source package in Jammy: Confirmed Status in apparmor source package in Lunar: Confirmed Status in evince source package in Lunar: In Progress Status in evince package in Debian: Confirmed Bug description: [Impact] * Users cannot open a hyperlink in a PDF opened with evince when the default browser is a snap. * The fix creates a snap_browsers abstraction on AppArmor which can be used in a transition for when the browser is executed. The snap_browsers abstraction provides the minimal amount of permissions required to execute a browser provided through snaps. This is a workaround since AppArmor currently does not provide mediation/filtering on enhanced environment variables. [Test Plan] * Make sure the default browser is provided through the snap store. * Open a PDF that contains a hyperlink using evince and click on the URL. * The browser should open the requested URL. [Where problems could occur] * If the browser or snap core update to have new requirements for opening a browser, then the current policy could become obsolete and will need to be updated again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+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 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
** Also affects: evince (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: apparmor (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: evince (Ubuntu Lunar) Status: New => Confirmed ** Changed in: apparmor (Ubuntu Lunar) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Confirmed Status in evince package in Ubuntu: Confirmed Status in apparmor source package in Jammy: Confirmed Status in evince source package in Jammy: Confirmed Status in apparmor source package in Lunar: Confirmed Status in evince source package in Lunar: Confirmed Status in evince package in Debian: Confirmed Bug description: [Impact] * Users cannot open a hyperlink in a PDF opened with evince when the default browser is a snap. * The fix creates a snap_browsers abstraction on AppArmor which can be used in a transition for when the browser is executed. The snap_browsers abstraction provides the minimal amount of permissions required to execute a browser provided through snaps. This is a workaround since AppArmor currently does not provide mediation/filtering on enhanced environment variables. [Test Plan] * Make sure the default browser is provided through the snap store. * Open a PDF that contains a hyperlink using evince and click on the URL. * The browser should open the requested URL. [Where problems could occur] * If the browser or snap core update to have new requirements for opening a browser, then the current policy could become obsolete and will need to be updated again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+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 1250875] Re: Lightdm sometimes fails to auto login
I confirm the same problem Xubuntu 22.04.1. Ligthdm version: 1.30.0-0ubuntu5 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1250875 Title: Lightdm sometimes fails to auto login Status in lightdm package in Ubuntu: Confirmed Bug description: Using ubuntu 14.04 and sometimes when I boot into ubuntu lightdm fails to auto login, and I must login manually in the unity greeter. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.9.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.12.0-2.7-generic 3.12.0 Uname: Linux 3.12.0-2-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.6-0ubuntu1 Architecture: amd64 Date: Wed Nov 13 14:33:18 2013 InstallationDate: Installed on 2013-10-10 (33 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131008) MarkForUpload: True SourcePackage: lightdm UpgradeStatus: Upgraded to trusty on 2013-11-04 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1250875/+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 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
** Changed in: evince (Ubuntu) Status: Incomplete => Confirmed ** Changed in: evince (Ubuntu Jammy) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Confirmed Status in evince package in Ubuntu: Confirmed Status in apparmor source package in Jammy: Confirmed Status in evince source package in Jammy: Confirmed Status in evince package in Debian: Confirmed Bug description: [Impact] * Users cannot open a hyperlink in a PDF opened with evince when the default browser is a snap. * The fix creates a snap_browsers abstraction on AppArmor which can be used in a transition for when the browser is executed. The snap_browsers abstraction provides the minimal amount of permissions required to execute a browser provided through snaps. This is a workaround since AppArmor currently does not provide mediation/filtering on enhanced environment variables. [Test Plan] * Make sure the default browser is provided through the snap store. * Open a PDF that contains a hyperlink using evince and click on the URL. * The browser should open the requested URL. [Where problems could occur] * If the browser or snap core update to have new requirements for opening a browser, then the current policy could become obsolete and will need to be updated again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+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 1975557] Re: blank screen does not turn off display backlight
I confirmed this bug occurs when the gnome-shell-extension-dash-to-dock is on. Turn it off and restart computer, the display shuts off after blank. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1975557 Title: blank screen does not turn off display backlight Status in gnome-shell package in Ubuntu: Expired Bug description: I updated a system from 21.10 to 22.04 and noticed that when the screen is blanked by no keyboard or mouse activity that the backlight in the VGA monitor is still on. The "settings->Displays" has "Unknown Display" which I assume means the system does not know what commands to send to the monitor to shut it off. I booted a live DVD of 21.10 and the settings has the VGA display as 'AOC 22" ' which is correct and the screen blanking works correctly. So it seems that the definition for the AOC displays have been removed from 22.04. This behavior is different on Ubuntu 21.10, the VGA display is blank and the backlight is off. A minor nit is on 21.10 the "settings->Displays" shows the VGA display manufacture name, on 22.04 the VGA display manufacture name is "Unknown Display". I have discovered that the settings have the following options "settings->Power->Screen Blank" with a time value to be selected and the following text on the next line "Turns the screen off after a period of inactivity" "settings->Privacy->Screen->Blank Screen Display" with a time value to be selected and the following text on the next line "Period of inactivity after which the screen will go blank" The two options have different actions but seem to be connected because changing the time on one changes the time on the other. My guess is that the update changed the action for Ubuntu 22.04. I would like the 21.10 behavior, that is to turn off the VGA display not just blank the display when selecting the "settings->Power->Screen Blank" for 22.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1975557/+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 2023580] [NEW] Touchscreen just works with Pen
Public bug reported: I have a Lenovo Yoga 730 and use the "active Pen 2". Everything worked fine with the previous Version of Ubuntu. Since i installed 23.04, i got some Problems. At the beginnig my Pen doesnt worked correctly. I solved this Problem with some Updates. After that i once changed to xorg and then came back to wayland. Nw in both of them, my Touchscreen just works with the Stylus and not with my fingers anymore, which is really annoiing. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 Uname: Linux 6.3.6-060306-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jun 12 20:00:06 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Lenovo WhiskeyLake-U GT2 [UHD Graphics 620] [17aa:39fe] InstallationDate: Installed on 2023-05-11 (32 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) MachineType: LENOVO 81JR ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.3.6-060306-generic root=UUID=5288c76f-982f-4f19-a751-1f28abac1f9f ro quiet splash resume=UUID=e07eea5d-7392-4dd3-bf67-4162e5574848 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2020 dmi.bios.release: 2.21 dmi.bios.vendor: LENOVO dmi.bios.version: 9NCN21WW(V2.06) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 730-13IWL dmi.ec.firmware.release: 2.21 dmi.modalias: dmi:bvnLENOVO:bvr9NCN21WW(V2.06):bd12/25/2020:br2.21:efr2.21:svnLENOVO:pn81JR:pvrLenovoYOGA730-13IWL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA730-13IWL:skuLENOVO_MT_81JR_BU_idea_FM_YOGA730-13IWL: dmi.product.family: YOGA 730-13IWL dmi.product.name: 81JR dmi.product.sku: LENOVO_MT_81JR_BU_idea_FM_YOGA 730-13IWL dmi.product.version: Lenovo YOGA 730-13IWL dmi.sys.vendor: LENOVO 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 N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar 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/2023580 Title: Touchscreen just works with Pen Status in xorg package in Ubuntu: New Bug description: I have a Lenovo Yoga 730 and use the "active Pen 2". Everything worked fine with the previous Version of Ubuntu. Since i installed 23.04, i got some Problems. At the beginnig my Pen doesnt worked correctly. I solved this Problem with some Updates. After that i once changed to xorg and then came back to wayland. Nw in both of them, my Touchscreen just works with the Stylus and not with my fingers anymore, which is really annoiing. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 Uname: Linux 6.3.6-060306-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jun 12 20:00:06 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Lenovo WhiskeyLake-U GT2 [UHD Graphics 620] [17aa:39fe] InstallationDate: Installed on 2023-05-11 (32 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) MachineType: LENOVO 81JR ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.3.6-060306-generic root=UUID=5288c76f-982f-4f19-a751-1f28abac1f9f ro quiet splash resume=UUID=e07eea5d-7392-4dd3-bf67-4162e5574848 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2020 dmi.bios.release: 2.21 dmi.bios.vendor: LENOVO dmi.bios.version:
[Desktop-packages] [Bug 2023571] Re: Update to gjs 1.76.1 and SRU it
** Description changed: [ Impact ] + There is a new bugfix release in the stable series associated with GNOME 44 - That's the current GNOME stable update, including some fixes and translation updates - https://gitlab.gnome.org/GNOME/gjs/-/commits/1.76.1 + https://gitlab.gnome.org/GNOME/gjs/-/blob/1.76.1/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. - 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). + 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). ** Tags added: lunar upgrade-software-version ** Changed in: gjs (Ubuntu Lunar) Status: Fix Committed => In Progress -- 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.1 and SRU it Status in gjs package in Ubuntu: Fix Committed 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.1/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 1970291] Re: [nvidia] Secondary monitor performance is slow on an Nvidia hybrid system in Wayland sessions
Wanted to update on this. I tested 525 and 530 and it has the same issue with 2 monitors. I will test 535 right now. -- 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 2023500] Re: Ctrl + click and Shift + click don't work to select multiple files
https://gitlab.gnome.org/GNOME/nautilus/-/issues/3002 suggests it was fixed in gtk, could you check if the gtk update on bug #2022851 is resolving the issue for you? ** Summary changed: - Ctrl + click and Shift + click don't work to select multiple files + Ctrl or Shift + click don't work to select multiple files in listview ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #3002 https://gitlab.gnome.org/GNOME/nautilus/-/issues/3002 -- 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/2023500 Title: Ctrl or Shift + click don't work to select multiple files in listview Status in nautilus package in Ubuntu: Incomplete Bug description: I am trying to select multiple files in nautilus with keyboard + mouse and none of the default method works. Neither Ctrl + left clicking on each file or Shift + left clicking and selecting the last item work. Selecting using only the mouse by dragging over multiple files do work. I can reproduce this bug in two different PCs running Ubuntu 23.04 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: nautilus 1:44.0-1ubuntu2 Uname: Linux 6.3.6-060306-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jun 11 17:05:50 2023 InstallationDate: Installed on 2022-02-02 (494 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: nautilus UpgradeStatus: Upgraded to lunar on 2023-04-15 (57 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2023500/+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] [NEW] SRU gjs 1.72.3 to jammy
Public bug reported: [ Impact ] That's the GNOME 42 stable update, including some fixes: https://gitlab.gnome.org/GNOME/gjs/-/commits/1.72.3 [ 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). ** Affects: gjs (Ubuntu) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: Fix Released ** Affects: gjs (Ubuntu Jammy) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress ** Also affects: gjs (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: gjs (Ubuntu Jammy) Status: New => In Progress ** Changed in: gjs (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: gjs (Ubuntu Jammy) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- 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.3 to jammy Status in gjs package in Ubuntu: Fix Released Status in gjs source package in Jammy: In Progress Bug description: [ Impact ] That's the GNOME 42 stable update, including some fixes: https://gitlab.gnome.org/GNOME/gjs/-/commits/1.72.3 [ 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.1 and SRU it
** Changed in: gjs (Ubuntu) Status: In Progress => Fix Committed ** Changed in: gjs (Ubuntu Lunar) Status: In Progress => Fix Committed -- 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.1 and SRU it Status in gjs package in Ubuntu: Fix Committed Status in gjs source package in Lunar: Fix Committed Bug description: [ Impact ] That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/gjs/-/commits/1.76.1 [ 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). 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 2023571] [NEW] Update to gjs 1.76.1 and SRU it
Public bug reported: [ Impact ] That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/gjs/-/commits/1.76.1 [ 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). 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). ** Affects: gjs (Ubuntu) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress ** Affects: gjs (Ubuntu Lunar) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress ** Also affects: gjs (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: gjs (Ubuntu Lunar) Status: New => Fix Committed ** Changed in: gjs (Ubuntu Lunar) Importance: Undecided => Medium ** Changed in: gjs (Ubuntu Lunar) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: gjs (Ubuntu Lunar) Status: Fix Committed => In Progress -- 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.1 and SRU it Status in gjs package in Ubuntu: In Progress Status in gjs source package in Lunar: In Progress Bug description: [ Impact ] That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/gjs/-/commits/1.76.1 [ 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). 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 2022882] Re: Lunar - gnome-shell crashes
I can confirm that there are no crashes anymore after the update to 44.1 ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2022882 Title: Lunar - gnome-shell crashes Status in gnome-shell package in Ubuntu: Fix Released Bug description: Since updating from Kinetic to Lunar my gnome-shell regularly crashes. It happens out of nothing, sorry I cannot give any hint on how to reproduce it :( This is happening ~ 3 to 5 times a day. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 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: Mon Jun 5 08:04:13 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-01-16 (139 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 44.0-2ubuntu4.23.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-05-10 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2022882/+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 2023500] Re: Ctrl + click and Shift + click don't work to select multiple files
I use list view. I just checked and the bug is not present in icon view, I am sorry I didn't realize it before. I am using a Spanish (latinamerica) layout, keyboard and mouse are the only input methods active. -- 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/2023500 Title: Ctrl + click and Shift + click don't work to select multiple files Status in nautilus package in Ubuntu: Incomplete Bug description: I am trying to select multiple files in nautilus with keyboard + mouse and none of the default method works. Neither Ctrl + left clicking on each file or Shift + left clicking and selecting the last item work. Selecting using only the mouse by dragging over multiple files do work. I can reproduce this bug in two different PCs running Ubuntu 23.04 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: nautilus 1:44.0-1ubuntu2 Uname: Linux 6.3.6-060306-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jun 11 17:05:50 2023 InstallationDate: Installed on 2022-02-02 (494 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: nautilus UpgradeStatus: Upgraded to lunar on 2023-04-15 (57 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2023500/+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 2015061] Re: [nvidia][lunar] Corrupted/missing windows title background when opening windows
This seems to have been fixed as of latest nvidia drivers or recent Ubuntu packages updates, at least I'm not observing it anymore since this weekend -- 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/2015061 Title: [nvidia][lunar] Corrupted/missing windows title background when opening windows Status in mutter package in Ubuntu: Confirmed Bug description: Since upgrading to Ubuntu 23.04 (from 22.10), the title bar of some apps are corrupted when the windows first open. As soon as I de-focus and re-focus them, the title bar starts working mostly correctly. You'll find a screenshot attached. Basically, the window just repeats the pattern of the edge, until it is de-focused, and then it will properly draw the "window inactive" background color. When the window is de-focused, clicking the title bar won't focus it, although double- clicking on it will maximize it. I need to click within the window body to focus it. Edit: Looking at the screenshot file, it seems like the screenshot even assumed the title bar was actually transparent (the alpha channel of the status bar is 0 in the screenshot!) All GNOME settings were reset using dconf after upgrade, and custom themes have been removed (this is all Yaru defaults). This is happening with almost all apps, including Terminator or Thunderbird. Gnome package versions: ii gir1.2-gnomeautoar-0.1:amd640.4.4-1 amd64GObject introspection data for GnomeAutoar ii gir1.2-gnomebg-4.0:amd6444.0-1 amd64Introspection data for GnomeBG (GTK 4) ii gir1.2-gnomebluetooth-3.0:amd64 42.5-3 amd64Introspection data for GnomeBluetooth ii gir1.2-gnomedesktop-3.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 3) ii gir1.2-gnomedesktop-4.0:amd64 44.0-1 amd64Introspection data for GnomeDesktop (GTK 4) ii gkbd-capplet3.28.1-1 amd64GNOME control center tools for libgnomekbd ii gnome-accessibility-themes 3.28-2ubuntu1 all High Contrast GTK 2 theme and icons ii gnome-bluetooth-3-common42.5-3 all GNOME Bluetooth 3 common files ii gnome-bluetooth-sendto 42.5-3 amd64GNOME Bluetooth Send To app ii gnome-calculator 1:44.0-1ubuntu1amd64 GNOME desktop calculator ii gnome-calendar 44.0-1 amd64Calendar application for GNOME ii gnome-characters44.0-1 amd64character map application ii gnome-control-center 1:44.0-1ubuntu4amd64 utilities to configure the GNOME desktop ii gnome-control-center-data 1:44.0-1ubuntu4all configuration applets for GNOME - data files ii gnome-control-center-faces 1:44.0-1ubuntu4all utilities to configure the GNOME desktop - faces images ii gnome-desktop3-data 44.0-1 all Common files for GNOME desktop apps ii gnome-disk-utility 44.0-1ubuntu1 amd64manage and configure disk drives and media ii gnome-font-viewer 44.0-1 amd64font viewer for GNOME ii gnome-initial-setup 44.0-1ubuntu1 amd64Initial GNOME system setup helper ii gnome-keyring 42.1-1
[Desktop-packages] [Bug 2022851] Re: Nautilus displays invalid directory content after deleting
Julien & Christians, I am unable to duplicate that issue if I use Nautilus 1:44.2.1-0ubuntu1 which is now also available in mantic- proposed. 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). -- 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 Committed 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 1997126] Re: nautilus freezes when renaming multiple folders
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at https://wiki.ubuntu.com/Backtrace#Already_running_programs and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem. ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- 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/1997126 Title: nautilus freezes when renaming multiple folders Status in nautilus package in Ubuntu: Incomplete Bug description: select more than 2 folders, hit F2 o select "rename" in contextual menu nautilus freezes ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-1009.10-lowlatency 5.19.7 Uname: Linux 5.19.0-1009-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Nov 18 21:05:15 2022 GsettingsChanges: b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'medium'" b'org.gnome.nautilus.window-state' b'initial-size' b'(1272, 787)' b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2022-05-13 (189 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: nautilus UpgradeStatus: Upgraded to kinetic on 2022-10-19 (30 days ago) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 python3-nautilus 4.0-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1997126/+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 1882878] Re: The user panel let you enroll the same finger several times
** Changed in: fprintd (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1882878 Title: The user panel let you enroll the same finger several times Status in gnome-control-center: Fix Released Status in fprintd package in Ubuntu: Fix Released Status in gnome-control-center package in Ubuntu: Fix Released Bug description: We are able to enroll the same finger for all 10 available options. (No error like 'Fingerprint is already enrolled' is observed). In windows it doesn’t allow to enroll the same finger, it has a duplicate check API. Here we have all 10 finger options are shown in GUI itself, so whichever finger is enrolled atleast the same finger can be grayed out so that user cannot enroll the same finger again. The release of Ubuntu: Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1882878/+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 1995059] Re: Gnome Control Center sometime hangs if invoked immediately after login from quick settings
Thank you for your bug report. Is that still an issue in the current version? If so could you add a 'journalctl -b 0' log from the system after hitting the issue? ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-control-center (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1995059 Title: Gnome Control Center sometime hangs if invoked immediately after login from quick settings Status in gnome-control-center package in Ubuntu: Incomplete Bug description: Gnome Control Center sometime hangs if invoked immediately after login from quick settings panel in wayland session. The display glitch and no window is displayed. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-control-center 1:43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Oct 28 08:56:20 2022 InstallationDate: Installed on 2022-10-21 (7 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1995059/+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 1995319] Re: Nautilus (Files program) window slides itself behind the programs-taskbar on left every once in a while.
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions: * Is this reproducible? * If so, what specific steps should we take to recreate this bug? This will help us to find and resolve the problem. ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- 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/1995319 Title: Nautilus (Files program) window slides itself behind the programs- taskbar on left every once in a while. Status in nautilus package in Ubuntu: Incomplete Bug description: No further information. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Nov 1 03:44:58 2022 InstallationDate: Installed on 2021-06-07 (511 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: nautilus UpgradeStatus: Upgraded to kinetic on 2022-10-26 (6 days ago) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 nautilus-share0.7.5-0.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1995319/+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 1994959] Re: "Switch input sources individually for each window" does not remember the input source
Thank you for your bug report, indeed that options handles active windows but doesn't store state between restarts ** Package changed: gnome-control-center (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1994959 Title: "Switch input sources individually for each window" does not remember the input source Status in gnome-shell package in Ubuntu: New Bug description: When using: Settings->keyboard->Input Source Switching->Switch input sources individually for each window and set an input source for a window, then if I close the window and reopen it, it does not remember what input source was set to it, I have to set it every time. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.7-0ubuntu0.22.04.5 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Oct 27 11:41:16 2022 InstallationDate: Installed on 2022-10-14 (12 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1994959/+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 1993573] Re: Blurry Ubuntu logo and name in about tab
Is that still an issue in the current version? ** Changed in: gnome-control-center (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1993573 Title: Blurry Ubuntu logo and name in about tab Status in gnome-control-center: Fix Released Status in gnome-control-center package in Ubuntu: Incomplete Status in gnome-control-center package in Fedora: Confirmed Bug description: I have a 4K display running on 1440p and I noticed the Ubuntu's logo and name are not sharp in the about page (see attached picture) --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2021-11-26 (326 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-control-center 1:43.0-1ubuntu2 PackageArchitecture: amd64 Tags: third-party-packages kinetic Uname: Linux 6.1.0-060100rc1-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-06-14 (126 days ago) UserGroups: adm cdrom dip docker kvm libvirt lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True 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: 2022-05-22T10:55:32.223191 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1993573/+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 1994183] Re: Freezes randomly, weird behaviour when I right click with my mouse
Thank you for your bug report. Is that still an issue in the current version? If so could you get a 'journalctl -b 0' log after hitting the issue and attach the log to the report? ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: Confirmed => Incomplete -- 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/1994183 Title: Freezes randomly, weird behaviour when I right click with my mouse Status in nautilus package in Ubuntu: Incomplete Bug description: When using the Files navigator, it sometimes freezes. When I right click with my mouse anywhere the menu that pops up has a lot of lag. All of this happened after the update from 22.04 to 22.10 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 25 22:22:28 2022 GsettingsChanges: b'org.gnome.nautilus.preferences' b'fts-enabled' b'false' b'org.gnome.nautilus.window-state' b'initial-size' b'(901, 550)' InstallationDate: Installed on 2022-06-13 (133 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) SourcePackage: nautilus UpgradeStatus: Upgraded to kinetic on 2022-10-22 (3 days ago) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1994183/+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 2013126] Re: file chooser dialog doesn't respect system theme
** Changed in: xdg-desktop-portal-gnome (Ubuntu) Status: Confirmed => Won't Fix ** Also affects: libadwaita-1 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: xdg-desktop-portal-gnome (Ubuntu Jammy) Importance: Undecided Status: New ** No longer affects: libadwaita-1 (Ubuntu Jammy) ** No longer affects: xdg-desktop-portal-gnome (Ubuntu Jammy) ** Also affects: libadwaita-1 (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: xdg-desktop-portal-gnome (Ubuntu Lunar) Importance: Undecided Status: New ** No longer affects: xdg-desktop-portal-gnome (Ubuntu Lunar) ** Changed in: libadwaita-1 (Ubuntu Lunar) Status: New => Fix Committed ** Changed in: libadwaita-1 (Ubuntu Lunar) Importance: Undecided => High ** Changed in: libadwaita-1 (Ubuntu Lunar) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal-gnome in Ubuntu. https://bugs.launchpad.net/bugs/2013126 Title: file chooser dialog doesn't respect system theme Status in libadwaita-1 package in Ubuntu: Fix Released Status in xdg-desktop-portal-gnome package in Ubuntu: Won't Fix Status in libadwaita-1 source package in Lunar: Fix Committed Bug description: The file chooser dialog uses the default (light) style, even when the dark style is enabled. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xdg-desktop-portal-gnome 44~beta-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Mar 28 21:08:55 2023 InstallationDate: Installed on 2022-09-07 (202 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: xdg-desktop-portal-gnome UpgradeStatus: Upgraded to lunar on 2023-03-28 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libadwaita-1/+bug/2013126/+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 2015465] Re: gnome-control-center crashed with SIGSEGV in undefined_value.lto_priv()
The issue seems similar to bug #2006500 and was fixed before lunar release ** Changed in: gnome-control-center (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2015465 Title: gnome-control-center crashed with SIGSEGV in undefined_value.lto_priv() Status in gnome-control-center package in Ubuntu: Fix Released Bug description: This is a fresh installation of Ubuntu 23.04 Beta in KVM. I resized the virt-manager windows and then gnome-control-center crashed. ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-control-center 1:44.0-1ubuntu4 ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6 Uname: Linux 6.2.0-19-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Thu Apr 6 12:55:26 2023 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2023-04-06 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Beta amd64 (20230329) ProcCmdline: /usr/bin/gnome-control-center ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0x7f2ec6642f10:shl$0x62,%dh PC (0x7f2ec6642f10) in non-executable VMA region: 0x7f2ec6642000-0x7f2ec67bd000 rw-p /usr/lib/x86_64-linux-gnu/libgtk-4.so.1.1000.1 source "$0x62" ok destination "%dh" ok SegvReason: executing writable VMA /usr/lib/x86_64-linux-gnu/libgtk-4.so.1.1000.1 Signal: 11 SourcePackage: gnome-control-center StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libgtk-4.so.1 ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2015465/+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 1998286] Re: Release mutter 42.9 to jammy
Are there any timeline for the updated mutter in jammy? We are waiting for this fix for one of the Xilinx's customer. -- 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/1998286 Title: Release mutter 42.9 to jammy Status in mutter package in Ubuntu: Triaged Bug description: Release mutter 42.9 to jammy At least 42.6 is required to fix bug 1961563 (Xilinx Wayland support) and bug 1988256 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1998286/+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 2023500] Re: Ctrl + click and Shift + click don't work to select multiple files
Thank you for your bug report. Do you use the list or icon view? Which keyboard layout and input method are active? ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: Confirmed => Incomplete -- 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/2023500 Title: Ctrl + click and Shift + click don't work to select multiple files Status in nautilus package in Ubuntu: Incomplete Bug description: I am trying to select multiple files in nautilus with keyboard + mouse and none of the default method works. Neither Ctrl + left clicking on each file or Shift + left clicking and selecting the last item work. Selecting using only the mouse by dragging over multiple files do work. I can reproduce this bug in two different PCs running Ubuntu 23.04 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: nautilus 1:44.0-1ubuntu2 Uname: Linux 6.3.6-060306-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jun 11 17:05:50 2023 InstallationDate: Installed on 2022-02-02 (494 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: nautilus UpgradeStatus: Upgraded to lunar on 2023-04-15 (57 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2023500/+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 2023548] [NEW] Update libadwaita to 1.1.7
Public bug reported: Impact -- 1. There is a new release in the stable 1.1 series. https://gitlab.gnome.org/GNOME/libadwaita/-/blob/1.1.7/NEWS Test Case 1 --- After installing the update, install gnome-text-editor or gnome-shell-extension-manager or file and run them. Ensure that the apps run and that the on/off switches, checkboxes, and other visual elements still display correctly. In gnome-control-center click Appearance in the sidebar. Verify that switching the style between Light and Dark works correctly. Also choose a different accent color and verify that elements like folder icons in Nautilus and on/off switches have correctly adopted the accent color you chose. Test Case 2 --- Run adwaita-1-demo run the style classes demo check that all elements are properly visible and check that link color has enough contrast with background. What Could Go Wrong --- libadwaita is an addon library to GTK4 to allow apps to easily use more of the GNOME style and allow for widgets to be added and improved faster than in the normal GTK development cycle. libadwaita is included in all Ubuntu desktop flavors except for Kubuntu & Lubuntu. Few default Ubuntu desktop in 22.04 use libadwaita, but they do all the snaps using desktop portals file UI elements or GNOME Shell extensions settings. As a component of GNOME core, there is a micro-release exception for libadwaita. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME ** Affects: libadwaita-1 (Ubuntu) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: Fix Released ** Affects: libadwaita-1 (Ubuntu Jammy) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress ** Also affects: libadwaita-1 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: libadwaita-1 (Ubuntu Jammy) Status: New => In Progress ** Changed in: libadwaita-1 (Ubuntu Jammy) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: libadwaita-1 (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: libadwaita-1 (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libadwaita-1 in Ubuntu. https://bugs.launchpad.net/bugs/2023548 Title: Update libadwaita to 1.1.7 Status in libadwaita-1 package in Ubuntu: Fix Released Status in libadwaita-1 source package in Jammy: In Progress Bug description: Impact -- 1. There is a new release in the stable 1.1 series. https://gitlab.gnome.org/GNOME/libadwaita/-/blob/1.1.7/NEWS Test Case 1 --- After installing the update, install gnome-text-editor or gnome-shell-extension-manager or file and run them. Ensure that the apps run and that the on/off switches, checkboxes, and other visual elements still display correctly. In gnome-control-center click Appearance in the sidebar. Verify that switching the style between Light and Dark works correctly. Also choose a different accent color and verify that elements like folder icons in Nautilus and on/off switches have correctly adopted the accent color you chose. Test Case 2 --- Run adwaita-1-demo run the style classes demo check that all elements are properly visible and check that link color has enough contrast with background. What Could Go Wrong --- libadwaita is an addon library to GTK4 to allow apps to easily use more of the GNOME style and allow for widgets to be added and improved faster than in the normal GTK development cycle. libadwaita is included in all Ubuntu desktop flavors except for Kubuntu & Lubuntu. Few default Ubuntu desktop in 22.04 use libadwaita, but they do all the snaps using desktop portals file UI elements or GNOME Shell extensions settings. As a component of GNOME core, there is a micro-release exception for libadwaita. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libadwaita-1/+bug/2023548/+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 1993046] Re: Nautilus Phone Bug
Thank you for your bug report. Could you provide a 'journalctl -b 0' log from the machine after hitting the issue? Could you also check the cable you are using and the connection to the phone? ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- 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/1993046 Title: Nautilus Phone Bug Status in nautilus package in Ubuntu: Incomplete Bug description: affects ubuntu affects ubuntu 22.04.1 LTS affects ubuntu 20.04 LTS. I searched the Launchpad bug list and did not find this bug listed. Most of the time when I try to browse my phone, it gives me the "Unhandled error message:The name:1.852 was not provided by any .service files" error comes up and I have to run "nautilus -q" to close all my files windows and then reopen and reposition them all. This bug has occurred with both a Samsung Galaxy S22 and Galaxy S9. Screen attached of Nautilus error message. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1993046/+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 1993797] Re: refreshing the view with F5 forgets the sort order
The issue seems indeed resolved in the current version ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: Confirmed => 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/1993797 Title: refreshing the view with F5 forgets the sort order Status in nautilus package in Ubuntu: Fix Released Bug description: Steps to reproduce: 1. Open Nautilus 2. Switch to list view 3. Sort by size or mtime by clicking on the relevant heading 4. Press F5 to refresh the view Expectation: - Nautilus remembers the sort order Actual behavior: - the list is now sorted by name (in ascending order) Additional information: - This is a regression since Ubuntu 22.04 LTS - I was unable to reproduce the problem using the org.gnome.NautilusDevel flatpak from gnome-nightly ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Oct 21 12:58:21 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2019-06-12 (1226 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: nautilus UpgradeStatus: Upgraded to kinetic on 2022-10-21 (0 days ago) usr_lib_nautilus: file-roller 43.0-1 nautilus-dropbox 2019.02.14-1.2 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1993797/+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 1965208] Update Released
The verification of the Stable Release Update for gnome-shell-extension- ubuntu-dock 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 gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1965208 Title: Ubuntu dock is visible too early during the login animation Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Jammy: Fix Released Bug description: [ Impact ] Ubuntu dock is visible too early during the login animation: It appears immediately, disappears, then appears again. [ Test case ] Run: env GNOME_SHELL_SESSION_MODE='ubuntu' GNOME_SHELL_SLOWDOWN_FACTOR=3 \ dbus-run-session gnome-shell --nested --wayland --unsafe-mode Observe that the dock should be hidden while the startup animation happens, and doesn't hide and snow again [ Regression potential ] Dock is never shown or animation is not properly executed. --- In jammy this problem only occurred in Xorg sessions, but in kinetic it now occurs in Wayland sessions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1965208/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1935070] Re: Traceback during 'ubuntu-drivers list'
This bug was fixed in the package ubuntu-drivers-common - 1:0.9.6.2~0.22.04.3 --- ubuntu-drivers-common (1:0.9.6.2~0.22.04.3) jammy; urgency=medium * UbuntuDrivers/detect.py: - Fix "882:5 local variable 'with_nvidia_kms' is assigned to but never used" FTBFS (triggered by tests/test_static.py). ubuntu-drivers-common (1:0.9.6.2~0.22.04.2) jammy; urgency=medium [ Alberto Milone ] * debian/rules: - Limit the tests to the selected architectures (amd64, arm64). This prevents armhf builds from failing. * UbuntuDrivers/detect.py: - Make sure all -open drivers have a lower priority, regardless of whether the --server parameter is passed in or not. - Update regex and unify package name parsing in the following functions by using the new NvidiaPkgNameInfo class: nvidia_desktop_pre_installation_hook, _get_headless_no_dkms_metapackage, nvidia_desktop_pre_installation_hook, get_linux_modules_metapackage, This prevents ubuntu-drivers from crashing when dealing with the -open NVIDIA drivers (LP: #1993019). * tests/test_ubuntu_drivers.py: - Add tests so we make sure to keep preferring non-open NVIDIA modules over the -open ones, at least until the open modules catch up feature wise and performance wise. [ gongzhengyang ] * UbuntuDrivers/detect.py: - Fix local variable 'version' being referenced before assignment when catching ValueError (LP: #1993019). [ Jeff Lane ] * detect-plugins/sl-modem.py: - Add some error trapping when aplay is not installed (on servers) (LP: #1935070). -- Alberto Milone Wed, 08 Mar 2023 16:03:28 + ** Changed in: ubuntu-drivers-common (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1935070 Title: Traceback during 'ubuntu-drivers list' Status in Ubuntu Drivers Common: New Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Kinetic: Fix Released Bug description: [ Impact ] * Calling the ubuntu-drivers tool where the alsa-utils package is not installed (mainly on servers), ubuntu-drivers (through the sl-modem plugin) complains, unnecessarily about the missing aplay binary. [ Test Plan ] * Install the new ubuntu-drivers-common from -proposed, and make sure that alsa-utils is not installed. * Run the ubuntu-drivers list command. * Check that ubuntu-drivers does not complain about the missing aplay tool. [ Where problems could occur ] * A problem in the ubuntu-drivers tool can cause it to install a driver which is not recommended for the detected hardware, or even cause the package installation to fail, and prevent users from logging in through the graphics interface. [ Other Info ] - ___ ubuntu@doubletusk:~$ sudo ubuntu-drivers list ERROR:root:could not open aplay -l Traceback (most recent call last): File "/usr/share/ubuntu-drivers-common/detect/sl-modem.py", line 35, in detect aplay = subprocess.Popen( File "/usr/lib/python3.8/subprocess.py", line 858, in __init__ self._execute_child(args, executable, preexec_fn, close_fds, File "/usr/lib/python3.8/subprocess.py", line 1704, in _execute_child raise child_exception_type(errno_num, err_msg, err_filename) FileNotFoundError: [Errno 2] No such file or directory: 'aplay' nvidia-driver-418-server, (kernel modules provided by nvidia-dkms-418-server) nvidia-driver-470, (kernel modules provided by nvidia-dkms-470) nvidia-driver-460-server, (kernel modules provided by nvidia-dkms-460-server) nvidia-driver-465, (kernel modules provided by nvidia-dkms-465) nvidia-driver-450-server, (kernel modules provided by nvidia-dkms-450-server) nvidia-driver-460, (kernel modules provided by nvidia-dkms-460) ubuntu@doubletusk:~$ apt-cache policy ubuntu-drivers-common ubuntu-drivers-common: Installed: 1:0.9.0~0.20.04.1 Candidate: 1:0.9.0~0.20.04.1 Version table: *** 1:0.9.0~0.20.04.1 500 500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1:0.8.6.5~0.20.04.1 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 1:0.8.1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages ubuntu@doubletusk:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS Release:20.04 Codename: focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-drivers-common/+bug/1935070/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1965208] Re: Ubuntu dock is visible too early during the login animation
This bug was fixed in the package gnome-shell-extension-ubuntu-dock - 72~ubuntu5.22.04.2.1 --- gnome-shell-extension-ubuntu-dock (72~ubuntu5.22.04.2.1) jammy; urgency=medium * Keep shell overview always visible and usable (LP: #1979096): - docking: Do ControlsManagerLayout allocation with box-adjusted workArea - docking: Be more consistent in reducing the overlay layout space - docking: Add both bottom and top spacing when there are no workspaces gnome-shell-extension-ubuntu-dock (72~ubuntu5.22.04.2) jammy; urgency=medium [ Marco Trevisan (Treviño) ] * debian/control: Update maintainer to myself * Ensure startup animations are performed on monitor changes (LP: #2019751): - utils: Ensure we destroy the Signals handler as last thing on destroy - docking: Do not wait for dash animation two times with no overview - docking: Ensure we perform the startup animation completely on docks updates (LP: #1965208) - docking: Use a try/catch statement on our promise to show errors in case - docking: Cleanup startup animation injections once done - docking: Handle monitors changed events while preparing startup animation - docking: Keep clip and coverPane size matching current setup - docking: Handle when dash is destroyed during the login animation * Do not hide the dock when menus are closed (LP: #1983130): - docking: Ignore hover changes if overview is visible (LP: #1983130) - docking: Check if autohide or intellihide is enabled on menu closed * Keep shell overview always visible and usable (LP: #1979096): - docking: Also reduce the app grid area when in auto-hide mode (LP: #1992847) - docking: Use an even width for the overview content area - docking: Keep overview controls layout proportions when resizing it (LP: #1992847) [ Daniel van Vugt ] * docking: Handle when dash is destroyed during the login animation (LP: #2019751) -- Marco Trevisan (Treviño) Fri, 02 Jun 2023 04:12:06 +0200 ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy) Status: Fix Committed => 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/1965208 Title: Ubuntu dock is visible too early during the login animation Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Jammy: Fix Released Bug description: [ Impact ] Ubuntu dock is visible too early during the login animation: It appears immediately, disappears, then appears again. [ Test case ] Run: env GNOME_SHELL_SESSION_MODE='ubuntu' GNOME_SHELL_SLOWDOWN_FACTOR=3 \ dbus-run-session gnome-shell --nested --wayland --unsafe-mode Observe that the dock should be hidden while the startup animation happens, and doesn't hide and snow again [ Regression potential ] Dock is never shown or animation is not properly executed. --- In jammy this problem only occurred in Xorg sessions, but in kinetic it now occurs in Wayland sessions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1965208/+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 1974293] Update Released
The verification of the Stable Release Update for gjs 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 gjs in Ubuntu. https://bugs.launchpad.net/bugs/1974293 Title: gnome-shell crashed on logout with SIGSEGV in js::gc::Cell::storeBuffer() from js::gc::PostWriteBarrierImpl() Status in gjs: Fix Released Status in OEM Priority Project: Confirmed Status in gjs package in Ubuntu: Fix Released Status in gjs source package in Jammy: Fix Released Status in gjs source package in Kinetic: Won't Fix Status in gjs source package in Lunar: Fix Released Status in gnome-shell package in Fedora: Confirmed Bug description: [ Impact ] gnome-shell often crashes on logout causing annoyance to the user as an error report dialog is displayed at the next login. [ Test Plan ] 1. Log into gnome-shell 2. Use gnome-shell for long enough to trigger a garbage collection cycle: Scroll the app grid and repeatedly open the calendar from the top bar for 30 seconds. 3. Log out. 4. Verify no new gnome-shell crash files appear in /var/crash/ [ Where problems could occur ] Only gnome-shell shutdown/logout is affected. [ Other Info ] https://errors.ubuntu.com/problem/256d1c0d1aad03bb024b525f4c80868e8f6a85b4 https://errors.ubuntu.com/problem/b1669e114babda005eb5a6414867a0eb7293f7e7 Description: Ubuntu 22.04 LTS Release: 22.04 ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri May 20 16:06:35 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1649813447 InstallationDate: Installed on 2022-05-05 (14 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/ubuntu RelatedPackageVersions: mutter-common 42.0-3ubuntu2 Signal: 11 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libmozjs-91.so.0 ?? () from /lib/x86_64-linux-gnu/libgjs.so.0 ?? () from /lib/x86_64-linux-gnu/libgjs.so.0 g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () Title: gnome-shell crashed with SIGSEGV in g_object_unref() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gjs/+bug/1974293/+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 1979096] Re: gnome-shell search can't launch apps if dock auto-hide is enabled
This bug was fixed in the package gnome-shell-extension-ubuntu-dock - 72~ubuntu5.22.04.2.1 --- gnome-shell-extension-ubuntu-dock (72~ubuntu5.22.04.2.1) jammy; urgency=medium * Keep shell overview always visible and usable (LP: #1979096): - docking: Do ControlsManagerLayout allocation with box-adjusted workArea - docking: Be more consistent in reducing the overlay layout space - docking: Add both bottom and top spacing when there are no workspaces gnome-shell-extension-ubuntu-dock (72~ubuntu5.22.04.2) jammy; urgency=medium [ Marco Trevisan (Treviño) ] * debian/control: Update maintainer to myself * Ensure startup animations are performed on monitor changes (LP: #2019751): - utils: Ensure we destroy the Signals handler as last thing on destroy - docking: Do not wait for dash animation two times with no overview - docking: Ensure we perform the startup animation completely on docks updates (LP: #1965208) - docking: Use a try/catch statement on our promise to show errors in case - docking: Cleanup startup animation injections once done - docking: Handle monitors changed events while preparing startup animation - docking: Keep clip and coverPane size matching current setup - docking: Handle when dash is destroyed during the login animation * Do not hide the dock when menus are closed (LP: #1983130): - docking: Ignore hover changes if overview is visible (LP: #1983130) - docking: Check if autohide or intellihide is enabled on menu closed * Keep shell overview always visible and usable (LP: #1979096): - docking: Also reduce the app grid area when in auto-hide mode (LP: #1992847) - docking: Use an even width for the overview content area - docking: Keep overview controls layout proportions when resizing it (LP: #1992847) [ Daniel van Vugt ] * docking: Handle when dash is destroyed during the login animation (LP: #2019751) -- Marco Trevisan (Treviño) Fri, 02 Jun 2023 04:12:06 +0200 ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy) Status: Fix Committed => 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/1979096 Title: gnome-shell search can't launch apps if dock auto-hide is enabled Status in Dash to dock: Fix Released Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Jammy: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Lunar: Fix Released Bug description: [ Impact ] Search [ Test case ] 1. From settings: a. Enable non-fractional scaling of 200% b. Show the dock on the left side c. Enable dock auto-hide 2. Hit Super key and search for any result 3. Hitting Enter key or clicking on an application icon should launch it [ Regression potential ] App grid has wrong sizes or not properly visible --- The problem happens, when I enable the dock to hide automatically. With this enabled, it is not possible to run the programs through the search. But when disabled, it is possible to search and run the programs. Here's the video of the problem. ProblemType: BugDistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 Uname: Linux 5.15.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 17 18:21:45 2022 DistUpgraded: 2022-04-21 13:52:59,951 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: v4l2loopback/0.12.5, 5.15.0-37-generic, x86_64: installed v4l2loopback/0.12.5, 5.15.0-39-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS780L [Radeon 3000] [1002:9616] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. RS780L [Radeon 3000] [1043:8388] InstallationDate: Installed on 2021-04-15 (428 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic root=UUID=7e3c483e-6d02-4fc2-be0e-48207eb147eb ro quiet splash vt.handoff=7SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-04-21 (57 days ago) dmi.bios.date: 03/04/2017 dmi.bios.release: 8.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1201
[Desktop-packages] [Bug 1974293] Re: gnome-shell crashed on logout with SIGSEGV in js::gc::Cell::storeBuffer() from js::gc::PostWriteBarrierImpl()
This bug was fixed in the package gjs - 1.72.2-0ubuntu2 --- gjs (1.72.2-0ubuntu2) jammy; urgency=medium [ Daniel van Vugt ] * Add context-Clear-all-vectors-of-JS-Heap-on-dispose.patch (LP: #1974293) -- Ghadi Elie Rahme Fri, 19 May 2023 11:12:55 + ** Changed in: gjs (Ubuntu Jammy) Status: Fix Committed => Fix Released -- 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/1974293 Title: gnome-shell crashed on logout with SIGSEGV in js::gc::Cell::storeBuffer() from js::gc::PostWriteBarrierImpl() Status in gjs: Fix Released Status in OEM Priority Project: Confirmed Status in gjs package in Ubuntu: Fix Released Status in gjs source package in Jammy: Fix Released Status in gjs source package in Kinetic: Won't Fix Status in gjs source package in Lunar: Fix Released Status in gnome-shell package in Fedora: Confirmed Bug description: [ Impact ] gnome-shell often crashes on logout causing annoyance to the user as an error report dialog is displayed at the next login. [ Test Plan ] 1. Log into gnome-shell 2. Use gnome-shell for long enough to trigger a garbage collection cycle: Scroll the app grid and repeatedly open the calendar from the top bar for 30 seconds. 3. Log out. 4. Verify no new gnome-shell crash files appear in /var/crash/ [ Where problems could occur ] Only gnome-shell shutdown/logout is affected. [ Other Info ] https://errors.ubuntu.com/problem/256d1c0d1aad03bb024b525f4c80868e8f6a85b4 https://errors.ubuntu.com/problem/b1669e114babda005eb5a6414867a0eb7293f7e7 Description: Ubuntu 22.04 LTS Release: 22.04 ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri May 20 16:06:35 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1649813447 InstallationDate: Installed on 2022-05-05 (14 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/ubuntu RelatedPackageVersions: mutter-common 42.0-3ubuntu2 Signal: 11 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libmozjs-91.so.0 ?? () from /lib/x86_64-linux-gnu/libgjs.so.0 ?? () from /lib/x86_64-linux-gnu/libgjs.so.0 g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () Title: gnome-shell crashed with SIGSEGV in g_object_unref() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gjs/+bug/1974293/+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 1983130] Re: Ubuntu dock set to auto-hide hides after a right-click menu is closed even when there are no reasons for it to do so.
This bug was fixed in the package gnome-shell-extension-ubuntu-dock - 72~ubuntu5.22.04.2.1 --- gnome-shell-extension-ubuntu-dock (72~ubuntu5.22.04.2.1) jammy; urgency=medium * Keep shell overview always visible and usable (LP: #1979096): - docking: Do ControlsManagerLayout allocation with box-adjusted workArea - docking: Be more consistent in reducing the overlay layout space - docking: Add both bottom and top spacing when there are no workspaces gnome-shell-extension-ubuntu-dock (72~ubuntu5.22.04.2) jammy; urgency=medium [ Marco Trevisan (Treviño) ] * debian/control: Update maintainer to myself * Ensure startup animations are performed on monitor changes (LP: #2019751): - utils: Ensure we destroy the Signals handler as last thing on destroy - docking: Do not wait for dash animation two times with no overview - docking: Ensure we perform the startup animation completely on docks updates (LP: #1965208) - docking: Use a try/catch statement on our promise to show errors in case - docking: Cleanup startup animation injections once done - docking: Handle monitors changed events while preparing startup animation - docking: Keep clip and coverPane size matching current setup - docking: Handle when dash is destroyed during the login animation * Do not hide the dock when menus are closed (LP: #1983130): - docking: Ignore hover changes if overview is visible (LP: #1983130) - docking: Check if autohide or intellihide is enabled on menu closed * Keep shell overview always visible and usable (LP: #1979096): - docking: Also reduce the app grid area when in auto-hide mode (LP: #1992847) - docking: Use an even width for the overview content area - docking: Keep overview controls layout proportions when resizing it (LP: #1992847) [ Daniel van Vugt ] * docking: Handle when dash is destroyed during the login animation (LP: #2019751) -- Marco Trevisan (Treviño) Fri, 02 Jun 2023 04:12:06 +0200 ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy) Status: Fix Committed => 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/1983130 Title: Ubuntu dock set to auto-hide hides after a right-click menu is closed even when there are no reasons for it to do so. Status in Dash to dock: Unknown Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Jammy: Fix Released Bug description: [ Impact ] Dash to dock hides when a right-click menu is closed, even if there's no need for it. [ Test case ] 1. From settings -> Appearance: Enable dock auto-hide 2. Open a window, ensuring the dock is visible 3. Right click on a dock icon, and then click outside the menu to close it 4. The dock should be visible again and not hide (unless is expected) [ Regression potential ] The dock does not hide after closing the menu if a window is below it --- Description: Ubuntu 22.04 LTS Release: 22.04 Expected behavior: Dock set to auto-hide would remain shown after either a right-click menu option is selected, or a right-click menu is cancelled. Actual behavior: Dock hides after a right-click menu closes even when there are no windows in its space. Additional notes: Dock can be temporarily reset to its normal behavior when one of these actions are performed: - when a window enters the dock's usual space - when the "show applications" menu is opened and closed - when a maximized window is opened and closed/minimized To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1983130/+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 1983130] Update Released
The verification of the Stable Release Update for gnome-shell-extension- ubuntu-dock 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 gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1983130 Title: Ubuntu dock set to auto-hide hides after a right-click menu is closed even when there are no reasons for it to do so. Status in Dash to dock: Unknown Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Jammy: Fix Released Bug description: [ Impact ] Dash to dock hides when a right-click menu is closed, even if there's no need for it. [ Test case ] 1. From settings -> Appearance: Enable dock auto-hide 2. Open a window, ensuring the dock is visible 3. Right click on a dock icon, and then click outside the menu to close it 4. The dock should be visible again and not hide (unless is expected) [ Regression potential ] The dock does not hide after closing the menu if a window is below it --- Description: Ubuntu 22.04 LTS Release: 22.04 Expected behavior: Dock set to auto-hide would remain shown after either a right-click menu option is selected, or a right-click menu is cancelled. Actual behavior: Dock hides after a right-click menu closes even when there are no windows in its space. Additional notes: Dock can be temporarily reset to its normal behavior when one of these actions are performed: - when a window enters the dock's usual space - when the "show applications" menu is opened and closed - when a maximized window is opened and closed/minimized To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1983130/+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 1992847] Update Released
The verification of the Stable Release Update for gnome-shell-extension- ubuntu-dock 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 gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1992847 Title: Left/right arrow in app-grid is not usable when using auto-hiding dock and big icons Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Jammy: Fix Released Bug description: [ Impact ] Left or right icons to switch the application grid is not visible or not properly centered in the overview when using auto-hiding dock [ Test case ] 1. Enable auto-hide in dock 1a. Increase the icons size (to make the bug clearer) 2. Open the app grid (super+a) 3. Try to navigate right/left using the right/left arrows 4. They should be usable and properly centered in the available space [ Regression potential ] App grid has not the proper size. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1992847/+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 1992847] Re: Left/right arrow in app-grid is not usable when using auto-hiding dock and big icons
This bug was fixed in the package gnome-shell-extension-ubuntu-dock - 72~ubuntu5.22.04.2.1 --- gnome-shell-extension-ubuntu-dock (72~ubuntu5.22.04.2.1) jammy; urgency=medium * Keep shell overview always visible and usable (LP: #1979096): - docking: Do ControlsManagerLayout allocation with box-adjusted workArea - docking: Be more consistent in reducing the overlay layout space - docking: Add both bottom and top spacing when there are no workspaces gnome-shell-extension-ubuntu-dock (72~ubuntu5.22.04.2) jammy; urgency=medium [ Marco Trevisan (Treviño) ] * debian/control: Update maintainer to myself * Ensure startup animations are performed on monitor changes (LP: #2019751): - utils: Ensure we destroy the Signals handler as last thing on destroy - docking: Do not wait for dash animation two times with no overview - docking: Ensure we perform the startup animation completely on docks updates (LP: #1965208) - docking: Use a try/catch statement on our promise to show errors in case - docking: Cleanup startup animation injections once done - docking: Handle monitors changed events while preparing startup animation - docking: Keep clip and coverPane size matching current setup - docking: Handle when dash is destroyed during the login animation * Do not hide the dock when menus are closed (LP: #1983130): - docking: Ignore hover changes if overview is visible (LP: #1983130) - docking: Check if autohide or intellihide is enabled on menu closed * Keep shell overview always visible and usable (LP: #1979096): - docking: Also reduce the app grid area when in auto-hide mode (LP: #1992847) - docking: Use an even width for the overview content area - docking: Keep overview controls layout proportions when resizing it (LP: #1992847) [ Daniel van Vugt ] * docking: Handle when dash is destroyed during the login animation (LP: #2019751) -- Marco Trevisan (Treviño) Fri, 02 Jun 2023 04:12:06 +0200 ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy) Status: Fix Committed => 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/1992847 Title: Left/right arrow in app-grid is not usable when using auto-hiding dock and big icons Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Jammy: Fix Released Bug description: [ Impact ] Left or right icons to switch the application grid is not visible or not properly centered in the overview when using auto-hiding dock [ Test case ] 1. Enable auto-hide in dock 1a. Increase the icons size (to make the bug clearer) 2. Open the app grid (super+a) 3. Try to navigate right/left using the right/left arrows 4. They should be usable and properly centered in the available space [ Regression potential ] App grid has not the proper size. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1992847/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1993019] Re: UnboundLocalError: local variable 'version' referenced before assignment
This bug was fixed in the package ubuntu-drivers-common - 1:0.9.6.2~0.22.04.3 --- ubuntu-drivers-common (1:0.9.6.2~0.22.04.3) jammy; urgency=medium * UbuntuDrivers/detect.py: - Fix "882:5 local variable 'with_nvidia_kms' is assigned to but never used" FTBFS (triggered by tests/test_static.py). ubuntu-drivers-common (1:0.9.6.2~0.22.04.2) jammy; urgency=medium [ Alberto Milone ] * debian/rules: - Limit the tests to the selected architectures (amd64, arm64). This prevents armhf builds from failing. * UbuntuDrivers/detect.py: - Make sure all -open drivers have a lower priority, regardless of whether the --server parameter is passed in or not. - Update regex and unify package name parsing in the following functions by using the new NvidiaPkgNameInfo class: nvidia_desktop_pre_installation_hook, _get_headless_no_dkms_metapackage, nvidia_desktop_pre_installation_hook, get_linux_modules_metapackage, This prevents ubuntu-drivers from crashing when dealing with the -open NVIDIA drivers (LP: #1993019). * tests/test_ubuntu_drivers.py: - Add tests so we make sure to keep preferring non-open NVIDIA modules over the -open ones, at least until the open modules catch up feature wise and performance wise. [ gongzhengyang ] * UbuntuDrivers/detect.py: - Fix local variable 'version' being referenced before assignment when catching ValueError (LP: #1993019). [ Jeff Lane ] * detect-plugins/sl-modem.py: - Add some error trapping when aplay is not installed (on servers) (LP: #1935070). -- Alberto Milone Wed, 08 Mar 2023 16:03:28 + ** Changed in: ubuntu-drivers-common (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1993019 Title: UnboundLocalError: local variable 'version' referenced before assignment Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Bionic: Triaged Status in ubuntu-drivers-common source package in Focal: Triaged Status in ubuntu-drivers-common source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Kinetic: Fix Released Bug description: [ Impact ] * The introduction of the -open NVIDIA drivers requires a change in the way we detect driver series and flavours. Failing to do so, causes the ubuntu-drivers tool to crash (LP: #1993019), or to prefer the -open drivers over the non-open ones (LP: #1988836). * Furthermore, calling the ubuntu-drivers tool where the alsa-utils package is not installed (mainly on servers), ubuntu-drivers (through the sl-modem plugin) complains, unnecessarily about the missing aplay binary. [ Test Plan ] * Install the new ubuntu-drivers-common from -proposed on a system where the GPU is compatible with the 515 series (or higher). * Run the ubuntu-drivers list command, and make sure that the 515 driver series (or higher) is listed. * Try installing the driver using the following command: sudo ubuntu-drivers install * Check which driver series was installed (you can use the "sudo ubuntu-drivers debug" command), and make sure that the installation does not cause ubuntu-drivers to crash. [ Where problems could occur ] * A problem in the ubuntu-drivers tool can cause it to install a driver which is not recommended for the detected hardware, or even cause the package installation to fail, and prevent users from logging in through the graphics interface. [ Other Info ] * To prevent failures of the test-suite on architectures such as armhf (as seen in Lunar), we are skipping the tests for any architectures other than amd64 and arm64 (which are the only ones actually using ubuntu-drivers). This was already the case with riscv, and we now have an easier way to do so in the debian/rules file. == Changelogs == === Kinetic and Jammy === [ Alberto Milone ] * New upstream release: * UbuntuDrivers/detect.py: - Make sure all -open drivers have a lower priority, regardless of whether the --server parameter is passed in or not. - Update regex in nvidia_desktop_pre_installation_hook. This prevents ubuntu-drivers from crashing when dealing with the -open NVIDIA drivers (LP: #1993019). * tests/test_ubuntu_drivers.py: - Add tests so we make sure to keep preferring non-open NVIDIA modules over the -open ones, at least until the open modules catch up feature wise and performance wise. [ gongzhengyang ] * UbuntuDrivers/detect.py: - Fix local variable 'version' being referenced before assignment when catching ValueError (LP: #1993019). [ Jeff Lane ]
[Desktop-packages] [Bug 2019751] Re: Desktop area may get clipped to a small rectangle if the hypervisor changes X11 screen resolution during the login animation
This bug was fixed in the package gnome-shell-extension-ubuntu-dock - 72~ubuntu5.22.04.2.1 --- gnome-shell-extension-ubuntu-dock (72~ubuntu5.22.04.2.1) jammy; urgency=medium * Keep shell overview always visible and usable (LP: #1979096): - docking: Do ControlsManagerLayout allocation with box-adjusted workArea - docking: Be more consistent in reducing the overlay layout space - docking: Add both bottom and top spacing when there are no workspaces gnome-shell-extension-ubuntu-dock (72~ubuntu5.22.04.2) jammy; urgency=medium [ Marco Trevisan (Treviño) ] * debian/control: Update maintainer to myself * Ensure startup animations are performed on monitor changes (LP: #2019751): - utils: Ensure we destroy the Signals handler as last thing on destroy - docking: Do not wait for dash animation two times with no overview - docking: Ensure we perform the startup animation completely on docks updates (LP: #1965208) - docking: Use a try/catch statement on our promise to show errors in case - docking: Cleanup startup animation injections once done - docking: Handle monitors changed events while preparing startup animation - docking: Keep clip and coverPane size matching current setup - docking: Handle when dash is destroyed during the login animation * Do not hide the dock when menus are closed (LP: #1983130): - docking: Ignore hover changes if overview is visible (LP: #1983130) - docking: Check if autohide or intellihide is enabled on menu closed * Keep shell overview always visible and usable (LP: #1979096): - docking: Also reduce the app grid area when in auto-hide mode (LP: #1992847) - docking: Use an even width for the overview content area - docking: Keep overview controls layout proportions when resizing it (LP: #1992847) [ Daniel van Vugt ] * docking: Handle when dash is destroyed during the login animation (LP: #2019751) -- Marco Trevisan (Treviño) Fri, 02 Jun 2023 04:12:06 +0200 ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy) Status: Fix Committed => 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/2019751 Title: Desktop area may get clipped to a small rectangle if the hypervisor changes X11 screen resolution during the login animation Status in gnome-shell package in Ubuntu: In Progress Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: Triaged Status in gnome-shell-extension-ubuntu-dock source package in Jammy: Fix Released Status in gnome-shell source package in Lunar: Triaged Status in gnome-shell-extension-ubuntu-dock source package in Lunar: Fix Released Bug description: [ Impact ] GNOME Shell startup animation may not complete during startup, leading to a non-functional GNOME shell because the workarea could be clipped or input events are ignored. [ Test case ] 1. Run this script: https://gitlab.gnome.org/3v1n0/gnome-shell/-/snippets/5749 2. It's expected to launch a gnome-shell nested instance and perform monitor changes 3. The shell should animate to the final state and everything should be usable: - Clicking in shell widgets should work - No area is hidden or clipped [ Regression potential ] GNOME Shell may not start properly, input events are ignored and/or the desktop area is clipped. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2019751/+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 2012388] Re: X11 window (usually AnyDesk) at top-right of the screen is invisible and steals mouse clicks
Important note: this is not only Ubuntu bug. I've got legacy tray icons enabled and AnyDesk as well on Garuda (Arch-based) Linux. Same thing here - invisible box with everything you're describing here. So, basically, I bet this bug affects almost all families of distributions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/2012388 Title: X11 window (usually AnyDesk) at top-right of the screen is invisible and steals mouse clicks Status in gnome-shell-extension-appindicator package in Ubuntu: Confirmed Bug description: Hardware Model: Dell Inc. Inspiron 16 Plus 7620 Firmware version: 1.5.1 CPU i7-12700H x20 GPU: Nvidia RTX3060 / MaxQ GPU: Intel Alder Lake-P Release: Lunar Lobster Architecture: AMD64 Kernel: 6.1.0-16-generic GNOME version: 44.rc Using Latest daily image of Ubuntu Lunar Lobster, I noticed an issue with window focus when windows are placed under the top-right system tray. Since it is hard to explain, I am attaching a screenshot. I am unable to click or interact with anything in the area within green rectangle. Applications affected: - Firefox (snap) - Chromium (snap) - Vivaldi Browser (deb) - Mattermost (snap) ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44~rc-1ubuntu2 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Mar 21 20:35:05 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-01-23 (56 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 44~rc-1ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-03-02 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/2012388/+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 1979096] Update Released
The verification of the Stable Release Update for gnome-shell-extension- ubuntu-dock 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 gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1979096 Title: gnome-shell search can't launch apps if dock auto-hide is enabled Status in Dash to dock: Fix Released Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Jammy: Fix Committed Status in gnome-shell-extension-ubuntu-dock source package in Lunar: Fix Released Bug description: [ Impact ] Search [ Test case ] 1. From settings: a. Enable non-fractional scaling of 200% b. Show the dock on the left side c. Enable dock auto-hide 2. Hit Super key and search for any result 3. Hitting Enter key or clicking on an application icon should launch it [ Regression potential ] App grid has wrong sizes or not properly visible --- The problem happens, when I enable the dock to hide automatically. With this enabled, it is not possible to run the programs through the search. But when disabled, it is possible to search and run the programs. Here's the video of the problem. ProblemType: BugDistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 Uname: Linux 5.15.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 17 18:21:45 2022 DistUpgraded: 2022-04-21 13:52:59,951 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: v4l2loopback/0.12.5, 5.15.0-37-generic, x86_64: installed v4l2loopback/0.12.5, 5.15.0-39-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS780L [Radeon 3000] [1002:9616] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. RS780L [Radeon 3000] [1043:8388] InstallationDate: Installed on 2021-04-15 (428 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic root=UUID=7e3c483e-6d02-4fc2-be0e-48207eb147eb ro quiet splash vt.handoff=7SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-04-21 (57 days ago) dmi.bios.date: 03/04/2017 dmi.bios.release: 8.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1201 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M LX/BR dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1201:bd03/04/2017:br8.15:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-MLX/BR:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2.1 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/dash-to-dock/+bug/1979096/+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 1979096] Re: gnome-shell search can't launch apps if dock auto-hide is enabled
This bug was fixed in the package gnome-shell-extension-ubuntu-dock - 79ubuntu2.23.04.2 --- gnome-shell-extension-ubuntu-dock (79ubuntu2.23.04.2) lunar; urgency=medium * Keep shell overview always visible and usable (LP: #1979096): - docking: Do ControlsManagerLayout allocation with box-adjusted workArea - docking: Be more consistent in reducing the overlay layout space - docking: Add both bottom and top spacing when there are no workspaces -- Marco Trevisan (Treviño) Fri, 02 Jun 2023 16:37:38 +0200 ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Lunar) Status: Fix Committed => 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/1979096 Title: gnome-shell search can't launch apps if dock auto-hide is enabled Status in Dash to dock: Fix Released Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Jammy: Fix Committed Status in gnome-shell-extension-ubuntu-dock source package in Lunar: Fix Released Bug description: [ Impact ] Search [ Test case ] 1. From settings: a. Enable non-fractional scaling of 200% b. Show the dock on the left side c. Enable dock auto-hide 2. Hit Super key and search for any result 3. Hitting Enter key or clicking on an application icon should launch it [ Regression potential ] App grid has wrong sizes or not properly visible --- The problem happens, when I enable the dock to hide automatically. With this enabled, it is not possible to run the programs through the search. But when disabled, it is possible to search and run the programs. Here's the video of the problem. ProblemType: BugDistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 Uname: Linux 5.15.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 17 18:21:45 2022 DistUpgraded: 2022-04-21 13:52:59,951 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: v4l2loopback/0.12.5, 5.15.0-37-generic, x86_64: installed v4l2loopback/0.12.5, 5.15.0-39-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS780L [Radeon 3000] [1002:9616] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. RS780L [Radeon 3000] [1043:8388] InstallationDate: Installed on 2021-04-15 (428 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic root=UUID=7e3c483e-6d02-4fc2-be0e-48207eb147eb ro quiet splash vt.handoff=7SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-04-21 (57 days ago) dmi.bios.date: 03/04/2017 dmi.bios.release: 8.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1201 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M LX/BR dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1201:bd03/04/2017:br8.15:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-MLX/BR:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2.1 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/dash-to-dock/+bug/1979096/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages
[Desktop-packages] [Bug 2017420] Re: Cannot open HEIF/HEIC images in 23.04/lunar anymore
This bug was fixed in the package libheif - 1.14.2-1ubuntu1 --- libheif (1.14.2-1ubuntu1) lunar; urgency=medium * debian/libheif1.dirs: - create the plugins directory, if it's missing the loader is bailing out. Fix opening of heif files in eog (lp: #2017420) -- Sebastien Bacher Thu, 01 Jun 2023 11:31:10 +0200 ** Changed in: libheif (Ubuntu Lunar) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/2017420 Title: Cannot open HEIF/HEIC images in 23.04/lunar anymore Status in eog package in Ubuntu: Invalid Status in gdk-pixbuf package in Ubuntu: Invalid Status in libheif package in Ubuntu: Fix Released Status in eog source package in Lunar: Invalid Status in gdk-pixbuf source package in Lunar: Invalid Status in libheif source package in Lunar: Fix Released Bug description: * Impact The libheif loader is bailing out due to a missing plugin directory which leads to image viewer as eog not being able to open pictures in that format anymore * Testcase Install libheif1 and heif-gdk-pixbuf and try to open a .heif file in eog * Where problems could occur The package build is using the option to not split the codec in separate plugins but the version of Lunar doesn't handle the missing plugins directory and bails out. The code of the version in mantic has been refactored in a way which fixes this problem. For lunar it's easier to just create the directory. The directory is included in the libheif1 binary but that should not create any conflict, it's a temporary situation for lunar only and even if the soname changed dpkg allows for several deb packages to provide the same directory. -- In previous Ubuntu versions, including 22.10, I was able to open HEIF/HEIC files by installing libheif1 and heif-gdk-pixbuf. This does not work anymore in 23.04. Running eog in a terminal displays: $ eog IMG_9996.HEIC ** (eog:44492): WARNING **: 14:29:17.537: Cannot read plugin directory. (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.537: gdk_pixbuf_animation_is_static_image: assertion 'GDK_IS_PIXBUF_ANIMATION (animation)' failed (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.538: gdk_pixbuf_animation_get_iter: assertion 'GDK_IS_PIXBUF_ANIMATION (animation)' failed (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.538: gdk_pixbuf_animation_iter_get_pixbuf: assertion 'GDK_IS_PIXBUF_ANIMATION_ITER (iter)' failed ** (eog:44492): WARNING **: 14:29:17.543: Cannot read plugin directory. (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.543: gdk_pixbuf_animation_is_static_image: assertion 'GDK_IS_PIXBUF_ANIMATION (animation)' failed (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.543: gdk_pixbuf_animation_get_iter: assertion 'GDK_IS_PIXBUF_ANIMATION (animation)' failed (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.543: gdk_pixbuf_animation_iter_get_pixbuf: assertion 'GDK_IS_PIXBUF_ANIMATION_ITER (iter)' failed eog then shows "Could not load image “IMG_9996.HEIC”. Image loading failed." gpicview even crashes immediately: $ gpicview IMG_9996.HEIC Gtk-Message: 14:30:30.216: Failed to load module "canberra-gtk-module" ** (gpicview:44624): WARNING **: 14:30:30.260: Cannot read plugin directory. ** (gpicview:44624): WARNING **: 14:30:30.265: Cannot read plugin directory. Segmentation fault (core dumped) The problem concerns all HEIF/HEIC images I tested. The installed versions of the (possibly) relevant packages are: libheif1: 1.14.2-1 heif-gdk-pixbuf: 1.14.2-1 libgdk-pixbuf-2.0-0: 2.42.10+dfsg-1build1 eog: 44.0-1 gpicview: 0.2.5-3build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/2017420/+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 2017420] Update Released
The verification of the Stable Release Update for libheif 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 eog in Ubuntu. https://bugs.launchpad.net/bugs/2017420 Title: Cannot open HEIF/HEIC images in 23.04/lunar anymore Status in eog package in Ubuntu: Invalid Status in gdk-pixbuf package in Ubuntu: Invalid Status in libheif package in Ubuntu: Fix Released Status in eog source package in Lunar: Invalid Status in gdk-pixbuf source package in Lunar: Invalid Status in libheif source package in Lunar: Fix Released Bug description: * Impact The libheif loader is bailing out due to a missing plugin directory which leads to image viewer as eog not being able to open pictures in that format anymore * Testcase Install libheif1 and heif-gdk-pixbuf and try to open a .heif file in eog * Where problems could occur The package build is using the option to not split the codec in separate plugins but the version of Lunar doesn't handle the missing plugins directory and bails out. The code of the version in mantic has been refactored in a way which fixes this problem. For lunar it's easier to just create the directory. The directory is included in the libheif1 binary but that should not create any conflict, it's a temporary situation for lunar only and even if the soname changed dpkg allows for several deb packages to provide the same directory. -- In previous Ubuntu versions, including 22.10, I was able to open HEIF/HEIC files by installing libheif1 and heif-gdk-pixbuf. This does not work anymore in 23.04. Running eog in a terminal displays: $ eog IMG_9996.HEIC ** (eog:44492): WARNING **: 14:29:17.537: Cannot read plugin directory. (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.537: gdk_pixbuf_animation_is_static_image: assertion 'GDK_IS_PIXBUF_ANIMATION (animation)' failed (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.538: gdk_pixbuf_animation_get_iter: assertion 'GDK_IS_PIXBUF_ANIMATION (animation)' failed (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.538: gdk_pixbuf_animation_iter_get_pixbuf: assertion 'GDK_IS_PIXBUF_ANIMATION_ITER (iter)' failed ** (eog:44492): WARNING **: 14:29:17.543: Cannot read plugin directory. (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.543: gdk_pixbuf_animation_is_static_image: assertion 'GDK_IS_PIXBUF_ANIMATION (animation)' failed (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.543: gdk_pixbuf_animation_get_iter: assertion 'GDK_IS_PIXBUF_ANIMATION (animation)' failed (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.543: gdk_pixbuf_animation_iter_get_pixbuf: assertion 'GDK_IS_PIXBUF_ANIMATION_ITER (iter)' failed eog then shows "Could not load image “IMG_9996.HEIC”. Image loading failed." gpicview even crashes immediately: $ gpicview IMG_9996.HEIC Gtk-Message: 14:30:30.216: Failed to load module "canberra-gtk-module" ** (gpicview:44624): WARNING **: 14:30:30.260: Cannot read plugin directory. ** (gpicview:44624): WARNING **: 14:30:30.265: Cannot read plugin directory. Segmentation fault (core dumped) The problem concerns all HEIF/HEIC images I tested. The installed versions of the (possibly) relevant packages are: libheif1: 1.14.2-1 heif-gdk-pixbuf: 1.14.2-1 libgdk-pixbuf-2.0-0: 2.42.10+dfsg-1build1 eog: 44.0-1 gpicview: 0.2.5-3build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/2017420/+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 2021935] Re: ubuntu desktop (mantic) error on post-install login
I doubt I'll be able to do anything here.. (beyond keep testing) This box had multiple installs, one (sda5) was reused without issue, the other (having ~same done to it) seemed to attract bugs, I see mention of SDA6 above, with later issues on that problematic install reported here - https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/2023000 (by which time it was mantic). If that install still exists; I think I need to clean install & see if issues occur again (after re-install). I'll get to that when I can. FYI: First install (sda5); second (sda6) was install.alongside or auto.resize. I always do Lubuntu first, Xubuntu second, if I've still got energy then it's Ubuntu-MATE & Ubuntu etc.. The details on the report also don't make sense to me... My last download & write of UBUNTU-MATE was on 16-April-2023 whilst still RC... My 23.04 (dc7700 is a testing box) installs were all made prior to release... My re-using those installs (without format) has been with MANTIC so why does it say LUNAR? 23.04? Unless I just booted that install on 31-May to test it prior to re-use for mantic, it asked me to file bugs so I did --- BUT why did my description mention MANTIC INSTALL?? Checking installs is done prior to the install, so maybe I got confused (installs were done ~twice for each of sda5 + sda6) if so incomplete likely applies. Starting again CLEAN on box to me makes sense. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ayatana-indicator-messages in Ubuntu. https://bugs.launchpad.net/bugs/2021935 Title: ubuntu desktop (mantic) error on post-install login Status in ayatana-indicator-messages package in Ubuntu: Incomplete Bug description: Ubuntu Desktop (mantic) install on hp dc7700 as QA-test. Install was a re-use of SDA6 which was Ubuntu-MATE 23.04 with music added to /home/Music, plus audacious, figlet, fortune, aptitude & other apps added earlier today expecting this re-install (no format) to auto-reinstall The install was PERFECT & as expected, but on first login I got an ERROR, PLEASE REPORT which is why this report. I've not detected any issues though. ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: ayatana-indicator-messages 22.9.0-1 Uname: Linux 6.2.0-20-generic x86_64 Architecture: amd64 CurrentDesktop: MATE Date: Wed May 31 15:43:45 2023 ExecutablePath: /usr/libexec/ayatana-indicator-messages/ayatana-indicator-messages-service ExecutableTimestamp: 1664708325 ProcCmdline: /usr/libexec/ayatana-indicator-messages/ayatana-indicator-messages-service ProcCwd: /home/guiverc ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 11 SourcePackage: ayatana-indicator-messages UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ayatana-indicator-messages/+bug/2021935/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1993019] Re: UnboundLocalError: local variable 'version' referenced before assignment
All related bugs https://bugs.launchpad.net/bugs/1988836 and https://bugs.launchpad.net/bugs/1935070 had been verified in Jammy. Can 0.9.6.2~0.22.04.3 be released to jammy-updates? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1993019 Title: UnboundLocalError: local variable 'version' referenced before assignment Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Bionic: Triaged Status in ubuntu-drivers-common source package in Focal: Triaged Status in ubuntu-drivers-common source package in Jammy: Fix Committed Status in ubuntu-drivers-common source package in Kinetic: Fix Released Bug description: [ Impact ] * The introduction of the -open NVIDIA drivers requires a change in the way we detect driver series and flavours. Failing to do so, causes the ubuntu-drivers tool to crash (LP: #1993019), or to prefer the -open drivers over the non-open ones (LP: #1988836). * Furthermore, calling the ubuntu-drivers tool where the alsa-utils package is not installed (mainly on servers), ubuntu-drivers (through the sl-modem plugin) complains, unnecessarily about the missing aplay binary. [ Test Plan ] * Install the new ubuntu-drivers-common from -proposed on a system where the GPU is compatible with the 515 series (or higher). * Run the ubuntu-drivers list command, and make sure that the 515 driver series (or higher) is listed. * Try installing the driver using the following command: sudo ubuntu-drivers install * Check which driver series was installed (you can use the "sudo ubuntu-drivers debug" command), and make sure that the installation does not cause ubuntu-drivers to crash. [ Where problems could occur ] * A problem in the ubuntu-drivers tool can cause it to install a driver which is not recommended for the detected hardware, or even cause the package installation to fail, and prevent users from logging in through the graphics interface. [ Other Info ] * To prevent failures of the test-suite on architectures such as armhf (as seen in Lunar), we are skipping the tests for any architectures other than amd64 and arm64 (which are the only ones actually using ubuntu-drivers). This was already the case with riscv, and we now have an easier way to do so in the debian/rules file. == Changelogs == === Kinetic and Jammy === [ Alberto Milone ] * New upstream release: * UbuntuDrivers/detect.py: - Make sure all -open drivers have a lower priority, regardless of whether the --server parameter is passed in or not. - Update regex in nvidia_desktop_pre_installation_hook. This prevents ubuntu-drivers from crashing when dealing with the -open NVIDIA drivers (LP: #1993019). * tests/test_ubuntu_drivers.py: - Add tests so we make sure to keep preferring non-open NVIDIA modules over the -open ones, at least until the open modules catch up feature wise and performance wise. [ gongzhengyang ] * UbuntuDrivers/detect.py: - Fix local variable 'version' being referenced before assignment when catching ValueError (LP: #1993019). [ Jeff Lane ] * detect-plugins/sl-modem.py: - Add some error trapping when aplay is not installed (on servers). === Jammy only (left over from 1:0.9.6.2~0.22.04.1) === * UbuntuDrivers/detect.py: - Make sure -open drivers have a lower priority (LP: #1988836). == Changelogs == === Kinetic and Jammy === [ Alberto Milone ] * debian/rules: - Limit the tests to the selected architectures (amd64, arm64). This prevents armhf builds from failing. * UbuntuDrivers/detect.py: - Make sure all -open drivers have a lower priority, regardless of whether the --server parameter is passed in or not. - Update regex and unify package name parsing in the following functions by using the new NvidiaPkgNameInfo class: nvidia_desktop_pre_installation_hook, _get_headless_no_dkms_metapackage, nvidia_desktop_pre_installation_hook, get_linux_modules_metapackage, This prevents ubuntu-drivers from crashing when dealing with the -open NVIDIA drivers (LP: #1993019). * tests/test_ubuntu_drivers.py: - Add tests so we make sure to keep preferring non-open NVIDIA modules over the -open ones, at least until the open modules catch up feature wise and performance wise. [ gongzhengyang ] * UbuntuDrivers/detect.py: - Fix local variable 'version' being referenced before assignment when catching ValueError (LP: #1993019). [ Jeff Lane ] * detect-plugins/sl-modem.py: - Add some error trapping when aplay is not installed (on servers). ===
[Desktop-packages] [Bug 2022930] Re: When deleting a file via Nautilus, following files can not be deleted
*** This bug is a duplicate of bug 2022851 ***
https://bugs.launchpad.net/bugs/2022851
and for the syntax, it's documented in the 'apt' manpage
SYNOPSIS
apt [-h] [-o=config_string] [-c=config_file] [-t=target_release]
[-a=architecture] {list | search | show | update |
install pkg [{=pkg_version_number | /target_release}]... |
the '[{=pkg_version_number | /target_release}]' bit
** 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/2022930
Title:
When deleting a file via Nautilus, following files can not be deleted
Status in nautilus package in Ubuntu:
New
Bug description:
1. Try to delete a file via Nautilus (Files). On the bottom right
corner you will see the whole name of the file with the word selected
on it. Press the Delete key on the keyboard and press enter.
2. try to delete a second file on the same folder. It will now show as
"" selected instead of the actual name of the file and it will not
delete anything.
3. You need to refresh nautilus for it to work once again, but it will
only work once, you need to refresh every time you delete a file.
An image on how it looks can be seen here: https://imgur.com/a/U5gumKp
ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: nautilus 1:44.0-1ubuntu2
Uname: Linux 6.2.16-060216-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Jun 5 07:26:13 2023
GsettingsChanges:
b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'small-plus'"
b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true'
b'org.gnome.nautilus.window-state' b'initial-size' b'(1402, 866)'
InstallationDate: Installed on 2023-04-20 (45 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
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
nautilus-share0.7.5-0.3
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2022930/+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 2021935] Re: ubuntu desktop (mantic) error on post-install login
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: ayatana-indicator-messages (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ayatana-indicator-messages in Ubuntu. https://bugs.launchpad.net/bugs/2021935 Title: ubuntu desktop (mantic) error on post-install login Status in ayatana-indicator-messages package in Ubuntu: Incomplete Bug description: Ubuntu Desktop (mantic) install on hp dc7700 as QA-test. Install was a re-use of SDA6 which was Ubuntu-MATE 23.04 with music added to /home/Music, plus audacious, figlet, fortune, aptitude & other apps added earlier today expecting this re-install (no format) to auto-reinstall The install was PERFECT & as expected, but on first login I got an ERROR, PLEASE REPORT which is why this report. I've not detected any issues though. ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: ayatana-indicator-messages 22.9.0-1 Uname: Linux 6.2.0-20-generic x86_64 Architecture: amd64 CurrentDesktop: MATE Date: Wed May 31 15:43:45 2023 ExecutablePath: /usr/libexec/ayatana-indicator-messages/ayatana-indicator-messages-service ExecutableTimestamp: 1664708325 ProcCmdline: /usr/libexec/ayatana-indicator-messages/ayatana-indicator-messages-service ProcCwd: /home/guiverc ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 11 SourcePackage: ayatana-indicator-messages UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ayatana-indicator-messages/+bug/2021935/+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 2022930] Re: When deleting a file via Nautilus, following files can not be deleted
*** This bug is a duplicate of bug 2022851 *** https://bugs.launchpad.net/bugs/2022851 Great, thanks for confirming, I'm marking it as duplicate of bug #2022851 -- 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/2022930 Title: When deleting a file via Nautilus, following files can not be deleted Status in nautilus package in Ubuntu: New Bug description: 1. Try to delete a file via Nautilus (Files). On the bottom right corner you will see the whole name of the file with the word selected on it. Press the Delete key on the keyboard and press enter. 2. try to delete a second file on the same folder. It will now show as "" selected instead of the actual name of the file and it will not delete anything. 3. You need to refresh nautilus for it to work once again, but it will only work once, you need to refresh every time you delete a file. An image on how it looks can be seen here: https://imgur.com/a/U5gumKp ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: nautilus 1:44.0-1ubuntu2 Uname: Linux 6.2.16-060216-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jun 5 07:26:13 2023 GsettingsChanges: b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'small-plus'" b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'initial-size' b'(1402, 866)' InstallationDate: Installed on 2023-04-20 (45 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= 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 nautilus-share0.7.5-0.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2022930/+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 2023375] Re: Feature request - Allow the user to select currencies in Preferences
** Changed in: gnome-calculator (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/2023375 Title: Feature request - Allow the user to select currencies in Preferences Status in gnome-calculator package in Ubuntu: New Bug description: If a user just uses 2-3 currencies, I don't see a reason to give him the whole range of currencies in the drop downs in Financial mode. My suggestion is to let the user select the currencies that he is going to use in the Preferences, and only these currencies will appear in Financial mode drop downs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/2023375/+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 2023491] Re: Deleting files causes folders in the directory to disappear and reappear after a refresh
*** This bug is a duplicate of bug 2022851 *** https://bugs.launchpad.net/bugs/2022851 Thanks, the issue is already reported and there is a gtk update including the fix available, see bug #2022851 ** Changed in: nautilus (Ubuntu) Status: New => Fix Released ** 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/2023491 Title: Deleting files causes folders in the directory to disappear and reappear after a refresh Status in Nautilus: Fix Released Status in nautilus package in Ubuntu: Fix Released Bug description: I'm experiencing some inconsistencies when using Nautilus and deleting files. I've found a bug report upstream that describes the same behavior: https://gitlab.gnome.org/GNOME/nautilus/-/issues/2941 Reproduced here for completeness: Steps to reproduce - Open a directory. - Delete some files, either permanently or move to wastebasket. - Refresh the current view. Current behavior - Folders that were not selected to be deleted disappear. Expected behavior - Only the selected files are deleted and removed from the file view. This bug (which affects me on Ubuntu 23.04) has apparently been fixed in upstream Gtk: https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/5873 Please pull the fixes into Ubuntu 23.04. 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 11 19:06:01 2023 GsettingsChanges: b'org.gnome.nautilus.compression' b'default-compression-format' b"'7z'" b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'small-plus'" b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'initial-size' b'(1607, 1234)' InstallationDate: Installed on 2021-11-12 (575 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: nautilus UpgradeStatus: Upgraded to lunar on 2023-04-12 (60 days ago) 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/nautilus/+bug/2023491/+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 2023363] Re: Mouse input latency in GNOME 44.1 Wayland sessions is one frame higher than it was in 44.0 and earlier
I don't think cursor motion latency is one of the most important things to test, and it's kind of too awkward for most people to test. So I would not recommend making it part of the primary test case but linking to this bug as a record of what can go wrong seems appropriate. -- 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/2023363 Title: Mouse input latency in GNOME 44.1 Wayland sessions is one frame higher than it was in 44.0 and earlier Status in mutter package in Ubuntu: In Progress Status in mutter source package in Lunar: Triaged Status in mutter source package in Mantic: In Progress Bug description: [ Impact ] Mouse input latency in Wayland sessions is slightly higher in 23.10 than 22.04 at the moment. I might be imagining things and it does feel like only one frame higher latency. But experimenting with MUTTER_DEBUG_TRIPLE_BUFFERING seems to confirm my suspicion: BAD: MUTTER_DEBUG_TRIPLE_BUFFERING=auto (the Ubuntu default) BAD: MUTTER_DEBUG_TRIPLE_BUFFERING=always GOOD: MUTTER_DEBUG_TRIPLE_BUFFERING=never [ Test Plan ] 0. Find a machine with an Intel GPU. 1. Add this to /etc/environment: CLUTTER_DEBUG=frame-timings 2. Reboot. 3. Log in to a Wayland session and wait for the desktop to become idle. 4. Also log in via ssh from a remote machine and run: journalctl -f /usr/bin/gnome-shell 5. Over your idle desktop just wiggle the mouse continuously. 6. In your ssh login, verify that the resulting log messages from gnome-shell say "[FRAME_TIMINGS]: Double buffering:" and not "[FRAME_TIMINGS]: Triple buffering:" when only the mouse pointer is moving. [ Where problems could occur ] In the frame rate and latency of the Ubuntu desktop experience. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023363/+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 1990341] Re: [SRU] Support to install nvidia driver by allowing list
I've added the bug reference to the changelog which is required by the
SRU process and uploaded now
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1990341
Title:
[SRU] Support to install nvidia driver by allowing list
Status in OEM Priority Project:
Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
Fix Released
Bug description:
[ Impact ]
* In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to
OEM/ODM for production.
In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA)
to use a specific nvidia version to development/production.
NVIDIA and OEN/ODM will announce the next generation combination at
the same time usually when the factory ready to ship the product.
We made Ubuntu as a leading distribution supports many cutting edge
devices, it's time to have an official way to make the nvidia
installation consistent in unannounced (yet) nvidia devices to support
OEM/ODM factory shipment for our growing counterparts.
[ Test Plan ]
* Steps to make sure it works:
1. pick a cutting edge nvidia graphic.
2. remove nv-525 from the pool.
3. check the nv support status:
```
$ ubuntu-drivers list
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
```
4. modify custom file
```
$ cat /etc/custom_supported_gpus.json
{
"chips": [
{
"devid": "0x24BA",
"name": "TEST 24BA",
"branch": "580.1234",
"features": [
"runtimepm"
]
},
{
"devid": "0x25BC",
"name": "TEST 25BC",
"branch": "510",
"features": [
"runtimepm"
]
}
]
}
```
5. make sure the hook works
```
$ ubuntu-drivers list
nvidia-driver-510, (kernel modules provided by nvidia-dkms-510)
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
[ Where problems could occur ]
* This feature only impact target system has a custom file
"/etc/custom_supported_gpus.json". And it won't generate automatically
which should not impact normal users
[ Other Info ]
* the patches are picked from
-
https://github.com/tseliot/ubuntu-drivers-common/commit/ec675fba22c68932da9fae95e0f4f2fd10732bf3
-
https://github.com/tseliot/ubuntu-drivers-common/commit/4776c6b9f78411ef3b269a28e9546e4ffd2b7115
-
https://github.com/tseliot/ubuntu-drivers-common/commit/83528313da84b55c04daa62b5edcbf823e5c067b.
* Discussion is in https://github.com/tseliot/ubuntu-drivers-common/pull/71
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1990341/+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 2020782] Re: Xdcv: Changing display scale setting and reverting it fails
Try logging into a non-GNOME Xorg session on Workspaces if you can. Then use the 'xrandr' command to set a mode to turn on one of the unused virtual monitors. If that causes the DCV client to go blank then we have proven it's not mutter's fault. -- 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/2020782 Title: Xdcv: Changing display scale setting and reverting it fails Status in mutter package in Ubuntu: In Progress Bug description: In Amazon Workspaces running Ubuntu 22.04, when attempting to change the Scale in the Gnome Display settings, if you click on a different scale (i.e. changing from 100% to 200%) and hitting apply, it will bring up a prompt asking if you want to keep or revert the changes and there will be a timer of 20 seconds. If you try to revert the changes (either by letting the timer expire or by clicking the "revert" button), we will hit one of the following two behaviors: 1 - The setting won't revert and will keep scaled 2 - gnome-shell will show some error messages in syslog and the display will be "corrupted", where the only window you are able to click is the display setting and if you try to drag it, it will leave a "blur" throughout the window (per discussions, this seems to be https://launchpad.net/bugs/1924689) For both situations, changing the display resolution (i.e. going into and out of full screen in the workspaces client) will fix the issue When hitting situation 1, syslog shows: May 17 17:33:10 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x1080 (19.958942) for monitor 'unknown unknown' When hitting situation 2, syslog shows: May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use fallback monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Impossible to set scaling on crtc 59 to 1.00, error id 2 May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Xlib: extension "DPMS" missing on display ":1". May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Object St.Label (0x557090d07de0), has been already disposed — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: == Stack trace for context 0x557090bee180 == May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #0 557093f00e68 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js:1349 (2cdac32b2e20 @ 105) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #1 557093f00dd8 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/dash.js:42 (2cdac32a5d80 @ 27) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #2 557093f00d58 i resource:///org/gnome/shell/ui/dash.js:545 (20c3e0d20970 @ 24) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: JS ERROR: TypeError: monitor is null#012_updateWorkAreaBox@resource:///org/gnome/shell/ui/overviewControls.js:58:26#012_init/<@resource:///org/gnome/shell/ui/overviewControls.js:51:45 Sometimes the stack trace isn't shown, but the symptom is the same: May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use fallback monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Impossible to set scaling on crtc 59 to 1.00, error id 2 May 17 18:31:40 U-1AZMIM8SIPZ6I gnome-shell[3030]: Xlib: extension "DPMS" missing on display ":1". I'm unable to reproduce the problem if I manually install ubuntu-desktop and use the Nice DCV Server (as used by Workspaces) by following the steps from (using the xorg-x11-drv-dummy): https://docs.aws.amazon.com/dcv/latest/adminguide/setting-up- installing-linux.html One relevant difference is that
[Desktop-packages] [Bug 2020782] Re: Xdcv: Changing display scale setting and reverting it fails
> I saw the details you mentioned on comment #16, and I also have fractional > scaling > turned off. By "having it off" I'm assuming this [1] is enough, right? For safety's sake I would recommend having Fractional Scaling disabled before you log in, or logging in again after disabling it. Because it's common in gnome-shell for some settings to only be fully actioned on startup. > i.e. Just want to make clear that I don't have the "mutter" package > installed, but > the ones above. That's fine, Ubuntu does not use "mutter". We only use "libmutter" so it's a common point of confusion. The source package name for both is "mutter". > Isn't it the fractional scaling, that was effectively removed from your > 42.5-0ubuntu1vv5 package? In this case, doesn't the errors showing up means > that > we're still trying to use something that isn't properly implemented in Xdcv? > Just for my own information, what's the difference between the vv5 and vv4 > builds? It's vv4 that has no fractional scaling, and vv5 reintroduced fractional scaling leaving only the "zero Hz" fix in vv5. The 3 unused monitors turning on is a side-effect of the "zero Hz" fix working. I can't tell if it's a bug or a feature right now. If it is a bug then it might be a bug in the Settings app or in mutter. Separately, the fact that the client goes blank on Workspaces but not in a VM might be a bug in Workspaces itself or a bug in the DCV client. Although I want to treat these remaining issues as separate it seems pretty clear that avoiding turning on the unused virtual monitors should solve them all... -- 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/2020782 Title: Xdcv: Changing display scale setting and reverting it fails Status in mutter package in Ubuntu: In Progress Bug description: In Amazon Workspaces running Ubuntu 22.04, when attempting to change the Scale in the Gnome Display settings, if you click on a different scale (i.e. changing from 100% to 200%) and hitting apply, it will bring up a prompt asking if you want to keep or revert the changes and there will be a timer of 20 seconds. If you try to revert the changes (either by letting the timer expire or by clicking the "revert" button), we will hit one of the following two behaviors: 1 - The setting won't revert and will keep scaled 2 - gnome-shell will show some error messages in syslog and the display will be "corrupted", where the only window you are able to click is the display setting and if you try to drag it, it will leave a "blur" throughout the window (per discussions, this seems to be https://launchpad.net/bugs/1924689) For both situations, changing the display resolution (i.e. going into and out of full screen in the workspaces client) will fix the issue When hitting situation 1, syslog shows: May 17 17:33:10 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x1080 (19.958942) for monitor 'unknown unknown' When hitting situation 2, syslog shows: May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use fallback monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Impossible to set scaling on crtc 59 to 1.00, error id 2 May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Xlib: extension "DPMS" missing on display ":1". May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Object St.Label (0x557090d07de0), has been already disposed — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: == Stack trace for context 0x557090bee180 == May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #0 557093f00e68 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js:1349 (2cdac32b2e20 @ 105) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #1 557093f00dd8 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/dash.js:42 (2cdac32a5d80 @ 27) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #2 557093f00d58 i resource:///org/gnome/shell/ui/dash.js:545 (20c3e0d20970 @ 24) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: JS ERROR: TypeError: monitor is
[Desktop-packages] [Bug 2022851] Re: Nautilus displays invalid directory content after deleting
I confirm that CTRL-Click is indeed broken in list view, but works in grid view. -- 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 Committed 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
Re: [Desktop-packages] [Bug 2023365] Re: Window movement is delayed in screen share in Wayland
I tried it again and could no longer reproduce it, so maybe it was. -- 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/2023365 Title: Window movement is delayed in screen share in Wayland Status in mutter package in Ubuntu: Incomplete Bug description: In Wayland, - Open Chromium or Firefox - Go to https://mozilla.github.io/webrtc-landing/gum_test.html - Start full screen capture - Drag some windows around Expected: The movement of each window is reproduced in the screen cast smoothly and immediately. Observed: It takes a couple of seconds until each moved window's position is verified in the screen cast. The issue does not appear in Xorg. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: mutter 44.1-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-21.21-generic 6.2.6 Uname: Linux 6.2.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 Date: Fri Jun 9 09:11:35 2023 InstallationDate: Installed on 2022-05-16 (388 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: mutter UpgradeStatus: Upgraded to mantic on 2023-01-17 (142 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023365/+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 2023400] Re: Upon clicking Thunderbird e-mail notifications, the e-mail doesn't open until clicking on a second notification
Launchpad has imported 6 comments from the remote bug at https://bugzilla.mozilla.org/show_bug.cgi?id=1745714. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2021-12-13T10:55:52+00:00 Célian Godefroid wrote: User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:95.0) Gecko/20100101 Firefox/95.0 Steps to reproduce: Received an e-mail, saw the notification, clicked it to open the e-mail. Actual results: The window did not switch to Thunderbird, it only selected the e-mail within the Thunderbird window. I then had to manually switch to Thunderbird to read the e-mail. Expected results: The window should have switched to Thunderbird, with a focus on the e-mail I received and for which I clicked the notification. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/2023400/comments/0 On 2021-12-13T11:26:03+00:00 Andre Klapper wrote: If Ubuntu's notifications are broken, have you reported this to Ubuntu? Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/2023400/comments/1 On 2021-12-13T11:27:16+00:00 Célian Godefroid wrote: (In reply to Andre Klapper from comment #1) > If Ubuntu's notifications are broken, have you reported this to Ubuntu? Pretty sure some other notifications do work. I'm about to report it to Ubuntu aswell. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/2023400/comments/2 On 2022-02-07T19:28:50+00:00 Andre Klapper wrote: Please provide a link yo your Ubuntu ticket. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/2023400/comments/3 On 2023-06-09T14:35:07+00:00 Célian Godefroid wrote: It's been a while. https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2023400 Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/2023400/comments/6 On 2023-06-09T17:12:58+00:00 Andre Klapper wrote: *** Bug 1837628 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/2023400/comments/7 -- 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/2023400 Title: Upon clicking Thunderbird e-mail notifications, the e-mail doesn't open until clicking on a second notification Status in Mozilla Thunderbird: Unknown Status in gnome-shell package in Ubuntu: New Status in thunderbird package in Ubuntu: New Bug description: When I receive an e-mail, a notification appears. I click it in order for Thunderbird to open on the correct e-mail. But Thunderbird doesn't open right away, a new notification "'Thunderbird' is ready" appears, which I have to click in order for Thunderbird to open correctly. Related : https://bugzilla.mozilla.org/show_bug.cgi?id=1745714 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 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 non accordée: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 9 16:31:36 2023 DistUpgraded: 2023-04-21 10:53:49,032 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell CometLake-H GT2 [UHD Graphics] [1028:098f] Subsystem: Dell TU117M [GeForce GTX 1650 Ti Mobile] [1028:098f] InstallationDate: Installed on 2021-04-12 (787 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. XPS 17 9700 ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-04-21 (49 days ago) dmi.bios.date: 03/14/2023 dmi.bios.release: 1.24 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.24.0 dmi.board.name: 0PV91W dmi.board.vendor: Dell Inc.
[Desktop-packages] [Bug 2023463] Re: Cannot remove items from side panel
Thanks for the bug report. Please provide a screenshot, photo or video so we can understand better what you are describing. Please also note that Ubuntu 22.10 reaches end of life in a couple of weeks so please upgrade when you can: https://ubuntu.com/download/desktop https://wiki.ubuntu.com/Releases ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/2023463 Title: Cannot remove items from side panel Status in Ubuntu: Incomplete Bug description: Only an annoying bug I cannot remove the attached from my menu on the side panel. Other items are removed ok. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-43.44-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.23.1-0ubuntu3.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 11 14:22:20 2023 DistUpgraded: 2023-05-30 14:55:36,989 DEBUG /openCache(), new cache size 74014 DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Skylake GT2 [HD Graphics 520] [1025:100c] InstallationDate: Installed on 2023-02-08 (123 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Acer Aspire F5-572 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic root=UUID=d5663606-7967-4f64-9bf3-a8843f95c2b6 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2023-05-30 (11 days ago) dmi.bios.date: 05/25/2017 dmi.bios.release: 0.0 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.18 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Zoro_SL dmi.board.vendor: Acer dmi.board.version: V1.18 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 2.70 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.18:bd05/25/2017:br0.0:efr2.70:svnAcer:pnAspireF5-572:pvrV1.18:rvnAcer:rnZoro_SL:rvrV1.18:cvnChassisManufacturer:ct10:cvrChassisVersion:skuAspireF5-572_100C_1.18: dmi.product.family: SKL dmi.product.name: Aspire F5-572 dmi.product.sku: Aspire F5-572_100C_1.18 dmi.product.version: V1.18 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.5-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2023463/+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 2023436] Re: Icons are showing as no entry signs
Thanks for the bug report. Please try running 'gnome-control-center' in a Terminal window. When the bug occurs again, please tell us what text if any has been logged to the Terminal window. ** Package changed: xorg (Ubuntu) => gtk+3.0 (Ubuntu) ** Changed in: gtk+3.0 (Ubuntu) Status: New => Incomplete -- 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/2023436 Title: Icons are showing as no entry signs Status in gtk+3.0 package in Ubuntu: Incomplete Bug description: I have tried looking in various places to see why icons aren't showing properly. Checked loads of log messages. Located the icons on the filesystem but for some reason the icons aren't loading. It is intermittent, for example sometimes the battery symbol shows and sometimes it doesn't. A bigger problem is that sometimes the screen goes black but the laptop is still on, the keyboard is still responding but it's impossible to use. Sometimes this happens a few times in an hour. Sometimes it can be days between using it. This is making my laptop pretty unusable. If there is anything I can do to investigate this further then please shout, happy to run all the commands and provide all the logs. I've attached a screenshot showing the issue in the settings panel but that isn't the only place this is happening. 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] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jun 10 10:17:48 2023 DistUpgraded: 2022-10-02 12:38:39,285 DEBUG icon theme changed, re-reading DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell CometLake-H GT2 [UHD Graphics] [1028:097d] Subsystem: Dell TU117M [GeForce GTX 1650 Ti Mobile] [1028:097d] InstallationDate: Installed on 2020-07-31 (1043 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. XPS 15 9500 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic root=UUID=7a62b7f7-b519-470b-bcb8-48e870873cc4 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-10-02 (250 days ago) dmi.bios.date: 03/16/2023 dmi.bios.release: 1.22 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.22.0 dmi.board.name: 05XYW7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.22.0:bd03/16/2023:br1.22:svnDellInc.:pnXPS159500:pvr:rvnDellInc.:rn05XYW7:rvrA00:cvnDellInc.:ct10:cvr:sku097D: dmi.product.family: XPS dmi.product.name: XPS 15 9500 dmi.product.sku: 097D dmi.sys.vendor: Dell Inc. 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.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2023436/+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 2023401] Re: Upon shutdown, shutdown process doesn't complete and the computer stays on
Thanks for the bug report. Please reproduce the bug again, wait a while and power off the machine. Then turn it on again and run: journalctl -b-1 > prevboot.txt and attach the resulting text file here. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/2023401 Title: Upon shutdown, shutdown process doesn't complete and the computer stays on Status in Ubuntu: Incomplete Bug description: When I want to shutdown my computer, very often since last Ubuntu version, the process seems not to go to the end, and the computer never shuts down. I used not to notice it, physically close my laptop and put it back in my bag, then hours later find it very hot and with fans going at full speed. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 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 non accordée: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 9 16:35:50 2023 DistUpgraded: 2023-04-21 10:53:49,032 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell CometLake-H GT2 [UHD Graphics] [1028:098f] Subsystem: Dell TU117M [GeForce GTX 1650 Ti Mobile] [1028:098f] InstallationDate: Installed on 2021-04-12 (787 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. XPS 17 9700 ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to lunar on 2023-04-21 (49 days ago) dmi.bios.date: 03/14/2023 dmi.bios.release: 1.24 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.24.0 dmi.board.name: 0PV91W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.24.0:bd03/14/2023:br1.24:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn0PV91W:rvrA00:cvnDellInc.:ct10:cvr:sku098F: dmi.product.family: XPS dmi.product.name: XPS 17 9700 dmi.product.sku: 098F 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 N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2023401/+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 2023403] Re: Dell XPS-17 trackpad stutters frequently
Thanks for the bug report. Please open a Terminal window and run 'top'. Now wait for the bug to occur again. Does 'top' show any process using high CPU when the stutter is happening? ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/2023403 Title: Dell XPS-17 trackpad stutters frequently Status in Ubuntu: Incomplete Bug description: Randomly, my trackpad has a lot of trouble detecting movement, for 10 to 20 seconds, until it comes back. Used to happen every day in previous versions, now every 3 days or so. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 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 non accordée: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 9 16:43:21 2023 DistUpgraded: 2023-04-21 10:53:49,032 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell CometLake-H GT2 [UHD Graphics] [1028:098f] Subsystem: Dell TU117M [GeForce GTX 1650 Ti Mobile] [1028:098f] InstallationDate: Installed on 2021-04-12 (787 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. XPS 17 9700 ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-04-21 (49 days ago) dmi.bios.date: 03/14/2023 dmi.bios.release: 1.24 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.24.0 dmi.board.name: 0PV91W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.24.0:bd03/14/2023:br1.24:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn0PV91W:rvrA00:cvnDellInc.:ct10:cvr:sku098F: dmi.product.family: XPS dmi.product.name: XPS 17 9700 dmi.product.sku: 098F 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 N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2023403/+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 2023400] Re: Upon clicking Thunderbird e-mail notifications, the e-mail doesn't open until clicking on a second notification
** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Bug watch added: Mozilla Bugzilla #1745714 https://bugzilla.mozilla.org/show_bug.cgi?id=1745714 ** Also affects: thunderbird via https://bugzilla.mozilla.org/show_bug.cgi?id=1745714 Importance: Unknown Status: Unknown ** Also affects: thunderbird (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2023400 Title: Upon clicking Thunderbird e-mail notifications, the e-mail doesn't open until clicking on a second notification Status in Mozilla Thunderbird: Unknown Status in gnome-shell package in Ubuntu: New Status in thunderbird package in Ubuntu: New Bug description: When I receive an e-mail, a notification appears. I click it in order for Thunderbird to open on the correct e-mail. But Thunderbird doesn't open right away, a new notification "'Thunderbird' is ready" appears, which I have to click in order for Thunderbird to open correctly. Related : https://bugzilla.mozilla.org/show_bug.cgi?id=1745714 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 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 non accordée: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 9 16:31:36 2023 DistUpgraded: 2023-04-21 10:53:49,032 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell CometLake-H GT2 [UHD Graphics] [1028:098f] Subsystem: Dell TU117M [GeForce GTX 1650 Ti Mobile] [1028:098f] InstallationDate: Installed on 2021-04-12 (787 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. XPS 17 9700 ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-04-21 (49 days ago) dmi.bios.date: 03/14/2023 dmi.bios.release: 1.24 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.24.0 dmi.board.name: 0PV91W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.24.0:bd03/14/2023:br1.24:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn0PV91W:rvrA00:cvnDellInc.:ct10:cvr:sku098F: dmi.product.family: XPS dmi.product.name: XPS 17 9700 dmi.product.sku: 098F 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 N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/2023400/+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 2023365] Re: Window movement is delayed in screen share in Wayland
I can't seem to reproduce the issue to any significant degree. There's a tiny delay for me, but also high CPU usage in the browser mostly. Is your CPU usage unreasonably high when it happens? ** Changed in: mutter (Ubuntu) Status: New => Incomplete ** Tags added: performance -- 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/2023365 Title: Window movement is delayed in screen share in Wayland Status in mutter package in Ubuntu: Incomplete Bug description: In Wayland, - Open Chromium or Firefox - Go to https://mozilla.github.io/webrtc-landing/gum_test.html - Start full screen capture - Drag some windows around Expected: The movement of each window is reproduced in the screen cast smoothly and immediately. Observed: It takes a couple of seconds until each moved window's position is verified in the screen cast. The issue does not appear in Xorg. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: mutter 44.1-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-21.21-generic 6.2.6 Uname: Linux 6.2.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 Date: Fri Jun 9 09:11:35 2023 InstallationDate: Installed on 2022-05-16 (388 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: mutter UpgradeStatus: Upgraded to mantic on 2023-01-17 (142 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023365/+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 2023473] Re: arrows and rotate icons do not autohide when making a screenshot
The problem doesn't seem to happen if you move the mouse cursor out of the window first, and wait for the arrows to fade out. Then press PrtScn. So this sounds like correct behaviour to me -- it's taking a screenshot of how the app was at the time. ** Changed in: eog (Ubuntu) Status: New => Opinion ** Changed in: gnome-shell (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/2023473 Title: arrows and rotate icons do not autohide when making a screenshot Status in eog package in Ubuntu: Opinion Status in gnome-shell package in Ubuntu: Opinion Bug description: Ubuntu 22.04 LTS on 11/6/2023 When trying to make a screenshot with gnome's baked in screenshot tool on a picture opened with EOG, the left/right arrows and rotate icons do not autohide from the picture as long as the screenshot greyed out preview tool is active, wich results to a screenshot with the arrows in the picture (see screenshot) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: eog 42.0-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: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Jun 11 11:38:17 2023 SourcePackage: eog UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/2023473/+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 2012931] Re: No way to permanently disable Check Spelling
This bug is invalid, I was using the context menu instead the view options and I was misled by the fact the option 'Check spelling' is present twice with different behaviors. ** Changed in: gnome-text-editor (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-text-editor in Ubuntu. https://bugs.launchpad.net/bugs/2012931 Title: No way to permanently disable Check Spelling Status in gnome-text-editor package in Ubuntu: Invalid Bug description: Editing a document i see many words underlined by red dots. Red dots disappear if I disable check spelling but after saving the documents next time red dots reappear. I find no way to permanently disable Check Spelling. see screenshot ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-text-editor 44~rc-1 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 27 15:04:20 2023 InstallationDate: Installed on 2023-02-25 (30 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230224) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-text-editor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-text-editor/+bug/2012931/+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 2022941] Re: Zoom window not centered on text cursor
Sounds like https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5557 ? ** Tags added: a11y zoom ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #5557 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5557 ** Package changed: mutter (Ubuntu) => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2022941 Title: Zoom window not centered on text cursor Status in gnome-shell package in Ubuntu: New Bug description: In certain applications, the zoomed in window moves to center on the text cursor instead of the pointer when typing but it does not focuses properly. This causes the typed text to be completely out of view. I use the default full-screen zoom in Ubuntu under the accessibility settings with the following settings: Magnification: 4.00 - 6.00 Magnifier position: Follow mouse cursor The problem primarily occurs when using Alt+Tab to witch tabs, but it sometimes appears when switching normally. To reproduce the problem, the following steps can be followed: - Activate the zoom function. - Start up Files and rename a file. - The zoomed in window will move to the upper left corner. Other applications in which the problem sometimes occurs (mostly when using Alt+Tab): Firefox, VSCode I also want to note that for other applications like Text Editor or Terminal, the cursor is always followed correctly. lsb_release -rd: Description: Ubuntu 22.04.2 LTS Release: 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2022941/+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 2018731] Re: Graphics memory (VRAM) leak in mutter-x11-frames
Great, thanks. It does sound like the change in 44.1 upstream mentioned was the fix. ** Changed in: mutter (Ubuntu) Status: Confirmed => Fix Released ** Tags added: fixed-in-mutter-44.1 fixed-upstream -- 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/2018731 Title: Graphics memory (VRAM) leak in mutter-x11-frames Status in Mutter: New Status in mutter package in Ubuntu: Fix Released Bug description: I'm seeing degraded performance with NVIDIA Geforce 3008 Mobile and two screens. After launching nvidia-smi, I can clearly see that there's a memory leak in mutter-x11-frames, which uses around 10-12 GB of VRAM. nvidia-drivers-525 Ubuntu 23.04 X11 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-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 525.105.17 Tue Mar 28 18:02:59 UTC 2023 GCC version: gcc version 12.2.0 (Ubuntu 12.2.0-17ubuntu1) ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 8 14:28:13 2023 DistUpgraded: 2023-04-20 10:00:59,509 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu DkmsStatus: nvidia/525.105.17, 6.2.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] [10de:24dc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] [17aa:3a58] InstallationDate: Installed on 2023-02-09 (87 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: LENOVO 82N6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=2a43fd27-b65c-4d7a-bc19-b001521b0771 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-04-20 (18 days ago) dmi.bios.date: 03/07/2023 dmi.bios.release: 1.60 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN60WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76461 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.60 dmi.modalias: dmi:bvnLENOVO:bvrGKCN60WW:bd03/07/2023:br1.60:efr1.60:svnLENOVO:pn82N6:pvrLegion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO 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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2018731/+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 1924689] Re: Window border corruption after changing display scale between 100% and 200% in Xorg
Yes sometimes we need to oversimplify bug descriptions to ensure people can find and understand them. I believe this is a general problem with the underlying X Window and Mutter actor getting out of sync, where one is still rendering (and interpreting input) at the old scale and the other expecting to render at the new scale. -- 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/1924689 Title: Window border corruption after changing display scale between 100% and 200% in Xorg Status in Mutter: New Status in OEM Priority Project: New Status in mutter package in Ubuntu: Triaged Bug description: Ubuntu release: Ubuntu 20.04.2 LTS Issue description: When the gnome-initial-setup launched, if user changes the scale 200 -> 400 or 100 -> 200. There is some garbage on the edge of the window. The issue is not seen if we login in wayland session. A video is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1924689/+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 1991022] Re: [SRU] Service activation via Systemd socket
Hi, what exactly does restarting the session mean? I could verify whether that would work. Otherwise the behavior I observed is consistent with https://source.puri.sm/kop316/mmsd/-/issues/3. ** Bug watch added: source.puri.sm/kop316/mmsd/-/issues #3 https://source.puri.sm/kop316/mmsd/-/issues/3 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to speech-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1991022 Title: [SRU] Service activation via Systemd socket Status in speech-dispatcher package in Ubuntu: Fix Released Status in speech-dispatcher source package in Jammy: Incomplete Status in speech-dispatcher source package in Kinetic: Incomplete Status in speech-dispatcher source package in Lunar: Incomplete Bug description: [Description] Systemd socket activation for Speech Dispatcher. - Creates the speech-dispatcher.socket; - Modifies the server so that it can detect it was automatically launched by that socket activation; and - Modifies the Autotools files accordingly. [Impact] Its relevance is described in [1], of which I quote the essential parts [my notes in brackets]: > Sandboxed applications [snaps] that use Speech Dispatcher currently bundle it inside of the sandbox, so that each application has its own "private" instance of Speech Dispatcher running. This works more or less, but it has the downside that speech dispatcher cannot coordinate simultaneous messages from multiple apps. When multiple sandboxed apps use Speech Dispatcher at the same time, the text reading overlaps. > > In order to solve this issue, I would really like to give sandboxed apps access to the Speech Dispatcher instance of the host. That can be done by implementing the action of the speech dispatcher service via a Systemd socket: > The only issue I see is having it auto launch. I think it would probably be a good step forward for speech-dispatcher to be auto launched by a systemd socket like other daemons already do on demand. That way the host speech-dispatcher with it's configuration would be used by all snaps, [Additional information] The changes are already merged upstream[21][22][23], but still not released. I have built and installed the package in Mantic and verified that running spd-say from inside a snap causes the host's dispatcher to spawn and emit sound — see 'Test case' for more details. This has also been verified in Jammy by Lissyx[31][32] and there is a merge proposal[4] for the Firefox snap that assumes the incorporation of this delta in speech-dispatcher. Note: Either the installed socket needs to be started manually to function correctly or the system needs to be rebooted. [Test case] Install the proposed speech-dispatcher and the snap[5] containing spd- say. Then, systemctl start --user speech-dispatcher.socket snap run --shell geheim $ XDG_RUNTIME_DIR=/run/user/1000 spd-say hi should say "hi" through your loudspeakers. If you have no loudspeakers or if you are testing in a virtual machine, you can use Pavucontrol to verify that the dummy output device meter shows activity right after you issue the last command. [Regression potential] If the socket communication were not working (e.g. connection refused), then this would result in text-to-speech failing, even for a not sandboxed program. Do note, however, that if the socket were not available for whatever reason (e.g. the user didn't start it manually nor rebooted), then the sd_listen_fds(0) >= 1 test would be false and no regression would be observed, as then the program would fallback to its usual operation. [1] https://github.com/brailcom/speechd/issues/335 [21] https://github.com/brailcom/speechd/pull/763 [22] https://github.com/brailcom/speechd/pull/776 [23] https://github.com/brailcom/speechd/pull/817 [31] https://irclogs.ubuntu.com/2023/05/17/%23ubuntu-desktop.html [32] https://bugzilla.mozilla.org/show_bug.cgi?id=1729750#c23 [4] https://github.com/canonical/firefox-snap/pull/12 [5] https://launchpad.net/~nteodosio/+snap/test-speechd/+build/2103550 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1991022/+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
