[Desktop-packages] [Bug 2036761] Re: [mantic] ppa-purge no longer purges what add-apt-repository adds
This bug was fixed in the package ppa-purge - 0.2.8+bzr63-0ubuntu1.23.10.1 --- ppa-purge (0.2.8+bzr63-0ubuntu1.23.10.1) mantic; urgency=medium * Add support for deb822 source format. (LP: #2036761) -- Ghadi Elie Rahme Tue, 19 Mar 2024 14:58:45 + ** Changed in: ppa-purge (Ubuntu Mantic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2036761 Title: [mantic] ppa-purge no longer purges what add-apt-repository adds Status in ppa-purge package in Ubuntu: Fix Released Status in software-properties package in Ubuntu: Invalid Status in ppa-purge source package in Mantic: Fix Released Status in software-properties source package in Mantic: Invalid Status in ppa-purge source package in Noble: Fix Released Status in software-properties source package in Noble: Invalid Bug description: Thank you @jbicha for the original bug report! [ Impact ] Currently ppa-purge fails to purge packages on distribution using the deb822 source format. Currently mantic and noble make use of this format and are affected by this issue. When running ppa-purge to remove a custom PPA, ppa-purge fails to disable the custom PPA since it cannot disable deb822 sources and leads to apt still querying the ppa when running: $ apt update In older versions of ubuntu, PPAs used the ".list" format which could be disabled by simply commenting out the "deb" line with a "#". This was the method that ppa-purge used to disable PPAs. This new patch allows ppa-purge to detect and disable deb822 source files by adding an "Enabled: no" field in each component section of the deb822 file. It also removes any line that starts with "Enabled:" to make sure the resulting file is clean. [ Test Plan ] The changes were tested on both mantic and noble in a lxc container using the oibaf mesa PPA (https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers) as the test PPA. The following steps were recorded in a noble lxc container. - First make sure that mesa-utils is installed in your environment: $ sudo apt update && sudo apt install mesa-utils - Add the oibaf PPA to your system using the following command: $ sudo add-apt-repository ppa:oibaf/graphics-drivers - Make sure that the mesa-utils packages were upgraded after adding the PPA: $ sudo apt update && sudo apt upgrade $ dpkg - l | grep mesa - output should be similar to the following: ii libegl-mesa0:amd64 24.1~git2402280600.41722c~oibaf~n amd64free implementation of the EGL API -- Mesa vendor library ii libgl1-mesa-dri:amd64 24.1~git2402280600.41722c~oibaf~n amd64free implementation of the OpenGL API -- DRI modules ii libglapi-mesa:amd64 24.1~git2402280600.41722c~oibaf~n amd64free implementation of the GL API -- shared library ii libglx-mesa0:amd64 24.1~git2402280600.41722c~oibaf~n amd64free implementation of the OpenGL API -- GLX vendor library ii mesa-utils 9.0.0-2 amd64Miscellaneous Mesa utilities -- symlinks ii mesa-utils-bin:amd649.0.0-2 amd64Miscellaneous Mesa utilities -- native applications ii mesa-vulkan-drivers:amd64 24.1~git2402280600.41722c~oibaf~n amd64Mesa Vulkan graphics drivers - Install and run ppa-purge: $ sudo apt install ppa-purge $ sudo ppa-purge ppa:oibaf/graphics-drivers - ppa-purge will report at the end that none of the oibaf packages need to be downgraded/removed: libglapi-mesa is already the newest version (24.1~git2402280600.41722c~oibaf~n). libglapi-mesa set to manually installed. libglx-mesa0 is already the newest version (24.1~git2402280600.41722c~oibaf~n). libglx-mesa0 set to manually installed. mesa-vulkan-drivers is already the newest version (24.1~git2402280600.41722c~oibaf~n). mesa-vulkan-drivers set to manually installed. Selected version '2.4.120+git2402271331.1b4e04~oibaf~n' (Updated Open Graphics Drivers - since 2011!:24.04/noble [amd64]) for 'libdrm-amdgpu1' Selected version '2.4.120+git2402271331.1b4e04~oibaf~n' (Updated Open Graphics Drivers - since 2011!:24.04/noble [all]) for 'libdrm-common' Selected version '2.4.120+git2402271331.1b4e04~oibaf~n' (Updated Open Graphics Drivers - since 2011!:24.04/noble [amd64]) for 'libdrm-intel1' Selected version '2.4.120+git2402271331.1b4e04~oibaf~n' (Updated Open Graphics Drivers - since 2011!:24.04/noble [amd64]) for 'libdrm-nouveau2' Selected version '2.4.120+git2402271331.1b4e04~oibaf~n' (Updated Open Graphics Drivers - since 2011!:24.04/noble
[Desktop-packages] [Bug 2064320] Re: unable to import a wireguard config from non-short filenames
** Changed in: gnome-control-center Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2064320 Title: unable to import a wireguard config from non-short filenames Status in gnome-control-center: New Status in gnome-control-center package in Ubuntu: Triaged Bug description: In Ubuntu 24.04 LTS fresh install. I am unable to import a Wireguard .conf configuration file from the gnome-control-center's Network panel. Parameters -> Network -> VPN -> + -> Import from file Select the .conf file that was sent by my VPN provider, then click Open Results in the following error (French) : Impossible d'importer la connexion VPN. Le fichier AirVPN_Canada_UDP-1637-Entry3.conf" est illisible ou ne contient pas d'informations de connexion VPN reconnues. Erreur: le greffon ne prend pas en charge la fonction d'importation. Fermer Which roughly translates to : Unable to import VPN connection. The AirVPN_Canada_UDP-1637-Entry3.conf" file is unreadable or does not contain recognized VPN connection information. Error: The plugin does not support the import function. Close ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-control-center 1:46.0.1-1ubuntu7 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 30 13:52:58 2024 InstallationDate: Installed on 2024-04-25 (5 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/2064320/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2063333] Re: gnome-remote-desktop.service: Failed to determine user credentials: No such process
That command did create some users Restarting gnome remote desktop now gives me ░░ Subject: A start job for unit gnome-remote-desktop.service has begun execution ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A start job for unit gnome-remote-desktop.service has begun execution. ░░ ░░ The job identifier is 52156. May 02 14:27:47 localhost gnome-remote-de[36906]: Init TPM credentials failed because No TPM device found, using GKeyFile as fallback May 02 14:27:47 localhost gnome-remote-de[36906]: Init file credentials failed: Error creating directory /var/lib/gnome-remote-desktop: Permission denied May 02 14:27:47 localhost gnome-remote-desktop-daemon[36906]: ** May 02 14:27:47 localhost gnome-remote-desktop-daemon[36906]: ERROR:../src/grd-settings.c:345:grd_settings_constructed: assertion failed: (priv->credentials) May 02 14:27:47 localhost gnome-remote-desktop-daemon[36906]: Bail out! ERROR:../src/grd-settings.c:345:grd_settings_constructed: assertion failed: (priv->credentials) May 02 14:27:47 localhost systemd[1]: gnome-remote-desktop.service: Main process exited, code=dumped, status=6/ABRT ░░ Subject: Unit process exited ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ An ExecStart= process belonging to unit gnome-remote-desktop.service has exited. ░░ ░░ The process' exit code is 'dumped' and its exit status is 6. Running: /usr/libexec/gnome-remote-desktop-daemon --system ** (gnome-remote-desktop-daemon:36919): WARNING **: 14:30:22.681: Init TPM credentials failed because No TPM device found, using GKeyFile as fallback Failed to register: Unable to acquire bus name 'org.gnome.RemoteDesktop' -- 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/206 Title: gnome-remote-desktop.service: Failed to determine user credentials: No such process Status in gnome-remote-desktop package in Ubuntu: Triaged Status in gnome-remote-desktop package in Debian: Unknown Bug description: On a RISC-V Ubuntu 24.04 I installed ubuntu-desktop. The desktop does not show up though gdm3 is running. I see the following error messages which might indicate a dependency issue: pr 24 12:29:35 unmatched systemd[1]: Starting gnome-remote-desktop.service - GNOME Remote Desktop... Apr 24 12:29:35 unmatched (p-daemon)[1752]: gnome-remote-desktop.service: Failed to determine user credentials: No such process Apr 24 12:29:35 unmatched systemd[1]: gnome-remote-desktop.service: Main process exited, code=exited, status=217/USER Apr 24 12:29:35 unmatched systemd[1]: gnome-remote-desktop.service: Failed with result 'exit-code'. Apr 24 12:29:35 unmatched systemd[1]: Failed to start gnome-remote-desktop.service - GNOME Remote Desktop. Apr 24 12:29:35 unmatched systemd[1]: gnome-remote-desktop.service: Scheduled restart job, restart counter is at 1. Apr 24 12:29:35 unmatched systemd[1]: Starting gnome-remote-desktop.service - GNOME Remote Desktop... Apr 24 12:29:35 unmatched (p-daemon)[1753]: gnome-remote-desktop.service: Failed to determine user credentials: No such process Apr 24 12:29:35 unmatched systemd[1]: gnome-remote-desktop.service: Main process exited, code=exited, status=217/USER Apr 24 12:29:35 unmatched systemd[1]: gnome-remote-desktop.service: Failed with result 'exit-code'. Apr 24 12:29:35 unmatched systemd[1]: Failed to start gnome-remote-desktop.service - GNOME Remote Desktop. Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Scheduled restart job, restart counter is at 2. Apr 24 12:29:36 unmatched systemd[1]: Starting gnome-remote-desktop.service - GNOME Remote Desktop... Apr 24 12:29:36 unmatched (p-daemon)[1754]: gnome-remote-desktop.service: Failed to determine user credentials: No such process Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Main process exited, code=exited, status=217/USER Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Failed with result 'exit-code'. Apr 24 12:29:36 unmatched systemd[1]: Failed to start gnome-remote-desktop.service - GNOME Remote Desktop. Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Scheduled restart job, restart counter is at 3. Apr 24 12:29:36 unmatched systemd[1]: Starting gnome-remote-desktop.service - GNOME Remote Desktop... Apr 24 12:29:36 unmatched (p-daemon)[1755]: gnome-remote-desktop.service: Failed to determine user credentials: No such process Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Main process exited, code=exited, status=217/USER Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Failed with result 'exit-code'. Apr 24 12:29:36 unmatched systemd[1]: Failed to start gnome-remote-desktop.service - GNOME Remote Desktop. Apr 24 12:29:36 unmatched systemd[1]:
[Desktop-packages] [Bug 2064096] Re: Services fail to start in noble deployed with TPM+FDE
> /usr/lib/systemd/systemd --switched-root --system --deserialize=40 splash Ok, --switched-root is there in PID 1, it's something I was looking to confirm. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2064096 Title: Services fail to start in noble deployed with TPM+FDE Status in apparmor package in Ubuntu: New Status in cups package in Ubuntu: Confirmed Status in rsyslog package in Ubuntu: Confirmed Status in sssd package in Ubuntu: Confirmed Bug description: What's known so far: - 24.04 desktop deployed with TPM+FDE shows this bug - services confined with apparmor that need to access something in /run/systemd (like the notify socket) fail to do so, even if the apparmor profile is in complain mode. And the apparmor profile does already have rules to allow that access - only after running aa-disable can the service start fine - paths logged by the apparmor DENIED or ALLOWED messages are missing the "/run" prefix from "/run/systemd/..". - When we add rules to the profile using "/systemd/" (i.e., also dropping the /run prefix), then it works - other access in /run/systemd/ are also blocked, but the most noticeable one is the notify mechanism - comment #2 also states that azure CVM images are also impacted - comment #4 has instructions on how to create such a VM locally with LXD vms Original description follows: This might be related to #2064088 The rsyslog service is continually timing out and restarting. If I use a service drop-in file and change the 'Type' from 'notify' to 'simple', the service starts and appears to work normally. In the journal, I can see the attached apparmor errors. I can't make sense of them, but if it's a similar issue to #2064088, then I suspect apparmor is preventing the systemd notify function from alerting systemd that the service is up and running. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: rsyslog 8.2312.0-3ubuntu9 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Mon Apr 29 10:37:46 2024 ProcEnviron: LANG=en_GB.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: rsyslog UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2064096/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2059756] Re: [SRU] adsys 0.14.1
OK, thanks. I guess we can review the Jammy upload for now then on the assumption that the Mantic upload won't have substantial changes until it arrives in the queue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/2059756 Title: [SRU] adsys 0.14.1 Status in adsys package in Ubuntu: Fix Released Status in golang-1.22 package in Ubuntu: Fix Released Status in adsys source package in Jammy: Confirmed Status in golang-1.22 source package in Jammy: Confirmed Status in adsys source package in Mantic: Confirmed Status in golang-1.22 source package in Mantic: Confirmed Bug description: [context] ADSys is a tool designed for administering and implementing Group Policy Objects (GPOs) from Active Directory on Linux systems. It includes a suite of services and commands that empower administrators to efficiently manage policy updates and maintain compliance with organizational business rules. Given that ADSys directly interfaces with Active Directory and needs to align with new business requirements in LTS releases, it has been essential to keep the package consistently updated with the latest changes of ADSys upstream source. As ADSys is a key component of our commercial offerings, our customers anticipate the availability of recently implemented features in the 22.04 release. Now that ADSys has a complete set of features, the request is to proceed with a one-off release of ADSys 0.14.1 to 22.04. Please note that any new features introduced in subsequent versions will be exclusively available in 24.04 and later releases. This version includes a comprehensive end to end automated test suite that runs ADSys against a real Active directory environment. Version 0.14.1 is available for 22.04 in a PPA (https://launchpad.net/~ubuntu-enterprise- desktop/+archive/ubuntu/adsys) and already used in production by customers. At this time of writing the number of open issues is 1 in Launchpad and 16 in GitHub including 6 enhancements. None of them have a high or critical importance. [references] LP: https://launchpad.net/ubuntu/+source/adsys LP Bugs: https://bugs.launchpad.net/ubuntu/+source/adsys GitHub: https://github.com/ubuntu/adsys/ GH Bugs: https://github.com/ubuntu/adsys/issues Documentation: https://canonical-adsys.readthedocs-hosted.com/en/stable/ Initial SRU discussion: https://lists.ubuntu.com/archives/ubuntu-release/2023-June/005650.html [changes] Full LP Changelog: https://launchpad.net/ubuntu/+source/adsys/+changelog * New features * New policies: - Add mount / network shares policy manager - Add AppArmor policy manager - Support multiple AD backends and implement Winbind support - Add system proxy policy manager - Add certificate policy manager for machines - Add adsysctl policy purge command to purge applied policies - Full documentation - Full end to end automated test suite. * Enhancements * Add a --machine / -m flag to adsysctl applied, indicating the policies applied to the current machine * Expose Ubuntu Pro status in the "status" command * Update scripts manager creation * List Pro policy types in service status output * Warn when Pro-only rules are configured * Use systemd via D-Bus instead of systemctl commands * Add placeholder notes for entry types * Rework Kerberos ticket handling logic to satisfy the Heimdal implementation of Kerberos * Rework policy application sync strategy * Print logs when policies are up to date * Update policy definitions to include dconf key for dark mode background * Infer user KRB5CCNAME path via the libkrb5 API (LP: #2049061) * Allow sssd backend to work without ad_domain being set (LP: #2054445) * Update apport hook to include journal errors and package logs * Bug fixes * Fix policy update failing when GPT.INI contains no version key * Fix object lookup for users having a FQDN as their hostname * Support special characters in domains when parsing sssd configuration * Fix DCONF_PROFILE not considering default_domain_suffix on sssd.conf * Ensure empty state for dconf policy * Handle case mismatches in GPT.INI file name * Ensure GPO URLs contain the FQDN of the domain controller * Add runtime dependency on nfs-common * Other * Updates to latest versions of Go (fixing known Go vulnerabilities) * Updates to latest versions of the Go dependencies * Updates and improvements to CI and QoL * Migrate translation support to native approach using go-i18n + gotext and switch to upstream gotext version Dependencies: * Build-dep: golang-go (>= 2:1.22~) * Dependencies to backport to 22.04: * golang-go >= 2:1.22 * ubuntu-proxy-manager (suggest. Required for Proxy support - feature will be disabled
[Desktop-packages] [Bug 2063333] Re: gnome-remote-desktop.service: Failed to determine user credentials: No such process
Nothing really reported from running the above command /usr/libexec/gnome-remote-desktop-daemon --system ** (gnome-remote-desktop-daemon:36048): WARNING **: 11:01:25.879: Init TPM credentials failed because No TPM device found, using GKeyFile as fallback But no ports are open netstat -tnlp Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp0 0 127.0.0.1:631 0.0.0.0:* LISTEN 29997/cupsd tcp0 0 127.0.0.54:53 0.0.0.0:* LISTEN 16105/systemd-resol tcp0 0 127.0.0.53:53 0.0.0.0:* LISTEN 16105/systemd-resol tcp6 0 0 ::1:631 :::*LISTEN 29997/cupsd tcp6 0 0 :::22 :::*LISTEN 1/systemd I restarted GDM3 ps -aux | grep gnome gdm35757 0.0 0.6 233060 6144 tty1 Ssl+ 11:01 0:00 /usr/libexec/gdm-wayland-session dbus-run-session -- gnome-session --autostart /usr/share/gdm/greeter/autostart gdm35761 0.0 0.2 6500 2432 tty1 S+ 11:01 0:00 dbus-run-session -- gnome-session --autostart /usr/share/gdm/greeter/autostart gdm35763 0.0 1.8 518252 18304 tty1 Sl+ 11:01 0:00 /usr/libexec/gnome-session-binary --autostart /usr/share/gdm/greeter/autostart gdm35772 1.0 22.0 3251940 217456 tty1 Sl+ 11:01 0:01 /usr/bin/gnome-shell gdm35799 0.0 0.7 236060 7552 tty1 Sl+ 11:01 0:00 /usr/libexec/at-spi2-registryd --use-gnome-session gdm35822 0.0 2.7 2590472 26852 tty1Sl+ 11:01 0:00 /usr/bin/gjs -m /usr/share/gnome-shell/org.gnome.Shell.Notifications gdm36027 0.0 2.7 2590464 26860 tty1Sl+ 11:01 0:00 /usr/bin/gjs -m /usr/share/gnome-shell/org.gnome.ScreenSaver root 36090 0.0 1.7 439656 16896 ttyS0Sl+ 11:02 0:00 /usr/libexec/gnome-remote-desktop-daemon --system -- 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/206 Title: gnome-remote-desktop.service: Failed to determine user credentials: No such process Status in gnome-remote-desktop package in Ubuntu: Confirmed Bug description: On a RISC-V Ubuntu 24.04 I installed ubuntu-desktop. The desktop does not show up though gdm3 is running. I see the following error messages which might indicate a dependency issue: pr 24 12:29:35 unmatched systemd[1]: Starting gnome-remote-desktop.service - GNOME Remote Desktop... Apr 24 12:29:35 unmatched (p-daemon)[1752]: gnome-remote-desktop.service: Failed to determine user credentials: No such process Apr 24 12:29:35 unmatched systemd[1]: gnome-remote-desktop.service: Main process exited, code=exited, status=217/USER Apr 24 12:29:35 unmatched systemd[1]: gnome-remote-desktop.service: Failed with result 'exit-code'. Apr 24 12:29:35 unmatched systemd[1]: Failed to start gnome-remote-desktop.service - GNOME Remote Desktop. Apr 24 12:29:35 unmatched systemd[1]: gnome-remote-desktop.service: Scheduled restart job, restart counter is at 1. Apr 24 12:29:35 unmatched systemd[1]: Starting gnome-remote-desktop.service - GNOME Remote Desktop... Apr 24 12:29:35 unmatched (p-daemon)[1753]: gnome-remote-desktop.service: Failed to determine user credentials: No such process Apr 24 12:29:35 unmatched systemd[1]: gnome-remote-desktop.service: Main process exited, code=exited, status=217/USER Apr 24 12:29:35 unmatched systemd[1]: gnome-remote-desktop.service: Failed with result 'exit-code'. Apr 24 12:29:35 unmatched systemd[1]: Failed to start gnome-remote-desktop.service - GNOME Remote Desktop. Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Scheduled restart job, restart counter is at 2. Apr 24 12:29:36 unmatched systemd[1]: Starting gnome-remote-desktop.service - GNOME Remote Desktop... Apr 24 12:29:36 unmatched (p-daemon)[1754]: gnome-remote-desktop.service: Failed to determine user credentials: No such process Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Main process exited, code=exited, status=217/USER Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Failed with result 'exit-code'. Apr 24 12:29:36 unmatched systemd[1]: Failed to start gnome-remote-desktop.service - GNOME Remote Desktop. Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Scheduled restart job, restart counter is at 3. Apr 24 12:29:36 unmatched systemd[1]: Starting gnome-remote-desktop.service - GNOME Remote Desktop... Apr 24 12:29:36 unmatched (p-daemon)[1755]: gnome-remote-desktop.service: Failed to determine user credentials: No such process Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Main process exited,
[Desktop-packages] [Bug 2063049] Re: Google Chrome and Chromium 124 have a transparent window on Wayland
I'm running 22.04LTS on an AMD 4700U with Wayland and I experience the same
result when starting Chromium Snap 124.0.6367.91.
A transparent/glitching window opens without seeing the actual browser.
When reverting to Chromium Snap 123.0.6312.58 I can use the browser again.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/2063049
Title:
Google Chrome and Chromium 124 have a transparent window on Wayland
Status in Chromium Browser:
Unknown
Status in chromium-browser package in Ubuntu:
Triaged
Bug description:
chromium snap only launches with titlebar and transparent window after
recent snap update on wayland and intel grafics.
Adding --ozone-platform=wayland fixes the issue for me. (workaround
from bug #1968610)
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: chromium-browser 2:1snap1-0ubuntu2
ProcVersionSignature: Ubuntu 6.8.0-28.28-generic 6.8.1
Uname: Linux 6.8.0-28-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: sway
Date: Sun Apr 21 20:25:30 2024
DiskUsage:
FilesystemType Size Used Avail Use% Mounted on
rpool/ROOT/ubuntu_gk6kaa zfs 50G 7,7G 42G 16% /
tmpfs tmpfs 16G 128M 16G 1% /dev/shm
rpool/USERDATA/k1l_0tberh zfs437G 396G 42G 91% /home/k1l
InstallationDate: Installed on 2022-03-24 (760 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220321)
ProcEnviron:
LANG=de_DE.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
Snap.Changes:
ID Status Spawn Ready Summary
635 Done2024-04-21T00:51:33+02:00 2024-04-21T00:52:11+02:00 Snap
"chromium" aktualisieren
Snap.ChromeDriverVersion: ChromeDriver 124.0.6367.60
(8771130bd84f76d855ae42fbe02752b03e352f17-refs/branch-heads/6367@{#798})
Snap.ChromiumVersion: Chromium 124.0.6367.60 snap
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to noble on 2024-03-25 (27 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/2063049/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2064025] Re: Ubuntu 24.04: Accented characters persisting in gnome-text-editor (in X11 session)
** Changed in: ibus Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/2064025 Title: Ubuntu 24.04: Accented characters persisting in gnome-text-editor (in X11 session) Status in ibus: New Status in gnome-text-editor package in Ubuntu: Invalid Status in ibus package in Ubuntu: Triaged Bug description: In the GNOME text editor, after typing an accent (e.g., "~"), the symbol remains visible at the cursor location instead of disappearing after subsequent character input. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-text-editor 46.1-1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.498 CloudArchitecture: x86_64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud) CurrentDesktop: ubuntu:GNOME Date: Sun Apr 28 16:47:16 2024 LiveMediaBuild: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-text-editor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/2064025/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2064559] Re: Screen clicks not working when app page maximised
*** This bug is a duplicate of bug 1181666 *** https://bugs.launchpad.net/bugs/1181666 ** This bug has been marked a duplicate of bug 1181666 gnome-shell randomly blocks mouse clicks from working in app windows -- 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/2064559 Title: Screen clicks not working when app page maximised Status in gnome-shell package in Ubuntu: New Bug description: Recently completed a fresh installation of Ubuntu 24.4 When apps are maximised to use full screen, clicks on buttons do not work and instead go through to whatever is behind the app. Restoring the app to a window rather than full screen clicks work normally. This happens for a number of apps but not all. I am using 2 monitors (join) and using monitor 2 as my primary display. Happy to provide more info, but not sure what will be helpful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2064559/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2011385] Re: [950XED, Realtek ALC298, Speaker, Internal] No sound at all
Great job, confirmed that fix works on a Razer Blade 16 - RZ09-0483. -- 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/2011385 Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Status in linux-hwe-5.19 package in Ubuntu: Confirmed Bug description: only bluetooth can work,im sungsang book2 pro ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 13 15:41:47 2023 InstallationDate: Installed on 2023-03-08 (4 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P08RGF.054.220817.ZQ dmi.board.asset.tag: No Asset Tag dmi.board.name: NT950XEW-A51AS dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGLFREEDOS-C00-R000-S+1.0. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP08RGF.054.220817.ZQ:bd08/17/2022:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn950XED:pvrP08RGF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNT950XEW-A51AS:rvrSGLFREEDOS-C00-R000-S+1.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-ICPS-A5A5-ADLP-PRGF: dmi.product.family: Galaxy Book2 Pro dmi.product.name: 950XED dmi.product.sku: SCAI-ICPS-A5A5-ADLP-PRGF dmi.product.version: P08RGF dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2011385/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2016914] Re: gsd-smartcard: segfault on startup
@Timothée, thanks for the debugging work, could you report your finding upstream in a gitlab ticket (or perhaps submit a fix there since you understand the problem)? ** Changed in: gnome-settings-daemon (Ubuntu) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2016914 Title: gsd-smartcard: segfault on startup Status in gnome-settings-daemon package in Ubuntu: Triaged Bug description: A smartcard reader attached to the computer on startup, containing a non-standard smartcard (in this case an NXP AV3 SAM card) causes gsd- smartcard to segfault and restart 200 times after login. System Info: This is Ubuntu 22.04.2 LTS at Kernel 5.19.0-38-generic The Smart Card reader is an Identiv uTrust 4711 F with both SAM and Contactless slots The system is an HP ZBook Firefly 14 G7 Detailed issue: When the smartcard reader is plugged into the system, and an NXP SAM AV3 card is inserted into the physical smartcard slot, upon login several (5) Ubuntu Error report windows will open asking to report a crash. The reader lights will flicker for about 5 minutes until they finally stop. No other issues are seen with the system during this time. Upon looking at /var/log/syslog, the errors listed in the attachment are visible as it appears gsd-smartcard is in a loop of restarting and crashing following an error. /var/crash contains two files from the crash loop, _usr_libexec_gsd_smartcard.1000.crash and _usr_libexec_gsd_smartcard_127.crash Eventually the crashes seem to stop and the light stops flickering, but a logout and log back in will restart the issue again, as will rebooting the machine. Re-plugging the device while logged in does not seem to cause it to start the crash loop again. To complete the standard questions: 1. I logged into my computer and saw error messages 2. I expected the smart card to be ignored if there was a card inserted that was unexpected or incompatible with the gnome settings daemon 3. I encountered several crash reporter messages upon logging in, which seem to have come from the gsd-smartcard program To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/2016914/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2064093] Re: if-up.d files do not have effect on ubuntu 24.04 LTS
It also looks like on 24.04, the if-up.d scripts aren't run at all when resuming from sleep. Before 24.04: - Boot - My if-up.d script that triggers for "IFACE=wlp0s20f3" gets properly triggered (it adds an IP alias to this interface using "ip addr add"). - Put ubuntu to sleep - Resume ubuntu - My if-up.d script that triggers for "IFACE=wlp0s20f3" gets properly triggered. After 24.04: - Boot - My if-up.d script that triggers for "IFACE=wlp0s20f3" gets properly triggered (it adds an IP alias to this interface using "ip addr add"). Apparently I could fix this by triggering this script with "IFACE=-all". For now I manually run the "ip addr add" command. - Put ubuntu to sleep - Resume ubuntu - My if-up.d script that triggers for "IFACE=wlp0s20f3" is not called (not even with "IFACE=-all"). The IP alias disappeared, so the interface did go down and get back up, but the script wasn't called at all. For this I don't think I have a fix? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2064093 Title: if-up.d files do not have effect on ubuntu 24.04 LTS Status in ifupdown package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: Some time ago I wrote a detailed answer to fix an error for lowering MTU size for a cisco-compatible VPN (here:https://unix.stackexchange.com/questions/768757/unable-to-ssh- into-remote-machine-but-able-to-ping-vpnc/768758#768758) After upgrading to Ubuntu 24.04 LTS, I'm unable with the same steps to lower the MTU size. In particular, if I run the following command from the terminal sudo ifconfig your_tunnel_name mtu 1370 up it seems to lower the MTU size. However, the script under /etc/network/if-up.d is not automatically triggered. Does something change with the newer Ubuntu version? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/2064093/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2026665] Re: gnome-text-editor ignores tab settings
Thanks, it seems upstream doesn't consider it a bug but just the current design though :/ ** Changed in: gnome-text-editor (Ubuntu) Status: Confirmed => Triaged ** Also affects: gnome-text-editor via https://gitlab.gnome.org/GNOME/gnome-text-editor/-/issues/670 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-text-editor in Ubuntu. https://bugs.launchpad.net/bugs/2026665 Title: gnome-text-editor ignores tab settings Status in GNOME Text Editor: Unknown Status in gnome-text-editor package in Ubuntu: Triaged Bug description: Trying to edit some kernel c code with it and it's a hassle. The tab settings are use tabs, tab size is 8, auto indent. It simply does 2 spaces. Regardless of what I'm setting. I'm using version 44.0 on lunar. Linux snapdragix 6.4.0-rc6+ #2 SMP PREEMPT Sun Jul 9 09:09:00 CEST 2023 aarch64 aarch64 aarch64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-text-editor/+bug/2026665/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2009825] Re: [snap] thunderbird cannot sign messages with external gnupg
Thanks for the details, it does sound like an issue with the snap confinement we should work on resolving indeed ** Changed in: thunderbird (Ubuntu) Importance: Undecided => High -- 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/2009825 Title: [snap] thunderbird cannot sign messages with external gnupg Status in thunderbird package in Ubuntu: Confirmed Bug description: Thunderbird supports smartcards through the external GnuPG option: https://wiki.mozilla.org/Thunderbird:OpenPGP:Smartcards. However, the snap package cannot sign outgoing messages this way and errors out. Works (apt list): thunderbird/jammy-updates,jammy-security,now 1:102.7.1+build2-0ubuntu0.22.04.1 amd64 [installed] Does not work (snap list): thunderbird 102.8.0-2 297 latest/stable canonical✓ - I don't know if this is an expected consequence of the sandboxed environment, but could not find the error anywhere else reported. To reproduce: Set mail.openpgp.allow_external_gnupg to true. Add external key in account settings. Key is found and set. Compose empty e-mail message to self, tick Digitally Sign option. Result: Message fails to send. Error console output: Found 6 public keys and 0 secret keys (0 protected, 0 unprotected) RNPLib.jsm:541:15 Successfully loaded optional OpenPGP library libgpgme.so.11 from system's standard library locations GPGMELib.jsm:69:13 gpgme version: 1.13.1-unknown GPGMELib.jsm:241:15 services.settings: Failed to load last_modified.json: TypeError: NetworkError when attempting to fetch resource. Utils.jsm:330 Trying to load /snap/thunderbird/297/libotr.so OTRLib.jsm:64:11 Successfully loaded OTR library /snap/thunderbird/297/libotr.so OTRLib.jsm:72:13 Loading failed for the
[Desktop-packages] [Bug 2064093] Re: if-up.d files do not have effect on ubuntu 24.04 LTS
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ifupdown (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2064093 Title: if-up.d files do not have effect on ubuntu 24.04 LTS Status in ifupdown package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: Some time ago I wrote a detailed answer to fix an error for lowering MTU size for a cisco-compatible VPN (here:https://unix.stackexchange.com/questions/768757/unable-to-ssh- into-remote-machine-but-able-to-ping-vpnc/768758#768758) After upgrading to Ubuntu 24.04 LTS, I'm unable with the same steps to lower the MTU size. In particular, if I run the following command from the terminal sudo ifconfig your_tunnel_name mtu 1370 up it seems to lower the MTU size. However, the script under /etc/network/if-up.d is not automatically triggered. Does something change with the newer Ubuntu version? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/2064093/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2064093] Re: if-up.d files do not have effect on ubuntu 24.04 LTS
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2064093 Title: if-up.d files do not have effect on ubuntu 24.04 LTS Status in ifupdown package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: Some time ago I wrote a detailed answer to fix an error for lowering MTU size for a cisco-compatible VPN (here:https://unix.stackexchange.com/questions/768757/unable-to-ssh- into-remote-machine-but-able-to-ping-vpnc/768758#768758) After upgrading to Ubuntu 24.04 LTS, I'm unable with the same steps to lower the MTU size. In particular, if I run the following command from the terminal sudo ifconfig your_tunnel_name mtu 1370 up it seems to lower the MTU size. However, the script under /etc/network/if-up.d is not automatically triggered. Does something change with the newer Ubuntu version? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/2064093/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2064320] Re: unable to import a wireguard config from non-short filenames
** Changed in: gnome-control-center Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2064320 Title: unable to import a wireguard config from non-short filenames Status in gnome-control-center: New Status in gnome-control-center package in Ubuntu: Triaged Bug description: In Ubuntu 24.04 LTS fresh install. I am unable to import a Wireguard .conf configuration file from the gnome-control-center's Network panel. Parameters -> Network -> VPN -> + -> Import from file Select the .conf file that was sent by my VPN provider, then click Open Results in the following error (French) : Impossible d'importer la connexion VPN. Le fichier AirVPN_Canada_UDP-1637-Entry3.conf" est illisible ou ne contient pas d'informations de connexion VPN reconnues. Erreur: le greffon ne prend pas en charge la fonction d'importation. Fermer Which roughly translates to : Unable to import VPN connection. The AirVPN_Canada_UDP-1637-Entry3.conf" file is unreadable or does not contain recognized VPN connection information. Error: The plugin does not support the import function. Close ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-control-center 1:46.0.1-1ubuntu7 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 30 13:52:58 2024 InstallationDate: Installed on 2024-04-25 (5 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/2064320/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2064025] Re: Ubuntu 24.04: Accented characters persisting in gnome-text-editor (in X11 session)
Thank you for your bug report and for helping to investigate with upstreams! ** Changed in: ibus (Ubuntu) Status: New => Triaged ** Changed in: ibus (Ubuntu) Importance: Undecided => High ** Changed in: gnome-text-editor (Ubuntu) Status: New => Invalid ** Bug watch added: github.com/ibus/ibus/issues #2637 https://github.com/ibus/ibus/issues/2637 ** Also affects: ibus via https://github.com/ibus/ibus/issues/2637 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/2064025 Title: Ubuntu 24.04: Accented characters persisting in gnome-text-editor (in X11 session) Status in ibus: Unknown Status in gnome-text-editor package in Ubuntu: Invalid Status in ibus package in Ubuntu: Triaged Bug description: In the GNOME text editor, after typing an accent (e.g., "~"), the symbol remains visible at the cursor location instead of disappearing after subsequent character input. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-text-editor 46.1-1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.498 CloudArchitecture: x86_64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud) CurrentDesktop: ubuntu:GNOME Date: Sun Apr 28 16:47:16 2024 LiveMediaBuild: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-text-editor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/2064025/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2064568] Re: can't set picture as desktop wallpaper in nautilus
I submitted another bug about nautilus, that also affects other system apps like the snap store, settings and text editor, about the apps not adhering to the dark theme when opened. I've noticed this only happens when I open those apps almost straight away after I've booted into the desktop, when I wait a couple of minutes after boot before opening the apps, they are displayed in dark mode as expected. The 'Set as Wallpaper...' bug only occurs when I open nautilus after boot and it's displayed in light mode. My system theme is 'Dark Style'. There's no errors when I open nautilus from the terminal. Here's the output: ** Message: 12:01:54.577: Connecting to org.freedesktop.Tracker3.Miner.Files I'm using the nvidia driver 535.171.04 and X11. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2064568 Title: can't set picture as desktop wallpaper in nautilus Status in nautilus package in Ubuntu: Incomplete Bug description: When right-clicking a picture in nautilus, and then clicking on the 'Set as Background...' option from the menu, it doesn't do anything. The wallpaper can be changed from the image viewer though. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: nautilus 1:46.0-0ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 2 09:01:15 2024 GsettingsChanges: InstallationDate: Installed on 2024-05-01 (0 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) 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/nautilus/+bug/2064568/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2063383] Re: [SRU] Ubuntu Unity takes 90 seconds to log out
I did not fix it for me. The logout still takes a long time (could be around a minute / 90 seconds) even with no applications running. ``` $ dpkg -l | grep 46.0-1ubuntu4.1 ii gnome-session 46.0-1ubuntu4.1 all GNOME Session Manager - GNOME 3 session ii gnome-session-bin 46.0-1ubuntu4.1 amd64GNOME Session Manager - Minimal runtime ii gnome-session-common 46.0-1ubuntu4.1 all GNOME Session Manager - common files ii gnome-startup-applications 46.0-1ubuntu4.1 amd64Startup Applications manager for GNOME ii ubuntu-session 46.0-1ubuntu4.1 all Ubuntu session with GNOME Shell ii unity-session 46.0-1ubuntu4.1 all Unity session, previous ubuntu default experience. ``` -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/2063383 Title: [SRU] Ubuntu Unity takes 90 seconds to log out Status in gnome-session package in Ubuntu: Confirmed Status in gnome-session source package in Noble: Fix Committed Bug description: [ Impact ] Ubuntu Unity reliably takes 90 seconds to log out. This is due to the user-level gnome-session.service systemd unit not properly terminating gnome-session on logout. An attempt is made to send SIGTERM to the process, which gnome-session does not care about. Instead, gnome-session-quit should be invoked when the systemd unit shuts down, which acts effectively and immediately. [ Test Plan ] Actual behavior: 1. Log in to a Unity session on Ubuntu Unity 24.04. 2. Log out of Ubuntu Unity. 3. Observe that only the wallpaper is shown for 90 seconds prior to the login manager showing again. Expected behavior: 1. Log in to a Unity session on Ubuntu Unity 24.04. 2. Log out of Ubuntu Unity. 3. Observe that logging out takes a few seconds at most, and you are able to log back in as the same user, or a different one. [ Where problems could occur ] If the gnome-session or gnome-session-quit binaries change the arguments they accept by default, log in and log out functionality on Unity sessions are likely to break. Additionally, if lightdm or systemd changes in a non-reverse- compatible way, this increases the chance of a user-facing regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/2063383/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2064096] Re: Services fail to start in noble deployed with TPM+FDE
Answering questions from #2064088 Q: Can you also show the output of: ps fauxwZ A: See attached ** Attachment added: "ps" https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2064096/+attachment/5774011/+files/ps -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2064096 Title: Services fail to start in noble deployed with TPM+FDE Status in apparmor package in Ubuntu: New Status in cups package in Ubuntu: Confirmed Status in rsyslog package in Ubuntu: Confirmed Status in sssd package in Ubuntu: Confirmed Bug description: What's known so far: - 24.04 desktop deployed with TPM+FDE shows this bug - services confined with apparmor that need to access something in /run/systemd (like the notify socket) fail to do so, even if the apparmor profile is in complain mode. And the apparmor profile does already have rules to allow that access - only after running aa-disable can the service start fine - paths logged by the apparmor DENIED or ALLOWED messages are missing the "/run" prefix from "/run/systemd/..". - When we add rules to the profile using "/systemd/" (i.e., also dropping the /run prefix), then it works - other access in /run/systemd/ are also blocked, but the most noticeable one is the notify mechanism - comment #2 also states that azure CVM images are also impacted - comment #4 has instructions on how to create such a VM locally with LXD vms Original description follows: This might be related to #2064088 The rsyslog service is continually timing out and restarting. If I use a service drop-in file and change the 'Type' from 'notify' to 'simple', the service starts and appears to work normally. In the journal, I can see the attached apparmor errors. I can't make sense of them, but if it's a similar issue to #2064088, then I suspect apparmor is preventing the systemd notify function from alerting systemd that the service is up and running. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: rsyslog 8.2312.0-3ubuntu9 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Mon Apr 29 10:37:46 2024 ProcEnviron: LANG=en_GB.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: rsyslog UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2064096/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2064096] Re: Services fail to start in noble deployed with TPM+FDE
Answering questions from #2064088 Q: Did you install this fde/tpm setup using the ubuntu desktop noble installer? Or was hit some manual setup? A: The install was performed using autoinstall with the desktop ISO. Attached is a copy of the autoinstall yaml ** Attachment added: "autoinstall user-data YAML" https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2064096/+attachment/5774010/+files/user-data -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2064096 Title: Services fail to start in noble deployed with TPM+FDE Status in apparmor package in Ubuntu: New Status in cups package in Ubuntu: Confirmed Status in rsyslog package in Ubuntu: Confirmed Status in sssd package in Ubuntu: Confirmed Bug description: What's known so far: - 24.04 desktop deployed with TPM+FDE shows this bug - services confined with apparmor that need to access something in /run/systemd (like the notify socket) fail to do so, even if the apparmor profile is in complain mode. And the apparmor profile does already have rules to allow that access - only after running aa-disable can the service start fine - paths logged by the apparmor DENIED or ALLOWED messages are missing the "/run" prefix from "/run/systemd/..". - When we add rules to the profile using "/systemd/" (i.e., also dropping the /run prefix), then it works - other access in /run/systemd/ are also blocked, but the most noticeable one is the notify mechanism - comment #2 also states that azure CVM images are also impacted - comment #4 has instructions on how to create such a VM locally with LXD vms Original description follows: This might be related to #2064088 The rsyslog service is continually timing out and restarting. If I use a service drop-in file and change the 'Type' from 'notify' to 'simple', the service starts and appears to work normally. In the journal, I can see the attached apparmor errors. I can't make sense of them, but if it's a similar issue to #2064088, then I suspect apparmor is preventing the systemd notify function from alerting systemd that the service is up and running. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: rsyslog 8.2312.0-3ubuntu9 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Mon Apr 29 10:37:46 2024 ProcEnviron: LANG=en_GB.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: rsyslog UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2064096/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2064320] Re: unable to import a wireguard config from non-short filenames
I've reported the error upstream https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/3042 It's a bit unclear if the bug is in the setting of the backend though, if you get a working system again would you mean trying to do $ nmcli connection import type wireguard file AirVPN_Canada_UDP-1637-Entry3.conf and see if that works? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2064320 Title: unable to import a wireguard config from non-short filenames Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: Triaged Bug description: In Ubuntu 24.04 LTS fresh install. I am unable to import a Wireguard .conf configuration file from the gnome-control-center's Network panel. Parameters -> Network -> VPN -> + -> Import from file Select the .conf file that was sent by my VPN provider, then click Open Results in the following error (French) : Impossible d'importer la connexion VPN. Le fichier AirVPN_Canada_UDP-1637-Entry3.conf" est illisible ou ne contient pas d'informations de connexion VPN reconnues. Erreur: le greffon ne prend pas en charge la fonction d'importation. Fermer Which roughly translates to : Unable to import VPN connection. The AirVPN_Canada_UDP-1637-Entry3.conf" file is unreadable or does not contain recognized VPN connection information. Error: The plugin does not support the import function. Close ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-control-center 1:46.0.1-1ubuntu7 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 30 13:52:58 2024 InstallationDate: Installed on 2024-04-25 (5 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/2064320/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2064277] Re: NetworkManager, default IPv4 route always through wifi, even if wired available
Thank you for your bug report. Could you perhaps also submit it upstream on https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2064277 Title: NetworkManager, default IPv4 route always through wifi, even if wired available Status in network-manager package in Ubuntu: New Bug description: If wifi is connected, the default IPv4 route is always through wifi, no route through wired connection is set up, even if wired faster, and connected to the same gw. The default IPv6 route is ok. Tested on a fresh install, same behavior. lionel@lionelux:~$ ip addr 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host noprefixroute valid_lft forever preferred_lft forever 2: wlo1: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 70:a8:d3:dc:fa:05 brd ff:ff:ff:ff:ff:ff altname wlp0s20f3 inet 10.0.0.66/24 brd 10.0.0.255 scope global dynamic noprefixroute wlo1 valid_lft 7153sec preferred_lft 7153sec inet6 2a01:e0a:51a:50d1:c4f5:20d5:51a:3666/64 scope global temporary dynamic valid_lft 604755sec preferred_lft 86110sec inet6 2a01:e0a:51a:50d1:3c79:4f2b:d7f1:a0d/64 scope global mngtmpaddr noprefixroute valid_lft forever preferred_lft forever inet6 fe80::e2e1:a4d7:bb8c:961a/64 scope link noprefixroute valid_lft forever preferred_lft forever 3: virbr0: mtu 1500 qdisc noqueue state DOWN group default qlen 1000 link/ether 52:54:00:4d:6c:56 brd ff:ff:ff:ff:ff:ff inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0 valid_lft forever preferred_lft forever 9: enx908d6e354c47: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 90:8d:6e:35:4c:47 brd ff:ff:ff:ff:ff:ff inet 10.0.0.65/24 brd 10.0.0.255 scope global dynamic noprefixroute enx908d6e354c47 valid_lft 7174sec preferred_lft 7174sec inet6 2a01:e0a:51a:50d1:7c69:4bd8:2924:9ff8/64 scope global temporary dynamic valid_lft 604775sec preferred_lft 86178sec inet6 2a01:e0a:51a:50d1:c87c:7002:3ad2:496e/64 scope global mngtmpaddr noprefixroute valid_lft forever preferred_lft forever inet6 fe80::ba1:bdae:e9c3:f29f/64 scope link noprefixroute valid_lft forever preferred_lft forever 10: enx186571a0c6a4: mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000 link/ether 18:65:71:a0:c6:a4 brd ff:ff:ff:ff:ff:ff lionel@lionelux:~$ ip route default via 10.0.0.1 dev wlo1 proto dhcp src 10.0.0.66 metric 600 10.0.0.0/24 dev wlo1 proto kernel scope link src 10.0.0.66 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown lionel@lionelux:~$ ip -6 route 2a01:e0a:51a:50d1::/64 dev enx908d6e354c47 proto ra metric 100 pref medium 2a01:e0a:51a:50d1::/64 dev wlo1 proto ra metric 600 pref medium fe80::/64 dev wlo1 proto kernel metric 1024 pref medium fe80::/64 dev enx908d6e354c47 proto kernel metric 1024 pref medium default via fe80::8b6b:4e44:c003:cca6 dev wlo1 proto ra metric 600 pref medium default via fe80::8b6b:4e44:c003:cca6 dev enx908d6e354c47 proto ra metric 20100 pref medium ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: network-manager 1.46.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 30 13:09:23 2024 InstallationDate: Installed on 2024-02-09 (81 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) IpRoute: default via 10.0.0.1 dev enx908d6e354c47 proto dhcp src 10.0.0.65 metric 100 default via 10.0.0.1 dev wlo1 proto dhcp src 10.0.0.66 metric 600 10.0.0.0/24 dev enx908d6e354c47 proto kernel scope link src 10.0.0.65 metric 100 10.0.0.0/24 dev wlo1 proto kernel scope link src 10.0.0.66 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: network-manager UpgradeStatus: Upgraded to noble on 2024-04-25 (5 days ago) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2024-02-14T13:52:12.489815 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running
[Desktop-packages] [Bug 2064320] Re: gnome-control-center : unable to import a wireguard configuration from file
Urg, sorry about those issues :-( Thanks for confirming the file length issue ** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => New ** Changed in: gnome-control-center (Ubuntu) Status: New => Triaged ** Summary changed: - gnome-control-center : unable to import a wireguard configuration from file + unable to import a wireguard config from non-short filenames ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #3042 https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/3042 ** Also affects: gnome-control-center via https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/3042 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2064320 Title: unable to import a wireguard config from non-short filenames Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: Triaged Bug description: In Ubuntu 24.04 LTS fresh install. I am unable to import a Wireguard .conf configuration file from the gnome-control-center's Network panel. Parameters -> Network -> VPN -> + -> Import from file Select the .conf file that was sent by my VPN provider, then click Open Results in the following error (French) : Impossible d'importer la connexion VPN. Le fichier AirVPN_Canada_UDP-1637-Entry3.conf" est illisible ou ne contient pas d'informations de connexion VPN reconnues. Erreur: le greffon ne prend pas en charge la fonction d'importation. Fermer Which roughly translates to : Unable to import VPN connection. The AirVPN_Canada_UDP-1637-Entry3.conf" file is unreadable or does not contain recognized VPN connection information. Error: The plugin does not support the import function. Close ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-control-center 1:46.0.1-1ubuntu7 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 30 13:52:58 2024 InstallationDate: Installed on 2024-04-25 (5 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/2064320/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
Thanks for the bug report and the update, let's close if it has been resolved with updates ** No longer affects: ubuntu ** Changed in: fontconfig (Ubuntu) Status: New => Invalid -- 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 fontconfig package in Ubuntu: Invalid 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/+source/fontconfig/+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 2063333] Re: gnome-remote-desktop.service: Failed to determine user credentials: No such process
/usr/lib/systemd/system/gnome-remote-desktop.service has User=gnome-remote-desktop But it seems that user isn't created by the package? I wonder if that would part of the issue but then it should be happening also on other systems... Could you try to manually start $ /usr/libexec/gnome-remote-desktop-daemon --system and see if that prints a more explicit error maybe? ** Changed in: gnome-remote-desktop (Ubuntu) Importance: Undecided => High -- 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/206 Title: gnome-remote-desktop.service: Failed to determine user credentials: No such process Status in gnome-remote-desktop package in Ubuntu: Confirmed Bug description: On a RISC-V Ubuntu 24.04 I installed ubuntu-desktop. The desktop does not show up though gdm3 is running. I see the following error messages which might indicate a dependency issue: pr 24 12:29:35 unmatched systemd[1]: Starting gnome-remote-desktop.service - GNOME Remote Desktop... Apr 24 12:29:35 unmatched (p-daemon)[1752]: gnome-remote-desktop.service: Failed to determine user credentials: No such process Apr 24 12:29:35 unmatched systemd[1]: gnome-remote-desktop.service: Main process exited, code=exited, status=217/USER Apr 24 12:29:35 unmatched systemd[1]: gnome-remote-desktop.service: Failed with result 'exit-code'. Apr 24 12:29:35 unmatched systemd[1]: Failed to start gnome-remote-desktop.service - GNOME Remote Desktop. Apr 24 12:29:35 unmatched systemd[1]: gnome-remote-desktop.service: Scheduled restart job, restart counter is at 1. Apr 24 12:29:35 unmatched systemd[1]: Starting gnome-remote-desktop.service - GNOME Remote Desktop... Apr 24 12:29:35 unmatched (p-daemon)[1753]: gnome-remote-desktop.service: Failed to determine user credentials: No such process Apr 24 12:29:35 unmatched systemd[1]: gnome-remote-desktop.service: Main process exited, code=exited, status=217/USER Apr 24 12:29:35 unmatched systemd[1]: gnome-remote-desktop.service: Failed with result 'exit-code'. Apr 24 12:29:35 unmatched systemd[1]: Failed to start gnome-remote-desktop.service - GNOME Remote Desktop. Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Scheduled restart job, restart counter is at 2. Apr 24 12:29:36 unmatched systemd[1]: Starting gnome-remote-desktop.service - GNOME Remote Desktop... Apr 24 12:29:36 unmatched (p-daemon)[1754]: gnome-remote-desktop.service: Failed to determine user credentials: No such process Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Main process exited, code=exited, status=217/USER Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Failed with result 'exit-code'. Apr 24 12:29:36 unmatched systemd[1]: Failed to start gnome-remote-desktop.service - GNOME Remote Desktop. Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Scheduled restart job, restart counter is at 3. Apr 24 12:29:36 unmatched systemd[1]: Starting gnome-remote-desktop.service - GNOME Remote Desktop... Apr 24 12:29:36 unmatched (p-daemon)[1755]: gnome-remote-desktop.service: Failed to determine user credentials: No such process Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Main process exited, code=exited, status=217/USER Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Failed with result 'exit-code'. Apr 24 12:29:36 unmatched systemd[1]: Failed to start gnome-remote-desktop.service - GNOME Remote Desktop. Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Scheduled restart job, restart counter is at 4. Apr 24 12:29:36 unmatched systemd[1]: Starting gnome-remote-desktop.service - GNOME Remote Desktop... Apr 24 12:29:36 unmatched (p-daemon)[1756]: gnome-remote-desktop.service: Failed to determine user credentials: No such process Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Main process exited, code=exited, status=217/USER Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Failed with result 'exit-code'. Apr 24 12:29:36 unmatched systemd[1]: Failed to start gnome-remote-desktop.service - GNOME Remote Desktop. Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Scheduled restart job, restart counter is at 5. Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Start request repeated too quickly. Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Failed with result 'exit-code'. Apr 24 12:29:36 unmatched systemd[1]: Failed to start gnome-remote-desktop.service - GNOME Remote Desktop. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-remote-desktop 46.1-1 ProcVersionSignature: Ubuntu 6.8.0-31.31.1-generic 6.8.1 Uname: Linux 6.8.0-31-generic riscv64 ApportVersion: 2.28.1-0ubuntu2
[Desktop-packages] [Bug 2064568] Re: can't set picture as desktop wallpaper in nautilus
Thank you for your bug report. Do you get any error printed if you start nautilus from a commandline ? It's supposed to the use desktop portal for setting the wallpaper so maybe that's not working as expected from some reason... ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2064568 Title: can't set picture as desktop wallpaper in nautilus Status in nautilus package in Ubuntu: Incomplete Bug description: When right-clicking a picture in nautilus, and then clicking on the 'Set as Background...' option from the menu, it doesn't do anything. The wallpaper can be changed from the image viewer though. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: nautilus 1:46.0-0ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 2 09:01:15 2024 GsettingsChanges: InstallationDate: Installed on 2024-05-01 (0 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) 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/nautilus/+bug/2064568/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2064569] Re: The shortcut for "Increment number at cursor" not works in gnome-text-editor
Thank you for bug report and the upstream reference ** Changed in: gnome-text-editor (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-text-editor (Ubuntu) Status: New => Triaged ** Bug watch added: gitlab.gnome.org/GNOME/gnome-text-editor/-/issues #623 https://gitlab.gnome.org/GNOME/gnome-text-editor/-/issues/623 ** Also affects: gnome-text-editor via https://gitlab.gnome.org/GNOME/gnome-text-editor/-/issues/623 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-text-editor in Ubuntu. https://bugs.launchpad.net/bugs/2064569 Title: The shortcut for "Increment number at cursor" not works in gnome-text- editor Status in GNOME Text Editor: Unknown Status in gnome-text-editor package in Ubuntu: Triaged Bug description: The shortcut for "Increment number at cursor" (Shift+Ctrl+A) not works in gnome-text-editor on Ubuntu 24.04. Note: The shortcut for "Decrement number at cursor" (Shift+Ctrl+X) works well. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-text-editor 46.1-1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.498 CloudArchitecture: x86_64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud) CurrentDesktop: ubuntu:GNOME Date: Thu May 2 06:33:33 2024 LiveMediaBuild: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-text-editor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-text-editor/+bug/2064569/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2064510] Re: File manager hang up
Thank you for your bug report. Could you attach the journalctl log from that session (you can use the '-' parameter to get the log from restarts ago It's a bit unclear in the description was only the filemanager not usable or also the rest of the session? ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2064510 Title: File manager hang up Status in nautilus package in Ubuntu: Incomplete Bug description: I was doing a large backup of files from an SSD drive to a external USB drive using rsync running in a terminal window. I then opened up a new file manager window and then (i think) I clicked on the same SSD drive (that was being copied) to get its properties (I wanted to see how much disk space was used up). I then got a dialog popup on the screen (I have a screenshot of this attached) saying the following "There was an error while getting the sharing information" Failed to execute child process "net" (No such file or directory) At this point all the file manager windows were unresponsive. They could not be closed, but I think they could be moved and they could come to foreground etc. In the end I had to crash power off my laptop. I took me 4 hours to chkdsk\recover file systems on both my external USB hard drives and the SSD as well (done using Win10 because they were all NTFS drives). Also as an aside (this is probably another bug)... every so often a file manager window will freeze on its righthand side. You can click on various drives on the lefthand side but it never updates the righthand side to show the file\folders on that clicked drive. I end up closing the filemanager window and opening up a new one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2064510/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2038761] Re: gnome-disk-utility does not give size of nvme disk
Great, let's close the bug then, thanks for the update! ** Package changed: udisks2 (Ubuntu) => gnome-disk-utility (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/2038761 Title: gnome-disk-utility does not give size of nvme disk Status in udisks: New Status in gnome-disk-utility package in Ubuntu: Triaged Bug description: Mantic gnome-disk-utility: 45.0-1ubuntu1 Size of nvme disk is blank while in Jammy 42.0-1ubuntu1 gives correct size. see attached image ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-disk-utility 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3 Uname: Linux 6.5.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Oct 8 17:16:12 2023 InstallationDate: Installed on 2023-10-07 (1 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20231005) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/udisks/+bug/2038761/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2064559] Re: Screen clicks not working when app page maximised
** Project changed: ubuntu-desktop-provision => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2064559 Title: Screen clicks not working when app page maximised Status in gnome-shell package in Ubuntu: New Bug description: Recently completed a fresh installation of Ubuntu 24.4 When apps are maximised to use full screen, clicks on buttons do not work and instead go through to whatever is behind the app. Restoring the app to a window rather than full screen clicks work normally. This happens for a number of apps but not all. I am using 2 monitors (join) and using monitor 2 as my primary display. Happy to provide more info, but not sure what will be helpful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2064559/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
Thanks for confirming, I'm marking the bug as verification-done ** Tags removed: verification-needed verification-needed-noble ** Tags added: verification-done verification-done-noble -- 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: Fix Committed Status in apport package in Ubuntu: Fix Committed Status in thunderbird package in Ubuntu: Invalid Status in apport source package in Noble: Fix Committed 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/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 2062967] Re: ubuntu-drivers no longer offers nvidia 550 drivers
The new version will be listed in the tools once available and tested -- 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: Confirmed 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 2064354] Re: File manager crashes on run
The crash from the previous comment is in libnvidia-vulkan-producer.so so also a nvidia driver issue, I'm reassigning > I wonder why 535 was the most recent driver offered by "Software & Updates -> > Additional Drivers". The rational is on bug #2061830 but basically the new version was available too late in the cycle to be properly tested before release but it will enabled there once we have confidence it's working correctly ** Package changed: nautilus (Ubuntu) => nvidia-graphics-drivers-535 (Ubuntu) ** Changed in: nvidia-graphics-drivers-535 (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2064354 Title: File manager crashes on run Status in nvidia-graphics-drivers-535 package in Ubuntu: New Bug description: Nautilus would not open a GUI window after a fresh Ubuntu 24.04 install. I obtained the following from the command prompt: $ nautilus ** Message: 16:12:45.453: Connecting to org.freedesktop.Tracker3.Miner.Files libEGL warning: egl: failed to create dri2 screen Segmentation fault (core dumped) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: nautilus 1:46.0-0ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 30 16:15:29 2024 GsettingsChanges: b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' InstallationDate: Installed on 2024-04-24 (6 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240410.2) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 44.1-1 nautilus-extension-gnome-terminal 3.52.0-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2064354/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows
New install of ubuntu 24.04, causes this issue -- 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/1181666 Title: gnome-shell randomly blocks mouse clicks from working in app windows Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Under GNOME 3, the use of the mouse-click stops occasionally, though I can still move the mouse around and can still click on items in the Activities screen and the top-bar. I can use alt-tab to cycle windows and can still type into already- active textboxes in windows, but I cannot click within the windows, and the mouse is not picked up at all by the windows. I can open the alt-f2 "run command" dialogue, but cannot type into it. The workaround I'm using is to open terminal (ctrl-alt-T) and run "gnome-shell -r", and restarting that command every time I have the problem again. Please ask if there's anything I forgot to mention. ADDITIONAL: The error tends to happen randomly, but it seems to happen upon opening a new window, changing windows, closing windows, or opening the activities pane (whether a change of window is thus instigated or not) ADDITIONAL 2: (sorry, it's early) The other workaround is to log out and to log in again, but that is also less than ideal ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-shell 3.6.3.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11 Uname: Linux 3.8.0-22-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Sun May 19 07:02:18 2013 DisplayManager: gdm GsettingsChanges: b'org.gnome.desktop.interface' b'clock-show-date' b'true' b'org.gnome.desktop.interface' b'clock-show-seconds' b'true' b'org.gnome.desktop.interface' b'document-font-name' b"'Sans 10'" b'org.gnome.desktop.interface' b'font-name' b"'Cantarell 10'" b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 12'" InstallationDate: Installed on 2013-05-04 (14 days ago) InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1181666/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2064559] [NEW] Screen clicks not working when app page maximised
You have been subscribed to a public bug: Recently completed a fresh installation of Ubuntu 24.4 When apps are maximised to use full screen, clicks on buttons do not work and instead go through to whatever is behind the app. Restoring the app to a window rather than full screen clicks work normally. This happens for a number of apps but not all. I am using 2 monitors (join) and using monitor 2 as my primary display. Happy to provide more info, but not sure what will be helpful. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- Screen clicks not working when app page maximised https://bugs.launchpad.net/bugs/2064559 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell 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 2059756] Re: [SRU] adsys 0.14.1
We plan to SRU the stack to Mantic and align all the supported releases on the same version. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/2059756 Title: [SRU] adsys 0.14.1 Status in adsys package in Ubuntu: Fix Released Status in golang-1.22 package in Ubuntu: Fix Released Status in adsys source package in Jammy: Confirmed Status in golang-1.22 source package in Jammy: Confirmed Status in adsys source package in Mantic: Confirmed Status in golang-1.22 source package in Mantic: Confirmed Bug description: [context] ADSys is a tool designed for administering and implementing Group Policy Objects (GPOs) from Active Directory on Linux systems. It includes a suite of services and commands that empower administrators to efficiently manage policy updates and maintain compliance with organizational business rules. Given that ADSys directly interfaces with Active Directory and needs to align with new business requirements in LTS releases, it has been essential to keep the package consistently updated with the latest changes of ADSys upstream source. As ADSys is a key component of our commercial offerings, our customers anticipate the availability of recently implemented features in the 22.04 release. Now that ADSys has a complete set of features, the request is to proceed with a one-off release of ADSys 0.14.1 to 22.04. Please note that any new features introduced in subsequent versions will be exclusively available in 24.04 and later releases. This version includes a comprehensive end to end automated test suite that runs ADSys against a real Active directory environment. Version 0.14.1 is available for 22.04 in a PPA (https://launchpad.net/~ubuntu-enterprise- desktop/+archive/ubuntu/adsys) and already used in production by customers. At this time of writing the number of open issues is 1 in Launchpad and 16 in GitHub including 6 enhancements. None of them have a high or critical importance. [references] LP: https://launchpad.net/ubuntu/+source/adsys LP Bugs: https://bugs.launchpad.net/ubuntu/+source/adsys GitHub: https://github.com/ubuntu/adsys/ GH Bugs: https://github.com/ubuntu/adsys/issues Documentation: https://canonical-adsys.readthedocs-hosted.com/en/stable/ Initial SRU discussion: https://lists.ubuntu.com/archives/ubuntu-release/2023-June/005650.html [changes] Full LP Changelog: https://launchpad.net/ubuntu/+source/adsys/+changelog * New features * New policies: - Add mount / network shares policy manager - Add AppArmor policy manager - Support multiple AD backends and implement Winbind support - Add system proxy policy manager - Add certificate policy manager for machines - Add adsysctl policy purge command to purge applied policies - Full documentation - Full end to end automated test suite. * Enhancements * Add a --machine / -m flag to adsysctl applied, indicating the policies applied to the current machine * Expose Ubuntu Pro status in the "status" command * Update scripts manager creation * List Pro policy types in service status output * Warn when Pro-only rules are configured * Use systemd via D-Bus instead of systemctl commands * Add placeholder notes for entry types * Rework Kerberos ticket handling logic to satisfy the Heimdal implementation of Kerberos * Rework policy application sync strategy * Print logs when policies are up to date * Update policy definitions to include dconf key for dark mode background * Infer user KRB5CCNAME path via the libkrb5 API (LP: #2049061) * Allow sssd backend to work without ad_domain being set (LP: #2054445) * Update apport hook to include journal errors and package logs * Bug fixes * Fix policy update failing when GPT.INI contains no version key * Fix object lookup for users having a FQDN as their hostname * Support special characters in domains when parsing sssd configuration * Fix DCONF_PROFILE not considering default_domain_suffix on sssd.conf * Ensure empty state for dconf policy * Handle case mismatches in GPT.INI file name * Ensure GPO URLs contain the FQDN of the domain controller * Add runtime dependency on nfs-common * Other * Updates to latest versions of Go (fixing known Go vulnerabilities) * Updates to latest versions of the Go dependencies * Updates and improvements to CI and QoL * Migrate translation support to native approach using go-i18n + gotext and switch to upstream gotext version Dependencies: * Build-dep: golang-go (>= 2:1.22~) * Dependencies to backport to 22.04: * golang-go >= 2:1.22 * ubuntu-proxy-manager (suggest. Required for Proxy support - feature will be disabled otherwise) * python3-cepces (suggest. Required for Certificates
[Desktop-packages] [Bug 2019137] Re: gnome-software should (?) be separated from the packagekit
This bug was fixed in the package gnome-software - 46.1-1 --- gnome-software (46.1-1) unstable; urgency=high * New upstream release -- Jeremy Bícha Mon, 29 Apr 2024 17:05:57 -0400 ** Changed in: gnome-software (Ubuntu) Status: Fix Committed => Fix Released -- 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/2019137 Title: gnome-software should (?) be separated from the packagekit Status in gnome-software package in Ubuntu: Fix Released Bug description: Given that the Snap Store is currently the default in Ubuntu instead of GNOME Software, the only reason GNOME Software (along with the Snap Store) can be installed is to support Flatpak applications. In the current instance, if you want to add flatpak support, GNOME Software is installed with both the apt packagekit add-on and the flatpak plugin, which is duplication of work (Software Updater already works on updates, and Snap Store works on showing deb apps). And since the future app store explicitly refuses [1], [2] to support flatpak applications, users who need this package format will be forced to put GNOME Software with everything I pointed out above. Therefore, it would be very nice if the developers removed the packagekit add-on from the "gnome-software part" and made it a "plug- in for gnome-software". I, unfortunately, have no such experience with packaging deb packages at the moment, and it turns out that it will obviously be necessary to work out both the code part (which, as far as I can see, won't be very difficult [3]), as well as the part where we will have to figure out where and how to insert the plugin as mandatory (for example, when the user completely gives up on snap packages) and as optional (because the Snap Store already stands). Also, let me know if this needs to be sent to upstream (Debian) instead of here. --- 1. https://github.com/ubuntu-flutter-community/software/issues/126 2. https://github.com/ubuntu-flutter-community/software/issues/30 3. https://build.opensuse.org/request/show/1031279 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2019137/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
This bug was fixed in the package gnome-software - 46.1-1 --- gnome-software (46.1-1) unstable; urgency=high * New upstream release -- Jeremy Bícha Mon, 29 Apr 2024 17:05:57 -0400 ** Changed in: gnome-software (Ubuntu) Status: New => Fix Released -- 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: Fix Released 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 2064275] Re: Blank screen after logging in Wayland using HP Thunderbolt G4 [drmModeAtomicCommit: Invalid argument]
I can reproduce it by turning off my computer and then directly logging in using wayland every time. ** Attachment added: "GSLog" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2064275/+attachment/5773978/+files/gslog.txt -- 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/2064275 Title: Blank screen after logging in Wayland using HP Thunderbolt G4 [drmModeAtomicCommit: Invalid argument] Status in linux package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Using two displayport 4k LG monitors on a HP Thunderbolt G4 dock. After logging in using wayland, both monitors goes blank and then enters power saving mode. If I replug the dock then the monitors wake up but with display settings reset. When using x-server, both screen work as normal after login remembering my screen placement etc. Optimus Laptop AMD+Nvidia graphics on-demand using USB-C alt mode. Ubuntu 24.04 with latest updtes installed. --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-04-26 (4 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 46.0-0ubuntu5 PackageArchitecture: amd64 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 RelatedPackageVersions: mutter-common 46.0-1ubuntu9 Tags: noble Uname: Linux 6.8.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin ollama plugdev sudo users _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-04-26 (4 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 46.0-0ubuntu5 PackageArchitecture: amd64 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 RelatedPackageVersions: mutter-common 46.0-1ubuntu9 Tags: noble wayland-session Uname: Linux 6.8.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin ollama plugdev sudo users _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064275/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2064510] Re: File manager hang up
** Package changed: ubuntu => nautilus (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2064510 Title: File manager hang up Status in nautilus package in Ubuntu: New Bug description: I was doing a large backup of files from an SSD drive to a external USB drive using rsync running in a terminal window. I then opened up a new file manager window and then (i think) I clicked on the same SSD drive (that was being copied) to get its properties (I wanted to see how much disk space was used up). I then got a dialog popup on the screen (I have a screenshot of this attached) saying the following "There was an error while getting the sharing information" Failed to execute child process "net" (No such file or directory) At this point all the file manager windows were unresponsive. They could not be closed, but I think they could be moved and they could come to foreground etc. In the end I had to crash power off my laptop. I took me 4 hours to chkdsk\recover file systems on both my external USB hard drives and the SSD as well (done using Win10 because they were all NTFS drives). Also as an aside (this is probably another bug)... every so often a file manager window will freeze on its righthand side. You can click on various drives on the lefthand side but it never updates the righthand side to show the file\folders on that clicked drive. I end up closing the filemanager window and opening up a new one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2064510/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2064510] [NEW] File manager hang up
You have been subscribed to a public bug: I was doing a large backup of files from an SSD drive to a external USB drive using rsync running in a terminal window. I then opened up a new file manager window and then (i think) I clicked on the same SSD drive (that was being copied) to get its properties (I wanted to see how much disk space was used up). I then got a dialog popup on the screen (I have a screenshot of this attached) saying the following "There was an error while getting the sharing information" Failed to execute child process "net" (No such file or directory) At this point all the file manager windows were unresponsive. They could not be closed, but I think they could be moved and they could come to foreground etc. In the end I had to crash power off my laptop. I took me 4 hours to chkdsk\recover file systems on both my external USB hard drives and the SSD as well (done using Win10 because they were all NTFS drives). Also as an aside (this is probably another bug)... every so often a file manager window will freeze on its righthand side. You can click on various drives on the lefthand side but it never updates the righthand side to show the file\folders on that clicked drive. I end up closing the filemanager window and opening up a new one. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- File manager hang up https://bugs.launchpad.net/bugs/2064510 You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus 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 2056767] Re: FFe: Sync gnome-software 46.0-4 (universe) from Debian unstable (main) with gnome-software packaging split
** Tags removed: block-proposed -- 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 2064569] [NEW] The shortcut for "Increment number at cursor" not works in gnome-text-editor
Public bug reported: The shortcut for "Increment number at cursor" (Shift+Ctrl+A) not works in gnome-text-editor on Ubuntu 24.04. Note: The shortcut for "Decrement number at cursor" (Shift+Ctrl+X) works well. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-text-editor 46.1-1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.498 CloudArchitecture: x86_64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud) CurrentDesktop: ubuntu:GNOME Date: Thu May 2 06:33:33 2024 LiveMediaBuild: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-text-editor UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-text-editor (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy noble -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-text-editor in Ubuntu. https://bugs.launchpad.net/bugs/2064569 Title: The shortcut for "Increment number at cursor" not works in gnome-text- editor Status in gnome-text-editor package in Ubuntu: New Bug description: The shortcut for "Increment number at cursor" (Shift+Ctrl+A) not works in gnome-text-editor on Ubuntu 24.04. Note: The shortcut for "Decrement number at cursor" (Shift+Ctrl+X) works well. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-text-editor 46.1-1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.498 CloudArchitecture: x86_64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud) CurrentDesktop: ubuntu:GNOME Date: Thu May 2 06:33:33 2024 LiveMediaBuild: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-text-editor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-text-editor/+bug/2064569/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2064568] [NEW] can't set picture as desktop wallpaper in nautilus
Public bug reported: When right-clicking a picture in nautilus, and then clicking on the 'Set as Background...' option from the menu, it doesn't do anything. The wallpaper can be changed from the image viewer though. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: nautilus 1:46.0-0ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 2 09:01:15 2024 GsettingsChanges: InstallationDate: Installed on 2024-05-01 (0 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: nautilus-extension-gnome-terminal 3.52.0-1ubuntu2 ** Affects: nautilus (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 nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2064568 Title: can't set picture as desktop wallpaper in nautilus Status in nautilus package in Ubuntu: New Bug description: When right-clicking a picture in nautilus, and then clicking on the 'Set as Background...' option from the menu, it doesn't do anything. The wallpaper can be changed from the image viewer though. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: nautilus 1:46.0-0ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 2 09:01:15 2024 GsettingsChanges: InstallationDate: Installed on 2024-05-01 (0 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) 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/nautilus/+bug/2064568/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
