[Desktop-packages] [Bug 2062980] Re: nautilus progress bar on ubuntu dock icon does not update
** Package changed: ubuntu => gnome-shell-extension-ubuntu-dock (Ubuntu) -- 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/2062980 Title: nautilus progress bar on ubuntu dock icon does not update Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: while copying files from another disk to /home folder, the progress bar on the nautilus icon in ubuntu dock does not update. however, the progress icon within nautilus does update. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: nautilus 1:46.0-0ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-28.28-generic 6.8.1 Uname: Linux 6.8.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Apr 20 22:46:11 2024 GsettingsChanges: b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'medium'" b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'initial-size' b'(1301, 915)' ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: nautilus-extension-gnome-terminal 3.52.0-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2062980/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2062980] [NEW] nautilus progress bar on ubuntu dock icon does not update
You have been subscribed to a public bug: while copying files from another disk to /home folder, the progress bar on the nautilus icon in ubuntu dock does not update. however, the progress icon within nautilus does update. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: nautilus 1:46.0-0ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-28.28-generic 6.8.1 Uname: Linux 6.8.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Apr 20 22:46:11 2024 GsettingsChanges: b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'medium'" b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'initial-size' b'(1301, 915)' ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: nautilus-extension-gnome-terminal 3.52.0-1ubuntu2 ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session -- nautilus progress bar on ubuntu dock icon does not update https://bugs.launchpad.net/bugs/2062980 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2063012] [NEW] package libglib2.0-0:armhf 2.72.4-0ubuntu2.2 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Public bug reported: Error while apt full-upgrade ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libglib2.0-0:armhf 2.72.4-0ubuntu2.2 Uname: Linux 4.9.140-l4t aarch64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: arm64 CasperMD5CheckResult: unknown Date: Sun Apr 21 11:23:54 2024 ErrorMessage: dependency problems - leaving triggers unprocessed PackageArchitecture: armhf Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.3 apt 2.4.12 SourcePackage: glib2.0 Title: package libglib2.0-0:armhf 2.72.4-0ubuntu2.2 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package armhf jammy third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2063012 Title: package libglib2.0-0:armhf 2.72.4-0ubuntu2.2 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in glib2.0 package in Ubuntu: New Bug description: Error while apt full-upgrade ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libglib2.0-0:armhf 2.72.4-0ubuntu2.2 Uname: Linux 4.9.140-l4t aarch64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: arm64 CasperMD5CheckResult: unknown Date: Sun Apr 21 11:23:54 2024 ErrorMessage: dependency problems - leaving triggers unprocessed PackageArchitecture: armhf Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.3 apt 2.4.12 SourcePackage: glib2.0 Title: package libglib2.0-0:armhf 2.72.4-0ubuntu2.2 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2063012/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2029416] Re: Can't move certain windows using touchscreen
*** This bug is a duplicate of bug 2063005 *** https://bugs.launchpad.net/bugs/2063005 ** This bug has been marked a duplicate of bug 2063005 Some shell elements don't respond to touchscreen in Xorg sessions -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2029416 Title: Can't move certain windows using touchscreen Status in mutter package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: When I try to move a window using the touchscreen by dragging the title bar, some programs work, but others don't. The behavior with the programs that don't work is particularly odd. When I start trying to drag the window, the cursor becomes visible (which it normally isn't when using the touchscreen), the cursor switches to the "move" shape, then the cursor follows my finger (the window doesn't move). When I remove my finger from the screen, the cursor remains visible and in the "move" shape, moving the mouse will then cause the window to move (even though I never clicked), and the window will remain attached to the mouse cursor until you click. Broken programs: - Files - Firefox - NVIDIA X Server Settings - Settings - Power Statistics - Extensions - Software & Updates - Text Editor - Shotwell - Calculator - Startup Disk Creator - Minecraft Launcher - xclock Working programs: - Cheese - Help - System Monitor - Videos - Mines - Terminal ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-26.26-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Aug 2 16:05:32 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-08-02 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 44.3-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2029416/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2063005] Re: Some shell elements don't respond to touchscreen in Xorg sessions
Previously reported in bug 2029416 but since that release is deprecated we will track it 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/2063005 Title: Some shell elements don't respond to touchscreen in Xorg sessions Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: Starting in GNOME 46 touchscreen input on the X11 session has become unusable the touchscreen is responsive on the desktop itself (moving the cursor) but does not interact with most things on GNOME 46 on the current version of Ubuntu Noble, touch input does NOT work with: - On screen keyboard (touch is registered but no keystrokes get input) - clicking options in gnome appindicators (indicators can be opened but clicking any option does nothing) - interacting with application overview (cannot press left and right buttons or search bar) - selecting textboxs - any of the touch gestures (eg: swipe up from bottom to bringup keyboard) All of the above worked just fine on GNOME 45 on Ubuntu Mantic (and Ubuntu Noble from March and earlier before it was "upgraded" to GNOME 46). Tested on a fresh image as well as an old image from February running GNOME 45 upgraded to the latest packages with GNOME 46 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2063005/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2063005] Re: Some shell elements don't respond to touchscreen in Xorg sessions
** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Changed in: xorg-server (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/2063005 Title: Some shell elements don't respond to touchscreen in Xorg sessions Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: Starting in GNOME 46 touchscreen input on the X11 session has become unusable the touchscreen is responsive on the desktop itself (moving the cursor) but does not interact with most things on GNOME 46 on the current version of Ubuntu Noble, touch input does NOT work with: - On screen keyboard (touch is registered but no keystrokes get input) - clicking options in gnome appindicators (indicators can be opened but clicking any option does nothing) - interacting with application overview (cannot press left and right buttons or search bar) - selecting textboxs - any of the touch gestures (eg: swipe up from bottom to bringup keyboard) All of the above worked just fine on GNOME 45 on Ubuntu Mantic (and Ubuntu Noble from March and earlier before it was "upgraded" to GNOME 46). Tested on a fresh image as well as an old image from February running GNOME 45 upgraded to the latest packages with GNOME 46 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2063005/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2063005] Re: Onscreen keyboard is disabled by default
Sorry, I missed the "X11 session" part. Bug confirmed. ** No longer affects: gsettings-desktop-schemas (Ubuntu) ** Summary changed: - Onscreen keyboard is disabled by default + Some shell elements don't respond to touchscreen in Xorg sessions ** Changed in: gnome-shell (Ubuntu) Importance: Low => Medium ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/2063005 Title: Some shell elements don't respond to touchscreen in Xorg sessions Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: Starting in GNOME 46 touchscreen input on the X11 session has become unusable the touchscreen is responsive on the desktop itself (moving the cursor) but does not interact with most things on GNOME 46 on the current version of Ubuntu Noble, touch input does NOT work with: - On screen keyboard (touch is registered but no keystrokes get input) - clicking options in gnome appindicators (indicators can be opened but clicking any option does nothing) - interacting with application overview (cannot press left and right buttons or search bar) - selecting textboxs - any of the touch gestures (eg: swipe up from bottom to bringup keyboard) All of the above worked just fine on GNOME 45 on Ubuntu Mantic (and Ubuntu Noble from March and earlier before it was "upgraded" to GNOME 46). Tested on a fresh image as well as an old image from February running GNOME 45 upgraded to the latest packages with GNOME 46 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2063005/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2063005] Re: Some shell elements don't respond to touchscreen in Xorg sessions
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 gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2063005 Title: Some shell elements don't respond to touchscreen in Xorg sessions Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: Starting in GNOME 46 touchscreen input on the X11 session has become unusable the touchscreen is responsive on the desktop itself (moving the cursor) but does not interact with most things on GNOME 46 on the current version of Ubuntu Noble, touch input does NOT work with: - On screen keyboard (touch is registered but no keystrokes get input) - clicking options in gnome appindicators (indicators can be opened but clicking any option does nothing) - interacting with application overview (cannot press left and right buttons or search bar) - selecting textboxs - any of the touch gestures (eg: swipe up from bottom to bringup keyboard) All of the above worked just fine on GNOME 45 on Ubuntu Mantic (and Ubuntu Noble from March and earlier before it was "upgraded" to GNOME 46). Tested on a fresh image as well as an old image from February running GNOME 45 upgraded to the latest packages with GNOME 46 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2063005/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2063005] Re: Onscreen keyboard is disabled by default
Looks like it's been disabled for at least 6 years: https://gitlab.gnome.org/GNOME/gsettings-desktop- schemas/-/blob/master/schemas/org.gnome.desktop.a11y.applications.gschema.xml.in?ref_type=heads so whether or not it gets toggled automatically is probably up to gnome- shell. ** Changed in: gsettings-desktop-schemas (Ubuntu) Status: New => Won't Fix ** Changed in: gnome-shell (Ubuntu) Importance: Medium => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/2063005 Title: Onscreen keyboard is disabled by default Status in gnome-shell package in Ubuntu: Confirmed Bug description: Starting in GNOME 46 touchscreen input on the X11 session has become unusable the touchscreen is responsive on the desktop itself (moving the cursor) but does not interact with most things on GNOME 46 on the current version of Ubuntu Noble, touch input does NOT work with: - On screen keyboard (touch is registered but no keystrokes get input) - clicking options in gnome appindicators (indicators can be opened but clicking any option does nothing) - interacting with application overview (cannot press left and right buttons or search bar) - selecting textboxs - any of the touch gestures (eg: swipe up from bottom to bringup keyboard) All of the above worked just fine on GNOME 45 on Ubuntu Mantic (and Ubuntu Noble from March and earlier before it was "upgraded" to GNOME 46). Tested on a fresh image as well as an old image from February running GNOME 45 upgraded to the latest packages with GNOME 46 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2063005/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2063005] Re: touchscreen input critical regressions in GNOME 45 to 46
Partially confirmed. It looks like the onscreen keyboard is always disabled by default. You have to enable it in: Settings > Accessibility > Typing > Screen Keyboard = ON After I did that, all the features mentioned here started working. ** Package changed: mutter (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Confirmed ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Medium ** Summary changed: - touchscreen input critical regressions in GNOME 45 to 46 + Onscreen keyboard is disabled by default ** Tags added: osk ** Also affects: gsettings-desktop-schemas (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/2063005 Title: Onscreen keyboard is disabled by default Status in gnome-shell package in Ubuntu: Confirmed Bug description: Starting in GNOME 46 touchscreen input on the X11 session has become unusable the touchscreen is responsive on the desktop itself (moving the cursor) but does not interact with most things on GNOME 46 on the current version of Ubuntu Noble, touch input does NOT work with: - On screen keyboard (touch is registered but no keystrokes get input) - clicking options in gnome appindicators (indicators can be opened but clicking any option does nothing) - interacting with application overview (cannot press left and right buttons or search bar) - selecting textboxs - any of the touch gestures (eg: swipe up from bottom to bringup keyboard) All of the above worked just fine on GNOME 45 on Ubuntu Mantic (and Ubuntu Noble from March and earlier before it was "upgraded" to GNOME 46). Tested on a fresh image as well as an old image from February running GNOME 45 upgraded to the latest packages with GNOME 46 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2063005/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2063005] Re: touchscreen input critical regressions in GNOME 45 to 46
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 2063005 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Changed in: mutter (Ubuntu) Status: New => Incomplete ** Tags added: noble touch touchscreen -- 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/2063005 Title: Onscreen keyboard is disabled by default Status in gnome-shell package in Ubuntu: Confirmed Bug description: Starting in GNOME 46 touchscreen input on the X11 session has become unusable the touchscreen is responsive on the desktop itself (moving the cursor) but does not interact with most things on GNOME 46 on the current version of Ubuntu Noble, touch input does NOT work with: - On screen keyboard (touch is registered but no keystrokes get input) - clicking options in gnome appindicators (indicators can be opened but clicking any option does nothing) - interacting with application overview (cannot press left and right buttons or search bar) - selecting textboxs - any of the touch gestures (eg: swipe up from bottom to bringup keyboard) All of the above worked just fine on GNOME 45 on Ubuntu Mantic (and Ubuntu Noble from March and earlier before it was "upgraded" to GNOME 46). Tested on a fresh image as well as an old image from February running GNOME 45 upgraded to the latest packages with GNOME 46 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2063005/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2062949] Re: gnome-remote-desktop-daemon crashed with SIGSEGV in g_main_context_iteration()
** No longer affects: gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/2062949 Title: gnome-remote-desktop-daemon crashed with SIGSEGV in g_main_context_iteration() Status in gnome-remote-desktop package in Ubuntu: New Bug description: In 24.04, attempting to launch into a Remote Login RDP session (which uses the wayland compositor) with an Nvidia GPU connected on the host gives a black screen. The purpose of having the GPU is to provide HW acceleration to gnome-remote-desktop on the host (the RDP host is a 24.04 VM.) The Nvidia GPU does not have a display adapter, therefore a dummy adapter cannot be used to fool the machine into believing there is a monitor attached. The Remote Login session is only black screen if the Nvidia GPU is attached. When the RDP client (I am using the standard Remote Desktop connection client on a Windows 10 device) logs out from gnome-remote-desktop, both grd and gnome-shell crash with SIGSEGV. In Ubuntu version 22.04, attaching a Nvidia GPU to the 22.04 host VM and launching a gnome-remote-desktop on "Ubuntu on Wayland" did not cause a crash or any black screens, and the RDP instance had fully supported HW acceleration for the desktop. ProblemType: Crash DistroRelease: Ubuntu 24.04 Package: gnome-remote-desktop 46.1-1 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 Date: Fri Apr 19 00:29:37 2024 ExecutablePath: /usr/libexec/gnome-remote-desktop-daemon InstallationDate: Installed on 2024-04-18 (1 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240410.2) ProcCmdline: /usr/libexec/gnome-remote-desktop-daemon --system ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SegvAnalysis: Segfault happened at: 0x76f9b13c9a11:cmpq $0x0,0x18(%rax) PC (0x76f9b13c9a11) ok source "$0x0" ok destination "0x18(%rax)" (0x0018) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SignalName: SIGSEGV SourcePackage: gnome-remote-desktop StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_application_run () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: gnome-remote-desktop-daemon crashed with SIGSEGV in g_main_context_iteration() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2062949/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2063005] Re: touchscreen input critical regressions in GNOME 45 to 46
** Description changed: Starting in GNOME 46 touchscreen input on the X11 session has become unusable - the touchscreen is responsive and on the desktop itself (moving the - cursor) but does not interact with most things + the touchscreen is responsive on the desktop itself (moving the cursor) + but does not interact with most things on GNOME 46 on the current version of Ubuntu Noble, touch input does NOT work with: - On screen keyboard (touch is registered but no keystrokes get input) - clicking options in gnome appindicators (indicators can be opened but clicking any option does nothing) - interacting with application overview (cannot press left and right buttons or search bar) - selecting textboxs - any of the touch gestures (eg: swipe up from bottom to bringup keyboard) All of the above worked just fine on GNOME 45 on Ubuntu Mantic (and Ubuntu Noble from March and earlier before it was "upgraded" to GNOME 46). Tested on a fresh image as well as an old image from February running GNOME 45 upgraded to the latest packages with GNOME 46 -- 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/2063005 Title: touchscreen input critical regressions in GNOME 45 to 46 Status in mutter package in Ubuntu: New Bug description: Starting in GNOME 46 touchscreen input on the X11 session has become unusable the touchscreen is responsive on the desktop itself (moving the cursor) but does not interact with most things on GNOME 46 on the current version of Ubuntu Noble, touch input does NOT work with: - On screen keyboard (touch is registered but no keystrokes get input) - clicking options in gnome appindicators (indicators can be opened but clicking any option does nothing) - interacting with application overview (cannot press left and right buttons or search bar) - selecting textboxs - any of the touch gestures (eg: swipe up from bottom to bringup keyboard) All of the above worked just fine on GNOME 45 on Ubuntu Mantic (and Ubuntu Noble from March and earlier before it was "upgraded" to GNOME 46). Tested on a fresh image as well as an old image from February running GNOME 45 upgraded to the latest packages with GNOME 46 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2063005/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2060534] Re: Thunderbird doesn't always clean nstmp cache files
Launchpad has imported 38 comments from the remote bug at https://bugzilla.mozilla.org/show_bug.cgi?id=1878541. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2024-02-04T09:38:58+00:00 Omry Yadan wrote: Created attachment 9378154 Screenshot_9.png User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/121.0.0.0 Safari/537.36 Edg/121.0.0.0 Steps to reproduce: I am not sure how to trigger it. I get system warnings about the disk being full and then I see a nstmp file using 1TB. I deleted it, and hours later it happened again. This have happened a few times for me in the past few weeks, but it seems to be happening more and more. Additional context: I am using imap. The entire mailbox on the server is 9.9GB. Thunderbird 123.0b2 (64-bit) OS: Edition Windows 11 Pro Version 22H2 Installed on22/01/2023 OS build22621.3007 Experience Windows Feature Experience Pack 1000.22681.1000.0 Reply at: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2060534/comments/0 On 2024-02-05T10:34:18+00:00 Mkmelin+mozilla wrote: That's only used for compacting folders. https://searchfox.org/comm-central/rev/1452d8f1e1582cc44529f638e1eba1c7b3804fe4/mailnews/base/src/nsMsgFolderCompactor.cpp#393 The sent folder is also quite large, 50GB. Is auto compact enabled, or do you do compaction only when it asks/or manually? Reply at: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2060534/comments/1 On 2024-02-05T11:19:45+00:00 Omry Yadan wrote: > Is auto compact enabled, or do you do compaction only when it asks/or manually? I didn't change the setting, so I think it's probably enabled by default. I dug through the settings now and was not able to locate it. > The sent folder is also quite large, 50GB. I noticed that too. I deleted it and it. The reconstructed file is 16GB. > That's only used for compacting folders. https://searchfox.org/comm- central/rev/1452d8f1e1582cc44529f638e1eba1c7b3804fe4/mailnews/base/src/nsMsgFolderCompactor.cpp#393 It looks like this function is not always cleaning up after itself. For example, if an exception is thrown here, CleanupTempFilesAfterError is never called: https://searchfox.org/comm-central/rev/1452d8f1e1582cc44529f638e1eba1c7b3804fe4/mailnews/base/src/nsMsgFolderCompactor.cpp#411 Why not wrap it with a big "try finally" to always delete the file if it exists when the function returns? Reply at: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2060534/comments/2 On 2024-02-05T11:20:48+00:00 Omry Yadan wrote: There is also the underlying question of why on earth the function is creating a file that is 1TB in size. It sounds like there is a quadratic usage of disk space in the compaction algorithm. Reply at: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2060534/comments/3 On 2024-02-05T11:30:25+00:00 Omry Yadan wrote: There is an attempt to clean up the file if it's still there in the destructor: https://searchfox.org/comm-central/source/mailnews/base/src/nsMsgFolderCompactor.cpp#171-177 However, it only kicks in if NV_FAILED returns true. Reply at: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2060534/comments/4 On 2024-02-05T13:11:17+00:00 Anjeyelf wrote: Sounds like the Sent-1 file is so big it's not possible to do compacting maybe because either Thunderbird is interrupted during the compacting eg: shutdown, crash or receiving mail into the folder being compacted, maybe another program is scanning the file or it's possible that you might not be able to compact a large folder because you don't have enough free disk space or memory or there is some type of corruption in the file. 50GB is very large for a single text file and it looks like it's been failing to compact for a while, so is full of old deleted mail. Does it say anything in the Error console ? Open Error console (Ctrl + Shift + J') or 'Tools' > 'Developer Tools' > 'Error Console' Clear Error console - top left bin icon right click on 'Sent' folder and select 'compact' If compacting does not work - Sent-1 is still 50Gb and nsmtp appears. What do you see in Error Console - please post an image. Either way you need a solution to overcome the current issue. Suggestion: - Create a new folder called 'Sent Store'. - Move all the wanted sent emails into 'Sent Store' as a precaution to
[Desktop-packages] [Bug 2063005] Re: touchscreen input critical regressions in GNOME 45 to 46
** Description changed: Starting in GNOME 46 touchscreen input on the X11 session has become unusable the touchscreen is responsive and on the desktop itself (moving the cursor) but does not interact with most things on GNOME 46 on the current version of Ubuntu Noble, touch input does NOT work with: - On screen keyboard (touch is registered but no keystrokes get input) - clicking options in gnome appindicators (indicators can be opened but clicking any option does nothing) - - iterating with application overview (cannot press left and right buttons or search bar) + - interacting with application overview (cannot press left and right buttons or search bar) - selecting textboxs - any of the touch gestures (eg: swipe up from bottom to bringup keyboard) - - All of the above worked just fine on GNOME 45 on Ubuntu Mantic (and Ubuntu Noble from March and earlier before it was "upgraded" to GNOME 46). + All of the above worked just fine on GNOME 45 on Ubuntu Mantic (and + Ubuntu Noble from March and earlier before it was "upgraded" to GNOME + 46). Tested on a fresh image as well as an old image from February running GNOME 45 upgraded to the latest packages with GNOME 46 -- 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/2063005 Title: touchscreen input critical regressions in GNOME 45 to 46 Status in mutter package in Ubuntu: New Bug description: Starting in GNOME 46 touchscreen input on the X11 session has become unusable the touchscreen is responsive and on the desktop itself (moving the cursor) but does not interact with most things on GNOME 46 on the current version of Ubuntu Noble, touch input does NOT work with: - On screen keyboard (touch is registered but no keystrokes get input) - clicking options in gnome appindicators (indicators can be opened but clicking any option does nothing) - interacting with application overview (cannot press left and right buttons or search bar) - selecting textboxs - any of the touch gestures (eg: swipe up from bottom to bringup keyboard) All of the above worked just fine on GNOME 45 on Ubuntu Mantic (and Ubuntu Noble from March and earlier before it was "upgraded" to GNOME 46). Tested on a fresh image as well as an old image from February running GNOME 45 upgraded to the latest packages with GNOME 46 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2063005/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2056767] Re: FFe: Sync gnome-software 46.0-4 (universe) from Debian unstable (main) with gnome-software packaging split
@theofficialgman the 1992498 change is dropped in this version ** Changed in: gnome-software (Ubuntu) Status: Incomplete => New -- 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/2056767 Title: FFe: Sync gnome-software 46.0-4 (universe) from Debian unstable (main) with gnome-software packaging split Status in gnome-software package in Ubuntu: New Bug description: Impact -- I request permission to sync the gnome-software packaging from Debian. The biggest change is splitting gnome-software's .deb support into a separate package, gnome-software-plugin-deb, to match the existing -snap and -flatpak packages. This will allow users and flavors to specifically opt into the parts of the GNOME Software experience they want. For instance, someone may want to use only the Flatpak part because they use the Snap Store to manage .debs and Snaps. Or maybe they want a different combination. This has been requested by multiple users on Ubuntu Discourse and at least one Launchpad bug and one Debian bug. fwupd plugin I am dropping the fwupd plugin (now in a separate package too) to Suggests so upgrades to Ubuntu 24.04 LTS will likely get it uninstalled and new installs won't have it either unless a user explicitly installs it later. Ubuntu Desktop includes the firmware-updater snap. Several Ubuntu desktop flavors also include it. For people who don't want snaps, there is also the gnome-firmware app packaged as a .deb. Because Ubuntu already has update-manager to handle apt update notifications, I am also dropping the autostart file to reduce background RAM use. A few Ubuntu desktop flavors do not provide any firmware updater app at all. Ubuntu Budgie developers thought a firmware updater app was too technical for inclusion in the default Ubuntu 24.04 LTS install. autostart - I have also dropped the autostart file since the fwupd plugin is no longer included by default and Ubuntu already has ways to notify users about available apt updates (update-manager and unattended upgrades) and snaps already automatically update. Potential Problems --- gnome-software has an explicit Recommend: gnome-software-plugin-deb so that people upgrading to Ubuntu 24.04 LTS will keep the deb support installed. That recommends will be dropped for Ubuntu 26.04 LTS because it won't be needed then. (There is a Depends on the virtual packages that enable installing apps.) Full Changelog Entries -- gnome-software (46.0-4) unstable; urgency=medium * Fix typo in gnome-software-plugin-deb package description * Add lintian overrides for desktop-command-not-in-package -- Jeremy Bícha Fri, 29 Mar 2024 16:45:30 -0400 gnome-software (46.0-3) unstable; urgency=medium * Update Homepage * Release to Unstable -- Jeremy Bícha Thu, 28 Mar 2024 13:23:28 -0400 gnome-software (46.0-2) experimental; urgency=medium * Split deb support into separate gnome-software-plugin-deb package (Closes: #1066030) (LP: #2019137, #2056767) * Have each plugin provide a virtual gnome-software-plugin package * Suggest all the gnome-software plugins * Recommend gnome-software-plugin-deb for upgrades * Split firmware update support into separate fwupd plugin & recommend it except on Ubuntu which provides a separate firmware-updater app Intentionally, do not have this provides the virtual gnome-software-plugin since it doesn't allow browsing apps. * Drop patch that hides upstreams Software Sources dialog (Closes: #1060803) * Drop Depends: software-properties-gtk * Stop recommending gnome-software-plugin-snap on Ubuntu -- Jeremy Bícha Wed, 27 Mar 2024 18:33:03 -0400 Build Logs -- https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/ppa/+sourcepub/15898505/+listing-archive-extra Desktop Flavors Affected GNOME Software is currently included in the default install for only Ubuntu Cinnamon. See Joshua's comment below. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2056767/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2063005] [NEW] touchscreen input critical regressions in GNOME 45 to 46
Public bug reported: Starting in GNOME 46 touchscreen input on the X11 session has become unusable the touchscreen is responsive and on the desktop itself (moving the cursor) but does not interact with most things on GNOME 46 on the current version of Ubuntu Noble, touch input does NOT work with: - On screen keyboard (touch is registered but no keystrokes get input) - clicking options in gnome appindicators (indicators can be opened but clicking any option does nothing) - interacting with application overview (cannot press left and right buttons or search bar) - selecting textboxs - any of the touch gestures (eg: swipe up from bottom to bringup keyboard) All of the above worked just fine on GNOME 45 on Ubuntu Mantic (and Ubuntu Noble from March and earlier before it was "upgraded" to GNOME 46). Tested on a fresh image as well as an old image from February running GNOME 45 upgraded to the latest packages with GNOME 46 ** Affects: mutter (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2063005 Title: touchscreen input critical regressions in GNOME 45 to 46 Status in mutter package in Ubuntu: New Bug description: Starting in GNOME 46 touchscreen input on the X11 session has become unusable the touchscreen is responsive and on the desktop itself (moving the cursor) but does not interact with most things on GNOME 46 on the current version of Ubuntu Noble, touch input does NOT work with: - On screen keyboard (touch is registered but no keystrokes get input) - clicking options in gnome appindicators (indicators can be opened but clicking any option does nothing) - interacting with application overview (cannot press left and right buttons or search bar) - selecting textboxs - any of the touch gestures (eg: swipe up from bottom to bringup keyboard) All of the above worked just fine on GNOME 45 on Ubuntu Mantic (and Ubuntu Noble from March and earlier before it was "upgraded" to GNOME 46). Tested on a fresh image as well as an old image from February running GNOME 45 upgraded to the latest packages with GNOME 46 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2063005/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2062995] [NEW] With nvidia-dkms-470 need GSK_RENDERER=cairo WEBKIT_DISABLE_DMABUF_RENDERER=1
Public bug reported: I have an Nvidia GeForce GT 710, which requires the legacy 470 proprietary driver. Both foliate and epiphany-browser display improperly by default. Some user interface elements are missing, and e-book and web pages are totally blank. To fix this, I added the following lines to /etc/environment : GSK_RENDERER=cairo WEBKIT_DISABLE_DMABUF_RENDERER=1 In the past WEBKIT_DISABLE_DMABUF_RENDERER=1 was enough, but in Ubuntu 24.04 I also require GSK_RENDERER=cairo. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: libwebkitgtk-6.0-4 2.44.0-2 ProcVersionSignature: Ubuntu 6.8.0-28.28-generic 6.8.1 Uname: Linux 6.8.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Apr 20 18:57:04 2024 SourcePackage: webkit2gtk UpgradeStatus: Upgraded to noble on 2024-04-17 (3 days ago) ** Affects: webkit2gtk (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 webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/2062995 Title: With nvidia-dkms-470 need GSK_RENDERER=cairo WEBKIT_DISABLE_DMABUF_RENDERER=1 Status in webkit2gtk package in Ubuntu: New Bug description: I have an Nvidia GeForce GT 710, which requires the legacy 470 proprietary driver. Both foliate and epiphany-browser display improperly by default. Some user interface elements are missing, and e-book and web pages are totally blank. To fix this, I added the following lines to /etc/environment : GSK_RENDERER=cairo WEBKIT_DISABLE_DMABUF_RENDERER=1 In the past WEBKIT_DISABLE_DMABUF_RENDERER=1 was enough, but in Ubuntu 24.04 I also require GSK_RENDERER=cairo. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: libwebkitgtk-6.0-4 2.44.0-2 ProcVersionSignature: Ubuntu 6.8.0-28.28-generic 6.8.1 Uname: Linux 6.8.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Apr 20 18:57:04 2024 SourcePackage: webkit2gtk UpgradeStatus: Upgraded to noble on 2024-04-17 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/2062995/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2056767] Re: FFe: Sync gnome-software 46.0-4 (universe) from Debian unstable (main) with gnome-software packaging split
Hopefully this can also be reverted or added in a separate package https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1992498 -- 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/2056767 Title: FFe: Sync gnome-software 46.0-4 (universe) from Debian unstable (main) with gnome-software packaging split Status in gnome-software package in Ubuntu: Incomplete Bug description: Impact -- I request permission to sync the gnome-software packaging from Debian. The biggest change is splitting gnome-software's .deb support into a separate package, gnome-software-plugin-deb, to match the existing -snap and -flatpak packages. This will allow users and flavors to specifically opt into the parts of the GNOME Software experience they want. For instance, someone may want to use only the Flatpak part because they use the Snap Store to manage .debs and Snaps. Or maybe they want a different combination. This has been requested by multiple users on Ubuntu Discourse and at least one Launchpad bug and one Debian bug. fwupd plugin I am dropping the fwupd plugin (now in a separate package too) to Suggests so upgrades to Ubuntu 24.04 LTS will likely get it uninstalled and new installs won't have it either unless a user explicitly installs it later. Ubuntu Desktop includes the firmware-updater snap. Several Ubuntu desktop flavors also include it. For people who don't want snaps, there is also the gnome-firmware app packaged as a .deb. Because Ubuntu already has update-manager to handle apt update notifications, I am also dropping the autostart file to reduce background RAM use. A few Ubuntu desktop flavors do not provide any firmware updater app at all. Ubuntu Budgie developers thought a firmware updater app was too technical for inclusion in the default Ubuntu 24.04 LTS install. autostart - I have also dropped the autostart file since the fwupd plugin is no longer included by default and Ubuntu already has ways to notify users about available apt updates (update-manager and unattended upgrades) and snaps already automatically update. Potential Problems --- gnome-software has an explicit Recommend: gnome-software-plugin-deb so that people upgrading to Ubuntu 24.04 LTS will keep the deb support installed. That recommends will be dropped for Ubuntu 26.04 LTS because it won't be needed then. (There is a Depends on the virtual packages that enable installing apps.) Full Changelog Entries -- gnome-software (46.0-4) unstable; urgency=medium * Fix typo in gnome-software-plugin-deb package description * Add lintian overrides for desktop-command-not-in-package -- Jeremy Bícha Fri, 29 Mar 2024 16:45:30 -0400 gnome-software (46.0-3) unstable; urgency=medium * Update Homepage * Release to Unstable -- Jeremy Bícha Thu, 28 Mar 2024 13:23:28 -0400 gnome-software (46.0-2) experimental; urgency=medium * Split deb support into separate gnome-software-plugin-deb package (Closes: #1066030) (LP: #2019137, #2056767) * Have each plugin provide a virtual gnome-software-plugin package * Suggest all the gnome-software plugins * Recommend gnome-software-plugin-deb for upgrades * Split firmware update support into separate fwupd plugin & recommend it except on Ubuntu which provides a separate firmware-updater app Intentionally, do not have this provides the virtual gnome-software-plugin since it doesn't allow browsing apps. * Drop patch that hides upstreams Software Sources dialog (Closes: #1060803) * Drop Depends: software-properties-gtk * Stop recommending gnome-software-plugin-snap on Ubuntu -- Jeremy Bícha Wed, 27 Mar 2024 18:33:03 -0400 Build Logs -- https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/ppa/+sourcepub/15898505/+listing-archive-extra Desktop Flavors Affected GNOME Software is currently included in the default install for only Ubuntu Cinnamon. See Joshua's comment below. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2056767/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2061995] Re: ULTS 22, 24: FontConfig broken by including ".conf" file
** Summary changed: - ULLTS 22,24: FontConfig broken by including ".conf" file + ULTS 22,24: FontConfig broken by including ".conf" file -- 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: ULTS 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 1940836] Re: Libreoffice Calc rendering very slow on GTK3
related upstream bug: https://bugs.documentfoundation.org/show_bug.cgi?id=154602 ** Bug watch added: Document Foundation Bugzilla #154602 https://bugs.documentfoundation.org/show_bug.cgi?id=154602 -- 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/1940836 Title: Libreoffice Calc rendering very slow on GTK3 Status in libreoffice package in Ubuntu: Confirmed Bug description: I'm on a MATE 20.04 machine, with Nvidia proprietary drivers (for reference, can't use Nouveau, since my machine doesn't boot with it). Libreoffice Calc renders slow. The delay is very noticeable, even when just typing characters. If I remove the GTK3 styling (`libreoffice-gtk3` package), then the rendering speed is fine (but of course, the program is unstyled, with some workflow consequences). I've tried to run on GTK2 (`libreoffice-gtk2` package installed), but I see Calc as unstyled, so it seems it's not actually running on GTK2. I've also tried to disable HW acceleration, but there is no improvement. I don't experience this slowness on any other program on my installation. I've noticed that when there's a delay, the Xorg process CPU occupation skyrockets (depending on how fast I type, it may go even to 100% (single thread)). I've reproduced the same problem on all the LO versions, from the default (6.4.7) to the latest (7.2). The kernel version doesn't affect the problem as well (experienced on different 5.x versions). I've tried a packaged LO (from https://libreoffice.soluzioniopen.com), and it has the same behavior. I'd be perfectly happy to run on GTK2 as workaround, if that allowed persistent copy/paste :) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice-calc 1:6.4.7-0ubuntu0.20.04.1 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Mon Aug 23 15:21:08 2021 InstallationDate: Installed on 2020-07-01 (418 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1940836/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2056758] Re: ubuntu-bug doesn't let me file bugs for Snap thunderbird
> Do you have the thunderbird deb also installed? Do you get prompted to report against the snap or deb? if by the deb you mean the transitional package, then i have it uninstalled, marked as "residual-config". I don't get prompted to file against the deb. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/2056758 Title: ubuntu-bug doesn't let me file bugs for Snap thunderbird Status in apport package in Ubuntu: Triaged Status in thunderbird package in Ubuntu: Incomplete Bug description: I'm trying to report a bug in the new Snap for Thunderbird. When I run "ubuntu-bug thunderbird", it: * Collects information correctly after I input the sudo password * Opens a page like https://bugs.launchpad.net/distros/+filebug/a9564134-dfa6-11ee-85a7-c7116d9f638e?, which does not seem to be valid. This is not the case for Firefox, which works fine with ubuntu-bug. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: apport 2.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CrashReports: 640:1000:124:483410:2024-03-11 14:47:26.874792575 +0400:2024-03-11 14:47:27.874792575 +0400:/var/crash/_opt_Citrix_ICAClient_util_storebrowse.1000.crash 640:0:124:29135:2024-03-10 17:02:30.124656623 +0400:2024-03-10 17:02:30.124656623 +0400:/var/crash/_usr_share_apport_apport.0.crash CurrentDesktop: KDE Date: Mon Mar 11 16:54:18 2024 InstallationDate: Installed on 2022-08-29 (560 days ago) InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to noble on 2024-02-23 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2056758/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2056760] Re: [snap]Thunderbird doesn't authenticate with sssd-kcm
Seems I do:
```
Ապր 20 23:24:32 helga-rashomon kernel: audit: type=1400
audit(1713641072.496:307): apparmor="DENIED" operation="open" class="file"
profile="snap.thunderbird.thunderbird" name="/etc/gss/mech.d/" pid=54398
comm="IMAP" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Ապր 20 23:24:32 helga-rashomon kernel: audit: type=1400
audit(1713641072.503:308): apparmor="DENIED" operation="connect" class="file"
profile="snap.thunderbird.thunderbird" name="/run/.heim_org.h5l.kcm-socket"
pid=54398 comm="IMAP" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=0
Ապր 20 23:24:32 helga-rashomon dbus-daemon[2973]: apparmor="DENIED"
operation="dbus_method_call" bus="session"
path="/org/freedesktop/Notifications" interface="org.freedesktop.Notifications"
member="GetServerInformation" mask="send" name=":1.26" pid=54398
label="snap.thunderbird.thunderbird" peer_pid=3360 peer_label="plasmashell"
Ապր 20 23:24:32 helga-rashomon kernel: audit: type=1400
audit(1713641072.529:309): apparmor="DENIED" operation="connect" class="file"
profile="snap.thunderbird.thunderbird" name="/run/.heim_org.h5l.kcm-socket"
pid=54398 comm="IMAP" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=0
```
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/2056760
Title:
[snap]Thunderbird doesn't authenticate with sssd-kcm
Status in sssd package in Ubuntu:
Incomplete
Status in thunderbird package in Ubuntu:
New
Bug description:
I have Kerberos authentication set up in Thunderbird for my mailbox.
My environment contains:
helga@helga-rashomon:~$ env | grep KRB
KRB5CCNAME=KCM:
This means that Kerberos authentication should work through the sssd-
kcm server.
I initialize Kerberos and verify that it functions correctly:
helga@helga-rashomon:~$ klist
Ticket cache: KCM:1000
Default principal: he...@example.org
Valid starting Expires Service principal
03/11/24 04:14:24 03/12/24 04:14:24 krbtgt/example@example.org
03/11/24 04:15:24 03/12/24 04:14:24 HTTP/redmine.example.org@
Ticket server: HTTP/redmine.example@example.org
(listing redacted to say example.org instead of the real address. the
redmine listing shows that Firefox works correctly with this address)
However, when I open the Snap Thunderbird, it does not recognize this
Kerberos setup, showing me "The Kerberos/GSSAPI ticket was not
accepted by the IMAP server". klist -A likewise shows no changes.
The exact same setup works when I specify KRB5CCNAME=DIR:${HOME}/krb5cc in
.profile instead.
The sssd-kcm setup also works in Thunderbird native and Flatpak profiles.
Considering the Flatpak specifically permits access to
/run/.heim_org.h5l.kcm-socket, could it be that the Thunderbird Snap
is not allowed to access this socket?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/2056760/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2062982] [NEW] [USB-Audio - SB Live! 24-bit External, playback] volume slider and mute button have no effect
Public bug reported: When the external sound card (SB Live! 24 bit) is used, the volume slider and the mute button have no effect. The volume is low. I tried two SB Live! 24 bit cards (at home and at work). The behaviour is the same. On Lubuntu 20.04, there was no problem. The embedded sound card operates normally and reacts on the volume slider. Ubuntu 22.04.4 LTS pulseaudio 1:15.99.1+dfsg1-1ubuntu2.2 pavucontrol 5.0-2 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 Uname: Linux 6.8.7-2-liquorix-amd64 x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Sat Apr 20 21:33:26 2024 InstallationDate: Installed on 2024-04-03 (16 days ago) InstallationMedia: Lubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240216) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: SoundBlaster Live! 24-bit External SB0490 - SB Live! 24-bit External Symptom_PulseAudioLog: кві 20 19:57:33 Lattitude dbus-daemon[590]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.33' (uid=1001 pid=845 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo") Symptom_Type: Volume slider, or mixer problems Title: [USB-Audio - SB Live! 24-bit External, playback] volume slider problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2023 dmi.bios.release: 1.32 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.32.2 dmi.board.name: 015DR5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.asset.tag: NTB71181 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.32.2:bd09/22/2023:br1.32:svnDellInc.:pnLatitude5480:pvr:rvnDellInc.:rn015DR5:rvrA00:cvnDellInc.:ct10:cvr:sku07A7: dmi.product.family: Latitude dmi.product.name: Latitude 5480 dmi.product.sku: 07A7 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (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 alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2062982 Title: [USB-Audio - SB Live! 24-bit External, playback] volume slider and mute button have no effect Status in alsa-driver package in Ubuntu: New Bug description: When the external sound card (SB Live! 24 bit) is used, the volume slider and the mute button have no effect. The volume is low. I tried two SB Live! 24 bit cards (at home and at work). The behaviour is the same. On Lubuntu 20.04, there was no problem. The embedded sound card operates normally and reacts on the volume slider. Ubuntu 22.04.4 LTS pulseaudio 1:15.99.1+dfsg1-1ubuntu2.2 pavucontrol 5.0-2 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 Uname: Linux 6.8.7-2-liquorix-amd64 x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Sat Apr 20 21:33:26 2024 InstallationDate: Installed on 2024-04-03 (16 days ago) InstallationMedia: Lubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240216) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: SoundBlaster Live! 24-bit External SB0490 - SB Live! 24-bit External Symptom_PulseAudioLog: кві 20 19:57:33 Lattitude dbus-daemon[590]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.33' (uid=1001 pid=845 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo") Symptom_Type: Volume slider, or mixer problems Title: [USB-Audio - SB Live! 24-bit External, playback] volume slider problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2023 dmi.bios.release: 1.32 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.32.2 dmi.board.name: 015DR5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.asset.tag: NTB71181 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.32.2:bd09/22/2023:br1.32:svnDellInc.:pnLatitude5480:pvr:rvnDellInc.:rn015DR5:rvrA00:cvnDellInc.:ct10:cvr:sku07A7: dmi.product.family: Latitude dmi.product.name: Latitude 5480 dmi.product.sku: 07A7 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2062982/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2062979] Re: unable to create ubuntu-noble image due to dictionaries-common config failure
** Description changed: + this is running with LC_ALL=C + + the following are output in terminal when configuring dictionaries- + common + Setting up dictionaries-common (1.29.7) ... Processing triggers for dictionaries-common (1.29.7) ... aspell-autobuildhash: processing: en [en-common]. Error: /dev/null:1: The key "/usr/bin/aspell" is unknown. Undefined subroutine ::subst called at /usr/sbin/aspell-autobuildhash line 54. dpkg: error processing package dictionaries-common (--configure): - installed dictionaries-common package post-installation script subprocess returned error exit status 2 + installed dictionaries-common package post-installation script subprocess returned error exit status 2 Errors were encountered while processing: - dictionaries-common + dictionaries-common + + this worked without issues when I last built images of ubuntu-noble in + late February 2024 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to aspell in Ubuntu. https://bugs.launchpad.net/bugs/2062979 Title: unable to create ubuntu-noble image due to dictionaries-common config failure Status in aspell package in Ubuntu: New Status in dictionaries-common package in Ubuntu: New Bug description: this is running with LC_ALL=C the following are output in terminal when configuring dictionaries- common Setting up dictionaries-common (1.29.7) ... Processing triggers for dictionaries-common (1.29.7) ... aspell-autobuildhash: processing: en [en-common]. Error: /dev/null:1: The key "/usr/bin/aspell" is unknown. Undefined subroutine ::subst called at /usr/sbin/aspell-autobuildhash line 54. dpkg: error processing package dictionaries-common (--configure): installed dictionaries-common package post-installation script subprocess returned error exit status 2 Errors were encountered while processing: dictionaries-common this worked without issues when I last built images of ubuntu-noble in late February 2024 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aspell/+bug/2062979/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2062979] [NEW] unable to create ubuntu-noble image due to dictionaries-common config failure
Public bug reported: Setting up dictionaries-common (1.29.7) ... Processing triggers for dictionaries-common (1.29.7) ... aspell-autobuildhash: processing: en [en-common]. Error: /dev/null:1: The key "/usr/bin/aspell" is unknown. Undefined subroutine ::subst called at /usr/sbin/aspell-autobuildhash line 54. dpkg: error processing package dictionaries-common (--configure): installed dictionaries-common package post-installation script subprocess returned error exit status 2 Errors were encountered while processing: dictionaries-common ** Affects: aspell (Ubuntu) Importance: Undecided Status: New ** Affects: dictionaries-common (Ubuntu) Importance: Undecided Status: New ** Also affects: aspell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to aspell in Ubuntu. https://bugs.launchpad.net/bugs/2062979 Title: unable to create ubuntu-noble image due to dictionaries-common config failure Status in aspell package in Ubuntu: New Status in dictionaries-common package in Ubuntu: New Bug description: Setting up dictionaries-common (1.29.7) ... Processing triggers for dictionaries-common (1.29.7) ... aspell-autobuildhash: processing: en [en-common]. Error: /dev/null:1: The key "/usr/bin/aspell" is unknown. Undefined subroutine ::subst called at /usr/sbin/aspell-autobuildhash line 54. dpkg: error processing package dictionaries-common (--configure): installed dictionaries-common package post-installation script subprocess returned error exit status 2 Errors were encountered while processing: dictionaries-common To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aspell/+bug/2062979/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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]
Unfortunately, my sound finally did fail again... But the symptoms seem different. Audacious just hangs for a while before ultimately giving up (and it stops hanging and stops trying to play). But this is a new type of failure so perhaps this patch did make a bit of a difference? https://bugzilla.kernel.org/show_bug.cgi?id=208555#c863 But this happened immediately after resuming from suspend. My laptop went to sleep with mute enabled, I started playing sound after resuming, noticed I was muted, and resumed... And sound was no longer working. Could bec7760a6c5fa59593dac264fa0c628e46815986 be the issue? This did not fixed my count: amixer -c 0 cset numid=3,name='Speaker Force Firmware Load' 1 (-c 1 is incorrect for my laptop.) -- 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 2016013] Re: New windows (like gnome-initial-setup) don't get centered if Desktop Icons NG is loaded
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/2016013 ** Tags added: iso-testing -- 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/2016013 Title: New windows (like gnome-initial-setup) don't get centered if Desktop Icons NG is loaded Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Bug description: New windows don't get centered if Desktop Icons NG is loaded. With vanilla GNOME, if an app window is too large for tiling (larger than a quarter of the screen) then it will be centered by default. But this doesn't happen when DING is loaded, probably because DING is incorrectly treated as an app window. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/+bug/2016013/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2016013] Re: New windows (like gnome-initial-setup) don't get centered if Desktop Icons NG is loaded
** Summary changed: - New windows don't get centered if Desktop Icons NG is loaded + New windows (like gnome-initial-setup) don't get centered if Desktop Icons NG is loaded -- 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/2016013 Title: New windows (like gnome-initial-setup) don't get centered if Desktop Icons NG is loaded Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Bug description: New windows don't get centered if Desktop Icons NG is loaded. With vanilla GNOME, if an app window is too large for tiling (larger than a quarter of the screen) then it will be centered by default. But this doesn't happen when DING is loaded, probably because DING is incorrectly treated as an app window. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/+bug/2016013/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2062971] [NEW] Enable Ubuntu Pro page formatting is hard to follow
Public bug reported: The Enable Ubuntu Pro page formatting is hard to follow and feels a little un-pro. There are two columns at the top, and then only one. ** Affects: gnome-initial-setup (Ubuntu) Importance: Medium Status: New ** Tags: noble visual-quality ** Attachment added: "Screenshot from 2024-04-20 22-20-44.png" https://bugs.launchpad.net/bugs/2062971/+attachment/5768528/+files/Screenshot%20from%202024-04-20%2022-20-44.png ** Changed in: gnome-initial-setup (Ubuntu) Milestone: None => ubuntu-24.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-initial-setup in Ubuntu. https://bugs.launchpad.net/bugs/2062971 Title: Enable Ubuntu Pro page formatting is hard to follow Status in gnome-initial-setup package in Ubuntu: New Bug description: The Enable Ubuntu Pro page formatting is hard to follow and feels a little un-pro. There are two columns at the top, and then only one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/2062971/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2062177] Re: Remmina crashes after RDP connection
For me it seems to crash at the same point.
[15:46:32:936] [295376:00048252] [FATAL][com.freerdp.winpr.assert] -
[winpr_log_backtrace_ex]: 8: unresolvable, address=(nil)
[1]295376 IOT instruction (core dumped) remmina
This is from a connection to a Windows 10 machine that is up and running and
the same connection used to work before I upgraded from Ubuntu 23.10 to 24:04.
remmina version: org.remmina.Remmina - 1.4.35 (git n/a)
I attached the core dump.
** Attachment added: "core.zip"
https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/2062177/+attachment/5768527/+files/core.zip
--
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/2062177
Title:
Remmina crashes after RDP connection
Status in remmina package in Ubuntu:
Confirmed
Bug description:
When connecting with RDP Remmina crashes. Syslog show the following:
2024-04-18T13:49:02.969819+02:00 localhost dbus-daemon[3214]: [session
uid=1001 pid=3214] Successfully activated service
'org.gnome.seahorse.Application'
2024-04-18T13:49:03.655883+02:00 localhost systemd[3176]: Started
app-gnome-org.remmina.Remmina-53436.scope - Application launched by gnome-shell.
2024-04-18T13:49:03.656884+02:00 localhost remmina[53441]: Remmina does not
log all output statements. Turn on more verbose output by using
"G_MESSAGES_DEBUG=remmina" as an environment variable.#012More info available
on the Remmina wiki
at:#012https://gitlab.com/Remmina/Remmina/-/wikis/Usage/Remmina-debugging
2024-04-18T13:49:03.766401+02:00 localhost remmina[53441]:
gtk_menu_attach_to_widget(): menu already attached to GtkMenuItem
2024-04-18T13:49:13.851397+02:00 localhost
org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116]
[ERROR][com.freerdp.common.settings] - [freerdp_settings_get_bool]: Invalid key
index 0 [FreeRDP_instance|FREERDP_SETTINGS_TYPE_POINTER]
2024-04-18T13:49:13.851716+02:00 localhost
org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116]
[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:637]
2024-04-18T13:49:13.851760+02:00 localhost
org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116]
[FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 0:
dli_fname=/lib/x86_64-linux-gnu/libwinpr3.so.3 [0x70e694e2b000],
dli_sname=winpr_backtrace [0x70e694e97660]
2024-04-18T13:49:13.851791+02:00 localhost
org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116]
[FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 1:
dli_fname=/lib/x86_64-linux-gnu/libwinpr3.so.3 [0x70e694e2b000],
dli_sname=winpr_log_backtrace_ex [0x70e694e9f150]
2024-04-18T13:49:13.851803+02:00 localhost
org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116]
[FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 2:
dli_fname=/lib/x86_64-linux-gnu/libfreerdp3.so.3 [0x70e69420],
dli_sname=(null) [(nil)]
2024-04-18T13:49:13.851815+02:00 localhost
org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116]
[FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 3:
dli_fname=/lib/x86_64-linux-gnu/libfreerdp3.so.3 [0x70e69420],
dli_sname=freerdp_settings_get_bool [0x70e6942658a0]
2024-04-18T13:49:13.851827+02:00 localhost
org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116]
[FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 4:
dli_fname=/usr/lib/x86_64-linux-gnu/remmina/plugins/remmina-plugin-rdp.so
[0x70e6958dd000], dli_sname=(null) [(nil)]
2024-04-18T13:49:13.851839+02:00 localhost
org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116]
[FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 5:
dli_fname=/usr/lib/x86_64-linux-gnu/remmina/plugins/remmina-plugin-rdp.so
[0x70e6958dd000], dli_sname=(null) [(nil)]
2024-04-18T13:49:13.851851+02:00 localhost
org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116]
[FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 6:
dli_fname=/usr/bin/../lib/x86_64-linux-gnu/libc.so.6 [0x70e69940],
dli_sname=(null) [(nil)]
2024-04-18T13:49:13.851873+02:00 localhost
org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116]
[FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 7:
dli_fname=/usr/bin/../lib/x86_64-linux-gnu/libc.so.6 [0x70e69940],
dli_sname=(null) [(nil)]
2024-04-18T13:49:13.851885+02:00 localhost
org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116]
[FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 8: unresolvable,
address=(nil)
2024-04-18T13:49:14.938231+02:00 localhost
org.remmina.Remmina.desktop[53436]: /usr/bin/remmina-file-wrapper: line 37:
53441 Aborted (core dumped) "$REMMINA" "${@}"
ProblemType: Bug
DistroRelease:
[Desktop-packages] [Bug 2062967] [NEW] ubuntu-drivers no longer offers nvidia 550 drivers
Public bug reported: While I am unclear which package update impacted the video drivers detected by ubuntu-drivers, the nvidia 545 and nvidia 550 video drivers are no longer shown as an option on NVIDIA GeForce GTX 1050 video card. I can understand the removal of the nvidia 545 drivers as the current kernel's linux-signatures-nvidia-6.8.0-28-generic package lacks signatures for the nvidia 545 kernel modules for secure boot but the nvidia 550 kernel modules signatures are available. So while it would be acceptable to downgrade the 'tested' default nvidia driver to 535, ubuntu-drivers and Additional Drivers should be offering the nvidia 550 drivers as an untested option. ** Affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/2062967 Title: ubuntu-drivers no longer offers nvidia 550 drivers Status in ubuntu-drivers-common package in Ubuntu: New Bug description: While I am unclear which package update impacted the video drivers detected by ubuntu-drivers, the nvidia 545 and nvidia 550 video drivers are no longer shown as an option on NVIDIA GeForce GTX 1050 video card. I can understand the removal of the nvidia 545 drivers as the current kernel's linux-signatures-nvidia-6.8.0-28-generic package lacks signatures for the nvidia 545 kernel modules for secure boot but the nvidia 550 kernel modules signatures are available. So while it would be acceptable to downgrade the 'tested' default nvidia driver to 535, ubuntu-drivers and Additional Drivers should be offering the nvidia 550 drivers as an untested option. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2062967/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2062406] Re: CVE-2024-32462: Sandbox escape via RequestBackground portal and CWE-88
I'm not working on the stable security updates now but I opened tasks for them in case someone else wants to contribute. ** Also affects: flatpak (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: flatpak (Ubuntu Mantic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flatpak in Ubuntu. https://bugs.launchpad.net/bugs/2062406 Title: CVE-2024-32462: Sandbox escape via RequestBackground portal and CWE-88 Status in flatpak package in Ubuntu: Fix Released Status in flatpak source package in Jammy: New Status in flatpak source package in Mantic: New Bug description: Upstream advisory: https://github.com/flatpak/flatpak/security/advisories/GHSA- phv6-cpc2-2fgj If possible please sync 1.14.6-1 from Debian instead of backporting fixes. That version only fixes the security issue and one other high- visibility bug (app developer names showing in the CLI as though they were the app's name). https://github.com/flatpak/flatpak/compare/1.14.5...1.14.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/2062406/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2060391] Re: gnome desktop cannot start as mutter fails to find drmModeCloseFB
Ok solved it, the issue was the optional and driver, it had installed libraries in /opt and ld was preferring them.. Removed the ld.conf entries and rebooted. All is good now. `ld /usr/bin/mutter | grep drm` Gave me the hint. -- 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/2060391 Title: gnome desktop cannot start as mutter fails to find drmModeCloseFB Status in mutter package in Ubuntu: Confirmed Bug description: mutter: symbol lookup error: /lib/x86_64-linux-gnu/libmutter-14.so.0: undefined symbol: drmModeCloseFB Package libdrm2: i 2.4.120-2 noble 500 Package libdrm2:i386: i 2.4.120-2 noble 500 Package libmutter-14-0: i 46.0-1ubuntu6 noble 500 Package mutter: i 46.0-1ubuntu6 noble 500 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2060391/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2060391] Re: gnome desktop cannot start as mutter fails to find drmModeCloseFB
Same here, stuck on upgraded system... -- 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/2060391 Title: gnome desktop cannot start as mutter fails to find drmModeCloseFB Status in mutter package in Ubuntu: Confirmed Bug description: mutter: symbol lookup error: /lib/x86_64-linux-gnu/libmutter-14.so.0: undefined symbol: drmModeCloseFB Package libdrm2: i 2.4.120-2 noble 500 Package libdrm2:i386: i 2.4.120-2 noble 500 Package libmutter-14-0: i 46.0-1ubuntu6 noble 500 Package mutter: i 46.0-1ubuntu6 noble 500 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2060391/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2062956] [NEW] CVE-2024-32462 - Need to update to the last secure patch
*** This bug is a security vulnerability *** Public security bug reported: Hello, There is a security issue in flatpack package, see: https://www.cve.org/CVERecord?id=CVE-2024-32462 To fix that, according to Ubuntu version we have to update the package to one of these versions: 1.10.9, 1.12.9, 1.14.6, and 1.15.8, Here is the current statut: Noble = OK Mantic = update required Jammy = update required Focal = update required Could you please check that and provide the patched version? Thanks in advance. ** Affects: flatpak (Ubuntu) Importance: Undecided Status: New ** Description changed: Hello, There is a security issue in flatpack package, see: https://www.cve.org/CVERecord?id=CVE-2024-32462 To fix that, according to Ubuntu version we have to update the package to one of these versions: 1.10.9, 1.12.9, 1.14.6, and 1.15.8, Here is the current statut: Noble = OK Mantic = update required - Jammy = update required + Jammy = update required Focal = update required Could you please check that and provide the patched version? Thanks in advance. ** Information type changed from Public to Public Security ** Information type changed from Public Security to Private Security ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flatpak in Ubuntu. https://bugs.launchpad.net/bugs/2062956 Title: CVE-2024-32462 - Need to update to the last secure patch Status in flatpak package in Ubuntu: New Bug description: Hello, There is a security issue in flatpack package, see: https://www.cve.org/CVERecord?id=CVE-2024-32462 To fix that, according to Ubuntu version we have to update the package to one of these versions: 1.10.9, 1.12.9, 1.14.6, and 1.15.8, Here is the current statut: Noble = OK Mantic = update required Jammy = update required Focal = update required Could you please check that and provide the patched version? Thanks in advance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/2062956/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2036817]
*** Bug 157855 has been marked as a duplicate of this bug. *** -- 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/2036817 Title: soffice.bin crashed with SIGSEGV in com::sun::star::uno::Reference::operator->() Status in LibreOffice: Fix Released Status in libreoffice package in Ubuntu: Fix Released Bug description: Occurred when exiting Calc/ ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: libreoffice-core 4:7.6.1~rc2-0ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 20 13:44:57 2023 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2023-09-17 (4 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230908.2) ProcAttrCurrent: libreoffice-soffice (complain) ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --calc file:///home/username/Documents/Comic%20Book%20Collection.ods --splash-pipe=5 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0x7f4aee4abf8e:mov(%rax,%rbp,1),%rdi PC (0x7f4aee4abf8e) ok source "(%rax,%rbp,1)" (0x558d207ac2b2) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: libreoffice StacktraceTop: ?? () from /usr/lib/libreoffice/program/libmergedlo.so comphelper::AccessibleEventNotifier::revokeClientNotifyDisposing(unsigned int, com::sun::star::uno::Reference const&) () from /usr/lib/libreoffice/program/libmergedlo.so comphelper::OAccessibleContextWrapper::disposing() () from /usr/lib/libreoffice/program/libmergedlo.so cppu::WeakComponentImplHelperBase::dispose() () from /usr/lib/libreoffice/program/libuno_cppuhelpergcc3.so.3 cppu::WeakComponentImplHelperBase::release() () from /usr/lib/libreoffice/program/libuno_cppuhelpergcc3.so.3 Title: soffice.bin crashed with SIGSEGV in comphelper::AccessibleEventNotifier::revokeClientNotifyDisposing() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/2036817/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
