[Desktop-packages] [Bug 2000275] Re: evince neither prints nor previews postscript documents
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: evince (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/2000275 Title: evince neither prints nor previews postscript documents Status in evince package in Ubuntu: Confirmed Bug description: evince does successfully display a ps document, but when attempting to print or preview (whether to a file or printer) fails, with either a blank page (for print) or blank window (for preview) produced, and some error output at the terminal. Any ps document (text or graphical) has this failure. A PDF document succeeds in the print preview, but with the same warning (see below examples) so the warning may not be important. qpdfview does successfully print the ps file, so not a hardware issue. User logged in using xorg. $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.04.1 LTS Release:22.04 Codename: jammy $ evince --version GNOME Document Viewer 42.3 $ ghostscript --version 9.55.0 Screen display works for ps files, but a warning and error are produced when attempting to print or preview a postscript file (see below). The same warning is produced for print/preview of a pdf file, but the preview succeeds. A comment was added to launchpad bug 1978838 which had this same warning when launching evince. evince does not crash, the display of the file is not affected when the print/preview fails. ===ps preview/print fails when preview button is pushed === $ evince ./parallel/mpi/mpich-1.2.0/doc/install.ps GPL Ghostscript 9.55.0: Unrecoverable error, exit code 1 (libspectre) ghostscript reports: fatal internal error -100 (evince-previewer:3039): dbind-WARNING **: 14:04:36.390: Couldn't connect to accessibility bus: Failed to connect to socket /run/user/1000/at-spi/bus_1: Permission denied === PDF preview succeeded even with the warning === $ evince ./patches/bdp1600/Upgrade_Guide_USB.pdf (evince-previewer:5688): dbind-WARNING **: 14:46:13.409: Couldn't connect to accessibility bus: Failed to connect to socket /run/user/1000/at-spi/bus_1: Permission denied ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 42.3-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Dec 21 15:12:58 2022 InstallationDate: Installed on 2022-06-10 (194 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/2000275/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2023939] Re: Items in the sidebar are not activated by the keyboard when has selected files
The attachment "848.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2023939 Title: Items in the sidebar are not activated by the keyboard when has selected files Status in nautilus package in Ubuntu: New Bug description: The selected items in the sidebar are not activated by the keyboard when there are selected files. Steps to reproduce the bug: 1) Open a directory that contains files; 2) Select a file; 2) Press F6 to change the focus to the sidebar; 3) Use arrows up or down to select an item in the sidebar; 4) Press Enter to activate the item in the sidebar. Unexpected behavior: - The selected file is opened. Expected behavior: - The selected item in the sidebar should open. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.6-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 14 21:04:52 2023 GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" b'org.gnome.nautilus.window-state' b'initial-size' b'(989, 679)' b'org.gnome.nautilus.window-state' b'sidebar-width' b'255' InstallationDate: Installed on 2023-06-03 (11 days ago) InstallationMedia: Ubuntu 22.04.2 2023.06.03 LTS (20230603) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-06-03T14:17:19 usr_lib_nautilus: evince42.3-0ubuntu3 file-roller 3.42.0-1 nautilus-extension-brasero3.12.3-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2023939/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1968792] Re: After F10 menu Enter key opens file instead of menu action
The attachment "848.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1968792 Title: After F10 menu Enter key opens file instead of menu action Status in nautilus package in Ubuntu: Triaged Bug description: When pressing F10 on Nautilus, the menu pops. Then the arrow keys navigate the menu, but when pressing Enter, does not execute the selected menu action. IE: if folder is selected, press F10, menu pops down arrow to choose "open in terminal", press enter, Nautilus navigates to the selected folder instead of opening terminal in the current location. Also with files: if text (or any) file is selected, press F10, menu pops, choose any action with arrows, press enter, gedit (or whatever) opens selected file. Tested all actions then selecting files or folders, same result. Expected behavior: After pressing F10, focus should be on the menu that just pops up, until ESC is pressed or mouse clicks somewhere else or focus is shifted by other means, so when pressing ENTER action gets performed. IE: file or folder is selected, press F10, down arrow to select PROPERTIES, press ENTER, PROPERTIES of selected item are shown. Also tried with SPACEBAR (just in case), but the result is the same. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckMismatches: ./preseed/ubuntu.seed ./pool/restricted/n/nvidia-graphics-drivers-470/nvidia-kernel-source-470_470.103.01-0ubuntu2_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/libnvidia-gl-510_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-compute-utils-510_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-driver-495_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-driver-510_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-kernel-common-510_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-kernel-source-510_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-utils-510_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/xserver-xorg-video-nvidia-510_510.60.02-0ubuntu1_amd64.deb CasperMD5CheckResult: fail CasperVersion: 1.468 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 12 23:08:24 2022 ExecutablePath: /usr/bin/nautilus GsettingsChanges: LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince42.1-2 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1968792/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990341] Re: [SRU] Support to install nvidia driver by allowing list
** Description changed:
[ 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.
+ 2. remove nv-525 from the pool by removing restricted in jammy-updates and
jammy-security
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
+ * 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
--
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 by removing restricted in jammy-updates and
jammy-security
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 featur
[Desktop-packages] [Bug 1899803] Re: Some comments on annotations are not visible
** Changed in: evince Status: Unknown => New -- 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/1899803 Title: Some comments on annotations are not visible Status in Evince: New Status in evince package in Ubuntu: Triaged Bug description: It is not possible to see some text/comment on annotations in a PDF file. This bug was tracking on: https://gitlab.gnome.org/GNOME/evince/-/issues/1347 I've replicated this bug here to document and add more people to help solve the problem. I've also tested using: - Ubuntu 20.04 with Evince 3.36.7 - Ubuntu 20.10 with Evince 3.38.0 To reproduce this bug, see the post: https://gitlab.gnome.org/GNOME/evince/-/issues/1347#note_745797 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evince 3.36.7-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 14 11:29:28 2020 InstallationDate: Installed on 2020-10-05 (9 days ago) InstallationMedia: Ubuntu 20.04.1 2020.09.19 LTS "Custom Focal Fossa" (20200920) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-09-19T23:53:28 To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1899803/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1968792] Re: After F10 menu Enter key opens file instead of menu action
This is the patch of the bug. From: https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/848/diffs#3c33043d4592495dd13d048ae9c8eee31a60fd08 ** Patch added: "848.patch" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1968792/+attachment/5679802/+files/848.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1968792 Title: After F10 menu Enter key opens file instead of menu action Status in nautilus package in Ubuntu: Triaged Bug description: When pressing F10 on Nautilus, the menu pops. Then the arrow keys navigate the menu, but when pressing Enter, does not execute the selected menu action. IE: if folder is selected, press F10, menu pops down arrow to choose "open in terminal", press enter, Nautilus navigates to the selected folder instead of opening terminal in the current location. Also with files: if text (or any) file is selected, press F10, menu pops, choose any action with arrows, press enter, gedit (or whatever) opens selected file. Tested all actions then selecting files or folders, same result. Expected behavior: After pressing F10, focus should be on the menu that just pops up, until ESC is pressed or mouse clicks somewhere else or focus is shifted by other means, so when pressing ENTER action gets performed. IE: file or folder is selected, press F10, down arrow to select PROPERTIES, press ENTER, PROPERTIES of selected item are shown. Also tried with SPACEBAR (just in case), but the result is the same. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckMismatches: ./preseed/ubuntu.seed ./pool/restricted/n/nvidia-graphics-drivers-470/nvidia-kernel-source-470_470.103.01-0ubuntu2_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/libnvidia-gl-510_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-compute-utils-510_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-driver-495_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-driver-510_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-kernel-common-510_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-kernel-source-510_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-utils-510_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/xserver-xorg-video-nvidia-510_510.60.02-0ubuntu1_amd64.deb CasperMD5CheckResult: fail CasperVersion: 1.468 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 12 23:08:24 2022 ExecutablePath: /usr/bin/nautilus GsettingsChanges: LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince42.1-2 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1968792/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2023939] Re: Items in the sidebar are not activated by the keyboard when has selected files
Possible patch for this bug. From: https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/848/diffs#3c33043d4592495dd13d048ae9c8eee31a60fd08 ** Patch added: "848.patch" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2023939/+attachment/5679803/+files/848.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2023939 Title: Items in the sidebar are not activated by the keyboard when has selected files Status in nautilus package in Ubuntu: New Bug description: The selected items in the sidebar are not activated by the keyboard when there are selected files. Steps to reproduce the bug: 1) Open a directory that contains files; 2) Select a file; 2) Press F6 to change the focus to the sidebar; 3) Use arrows up or down to select an item in the sidebar; 4) Press Enter to activate the item in the sidebar. Unexpected behavior: - The selected file is opened. Expected behavior: - The selected item in the sidebar should open. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.6-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 14 21:04:52 2023 GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" b'org.gnome.nautilus.window-state' b'initial-size' b'(989, 679)' b'org.gnome.nautilus.window-state' b'sidebar-width' b'255' InstallationDate: Installed on 2023-06-03 (11 days ago) InstallationMedia: Ubuntu 22.04.2 2023.06.03 LTS (20230603) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-06-03T14:17:19 usr_lib_nautilus: evince42.3-0ubuntu3 file-roller 3.42.0-1 nautilus-extension-brasero3.12.3-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2023939/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2023939] Re: Items in the sidebar are not activated by the keyboard when has selected files
I've reported the bug in the upstream: https://gitlab.gnome.org/GNOME/nautilus/-/issues/3005 ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #3005 https://gitlab.gnome.org/GNOME/nautilus/-/issues/3005 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2023939 Title: Items in the sidebar are not activated by the keyboard when has selected files Status in nautilus package in Ubuntu: New Bug description: The selected items in the sidebar are not activated by the keyboard when there are selected files. Steps to reproduce the bug: 1) Open a directory that contains files; 2) Select a file; 2) Press F6 to change the focus to the sidebar; 3) Use arrows up or down to select an item in the sidebar; 4) Press Enter to activate the item in the sidebar. Unexpected behavior: - The selected file is opened. Expected behavior: - The selected item in the sidebar should open. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.6-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 14 21:04:52 2023 GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" b'org.gnome.nautilus.window-state' b'initial-size' b'(989, 679)' b'org.gnome.nautilus.window-state' b'sidebar-width' b'255' InstallationDate: Installed on 2023-06-03 (11 days ago) InstallationMedia: Ubuntu 22.04.2 2023.06.03 LTS (20230603) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-06-03T14:17:19 usr_lib_nautilus: evince42.3-0ubuntu3 file-roller 3.42.0-1 nautilus-extension-brasero3.12.3-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2023939/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1968792] Re: After F10 menu Enter key opens file instead of menu action
This bug is similar to the bug (but not duplicated): https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2023939 "When has selected files, the selected menus don't activate by the keyboard..." -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1968792 Title: After F10 menu Enter key opens file instead of menu action Status in nautilus package in Ubuntu: Triaged Bug description: When pressing F10 on Nautilus, the menu pops. Then the arrow keys navigate the menu, but when pressing Enter, does not execute the selected menu action. IE: if folder is selected, press F10, menu pops down arrow to choose "open in terminal", press enter, Nautilus navigates to the selected folder instead of opening terminal in the current location. Also with files: if text (or any) file is selected, press F10, menu pops, choose any action with arrows, press enter, gedit (or whatever) opens selected file. Tested all actions then selecting files or folders, same result. Expected behavior: After pressing F10, focus should be on the menu that just pops up, until ESC is pressed or mouse clicks somewhere else or focus is shifted by other means, so when pressing ENTER action gets performed. IE: file or folder is selected, press F10, down arrow to select PROPERTIES, press ENTER, PROPERTIES of selected item are shown. Also tried with SPACEBAR (just in case), but the result is the same. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckMismatches: ./preseed/ubuntu.seed ./pool/restricted/n/nvidia-graphics-drivers-470/nvidia-kernel-source-470_470.103.01-0ubuntu2_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/libnvidia-gl-510_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-compute-utils-510_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-driver-495_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-driver-510_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-kernel-common-510_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-kernel-source-510_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-utils-510_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/xserver-xorg-video-nvidia-510_510.60.02-0ubuntu1_amd64.deb CasperMD5CheckResult: fail CasperVersion: 1.468 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 12 23:08:24 2022 ExecutablePath: /usr/bin/nautilus GsettingsChanges: LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince42.1-2 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1968792/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2023939] Re: Items in the sidebar are not activated by the keyboard when has selected files
This bug is similar to the bug (but not duplicated): https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1968792 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2023939 Title: Items in the sidebar are not activated by the keyboard when has selected files Status in nautilus package in Ubuntu: New Bug description: The selected items in the sidebar are not activated by the keyboard when there are selected files. Steps to reproduce the bug: 1) Open a directory that contains files; 2) Select a file; 2) Press F6 to change the focus to the sidebar; 3) Use arrows up or down to select an item in the sidebar; 4) Press Enter to activate the item in the sidebar. Unexpected behavior: - The selected file is opened. Expected behavior: - The selected item in the sidebar should open. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.6-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 14 21:04:52 2023 GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" b'org.gnome.nautilus.window-state' b'initial-size' b'(989, 679)' b'org.gnome.nautilus.window-state' b'sidebar-width' b'255' InstallationDate: Installed on 2023-06-03 (11 days ago) InstallationMedia: Ubuntu 22.04.2 2023.06.03 LTS (20230603) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-06-03T14:17:19 usr_lib_nautilus: evince42.3-0ubuntu3 file-roller 3.42.0-1 nautilus-extension-brasero3.12.3-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2023939/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 179531] Re: [Upstream] [hardy] Chart lines moved importing Excel xls
** Changed in: df-libreoffice Importance: Medium => Wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/179531 Title: [Upstream] [hardy] Chart lines moved importing Excel xls Status in LibreOffice: Confirmed Status in OpenOffice: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in openoffice.org package in Ubuntu: Won't Fix Bug description: Binary package hint: openoffice.org 1) lsb_release -rd Description: Ubuntu 11.04 Release: 11.04 2) apt-cache policy libreoffice-calc libreoffice-calc: Installed: 1:3.3.3-1ubuntu2 Candidate: 1:3.3.3-1ubuntu2 Version table: *** 1:3.3.3-1ubuntu2 0 100 /var/lib/dpkg/status 1:3.3.2-1ubuntu5 0 500 http://us.archive.ubuntu.com/ubuntu/ natty-updates/main i386 Packages 1:3.3.2-1ubuntu4 0 500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages 3) What is expected to happen in LibreOffice Calc via the Terminal: cd ~/Desktop && wget https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/179531/+attachment/2145491/+files/to-m20e_4.xls && localc -nologo to-m20e_4.xls is the graph looks like as it does in Excel ( https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/179531/+attachment/2145492/+files/SS_image.gif ). 4) What happens instead is the colored lines of the graph are moved in Calc. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/179531/+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 1899803] Re: Some comments on annotations are not visible
The bug still continues. I've also tested using: - Ubuntu 22.04.2 with Evince 42.3 Upstream bug track: https://gitlab.gnome.org/GNOME/evince/-/issues/171 ** Bug watch added: gitlab.gnome.org/GNOME/evince/-/issues #171 https://gitlab.gnome.org/GNOME/evince/-/issues/171 ** Changed in: evince Status: Fix Released => Unknown ** Changed in: evince Remote watch: gitlab.gnome.org/GNOME/evince/-/issues #1347 => gitlab.gnome.org/GNOME/evince/-/issues #171 -- 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/1899803 Title: Some comments on annotations are not visible Status in Evince: Unknown Status in evince package in Ubuntu: Triaged Bug description: It is not possible to see some text/comment on annotations in a PDF file. This bug was tracking on: https://gitlab.gnome.org/GNOME/evince/-/issues/1347 I've replicated this bug here to document and add more people to help solve the problem. I've also tested using: - Ubuntu 20.04 with Evince 3.36.7 - Ubuntu 20.10 with Evince 3.38.0 To reproduce this bug, see the post: https://gitlab.gnome.org/GNOME/evince/-/issues/1347#note_745797 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evince 3.36.7-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 14 11:29:28 2020 InstallationDate: Installed on 2020-10-05 (9 days ago) InstallationMedia: Ubuntu 20.04.1 2020.09.19 LTS "Custom Focal Fossa" (20200920) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-09-19T23:53:28 To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1899803/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2023939] [NEW] Items in the sidebar are not activated by the keyboard when has selected files
Public bug reported: The selected items in the sidebar are not activated by the keyboard when there are selected files. Steps to reproduce the bug: 1) Open a directory that contains files; 2) Select a file; 2) Press F6 to change the focus to the sidebar; 3) Use arrows up or down to select an item in the sidebar; 4) Press Enter to activate the item in the sidebar. Unexpected behavior: - The selected file is opened. Expected behavior: - The selected item in the sidebar should open. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.6-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 14 21:04:52 2023 GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" b'org.gnome.nautilus.window-state' b'initial-size' b'(989, 679)' b'org.gnome.nautilus.window-state' b'sidebar-width' b'255' InstallationDate: Installed on 2023-06-03 (11 days ago) InstallationMedia: Ubuntu 22.04.2 2023.06.03 LTS (20230603) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-06-03T14:17:19 usr_lib_nautilus: evince42.3-0ubuntu3 file-roller 3.42.0-1 nautilus-extension-brasero3.12.3-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2023939 Title: Items in the sidebar are not activated by the keyboard when has selected files Status in nautilus package in Ubuntu: New Bug description: The selected items in the sidebar are not activated by the keyboard when there are selected files. Steps to reproduce the bug: 1) Open a directory that contains files; 2) Select a file; 2) Press F6 to change the focus to the sidebar; 3) Use arrows up or down to select an item in the sidebar; 4) Press Enter to activate the item in the sidebar. Unexpected behavior: - The selected file is opened. Expected behavior: - The selected item in the sidebar should open. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.6-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 14 21:04:52 2023 GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" b'org.gnome.nautilus.window-state' b'initial-size' b'(989, 679)' b'org.gnome.nautilus.window-state' b'sidebar-width' b'255' InstallationDate: Installed on 2023-06-03 (11 days ago) InstallationMedia: Ubuntu 22.04.2 2023.06.03 LTS (20230603) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-06-03T14:17:19 usr_lib_nautilus: evince42.3-0ubuntu3 file-roller 3.42.0-1 nautilus-extension-brasero3.12.3-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2023939/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1993907] Re: nautilus freezes randomly
Just upgraded from Ubuntu 20 to 22. Nautilus freezes every single time I use the search function. -- 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/1993907 Title: nautilus freezes randomly Status in nautilus package in Ubuntu: Confirmed Bug description: nautilus becomes unresponsive and "files" is not responding sign appears at random ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-1007.7-lowlatency 5.19.7 Uname: Linux 5.19.0-1007-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Oct 22 15:39:58 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 (161 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: nautilus UpgradeStatus: Upgraded to kinetic on 2022-10-19 (3 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/1993907/+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 2023928] Re: Meetings change to the organizers timezone instead of my timezone
This is not an isolated incident. It has happened quite a few times. Somebody schedules a meeting for a certain time in their timezone, and when I look at it, it's at the right time. Later, the time has changed to the wrong time and I don't get a notification for the meeting until after it's over. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/2023928 Title: Meetings change to the organizers timezone instead of my timezone Status in gnome-calendar package in Ubuntu: New Bug description: My calendar is misbehaving. I had this problem way back in 2021, on both Windows and Ubuntu, then it went away. Now it's back. I am exclusively on Ubuntu now. I have my google calendar synced to Ubuntu/Gnome. So my meetings result in OS notifications. I even installed a program that plays a very loud and annoying sound for calendar alerts (gaudible). I did not get a notification for an important meeting. While looking into it, I literally watched the meeting jump forward by two hours without me doing anything. The meeting was scheduled for 3 PM eastern today, so 1 PM mountain (my timezone). Now it is sitting at 3 PM mountain. When this happens, the notification does not come at the right time, and I miss meetings. I have no idea whether the problem is in Google Calendar or Gnome, but I suspect that Gnome is "fixing" the meeting and doing it incorrectly. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-calendar 41.2-3 ProcVersionSignature: Ubuntu 6.1.0-1013.13-oem 6.1.25 Uname: Linux 6.1.0-1013-oem x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 14 14:59:16 2023 InstallationDate: Installed on 2022-11-24 (201 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-calendar UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/2023928/+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 2023912] Re: When deleting a file (or files) via hitting the DEL button in Nautilus, the files deleted are still present in the window
*** This bug is a duplicate of bug 2022851 *** https://bugs.launchpad.net/bugs/2022851 Thank you for your bug report, that's bug #2022851 and a candidate fix is available for it ** 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/2023912 Title: When deleting a file (or files) via hitting the DEL button in Nautilus, the files deleted are still present in the window Status in nautilus package in Ubuntu: Confirmed Bug description: When deleting a file (or files) via hitting the DEL button in Nautilus, the files deleted are still present in the window after the deletion has finished. If I press F5 to refresh, then the files disappear. Sometimes, these files are being moved to the top of the list and other times they just sit in place where they were, with a tint of transparency? Hitting F5 will refresh the window's content and the files deleted eventually disappear. (SHIFT+DEL seems to have the file disappear as expected, after deletion.) 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: Wed Jun 14 19:30:59 2023 GsettingsChanges: b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' InstallationDate: Installed on 2022-12-15 (181 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: nautilus UpgradeStatus: Upgraded to lunar on 2023-06-08 (6 days ago) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.48.0-1ubuntu1 nautilus-image-converter 0.4.0-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2023912/+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 2023918] Re: Nautilus does not refresh folder during deleting file
*** This bug is a duplicate of bug 2022851 *** https://bugs.launchpad.net/bugs/2022851 ** This bug is no longer a duplicate of bug 2023912 When deleting a file (or files) via hitting the DEL button in Nautilus, the files deleted are still present in the window ** 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/2023918 Title: Nautilus does not refresh folder during deleting file Status in nautilus package in Ubuntu: New Bug description: ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: nautilus 1:44.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 14 21:02:42 2023 EcryptfsInUse: Yes ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.compression' b'default-compression-format' b"'encrypted_zip'" b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" 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'(1680, 870)' InstallationDate: Installed on 2023-06-01 (13 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: nautilus UpgradeStatus: Upgraded to lunar on 2023-06-01 (13 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/ubuntu/+source/nautilus/+bug/2023918/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2023086] Re: Gtk-4 update breaks nautilus
@RonsonK, thanks for the tip with Proposed. If Canonical pushed Nautilus 1:44.2.1 to Proposed to fix this I have to say that's just unacceptable. It's 8 days since Nautilus broke. And how should a random average user who is not dedicating his life to figure out the quirks of Ubuntu supposed to fix this issue? One really needs to be deep into Linux to understand that a gtk4-upgrade went wrong here. Meh, very disappointing. And no reaction from the devs too. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2023086 Title: Gtk-4 update breaks nautilus Status in gtk4 package in Ubuntu: Confirmed Bug description: It took me 2 hours to find out what the problem is. I reset Gnome desktop because I thought doing the good old dconf reset helps. Folks at Ubuntu - this kind of quality is just very annoying and unacceptable! Now to the bug. This is Ubuntu 23.04. Updates up-to-date. The latest update of libgtk-4 from version 4.10.1 to 4.10.3 breaks nautilus' move-to-trash behavior and copying is broken too. If you move a file to trash with libgtk-4.10.3 installed, the wrong icon is removed from the icon view. Just watch the attached video to see the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2023086/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1959848] Re: "_" not accepted within email addresses for copying
** Tags added: jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1959848 Title: "_" not accepted within email addresses for copying Status in gnome-terminal package in Ubuntu: Confirmed Bug description: step 1) hover the mouse over an email address with an _ in it like test_emai...@sharklasers.com 2) what happens only the part after the last _ is underlined (eg 1...@sharklasers.com ) what should happen the whole email should be underlined (eg test_emai...@sharklasers.com ) gnome-terminal: 3.36.1.1-1ubuntu1 ubuntu 20.04 focal --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2017-04-18 (1751 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: gnome-terminal 3.36.1.1-1ubuntu1jeff2 [origin: unknown] PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Tags: third-party-packages focal Uname: Linux 4.15.0-45-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: Upgraded to focal on 2020-04-25 (648 days ago) UserGroups: adm audio debian-tor docker _MarkForUpload: True modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2020-06-07T21:16:26.397404 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1959848/+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 2023928] [NEW] Meetings change to the organizers timezone instead of my timezone
Public bug reported: My calendar is misbehaving. I had this problem way back in 2021, on both Windows and Ubuntu, then it went away. Now it's back. I am exclusively on Ubuntu now. I have my google calendar synced to Ubuntu/Gnome. So my meetings result in OS notifications. I even installed a program that plays a very loud and annoying sound for calendar alerts (gaudible). I did not get a notification for an important meeting. While looking into it, I literally watched the meeting jump forward by two hours without me doing anything. The meeting was scheduled for 3 PM eastern today, so 1 PM mountain (my timezone). Now it is sitting at 3 PM mountain. When this happens, the notification does not come at the right time, and I miss meetings. I have no idea whether the problem is in Google Calendar or Gnome, but I suspect that Gnome is "fixing" the meeting and doing it incorrectly. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-calendar 41.2-3 ProcVersionSignature: Ubuntu 6.1.0-1013.13-oem 6.1.25 Uname: Linux 6.1.0-1013-oem x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 14 14:59:16 2023 InstallationDate: Installed on 2022-11-24 (201 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-calendar UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-calendar (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/2023928 Title: Meetings change to the organizers timezone instead of my timezone Status in gnome-calendar package in Ubuntu: New Bug description: My calendar is misbehaving. I had this problem way back in 2021, on both Windows and Ubuntu, then it went away. Now it's back. I am exclusively on Ubuntu now. I have my google calendar synced to Ubuntu/Gnome. So my meetings result in OS notifications. I even installed a program that plays a very loud and annoying sound for calendar alerts (gaudible). I did not get a notification for an important meeting. While looking into it, I literally watched the meeting jump forward by two hours without me doing anything. The meeting was scheduled for 3 PM eastern today, so 1 PM mountain (my timezone). Now it is sitting at 3 PM mountain. When this happens, the notification does not come at the right time, and I miss meetings. I have no idea whether the problem is in Google Calendar or Gnome, but I suspect that Gnome is "fixing" the meeting and doing it incorrectly. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-calendar 41.2-3 ProcVersionSignature: Ubuntu 6.1.0-1013.13-oem 6.1.25 Uname: Linux 6.1.0-1013-oem x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 14 14:59:16 2023 InstallationDate: Installed on 2022-11-24 (201 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-calendar UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/2023928/+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 2023928] Re: Meetings change to the organizers timezone instead of my timezone
When I was on Windows, I had Thunderbird syncing the calendar. I think Thunderbird was doing the same sort of "fixing". -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/2023928 Title: Meetings change to the organizers timezone instead of my timezone Status in gnome-calendar package in Ubuntu: New Bug description: My calendar is misbehaving. I had this problem way back in 2021, on both Windows and Ubuntu, then it went away. Now it's back. I am exclusively on Ubuntu now. I have my google calendar synced to Ubuntu/Gnome. So my meetings result in OS notifications. I even installed a program that plays a very loud and annoying sound for calendar alerts (gaudible). I did not get a notification for an important meeting. While looking into it, I literally watched the meeting jump forward by two hours without me doing anything. The meeting was scheduled for 3 PM eastern today, so 1 PM mountain (my timezone). Now it is sitting at 3 PM mountain. When this happens, the notification does not come at the right time, and I miss meetings. I have no idea whether the problem is in Google Calendar or Gnome, but I suspect that Gnome is "fixing" the meeting and doing it incorrectly. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-calendar 41.2-3 ProcVersionSignature: Ubuntu 6.1.0-1013.13-oem 6.1.25 Uname: Linux 6.1.0-1013-oem x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 14 14:59:16 2023 InstallationDate: Installed on 2022-11-24 (201 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-calendar UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/2023928/+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 2023927] [NEW] Screen flickering whe update images
Public bug reported: Often, when there are small changes in image displayed, an horizontal flickering is observed. This happen for example on a mouse right button menu, or when a hyperlink description appears on the screen bottom when mouse pointer cross some field on a webpage, also when favorites menu appear. The flickering usually disappear in a few moments, sometimes (usually when a few pixels are updating) it can last for seconds. This flickering is caused by a late updating of some horizontal lines, so for awhile a few lines of previous image coexist with a majority of new ones ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-41.46~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jun 14 22:44:12 2023 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.32, 5.13.0-40-generic, x86_64: installed virtualbox, 6.1.32, 5.13.0-41-generic, x86_64: installed virtualbox, 6.1.32, 5.4.0-126-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Device [1e39:a025] InstallationDate: Installed on 2022-01-01 (529 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Lsusb: Error: command ['lsusb'] failed with exit code 127: lsusb: symbol lookup error: lsusb: undefined symbol: libusb_error_name Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 127: lsusb: symbol lookup error: lsusb: undefined symbol: libusb_error_name Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 127: lsusb: symbol lookup error: lsusb: undefined symbol: libusb_error_name MachineType: MEDION S15449 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-41-generic root=UUID=cbfc0023-baf3-4a11-b0aa-6dadbd0f60f7 ro quiet splash pci=noaer vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 212 dmi.board.asset.tag: Default string dmi.board.name: M15T dmi.board.vendor: MEDION dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: MEDION dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr212:bd04/09/2021:br5.19:svnMEDION:pnS15449:pvrDefaultstring:rvnMEDION:rnM15T:rvrDefaultstring:cvnMEDION:ct10:cvrDefaultstring:skuML-23000830031014: dmi.product.family: Akoya dmi.product.name: S15449 dmi.product.sku: ML-230008 30031014 dmi.product.version: Default string dmi.sys.vendor: MEDION version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu ** Attachment added: "video explaining the bug when favorites menu appear/disappear" https://bugs.launchpad.net/bugs/2023927/+attachment/5679762/+files/WhatsApp%20Video%202023-06-14%20at%2022.59.56.mp4 -- 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/2023927 Title: Screen flickering whe update images Status in xorg package in Ubuntu: New Bug description: Often, when there are small changes in image displayed, an horizontal flickering is observed. This happen for example on a mouse right button menu, or when a hyperlink description appears on the screen bottom when mouse pointer cross some field on a webpage, also when favorites menu appear. The flickering usually disappear in a few moments, sometimes (usually when a few pixels are updating) it can last for seconds. This flickering is caused by a late updating of some horizontal lines, so for awhile a few lines of previous image coexist with a majority of new ones ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-41.46~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 BootLog: Error: [Errno 13] Permission
[Desktop-packages] [Bug 2017011] Re: [snap] unable to read /proc/pressure/{cpu, io, memory}
** Tags added: jammy
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/2017011
Title:
[snap] unable to read /proc/pressure/{cpu,io,memory}
Status in chromium-browser package in Ubuntu:
Triaged
Bug description:
During normal operation, chromium wants to read
/proc/pressure/{cpu,io,memory} but is denied by the Apparmor policy:
$ journalctl -b0 -k --grep 'chromium.chromium' | grep -F
'name="/proc/pressure/'
Apr 19 10:40:27 sdeziel-lemur kernel: audit: type=1400
audit(1681915227.726:817): apparmor="DENIED" operation="open" class="file"
profile="snap.chromium.chromium" name="/proc/pressure/cpu" pid=395005
comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Apr 19 10:40:27 sdeziel-lemur kernel: audit: type=1400
audit(1681915227.726:818): apparmor="DENIED" operation="open" class="file"
profile="snap.chromium.chromium" name="/proc/pressure/io" pid=395005
comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Apr 19 10:40:27 sdeziel-lemur kernel: audit: type=1400
audit(1681915227.726:819): apparmor="DENIED" operation="open" class="file"
profile="snap.chromium.chromium" name="/proc/pressure/memory" pid=395005
comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Note that simply starting the browser doesn't prompt it try and read
those files, you need to do something more involving like watching
Youtube for example.
Additional information:
$ snap list chromium core20
Name VersionRev Tracking Publisher Notes
chromium 112.0.5615.49 2424 latest/stable canonical✓ -
core2020230308 1852 latest/stable canonical✓ base
$ lsb_release -rd
Description: Ubuntu 22.04.2 LTS
Release: 22.04
$ uname -a
Linux sdeziel-lemur 5.19.0-40-generic #41~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC
Fri Mar 31 16:00:14 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2017011/+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 1875019] Re: ftbfs: Test failed: Basic functionality with the bind-mounted cache dir
** Tags added: jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1875019 Title: ftbfs: Test failed: Basic functionality with the bind-mounted cache dir Status in fontconfig package in Ubuntu: New Bug description: 1) apt-src install fontconfig 2) cd fontconfig-2.13.1/ 3) debuild -us -uc -b gets to PASS: test-hash PASS: test-bz106632 FAIL: run-test.sh fontconfig 2.13.1: test/test-suite.log # TOTAL: 7 # PASS: 6 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 .. contents:: :depth: 2 FAIL: run-test == Running: Basic check Running: With a subdir Running: Subdir with a cache file Running: Complicated directory structure Running: Subdir with an out-of-date cache file Running: Dir with an out-of-date cache file Running: Re-creating .uuid Running: Consistency between .uuid and cache name b41b6931-2503-44dd-a5d0-465a2c171511/home/z/fontconfig-2.13.1/test/cache.dir/08acdce6-36bc-4684-9a7b-0f24192abc6b-le64.cache-7 Running: Keep mtime of the font directory Running: Basic functionality with the bind-mounted cache dir *** Test failed: Basic functionality with the bind-mounted cache dir cache was updated. FAIL run-test.sh (exit status: 1) ubuntu: focal 20.04 LTS fontconfig1: fontconfig: Installed: 2.13.1-2ubuntu3 Candidate: 2.13.1-2ubuntu3 Version table: *** 2.13.1-2ubuntu3 500 500 http://speglar.simnet.is/ubuntu focal/main amd64 Packages 500 http://ubuntu.hysing.is/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: fontconfig 2.13.1-2ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Apr 25 13:15:14 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: fontconfig UpgradeStatus: Upgraded to focal on 2020-04-25 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1875019/+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 CTRL-click issue is fixed with libnautilus-extension4=1:44.2.1-0ubuntu1 nautilus-data=1:44.2.1-0ubuntu1 nautilus=1:44.2.1-0ubuntu1 Tks RonsonK #19 -- 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 2023920] Re: cheese doesn't open after upgrade to 22.04
how did this get assigned to "linux"? might be an apport bug -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/2023920 Title: cheese doesn't open after upgrade to 22.04 Status in cheese package in Ubuntu: New Status in linux package in Ubuntu: Invalid Bug description: current behaviour: when 'cheese' is run either via commandline or by search, either with -f or without, with webcam plugged in or not, it fails to bring up a cheese window this is what id displayed on the console: themusicgod1@eva1:~$ cheese -f ** (cheese:9307): WARNING **: 13:42:43.833: Couldn't load icon: Icon 'image-loading' not present in theme Yaru ** (cheese:9307): WARNING **: 13:42:43.833: Couldn't load icon: Icon 'image-loading' not present in theme Yaru ** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon 'image-loading' not present in theme Yaru ** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon 'image-loading' not present in theme Yaru ** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon 'image-loading' not present in theme Yaru ** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon 'image-loading' not present in theme Yaru ** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon 'image-loading' not present in theme Yaru ** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon 'image-loading' not present in theme Yaru ** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon 'image-loading' not present in theme Yaru ** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon 'image-loading' not present in theme Yaru ** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon 'image-loading' not present in theme Yaru expected behavior: cheese should load as it did in 20.04 what should happen: cheese runs ubuntu: 22.04 LTS Bus 001 Device 005: ID 046d:08c1 Logitech, Inc. QuickCam Fusion themusicgod1@eva1:~$ apt-cache policy cheese cheese: Installed: 41.1-1build1 Candidate: 41.1-1build1 Version table: *** 41.1-1build1 500 500 http://muug.ca/mirror/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status gnome 42.5 windowing system: wayland ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cheese 41.1-1build1 Uname: Linux 6.0.7-gnulibre-squashfix x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jun 14 13:40:09 2023 InstallationDate: Installed on 2017-04-18 (2248 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: MSI MS-7994 RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2023-06-14 (0 days ago) dmi.bios.date: 12/16/2016 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.80 dmi.board.asset.tag: Default string dmi.board.name: H110M GAMING (MS-7994) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.80:bd12/16/2016:br5.12:svnMSI:pnMS-7994:pvr1.0:rvnMSI:rnH110MGAMING(MS-7994):rvr1.0:cvnMSI:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7994 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI mtime.conffile..etc.apport.crashdb.conf: 2020-06-07T21:16:26.397404 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/2023920/+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 2023923] [NEW] Update gnome-desktop to 42.9
Public bug reported: Impact -- The only thing this update does is update the GNOME version number shown in the GNOME Settings > About dialog from 42.5 to 42.9 That's desired because we will include GNOME Shell 42.9 and people assume the version shown here is the version of GNOME Shell. There is a gnome-desktop 42.10 because the final official release of GNOME 42 was 42.10 but GNOME Shell skipped a release earlier so the versions aren't in sync. This update also cherry-picks one change from 42.10 to update the German translation. Because we use Ubuntu language packs, the new translation won't actually be used until the next language pack update, which is expected shortly before the Ubuntu 22.04.3 LTS release. Test Case - Install the updated packages Open the Settings app. Scroll down in the left sidebar and click About The GNOME Version should be 42.9 What Could Go Wrong --- Because this is part of core GNOME, it falls under the microrelease exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- GNOME 43 used GNOME Shell to display the version number so this kind of SRU is no longer needed after Ubuntu 22.04 LTS. GNOME 45 will simplify the version string to no longer report the minor version number (42 instead of 42.9) because GNOME Shell frequently is not released on exactly the same schedule as the overall GNOME project. ** Affects: gnome-desktop (Ubuntu) Importance: Low Status: Fix Released ** Affects: gnome-desktop (Ubuntu Jammy) Importance: Low Assignee: Jeremy Bícha (jbicha) Status: In Progress ** Tags: jammy upgrade-software-version ** Also affects: gnome-desktop (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: gnome-desktop (Ubuntu Jammy) Importance: Undecided => Low ** Changed in: gnome-desktop (Ubuntu Jammy) Status: New => In Progress ** Changed in: gnome-desktop (Ubuntu Jammy) Assignee: (unassigned) => Jeremy Bícha (jbicha) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop in Ubuntu. https://bugs.launchpad.net/bugs/2023923 Title: Update gnome-desktop to 42.9 Status in gnome-desktop package in Ubuntu: Fix Released Status in gnome-desktop source package in Jammy: In Progress Bug description: Impact -- The only thing this update does is update the GNOME version number shown in the GNOME Settings > About dialog from 42.5 to 42.9 That's desired because we will include GNOME Shell 42.9 and people assume the version shown here is the version of GNOME Shell. There is a gnome-desktop 42.10 because the final official release of GNOME 42 was 42.10 but GNOME Shell skipped a release earlier so the versions aren't in sync. This update also cherry-picks one change from 42.10 to update the German translation. Because we use Ubuntu language packs, the new translation won't actually be used until the next language pack update, which is expected shortly before the Ubuntu 22.04.3 LTS release. Test Case - Install the updated packages Open the Settings app. Scroll down in the left sidebar and click About The GNOME Version should be 42.9 What Could Go Wrong --- Because this is part of core GNOME, it falls under the microrelease exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- GNOME 43 used GNOME Shell to display the version number so this kind of SRU is no longer needed after Ubuntu 22.04 LTS. GNOME 45 will simplify the version string to no longer report the minor version number (42 instead of 42.9) because GNOME Shell frequently is not released on exactly the same schedule as the overall GNOME project. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop/+bug/2023923/+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 1998017] Re: inhibitShortcutsDialog not working in Ubuntu 22.10 / Gnome 43. Breaks keygrab and passing keys to VMs/remote systems
** Changed in: gnome-shell (Ubuntu Kinetic) Status: Won't Fix => 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/1998017 Title: inhibitShortcutsDialog not working in Ubuntu 22.10 / Gnome 43. Breaks keygrab and passing keys to VMs/remote systems Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: Fix Committed Status in gnome-shell source package in Kinetic: Fix Released Status in gnome-shell source package in Lunar: Fix Released Bug description: inhibitShortcutsDialog not working in Ubuntu 22.10 / Gnome 43. Breaks keygrab and passing keys to VMs/remote systems Bug is fixed upstream: https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/6107 Without that fix it is impossible to use same system shortcuts (Alt+Shift, etc.) in main system and in VM in virt-manager. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1998017/+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 2023920] Re: cheese doesn't open after upgrade to 22.04
** Also affects: cheese (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/2023920 Title: cheese doesn't open after upgrade to 22.04 Status in cheese package in Ubuntu: New Status in linux package in Ubuntu: Invalid Bug description: current behaviour: when 'cheese' is run either via commandline or by search, either with -f or without, with webcam plugged in or not, it fails to bring up a cheese window this is what id displayed on the console: themusicgod1@eva1:~$ cheese -f ** (cheese:9307): WARNING **: 13:42:43.833: Couldn't load icon: Icon 'image-loading' not present in theme Yaru ** (cheese:9307): WARNING **: 13:42:43.833: Couldn't load icon: Icon 'image-loading' not present in theme Yaru ** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon 'image-loading' not present in theme Yaru ** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon 'image-loading' not present in theme Yaru ** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon 'image-loading' not present in theme Yaru ** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon 'image-loading' not present in theme Yaru ** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon 'image-loading' not present in theme Yaru ** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon 'image-loading' not present in theme Yaru ** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon 'image-loading' not present in theme Yaru ** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon 'image-loading' not present in theme Yaru ** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon 'image-loading' not present in theme Yaru expected behavior: cheese should load as it did in 20.04 what should happen: cheese runs ubuntu: 22.04 LTS Bus 001 Device 005: ID 046d:08c1 Logitech, Inc. QuickCam Fusion themusicgod1@eva1:~$ apt-cache policy cheese cheese: Installed: 41.1-1build1 Candidate: 41.1-1build1 Version table: *** 41.1-1build1 500 500 http://muug.ca/mirror/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status gnome 42.5 windowing system: wayland ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cheese 41.1-1build1 Uname: Linux 6.0.7-gnulibre-squashfix x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jun 14 13:40:09 2023 InstallationDate: Installed on 2017-04-18 (2248 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: MSI MS-7994 RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2023-06-14 (0 days ago) dmi.bios.date: 12/16/2016 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.80 dmi.board.asset.tag: Default string dmi.board.name: H110M GAMING (MS-7994) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.80:bd12/16/2016:br5.12:svnMSI:pnMS-7994:pvr1.0:rvnMSI:rnH110MGAMING(MS-7994):rvr1.0:cvnMSI:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7994 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI mtime.conffile..etc.apport.crashdb.conf: 2020-06-07T21:16:26.397404 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/2023920/+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 2023913] Re: Release gnome-shell 42.9 to Jammy
** Changed in: gnome-shell (Ubuntu Jammy) Status: New => In Progress ** Changed in: gnome-shell (Ubuntu Jammy) Importance: Undecided => High ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => High -- 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/2023913 Title: Release gnome-shell 42.9 to Jammy Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: In Progress Bug description: Impact -- There is a new bugfix release in the stable 42 series. https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/42.9/NEWS The overall GNOME project considers GNOME 42 to be end of life now and there are no more scheduled releases for GNOME Shell 42 after 42.9 The current version of GNOME Shell in Jammy is 42.5. Test Case - Complete all the non-optional test cases at https://wiki.ubuntu.com/DesktopTeam/TestPlans/GNOMEShell What Could Go Wrong --- GNOME Shell is the heart of the Ubuntu desktop experience. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. GNOME Shell is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- This update requires mutter 42.9 (LP: #1998286). This was done with bumped dependencies in debian/control. gnome-shell 42.9 could be run with mutter 42.5, but mixing different versions of mutter & gnome-shell is not supported upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2023913/+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 2023913] Re: Release gnome-shell 42.9 to Jammy
** Description changed: Impact -- + There is a new bugfix release in the stable 42 series. + + https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/42.9/NEWS + + The overall GNOME project considers GNOME 42 to be end of life now and + there are no more scheduled releases for GNOME Shell 42 after 42.9 + + The current version of GNOME Shell in Jammy is 42.5. + + Test Case + - + Complete all the non-optional test cases at https://wiki.ubuntu.com/DesktopTeam/TestPlans/GNOMEShell + + What Could Go Wrong + --- + GNOME Shell is the heart of the Ubuntu desktop experience. + + A severe enough bug could mean that people are unable to use their + desktop version of Ubuntu. + + Smaller bugs could interrupt people's workflows. + + GNOME Shell is included in the GNOME micro release exception + + https://wiki.ubuntu.com/StableReleaseUpdates/GNOME + + Other Info + -- + This update requires mutter 42.9 (LP: #1998286). This was done with bumped dependencies in debian/control. gnome-shell 42.9 could be run with mutter 42.5, but mixing different versions of mutter & gnome-shell is not supported upstream. ** Also affects: gnome-shell (Ubuntu Jammy) 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/2023913 Title: Release gnome-shell 42.9 to Jammy Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: New Bug description: Impact -- There is a new bugfix release in the stable 42 series. https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/42.9/NEWS The overall GNOME project considers GNOME 42 to be end of life now and there are no more scheduled releases for GNOME Shell 42 after 42.9 The current version of GNOME Shell in Jammy is 42.5. Test Case - Complete all the non-optional test cases at https://wiki.ubuntu.com/DesktopTeam/TestPlans/GNOMEShell What Could Go Wrong --- GNOME Shell is the heart of the Ubuntu desktop experience. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. GNOME Shell is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- This update requires mutter 42.9 (LP: #1998286). This was done with bumped dependencies in debian/control. gnome-shell 42.9 could be run with mutter 42.5, but mixing different versions of mutter & gnome-shell is not supported upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2023913/+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 508618] Re: Setting max-specpdl-size of 34295 allows segfaults with 'simple' elisp
** Changed in: emacs25 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to emacs24 in Ubuntu. https://bugs.launchpad.net/bugs/508618 Title: Setting max-specpdl-size of 34295 allows segfaults with 'simple' elisp Status in emacs23 package in Ubuntu: New Status in emacs24 package in Ubuntu: New Status in emacs25 package in Ubuntu: Fix Released Status in emacs25 package in Debian: New Bug description: Binary package hint: emacs23 Setting max-specpdl-size higher than 34295, and then running the following code results in a segfault of emacs. I am running a system of mostly 9.04 with some packages (such as this one) upgraded. I know it's kind of pushing emacs to the limit, but still; this seems like an arbitrary limit on emacs' otherwise diety-like functionality. What should happen is emacs should continue to fail to execute with "file-truename: Variable binding depth exceeds max-specpdl-size" as it does below 34295., or at the very least when setting max-specpdl-size higher than 34295 it should warn you that you are making some kind of error if this is not acceptable. example code: (defun por (pcurrent pb numberleft) (if (= numberleft 0) pcurrent (por (- (+ pcurrent pb) (* pcurrent pb)) pb (- numberleft 1 (por 0 0.01 1) (setq max-lisp-eval-depth 100) ; this may be necessary, but doesn't appear to be the problem (setq max-specpdl-size 34295) ; setting this lower results in predictable, expected behaviour - emacs refuses to run the result, citing max-specpdl-size not high enough. Setting this higher (like...34296), results in a segfault of emacs emacs23: Installé : 23.1+1-4ubuntu3 Candidat : 23.1+1-4ubuntu3 Table de version : *** 23.1+1-4ubuntu3 0 100 /var/lib/dpkg/status ProblemType: Bug Architecture: amd64 DistroRelease: Ubuntu 9.04 Package: emacs23 23.1+1-4ubuntu3 ProcEnviron: PATH=(custom, user) LANG=fr_CA.UTF-8 SHELL=/bin/bash SourcePackage: emacs23 Uname: Linux 2.6.28-16-generic x86_64 UnreportableReason: Ceci n'est pas un authentique paquet Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacs23/+bug/508618/+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 2023918] Re: Nautilus does not refresh folder during deleting file
*** This bug is a duplicate of bug 2023912 *** https://bugs.launchpad.net/bugs/2023912 ** This bug has been marked a duplicate of bug 2023912 When deleting a file (or files) via hitting the DEL button in Nautilus, the files deleted are still present in the window ** Description changed: - Seems it affects only folder where are the files WITH extension. - Example 1: - -folder with three files without extension (file01, file02, file03) - works OK - -folder with three files without extension (file01, file02, file03) and one file with extension (file04.sql) - not working (BAD) ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: nautilus 1:44.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 14 21:02:42 2023 EcryptfsInUse: Yes ExecutablePath: /usr/bin/nautilus GsettingsChanges: - b'org.gnome.nautilus.compression' b'default-compression-format' b"'encrypted_zip'" - b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" - 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'(1680, 870)' + b'org.gnome.nautilus.compression' b'default-compression-format' b"'encrypted_zip'" + b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" + 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'(1680, 870)' InstallationDate: Installed on 2023-06-01 (13 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: nautilus UpgradeStatus: Upgraded to lunar on 2023-06-01 (13 days ago) usr_lib_nautilus: - file-roller 43.0-1 - nautilus-extension-gnome-terminal 3.48.0-1ubuntu1 + file-roller 43.0-1 + nautilus-extension-gnome-terminal 3.48.0-1ubuntu1 -- 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/2023918 Title: Nautilus does not refresh folder during deleting file Status in nautilus package in Ubuntu: New Bug description: ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: nautilus 1:44.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 14 21:02:42 2023 EcryptfsInUse: Yes ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.compression' b'default-compression-format' b"'encrypted_zip'" b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" 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'(1680, 870)' InstallationDate: Installed on 2023-06-01 (13 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: nautilus UpgradeStatus: Upgraded to lunar on 2023-06-01 (13 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/ubuntu/+source/nautilus/+bug/2023918/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1981837] Re: Using DiNG triggers ubuntu-dock opacity
See https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension- ubuntu-dock/+bug/2023916 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1981837 Title: Using DiNG triggers ubuntu-dock opacity Status in Gnome Shell Extension Desktop Icons Ng: Fix Released Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Won't Fix Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Bug description: Hi, Ubuntu 22.04 LTS jammy Linux 5.15.0-40-generic x86_64 x86_64 ubuntu-xorg / x11 I prefer panel and dock to become fully opaque only when windows are maximized. So I use this extension for panel : Transparent Top Bar (Adjustable transparency) which JustWorks™ in both Xorg and Wayland. In ubuntu-dock, dynamic-transparency is set through dconf-editor ( transparency-mode, min-alpha, max-alpha. ) When using DiNG under Wayland, opacity is triggered as if « desktop » was considered as a maximized window. Under Xorg, DiNG does not trigger dock opacity, as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons-ng/+bug/1981837/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1981837] Re: Using DiNG triggers ubuntu-dock opacity
It has been fixed a moment and now it's back… 22.04 LTS gnome-shell-extension-ubuntu-dock 72~ubuntu5.22.04.2.1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1981837 Title: Using DiNG triggers ubuntu-dock opacity Status in Gnome Shell Extension Desktop Icons Ng: Fix Released Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Won't Fix Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Bug description: Hi, Ubuntu 22.04 LTS jammy Linux 5.15.0-40-generic x86_64 x86_64 ubuntu-xorg / x11 I prefer panel and dock to become fully opaque only when windows are maximized. So I use this extension for panel : Transparent Top Bar (Adjustable transparency) which JustWorks™ in both Xorg and Wayland. In ubuntu-dock, dynamic-transparency is set through dconf-editor ( transparency-mode, min-alpha, max-alpha. ) When using DiNG under Wayland, opacity is triggered as if « desktop » was considered as a maximized window. Under Xorg, DiNG does not trigger dock opacity, as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons-ng/+bug/1981837/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1998286] Re: Release mutter 42.9 to jammy
** Description changed: - Release mutter 42.9 to jammy + Impact + -- + There is a new bugfix release in the stable 42 series. + https://gitlab.gnome.org/GNOME/mutter/-/blob/42.9/NEWS - At least 42.6 is required to fix bug 1961563 (Xilinx Wayland support) - and bug 1988256 + The overall GNOME project considers GNOME 42 to be end of life now and + there are no more scheduled releases for mutter 42 after 42.9 + + This is basically a prerequisite for GNOME Shell 42.9 LP: #2023913 + + The current version of Mutter in Jammy is 42.5. + + Test Case + - + Complete the test case from + + https://wiki.ubuntu.com/DesktopTeam/TestPlans/Mutter + + Extra Test Case 1 + - + This release also cherry-picks a patch to fix the prompt to enable accessibility features using keyboard shortcuts. + + 0. Install the updated mutter packages. Then log out and log back in. + 1. Open the Settings app (gnome-control-center) + 2. In the left sidebar, click Accessibility + 3. In the typing section, lick Typing Assist + 4. Turn on the first switch to enable turning accessibility features on and off using the keyboard + 5. Close the Settings app + 6. Press the Shift key 5 or 6 times in a row + 7. You should see a system prompt about turning on Sticky Keys + + What Could Go Wrong + --- + Mutter is an essential component of the default Ubuntu desktop and for the desktop used by Ubuntu Budgie. + + A severe enough bug could mean that people are unable to use their + desktop version of Ubuntu. + + Smaller bugs could interrupt people's workflows. + + mutter is part of GNOME Core and is included in the GNOME micro release + exception + + https://wiki.ubuntu.com/StableReleaseUpdates/GNOME + + Other Info + -- + Upstream assumes that people will be using matching versions of mutter and gnome-shell. To be cautious, I therefore bumped the dependency version in GNOME Shell 42.9 to require mutter >= 42.9 (even though GNOME Shell 42.9 appears to run ok with Mutter 42.5). I believe the only way to make the dependency relationship work the other way (not allow Mutter 42.9 with GNOME Shell 42.5) requires bumping the Breaks version but I don't think it's worth using Breaks unless necessary. + + This release will also enable AMD Xilinx/Mali support on Wayland. See + https://ubuntu.com/download/amd-xilinx or private bug 1961563 or the + 42.6 release notes. ** Changed in: mutter (Ubuntu) Status: Triaged => Fix Released ** Changed in: mutter (Ubuntu) Importance: Medium => High ** Also affects: mutter (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu Jammy) Importance: Undecided => High ** Changed in: mutter (Ubuntu Jammy) Status: New => In Progress ** Changed in: mutter (Ubuntu Jammy) Assignee: (unassigned) => Jeremy Bícha (jbicha) -- 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: Fix Released Status in mutter source package in Jammy: In Progress Bug description: Impact -- There is a new bugfix release in the stable 42 series. https://gitlab.gnome.org/GNOME/mutter/-/blob/42.9/NEWS The overall GNOME project considers GNOME 42 to be end of life now and there are no more scheduled releases for mutter 42 after 42.9 This is basically a prerequisite for GNOME Shell 42.9 LP: #2023913 The current version of Mutter in Jammy is 42.5. Test Case - Complete the test case from https://wiki.ubuntu.com/DesktopTeam/TestPlans/Mutter Extra Test Case 1 - This release also cherry-picks a patch to fix the prompt to enable accessibility features using keyboard shortcuts. 0. Install the updated mutter packages. Then log out and log back in. 1. Open the Settings app (gnome-control-center) 2. In the left sidebar, click Accessibility 3. In the typing section, lick Typing Assist 4. Turn on the first switch to enable turning accessibility features on and off using the keyboard 5. Close the Settings app 6. Press the Shift key 5 or 6 times in a row 7. You should see a system prompt about turning on Sticky Keys What Could Go Wrong --- Mutter is an essential component of the default Ubuntu desktop and for the desktop used by Ubuntu Budgie. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. mutter is part of GNOME Core and is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- Upstream assumes that people will be using matching versions of mutter and gnome-shell. To be cautious, I therefore bumped the dependency version in GNOME Shell 42.9 to require mutter >= 42.9 (even t
[Desktop-packages] [Bug 2012178] Re: toolbox.py crashed with NameError in __readAuthType(): name 'get_distro_std_name' is not defined
** Description changed: + [ Impact ] + + HP's GUI tool hp-toolbox does not start at all, independent which + printer(s) is used. + + With this users lose GUI-based maintenance functionality like ink level + check, print head cleaning, ... + + As a workaround on all network printers (independent whether they are + driverless IPP or not) the printer's web administration interface can be + used, going to http://HOSTNAME/ with a browser, HOSTNAME being host name + or IP of the printer. On USB only driverless printers allow access to + the web administration interface, via http://localhost:6/, but most + modern printers are driverless. + + hp-toolbox only supports HP printers, no other manufacturers. + + Also, hp-toolbox, being part of hplip-gui is only used by very few + users, as it is not installed by default. + + Printing and scanning is not affected. Your printer gets set up fully + automatically or you can set up as any non-HP printer with GNOME Control + Center, system-config-printer, or via HTTP://localhost:631/. + + Scanners in HP's devices will get automatically discovered by scanning + frontends, like simple-scan. + + [ Test plan ] + + Start the toolbox with + +hp-toolbox + + Without the fix you will get the crash mentioned in the title of this + bug report. With the SRU applied, the toolbox starts normally and can be + used. + + This test can be done independently of whether one has an HP printer or + not. + + [ Where problems could occur ] + + The changes are very small and easy to understand, so the risk of a + regression is low, and as this is code for HPLIP's GUI there cannot + happen more than now, that the GUI tools crash. The patch only applies + to GUI code, printing and scanning cannot get affected by it. + + [ Original description ] + Error occurred after installing hplip-gui ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: hplip-data 3.22.10+dfsg0-1 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: KDE Date: Sun Mar 19 05:07:34 2023 ExecutablePath: /usr/share/hplip/toolbox.py InstallationDate: Installed on 2023-03-18 (0 days ago) InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230318) InterpreterPath: /usr/bin/python3.11 JournalErrors: -- No entries -- Lpstat: device for HP_Color_LaserJet_Pro_MFP_M177fw_0342B1: implicitclass://HP_Color_LaserJet_Pro_MFP_M177fw_0342B1/ MachineType: HP HP ZBook 17 G4 PackageArchitecture: all Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_Pro_MFP_M177fw_0342B1.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_Pro_MFP_M177fw_0342B1.ppd: Permission denied ProcCmdline: /usr/bin/python3 /usr/bin/hp-toolbox ProcEnviron: - LANG=en_US.UTF-8 - PATH=(custom, no user) - SHELL=/bin/bash - XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + PATH=(custom, no user) + SHELL=/bin/bash + XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-16-generic root=UUID=20a0c66a-2dc4-41ec-a5f0-7eb86e995862 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonArgs: ['/usr/bin/hp-toolbox'] PythonDetails: N/A SourcePackage: hplip Title: toolbox.py crashed with NameError in __readAuthType(): name 'get_distro_std_name' is not defined UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users dmi.bios.date: 04/08/2022 dmi.bios.release: 1.41 dmi.bios.vendor: HP dmi.bios.version: P70 Ver. 01.41 dmi.board.name: 8270 dmi.board.vendor: HP dmi.board.version: KBC Version 46.80 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 70.128 dmi.modalias: dmi:bvnHP:bvrP70Ver.01.41:bd04/08/2022:br1.41:efr70.128:svnHP:pnHPZBook17G4:pvr:rvnHP:rn8270:rvrKBCVersion46.80:cvnHP:ct10:cvr:skuY3J83AV: dmi.product.family: 103C_5336AN dmi.product.name: HP ZBook 17 G4 dmi.product.sku: Y3J83AV dmi.sys.vendor: HP -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/2012178 Title: toolbox.py crashed with NameError in __readAuthType(): name 'get_distro_std_name' is not defined Status in hplip package in Ubuntu: Fix Released Status in hplip source package in Lunar: In Progress Bug description: [ Impact ] HP's GUI tool hp-toolbox does not start at all, independent which printer(s) is used. With this users lose GUI-based maintenance functionality like ink level check, print head cleaning, ... As a workaround on all network printers (independent whether they are driverless IPP or not) the printer's web administration interface can be used,
[Desktop-packages] [Bug 2023916] [NEW] Dock opacity is triggered by DING extension in Wayland
Public bug reported: Hi, if dock transparency is set to DYNAMIC, dock opacity is triggered by DING extension in Wayland. Works as expected under Xorg, dock background stays transparent while DING is enabled. Not the first time this happens ( https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop- icons-ng/+bug/1981837 ) it has been fixed for a moment and now issue is back with latest version of gnome-shell-extension-ubuntu-dock. I can see that issue on many installations / machines running Ubuntu 22.04 LTS. If of any interest, other gnome shell extensions ( transparent top bar, dash to panel ) are not impacted by this issue. So far. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu5.22.04.2.1 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 14 21:09:46 2023 InstallationDate: Installed on 2022-06-01 (378 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Description changed: Hi, if dock transparency is set to DYNAMIC, dock opacity is triggered by DING extension in Wayland. Works as expected under Xorg, dock background stays transparent while DING is enabled. Not the first time this happens it has been fixed for a moment and now issue is back with latest version of gnome-shell-extension-ubuntu-dock. + + I can see that issue on many installations / machines running Ubuntu + 22.04 LTS. + + If of any interest, other gnome shell extensions ( transparent top bar, + dash to panel ) are not impacted by this issue. So far. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu5.22.04.2.1 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 14 21:09:46 2023 InstallationDate: Installed on 2022-06-01 (378 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=fr_FR.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=fr_FR.UTF-8 + SHELL=/bin/bash SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: Hi, if dock transparency is set to DYNAMIC, dock opacity is triggered by DING extension in Wayland. Works as expected under Xorg, dock background stays transparent while DING is enabled. - Not the first time this happens it has been fixed for a moment and now - issue is back with latest version of gnome-shell-extension-ubuntu-dock. + Not the first time this happens ( + https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop- + icons-ng/+bug/1981837 ) it has been fixed for a moment and now issue is + back with latest version of gnome-shell-extension-ubuntu-dock. I can see that issue on many installations / machines running Ubuntu 22.04 LTS. If of any interest, other gnome shell extensions ( transparent top bar, dash to panel ) are not impacted by this issue. So far. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu5.22.04.2.1 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 14 21:09:46 2023 InstallationDate: Installed on 2022-06-01 (378 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/2023916 Title: Dock opacity is triggered by DING extension in Wayland Status in gnome-shell-extension-ubuntu
[Desktop-packages] [Bug 1985089] Re: Resizing two edge tiled windows is laggy
** Description changed: - Just to report an issue that other people have reported to GNOME and in - Reddit, that seems to also affect Ubuntu 22.04. + Impact + -- + Mutter 42.9 includes a fix for tiled window resizing. Before the fix, window resizing could use very large amounts of memory and be laggy. + + Test Case + - + 0. Install the updated mutter packages. Log out then log back in. + 1. Open System Monitor. Tile it to the Left. + 2. Open a Terminal. Tile it to the right. + 3. Click the Resources tab in System Monitor. + 3. Right-click the System Monitor in the headerbar and click Resize. + 4. Move your mouse left and right to resize the window. + 5. The memory should not dramatically spike higher as seen in the System Monitor's Resources tab. + + What Could Go Wrong + --- + See the master mutter 42.9 bug LP: #1998286 + + Original Bug Report + --- + Just to report an issue that other people have reported to GNOME and in Reddit, that seems to also affect Ubuntu 22.04. If you snap 2 windows side-by-side in Wayland and then try to resize them, it's very slow and uses a lot of memory. Check here for more details: - https://gitlab.gnome.org/GNOME/mutter/-/issues/2246 - https://old.reddit.com/r/gnome/comments/whjgel/resizing_two_tiled_windows_leaks_memory_and_is/ ** Also affects: mutter (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu Jammy) Status: New => In Progress ** Changed in: mutter (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: mutter (Ubuntu Jammy) Assignee: (unassigned) => Jeremy Bícha (jbicha) -- 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/1985089 Title: Resizing two edge tiled windows is laggy Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: In Progress Bug description: Impact -- Mutter 42.9 includes a fix for tiled window resizing. Before the fix, window resizing could use very large amounts of memory and be laggy. Test Case - 0. Install the updated mutter packages. Log out then log back in. 1. Open System Monitor. Tile it to the Left. 2. Open a Terminal. Tile it to the right. 3. Click the Resources tab in System Monitor. 3. Right-click the System Monitor in the headerbar and click Resize. 4. Move your mouse left and right to resize the window. 5. The memory should not dramatically spike higher as seen in the System Monitor's Resources tab. What Could Go Wrong --- See the master mutter 42.9 bug LP: #1998286 Original Bug Report --- Just to report an issue that other people have reported to GNOME and in Reddit, that seems to also affect Ubuntu 22.04. If you snap 2 windows side-by-side in Wayland and then try to resize them, it's very slow and uses a lot of memory. Check here for more details: - https://gitlab.gnome.org/GNOME/mutter/-/issues/2246 - https://old.reddit.com/r/gnome/comments/whjgel/resizing_two_tiled_windows_leaks_memory_and_is/ To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1985089/+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 1998017] Re: inhibitShortcutsDialog not working in Ubuntu 22.10 / Gnome 43. Breaks keygrab and passing keys to VMs/remote systems
** Changed in: gnome-shell (Ubuntu Kinetic) Status: Fix Committed => Won't Fix -- 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/1998017 Title: inhibitShortcutsDialog not working in Ubuntu 22.10 / Gnome 43. Breaks keygrab and passing keys to VMs/remote systems Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: Fix Committed Status in gnome-shell source package in Kinetic: Won't Fix Status in gnome-shell source package in Lunar: Fix Released Bug description: inhibitShortcutsDialog not working in Ubuntu 22.10 / Gnome 43. Breaks keygrab and passing keys to VMs/remote systems Bug is fixed upstream: https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/6107 Without that fix it is impossible to use same system shortcuts (Alt+Shift, etc.) in main system and in VM in virt-manager. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1998017/+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 2023918] [NEW] Nautilus does not refresh folder during deleting file
Public bug reported: Seems it affects only folder where are the files WITH extension. Example 1: -folder with three files without extension (file01, file02, file03) - works OK -folder with three files without extension (file01, file02, file03) and one file with extension (file04.sql) - not working (BAD) ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: nautilus 1:44.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 14 21:02:42 2023 EcryptfsInUse: Yes ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.compression' b'default-compression-format' b"'encrypted_zip'" b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" 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'(1680, 870)' InstallationDate: Installed on 2023-06-01 (13 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: nautilus UpgradeStatus: Upgraded to lunar on 2023-06-01 (13 days ago) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.48.0-1ubuntu1 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar wayland-session ** Attachment added: "Video showing bug in nautilus during deleteing file" https://bugs.launchpad.net/bugs/2023918/+attachment/5679744/+files/Screencast%20from%202023-06-14%2021-15-18.webm -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2023918 Title: Nautilus does not refresh folder during deleting file Status in nautilus package in Ubuntu: New Bug description: Seems it affects only folder where are the files WITH extension. Example 1: -folder with three files without extension (file01, file02, file03) - works OK -folder with three files without extension (file01, file02, file03) and one file with extension (file04.sql) - not working (BAD) ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: nautilus 1:44.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 14 21:02:42 2023 EcryptfsInUse: Yes ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.compression' b'default-compression-format' b"'encrypted_zip'" b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" 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'(1680, 870)' InstallationDate: Installed on 2023-06-01 (13 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: nautilus UpgradeStatus: Upgraded to lunar on 2023-06-01 (13 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/ubuntu/+source/nautilus/+bug/2023918/+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 2023912] Re: When deleting a file (or files) via hitting the DEL button in Nautilus, the files deleted are still present in the window
Just confirming, DEL or SHIFT+DEL does the same result, the file deleted will still be visible after deletion has finished. -- 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/2023912 Title: When deleting a file (or files) via hitting the DEL button in Nautilus, the files deleted are still present in the window Status in nautilus package in Ubuntu: Confirmed Bug description: When deleting a file (or files) via hitting the DEL button in Nautilus, the files deleted are still present in the window after the deletion has finished. If I press F5 to refresh, then the files disappear. Sometimes, these files are being moved to the top of the list and other times they just sit in place where they were, with a tint of transparency? Hitting F5 will refresh the window's content and the files deleted eventually disappear. (SHIFT+DEL seems to have the file disappear as expected, after deletion.) 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: Wed Jun 14 19:30:59 2023 GsettingsChanges: b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' InstallationDate: Installed on 2022-12-15 (181 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: nautilus UpgradeStatus: Upgraded to lunar on 2023-06-08 (6 days ago) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.48.0-1ubuntu1 nautilus-image-converter 0.4.0-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2023912/+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 2012178] Re: toolbox.py crashed with NameError in __readAuthType(): name 'get_distro_std_name' is not defined
** Changed in: hplip (Ubuntu Lunar) Status: Triaged => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/2012178 Title: toolbox.py crashed with NameError in __readAuthType(): name 'get_distro_std_name' is not defined Status in hplip package in Ubuntu: Fix Released Status in hplip source package in Lunar: In Progress Bug description: Error occurred after installing hplip-gui ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: hplip-data 3.22.10+dfsg0-1 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: KDE Date: Sun Mar 19 05:07:34 2023 ExecutablePath: /usr/share/hplip/toolbox.py InstallationDate: Installed on 2023-03-18 (0 days ago) InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230318) InterpreterPath: /usr/bin/python3.11 JournalErrors: -- No entries -- Lpstat: device for HP_Color_LaserJet_Pro_MFP_M177fw_0342B1: implicitclass://HP_Color_LaserJet_Pro_MFP_M177fw_0342B1/ MachineType: HP HP ZBook 17 G4 PackageArchitecture: all Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_Pro_MFP_M177fw_0342B1.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_Pro_MFP_M177fw_0342B1.ppd: Permission denied ProcCmdline: /usr/bin/python3 /usr/bin/hp-toolbox ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-16-generic root=UUID=20a0c66a-2dc4-41ec-a5f0-7eb86e995862 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonArgs: ['/usr/bin/hp-toolbox'] PythonDetails: N/A SourcePackage: hplip Title: toolbox.py crashed with NameError in __readAuthType(): name 'get_distro_std_name' is not defined UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users dmi.bios.date: 04/08/2022 dmi.bios.release: 1.41 dmi.bios.vendor: HP dmi.bios.version: P70 Ver. 01.41 dmi.board.name: 8270 dmi.board.vendor: HP dmi.board.version: KBC Version 46.80 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 70.128 dmi.modalias: dmi:bvnHP:bvrP70Ver.01.41:bd04/08/2022:br1.41:efr70.128:svnHP:pnHPZBook17G4:pvr:rvnHP:rn8270:rvrKBCVersion46.80:cvnHP:ct10:cvr:skuY3J83AV: dmi.product.family: 103C_5336AN dmi.product.name: HP ZBook 17 G4 dmi.product.sku: Y3J83AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/2012178/+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 2023912] Re: When deleting a file (or files) via hitting the DEL button in Nautilus, the files deleted are still present in the window
Happens to me as well, see attached screencast. ** Attachment added: "Screencast from 2023-06-14 20-58-05.webm" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2023912/+attachment/5679741/+files/Screencast%20from%202023-06-14%2020-58-05.webm -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2023912 Title: When deleting a file (or files) via hitting the DEL button in Nautilus, the files deleted are still present in the window Status in nautilus package in Ubuntu: Confirmed Bug description: When deleting a file (or files) via hitting the DEL button in Nautilus, the files deleted are still present in the window after the deletion has finished. If I press F5 to refresh, then the files disappear. Sometimes, these files are being moved to the top of the list and other times they just sit in place where they were, with a tint of transparency? Hitting F5 will refresh the window's content and the files deleted eventually disappear. (SHIFT+DEL seems to have the file disappear as expected, after deletion.) 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: Wed Jun 14 19:30:59 2023 GsettingsChanges: b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' InstallationDate: Installed on 2022-12-15 (181 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: nautilus UpgradeStatus: Upgraded to lunar on 2023-06-08 (6 days ago) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.48.0-1ubuntu1 nautilus-image-converter 0.4.0-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2023912/+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 2023912] Re: When deleting a file (or files) via hitting the DEL button in Nautilus, the files deleted are still present in the window
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nautilus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2023912 Title: When deleting a file (or files) via hitting the DEL button in Nautilus, the files deleted are still present in the window Status in nautilus package in Ubuntu: Confirmed Bug description: When deleting a file (or files) via hitting the DEL button in Nautilus, the files deleted are still present in the window after the deletion has finished. If I press F5 to refresh, then the files disappear. Sometimes, these files are being moved to the top of the list and other times they just sit in place where they were, with a tint of transparency? Hitting F5 will refresh the window's content and the files deleted eventually disappear. (SHIFT+DEL seems to have the file disappear as expected, after deletion.) 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: Wed Jun 14 19:30:59 2023 GsettingsChanges: b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' InstallationDate: Installed on 2022-12-15 (181 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: nautilus UpgradeStatus: Upgraded to lunar on 2023-06-08 (6 days ago) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.48.0-1ubuntu1 nautilus-image-converter 0.4.0-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2023912/+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 2023913] [NEW] Release gnome-shell 42.9 to Jammy
Public bug reported: Impact -- ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: Fix Released ** Tags: jammy upgrade-software-version -- 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/2023913 Title: Release gnome-shell 42.9 to Jammy Status in gnome-shell package in Ubuntu: Fix Released Bug description: Impact -- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2023913/+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 2012178] Re: toolbox.py crashed with NameError in __readAuthType(): name 'get_distro_std_name' is not defined
3.22.10+dfsg0-2 got already synced from Debian into Mantic, so it is fixed in Mantic. ** Changed in: hplip (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/2012178 Title: toolbox.py crashed with NameError in __readAuthType(): name 'get_distro_std_name' is not defined Status in hplip package in Ubuntu: Fix Released Status in hplip source package in Lunar: Triaged Bug description: Error occurred after installing hplip-gui ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: hplip-data 3.22.10+dfsg0-1 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: KDE Date: Sun Mar 19 05:07:34 2023 ExecutablePath: /usr/share/hplip/toolbox.py InstallationDate: Installed on 2023-03-18 (0 days ago) InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230318) InterpreterPath: /usr/bin/python3.11 JournalErrors: -- No entries -- Lpstat: device for HP_Color_LaserJet_Pro_MFP_M177fw_0342B1: implicitclass://HP_Color_LaserJet_Pro_MFP_M177fw_0342B1/ MachineType: HP HP ZBook 17 G4 PackageArchitecture: all Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_Pro_MFP_M177fw_0342B1.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_Pro_MFP_M177fw_0342B1.ppd: Permission denied ProcCmdline: /usr/bin/python3 /usr/bin/hp-toolbox ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-16-generic root=UUID=20a0c66a-2dc4-41ec-a5f0-7eb86e995862 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonArgs: ['/usr/bin/hp-toolbox'] PythonDetails: N/A SourcePackage: hplip Title: toolbox.py crashed with NameError in __readAuthType(): name 'get_distro_std_name' is not defined UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users dmi.bios.date: 04/08/2022 dmi.bios.release: 1.41 dmi.bios.vendor: HP dmi.bios.version: P70 Ver. 01.41 dmi.board.name: 8270 dmi.board.vendor: HP dmi.board.version: KBC Version 46.80 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 70.128 dmi.modalias: dmi:bvnHP:bvrP70Ver.01.41:bd04/08/2022:br1.41:efr70.128:svnHP:pnHPZBook17G4:pvr:rvnHP:rn8270:rvrKBCVersion46.80:cvnHP:ct10:cvr:skuY3J83AV: dmi.product.family: 103C_5336AN dmi.product.name: HP ZBook 17 G4 dmi.product.sku: Y3J83AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/2012178/+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 2023912] [NEW] When deleting a file (or files) via hitting the DEL button in Nautilus, the files deleted are still present in the window
Public bug reported: When deleting a file (or files) via hitting the DEL button in Nautilus, the files deleted are still present in the window after the deletion has finished. If I press F5 to refresh, then the files disappear. Sometimes, these files are being moved to the top of the list and other times they just sit in place where they were, with a tint of transparency? Hitting F5 will refresh the window's content and the files deleted eventually disappear. (SHIFT+DEL seems to have the file disappear as expected, after deletion.) 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: Wed Jun 14 19:30:59 2023 GsettingsChanges: b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' InstallationDate: Installed on 2022-12-15 (181 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: nautilus UpgradeStatus: Upgraded to lunar on 2023-06-08 (6 days ago) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.48.0-1ubuntu1 nautilus-image-converter 0.4.0-2 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar third-party-packages wayland-session -- 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/2023912 Title: When deleting a file (or files) via hitting the DEL button in Nautilus, the files deleted are still present in the window Status in nautilus package in Ubuntu: New Bug description: When deleting a file (or files) via hitting the DEL button in Nautilus, the files deleted are still present in the window after the deletion has finished. If I press F5 to refresh, then the files disappear. Sometimes, these files are being moved to the top of the list and other times they just sit in place where they were, with a tint of transparency? Hitting F5 will refresh the window's content and the files deleted eventually disappear. (SHIFT+DEL seems to have the file disappear as expected, after deletion.) 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: Wed Jun 14 19:30:59 2023 GsettingsChanges: b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' InstallationDate: Installed on 2022-12-15 (181 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: nautilus UpgradeStatus: Upgraded to lunar on 2023-06-08 (6 days ago) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.48.0-1ubuntu1 nautilus-image-converter 0.4.0-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2023912/+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 2000275] Re: evince neither prints nor previews postscript documents
I have the same bug here, with same symptoms (blank page when printing PDF/PS file from evince). $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.04.2 LTS Release:22.04 Codename: jammy $ evince --version GNOME Document Viewer 42.3 $ ghostscript --version 9.55.0 This bug has not been assigned yet ? -- 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/2000275 Title: evince neither prints nor previews postscript documents Status in evince package in Ubuntu: New Bug description: evince does successfully display a ps document, but when attempting to print or preview (whether to a file or printer) fails, with either a blank page (for print) or blank window (for preview) produced, and some error output at the terminal. Any ps document (text or graphical) has this failure. A PDF document succeeds in the print preview, but with the same warning (see below examples) so the warning may not be important. qpdfview does successfully print the ps file, so not a hardware issue. User logged in using xorg. $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.04.1 LTS Release:22.04 Codename: jammy $ evince --version GNOME Document Viewer 42.3 $ ghostscript --version 9.55.0 Screen display works for ps files, but a warning and error are produced when attempting to print or preview a postscript file (see below). The same warning is produced for print/preview of a pdf file, but the preview succeeds. A comment was added to launchpad bug 1978838 which had this same warning when launching evince. evince does not crash, the display of the file is not affected when the print/preview fails. ===ps preview/print fails when preview button is pushed === $ evince ./parallel/mpi/mpich-1.2.0/doc/install.ps GPL Ghostscript 9.55.0: Unrecoverable error, exit code 1 (libspectre) ghostscript reports: fatal internal error -100 (evince-previewer:3039): dbind-WARNING **: 14:04:36.390: Couldn't connect to accessibility bus: Failed to connect to socket /run/user/1000/at-spi/bus_1: Permission denied === PDF preview succeeded even with the warning === $ evince ./patches/bdp1600/Upgrade_Guide_USB.pdf (evince-previewer:5688): dbind-WARNING **: 14:46:13.409: Couldn't connect to accessibility bus: Failed to connect to socket /run/user/1000/at-spi/bus_1: Permission denied ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 42.3-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Dec 21 15:12:58 2022 InstallationDate: Installed on 2022-06-10 (194 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/2000275/+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 2023909] [NEW] gnome-s+ CPU useage spike to 100%+ on mouse move
Public bug reported: when i move my mouse, the gnome-s+ CPU usage spike > 100%, RES > 1G. iam using Ubunto 22.4 LS and i'm using X11. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 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.4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 14 18:36:49 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-11-21 (205 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2023909 Title: gnome-s+ CPU useage spike to 100%+ on mouse move Status in gnome-shell package in Ubuntu: New Bug description: when i move my mouse, the gnome-s+ CPU usage spike > 100%, RES > 1G. iam using Ubunto 22.4 LS and i'm using X11. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 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.4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 14 18:36:49 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-11-21 (205 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2023909/+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 or Shift + click don't work to select multiple files in listview
I can confirm too, I've done the same - installed nautilus from proposed and it's work well: shift + click, copying/pasting/deleting files etc. -- 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 1971242] Re: printing PDF appears always grey, no color
Uploaded CUPS 2.4.5 to Mantic. This version has the mentioned fixes
included.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1971242
Title:
printing PDF appears always grey, no color
Status in CUPS:
Fix Released
Status in atril package in Ubuntu:
Confirmed
Status in cups package in Ubuntu:
Fix Committed
Status in okular package in Ubuntu:
Confirmed
Status in cups source package in Jammy:
In Progress
Bug description:
After upgrading from 20.04 LTS to 22.04 LTS I can't print colored PDF
document. The print appears always b/w regardless color printing was
enabled or not. Printing from LibreOffice produces a color print. This
behavior (bug) is reproducible on three upgraded machines. It would be
nice to have color print back again.
[ Impact ]
If the PPD file for a printer has a ColorModel option and the only
choice in it for printing in color is not named RGB but CMYK instead,
the printer cannot be made printing in color with intuitive methods,
usually selcting the color choice in the print dialog (which makes
ColorModel=CMYK be sent along with the job).
Only an ugly command-line-based workaround, running the command
lpadmin -p PRINTER -o print-color-mode-default=color
makes the printer print in color.
An example for printers with such PPDs are printers from RICOH and OEM
(Lanier, InfoTec, Savin, ..), so many high-end color laser printers
are affected.
[ Test Plan ]
Remove the workaround if you had applied it:
lpadmin -p PRINTER -R print-color-mode-default
If you have an affected printer, print a PDF file (or use the print
functionality in an application) with colored content and choose the
setting for color printing in the print dialog. When printing via
command line do
lp -d PRINTER -o ColorModel=CMYK FILE.pdf
Without the SRU applied you will get a grayscale/monochrome printout,
with it applied, you will get a colored printout.
To test without a printer:
Stop CUPS:
sudo systemctl stop cups
Edit /etc/cups/cups-files.conf to have a line
FiileDevice Yes
ans start CUPS again:
sudo systemctl start cups
Then create a queue using the attached sample PPD file:
lpadmin -p color-test -E -v file:/tmp/printout -P Ricoh-
PDF_Printer-PDF.ppd
Print a file to this queue as described above. When the job is done
("lpstat" does not show it any more), open /tmp/printout with a text
editor. Chcke whether it contains a line
@PJL SET RENDERMODE=COLOR
near its beginning, and NOT a line
@PJL SET RENDERMODE=GRAYSCALE
[ Where problems could occur ]
The patches are simple and they are also for some time in newer CUPS
versions (2.4.2 and newer) which are included in several distributions
(Ubuntu 22.10, 23.04, and others) and did not cause any complaints
about color printing. So the regression potential is very low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cups/+bug/1971242/+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 1971242] Re: printing PDF appears always grey, no color
** Changed in: cups (Ubuntu Lunar)
Status: New => In Progress
** Changed in: cups (Ubuntu)
Status: Confirmed => Fix Committed
** Also affects: okular (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: cups (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: atril (Ubuntu Jammy)
Importance: Undecided
Status: New
** No longer affects: cups (Ubuntu Lunar)
** Changed in: cups (Ubuntu Jammy)
Importance: Undecided => High
** Changed in: cups (Ubuntu Jammy)
Status: New => In Progress
** No longer affects: okular (Ubuntu Lunar)
** No longer affects: okular (Ubuntu Jammy)
** No longer affects: atril (Ubuntu Lunar)
** No longer affects: atril (Ubuntu Jammy)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1971242
Title:
printing PDF appears always grey, no color
Status in CUPS:
Fix Released
Status in atril package in Ubuntu:
Confirmed
Status in cups package in Ubuntu:
Fix Committed
Status in okular package in Ubuntu:
Confirmed
Status in cups source package in Jammy:
In Progress
Bug description:
After upgrading from 20.04 LTS to 22.04 LTS I can't print colored PDF
document. The print appears always b/w regardless color printing was
enabled or not. Printing from LibreOffice produces a color print. This
behavior (bug) is reproducible on three upgraded machines. It would be
nice to have color print back again.
[ Impact ]
If the PPD file for a printer has a ColorModel option and the only
choice in it for printing in color is not named RGB but CMYK instead,
the printer cannot be made printing in color with intuitive methods,
usually selcting the color choice in the print dialog (which makes
ColorModel=CMYK be sent along with the job).
Only an ugly command-line-based workaround, running the command
lpadmin -p PRINTER -o print-color-mode-default=color
makes the printer print in color.
An example for printers with such PPDs are printers from RICOH and OEM
(Lanier, InfoTec, Savin, ..), so many high-end color laser printers
are affected.
[ Test Plan ]
Remove the workaround if you had applied it:
lpadmin -p PRINTER -R print-color-mode-default
If you have an affected printer, print a PDF file (or use the print
functionality in an application) with colored content and choose the
setting for color printing in the print dialog. When printing via
command line do
lp -d PRINTER -o ColorModel=CMYK FILE.pdf
Without the SRU applied you will get a grayscale/monochrome printout,
with it applied, you will get a colored printout.
To test without a printer:
Stop CUPS:
sudo systemctl stop cups
Edit /etc/cups/cups-files.conf to have a line
FiileDevice Yes
ans start CUPS again:
sudo systemctl start cups
Then create a queue using the attached sample PPD file:
lpadmin -p color-test -E -v file:/tmp/printout -P Ricoh-
PDF_Printer-PDF.ppd
Print a file to this queue as described above. When the job is done
("lpstat" does not show it any more), open /tmp/printout with a text
editor. Chcke whether it contains a line
@PJL SET RENDERMODE=COLOR
near its beginning, and NOT a line
@PJL SET RENDERMODE=GRAYSCALE
[ Where problems could occur ]
The patches are simple and they are also for some time in newer CUPS
versions (2.4.2 and newer) which are included in several distributions
(Ubuntu 22.10, 23.04, and others) and did not cause any complaints
about color printing. So the regression potential is very low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cups/+bug/1971242/+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
Hi Daniel,
Thanks again, and I totally agree that we need to focus on the revert
resolution issue in this LP bug. I wasn't willing to discuss the other
issues here, but to summarize my understanding so far, so as to make
sure we are on the same page.
Also, I tested "xrandr --output VNC-output-1 --auto" to enable another
monitor using Budgie and Xfce (I believe none of them use mutter), and I
can't reproduce the "blank screen". It doesn't really do anything, but
also doesn't reproduce the blank screen issue.
This is what I see in Xfce:
https://pastebin.ubuntu.com/p/BNs9KJqbHz/
And Budgie:
https://pastebin.ubuntu.com/p/pKTGzJb8bN/
My previous suggestion (patch with zero hz fix + no fractional scaling)
was because I thought vv1 was also exposed to the issue you mentioned on
comment #19 ("fractional scaling patch is trying to implement the revert
using fractional scaling"), but I guess not, and it still fails with the
"Invalid mode 800x600 (-nan)" errors, which is the zero hz issue, and
led us to vv2 and then vv4.
So, the current situation is that either with vv4 (zero hz patch + no
fractional scaling) OR vv5 with fractional scaling disabled (zero hz
patch included) we get to the situation where the extra monitors are
automatically enabled and the resolution is changed to 800x600:
https://pastebin.ubuntu.com/p/k822YMHM5v/
And IIUC this is what needs to be investigated next.
And no need to apologize if not able to respond this daily, completely
understandable and you're already doing a lot for this bug. Thank you
very very much for that!
I'll also be OoO for the next couple of days, back on Monday anyway.
Cheers,
Fabio Martins
--
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:
m
[Desktop-packages] [Bug 2022851] Re: Nautilus displays invalid directory content after deleting
Also confirm that Nautilus 44.2.1 fixes the issue. :) -- 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 2022997] Re: Nautilus does not update view properly when deleting or moving files unless refreshed
*** This bug is a duplicate of bug 2022851 *** https://bugs.launchpad.net/bugs/2022851 I do confirm that is fixed after install of nautilus 44.2.1 :) -- 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/2022997 Title: Nautilus does not update view properly when deleting or moving files unless refreshed Status in Nautilus: Fix Released Status in nautilus package in Ubuntu: Confirmed Bug description: This issue happens in Nautilus 44.0, both on Wayland and X11, and has also been noted in upstream Gnome as well: https://gitlab.gnome.org/GNOME/nautilus/-/issues/2945 When deleting files, only the file being deleted should be shown as deleted, and when moving files/folders, the file/folder should appear as-is in the destination directory. However, this is not the case here. When deleting, the file/folder gets deleted correctly in the filesystem, but Nautilus does not update the view properly. The file being deleted still remains, instead showing another file to be deleted and when undoing delete operation via [Ctrl-Z], it shows a duplicate of the deleted file/folder. This issue persists until you refresh the view [F5], when the view shows up correctly. Also, when moving files/folders to another directory, the file/folder initially shows up as a blank 'text' file named '', until you refresh the view, when it shows up correctly. It is worth noting that this issue has apparently been fixed in Fedora and Arch for a while (see gitlab bug report linked above). Please implement the same fixes here in Ubuntu as well. System details: OS: Ubuntu Version: 23.04 GNOME Version: 44.0 Kernel: Linux 6.2.0-20-generic Package details: nautilus: Installed: 1:44.0-1ubuntu2 Candidate: 1:44.0-1ubuntu2 Version table: *** 1:44.0-1ubuntu2 500 500 http://ae.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status 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: Tue Jun 6 08:45:58 2023 GsettingsChanges: b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.preferences' b'show-create-link' b'true' b'org.gnome.nautilus.preferences' b'show-delete-permanently' b'true' b'org.gnome.nautilus.window-state' b'initial-size' b'(890, 549)' InstallationDate: Installed on 2023-06-03 (2 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 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/2022997/+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 2023675] Re: flip effect doesn't work on GStreamer 1.22
** Changed in: gnome-video-effects (Debian) Status: Unknown => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-video-effects in Ubuntu. https://bugs.launchpad.net/bugs/2023675 Title: flip effect doesn't work on GStreamer 1.22 Status in GNOME Video Effects: Fix Released Status in gnome-video-effects package in Ubuntu: Fix Released Status in gnome-video-effects source package in Lunar: In Progress Status in gnome-video-effects package in Debian: Fix Released Bug description: Impact -- The Flip effect in the Cheese app doesn't work in Ubuntu 23.10. Test Case - 1. Install the updated gnome-video-effects packages 2. Open the Cheese app 3. Click the Effects button and verify that Flip is showing a reversed version of No Effect What Could Go Wrong --- This is a simple one-line patch. gnome-video-effects has only one reverse dependency in Ubuntu: cheese. Original Bug Report --- Distributor ID: Ubuntu Description: Ubuntu 23.04 Release: 23.04 Codename: lunar gnome-video-effects: Installed: 0.5.0-1ubuntu1 Candidate: 0.5.0-1ubuntu1 Version table: *** 0.5.0-1ubuntu1 500 500 http://br.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status The file located in: /usr/share/gnome-video-effects/flip.effect is using the property "method" which is deprecated as you can see in GStreamer "https://gstreamer.freedesktop.org/documentation/videofilter/videoflip.html?gi- language=c" Deprecated version: PipelineDescription=videoflip method=horizontal- flip So the fix for this problem is to change the property to the new one, which is called video-direction, after this the effect will work correctly. Fix: PipelineDescription=videoflip video-direction=horiz The program that I used to test this effect was Cheese. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-video-effects/+bug/2023675/+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 2020049] Re: gnome-shell crashed with SIGSEGV in clutter_stage_view_get_onscreen() from meta_stage_impl_add_onscreen_frame_info() from add_onscreen_frame_info() from post_finis
Me too. From lock screen, I unlocked with password and turned on my monitor. 2 seconds later it crashed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2020049 Title: gnome-shell crashed with SIGSEGV in clutter_stage_view_get_onscreen() from meta_stage_impl_add_onscreen_frame_info() from add_onscreen_frame_info() from post_finish_frame() from try_post_latest_swap() Status in mutter package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 44.0-2ubuntu3, the problem page at https://errors.ubuntu.com/problem/c675f1d61cef940571272d7e655162f1b1cddab1 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2020049/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2023788] [NEW] New version 1.0 available in experimental but not ready
Public bug reported: It was synced to mantic but removed for now - The new version is incompatible with the previous one and the .pc got renamed, there is a discussion in https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=934811 about renaming the binaries - Pipewire also currently fail to build with it, https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/1263 - the i386 build failed, https://launchpad.net/ubuntu/+source/webrtc- audio-processing/1.0-0.2/+build/26295875 we should wait for Debian to upload to unstable instead ** Affects: webrtc-audio-processing (Ubuntu) Importance: Wishlist Status: Triaged ** Tags: upgrade-software-version -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webrtc-audio-processing in Ubuntu. https://bugs.launchpad.net/bugs/2023788 Title: New version 1.0 available in experimental but not ready Status in webrtc-audio-processing package in Ubuntu: Triaged Bug description: It was synced to mantic but removed for now - The new version is incompatible with the previous one and the .pc got renamed, there is a discussion in https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=934811 about renaming the binaries - Pipewire also currently fail to build with it, https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/1263 - the i386 build failed, https://launchpad.net/ubuntu/+source/webrtc- audio-processing/1.0-0.2/+build/26295875 we should wait for Debian to upload to unstable instead To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webrtc-audio-processing/+bug/2023788/+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 2022997] Re: Nautilus does not update view properly when deleting or moving files unless refreshed
*** This bug is a duplicate of bug 2022851 *** https://bugs.launchpad.net/bugs/2022851 Same issue on my dell 7420 Ubuntu 23.04. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2022997 Title: Nautilus does not update view properly when deleting or moving files unless refreshed Status in Nautilus: Fix Released Status in nautilus package in Ubuntu: Confirmed Bug description: This issue happens in Nautilus 44.0, both on Wayland and X11, and has also been noted in upstream Gnome as well: https://gitlab.gnome.org/GNOME/nautilus/-/issues/2945 When deleting files, only the file being deleted should be shown as deleted, and when moving files/folders, the file/folder should appear as-is in the destination directory. However, this is not the case here. When deleting, the file/folder gets deleted correctly in the filesystem, but Nautilus does not update the view properly. The file being deleted still remains, instead showing another file to be deleted and when undoing delete operation via [Ctrl-Z], it shows a duplicate of the deleted file/folder. This issue persists until you refresh the view [F5], when the view shows up correctly. Also, when moving files/folders to another directory, the file/folder initially shows up as a blank 'text' file named '', until you refresh the view, when it shows up correctly. It is worth noting that this issue has apparently been fixed in Fedora and Arch for a while (see gitlab bug report linked above). Please implement the same fixes here in Ubuntu as well. System details: OS: Ubuntu Version: 23.04 GNOME Version: 44.0 Kernel: Linux 6.2.0-20-generic Package details: nautilus: Installed: 1:44.0-1ubuntu2 Candidate: 1:44.0-1ubuntu2 Version table: *** 1:44.0-1ubuntu2 500 500 http://ae.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status 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: Tue Jun 6 08:45:58 2023 GsettingsChanges: b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.preferences' b'show-create-link' b'true' b'org.gnome.nautilus.preferences' b'show-delete-permanently' b'true' b'org.gnome.nautilus.window-state' b'initial-size' b'(890, 549)' InstallationDate: Installed on 2023-06-03 (2 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 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/2022997/+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] Re: PDF fonts messed up in evince, mupdf, are fine in chrome
It's also worth noting that the evince snap doesn't have the same problem so it could be due to a poppler version or a fonts configuration difference -- 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: Confirmed 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 2023588] Re: PDF fonts messed up in evince, mupdf, are fine in chrome
Thanks, indeed I can confirm with that document ** Changed in: evince (Ubuntu) Status: New => Confirmed ** Changed in: evince (Ubuntu) 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/2023588 Title: PDF fonts messed up in evince, mupdf, are fine in chrome Status in evince package in Ubuntu: Confirmed 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 2000628] Re: The wifi password prompt disappear immediately after showing up on 22.04
I’m also experiencing this bug (Ubuntu 22.04, xorg) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2000628 Title: The wifi password prompt disappear immediately after showing up on 22.04 Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: Some other people reported this bug [here](https://askubuntu.com/questions/1409433/22-04-cant-input- password-for-wifi) Basically, when you try to log into a network, there is no way to input your password. The only way to reach a visible network seems to be by one of the workarounds: use the "Connect to Hidden Network" option, or directly edit the network config files. It seems like a critical bug to me because it can demotivate new users of Ubuntu and Linux. I joined a screen record of the prompt blinking on screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2000628/+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
It looks like the fix for bug 2023766 will do a better job at fixing this one too, in theory. And that fix is no longer part of triple buffering so can be patched independently. -- 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: Fix Committed Status in mutter source package in Lunar: In Progress Status in mutter source package in Mantic: Fix Committed 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 2023588] Re: PDF fonts messed up in evince, mupdf, are fine in chrome
** Attachment added: "same page which demonstrates this issue" https://bugs.launchpad.net/ubuntu/+source/evince/+bug/2023588/+attachment/5679706/+files/sample.pdf -- 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 2023086] Re: Gtk-4 update breaks nautilus
I can confirm that installing Nautilus 1:44.2.1-0ubuntu1 through Proposed solves the issue for me. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2023086 Title: Gtk-4 update breaks nautilus Status in gtk4 package in Ubuntu: Confirmed Bug description: It took me 2 hours to find out what the problem is. I reset Gnome desktop because I thought doing the good old dconf reset helps. Folks at Ubuntu - this kind of quality is just very annoying and unacceptable! Now to the bug. This is Ubuntu 23.04. Updates up-to-date. The latest update of libgtk-4 from version 4.10.1 to 4.10.3 breaks nautilus' move-to-trash behavior and copying is broken too. If you move a file to trash with libgtk-4.10.3 installed, the wrong icon is removed from the icon view. Just watch the attached video to see the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2023086/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2023766] Re: Mouse cursor stutters but only over GUI elements that are animated
** Tags removed: triple-buffering ** Changed in: mutter (Ubuntu Mantic) Status: Fix Committed => In Progress ** Also affects: mutter (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu Jammy) Status: New => Triaged ** Changed in: mutter (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: mutter (Ubuntu Jammy) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Tags added: jammy lunar -- 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/2023766 Title: Mouse cursor stutters but only over GUI elements that are animated Status in mutter package in Ubuntu: In Progress Status in mutter source package in Jammy: Triaged Status in mutter source package in Lunar: Triaged Status in mutter source package in Mantic: In Progress Bug description: Mouse cursor stutters but only over GUI elements that are animated. You can notice this in Settings > Screen Display if the cursor moves over a list containing fade animations. But it doesn't stutter over non-animated elements or constantly-animated elements. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023766/+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 1971242] Re: printing PDF appears always grey, no color
Sample PPD file for the SRU test plan.
** Description changed:
After upgrading from 20.04 LTS to 22.04 LTS I can't print colored PDF
document. The print appears always b/w regardless color printing was
enabled or not. Printing from LibreOffice produces a color print. This
behavior (bug) is reproducible on three upgraded machines. It would be
nice to have color print back again.
+
+ [ Impact ]
+
+ If the PPD file for a printer has a ColorModel option and the only
+ choice in it for printing in color is not named RGB but CMYK instead,
+ the printer cannot be made printing in color with intuitive methods,
+ usually selcting the color choice in the print dialog (which makes
+ ColorModel=CMYK be sent along with the job).
+
+ Only an ugly command-line-based workaround, running the command
+
+ lpadmin -p PRINTER -o print-color-mode-default=color
+
+ makes the printer print in color.
+
+ An example for printers with such PPDs are printers from RICOH and OEM
+ (Lanier, InfoTec, Savin, ..), so many high-end color laser printers are
+ affected.
+
+ [ Test Plan ]
+
+ Remove the workaround if you had applied it:
+
+ lpadmin -p PRINTER -R print-color-mode-default
+
+ If you have an affected printer, print a PDF file (or use the print
+ functionality in an application) with colored content and choose the
+ setting for color printing in the print dialog. When printing via
+ command line do
+
+ lp -d PRINTER -o ColorModel=CMYK FILE.pdf
+
+ Without the SRU applied you will get a grayscale/monochrome printout,
+ with it applied, you will get a colored printout.
+
+ To test without a printer:
+
+ Stop CUPS:
+
+ sudo systemctl stop cups
+
+ Edit /etc/cups/cups-files.conf to have a line
+
+ FiileDevice Yes
+
+ ans start CUPS again:
+
+ sudo systemctl start cups
+
+ Then create a queue using the attached sample PPD file:
+
+ lpadmin -p color-test -E -v file:/tmp/printout -P Ricoh-PDF_Printer-
+ PDF.ppd
+
+ Print a file to this queue as described above. When the job is done
+ ("lpstat" does not show it any more), open /tmp/printout with a text
+ editor. Chcke whether it contains a line
+
+ @PJL SET RENDERMODE=COLOR
+
+ near its beginning, and NOT a line
+
+ @PJL SET RENDERMODE=GRAYSCALE
+
+ [ Where problems could occur ]
+
+ The patches are simple and they are also for some time in newer CUPS
+ versions (2.4.2 and newer) which are included in several distributions
+ (Ubuntu 22.10, 23.04, and others) and did not cause any complaints about
+ color printing. So the regression potential is very low.
** Attachment added: "Ricoh-PDF_Printer-PDF.ppd"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1971242/+attachment/5679703/+files/Ricoh-PDF_Printer-PDF.ppd
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1971242
Title:
printing PDF appears always grey, no color
Status in CUPS:
Fix Released
Status in atril package in Ubuntu:
Confirmed
Status in cups package in Ubuntu:
Confirmed
Status in okular package in Ubuntu:
Confirmed
Status in atril source package in Lunar:
New
Status in cups source package in Lunar:
New
Status in okular source package in Lunar:
New
Bug description:
After upgrading from 20.04 LTS to 22.04 LTS I can't print colored PDF
document. The print appears always b/w regardless color printing was
enabled or not. Printing from LibreOffice produces a color print. This
behavior (bug) is reproducible on three upgraded machines. It would be
nice to have color print back again.
[ Impact ]
If the PPD file for a printer has a ColorModel option and the only
choice in it for printing in color is not named RGB but CMYK instead,
the printer cannot be made printing in color with intuitive methods,
usually selcting the color choice in the print dialog (which makes
ColorModel=CMYK be sent along with the job).
Only an ugly command-line-based workaround, running the command
lpadmin -p PRINTER -o print-color-mode-default=color
makes the printer print in color.
An example for printers with such PPDs are printers from RICOH and OEM
(Lanier, InfoTec, Savin, ..), so many high-end color laser printers
are affected.
[ Test Plan ]
Remove the workaround if you had applied it:
lpadmin -p PRINTER -R print-color-mode-default
If you have an affected printer, print a PDF file (or use the print
functionality in an application) with colored content and choose the
setting for color printing in the print dialog. When printing via
command line do
lp -d PRINTER -o ColorModel=CMYK FILE.pdf
Without the SRU applied you will get a grayscale/monochrome printout,
with it applied, you will get a colored printout.
To test without a printer:
Stop CUPS:
sudo systemctl stop cups
Edit /etc/cups/cups-files.conf to have a line
FiileDevice Yes
ans start CUPS again:
[Desktop-packages] [Bug 2022851] Re: Nautilus displays invalid directory content after deleting
Christians - I had the same CTRL-click issue in Nautilus. Upgrading to Nautilus 1:44.2.1-0ubuntu1 from Proposed solved that issue -- 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 2023766] Re: Mouse cursor stutters but only over GUI elements that are animated
Fixed better in https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3074 -- 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/2023766 Title: Mouse cursor stutters but only over GUI elements that are animated 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: Mouse cursor stutters but only over GUI elements that are animated. You can notice this in Settings > Screen Display if the cursor moves over a list containing fade animations. But it doesn't stutter over non-animated elements or constantly-animated elements. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023766/+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 2023776] Re: Ubuntu 23.04 + Gnome + Nvidia 525 + Vsync = low fps
Btw, I just noticed that some drop down windows, such as the ones in the
Chromium Snap, also have a little bit of pixelation in them when vsync
is active in nvidia-settings.
--
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/2023776
Title:
Ubuntu 23.04 + Gnome + Nvidia 525 + Vsync = low fps
Status in gnome-shell package in Ubuntu:
New
Bug description:
Currently using Nvidia driver 525, which is the "tested" and
recommended driver according to Ubuntu's additional driver tool (as of
this writing).
- manually resizing "files" windows = low fps and a little bit of
pixelation
- moving windows around = drop in fps every now and then
- opening the Gnome overview = sometimes buttery smooth 60fps but
sometimes stuttery low fps that takes time to "catch up" to smoothness
again
- resizing Chromium or Firefox window = low fps, glitchy window
behaviour etc.
How to fix it? Well, this is what I found works thus far:
- disable both "vsync" and "allow flipping" in Nvidia-settings
- now everything is buttery smooth again; all animations, apps, games
and more
- doing this will introduce lots of tearing on the Gnome desktop and
applications though
- then force full composition pipeline to get rid of the tearing by
adding this start-up line to Ubuntu's start-up applications: nvidia-
settings --assign CurrentMetaMode="nvidia-auto-select +0+0
{ForceFullCompositionPipeline=On}"
- Use Wayland alternatively: Wayland doesn't have any of these issues
at all, it's a buttery smooth fully vsynced experience ootb, but a
bunch of new problems arise instead: Can't set global hotkeys for
recording in OBS, OBS recording performance is pretty bad, Gnome
folder windows start flickering somestimes, Gnome windows glitch out
when trying to resize them manually, Steam flickering sometimes,
browsers such as Firefox and Chromium have to be set to Wayland mode
in order to solve stuttering video playback issues, Nvidia-settings is
missing a bunch of settings and features when compared to X11... and
more
Hard- and Software:
- Ubuntu 23.04
- Nvidia driver version 525 (tested) from Ubuntu's additional drivers tool
- Core i7 7700
- 32 GB DDR4 RAM
- Lenovo Nvidia RTX A2000 workstation GPU
- TWO fullHD monitors connected via display port
ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: gnome-shell 44.1-0ubuntu1
ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
Uname: Linux 6.2.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Jun 14 14:58:08 2023
DisplayManager: gdm3
InstallationDate: Installed on 2023-05-20 (24 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
ProcEnviron:
LANG=de_DE.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
RelatedPackageVersions: mutter-common 44.1-0ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2023776/+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 2023776] [NEW] Ubuntu 23.04 + Gnome + Nvidia 525 + Vsync = low fps
Public bug reported:
Currently using Nvidia driver 525, which is the "tested" and recommended
driver according to Ubuntu's additional driver tool (as of this
writing).
- manually resizing "files" windows = low fps and a little bit of
pixelation
- moving windows around = drop in fps every now and then
- opening the Gnome overview = sometimes buttery smooth 60fps but
sometimes stuttery low fps that takes time to "catch up" to smoothness
again
- resizing Chromium or Firefox window = low fps, glitchy window
behaviour etc.
How to fix it? Well, this is what I found works thus far:
- disable both "vsync" and "allow flipping" in Nvidia-settings
- now everything is buttery smooth again; all animations, apps, games
and more
- doing this will introduce lots of tearing on the Gnome desktop and
applications though
- then force full composition pipeline to get rid of the tearing by
adding this start-up line to Ubuntu's start-up applications: nvidia-
settings --assign CurrentMetaMode="nvidia-auto-select +0+0
{ForceFullCompositionPipeline=On}"
- Use Wayland alternatively: Wayland doesn't have any of these issues at
all, it's a buttery smooth fully vsynced experience ootb, but a bunch of
new problems arise instead: Can't set global hotkeys for recording in
OBS, OBS recording performance is pretty bad, Gnome folder windows start
flickering somestimes, Gnome windows glitch out when trying to resize
them manually, Steam flickering sometimes, browsers such as Firefox and
Chromium have to be set to Wayland mode in order to solve stuttering
video playback issues, Nvidia-settings is missing a bunch of settings
and features when compared to X11... and more
Hard- and Software:
- Ubuntu 23.04
- Nvidia driver version 525 (tested) from Ubuntu's additional drivers tool
- Core i7 7700
- 32 GB DDR4 RAM
- Lenovo Nvidia RTX A2000 workstation GPU
- TWO fullHD monitors connected via display port
ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: gnome-shell 44.1-0ubuntu1
ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
Uname: Linux 6.2.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Jun 14 14:58:08 2023
DisplayManager: gdm3
InstallationDate: Installed on 2023-05-20 (24 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
ProcEnviron:
LANG=de_DE.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
RelatedPackageVersions: mutter-common 44.1-0ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug lunar
--
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/2023776
Title:
Ubuntu 23.04 + Gnome + Nvidia 525 + Vsync = low fps
Status in gnome-shell package in Ubuntu:
New
Bug description:
Currently using Nvidia driver 525, which is the "tested" and
recommended driver according to Ubuntu's additional driver tool (as of
this writing).
- manually resizing "files" windows = low fps and a little bit of
pixelation
- moving windows around = drop in fps every now and then
- opening the Gnome overview = sometimes buttery smooth 60fps but
sometimes stuttery low fps that takes time to "catch up" to smoothness
again
- resizing Chromium or Firefox window = low fps, glitchy window
behaviour etc.
How to fix it? Well, this is what I found works thus far:
- disable both "vsync" and "allow flipping" in Nvidia-settings
- now everything is buttery smooth again; all animations, apps, games
and more
- doing this will introduce lots of tearing on the Gnome desktop and
applications though
- then force full composition pipeline to get rid of the tearing by
adding this start-up line to Ubuntu's start-up applications: nvidia-
settings --assign CurrentMetaMode="nvidia-auto-select +0+0
{ForceFullCompositionPipeline=On}"
- Use Wayland alternatively: Wayland doesn't have any of these issues
at all, it's a buttery smooth fully vsynced experience ootb, but a
bunch of new problems arise instead: Can't set global hotkeys for
recording in OBS, OBS recording performance is pretty bad, Gnome
folder windows start flickering somestimes, Gnome windows glitch out
when trying to resize them manually, Steam flickering sometimes,
browsers such as Firefox and Chromium have to be set to Wayland mode
in order to solve stuttering video playback issues, Nvidia-settings is
missing a bunch of settings and features when compared to X11... and
more
Hard- and Software:
- Ubuntu 23.04
- Nvidia driver version 525 (tested) from Ubuntu's additional drivers tool
- Core i7 7700
- 32 GB DDR4 RAM
- Lenovo Nvidia RTX A2000 workstation GPU
- TWO
[Desktop-packages] [Bug 2023500] Re: Ctrl or Shift + click don't work to select multiple files in listview
I can confirm that installing Nautilus 1:44.2.1-0ubuntu1 through Proposed solves the issue for me. -- 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 2023086] Re: Gtk-4 update breaks nautilus
Affects me as well. Cannot select multiple files in Detail view with CTRL. Shift still works for multiple files. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2023086 Title: Gtk-4 update breaks nautilus Status in gtk4 package in Ubuntu: Confirmed Bug description: It took me 2 hours to find out what the problem is. I reset Gnome desktop because I thought doing the good old dconf reset helps. Folks at Ubuntu - this kind of quality is just very annoying and unacceptable! Now to the bug. This is Ubuntu 23.04. Updates up-to-date. The latest update of libgtk-4 from version 4.10.1 to 4.10.3 breaks nautilus' move-to-trash behavior and copying is broken too. If you move a file to trash with libgtk-4.10.3 installed, the wrong icon is removed from the icon view. Just watch the attached video to see the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2023086/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2022155] Re: File selection dialog does not allow selecting multiple files using Ctrl
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gtk4 (Ubuntu) Status: New => Confirmed -- 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/2022155 Title: File selection dialog does not allow selecting multiple files using Ctrl Status in gtk+3.0 package in Ubuntu: Confirmed Status in gtk4 package in Ubuntu: Confirmed Bug description: I have no idea if I have filed this against the right package. It happens in both Firefox and Chrome, whatever provides their file selection dialog for uploads is apparently the problem, I don't know if that's gnome shell or something else. When I want to upload multiple files in a web browser, I can do that if I hit shift, and then click another file. But, that selects not just the two files that I clicked on, but every file in between them in the dialog (which is the expected behaviour when shift clicking in a file selection dialog). When I just want to select two files that are not displayed next to each other, I expect to be able to Ctrl+click on the files, and for them and only them to be selected. But, this doesn't happen, the second file does not get selected when I do that. 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: Fri Jun 2 10:08:32 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2022-08-04 (301 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 44.0-2ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-04-21 (41 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2022155/+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 2022155] Re: File selection dialog does not allow selecting multiple files using Ctrl
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gtk+3.0 (Ubuntu) Status: New => Confirmed -- 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/2022155 Title: File selection dialog does not allow selecting multiple files using Ctrl Status in gtk+3.0 package in Ubuntu: Confirmed Status in gtk4 package in Ubuntu: Confirmed Bug description: I have no idea if I have filed this against the right package. It happens in both Firefox and Chrome, whatever provides their file selection dialog for uploads is apparently the problem, I don't know if that's gnome shell or something else. When I want to upload multiple files in a web browser, I can do that if I hit shift, and then click another file. But, that selects not just the two files that I clicked on, but every file in between them in the dialog (which is the expected behaviour when shift clicking in a file selection dialog). When I just want to select two files that are not displayed next to each other, I expect to be able to Ctrl+click on the files, and for them and only them to be selected. But, this doesn't happen, the second file does not get selected when I do that. 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: Fri Jun 2 10:08:32 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2022-08-04 (301 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 44.0-2ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-04-21 (41 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2022155/+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 1971242] Re: printing PDF appears always grey, no color
** Also affects: okular (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: cups (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: atril (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: cups (Ubuntu Lunar) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1971242 Title: printing PDF appears always grey, no color Status in CUPS: Fix Released Status in atril package in Ubuntu: Confirmed Status in cups package in Ubuntu: Confirmed Status in okular package in Ubuntu: Confirmed Status in atril source package in Lunar: New Status in cups source package in Lunar: New Status in okular source package in Lunar: New Bug description: After upgrading from 20.04 LTS to 22.04 LTS I can't print colored PDF document. The print appears always b/w regardless color printing was enabled or not. Printing from LibreOffice produces a color print. This behavior (bug) is reproducible on three upgraded machines. It would be nice to have color print back again. To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1971242/+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
Hi,
Thanks for your contribution. Since Kinetic is going to be skipped and
the Jammy debdiff has been uploaded, I'm unsubscribing ubuntu-sponsors
from this bug. Feel free to re-subscribe the team should the need arise.
--
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 2017076] Re: default Chinese font in snap apps is ugly
> The first screenshot after the description is one from firefox showing an issue, reading the comments my understanding is that the report was about the firefox issue which has been resolved now Yes :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/2017076 Title: default Chinese font in snap apps is ugly Status in Snappy: Confirmed Status in fontconfig package in Ubuntu: Invalid Status in language-selector package in Ubuntu: Invalid Bug description: After installs Ubuntu 23.04 with Chinese language selected, the default font is chosen to AR PL UMing CN, which is very ugly. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: fontconfig 2.14.1-3ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Thu Apr 20 14:18:45 2023 InstallationDate: Installed on 2023-04-20 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=zh_CN.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: fontconfig UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/2017076/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1983112] Re: Appstream does not install config file
** Also affects: subiquity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1983112 Title: Appstream does not install config file Status in appstream package in Ubuntu: New Status in subiquity package in Ubuntu: New Bug description: After performing an Ubuntu automated server install, and installing the ubuntu-desktop-minimal package (which includes appstream as a dependency) then the snap-store, the snap-store will fail to display search results for .deb packages in the Ubuntu apt repositories. This is due to a missing config file (/etc/apt/apt.conf.d/50appstream) which is supposed to be installed as part of the appstream package. The issue can be fixed by re-installing appstream with the following command-line: apt-get -y install --reinstall -o Dpkg::Options::="--force-confmiss" appstream ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: appstream 0.15.2-2 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Fri Jul 29 15:25:44 2022 InstallationDate: Installed on 2022-07-27 (1 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: appstream UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017076] Re: default Chinese font in snap apps is ugly
> The installer is mentioned in the first sentence in the bug description. :) No it isn't? The description states 'After installs Ubuntu 23.04 with Chinese language' which refers to the installed system and not the installer? (just to be clear to me 'installer' is ubuntu-desktop- installer in lunar which is a flutter UI distributed as a snap that let you install Ubuntu) The first screenshot after the description is one from firefox showing an issue, reading the comments my understanding is that the report was about the firefox issue which has been resolved now -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/2017076 Title: default Chinese font in snap apps is ugly Status in Snappy: Confirmed Status in fontconfig package in Ubuntu: Invalid Status in language-selector package in Ubuntu: Invalid Bug description: After installs Ubuntu 23.04 with Chinese language selected, the default font is chosen to AR PL UMing CN, which is very ugly. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: fontconfig 2.14.1-3ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Thu Apr 20 14:18:45 2023 InstallationDate: Installed on 2023-04-20 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=zh_CN.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: fontconfig UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/2017076/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2023363] Re: Mouse input latency in GNOME 44.1 Wayland sessions is one frame higher than it was in 44.0 and earlier
** Changed in: mutter (Ubuntu Mantic) Status: In Progress => Fix Committed -- 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: Fix Committed Status in mutter source package in Lunar: In Progress Status in mutter source package in Mantic: Fix Committed 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 2023766] Re: Mouse cursor stutters but only over GUI elements that are animated
https://gitlab.gnome.org/Community/Ubuntu/mutter/-/commit/1987011f2d183a02160ae66afaf0e82218166521 ** Description changed: Mouse cursor stutters but only over GUI elements that are animated. You can notice this in Settings > Screen Display if the cursor moves over a list containing fade animations. But it doesn't stutter over non- - animated elements. + animated elements or constantly-animated elements. ** Changed in: mutter (Ubuntu) Status: In Progress => Fix Committed ** Also affects: mutter (Ubuntu Mantic) Importance: Medium Assignee: Daniel van Vugt (vanvugt) Status: Fix Committed ** Also affects: mutter (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu Lunar) Status: New => Triaged ** Changed in: mutter (Ubuntu Lunar) Importance: Undecided => Medium ** Changed in: mutter (Ubuntu Lunar) Assignee: (unassigned) => Daniel van Vugt (vanvugt) -- 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/2023766 Title: Mouse cursor stutters but only over GUI elements that are animated Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Lunar: Triaged Status in mutter source package in Mantic: Fix Committed Bug description: Mouse cursor stutters but only over GUI elements that are animated. You can notice this in Settings > Screen Display if the cursor moves over a list containing fade animations. But it doesn't stutter over non-animated elements or constantly-animated elements. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023766/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017076] Re: default Chinese font in snap apps is ugly
The installer is mentioned in the first sentence in the bug description. :) I was thinking that the installer still ships the old snap without the fix. Then, if the user opens FF before refreshing the snaps, they would still have the wrong default in FF. Maybe I'm wrong. I haven't done any tests. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/2017076 Title: default Chinese font in snap apps is ugly Status in Snappy: Confirmed Status in fontconfig package in Ubuntu: Invalid Status in language-selector package in Ubuntu: Invalid Bug description: After installs Ubuntu 23.04 with Chinese language selected, the default font is chosen to AR PL UMing CN, which is very ugly. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: fontconfig 2.14.1-3ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Thu Apr 20 14:18:45 2023 InstallationDate: Installed on 2023-04-20 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=zh_CN.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: fontconfig UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/2017076/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2023766] Re: Mouse cursor stutters but only over GUI elements that are animated
** Tags added: triple-buffering -- 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/2023766 Title: Mouse cursor stutters but only over GUI elements that are animated Status in mutter package in Ubuntu: In Progress Bug description: Mouse cursor stutters but only over GUI elements that are animated. You can notice this in Settings > Screen Display if the cursor moves over a list containing fade animations. But it doesn't stutter over non-animated elements. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023766/+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 1690719] Re: Mouse pointer randomly pauses/stutters in gnome shell Wayland sessions
This bug is now so old that we're probably seeing multiple different issues like: 1. CPU usage is too high in 44.x: https://gitlab.gnome.org/GNOME/mutter/-/issues/2459 (fixed in 45.0) 2. Bug 2023766. ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2459 https://gitlab.gnome.org/GNOME/mutter/-/issues/2459 -- 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/1690719 Title: Mouse pointer randomly pauses/stutters in gnome shell Wayland sessions Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: Triaged Bug description: The mouse pointer randomly pauses/stutters in Gnome Shell (Wayland). It's not reliably smooth like you would see in Xorg or Mir demo servers. Feels like there is a blocking call being made in a GUI thread that shouldn't have any blocking calls. Although it's not clear if this is just a problem with pointer input or the shell compositing in general. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.4-0ubuntu7 Architecture: amd64 Date: Mon May 15 13:23:22 2017 DisplayManager: lightdm GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1' InstallationDate: Installed on 2017-05-03 (12 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1690719/+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 2023763] Re: Wron directory items list after removal operation
*** This bug is a duplicate of bug 2022851 *** https://bugs.launchpad.net/bugs/2022851 Thank you for your bug report, that's bug #2022851 and a candidate fix is available for it ** 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/2023763 Title: Wron directory items list after removal operation Status in nautilus package in Ubuntu: New Bug description: Let assume that we have 4 items in directory - ABCD. When deleting the D, the D is actually removed but the list may be ABD. After reentering into directory the list is correct and is ABC. 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: Wed Jun 14 12:28:23 2023 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.compression' b'default-compression-format' b"'tar.xz'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' 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'maximized' b'true' InstallationDate: Installed on 2022-08-26 (291 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.48.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2023763/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017076] Re: default Chinese font in snap apps is ugly
@Gunnar, what's the issue with the installer? it's the first time the installer is mentioned on that report so I'm not sure to understand the question -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/2017076 Title: default Chinese font in snap apps is ugly Status in Snappy: Confirmed Status in fontconfig package in Ubuntu: Invalid Status in language-selector package in Ubuntu: Invalid Bug description: After installs Ubuntu 23.04 with Chinese language selected, the default font is chosen to AR PL UMing CN, which is very ugly. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: fontconfig 2.14.1-3ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Thu Apr 20 14:18:45 2023 InstallationDate: Installed on 2023-04-20 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=zh_CN.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: fontconfig UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/2017076/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2023766] [NEW] Mouse cursor stutters but only over GUI elements that are animated
Public bug reported: Mouse cursor stutters but only over GUI elements that are animated. You can notice this in Settings > Screen Display if the cursor moves over a list containing fade animations. But it doesn't stutter over non- animated elements. ** Affects: mutter (Ubuntu) Importance: Medium Assignee: Daniel van Vugt (vanvugt) Status: In Progress ** Tags: cursor mantic 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/2023766 Title: Mouse cursor stutters but only over GUI elements that are animated Status in mutter package in Ubuntu: In Progress Bug description: Mouse cursor stutters but only over GUI elements that are animated. You can notice this in Settings > Screen Display if the cursor moves over a list containing fade animations. But it doesn't stutter over non-animated elements. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023766/+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 2022954] Re: RDP and VNC fail when headless with no monitor (but work otherwise!)
** Changed in: gnome-remote-desktop Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2022954 Title: RDP and VNC fail when headless with no monitor (but work otherwise!) Status in GNOME Remote Desktop: New Status in mutter package in Ubuntu: Triaged Bug description: Steps to reproduce: * Install fresh Ubuntu 22.04.2 LTS * Enable RDP and VNC via sharing control panel * Test RDP and VNC, verify working * Unplug monitor * Try RDP. Authenticate, then connection closed with no display * Try VNC. Authenticate, then connection closed with no display * Plug monitor back in * Try RDP. Works! * Try VNC. Works! * Unplug monitor * Try RDP. AUthenticate, then connection closed with no display * Try VNC. Authenticate, then connection closed with no display * GOTO 10 Symptoms are present with both wayland and X11. 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 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jun 5 11:02:41 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [19da:b301] InstallationDate: Installed on 2023-06-01 (4 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: ZOTAC ZBOX-CI323NANO ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_j45abz@/vmlinuz-5.19.0-43-generic root=ZFS=rpool/ROOT/ubuntu_j45abz ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/11/2019 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B301P027 dmi.board.asset.tag: N/A dmi.board.name: ZBOX-CI323NANO dmi.board.vendor: ZOTAC dmi.board.version: XX dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrB301P027:bd09/11/2019:br5.11:svnZOTAC:pnZBOX-CI323NANO:pvrXX:rvnZOTAC:rnZBOX-CI323NANO:rvrXX:cvnDefaultstring:ct3:cvrDefaultstring:skuN/A: dmi.product.family: N/A dmi.product.name: ZBOX-CI323NANO dmi.product.sku: N/A dmi.product.version: XX dmi.sys.vendor: ZOTAC 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 N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-remote-desktop/+bug/2022954/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2023647] Re: Screens go into flicker cycle after going blank with external monitor(s)
** Changed in: mutter Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2023647 Title: Screens go into flicker cycle after going blank with external monitor(s) Status in Mutter: New Status in mutter package in Ubuntu: Incomplete Bug description: This happens whenever screen goes blank after inactivity with external monitors. When there is only one external monitor after few cycles the system recovers from the bug. When there are more than one monitors the system almost never recovers until unplugging extra monitor, as shown in video: https://photos.app.goo.gl/td6coEKFQd3DKe9C7 Happens on desktop and login screen. The same result with Wayland and X11. Does not depend on size of the monitor, cable (HDMI or USB-C) or is it connected via USB-C hub or directly. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.1-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jun 13 12:36:44 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-04-13 (60 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 44.1-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-04-21 (52 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2023647/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2023746] Re: [SRU] Add Quectel EM05-G/EM05-CN PID information to support WWAN LVFS
** Description changed: [SRU] Add Quectel EM05-G/EM05-CN PID information to support WWAN LVFS [ Impact ] The modemmanager v1.20.0 doesn't have Quectel EM05-G/EM05-CN PID (0x311/0x312) information. Fwupd can't base on modemmanager to identify the modem for supporting WWAN LVFS on a x86-based platform with Intel EHL, which is working with Jammy. (lp: #2019555) [ Test Plan ] Under Jammy environment, check fwupd (snap version) can identify EM05-G/EM05-CN modems to support WWAN LVFS on the target platform $ fwupdmgr refresh --force $ sudo fwupdmgr install # Select EM05-G/EM05-CN [ Where problems could occur ] The EM05-G/EM05-CN PID information is upstreamed to modemmanager v1.20.4 1. https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/b43cae70b078ee1af5b454cfd2b452e8dc711453 2. https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/e30b3a07a8d0f2bf5676cdcaf74da76f4af98b63 The Lunar and Mantic already working with modemmanager v1.20.4. - The Lenovo SE10 platform WWAN LVFS function works well on Lunar and Mantic. + The target platform WWAN LVFS function works well on Lunar and Mantic. The change parts just only add VID/PIDs for Quectel's new modems under the Quectel plugin. [ Other Info ] N/A -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/2023746 Title: [SRU] Add Quectel EM05-G/EM05-CN PID information to support WWAN LVFS Status in OEM Priority Project: New Status in modemmanager package in Ubuntu: Fix Released Status in modemmanager source package in Jammy: Fix Committed Bug description: [SRU] Add Quectel EM05-G/EM05-CN PID information to support WWAN LVFS [ Impact ] The modemmanager v1.20.0 doesn't have Quectel EM05-G/EM05-CN PID (0x311/0x312) information. Fwupd can't base on modemmanager to identify the modem for supporting WWAN LVFS on a x86-based platform with Intel EHL, which is working with Jammy. (lp: #2019555) [ Test Plan ] Under Jammy environment, check fwupd (snap version) can identify EM05-G/EM05-CN modems to support WWAN LVFS on the target platform $ fwupdmgr refresh --force $ sudo fwupdmgr install # Select EM05-G/EM05-CN [ Where problems could occur ] The EM05-G/EM05-CN PID information is upstreamed to modemmanager v1.20.4 1. https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/b43cae70b078ee1af5b454cfd2b452e8dc711453 2. https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/e30b3a07a8d0f2bf5676cdcaf74da76f4af98b63 The Lunar and Mantic already working with modemmanager v1.20.4. The target platform WWAN LVFS function works well on Lunar and Mantic. The change parts just only add VID/PIDs for Quectel's new modems under the Quectel plugin. [ Other Info ] N/A To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2023746/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2023763] [NEW] Wron directory items list after removal operation
Public bug reported: Let assume that we have 4 items in directory - ABCD. When deleting the D, the D is actually removed but the list may be ABD. After reentering into directory the list is correct and is ABC. 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: Wed Jun 14 12:28:23 2023 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.compression' b'default-compression-format' b"'tar.xz'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' 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'maximized' b'true' InstallationDate: Installed on 2022-08-26 (291 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.48.0-1ubuntu1 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar wayland-session ** Attachment added: "nautilus-bug.pdf" https://bugs.launchpad.net/bugs/2023763/+attachment/5679643/+files/nautilus-bug.pdf -- 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/2023763 Title: Wron directory items list after removal operation Status in nautilus package in Ubuntu: New Bug description: Let assume that we have 4 items in directory - ABCD. When deleting the D, the D is actually removed but the list may be ABD. After reentering into directory the list is correct and is ABC. 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: Wed Jun 14 12:28:23 2023 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.compression' b'default-compression-format' b"'tar.xz'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' 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'maximized' b'true' InstallationDate: Installed on 2022-08-26 (291 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.48.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2023763/+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 2023759] Re: Remote desktop does not function
I assumed it would be fixed with the update to 44.2 https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2988 https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2987 https://gitlab.gnome.org/GNOME/mutter/-/issues/2783 https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2804 from this thread https://discussion.fedoraproject.org/t/after-upgrading-to-fedora-38-cannot-connect-to-computer-using-remote-desktop/82353?page=2 ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2783 https://gitlab.gnome.org/GNOME/mutter/-/issues/2783 -- 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/2023759 Title: Remote desktop does not function Status in gnome-shell package in Ubuntu: Incomplete Bug description: When i use the bulit in RDP of gnome it just shows a black screen if I use VNC I can use it for a few second before it stops responding to the mouse. I rolled back to 44.0.2 and now its fine afer reinstalling the whole shell. Looking in the fedora comments there was a comment that mutter broke something in 44.1 Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2023759/+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 2023759] Re: Remote desktop does not function
Also 44.2 is already in Ubuntu 23.10 and in proposed for 23.04. Please check to see if 44.2 has fixed the issue. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2023759 Title: Remote desktop does not function Status in gnome-shell package in Ubuntu: Incomplete Bug description: When i use the bulit in RDP of gnome it just shows a black screen if I use VNC I can use it for a few second before it stops responding to the mouse. I rolled back to 44.0.2 and now its fine afer reinstalling the whole shell. Looking in the fedora comments there was a comment that mutter broke something in 44.1 Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2023759/+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 2023759] Re: Remote desktop does not function
Can you provide a link to "the fedora comments"? -- 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/2023759 Title: Remote desktop does not function Status in gnome-shell package in Ubuntu: New Bug description: When i use the bulit in RDP of gnome it just shows a black screen if I use VNC I can use it for a few second before it stops responding to the mouse. I rolled back to 44.0.2 and now its fine afer reinstalling the whole shell. Looking in the fedora comments there was a comment that mutter broke something in 44.1 Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2023759/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017076] Re: default Chinese font in snap apps is ugly
This seems to be fixed in Firefox latest/stable/ubuntu-23.04 114.0.1. @Sebastien: But that doesn't fix the 23.04 installer, does it? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/2017076 Title: default Chinese font in snap apps is ugly Status in Snappy: Confirmed Status in fontconfig package in Ubuntu: Invalid Status in language-selector package in Ubuntu: Invalid Bug description: After installs Ubuntu 23.04 with Chinese language selected, the default font is chosen to AR PL UMing CN, which is very ugly. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: fontconfig 2.14.1-3ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Thu Apr 20 14:18:45 2023 InstallationDate: Installed on 2023-04-20 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=zh_CN.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: fontconfig UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/2017076/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2023759] [NEW] Remote desktop does not function
Public bug reported: When i use the bulit in RDP of gnome it just shows a black screen if I use VNC I can use it for a few second before it stops responding to the mouse. I rolled back to 44.0.2 and now its fine afer reinstalling the whole shell. Looking in the fedora comments there was a comment that mutter broke something in 44.1 Thanks ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2023759 Title: Remote desktop does not function Status in gnome-shell package in Ubuntu: New Bug description: When i use the bulit in RDP of gnome it just shows a black screen if I use VNC I can use it for a few second before it stops responding to the mouse. I rolled back to 44.0.2 and now its fine afer reinstalling the whole shell. Looking in the fedora comments there was a comment that mutter broke something in 44.1 Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2023759/+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 1988836] Re: LRMv7: Enable the open NVIDIA kernel modules
** 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/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: Fix Released Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Released Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+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] Re: PDF fonts messed up in evince, mupdf, are fine in chrome
Thank you for your bug report. Is there any chance you could try to get a small example not including private informations? You could perhaps try to use 'pdfseparate' to extract one page of the document if there are any without private data and see if that also show the issue? -- 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
