[Desktop-packages] [Bug 2036889] Re: gnome-shell crashed with SIGABRT: libmutter:ERROR:../src/backends/x11/meta-barrier-x11.c:231:meta_x11_barriers_free: assertion failed: (g_hash_table_size (x11_barr
** Changed in: mutter Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2036889 Title: gnome-shell crashed with SIGABRT: libmutter:ERROR:../src/backends/x11/meta- barrier-x11.c:231:meta_x11_barriers_free: assertion failed: (g_hash_table_size (x11_barriers->barriers) == 0) Status in Mutter: New Status in mutter package in Ubuntu: Confirmed Bug description: it just showed this report ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 21 13:19:48 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-02 (19 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230829) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45.0-1ubuntu1 Signal: 6 SourcePackage: gnome-shell Stacktrace: #0 0x7fcc84cb in ?? () No symbol table info available. Backtrace stopped: Cannot access memory at address 0x7ffe88bb8120 StacktraceTop: ?? () Title: gnome-shell crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2036889/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017173] Re: Ubuntu desktop settings unavailable
I've deleted `~/.local/share/gnome-shell/extensions` and reinstalled gnome-control-center and rebooted the system but the bug still persisted till I reinstalled ubuntu-desktop using the following command: sudo apt install --reinstall ubuntu-desktop -- 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/2017173 Title: Ubuntu desktop settings unavailable Status in gnome-control-center package in Ubuntu: Invalid Bug description: I have just upgraded from 22.10 to 23.04. Now, in "Settings", the "Ubuntu Desktop" option shows: "No ubuntu settings found. Oops, something has gone wrong. Please report a bug in Launchpad." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2017173/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017173] Re: Ubuntu desktop settings unavailable
-- 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/2017173 Title: Ubuntu desktop settings unavailable Status in gnome-control-center package in Ubuntu: Invalid Bug description: I have just upgraded from 22.10 to 23.04. Now, in "Settings", the "Ubuntu Desktop" option shows: "No ubuntu settings found. Oops, something has gone wrong. Please report a bug in Launchpad." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2017173/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037017] Re: Sharing tab hangs gnome-control-center
Thank you for your bug report. I haven't see the issue on amd64 but I don't know if that means it's arm64 specific. Could you check if there is anything printed in the journal at this time? It could be an issue with rygel or another of the sharing services. Also could you get a gdb 't a a bt' of the process while it's hanging? Ideally with libglib2.0-0-dbgsym libgtk-4-1-dbgsym gnome-control-center- dbgsym installed? It should give us a clue of where it's hanging (likely waiting for a reply from a dbus service) ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => High ** Changed in: gnome-control-center (Ubuntu) Status: New => Incomplete -- 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/2037017 Title: Sharing tab hangs gnome-control-center Status in gnome-control-center package in Ubuntu: Incomplete Bug description: On the Ubuntu Desktop for Raspberry Pi current Mantic beta images (with gnome-control-center version 1.45.0-1ubuntu1), on a Raspberry Pi 4B, switching to the "Sharing" tab hangs the application (presenting the Force Quit / Wait overlay prompt). Worse, re-launching the application simply re-opens the "Sharing" tab resulting in another hang. A workaround for now is to launch the application from the command-line, forcing initial selection of a different tab, e.g. "gnome-control-center info-overview". Launching the application from the command line with "gnome-control- center sharing" also causes the hang, but unfortunately there's no additional console output to shed any light on the situation. I'm not sure if this is Pi specific (haven't attempted it on any other platforms yet). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2037017/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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]
Hi, seems like I'm a bit late to the party, but anyways ... I recently reported a bug against liferea (a GTK3 based RSS reader using WebkitGTK as an HTML rendering engine), where the HTML preview frame would appear empty with the newly released webkitgtk-2.42.0, while with webkitgtk-2.40.5 (and all previous webkitgtk versions) the preview frame would be rendered "normally" (ie. as expected). The devs asked me if I had an Nvidia GPU, and if the problem would disappear if I ran liferea with WEBKIT_DISABLE_COMPOSITING_MODE=1. I do and it did, so they directed me over here. Here's a link to my bug report, which also includes screenshots: https://github.com/lwindolf/liferea/issues/1306 Is this the same bug that is being discussed here? If not, should I open a new bug report, or is there already an existing one that I could follow? Please let me know. Thanks! -- 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 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: Confirmed 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 ac
[Desktop-packages] [Bug 2023322]
(In reply to Thomas Zajic from comment #56) > Is this the same bug that is being discussed here? No, because the problem here is specific to GTK 4 and has been around for years. That is, since you didn't have this problem with 2.40, this bug is not your bug. You're probably hitting either bug #259644 or bug #261874, depending on whether or not you see those KMS DRM_IOCTL_MODE_CREATE_DUMB error messages. Please confirm. (In reply to Kdwk from comment #55) > Copied over from the duplicate bug, my setup is the following: > > Tested with: Epiphany Technology Preview/ WebKitGTK 2.41.6; Nvidia RTX 4070 > (driver version 535, via Universal Blue Nvidia Image) > > No web view is rendered. Blank screen. > > Console output: > [kdwk@fedora ~]$ flatpak run org.gnome.Epiphany.Devel > KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied > Failed to create GBM buffer of size 1148x893: Permission denied > KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied > Failed to create GBM buffer of size 1148x893: Permission denied > KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied > Failed to create GBM buffer of size 1148x893: Permission denied > Failed to create EGL images for DMABufs with file descriptors -1, -1 and -1 > [reply] [−] Comment 1 This issue is now tracked in bug #259644. -- 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 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: Confirmed 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 C
[Desktop-packages] [Bug 2023322] Re: Unable to setup Google Online Accounts with Nvidia drivers
** Bug watch added: github.com/lwindolf/liferea/issues #1306 https://github.com/lwindolf/liferea/issues/1306 -- 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 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: Confirmed 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 accor
[Desktop-packages] [Bug 2037016] Re: Firefox redundantly appears twice in Default Apps
Thanks, the issue there is the firefox deb ships a firefox.desktop in addition of the one provided by the snap and settings don't filter out NoDisplay items by design. I think the firefox.desktop was there for compatibility reason on upgrade (having the file vanishing from disk would make the launcher remove the entry before we would have the opportunity to update the configuration) but we could probably remove it now. ** Package changed: gnome-control-center (Ubuntu) => firefox (Ubuntu) ** Changed in: firefox (Ubuntu) Status: New => Triaged -- 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/2037016 Title: Firefox redundantly appears twice in Default Apps Status in firefox package in Ubuntu: Triaged Bug description: Under the current Mantic beta, Firefox redundantly appears twice in the Web and Photos drop-downs under the "Default Apps" tab of gnome- control-center. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2037016/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017173] Re: Ubuntu desktop settings unavailable
if you still have the issue please report a new bug using 'ubuntu-bug gnome-control-center' -- 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/2017173 Title: Ubuntu desktop settings unavailable Status in gnome-control-center package in Ubuntu: Invalid Bug description: I have just upgraded from 22.10 to 23.04. Now, in "Settings", the "Ubuntu Desktop" option shows: "No ubuntu settings found. Oops, something has gone wrong. Please report a bug in Launchpad." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2017173/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037055] Re: gnome-shell crashed with SIGABRT: ERROR:../src/shell-app.c:1644:shell_app_dispose: assertion failed: (app->state == SHELL_APP_STATE_STOPPED)
** Summary changed: - gnome-shell crashed with SIGABRT in __pthread_kill_implementation() + gnome-shell crashed with SIGABRT: ERROR:../src/shell-app.c:1644:shell_app_dispose: assertion failed: (app->state == SHELL_APP_STATE_STOPPED) ** Information type changed from Private to Public -- 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/2037055 Title: gnome-shell crashed with SIGABRT: ERROR:../src/shell- app.c:1644:shell_app_dispose: assertion failed: (app->state == SHELL_APP_STATE_STOPPED) Status in gnome-shell package in Ubuntu: New Bug description: Running MATLAB 2023b with Matlab Connector installed suddenly crashed gnome-shell and returned to gdm. Has been running fine w/o the Connector but not sure it's related. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Sep 22 10:05:51 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-18 (4 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230918) JournalErrors: -- No entries -- ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45.0-1ubuntu1 Signal: 6 SourcePackage: gnome-shell StacktraceTop: ??? () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 ??? () at /usr/lib/gnome-shell/libshell-13.so g_object_unref () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ??? () at /lib/x86_64-linux-gnu/libgjs.so.0 Title: gnome-shell crashed with SIGABRT in ???() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037055/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2036611] Re: FFe: Mesa 23.2.0
i386 build fixed by a new upstream bugfix ** Description changed: Upstream still hasn't released Mesa 23.2.0 (as of Sep 19th) which is almost seven weeks past it's original release date. But at least we have an rc3 which is "only" two weeks old. Yes, we are getting close to mantic release but this series is something we want for Intel Meteor Lake support. This is now fresh in Debian unstable, and has been in Fedora 39 for a month already without any apparent drama. Build available at the x-staging ppa https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging/+packages - (status: i386 build failed due to an upstream bug, which requires llvmspirvlib headers to exist even if rusticl OpenCL driver is not enabled) xnox: Separately to amd64, this new mesa would also be useful on many arm64 platforms with a lot of improvements for RaspberryPi, Ubuntu Concept X13s, and Apple / Asahi hardware. I strongly request that upgrade of mesa is also considered because of the Arm platform improvements in Mesa 23.2.0. The request is to ship rc, SRU upto final upstream GA .0 release, and enforce SRU policy after that. Other distributions are also shipping this Mesa RC largely due to the very same reasons, thus this will align hardware compatiblity and performance with other distributions launching this autumn. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2036611 Title: FFe: Mesa 23.2.0 Status in mesa package in Ubuntu: New Bug description: Upstream still hasn't released Mesa 23.2.0 (as of Sep 19th) which is almost seven weeks past it's original release date. But at least we have an rc3 which is "only" two weeks old. Yes, we are getting close to mantic release but this series is something we want for Intel Meteor Lake support. This is now fresh in Debian unstable, and has been in Fedora 39 for a month already without any apparent drama. Build available at the x-staging ppa https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging/+packages xnox: Separately to amd64, this new mesa would also be useful on many arm64 platforms with a lot of improvements for RaspberryPi, Ubuntu Concept X13s, and Apple / Asahi hardware. I strongly request that upgrade of mesa is also considered because of the Arm platform improvements in Mesa 23.2.0. The request is to ship rc, SRU upto final upstream GA .0 release, and enforce SRU policy after that. Other distributions are also shipping this Mesa RC largely due to the very same reasons, thus this will align hardware compatiblity and performance with other distributions launching this autumn. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2036611/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen in Wayland
** Changed in: mutter Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen in Wayland Status in Linux: New Status in Mutter: New Status in X.Org X server: Fix Released Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: In Progress Status in linux source package in Mantic: Confirmed Status in mutter source package in Mantic: In Progress Bug description: I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. All works in xorg. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 22:32:22 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-03 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037076] [NEW] System Details incorrectly shows multiple GPUs
Public bug reported: My system has multiple GPUs: 00:02.0 Display controller: Intel Corporation HD Graphics 630 (rev 04) 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Polaris 22 XT [Radeon RX Vega M GH] (rev c0) 40:00.0 VGA compatible controller: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] (rev a1) It's an Intel Hades Canyon NUC with an external GPU in an enclosure. But it's equally valid to have multiple different GPUs in one desktop computer. What happens (see screenshot) In GNOME Control Center, the System Details overlay lists them as: -- Graphics NVIDIA GeForce GTX 1080 Ti Graphics 1 NVIDIA GeForce GTX 1080 Ti Graphics 2 NVIDIA GeForce GTX 1080 Ti -- Expected outcome I would expect each GPU to be displayed correctly. -- Graphics 1 NVIDIA GeForce GTX 1080 Ti Graphics 2 Intel HD Graphics 630 Graphics 3 AMD ATI Radeon RX Vega M GH -- ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-control-center 1:45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Sep 22 11:41:21 2023 InstallationDate: Installed on 2023-08-06 (47 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-control-center UpgradeStatus: Upgraded to mantic on 2023-09-18 (4 days ago) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic ** Attachment added: "Screenshot from 2023-09-22 11-39-20.png" https://bugs.launchpad.net/bugs/2037076/+attachment/5703519/+files/Screenshot%20from%202023-09-22%2011-39-20.png -- 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/2037076 Title: System Details incorrectly shows multiple GPUs Status in gnome-control-center package in Ubuntu: New Bug description: My system has multiple GPUs: 00:02.0 Display controller: Intel Corporation HD Graphics 630 (rev 04) 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Polaris 22 XT [Radeon RX Vega M GH] (rev c0) 40:00.0 VGA compatible controller: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] (rev a1) It's an Intel Hades Canyon NUC with an external GPU in an enclosure. But it's equally valid to have multiple different GPUs in one desktop computer. What happens (see screenshot) In GNOME Control Center, the System Details overlay lists them as: -- Graphics NVIDIA GeForce GTX 1080 Ti Graphics 1 NVIDIA GeForce GTX 1080 Ti Graphics 2 NVIDIA GeForce GTX 1080 Ti -- Expected outcome I would expect each GPU to be displayed correctly. -- Graphics 1 NVIDIA GeForce GTX 1080 Ti Graphics 2 Intel HD Graphics 630 Graphics 3 AMD ATI Radeon RX Vega M GH -- ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-control-center 1:45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Sep 22 11:41:21 2023 InstallationDate: Installed on 2023-08-06 (47 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-control-center UpgradeStatus: Upgraded to mantic on 2023-09-18 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2037076/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037076] Re: System Details incorrectly shows multiple GPUs
** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #2662 https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2662 ** Also affects: gnome-control-center via https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2662 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/2037076 Title: System Details incorrectly shows multiple GPUs Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: New Bug description: My system has multiple GPUs: 00:02.0 Display controller: Intel Corporation HD Graphics 630 (rev 04) 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Polaris 22 XT [Radeon RX Vega M GH] (rev c0) 40:00.0 VGA compatible controller: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] (rev a1) It's an Intel Hades Canyon NUC with an external GPU in an enclosure. But it's equally valid to have multiple different GPUs in one desktop computer. What happens (see screenshot) In GNOME Control Center, the System Details overlay lists them as: -- Graphics NVIDIA GeForce GTX 1080 Ti Graphics 1 NVIDIA GeForce GTX 1080 Ti Graphics 2 NVIDIA GeForce GTX 1080 Ti -- Expected outcome I would expect each GPU to be displayed correctly. -- Graphics 1 NVIDIA GeForce GTX 1080 Ti Graphics 2 Intel HD Graphics 630 Graphics 3 AMD ATI Radeon RX Vega M GH -- ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-control-center 1:45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Sep 22 11:41:21 2023 InstallationDate: Installed on 2023-08-06 (47 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-control-center UpgradeStatus: Upgraded to mantic on 2023-09-18 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/2037076/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1732482] Re: [snap] doesn't properly save desktop files for "create shortcuts" action
A. Tested https://signals.rotor-rig.com/ with stable version snap x64 (117.0.5938.88): File chrome-pdplehbldmmknfihajdehomkoigcbhib-Default.desktop was created in ~/Desktop #!/usr/bin/env xdg-open [Desktop Entry] Version=1.0 Terminal=false Type=Application Name=Signals Exec=/snap/bin/chromium --profile-directory=Default --app-id=pdplehbldmmknfihajdehomkoigcbhib Icon=chrome-pdplehbldmmknfihajdehomkoigcbhib-Default StartupWMClass=crx_pdplehbldmmknfihajdehomkoigcbhib No file was created in ~/.local/share/applications . So, it's not possible to find it in the launcher File icon in desktop has no icon and allow launching needs to be clicked, worked after that. App had no icon. B. Tested in snap beta (118.0.5993.11) File was not created in ~/Desktop , so no Desktop Icon File chrome-pdplehbldmmknfihajdehomkoigcbhib-Default.desktop was created in ~/.local/share/applications #!/usr/bin/env xdg-open [Desktop Entry] Version=1.0 Terminal=false Type=Application Name=Signals Exec=/snap/bin/chromium --profile-directory=Default --app-id=pdplehbldmmknfihajdehomkoigcbhib Icon=chrome-pdplehbldmmknfihajdehomkoigcbhib-Default StartupWMClass=crx_pdplehbldmmknfihajdehomkoigcbhib App was available in Ubuntu Launcher. C. Tested in edge (118.0.5993.11) Same behavior than Beta, file in ~/Desktop was not created but it was created in ~/.local/share/applications In all 3 cases the dock never showed the App icon when I opened the app but the Chromium Icon. I don't know if this could be fixed as if I open any PWA and then I want to open Chromium, it will show the PWA window and not open a Chromium window. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1732482 Title: [snap] doesn't properly save desktop files for "create shortcuts" action Status in chromium-browser package in Ubuntu: Fix Committed Bug description: For chrome apps, the create shortcuts action should create desktop files but it doesn't. I suspect it has something to do with paths. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1732482/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037088] [NEW] While using secondary display - Top right display not responsive
Public bug reported: While I am using my laptop (main screen) and have my secondary screen plugged in I cannot click anything in the top right corner. Ether in toolbar or top right pixels of an open app. Problem occuring on Mantic Minotaur beta, working on lunar. Freshed installed Ubuntu with defauls. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: mantic -- 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/2037088 Title: While using secondary display - Top right display not responsive Status in gnome-shell package in Ubuntu: New Bug description: While I am using my laptop (main screen) and have my secondary screen plugged in I cannot click anything in the top right corner. Ether in toolbar or top right pixels of an open app. Problem occuring on Mantic Minotaur beta, working on lunar. Freshed installed Ubuntu with defauls. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037088/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1732482] Re: [snap] doesn't properly save desktop files for "create shortcuts" action
Thanks for testing! Julian, I think you already know that and just wanted to perform thorough testing, but in case it was not clear, the fix is not yet in stable. Yet you noted something in test case A: > File chrome-pdplehbldmmknfihajdehomkoigcbhib-Default.desktop was created in ~/Desktop Did you expect that? I'd assume that is the wrong behavior but then I don't use PWAs. What you describe in cases B and C is (what I believe to be) the expected behavior. > In all 3 cases the dock never showed the App icon when I opened the app but the Chromium Icon. I don't know if this could be fixed as if I open any PWA and then I want to open Chromium, it will show the PWA window and not open a Chromium window. That is a known issue but with Gnome Shell (c.f. LP:#2007652 for that); it doesn't happen in other desktop environments (tested Unity, Icewm). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1732482 Title: [snap] doesn't properly save desktop files for "create shortcuts" action Status in chromium-browser package in Ubuntu: Fix Committed Bug description: For chrome apps, the create shortcuts action should create desktop files but it doesn't. I suspect it has something to do with paths. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1732482/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1732482] Re: [snap] doesn't properly save desktop files for "create shortcuts" action
WBGSReject, you seem to have tested stable! And apparently you observed the same as Julian (#34) in test A. So I also extend my question to you: Do you expect the PWA on the desktop or as a launcher? I'll be investigating if there is any consensus on that, but otherwise I might simply combine the two approaches, namely creating both a desktop launcher (~/Desktop) and a dock/activities/menu launcher (~/.local/share/applications). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1732482 Title: [snap] doesn't properly save desktop files for "create shortcuts" action Status in chromium-browser package in Ubuntu: Fix Committed Bug description: For chrome apps, the create shortcuts action should create desktop files but it doesn't. I suspect it has something to do with paths. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1732482/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037076] Re: System Details incorrectly shows multiple GPUs
** 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/2037076 Title: System Details incorrectly shows multiple GPUs Status in gnome-control-center: New Status in gnome-control-center package in Ubuntu: New Bug description: My system has multiple GPUs: 00:02.0 Display controller: Intel Corporation HD Graphics 630 (rev 04) 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Polaris 22 XT [Radeon RX Vega M GH] (rev c0) 40:00.0 VGA compatible controller: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] (rev a1) It's an Intel Hades Canyon NUC with an external GPU in an enclosure. But it's equally valid to have multiple different GPUs in one desktop computer. What happens (see screenshot) In GNOME Control Center, the System Details overlay lists them as: -- Graphics NVIDIA GeForce GTX 1080 Ti Graphics 1 NVIDIA GeForce GTX 1080 Ti Graphics 2 NVIDIA GeForce GTX 1080 Ti -- Expected outcome I would expect each GPU to be displayed correctly. -- Graphics 1 NVIDIA GeForce GTX 1080 Ti Graphics 2 Intel HD Graphics 630 Graphics 3 AMD ATI Radeon RX Vega M GH -- ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-control-center 1:45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Sep 22 11:41:21 2023 InstallationDate: Installed on 2023-08-06 (47 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-control-center UpgradeStatus: Upgraded to mantic on 2023-09-18 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/2037076/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037088] Re: While using secondary display - Top right display not responsive
Seems to be when I have a program open maximised -- 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/2037088 Title: While using secondary display - Top right display not responsive Status in gnome-shell package in Ubuntu: New Bug description: While I am using my laptop (main screen) and have my secondary screen plugged in I cannot click anything in the top right corner. Ether in toolbar or top right pixels of an open app. Problem occuring on Mantic Minotaur beta, working on lunar. Freshed installed Ubuntu with defauls. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037088/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037093] [NEW] Chromium glitches and images/stylesheets not loading well
Public bug reported: Hello, I am using Chromium installed through the software center. Running Ubuntu LTS 22.04.2 on a Lenovo ThinkPad T14 Gen 1. The app has several glitches, screen breaks and crashes. Upon reloading some stylesheets and images don't load correctly. Happy to add more screenshots or help test/reproduce. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Attachment added: "example of stylesheet issue" https://bugs.launchpad.net/bugs/2037093/+attachment/5703565/+files/Screenshot%20from%202023-09-22%2010-00-48.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2037093 Title: Chromium glitches and images/stylesheets not loading well Status in chromium-browser package in Ubuntu: New Bug description: Hello, I am using Chromium installed through the software center. Running Ubuntu LTS 22.04.2 on a Lenovo ThinkPad T14 Gen 1. The app has several glitches, screen breaks and crashes. Upon reloading some stylesheets and images don't load correctly. Happy to add more screenshots or help test/reproduce. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2037093/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037076] Re: System Details incorrectly shows multiple GPUs
Thanks for the report and for opening it also upstream. What's the output of $ switcherooctl on your system? ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-control-center (Ubuntu) Status: New => Incomplete -- 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/2037076 Title: System Details incorrectly shows multiple GPUs Status in gnome-control-center: New Status in gnome-control-center package in Ubuntu: Incomplete Bug description: My system has multiple GPUs: 00:02.0 Display controller: Intel Corporation HD Graphics 630 (rev 04) 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Polaris 22 XT [Radeon RX Vega M GH] (rev c0) 40:00.0 VGA compatible controller: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] (rev a1) It's an Intel Hades Canyon NUC with an external GPU in an enclosure. But it's equally valid to have multiple different GPUs in one desktop computer. What happens (see screenshot) In GNOME Control Center, the System Details overlay lists them as: -- Graphics NVIDIA GeForce GTX 1080 Ti Graphics 1 NVIDIA GeForce GTX 1080 Ti Graphics 2 NVIDIA GeForce GTX 1080 Ti -- Expected outcome I would expect each GPU to be displayed correctly. -- Graphics 1 NVIDIA GeForce GTX 1080 Ti Graphics 2 Intel HD Graphics 630 Graphics 3 AMD ATI Radeon RX Vega M GH -- ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-control-center 1:45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Sep 22 11:41:21 2023 InstallationDate: Installed on 2023-08-06 (47 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-control-center UpgradeStatus: Upgraded to mantic on 2023-09-18 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/2037076/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1732482] Re: [snap] doesn't properly save desktop files for "create shortcuts" action
Nathan - yes, I checked stable only. When I first reported this, the desktop icon didn't work at all on stable, so I was pleased to see it working now. I did see the app icon on the desktop though - that seems to differ from Julian's tests. Seeing it work on the desktop was good. Of course it would be even better if it worked as a launcher. Having the PWA install to both desktop and launcher might be confusing. When an Ubuntu application is installed it appears as a launcher, so that is what I think would be best for a PWA too IMHO. On Fri, 22 Sept 2023 at 13:51, Nathan Teodosio <1732...@bugs.launchpad.net> wrote: > WBGSReject, you seem to have tested stable! And apparently you observed > the same as Julian (#34) in test A. So I also extend my question to you: > Do you expect the PWA on the desktop or as a launcher? > > I'll be investigating if there is any consensus on that, but otherwise I > might simply combine the two approaches, namely creating both a desktop > launcher (~/Desktop) and a dock/activities/menu launcher > (~/.local/share/applications). > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1863897). > https://bugs.launchpad.net/bugs/1732482 > > Title: > [snap] doesn't properly save desktop files for "create shortcuts" > action > > Status in chromium-browser package in Ubuntu: > Fix Committed > > Bug description: > For chrome apps, the create shortcuts action should create desktop > files but it doesn't. I suspect it has something to do with paths. > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1732482/+subscriptions > > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1732482 Title: [snap] doesn't properly save desktop files for "create shortcuts" action Status in chromium-browser package in Ubuntu: Fix Committed Bug description: For chrome apps, the create shortcuts action should create desktop files but it doesn't. I suspect it has something to do with paths. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1732482/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2036611] Re: FFe: Mesa 23.2.0
Given that this is required for hardware support, rc3 is tested already in Debian and other distros, Mantic is an interim release, and also taking into account Timo's familiarity with the package (see d/changelog), I'm +1 with this request. I also tested the PPA packages and they worked fine for me. +1 also for the plan to SRU upstream release up to .0 and then follow the normal SRU policy. For reference, a similar request was handled in LP: #1990387, and approved with a similar rationale. FFe approved. ** Changed in: mesa (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2036611 Title: FFe: Mesa 23.2.0 Status in mesa package in Ubuntu: Triaged Bug description: Upstream still hasn't released Mesa 23.2.0 (as of Sep 19th) which is almost seven weeks past it's original release date. But at least we have an rc3 which is "only" two weeks old. Yes, we are getting close to mantic release but this series is something we want for Intel Meteor Lake support. This is now fresh in Debian unstable, and has been in Fedora 39 for a month already without any apparent drama. Build available at the x-staging ppa https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging/+packages xnox: Separately to amd64, this new mesa would also be useful on many arm64 platforms with a lot of improvements for RaspberryPi, Ubuntu Concept X13s, and Apple / Asahi hardware. I strongly request that upgrade of mesa is also considered because of the Arm platform improvements in Mesa 23.2.0. The request is to ship rc, SRU upto final upstream GA .0 release, and enforce SRU policy after that. Other distributions are also shipping this Mesa RC largely due to the very same reasons, thus this will align hardware compatiblity and performance with other distributions launching this autumn. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2036611/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037093] Re: Chromium glitches and images/stylesheets not loading well
Thanks for the report, Gloria. Can you please run 'apport-collect 2037093'? Is the issue reproducible if you disable hardware acceleration, i.e. 'chromium --disable-gpu'? What if you revert to the previous revision with 'snap revert chromium'? Does Chromium report something suspicious in stderr? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2037093 Title: Chromium glitches and images/stylesheets not loading well Status in chromium-browser package in Ubuntu: New Bug description: Hello, I am using Chromium installed through the software center. Running Ubuntu LTS 22.04.2 on a Lenovo ThinkPad T14 Gen 1. The app has several glitches, screen breaks and crashes. Upon reloading some stylesheets and images don't load correctly. Happy to add more screenshots or help test/reproduce. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2037093/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2035016] Re: one of 3 monitors "frozen" when a window moves there
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1441#note_1851306 ** Changed in: mutter (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2035016 Title: one of 3 monitors "frozen" when a window moves there Status in mutter package in Ubuntu: Fix Committed Bug description: When I move a window to one of my 3 monitors (not the main display), the monitor freezes. That means that moving the mouse there doesn't work and the picture is frozen on that monitor (including the mouse pointer which is visible there). The journal has those logs: Sep 10 07:21:49 clown-t14 gnome-shell[5640]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed Sep 10 07:21:49 clown-t14 systemd[5341]: Started vte-spawn-99883356-4f85-429c-a61b-60abac42.scope - VTE child process 15895 launched by kgx process 7379. Sep 10 07:22:00 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 10 07:22:05 clown-t14 gnome-shell[5640]: Object .Gjs_ui_workspaceThumbnail_ThumbnailsBox (0x55b07b31e510), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Sep 10 07:22:05 clown-t14 gnome-shell[5640]: == Stack trace for context 0x55b0777837f0 == Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #0 7ffe4d1d5260 b resource:///org/gnome/shell/ui/workspacesView.js:646 (276d81d44970 @ 33) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #1 7ffe4d1d53b0 b resource:///org/gnome/shell/ui/workspacesView.js:693 (276d81d44a10 @ 472) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #2 55b07789ddb8 i resource:///org/gnome/shell/ui/workspace.js:856 (276d81d040b0 @ 369) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #3 55b07789dd30 i resource:///org/gnome/shell/ui/workspace.js:808 (9aad18f9fb0 @ 17) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #4 55b07789dc98 i resource:///org/gnome/shell/ui/workspacesView.js:1014 (276d81d45420 @ 129) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #5 55b07789dc08 i resource:///org/gnome/shell/ui/overviewControls.js:699 (9aad188a100 @ 50) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #6 55b07789db80 i resource:///org/gnome/shell/ui/layout.js:372 (793307f55b0 @ 22) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #7 55b07789daf0 i resource:///org/gnome/shell/ui/overview.js:652 (9aad1885f10 @ 190) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #8 55b07789da70 i resource:///org/gnome/shell/ui/overview.js:635 (9aad1885ec0 @ 12) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #9 55b07789d9f0 i resource:///org/gnome/shell/ui/overviewControls.js:750 (9aad188a330 @ 55) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #10 7ffe4d1dc560 b resource:///org/gnome/shell/ui/environment.js:84 (7933077d560 @ 39) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #11 55b07789d968 i resource:///org/gnome/shell/ui/environment.js:250 (7933077da60 @ 14) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #12 55b07789d8d8 i resource:///org/gnome/shell/ui/init.js:21 (7933077d060 @ 48) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: == Stack trace for context 0x55b0777837f0 == Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #0 7ffe4d1d53b0 b resource:///org/gnome/shell/ui/workspacesView.js:695 (276d81d44a10 @ 489) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #1 55b07789ddb8 i resource:///org/gnome/shell/ui/workspace.js:856 (276d81d040b0 @ 369) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #2 55b07789dd30 i resource:///org/gnome/shell/ui/workspace.js:808 (9aad18f9fb0 @ 17) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #3 55b07789dc98 i resource:///org/gnome/shell/ui/workspacesView.js:1014 (276d81d45420 @ 129) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #4 55b07789dc08 i resource:///org/gnome/shell/ui/overviewControls.js:699 (9aad188a100 @ 50) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #5 55b07789db80 i resource:///org/gnome/shell/ui/layout.js:372 (793307f55b0 @ 22) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #6 55b07789daf0 i resource:///org/gnome/shell/ui/overview.js:652 (9aad1885f10 @ 190) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #7 55b07789da70 i resource:///org/gnome/shell/ui/overview.js:635 (9aad1885ec0 @ 12) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #8 55b07789d9f0 i resource:///org/gnome/shell/ui/overviewControls.js:
[Desktop-packages] [Bug 2037115] [NEW] Focus is not given when a new window is launched from overview
Public bug reported: Ubuntu 23.04 Lunar Mutter 44.3 upstream bug https://gitlab.gnome.org/GNOME/mutter/-/issues/2690 >From the upstream bug: "When opening a new app window from the overview, the window focus is not properly given to the new window and the user input still go to the old focused window. Both windows appear to be in focus, however, the old window has the proper focus." This may cause data loss or security issues due to input still going to another application if the user is not aware. This appears to be fixed in the latest mutter release 44.5, any chance we can get this in Lunar? Thanks. ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Description changed: + Ubuntu 23.04 Lunar + Mutter 44.3 + upstream bug https://gitlab.gnome.org/GNOME/mutter/-/issues/2690 From the upstream bug: "When opening a new app window from the overview, the window focus is not properly given to the new window and the user input still go to the old focused window. Both windows appear to be in focus, however, the old window has the proper focus." This may cause data loss or security issues due to input still going to another application if the user is not aware. This appears to be fixed in the latest mutter release 44.5, any chance we can get this in Lunar? Thanks. -- 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/2037115 Title: Focus is not given when a new window is launched from overview Status in mutter package in Ubuntu: New Bug description: Ubuntu 23.04 Lunar Mutter 44.3 upstream bug https://gitlab.gnome.org/GNOME/mutter/-/issues/2690 From the upstream bug: "When opening a new app window from the overview, the window focus is not properly given to the new window and the user input still go to the old focused window. Both windows appear to be in focus, however, the old window has the proper focus." This may cause data loss or security issues due to input still going to another application if the user is not aware. This appears to be fixed in the latest mutter release 44.5, any chance we can get this in Lunar? Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2037115/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990341] Re: [SRU] Support to install nvidia driver by allowing list
The jammy debdiff in comment #25 was based on some local copy of ubuntu-
drivers-common so contained a different changelog entry, than what is in
-proposed, for version 1:0.9.6.2~0.22.04.5 with "Let OEM image can
locally" vs "Let OEM image locally" and different date. Given that these
two changes were trivial to fix up locally I've done just that.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1990341
Title:
[SRU] Support to install nvidia driver by allowing list
Status in OEM Priority Project:
Triaged
Status in ubuntu-drivers-common package in Ubuntu:
Fix Released
Status in ubuntu-drivers-common source package in Jammy:
Confirmed
Status in ubuntu-drivers-common source package in Lunar:
Confirmed
Bug description:
[ Impact ]
* In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to
OEM/ODM for production.
In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA)
to use a specific nvidia version to development/production.
NVIDIA and OEN/ODM will announce the next generation combination at
the same time usually when the factory ready to ship the product.
We made Ubuntu as a leading distribution supports many cutting edge
devices, it's time to have an official way to make the nvidia
installation consistent in unannounced (yet) nvidia devices to support
OEM/ODM factory shipment for our growing counterparts.
[ Test Plan ]
* Steps to make sure it works:
1. pick a cutting edge nvidia graphic.
2. remove nv-525 from the pool by removing restricted in jammy-updates and
jammy-security
3. check the nv support status:
```
$ ubuntu-drivers list
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
```
4. modify custom file
```
$ cat /etc/custom_supported_gpus.json
{
"chips": [
{
"devid": "0x24BA",
"name": "TEST 24BA",
"branch": "580.1234",
"features": [
"runtimepm"
]
},
{
"devid": "0x25BC",
"name": "TEST 25BC",
"branch": "510",
"features": [
"runtimepm"
]
}
]
}
```
5. make sure the hook works
```
$ ubuntu-drivers list
nvidia-driver-510, (kernel modules provided by nvidia-dkms-510)
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
[ Where problems could occur ]
* This feature only impact target system has a custom file
"/etc/custom_supported_gpus.json". And it won't generate automatically
which should not impact normal users
[ Other Info ]
* the patches are picked from
-
https://github.com/tseliot/ubuntu-drivers-common/commit/ec675fba22c68932da9fae95e0f4f2fd10732bf3
-
https://github.com/tseliot/ubuntu-drivers-common/commit/4776c6b9f78411ef3b269a28e9546e4ffd2b7115
-
https://github.com/tseliot/ubuntu-drivers-common/commit/83528313da84b55c04daa62b5edcbf823e5c067b.
* Discussion is in https://github.com/tseliot/ubuntu-drivers-common/pull/71
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1990341/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990341] Re: [SRU] Support to install nvidia driver by allowing list
I sponsored the changes for both Jammy and Lunar.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1990341
Title:
[SRU] Support to install nvidia driver by allowing list
Status in OEM Priority Project:
Triaged
Status in ubuntu-drivers-common package in Ubuntu:
Fix Released
Status in ubuntu-drivers-common source package in Jammy:
Confirmed
Status in ubuntu-drivers-common source package in Lunar:
Confirmed
Bug description:
[ Impact ]
* In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to
OEM/ODM for production.
In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA)
to use a specific nvidia version to development/production.
NVIDIA and OEN/ODM will announce the next generation combination at
the same time usually when the factory ready to ship the product.
We made Ubuntu as a leading distribution supports many cutting edge
devices, it's time to have an official way to make the nvidia
installation consistent in unannounced (yet) nvidia devices to support
OEM/ODM factory shipment for our growing counterparts.
[ Test Plan ]
* Steps to make sure it works:
1. pick a cutting edge nvidia graphic.
2. remove nv-525 from the pool by removing restricted in jammy-updates and
jammy-security
3. check the nv support status:
```
$ ubuntu-drivers list
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
```
4. modify custom file
```
$ cat /etc/custom_supported_gpus.json
{
"chips": [
{
"devid": "0x24BA",
"name": "TEST 24BA",
"branch": "580.1234",
"features": [
"runtimepm"
]
},
{
"devid": "0x25BC",
"name": "TEST 25BC",
"branch": "510",
"features": [
"runtimepm"
]
}
]
}
```
5. make sure the hook works
```
$ ubuntu-drivers list
nvidia-driver-510, (kernel modules provided by nvidia-dkms-510)
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
[ Where problems could occur ]
* This feature only impact target system has a custom file
"/etc/custom_supported_gpus.json". And it won't generate automatically
which should not impact normal users
[ Other Info ]
* the patches are picked from
-
https://github.com/tseliot/ubuntu-drivers-common/commit/ec675fba22c68932da9fae95e0f4f2fd10732bf3
-
https://github.com/tseliot/ubuntu-drivers-common/commit/4776c6b9f78411ef3b269a28e9546e4ffd2b7115
-
https://github.com/tseliot/ubuntu-drivers-common/commit/83528313da84b55c04daa62b5edcbf823e5c067b.
* Discussion is in https://github.com/tseliot/ubuntu-drivers-common/pull/71
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1990341/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037121] [NEW] Freeze when going full screen while watching video
Public bug reported: Hi. The screen freezes when I switch a running video into fullscreen mode. It happens with Gnome Totem, VLC, Firefox, so the issue is not connected to a certain app. I can hear the audio playing in the background while the video output gets stuck. The keyboard keeps working but switching to another app via keyboard doesn't work because the screen keeps stuck with the video. Way to reproduce: 1) Boot Ubuntu 2) Close lid and let the laptop go to sleep mode 3) Open the lid and login 4) Start a random video on Youtube/VLC/Totem 5) Switch to fullscreen -> Immediate freeze of the screen Workaround after the video froze: 1) Press ESC key to leave the full screen mode of the video 2) Close the lid 3) Wait until the laptop goes into sleep mode 4) Open the lid and login again Step 1) is necessary to leave the fullscreen before going to sleep. Otherwise after sleep and logging in again the screen gets stuck again immediately because the video is continued in fullscreen. Syslog tell me this: gnome-shell[1744]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed Ubuntu 23.10 beta with all updates of 22.09.2023 Ryzen 7 PRO 6850U Kernel 6.5.0-5-generic ** Affects: mutter Importance: Undecided Status: New ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd freeze gnome mutter shell ** Also affects: mutter Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2037121 Title: Freeze when going full screen while watching video Status in Mutter: New Status in mutter package in Ubuntu: New Bug description: Hi. The screen freezes when I switch a running video into fullscreen mode. It happens with Gnome Totem, VLC, Firefox, so the issue is not connected to a certain app. I can hear the audio playing in the background while the video output gets stuck. The keyboard keeps working but switching to another app via keyboard doesn't work because the screen keeps stuck with the video. Way to reproduce: 1) Boot Ubuntu 2) Close lid and let the laptop go to sleep mode 3) Open the lid and login 4) Start a random video on Youtube/VLC/Totem 5) Switch to fullscreen -> Immediate freeze of the screen Workaround after the video froze: 1) Press ESC key to leave the full screen mode of the video 2) Close the lid 3) Wait until the laptop goes into sleep mode 4) Open the lid and login again Step 1) is necessary to leave the fullscreen before going to sleep. Otherwise after sleep and logging in again the screen gets stuck again immediately because the video is continued in fullscreen. Syslog tell me this: gnome-shell[1744]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed Ubuntu 23.10 beta with all updates of 22.09.2023 Ryzen 7 PRO 6850U Kernel 6.5.0-5-generic To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2037121/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037121] Re: Freeze when going full screen while watching video
** Description changed: Hi. The screen freezes when I switch a running video into fullscreen mode. It happens with Gnome Totem, VLC, Firefox, so the issue is not connected to a certain app. I can hear the audio playing in the background while the video output gets stuck. The keyboard keeps working but switching to another app via keyboard doesn't work because the screen keeps stuck with the video. Way to reproduce: 1) Boot Ubuntu 2) Close lid and let the laptop go to sleep mode 3) Open the lid and login 4) Start a random video on Youtube/VLC/Totem 5) Switch to fullscreen -> Immediate freeze of the screen Workaround after the video froze: - 1) Press ESC key to leave the full screen mode of the video + 1) Press ESC key (As if you would usually leave the fullscreen mode, however, the screen will stay stuck) 2) Close the lid 3) Wait until the laptop goes into sleep mode 4) Open the lid and login again Step 1) is necessary to leave the fullscreen before going to sleep. Otherwise after sleep and logging in again the screen gets stuck again immediately because the video is continued in fullscreen. Syslog tell me this: gnome-shell[1744]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed - Ubuntu 23.10 beta with all updates of 22.09.2023 Ryzen 7 PRO 6850U Kernel 6.5.0-5-generic -- 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/2037121 Title: Freeze when going full screen while watching video Status in Mutter: New Status in mutter package in Ubuntu: New Bug description: Hi. The screen freezes when I switch a running video into fullscreen mode. It happens with Gnome Totem, VLC, Firefox, so the issue is not connected to a certain app. I can hear the audio playing in the background while the video output gets stuck. The keyboard keeps working but switching to another app via keyboard doesn't work because the screen keeps stuck with the video. Way to reproduce: 1) Boot Ubuntu 2) Close lid and let the laptop go to sleep mode 3) Open the lid and login 4) Start a random video on Youtube/VLC/Totem 5) Switch to fullscreen -> Immediate freeze of the screen Workaround after the video froze: 1) Press ESC key (As if you would usually leave the fullscreen mode, however, the screen will stay stuck) 2) Close the lid 3) Wait until the laptop goes into sleep mode 4) Open the lid and login again Step 1) is necessary to leave the fullscreen before going to sleep. Otherwise after sleep and logging in again the screen gets stuck again immediately because the video is continued in fullscreen. Syslog tell me this: gnome-shell[1744]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed Ubuntu 23.10 beta with all updates of 22.09.2023 Ryzen 7 PRO 6850U Kernel 6.5.0-5-generic To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2037121/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2033433] Re: Chromium leaks tens of gigabytes of pixmaps (in the Xorg process) after using hardware accelerated video
Upstream bug got an update: https://bugs.chromium.org/p/chromium/issues/detail?id=1467689#c41 Patch? https://chromium.googlesource.com/chromium/src/+/42d57d016f5fb6d2a1a354743b9be911c1be87e8%5E%21/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2033433 Title: Chromium leaks tens of gigabytes of pixmaps (in the Xorg process) after using hardware accelerated video Status in chromium-browser package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Opinion Bug description: https://crbug.com/1467689 --- chromium 118.0.5966.0 2604 latest/edge Whenever I use chromium in a video session (meet, youtube) that used hardware acceleration, for a long time (like 20min or more), and then close it, the whole desktop freezes, and the laptop fan turns on. Logging in remotely I see that Xorg is at 100% CPU. The rest of the system is operational, but nothing graphical is. Just the mouse cursor moves around. SOMETIMES, if I wait a few minutes, Xorg resumes behaving normally, and I can use the desktop again, but most of the time I have to login remotely and kill -9 xorg (plain kill won't do it). With wayland, this does not happen. This could very well be an Xorg bug, but filing here first for visibility. $ lsgpu card0Intel Alderlake_p (Gen12) drm:/dev/dri/card0 └─renderD128 $ lscpu Architecture:x86_64 CPU op-mode(s):32-bit, 64-bit Address sizes: 46 bits physical, 48 bits virtual Byte Order:Little Endian CPU(s): 16 On-line CPU(s) list: 0-15 Vendor ID: GenuineIntel Model name:12th Gen Intel(R) Core(TM) i7-1270P CPU family: 6 Model: 154 Thread(s) per core: 2 Core(s) per socket: 12 Socket(s): 1 Stepping:3 CPU(s) scaling MHz: 41% CPU max MHz: 4800, CPU min MHz: 400, BogoMIPS:4992,00 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdp e1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqd q dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave a vx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept_ ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid rdseed adx smap clflushopt clwb intel_pt sha_ni xsaveopt xsavec xgetbv1 xsaves split_lock_detect avx_vnni dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp hwp_pkg_req hfi umip pku ospke waitpkg gfni vaes vpclmulqdq tme rdpid movdiri movdir64b fsrm md_clear serialize pconfig arch_lbr ibt flush_l1d arch_capabilities Virtualization features: Virtualization:VT-x Caches (sum of all): L1d: 448 KiB (12 instances) L1i: 640 KiB (12 instances) L2:9 MiB (6 instances) L3:18 MiB (1 instance) NUMA: NUMA node(s): 1 NUMA node0 CPU(s): 0-15 Vulnerabilities: Itlb multihit: Not affected L1tf: Not affected Mds: Not affected Meltdown: Not affected Mmio stale data: Not affected Retbleed: Not affected Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl Spectre v1:Mitigation; usercopy/swapgs barriers and __user pointer sanitization Spectre v2:Mitigation; Enhanced IBRS, IBPB conditional, RSB filling, PBRSB-eIBRS SW sequence Srbds: Not affected Tsx async abort: Not affected ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 6.2.0-27.28-generic 6.2.15 Uname: Linux 6.2.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Aug 29 16:47:30 2023 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2033433/+subscriptions -- Mailing list
[Desktop-packages] [Bug 2036440] Re: Choosing "Try Ubuntu" on daily-legacy image produced a crash
The gnome-shell crash is easily reproducible by choosing Try Ubuntu when using a mantic desktop legacy image. ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2036440/+attachment/5703615/+files/journal.txt -- 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/2036440 Title: Choosing "Try Ubuntu" on daily-legacy image produced a crash Status in apport package in Ubuntu: New Status in gnome-shell package in Ubuntu: Incomplete Bug description: I was booting up a daily-legacy image from 20230918 and received a crash report after choosing "Try Ubuntu". ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~rc-0ubuntu3 Uname: Linux 6.5.0-5-generic x86_64 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 18 15:20:58 2023 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1694375959 ProcCmdline: gnome-shell --sm-disable --mode=ubiquity ProcCwd: /home/ubuntu ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= Signal: 6 SourcePackage: gnome-shell UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2036440/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1993226] Re: mutter autopkgtests fail to detect regressions in mesa
** Tags added: rls-mm-incoming -- 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/1993226 Title: mutter autopkgtests fail to detect regressions in mesa Status in mutter package in Ubuntu: New Bug description: a last-hour upload of mutter for kinetic release fails to build from source on armhf due to what appears to be a regression in mesa's llvmpipe implementation in the mesa 22.2.1-1ubuntu1 build. If this is a regression in mesa, it should have been possible to detect it before mesa was promoted, via autopkgtests in the mutter package. Counterintuitively, mutter declares autopkgtests, but the autopkgtests do NOT test any of the OpenGL functionality via the mutter "nested view". Therefore the regression was only detected at the next upload of mutter, NOT before mesa was promoted to the release, when we want to be catching it. Please fix mutter to ensure that the autopkgtests have at least as much coverage as the build-time tests, which is the right way around. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1993226/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2018555] Re: Nautilus rendering is broken if GTK_THEME env variable exists
This looks fixed in Ubuntu 23.04 and this was reported against Ubuntu 22.10. So, now that Ubuntu 22.10 is not supported, this can be considered fixed. That said, I don't understand why this bug was closed because “there has been no activity for 60 days”. The bug was still reproducible on Ubuntu 22.10 and reproduction instructions properly described. Bugs don't disappear by magic because there is no comment to add. I noticed that setting GTK_THEME to empty string (you also have to export the variable) still changes the way nautilus look in Ubuntu 23.04, but the different look doesn't make nautilus unusable (unlike what happened on Ubuntu 22.10). ``` killall nautilus export GTK_THEME= nautilus ``` I'm not sure what happens on Ubuntu 23.04 is a bug, though. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2018555 Title: Nautilus rendering is broken if GTK_THEME env variable exists Status in nautilus package in Ubuntu: Expired Bug description: In Ubuntu 22.10, nautilus rendering is broken as soon as GTK_THEME environment exists, and there are some other components of GNOME that sets it at desktop launch (for example the Desktop may set it as GTK_THEME=Adwaita:dark). I have found no GTK_THEME value to make nautilus render properly, even the empty string breaks nautilus. How to reproduce: ``` killall nautilus GTK_THEME= nautilus ``` Then try to select some icons, selected icons will not be displayed as selected. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Fri May 5 06:49:41 2023 GsettingsChanges: ProcEnviron: LANGUAGE=fr_FR:en TERM=xterm-256color PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2018-06-16T17:39:00.798346 usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 nautilus-image-converter 0.4.0-2 python3-nautilus 4.0-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2018555/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037141] [NEW] Multi monitor with different scale factors causes windows to use scale factor of adjacent monitor before arriving at boundary
Public bug reported: On a dual/multi monitor setup, if the monitor adjacent uses a different scale factor, when moving an application window to the boundary the application will change its scaling just slightly before the actual apparent window starts crossing over. Taking a look at looking glass shows the transition occurs when the MetaSurfaceActorWayland region (larger than the actual window) meets the boundary. My monitor configuration is: 1920X1080 monitor using 100% scaling 2560X1600 monitor using 150% scaling ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Sep 23 00:22:04 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-31 (540 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) RelatedPackageVersions: mutter-common 45.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland-session ** Attachment added: "Screencast showing point at which scale factor changes" https://bugs.launchpad.net/bugs/2037141/+attachment/5703627/+files/Screencast%20from%202023-09-23%2001-45-20.webm -- 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/2037141 Title: Multi monitor with different scale factors causes windows to use scale factor of adjacent monitor before arriving at boundary Status in gnome-shell package in Ubuntu: New Bug description: On a dual/multi monitor setup, if the monitor adjacent uses a different scale factor, when moving an application window to the boundary the application will change its scaling just slightly before the actual apparent window starts crossing over. Taking a look at looking glass shows the transition occurs when the MetaSurfaceActorWayland region (larger than the actual window) meets the boundary. My monitor configuration is: 1920X1080 monitor using 100% scaling 2560X1600 monitor using 150% scaling ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Sep 23 00:22:04 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-31 (540 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) RelatedPackageVersions: mutter-common 45.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037141/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037141] Re: Multi monitor with different scale factors causes windows to use scale factor of adjacent monitor before arriving at boundary
Screenshot of the looking glass inspector being used to on application window at the point where the scaling changes. ** Attachment added: "Screenshot from 2023-09-23 01-49-27.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037141/+attachment/5703634/+files/Screenshot%20from%202023-09-23%2001-49-27.png -- 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/2037141 Title: Multi monitor with different scale factors causes windows to use scale factor of adjacent monitor before arriving at boundary Status in gnome-shell package in Ubuntu: New Bug description: On a dual/multi monitor setup, if the monitor adjacent uses a different scale factor, when moving an application window to the boundary the application will change its scaling just slightly before the actual apparent window starts crossing over. Taking a look at looking glass shows the transition occurs when the MetaSurfaceActorWayland region (larger than the actual window) meets the boundary. My monitor configuration is: 1920X1080 monitor using 100% scaling 2560X1600 monitor using 150% scaling ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Sep 23 00:22:04 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-31 (540 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) RelatedPackageVersions: mutter-common 45.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037141/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037143] [NEW] Autohide enabled Dock scaling breaks on multi monitor with different scale factors (low to high scale)
Public bug reported: The dock with autohide enabled breaks scaling on multi monitor setups when revealed from a hidden state if it is on the edge of the monitor adjacent to the other monitor where the next monitor has a higher scale factor. In my case the dock is on the monitor with 100% scale factor and the monitor adjacent has 150% scaling. When the bug occurs a bunch of the following messages appear in the log: gnome-shell[4226]: Can't update stage views actor [:0x562389bfc9e0] is on because it needs an allocation. I suspect this could be linked to my findings in this bug: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037141 Attached a screencast demonstrating the bug. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell-extension-ubuntu-dock 87ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Sep 23 01:57:23 2023 InstallationDate: Installed on 2022-03-31 (540 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland-session ** Attachment added: "Screencast from 2023-09-23 02-08-53.webm" https://bugs.launchpad.net/bugs/2037143/+attachment/5703635/+files/Screencast%20from%202023-09-23%2002-08-53.webm ** Description changed: The dock with autohide enabled breaks scaling on multi monitor setups when revealed from a hidden state if it is on the edge of the monitor adjacent to the other monitor where the next monitor has a higher scale factor. - I suspect this could be linked to + When the bug occurs a bunch of the following messages appear in the log: + gnome-shell[4226]: Can't update stage views actor [:0x562389bfc9e0] is on because it needs an allocation. + + I suspect this could be linked to my findings in this bug: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037141 Attached a screencast demonstrating the bug. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell-extension-ubuntu-dock 87ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Sep 23 01:57:23 2023 InstallationDate: Installed on 2022-03-31 (540 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: The dock with autohide enabled breaks scaling on multi monitor setups when revealed from a hidden state if it is on the edge of the monitor adjacent to the other monitor where the next monitor has a higher scale - factor. + factor. In my case the dock is on the monitor with 100% scale factor and + the monitor adjacent has 150% scaling. When the bug occurs a bunch of the following messages appear in the log: gnome-shell[4226]: Can't update stage views actor [:0x562389bfc9e0] is on because it needs an allocation. I suspect this could be linked to my findings in this bug: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037141 Attached a screencast demonstrating the bug. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell-extension-ubuntu-dock 87ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Sep 23 01:57:23 2023 InstallationDate: Installed on 2022-03-31 (540 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/2037143 Title: Autohide enabled Dock scaling breaks on multi monitor with different scale factors (low to high scale) Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: The dock with autohide enabled breaks scaling on multi monitor setups when revealed from a hidden state if it is on the edge of the monitor adjacent to the other monitor where the next monitor has a higher scale factor. In my case the dock is on the monitor with 100% scale factor and the
[Desktop-packages] [Bug 2035016] Re: one of 3 monitors "frozen" when a window moves there
This bug was fixed in the package mutter - 45.0-2ubuntu1 --- mutter (45.0-2ubuntu1) mantic; urgency=medium * Merge with Debian. Remaining changes: - Add x11-Add-support-for-fractional-scaling-using-Randr.patch - Add window-Add-ability-to-override-the-edge-constraints.patch + Make possible for extensions (such as Tiling Assistant) to override window constraints mutter (45.0-2) experimental; urgency=medium [ Daniel van Vugt ] * Update triple buffering patch to fix freezing seen when running apps full screen (LP: #2035016) [ Jeremy Bícha ] * Cherry-pick patch to fix changing input language in modal popups -- Jeremy Bícha Fri, 22 Sep 2023 11:27:59 -0400 ** Changed in: mutter (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2035016 Title: one of 3 monitors "frozen" when a window moves there Status in mutter package in Ubuntu: Fix Released Bug description: When I move a window to one of my 3 monitors (not the main display), the monitor freezes. That means that moving the mouse there doesn't work and the picture is frozen on that monitor (including the mouse pointer which is visible there). The journal has those logs: Sep 10 07:21:49 clown-t14 gnome-shell[5640]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed Sep 10 07:21:49 clown-t14 systemd[5341]: Started vte-spawn-99883356-4f85-429c-a61b-60abac42.scope - VTE child process 15895 launched by kgx process 7379. Sep 10 07:22:00 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 10 07:22:05 clown-t14 gnome-shell[5640]: Object .Gjs_ui_workspaceThumbnail_ThumbnailsBox (0x55b07b31e510), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Sep 10 07:22:05 clown-t14 gnome-shell[5640]: == Stack trace for context 0x55b0777837f0 == Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #0 7ffe4d1d5260 b resource:///org/gnome/shell/ui/workspacesView.js:646 (276d81d44970 @ 33) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #1 7ffe4d1d53b0 b resource:///org/gnome/shell/ui/workspacesView.js:693 (276d81d44a10 @ 472) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #2 55b07789ddb8 i resource:///org/gnome/shell/ui/workspace.js:856 (276d81d040b0 @ 369) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #3 55b07789dd30 i resource:///org/gnome/shell/ui/workspace.js:808 (9aad18f9fb0 @ 17) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #4 55b07789dc98 i resource:///org/gnome/shell/ui/workspacesView.js:1014 (276d81d45420 @ 129) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #5 55b07789dc08 i resource:///org/gnome/shell/ui/overviewControls.js:699 (9aad188a100 @ 50) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #6 55b07789db80 i resource:///org/gnome/shell/ui/layout.js:372 (793307f55b0 @ 22) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #7 55b07789daf0 i resource:///org/gnome/shell/ui/overview.js:652 (9aad1885f10 @ 190) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #8 55b07789da70 i resource:///org/gnome/shell/ui/overview.js:635 (9aad1885ec0 @ 12) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #9 55b07789d9f0 i resource:///org/gnome/shell/ui/overviewControls.js:750 (9aad188a330 @ 55) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #10 7ffe4d1dc560 b resource:///org/gnome/shell/ui/environment.js:84 (7933077d560 @ 39) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #11 55b07789d968 i resource:///org/gnome/shell/ui/environment.js:250 (7933077da60 @ 14) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #12 55b07789d8d8 i resource:///org/gnome/shell/ui/init.js:21 (7933077d060 @ 48) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: == Stack trace for context 0x55b0777837f0 == Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #0 7ffe4d1d53b0 b resource:///org/gnome/shell/ui/workspacesView.js:695 (276d81d44a10 @ 489) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #1 55b07789ddb8 i resource:///org/gnome/shell/ui/workspace.js:856 (276d81d040b0 @ 369) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #2 55b07789dd30 i resource:///org/gnome/shell/ui/workspace.js:808 (9aad18f9fb0 @ 17) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #3 55b07789dc98 i resource:///org/gnome/shell/ui/workspacesView.js:1014 (276d81d45420 @ 129) Sep 10 07:22:05 clown-t14 gn
[Desktop-packages] [Bug 2037093] Re: Chromium glitches and images/stylesheets not loading well
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: chromium-browser (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2037093 Title: Chromium glitches and images/stylesheets not loading well Status in chromium-browser package in Ubuntu: Confirmed Bug description: Hello, I am using Chromium installed through the software center. Running Ubuntu LTS 22.04.2 on a Lenovo ThinkPad T14 Gen 1. The app has several glitches, screen breaks and crashes. Upon reloading some stylesheets and images don't load correctly. Happy to add more screenshots or help test/reproduce. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2037093/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2028311] Re: 22.04 : Default screenshot utility can be triggered from login-screen but useless.
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- 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/2028311 Title: 22.04 : Default screenshot utility can be triggered from login-screen but useless. Status in gnome-shell package in Ubuntu: Expired Bug description: Hi, Ubuntu 22.04 ( Gnome, GDM, Wayland ) Hitting « PrintScreen » key in login-screen launches default « new » screenshot utility. It seems to work, at the end it says « picture has been saved in the paperboard ». But how get hands on that paperboard later ? No picture is saved in /root. I suspect the screenshot utility should not be launch-able from login- screen, as it suggests something impossible to do ( get a screenshot of login-screen. ) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-06-01 (414 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Package: gnome-shell 42.9-0ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17 RelatedPackageVersions: mutter-common 42.9-0ubuntu1 Tags: jammy wayland-session Uname: Linux 5.19.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo users _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2028311/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037093] Re: Chromium glitches and images/stylesheets not loading well
i am having the same issue, running Chromium snap (says Version 117.0.5938.88 (Official Build) snap 64-bit ) on LTS 22.04.3, ASUS ROG Strix G513IC_G with GeForce RTX 3050 GPU my theory what this problem is short version: i think it's very similar to this: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2035360 ALSO, Brave has already fixed the issue! I got a snap update from them about 8 hours ago and YES it fixed it. know anyone on their tech team, who can tell you how they fixed it? ;-);-) longer version: it affects both Brave and Chromium (same rendering engine) symptoms are identical with this: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2020604 (and https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/2035360 IMHO the Sketcher is a red herring as it is not the cause, just where the bug is manifesting) last night i tried some of the fixes suggested in the former, and also this related post: https://askubuntu.com/questions/1469116/since-23-may-2023-ubuntu-22-04-mesa- updates-chrome-wont-display-website-graphi i tried these fixes: MESA_LOADER_DRIVER_OVERRIDE=i965 chromium deleting ~/.config/google-chrome/Default/GPUCache deleting a folder called ShaderCache, from same folder i assume? neither one existed on my machine. also tried using this PPA: https://launchpad.net/~kisak/+archive/ubuntu/kisak-mesa?ref=itsfoss.com and it enabled me to get a newer version of Mesa than what had been provided by Ubuntu (it upgraded to version 23.1.8, sorry i don't remember original version but it definitely changed, i think it was 23.0 something) , ie: whatever Ubuntu would set it to. and... NONE of these fixes worked! now you know what NOT to try :) HOWEVER... this one SORT OF worked: chromium --disable-gpu-driver-bug-workarounds i say "sort of" because my three test pages were: google forms, google sheets and facebook. believe it or not, running it with disable-gpu- driver-bug-workarounds worked, totally fixed the glitches... but for only TWO of those three pages :-( google sheets page is still glitching as before. i have no theories as to why it didn't fix them all. as i said above, Brave seems to have fixed thIs issue already, so that might help you in some way. GOOD LUCK! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2037093 Title: Chromium glitches and images/stylesheets not loading well Status in chromium-browser package in Ubuntu: Confirmed Bug description: Hello, I am using Chromium installed through the software center. Running Ubuntu LTS 22.04.2 on a Lenovo ThinkPad T14 Gen 1. The app has several glitches, screen breaks and crashes. Upon reloading some stylesheets and images don't load correctly. Happy to add more screenshots or help test/reproduce. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2037093/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037093] Re: Chromium glitches and images/stylesheets not loading well
note, i tried to post the bug from my machine, using Apport, into this existing issue. it didn't work that way, it created a new issue: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/2037151 you can see my proc files there if you want. and YES it should have posted to package "chromium-browser", not "gnome- panel", see the issue comments for why. can it be moved to the right department? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2037093 Title: Chromium glitches and images/stylesheets not loading well Status in chromium-browser package in Ubuntu: Confirmed Bug description: Hello, I am using Chromium installed through the software center. Running Ubuntu LTS 22.04.2 on a Lenovo ThinkPad T14 Gen 1. The app has several glitches, screen breaks and crashes. Upon reloading some stylesheets and images don't load correctly. Happy to add more screenshots or help test/reproduce. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2037093/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
