[Desktop-packages] [Bug 2023322] Re: Unable to setup Google Online Accounts with Nvidia drivers
It looks like a significant proportion of webkit2gtk crashes are Nvidia- specific and don't have retraces (which is actually a bug in errors.ubuntu.com because that doesn't happen when debugging locally): https://errors.ubuntu.com/?release=Ubuntu%2023.04=webkit2gtk=week So it looks like we will need to catch a crash file and then debug it on the original machine (apport-unpack, gdb). ** Project changed: gnome-control-center => ubuntu ** No longer affects: ubuntu ** No longer affects: gnome-control-center (Ubuntu) ** No longer affects: gnome-online-accounts (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/2023322 Title: Unable to setup Google Online Accounts with Nvidia drivers Status in Webkit: Confirmed Status in webkit2gtk package in Ubuntu: Incomplete Status in webkit2gtk package in Debian: New Bug description: When I go into Settings > Online Accounts > Google, I get to the prompt for email address, once in a while it stops accepting input there. But often I can get to the password screen. Once I do, I can't type anything or paste anything. This is a fresh install of Ubuntu 23.04 and I have installed all updates. Nothing in /var/crash Jun 08 11:15:59 CCW-HAL systemd[3523]: vte-spawn-8b4a59a3-a060-4bdd-92e6-285656bdb9a2.scope: Consumed 3.448s CPU time. Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:29 CCW-HAL systemd[3523]: Started app-gnome-org.gnome.Terminal-10924.scope - Application launched by gnome-shell. Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.167' (uid=1000 pid=10927 comm="/usr/bin/gnome-terminal.real" label="unconfined") Jun 08 11:16:29 CCW-HAL systemd[3523]: Starting gnome-terminal-server.service - GNOME Terminal Server... Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] Successfully activated service 'org.gnome.Terminal' Jun 08 11:16:29 CCW-HAL systemd[3523]: Started gnome-terminal-server.service - GNOME Terminal Server. Jun 08 11:16:29 CCW-HAL systemd[3523]: Started vte-spawn-9cee1911-372a-4bb4-8b57-694984e43990.scope - VTE child process 10955 launched by gnome-terminal-server process 10931. Jun 08 11:16:49 CCW-HAL gnome-control-c[8079]: Error showing account: Child process exited with code 1 Jun 08 11:16:53 CCW-HAL gnome-online-accounts-panel.desktop[9764]: GLib-GIO: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)GLib-GIO: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’GLib: unsetenv() is not thread-safe and should not be used after threads are createdGLib-GIO: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’GoaBackend: Loading all providers: GoaBackend: - googleGoaBackend: - owncloudGoaBackend: - windows_liveGoaBackend: - exchangeGoaBackend: - lastfmGoaBackend: - imap_smtpGoaBackend: - kerberosGoaBackend: activated kerberos providerGLib-GIO: _g_io_module_get_default: Found default implementation gnutls (GTlsBackendGnutls) for ‘gio-tls-backend’Failed to create account: Dialog was dismissed Jun 08 11:16:53 CCW-HAL xdg-desktop-por[3907]: Realtime error: Could not map pid: Could not determine pid namespace: Could not find instance-id in process's /.flatpak-info Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0) Jun 08 11:17:01 CCW-HAL CRON[11094]: (root) CMD (cd / && run-parts --report /etc/cron.hourly) Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session closed for user root Jun 08 11:17:06 CCW-HAL kernel: WebKitWebProces[11026]: segfault at 55bd22ad9adc ip 55bd22ad9adc sp 7ffd1f6adbe8 error 14 likely on CPU 2 (core 2, socket 0) Jun 08 11:17:06 CCW-HAL kernel: Code: Unable to access opcode bytes at 0x55bd22ad9ab2. Jun 08 11:17:36 CCW-HAL gnome-shell[3803]: Window manager warning: WM_TRANSIENT_FOR window 0x3a02767 for 0x3a02778 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x3a006dc. Jun 08 11:17:42 CCW-HAL systemd[1]: Starting systemd-tmpfiles-clean.service - Cleanup of Temporary Directories... Jun 08 11:17:42 CCW-HAL systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully. Jun 08 11:17:42 CCW-HAL systemd[1]: Finished systemd-tmpfiles-clean.service - Cleanup of
[Desktop-packages] [Bug 2018163] Re: Ctrl+click no longer allows multiple files to be selected in the file upload window after upgrade to Lunar
Switching the package to name the culprit rather than the program with symptoms. ** Package changed: xdg-desktop-portal-gnome (Ubuntu) => libadwaita-1 (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libadwaita-1 in Ubuntu. https://bugs.launchpad.net/bugs/2018163 Title: Ctrl+click no longer allows multiple files to be selected in the file upload window after upgrade to Lunar Status in libadwaita-1 package in Ubuntu: Fix Committed Bug description: When uploading a file anywhere, using ctrl+click allows you to select more than one file at a time to upload several things in one go. After upgrading to Lunar, this no longer works. Shift+click still works for uploading multiple consecutive files in a list, but if they are needed in a certain order or not sitting one after another, you can no longer select them all by holding ctrl. It's only letting me select one file at a time. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xdg-desktop-portal-gnome 44~beta-1ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Apr 29 15:42:41 2023 ExecutablePath: /usr/libexec/xdg-desktop-portal-gnome InstallationDate: Installed on 2022-07-09 (294 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: xdg-desktop-portal-gnome UpgradeStatus: Upgraded to lunar on 2023-04-26 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libadwaita-1/+bug/2018163/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2021906] Re: webkit2gtk 2.40.2 fails to build on riscv64
** Changed in: webkit2gtk (Debian) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/2021906 Title: webkit2gtk 2.40.2 fails to build on riscv64 Status in webkit2gtk package in Ubuntu: Fix Released Status in webkit2gtk package in Debian: Fix Released Bug description: webkit2gtk 2.40.2 fails to build on riscv64 because bubblewrap support is disabled in debian/rules but the upstream build system appears to have a bug in disabling it. See the attached Debian bug. /<>/Source/WTF/wtf/glib/Sandbox.cpp:49:13: error: ‘BWRAP_EXECUTABLE’ was not declared in this scope 49 | BWRAP_EXECUTABLE, | ^~~~ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/2021906/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2023322] Re: Unable to setup Google Online Accounts with Nvidia drivers
In that case please try reproducing the bug again and then repeat the steps in comment #7. ** Tags added: nvidia -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/2023322 Title: Unable to setup Google Online Accounts with Nvidia drivers Status in gnome-control-center: Fix Released Status in Webkit: Confirmed Status in gnome-control-center package in Ubuntu: Triaged Status in gnome-online-accounts package in Ubuntu: Triaged Status in webkit2gtk package in Ubuntu: Incomplete Status in webkit2gtk package in Debian: New Bug description: When I go into Settings > Online Accounts > Google, I get to the prompt for email address, once in a while it stops accepting input there. But often I can get to the password screen. Once I do, I can't type anything or paste anything. This is a fresh install of Ubuntu 23.04 and I have installed all updates. Nothing in /var/crash Jun 08 11:15:59 CCW-HAL systemd[3523]: vte-spawn-8b4a59a3-a060-4bdd-92e6-285656bdb9a2.scope: Consumed 3.448s CPU time. Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:29 CCW-HAL systemd[3523]: Started app-gnome-org.gnome.Terminal-10924.scope - Application launched by gnome-shell. Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.167' (uid=1000 pid=10927 comm="/usr/bin/gnome-terminal.real" label="unconfined") Jun 08 11:16:29 CCW-HAL systemd[3523]: Starting gnome-terminal-server.service - GNOME Terminal Server... Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] Successfully activated service 'org.gnome.Terminal' Jun 08 11:16:29 CCW-HAL systemd[3523]: Started gnome-terminal-server.service - GNOME Terminal Server. Jun 08 11:16:29 CCW-HAL systemd[3523]: Started vte-spawn-9cee1911-372a-4bb4-8b57-694984e43990.scope - VTE child process 10955 launched by gnome-terminal-server process 10931. Jun 08 11:16:49 CCW-HAL gnome-control-c[8079]: Error showing account: Child process exited with code 1 Jun 08 11:16:53 CCW-HAL gnome-online-accounts-panel.desktop[9764]: GLib-GIO: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)GLib-GIO: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’GLib: unsetenv() is not thread-safe and should not be used after threads are createdGLib-GIO: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’GoaBackend: Loading all providers: GoaBackend: - googleGoaBackend: - owncloudGoaBackend: - windows_liveGoaBackend: - exchangeGoaBackend: - lastfmGoaBackend: - imap_smtpGoaBackend: - kerberosGoaBackend: activated kerberos providerGLib-GIO: _g_io_module_get_default: Found default implementation gnutls (GTlsBackendGnutls) for ‘gio-tls-backend’Failed to create account: Dialog was dismissed Jun 08 11:16:53 CCW-HAL xdg-desktop-por[3907]: Realtime error: Could not map pid: Could not determine pid namespace: Could not find instance-id in process's /.flatpak-info Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0) Jun 08 11:17:01 CCW-HAL CRON[11094]: (root) CMD (cd / && run-parts --report /etc/cron.hourly) Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session closed for user root Jun 08 11:17:06 CCW-HAL kernel: WebKitWebProces[11026]: segfault at 55bd22ad9adc ip 55bd22ad9adc sp 7ffd1f6adbe8 error 14 likely on CPU 2 (core 2, socket 0) Jun 08 11:17:06 CCW-HAL kernel: Code: Unable to access opcode bytes at 0x55bd22ad9ab2. Jun 08 11:17:36 CCW-HAL gnome-shell[3803]: Window manager warning: WM_TRANSIENT_FOR window 0x3a02767 for 0x3a02778 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x3a006dc. Jun 08 11:17:42 CCW-HAL systemd[1]: Starting systemd-tmpfiles-clean.service - Cleanup of Temporary Directories... Jun 08 11:17:42 CCW-HAL systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully. Jun 08 11:17:42 CCW-HAL systemd[1]: Finished systemd-tmpfiles-clean.service - Cleanup of Temporary Directories. Jun 08 11:17:42 CCW-HAL systemd[1]: run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated successfully. Jun 08 11:18:10 CCW-HAL gnome-shell[3803]: Window manager warning: WM_TRANSIENT_FOR window 0x3a029e2 for 0x3a029f0 window override-redirect is an
[Desktop-packages] [Bug 2023322] Re: Unable to setup Google Online Accounts with Nvidia drivers
Launchpad has imported 51 comments from the remote bug at https://bugs.webkit.org/show_bug.cgi?id=228268. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2021-07-24T22:00:53+00:00 Emil Sayahi wrote: Hello! This is my first time submitting a bug report, so apologies if I'm not as helpful as I should be. I'm currently successfully building `libwebkitgtk-5.0`, and I've embedded it as part of developing a new browser project. I was originally using the stable release of WebKitGTK from the Arch Linux package repositories, but as part of porting my browser to GTK4 I've had to recompile the library myself for GTK4 support (here's the script I wrote to do this: https://raw.githubusercontent.com/Dirout/oku/50c1bd443ac50943b359b16e9d3a140faa604c89/build-dependencies.sh) Presently, this build of WebKitGTK is completely blank—no content or developer tools menu elements visible—unless I select and drag something offscreen, at which point it becomes visible until I let go of the mouse again. Perhaps this rendering bug is connected to the fact that I have an Nvidia GPU? I'll need to do further testing on an old laptop I have somewhere. Additionally, almost all page loads fail while emitting any of the following warnings: ``` (process:70483): GLib-Net-WARNING **: 17:44:39.051: ../glib-networking/tls/gnutls/gtlscertificate-gnutls.c:161: invalid property id 3 for "private-key" of type 'GParamBoxed' in 'GTlsCertificateGnutls' (process:67609): GLib-GIO-WARNING **: 17:13:47.931: ../subprojects/glib/gio/gtlsconnection.c:397: invalid property id 12 for "protocol-version" of type 'GParamEnum' in 'GTlsClientConnectionGnutls' (process:67609): GLib-GIO-WARNING **: 17:13:47.931: ../subprojects/glib/gio/gtlsconnection.c:397: invalid property id 13 for "ciphersuite-name" of type 'GParamString' in 'GTlsClientConnectionGnutls' ``` In the browser, the page contents simply are 'Error reading data from TLS socket: The specified session has been invalidated for some reason.' or, sometimes, 'Could not parse HTTP response'. This is not always reproducible, sometimes, rarely, page loads just randomly work, but 99% of the time they don't. I've tried Google, YouTube, Reddit, 'https://example.com', and 'https://www.iana.org/domains/reserved'. My best guess is that this is some bug introduced in `libsoup-3.0`, maybe in its `glib` dependency? I had to recompile `libsoup` as well, for the same reasons I had to recompile WebKitGTK. My biggest concern, by far, is the visibility issue. It does appear that things are being rendered, it's just pure white unless I drag things away with my mouse. To be clear, every other GUI element of my GTK app is visible and working properly, it's just the WebView which is experiencing this. I'm running Arch Linux with GNOME DE, X11 (because Nvidia GPU), using proprietary Nvidia drivers, with all installed packages up-to-date. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-online- accounts/+bug/2023322/comments/0 On 2021-07-25T00:18:40+00:00 Emil Sayahi wrote: Ah, interesting. I've discovered the rendering isn't actually pure white, but slightly darker. I ramped up my Night Shift intensity in the GNOME settings app, and I can slightly make out some text from the WebView in a very light grey. The developer tools, accessed from the 'Inspect Element' context menu option, are completely invisible, however. Context menus, like the rest of the GTK elements, appear to be working just fine. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-online- accounts/+bug/2023322/comments/1 On 2021-07-25T03:45:58+00:00 Emil Sayahi wrote: I've made a discovery regarding the page loading failure. Based on the errors, I guessed it was an issue with HTTPS. I've been able to connect to 'http://neverssl.com/' and 'http://example.com' (as opposed to the https version) consistently. I'm now updating the bug report title to mention this issue Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-online- accounts/+bug/2023322/comments/2 On 2021-07-25T18:02:26+00:00 Mcatanzaro-c wrote: (In reply to Emil Sayahi from comment #0) > Additionally, almost all page loads fail while emitting any of the following > warnings: > ``` > (process:70483): GLib-Net-WARNING **: 17:44:39.051: > ../glib-networking/tls/gnutls/gtlscertificate-gnutls.c:161: invalid property > id 3 for "private-key" of type 'GParamBoxed' in 'GTlsCertificateGnutls' > > (process:67609): GLib-GIO-WARNING **: 17:13:47.931: >
[Desktop-packages] [Bug 2023322] Re: Unable to setup Google Online Accounts with Nvidia drivers
Nothing in /var/crash. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/2023322 Title: Unable to setup Google Online Accounts with Nvidia drivers Status in gnome-control-center: Fix Released Status in Webkit: Unknown Status in gnome-control-center package in Ubuntu: Triaged Status in gnome-online-accounts package in Ubuntu: Triaged Status in webkit2gtk package in Ubuntu: Incomplete Status in webkit2gtk package in Debian: New Bug description: When I go into Settings > Online Accounts > Google, I get to the prompt for email address, once in a while it stops accepting input there. But often I can get to the password screen. Once I do, I can't type anything or paste anything. This is a fresh install of Ubuntu 23.04 and I have installed all updates. Nothing in /var/crash Jun 08 11:15:59 CCW-HAL systemd[3523]: vte-spawn-8b4a59a3-a060-4bdd-92e6-285656bdb9a2.scope: Consumed 3.448s CPU time. Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:29 CCW-HAL systemd[3523]: Started app-gnome-org.gnome.Terminal-10924.scope - Application launched by gnome-shell. Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.167' (uid=1000 pid=10927 comm="/usr/bin/gnome-terminal.real" label="unconfined") Jun 08 11:16:29 CCW-HAL systemd[3523]: Starting gnome-terminal-server.service - GNOME Terminal Server... Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] Successfully activated service 'org.gnome.Terminal' Jun 08 11:16:29 CCW-HAL systemd[3523]: Started gnome-terminal-server.service - GNOME Terminal Server. Jun 08 11:16:29 CCW-HAL systemd[3523]: Started vte-spawn-9cee1911-372a-4bb4-8b57-694984e43990.scope - VTE child process 10955 launched by gnome-terminal-server process 10931. Jun 08 11:16:49 CCW-HAL gnome-control-c[8079]: Error showing account: Child process exited with code 1 Jun 08 11:16:53 CCW-HAL gnome-online-accounts-panel.desktop[9764]: GLib-GIO: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)GLib-GIO: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’GLib: unsetenv() is not thread-safe and should not be used after threads are createdGLib-GIO: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’GoaBackend: Loading all providers: GoaBackend: - googleGoaBackend: - owncloudGoaBackend: - windows_liveGoaBackend: - exchangeGoaBackend: - lastfmGoaBackend: - imap_smtpGoaBackend: - kerberosGoaBackend: activated kerberos providerGLib-GIO: _g_io_module_get_default: Found default implementation gnutls (GTlsBackendGnutls) for ‘gio-tls-backend’Failed to create account: Dialog was dismissed Jun 08 11:16:53 CCW-HAL xdg-desktop-por[3907]: Realtime error: Could not map pid: Could not determine pid namespace: Could not find instance-id in process's /.flatpak-info Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0) Jun 08 11:17:01 CCW-HAL CRON[11094]: (root) CMD (cd / && run-parts --report /etc/cron.hourly) Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session closed for user root Jun 08 11:17:06 CCW-HAL kernel: WebKitWebProces[11026]: segfault at 55bd22ad9adc ip 55bd22ad9adc sp 7ffd1f6adbe8 error 14 likely on CPU 2 (core 2, socket 0) Jun 08 11:17:06 CCW-HAL kernel: Code: Unable to access opcode bytes at 0x55bd22ad9ab2. Jun 08 11:17:36 CCW-HAL gnome-shell[3803]: Window manager warning: WM_TRANSIENT_FOR window 0x3a02767 for 0x3a02778 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x3a006dc. Jun 08 11:17:42 CCW-HAL systemd[1]: Starting systemd-tmpfiles-clean.service - Cleanup of Temporary Directories... Jun 08 11:17:42 CCW-HAL systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully. Jun 08 11:17:42 CCW-HAL systemd[1]: Finished systemd-tmpfiles-clean.service - Cleanup of Temporary Directories. Jun 08 11:17:42 CCW-HAL systemd[1]: run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated successfully. Jun 08 11:18:10 CCW-HAL gnome-shell[3803]: Window manager warning: WM_TRANSIENT_FOR window 0x3a029e2 for 0x3a029f0 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll
[Desktop-packages] [Bug 2023322] Re: Unable to setup Google Online Accounts with Nvidia drivers
https://errors.ubuntu.com/user/71bccc9eec8b281afbf94f22b6f69c64a37ecb7e24b101ec466be8c2cd4977590e029bded41a9364d90f45402e96cb8f3c33b48ae17febc41fc2a442a21d0ece -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/2023322 Title: Unable to setup Google Online Accounts with Nvidia drivers Status in gnome-control-center: Fix Released Status in Webkit: Unknown Status in gnome-control-center package in Ubuntu: Triaged Status in gnome-online-accounts package in Ubuntu: Triaged Status in webkit2gtk package in Ubuntu: Incomplete Status in webkit2gtk package in Debian: New Bug description: When I go into Settings > Online Accounts > Google, I get to the prompt for email address, once in a while it stops accepting input there. But often I can get to the password screen. Once I do, I can't type anything or paste anything. This is a fresh install of Ubuntu 23.04 and I have installed all updates. Nothing in /var/crash Jun 08 11:15:59 CCW-HAL systemd[3523]: vte-spawn-8b4a59a3-a060-4bdd-92e6-285656bdb9a2.scope: Consumed 3.448s CPU time. Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:29 CCW-HAL systemd[3523]: Started app-gnome-org.gnome.Terminal-10924.scope - Application launched by gnome-shell. Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.167' (uid=1000 pid=10927 comm="/usr/bin/gnome-terminal.real" label="unconfined") Jun 08 11:16:29 CCW-HAL systemd[3523]: Starting gnome-terminal-server.service - GNOME Terminal Server... Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] Successfully activated service 'org.gnome.Terminal' Jun 08 11:16:29 CCW-HAL systemd[3523]: Started gnome-terminal-server.service - GNOME Terminal Server. Jun 08 11:16:29 CCW-HAL systemd[3523]: Started vte-spawn-9cee1911-372a-4bb4-8b57-694984e43990.scope - VTE child process 10955 launched by gnome-terminal-server process 10931. Jun 08 11:16:49 CCW-HAL gnome-control-c[8079]: Error showing account: Child process exited with code 1 Jun 08 11:16:53 CCW-HAL gnome-online-accounts-panel.desktop[9764]: GLib-GIO: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)GLib-GIO: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’GLib: unsetenv() is not thread-safe and should not be used after threads are createdGLib-GIO: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’GoaBackend: Loading all providers: GoaBackend: - googleGoaBackend: - owncloudGoaBackend: - windows_liveGoaBackend: - exchangeGoaBackend: - lastfmGoaBackend: - imap_smtpGoaBackend: - kerberosGoaBackend: activated kerberos providerGLib-GIO: _g_io_module_get_default: Found default implementation gnutls (GTlsBackendGnutls) for ‘gio-tls-backend’Failed to create account: Dialog was dismissed Jun 08 11:16:53 CCW-HAL xdg-desktop-por[3907]: Realtime error: Could not map pid: Could not determine pid namespace: Could not find instance-id in process's /.flatpak-info Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0) Jun 08 11:17:01 CCW-HAL CRON[11094]: (root) CMD (cd / && run-parts --report /etc/cron.hourly) Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session closed for user root Jun 08 11:17:06 CCW-HAL kernel: WebKitWebProces[11026]: segfault at 55bd22ad9adc ip 55bd22ad9adc sp 7ffd1f6adbe8 error 14 likely on CPU 2 (core 2, socket 0) Jun 08 11:17:06 CCW-HAL kernel: Code: Unable to access opcode bytes at 0x55bd22ad9ab2. Jun 08 11:17:36 CCW-HAL gnome-shell[3803]: Window manager warning: WM_TRANSIENT_FOR window 0x3a02767 for 0x3a02778 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x3a006dc. Jun 08 11:17:42 CCW-HAL systemd[1]: Starting systemd-tmpfiles-clean.service - Cleanup of Temporary Directories... Jun 08 11:17:42 CCW-HAL systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully. Jun 08 11:17:42 CCW-HAL systemd[1]: Finished systemd-tmpfiles-clean.service - Cleanup of Temporary Directories. Jun 08 11:17:42 CCW-HAL systemd[1]: run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated successfully. Jun 08 11:18:10 CCW-HAL gnome-shell[3803]: Window manager warning: WM_TRANSIENT_FOR window 0x3a029e2
[Desktop-packages] [Bug 2025308] Re: package appstream 0.15.2-2 failed to install/upgrade: installed appstream package post-installation script subprocess returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/2025308 Title: package appstream 0.15.2-2 failed to install/upgrade: installed appstream package post-installation script subprocess returned error exit status 1 Status in appstream package in Ubuntu: New Bug description: unknown ProblemType: Package DistroRelease: Ubuntu 22.04 Package: appstream 0.15.2-2 Uname: Linux 5.10.104-tegra aarch64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: arm64 CasperMD5CheckResult: unknown Date: Wed Jun 28 21:47:23 2023 ErrorMessage: installed appstream package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python3.10, Python 3.10.6, python-is-python3, 3.9.2-2 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 SourcePackage: appstream Title: package appstream 0.15.2-2 failed to install/upgrade: installed appstream package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2023-06-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/2025308/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2025308] [NEW] package appstream 0.15.2-2 failed to install/upgrade: installed appstream package post-installation script subprocess returned error exit status 1
Public bug reported: unknown ProblemType: Package DistroRelease: Ubuntu 22.04 Package: appstream 0.15.2-2 Uname: Linux 5.10.104-tegra aarch64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: arm64 CasperMD5CheckResult: unknown Date: Wed Jun 28 21:47:23 2023 ErrorMessage: installed appstream package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python3.10, Python 3.10.6, python-is-python3, 3.9.2-2 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 SourcePackage: appstream Title: package appstream 0.15.2-2 failed to install/upgrade: installed appstream package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2023-06-29 (0 days ago) ** Affects: appstream (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package arm64 jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/2025308 Title: package appstream 0.15.2-2 failed to install/upgrade: installed appstream package post-installation script subprocess returned error exit status 1 Status in appstream package in Ubuntu: New Bug description: unknown ProblemType: Package DistroRelease: Ubuntu 22.04 Package: appstream 0.15.2-2 Uname: Linux 5.10.104-tegra aarch64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: arm64 CasperMD5CheckResult: unknown Date: Wed Jun 28 21:47:23 2023 ErrorMessage: installed appstream package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python3.10, Python 3.10.6, python-is-python3, 3.9.2-2 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 SourcePackage: appstream Title: package appstream 0.15.2-2 failed to install/upgrade: installed appstream package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2023-06-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/2025308/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2023322] Re: Unable to setup Google Online Accounts with Nvidia drivers
The main issue here looks like: Jun 08 11:17:06 CCW-HAL kernel: WebKitWebProces[11026]: segfault at 55bd22ad9adc ip 55bd22ad9adc sp 7ffd1f6adbe8 error 14 likely on CPU 2 (core 2, socket 0) even though that doesn't sound the same as the upstream bugs. Maybe we'll need to detach those... To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Bug watch added: bugs.webkit.org/ #228268 https://bugs.webkit.org/show_bug.cgi?id=228268 ** Also affects: webkit via https://bugs.webkit.org/show_bug.cgi?id=228268 Importance: Unknown Status: Unknown ** Changed in: webkit2gtk (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/2023322 Title: Unable to setup Google Online Accounts with Nvidia drivers Status in gnome-control-center: Fix Released Status in Webkit: Unknown Status in gnome-control-center package in Ubuntu: Triaged Status in gnome-online-accounts package in Ubuntu: Triaged Status in webkit2gtk package in Ubuntu: Incomplete Status in webkit2gtk package in Debian: New Bug description: When I go into Settings > Online Accounts > Google, I get to the prompt for email address, once in a while it stops accepting input there. But often I can get to the password screen. Once I do, I can't type anything or paste anything. This is a fresh install of Ubuntu 23.04 and I have installed all updates. Nothing in /var/crash Jun 08 11:15:59 CCW-HAL systemd[3523]: vte-spawn-8b4a59a3-a060-4bdd-92e6-285656bdb9a2.scope: Consumed 3.448s CPU time. Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:29 CCW-HAL systemd[3523]: Started app-gnome-org.gnome.Terminal-10924.scope - Application launched by gnome-shell. Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.167' (uid=1000 pid=10927 comm="/usr/bin/gnome-terminal.real" label="unconfined") Jun 08 11:16:29 CCW-HAL systemd[3523]: Starting gnome-terminal-server.service - GNOME Terminal Server... Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] Successfully activated service 'org.gnome.Terminal' Jun 08 11:16:29 CCW-HAL systemd[3523]: Started gnome-terminal-server.service - GNOME Terminal Server. Jun 08 11:16:29 CCW-HAL systemd[3523]: Started vte-spawn-9cee1911-372a-4bb4-8b57-694984e43990.scope - VTE child process 10955 launched by gnome-terminal-server process 10931. Jun 08 11:16:49 CCW-HAL gnome-control-c[8079]: Error showing account: Child process exited with code 1 Jun 08 11:16:53 CCW-HAL gnome-online-accounts-panel.desktop[9764]: GLib-GIO: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)GLib-GIO: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’GLib: unsetenv() is not thread-safe and should not be used after threads are createdGLib-GIO: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’GoaBackend: Loading all providers: GoaBackend: - googleGoaBackend: - owncloudGoaBackend: - windows_liveGoaBackend: - exchangeGoaBackend: - lastfmGoaBackend: - imap_smtpGoaBackend: - kerberosGoaBackend: activated kerberos providerGLib-GIO: _g_io_module_get_default: Found default implementation gnutls (GTlsBackendGnutls) for ‘gio-tls-backend’Failed to create account: Dialog was dismissed Jun 08 11:16:53 CCW-HAL xdg-desktop-por[3907]: Realtime error: Could not map pid: Could not determine pid namespace: Could not find instance-id in process's /.flatpak-info Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0) Jun 08 11:17:01 CCW-HAL CRON[11094]: (root) CMD (cd / && run-parts --report /etc/cron.hourly) Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session closed for user root Jun 08 11:17:06 CCW-HAL kernel: WebKitWebProces[11026]: segfault at 55bd22ad9adc
[Desktop-packages] [Bug 1971984] Re: pcscd.socket is disabled after installation
I uploaded this the other day and its now waiting review from an SRU team member. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1971984 Title: pcscd.socket is disabled after installation Status in pcsc-lite package in Ubuntu: Fix Released Status in pcsc-lite source package in Jammy: In Progress Status in pcsc-lite source package in Kinetic: In Progress Status in pcsc-lite source package in Lunar: In Progress Status in pcsc-lite package in Debian: Fix Released Bug description: [ Impact ] The pscc-lite package provides an open source implementation of PC/SC, the de-facto standard to interface Personal Computers with Smart Cards/Readers. This bug is in the upstream debian packaging, and results in the pcscd.socket being disabled after installation. This prevents automatic startup of the associated pcscd.service, thus preventing automatic handling of Smart Cards/Readers w/out manual intervention to enable the socket (which doesn't persist across reboots). This is especially painful for users that require Smart Authentication for login. [ Test Plan ] Steps to reproduce: 1. If installed, remove and do a fresh install of the package pcscd (the sole version released for jammy is 1.9.5-3). 2. Verify that the pcscd.socket is disabled: $ systemctl status pcscd.socket ○ pcscd.socket - PC/SC Smart Card Daemon Activation Socket Loaded: loaded (/lib/systemd/system/pcscd.socket; disabled; vendor preset: enabled) Active: inactive (dead) Triggers: ● pcscd.service Listen: /run/pcscd/pcscd.comm (Stream) 3. [Optional] insert a Smart Card or Crypto Token (e.g. a Yubikey or Nitrokey) that's known to work on Ubuntu and verify that it fails to work. Repeating the same steps with a package built with the patch attached to comment #27 should ensure that the socket is enabled, and that interaction with a Smart Card or Crypto Token should work w/out manual intervention. [ Where problems could occur ] This is a back-ported change from upstream and is a result of a bug in dh_installsystemd (see comment #26). As such the risk is minimal. The only potential risk of failure I can come up with is a snap that stages the old version of the client library, as it would be looking in the wrong place for the socket. [ Other Info ] This bug was originally reported against Ubuntu Mate 22.04, however it applies to all derivatives of Ubuntu Desktop 22.04 LTS. Note - while there's some disagreement as to whether this bug occurs 100% of the time across all 22.04 installations, it's pretty clear from the upstream Debian bug and subsequent packaging fix that we should land this. As the upstream fix landed in 1.9.9-2 (which is already released in mantic) only the following releases are impacted by this bug: - jammy - kinetic - lunar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2025299] Re: Firefox 115.0+build1-0ubuntu0.18.04.1~mt1 - Unity Global Menu Missing
** Package changed: ubuntu => firefox (Ubuntu) ** Tags added: bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2025299 Title: Firefox 115.0+build1-0ubuntu0.18.04.1~mt1 - Unity Global Menu Missing Status in firefox package in Ubuntu: New Bug description: Please accept my apologies if this is the incorrect place to submit this bug. Using Ubuntu 18.04 ESR (Unity Desktop). Upon upgrade from Firefox 114 to 115 noticed that the Unity Global Menu no longer works. Rolling back the package to 114 and installing 102.12 ESR global menu works as expected. This is the package that is on the mozillateam PPA. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2025299/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2025268] Re: firefox geckodriver in snap does not work
refreshed snap and update version of selenium to 4.10 (initially was
4.9), looks to work now
even no need to TMP anymore, just works as it should be
see example https://github.com/beliaev-maksim/firefox-selenium
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/2025268
Title:
firefox geckodriver in snap does not work
Status in firefox package in Ubuntu:
New
Bug description:
once trying to connect to geckodriver from selenium get:
```
Traceback (most recent call last):
File
"/home/maksim/git/kubeflow/bundle-kubeflow/tests-bundle/1.7/conftest.py", line
38, in driver
driver = webdriver.Firefox(options=options, service=service)
File
"/home/maksim/git/kubeflow/bundle-kubeflow/venv/lib/python3.10/site-packages/selenium/webdriver/firefox/webdriver.py",
line 196, in __init__
self.service.start()
File
"/home/maksim/git/kubeflow/bundle-kubeflow/venv/lib/python3.10/site-packages/selenium/webdriver/common/service.py",
line 100, in start
self.assert_process_still_running()
File
"/home/maksim/git/kubeflow/bundle-kubeflow/venv/lib/python3.10/site-packages/selenium/webdriver/common/service.py",
line 113, in assert_process_still_running
raise WebDriverException(f"Service {self._path} unexpectedly exited.
Status code was: {return_code}")
selenium.common.exceptions.WebDriverException: Message: Service
/snap/bin/firefox.geckodriver unexpectedly exited. Status code was: -6
```
here is a code to reproduce (see lines to toggle with comment `#
toggle lines to reproduce`). Create conftest.py with content
```
import os
import time
from datetime import datetime
from pathlib import Path
import pytest
from selenium import webdriver
from selenium.webdriver.firefox.options import Options
from selenium.webdriver.firefox.service import Service
from webdriver_manager.firefox import GeckoDriverManager
DEBUG = os.environ.get("DEBUG_KF", False)
@pytest.fixture(scope='session')
def driver(request):
"""Set up webdriver fixture."""
options = Options()
if not DEBUG:
print("Running in headless mode")
options.add_argument('--headless')
options.add_argument('--disable-gpu')
else:
options.log.level = "trace"
options.add_argument('--no-sandbox')
options.add_argument('--disable-dev-shm-usage')
options.binary_location = "/snap/bin/firefox"
# must create path,
# see https://github.com/mozilla/geckodriver/releases/tag/v0.31.0
tmp_user = Path("~/tmp").expanduser()
os.environ["TMPDIR"] = str(tmp_user)
tmp_user.mkdir(parents=True, exist_ok=True)
# toggle lines to reproduce
service = Service(GeckoDriverManager().install())
service = Service(executable_path="firefox.geckodriver")
driver = webdriver.Firefox(options=options, service=service)
driver.set_window_size(1920, 1080)
driver.maximize_window()
driver.implicitly_wait(10)
yield driver
driver.quit()
```
and test_driver.py with
```
def test_1(driver):
driver.get("https://google.de;)
a = 1
```
firefox --version
Mozilla Firefox 113.0.2
pip freeze:
absl-py==1.4.0
anyio==3.6.2
asttokens==2.2.1
async-generator==1.10
attrs==22.2.0
backcall==0.2.0
bcrypt==4.0.1
cachetools==5.3.0
certifi==2022.12.7
cffi==1.15.1
charset-normalizer==3.1.0
click==7.1.2
cloudpickle==2.2.1
cryptography==40.0.1
decorator==5.1.1
Deprecated==1.2.13
docstring-parser==0.15
exceptiongroup==1.1.1
executing==1.2.0
fire==0.5.0
google-api-core==2.11.0
google-api-python-client==1.12.11
google-auth==2.17.2
google-auth-httplib2==0.1.0
google-cloud-core==2.3.2
google-cloud-storage==2.8.0
google-crc32c==1.5.0
google-resumable-media==2.4.1
googleapis-common-protos==1.59.0
h11==0.14.0
httpcore==0.16.3
httplib2==0.22.0
httpx==0.23.3
hvac==1.1.0
idna==3.4
iniconfig==2.0.0
ipdb==0.13.13
ipython==8.12.0
jedi==0.18.2
Jinja2==3.1.2
jsonschema==4.17.3
juju==2.9.42.1
jujubundlelib==0.5.7
kfp==1.8.19
kfp-pipeline-spec==0.1.16
kfp-server-api==1.8.5
kubernetes==19.15.0
lightkube==0.12.0
lightkube-models==1.26.0.4
macaroonbakery==1.3.1
MarkupSafe==2.1.2
matplotlib-inline==0.1.6
mypy-extensions==1.0.0
oauthlib==3.2.2
outcome==1.2.0
packaging==23.0
paramiko==2.12.0
parso==0.8.3
pexpect==4.8.0
pickleshare==0.7.5
pluggy==1.0.0
prompt-toolkit==3.0.38
protobuf==3.20.3
psutil==5.9.5
ptyprocess==0.7.0
pure-eval==0.2.2
pyasn1==0.4.8
pyasn1-modules==0.2.8
pycparser==2.21
pydantic==1.10.7
Pygments==2.14.0
pyhcl==0.4.4
pymacaroons==0.13.0
PyNaCl==1.5.0
pyparsing==3.0.9
pyRFC3339==1.1
pyrsistent==0.19.3
PySocks==1.7.1
pytest==7.2.2
pytest-asyncio==0.21.0
pytest-dependency==0.5.1
pytest-operator==0.26.0
[Desktop-packages] [Bug 2025290] Re: user-accounts: GFileInfo created without standard::symlink-target
** 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/2025290 Title: user-accounts: GFileInfo created without standard::symlink-target Status in gnome-control-center: New Status in gnome-control-center package in Ubuntu: Triaged Bug description: If I open g-c-c from terminal on an updated mantic install and switch to the Users panel, I see some warning messages (see attachment). I don't know the significance of it, but it does not look right... ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-control-center 1:44.1-1ubuntu1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 28 20:55:07 2023 InstallationDate: Installed on 2022-05-07 (416 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to mantic on 2023-06-20 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/2025290/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2025268] Re: firefox geckodriver in snap does not work
On Ubuntu 23.04 with Firefox snap 114.0.1 and its geckodriver 0.33, I
put the above two files in a new directory, then ran
python3 -m venv venv
. venv/bin/activate
pip3 install selenium webdriver-manager
pytest test_driver.py
The run failed with the following error:
ERROR test_driver.py::test_1 -
selenium.common.exceptions.InvalidArgumentException: Message: binary is
not a Firefox executable
Per
https://github.com/mozilla/geckodriver/issues/2010#issuecomment-1116203839,
setting options.binary_location =
"/snap/firefox/current/firefox.launcher" fixed it and the test passed.
I believe this is the default in recent versions, so just not setting
options.binary_location worked as well.
I then tried commenting out the ~/tmp directory creation bit, as well as
toggling between the two 'service' assignments, and in every case the
test continued to pass.
Are you using a recent Firefox snap (and its geckodriver) version?
** Bug watch added: github.com/mozilla/geckodriver/issues #2010
https://github.com/mozilla/geckodriver/issues/2010
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/2025268
Title:
firefox geckodriver in snap does not work
Status in firefox package in Ubuntu:
New
Bug description:
once trying to connect to geckodriver from selenium get:
```
Traceback (most recent call last):
File
"/home/maksim/git/kubeflow/bundle-kubeflow/tests-bundle/1.7/conftest.py", line
38, in driver
driver = webdriver.Firefox(options=options, service=service)
File
"/home/maksim/git/kubeflow/bundle-kubeflow/venv/lib/python3.10/site-packages/selenium/webdriver/firefox/webdriver.py",
line 196, in __init__
self.service.start()
File
"/home/maksim/git/kubeflow/bundle-kubeflow/venv/lib/python3.10/site-packages/selenium/webdriver/common/service.py",
line 100, in start
self.assert_process_still_running()
File
"/home/maksim/git/kubeflow/bundle-kubeflow/venv/lib/python3.10/site-packages/selenium/webdriver/common/service.py",
line 113, in assert_process_still_running
raise WebDriverException(f"Service {self._path} unexpectedly exited.
Status code was: {return_code}")
selenium.common.exceptions.WebDriverException: Message: Service
/snap/bin/firefox.geckodriver unexpectedly exited. Status code was: -6
```
here is a code to reproduce (see lines to toggle with comment `#
toggle lines to reproduce`). Create conftest.py with content
```
import os
import time
from datetime import datetime
from pathlib import Path
import pytest
from selenium import webdriver
from selenium.webdriver.firefox.options import Options
from selenium.webdriver.firefox.service import Service
from webdriver_manager.firefox import GeckoDriverManager
DEBUG = os.environ.get("DEBUG_KF", False)
@pytest.fixture(scope='session')
def driver(request):
"""Set up webdriver fixture."""
options = Options()
if not DEBUG:
print("Running in headless mode")
options.add_argument('--headless')
options.add_argument('--disable-gpu')
else:
options.log.level = "trace"
options.add_argument('--no-sandbox')
options.add_argument('--disable-dev-shm-usage')
options.binary_location = "/snap/bin/firefox"
# must create path,
# see https://github.com/mozilla/geckodriver/releases/tag/v0.31.0
tmp_user = Path("~/tmp").expanduser()
os.environ["TMPDIR"] = str(tmp_user)
tmp_user.mkdir(parents=True, exist_ok=True)
# toggle lines to reproduce
service = Service(GeckoDriverManager().install())
service = Service(executable_path="firefox.geckodriver")
driver = webdriver.Firefox(options=options, service=service)
driver.set_window_size(1920, 1080)
driver.maximize_window()
driver.implicitly_wait(10)
yield driver
driver.quit()
```
and test_driver.py with
```
def test_1(driver):
driver.get("https://google.de;)
a = 1
```
firefox --version
Mozilla Firefox 113.0.2
pip freeze:
absl-py==1.4.0
anyio==3.6.2
asttokens==2.2.1
async-generator==1.10
attrs==22.2.0
backcall==0.2.0
bcrypt==4.0.1
cachetools==5.3.0
certifi==2022.12.7
cffi==1.15.1
charset-normalizer==3.1.0
click==7.1.2
cloudpickle==2.2.1
cryptography==40.0.1
decorator==5.1.1
Deprecated==1.2.13
docstring-parser==0.15
exceptiongroup==1.1.1
executing==1.2.0
fire==0.5.0
google-api-core==2.11.0
google-api-python-client==1.12.11
google-auth==2.17.2
google-auth-httplib2==0.1.0
google-cloud-core==2.3.2
google-cloud-storage==2.8.0
google-crc32c==1.5.0
google-resumable-media==2.4.1
googleapis-common-protos==1.59.0
h11==0.14.0
httpcore==0.16.3
httplib2==0.22.0
httpx==0.23.3
hvac==1.1.0
idna==3.4
iniconfig==2.0.0
ipdb==0.13.13
ipython==8.12.0
jedi==0.18.2
Jinja2==3.1.2
[Desktop-packages] [Bug 2025290] Re: user-accounts: GFileInfo created without standard::symlink-target
** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #2547 https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2547 ** Also affects: gnome-control-center via https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2547 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/2025290 Title: user-accounts: GFileInfo created without standard::symlink-target Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: Triaged Bug description: If I open g-c-c from terminal on an updated mantic install and switch to the Users panel, I see some warning messages (see attachment). I don't know the significance of it, but it does not look right... ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-control-center 1:44.1-1ubuntu1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 28 20:55:07 2023 InstallationDate: Installed on 2022-05-07 (416 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to mantic on 2023-06-20 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/2025290/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2025290] Re: user-accounts: GFileInfo created without standard::symlink-target
I believe this is triggered by https://launchpad.net/ubuntu/+source/glib2.0/2.76.3-1ubuntu1 It should be fixed upstream. Could you report this issue there? https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues ** Changed in: gnome-control-center (Ubuntu) Status: New => Triaged ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low -- 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/2025290 Title: user-accounts: GFileInfo created without standard::symlink-target Status in gnome-control-center package in Ubuntu: Triaged Bug description: If I open g-c-c from terminal on an updated mantic install and switch to the Users panel, I see some warning messages (see attachment). I don't know the significance of it, but it does not look right... ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-control-center 1:44.1-1ubuntu1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 28 20:55:07 2023 InstallationDate: Installed on 2022-05-07 (416 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to mantic on 2023-06-20 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2025290/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2025287] Re: mutter cogl-test-framebuffer-get-bits-gl3 failure
** Changed in: mutter (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2025287 Title: mutter cogl-test-framebuffer-get-bits-gl3 failure Status in mutter package in Ubuntu: Fix Committed Bug description: mutter has one failing build test in Mantic. Debian Experimental has the same build test failure but Ubuntu 23.04 (Lunar) does not. This is reproducible with mutter 44.2-1 from earlier in June so this appears to be triggered by a change in one of the dependencies. https://launchpad.net/ubuntu/+source/mutter/44.2-2ubuntu1 Build log excerpt = 67/179 mutter:cogl+cogl/conform / cogl-test-framebuffer-get-bits-gl3 RUNNING >>> LD_LIBRARY_PATH=/<>/obj-x86_64-linux-gnu/cogl/cogl:/<>/obj-x86_64-linux-gnu/src:/<>/obj-x86_64-linux-gnu/cogl/cogl-pango:/<>/obj-x86_64-linux-gnu/src/tests:/<>/obj-x86_64-linux-gnu/clutter/clutter G_ENABLE_DIAGNOSTIC=0 G_TEST_BUILDDIR=/<>/obj-x86_64-linux-gnu/src/tests/cogl/conform G_TEST_SRCDIR=/<>/src/tests/cogl/conform COGL_DRIVER=gl3 MALLOC_PERTURB_=209 MUTTER_TEST_PLUGIN_PATH=/<>/obj-x86_64-linux-gnu/src/compositor/plugins/libdefault.so /<>/src/tests/meta-dbus-runner.py -- /<>/obj-x86_64-linux-gnu/src/tests/cogl/conform/cogl-test-framebuffer-get-bits ― ✀ ― Starting D-Bus daemons (session & system)... Launching required services... Starting mocked services... Running test case... TAP version 13 # random seed: R02Scf195b999d71877c99f7f10a5670c4cb # GLib-GIO-DEBUG: _g_io_module_get_default: Found default implementation memory (GMemorySettingsBackend) for ‘gsettings-backend’ # libmutter-MESSAGE: Running Mutter Test (using mutter 44.2) as a Wayland display server # libmutter-MESSAGE: Created surfaceless renderer without GPU # GLib-GIO-DEBUG: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ‘gio-vfs’ # libmutter-MESSAGE: Disabling DMA buffer screen sharing (not hardware accelerated) # libmutter-MESSAGE: Disabling DMA buffer screen sharing (implicit modifiers not supported) # libmutter-DEBUG: WL: loaded libnvidia-egl-wayland.so.1:wl_eglstream_controller. # libmutter-MESSAGE: Using Wayland display name 'mutter-test-display' Window manager warning: Failed to set environment variable WAYLAND_DISPLAY for gnome-session: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.gnome.SessionManager" does not exist 1..1 # Start of framebuffer tests ** ERROR:../src/tests/cogl/conform/test-framebuffer-get-bits.c:39:test_framebuffer_get_bits: assertion failed (cogl_framebuffer_get_alpha_bits (fb_a) >= 1): (0 >= 1) not ok /framebuffer/get-bits - ERROR:../src/tests/cogl/conform/test-framebuffer-get-bits.c:39:test_framebuffer_get_bits: assertion failed (cogl_framebuffer_get_alpha_bits (fb_a) >= 1): (0 >= 1) Bail out! ―― 67/179 mutter:cogl+cogl/conform / cogl-test-framebuffer-get-bits-gl3 FAIL 1.09s (exit status 250 or signal 122 SIGinvalid) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2025287/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2025290] Re: user-accounts: GFileInfo created without standard::symlink-target
Possibly the updated accountsservice has something to do with it. -- 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/2025290 Title: user-accounts: GFileInfo created without standard::symlink-target Status in gnome-control-center package in Ubuntu: New Bug description: If I open g-c-c from terminal on an updated mantic install and switch to the Users panel, I see some warning messages (see attachment). I don't know the significance of it, but it does not look right... ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-control-center 1:44.1-1ubuntu1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 28 20:55:07 2023 InstallationDate: Installed on 2022-05-07 (416 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to mantic on 2023-06-20 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2025290/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1998286] Re: Release mutter 42.9 to jammy
** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1998286 Title: Release mutter 42.9 to jammy Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: Fix Committed Bug description: Impact -- There is a new bugfix release in the stable 42 series. https://gitlab.gnome.org/GNOME/mutter/-/blob/42.9/NEWS The overall GNOME project considers GNOME 42 to be end of life now and there are no more scheduled releases for mutter 42 after 42.9 This is basically a prerequisite for GNOME Shell 42.9 LP: #2023913 The current version of Mutter in Jammy is 42.5. Test Case - Complete the test case from https://wiki.ubuntu.com/DesktopTeam/TestPlans/Mutter Extra Test Case 1 - This release also cherry-picks a patch to fix the prompt to enable accessibility features using keyboard shortcuts. 0. Install the updated mutter packages. Then log out and log back in. 1. Open the Settings app (gnome-control-center) 2. In the left sidebar, click Accessibility 3. In the typing section, lick Typing Assist 4. Turn on the first switch to enable turning accessibility features on and off using the keyboard 5. Close the Settings app 6. Press the Shift key 5 or 6 times in a row 7. You should see a system prompt about turning on Sticky Keys What Could Go Wrong --- Mutter is an essential component of the default Ubuntu desktop and for the desktop used by Ubuntu Budgie. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. mutter is part of GNOME Core and is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- Upstream assumes that people will be using matching versions of mutter and gnome-shell. To be cautious, I therefore bumped the dependency version in GNOME Shell 42.9 to require mutter >= 42.9 (even though GNOME Shell 42.9 appears to run ok with Mutter 42.5). I believe the only way to make the dependency relationship work the other way (not allow Mutter 42.9 with GNOME Shell 42.5) requires bumping the Breaks version but I don't think it's worth using Breaks unless necessary. This release will also enable AMD Xilinx/Mali support on Wayland. See https://ubuntu.com/download/amd-xilinx or private bug 1961563 or the 42.6 release notes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1998286/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2023322] Re: Unable to setup Google Online Accounts with Nvidia drivers
** Changed in: webkit2gtk (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/2023322 Title: Unable to setup Google Online Accounts with Nvidia drivers Status in gnome-control-center: Fix Released Status in gnome-control-center package in Ubuntu: Triaged Status in gnome-online-accounts package in Ubuntu: Triaged Status in webkit2gtk package in Ubuntu: Triaged Status in webkit2gtk package in Debian: New Bug description: When I go into Settings > Online Accounts > Google, I get to the prompt for email address, once in a while it stops accepting input there. But often I can get to the password screen. Once I do, I can't type anything or paste anything. This is a fresh install of Ubuntu 23.04 and I have installed all updates. Nothing in /var/crash Jun 08 11:15:59 CCW-HAL systemd[3523]: vte-spawn-8b4a59a3-a060-4bdd-92e6-285656bdb9a2.scope: Consumed 3.448s CPU time. Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:29 CCW-HAL systemd[3523]: Started app-gnome-org.gnome.Terminal-10924.scope - Application launched by gnome-shell. Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.167' (uid=1000 pid=10927 comm="/usr/bin/gnome-terminal.real" label="unconfined") Jun 08 11:16:29 CCW-HAL systemd[3523]: Starting gnome-terminal-server.service - GNOME Terminal Server... Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] Successfully activated service 'org.gnome.Terminal' Jun 08 11:16:29 CCW-HAL systemd[3523]: Started gnome-terminal-server.service - GNOME Terminal Server. Jun 08 11:16:29 CCW-HAL systemd[3523]: Started vte-spawn-9cee1911-372a-4bb4-8b57-694984e43990.scope - VTE child process 10955 launched by gnome-terminal-server process 10931. Jun 08 11:16:49 CCW-HAL gnome-control-c[8079]: Error showing account: Child process exited with code 1 Jun 08 11:16:53 CCW-HAL gnome-online-accounts-panel.desktop[9764]: GLib-GIO: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)GLib-GIO: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’GLib: unsetenv() is not thread-safe and should not be used after threads are createdGLib-GIO: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’GoaBackend: Loading all providers: GoaBackend: - googleGoaBackend: - owncloudGoaBackend: - windows_liveGoaBackend: - exchangeGoaBackend: - lastfmGoaBackend: - imap_smtpGoaBackend: - kerberosGoaBackend: activated kerberos providerGLib-GIO: _g_io_module_get_default: Found default implementation gnutls (GTlsBackendGnutls) for ‘gio-tls-backend’Failed to create account: Dialog was dismissed Jun 08 11:16:53 CCW-HAL xdg-desktop-por[3907]: Realtime error: Could not map pid: Could not determine pid namespace: Could not find instance-id in process's /.flatpak-info Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0) Jun 08 11:17:01 CCW-HAL CRON[11094]: (root) CMD (cd / && run-parts --report /etc/cron.hourly) Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session closed for user root Jun 08 11:17:06 CCW-HAL kernel: WebKitWebProces[11026]: segfault at 55bd22ad9adc ip 55bd22ad9adc sp 7ffd1f6adbe8 error 14 likely on CPU 2 (core 2, socket 0) Jun 08 11:17:06 CCW-HAL kernel: Code: Unable to access opcode bytes at 0x55bd22ad9ab2. Jun 08 11:17:36 CCW-HAL gnome-shell[3803]: Window manager warning: WM_TRANSIENT_FOR window 0x3a02767 for 0x3a02778 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x3a006dc. Jun 08 11:17:42 CCW-HAL systemd[1]: Starting systemd-tmpfiles-clean.service - Cleanup of Temporary Directories... Jun 08 11:17:42 CCW-HAL systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully. Jun 08 11:17:42 CCW-HAL systemd[1]: Finished systemd-tmpfiles-clean.service - Cleanup of Temporary Directories. Jun 08 11:17:42 CCW-HAL systemd[1]: run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated successfully. Jun 08 11:18:10 CCW-HAL gnome-shell[3803]: Window manager warning: WM_TRANSIENT_FOR window 0x3a029e2 for 0x3a029f0 window override-redirect is an override-redirect window and this is not correct according to the standard, so
[Desktop-packages] [Bug 2025290] [NEW] user-accounts: GFileInfo created without standard::symlink-target
Public bug reported: If I open g-c-c from terminal on an updated mantic install and switch to the Users panel, I see some warning messages (see attachment). I don't know the significance of it, but it does not look right... ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-control-center 1:44.1-1ubuntu1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 28 20:55:07 2023 InstallationDate: Installed on 2022-05-07 (416 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to mantic on 2023-06-20 (8 days ago) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland-session ** Attachment added: "settings-users-warning-messages.txt" https://bugs.launchpad.net/bugs/2025290/+attachment/5682583/+files/settings-users-warning-messages.txt -- 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/2025290 Title: user-accounts: GFileInfo created without standard::symlink-target Status in gnome-control-center package in Ubuntu: New Bug description: If I open g-c-c from terminal on an updated mantic install and switch to the Users panel, I see some warning messages (see attachment). I don't know the significance of it, but it does not look right... ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-control-center 1:44.1-1ubuntu1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 28 20:55:07 2023 InstallationDate: Installed on 2022-05-07 (416 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to mantic on 2023-06-20 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2025290/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2023322] Re: Unable to setup Google Online Accounts with Nvidia drivers
** Changed in: gnome-control-center Status: Unknown => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/2023322 Title: Unable to setup Google Online Accounts with Nvidia drivers Status in gnome-control-center: Fix Released Status in gnome-control-center package in Ubuntu: Triaged Status in gnome-online-accounts package in Ubuntu: Triaged Status in webkit2gtk package in Ubuntu: Triaged Status in webkit2gtk package in Debian: Unknown Bug description: When I go into Settings > Online Accounts > Google, I get to the prompt for email address, once in a while it stops accepting input there. But often I can get to the password screen. Once I do, I can't type anything or paste anything. This is a fresh install of Ubuntu 23.04 and I have installed all updates. Nothing in /var/crash Jun 08 11:15:59 CCW-HAL systemd[3523]: vte-spawn-8b4a59a3-a060-4bdd-92e6-285656bdb9a2.scope: Consumed 3.448s CPU time. Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:29 CCW-HAL systemd[3523]: Started app-gnome-org.gnome.Terminal-10924.scope - Application launched by gnome-shell. Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.167' (uid=1000 pid=10927 comm="/usr/bin/gnome-terminal.real" label="unconfined") Jun 08 11:16:29 CCW-HAL systemd[3523]: Starting gnome-terminal-server.service - GNOME Terminal Server... Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] Successfully activated service 'org.gnome.Terminal' Jun 08 11:16:29 CCW-HAL systemd[3523]: Started gnome-terminal-server.service - GNOME Terminal Server. Jun 08 11:16:29 CCW-HAL systemd[3523]: Started vte-spawn-9cee1911-372a-4bb4-8b57-694984e43990.scope - VTE child process 10955 launched by gnome-terminal-server process 10931. Jun 08 11:16:49 CCW-HAL gnome-control-c[8079]: Error showing account: Child process exited with code 1 Jun 08 11:16:53 CCW-HAL gnome-online-accounts-panel.desktop[9764]: GLib-GIO: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)GLib-GIO: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’GLib: unsetenv() is not thread-safe and should not be used after threads are createdGLib-GIO: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’GoaBackend: Loading all providers: GoaBackend: - googleGoaBackend: - owncloudGoaBackend: - windows_liveGoaBackend: - exchangeGoaBackend: - lastfmGoaBackend: - imap_smtpGoaBackend: - kerberosGoaBackend: activated kerberos providerGLib-GIO: _g_io_module_get_default: Found default implementation gnutls (GTlsBackendGnutls) for ‘gio-tls-backend’Failed to create account: Dialog was dismissed Jun 08 11:16:53 CCW-HAL xdg-desktop-por[3907]: Realtime error: Could not map pid: Could not determine pid namespace: Could not find instance-id in process's /.flatpak-info Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0) Jun 08 11:17:01 CCW-HAL CRON[11094]: (root) CMD (cd / && run-parts --report /etc/cron.hourly) Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session closed for user root Jun 08 11:17:06 CCW-HAL kernel: WebKitWebProces[11026]: segfault at 55bd22ad9adc ip 55bd22ad9adc sp 7ffd1f6adbe8 error 14 likely on CPU 2 (core 2, socket 0) Jun 08 11:17:06 CCW-HAL kernel: Code: Unable to access opcode bytes at 0x55bd22ad9ab2. Jun 08 11:17:36 CCW-HAL gnome-shell[3803]: Window manager warning: WM_TRANSIENT_FOR window 0x3a02767 for 0x3a02778 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x3a006dc. Jun 08 11:17:42 CCW-HAL systemd[1]: Starting systemd-tmpfiles-clean.service - Cleanup of Temporary Directories... Jun 08 11:17:42 CCW-HAL systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully. Jun 08 11:17:42 CCW-HAL systemd[1]: Finished systemd-tmpfiles-clean.service - Cleanup of Temporary Directories. Jun 08 11:17:42 CCW-HAL systemd[1]: run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated successfully. Jun 08 11:18:10 CCW-HAL gnome-shell[3803]: Window manager warning: WM_TRANSIENT_FOR window 0x3a029e2 for 0x3a029f0 window override-redirect is an override-redirect window and this is not correct according to the
[Desktop-packages] [Bug 2025287] [NEW] mutter cogl-test-framebuffer-get-bits-gl3 failure
Public bug reported: mutter has one failing build test in Mantic. Debian Experimental has the same build test failure but Ubuntu 23.04 (Lunar) does not. This is reproducible with mutter 44.2-1 from earlier in June so this appears to be triggered by a change in one of the dependencies. https://launchpad.net/ubuntu/+source/mutter/44.2-2ubuntu1 Build log excerpt = 67/179 mutter:cogl+cogl/conform / cogl-test-framebuffer-get-bits-gl3 RUNNING >>> LD_LIBRARY_PATH=/<>/obj-x86_64-linux-gnu/cogl/cogl:/<>/obj-x86_64-linux-gnu/src:/<>/obj-x86_64-linux-gnu/cogl/cogl-pango:/<>/obj-x86_64-linux-gnu/src/tests:/<>/obj-x86_64-linux-gnu/clutter/clutter >>> G_ENABLE_DIAGNOSTIC=0 >>> G_TEST_BUILDDIR=/<>/obj-x86_64-linux-gnu/src/tests/cogl/conform >>> G_TEST_SRCDIR=/<>/src/tests/cogl/conform COGL_DRIVER=gl3 >>> MALLOC_PERTURB_=209 >>> MUTTER_TEST_PLUGIN_PATH=/<>/obj-x86_64-linux-gnu/src/compositor/plugins/libdefault.so >>> /<>/src/tests/meta-dbus-runner.py -- >>> /<>/obj-x86_64-linux-gnu/src/tests/cogl/conform/cogl-test-framebuffer-get-bits ― ✀ ― Starting D-Bus daemons (session & system)... Launching required services... Starting mocked services... Running test case... TAP version 13 # random seed: R02Scf195b999d71877c99f7f10a5670c4cb # GLib-GIO-DEBUG: _g_io_module_get_default: Found default implementation memory (GMemorySettingsBackend) for ‘gsettings-backend’ # libmutter-MESSAGE: Running Mutter Test (using mutter 44.2) as a Wayland display server # libmutter-MESSAGE: Created surfaceless renderer without GPU # GLib-GIO-DEBUG: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ‘gio-vfs’ # libmutter-MESSAGE: Disabling DMA buffer screen sharing (not hardware accelerated) # libmutter-MESSAGE: Disabling DMA buffer screen sharing (implicit modifiers not supported) # libmutter-DEBUG: WL: loaded libnvidia-egl-wayland.so.1:wl_eglstream_controller. # libmutter-MESSAGE: Using Wayland display name 'mutter-test-display' Window manager warning: Failed to set environment variable WAYLAND_DISPLAY for gnome-session: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.gnome.SessionManager" does not exist 1..1 # Start of framebuffer tests ** ERROR:../src/tests/cogl/conform/test-framebuffer-get-bits.c:39:test_framebuffer_get_bits: assertion failed (cogl_framebuffer_get_alpha_bits (fb_a) >= 1): (0 >= 1) not ok /framebuffer/get-bits - ERROR:../src/tests/cogl/conform/test-framebuffer-get-bits.c:39:test_framebuffer_get_bits: assertion failed (cogl_framebuffer_get_alpha_bits (fb_a) >= 1): (0 >= 1) Bail out! ―― 67/179 mutter:cogl+cogl/conform / cogl-test-framebuffer-get-bits-gl3 FAIL 1.09s (exit status 250 or signal 122 SIGinvalid) ** Affects: mutter (Ubuntu) Importance: High Status: Triaged ** Tags: ftbfs mantic update-excuse -- 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/2025287 Title: mutter cogl-test-framebuffer-get-bits-gl3 failure Status in mutter package in Ubuntu: Triaged Bug description: mutter has one failing build test in Mantic. Debian Experimental has the same build test failure but Ubuntu 23.04 (Lunar) does not. This is reproducible with mutter 44.2-1 from earlier in June so this appears to be triggered by a change in one of the dependencies. https://launchpad.net/ubuntu/+source/mutter/44.2-2ubuntu1 Build log excerpt = 67/179 mutter:cogl+cogl/conform / cogl-test-framebuffer-get-bits-gl3 RUNNING >>> LD_LIBRARY_PATH=/<>/obj-x86_64-linux-gnu/cogl/cogl:/<>/obj-x86_64-linux-gnu/src:/<>/obj-x86_64-linux-gnu/cogl/cogl-pango:/<>/obj-x86_64-linux-gnu/src/tests:/<>/obj-x86_64-linux-gnu/clutter/clutter G_ENABLE_DIAGNOSTIC=0 G_TEST_BUILDDIR=/<>/obj-x86_64-linux-gnu/src/tests/cogl/conform G_TEST_SRCDIR=/<>/src/tests/cogl/conform COGL_DRIVER=gl3 MALLOC_PERTURB_=209 MUTTER_TEST_PLUGIN_PATH=/<>/obj-x86_64-linux-gnu/src/compositor/plugins/libdefault.so /<>/src/tests/meta-dbus-runner.py -- /<>/obj-x86_64-linux-gnu/src/tests/cogl/conform/cogl-test-framebuffer-get-bits ― ✀ ― Starting D-Bus daemons (session & system)... Launching required services... Starting mocked services... Running test case... TAP version 13 # random seed: R02Scf195b999d71877c99f7f10a5670c4cb # GLib-GIO-DEBUG: _g_io_module_get_default: Found default implementation memory (GMemorySettingsBackend) for ‘gsettings-backend’ # libmutter-MESSAGE: Running Mutter Test (using mutter 44.2) as a Wayland display server # libmutter-MESSAGE: Created surfaceless renderer
[Desktop-packages] [Bug 1998286] Re: Release mutter 42.9 to jammy
Installed libmutter-10-0 from jammy-proposed v42.9-0ubuntu1 in Ubuntu Budgie Logout and login. Tested standard window manipulation (maximise/minimise) as well as side-by-side tiling with center resizing - no issues Examined /var/crash - no issues shortcut keys to scroll left/right in workspace works ok Note - extra test case 1 no system prompt is visible - but that appears to be a gnome-shell specific thing since it wasnt visible in v10.5 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1998286 Title: Release mutter 42.9 to jammy Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: Fix Committed Bug description: Impact -- There is a new bugfix release in the stable 42 series. https://gitlab.gnome.org/GNOME/mutter/-/blob/42.9/NEWS The overall GNOME project considers GNOME 42 to be end of life now and there are no more scheduled releases for mutter 42 after 42.9 This is basically a prerequisite for GNOME Shell 42.9 LP: #2023913 The current version of Mutter in Jammy is 42.5. Test Case - Complete the test case from https://wiki.ubuntu.com/DesktopTeam/TestPlans/Mutter Extra Test Case 1 - This release also cherry-picks a patch to fix the prompt to enable accessibility features using keyboard shortcuts. 0. Install the updated mutter packages. Then log out and log back in. 1. Open the Settings app (gnome-control-center) 2. In the left sidebar, click Accessibility 3. In the typing section, lick Typing Assist 4. Turn on the first switch to enable turning accessibility features on and off using the keyboard 5. Close the Settings app 6. Press the Shift key 5 or 6 times in a row 7. You should see a system prompt about turning on Sticky Keys What Could Go Wrong --- Mutter is an essential component of the default Ubuntu desktop and for the desktop used by Ubuntu Budgie. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. mutter is part of GNOME Core and is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- Upstream assumes that people will be using matching versions of mutter and gnome-shell. To be cautious, I therefore bumped the dependency version in GNOME Shell 42.9 to require mutter >= 42.9 (even though GNOME Shell 42.9 appears to run ok with Mutter 42.5). I believe the only way to make the dependency relationship work the other way (not allow Mutter 42.9 with GNOME Shell 42.5) requires bumping the Breaks version but I don't think it's worth using Breaks unless necessary. This release will also enable AMD Xilinx/Mali support on Wayland. See https://ubuntu.com/download/amd-xilinx or private bug 1961563 or the 42.6 release notes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1998286/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2025280] [NEW] ubuntu-drivers does not list the driver for GPU Tesla V100 on DGX Station
Public bug reported: I have a DGX Station running Jammy and I invoked `ubuntu-drivers` shows nothing. I expect nvidia driver R460 or R525 should be shown as there are 4 Tesla V100 are installed. Steps to Reproduce: 1. Invoke `ubuntu-drivers list --gpgpu` 2. Invoke `ubuntu-drivers list` Expected Results: At least one GPU driver is listed. Actual Results: ubuntu@nvidia-dgx-station-c25989:~$ ubuntu-drivers list --gpgpu ubuntu@nvidia-dgx-station-c25989:~$ ubuntu-drivers list Additional Information: ubuntu@nvidia-dgx-station-c25989:~$ lspci -nn | grep -i vga 07:00.0 VGA compatible controller [0300]: NVIDIA Corporation GV100GL [Tesla V100 DGXS 16GB] [10de:1db2] (rev a1) 08:00.0 VGA compatible controller [0300]: NVIDIA Corporation GV100GL [Tesla V100 DGXS 16GB] [10de:1db2] (rev a1) 0e:00.0 VGA compatible controller [0300]: NVIDIA Corporation GV100GL [Tesla V100 DGXS 16GB] [10de:1db2] (rev a1) 0f:00.0 VGA compatible controller [0300]: NVIDIA Corporation GV100GL [Tesla V100 DGXS 16GB] [10de:1db2] (rev a1) ubuntu@nvidia-dgx-station-c25989:~$ dpkg -l ubuntu-drivers-common Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-=--- ii ubuntu-drivers-common 1:0.9.6.1amd64Detect and install additional Ubuntu driver packages ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-drivers-common 1:0.9.6.1 ProcVersionSignature: Ubuntu 5.15.0-1027.27-nvidia 5.15.99 Uname: Linux 5.15.0-1027-nvidia x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Jun 28 13:11:04 2023 InstallationDate: Installed on 2022-05-10 (413 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: ubuntu-drivers-common UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy uec-images ** Also affects: ubiquity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/2025280 Title: ubuntu-drivers does not list the driver for GPU Tesla V100 on DGX Station Status in ubiquity package in Ubuntu: New Status in ubuntu-drivers-common package in Ubuntu: New Bug description: I have a DGX Station running Jammy and I invoked `ubuntu-drivers` shows nothing. I expect nvidia driver R460 or R525 should be shown as there are 4 Tesla V100 are installed. Steps to Reproduce: 1. Invoke `ubuntu-drivers list --gpgpu` 2. Invoke `ubuntu-drivers list` Expected Results: At least one GPU driver is listed. Actual Results: ubuntu@nvidia-dgx-station-c25989:~$ ubuntu-drivers list --gpgpu ubuntu@nvidia-dgx-station-c25989:~$ ubuntu-drivers list Additional Information: ubuntu@nvidia-dgx-station-c25989:~$ lspci -nn | grep -i vga 07:00.0 VGA compatible controller [0300]: NVIDIA Corporation GV100GL [Tesla V100 DGXS 16GB] [10de:1db2] (rev a1) 08:00.0 VGA compatible controller [0300]: NVIDIA Corporation GV100GL [Tesla V100 DGXS 16GB] [10de:1db2] (rev a1) 0e:00.0 VGA compatible controller [0300]: NVIDIA Corporation GV100GL [Tesla V100 DGXS 16GB] [10de:1db2] (rev a1) 0f:00.0 VGA compatible controller [0300]: NVIDIA Corporation GV100GL [Tesla V100 DGXS 16GB] [10de:1db2] (rev a1) ubuntu@nvidia-dgx-station-c25989:~$ dpkg -l ubuntu-drivers-common Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-=--- ii ubuntu-drivers-common 1:0.9.6.1amd64Detect and install additional Ubuntu driver packages ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-drivers-common 1:0.9.6.1 ProcVersionSignature: Ubuntu 5.15.0-1027.27-nvidia 5.15.99 Uname: Linux 5.15.0-1027-nvidia x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Jun 28 13:11:04 2023 InstallationDate: Installed on 2022-05-10 (413 days ago) InstallationMedia: Ubuntu 22.04 LTS
[Desktop-packages] [Bug 2025280] Re: ubuntu-drivers does not list the driver for GPU Tesla V100 on DGX Station
Set the bug report as also affecting ubiquity since ubiquity would use ubuntu-drivers to install drivers if I understand correctly. -- 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/2025280 Title: ubuntu-drivers does not list the driver for GPU Tesla V100 on DGX Station Status in ubiquity package in Ubuntu: New Status in ubuntu-drivers-common package in Ubuntu: New Bug description: I have a DGX Station running Jammy and I invoked `ubuntu-drivers` shows nothing. I expect nvidia driver R460 or R525 should be shown as there are 4 Tesla V100 are installed. Steps to Reproduce: 1. Invoke `ubuntu-drivers list --gpgpu` 2. Invoke `ubuntu-drivers list` Expected Results: At least one GPU driver is listed. Actual Results: ubuntu@nvidia-dgx-station-c25989:~$ ubuntu-drivers list --gpgpu ubuntu@nvidia-dgx-station-c25989:~$ ubuntu-drivers list Additional Information: ubuntu@nvidia-dgx-station-c25989:~$ lspci -nn | grep -i vga 07:00.0 VGA compatible controller [0300]: NVIDIA Corporation GV100GL [Tesla V100 DGXS 16GB] [10de:1db2] (rev a1) 08:00.0 VGA compatible controller [0300]: NVIDIA Corporation GV100GL [Tesla V100 DGXS 16GB] [10de:1db2] (rev a1) 0e:00.0 VGA compatible controller [0300]: NVIDIA Corporation GV100GL [Tesla V100 DGXS 16GB] [10de:1db2] (rev a1) 0f:00.0 VGA compatible controller [0300]: NVIDIA Corporation GV100GL [Tesla V100 DGXS 16GB] [10de:1db2] (rev a1) ubuntu@nvidia-dgx-station-c25989:~$ dpkg -l ubuntu-drivers-common Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-=--- ii ubuntu-drivers-common 1:0.9.6.1amd64Detect and install additional Ubuntu driver packages ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-drivers-common 1:0.9.6.1 ProcVersionSignature: Ubuntu 5.15.0-1027.27-nvidia 5.15.99 Uname: Linux 5.15.0-1027-nvidia x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Jun 28 13:11:04 2023 InstallationDate: Installed on 2022-05-10 (413 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: ubuntu-drivers-common UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/2025280/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2019739] Re: Cannot reauthorize Google account or authorize again. The app crashes
*** This bug is a duplicate of bug 2023322 *** https://bugs.launchpad.net/bugs/2023322 ** This bug has been marked a duplicate of bug 2023322 Unable to connect Ubuntu with Google Online Accounts -- 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/2019739 Title: Cannot reauthorize Google account or authorize again. The app crashes Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-online-accounts package in Ubuntu: Confirmed Bug description: As in title I tried to relogin, The window prompt appears and quickly exits and nothing happens. Still cannot not logged in. Have to remove account and sign in again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-online-accounts 3.44.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon May 15 17:45:34 2023 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2019739/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2007411] Re: gnome-control-center-goa-helper hangs after toggling a rocker switch
*** This bug is a duplicate of bug 2023322 *** https://bugs.launchpad.net/bugs/2023322 Because you are using Nvidia drivers, I am marking this a duplicate of bug 2023322 ** This bug has been marked a duplicate of bug 2023322 Unable to setup Google Online Accounts with Nvidia drivers -- 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/2007411 Title: gnome-control-center-goa-helper hangs after toggling a rocker switch Status in gnome-control-center package in Ubuntu: New Bug description: 1. Open Settings. 2. Go to Online Accounts. 3. Add a Google account, or if you already have one, click on it, to open the Google Account window. 4. Toggle one of the rocker switches from on to off or vice versa. 5. Observe that at this point the window becomes unresponsive and can't be closed. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-control-center 1:44~alpha-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Feb 15 11:15:03 2023 InstallationDate: Installed on 2019-01-02 (1505 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to lunar on 2022-11-24 (82 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2007411/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2023322] Re: Unable to setup Google Online Accounts with Nvidia drivers
** Summary changed: - Unable to connect Ubuntu with Google Online Accounts + Unable to setup Google Online Accounts with Nvidia drivers ** Changed in: gnome-online-accounts (Ubuntu) Importance: Undecided => High ** Changed in: gnome-online-accounts (Ubuntu) Status: Confirmed => Triaged ** Also affects: webkit2gtk (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Changed in: webkit2gtk (Ubuntu) Importance: Undecided => High ** Changed in: webkit2gtk (Ubuntu) Status: New => Triaged ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => High ** Changed in: gnome-control-center (Ubuntu) Status: New => Triaged ** Bug watch added: Debian Bug tracker #1039720 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039720 ** Also affects: webkit2gtk (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039720 Importance: Unknown Status: Unknown ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #2498 https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2498 ** Also affects: gnome-control-center via https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2498 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/2023322 Title: Unable to setup Google Online Accounts with Nvidia drivers Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: Triaged Status in gnome-online-accounts package in Ubuntu: Triaged Status in webkit2gtk package in Ubuntu: Triaged Status in webkit2gtk package in Debian: Unknown Bug description: When I go into Settings > Online Accounts > Google, I get to the prompt for email address, once in a while it stops accepting input there. But often I can get to the password screen. Once I do, I can't type anything or paste anything. This is a fresh install of Ubuntu 23.04 and I have installed all updates. Nothing in /var/crash Jun 08 11:15:59 CCW-HAL systemd[3523]: vte-spawn-8b4a59a3-a060-4bdd-92e6-285656bdb9a2.scope: Consumed 3.448s CPU time. Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:29 CCW-HAL systemd[3523]: Started app-gnome-org.gnome.Terminal-10924.scope - Application launched by gnome-shell. Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.167' (uid=1000 pid=10927 comm="/usr/bin/gnome-terminal.real" label="unconfined") Jun 08 11:16:29 CCW-HAL systemd[3523]: Starting gnome-terminal-server.service - GNOME Terminal Server... Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] Successfully activated service 'org.gnome.Terminal' Jun 08 11:16:29 CCW-HAL systemd[3523]: Started gnome-terminal-server.service - GNOME Terminal Server. Jun 08 11:16:29 CCW-HAL systemd[3523]: Started vte-spawn-9cee1911-372a-4bb4-8b57-694984e43990.scope - VTE child process 10955 launched by gnome-terminal-server process 10931. Jun 08 11:16:49 CCW-HAL gnome-control-c[8079]: Error showing account: Child process exited with code 1 Jun 08 11:16:53 CCW-HAL gnome-online-accounts-panel.desktop[9764]: GLib-GIO: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)GLib-GIO: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’GLib: unsetenv() is not thread-safe and should not be used after threads are createdGLib-GIO: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’GoaBackend: Loading all providers: GoaBackend: - googleGoaBackend: - owncloudGoaBackend: - windows_liveGoaBackend: - exchangeGoaBackend: - lastfmGoaBackend: - imap_smtpGoaBackend: - kerberosGoaBackend: activated kerberos providerGLib-GIO: _g_io_module_get_default: Found default implementation gnutls (GTlsBackendGnutls) for ‘gio-tls-backend’Failed to create account: Dialog was dismissed Jun 08 11:16:53 CCW-HAL xdg-desktop-por[3907]: Realtime error: Could not map pid: Could not determine pid namespace: Could not find instance-id in process's /.flatpak-info Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0) Jun 08 11:17:01 CCW-HAL CRON[11094]: (root) CMD (cd / && run-parts --report /etc/cron.hourly) Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session closed for
[Desktop-packages] [Bug 2023322] Re: Unable to connect Ubuntu with Google Online Accounts
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-online-accounts (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/2023322 Title: Unable to setup Google Online Accounts with Nvidia drivers Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: Triaged Status in gnome-online-accounts package in Ubuntu: Triaged Status in webkit2gtk package in Ubuntu: Triaged Status in webkit2gtk package in Debian: Unknown Bug description: When I go into Settings > Online Accounts > Google, I get to the prompt for email address, once in a while it stops accepting input there. But often I can get to the password screen. Once I do, I can't type anything or paste anything. This is a fresh install of Ubuntu 23.04 and I have installed all updates. Nothing in /var/crash Jun 08 11:15:59 CCW-HAL systemd[3523]: vte-spawn-8b4a59a3-a060-4bdd-92e6-285656bdb9a2.scope: Consumed 3.448s CPU time. Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:29 CCW-HAL systemd[3523]: Started app-gnome-org.gnome.Terminal-10924.scope - Application launched by gnome-shell. Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.167' (uid=1000 pid=10927 comm="/usr/bin/gnome-terminal.real" label="unconfined") Jun 08 11:16:29 CCW-HAL systemd[3523]: Starting gnome-terminal-server.service - GNOME Terminal Server... Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] Successfully activated service 'org.gnome.Terminal' Jun 08 11:16:29 CCW-HAL systemd[3523]: Started gnome-terminal-server.service - GNOME Terminal Server. Jun 08 11:16:29 CCW-HAL systemd[3523]: Started vte-spawn-9cee1911-372a-4bb4-8b57-694984e43990.scope - VTE child process 10955 launched by gnome-terminal-server process 10931. Jun 08 11:16:49 CCW-HAL gnome-control-c[8079]: Error showing account: Child process exited with code 1 Jun 08 11:16:53 CCW-HAL gnome-online-accounts-panel.desktop[9764]: GLib-GIO: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)GLib-GIO: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’GLib: unsetenv() is not thread-safe and should not be used after threads are createdGLib-GIO: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’GoaBackend: Loading all providers: GoaBackend: - googleGoaBackend: - owncloudGoaBackend: - windows_liveGoaBackend: - exchangeGoaBackend: - lastfmGoaBackend: - imap_smtpGoaBackend: - kerberosGoaBackend: activated kerberos providerGLib-GIO: _g_io_module_get_default: Found default implementation gnutls (GTlsBackendGnutls) for ‘gio-tls-backend’Failed to create account: Dialog was dismissed Jun 08 11:16:53 CCW-HAL xdg-desktop-por[3907]: Realtime error: Could not map pid: Could not determine pid namespace: Could not find instance-id in process's /.flatpak-info Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0) Jun 08 11:17:01 CCW-HAL CRON[11094]: (root) CMD (cd / && run-parts --report /etc/cron.hourly) Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session closed for user root Jun 08 11:17:06 CCW-HAL kernel: WebKitWebProces[11026]: segfault at 55bd22ad9adc ip 55bd22ad9adc sp 7ffd1f6adbe8 error 14 likely on CPU 2 (core 2, socket 0) Jun 08 11:17:06 CCW-HAL kernel: Code: Unable to access opcode bytes at 0x55bd22ad9ab2. Jun 08 11:17:36 CCW-HAL gnome-shell[3803]: Window manager warning: WM_TRANSIENT_FOR window 0x3a02767 for 0x3a02778 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x3a006dc. Jun 08 11:17:42 CCW-HAL systemd[1]: Starting systemd-tmpfiles-clean.service - Cleanup of Temporary Directories... Jun 08 11:17:42 CCW-HAL systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully. Jun 08 11:17:42 CCW-HAL systemd[1]: Finished systemd-tmpfiles-clean.service - Cleanup of Temporary Directories. Jun 08 11:17:42 CCW-HAL systemd[1]: run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated successfully. Jun 08 11:18:10 CCW-HAL gnome-shell[3803]: Window manager warning: WM_TRANSIENT_FOR window 0x3a029e2 for 0x3a029f0 window override-redirect is an
[Desktop-packages] [Bug 2024182] Re: GHSL-2023-139: use-after-free in user.c
** Tags added: patch
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/2024182
Title:
GHSL-2023-139: use-after-free in user.c
Status in accountsservice package in Ubuntu:
In Progress
Status in accountsservice source package in Focal:
Fix Released
Status in accountsservice source package in Jammy:
Fix Released
Status in accountsservice source package in Kinetic:
Fix Released
Status in accountsservice source package in Lunar:
Fix Released
Status in accountsservice source package in Mantic:
In Progress
Bug description:
# GitHub Security Lab (GHSL) Vulnerability Report, accountsservice:
`GHSL-2023-139`
The [GitHub Security Lab](https://securitylab.github.com) team has
identified a potential security vulnerability in
[accountsservice](https://code.launchpad.net/ubuntu/+source/accountsservice).
We are committed to working with you to help resolve this issue. In
this report you will find everything you need to effectively
coordinate a resolution of this issue with the GHSL team.
If at any point you have concerns or questions about this process,
please do not hesitate to reach out to us at `security...@github.com`
(please include `GHSL-2023-139` as a reference).
If you are _NOT_ the correct point of contact for this report, please
let us know!
## Summary
An unprivileged local attacker can trigger a use-after-free
vulnerability in accountsservice by sending a D-Bus message to the
accounts-daemon process.
## Product
accountsservice
## Tested Version
[22.08.8-1ubuntu7](https://launchpad.net/ubuntu/+source/accountsservice/22.08.8-1ubuntu7)
The bug is easier to observe on Ubuntu 23.04 than on Ubuntu 22.04 LTS,
but it is present on both.
## Details
### Use-after-free when `throw_error` is called (`GHSL-2023-139`)
After receiving a D-Bus [method
call](https://dbus.freedesktop.org/doc/dbus-
specification.html#message-protocol-types), a D-Bus server is expected
to send either a `METHOD_RETURN` or a `ERROR` message back to the
client, _but not both_. This is done incorrectly in several places in
accountsservice. For example, in
[`user_change_language_authorized_cb`](https://git.launchpad.net/ubuntu/+source/accountsservice/tree/debian/patches/0010-set-
language.patch?h=import/22.08.8-1ubuntu7#n427):
```c
static void
user_change_language_authorized_cb (Daemon*daemon,
User *user,
GDBusMethodInvocation *context,
gpointer data)
{
const gchar *language = data;
if (!user_HOME_available (user)) {
/* SetLanguage was probably called from a login greeter,
and HOME not mounted and/or not decrypted.
Hence don't save anything, or else accountsservice
and ~/.pam_environment would become out of sync. */
throw_error (context, ERROR_FAILED, "not access to HOME yet
so language not saved"); <= 1
goto out;
}
out:
accounts_user_complete_set_language (ACCOUNTS_USER (user), context);
<= 2
}
```
If `user_HOME_available` returns an error, then `throw_error` is
called at 1 to send an `ERROR` message, but a regular `METHOD_RETURN`
is also sent at 2. This is incorrect D-Bus protocol, but the more
serious problem is that it causes a use-after-free because both
`throw_error` and `accounts_user_complete_set_language` decrease the
reference count on `context`. In other words, `context` is freed by
`throw_error` and a UAF occurs in
`accounts_user_complete_set_language`.
An attacker can trigger the bug above by causing `user_HOME_available`
to fail, which they can do by deleting all the files from their home
directory. But there are other incorrect uses of `throw_error` in
`user.c` which are less inconvenient to trigger. For example, this
command triggers a call to `throw_error` in `user_update_environment`
due to the invalid characters in the string.
```bash
dbus-send --system --print-reply --dest=org.freedesktop.Accounts
/org/freedesktop/Accounts/User`id -u` org.freedesktop.Accounts.User.SetLanguage
string:'**'
```
On Ubuntu 23.04, the above command causes `accounts-daemon` to crash
with a `SIGSEGV`. But on Ubuntu 22.04 LTS it doesn't cause any visible
harm. The difference is due to a recent [change in
GLib's](https://gitlab.gnome.org/GNOME/glib/-/commit/69e9ba80e2f4d2061a1a68d72bae1c32c1e4f8fa)
memory allocation: older versions of GLib used the "slice" allocator,
but newer version uses the system allocator. The system allocator
trashes the memory when it's freed in a way that causes the use-after-
free to trigger a SIGSEGV, whereas
[Desktop-packages] [Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
I have verified on lunar with both apparmor and evince packages updated from the proposed pocket, it works as expected. ** Tags removed: verification-needed-lunar ** Tags added: verification-done-lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Fix Released Status in evince package in Ubuntu: Fix Released Status in apparmor source package in Jammy: Fix Committed Status in evince source package in Jammy: In Progress Status in apparmor source package in Lunar: Fix Committed Status in evince source package in Lunar: Fix Committed Status in evince package in Debian: Confirmed Bug description: [Impact] * Users cannot open a hyperlink in a PDF opened with evince when the default browser is a snap. * The fix creates a snap_browsers abstraction on AppArmor which can be used in a transition for when the browser is executed. The snap_browsers abstraction provides the minimal amount of permissions required to execute a browser provided through snaps. This is a workaround since AppArmor currently does not provide mediation/filtering on enhanced environment variables. [Test Plan] * Make sure the default browser is provided through the snap store. * Open a PDF that contains a hyperlink using evince and click on the URL. * The browser should open the requested URL. [Where problems could occur] * If the browser or snap core update to have new requirements for opening a browser, then the current policy could become obsolete and will need to be updated again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2004552] Re: Sound doesn't work on ASUS X670E-E motherboard.
affects me too. DistroRelease: Ubuntu 22.10 Base Board Information Manufacturer: ASUSTeK COMPUTER INC. Product Name: ROG STRIX X670E-F GAMING WIFI Version: Rev 1.xx I suppose any x670E-... range of boards, perhaps eve the hero will all have this issue. -- 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/2004552 Title: Sound doesn't work on ASUS X670E-E motherboard. Status in alsa-driver package in Ubuntu: New Bug description: None of the outputs work for my digital optical output on my ASUS ROG STRIX X670E-E GAMING WIFI motherboard since updating the ALC4080/ALC4082 firmware. The issue is resolved in the upstream package of alsa-ucm-conf (https://github.com/alsa-project/alsa-ucm-conf). When I applied the newer configs sound started working again. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Feb 2 06:08:15 2023 InstallationDate: Installed on 2023-01-08 (24 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/04/2022 dmi.bios.release: 8.5 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0805 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX X670E-E GAMING WIFI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0805:bd11/04/2022:br8.5:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX670E-EGAMINGWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2004552/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2025268] [NEW] firefox geckodriver in snap does not work
Public bug reported:
once trying to connect to geckodriver from selenium get:
```
Traceback (most recent call last):
File
"/home/maksim/git/kubeflow/bundle-kubeflow/tests-bundle/1.7/conftest.py", line
38, in driver
driver = webdriver.Firefox(options=options, service=service)
File
"/home/maksim/git/kubeflow/bundle-kubeflow/venv/lib/python3.10/site-packages/selenium/webdriver/firefox/webdriver.py",
line 196, in __init__
self.service.start()
File
"/home/maksim/git/kubeflow/bundle-kubeflow/venv/lib/python3.10/site-packages/selenium/webdriver/common/service.py",
line 100, in start
self.assert_process_still_running()
File
"/home/maksim/git/kubeflow/bundle-kubeflow/venv/lib/python3.10/site-packages/selenium/webdriver/common/service.py",
line 113, in assert_process_still_running
raise WebDriverException(f"Service {self._path} unexpectedly exited. Status
code was: {return_code}")
selenium.common.exceptions.WebDriverException: Message: Service
/snap/bin/firefox.geckodriver unexpectedly exited. Status code was: -6
```
here is a code to reproduce (see lines to toggle with comment `# toggle
lines to reproduce`). Create conftest.py with content
```
import os
import time
from datetime import datetime
from pathlib import Path
import pytest
from selenium import webdriver
from selenium.webdriver.firefox.options import Options
from selenium.webdriver.firefox.service import Service
from webdriver_manager.firefox import GeckoDriverManager
DEBUG = os.environ.get("DEBUG_KF", False)
@pytest.fixture(scope='session')
def driver(request):
"""Set up webdriver fixture."""
options = Options()
if not DEBUG:
print("Running in headless mode")
options.add_argument('--headless')
options.add_argument('--disable-gpu')
else:
options.log.level = "trace"
options.add_argument('--no-sandbox')
options.add_argument('--disable-dev-shm-usage')
options.binary_location = "/snap/bin/firefox"
# must create path,
# see https://github.com/mozilla/geckodriver/releases/tag/v0.31.0
tmp_user = Path("~/tmp").expanduser()
os.environ["TMPDIR"] = str(tmp_user)
tmp_user.mkdir(parents=True, exist_ok=True)
# toggle lines to reproduce
service = Service(GeckoDriverManager().install())
service = Service(executable_path="firefox.geckodriver")
driver = webdriver.Firefox(options=options, service=service)
driver.set_window_size(1920, 1080)
driver.maximize_window()
driver.implicitly_wait(10)
yield driver
driver.quit()
```
and test_driver.py with
```
def test_1(driver):
driver.get("https://google.de;)
a = 1
```
firefox --version
Mozilla Firefox 113.0.2
pip freeze:
absl-py==1.4.0
anyio==3.6.2
asttokens==2.2.1
async-generator==1.10
attrs==22.2.0
backcall==0.2.0
bcrypt==4.0.1
cachetools==5.3.0
certifi==2022.12.7
cffi==1.15.1
charset-normalizer==3.1.0
click==7.1.2
cloudpickle==2.2.1
cryptography==40.0.1
decorator==5.1.1
Deprecated==1.2.13
docstring-parser==0.15
exceptiongroup==1.1.1
executing==1.2.0
fire==0.5.0
google-api-core==2.11.0
google-api-python-client==1.12.11
google-auth==2.17.2
google-auth-httplib2==0.1.0
google-cloud-core==2.3.2
google-cloud-storage==2.8.0
google-crc32c==1.5.0
google-resumable-media==2.4.1
googleapis-common-protos==1.59.0
h11==0.14.0
httpcore==0.16.3
httplib2==0.22.0
httpx==0.23.3
hvac==1.1.0
idna==3.4
iniconfig==2.0.0
ipdb==0.13.13
ipython==8.12.0
jedi==0.18.2
Jinja2==3.1.2
jsonschema==4.17.3
juju==2.9.42.1
jujubundlelib==0.5.7
kfp==1.8.19
kfp-pipeline-spec==0.1.16
kfp-server-api==1.8.5
kubernetes==19.15.0
lightkube==0.12.0
lightkube-models==1.26.0.4
macaroonbakery==1.3.1
MarkupSafe==2.1.2
matplotlib-inline==0.1.6
mypy-extensions==1.0.0
oauthlib==3.2.2
outcome==1.2.0
packaging==23.0
paramiko==2.12.0
parso==0.8.3
pexpect==4.8.0
pickleshare==0.7.5
pluggy==1.0.0
prompt-toolkit==3.0.38
protobuf==3.20.3
psutil==5.9.5
ptyprocess==0.7.0
pure-eval==0.2.2
pyasn1==0.4.8
pyasn1-modules==0.2.8
pycparser==2.21
pydantic==1.10.7
Pygments==2.14.0
pyhcl==0.4.4
pymacaroons==0.13.0
PyNaCl==1.5.0
pyparsing==3.0.9
pyRFC3339==1.1
pyrsistent==0.19.3
PySocks==1.7.1
pytest==7.2.2
pytest-asyncio==0.21.0
pytest-dependency==0.5.1
pytest-operator==0.26.0
python-dateutil==2.8.2
python-dotenv==1.0.0
pytz==2023.3
PyYAML==5.4.1
requests==2.28.2
requests-oauthlib==1.3.1
requests-toolbelt==0.10.1
rfc3986==1.5.0
rsa==4.9
selenium==4.9.0
six==1.16.0
sniffio==1.3.0
sortedcontainers==2.4.0
stack-data==0.6.2
strip-hints==0.1.10
tabulate==0.9.0
termcolor==2.2.0
theblues==0.5.2
tomli==2.0.1
toposort==1.10
tqdm==4.65.0
traitlets==5.9.0
trio==0.22.0
trio-websocket==0.10.2
typer==0.7.0
typing-extensions==4.5.0
typing-inspect==0.8.0
uritemplate==3.0.1
urllib3==1.26.15
wcwidth==0.2.6
webdriver-manager==3.8.5
websocket-client==1.5.1
websockets==11.0.1
wrapt==1.15.0
wsproto==1.2.0
** Affects: firefox (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
-
once trying to connect to geckodriver
[Desktop-packages] [Bug 2016990] Re: Irregular frame rate in some fullscreen games
** Changed in: mutter (Ubuntu Lunar) Status: Fix Committed => Triaged -- 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/2016990 Title: Irregular frame rate in some fullscreen games Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Jammy: Won't Fix Status in mutter source package in Lunar: Triaged Status in mutter source package in Mantic: Fix Committed Bug description: [ Impact ] I'm having a strange issue with the game Path of Exile (free). With Ubuntu Wayland session, vsync on, I get very irregular frame rates, it jumps around 40 fps. If I switch to Plasma Wayland the game is very smooth 60 fps. I'm running the game from Steam with Proton. I've tried Proton Experimental and Proton 8.0 so far, no difference. The game uses Vulkan so I guess it's being allowed to set up all the swap and presentation stuff pretty much itself... ? MUTTER_DEBUG_DISABLE_TRIPLE_BUFFERING=1 doesn't help Mutter so it's not strictly related to triple buffering, which makes sense since it's a full screen game anyway. [ Test Plan ] None known, other than the OP to run the game. [ Where problems could occur ] In rendering performance of fullscreen apps/games. [ Workaround ] Add this to /etc/environment: CLUTTER_PAINT=disable-dynamic-max-render-time [ Other Info ] Kernel: 6.2.0-1003-lowlatency GPU: Radeon 6800 XT CPU: Ryzen 9 5900X To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2016990/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2023766] Re: Mouse cursor stutters but only over GUI elements that are animated
** Changed in: mutter (Ubuntu Lunar) Status: Fix Committed => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2023766 Title: Mouse cursor stutters but only over GUI elements that are animated Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Jammy: Triaged Status in mutter source package in Lunar: Triaged Status in mutter source package in Mantic: Fix Committed Bug description: [ Impact ] Mouse cursor stutters but only over GUI elements that are animated. [ Test Plan ] 1. Open Settings. 2. Move the cursor up/down over an empty area of the desktop. 3. Move the cursor up/down over the list pane on the left side of the Settings window. Expect: No difference in cursor smoothness whether the window below is animating in response to movement or not. [ Where problems could occur ] In frame scheduling, so the risk is more stuttering or screen freezes. [ Workaround ] Add this to /etc/environment: CLUTTER_PAINT=disable-dynamic-max-render-time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023766/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2024182] Re: GHSL-2023-139: use-after-free in user.c
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/2024182
Title:
GHSL-2023-139: use-after-free in user.c
Status in accountsservice package in Ubuntu:
In Progress
Status in accountsservice source package in Focal:
Fix Released
Status in accountsservice source package in Jammy:
Fix Released
Status in accountsservice source package in Kinetic:
Fix Released
Status in accountsservice source package in Lunar:
Fix Released
Status in accountsservice source package in Mantic:
In Progress
Bug description:
# GitHub Security Lab (GHSL) Vulnerability Report, accountsservice:
`GHSL-2023-139`
The [GitHub Security Lab](https://securitylab.github.com) team has
identified a potential security vulnerability in
[accountsservice](https://code.launchpad.net/ubuntu/+source/accountsservice).
We are committed to working with you to help resolve this issue. In
this report you will find everything you need to effectively
coordinate a resolution of this issue with the GHSL team.
If at any point you have concerns or questions about this process,
please do not hesitate to reach out to us at `security...@github.com`
(please include `GHSL-2023-139` as a reference).
If you are _NOT_ the correct point of contact for this report, please
let us know!
## Summary
An unprivileged local attacker can trigger a use-after-free
vulnerability in accountsservice by sending a D-Bus message to the
accounts-daemon process.
## Product
accountsservice
## Tested Version
[22.08.8-1ubuntu7](https://launchpad.net/ubuntu/+source/accountsservice/22.08.8-1ubuntu7)
The bug is easier to observe on Ubuntu 23.04 than on Ubuntu 22.04 LTS,
but it is present on both.
## Details
### Use-after-free when `throw_error` is called (`GHSL-2023-139`)
After receiving a D-Bus [method
call](https://dbus.freedesktop.org/doc/dbus-
specification.html#message-protocol-types), a D-Bus server is expected
to send either a `METHOD_RETURN` or a `ERROR` message back to the
client, _but not both_. This is done incorrectly in several places in
accountsservice. For example, in
[`user_change_language_authorized_cb`](https://git.launchpad.net/ubuntu/+source/accountsservice/tree/debian/patches/0010-set-
language.patch?h=import/22.08.8-1ubuntu7#n427):
```c
static void
user_change_language_authorized_cb (Daemon*daemon,
User *user,
GDBusMethodInvocation *context,
gpointer data)
{
const gchar *language = data;
if (!user_HOME_available (user)) {
/* SetLanguage was probably called from a login greeter,
and HOME not mounted and/or not decrypted.
Hence don't save anything, or else accountsservice
and ~/.pam_environment would become out of sync. */
throw_error (context, ERROR_FAILED, "not access to HOME yet
so language not saved"); <= 1
goto out;
}
out:
accounts_user_complete_set_language (ACCOUNTS_USER (user), context);
<= 2
}
```
If `user_HOME_available` returns an error, then `throw_error` is
called at 1 to send an `ERROR` message, but a regular `METHOD_RETURN`
is also sent at 2. This is incorrect D-Bus protocol, but the more
serious problem is that it causes a use-after-free because both
`throw_error` and `accounts_user_complete_set_language` decrease the
reference count on `context`. In other words, `context` is freed by
`throw_error` and a UAF occurs in
`accounts_user_complete_set_language`.
An attacker can trigger the bug above by causing `user_HOME_available`
to fail, which they can do by deleting all the files from their home
directory. But there are other incorrect uses of `throw_error` in
`user.c` which are less inconvenient to trigger. For example, this
command triggers a call to `throw_error` in `user_update_environment`
due to the invalid characters in the string.
```bash
dbus-send --system --print-reply --dest=org.freedesktop.Accounts
/org/freedesktop/Accounts/User`id -u` org.freedesktop.Accounts.User.SetLanguage
string:'**'
```
On Ubuntu 23.04, the above command causes `accounts-daemon` to crash
with a `SIGSEGV`. But on Ubuntu 22.04 LTS it doesn't cause any visible
harm. The difference is due to a recent [change in
GLib's](https://gitlab.gnome.org/GNOME/glib/-/commit/69e9ba80e2f4d2061a1a68d72bae1c32c1e4f8fa)
memory allocation: older versions of GLib used the "slice" allocator,
but newer version uses the system allocator. The system allocator
trashes the memory when it's freed in a way that causes the
[Desktop-packages] [Bug 2024560] Re: Check if 0010-set-language needs to be update for the new languages property
It's probably because you still have that colon separated list in your keyfile in /var/lib/AccountsService/users after having played with version 23.13.9-1ubuntu1. * Go to Settings -> Region & Language (it will complain there too) * Change the language to French, which alters the applicable keyfile entry to "Languages=fr;" Does that fix it? ** Changed in: accountsservice (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/2024560 Title: Check if 0010-set-language needs to be update for the new languages property Status in accountsservice package in Ubuntu: Incomplete Bug description: Upstream did changes to add a languages properties https://gitlab.freedesktop.org/accountsservice/accountsservice/-/commit/881e0ea7 I've rebased 0010-set-language to apply correctly but we should review if we need to adapt the patch to apply a similar logic to the new languages property that it's doing for old language one To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/2024560/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966413] Re: [SRU] --no-oem option is broken
This bug was fixed in the package ubuntu-drivers-common - 1:0.9.6.2~0.22.04.4 --- ubuntu-drivers-common (1:0.9.6.2~0.22.04.4) jammy; urgency=medium * ubuntu-drivers: - Fix --no-oem option stored in wrong config variable (LP: #1966413). -- Olivier Gayot Fri, 16 Jun 2023 11:49:53 +0200 -- 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/1966413 Title: [SRU] --no-oem option is broken Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Focal: New Status in ubuntu-drivers-common source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Kinetic: Won't Fix Status in ubuntu-drivers-common source package in Lunar: Fix Released Bug description: [Impact] * ubuntu-drivers supports the --no-oem option, which is meant to filter-out the OEM metapackages when running on certified hardware. * When ubuntu-drivers is invoked with --no-oem as a global option (i.e., `ubuntu-drivers --no-oem list` or `ubuntu-drivers --no-oem install`, the script crashes with the following exception: NameError: name 'install_oem_meta' is not defined * When ubuntu-drivers is invoked with --no-oem as a sub-option of "install" (i.e., `ubuntu-drivers install --no-oem`), the script does not crash but the option is silently ignored - resulting in an OEM metapackage to be installed if we are running on certified hardware. This defeats the purpose of the option. * Today, the --no-oem option can be passed to ubuntu-drivers by ubiquity as a suboption of `ubuntu-drivers install`. By default, the option is not passed to ubuntu-drivers but the users can opt-in using preseeds. If they do, their decision is essentially ignored since the OEM metapackage will still be installed: https://git.launchpad.net/ubiquity/tree/scripts/simple-plugins#n20 * As part of the 23.10 cycle, subiquity will start replacing the functionality from ubiquity for OEM installs. At the moment, subiquity relies on the version of ubuntu-drivers-common from the system being installed. But going forward, we might have to ship ubuntu-drivers- common in the subiquity snap. This means we will fetch the deb from jammy-updates since subiquity is a core22-based snap. [Test plan] 1. We will compare the result of the following commands with and without the patch (both on certified and on un-certified hardware): * ubuntu-drivers --no-oem list -> crashes without the patch. Should not crash with the patch. The list returned should not include the OEM metapackage. * ubuntu-drivers --no-oem install -> crashes without the patch. Should not crash with the patch. The list of packages installed should not include the OEM metapackage. * ubuntu-drivers install --no-oem -> without the patch, the OEM metapackage gets installed on certified hardware. With the patch, it should not. 2. We will ensure ubiquity stills manages to install ubuntu on certified hardware. We will also ensure that the OEM metapackage does not get installed when it should not. [Where problems could occur] * When used as a global option, --no-oem currently makes the script crash unconditionally. Therefore, the change should be very low risk in that regard. * When used as a suboption of "install", the --no-oem option currently gets ignored silently. If people have been automating ubuntu deployment in one way or another and have used --no-oem, they might be surprised to notice that fewer packages get installed on their target system, after the option is fixed. This is theoretically a good thing, but might require some adjustments on their end. [Original description] $ ubuntu-drivers --no-oem install Traceback (most recent call last): File "/usr/bin/ubuntu-drivers", line 490, in greet() File "/usr/lib/python3/dist-packages/click/core.py", line 764, in __call__ return self.main(*args, **kwargs) File "/usr/lib/python3/dist-packages/click/core.py", line 717, in main rv = self.invoke(ctx) File "/usr/lib/python3/dist-packages/click/core.py", line 1134, in invoke Command.invoke(self, ctx) File "/usr/lib/python3/dist-packages/click/core.py", line 956, in invoke return ctx.invoke(self.callback, **ctx.params) File "/usr/lib/python3/dist-packages/click/core.py", line 555, in invoke return callback(*args, **kwargs) File "/usr/lib/python3/dist-packages/click/decorators.py", line 64, in new_func return ctx.invoke(f, obj, *args, **kwargs) File "/usr/lib/python3/dist-packages/click/core.py", line 555, in invoke return callback(*args, **kwargs) File "/usr/bin/ubuntu-drivers", line 376, in greet config.no_oem = install_oem_meta NameError: name 'install_oem_meta' is not defined ProblemType: Bug
[Desktop-packages] [Bug 1966413] Re: [SRU] --no-oem option is broken
This bug was fixed in the package ubuntu-drivers-common - 1:0.9.7.1.1 --- ubuntu-drivers-common (1:0.9.7.1.1) lunar; urgency=medium * ubuntu-drivers: - Fix --no-oem option stored in wrong config variable (LP: #1966413) -- Olivier Gayot Fri, 16 Jun 2023 12:28:43 +0200 ** Changed in: ubuntu-drivers-common (Ubuntu Lunar) Status: Fix Committed => Fix Released ** Changed in: ubuntu-drivers-common (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1966413 Title: [SRU] --no-oem option is broken Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Focal: New Status in ubuntu-drivers-common source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Kinetic: Won't Fix Status in ubuntu-drivers-common source package in Lunar: Fix Released Bug description: [Impact] * ubuntu-drivers supports the --no-oem option, which is meant to filter-out the OEM metapackages when running on certified hardware. * When ubuntu-drivers is invoked with --no-oem as a global option (i.e., `ubuntu-drivers --no-oem list` or `ubuntu-drivers --no-oem install`, the script crashes with the following exception: NameError: name 'install_oem_meta' is not defined * When ubuntu-drivers is invoked with --no-oem as a sub-option of "install" (i.e., `ubuntu-drivers install --no-oem`), the script does not crash but the option is silently ignored - resulting in an OEM metapackage to be installed if we are running on certified hardware. This defeats the purpose of the option. * Today, the --no-oem option can be passed to ubuntu-drivers by ubiquity as a suboption of `ubuntu-drivers install`. By default, the option is not passed to ubuntu-drivers but the users can opt-in using preseeds. If they do, their decision is essentially ignored since the OEM metapackage will still be installed: https://git.launchpad.net/ubiquity/tree/scripts/simple-plugins#n20 * As part of the 23.10 cycle, subiquity will start replacing the functionality from ubiquity for OEM installs. At the moment, subiquity relies on the version of ubuntu-drivers-common from the system being installed. But going forward, we might have to ship ubuntu-drivers- common in the subiquity snap. This means we will fetch the deb from jammy-updates since subiquity is a core22-based snap. [Test plan] 1. We will compare the result of the following commands with and without the patch (both on certified and on un-certified hardware): * ubuntu-drivers --no-oem list -> crashes without the patch. Should not crash with the patch. The list returned should not include the OEM metapackage. * ubuntu-drivers --no-oem install -> crashes without the patch. Should not crash with the patch. The list of packages installed should not include the OEM metapackage. * ubuntu-drivers install --no-oem -> without the patch, the OEM metapackage gets installed on certified hardware. With the patch, it should not. 2. We will ensure ubiquity stills manages to install ubuntu on certified hardware. We will also ensure that the OEM metapackage does not get installed when it should not. [Where problems could occur] * When used as a global option, --no-oem currently makes the script crash unconditionally. Therefore, the change should be very low risk in that regard. * When used as a suboption of "install", the --no-oem option currently gets ignored silently. If people have been automating ubuntu deployment in one way or another and have used --no-oem, they might be surprised to notice that fewer packages get installed on their target system, after the option is fixed. This is theoretically a good thing, but might require some adjustments on their end. [Original description] $ ubuntu-drivers --no-oem install Traceback (most recent call last): File "/usr/bin/ubuntu-drivers", line 490, in greet() File "/usr/lib/python3/dist-packages/click/core.py", line 764, in __call__ return self.main(*args, **kwargs) File "/usr/lib/python3/dist-packages/click/core.py", line 717, in main rv = self.invoke(ctx) File "/usr/lib/python3/dist-packages/click/core.py", line 1134, in invoke Command.invoke(self, ctx) File "/usr/lib/python3/dist-packages/click/core.py", line 956, in invoke return ctx.invoke(self.callback, **ctx.params) File "/usr/lib/python3/dist-packages/click/core.py", line 555, in invoke return callback(*args, **kwargs) File "/usr/lib/python3/dist-packages/click/decorators.py", line 64, in new_func return ctx.invoke(f, obj, *args, **kwargs) File "/usr/lib/python3/dist-packages/click/core.py", line 555, in invoke return callback(*args,
[Desktop-packages] [Bug 2018504] Re: cups-browsed is using an excessive amount of CPU
This bug was fixed in the package cups-browsed - 2.0~rc1-0ubuntu1.1 --- cups-browsed (2.0~rc1-0ubuntu1.1) lunar; urgency=medium * Fixed handling of failures when creating local print queues. On a failure a global variable was set by the queue creation function running as background thread, to stop the loop for updating the local queues, but the variable was never reset, making no local queue updates done any more for the rest of the life of the daemon, making the daemon falling into a busy loop. Completely done away with the variable. It is actually not needed (LP: #2018504). -- Till Kamppeter Sun, 4 Jun 2023 18:50:57 +0200 ** Changed in: cups-browsed (Ubuntu Lunar) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-browsed in Ubuntu. https://bugs.launchpad.net/bugs/2018504 Title: cups-browsed is using an excessive amount of CPU Status in cups-browsed package in Ubuntu: Fix Released Status in cups-browsed source package in Lunar: Fix Released Bug description: [ Impact ] One observes that a certain time after booting cups-browsed suddenly starts to occupy a certain percentage or all of one CPU core. This slows down other processes on the system, consumes battery power, causes noise of the CPU fan. It does not require to have any local printers set up on ones machine, but there must be printers available in the local network. A typical trigger for this bug is a sudden disappearing of a printer in the network, for example if a laptop shares a printer and it gets suspended by closing the lid. This way the shared printer most probably disappears without the laptop's Avahi sending out some "disappered" notification. cups-browsed does not recover from the failure, once failed it consumes CPU and stops working, until being restarted, for most with the next boot. The problem got introduced on the transition from cups-browsed 1.x to 2.x (in Ubuntu 23.04). cups-browsed got a multi-threading feature added to be able to create more local queues at a time, especially when there are many printers available in the network.. The bug is in the error handling: If cups-browsed fails to access a remote printer in a sub-thread, it sets a flag to inform the main thread, to stop an update loop. The main thread misses to reset the flag once it has stopped the loop and so any further update loop during the rest of the life of cups-browsed gets stopped immediately, no printers updated at all, and as because of the updates not performed, updates are still needed and so the loop called again immediately, ending up in an infinite busy loop. And these access errors happen especially if a remote printer goes away without any DNS-SD/Avahi notification about it disappearing. So not only CPU load is caused but cups-browsed ceases completely to work. [ Test Plan ] This bug is not easy to reproduce, but at least for everyone who reported it here it occurs again and again. So everyone already suffering it is asked to test the proposed SRU package. To try to reproduce it one ideally takes 2 computers, one running Ubuntu 23.04 with the affected cups-browsed (the client) and one running any Linux and sharing printers by means of CUPS queues, Printer Applications, or the ippeveprinter utility (the server). Some ways to try to trigger the failure on the client: - Suspend the server, either by closing its laptpp lid or by selecting the "Suspend" function in its desktop's menus. - On the server start a Printer Application or ippeveprinter manually (this way no systemd watch dog applies to it). Then hard-kill its process with "kill -9 ...". - If the server is connected to the local network only by wired Ethernet, unplug its Ethernet cable. - If the server is connected to the local network only by Wi-Fi, switch it into flight mode. All these methods should make (a) shared printer(s) on the server go away without getting it properly de-registered from Avahi on the server, and so no notification being broadcasted into the local network. So the client's cups-browsed would not remove the corresponding local print queue and keep maintaining it, sooner or later failing to access the printer and then getting stuck as described above. Anyone who is suffering this bug could also simply install the proposed package and observe and when the CPU load by cups-browsed does not appear again after some days consider the fix as verified. [ Where problems could occur ] The fix does nothing more than removing the mentioned flag, and instead mark the remote printer as disappeared. This way the update loop is not stopped but finishes normally, which is no problem as the remote printers are independent, there is no reason to skip updating printers
[Desktop-packages] [Bug 2023675] Re: flip effect doesn't work on GStreamer 1.22
This bug was fixed in the package gnome-video-effects - 0.5.0-1ubuntu2 --- gnome-video-effects (0.5.0-1ubuntu2) lunar; urgency=medium * Cherry-pick patch to fix flip effect with gstreamer 1.22 (LP: #2023675) -- Jeremy Bícha Tue, 13 Jun 2023 15:34:22 -0400 ** Changed in: gnome-video-effects (Ubuntu Lunar) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-video-effects in Ubuntu. https://bugs.launchpad.net/bugs/2023675 Title: flip effect doesn't work on GStreamer 1.22 Status in GNOME Video Effects: Fix Released Status in gnome-video-effects package in Ubuntu: Fix Released Status in gnome-video-effects source package in Lunar: Fix Released Status in gnome-video-effects package in Debian: Fix Released Bug description: Impact -- The Flip effect in the Cheese app doesn't work in Ubuntu 23.10. Test Case - 1. Install the updated gnome-video-effects packages 2. Open the Cheese app 3. Click the Effects button and verify that Flip is showing a reversed version of No Effect What Could Go Wrong --- This is a simple one-line patch. gnome-video-effects has only one reverse dependency in Ubuntu: cheese. Original Bug Report --- Distributor ID: Ubuntu Description: Ubuntu 23.04 Release: 23.04 Codename: lunar gnome-video-effects: Installed: 0.5.0-1ubuntu1 Candidate: 0.5.0-1ubuntu1 Version table: *** 0.5.0-1ubuntu1 500 500 http://br.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status The file located in: /usr/share/gnome-video-effects/flip.effect is using the property "method" which is deprecated as you can see in GStreamer "https://gstreamer.freedesktop.org/documentation/videofilter/videoflip.html?gi- language=c" Deprecated version: PipelineDescription=videoflip method=horizontal- flip So the fix for this problem is to change the property to the new one, which is called video-direction, after this the effect will work correctly. Fix: PipelineDescription=videoflip video-direction=horiz The program that I used to test this effect was Cheese. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-video-effects/+bug/2023675/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012978] Autopkgtest regression report (gjs/1.72.4-0ubuntu0.22.04.1)
All autopkgtests for the newly accepted gjs (1.72.4-0ubuntu0.22.04.1) for jammy
have finished running.
The following regressions have been reported in tests triggered by the package:
gjs/1.72.4-0ubuntu0.22.04.1 (amd64)
Please visit the excuses page listed below and investigate the failures,
proceeding afterwards as per the StableReleaseUpdates policy regarding
autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#gjs
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gjs in Ubuntu.
https://bugs.launchpad.net/bugs/2012978
Title:
Memory leak
Status in gjs package in Ubuntu:
Fix Released
Status in gjs source package in Jammy:
Fix Committed
Status in gjs source package in Kinetic:
Won't Fix
Bug description:
[ Impact ]
High Memory Usage 3.1gb in 2h after reboot
[ Test case ]
Run:
env G_SLICE=always-malloc valgrind --leak-check=full \
--suppressions=/usr/share/glib-2.0/valgrind/glib.supp \
gjs -c "const GLib=imports.gi['GLib'];function leak(){const
l=GLib.Variant['new']('i',1)};leak();imports.system.gc();"
No leak should be detected
Running more installed tests under valgrind should output no leaks
(unless those caused by gobject-introspection):
sudo apt install gjs-tests
env GJS_DEBUG_TOPICS= valgrind --leak-check=full \
--suppressions=/usr/share/glib-2.0/valgrind/glib.supp \
/usr/libexec/installed-tests/gjs/minijasmine \
/usr/libexec/installed-tests/gjs/js/testGIMarshalling.js
There may be only two leaks caused by
gi_marshalling_tests_garray_boxed_struct_full_return and a gbytes one
after a ObjectInstance::prop_setter_impl call (these are leaks in the
test library that are expected with gobject-introspection 42, but
fixed in later versions).
env GJS_DEBUG_TOPICS= valgrind --leak-check=full \
--suppressions=/usr/share/glib-2.0/valgrind/glib.supp \
/usr/libexec/installed-tests/gjs/minijasmine \
/usr/libexec/installed-tests/gjs/js/testRegress.js
No leak expected
[ Regression potential ]
Gjs applications (including gnome Shell) using GVariant may misbehave
---
ProblemType: BugDistroRelease: Ubuntu 22.04
Package: gnome-shell 42.5-0ubuntu1
Uname: Linux 6.2.8-060208-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 27 22:46:07 2023
DisplayManager: gdm3
InstallationDate: Installed on 2022-03-25 (366 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
RelatedPackageVersions: mutter-common 42.5-0ubuntu1SourcePackage: gnome-shell
UpgradeStatus: Upgraded to jammy on 2022-09-03 (205 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2012978/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2023572] Autopkgtest regression report (gjs/1.72.4-0ubuntu0.22.04.1)
All autopkgtests for the newly accepted gjs (1.72.4-0ubuntu0.22.04.1) for jammy have finished running. The following regressions have been reported in tests triggered by the package: gjs/1.72.4-0ubuntu0.22.04.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#gjs [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2023572 Title: SRU gjs 1.72.4 to jammy Status in gjs package in Ubuntu: Fix Released Status in gjs source package in Jammy: Fix Committed Bug description: [ Impact ] That's the GNOME 42 stable update, including some fixes: https://gitlab.gnome.org/GNOME/gjs/-/commits/1.72.4 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME The test plan that will be used is documented at https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs [ Regression potential ] Gjs is fundamental part of the ubuntu desktop, so any failure of it may cause the desktop not even to boot (because it's being used by gdm too). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2023572/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2023215] Re: [SRU] appstream-glib can't handle em or code tags, breaking Flathub
** Description changed:
[ Impact ]
* Currently, any application that is using modern AppStream metadata
containing / tags in their description, and that is still using the
deprecated appstream-glib will fail to parse this data.
* Unfortunately, this affects some high-visibility applications now, like
Flatpak, which are unable to perform proper searches. See
https://github.com/flatpak/flatpak/issues/5434 for reference.
* This kind of issue may potentially affect more tools as well.
[ Test Plan ]
1. Open a terminal and run
sudo apt install flatpak
2. Then run
flatpak remote-add --if-not-exists flathub
https://flathub.org/repo/flathub.flatpakrepo
3. Run
flatpak search meld
The broken output may look something like:
F: Failed to parse
/var/lib/flatpak/appstream/flathub/x86_64/active/appstream.xml.gz file: Error
on line 1960 char 29: already set '
Organic Maps is a free Android & iOS offline maps app for travelers,
tourists, hikers, and cyclists.
It uses crowd-sourced OpenStreetMap data and is developed with love by
' and tried to replace with ' ('
No matches found
4. Install the updated appstream-glib packages.
5. Restart your computer then log back in.
6. Open a terminal and run
- flatpak search firefox
+ flatpak search meld
The working output looks something like
Name DescriptionApplication ID Version Branch
Remotes
Meld Compare and merge your files org.gnome.meld 3.22.0 stable
flathub
[ Where problems could occur ]
* The reverse-dependencies for appstream-glib in Ubuntu Jammy are:
flatpak-tests
unity
libmalcontent-ui-0-0
libappstream-glib-dev
gir1.2-appstreamglib-1.0
appstream-util
flatpak
* Flatpak should continue to work, and there should be no new errors in
GNOME/Unity.
[ Other Info ]
* None. Updating this should mainly help Flatpak users and should have
no ill effects on any other component of the OS.
* This issue was fixed upstream in appstream-glib 0.8.1 which is
available in Ubuntu 22.10 and newer releases.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream-glib in Ubuntu.
https://bugs.launchpad.net/bugs/2023215
Title:
[SRU] appstream-glib can't handle em or code tags, breaking Flathub
Status in appstream-glib package in Ubuntu:
Fix Released
Status in appstream-glib source package in Focal:
Fix Committed
Status in appstream-glib source package in Jammy:
Fix Released
Bug description:
[ Impact ]
* Currently, any application that is using modern AppStream metadata
containing / tags in their description, and that is still using the
deprecated appstream-glib will fail to parse this data.
* Unfortunately, this affects some high-visibility applications now, like
Flatpak, which are unable to perform proper searches. See
https://github.com/flatpak/flatpak/issues/5434 for reference.
* This kind of issue may potentially affect more tools as well.
[ Test Plan ]
1. Open a terminal and run
sudo apt install flatpak
2. Then run
flatpak remote-add --if-not-exists flathub
https://flathub.org/repo/flathub.flatpakrepo
3. Run
flatpak search meld
The broken output may look something like:
F: Failed to parse
/var/lib/flatpak/appstream/flathub/x86_64/active/appstream.xml.gz file: Error
on line 1960 char 29: already set '
Organic Maps is a free Android & iOS offline maps app for travelers,
tourists, hikers, and cyclists.
It uses crowd-sourced OpenStreetMap data and is developed with love by
' and tried to replace with ' ('
No matches found
4. Install the updated appstream-glib packages.
5. Restart your computer then log back in.
6. Open a terminal and run
flatpak search meld
The working output looks something like
Name DescriptionApplication ID Version Branch
Remotes
Meld Compare and merge your files org.gnome.meld 3.22.0 stable
flathub
[ Where problems could occur ]
* The reverse-dependencies for appstream-glib in Ubuntu Jammy are:
flatpak-tests
unity
libmalcontent-ui-0-0
libappstream-glib-dev
gir1.2-appstreamglib-1.0
appstream-util
flatpak
* Flatpak should continue to work, and there should be no new errors
in GNOME/Unity.
[ Other Info ]
* None. Updating this should mainly help Flatpak users and should
have no ill effects on any other component of the OS.
* This issue was fixed upstream in appstream-glib 0.8.1 which is
available in Ubuntu 22.10 and newer releases.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appstream-glib/+bug/2023215/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe :
[Desktop-packages] [Bug 2025169] Re: pasdsp LIB dir incorrect
** Changed in: pulseaudio (Debian) Status: Unknown => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2025169 Title: pasdsp LIB dir incorrect Status in pulseaudio package in Ubuntu: Fix Committed Status in pulseaudio package in Debian: Fix Committed Bug description: /usr/bin/padsp script is generated with wrong LD_PRELOAD="/usr/\\$$LIB/pulseaudio/libpulsedsp.so" It must be generated like LD_PRELOAD="/usr/\$LIB/pulseaudio/libpulsedsp.so" A patch is anexed thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2025169/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2025258] [NEW] return to login during a session using either synaptic or xsane
Public bug reported: hello I've just freshly installed ubuntu mate 22.04 jelly, updated package, and added 'synaptic'. Once synaptic launched, clicking on the search button (top right panel or same from the drop down menu), I am directly disconnected / exited from the session... moreover, i've the same problem with XSane but these 2 problems do not appear with the same computer under ubuntu-mate 20.04 thanks to help me for synaptic: /usr/bin/synaptic-pkexec for xsane: /usr/bin/xsane for ubuntu: Description: Ubuntu 22.04.2 LTS Release: 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-75.82-generic 5.15.99 Uname: Linux 5.15.0-75-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: MATE Date: Wed Jun 28 14:09:15 2023 DistUpgraded: 2022-10-07 15:36:36,383 DEBUG icon theme changed, re-reading DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0042] (rev 12) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics Controller [103c:2a9c] InstallationDate: Installed on 2021-06-20 (738 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: HP-Pavilion WC963AA-ABF p6355fr ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-75-generic root=UUID=82fa9fb2-b31f-47e2-88ca-361cdedad895 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to jammy on 2022-10-07 (263 days ago) dmi.bios.date: 01/28/2010 dmi.bios.release: 0.0 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.name: IONA dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd01/28/2010:br0.0:svnHP-Pavilion:pnWC963AA-ABFp6355fr:pvr:rvnMSI:rnIONA:rvr1.0:cvnHewlett-Packard:ct3:cvr:skuWC963AA#ABF: dmi.product.family: 103C_53316J dmi.product.name: WC963AA-ABF p6355fr dmi.product.sku: WC963AA#ABF dmi.sys.vendor: HP-Pavilion version.compiz: compiz 1:0.9.14.1+22.04.20220820-0ubuntu1 version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.3 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2025258 Title: return to login during a session using either synaptic or xsane Status in xorg package in Ubuntu: New Bug description: hello I've just freshly installed ubuntu mate 22.04 jelly, updated package, and added 'synaptic'. Once synaptic launched, clicking on the search button (top right panel or same from the drop down menu), I am directly disconnected / exited from the session... moreover, i've the same problem with XSane but these 2 problems do not appear with the same computer under ubuntu-mate 20.04 thanks to help me for synaptic: /usr/bin/synaptic-pkexec for xsane: /usr/bin/xsane for ubuntu: Description: Ubuntu 22.04.2 LTS Release: 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-75.82-generic 5.15.99 Uname: Linux 5.15.0-75-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: MATE Date: Wed Jun 28 14:09:15 2023 DistUpgraded: 2022-10-07 15:36:36,383 DEBUG icon theme changed, re-reading DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0042] (rev 12) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics Controller [103c:2a9c] InstallationDate: Installed on 2021-06-20 (738 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: HP-Pavilion WC963AA-ABF p6355fr ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-75-generic
[Desktop-packages] [Bug 1968910] Re: Extension NAME already installed in /usr/share/gnome-shell/extensions/NAME. /usr/share/gnome-shell/extensions/NAME will not be loaded
Here is an updated error message list from lunar: # journalctl | grep Extension Jun 28 08:27:35 vougeot gnome-shell[4088]: Extension apps-m...@gnome-shell-extensions.gcampax.github.com already installed in /usr/share/gnome-shell/extensions/apps-m...@gnome-shell-extensions.gcampax.github.com. /usr/share/gnome-shell/extensions/apps-m...@gnome-shell-extensions.gcampax.github.com will not be loaded Jun 28 08:27:35 vougeot gnome-shell[4088]: Extension auto-move-wind...@gnome-shell-extensions.gcampax.github.com already installed in /usr/share/gnome-shell/extensions/auto-move-wind...@gnome-shell-extensions.gcampax.github.com. /usr/share/gnome-shell/extensions/auto-move-wind...@gnome-shell-extensions.gcampax.github.com will not be loaded Jun 28 08:27:35 vougeot gnome-shell[4088]: Extension drive-m...@gnome-shell-extensions.gcampax.github.com already installed in /usr/share/gnome-shell/extensions/drive-m...@gnome-shell-extensions.gcampax.github.com. /usr/share/gnome-shell/extensions/drive-m...@gnome-shell-extensions.gcampax.github.com will not be loaded Jun 28 08:27:35 vougeot gnome-shell[4088]: Extension launch-new-insta...@gnome-shell-extensions.gcampax.github.com already installed in /usr/share/gnome-shell/extensions/launch-new-insta...@gnome-shell-extensions.gcampax.github.com. /usr/share/gnome-shell/extensions/launch-new-insta...@gnome-shell-extensions.gcampax.github.com will not be loaded Jun 28 08:27:35 vougeot gnome-shell[4088]: Extension native-window-placem...@gnome-shell-extensions.gcampax.github.com already installed in /usr/share/gnome-shell/extensions/native-window-placem...@gnome-shell-extensions.gcampax.github.com. /usr/share/gnome-shell/extensions/native-window-placem...@gnome-shell-extensions.gcampax.github.com will not be loaded Jun 28 08:27:35 vougeot gnome-shell[4088]: Extension places-m...@gnome-shell-extensions.gcampax.github.com already installed in /usr/share/gnome-shell/extensions/places-m...@gnome-shell-extensions.gcampax.github.com. /usr/share/gnome-shell/extensions/places-m...@gnome-shell-extensions.gcampax.github.com will not be loaded Jun 28 08:27:35 vougeot gnome-shell[4088]: Extension screenshot-window-si...@gnome-shell-extensions.gcampax.github.com already installed in /usr/share/gnome-shell/extensions/screenshot-window-si...@gnome-shell-extensions.gcampax.github.com. /usr/share/gnome-shell/extensions/screenshot-window-si...@gnome-shell-extensions.gcampax.github.com will not be loaded Jun 28 08:27:35 vougeot gnome-shell[4088]: Extension ubuntu-appindicat...@ubuntu.com already installed in /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com. /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com will not be loaded Jun 28 08:27:35 vougeot gnome-shell[4088]: Extension ubuntu-d...@ubuntu.com already installed in /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com. /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com will not be loaded Jun 28 08:27:35 vougeot gnome-shell[4088]: Extension user-th...@gnome-shell-extensions.gcampax.github.com already installed in /usr/share/gnome-shell/extensions/user-th...@gnome-shell-extensions.gcampax.github.com. /usr/share/gnome-shell/extensions/user-th...@gnome-shell-extensions.gcampax.github.com will not be loaded Jun 28 08:27:35 vougeot gnome-shell[4088]: Extension window-l...@gnome-shell-extensions.gcampax.github.com already installed in /usr/share/gnome-shell/extensions/window-l...@gnome-shell-extensions.gcampax.github.com. /usr/share/gnome-shell/extensions/window-l...@gnome-shell-extensions.gcampax.github.com will not be loaded Jun 28 08:27:35 vougeot gnome-shell[4088]: Extension windowsnaviga...@gnome-shell-extensions.gcampax.github.com already installed in /usr/share/gnome-shell/extensions/windowsnaviga...@gnome-shell-extensions.gcampax.github.com. /usr/share/gnome-shell/extensions/windowsnaviga...@gnome-shell-extensions.gcampax.github.com will not be loaded Jun 28 08:27:35 vougeot gnome-shell[4088]: Extension workspace-indica...@gnome-shell-extensions.gcampax.github.com already installed in /usr/share/gnome-shell/extensions/workspace-indica...@gnome-shell-extensions.gcampax.github.com. /usr/share/gnome-shell/extensions/workspace-indica...@gnome-shell-extensions.gcampax.github.com will not be loaded Jun 28 08:27:35 vougeot gnome-shell[4088]: Extension d...@rastersoft.com already installed in /usr/share/gnome-shell/extensions/d...@rastersoft.com. /usr/share/gnome-shell/extensions/d...@rastersoft.com will not be loaded [...] ** Tags added: kinetic lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1968910 Title: Extension NAME already installed in /usr/share/gnome- shell/extensions/NAME. /usr/share/gnome-shell/extensions/NAME will not be loaded Status in gnome-shell package in Ubuntu: Confirmed Bug description:
[Desktop-packages] [Bug 2025027] Re: When I disconnect PC from LAN, I can't turn on Wi-Fi software-wise. The option to enable Wi-Fi is not available (does not pop up and it is hidden while on LAN). Th
Based on the files attached to the bug report, the Wifi interface is not present in the system. I can see the system tried to initialize it: jún 20 08:37:40 peter-ROG-Zephyrus-G14-GA401IV-GA401IV kernel: iwlwifi :02:00.0: retry init count 0 jún 20 08:37:40 peter-ROG-Zephyrus-G14-GA401IV-GA401IV kernel: iwlwifi :02:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340 jún 20 08:37:40 peter-ROG-Zephyrus-G14-GA401IV-GA401IV kernel: iwlwifi :02:00.0: retry init count 1 jún 20 08:37:40 peter-ROG-Zephyrus-G14-GA401IV-GA401IV kernel: iwlwifi :02:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340 jún 20 08:37:41 peter-ROG-Zephyrus-G14-GA401IV-GA401IV kernel: iwlwifi :02:00.0: retry init count 2 Run the command "rfkill list", does your wifi interface show up in the output? Also check the output of "ip link". If it's not showing up it might be a problem with the kernel driver or the hardware itself. You could try to install the kernel 5.19 to see if it fixes the problem. But as far as I can see it's not a problem with Network Manager. -- 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/2025027 Title: When I disconnect PC from LAN, I can't turn on Wi-Fi software-wise. The option to enable Wi-Fi is not available (does not pop up and it is hidden while on LAN). Therefore, I can't see any available WiFi networks. The issue gets resolved when I reboot the PC. Status in network-manager package in Ubuntu: Incomplete Bug description: See my public question open here: https://askubuntu.com/questions/1474771/wifi-control-gone-after-used-lan-cable-22-04-mate I'd expect, to see the option "dis/enable wifi" at least when I disconnect from LAN, (if not regardless on LAN connection). But I can not see that option to enable wifi, nor available wifi networks even when I disconnect the LAN cable.. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: network-manager 1.36.6-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-75.82-generic 5.15.99 Uname: Linux 5.15.0-75-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Mon Jun 26 09:48:33 2023 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source /etc/network/interfaces.d/* InstallationDate: Installed on 2023-02-09 (136 days ago) InstallationMedia: Ubuntu-MATE 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IpRoute: default via 192.168.1.1 dev enx00051b9a09b6 proto dhcp metric 100 169.254.0.0/16 dev enx00051b9a09b6 scope link metric 1000 192.168.1.0/24 dev enx00051b9a09b6 proto kernel scope link src 192.168.1.2 metric 100 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.6 connected started full enabled enabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2025027/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2025169] Re: pasdsp LIB dir incorrect
** Changed in: pulseaudio (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2025169 Title: pasdsp LIB dir incorrect Status in pulseaudio package in Ubuntu: Fix Committed Status in pulseaudio package in Debian: Unknown Bug description: /usr/bin/padsp script is generated with wrong LD_PRELOAD="/usr/\\$$LIB/pulseaudio/libpulsedsp.so" It must be generated like LD_PRELOAD="/usr/\$LIB/pulseaudio/libpulsedsp.so" A patch is anexed thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2025169/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2024240] Please test proposed package
Hello errors.ubuntu.com, or anyone else affected, Accepted gnome-remote-desktop into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-remote- desktop/42.8-0ubuntu0.22.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/2024240 Title: [rdp] gnome-remote-desktop-daemon crashes in push_queue -> pw_stream_queue_buffer -> on_frame_ready -> process_frame_data -> impl_node_process_input Status in gnome-remote-desktop package in Ubuntu: Fix Released Status in gnome-remote-desktop source package in Jammy: Fix Committed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-remote-desktop. This problem was most recently seen with package version 42.7-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/11f28bb1ebb12472ffcc6dfe3e664af697e8a47a contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. Related to https://bugs.launchpad.net/ubuntu/+source/gnome-remote- desktop/+bug/2024238 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2024240/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2024240] Re: [rdp] gnome-remote-desktop-daemon crashes in push_queue -> pw_stream_queue_buffer -> on_frame_ready -> process_frame_data -> impl_node_process_input
(and it's a current topic in the ubuntu-release@ thread, so sort of unresolved generally) ** Changed in: gnome-remote-desktop (Ubuntu Jammy) Status: Incomplete => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- 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/2024240 Title: [rdp] gnome-remote-desktop-daemon crashes in push_queue -> pw_stream_queue_buffer -> on_frame_ready -> process_frame_data -> impl_node_process_input Status in gnome-remote-desktop package in Ubuntu: Fix Released Status in gnome-remote-desktop source package in Jammy: Fix Committed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-remote-desktop. This problem was most recently seen with package version 42.7-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/11f28bb1ebb12472ffcc6dfe3e664af697e8a47a contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. Related to https://bugs.launchpad.net/ubuntu/+source/gnome-remote- desktop/+bug/2024238 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2024240/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2024248] Please test proposed package
Hello Jeremy, or anyone else affected, Accepted gnome-remote-desktop into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-remote- desktop/42.8-0ubuntu0.22.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/2024248 Title: Update gnome-remote-desktop to 42.8 Status in gnome-remote-desktop package in Ubuntu: Fix Released Status in gnome-remote-desktop source package in Jammy: Fix Committed Bug description: Impact -- This is a new stable release in the GNOME 42 series It backports fixes for some crashes reported to errors.ubuntu.com Changes since the current Ubuntu 22.04 LTS release: https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/compare/42.7...42.8 Test Cases -- Complete all the test cases from https://wiki.ubuntu.com/DesktopTeam/TestPlans/RemoteDesktop except for the "New Audio Forwarding Feature" test case. What Could Go Wrong --- RDP Sharing is a new feature for Ubuntu 22.04 LTS as part of GNOME 42. (Previously only VNC Sharing was offered.) RDP Sharing can be used for providing remote support so it's important that this feature works well because it may be difficult for the remote admin to fix issues in person. gnome-remote-desktop is part of GNOME Core and falls under the GNOME Stable Release Update microrelease exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- The previous 22.04 LTS SRU, 42.7-0ubuntu1, got stuck in phased updates. We worked with upstream to do a new 42 release in hopes that this update along with the SRU for mutter 42.9 (LP: #1998286) will significantly improve the error rate. 42.7-0ubuntu1 was included in Ubuntu Desktop 22.04.2 so many users already have that version from the original install or got it before phasing was halted. https://ubuntu-archive-team.ubuntu.com/phased-updates.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2024248/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2024240] Re: [rdp] gnome-remote-desktop-daemon crashes in push_queue -> pw_stream_queue_buffer -> on_frame_ready -> process_frame_data -> impl_node_process_input
I'm accepting as this question can be resolved after accept but before release. -- 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/2024240 Title: [rdp] gnome-remote-desktop-daemon crashes in push_queue -> pw_stream_queue_buffer -> on_frame_ready -> process_frame_data -> impl_node_process_input Status in gnome-remote-desktop package in Ubuntu: Fix Released Status in gnome-remote-desktop source package in Jammy: Fix Committed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-remote-desktop. This problem was most recently seen with package version 42.7-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/11f28bb1ebb12472ffcc6dfe3e664af697e8a47a contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. Related to https://bugs.launchpad.net/ubuntu/+source/gnome-remote- desktop/+bug/2024238 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2024240/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2024238] Re: [vnc] gnome-remote-desktop-daemon crashes on -> push_queue -> pw_stream_queue_buffer -> on_frame_ready -> download_in_impl -> grd_thread_dispatch_in_impl
Hello errors.ubuntu.com, or anyone else affected, Accepted gnome-remote-desktop into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-remote- desktop/42.8-0ubuntu0.22.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gnome-remote-desktop (Ubuntu Jammy) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- 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/2024238 Title: [vnc] gnome-remote-desktop-daemon crashes on -> push_queue -> pw_stream_queue_buffer -> on_frame_ready -> download_in_impl -> grd_thread_dispatch_in_impl Status in gnome-remote-desktop package in Ubuntu: Fix Released Status in gnome-remote-desktop source package in Jammy: Fix Committed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-remote-desktop. This problem was most recently seen with package version 42.7-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/e097eda971e1f65f9170b00258037980eee90aca contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. Related to https://bugs.launchpad.net/ubuntu/+source/gnome-remote- desktop/+bug/2024240 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2024238/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2024248] Re: Update gnome-remote-desktop to 42.8
Accepting, thanks. FTR, I think it's fine to have made improvements in testing without a separate SRU bug. I have reviewed this change and testing looks objectively better now. ** Changed in: gnome-remote-desktop (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- 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/2024248 Title: Update gnome-remote-desktop to 42.8 Status in gnome-remote-desktop package in Ubuntu: Fix Released Status in gnome-remote-desktop source package in Jammy: Fix Committed Bug description: Impact -- This is a new stable release in the GNOME 42 series It backports fixes for some crashes reported to errors.ubuntu.com Changes since the current Ubuntu 22.04 LTS release: https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/compare/42.7...42.8 Test Cases -- Complete all the test cases from https://wiki.ubuntu.com/DesktopTeam/TestPlans/RemoteDesktop except for the "New Audio Forwarding Feature" test case. What Could Go Wrong --- RDP Sharing is a new feature for Ubuntu 22.04 LTS as part of GNOME 42. (Previously only VNC Sharing was offered.) RDP Sharing can be used for providing remote support so it's important that this feature works well because it may be difficult for the remote admin to fix issues in person. gnome-remote-desktop is part of GNOME Core and falls under the GNOME Stable Release Update microrelease exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- The previous 22.04 LTS SRU, 42.7-0ubuntu1, got stuck in phased updates. We worked with upstream to do a new 42 release in hopes that this update along with the SRU for mutter 42.9 (LP: #1998286) will significantly improve the error rate. 42.7-0ubuntu1 was included in Ubuntu Desktop 22.04.2 so many users already have that version from the original install or got it before phasing was halted. https://ubuntu-archive-team.ubuntu.com/phased-updates.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2024248/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2025027] Re: When I disconnect PC from LAN, I can't turn on Wi-Fi software-wise. The option to enable Wi-Fi is not available (does not pop up and it is hidden while on LAN). Th
Or do you want me to record a video ? -- 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/2025027 Title: When I disconnect PC from LAN, I can't turn on Wi-Fi software-wise. The option to enable Wi-Fi is not available (does not pop up and it is hidden while on LAN). Therefore, I can't see any available WiFi networks. The issue gets resolved when I reboot the PC. Status in network-manager package in Ubuntu: Incomplete Bug description: See my public question open here: https://askubuntu.com/questions/1474771/wifi-control-gone-after-used-lan-cable-22-04-mate I'd expect, to see the option "dis/enable wifi" at least when I disconnect from LAN, (if not regardless on LAN connection). But I can not see that option to enable wifi, nor available wifi networks even when I disconnect the LAN cable.. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: network-manager 1.36.6-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-75.82-generic 5.15.99 Uname: Linux 5.15.0-75-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Mon Jun 26 09:48:33 2023 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source /etc/network/interfaces.d/* InstallationDate: Installed on 2023-02-09 (136 days ago) InstallationMedia: Ubuntu-MATE 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IpRoute: default via 192.168.1.1 dev enx00051b9a09b6 proto dhcp metric 100 169.254.0.0/16 dev enx00051b9a09b6 scope link metric 1000 192.168.1.0/24 dev enx00051b9a09b6 proto kernel scope link src 192.168.1.2 metric 100 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.6 connected started full enabled enabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2025027/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2025027] Re: When I disconnect PC from LAN, I can't turn on Wi-Fi software-wise. The option to enable Wi-Fi is not available (does not pop up and it is hidden while on LAN). Th
I do not think there can be anything more concrete. I think I have followed everything prescribed (yes it is time consuming for me to read all that tons of text, but do wonder - I did it..) Now, if you guys do not have capacity to investigate, it'd be quite fair to admit that, rather than trying to cover it and discourage users from insisting on solution, by figuring out tasks like: First kill 6 heads dragon and bring bring three golden feathers from the phoenix firebird ;) -- 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/2025027 Title: When I disconnect PC from LAN, I can't turn on Wi-Fi software-wise. The option to enable Wi-Fi is not available (does not pop up and it is hidden while on LAN). Therefore, I can't see any available WiFi networks. The issue gets resolved when I reboot the PC. Status in network-manager package in Ubuntu: Incomplete Bug description: See my public question open here: https://askubuntu.com/questions/1474771/wifi-control-gone-after-used-lan-cable-22-04-mate I'd expect, to see the option "dis/enable wifi" at least when I disconnect from LAN, (if not regardless on LAN connection). But I can not see that option to enable wifi, nor available wifi networks even when I disconnect the LAN cable.. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: network-manager 1.36.6-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-75.82-generic 5.15.99 Uname: Linux 5.15.0-75-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Mon Jun 26 09:48:33 2023 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source /etc/network/interfaces.d/* InstallationDate: Installed on 2023-02-09 (136 days ago) InstallationMedia: Ubuntu-MATE 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IpRoute: default via 192.168.1.1 dev enx00051b9a09b6 proto dhcp metric 100 169.254.0.0/16 dev enx00051b9a09b6 scope link metric 1000 192.168.1.0/24 dev enx00051b9a09b6 proto kernel scope link src 192.168.1.2 metric 100 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.6 connected started full enabled enabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2025027/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2025169] Re: pasdsp LIB dir incorrect
Thank you for your bug report, indeed it's also reported in Debian https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028329 ** Bug watch added: Debian Bug tracker #1028329 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028329 ** Also affects: pulseaudio (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028329 Importance: Unknown Status: Unknown ** Changed in: pulseaudio (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2025169 Title: pasdsp LIB dir incorrect Status in pulseaudio package in Ubuntu: New Status in pulseaudio package in Debian: Unknown Bug description: /usr/bin/padsp script is generated with wrong LD_PRELOAD="/usr/\\$$LIB/pulseaudio/libpulsedsp.so" It must be generated like LD_PRELOAD="/usr/\$LIB/pulseaudio/libpulsedsp.so" A patch is anexed thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2025169/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020782] Re: Xdcv: Changing display scale setting and reverting it fails
Also the virtual monitors turning on at revert stops happening if you get your config file (~/.config/monitors.xml) to a state where the secondary monitors are explicitly listed as . So there is a difference between the default mutter config when monitors.xml doesn't exist, and when they are explicitly disabled by the config file. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2020782 Title: Xdcv: Changing display scale setting and reverting it fails Status in mutter package in Ubuntu: In Progress Bug description: In Amazon Workspaces running Ubuntu 22.04, when attempting to change the Scale in the Gnome Display settings, if you click on a different scale (i.e. changing from 100% to 200%) and hitting apply, it will bring up a prompt asking if you want to keep or revert the changes and there will be a timer of 20 seconds. If you try to revert the changes (either by letting the timer expire or by clicking the "revert" button), we will hit one of the following two behaviors: 1 - The setting won't revert and will keep scaled 2 - gnome-shell will show some error messages in syslog and the display will be "corrupted", where the only window you are able to click is the display setting and if you try to drag it, it will leave a "blur" throughout the window (per discussions, this seems to be https://launchpad.net/bugs/1924689) For both situations, changing the display resolution (i.e. going into and out of full screen in the workspaces client) will fix the issue When hitting situation 1, syslog shows: May 17 17:33:10 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x1080 (19.958942) for monitor 'unknown unknown' When hitting situation 2, syslog shows: May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use fallback monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Impossible to set scaling on crtc 59 to 1.00, error id 2 May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Xlib: extension "DPMS" missing on display ":1". May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Object St.Label (0x557090d07de0), has been already disposed — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: == Stack trace for context 0x557090bee180 == May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #0 557093f00e68 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js:1349 (2cdac32b2e20 @ 105) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #1 557093f00dd8 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/dash.js:42 (2cdac32a5d80 @ 27) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #2 557093f00d58 i resource:///org/gnome/shell/ui/dash.js:545 (20c3e0d20970 @ 24) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: JS ERROR: TypeError: monitor is null#012_updateWorkAreaBox@resource:///org/gnome/shell/ui/overviewControls.js:58:26#012_init/<@resource:///org/gnome/shell/ui/overviewControls.js:51:45 Sometimes the stack trace isn't shown, but the symptom is the same: May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use fallback monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Impossible to set scaling on crtc 59 to 1.00, error id 2 May 17 18:31:40 U-1AZMIM8SIPZ6I gnome-shell[3030]: Xlib: extension "DPMS" missing on display ":1". I'm unable to reproduce the problem if I manually install ubuntu-desktop and use the Nice DCV Server (as used by Workspaces) by following the steps from (using the xorg-x11-drv-dummy):
[Desktop-packages] [Bug 2020782] Re: Xdcv: Changing display scale setting and reverting it fails
Looking at this again, I'm now testing an even smaller patch (named vv6): @@ -92,6 +92,9 @@ calculate_xrandr_refresh_rate (XRRModeIn float h_total; float v_total; + if (xmode->hTotal == 0 || xmode->vTotal == 0) +return 0.0f; + h_total = (float) xmode->hTotal; v_total = (float) xmode->vTotal; and it seems it still has the same problem. The interesting thing about this is that the patch is now so small that it shows the remaining problem (other virtual monitors automatically turned on) is not a bug in my patch but is a pre-existing bug somewhere. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2020782 Title: Xdcv: Changing display scale setting and reverting it fails Status in mutter package in Ubuntu: In Progress Bug description: In Amazon Workspaces running Ubuntu 22.04, when attempting to change the Scale in the Gnome Display settings, if you click on a different scale (i.e. changing from 100% to 200%) and hitting apply, it will bring up a prompt asking if you want to keep or revert the changes and there will be a timer of 20 seconds. If you try to revert the changes (either by letting the timer expire or by clicking the "revert" button), we will hit one of the following two behaviors: 1 - The setting won't revert and will keep scaled 2 - gnome-shell will show some error messages in syslog and the display will be "corrupted", where the only window you are able to click is the display setting and if you try to drag it, it will leave a "blur" throughout the window (per discussions, this seems to be https://launchpad.net/bugs/1924689) For both situations, changing the display resolution (i.e. going into and out of full screen in the workspaces client) will fix the issue When hitting situation 1, syslog shows: May 17 17:33:10 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x1080 (19.958942) for monitor 'unknown unknown' When hitting situation 2, syslog shows: May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use fallback monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Impossible to set scaling on crtc 59 to 1.00, error id 2 May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Xlib: extension "DPMS" missing on display ":1". May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Object St.Label (0x557090d07de0), has been already disposed — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: == Stack trace for context 0x557090bee180 == May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #0 557093f00e68 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js:1349 (2cdac32b2e20 @ 105) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #1 557093f00dd8 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/dash.js:42 (2cdac32a5d80 @ 27) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #2 557093f00d58 i resource:///org/gnome/shell/ui/dash.js:545 (20c3e0d20970 @ 24) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: JS ERROR: TypeError: monitor is null#012_updateWorkAreaBox@resource:///org/gnome/shell/ui/overviewControls.js:58:26#012_init/<@resource:///org/gnome/shell/ui/overviewControls.js:51:45 Sometimes the stack trace isn't shown, but the symptom is the same: May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use fallback monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Impossible to set scaling on crtc 59 to 1.00, error id 2 May 17 18:31:40 U-1AZMIM8SIPZ6I gnome-shell[3030]: Xlib: extension "DPMS" missing on display ":1".
[Desktop-packages] [Bug 2023572] Please test proposed package
Hello Marco, or anyone else affected, Accepted gjs into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gjs/1.72.4-0ubuntu0.22.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2023572 Title: SRU gjs 1.72.4 to jammy Status in gjs package in Ubuntu: Fix Released Status in gjs source package in Jammy: Fix Committed Bug description: [ Impact ] That's the GNOME 42 stable update, including some fixes: https://gitlab.gnome.org/GNOME/gjs/-/commits/1.72.4 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME The test plan that will be used is documented at https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs [ Regression potential ] Gjs is fundamental part of the ubuntu desktop, so any failure of it may cause the desktop not even to boot (because it's being used by gdm too). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2023572/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012978] Re: Memory leak
Hello Vladimir, or anyone else affected,
Accepted gjs into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/gjs/1.72.4-0ubuntu0.22.04.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: gjs (Ubuntu Jammy)
Status: Triaged => Fix Committed
** Tags added: verification-needed verification-needed-jammy
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gjs in Ubuntu.
https://bugs.launchpad.net/bugs/2012978
Title:
Memory leak
Status in gjs package in Ubuntu:
Fix Released
Status in gjs source package in Jammy:
Fix Committed
Status in gjs source package in Kinetic:
Won't Fix
Bug description:
[ Impact ]
High Memory Usage 3.1gb in 2h after reboot
[ Test case ]
Run:
env G_SLICE=always-malloc valgrind --leak-check=full \
--suppressions=/usr/share/glib-2.0/valgrind/glib.supp \
gjs -c "const GLib=imports.gi['GLib'];function leak(){const
l=GLib.Variant['new']('i',1)};leak();imports.system.gc();"
No leak should be detected
Running more installed tests under valgrind should output no leaks
(unless those caused by gobject-introspection):
sudo apt install gjs-tests
env GJS_DEBUG_TOPICS= valgrind --leak-check=full \
--suppressions=/usr/share/glib-2.0/valgrind/glib.supp \
/usr/libexec/installed-tests/gjs/minijasmine \
/usr/libexec/installed-tests/gjs/js/testGIMarshalling.js
There may be only two leaks caused by
gi_marshalling_tests_garray_boxed_struct_full_return and a gbytes one
after a ObjectInstance::prop_setter_impl call (these are leaks in the
test library that are expected with gobject-introspection 42, but
fixed in later versions).
env GJS_DEBUG_TOPICS= valgrind --leak-check=full \
--suppressions=/usr/share/glib-2.0/valgrind/glib.supp \
/usr/libexec/installed-tests/gjs/minijasmine \
/usr/libexec/installed-tests/gjs/js/testRegress.js
No leak expected
[ Regression potential ]
Gjs applications (including gnome Shell) using GVariant may misbehave
---
ProblemType: BugDistroRelease: Ubuntu 22.04
Package: gnome-shell 42.5-0ubuntu1
Uname: Linux 6.2.8-060208-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 27 22:46:07 2023
DisplayManager: gdm3
InstallationDate: Installed on 2022-03-25 (366 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
RelatedPackageVersions: mutter-common 42.5-0ubuntu1SourcePackage: gnome-shell
UpgradeStatus: Upgraded to jammy on 2022-09-03 (205 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2012978/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2023572] Re: SRU gjs 1.72.4 to jammy
This looks good. Accepting, but subject to test plan review. See https://discourse.ubuntu.com/t/scope-of-gnome-mru/18041/61?u=rbasak. It's probably worth waiting on SRU verification until the test plan is approved. ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2023572 Title: SRU gjs 1.72.4 to jammy Status in gjs package in Ubuntu: Fix Released Status in gjs source package in Jammy: Fix Committed Bug description: [ Impact ] That's the GNOME 42 stable update, including some fixes: https://gitlab.gnome.org/GNOME/gjs/-/commits/1.72.4 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME The test plan that will be used is documented at https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs [ Regression potential ] Gjs is fundamental part of the ubuntu desktop, so any failure of it may cause the desktop not even to boot (because it's being used by gdm too). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2023572/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2023572] Re: SRU gjs 1.72.4 to jammy
** Description changed: [ Impact ] That's the GNOME 42 stable update, including some fixes: https://gitlab.gnome.org/GNOME/gjs/-/commits/1.72.4 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME - Gjs applications (such as GNOME Maps, GNOME Characters, GNOME - Weather...) and GNOME Shell and its components and extensions should - continue working. + The test plan that will be used is documented at + https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs [ Regression potential ] Gjs is fundamental part of the ubuntu desktop, so any failure of it may cause the desktop not even to boot (because it's being used by gdm too). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2023572 Title: SRU gjs 1.72.4 to jammy Status in gjs package in Ubuntu: Fix Released Status in gjs source package in Jammy: Fix Committed Bug description: [ Impact ] That's the GNOME 42 stable update, including some fixes: https://gitlab.gnome.org/GNOME/gjs/-/commits/1.72.4 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME The test plan that will be used is documented at https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs [ Regression potential ] Gjs is fundamental part of the ubuntu desktop, so any failure of it may cause the desktop not even to boot (because it's being used by gdm too). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2023572/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1979891] Re: Firefox becomes unusable when adjusting window size
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: firefox (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1979891 Title: Firefox becomes unusable when adjusting window size Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Confirmed Bug description: OS version: Ubuntu 22.04 LTS Firefox version: 1:1snap1-0ubuntu2 - 101.0.1 (64-bit) Sometimes when I adjust the size of a Firefox window, that window becomes messed up: the contents don't fill the window, not all the controls are visible, and clicks are offset, so if I click on one spot, the window behaves as if I clicked on a different spot (so it's impossible to use Firefox in that window anymore). I seem to remember being able to fix this by dragging and dropping the window onto a different monitor or workspace in the GNOME Activities view, but I'm currently experiencing the problem and that is not helping. I took a screenshot of what's currently going on (attached) which happened when I tried to maximize the window. This is on a laptop with an external monitor that I'm using in portrait mode, via a USB-C connection that's converted to HDMI. I had plugged in to the external monitor a few minutes before this happens, and plugging in or possibly unplugging seems to make this bug more likely. This is a relatively new problem, starting within the last few weeks. (Maybe after I switched to the snap version of Firefox? I guess that was when I upgraded from the previous LTS version of Ubuntu.) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jun 25 15:23:13 2022 DistUpgraded: 2022-05-27 14:03:05,108 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.32, 5.15.0-39-generic, x86_64: installed virtualbox/6.1.32, 5.15.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:07e6] InstallationDate: Installed on 2018-11-23 (1309 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. XPS 13 9370 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-40-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-05-27 (29 days ago) dmi.bios.date: 03/22/2022 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.0 dmi.board.name: 0H0VG3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.0:bd03/22/2022:br1.19:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0H0VG3:rvrA00:cvnDellInc.:ct10:cvr:sku07E6: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1979891/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2016990] Re: Irregular frame rate in some fullscreen games
** Tags removed: fixed-in-mutter-45 ** Tags added: fixed-in-mutter-44.3 ** Changed in: mutter (Ubuntu Lunar) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2016990 Title: Irregular frame rate in some fullscreen games Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Jammy: Won't Fix Status in mutter source package in Lunar: Fix Committed Status in mutter source package in Mantic: Fix Committed Bug description: [ Impact ] I'm having a strange issue with the game Path of Exile (free). With Ubuntu Wayland session, vsync on, I get very irregular frame rates, it jumps around 40 fps. If I switch to Plasma Wayland the game is very smooth 60 fps. I'm running the game from Steam with Proton. I've tried Proton Experimental and Proton 8.0 so far, no difference. The game uses Vulkan so I guess it's being allowed to set up all the swap and presentation stuff pretty much itself... ? MUTTER_DEBUG_DISABLE_TRIPLE_BUFFERING=1 doesn't help Mutter so it's not strictly related to triple buffering, which makes sense since it's a full screen game anyway. [ Test Plan ] None known, other than the OP to run the game. [ Where problems could occur ] In rendering performance of fullscreen apps/games. [ Workaround ] Add this to /etc/environment: CLUTTER_PAINT=disable-dynamic-max-render-time [ Other Info ] Kernel: 6.2.0-1003-lowlatency GPU: Radeon 6800 XT CPU: Ryzen 9 5900X To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2016990/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2023766] Re: Mouse cursor stutters but only over GUI elements that are animated
** Tags removed: fixed-in-mutter-45 ** Tags added: fixed-in-mutter-44.3 ** Changed in: mutter (Ubuntu Lunar) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2023766 Title: Mouse cursor stutters but only over GUI elements that are animated Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Jammy: Triaged Status in mutter source package in Lunar: Fix Committed Status in mutter source package in Mantic: Fix Committed Bug description: [ Impact ] Mouse cursor stutters but only over GUI elements that are animated. [ Test Plan ] 1. Open Settings. 2. Move the cursor up/down over an empty area of the desktop. 3. Move the cursor up/down over the list pane on the left side of the Settings window. Expect: No difference in cursor smoothness whether the window below is animating in response to movement or not. [ Where problems could occur ] In frame scheduling, so the risk is more stuttering or screen freezes. [ Workaround ] Add this to /etc/environment: CLUTTER_PAINT=disable-dynamic-max-render-time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023766/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2024560] Re: Check if 0010-set-language needs to be update for the new languages property
I'm reopening because I think there is still work to be done there, opening the users panel in setting leads to those warnings 10:11:00.4223 **[19511]: WARNING: Couldn't get locale for language: fr_FR:en 10:11:00.4224 GnomeDesktop[19511]:CRITICAL: gnome_get_language_from_locale: assertion '*locale != '\0'' failed ii accountsservice23.13.9-2ubuntu1 amd64query and manipulate user account information ** Changed in: accountsservice (Ubuntu) Status: Fix Released => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/2024560 Title: Check if 0010-set-language needs to be update for the new languages property Status in accountsservice package in Ubuntu: Confirmed Bug description: Upstream did changes to add a languages properties https://gitlab.freedesktop.org/accountsservice/accountsservice/-/commit/881e0ea7 I've rebased 0010-set-language to apply correctly but we should review if we need to adapt the patch to apply a similar logic to the new languages property that it's doing for old language one To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/2024560/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2015962] Re: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_obje
This bug was fixed in the package accountsservice - 23.13.9-2ubuntu1 --- accountsservice (23.13.9-2ubuntu1) mantic; urgency=medium * Includes some extra upstream bugfixes accountsservice (23.13.9-2) unstable; urgency=medium * debian/patches/git_user_manager.patch: - Disconnect from manager signals when freeing a request and resolve indicator-messages crashing on logout (lp: #2015962) * debian/patches/git_default_gdm.patch: - default to gdm if there display-manager.service isn't a known target, which is the case for our gdm called gdm3, fixes the service crashing when trying to toggle autologin (lp: #2024870) -- Sebastien Bacher Mon, 26 Jun 2023 16:25:07 +0200 ** Changed in: accountsservice (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ayatana-indicator-messages in Ubuntu. https://bugs.launchpad.net/bugs/2015962 Title: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object_unref() from im_accounts_service_dispose() Status in accountsservice: Fix Released Status in accountsservice package in Ubuntu: Fix Released Status in ayatana-indicator-messages package in Ubuntu: In Progress Status in indicator-messages package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-messages. This problem was most recently seen with package version 13.10.1+18.10.20180918-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/94c77bb11d79da78a8cb610adb9252f41d2ab4a4 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/2015962/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2024560] Re: Check if 0010-set-language needs to be update for the new languages property
This bug was fixed in the package accountsservice - 23.13.9-2ubuntu1 --- accountsservice (23.13.9-2ubuntu1) mantic; urgency=medium * Includes some extra upstream bugfixes accountsservice (23.13.9-2) unstable; urgency=medium * debian/patches/git_user_manager.patch: - Disconnect from manager signals when freeing a request and resolve indicator-messages crashing on logout (lp: #2015962) * debian/patches/git_default_gdm.patch: - default to gdm if there display-manager.service isn't a known target, which is the case for our gdm called gdm3, fixes the service crashing when trying to toggle autologin (lp: #2024870) -- Sebastien Bacher Mon, 26 Jun 2023 16:25:07 +0200 ** Changed in: accountsservice (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/2024560 Title: Check if 0010-set-language needs to be update for the new languages property Status in accountsservice package in Ubuntu: Fix Released Bug description: Upstream did changes to add a languages properties https://gitlab.freedesktop.org/accountsservice/accountsservice/-/commit/881e0ea7 I've rebased 0010-set-language to apply correctly but we should review if we need to adapt the patch to apply a similar logic to the new languages property that it's doing for old language one To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/2024560/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2024870] Re: accountsservice segfault when toggling autologin
This bug was fixed in the package accountsservice - 23.13.9-2ubuntu1 --- accountsservice (23.13.9-2ubuntu1) mantic; urgency=medium * Includes some extra upstream bugfixes accountsservice (23.13.9-2) unstable; urgency=medium * debian/patches/git_user_manager.patch: - Disconnect from manager signals when freeing a request and resolve indicator-messages crashing on logout (lp: #2015962) * debian/patches/git_default_gdm.patch: - default to gdm if there display-manager.service isn't a known target, which is the case for our gdm called gdm3, fixes the service crashing when trying to toggle autologin (lp: #2024870) -- Sebastien Bacher Mon, 26 Jun 2023 16:25:07 +0200 ** Changed in: accountsservice (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/2024870 Title: accountsservice segfault when toggling autologin Status in accountsservice package in Ubuntu: Fix Released Bug description: Error encountered after first boot ubuntu-gnome-desktop installed on LiveServer Daily 23.10 attempting to set AutoLogin in Settings>User. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: accountsservice 23.13.9-1ubuntu1 Uname: Linux 6.3.0-7-generic x86_64 Architecture: amd64 Date: Thu Jun 22 21:28:14 2023 ExecutablePath: /usr/libexec/accounts-daemon ExecutableTimestamp: 1687359023 ProcCmdline: /usr/libexec/accounts-daemon ProcCwd: / ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) Signal: 11 SourcePackage: accountsservice UserGroups: N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/2024870/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1991022] Re: [SRU] Service activation via Systemd socket
Verified in Lobster (0.11.4-2ubuntu0.1) and Kinetic (0.11.3-1ubuntu1.1) that the test case produces sound. ** Tags removed: verification-needed verification-needed-kinetic verification-needed-lunar ** Tags added: verification-done verification-done-kinetic verification-done-lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to speech-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1991022 Title: [SRU] Service activation via Systemd socket Status in speech-dispatcher package in Ubuntu: Fix Released Status in speech-dispatcher source package in Jammy: Fix Committed Status in speech-dispatcher source package in Kinetic: Fix Committed Status in speech-dispatcher source package in Lunar: Fix Committed Bug description: [Description] Systemd socket activation for Speech Dispatcher. - Creates the speech-dispatcher.socket; - Modifies the server so that it can detect it was automatically launched by that socket activation; and - Modifies the Autotools files accordingly. [Impact] Its relevance is described in [1], of which I quote the essential parts [my notes in brackets]: > Sandboxed applications [snaps] that use Speech Dispatcher currently bundle it inside of the sandbox, so that each application has its own "private" instance of Speech Dispatcher running. This works more or less, but it has the downside that speech dispatcher cannot coordinate simultaneous messages from multiple apps. When multiple sandboxed apps use Speech Dispatcher at the same time, the text reading overlaps. > > In order to solve this issue, I would really like to give sandboxed apps access to the Speech Dispatcher instance of the host. That can be done by implementing the action of the speech dispatcher service via a Systemd socket: > The only issue I see is having it auto launch. I think it would probably be a good step forward for speech-dispatcher to be auto launched by a systemd socket like other daemons already do on demand. That way the host speech-dispatcher with it's configuration would be used by all snaps, [Additional information] The changes are already merged upstream[21][22][23], but still not released. I have built and installed the package in Mantic and verified that running spd-say from inside a snap causes the host's dispatcher to spawn and emit sound — see 'Test case' for more details. This has also been verified in Jammy by Lissyx[31][32] and there is a merge proposal[4] for the Firefox snap that assumes the incorporation of this delta in speech-dispatcher. Note: Either the installed socket needs to be started manually to function correctly or the session must be restarted or the system needs to be rebooted. [Test case] Install the proposed speech-dispatcher and the snap[5] containing spd- say. Restart the user session so the new systemd unit gets activated. Then, snap run --shell geheim $ XDG_RUNTIME_DIR=/run/user/1000 spd-say hi should say "hi" through your loudspeakers. If you have no loudspeakers or if you are testing in a virtual machine, you can use Pavucontrol to verify that the dummy output device meter shows activity right after you issue the last command. [Regression potential] If the socket communication were not working (e.g. connection refused), then this would result in text-to-speech failing, even for a not sandboxed program. Do note, however, that if the socket were not available for whatever reason (e.g. the user didn't start it manually nor rebooted), then the sd_listen_fds(0) >= 1 test would be false and no regression would be observed, as then the program would fallback to its usual operation. [1] https://github.com/brailcom/speechd/issues/335 [21] https://github.com/brailcom/speechd/pull/763 [22] https://github.com/brailcom/speechd/pull/776 [23] https://github.com/brailcom/speechd/pull/817 [31] https://irclogs.ubuntu.com/2023/05/17/%23ubuntu-desktop.html [32] https://bugzilla.mozilla.org/show_bug.cgi?id=1729750#c23 [4] https://github.com/canonical/firefox-snap/pull/12 [5] https://launchpad.net/~nteodosio/+snap/test-speechd/+build/2103550 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1991022/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
