[Desktop-packages] [Bug 2062082] Re: 24.04 Wayland vs Nautilus performance problem
BTW Chrome probably still defaults to using X11 instead of Wayland, and so you likely would hit bug 1970389. That's why I mention xlsclients... It's also why we default to Xorg for Nvidia systems and recommend you use Xorg with the Nvidia proprietary driver. P.S. Is "zink Vulkan 1.3" something you configured or was that the system default? Where did you get that information from? -- 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/2062082 Title: 24.04 Wayland vs Nautilus performance problem Status in nautilus package in Ubuntu: Incomplete Bug description: Apologies if I have misfiled this bug - this is a report of an issue affecting Wayland in Ubuntu 24.04 beta. Using 24.04 beta logging in with Wayland. Nautilus has very significant performance issues. Doesn't happen when logging in with Xorg instead of Wayland. Opening Nautilus windows - including normal windows navigation, and the file download location dialogue in things like Chrome - extremely slow. Takes approx. 10 seconds to process user double clicking to open folder. Attempting to drag folder across screen usually doesn't work, or takes a very long time. Not very skilled at debugging, but programmes like Gimp, which has its own built-in folder explorer for choosing a location to save an image, do not have this problem. Ubuntu 24.04 with X does not have this problem. No performance issues have been noticed with folder navigation, stat'ing files etc. over the command line. It is only nautilus and Wayland that give me this issue, so I suspect it is not an issue with my SSD. The following output was observed when starting nautilus over the command line: /home/me/ $ nautilus . ** Message: 23:43:50.560: Connecting to org.freedesktop.Tracker3.Miner.Files libEGL warning: egl: failed to create dri2 screen After approx. 10 seconds, the folder opened on screen. I double clicked on a sub directory, and it took about 9 seconds to open. I have attempted to show that this is not an issue with my SSD here: /home/me/ $ date; cd workspace/; touch foo.txt; ls foo*; cd ../; date; Wed Apr 17 11:58:16 PM BST 2024 foo.txt Wed Apr 17 11:58:16 PM BST 2024 As you can see, no unusual slowdown was observed. Obtaining the following setting for my bug report, I note that the 'Settings' GUI utility is among the areas affect by my very significant system slowdown. I have copied some details about my system including its graphics card in case that helps. # System Details Report --- ## Report details - **Date generated:** 2024-04-17 23:59:54 ## Hardware Information: - **Hardware Model:** ASUS ROG STRIX B550-F GAMING - **Memory:** 32.0 GiB - **Processor:** AMD Ryzen™ 7 5800X × 16 - **Graphics:**zink Vulkan 1.3(NVIDIA GeForce GTX 1050 Ti (NVIDIA_PROPRIETARY)) - **Disk Capacity:** 2.0 TB ## Software Information: - **Firmware Version:**2006 - **OS Name:** Ubuntu Noble Numbat (development branch) - **OS Build:**(null) - **OS Type:** 64-bit - **GNOME Version:** 46 - **Windowing System:**Wayland - **Kernel Version:** Linux 6.8.0-22-generic ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..09.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 545.29.06 Thu Nov 16 01:59:08 UTC 2023 GCC version: ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Apr 17 23:44:47 2024 DistUpgraded: 2024-04-11 13:09:51,904 DEBUG migrateToDeb822Sources() DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA
[Desktop-packages] [Bug 2062082] Re: 24.04 Wayland vs Nautilus performance problem
Thanks for the bug report. Please try: 1. sudo rm /dev/dri/card0 # to work around bug 2060268, and then log in again. Did that solve it? 2. When the problem starts happening please open a Terminal and run: journalctl -b0 > journal.txt xlsclients > xclients.txt and attach the resulting text files here. 3. While the problem is happening run 'top' in a Terminal window and tell us which process (if any) is using high CPU. ** Package changed: xorg (Ubuntu) => nautilus (Ubuntu) ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2062082 Title: 24.04 Wayland vs Nautilus performance problem Status in nautilus package in Ubuntu: Incomplete Bug description: Apologies if I have misfiled this bug - this is a report of an issue affecting Wayland in Ubuntu 24.04 beta. Using 24.04 beta logging in with Wayland. Nautilus has very significant performance issues. Doesn't happen when logging in with Xorg instead of Wayland. Opening Nautilus windows - including normal windows navigation, and the file download location dialogue in things like Chrome - extremely slow. Takes approx. 10 seconds to process user double clicking to open folder. Attempting to drag folder across screen usually doesn't work, or takes a very long time. Not very skilled at debugging, but programmes like Gimp, which has its own built-in folder explorer for choosing a location to save an image, do not have this problem. Ubuntu 24.04 with X does not have this problem. No performance issues have been noticed with folder navigation, stat'ing files etc. over the command line. It is only nautilus and Wayland that give me this issue, so I suspect it is not an issue with my SSD. The following output was observed when starting nautilus over the command line: /home/me/ $ nautilus . ** Message: 23:43:50.560: Connecting to org.freedesktop.Tracker3.Miner.Files libEGL warning: egl: failed to create dri2 screen After approx. 10 seconds, the folder opened on screen. I double clicked on a sub directory, and it took about 9 seconds to open. I have attempted to show that this is not an issue with my SSD here: /home/me/ $ date; cd workspace/; touch foo.txt; ls foo*; cd ../; date; Wed Apr 17 11:58:16 PM BST 2024 foo.txt Wed Apr 17 11:58:16 PM BST 2024 As you can see, no unusual slowdown was observed. Obtaining the following setting for my bug report, I note that the 'Settings' GUI utility is among the areas affect by my very significant system slowdown. I have copied some details about my system including its graphics card in case that helps. # System Details Report --- ## Report details - **Date generated:** 2024-04-17 23:59:54 ## Hardware Information: - **Hardware Model:** ASUS ROG STRIX B550-F GAMING - **Memory:** 32.0 GiB - **Processor:** AMD Ryzen™ 7 5800X × 16 - **Graphics:**zink Vulkan 1.3(NVIDIA GeForce GTX 1050 Ti (NVIDIA_PROPRIETARY)) - **Disk Capacity:** 2.0 TB ## Software Information: - **Firmware Version:**2006 - **OS Name:** Ubuntu Noble Numbat (development branch) - **OS Build:**(null) - **OS Type:** 64-bit - **GNOME Version:** 46 - **Windowing System:**Wayland - **Kernel Version:** Linux 6.8.0-22-generic ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..09.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 545.29.06 Thu Nov 16 01:59:08 UTC 2023 GCC version: ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Apr 17 23:44:47 2024 DistUpgraded: 2024-04-11 13:09:51,904 DEBUG migrateToDeb822Sources() DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including
[Desktop-packages] [Bug 2062082] Re: 24.04 Wayland vs Nautilus performance problem
** Tags added: nvidia nvidia-wayland -- 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/2062082 Title: 24.04 Wayland vs Nautilus performance problem Status in xorg package in Ubuntu: New Bug description: Apologies if I have misfiled this bug - this is a report of an issue affecting Wayland in Ubuntu 24.04 beta. Using 24.04 beta logging in with Wayland. Nautilus has very significant performance issues. Doesn't happen when logging in with Xorg instead of Wayland. Opening Nautilus windows - including normal windows navigation, and the file download location dialogue in things like Chrome - extremely slow. Takes approx. 10 seconds to process user double clicking to open folder. Attempting to drag folder across screen usually doesn't work, or takes a very long time. Not very skilled at debugging, but programmes like Gimp, which has its own built-in folder explorer for choosing a location to save an image, do not have this problem. Ubuntu 24.04 with X does not have this problem. No performance issues have been noticed with folder navigation, stat'ing files etc. over the command line. It is only nautilus and Wayland that give me this issue, so I suspect it is not an issue with my SSD. The following output was observed when starting nautilus over the command line: /home/me/ $ nautilus . ** Message: 23:43:50.560: Connecting to org.freedesktop.Tracker3.Miner.Files libEGL warning: egl: failed to create dri2 screen After approx. 10 seconds, the folder opened on screen. I double clicked on a sub directory, and it took about 9 seconds to open. I have attempted to show that this is not an issue with my SSD here: /home/me/ $ date; cd workspace/; touch foo.txt; ls foo*; cd ../; date; Wed Apr 17 11:58:16 PM BST 2024 foo.txt Wed Apr 17 11:58:16 PM BST 2024 As you can see, no unusual slowdown was observed. Obtaining the following setting for my bug report, I note that the 'Settings' GUI utility is among the areas affect by my very significant system slowdown. I have copied some details about my system including its graphics card in case that helps. # System Details Report --- ## Report details - **Date generated:** 2024-04-17 23:59:54 ## Hardware Information: - **Hardware Model:** ASUS ROG STRIX B550-F GAMING - **Memory:** 32.0 GiB - **Processor:** AMD Ryzen™ 7 5800X × 16 - **Graphics:**zink Vulkan 1.3(NVIDIA GeForce GTX 1050 Ti (NVIDIA_PROPRIETARY)) - **Disk Capacity:** 2.0 TB ## Software Information: - **Firmware Version:**2006 - **OS Name:** Ubuntu Noble Numbat (development branch) - **OS Build:**(null) - **OS Type:** 64-bit - **GNOME Version:** 46 - **Windowing System:**Wayland - **Kernel Version:** Linux 6.8.0-22-generic ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..09.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 545.29.06 Thu Nov 16 01:59:08 UTC 2023 GCC version: ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Apr 17 23:44:47 2024 DistUpgraded: 2024-04-11 13:09:51,904 DEBUG migrateToDeb822Sources() DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] InstallationDate: Installed on 2024-04-11 (6 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) MachineType: ASUS System Product Name ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=
[Desktop-packages] [Bug 2062115] [NEW] Connected Google account, but Drive is not shown
Public bug reported: After the recent updates of Ubuntu 24.04 Noble Numbat, Nautilus is unable to access Google Drive: it is not shown. I cannot find any error message in the logs. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-online-accounts 3.50.0-4ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Apr 18 06:56:05 2024 InstallationDate: Installed on 2023-07-05 (288 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.init.d.apport: [modified] mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00 ** Affects: gnome-online-accounts (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/2062115 Title: Connected Google account, but Drive is not shown Status in gnome-online-accounts package in Ubuntu: New Bug description: After the recent updates of Ubuntu 24.04 Noble Numbat, Nautilus is unable to access Google Drive: it is not shown. I cannot find any error message in the logs. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-online-accounts 3.50.0-4ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Apr 18 06:56:05 2024 InstallationDate: Installed on 2023-07-05 (288 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.init.d.apport: [modified] mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/2062115/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2062078] Re: Mouse animations do not follow accent colors
This bug was fixed in the package gnome-control-center - 1:46.0.1-1ubuntu4 --- gnome-control-center (1:46.0.1-1ubuntu4) noble; urgency=medium * d/p/ubuntu/mouse-Add-animations-following-the-accent-colors.patch: Regenerate the ubuntu-accented assets using the same source blender file as in GNOME and include the missing animations (LP: #2062078) -- Marco Trevisan (Treviño) Thu, 18 Apr 2024 00:50:26 +0200 ** Changed in: gnome-control-center (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2062078 Title: Mouse animations do not follow accent colors Status in gnome-control-center package in Ubuntu: Fix Released Bug description: This is a regression from previous releases, the mouse animations do not follow the user-selected accent color The missing assets needs to be regenerated with this script: - https://gitlab.gnome.org/-/snippets/5549 Sources are: - https://gitlab.gnome.org/Teams/Design/settings-mockups/-/commits/master/mouse-and-touchpad/src/mouse-touchpad-v2.blend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2062078/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2061857] Re: [FFe] enable the new GNOME OneDrive backend
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gvfs (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/2061857 Title: [FFe] enable the new GNOME OneDrive backend Status in gnome-online-accounts package in Ubuntu: Confirmed Status in gvfs package in Ubuntu: Confirmed Bug description: One of the new features of the new GNOME 46 is the support of Microsoft OneDrive accounts. The code relies on a new library 'msgraph'. The MIR bug #2060035 just got approved and such we would like to turn on the option now in Noble. The changes are in - gnome-online-accounts, adding a new provider for OneDrive The package with the change has been built in the desktop ppa https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/ppa/+sourcepub/15971851/+listing-archive-extra The change is basically adding the libmsgraph-dev Build-Depends in debian/control and changing the option to true in debian/rules - gvfs, adding a new backend to be able to browse those locations from nautilus The package is similar built in our ppa https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/ppa/+sourcepub/15972025/+listing-archive-extra And the change are similar Build-Depends/rules option The regression potential is low since those are new backends and not changing existing features. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/2061857/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2061857] Re: [FFe] enable the new GNOME OneDrive backend
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-online-accounts (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/2061857 Title: [FFe] enable the new GNOME OneDrive backend Status in gnome-online-accounts package in Ubuntu: Confirmed Status in gvfs package in Ubuntu: Confirmed Bug description: One of the new features of the new GNOME 46 is the support of Microsoft OneDrive accounts. The code relies on a new library 'msgraph'. The MIR bug #2060035 just got approved and such we would like to turn on the option now in Noble. The changes are in - gnome-online-accounts, adding a new provider for OneDrive The package with the change has been built in the desktop ppa https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/ppa/+sourcepub/15971851/+listing-archive-extra The change is basically adding the libmsgraph-dev Build-Depends in debian/control and changing the option to true in debian/rules - gvfs, adding a new backend to be able to browse those locations from nautilus The package is similar built in our ppa https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/ppa/+sourcepub/15972025/+listing-archive-extra And the change are similar Build-Depends/rules option The regression potential is low since those are new backends and not changing existing features. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/2061857/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2061739] Re: crash in meta_wayland_transaction_commit
A lot of extensions are listed in ShellJournal.txt but maybe they're not active? Looks like they came from 'gnome-shell-extensions' which we don't install by default. So try uninstalling 'gnome-shell-extensions'. -- 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/2061739 Title: crash in meta_wayland_transaction_commit Status in gnome-shell package in Ubuntu: Incomplete Bug description: Hi, The system is Ubuntu Noble with a regular daily updates. This happens many times since few days ago but not clear at all how to reproduce it. Regards, Patrice ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-shell 46.0-0ubuntu4 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Apr 16 09:26:16 2024 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2019-05-24 (1789 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 46.0-1ubuntu6 SourcePackage: gnome-shell UpgradeStatus: Upgraded to noble on 2019-05-28 (1785 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2061739/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2061985] Re: Other users are also highlighted although unselected
I noticed similar theme weirdness in the overview (search results). It's probably Yaru. ** Tags added: noble visual-quality ** Package changed: gdm3 (Ubuntu) => gnome-shell (Ubuntu) ** Also affects: yaru-theme (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/2061985 Title: Other users are also highlighted although unselected Status in gnome-shell package in Ubuntu: New Status in yaru-theme package in Ubuntu: New Bug description: If there is more than one user available, both are highlighted in gray, although only one is highlighted with a orange border. Ubuntu 24.04, gdm 46.0-2ubuntu1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2061985/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2062046] Re: Nautilus icons are not using yaru theme
** Bug watch added: github.com/ubuntu/yaru/issues #4055 https://github.com/ubuntu/yaru/issues/4055 ** Also affects: yaru via https://github.com/ubuntu/yaru/issues/4055 Importance: Unknown Status: Unknown ** Tags added: noble -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/2062046 Title: Nautilus icons are not using yaru theme Status in Yaru Theme: Unknown Status in yaru-theme package in Ubuntu: Fix Committed Bug description: As reported upstream: https://github.com/ubuntu/yaru/issues/4055 The nautilus search icons are using adwaita theme, and they don't fit well with the whole system theme. To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/2062046/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2060692] Re: cupsd 2.4.7-1.2ubuntu5 on noble crashes due to recently backported commits from 2.4.x git
This bug was fixed in the package cups - 2.4.7-1.2ubuntu7 --- cups (2.4.7-1.2ubuntu7) noble; urgency=low * Another fix for crash caused by the fix of the background polling of printer capability information in ...ubuntu4. Added also commit 6aeb03b from 2.4.x GIT branch to the patch (LP: #2060692, Upstream issue #934, pull request #935). -- Till Kamppeter Fri, 12 Apr 2024 22:13:19 +0200 ** Changed in: cups (Ubuntu) Status: Fix Committed => Fix Released -- 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/2060692 Title: cupsd 2.4.7-1.2ubuntu5 on noble crashes due to recently backported commits from 2.4.x git Status in cups package in Ubuntu: Fix Released Bug description: While checking out the latest versions of cups (2.4.7-1.2ubuntu4 and 2.4.7-1.2ubuntu5), I noticed that cupsd crashes consistently after closing my Firefox tab / window. The title of the crash (from the bug-report window) is "cupsd crashed with SIGSEGV in ???()" I'm running the noble-desktop-amd64.iso from 2024-03-25 after applying some updates from the noble and noble-proposed pockets. Reproduction steps: 1. Open Firefox and manage CUPS on http://localhost:631 2. Go to Administration -> Printers -> Add Printer and choose your printer 3. Add your printer (I used the ipps:// protocol to manage the printer) 4. After clicking the "Add printer" button, immediately close your Firefox tab 5. cupsd will crash and Ubuntu will display a bug-report popup Versions: Firefox - 124.0.1-1 r4033 CUPS - 2.4.7-1.2ubuntu5 Printer: Lexmark MS415dn (supported) I am unable to reproduce this bug on versions prior to 2.4.7-1.2ubuntu4 (Tried with 2.4.7-1.2ubuntu1 and 2.4.7-1.2ubuntu2). Versions 2.4.7-1.2ubuntu4 and 2.4.7-1.2ubuntu5 only backported commits from the 2.4.x upstream git branch, so I also opened an issue on GitHub: https://github.com/OpenPrinting/cups/issues/934 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2060692/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2062044] Re: Dock icons for focused applications are not highlighted
** This bug is no longer a duplicate of bug 2061729 Ubuntu Dock icon highlight is practically invisible when a white or grey window is behind it -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/2062044 Title: Dock icons for focused applications are not highlighted Status in yaru-theme package in Ubuntu: In Progress Bug description: The icon for the application that is currently focused should be highlighted but this is not the case in noble. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/2062044/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2062082] Re: 24.04 Wayland vs Nautilus performance problem
-- 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/2062082 Title: 24.04 Wayland vs Nautilus performance problem Status in xorg package in Ubuntu: New Bug description: Apologies if I have misfiled this bug - this is a report of an issue affecting Wayland in Ubuntu 24.04 beta. Using 24.04 beta logging in with Wayland. Nautilus has very significant performance issues. Doesn't happen when logging in with Xorg instead of Wayland. Opening Nautilus windows - including normal windows navigation, and the file download location dialogue in things like Chrome - extremely slow. Takes approx. 10 seconds to process user double clicking to open folder. Attempting to drag folder across screen usually doesn't work, or takes a very long time. Not very skilled at debugging, but programmes like Gimp, which has its own built-in folder explorer for choosing a location to save an image, do not have this problem. Ubuntu 24.04 with X does not have this problem. No performance issues have been noticed with folder navigation, stat'ing files etc. over the command line. It is only nautilus and Wayland that give me this issue, so I suspect it is not an issue with my SSD. The following output was observed when starting nautilus over the command line: /home/me/ $ nautilus . ** Message: 23:43:50.560: Connecting to org.freedesktop.Tracker3.Miner.Files libEGL warning: egl: failed to create dri2 screen After approx. 10 seconds, the folder opened on screen. I double clicked on a sub directory, and it took about 9 seconds to open. I have attempted to show that this is not an issue with my SSD here: /home/me/ $ date; cd workspace/; touch foo.txt; ls foo*; cd ../; date; Wed Apr 17 11:58:16 PM BST 2024 foo.txt Wed Apr 17 11:58:16 PM BST 2024 As you can see, no unusual slowdown was observed. Obtaining the following setting for my bug report, I note that the 'Settings' GUI utility is among the areas affect by my very significant system slowdown. I have copied some details about my system including its graphics card in case that helps. # System Details Report --- ## Report details - **Date generated:** 2024-04-17 23:59:54 ## Hardware Information: - **Hardware Model:** ASUS ROG STRIX B550-F GAMING - **Memory:** 32.0 GiB - **Processor:** AMD Ryzen™ 7 5800X × 16 - **Graphics:**zink Vulkan 1.3(NVIDIA GeForce GTX 1050 Ti (NVIDIA_PROPRIETARY)) - **Disk Capacity:** 2.0 TB ## Software Information: - **Firmware Version:**2006 - **OS Name:** Ubuntu Noble Numbat (development branch) - **OS Build:**(null) - **OS Type:** 64-bit - **GNOME Version:** 46 - **Windowing System:**Wayland - **Kernel Version:** Linux 6.8.0-22-generic ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..09.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 545.29.06 Thu Nov 16 01:59:08 UTC 2023 GCC version: ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Apr 17 23:44:47 2024 DistUpgraded: 2024-04-11 13:09:51,904 DEBUG migrateToDeb822Sources() DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] InstallationDate: Installed on 2024-04-11 (6 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) MachineType: ASUS System Product Name ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine:
[Desktop-packages] [Bug 2062044] Re: Dock icons for focused applications are not highlighted
*** This bug is a duplicate of bug 2061729 *** https://bugs.launchpad.net/bugs/2061729 I think you mean bug 2061729? ** This bug has been marked a duplicate of bug 2061729 Ubuntu Dock icon highlight is practically invisible when a white or grey window is behind it -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/2062044 Title: Dock icons for focused applications are not highlighted Status in yaru-theme package in Ubuntu: In Progress Bug description: The icon for the application that is currently focused should be highlighted but this is not the case in noble. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/2062044/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2062089] Re: [NVIDIA] Ubuntu 24.04 detects a third unknown monitor (instead of two)
*** This bug is a duplicate of bug 2060268 *** https://bugs.launchpad.net/bugs/2060268 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 2060268, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Package changed: gnome-shell (Ubuntu) => nvidia-graphics-drivers-535 (Ubuntu) ** This bug has been marked a duplicate of bug 2060268 Phantom 46" monitor (simpledrm) shown in Settings after installing the Nvidia driver -- 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/2062089 Title: [NVIDIA] Ubuntu 24.04 detects a third unknown monitor (instead of two) Status in nvidia-graphics-drivers-535 package in Ubuntu: New Bug description: I recently installed Ubuntu 24.04 for testing purposes and have encountered an unexpected issue. The 'Displays' configuration indicates the presence of three monitors, like this: 1) Dell Inc. 27" 2) Dell Inc. 27" 3) Unknown Display However, I only have two displays and not a third one. When moving the cursor to the extreme right corner of the screen, the entire display shifts to the right. Below are the pertinent details: Configuration: - Utilizing: two monitors - Graphics Card: NVIDIA GeForce GTX 1660 SUPER - Environment: Xorg - Driver Version: Nvidia driver 535.161.07 This behavior disrupts normal workflow and consistency in display management. Any insights or solutions to address this issue would be greatly appreciated. Thank you for your attention to this matter. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-shell 46.0-0ubuntu5 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 17 21:43:13 2024 DisplayManager: gdm3 InstallationDate: Installed on 2024-04-17 (0 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240417.2) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 46.0-1ubuntu7 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/nvidia-graphics-drivers-535/+bug/2062089/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1383184] Business Opportunity
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1383184 Title: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] is not supported Status in HWE Next: Fix Released Status in HWE Next wily series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Invalid Status in linux source package in Wily: Fix Released Status in linux-firmware source package in Wily: Fix Released Bug description: = CURRENT STATUS: Wily(15.10) could not work with and don't need Adam's dkms package 1.0 or 1.1 Wily(15.10) has already fixed the driver part, and the firmware part is in progress. For now, you guys could use 15.10(purge the ath10k-dkms if you tried installing it), and make a copy of https://git.kernel.org/cgit/linux/kernel/git/firmware/linux- firmware.git/plain/ath10k/QCA6174 into /lib/firmware/ath10k/ 15.10 will work in a week by a simple `apt upgrade` Distros before 15.10(lower than 4.2 kernel) please keep using the dkms(which will be relocated soon) = Card detail: Qualcomm Atheros Device [168c:003e] (rev 20) Subsystem: Bigfoot Networks, Inc. Device [1a56:1525] This is on a fully updated Ubuntu Server 14.04 installation, with the ubuntu-desktop environment installed. This happened in order to get the md raid drivers for raid0 on my system, as the desktop version doesn't support them. --- ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: matanis2333 F pulseaudio /dev/snd/controlC0: matanis2333 F pulseaudio CRDA: Error: [Errno 2] No such file or directory CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=1b192ee3-f592-43e9-bdcf-08b91c0aa9b6 InstallationDate: Installed on 2014-10-16 (3 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.3) IwConfig: p2p1 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd. GT72 2QE NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic.efi.signed root=UUID=80998dbb-1f89-4eda-be90-25e35e1c0a90 ro ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 RelatedPackageVersions: linux-restricted-modules-3.13.0-37-generic N/A linux-backports-modules-3.13.0-37-generic N/A linux-firmware 1.127.7 RfKill: Tags: trusty Uname: Linux 3.13.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1781IMS.10D dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1781 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1781IMS.10D:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT722QE:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1781:rvrREV0.C:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: GT72 2QE dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. Qualcomm Atheros Device [168c:003e] (rev 20) mainline commit d63955b33b3bee45d784ffdfafeb93076c765660 [6.221281] ath10k_pci :02:00.0: pci irq msi interrupts 1 irq_mode 0 reset_mode 0 [6.417386] ath10k_pci :02:00.0: Direct firmware load for ath10k/cal-pci-:02:00.0.bin failed with error -2 [6.417404] ath10k_pci :02:00.0: Direct firmware load for ath10k/QCA6174/hw2.1/board-pci-168c:003e:17aa:3044.bin failed with error -2 [6.417407] ath10k_pci :02:00.0: failed to load spec board file, falling back to generic: -2 [6.417416] ath10k_pci :02:00.0: Direct firmware load for ath10k/QCA6174/hw2.1/board.bin failed with error -2 [6.417418] ath10k_pci :02:00.0: failed to fetch generic board data: -2 [6.417420] ath10k_pci :02:00.0: failed to fetch board file: -2 [6.417421] ath10k_pci :02:00.0: could not fetch firmware files (-2) [6.417423] ath10k_pci :02:00.0: could not probe fw (-2) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1383184/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post
[Desktop-packages] [Bug 1207812] Business Opportunity
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1207812 Title: [FFe] Update libimobiledevice to support iOS 7, fix Trust Prompt Looping Status in Linux Mint: Fix Released Status in libimobiledevice package in Ubuntu: Fix Released Status in libimobiledevice package in Debian: Fix Released Bug description: The latest libimobiledevice release 1.1.5 is a year old and does not support iOS7 devices. Most iOS devices have been updated to iOS7 by now, so currently the library is broken in functionality for most users. The git snapshot has been tested to work, but there seems to be no new upstream release being prepared for the time being. The new git snapshot includes several fixes, including the security fix that was previously patched on top of 1.1.5 in Ubuntu. Packaging branch merge request attached to this bug report. --- Original report --- The iPhone reporting "Trust the currently connected computer?" Trust/Don't Trust. This then happens in a continous loop when clicking Trust. --- ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nrawlins 2068 F pulseaudio DistroRelease: Ubuntu 13.04 HibernationDevice: RESUME=UUID=f089ceb3-a892-4f99-92d3-a61c99bb2feb InstallationDate: Installed on 2013-08-15 (3 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Sony Corporation VGN-SR29XN_S MarkForUpload: True Package: linux 3.8.0.27.45 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-27-generic root=UUID=7656e9f3-5437-4e10-a467-62d52144f471 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 RelatedPackageVersions: linux-restricted-modules-3.8.0-27-generic N/A linux-backports-modules-3.8.0-27-generic N/A linux-firmware1.106 Tags: raring Uname: Linux 3.8.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 08/28/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R1130Y1 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR1130Y1:bd08/28/2009:svnSonyCorporation:pnVGN-SR29XN_S:pvrC6017UKK:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VGN-SR29XN_S dmi.product.version: C6017UKK dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1207812/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2062089] Re: [NVIDIA] Ubuntu 24.04 detects three monitors instead of two
** Summary changed: - [NVIDIA] Cursor movement to right corner causes screen shift + [NVIDIA] Ubuntu 24.04 detects three monitors instead of two ** Summary changed: - [NVIDIA] Ubuntu 24.04 detects three monitors instead of two + [NVIDIA] Ubuntu 24.04 detects a third unknown monitor (instead of two) ** Description changed: I recently installed Ubuntu 24.04 for testing purposes and have - encountered an unexpected issue. When moving the cursor to the extreme - right corner of the screen, the entire display shifts to the right. - Below are the pertinent details: + encountered an unexpected issue. + + The 'Displays' configuration indicates the presence of three monitors, like this: + 1) Dell Inc. 27" + 2) Dell Inc. 27" + 3) Unknown Display + However, I only have two displays and not a third one. + + + When moving the cursor to the extreme right corner of the screen, the entire display shifts to the right. Below are the pertinent details: Configuration: - Utilizing: two monitors - Graphics Card: NVIDIA GeForce GTX 1660 SUPER - Environment: Xorg - Driver Version: Nvidia driver 535.161.07 This behavior disrupts normal workflow and consistency in display management. Any insights or solutions to address this issue would be greatly appreciated. Thank you for your attention to this matter. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-shell 46.0-0ubuntu5 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 17 21:43:13 2024 DisplayManager: gdm3 InstallationDate: Installed on 2024-04-17 (0 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240417.2) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 46.0-1ubuntu7 SourcePackage: gnome-shell 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 in Ubuntu. https://bugs.launchpad.net/bugs/2062089 Title: [NVIDIA] Ubuntu 24.04 detects a third unknown monitor (instead of two) Status in gnome-shell package in Ubuntu: New Bug description: I recently installed Ubuntu 24.04 for testing purposes and have encountered an unexpected issue. The 'Displays' configuration indicates the presence of three monitors, like this: 1) Dell Inc. 27" 2) Dell Inc. 27" 3) Unknown Display However, I only have two displays and not a third one. When moving the cursor to the extreme right corner of the screen, the entire display shifts to the right. Below are the pertinent details: Configuration: - Utilizing: two monitors - Graphics Card: NVIDIA GeForce GTX 1660 SUPER - Environment: Xorg - Driver Version: Nvidia driver 535.161.07 This behavior disrupts normal workflow and consistency in display management. Any insights or solutions to address this issue would be greatly appreciated. Thank you for your attention to this matter. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-shell 46.0-0ubuntu5 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 17 21:43:13 2024 DisplayManager: gdm3 InstallationDate: Installed on 2024-04-17 (0 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240417.2) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 46.0-1ubuntu7 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/2062089/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2062090] [NEW] background colour tool not working
Public bug reported: (although it seems similar to #1427346 it does seem to be a different bug) steps to reproduce 1) open new spreadsheet 2) type something in first cell 3) click on the 'background colour' dropdown, select a colour (from libreoffice pallet, say red) 4) click on 'background colour' ie to make that cell that colour (say red) what should happen: the cell background should turn red what does happen: nothing libreoffice-calc: Installed: 1:7.3.7-0ubuntu0.22.04.4 Candidate: 1:7.3.7-0ubuntu0.22.04.4 Version table: *** 1:7.3.7-0ubuntu0.22.04.4 500 500 http://muug.ca/mirror/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 1:7.3.2-0ubuntu2 500 500 http://muug.ca/mirror/ubuntu jammy/main amd64 Packages DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu 22.04.4 LTS" ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libreoffice-calc 1:7.3.7-0ubuntu0.22.04.4 Uname: Linux 6.0.7-gnulibre-squashfix x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 17 18:57:53 2024 InstallationDate: Installed on 2017-04-18 (2556 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: libreoffice UpgradeStatus: Upgraded to jammy on 2023-06-14 (308 days ago) mtime.conffile..etc.apport.crashdb.conf: 2020-06-07T21:16:26.397404 ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2062090 Title: background colour tool not working Status in libreoffice package in Ubuntu: New Bug description: (although it seems similar to #1427346 it does seem to be a different bug) steps to reproduce 1) open new spreadsheet 2) type something in first cell 3) click on the 'background colour' dropdown, select a colour (from libreoffice pallet, say red) 4) click on 'background colour' ie to make that cell that colour (say red) what should happen: the cell background should turn red what does happen: nothing libreoffice-calc: Installed: 1:7.3.7-0ubuntu0.22.04.4 Candidate: 1:7.3.7-0ubuntu0.22.04.4 Version table: *** 1:7.3.7-0ubuntu0.22.04.4 500 500 http://muug.ca/mirror/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 1:7.3.2-0ubuntu2 500 500 http://muug.ca/mirror/ubuntu jammy/main amd64 Packages DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu 22.04.4 LTS" ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libreoffice-calc 1:7.3.7-0ubuntu0.22.04.4 Uname: Linux 6.0.7-gnulibre-squashfix x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 17 18:57:53 2024 InstallationDate: Installed on 2017-04-18 (2556 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: libreoffice UpgradeStatus: Upgraded to jammy on 2023-06-14 (308 days ago) 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/libreoffice/+bug/2062090/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2062089] Re: [NVIDIA] Cursor movement to right corner causes screen shift
Further details: The 'Displays' configuration indicates the presence of three monitors, like this: 1) Dell Inc. 27" 2) Dell Inc. 27" 3) Unknown Display However, I only have two displays and not a third one. -- 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/2062089 Title: [NVIDIA] Ubuntu 24.04 detects a third unknown monitor (instead of two) Status in gnome-shell package in Ubuntu: New Bug description: I recently installed Ubuntu 24.04 for testing purposes and have encountered an unexpected issue. When moving the cursor to the extreme right corner of the screen, the entire display shifts to the right. Below are the pertinent details: Configuration: - Utilizing: two monitors - Graphics Card: NVIDIA GeForce GTX 1660 SUPER - Environment: Xorg - Driver Version: Nvidia driver 535.161.07 This behavior disrupts normal workflow and consistency in display management. Any insights or solutions to address this issue would be greatly appreciated. Thank you for your attention to this matter. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-shell 46.0-0ubuntu5 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 17 21:43:13 2024 DisplayManager: gdm3 InstallationDate: Installed on 2024-04-17 (0 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240417.2) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 46.0-1ubuntu7 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/2062089/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2060659] Re: X11 fractional scaling support is missing in 46.0
** Changed in: mutter (Ubuntu) Status: Confirmed => In Progress -- 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/2060659 Title: X11 fractional scaling support is missing in 46.0 Status in mutter package in Ubuntu: In Progress Bug description: X11 fractional scaling support is missing in mutter/gnome-shell 46.0 https://salsa.debian.org/gnome- team/mutter/-/commit/414010ddef06757000175c30238371739199d29a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2060659/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2062082] [NEW] 24.04 Wayland vs Nautilus performance problem
Public bug reported: Apologies if I have misfiled this bug - this is a report of an issue affecting Wayland in Ubuntu 24.04 beta. Using 24.04 beta logging in with Wayland. Nautilus has very significant performance issues. Doesn't happen when logging in with Xorg instead of Wayland. Opening Nautilus windows - including normal windows navigation, and the file download location dialogue in things like Chrome - extremely slow. Takes approx. 10 seconds to process user double clicking to open folder. Attempting to drag folder across screen usually doesn't work, or takes a very long time. Not very skilled at debugging, but programmes like Gimp, which has its own built-in folder explorer for choosing a location to save an image, do not have this problem. Ubuntu 24.04 with X does not have this problem. No performance issues have been noticed with folder navigation, stat'ing files etc. over the command line. It is only nautilus and Wayland that give me this issue, so I suspect it is not an issue with my SSD. The following output was observed when starting nautilus over the command line: /home/me/ $ nautilus . ** Message: 23:43:50.560: Connecting to org.freedesktop.Tracker3.Miner.Files libEGL warning: egl: failed to create dri2 screen After approx. 10 seconds, the folder opened on screen. I double clicked on a sub directory, and it took about 9 seconds to open. I have attempted to show that this is not an issue with my SSD here: /home/me/ $ date; cd workspace/; touch foo.txt; ls foo*; cd ../; date; Wed Apr 17 11:58:16 PM BST 2024 foo.txt Wed Apr 17 11:58:16 PM BST 2024 As you can see, no unusual slowdown was observed. Obtaining the following setting for my bug report, I note that the 'Settings' GUI utility is among the areas affect by my very significant system slowdown. I have copied some details about my system including its graphics card in case that helps. # System Details Report --- ## Report details - **Date generated:** 2024-04-17 23:59:54 ## Hardware Information: - **Hardware Model:** ASUS ROG STRIX B550-F GAMING - **Memory:** 32.0 GiB - **Processor:** AMD Ryzen™ 7 5800X × 16 - **Graphics:**zink Vulkan 1.3(NVIDIA GeForce GTX 1050 Ti (NVIDIA_PROPRIETARY)) - **Disk Capacity:** 2.0 TB ## Software Information: - **Firmware Version:**2006 - **OS Name:** Ubuntu Noble Numbat (development branch) - **OS Build:**(null) - **OS Type:** 64-bit - **GNOME Version:** 46 - **Windowing System:**Wayland - **Kernel Version:** Linux 6.8.0-22-generic ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..09.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 545.29.06 Thu Nov 16 01:59:08 UTC 2023 GCC version: ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Apr 17 23:44:47 2024 DistUpgraded: 2024-04-11 13:09:51,904 DEBUG migrateToDeb822Sources() DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] InstallationDate: Installed on 2024-04-11 (6 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) MachineType: ASUS System Product Name ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-22-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to noble on 2024-04-11 (6 days ago) dmi.bios.date: 03/19/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2006 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B550-F GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x
[Desktop-packages] [Bug 2062078] [NEW] Mouse animations do not follow accent colors
Public bug reported: This is a regression from previous releases, the mouse animations do not follow the user-selected accent color The missing assets needs to be regenerated with this script: - https://gitlab.gnome.org/-/snippets/5549 Sources are: - https://gitlab.gnome.org/Teams/Design/settings-mockups/-/commits/master/mouse-and-touchpad/src/mouse-touchpad-v2.blend ** Affects: gnome-control-center (Ubuntu) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2062078 Title: Mouse animations do not follow accent colors Status in gnome-control-center package in Ubuntu: In Progress Bug description: This is a regression from previous releases, the mouse animations do not follow the user-selected accent color The missing assets needs to be regenerated with this script: - https://gitlab.gnome.org/-/snippets/5549 Sources are: - https://gitlab.gnome.org/Teams/Design/settings-mockups/-/commits/master/mouse-and-touchpad/src/mouse-touchpad-v2.blend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2062078/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2061118] Re: Rendering issues in vmware with 3d on (GTK ngl backend)
My issue is compounded by the fact that Ubuntu registers no network interfaces in Ubuntu on vmwareplayer in NAT mode and it sees a connection but can't connect in bridged mode. As a result I can't apply updates on install or upgrade my NVIDIA drivers which may help resolve the issue. I will try again with the newer NVIDIA drivers in the next daily. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2061118 Title: Rendering issues in vmware with 3d on (GTK ngl backend) Status in GTK+: New Status in Mesa: New Status in gtk4 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Triaged Status in gtk4 source package in Noble: Invalid Status in mesa source package in Noble: Triaged Bug description: Build: Noble Daily Current from 12th April Host OS: Windows 11 VM App: VMWare Workstation 17 Player Issue: During installation there is continuous black flickering artefacts throughout the flow. Installation completed successfully, got to GDM, logged in but desktop screen is black and then locks up the whole application, cannot shutdown or interact with Player and need to hard kill from task manager. The issue appears does not appear with Mantic with the exact same machine configuration and appears to be an issue with GPU, my host machine is running an NVIDIA 4070ti with the latest windows drivers. On reboot some elements of the desktop are visible but cannot be interacted with without further lockups. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2061118/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
this affected me as well -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2055012 Title: When I upgraded from 22.04 to 24.04, DNS resolution went wrong. Status in network-manager package in Ubuntu: Confirmed Bug description: I was an unpatient idiot, and I upgraded from 22.04 to 24.04. Near to the end of the upgrade, I got an „Oh, no! Something has gone wrong and the system cannot recover. Call the system administrator” message after a red FAILED in the terminal. The system administrator is myself, because my computer is a personal one. Hard reset, same error, Ctrl+Alt+F3, sudo apt reinstall gdm3. Obviously. I needed to finish the update with dpkg. While dpkg was upgrading, it printed an error message for every WiFi connection: „[Failed] Failed to migrate [I do not remember, something with /etc/netplan]” It took at least one and a half hour to find the solution on Ask Ubuntu. The problem was: /etc/resolv.conf became a broken link, along with systemd-resolve.service. I needed to remove both of them and write a new resolv.conf to fix the error. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: network-manager 1.45.90-1ubuntu1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Feb 26 08:21:02 2024 InstallationDate: Installed on 2023-07-05 (236 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) IpRoute: default via 192.168.0.1 dev wlp3s0 proto dhcp src 192.168.0.100 metric 600 192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.100 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: Upgraded to noble on 2024-02-24 (2 days ago) modified.conffile..etc.init.d.apport: [modified] mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.45.90 connected started full enabled enabled enabled missing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1448220] Re: package sgml-base 1.26+nmu4ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
This bug is still present in 1.30. I fixed it the same way as mfisheresq, before finding this report. ## Bug Fix The sgml-base package should create the /var/lib/sgml-base directory, and not even need to check whether it exists. $ sudo dpkg --configure sgml-base Setting up sgml-base (1.30) ... cannot open /var/lib/sgml-base/supercatalog.new for writing: No such file or directory at /usr/sbin/update-catalog line 312. dpkg: error processing package sgml-base (--configure): installed sgml-base package post-installation script subprocess returned error exit status 2 Errors were encountered while processing: sgml-base ## Context & Importance This bug prevents any other packages from being installed until it's manually fixed, and sgml-base cannot be blindly removed because of its role as a dependency for help documentation that's a default part of plasma desktop, and presumable other deafult help applications distributed as a default part of desktop environments. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sgml-base in Ubuntu. https://bugs.launchpad.net/bugs/1448220 Title: package sgml-base 1.26+nmu4ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 Status in sgml-base package in Ubuntu: Confirmed Bug description: The bug seems very similar to 1074475, but I encountered it in upgrading from 14.10 to 15.04, and in my case, the post-installation script returns error code 2. As a consequence of this bug, dpkg reports dependency problems while processing: sgml-base metacity-common libmetacity-private2 compiz-gnome compiz unity libunity-2d-private0 metacity sgml-data ubuntu-desktop unity-2d unity-2d-common unity-2d-panel unity-2d-shell unity-2d-spread compizconfig-backend-gconf ProblemType: Package DistroRelease: Ubuntu 15.04 Package: sgml-base 1.26+nmu4ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Fri Apr 24 17:24:36 2015 DuplicateSignature: package:sgml-base:1.26+nmu4ubuntu1:subprocess installed post-installation script returned error exit status 2 ErrorMessage: subprocess installed post-installation script returned error exit status 2 PackageArchitecture: all RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4 SourcePackage: sgml-base Title: package sgml-base 1.26+nmu4ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: Upgraded to vivid on 2015-04-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sgml-base/+bug/1448220/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2043820] Re: Unable to contact snap store on Xubuntu from Jammy to Noble
** Changed in: firefox (Ubuntu Noble) Milestone: ubuntu-24.04-beta => ubuntu-24.04 ** Changed in: firefox (Ubuntu Noble) Milestone: ubuntu-24.04 => noble-updates -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2043820 Title: Unable to contact snap store on Xubuntu from Jammy to Noble Status in firefox package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Status in firefox source package in Noble: Confirmed Status in snapd source package in Noble: Confirmed Bug description: When running `do-release-upgrade -d` on Jammy Xubuntu, the upgrade fails consistently at the `Installing the firefox snap` step. This was first detected on Jenkins [1], then reproduced locally with `auto-upgrade-testing`, then finally by manually running a `do- release-upgrade -d` in a VM. [1]: https://platform-qa-jenkins.ps5.ubuntu.com/view/upgrade- list/job/upgrade_ubuntu-jammy-noble-xubuntu-amd64_qemu/7/consoleFull (Jenkins full log attached) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.17 ProcVersionSignature: User Name 5.15.0-88.98-generic 5.15.126 Uname: Linux 5.15.0-88-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: XFCE Date: Fri Nov 17 18:24:22 2023 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2043820/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2061118] Re: Rendering issues in vmware with 3d on (GTK ngl backend)
(The latest version of the Ubuntu Desktop installer installs all available updates at the end of the install. It's a nice feature in cases like this.) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2061118 Title: Rendering issues in vmware with 3d on (GTK ngl backend) Status in GTK+: New Status in Mesa: New Status in gtk4 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Triaged Status in gtk4 source package in Noble: Invalid Status in mesa source package in Noble: Triaged Bug description: Build: Noble Daily Current from 12th April Host OS: Windows 11 VM App: VMWare Workstation 17 Player Issue: During installation there is continuous black flickering artefacts throughout the flow. Installation completed successfully, got to GDM, logged in but desktop screen is black and then locks up the whole application, cannot shutdown or interact with Player and need to hard kill from task manager. The issue appears does not appear with Mantic with the exact same machine configuration and appears to be an issue with GPU, my host machine is running an NVIDIA 4070ti with the latest windows drivers. On reboot some elements of the desktop are visible but cannot be interacted with without further lockups. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2061118/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2061118] Re: Rendering issues in vmware with 3d on (GTK ngl backend)
OK, so I just tried this out on the same host I did my Fedora 40 testing, a Windows 11 23H2 system with Intel graphics (no NVIDIA) and VMWare Player 17. I grabbed the Ubuntu 24.04 beta desktop image - ubuntu-24.04-beta- desktop-amd64.iso - and booted it. From that environment I could reproduce the bug. I tested using "Files" (nautilus) - I ran it and it was completely messed up in much the same way as on Fedora, lots of bits of the UI just not shown at all. Then I ran an install. I guess your installs work differently from ours, they don't just dump the live environment onto the disk, because when I booted the installed system, it had mesa 24.0.5 already (verified with `dpkg -l`). And for me, the bug is indeed fixed. Now when I run Files, it renders perfectly. Ditto Text Editor (another GTK4 app). However, reading Oliver's original description again, it really doesn't sound like the same bug. I didn't observe any "black flickering artifacts" during install, and I never saw such a thing in Fedora 40 testing either. I also didn't see anything like "desktop screen is black and then locks up the whole application, cannot shutdown or interact with Player". For me, both in Ubuntu and Fedora, when a system is affected by this bug, GTK 4-based apps tend to be missing large amounts of UI elements, but the desktop shell itself is not affected at all, let alone does it lock up or become unresponsive. So, I think Oliver is seeing something else, but I don't know what. I'd recommend you get a few more folks to test and see what they see, and report the host hardware config. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2061118 Title: Rendering issues in vmware with 3d on (GTK ngl backend) Status in GTK+: New Status in Mesa: New Status in gtk4 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Triaged Status in gtk4 source package in Noble: Invalid Status in mesa source package in Noble: Triaged Bug description: Build: Noble Daily Current from 12th April Host OS: Windows 11 VM App: VMWare Workstation 17 Player Issue: During installation there is continuous black flickering artefacts throughout the flow. Installation completed successfully, got to GDM, logged in but desktop screen is black and then locks up the whole application, cannot shutdown or interact with Player and need to hard kill from task manager. The issue appears does not appear with Mantic with the exact same machine configuration and appears to be an issue with GPU, my host machine is running an NVIDIA 4070ti with the latest windows drivers. On reboot some elements of the desktop are visible but cannot be interacted with without further lockups. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2061118/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2061860] Re: Update mozjs115 to 115.10.0
This bug was fixed in the package mozjs115 - 115.10.0-1 --- mozjs115 (115.10.0-1) unstable; urgency=high * New upstream release (LP: #2061860) - CVE-2024-3852: GetBoundName in the JIT returned the wrong object - CVE-2024-3854: Out-of-bounds-read after mis-optimized switch statement - CVE-2024-3857: Incorrect JITting of arguments led to use-after-free during garbage collection -- Jeremy Bícha Tue, 16 Apr 2024 07:52:09 -0400 ** Changed in: mozjs115 (Ubuntu) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-3852 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-3854 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-3857 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mozjs115 in Ubuntu. https://bugs.launchpad.net/bugs/2061860 Title: Update mozjs115 to 115.10.0 Status in mozjs115 package in Ubuntu: Fix Released Bug description: Includes some security fixes The build is fairly quick and the autopkgtest burden should be minimal, probably just gjs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mozjs115/+bug/2061860/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2061728] Re: Apps don't launch from GNOME Software
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-software (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/2061728 Title: Apps don't launch from GNOME Software Status in gnome-software package in Ubuntu: Confirmed Bug description: Install apps from gnome-software. Open the app from gnome-software,the app crash with the next error: "ldconfig failed, exit status 256" ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-software 46.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-25.25-generic 6.8.1 Uname: Linux 6.8.0-25-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 16 07:58:06 2024 InstallationDate: Installed on 2024-04-08 (8 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240407.2) InstalledPlugins: gnome-software-plugin-flatpak 46.0-1ubuntu2 gnome-software-plugin-snap46.0-1ubuntu2 ProcEnviron: LANG=es_ES.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2061728/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2061118] Re: Rendering issues in vmware with 3d on (GTK ngl backend)
FWIW, I did my testing - which found this is broken for a Fedora 40 guest with mesa 24.0.4, but fixed with 24.0.5 - on a Windows 11 (23H2) host. No idea what's different for Oliver, sorry :( I guess I could try with an Ubuntu guest on my test setup, I've got a bit of spare time today. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2061118 Title: Rendering issues in vmware with 3d on (GTK ngl backend) Status in GTK+: New Status in Mesa: New Status in gtk4 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Triaged Status in gtk4 source package in Noble: Invalid Status in mesa source package in Noble: Triaged Bug description: Build: Noble Daily Current from 12th April Host OS: Windows 11 VM App: VMWare Workstation 17 Player Issue: During installation there is continuous black flickering artefacts throughout the flow. Installation completed successfully, got to GDM, logged in but desktop screen is black and then locks up the whole application, cannot shutdown or interact with Player and need to hard kill from task manager. The issue appears does not appear with Mantic with the exact same machine configuration and appears to be an issue with GPU, my host machine is running an NVIDIA 4070ti with the latest windows drivers. On reboot some elements of the desktop are visible but cannot be interacted with without further lockups. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2061118/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2060816] Re: App grid icon is Ubuntu logo, need to find override
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: In Progress => Fix Committed -- 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/2060816 Title: App grid icon is Ubuntu logo, need to find override Status in Yaru Theme: Fix Released Status in edubuntu-artwork package in Ubuntu: Fix Committed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Committed Status in yaru-theme package in Ubuntu: Fix Committed Bug description: The app grid icon is now the Ubuntu logo. We need to find a way to override this to the Edubuntu logo. To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/2060816/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1986450] Re: Visual artifact 1px vertical white line right side of the wallpaper with Ambiance/Radiance
> .background.decorated:backdrop {
This still doesn't feel entirely good. The background can be applied to
a window, in which case it needs to be restricted to the .decorated
property; but I presume it can also be applied to many other GTK widgets
in which case it shouldn't be restricted, at least in order not to
change the current behavior because I don't know how to test any change.
So if I'd like to perform the smallest possible change, the smallest
possible impact of the change (preferably: no other change than fixing
this bug) then I'd need to select for "either window.decorated or
something non-window", which I'm not sure how to express in CSS (at
least not in a single step).
Maybe leave the first block untouched, and then revert its effect in the
next rule for undecorated windows (effectively moving the above-proposed
user workaround into the main theme, restricted to the element being a
window).
So the theme itself would go like (the first block is unchanged, the
second one is newly added):
.background:backdrop {
color: @backdrop_fg_color;
box-shadow: inset -1px 0 shade (@bg_color, 0.94);
}
window.background:not(.decorated):backdrop {
box-shadow: none;
}
Dunno how much it makes sense. Would really love to get it reviewed by a
CSS expert :)
--
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/1986450
Title:
Visual artifact 1px vertical white line right side of the wallpaper
with Ambiance/Radiance
Status in gnome-shell package in Ubuntu:
New
Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu:
New
Status in ubuntu-themes package in Ubuntu:
New
Bug description:
After manually upgrading from 20.04 LTS to 22.04.1 LTS I find that
there is a 1px wide vertical white line on the desktop that appears
whenever an application has focus. It is on the right side of the
monitor, covering the background wallpaper but not the menu.
Workaround: in Displays, change scale to something else than 100% and then
change back to 100%. That white vertical line will stay at the former 100%
window size location until the Settings window is closed. It disappears when
the Settings is closed.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2018-04-27 (1570 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Package: gnome-shell 42.2-0ubuntu0.2
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
RelatedPackageVersions: mutter-common 42.2-0ubuntu1
Tags: wayland-session jammy
Uname: Linux 5.15.0-46-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1986450/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1986450] Re: Visual artifact 1px vertical white line right side of the wallpaper with Ambiance/Radiance
DING developer's response is basically that they clear the "decorated"
property of the window, and the theme should handle that.
Based on this, I think the correct solution for the Ambiance/Radiance
themes is to further restrict the offending block with the ".decorated"
selector, i.e.
.background.decorated:backdrop {
color: @backdrop_fg_color;
box-shadow: inset -1px 0 shade (@bg_color, 0.94);
}
or for the user's own gtk.css to select for its negated
":not(.decorated)" for the workaround:
.background:not(.decorated):backdrop {
box-shadow: none;
}
--
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/1986450
Title:
Visual artifact 1px vertical white line right side of the wallpaper
with Ambiance/Radiance
Status in gnome-shell package in Ubuntu:
New
Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu:
New
Status in ubuntu-themes package in Ubuntu:
New
Bug description:
After manually upgrading from 20.04 LTS to 22.04.1 LTS I find that
there is a 1px wide vertical white line on the desktop that appears
whenever an application has focus. It is on the right side of the
monitor, covering the background wallpaper but not the menu.
Workaround: in Displays, change scale to something else than 100% and then
change back to 100%. That white vertical line will stay at the former 100%
window size location until the Settings window is closed. It disappears when
the Settings is closed.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2018-04-27 (1570 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Package: gnome-shell 42.2-0ubuntu0.2
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
RelatedPackageVersions: mutter-common 42.2-0ubuntu1
Tags: wayland-session jammy
Uname: Linux 5.15.0-46-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1986450/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2061729] Re: Ubuntu Dock icon highlight is practically invisible when a white or grey window is behind it
** Changed in: yaru-theme (Ubuntu) Importance: Undecided => Low ** Changed in: yaru-theme (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: yaru-theme (Ubuntu) Status: New => In Progress ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: New => Won't Fix -- 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/2061729 Title: Ubuntu Dock icon highlight is practically invisible when a white or grey window is behind it Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Won't Fix Status in yaru-theme package in Ubuntu: In Progress Bug description: Ubuntu Dock icon highlight is practically invisible when a white or grey window is behind it (like when autohide is enabled). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2061729/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2062046] [NEW] Nautilus icons are not using yaru theme
Public bug reported: As reported upstream: https://github.com/ubuntu/yaru/issues/4055 The nautilus search icons are using adwaita theme, and they don't fit well with the whole system theme. ** Affects: yaru-theme (Ubuntu) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/2062046 Title: Nautilus icons are not using yaru theme Status in yaru-theme package in Ubuntu: Fix Committed Bug description: As reported upstream: https://github.com/ubuntu/yaru/issues/4055 The nautilus search icons are using adwaita theme, and they don't fit well with the whole system theme. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/2062046/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2041094] Re: application doesn't show its proper icon and name under the dock
Why it is not yet solved ? I am on 24.04 LTS Beta and Transmission icon in the dock is not showing correctly ! It is just a gear look a like icon instead of the real Transmission icon !? If Ubuntu wants to gain market share, and users also , this kind of bug should not be there ! ** Attachment added: "Transmission not showing the right icon" https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/2041094/+attachment/5766885/+files/Capture%20d%E2%80%99%C3%A9cran%20du%202024-04-17%2014-04-18.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/2041094 Title: application doesn't show its proper icon and name under the dock Status in transmission package in Ubuntu: Confirmed Bug description: In mantic, when transmission-gtk is run, its icon is not showing properly in the dash. With the application pinned in the dash, when the active application creates another generic "gear" icon and names itself `com.transmissionbt.transmission_66306_16121871` on the previous lunar release, the functionality was correct To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/2041094/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2041094] Re: application doesn't show its proper icon and name under the dock
This bug was not solved under 23.10 and now it appears in a LTS release come on guys ! and why it is not yet assigned to anyone ??? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/2041094 Title: application doesn't show its proper icon and name under the dock Status in transmission package in Ubuntu: Confirmed Bug description: In mantic, when transmission-gtk is run, its icon is not showing properly in the dash. With the application pinned in the dash, when the active application creates another generic "gear" icon and names itself `com.transmissionbt.transmission_66306_16121871` on the previous lunar release, the functionality was correct To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/2041094/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2061993] Re: RDP Remmina closes when trying to connect to a remote desktop - the same configuration works fine on other editions.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: remmina (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/2061993 Title: RDP Remmina closes when trying to connect to a remote desktop - the same configuration works fine on other editions. Status in remmina package in Ubuntu: Confirmed Bug description: blox_land@blox-land-numbat:~$ remmina remmina-Message: 13:25:34.158: Remmina does not log all output statements. Turn on more verbose output by using "G_MESSAGES_DEBUG=remmina" as an environment variable. More info available on the Remmina wiki at: https://gitlab.com/Remmina/Remmina/-/wikis/Usage/Remmina-debugging (org.remmina.Remmina:11727): Gtk-WARNING **: 13:25:35.117: gtk_menu_attach_to_widget(): menu already attached to GtkMenuItem [13:25:41:43] [11727:2e1c] [ERROR][com.freerdp.common.settings] - [freerdp_settings_get_bool]: Invalid key index 0 [FreeRDP_instance|FREERDP_SETTINGS_TYPE_POINTER] [13:25:41:44] [11727:2e1c] [FATAL][com.freerdp.winpr.assert] - [winpr_int_assert]: FALSE [obj-x86_64-linux-gnu/libfreerdp/CMakeFiles/freerdp.dir/compiler_depend.ts:freerdp_settings_get_bool:634] [13:25:41:44] [11727:2e1c] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 0: dli_fname=/lib/x86_64-linux-gnu/libwinpr3.so.3 [0x766d98ccc000], dli_sname=winpr_backtrace [0x766d98d38540] [13:25:41:44] [11727:2e1c] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 1: dli_fname=/lib/x86_64-linux-gnu/libwinpr3.so.3 [0x766d98ccc000], dli_sname=winpr_log_backtrace_ex [0x766d98d3ffe0] [13:25:41:44] [11727:2e1c] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 2: dli_fname=/lib/x86_64-linux-gnu/libfreerdp3.so.3 [0x766d93c0], dli_sname=(null) [(nil)] [13:25:41:44] [11727:2e1c] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 3: dli_fname=/lib/x86_64-linux-gnu/libfreerdp3.so.3 [0x766d93c0], dli_sname=freerdp_settings_get_bool [0x766d93c648a0] [13:25:41:44] [11727:2e1c] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 4: dli_fname=/usr/lib/x86_64-linux-gnu/remmina/plugins/remmina-plugin-rdp.so [0x766d9a047000], dli_sname=(null) [(nil)] [13:25:41:44] [11727:2e1c] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 5: dli_fname=/usr/lib/x86_64-linux-gnu/remmina/plugins/remmina-plugin-rdp.so [0x766d9a047000], dli_sname=(null) [(nil)] [13:25:41:44] [11727:2e1c] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 6: dli_fname=/usr/bin/../lib/x86_64-linux-gnu/libc.so.6 [0x766d9da0], dli_sname=(null) [(nil)] [13:25:41:44] [11727:2e1c] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 7: dli_fname=/usr/bin/../lib/x86_64-linux-gnu/libc.so.6 [0x766d9da0], dli_sname=(null) [(nil)] [13:25:41:44] [11727:2e1c] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 8: unresolvable, address=(nil) Aborted (core dumped) blox_land@blox-land-numbat:~$ remmina --version remmina-Message: 13:26:03.550: Remmina does not log all output statements. Turn on more verbose output by using "G_MESSAGES_DEBUG=remmina" as an environment variable. More info available on the Remmina wiki at: https://gitlab.com/Remmina/Remmina/-/wikis/Usage/Remmina-debugging org.remmina.Remmina - 1.4.35 (git n/a) blox_land@blox-land-numbat:~$ ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: remmina 1.4.35+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 17 13:22:37 2024 InstallationDate: Installed on 2024-04-14 (3 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240410.2) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: remmina UpgradeStatus: No upgrade log present (probably fresh install) blox_land@blox-land-numbat:~$ G_MESSAGES_DEBUG=remmina remmina (process:12618): remmina-DEBUG: 14:26:56.726: (remmina_file_manager_init) - Initialized the "/home/blox_land/.local/share/remmina" data folder (process:12618): remmina-DEBUG: 14:26:56.919: (remmina_plugin_manager_register_plugin) - Remmina plugin glibsecret (type=Secret) has been registered, but is not yet initialized/activated. The initialization order is 2000. (process:12618): remmina-DEBUG: 14:26:57.711: (remmina_plugin_entry) - gfx_h264_available: 0 (process:12618): remmina-DEBUG: 14:26:57.727: (remmina_rdp_settings_kbd_init) - rdp_keyboard_remapping_list:
[Desktop-packages] [Bug 2062044] [NEW] Dock icons for focused applications are not highlighted
Public bug reported: The icon for the application that is currently focused should be highlighted but this is not the case in noble. ** Affects: yaru-theme (Ubuntu) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/2062044 Title: Dock icons for focused applications are not highlighted Status in yaru-theme package in Ubuntu: In Progress Bug description: The icon for the application that is currently focused should be highlighted but this is not the case in noble. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/2062044/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2060816] Re: App grid icon is Ubuntu logo, need to find override
** Changed in: edubuntu-artwork (Ubuntu) Status: In Progress => Fix Committed -- 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/2060816 Title: App grid icon is Ubuntu logo, need to find override Status in Yaru Theme: Fix Released Status in edubuntu-artwork package in Ubuntu: Fix Committed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: In Progress Status in yaru-theme package in Ubuntu: Fix Committed Bug description: The app grid icon is now the Ubuntu logo. We need to find a way to override this to the Edubuntu logo. To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/2060816/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2062043] [NEW] WebKitWebProcess SIGSEGV when loading an MJPEG stream
Public bug reported: After an upgrade on all of the following packages: ``` libwebkit2gtk-4.0-dev :: 2.42.5-0ubuntu0.22.04.2 -> 2.44.0-0ubuntu0.22.04.1 libgnutls30 :: 3.7.3-4ubuntu1.4 -> 3.7.3-4ubuntu1.5 libjavascriptcoregtk-4.0-dev :: 2.42.5-0ubuntu0.22.04.2 -> 2.44.0-0ubuntu0.22.04.1 gir1.2-webkit2-4.0 :: 2.42.5-0ubuntu0.22.04.2 -> 2.44.0-0ubuntu0.22.04.1 gir1.2-javascriptcoregtk-4.0 :: 2.42.5-0ubuntu0.22.04.2 -> 2.44.0-0ubuntu0.22.04.1 libwebkit2gtk-4.0-37 :: 2.42.5-0ubuntu0.22.04.2 -> 2.44.0-0ubuntu0.22.04.1 libjavascriptcoregtk-4.0-18 :: 2.42.5-0ubuntu0.22.04.2 -> 2.44.0-0ubuntu0.22.04.1 klibc-utils :: 2.0.10-4 -> 2.0.10-4ubuntu0.1 libklibc :: 2.0.10-4 -> 2.0.10-4ubuntu0.1 ``` My webkit2gtk app has stopped working. Specifically, when my app tries to load an MJPEG endpoint into an `img` element, the WebKitWebProcess process instantly segfaults. The app works perfectly when this `img` element is removed. Removing this element is not a viable solution for me, as it is part of the core functionality of the application. I am not perfectly certain which of these packages contains the actual bug, I'm just assuming it's `libwebkit2gtk-4.0-37` because that is the package that provides the `WebKitWebProcess` binary. Thank you, Campbell ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libwebkit2gtk-4.0-37 2.44.0-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 17 12:48:57 2024 InstallationDate: Installed on 2023-11-10 (159 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: TERM=xterm-kitty PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh SourcePackage: webkit2gtk UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: webkit2gtk (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 webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/2062043 Title: WebKitWebProcess SIGSEGV when loading an MJPEG stream Status in webkit2gtk package in Ubuntu: New Bug description: After an upgrade on all of the following packages: ``` libwebkit2gtk-4.0-dev :: 2.42.5-0ubuntu0.22.04.2 -> 2.44.0-0ubuntu0.22.04.1 libgnutls30 :: 3.7.3-4ubuntu1.4 -> 3.7.3-4ubuntu1.5 libjavascriptcoregtk-4.0-dev :: 2.42.5-0ubuntu0.22.04.2 -> 2.44.0-0ubuntu0.22.04.1 gir1.2-webkit2-4.0 :: 2.42.5-0ubuntu0.22.04.2 -> 2.44.0-0ubuntu0.22.04.1 gir1.2-javascriptcoregtk-4.0 :: 2.42.5-0ubuntu0.22.04.2 -> 2.44.0-0ubuntu0.22.04.1 libwebkit2gtk-4.0-37 :: 2.42.5-0ubuntu0.22.04.2 -> 2.44.0-0ubuntu0.22.04.1 libjavascriptcoregtk-4.0-18 :: 2.42.5-0ubuntu0.22.04.2 -> 2.44.0-0ubuntu0.22.04.1 klibc-utils :: 2.0.10-4 -> 2.0.10-4ubuntu0.1 libklibc :: 2.0.10-4 -> 2.0.10-4ubuntu0.1 ``` My webkit2gtk app has stopped working. Specifically, when my app tries to load an MJPEG endpoint into an `img` element, the WebKitWebProcess process instantly segfaults. The app works perfectly when this `img` element is removed. Removing this element is not a viable solution for me, as it is part of the core functionality of the application. I am not perfectly certain which of these packages contains the actual bug, I'm just assuming it's `libwebkit2gtk-4.0-37` because that is the package that provides the `WebKitWebProcess` binary. Thank you, Campbell ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libwebkit2gtk-4.0-37 2.44.0-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 17 12:48:57 2024 InstallationDate: Installed on 2023-11-10 (159 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: TERM=xterm-kitty PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh SourcePackage: webkit2gtk UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/2062043/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970291] Re: [nvidia] Secondary monitor performance is slow on an Nvidia hybrid system in Wayland sessions
** Changed in: gnome-shell Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1970291 Title: [nvidia] Secondary monitor performance is slow on an Nvidia hybrid system in Wayland sessions Status in GNOME Shell: Fix Released Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Bug description: In session with Wayland the Nvidia driver settings do not load. And there is a sluggishness when opening apps, show applications menu, maximize, changing workspace, resize, changing monitor windows etc. When in an Xorg session the Nvidia settings load correctly and the performance is satisfactory. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.60.02 Wed Mar 16 11:24:05 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 25 21:18:08 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:2086] NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation TU116M [GeForce GTX 1660 Ti Mobile] [8086:2086] InstallationDate: Installed on 2022-04-24 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) MachineType: Avell High Performance A60 MUV ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=894cb598-7172-481c-a449-3133b8f226e5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/11/2020 dmi.bios.release: 5.13 dmi.bios.vendor: Intel Corp. dmi.bios.version: QCCFL357.0122.2020.0911.1520 dmi.board.name: Avell High Performance dmi.board.vendor: Avell High Performance dmi.chassis.type: 10 dmi.chassis.vendor: Avell High Performance dmi.chassis.version: 1.0 dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnIntelCorp.:bvrQCCFL357.0122.2020.0911.1520:bd09/11/2020:br5.13:efr1.25:svnAvellHighPerformance:pnA60MUV:pvr:rvnAvellHighPerformance:rnAvellHighPerformance:rvr:cvnAvellHighPerformance:ct10:cvr1.0:skuA60MUV: dmi.product.family: A60 MUV dmi.product.name: A60 MUV dmi.product.sku: A60 MUV dmi.sys.vendor: Avell High Performance version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1970291/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2062038] [NEW] Update gnome-mahjongg to 3.40.1
Public bug reported: gnome-mahjongg 3.40.1 includes several important bugfixes and almost a year of translation updates. gnome-mahjopngg is included by default in some Ubuntu desktop flavors. https://gitlab.gnome.org/GNOME/gnome-mahjongg/-/blob/3.40.1/NEWS https://gitlab.gnome.org/GNOME/gnome-mahjongg/-/compare/3.40.0...3.40.1 ** Affects: gnome-mahjongg (Ubuntu) Importance: High Status: In Progress ** Tags: noble upgrade-software-version ** Description changed: gnome-mahjongg 3.40.1 includes several important bugfixes and almost a year of translation updates. gnome-mahjopngg is included by default in some Ubuntu desktop flavors. + + https://gitlab.gnome.org/GNOME/gnome-mahjongg/-/blob/3.40.1/NEWS + + https://gitlab.gnome.org/GNOME/gnome-mahjongg/-/compare/3.40.0...3.40.1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-mahjongg in Ubuntu. https://bugs.launchpad.net/bugs/2062038 Title: Update gnome-mahjongg to 3.40.1 Status in gnome-mahjongg package in Ubuntu: In Progress Bug description: gnome-mahjongg 3.40.1 includes several important bugfixes and almost a year of translation updates. gnome-mahjopngg is included by default in some Ubuntu desktop flavors. https://gitlab.gnome.org/GNOME/gnome-mahjongg/-/blob/3.40.1/NEWS https://gitlab.gnome.org/GNOME/gnome- mahjongg/-/compare/3.40.0...3.40.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-mahjongg/+bug/2062038/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2060816] Re: App grid icon is Ubuntu logo, need to find override
That sounds wonderful, but we use the ubuntu session currently and it's too late to change that. Therefore, we'll have to just do a `dpkg- divert` `view-app-grid-ubuntu-symbolic` now, which means my existing `dpkg-divert` of `view-app-grid-symbolic` will need to change and I need to go back to the drawing board a bit. Not a huge issue, just minor inconvenience since I just uploaded that fix. ** Changed in: edubuntu-artwork (Ubuntu) Status: Fix Committed => In Progress -- 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/2060816 Title: App grid icon is Ubuntu logo, need to find override Status in Yaru Theme: Fix Released Status in edubuntu-artwork package in Ubuntu: In Progress Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: In Progress Status in yaru-theme package in Ubuntu: Fix Committed Bug description: The app grid icon is now the Ubuntu logo. We need to find a way to override this to the Edubuntu logo. To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/2060816/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2058819] Re: gnome-shell-extension-ubuntu-dock -dock asymmetrical
** Changed in: yaru-theme (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/2058819 Title: gnome-shell-extension-ubuntu-dock -dock asymmetrical Status in yaru-theme package in Ubuntu: Fix Released Bug description: gnome-shell-extension-ubuntu-dock 89ubuntu3 installed from https://ppa.launchpadcontent.net/ubuntu-desktop/ppa/ubuntu noble/main amd64 Packages icons are not centered in the dock. See attachment. The Ubuntu icon at bottom is centered. Note: I don't know if it's appropriate to open a bug for a PPA program. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-shell-extension-ubuntu-dock 89ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 23 19:31:51 2024 InstallationDate: Installed on 2024-03-10 (13 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240310) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/2058819/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2060816] Re: App grid icon is Ubuntu logo, need to find override
FYI we're going to provide a way to override this by defining a new
gnome shell session (you can inherit the ubuntu one) and the icon should
be named `view-app-grid-${currentMode}-symbolic` e.g. `view-app-grid-
edubuntu-symbolic`, otherwise the default (view-app-grid-symbolic) will
be used
** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
Status: New => In Progress
** Changed in: yaru-theme (Ubuntu)
Status: Triaged => Fix Committed
--
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/2060816
Title:
App grid icon is Ubuntu logo, need to find override
Status in Yaru Theme:
Fix Released
Status in edubuntu-artwork package in Ubuntu:
Fix Committed
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
In Progress
Status in yaru-theme package in Ubuntu:
Fix Committed
Bug description:
The app grid icon is now the Ubuntu logo. We need to find a way to
override this to the Edubuntu logo.
To manage notifications about this bug go to:
https://bugs.launchpad.net/yaru/+bug/2060816/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2061981] Re: chromium fails to start with non-standard home directory
1)
user_name@computer:~$ stat /home/department/user_name/
File: /home/department/user_name/
Size: 267 Blocks: 289IO Block: 16384 directory
Device: 27h/39d Inode: 9542Links: 146
Access: (0755/drwxr-xr-x) Uid: (X/user_name) Gid:
(/default_group)
Access: 2024-03-20 14:50:40.921533172 +0100
Modify: 2024-04-17 18:20:30.872510781 +0200
Change: 2024-04-17 18:20:30.872510781 +0200
Birth: 2019-06-03 16:14:43.032386913 +0200
2) as far as I know, no apparmor specific denials.
The non-standard home directory is added to the apparmor ${HOMEDIRS} paramater
(see
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2061981/comments/3)
The only error message I get is:
user_name@computer:~$ chromium
cannot update snap namespace: cannot expand mount entry (none
$HOME/.local/share none x-snapd.kind=ensure-dir,x-snapd.must-exist-dir=$HOME 0
0): cannot use invalid home directory "/home/department/user_name": permission
denied
snap-update-ns failed with code 1
--
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/2061981
Title:
chromium fails to start with non-standard home directory
Status in chromium-browser package in Ubuntu:
Confirmed
Status in snapd package in Ubuntu:
Confirmed
Bug description:
CURRENT WORKAROUND
--
snap disconnect chromium:dot-local-share-applications
snap disconnect chromium:dot-local-share-icons
Those are just "quality of life" interfaces (c.f. LP:1732482) that
most users probably do not even use, disconnecting them will cause no
breakage. (Of course, a proper diagnosis and fix is due.)
ORIGINAL REPORT
---
cannot update snap namespace: cannot expand mount entry (none
$HOME/.local/share none x-snapd.kind=ensure-dir,x-snapd.must-exist-
dir=$HOME 0 0): cannot use invalid home directory
"/home/department/user_name": permission denied
Fails to start on Ubuntu 22.04 for users with 'non-standard' home directory
/home/department/user_name
Used to work fine up to last week.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: chromium-browser 1:85.0.4183.83-0ubuntu2.22.04.1
ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13
Uname: Linux 6.5.0-27-generic x86_64
NonfreeKernelModules: zfs nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: XFCE
Date: Wed Apr 17 10:32:18 2024
InstallationDate: Installed on 2017-03-24 (2580 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
Snap.Changes:
ID Status Spawn Ready Summary
206 Error 2024-04-16T19:08:43+02:00 2024-04-16T19:16:51+02:00 Remove
"chromium" snap
207 Done2024-04-16T19:17:27+02:00 2024-04-16T19:18:44+02:00 Remove
"chromium" snap
208 Done2024-04-16T19:18:46+02:00 2024-04-16T19:19:47+02:00 Install
"chromium" snap
209 Done2024-04-17T10:31:58+02:00 2024-04-17T10:32:02+02:00 Connect
chromium:password-manager-service to snapd:password-manager-service
SourcePackage: chromium-browser
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2061981/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2061981] Re: chromium fails to start with non-standard home directory
I will do some tests myself for non-standard home directory. -- 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/2061981 Title: chromium fails to start with non-standard home directory Status in chromium-browser package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Bug description: CURRENT WORKAROUND -- snap disconnect chromium:dot-local-share-applications snap disconnect chromium:dot-local-share-icons Those are just "quality of life" interfaces (c.f. LP:1732482) that most users probably do not even use, disconnecting them will cause no breakage. (Of course, a proper diagnosis and fix is due.) ORIGINAL REPORT --- cannot update snap namespace: cannot expand mount entry (none $HOME/.local/share none x-snapd.kind=ensure-dir,x-snapd.must-exist- dir=$HOME 0 0): cannot use invalid home directory "/home/department/user_name": permission denied Fails to start on Ubuntu 22.04 for users with 'non-standard' home directory /home/department/user_name Used to work fine up to last week. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: chromium-browser 1:85.0.4183.83-0ubuntu2.22.04.1 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Wed Apr 17 10:32:18 2024 InstallationDate: Installed on 2017-03-24 (2580 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Snap.Changes: ID Status Spawn Ready Summary 206 Error 2024-04-16T19:08:43+02:00 2024-04-16T19:16:51+02:00 Remove "chromium" snap 207 Done2024-04-16T19:17:27+02:00 2024-04-16T19:18:44+02:00 Remove "chromium" snap 208 Done2024-04-16T19:18:46+02:00 2024-04-16T19:19:47+02:00 Install "chromium" snap 209 Done2024-04-17T10:31:58+02:00 2024-04-17T10:32:02+02:00 Connect chromium:password-manager-service to snapd:password-manager-service SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2061981/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2061981] Re: chromium fails to start with non-standard home directory
As Nathan correctly suggest, this behaviour relates to a snapd 2.62 new ability introduced for the personal files interface, to create missing parent directories of write paths/files indicated in the plug declaration. Release notes: https://forum.snapcraft.io/t/the-snapd- roadmap/1973 isPlausibleHome() is an early check (does not result in termination itself) to determine if the calling user have access to its supposed home directory, as a basic way to verify that unintended user cannot exploit the mechanism. In the reported case the personal-files interface connection results in a special type of mount entry that instructs creation of missing parent directories between $HOME and $HOME/.local/share. none $HOME/.local/share none x-snapd.kind=ensure-dir,x-snapd.must-exist- dir=$HOME 0 0 Because this entry exists (when the interface is connected), the result from isPlausibleHome() informs if directory creation within $HOME should be allowed or not. This is way disconnecting the interface would solve the problem. (1) Please `stat /home/department/user_name` (2) Does the "permission denied" result in any AppArmor denials? -- 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/2061981 Title: chromium fails to start with non-standard home directory Status in chromium-browser package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Bug description: CURRENT WORKAROUND -- snap disconnect chromium:dot-local-share-applications snap disconnect chromium:dot-local-share-icons Those are just "quality of life" interfaces (c.f. LP:1732482) that most users probably do not even use, disconnecting them will cause no breakage. (Of course, a proper diagnosis and fix is due.) ORIGINAL REPORT --- cannot update snap namespace: cannot expand mount entry (none $HOME/.local/share none x-snapd.kind=ensure-dir,x-snapd.must-exist- dir=$HOME 0 0): cannot use invalid home directory "/home/department/user_name": permission denied Fails to start on Ubuntu 22.04 for users with 'non-standard' home directory /home/department/user_name Used to work fine up to last week. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: chromium-browser 1:85.0.4183.83-0ubuntu2.22.04.1 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Wed Apr 17 10:32:18 2024 InstallationDate: Installed on 2017-03-24 (2580 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Snap.Changes: ID Status Spawn Ready Summary 206 Error 2024-04-16T19:08:43+02:00 2024-04-16T19:16:51+02:00 Remove "chromium" snap 207 Done2024-04-16T19:17:27+02:00 2024-04-16T19:18:44+02:00 Remove "chromium" snap 208 Done2024-04-16T19:18:46+02:00 2024-04-16T19:19:47+02:00 Install "chromium" snap 209 Done2024-04-17T10:31:58+02:00 2024-04-17T10:32:02+02:00 Connect chromium:password-manager-service to snapd:password-manager-service SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2061981/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2028054] Re: [MIR] python-rlpycairo
As I said in comment #4 - The binary package libsane-hpaio DOES NOT depend on the binary package hplip, not even indirectly, so the binary package hplip can get demoted to Universe. the binary package printer-driver-hpcups also does not depend on the binary package hplip, but printer-driver-hpcups itself can already get demoted to Universe as we replace the printer drivers by Printer Application Snaps (this driver provided by the HPLIP Printer Application, hplip-printer-app). So hp-scan as part of the binary package hplip will go to Universe, hp-sendfax as part of the binary package hplip-gui is already in Universe. - Now, keeping CUPS as DEB packages for the time being, we continue with libsane-hpaio and printer-driver-hpcups in Main, but we can demote the binary package hplip into Universe, so the dependency on python- reportlab goes completely into Universe, eliminating the need of this MIR at least from the printing-stack side. -- 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/2028054 Title: [MIR] python-rlpycairo Status in hplip package in Ubuntu: Confirmed Status in python-reportlab package in Ubuntu: Incomplete Status in python-rlpycairo package in Ubuntu: Incomplete Bug description: python-rlpycairo is a new dependency of python-reportlab (currently owned by Foundations). The only consumer of python-reportlab is hplip (owned by Desktop), apparently it needs it for scanning: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=651240 $ reverse-depends src:python-reportlab -c main -r mantic Reverse-Depends === * hplip (for python3-reportlab) Packages without architectures listed are reverse-dependencies in: amd64, arm64, armhf, ppc64el, s390x src:hplip -> src:python-reportlab -> src:python-rlpycairo -> src:freetype-py & src:ttf-bitstream-vera So from the above, it sounds like this new dependency is actually needed (after the reportlab package dropped its renderpm extension). It should be discussed between Foundations and Desktop who's owning those dependencies and doing the MIRs for python-rlpycairo, freetype- py and ttf-bitstream-vera To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/2028054/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2061153] Re: No login prompt or user list on login screen [JS ERROR: TypeError: this._button is undefined]
I'm not sure if there's any bug retest workflows to follow, but I can confirm this fixed the issue when using Gnome's remote connection. I will test HyperV later today. Thanks Marco and Daniel!! -- 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/2061153 Title: No login prompt or user list on login screen [JS ERROR: TypeError: this._button is undefined] Status in gnome-shell package in Ubuntu: Fix Released Bug description: I installed the 24.04 beta ISO (the version from 2024-04-12) on a HyperV VM. Running through the installer itself seemed fine, but after rebooting GDM seemed to start but doesn't offer any users to login with. Not even an "Other" button. GDM itself has definitely started, as the current time is visible at the top of the screen, and the network and accessibility icons are visible at the top right of the screen. But the center of the screen is blank. If I manually mount the drive and examine the journal logs, I see a "JS Error" from gnome-shell that seems likely to be related: Apr 12 14:47:29 jwilcox-u24b gnome-shell[1735]: Starting Authd!!! Apr 12 14:47:29 jwilcox-u24b gnome-shell[1735]: JS ERROR: TypeError: this._button is undefined _createSessionMenuButton@resource:///org/gnome/shell/gdm/loginDialog.js:663:13 _init@resource:///org/gnome/shell/gdm/loginDialog.js:589:14 LoginDialog@resource:///org/gnome/shell/gdm/loginDialog.js:487:4 _ensureUnlockDialog@resource:///org/gnome/shell/ui/screenShield.js:472:28 showDialog@resource:///org/gnome/shell/ui/screenShield.js:404:14 _initializeUI/<@resource:///org/gnome/shell/ui/main.js:317:26 _prepareStartupAnimation@resource:///org/gnome/shell/ui/layout.js:764:18 _loadBackground/signalIdhttps://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2061153/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2060816] Re: App grid icon is Ubuntu logo, need to find override
Oops, something's not quite right here. Fixing... ** Changed in: edubuntu-artwork (Ubuntu) Status: Fix Released => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/2060816 Title: App grid icon is Ubuntu logo, need to find override Status in Yaru Theme: Fix Released Status in edubuntu-artwork package in Ubuntu: In Progress Status in yaru-theme package in Ubuntu: Triaged Bug description: The app grid icon is now the Ubuntu logo. We need to find a way to override this to the Edubuntu logo. To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/2060816/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2062031] [NEW] Periodically Sound intermittantly working on 24.04
Public bug reported: Hello, I have 24.04 development branch on my tower pc and I notice last night sometimes the sound doesnt work I ran journalctl and heres my log Apr 09 22:07:13 Tower-PC kernel: Linux version 6.5.0-27-generic (buildd@lcy02-a> Apr 09 22:07:13 Tower-PC kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-6.5.0-2> Apr 09 22:07:13 Tower-PC kernel: KERNEL supported cpus: Apr 09 22:07:13 Tower-PC kernel: Intel GenuineIntel Apr 09 22:07:13 Tower-PC kernel: AMD AuthenticAMD Apr 09 22:07:13 Tower-PC kernel: Hygon HygonGenuine Apr 09 22:07:13 Tower-PC kernel: Centaur CentaurHauls Apr 09 22:07:13 Tower-PC kernel: zhaoxin Shanghai Apr 09 22:07:13 Tower-PC kernel: BIOS-provided physical RAM map: Apr 09 22:07:13 Tower-PC kernel: BIOS-e820: [mem 0x-0x0> Apr 09 22:07:13 Tower-PC kernel: BIOS-e820: [mem 0x0010-0xb> Apr 09 22:07:13 Tower-PC kernel: BIOS-e820: [mem 0xbae21000-0xb> Apr 09 22:07:13 Tower-PC kernel: BIOS-e820: [mem 0xbb10d000-0xb> Apr 09 22:07:13 Tower-PC kernel: BIOS-e820: [mem 0xbb11d000-0xb> Apr 09 22:07:13 Tower-PC kernel: BIOS-e820: [mem 0xbbe7b000-0xb> Apr 09 22:07:13 Tower-PC kernel: BIOS-e820: [mem 0xbca14000-0xb> Apr 09 22:07:13 Tower-PC kernel: BIOS-e820: [mem 0xbca15000-0xb> Apr 09 22:07:13 Tower-PC kernel: BIOS-e820: [mem 0xbcc18000-0xb> Apr 09 22:07:13 Tower-PC kernel: BIOS-e820: [mem 0xbd043000-0xb> Apr 09 22:07:13 Tower-PC kernel: BIOS-e820: [mem 0xbd7f4000-0xb> I suspect its a pulseaudio issue i had to install it yesterday bc it was a dependancy of another app so i will try uninstalling it. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2062031 Title: Periodically Sound intermittantly working on 24.04 Status in pulseaudio package in Ubuntu: New Bug description: Hello, I have 24.04 development branch on my tower pc and I notice last night sometimes the sound doesnt work I ran journalctl and heres my log Apr 09 22:07:13 Tower-PC kernel: Linux version 6.5.0-27-generic (buildd@lcy02-a> Apr 09 22:07:13 Tower-PC kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-6.5.0-2> Apr 09 22:07:13 Tower-PC kernel: KERNEL supported cpus: Apr 09 22:07:13 Tower-PC kernel: Intel GenuineIntel Apr 09 22:07:13 Tower-PC kernel: AMD AuthenticAMD Apr 09 22:07:13 Tower-PC kernel: Hygon HygonGenuine Apr 09 22:07:13 Tower-PC kernel: Centaur CentaurHauls Apr 09 22:07:13 Tower-PC kernel: zhaoxin Shanghai Apr 09 22:07:13 Tower-PC kernel: BIOS-provided physical RAM map: Apr 09 22:07:13 Tower-PC kernel: BIOS-e820: [mem 0x-0x0> Apr 09 22:07:13 Tower-PC kernel: BIOS-e820: [mem 0x0010-0xb> Apr 09 22:07:13 Tower-PC kernel: BIOS-e820: [mem 0xbae21000-0xb> Apr 09 22:07:13 Tower-PC kernel: BIOS-e820: [mem 0xbb10d000-0xb> Apr 09 22:07:13 Tower-PC kernel: BIOS-e820: [mem 0xbb11d000-0xb> Apr 09 22:07:13 Tower-PC kernel: BIOS-e820: [mem 0xbbe7b000-0xb> Apr 09 22:07:13 Tower-PC kernel: BIOS-e820: [mem 0xbca14000-0xb> Apr 09 22:07:13 Tower-PC kernel: BIOS-e820: [mem 0xbca15000-0xb> Apr 09 22:07:13 Tower-PC kernel: BIOS-e820: [mem 0xbcc18000-0xb> Apr 09 22:07:13 Tower-PC kernel: BIOS-e820: [mem 0xbd043000-0xb> Apr 09 22:07:13 Tower-PC kernel: BIOS-e820: [mem 0xbd7f4000-0xb> I suspect its a pulseaudio issue i had to install it yesterday bc it was a dependancy of another app so i will try uninstalling it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2062031/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2028054] Re: [MIR] python-rlpycairo
** Tags removed: foundations-todo -- 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/2028054 Title: [MIR] python-rlpycairo Status in hplip package in Ubuntu: Confirmed Status in python-reportlab package in Ubuntu: Incomplete Status in python-rlpycairo package in Ubuntu: Incomplete Bug description: python-rlpycairo is a new dependency of python-reportlab (currently owned by Foundations). The only consumer of python-reportlab is hplip (owned by Desktop), apparently it needs it for scanning: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=651240 $ reverse-depends src:python-reportlab -c main -r mantic Reverse-Depends === * hplip (for python3-reportlab) Packages without architectures listed are reverse-dependencies in: amd64, arm64, armhf, ppc64el, s390x src:hplip -> src:python-reportlab -> src:python-rlpycairo -> src:freetype-py & src:ttf-bitstream-vera So from the above, it sounds like this new dependency is actually needed (after the reportlab package dropped its renderpm extension). It should be discussed between Foundations and Desktop who's owning those dependencies and doing the MIRs for python-rlpycairo, freetype- py and ttf-bitstream-vera To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/2028054/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2054827] Re: [regression] GUI crashed after installed proposed package after mesa updates
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2054827 Title: [regression] GUI crashed after installed proposed package after mesa updates Status in mesa package in Ubuntu: Confirmed Bug description: Dear all, after the upgrade of various mesa packages on monday (23.2.1-1ubuntu3.1~22.04.2 from repo jammy-updates), I suffer similar symptoms at startup (causing a blank screen with no GDM running and message "something went wrong) than those reported there https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2051068. I am using 22.04.3 LTS "Jammy Jellyfish" with kernel 6.1.0-1034-oem but the issue remains with kernel 6.2.0-26-generic). I have a Dell precision 5480. The issue occurs if I use either the nouveau driver or the proprietary nvidia driver (535 from ubuntu repo) with profile "on-demand". The problem is solved with proprietary driver and profile "nvidia" (but costs a lot to the battery lifetime). I enclose the syslog before the crash which mentions an issue with mesa drivers. I will enclose also the apt log describing the operations that have cause the bug I suspect that this bug is related to this one https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2051068 Description: Ubuntu 22.04.4 LTS Release: 22.04 libegl-mesa0: Installé : 23.2.1-1ubuntu3.1~22.04.2 Candidat : 23.2.1-1ubuntu3.1~22.04.2 Table de version : *** 23.2.1-1ubuntu3.1~22.04.2 500 500 http://fr.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 22.0.1-1ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages libgl1-mesa-dri: Installé : 23.2.1-1ubuntu3.1~22.04.2 Candidat : 23.2.1-1ubuntu3.1~22.04.2 Table de version : *** 23.2.1-1ubuntu3.1~22.04.2 500 500 http://fr.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 22.0.1-1ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages [Summary] After upgrade of packages last monday, reboot system when using nouveau driver, nvidia-driver with on-demand profile, with kernel 6.1oem, 6.2 generic. It works if using nvidia-driver with profile nvidia. [Steps to reproduce] 1. Boot into OS 2. sudo apt update 3. sudo apt upgrade 4. After upgrade process finished, reboot system. 5. GUI crashed. [Expected result] GUI displayed normally [Actual result] GUI crashed [Failure rate] 100% ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libegl-mesa0 23.2.1-1ubuntu3.1~22.04.2 ProcVersionSignature: Ubuntu 6.1.0-1034.34-oem 6.1.73 Uname: Linux 6.1.0-1034-oem x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.154.05 Thu Dec 28 15:37:48 UTC 2023 GCC version: gcc version 12.3.0 (Ubuntu 12.3.0-1ubuntu1~22.04) ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 23 16:21:34 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/535.154.05, 6.1.0-1034-oem, x86_64: installed nvidia/535.154.05, 6.2.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:a7a0] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0c40] Subsystem: Dell Device [1028:0c40] InstallationDate: Installed on 2024-01-12 (42 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: Dell Inc. Precision 5480 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.1.0-1034-oem root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2023 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.0 dmi.board.name: 0VCJYY dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.16 dmi.modalias: dmi:bvnDellInc.:bvr1.8.0:bd12/18/2023:br1.8:efr1.16:svnDellInc.:pnPrecision5480:pvr:rvnDellInc.:rn0VCJYY:rvrA01:cvnDellInc.:ct10:cvr:sku0C40: dmi.product.family:
[Desktop-packages] [Bug 2054827] Re: [regression] GUI crashed after installed proposed package after mesa updates
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2054827 Title: [regression] GUI crashed after installed proposed package after mesa updates Status in mesa package in Ubuntu: Confirmed Bug description: Dear all, after the upgrade of various mesa packages on monday (23.2.1-1ubuntu3.1~22.04.2 from repo jammy-updates), I suffer similar symptoms at startup (causing a blank screen with no GDM running and message "something went wrong) than those reported there https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2051068. I am using 22.04.3 LTS "Jammy Jellyfish" with kernel 6.1.0-1034-oem but the issue remains with kernel 6.2.0-26-generic). I have a Dell precision 5480. The issue occurs if I use either the nouveau driver or the proprietary nvidia driver (535 from ubuntu repo) with profile "on-demand". The problem is solved with proprietary driver and profile "nvidia" (but costs a lot to the battery lifetime). I enclose the syslog before the crash which mentions an issue with mesa drivers. I will enclose also the apt log describing the operations that have cause the bug I suspect that this bug is related to this one https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2051068 Description: Ubuntu 22.04.4 LTS Release: 22.04 libegl-mesa0: Installé : 23.2.1-1ubuntu3.1~22.04.2 Candidat : 23.2.1-1ubuntu3.1~22.04.2 Table de version : *** 23.2.1-1ubuntu3.1~22.04.2 500 500 http://fr.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 22.0.1-1ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages libgl1-mesa-dri: Installé : 23.2.1-1ubuntu3.1~22.04.2 Candidat : 23.2.1-1ubuntu3.1~22.04.2 Table de version : *** 23.2.1-1ubuntu3.1~22.04.2 500 500 http://fr.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 22.0.1-1ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages [Summary] After upgrade of packages last monday, reboot system when using nouveau driver, nvidia-driver with on-demand profile, with kernel 6.1oem, 6.2 generic. It works if using nvidia-driver with profile nvidia. [Steps to reproduce] 1. Boot into OS 2. sudo apt update 3. sudo apt upgrade 4. After upgrade process finished, reboot system. 5. GUI crashed. [Expected result] GUI displayed normally [Actual result] GUI crashed [Failure rate] 100% ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libegl-mesa0 23.2.1-1ubuntu3.1~22.04.2 ProcVersionSignature: Ubuntu 6.1.0-1034.34-oem 6.1.73 Uname: Linux 6.1.0-1034-oem x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.154.05 Thu Dec 28 15:37:48 UTC 2023 GCC version: gcc version 12.3.0 (Ubuntu 12.3.0-1ubuntu1~22.04) ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 23 16:21:34 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/535.154.05, 6.1.0-1034-oem, x86_64: installed nvidia/535.154.05, 6.2.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:a7a0] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0c40] Subsystem: Dell Device [1028:0c40] InstallationDate: Installed on 2024-01-12 (42 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: Dell Inc. Precision 5480 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.1.0-1034-oem root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2023 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.0 dmi.board.name: 0VCJYY dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.16 dmi.modalias:
[Desktop-packages] [Bug 2061880] Re: Crash on Xubuntu 24.04 Beta when trying to RDP
Until problem is resolved, as workaround You may install snap version, which seems to be unaffected. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/2061880 Title: Crash on Xubuntu 24.04 Beta when trying to RDP Status in remmina package in Ubuntu: Confirmed Bug description: This could be related to https://gitlab.com/Remmina/Remmina/-/issues/3090 remmina-Message: 19:16:12.858: Remmina does not log all output statements. Turn on more verbose output by using "G_MESSAGES_DEBUG=remmina" as an environment variable. More info available on the Remmina wiki at: https://gitlab.com/Remmina/Remmina/-/wikis/Usage/Remmina-debugging (org.remmina.Remmina:15044): Gtk-WARNING **: 19:16:12.981: gtk_menu_attach_to_widget(): menu already attached to GtkMenuItem [19:16:16:108] [15044:3b0f] [ERROR][com.freerdp.common.settings] - [freerdp_settings_get_bool]: Invalid key index 0 [FreeRDP_instance|FREERDP_SETTINGS_TYPE_POINTER] [19:16:16:108] [15044:3b0f] [FATAL][com.freerdp.winpr.assert] - [winpr_int_assert]: FALSE [obj-x86_64-linux-gnu/libfreerdp/CMakeFiles/freerdp.dir/compiler_depend.ts:freerdp_settings_get_bool:634] [19:16:16:108] [15044:3b0f] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 0: dli_fname=/lib/x86_64-linux-gnu/libwinpr3.so.3 [0x72d1f542b000], dli_sname=winpr_backtrace [0x72d1f5497540] [19:16:16:108] [15044:3b0f] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 1: dli_fname=/lib/x86_64-linux-gnu/libwinpr3.so.3 [0x72d1f542b000], dli_sname=winpr_log_backtrace_ex [0x72d1f549efe0] [19:16:16:108] [15044:3b0f] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 2: dli_fname=/lib/x86_64-linux-gnu/libfreerdp3.so.3 [0x72d1efc0], dli_sname=(null) [(nil)] [19:16:16:108] [15044:3b0f] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 3: dli_fname=/lib/x86_64-linux-gnu/libfreerdp3.so.3 [0x72d1efc0], dli_sname=freerdp_settings_get_bool [0x72d1efc648a0] [19:16:16:108] [15044:3b0f] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 4: dli_fname=/usr/lib/x86_64-linux-gnu/remmina/plugins/remmina-plugin-rdp.so [0x72d1f5efa000], dli_sname=(null) [(nil)] [19:16:16:108] [15044:3b0f] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 5: dli_fname=/usr/lib/x86_64-linux-gnu/remmina/plugins/remmina-plugin-rdp.so [0x72d1f5efa000], dli_sname=(null) [(nil)] [19:16:16:108] [15044:3b0f] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 6: dli_fname=/usr/bin/../lib/x86_64-linux-gnu/libc.so.6 [0x72d1f9a0], dli_sname=(null) [(nil)] [19:16:16:108] [15044:3b0f] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 7: dli_fname=/usr/bin/../lib/x86_64-linux-gnu/libc.so.6 [0x72d1f9a0], dli_sname=(null) [(nil)] [19:16:16:108] [15044:3b0f] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 8: unresolvable, address=(nil) Aborted (core dumped) wil@williambell:/var/crash$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/2061880/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2059847] Re: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?"
This bug was fixed in the package mutter - 46.0-1ubuntu7 --- mutter (46.0-1ubuntu7) noble; urgency=medium [ Daniel van Vugt ] * debian/control: mutter-common now breaks libmutter back to focal. Because we have dropped X11 fractional scaling support for now, `org.gnome.mutter.x11.gschema.xml` is no longer shipped and those older versions of libmutter will fail to start(LP: #2060423) * Add compositor-sync-ring-Allow-the-gpu_fence-to-be-moved.patch to fix lag and freezes on the Nvidia Xorg driver (LP: #2059847) -- Jeremy Bícha Tue, 16 Apr 2024 08:46:54 -0400 ** Changed in: mutter (Ubuntu Noble) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2059847 Title: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?" Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: In Progress Status in mutter source package in Mantic: In Progress Status in mutter source package in Noble: Fix Released Bug description: [ Impact ] Input or the entire screen may freeze at times on systems using the Nvidia Xorg driver with GNOME. [ Test Plan ] 0. Set up a desktop with Nvidia driver 545 or 550. 1. Log into Ubuntu, ensuring it's a Xorg session. 2. Open a Terminal, resize it vigorously, and type several lines of text. 3. Run: journalctl -b0 | grep MetaSyncRing 4. Verify the above command does NOT show "MetaSyncRing" messages such as: Window manager warning: MetaSyncRing: Sync object is not ready -- were events handled properly? Window manager warning: MetaSyncRing: Sync object is not ready -- were events handled properly? Window manager warning: MetaSyncRing: Sync object is not ready -- were events handled properly? Window manager warning: MetaSyncRing: Too many reboots -- disabling [ Where problems could occur ] Anywhere in Nvidia (proprietary driver) Xorg sessions since the code being modified is only used with that driver. [ Original Description ] There is a noticeable delay in input while using the native terminal. I belive it was caused by a recent software update, as this issue is relatively new. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 30 19:57:13 2024 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2024-03-30 (0 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) SourcePackage: ubiquity Symptom: installation UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2059847/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2060575] Re: gnome-keyring fails to automatically unlock login keyring after recent updates in noble
This bug was fixed in the package gnome-shell - 46.0-0ubuntu5 --- gnome-shell (46.0-0ubuntu5) noble; urgency=medium [ Daniel van Vugt ] * Drop loginDialog-Create-footer-container.patch - it's buggy and still under active development (LP: #2060893) [ Marco Trevisan (Treviño) ] * debian/patches/ubuntu-authd: Hide the right button if there are no sessions to choose (LP: #2061153) * debian/patches/ubuntu-authd: Do not start an unavailable authentication service (LP: #2060575) * d/p/ubuntu-authd: Fix selection of multi-factor auth modes (related to lp:2060546) -- Marco Trevisan (Treviño) Wed, 17 Apr 2024 07:45:42 +0200 ** Changed in: gnome-shell (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/2060575 Title: gnome-keyring fails to automatically unlock login keyring after recent updates in noble Status in gdm3 package in Ubuntu: Opinion Status in gnome-keyring package in Ubuntu: Won't Fix Status in gnome-shell package in Ubuntu: Fix Released Bug description: After installing recent updates in 24.04, upon logging in the gnome- shell based UI pops up saying that the login keyring was not unlocked and asking for the users password to be input to unlock it. Similarly a second, non-gnome-shell based UI is also present asking the same thing. Will try and get a screenshot to attach. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: libpam-gnome-keyring 46.1-2build1 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 9 06:16:46 2024 InstallationDate: Installed on 2021-08-03 (980 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210802) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-keyring UpgradeStatus: Upgraded to noble on 2024-01-31 (68 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2060575/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2060423] Re: gnome-shell crashes ("Oh no! Something has gone wrong.") instead of displaying a login screen (mutter-common package version mismatch)
This bug was fixed in the package mutter - 46.0-1ubuntu7
---
mutter (46.0-1ubuntu7) noble; urgency=medium
[ Daniel van Vugt ]
* debian/control: mutter-common now breaks libmutter back to focal.
Because we have dropped X11 fractional scaling support for now,
`org.gnome.mutter.x11.gschema.xml` is no longer shipped and those
older versions of libmutter will fail to start(LP: #2060423)
* Add compositor-sync-ring-Allow-the-gpu_fence-to-be-moved.patch
to fix lag and freezes on the Nvidia Xorg driver (LP: #2059847)
-- Jeremy Bícha Tue, 16 Apr 2024 08:46:54 -0400
** Changed in: mutter (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2060423
Title:
gnome-shell crashes ("Oh no! Something has gone wrong.") instead of
displaying a login screen (mutter-common package version mismatch)
Status in mutter package in Ubuntu:
Fix Released
Bug description:
gnome-shell crashes instead of displaying a login screen:
gnome-shell[1954]: Running GNOME Shell (using mutter 45.3) as a Wayland
display server
gnome-shell[1954]: Settings schema 'org.gnome.mutter.x11' is not installed
It seems the cause is a package version mismatch in mutter-common:
ii gir1.2-mutter-13:amd64 45.3-1ubuntu1
amd64GObject introspection data for Mutter
ii libmutter-13-0:amd64 45.3-1ubuntu1
amd64window manager library from the Mutter window
manager
ii libmutter-13-dev:amd64 45.3-1ubuntu1
amd64Development files for the Mutter window manager
ii libmutter-test-13 45.3-1ubuntu1
amd64Test helper library for GNOME's window manager
library
ii mutter 45.3-1ubuntu1
amd64Example window manager using GNOME's window manager
library
ii mutter-13-tests45.3-1ubuntu1
amd64Tests for GNOME's window manager library
ii mutter-common 46.0-1ubuntu6
all shared files for the Mutter window manager
ii mutter-common-bin 45.3-1ubuntu1
amd64shared programs for the Mutter window manager
Downgrading mutter-common to
https://launchpad.net/ubuntu/+source/mutter/45.3-1ubuntu1/+build/27621415/+files/mutter-
common_45.3-1ubuntu1_all.deb appears to fix it.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2060423/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2060893] Re: Ubuntu logo on the login screen jumps up and disappears after selecting the user
This bug was fixed in the package gnome-shell - 46.0-0ubuntu5 --- gnome-shell (46.0-0ubuntu5) noble; urgency=medium [ Daniel van Vugt ] * Drop loginDialog-Create-footer-container.patch - it's buggy and still under active development (LP: #2060893) [ Marco Trevisan (Treviño) ] * debian/patches/ubuntu-authd: Hide the right button if there are no sessions to choose (LP: #2061153) * debian/patches/ubuntu-authd: Do not start an unavailable authentication service (LP: #2060575) * d/p/ubuntu-authd: Fix selection of multi-factor auth modes (related to lp:2060546) -- Marco Trevisan (Treviño) Wed, 17 Apr 2024 07:45:42 +0200 ** Changed in: gnome-shell (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2060893 Title: Ubuntu logo on the login screen jumps up and disappears after selecting the user Status in gnome-shell package in Ubuntu: Fix Released Status in yaru-theme package in Ubuntu: Invalid Bug description: Ubuntu logo on the login screen jumps up after selecting the user. Be careful to avoid confusing this with bug 1872594. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2060893/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2061153] Re: No login prompt or user list on login screen [JS ERROR: TypeError: this._button is undefined]
This bug was fixed in the package gnome-shell - 46.0-0ubuntu5 --- gnome-shell (46.0-0ubuntu5) noble; urgency=medium [ Daniel van Vugt ] * Drop loginDialog-Create-footer-container.patch - it's buggy and still under active development (LP: #2060893) [ Marco Trevisan (Treviño) ] * debian/patches/ubuntu-authd: Hide the right button if there are no sessions to choose (LP: #2061153) * debian/patches/ubuntu-authd: Do not start an unavailable authentication service (LP: #2060575) * d/p/ubuntu-authd: Fix selection of multi-factor auth modes (related to lp:2060546) -- Marco Trevisan (Treviño) Wed, 17 Apr 2024 07:45:42 +0200 ** Changed in: gnome-shell (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2061153 Title: No login prompt or user list on login screen [JS ERROR: TypeError: this._button is undefined] Status in gnome-shell package in Ubuntu: Fix Released Bug description: I installed the 24.04 beta ISO (the version from 2024-04-12) on a HyperV VM. Running through the installer itself seemed fine, but after rebooting GDM seemed to start but doesn't offer any users to login with. Not even an "Other" button. GDM itself has definitely started, as the current time is visible at the top of the screen, and the network and accessibility icons are visible at the top right of the screen. But the center of the screen is blank. If I manually mount the drive and examine the journal logs, I see a "JS Error" from gnome-shell that seems likely to be related: Apr 12 14:47:29 jwilcox-u24b gnome-shell[1735]: Starting Authd!!! Apr 12 14:47:29 jwilcox-u24b gnome-shell[1735]: JS ERROR: TypeError: this._button is undefined _createSessionMenuButton@resource:///org/gnome/shell/gdm/loginDialog.js:663:13 _init@resource:///org/gnome/shell/gdm/loginDialog.js:589:14 LoginDialog@resource:///org/gnome/shell/gdm/loginDialog.js:487:4 _ensureUnlockDialog@resource:///org/gnome/shell/ui/screenShield.js:472:28 showDialog@resource:///org/gnome/shell/ui/screenShield.js:404:14 _initializeUI/<@resource:///org/gnome/shell/ui/main.js:317:26 _prepareStartupAnimation@resource:///org/gnome/shell/ui/layout.js:764:18 _loadBackground/signalIdhttps://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2061153/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1980836] Re: Regression in Ubuntu 22.04: Content of form field stored invisibly
I have a PDF form that provably works in 20.04's version of Evince (poppler) but does not in 22.04, so came to search for an existing bug. I can confirm this patch fixes the issue for me too on 22.04. I built it now at https://launchpad.net/~timo-jyrinki/+archive/ubuntu/poppler-jammy and confirmed it works. Annoyingly publishing is taking ages so the PPA repository is not ready yet, but I downloaded the debs manually from the amd64 build for testing. Since I happen to be a Ubuntu developer too, I now uploaded it with the correct version number to the jammy's queue https://launchpad.net/ubuntu/jammy/+queue?queue_state=1_text=poppler - let's see if it will get accepted eventually in the proposed SRUs from there. If it will, this bug will be updated asking for a verification of the fix by using the exact version from proposed to get it forward. -- 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/1980836 Title: Regression in Ubuntu 22.04: Content of form field stored invisibly Status in Poppler: Fix Released Status in evince package in Ubuntu: Invalid Status in poppler package in Ubuntu: Triaged Bug description: Evince on Ubuntu 22.04 is not able to handle some PDF forms correctly anymore that it was able to handle on Ubuntu 21.10 and on Ubuntu 20.04. The symptom is that one can edit the form content and also save it, but that the entered text is only visible when the form field is focused and in edit mode. Otherwise the text it is invisible, also on printouts. Such bugs have been reported against Evince for a long time (e.g., https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/265033) but I am reporting this as a new bug because for the current form with which I am experiencing this it is a regression. I have attached the problematic form with two form fields filled out, one in the upper left corner and the big one in the lower half. I have produced this by taking the original, empty form (produced by somebody else) and first opened it in Evince 41.4, which I have installed from the snap package (revision 1017) on Ubuntu 22.04. I entered text in the upper left field and saved the form. Then I opened the PDF in Evince 42.3 from the apt package of Ubuntu 22.04 and entered text in the big field and saved the form. Evince 3.36 on Ubuntu 20.04 has the same (correct) behavior as Evince 41.4. When I open the PDF again, only the text in the first field is visible. The text in the second field is visible only if I click into the field. The visibility of the field contents is the same for Evince 41.4 (snap), Evince 42.3 (apt), and Okular 20.12.3 (snap). So it seems that the problem is with Evince 42.3 incorrectly saving the field content, not with displaying it. Firefox shows and prints the content of both fields, though. Note that I cannot switch back to Evince 41 because for some other forms that I have the exact same problem happens only with the old version and the new version fixes it. So it seems that something changed that fixed it for some forms and broke it for others. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 42.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jul 6 14:32:27 2022 InstallationDate: Installed on 2021-11-26 (222 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RebootRequiredPkgs: Error: path contained symlinks. Snap.Changes: ID Status Spawn Bereit Zusammenfassung 137 Done2022-07-06T12:48:33+02:00 2022-07-06T12:48:41+02:00 Installiere "evince" Snap SourcePackage: evince UpgradeStatus: Upgraded to jammy on 2022-06-22 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/1980836/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2061981] Re: chromium fails to start with non-standard home directory
Thanks!
As a note for self, I diffed snapd 2.61.2 and 2.62 and found in
cmd/snap-update-ns/user.go:
--->
+func isPlausibleHome(path string) error {
+ if path == "" {
+ return fmt.Errorf("cannot allow empty path")
+ }
+ if path != filepath.Clean(path) {
+ return fmt.Errorf("cannot allow unclean path")
+ }
+ if !filepath.IsAbs(path) {
+ return fmt.Errorf("cannot allow relative path")
+ }
+ const openFlags = syscall.O_NOFOLLOW | syscall.O_CLOEXEC |
syscall.O_DIRECTORY
+ fd, err := sysOpen(path, openFlags, 0)
+ if err != nil {
+ return err
+ }
+ sysClose(fd)
+ return nil
+}
<---
--->
+ if err := isPlausibleHome(realHome); err != nil {
+ realHomeError = fmt.Errorf("cannot use invalid home directory
%q: %v", realHome, err)
<---
It remains to be ascertained whether this lack of permission always
existed but didn't cause the launch of the snap to fail.
--
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/2061981
Title:
chromium fails to start with non-standard home directory
Status in chromium-browser package in Ubuntu:
Confirmed
Status in snapd package in Ubuntu:
Confirmed
Bug description:
CURRENT WORKAROUND
--
snap disconnect chromium:dot-local-share-applications
snap disconnect chromium:dot-local-share-icons
Those are just "quality of life" interfaces (c.f. LP:1732482) that
most users probably do not even use, disconnecting them will cause no
breakage. (Of course, a proper diagnosis and fix is due.)
ORIGINAL REPORT
---
cannot update snap namespace: cannot expand mount entry (none
$HOME/.local/share none x-snapd.kind=ensure-dir,x-snapd.must-exist-
dir=$HOME 0 0): cannot use invalid home directory
"/home/department/user_name": permission denied
Fails to start on Ubuntu 22.04 for users with 'non-standard' home directory
/home/department/user_name
Used to work fine up to last week.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: chromium-browser 1:85.0.4183.83-0ubuntu2.22.04.1
ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13
Uname: Linux 6.5.0-27-generic x86_64
NonfreeKernelModules: zfs nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: XFCE
Date: Wed Apr 17 10:32:18 2024
InstallationDate: Installed on 2017-03-24 (2580 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
Snap.Changes:
ID Status Spawn Ready Summary
206 Error 2024-04-16T19:08:43+02:00 2024-04-16T19:16:51+02:00 Remove
"chromium" snap
207 Done2024-04-16T19:17:27+02:00 2024-04-16T19:18:44+02:00 Remove
"chromium" snap
208 Done2024-04-16T19:18:46+02:00 2024-04-16T19:19:47+02:00 Install
"chromium" snap
209 Done2024-04-17T10:31:58+02:00 2024-04-17T10:32:02+02:00 Connect
chromium:password-manager-service to snapd:password-manager-service
SourcePackage: chromium-browser
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2061981/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2061981] Re: chromium fails to start with non-standard home directory
Reverting snapd fixes it for me too on multiple computers. -- 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/2061981 Title: chromium fails to start with non-standard home directory Status in chromium-browser package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Bug description: CURRENT WORKAROUND -- snap disconnect chromium:dot-local-share-applications snap disconnect chromium:dot-local-share-icons Those are just "quality of life" interfaces (c.f. LP:1732482) that most users probably do not even use, disconnecting them will cause no breakage. (Of course, a proper diagnosis and fix is due.) ORIGINAL REPORT --- cannot update snap namespace: cannot expand mount entry (none $HOME/.local/share none x-snapd.kind=ensure-dir,x-snapd.must-exist- dir=$HOME 0 0): cannot use invalid home directory "/home/department/user_name": permission denied Fails to start on Ubuntu 22.04 for users with 'non-standard' home directory /home/department/user_name Used to work fine up to last week. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: chromium-browser 1:85.0.4183.83-0ubuntu2.22.04.1 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Wed Apr 17 10:32:18 2024 InstallationDate: Installed on 2017-03-24 (2580 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Snap.Changes: ID Status Spawn Ready Summary 206 Error 2024-04-16T19:08:43+02:00 2024-04-16T19:16:51+02:00 Remove "chromium" snap 207 Done2024-04-16T19:17:27+02:00 2024-04-16T19:18:44+02:00 Remove "chromium" snap 208 Done2024-04-16T19:18:46+02:00 2024-04-16T19:19:47+02:00 Install "chromium" snap 209 Done2024-04-17T10:31:58+02:00 2024-04-17T10:32:02+02:00 Connect chromium:password-manager-service to snapd:password-manager-service SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2061981/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2060400] Re: Remmina crashes instantly when trying to open a remote session
fwiw, the snap works, however it won't import my (many) RDP profiles
from ~/.local/share/remmina ("cannot import {file}").
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to remmina in Ubuntu.
https://bugs.launchpad.net/bugs/2060400
Title:
Remmina crashes instantly when trying to open a remote session
Status in remmina package in Ubuntu:
Confirmed
Bug description:
I've been testing Noble for a couple of weeks and Remmina has not been
working. Fully upto date with regards to updates now and it's still
crashing.
The initial windows comes up allowing you to select a session. The
various preference dialogues seem to work but as soon as you try to
initiate a remote session it crashes instantly.
No crash is shown on the command line.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: remmina 1.4.35+dfsg-0ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
Uname: Linux 6.8.0-11-generic x86_64
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 7 20:17:02 2024
InstallationDate: Installed on 2024-03-25 (13 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240323)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
SourcePackage: remmina
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/2060400/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2061981] Re: chromium fails to start with non-standard home directory
Thank you very much for testing that, having the input of the directly affected user is always highly valuable for debugging. ** Description changed: - chromium 123.0.6312.122 2821 latest/stablecanonical + CURRENT WORKAROUND + -- + + snap disconnect chromium:dot-local-share-applications + snap disconnect chromium:dot-local-share-icons + + Those are just "quality of life" interfaces (c.f. LP:1732482) that most + users probably do not even use, disconnecting them will cause no + breakage. (Of course, a proper diagnosis and fix is due.) + + ORIGINAL REPORT + --- cannot update snap namespace: cannot expand mount entry (none $HOME/.local/share none x-snapd.kind=ensure-dir,x-snapd.must-exist- dir=$HOME 0 0): cannot use invalid home directory "/home/department/user_name": permission denied Fails to start on Ubuntu 22.04 for users with 'non-standard' home directory /home/department/user_name Used to work fine up to last week. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: chromium-browser 1:85.0.4183.83-0ubuntu2.22.04.1 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Wed Apr 17 10:32:18 2024 InstallationDate: Installed on 2017-03-24 (2580 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Snap.Changes: - ID Status Spawn Ready Summary - 206 Error 2024-04-16T19:08:43+02:00 2024-04-16T19:16:51+02:00 Remove "chromium" snap - 207 Done2024-04-16T19:17:27+02:00 2024-04-16T19:18:44+02:00 Remove "chromium" snap - 208 Done2024-04-16T19:18:46+02:00 2024-04-16T19:19:47+02:00 Install "chromium" snap - 209 Done2024-04-17T10:31:58+02:00 2024-04-17T10:32:02+02:00 Connect chromium:password-manager-service to snapd:password-manager-service + ID Status Spawn Ready Summary + 206 Error 2024-04-16T19:08:43+02:00 2024-04-16T19:16:51+02:00 Remove "chromium" snap + 207 Done2024-04-16T19:17:27+02:00 2024-04-16T19:18:44+02:00 Remove "chromium" snap + 208 Done2024-04-16T19:18:46+02:00 2024-04-16T19:19:47+02:00 Install "chromium" snap + 209 Done2024-04-17T10:31:58+02:00 2024-04-17T10:32:02+02:00 Connect chromium:password-manager-service to snapd:password-manager-service SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) ** Changed in: chromium-browser (Ubuntu) Importance: Undecided => High ** Changed in: chromium-browser (Ubuntu) Assignee: (unassigned) => Nathan Teodosio (nteodosio) -- 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/2061981 Title: chromium fails to start with non-standard home directory Status in chromium-browser package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Bug description: CURRENT WORKAROUND -- snap disconnect chromium:dot-local-share-applications snap disconnect chromium:dot-local-share-icons Those are just "quality of life" interfaces (c.f. LP:1732482) that most users probably do not even use, disconnecting them will cause no breakage. (Of course, a proper diagnosis and fix is due.) ORIGINAL REPORT --- cannot update snap namespace: cannot expand mount entry (none $HOME/.local/share none x-snapd.kind=ensure-dir,x-snapd.must-exist- dir=$HOME 0 0): cannot use invalid home directory "/home/department/user_name": permission denied Fails to start on Ubuntu 22.04 for users with 'non-standard' home directory /home/department/user_name Used to work fine up to last week. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: chromium-browser 1:85.0.4183.83-0ubuntu2.22.04.1 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Wed Apr 17 10:32:18 2024 InstallationDate: Installed on 2017-03-24 (2580 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Snap.Changes: ID Status Spawn Ready Summary 206 Error 2024-04-16T19:08:43+02:00 2024-04-16T19:16:51+02:00 Remove "chromium" snap 207 Done2024-04-16T19:17:27+02:00 2024-04-16T19:18:44+02:00 Remove "chromium" snap 208 Done2024-04-16T19:18:46+02:00 2024-04-16T19:19:47+02:00 Install "chromium" snap 209 Done2024-04-17T10:31:58+02:00 2024-04-17T10:32:02+02:00
[Desktop-packages] [Bug 2061995] Re: ULLTS 22, 24: FontConfig broken by including ".conf" file
** Also affects: fontconfig (Ubuntu) Importance: Undecided Status: New -- 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/2061995 Title: ULLTS 22,24: FontConfig broken by including ".conf" file Status in Ubuntu: New Status in fontconfig package in Ubuntu: New Bug description: This happens to me on both ULTS 22 and ULKTS 24 on FotnConfig in somewhat different ways: * In ULTS 24 if there is a file '/etc/fonts/local.conf' then all fonts are rendered as if the font were not hinted or 'hinting' were 'false'. This is not noticeable if antialiasing is on, and most users default to antialiasing. * In ULTS 22 if there is a file '$XDG_CONFIG_HOME/fontconfig/fonts.conf' then some fonts are no longer found, or get rendered with rectangular shapes. I guess not many users customize their font settings. A telling example from ULTS 22: $ cat /etc/fonts/conf.d/10-antialias.conf false $ cp -p /etc/fonts/conf.d/10-antialias.conf $XDG_CONFIG_HOME/fontconfig/fonts.conf $ fc-list 'dejavu sans mono' family $ rm $XDG_CONFIG_HOME/fontconfig/fonts.conf $ fc-list 'dejavu sans mono' family DejaVu Sans Mono This happens also with a skeleton '$XDG_CONFIG_HOME/fontconfig/fonts.conf' (or '/etc/fonts/local.conf') too: $ cat > $XDG_CONFIG_HOME/fontconfig/fonts.conf $ fc-list 'dejavu sans mono' family $ rm $XDG_CONFIG_HOME/fontconfig/fonts.conf $ fc-list 'dejavu sans mono' family DejaVu Sans Mono None of these anomalies happen under ULST 20. My impression: symptoms vary and are weird, so probably it is something like a buffer overflow when reading the ".conf" files or the use of not-initialized memory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2061995/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2061993] Re: RDP Remmina closes when trying to connect to a remote desktop - the same configuration works fine on other editions.
** Description changed: blox_land@blox-land-numbat:~$ remmina remmina-Message: 13:25:34.158: Remmina does not log all output statements. Turn on more verbose output by using "G_MESSAGES_DEBUG=remmina" as an environment variable. More info available on the Remmina wiki at: https://gitlab.com/Remmina/Remmina/-/wikis/Usage/Remmina-debugging (org.remmina.Remmina:11727): Gtk-WARNING **: 13:25:35.117: gtk_menu_attach_to_widget(): menu already attached to GtkMenuItem [13:25:41:43] [11727:2e1c] [ERROR][com.freerdp.common.settings] - [freerdp_settings_get_bool]: Invalid key index 0 [FreeRDP_instance|FREERDP_SETTINGS_TYPE_POINTER] [13:25:41:44] [11727:2e1c] [FATAL][com.freerdp.winpr.assert] - [winpr_int_assert]: FALSE [obj-x86_64-linux-gnu/libfreerdp/CMakeFiles/freerdp.dir/compiler_depend.ts:freerdp_settings_get_bool:634] [13:25:41:44] [11727:2e1c] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 0: dli_fname=/lib/x86_64-linux-gnu/libwinpr3.so.3 [0x766d98ccc000], dli_sname=winpr_backtrace [0x766d98d38540] [13:25:41:44] [11727:2e1c] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 1: dli_fname=/lib/x86_64-linux-gnu/libwinpr3.so.3 [0x766d98ccc000], dli_sname=winpr_log_backtrace_ex [0x766d98d3ffe0] [13:25:41:44] [11727:2e1c] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 2: dli_fname=/lib/x86_64-linux-gnu/libfreerdp3.so.3 [0x766d93c0], dli_sname=(null) [(nil)] [13:25:41:44] [11727:2e1c] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 3: dli_fname=/lib/x86_64-linux-gnu/libfreerdp3.so.3 [0x766d93c0], dli_sname=freerdp_settings_get_bool [0x766d93c648a0] [13:25:41:44] [11727:2e1c] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 4: dli_fname=/usr/lib/x86_64-linux-gnu/remmina/plugins/remmina-plugin-rdp.so [0x766d9a047000], dli_sname=(null) [(nil)] [13:25:41:44] [11727:2e1c] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 5: dli_fname=/usr/lib/x86_64-linux-gnu/remmina/plugins/remmina-plugin-rdp.so [0x766d9a047000], dli_sname=(null) [(nil)] [13:25:41:44] [11727:2e1c] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 6: dli_fname=/usr/bin/../lib/x86_64-linux-gnu/libc.so.6 [0x766d9da0], dli_sname=(null) [(nil)] [13:25:41:44] [11727:2e1c] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 7: dli_fname=/usr/bin/../lib/x86_64-linux-gnu/libc.so.6 [0x766d9da0], dli_sname=(null) [(nil)] [13:25:41:44] [11727:2e1c] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 8: unresolvable, address=(nil) Aborted (core dumped) blox_land@blox-land-numbat:~$ remmina --version remmina-Message: 13:26:03.550: Remmina does not log all output statements. Turn on more verbose output by using "G_MESSAGES_DEBUG=remmina" as an environment variable. More info available on the Remmina wiki at: https://gitlab.com/Remmina/Remmina/-/wikis/Usage/Remmina-debugging org.remmina.Remmina - 1.4.35 (git n/a) blox_land@blox-land-numbat:~$ ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: remmina 1.4.35+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 17 13:22:37 2024 InstallationDate: Installed on 2024-04-14 (3 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240410.2) ProcEnviron: - LANG=en_US.UTF-8 - PATH=(custom, no user) - SHELL=/bin/bash - TERM=xterm-256color - XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + PATH=(custom, no user) + SHELL=/bin/bash + TERM=xterm-256color + XDG_RUNTIME_DIR= SourcePackage: remmina UpgradeStatus: No upgrade log present (probably fresh install) + + + + blox_land@blox-land-numbat:~$ G_MESSAGES_DEBUG=remmina remmina + (process:12618): remmina-DEBUG: 14:26:56.726: (remmina_file_manager_init) - Initialized the "/home/blox_land/.local/share/remmina" data folder + (process:12618): remmina-DEBUG: 14:26:56.919: (remmina_plugin_manager_register_plugin) - Remmina plugin glibsecret (type=Secret) has been registered, but is not yet initialized/activated. The initialization order is 2000. + (process:12618): remmina-DEBUG: 14:26:57.711: (remmina_plugin_entry) - gfx_h264_available: 0 + (process:12618): remmina-DEBUG: 14:26:57.727: (remmina_rdp_settings_kbd_init) - rdp_keyboard_remapping_list: (null) + (process:12618): remmina-DEBUG: 14:26:57.851: (remmina_plugin_manager_load_plugins) - The glibsecret secret plugin has been initialized and it will be your default secret plugin + remmina-INFO: 14:26:58.495: StatusNotifier/Appindicator support in “ubuntu:gnome ubuntu-xorg”: your desktop does support it + remmina-INFO: 14:26:58.495:
[Desktop-packages] [Bug 2043376] Re: adsys cant fetch gpos ubuntu 22.04.3
Hi, I have (I believe) the exact same error message. I am setting up my personal samba AD server (running on ubuntu 22.04). I can join windows computers without any problem to the domain. I can use RAST (users and groups) from windows to manage the domain (add/create/change users/groups). I can also join linux computers (ubuntu 23.04 and ubuntu 23.10), and I can login with a domain user. But, when I login, I get errors from the server ``` bp@legion-ubuntu:~ % sudo login legion-ubuntu.sb.lan login: SB\bp Password: Login incorrect legion-ubuntu.sb.lan login: SB\bp Password: Welcome to Ubuntu 23.04 (GNU/Linux 6.2.0-37-generic x86_64) * Documentation: https://help.ubuntu.com * Management: https://landscape.canonical.com * Support:https://ubuntu.com/pro 3 updates can be applied immediately. To see these additional updates run: apt list --upgradable Your Ubuntu release is not supported anymore. For upgrade information, please visit: http://www.ubuntu.com/releaseendoflife New release '23.10' available. Run 'do-release-upgrade' to upgrade to it. The programs included with the Ubuntu system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Ubuntu comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. The programs included with the Ubuntu system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Ubuntu comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. Last login: Wed Apr 17 14:05:59 CEST 2024 on pts/1 Applying machine settings ERROR Error from server: error while updating policy: can't get policies for "legion-ubuntu": failed to retrieve the list of GPO (exited with 1): exit status 1 Failed to bind - LDAP client internal error: NT_STATUS_INVALID_PARAMETER Failed to connect to 'ldap://dc.sb.lan' with backend 'ldap': LDAP client internal error: NT_STATUS_INVALID_PARAMETER Failed to open session: (1, 'LDAP client internal error: NT_STATUS_INVALID_PARAMETER') Failure setting user credentials ``` This prevents me from logging in through normal login screen. My sssd.conf ``` bp@legion-ubuntu:~ % sudo cat /etc/sssd/sssd.conf [sssd] domains = sb.lan config_file_version = 2 services = nss, pam debug_level = 10 [domain/sb.lan] default_shell = /bin/bash krb5_store_password_if_offline = True cache_credentials = True krb5_realm = SB.LAN realmd_tags = manages-system joined-with-adcli id_provider = ad fallback_homedir = /home/%u@%d ad_domain = sb.lan use_fully_qualified_names = True ldap_id_mapping = True access_provider = ad timeout = 20 ldap_uri = ldap://dc.sb.lan ldap_search_base = dc=sb,dc=lan auth_provider = krb5 krb5_server = dc.sb.lan krb5_passwd = dc.sb.lan krb5_validate = True # https://serverfault.com/questions/872542/debugging-sssd-login-pam-sss-system-error # suggested work around in question ad_gpo_access_control = permissive ``` Any chance you could point me in the right direction? I am sure there is something wrong (I expect it to be client side since windows computers seem to work perfectly fine in the samba AD domain) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/2043376 Title: adsys cant fetch gpos ubuntu 22.04.3 Status in adsys package in Ubuntu: Incomplete Bug description: VERSIONS: ubuntu 22.04.3 libsmbclient 2:4.15.13+dfsg-0ubuntu1.5 adsysctl 0.9.2~22.04.2 adsysd 0.9.2~22.04.2 Hi when i try the command adsysctl update -m or --all i receive this error: Error from server: error while updating policy: cant get policies for "ubuntuvm": failed to retrieve the list of GPO (exited with -1): signal: killed Failed to bind - LDAP client internal error: NT_STATUS_INVALID_PARAMETER Failed to connect to 'ldap://addc01.domain.com' with backend 'ldap': LDAP client internal error: NT_STATUS_INVALID_PARAMETER Failed to open session: (1, 'LDAP client internal error: NT_STATUS_INVALID_PARAMETER'). Result of adsysctl service cat -vvv NFO github.com/ubuntu/adsys/internal/config/config.go:73 Init() No configuration file: Config File "adsys" Not Found in "[/home/ubuntuvm /etc /usr/sbin]". We will only use the defaults, env variables or flags. DEBUG Connecting as [[41753:876951]] DEBUG github.com/ubuntu/adsys/internal/grpc/logconnections/logconnections.go:27 StreamServerInterceptor.func1() New request /service/Cat DEBUG github.com/ubuntu/adsys/internal/grpc/logconnections/logconnections.go:60 loggedServerStream.RecvMsg() Requesting with parameters: DEBUG github.com/ubuntu/adsys/internal/authorizer/authorizer.go:111 Authorizer.IsAllowedFromContext() Check if grpc request peer is authorized DEBUG github.com/ubuntu/adsys/internal/authorizer/authorizer.go:191 Authorizer.isAllowed() Polkit call result,
[Desktop-packages] [Bug 2061981] Re: chromium fails to start with non-standard home directory
I don't have an encrypted home directory (though it is on a ZFS filesystem, but that one is also NOT encrypted). W. -- 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/2061981 Title: chromium fails to start with non-standard home directory Status in chromium-browser package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Bug description: chromium 123.0.6312.122 2821 latest/stablecanonical cannot update snap namespace: cannot expand mount entry (none $HOME/.local/share none x-snapd.kind=ensure-dir,x-snapd.must-exist- dir=$HOME 0 0): cannot use invalid home directory "/home/department/user_name": permission denied Fails to start on Ubuntu 22.04 for users with 'non-standard' home directory /home/department/user_name Used to work fine up to last week. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: chromium-browser 1:85.0.4183.83-0ubuntu2.22.04.1 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Wed Apr 17 10:32:18 2024 InstallationDate: Installed on 2017-03-24 (2580 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Snap.Changes: ID Status Spawn Ready Summary 206 Error 2024-04-16T19:08:43+02:00 2024-04-16T19:16:51+02:00 Remove "chromium" snap 207 Done2024-04-16T19:17:27+02:00 2024-04-16T19:18:44+02:00 Remove "chromium" snap 208 Done2024-04-16T19:18:46+02:00 2024-04-16T19:19:47+02:00 Install "chromium" snap 209 Done2024-04-17T10:31:58+02:00 2024-04-17T10:32:02+02:00 Connect chromium:password-manager-service to snapd:password-manager-service SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2061981/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2061997] [NEW] gnome-shell and fprintd : Authorization denied to :1.65 to call method 'Claim' for device 'Elan MOC Sensors': Device was already claimed
Public bug reported: Hi, I have registered a fingerprint in fprintd and when when system boots and starts gdm, the following error messages are logged: # journalctl -b | grep fprintd Apr 17 14:08:45 vougeot dbus-daemon[1799]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' requested by ':1.42' (uid=108 pid=4112 comm="/usr/bin/gnome-shell") Apr 17 14:08:46 vougeot systemd[1]: Starting fprintd.service - Fingerprint Authentication Daemon... Apr 17 14:08:46 vougeot systemd[1]: Started fprintd.service - Fingerprint Authentication Daemon. Apr 17 14:08:52 vougeot fprintd[4606]: Authorization denied to :1.65 to call method 'Claim' for device 'Elan MOC Sensors': Device was already claimed ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-shell 46.0-0ubuntu4 Uname: Linux 6.8.7-060807-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Apr 17 14:19:44 2024 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 46.0-1ubuntu6 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: fprintd (Ubuntu) Importance: Undecided Status: New ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble ** Also affects: fprintd (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/2061997 Title: gnome-shell and fprintd : Authorization denied to :1.65 to call method 'Claim' for device 'Elan MOC Sensors': Device was already claimed Status in fprintd package in Ubuntu: New Status in gnome-shell package in Ubuntu: New Bug description: Hi, I have registered a fingerprint in fprintd and when when system boots and starts gdm, the following error messages are logged: # journalctl -b | grep fprintd Apr 17 14:08:45 vougeot dbus-daemon[1799]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' requested by ':1.42' (uid=108 pid=4112 comm="/usr/bin/gnome-shell") Apr 17 14:08:46 vougeot systemd[1]: Starting fprintd.service - Fingerprint Authentication Daemon... Apr 17 14:08:46 vougeot systemd[1]: Started fprintd.service - Fingerprint Authentication Daemon. Apr 17 14:08:52 vougeot fprintd[4606]: Authorization denied to :1.65 to call method 'Claim' for device 'Elan MOC Sensors': Device was already claimed ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-shell 46.0-0ubuntu4 Uname: Linux 6.8.7-060807-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Apr 17 14:19:44 2024 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 46.0-1ubuntu6 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/fprintd/+bug/2061997/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1958019]
> Please try the following and report if it fixes the issue: > amixer -c 1 cset numid=3,name='Speaker Force Firmware Load' 1 What is the expected result of the above? > I had some time this morning to try and repeat the issue.. I couldn't do it I can reproduce in < 5 mins on average. I played a video and paused / resumed after a while, until the issue kicked in. Ran: `amixer -c 1 cset numid=3,name='Speaker Force Firmware Load' 1` No effect, sound still broken. The output looked ok. Checked both `amixer -c 1 contents` or `amixer -c 0 contents`. - there are a lot of entries, what exactly am I looking for? Here's the interesting part though: In that same session, I made the laptop close lid action + sleep On wake, audio was working again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1958019]
On 4/16/24 16:54, bugzilla-dae...@kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=208555 > > --- Comment #859 from Gergo K (so...@irl.hu) --- > What else came to mind, the driver currently writes the calibration data to > one > of the wrong registers of tas2781, which can also cause problems. If anyone > wants to know what fixes the problem, please try this patch as well: > > https://lore.kernel.org/all/20240406132010.341-1-shenghao-d...@ti.com/ > Pretty good find/catch! I checked the source of my current kernel (6.8.6) and it didn't have that patch installed... So I applied it. We'll see how this goes... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1958019]
What else came to mind, the driver currently writes the calibration data to one of the wrong registers of tas2781, which can also cause problems. If anyone wants to know what fixes the problem, please try this patch as well: https://lore.kernel.org/all/20240406132010.341-1-shenghao-d...@ti.com/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1958019]
I had some time this morning to try and repeat the issue.. I couldn't do it. So until I can find a way to repeat it, it's not worth testing other kernel releases. I will try Gergo's command once it happens again and report back. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1986450] Re: Visual artifact 1px vertical white line right side of the wallpaper with Ambiance/Radiance
Let's see what DING devs think: https://gitlab.com/rastersoft/desktop- icons-ng/-/issues/315 ** Bug watch added: gitlab.com/rastersoft/desktop-icons-ng/-/issues #315 https://gitlab.com/rastersoft/desktop-icons-ng/-/issues/315 -- 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/1986450 Title: Visual artifact 1px vertical white line right side of the wallpaper with Ambiance/Radiance Status in gnome-shell package in Ubuntu: New Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: New Status in ubuntu-themes package in Ubuntu: New Bug description: After manually upgrading from 20.04 LTS to 22.04.1 LTS I find that there is a 1px wide vertical white line on the desktop that appears whenever an application has focus. It is on the right side of the monitor, covering the background wallpaper but not the menu. Workaround: in Displays, change scale to something else than 100% and then change back to 100%. That white vertical line will stay at the former 100% window size location until the Settings window is closed. It disappears when the Settings is closed. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2018-04-27 (1570 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: gnome-shell 42.2-0ubuntu0.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RelatedPackageVersions: mutter-common 42.2-0ubuntu1 Tags: wayland-session jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1986450/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2061981] Re: chromium fails to start with non-standard home directory
$ snap connect chromium:dot-local-share-applications $ snap connect chromium:dot-local-share-icons $ snap revert snapd 2024-04-17T14:16:18+02:00 INFO Waiting for automatic snapd restart... snapd revenu à 2.61.2 $ chromium & also works, so snapd update seems to be the cause :) -- 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/2061981 Title: chromium fails to start with non-standard home directory Status in chromium-browser package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Bug description: chromium 123.0.6312.122 2821 latest/stablecanonical cannot update snap namespace: cannot expand mount entry (none $HOME/.local/share none x-snapd.kind=ensure-dir,x-snapd.must-exist- dir=$HOME 0 0): cannot use invalid home directory "/home/department/user_name": permission denied Fails to start on Ubuntu 22.04 for users with 'non-standard' home directory /home/department/user_name Used to work fine up to last week. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: chromium-browser 1:85.0.4183.83-0ubuntu2.22.04.1 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Wed Apr 17 10:32:18 2024 InstallationDate: Installed on 2017-03-24 (2580 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Snap.Changes: ID Status Spawn Ready Summary 206 Error 2024-04-16T19:08:43+02:00 2024-04-16T19:16:51+02:00 Remove "chromium" snap 207 Done2024-04-16T19:17:27+02:00 2024-04-16T19:18:44+02:00 Remove "chromium" snap 208 Done2024-04-16T19:18:46+02:00 2024-04-16T19:19:47+02:00 Install "chromium" snap 209 Done2024-04-17T10:31:58+02:00 2024-04-17T10:32:02+02:00 Connect chromium:password-manager-service to snapd:password-manager-service SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2061981/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2060575] Re: gnome-keyring fails to automatically unlock login keyring after recent updates in noble
Can you give me an answer to my question if this is related or if I should file a new bug? https://bugs.launchpad.net/ubuntu/+source/gnome- keyring/+bug/2060575/comments/20 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/2060575 Title: gnome-keyring fails to automatically unlock login keyring after recent updates in noble Status in gdm3 package in Ubuntu: Opinion Status in gnome-keyring package in Ubuntu: Won't Fix Status in gnome-shell package in Ubuntu: Fix Committed Bug description: After installing recent updates in 24.04, upon logging in the gnome- shell based UI pops up saying that the login keyring was not unlocked and asking for the users password to be input to unlock it. Similarly a second, non-gnome-shell based UI is also present asking the same thing. Will try and get a screenshot to attach. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: libpam-gnome-keyring 46.1-2build1 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 9 06:16:46 2024 InstallationDate: Installed on 2021-08-03 (980 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210802) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-keyring UpgradeStatus: Upgraded to noble on 2024-01-31 (68 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2060575/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2061981] Re: chromium fails to start with non-standard home directory
Thank you for the additional information. enaira05, you can disconnect them with snap disconnect chromium:dot-local-share-applications snap disconnect chromium:dot-local-share-icons wouterd, glad to hear that solves your problem. The interface has been present for a long time. The Chromium update I released yesterday was just a new upstream release and as such introduces nothing that would trigger such an error. On my side I can see in 'snap changes' 1618 Donetoday at 12:40 CEST today at 12:43 CEST Auto-refresh snap "snapd" So I'm placing my bets on that change. Are you able to 'snap revert snapd' for a test? If yes, please remember to reconnect the interfaces for the test. -- 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/2061981 Title: chromium fails to start with non-standard home directory Status in chromium-browser package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Bug description: chromium 123.0.6312.122 2821 latest/stablecanonical cannot update snap namespace: cannot expand mount entry (none $HOME/.local/share none x-snapd.kind=ensure-dir,x-snapd.must-exist- dir=$HOME 0 0): cannot use invalid home directory "/home/department/user_name": permission denied Fails to start on Ubuntu 22.04 for users with 'non-standard' home directory /home/department/user_name Used to work fine up to last week. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: chromium-browser 1:85.0.4183.83-0ubuntu2.22.04.1 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Wed Apr 17 10:32:18 2024 InstallationDate: Installed on 2017-03-24 (2580 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Snap.Changes: ID Status Spawn Ready Summary 206 Error 2024-04-16T19:08:43+02:00 2024-04-16T19:16:51+02:00 Remove "chromium" snap 207 Done2024-04-16T19:17:27+02:00 2024-04-16T19:18:44+02:00 Remove "chromium" snap 208 Done2024-04-16T19:18:46+02:00 2024-04-16T19:19:47+02:00 Install "chromium" snap 209 Done2024-04-17T10:31:58+02:00 2024-04-17T10:32:02+02:00 Connect chromium:password-manager-service to snapd:password-manager-service SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2061981/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2061981] Re: chromium fails to start with non-standard home directory
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: snapd (Ubuntu) Status: New => Confirmed -- 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/2061981 Title: chromium fails to start with non-standard home directory Status in chromium-browser package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Bug description: chromium 123.0.6312.122 2821 latest/stablecanonical cannot update snap namespace: cannot expand mount entry (none $HOME/.local/share none x-snapd.kind=ensure-dir,x-snapd.must-exist- dir=$HOME 0 0): cannot use invalid home directory "/home/department/user_name": permission denied Fails to start on Ubuntu 22.04 for users with 'non-standard' home directory /home/department/user_name Used to work fine up to last week. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: chromium-browser 1:85.0.4183.83-0ubuntu2.22.04.1 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Wed Apr 17 10:32:18 2024 InstallationDate: Installed on 2017-03-24 (2580 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Snap.Changes: ID Status Spawn Ready Summary 206 Error 2024-04-16T19:08:43+02:00 2024-04-16T19:16:51+02:00 Remove "chromium" snap 207 Done2024-04-16T19:17:27+02:00 2024-04-16T19:18:44+02:00 Remove "chromium" snap 208 Done2024-04-16T19:18:46+02:00 2024-04-16T19:19:47+02:00 Install "chromium" snap 209 Done2024-04-17T10:31:58+02:00 2024-04-17T10:32:02+02:00 Connect chromium:password-manager-service to snapd:password-manager-service SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2061981/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2061907] Re: Update freerdp3 to 3.5.0
This bug was fixed in the package freerdp3 - 3.5.0+dfsg1-0ubuntu1 --- freerdp3 (3.5.0+dfsg1-0ubuntu1) noble; urgency=medium * New upstream release (LP: #2061907) - CVE-2024-32039 [Moderate] Integer overflow & OutOfBound Write in clear_decompress_residual_data - CVE-2024-32040 [Low] integer underflow in nsc_rle_decode - CVE-2024-32041 [Low] OutOfBound Read in zgfx_decompress_segment - CVE-2024-32458 [Low] OutOfBound Read in planar_skip_plane_rle - CVE-2024-32459 [Low] OutOfBound Read in ncrush_decompress - CVE-2024-32460 [Low] OutOfBound Read in interleaved_decompress -- Jeremy Bícha Tue, 16 Apr 2024 17:23:57 -0400 ** Changed in: freerdp3 (Ubuntu) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-32039 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-32040 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-32041 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-32458 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-32459 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-32460 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to freerdp3 in Ubuntu. https://bugs.launchpad.net/bugs/2061907 Title: Update freerdp3 to 3.5.0 Status in freerdp3 package in Ubuntu: Fix Released Bug description: freerdp 3.5.0 was released as a security update. https://github.com/FreeRDP/FreeRDP/releases/tag/3.5.0 https://github.com/FreeRDP/FreeRDP/compare/3.4.0...3.5.0 There are a very large number of coverity fixes and bound check fixes and resource leak updates in the new release. It does not look very practical to cherry-pick only some of those fixes. And the git commits aren't directly associated with which CVE they are supposed to fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freerdp3/+bug/2061907/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2061981] Re: chromium fails to start with non-standard home directory
$ snap disconnect chromium:dot-local-share-applications $ snap disconnect chromium:dot-local-share-icons also helped in my case to be able to start chromium :) But for how long ...? -- 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/2061981 Title: chromium fails to start with non-standard home directory Status in chromium-browser package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Bug description: chromium 123.0.6312.122 2821 latest/stablecanonical cannot update snap namespace: cannot expand mount entry (none $HOME/.local/share none x-snapd.kind=ensure-dir,x-snapd.must-exist- dir=$HOME 0 0): cannot use invalid home directory "/home/department/user_name": permission denied Fails to start on Ubuntu 22.04 for users with 'non-standard' home directory /home/department/user_name Used to work fine up to last week. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: chromium-browser 1:85.0.4183.83-0ubuntu2.22.04.1 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Wed Apr 17 10:32:18 2024 InstallationDate: Installed on 2017-03-24 (2580 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Snap.Changes: ID Status Spawn Ready Summary 206 Error 2024-04-16T19:08:43+02:00 2024-04-16T19:16:51+02:00 Remove "chromium" snap 207 Done2024-04-16T19:17:27+02:00 2024-04-16T19:18:44+02:00 Remove "chromium" snap 208 Done2024-04-16T19:18:46+02:00 2024-04-16T19:19:47+02:00 Install "chromium" snap 209 Done2024-04-17T10:31:58+02:00 2024-04-17T10:32:02+02:00 Connect chromium:password-manager-service to snapd:password-manager-service SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2061981/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2061981] Re: chromium fails to start with non-standard home directory
PS: Can't revert as I uninstalled and reinstalled chromium yesterday when I first encountered the problem. user_name@computer:~$ sudo snap revert chromium error: cannot revert "chromium": no revision to revert to -- 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/2061981 Title: chromium fails to start with non-standard home directory Status in chromium-browser package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Bug description: chromium 123.0.6312.122 2821 latest/stablecanonical cannot update snap namespace: cannot expand mount entry (none $HOME/.local/share none x-snapd.kind=ensure-dir,x-snapd.must-exist- dir=$HOME 0 0): cannot use invalid home directory "/home/department/user_name": permission denied Fails to start on Ubuntu 22.04 for users with 'non-standard' home directory /home/department/user_name Used to work fine up to last week. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: chromium-browser 1:85.0.4183.83-0ubuntu2.22.04.1 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Wed Apr 17 10:32:18 2024 InstallationDate: Installed on 2017-03-24 (2580 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Snap.Changes: ID Status Spawn Ready Summary 206 Error 2024-04-16T19:08:43+02:00 2024-04-16T19:16:51+02:00 Remove "chromium" snap 207 Done2024-04-16T19:17:27+02:00 2024-04-16T19:18:44+02:00 Remove "chromium" snap 208 Done2024-04-16T19:18:46+02:00 2024-04-16T19:19:47+02:00 Install "chromium" snap 209 Done2024-04-17T10:31:58+02:00 2024-04-17T10:32:02+02:00 Connect chromium:password-manager-service to snapd:password-manager-service SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2061981/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1986450] Re: Visual artifact 1px vertical white line right side of the wallpaper
Ambiance/Radiance are basically unmaintained so if there's a bug it would probably be easier for you to propose a fix then trying to find someone else to do it. If you have concerns about the extension, I suggest filing an upstream issue: https://gitlab.com/rastersoft/desktop-icons-ng/-/issues ** Summary changed: - Visual artifact 1px vertical white line right side of the wallpaper + Visual artifact 1px vertical white line right side of the wallpaper with Ambiance/Radiance -- 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/1986450 Title: Visual artifact 1px vertical white line right side of the wallpaper with Ambiance/Radiance Status in gnome-shell package in Ubuntu: New Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: New Status in ubuntu-themes package in Ubuntu: New Bug description: After manually upgrading from 20.04 LTS to 22.04.1 LTS I find that there is a 1px wide vertical white line on the desktop that appears whenever an application has focus. It is on the right side of the monitor, covering the background wallpaper but not the menu. Workaround: in Displays, change scale to something else than 100% and then change back to 100%. That white vertical line will stay at the former 100% window size location until the Settings window is closed. It disappears when the Settings is closed. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2018-04-27 (1570 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: gnome-shell 42.2-0ubuntu0.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RelatedPackageVersions: mutter-common 42.2-0ubuntu1 Tags: wayland-session jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1986450/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2061880] Re: Crash on Xubuntu 24.04 Beta when trying to RDP
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: remmina (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/2061880 Title: Crash on Xubuntu 24.04 Beta when trying to RDP Status in remmina package in Ubuntu: Confirmed Bug description: This could be related to https://gitlab.com/Remmina/Remmina/-/issues/3090 remmina-Message: 19:16:12.858: Remmina does not log all output statements. Turn on more verbose output by using "G_MESSAGES_DEBUG=remmina" as an environment variable. More info available on the Remmina wiki at: https://gitlab.com/Remmina/Remmina/-/wikis/Usage/Remmina-debugging (org.remmina.Remmina:15044): Gtk-WARNING **: 19:16:12.981: gtk_menu_attach_to_widget(): menu already attached to GtkMenuItem [19:16:16:108] [15044:3b0f] [ERROR][com.freerdp.common.settings] - [freerdp_settings_get_bool]: Invalid key index 0 [FreeRDP_instance|FREERDP_SETTINGS_TYPE_POINTER] [19:16:16:108] [15044:3b0f] [FATAL][com.freerdp.winpr.assert] - [winpr_int_assert]: FALSE [obj-x86_64-linux-gnu/libfreerdp/CMakeFiles/freerdp.dir/compiler_depend.ts:freerdp_settings_get_bool:634] [19:16:16:108] [15044:3b0f] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 0: dli_fname=/lib/x86_64-linux-gnu/libwinpr3.so.3 [0x72d1f542b000], dli_sname=winpr_backtrace [0x72d1f5497540] [19:16:16:108] [15044:3b0f] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 1: dli_fname=/lib/x86_64-linux-gnu/libwinpr3.so.3 [0x72d1f542b000], dli_sname=winpr_log_backtrace_ex [0x72d1f549efe0] [19:16:16:108] [15044:3b0f] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 2: dli_fname=/lib/x86_64-linux-gnu/libfreerdp3.so.3 [0x72d1efc0], dli_sname=(null) [(nil)] [19:16:16:108] [15044:3b0f] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 3: dli_fname=/lib/x86_64-linux-gnu/libfreerdp3.so.3 [0x72d1efc0], dli_sname=freerdp_settings_get_bool [0x72d1efc648a0] [19:16:16:108] [15044:3b0f] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 4: dli_fname=/usr/lib/x86_64-linux-gnu/remmina/plugins/remmina-plugin-rdp.so [0x72d1f5efa000], dli_sname=(null) [(nil)] [19:16:16:108] [15044:3b0f] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 5: dli_fname=/usr/lib/x86_64-linux-gnu/remmina/plugins/remmina-plugin-rdp.so [0x72d1f5efa000], dli_sname=(null) [(nil)] [19:16:16:108] [15044:3b0f] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 6: dli_fname=/usr/bin/../lib/x86_64-linux-gnu/libc.so.6 [0x72d1f9a0], dli_sname=(null) [(nil)] [19:16:16:108] [15044:3b0f] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 7: dli_fname=/usr/bin/../lib/x86_64-linux-gnu/libc.so.6 [0x72d1f9a0], dli_sname=(null) [(nil)] [19:16:16:108] [15044:3b0f] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 8: unresolvable, address=(nil) Aborted (core dumped) wil@williambell:/var/crash$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/2061880/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2061981] Re: chromium fails to start with non-standard home directory
user_name@computer:~$ snap connections chromium | grep personal-files personal-fileschromium:chromium-config :personal-files - personal-fileschromium:dot-local-share-applications :personal-files - personal-fileschromium:dot-local-share-icons :personal-files - disconnecting "chromium:dot-local-share-applications" and "chromium:dot-local-share-icons" seems to fix the problem. Thanks! W;-) -- 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/2061981 Title: chromium fails to start with non-standard home directory Status in chromium-browser package in Ubuntu: Confirmed Status in snapd package in Ubuntu: New Bug description: chromium 123.0.6312.122 2821 latest/stablecanonical cannot update snap namespace: cannot expand mount entry (none $HOME/.local/share none x-snapd.kind=ensure-dir,x-snapd.must-exist- dir=$HOME 0 0): cannot use invalid home directory "/home/department/user_name": permission denied Fails to start on Ubuntu 22.04 for users with 'non-standard' home directory /home/department/user_name Used to work fine up to last week. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: chromium-browser 1:85.0.4183.83-0ubuntu2.22.04.1 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Wed Apr 17 10:32:18 2024 InstallationDate: Installed on 2017-03-24 (2580 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Snap.Changes: ID Status Spawn Ready Summary 206 Error 2024-04-16T19:08:43+02:00 2024-04-16T19:16:51+02:00 Remove "chromium" snap 207 Done2024-04-16T19:17:27+02:00 2024-04-16T19:18:44+02:00 Remove "chromium" snap 208 Done2024-04-16T19:18:46+02:00 2024-04-16T19:19:47+02:00 Install "chromium" snap 209 Done2024-04-17T10:31:58+02:00 2024-04-17T10:32:02+02:00 Connect chromium:password-manager-service to snapd:password-manager-service SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2061981/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2061981] Re: chromium fails to start with non-standard home directory
I saw in another discussion that what we (people having this issue) could have in common is an encrypted home directory. Mine is encrypted and I have the issue. Btw, I tried 'snap revert chromium' but it reverted to a version that also doesn't start. $ snap connections chromium | grep personal-files personal-fileschromium:chromium-config :personal-files - personal-fileschromium:dot-local-share-applications :personal-files - personal-fileschromium:dot-local-share-icons :personal-files - How do we "disconnect the dot-local-share ones" ? -- 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/2061981 Title: chromium fails to start with non-standard home directory Status in chromium-browser package in Ubuntu: Confirmed Status in snapd package in Ubuntu: New Bug description: chromium 123.0.6312.122 2821 latest/stablecanonical cannot update snap namespace: cannot expand mount entry (none $HOME/.local/share none x-snapd.kind=ensure-dir,x-snapd.must-exist- dir=$HOME 0 0): cannot use invalid home directory "/home/department/user_name": permission denied Fails to start on Ubuntu 22.04 for users with 'non-standard' home directory /home/department/user_name Used to work fine up to last week. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: chromium-browser 1:85.0.4183.83-0ubuntu2.22.04.1 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Wed Apr 17 10:32:18 2024 InstallationDate: Installed on 2017-03-24 (2580 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Snap.Changes: ID Status Spawn Ready Summary 206 Error 2024-04-16T19:08:43+02:00 2024-04-16T19:16:51+02:00 Remove "chromium" snap 207 Done2024-04-16T19:17:27+02:00 2024-04-16T19:18:44+02:00 Remove "chromium" snap 208 Done2024-04-16T19:18:46+02:00 2024-04-16T19:19:47+02:00 Install "chromium" snap 209 Done2024-04-17T10:31:58+02:00 2024-04-17T10:32:02+02:00 Connect chromium:password-manager-service to snapd:password-manager-service SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2061981/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2061981] Re: chromium fails to start with non-standard home directory
** Changed in: chromium-browser (Ubuntu) Status: New => Confirmed ** Also affects: snapd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2061981 Title: chromium fails to start with non-standard home directory Status in chromium-browser package in Ubuntu: Confirmed Status in snapd package in Ubuntu: New Bug description: chromium 123.0.6312.122 2821 latest/stablecanonical cannot update snap namespace: cannot expand mount entry (none $HOME/.local/share none x-snapd.kind=ensure-dir,x-snapd.must-exist- dir=$HOME 0 0): cannot use invalid home directory "/home/department/user_name": permission denied Fails to start on Ubuntu 22.04 for users with 'non-standard' home directory /home/department/user_name Used to work fine up to last week. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: chromium-browser 1:85.0.4183.83-0ubuntu2.22.04.1 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Wed Apr 17 10:32:18 2024 InstallationDate: Installed on 2017-03-24 (2580 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Snap.Changes: ID Status Spawn Ready Summary 206 Error 2024-04-16T19:08:43+02:00 2024-04-16T19:16:51+02:00 Remove "chromium" snap 207 Done2024-04-16T19:17:27+02:00 2024-04-16T19:18:44+02:00 Remove "chromium" snap 208 Done2024-04-16T19:18:46+02:00 2024-04-16T19:19:47+02:00 Install "chromium" snap 209 Done2024-04-17T10:31:58+02:00 2024-04-17T10:32:02+02:00 Connect chromium:password-manager-service to snapd:password-manager-service SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2061981/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2061355] Re: fractional scaling does not work on X11
*** This bug is a duplicate of bug 2060659 *** https://bugs.launchpad.net/bugs/2060659 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- 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/2061355 Title: fractional scaling does not work on X11 Status in mutter package in Ubuntu: Confirmed Bug description: On the Noble Beta version, Fractional scaling does not work on Xorg/Gnome. I can neither enable it through the control center nor the gsettings. Please advice. It works on Wayland, but somehow QT applications including VS Code are hazy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2061355/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2061993] [NEW] RDP Remmina closes when trying to connect to a remote desktop - the same configuration works fine on other editions.
Public bug reported: blox_land@blox-land-numbat:~$ remmina remmina-Message: 13:25:34.158: Remmina does not log all output statements. Turn on more verbose output by using "G_MESSAGES_DEBUG=remmina" as an environment variable. More info available on the Remmina wiki at: https://gitlab.com/Remmina/Remmina/-/wikis/Usage/Remmina-debugging (org.remmina.Remmina:11727): Gtk-WARNING **: 13:25:35.117: gtk_menu_attach_to_widget(): menu already attached to GtkMenuItem [13:25:41:43] [11727:2e1c] [ERROR][com.freerdp.common.settings] - [freerdp_settings_get_bool]: Invalid key index 0 [FreeRDP_instance|FREERDP_SETTINGS_TYPE_POINTER] [13:25:41:44] [11727:2e1c] [FATAL][com.freerdp.winpr.assert] - [winpr_int_assert]: FALSE [obj-x86_64-linux-gnu/libfreerdp/CMakeFiles/freerdp.dir/compiler_depend.ts:freerdp_settings_get_bool:634] [13:25:41:44] [11727:2e1c] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 0: dli_fname=/lib/x86_64-linux-gnu/libwinpr3.so.3 [0x766d98ccc000], dli_sname=winpr_backtrace [0x766d98d38540] [13:25:41:44] [11727:2e1c] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 1: dli_fname=/lib/x86_64-linux-gnu/libwinpr3.so.3 [0x766d98ccc000], dli_sname=winpr_log_backtrace_ex [0x766d98d3ffe0] [13:25:41:44] [11727:2e1c] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 2: dli_fname=/lib/x86_64-linux-gnu/libfreerdp3.so.3 [0x766d93c0], dli_sname=(null) [(nil)] [13:25:41:44] [11727:2e1c] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 3: dli_fname=/lib/x86_64-linux-gnu/libfreerdp3.so.3 [0x766d93c0], dli_sname=freerdp_settings_get_bool [0x766d93c648a0] [13:25:41:44] [11727:2e1c] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 4: dli_fname=/usr/lib/x86_64-linux-gnu/remmina/plugins/remmina-plugin-rdp.so [0x766d9a047000], dli_sname=(null) [(nil)] [13:25:41:44] [11727:2e1c] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 5: dli_fname=/usr/lib/x86_64-linux-gnu/remmina/plugins/remmina-plugin-rdp.so [0x766d9a047000], dli_sname=(null) [(nil)] [13:25:41:44] [11727:2e1c] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 6: dli_fname=/usr/bin/../lib/x86_64-linux-gnu/libc.so.6 [0x766d9da0], dli_sname=(null) [(nil)] [13:25:41:44] [11727:2e1c] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 7: dli_fname=/usr/bin/../lib/x86_64-linux-gnu/libc.so.6 [0x766d9da0], dli_sname=(null) [(nil)] [13:25:41:44] [11727:2e1c] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 8: unresolvable, address=(nil) Aborted (core dumped) blox_land@blox-land-numbat:~$ remmina --version remmina-Message: 13:26:03.550: Remmina does not log all output statements. Turn on more verbose output by using "G_MESSAGES_DEBUG=remmina" as an environment variable. More info available on the Remmina wiki at: https://gitlab.com/Remmina/Remmina/-/wikis/Usage/Remmina-debugging org.remmina.Remmina - 1.4.35 (git n/a) blox_land@blox-land-numbat:~$ ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: remmina 1.4.35+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 17 13:22:37 2024 InstallationDate: Installed on 2024-04-14 (3 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240410.2) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: remmina UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: remmina (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/2061993 Title: RDP Remmina closes when trying to connect to a remote desktop - the same configuration works fine on other editions. Status in remmina package in Ubuntu: New Bug description: blox_land@blox-land-numbat:~$ remmina remmina-Message: 13:25:34.158: Remmina does not log all output statements. Turn on more verbose output by using "G_MESSAGES_DEBUG=remmina" as an environment variable. More info available on the Remmina wiki at: https://gitlab.com/Remmina/Remmina/-/wikis/Usage/Remmina-debugging (org.remmina.Remmina:11727): Gtk-WARNING **: 13:25:35.117: gtk_menu_attach_to_widget(): menu already attached to GtkMenuItem [13:25:41:43] [11727:2e1c] [ERROR][com.freerdp.common.settings] - [freerdp_settings_get_bool]: Invalid key index 0 [FreeRDP_instance|FREERDP_SETTINGS_TYPE_POINTER] [13:25:41:44] [11727:2e1c] [FATAL][com.freerdp.winpr.assert] - [winpr_int_assert]: FALSE
[Desktop-packages] [Bug 1986450] Re: Visual artifact 1px vertical white line right side of the wallpaper
> Wow, I didn't realize that people were still trying to use Ambiance and Radiance (from source package ubuntu-themes) with Ubuntu 24.04 LTS. I'd love to switch to Adwaita or Yaru, but I prefer to have dark window header and light window contents, and I haven't found yet how to do it in those. (I'm also in the process of evaluating whether I want to leave Unity behind and switch to GNOME or its Ubuntu desktop flavor... that's how I came across this issue.) > Would you like to submit a patch and subscribe ubuntu-sponsors? The thing is, I'm not confident that I'm doing the right thing and not causing side effects elsewhere. I'm even unsure at this moment whether the fix needs to go into the theme, or the extension should ship the override. I'd much rather prefer if someone familiar with GTK theming/CSS could take over from here. -- 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/1986450 Title: Visual artifact 1px vertical white line right side of the wallpaper Status in gnome-shell package in Ubuntu: New Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: New Status in ubuntu-themes package in Ubuntu: New Bug description: After manually upgrading from 20.04 LTS to 22.04.1 LTS I find that there is a 1px wide vertical white line on the desktop that appears whenever an application has focus. It is on the right side of the monitor, covering the background wallpaper but not the menu. Workaround: in Displays, change scale to something else than 100% and then change back to 100%. That white vertical line will stay at the former 100% window size location until the Settings window is closed. It disappears when the Settings is closed. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2018-04-27 (1570 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: gnome-shell 42.2-0ubuntu0.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RelatedPackageVersions: mutter-common 42.2-0ubuntu1 Tags: wayland-session jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1986450/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1986450] Re: Visual artifact 1px vertical white line right side of the wallpaper
Without root access (or being worried of an update overwriting the
changes), this is how I could fix it as a user.
I've placed this in my ~/.config/gtk-3.0/gtk.css file:
window.desktopwindow.background:backdrop {
box-shadow: none;
}
Don't ask why it's gtk-3.0 and not 3.20 or 4.0, I have no clue.
The "window.desktopwindow" selector is something I've found in gnome-
shell-extension-desktop-icons-ng's source. It's a more specific selector
than the one in the theme, hence takes precedence over that. Without
this selector they would be of the same precedence, and for some reason
the one in the theme is used, the one in the user's config is ignored.
And GTK doesn't seem to support "!important".
This extra selector luckily gives some confidence that the rule probably
doesn't have an effect on others. (However, the disclaimer from my
previous comment still applies.)
In extension-manager toggle the said extension back and forth to apply
the change.
--
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/1986450
Title:
Visual artifact 1px vertical white line right side of the wallpaper
Status in gnome-shell package in Ubuntu:
New
Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu:
New
Status in ubuntu-themes package in Ubuntu:
New
Bug description:
After manually upgrading from 20.04 LTS to 22.04.1 LTS I find that
there is a 1px wide vertical white line on the desktop that appears
whenever an application has focus. It is on the right side of the
monitor, covering the background wallpaper but not the menu.
Workaround: in Displays, change scale to something else than 100% and then
change back to 100%. That white vertical line will stay at the former 100%
window size location until the Settings window is closed. It disappears when
the Settings is closed.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2018-04-27 (1570 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Package: gnome-shell 42.2-0ubuntu0.2
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
RelatedPackageVersions: mutter-common 42.2-0ubuntu1
Tags: wayland-session jammy
Uname: Linux 5.15.0-46-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1986450/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2061981] Re: chromium fails to start with non-standard home directory
What is 'snap connections chromium | grep personal-files'? If you disconnect the dot-local-share ones, does Chromium start? -- 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/2061981 Title: chromium fails to start with non-standard home directory Status in chromium-browser package in Ubuntu: New Bug description: chromium 123.0.6312.122 2821 latest/stablecanonical cannot update snap namespace: cannot expand mount entry (none $HOME/.local/share none x-snapd.kind=ensure-dir,x-snapd.must-exist- dir=$HOME 0 0): cannot use invalid home directory "/home/department/user_name": permission denied Fails to start on Ubuntu 22.04 for users with 'non-standard' home directory /home/department/user_name Used to work fine up to last week. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: chromium-browser 1:85.0.4183.83-0ubuntu2.22.04.1 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Wed Apr 17 10:32:18 2024 InstallationDate: Installed on 2017-03-24 (2580 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Snap.Changes: ID Status Spawn Ready Summary 206 Error 2024-04-16T19:08:43+02:00 2024-04-16T19:16:51+02:00 Remove "chromium" snap 207 Done2024-04-16T19:17:27+02:00 2024-04-16T19:18:44+02:00 Remove "chromium" snap 208 Done2024-04-16T19:18:46+02:00 2024-04-16T19:19:47+02:00 Install "chromium" snap 209 Done2024-04-17T10:31:58+02:00 2024-04-17T10:32:02+02:00 Connect chromium:password-manager-service to snapd:password-manager-service SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2061981/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2061981] Re: chromium fails to start with non-standard home directory
Thanks, I'll look into the issue, for now you can use `snap revert chromium` to use the previous version. ** This bug is no longer a duplicate of bug 1620771 when /home is somewhere else, snaps don't work -- 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/2061981 Title: chromium fails to start with non-standard home directory Status in chromium-browser package in Ubuntu: New Bug description: chromium 123.0.6312.122 2821 latest/stablecanonical cannot update snap namespace: cannot expand mount entry (none $HOME/.local/share none x-snapd.kind=ensure-dir,x-snapd.must-exist- dir=$HOME 0 0): cannot use invalid home directory "/home/department/user_name": permission denied Fails to start on Ubuntu 22.04 for users with 'non-standard' home directory /home/department/user_name Used to work fine up to last week. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: chromium-browser 1:85.0.4183.83-0ubuntu2.22.04.1 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Wed Apr 17 10:32:18 2024 InstallationDate: Installed on 2017-03-24 (2580 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Snap.Changes: ID Status Spawn Ready Summary 206 Error 2024-04-16T19:08:43+02:00 2024-04-16T19:16:51+02:00 Remove "chromium" snap 207 Done2024-04-16T19:17:27+02:00 2024-04-16T19:18:44+02:00 Remove "chromium" snap 208 Done2024-04-16T19:18:46+02:00 2024-04-16T19:19:47+02:00 Install "chromium" snap 209 Done2024-04-17T10:31:58+02:00 2024-04-17T10:32:02+02:00 Connect chromium:password-manager-service to snapd:password-manager-service SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2061981/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1964100] Re: Cannot connect to open WLAN with 1.36.0-1ubuntu2 on Jammy
** Changed in: network-manager (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1964100 Title: Cannot connect to open WLAN with 1.36.0-1ubuntu2 on Jammy Status in network-manager package in Ubuntu: New Bug description: I'm trying to connect to an open (i.e. no ecryption) WLAN with network-manager 1.36.0-1ubuntu2 on 22.04 but it's failing with the following error message (after selecting the network from the network- manager applet prompt): Mär 08 10:50:04 Isaac-Laptop NetworkManager[31754]: [1646733004.4425] audit: op="connection-add-activate" pid=12122 uid=1000 result="fail" reason="802-11-wireless-security.key-mgmt: Access point does not support PSK but setting requires it" I haven't changed any of the default settings for network-manager and this network worked on 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1964100/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1986450] Re: Visual artifact 1px vertical white line right side of the wallpaper
Wow, I didn't realize that people were still trying to use Ambiance and Radiance (from source package ubuntu-themes) with Ubuntu 24.04 LTS. Would you like to submit a patch and subscribe ubuntu-sponsors? ** Package changed: light-themes (Ubuntu) => ubuntu-themes (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1986450 Title: Visual artifact 1px vertical white line right side of the wallpaper Status in gnome-shell package in Ubuntu: New Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: New Status in ubuntu-themes package in Ubuntu: New Bug description: After manually upgrading from 20.04 LTS to 22.04.1 LTS I find that there is a 1px wide vertical white line on the desktop that appears whenever an application has focus. It is on the right side of the monitor, covering the background wallpaper but not the menu. Workaround: in Displays, change scale to something else than 100% and then change back to 100%. That white vertical line will stay at the former 100% window size location until the Settings window is closed. It disappears when the Settings is closed. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2018-04-27 (1570 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: gnome-shell 42.2-0ubuntu0.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RelatedPackageVersions: mutter-common 42.2-0ubuntu1 Tags: wayland-session jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1986450/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2061118] Re: Rendering issues in vmware with 3d on (GTK ngl backend)
I was unable to complete the VMWare Workstation Player 17 install on a Ubuntu 24.04 LTS host even though there is a Linux installer. Note that this bug report says that the host is Windows 11. Similarly, I was able to install VirtualBox on a Ubuntu 24.04 LTS host but was unable to duplicate https://launchpad.net/bugs/2061584 . I suspect that it happens on a Windows 11 host because I have heard reports of it affecting someone with a Windows 11 host with Intel graphics (no Nvidia). I have other priority work I need to do today, but someone interested in trying to duplicate this bug should check if it happens with a Windows 11 host. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2061118 Title: Rendering issues in vmware with 3d on (GTK ngl backend) Status in GTK+: New Status in Mesa: New Status in gtk4 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Triaged Status in gtk4 source package in Noble: Invalid Status in mesa source package in Noble: Triaged Bug description: Build: Noble Daily Current from 12th April Host OS: Windows 11 VM App: VMWare Workstation 17 Player Issue: During installation there is continuous black flickering artefacts throughout the flow. Installation completed successfully, got to GDM, logged in but desktop screen is black and then locks up the whole application, cannot shutdown or interact with Player and need to hard kill from task manager. The issue appears does not appear with Mantic with the exact same machine configuration and appears to be an issue with GPU, my host machine is running an NVIDIA 4070ti with the latest windows drivers. On reboot some elements of the desktop are visible but cannot be interacted with without further lockups. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2061118/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
